I just unlocked and re-rooted (verified with root checker) and have tried flashing 3 different CWM recoveries via fastboot and cannot get into recovery. Always says the recovery flashed fine but when booting and trying to select from boot menu it I keep getting the black screen with the green android guy and exclamation mark.
What can I do to get recovery going so I can flash some roms?
*EDIT...I found a solution to this and got it going. Never do this while wrapped up in March Madness.
Same prob only exclamation guy through CM9 install, wiped phone and have no reboot into anything. Now phone won't hold charge enough to fast boot.how did you resolve your issue???
Related
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
Alright guys, I need some help.
I tried installing twrp using adp / fastboot. I thought everything was going well. Everything came up as finish, the blue bar was full for a good 10 min, so I issued the restart command, and crossed my fingers it restarted.
I stared as I hoped I didn't screw something up.... android seemed to load fine and go to the lock screen. I was relieved. :
So, I tried rebooting (PWR + Vol Down) and choose RCK to load twrp. Now it just sits there, at " Booting recovery kernal image" and dosen't go anywhere.
Any ideas?
My goal is to flash AndroWook HairyBean.
Edit
Let me add that I am a novice at this at best. As far as I know, twrp may not have even took? But once I get twrp working, I can flash Hairybean, right?
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
Yesterday I was trying to update my Nexus 5 from 4.4.2 to 4.4.3. It rebooted me into CWM recovery and asked me to install the .zip to update. It finished successfully, but then it asked me something upon rebooting about fixing root that I had not seen before. I clicked "Go Back" but when I did it shut down and now it will not boot android (all I can see if the coloured circles forever) and when I try to enter recovery mode all I can see is an android symbol with its chest open and a red error triangle. So I have no access to android or CWM, and only to fastboot mode. Is my phone bricked or is there a fix?
mrxip1 said:
Yesterday I was trying to update my Nexus 5 from 4.4.2 to 4.4.3. It rebooted me into CWM recovery and asked me to install the .zip to update. It finished successfully, but then it asked me something upon rebooting about fixing root that I had not seen before. I clicked "Go Back" but when I did it shut down and now it will not boot android (all I can see if the coloured circles forever) and when I try to enter recovery mode all I can see is an android symbol with its chest open and a red error triangle. So I have no access to android or CWM, and only to fastboot mode. Is my phone bricked or is there a fix?
Click to expand...
Click to collapse
Don't worry your device is not fully bricked, just soft-bricked. You have two options, since you have access, to fastboot you can reflash a custom recovery and then sideload a custom ROM and flash that in the custom recovery. Or your other option is to use fastboot to flash the stock factory image for Android 4.4.3 for the Nexus 5 which can be found here. Let me know if you still have questions I'll be happy to help you out.
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.