Hey all, after intall MeDroid ICS ROM, I can no longer access CWR, only white Recovery screen. When I choose recovery, it says reboots into itself. I don't have a lot of experience with Blackrose or ICS, but I just want to get back to CM7 or MIUI, how can I get back into Clockwork Recovery?
Thanks,
Matt
you probably lost your recovery, happened to me twice
I had to flash new one thru fastboot--one time had to erase system thru fastboot first then flash recovery
try amon ra 2.2.1 instaed of cwr
dl it to pc and fastboot flash it
Thanks! What is the command for fastboot install?
Reflashed from inside clockwork, thanks!
Glad you got it--missed first post after mine
I would keep Nandroids, as I said I lost recovery twice. But, using AR had to fastboot new one. No big deal.
Related
After putting a new kernel on my device running cm 6 RC1 and supposedly clockworkmod recovery latest, I now do not have a working phone as it stops at the mytouch screen and does not go further, only thing available to use is fastboot which to my dismay, I am having the perfect spl error (remote: not allow), any insight in this problem would be much appreciated.
Trunekind said:
After putting a new kernel on my device running cm 6 RC1 and supposedly clockworkmod recovery latest, I now do not have a working phone as it stops at the mytouch screen and does not go further, only thing available to use is fastboot which to my dismay, I am having the perfect spl error (remote: not allow), any insight in this problem would be much appreciated.
Click to expand...
Click to collapse
Just reboot into Clockworkmod Recovery and flash a new rom and the old kernel
Clockwork recovery sometimes doesn't flash correctly through rom manager. Try downloading among RA's recovery and doing "fastboot flash recovery recovery.img". You will need an engineering spl though.
Sent from my HTC Magic using XDA App
Something went wrong. I don't know why all you new android nubs have to use "clockwork or "sp" recovery. A good ol Recovery image like Amon Ra's latest 1.7.0G works great. Anyway, you didn't brick the device. Just try re-flashing or flashing another rom. (one you know for a fact works) Oh, if you did a nandroid backup, I suggest you restore it. And if you can't get into "clockwork" recovery upon boot. Then I suggest you do what @caedus90 advised and flash Amon RA's recovery through ADB.
Hope this helps. And stop using those idiot friendly recovery alternatives. =P
later
xIoNiCx said:
Something went wrong. I don't know why all you new android nubs have to use "clockwork or "sp" recovery. A good ol Recovery image like Amon Ra's latest 1.7.0G works great. Anyway, you didn't brick the device. Just try re-flashing or flashing another rom. (one you know for a fact works) Oh, if you did a nandroid backup, I suggest you restore it. And if you can't get into "clockwork" recovery upon boot. Then I suggest you do what @caedus90 advised and flash Amon RA's recovery through ADB.
Hope this helps. And stop using those idiot friendly recovery alternatives. =P
later
Click to expand...
Click to collapse
OMG...I feel so dumb right now...I don't know why I didn't just stick with Amon's recovery...I got curious too and try to use Rom Manager to play around and now I am stuck as well...but my case is a little different in that I cannot get into recovery BUT my phone still boots right into Android like normal...
I flashed Amon's recovery via Rom Manager but still cannot get back into recovery...flashed ClockworkMod recovery but still no recovery...
So advice, please...I think I've learned my lesson and stay with the manual work from now on...lol...I was totally fine with Amon's recovery too...guess my curiosity will kill the cat eventually if I don't wise up...
What's the best way to get recovery back? I have Cyanogen's CM6 on my mt3g 32b...Much thanks for any advice...
UPDATE: Just thought I let you guys know that I was able to get Amon's recovery to work again by keep trying the reflash while in Rom Manager thanks to a tip from another member...Last time I'm touching Rom Manager...It's not a bad program, just us users who are causing problem...
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
highrolla1866 said:
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
Click to expand...
Click to collapse
I havent had that issue exactly, but I might be able to help wlk you through getting this fixed. Ive had problems more than once myself on recovery, and helped a couple others solve other issues on here. If you want, add me on google talk (same username as on xda), and Ill walk you through it. Might have to wait till the morning, though, as Im probably gonna head to bed soon.
Fastboot 2.5 recovery and reflash froyo rom. If you decide to install CM7 again - read,search and make sure that you understand what you're doing. It has been stated at least few dozen times that Rom Manager is useless with gingerbread until Koush updates it.
Same Issue??
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
fosunite said:
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
Click to expand...
Click to collapse
Jmg90300zx said:
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
Click to expand...
Click to collapse
Sounds like both of you should of never of done this. This has been discussed a few times, and the end result is always the same.....
Download the correct Recovery image (which can be found in the Development section) and install it to your phone by using the ADB commands, in the fastboot mode. you can find a quick and painless way to set those up in my signature. Once you have installed the recovery image you can boot into hBoot and select recovery. from there you can flash CM7 and the gapps. Once you have done all that download the official clockwork ROM manager from the market and flash his current recovery image.
I don't know if this could be really repetetive, since it's only happened twice, but it's 2 times in a week and a half, with a RUU and reroot, etc in between.
Reboot the phone and it white screens/freezes for no reason.
Clearing caches or doing a full wipe doesn't fix that issue.
Go to recovery and try to do a nandroid restore and get an "oops... something went wrong error"
Also notice my latest nandroid doesn't show up in the restore list.
I have to pull the sdcard, put it in my spare phone, connect to my pc and move Amon Ra back to the SD Card/Root, then put it back in the Evo, and reboot to Hboot so I can reflash recovery, and then everything seems to work again.
Including my latest nandroid showing the restore list again.
Anyhone encounter this, or know why it's happening?
BTW, using v2.3
Flash it through Rom manager, flash clockwork and after you flash clockwork, then you flash alternate recover aka amon ra
HipKat said:
I don't know if this could be really repetetive, since it's only happened twice, but it's 2 times in a week and a half, with a RUU and reroot, etc in between.
Reboot the phone and it white screens/freezes for no reason.
Clearing caches or doing a full wipe doesn't fix that issue.
Go to recovery and try to do a nandroid restore and get an "oops... something went wrong error"
Also notice my latest nandroid doesn't show up in the restore list.
I have to pull the sdcard, put it in my spare phone, connect to my pc and move Amon Ra back to the SD Card/Root, then put it back in the Evo, and reboot to Hboot so I can reflash recovery, and then everything seems to work again.
Including my latest nandroid showing the restore list again.
Anyhone encounter this, or know why it's happening?
BTW, using v2.3
Click to expand...
Click to collapse
im pretty sure the ruu deletes the recovery because stock does not have a recovery.
drtdiver83 said:
im pretty sure the ruu deletes the recovery because stock does not have a recovery.
Click to expand...
Click to collapse
Well, of course it does. That's not the issue.
Obviously, I had to reflash recovery after running the RUU.
The point is, it happened a few days before and a few days after I ran RUU.
I'm wondering if it's a recovery issue or an SD Card issue.
Treated, I root with UnrEVOked, which flashes clockwork, then I flash A.R. after that, but if it happens again, and I can boot up, I'll try flashing CW from Rom Manager and then A.R. afterwards.
Earlier today I installed the "Royal Ginger" ROM using ROM Manager + CWD 3.0.0.5. I made a backup of my previous ROM prior to this.
After the install was completed (as it said in recovery), I tried booting up. I'm in the boot screen for the ROM, and it keeps repeating over and over. I went back into recovery, wiped cache and delvik, and rebooted. Same problem.
Again in recovery, I installed my previous working ROM (the one I have been using for months), and I'm in a bootloop again.
After some google searches, I traced the problem to be CWD 3.0.0.5 and found out that I should flash 3.0.0.6. However, I can't as there is absolutely no way for me to get back into Andriod (stuck in bootloop no matter what ROM is installed.)
Is there anyway to manually flash it? I have the file on my SD card, I just don't know how. Or is there a compatible ROM with 3.0.0.5 that will allow me to install, get in to the market, and use ROM manager to update to 3.0.0.6?
This is very frustrating and would greatly appreciate any help you guys have to offer.
did you make a nandroid of your stock rom, or at least previous rom?
I don't know what a nandriod is unfortunately. I tried a manual flash of 3.0.0.6 using adb shell method, and now the recovery won't even load. FML. I guess I deserve this.
Follow this link to restore back to stock and start again:
http://forum.xda-developers.com/showthread.php?t=845756
Good luck
[email protected] said:
I don't know what a nandriod is unfortunately. I tried a manual flash of 3.0.0.6 using adb shell method, and now the recovery won't even load. FML. I guess I deserve this.
Click to expand...
Click to collapse
Nandroid will back up you're current rom in the state it is. it is HIGHLY suggested to do so before flashing another rom, so you can always revert back to what you had incase there is such problems. It's in the menu of CWM. I would suggest doing it before flashing any rom, it will save you from taking more steps backwards than needed
There is no Nandriod option on my CWD, though I did make a backup of my Old rom. I can't get into CWD anymore anyways, so I guess the only option is to go back to stock?
[email protected] said:
Earlier today I installed the "Royal Ginger" ROM using ROM Manager + CWD 3.0.0.5. I made a backup of my previous ROM prior to this.
After the install was completed (as it said in recovery), I tried booting up. I'm in the boot screen for the ROM, and it keeps repeating over and over. I went back into recovery, wiped cache and delvik, and rebooted. Same problem.
Again in recovery, I installed my previous working ROM (the one I have been using for months), and I'm in a bootloop again.
After some google searches, I traced the problem to be CWD 3.0.0.5 and found out that I should flash 3.0.0.6. However, I can't as there is absolutely no way for me to get back into Andriod (stuck in bootloop no matter what ROM is installed.)
Is there anyway to manually flash it? I have the file on my SD card, I just don't know how. Or is there a compatible ROM with 3.0.0.5 that will allow me to install, get in to the market, and use ROM manager to update to 3.0.0.6?
This is very frustrating and would greatly appreciate any help you guys have to offer.
Click to expand...
Click to collapse
You need to flash a rom that is ext3.. More or less a froyo rom.. After you do that you should update to cwm 3.0.2.4
Sent from my demonSPEED! Glacier
I can't get into recovery. I tried doing the stock method and the following occured:
C:\adb>fastboot flash recovery recovery2.img
sending 'recovery' (3948 KB)... OKAY [ 1.357s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.378s
C:\adb>
What happens if I press the factory reset option from the power screen?
Also, how can I push a recovery image using ADB, and then following it up with an installation using ADB commands? I cannot mount the SD card as the recovery is stuck at the splash screen, so the only option is to run a command through ADB installing an image pushed onto the phones main memory.
Why are u using 3.0.0.5? There is a newer version in rom mgr.
Sent from my MyTouch 4G using XDA Premium App
I didn't know there was. I can't get back into android to do anything about it though, no matter what I try. Recovery gets me stuck at a splash screen,as does a normal boot.
Can u not boot into recovery from hboot (volume down + power button)?? If not, flash the new recovery in fastboot
Sent from my Acer Iconia Tab A500 using XDA Premium App
OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!
xodus1914 said:
OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!
Click to expand...
Click to collapse
Well, not sure if I can get you up and running. This is going to depend on if you followed traditional installation instructions that are posted on every thread that contains a Rom.
But first, let's cover where you went wrong. And that would probably be when you went back to Recovery. It seems, you didn't hit Vol - and PWR, but instead selected Vol + and PWR. And as such, it tried to run an update.zip file, which is a no-no. This resulted in a corrupted image.
Secondly, Rom Manager is a phone app. This will in most cases, bork your tab.
First, I would try Acer Installer (newest version) and try to install RA Recovery. If you were using CWM before, you probably can't flash it again.
If that doesn't work, then you will have to roll back from ICS, and you will need your original UID number. Hopefully you wrote this down somewhere. If you were using RA Recovery, you will find the UID number in the UID.txt on your SD Card in the Recovery folder (if you made a system backup before flashing ICS roms). If you were using CWM, well, it might be buried in one of the .img files in the clockwork folder (again, if you made a backup before flashing ICS). You will have to de-compile the image files to find it (hopefully).
If your ADB seems to be working, you may want to push the RA Recovery;
http://forum.xda-developers.com/showthread.php?t=1459821
If you have your original UID number, then you may want to try this;
http://forum.xda-developers.com/showthread.php?t=1522384
or this;
http://forum.xda-developers.com/showthread.php?t=1516012
Hope you get it going. From what I have seen, mostly when the people lose their recovery, they were using CWM. Haven't heard of any losing it when using RA Recovery. But anyhow, use Acer Recovery first, and try the RA Recovery.