Related
I just reset mytouch 4g phone and during restart the recovery screen just come out but I can't move down or up anything on the screen it just stuck..
I just update cm to version 3 of something
please I really need help on this my phone is already S-off
when I plug the phone with USB it response something by HBOOT has changed to HBOOT USB PLUG
I use Stock Rom just update Kernal only
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Marine6680 said:
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Click to expand...
Click to collapse
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
wibul_10 said:
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
Click to expand...
Click to collapse
In clockwork you use the trackball to navigate. Volume buttons won't work.
Lakeshow423 said:
In clockwork you use the trackball to navigate. Volume buttons won't work.
Click to expand...
Click to collapse
no response on trackball too. it just stuck on this screen and can't move anywhere....any solution
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
jggimi said:
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
Click to expand...
Click to collapse
when I turn the phone on everytime it just show this bootloader and no response on all volume up/down and power button...only way to turn off is to unplug battery ....
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
jggimi said:
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
Click to expand...
Click to collapse
One more question, after following your advice, I found that I now can restart my phone again but when I shut down the phone and turn it on again it still stuck on bootloader screen all the times...any suggestion would be appreciate...
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
jggimi said:
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
Click to expand...
Click to collapse
I can't download it...need new link
anyway thank very much for your help
[SOLVED]
I rooted this, installed clockworkmod, then went and got an cm7 dated april something 2012 u8160 rom from psyke83 website.
installed it through clockworkmod install from sd card option with success (also clicked option to backup everything).
yet when phone reboots it hangs on the blue arrow in a circle spinning around, sometimes reboots n repeats but it never goes past that.
I have tried going into recovery mode holding down volume buttons and power
and I get 1 of 2 errors:
with sd card in:
firmware update
step 1/2
unpacking
update failed
with sd card out:
purple screen.
I am a first time android modder, can someone please, please tell me how to fix this. I can access the sd card with a reader if need be to put whatever files on it that I should.
Thank you.
Start the phone by pressing volume up + power OR volume down + power. You should be able to boot to recovery with one of those combinations (other one boots to fastboot most probably). After that do the wipe data/cache and try to reboot once again.
What was wrong in the beginning was that you did not wipe data/cache. That made the CM use old OS's data files which obviously won't work.
The unpacking thing was caused by pressing volume up + volume down + power. That causes the phone to go to upgrade mode if there is an update package found.
Nope. still goes to the blue arrow circling then freezes then reboots....
mrw187 said:
Nope. still goes to the blue arrow circling then freezes then reboots....
Click to expand...
Click to collapse
You are right about me not wiping the data/cache though...
But in your phone forum, are there tutorials on how to boot to recovery? Do you have any other hard keys on the phone?
there is one other button but that didn't work either.
I cannot find a forum for Huawei model u8180 (
mrw187 said:
there is one other button but that didn't work either.
I cannot find a forum for Huawei model u8180 (
Click to expand...
Click to collapse
Hmm, would this work?
yay!!
it was volume up + power + cancel button (? maybe home button? not sure on what this button is but its the biggest).
wiped all data n cache n then it booted properly.
So the problem is solved? If you can, mark first post title with [SOLVED].
Sent from my U8800 using Tapatalk 2
huaweiU8180 freeze on boot to recovery
I have tried all the solution but failed the problem is my HuaweiU8180 keeps on hanging wen I try booting to recovery mode now I can't format my phone and I can't install a custom ROM even when the phone is rooted and I hav ROM manager premium installed and I flashed CWM but still someone help me please
I'm having reral trouble gettng my n4 into fastboot. all the buttons work, vol up, vol down and the power on all work fine but if I try and press all 3 simultaneously I just boot the device normally. I've managed to get to fast boot just once in 2 dozen tries. what is the trick? I've tried pushing all 3 at once, I've tied pressing both vol up and down, holding thm, then pressing and holding the power button too. always just vibrates, and boots normally.
just now while trying on the last attempt it booted normally but the screen had 'safe mode' in the bottom left corner. that freaked me a bit. turned it off, then on again and it went away. wtf is 'safe mode' and how did I get it?
I want to...I think...root and flash a rom the proper way, step by step using efrant's guide on here, rather than a script from the toolkit, but since I can't seem to get to fastboot I'm stuck
this is all just to get to 4.3 really....I rooted using the toolkit and OTA updates haven't been running so still on 4.2.1 and thought I should sort that out. had a bit of a 'mare l2 nights agot when I unlocked the bootloader to go about returning to stock and forgot that would wipe the device...losing lat weeks holiday photos in the process I think the tool kit and one press type 'unlock, flash this, flash that etc etc' commands lulled me into not thinking for myself so perhaps I ought to do this properly!
BTW, I'm currently with a locked bootloader, stock 4.2.1 rom, stock recovery reflashed, no su binary (cinfirmed by attempting to run SU app, and it not finding the binary). I've been waiting for the OTA update to push to the device again (I've forced checkins but to no avail) to attempt to run it, should it run properly now or have I to do something more?
You need to hold power and volume down, if that doesn't work then try adb reboot boot loader
Sent from my Nexus 4 using Tapatalk 4
justin11141 said:
You need to hold power and volume down, if that doesn't work then try adb reboot boot loader
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
thanks. tried holding volume down and then also power as well and again it booted normally. looks like adb commands it is then. bit of a pain to have to hook to a pc to do this....not that I'm a regular custom rom flasher/swapping between roms and nandroid backups etc but it would be handy....I learnt that with my old desire.
has anyone else had problems getting there holding the buttons?
oh and I found what safe mode is from the google nexus 4 site. a mode where the apps don't work so you can check for problems that they may be causing. how I got to it doesn't match with the descried way though...just a weird glitch I guess.
okay I'm all sorted for now. I used the toolkit and flashed the entire set of stock .img after downloading the archive from google
now on 4.3, and as far as I can see that is with stock recovery, system, radio the lot. I've left it unrooted (so no su binary, no busy box, no su app - although the phone is currently synching and downloading my apps again..I guess this will come too) so if I understand things correctly future OTAs will run.
I've left the bootloader unlocked as efrant, in his 'how to' guide says
'Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all.' and he explains that unlocking in the future to enable fastboot commands to work and hence flash roms in the future results in a wipe of data. So...I think...I'm up to date, stock, safe and future OTAs will run....i hope. I do understand though, that should the device need to back to Google I should relock the bootloader first or they will know I've been playing around (where possibly I shouldn't!)
okay....think I can go ahead and set up again. :victory:
Ooo good! and whatever I've done I can get into the bootloader fine now :victory: simply holding vol down and then pressing and holding the power button now works every time. good.
Please help me. I am in a sort of panic right now.
I have a ZTE Blade C2 v809, sold here in Portugal as Meo Smart A12. It was rooted and working fine. I was however getting some error 24's trying to install apps. I thought this might have had to do with using Titanium Backup to remove TouchPal (I did make a backup first), so I decided to restore TouchPal. There were however some errors in the restore and it was stuck there, so I decided to reboot the phone.
Chaos. Now it wont boot. If I press the button normally, the phone boots, I see the android logo, the screen goes black (Not shutdown black, a sort of light black background) and nothing happens. If I try to boot into Recovery mode by holding the power button and the volume down key, I just get the android logo stuck there, nothing happens. If I hold the power button and the volume up key, I get the picture of that laying down android with the message error.
Any more info I must provide please tell me, I am desperate for a solution, If I lose this phone I wont be able to get another one.
Okay I fixed it. Turns out the recovery menu DID work if I waited for a long time and tapped the screen. Used the update.zip available from the site, and it works like a charm
Yay, I bricked my phone, too.
I did something similar, changed recovery-from-boot.p name to recovery-from-boot.p-bak and install-recovery.sh to install-recovery.sh-bak
Now the phone doesn't boot properly, in fact it's stuck in a boot loop:
>starts
>shows white ZTE logo on screen
>restarts
Tried connecting the phone via USB cable and used fastboot devices & adb devices commands, no devices found.
Also tried pressing "power + vol down" and "power + vol up", nothing. I can't enter recovery mode or bootloader.
Apparently the remaining way to get in it's trough the SD slot, or maybe there's another way.
I kindly ask for help, couldn't be possible that I ruined this cell phone so fast.
Ideas, somebody?
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Dharmost said:
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Click to expand...
Click to collapse
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
D4ND310 said:
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
Click to expand...
Click to collapse
I didn't dip the smartphone into a cup of liquid, i just took a piece of cotton, poured a bit of nail pain remover (don't know the exact name in english, sorry) on it and then scratched the part where the chewing gum was on (on the soft touch back key, which works 100% fine).
I am trying using the method you described, but it seems i can't go into recovery. Maybe i'm not quick enough! will keep trying. If you have any other suggestions i will be glad to hear that!
You could try to make a USB jig, or buy one off of eBay. They're really cheap. Its basicly just a resistens that force the phone to download mode. It have worked fine for all my Sammy's including A310 so it probably works for A (15) series as well.
Just put it in USB connector and press power for a few secs and you should be in download mode.
Just an idea if everything else fails
Sent from my Honor 5X using Tapatalk
go to samsung
A hardware problem could NEVER be fixed by software ways... Unfortunatelly...
It seems that liquid made some changes on your PCB (maybe dissolved some isolators inside??)...
Anyway, go to service or replace it!
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Dharmost said:
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Click to expand...
Click to collapse
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
babyyeobo14 said:
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but still couldn't get into recovery. I think the home button is really broken, therefore i need to access recovery in another way.
Cause i flashed the stock samsung firmware twice with odin and i can't still start the phone properly, every guide says that a wipe of cache and dalvik solves the situation. But i need to get into recovery for that.
I can't go into recovery with normal procedure probably because the home button is not working, and all the guides about adb commands say that you need to plug in your phone when it has fully started. So i either need a way to force the device into recovery with my computer, or a firmware that once flashed doesn't give me bootloop