Database Users

[Q] Can't boot into recovery after flashing new CW 3.0.2.4 recovery help!!!

So... I was rooted using gfree method and had recovery 2.5.1.4 installed running the ice glacier rom. Then I decided i was going to upgrade to a gingerbread rom so I updated my rom manager and flashed the new CW 3.0.2.4 rom and now it wont boot into recovery. When I try to boot into recovery it shows the mytouch logo for a bit, the screen turns black and the phone reboots. I tried to flash the old recovery again but I get an error message saying: An error occurred while flashing your recovery. I can still flash CW 3.0.2.4 and CW 3.0.0.5 but both will not boot into recovery.
I also tried flashing the 3.0.2.4 recovery manually through fastboot flash recovery recovery.img but I still get the same problem. I couldn't find an active download link for the 2.5.1.4 recovery to try to flash manually so I don't know if it helps to do this.
I read on the forum somewhere to revert back to stock recovery using the stock PD15IMG IMG file and try again. This took me back to stock and I was able to boot into the stock recovery. Then i reran visionary for permroot again, deleted my clockworks folder from my sdcard and tried again, but the problem came back.... Mytouch logo then black screen then auto reboot.
My root access still works fine but I cant get into recovery to flash a new rom.... and now I am stuck on a stock rom. :[ After 6 hours of trying to fix the issue I'm still very confused.
Any help / suggestions would be appreciated Thanks.

Its doing this after you go into hboot and select "Recovery"?

JDV28 said:
Its doing this after you go into hboot and select "Recovery"?
Click to expand...
Click to collapse
Yes, from Hboot and from rom manager, but sometimes if i try from rom manager it will also hang at the white mytouch logo screen.

Update
Ok. So i have a partially functional recovery again i found the recovery image for 2.5.1.2 and flashed it using fastboot flash. I am now able to get into recovery again and install custom froyo roms, but every time i try to upgrade to a higher version like 3.0.0.5 or 3.0.2.5 no matter which method i use, I still get the same reboot while trying to get into recovery.
Please help. Thanks

Recovery not "sticking" ?

Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?

Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go

4.2.2 recovery help

Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?

ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.

bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app

There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.

A500 recovery stuck "loading recovery kernel image"

Hi awesome XDA dudes
I've searched the forums, and even posted in the basic QA section to no avail. I may have just missed it somewhere, but here is the issue.
Tablet will work fine in Lightspeed 4.8 ROM. No issue there. But, when I try to get into the recovery (power and volume down) I get "booting recovery kernel image," forever.
I recently changed from the Clockwork to TWRP recovery and that is when the recovery function would no longer load.
How can I get back to Clockwork or smililar so that I can put a different ROM on my tab?
Thanks in advance!
Tom

Fixed this problem, only to find another.
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:

SOLVED !!
tfbielawski said:
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
Click to expand...
Click to collapse
Ok, so I had a working ROM but my recovery was fried. So, using Acer Recovery Installer I was able to get a working recovery going.
Then the next problem was that I could not get CM10 to install. When I realized I needed to flash the bootloader (and yes fellow noobs this is different than the recovery) I was unsuccessful.
I tried the automated route using the Blackthund3r app, but the process would just hang at Entering bootloader.
I tried the manual NVFlash route provided by Dibbs and it would get past this point and then hang.
So Dibbs (thanks dude) helped me out via email and suggested I download babsector.rar
After I extracted the rar file, I saw the A501 A.bat file and flashed it. This provided me with hope as it flashed the tablet and the screen atcually read "PASS." But, I wasn't done yet as I still could not install CM10. So, back to APX mode and back into the babsector rar folder. I flashed the Tab with A501 B.bat and followed that immediately with flashing the v8.bat file. In the V8.bet file I chose the Thor 1.7.3 recovery (as suggested by Dibbs and others) and WOOHOOO.....PASS on the tablet again.
Feeling ever more confident, I booted into recovery and flashed the CM10 Rom....SUCCESS!!!!!!!!!!!!!!!
If you are having trouble....don't give up. Thanks again for the help to Dibbs and OKAstro!!

[Q] Custom Recovery Doesn't Work Anymore

Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!

So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?

You'll probably have to Odin back to stock and start over...

Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?

Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.

Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?

Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!

No problem. Glad you got it figured out!
[emoji106]