Database Users

[Q] Clockworkmod recovery disappears after reboot

I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?

If you flashed CWM 3.2.0.0, that may be your problem. Look at this thread > http://forum.xda-developers.com/showthread.php?t=1074979
Note in the last several pages that some posts were having the same problem as you. I flashed back to 3.0.2.8, and it solved my problem.

Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.

olafski72 said:
I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?
Click to expand...
Click to collapse
Without a rooted boot.img if will keep deleting The recovery. You can also delete the recovery-boot.p file from the system folder to stop it.
Sent From My Evo

olafski72 said:
Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.
Click to expand...
Click to collapse
Bwcorvus is right.
Sent from my ADR6300 using Tapatalk

I have flashed with 3.0.2.8, with my Xoom rooted. Again, the first attempt was succesfull, I came into the CWM menu. I rebooted again to Android. Rebooted with the Sirius Fastboot in Recovery, but there it was again, the stock recovery!
I have not deleted the recovery-from-boot.p since that sounds kind of scary? What can go wrong? When I delete it, that will stop the stock recovery and bring me into the CWM recovery?
Someone also told me I need a SDcard. Is this true and what should I do with it then? The img is on my PC in the same folder as the ADB tools. So why should I need the SDcard for then?

You must have a SD card for CWM.
Sent from my Xoom using Tapatalk

Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?

olafski72 said:
Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?
Click to expand...
Click to collapse
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.

cam30era said:
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
Click to expand...
Click to collapse
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.
Click to expand...
Click to collapse
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.

olafski72 said:
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.
Click to expand...
Click to collapse
We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support. You need to refer to the appropriate thread(s) in the development section to do this. You need to find a thread that is for your country, your type of Xoom (3g+wifi, or wifi only), and the version of Honeycomb that is currently running on your Xoom (3.0 or 3.1). Hope this helps.
Sent from my Xoom using Tapatalk

We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support.
Click to expand...
Click to collapse
Hm, I have copied the language pack zip file on my sdcard(via my PC and my X10 phone :-D ) and then put it back in my Xoom. I have not the Tiamat kernel yet. This is a Xoom US wifi version, HMJ37, it came with 3.0 but I got 3.1 OTA(although I live in the Netherlands). Then I flashed CWM and rebooted in recovery. I choose to install zip from SDcard and the language pack.zip was there. With CWM I probably CAN browse on my SD without the Tiamat. I installed and rebooted. Unfortunately it got stuck in the animation screen. I rebooted (power button and vol up button) and when Motorola logo showed I pressed vol down. I came in the stock recovery again and did a factory reset. This worked fine and it reboot again. When I went through the wizard succesfully, it surprised me too that the language pack was succesfully installed. I have a Dutch version now and finally a Dutch dictionary for my keyboard. And I am very happy.
Since I have put the Tiamat kernel on my sdcard as well, I could flash the Tiamat kernel the same way. I can flash CWM again(AGAIN!) and install the ZIP from the SD like I did with the language pack. But I am a bit scared to do so.... yet

You need to follow the instructions in this thread > http://forum.xda-developers.com/showthread.php?t=1078019
Read the OP, and make sure that you fully understand it. If you have questions, be sure to ask them on that thread. If you decide to proceed, be sure that you understand and follow EXACTLY each step. No shortcuts.
Also, you should not go any further if you can not afford (emotionally or financially) to brick your Xoom. While it is unlikely to happen, you must accept that it could happen before you proceed.
Good luck.

Thanks, I will look at the thread. I think I have all requirements (3.1, root, wifi only, us model) to do it. But I certainly will have a look. I don't wanna brick my Xoom and go boom.

I have just read this link you posted, but this is about rooting?! I have unlocked and rooted my 3.1 already like this. With a different root tool, but in the same way. That is not the issue. The issue is that I can(!) flash CWM and the first(!) time I reboot I can(!) enter CWM and do all you can in CWM. After I reboot again and go to recovery, the stock Android recovery is back.
The only thing I want is the Tiamat kernel now. It is on my sdcard. So I will flash CWM one more time, reboot into recovery again, and then flash the tiamat kernel into it. But I am in doubt whether I should. I will sleep over it.
Bu the main problem, as mentioned in topic subject, is that CWM will(!) install succesfully and starts the first time, but disappears after the first reboot (in CWM).

Sorry, I didn't understand from your previous posts that you were rooted. Follow the instructions in the OP for the Tiamat 1.4.4 kernel thread.
Sent from my Xoom using Tapatalk

No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!

You could do a nandroid backup (in CWM) and then delete the file. If things go badly, you should be able to boot into recovery and restore.
Sent from my Xoom using Tapatalk

That is a good one. But I was just thinking, after the second reboot CWM disappears, so I can't restore
I have to think about this.

olafski72 said:
No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!
Click to expand...
Click to collapse
There can be no problems from removing it. If you are truly scarred just rename it rec.bak. Its just a text file that runs at boot to make sure the recovery is stock. If its not, it makes it stock.
Sent From My Evo

[Q] ClockworkMod vs. Acer Recovery?

Mates,
I used ClockworkMod to flash .22. Immediately, I was prompted to update to. 30. Then I installed ClockworkMod recovery and made a full backup.
Today, I was prompted to update to. 38 but it failed because it needs Acer recovery not ClockworkMod. How can I revert back to Acer recovery so I can update to. 38? Thanks.
Dr. Sam
Edit: sorry it is ClockworkMod

Use the Acer Recovery app to restore the stock Recovery.
Oh, and dude? Fix your title! It's CLOCKWORK, not WORKCLOCK!

FloatingFatMan said:
Use the Acer Recovery app to restore the stock Recovery.
Oh, and dude? Fix your title! It's CLOCKWORK, not WORKCLOCK!
Click to expand...
Click to collapse
Thanks mate. What should I do to revert back? Thanks again.

Hi mate,
When I run acer recovery app, which option I shoul select to revert to stock? Is it the last option? Thanks.
Sent from my PC36100 using XDA Premium App

Use the option that says "Stock USA 1.141.07_COM_GEN1 recovery". That should work fine as I'm pretty certain Acer haven't updated the recovery at all. No need for them to do so.

FloatingFatMan said:
Use the option that says "Stock USA 1.141.07_COM_GEN1 recovery". That should work fine as I'm pretty certain Acer haven't updated the recovery at all. No need for them to do so.
Click to expand...
Click to collapse
Thank you very much. Done, I am on. 38 now.

That's good to know.. the stock 1.141.07 recovery will work 3.1. I'm actually quite surprised by that.

Euclid's Brother said:
That's good to know.. the stock 1.141.07 recovery will work 3.1. I'm actually quite surprised by that.
Click to expand...
Click to collapse
I'm not. I knew it'd work.

It's strange. In my Iconia 3.1 (4.010.04 build) when i tried revert to the stock 1.141.07 recovery using Acer Recovery Installer i see:
/ \
/ ! \
/____ \
How can I fix this?

Raphaello said:
It's strange. In my Iconia 3.1 (4.010.04 build) when i tried revert to the stock 1.141.07 recovery using Acer Recovery Installer i see:
/ \
/ ! \
/____ \
How can I fix this?
Click to expand...
Click to collapse
Flash ClockworksMod image, reboot into recovery, reboot your system. Then run Acer recovery program and flash stock image. Exit the program and now you should be fine. Tell us if it worked.

I tried few times but nothing happened The same situation. ClockworksMod image works perfectly.

Raphaello said:
I tried few times but nothing happened The same situation. ClockworksMod image works perfectly.
Click to expand...
Click to collapse
So, I see that ClockworkMod image is working. That is great. Now, run Acer Recovery app., then select the last choice to flash 1.141.07 image.
Exit the program, turn off your device. Reboot the device. Now you should have Acer stock recovery image. Let me know if this is true to move to the next step. We must get this done before moving forward.
Peace.

Yeah, ClockworkMod is working. It's better than nothing but the problem is when I flash 1.141.07 image and reboot into recovery I see this triangle with "!".
Thanks for helping me.

Raphaello said:
Yeah, ClockworkMod is working. It's better than nothing but the problem is when I flash 1.141.07 image and reboot into recovery I see this triangle with "!".
Thanks for helping me.
Click to expand...
Click to collapse
I can confirm this, as I got bored one day, and tried it for sh!TS and giggles. The option is there in Acer recovery, but it never worked for me!?!?

Raphaello said:
Yeah, ClockworkMod is working. It's better than nothing but the problem is when I flash 1.141.07 image and reboot into recovery I see this triangle with "!".
Thanks for helping me.
Click to expand...
Click to collapse
What is your system build?

kjy2010 said:
I can confirm this, as I got bored one day, and tried it for sh!TS and giggles. The option is there in Acer recovery, but it never worked for me!?!?
Click to expand...
Click to collapse
I believe you will get the triangle error if the stock acer recovery does NOT see a file named update.zip in the root of your sd card.....

bonzer2u said:
I believe you will get the triangle error if the stock acer recovery does NOT see a file named update.zip in the root of your sd card.....
Click to expand...
Click to collapse
That is quite true & I believed you have nailed it on the head !!
I've seen post from people saying they reflashed the stock recovery using Acer Recovery Installer .... then after installed... they chose to reboot into recovery ( the just installed stock recovery)...etc
stock recovery have no menu !! ( atleast I've never seen it except for when invoked, It shown few line of text in upper left corner....etc )
when it's invoked... it needs and will auto search for the update.zip in root of ext. SD Card.
I believed this is why some experienced the "droid exclaimation screen"
solution....
/After stock recovery re-installation.... you need to shutdown the device....
/transfer the update.zip to root of ext. SD Card...
/Now you can invoke the stock recovery ( Power & Volume down ) ...
solved

bonzer2u said:
I believe you will get the triangle error if the stock acer recovery does NOT see a file named update.zip in the root of your sd card.....
Click to expand...
Click to collapse
Yes you're right. I didn't see this file. Where can I find this update.zip? My build is 4.010.04_COM_GEN1. So stock recovery didn't work without update.zip?

bonzer2u said:
I believe you will get the triangle error if the stock acer recovery does NOT see a file named update.zip in the root of your sd card.....
Click to expand...
Click to collapse
Absolutely! CMIIW, but I thought this option was supposed to put the "update.zip" on ?!?

kjy2010 said:
Absolutely! CMIIW, but I thought this option was supposed to put the "update.zip" on ?!?
Click to expand...
Click to collapse
NOPE !!!
Think about this:
flashing the 1.141.07 recovery using the program Acer Recovery Installer only restore your stock recovery ... basically up to this point there is only one stock recovery !
whether you chose to backup your stock recovery before you'd flashed the CWM and installed custom rom.... or whether you are re-flashing using the Acer Recovery Installer's 1.141.07 recovery... you will end up with the same stock recovery...etc
and the program as a whole is only a few MB (?).... the whole full rom update.zip is about 300+ MB.... you are not seriously thought that the option above actually placed an update.zip in the root of your SD Card for you...did you ??
so now.... you can read my last post regarding "placing an update.zip" after re-flashing the stock recovery steps

Clockwork recovery won't boot nexus s

Hey guys
I'm having an issue booting into clockwork recovery. and i'm having even more of an issue finding the answer, I'm pretty sure that someone is gonna come up with a thread which already answers my Q, I just don't know enough of the terms to search sorry
I've followed instructions here in Kursks walk through to unlock my loader, install super user and install clockwork mod etc.
Clockwork mod and super user are now fully upto date.
I've managed to do a backup of my current rom using clockwork mod.
I have also managed to get the phone to boot in to clockwork recovery from within the android app. But only once.
when ever i now try to do a backup, reboot into recovery, or boot to loader menu and select recovery it always fails.
I get the image of a box with the arrow next to android, then after a few seconds the box and arrow turn into a triangle with "!" inside it.
I'm probably making a rookie error here, but I'm having trouble finding the answer.
Thanks in advance for any help you can offer.
Matt

Yetidragon said:
Hey guys
I'm having an issue booting into clockwork recovery. and i'm having even more of an issue finding the answer, I'm pretty sure that someone is gonna come up with a thread which already answers my Q, I just don't know enough of the terms to search sorry
I've followed instructions here in Kursks walk through to unlock my loader, install super user and install clockwork mod etc.
Clockwork mod and super user are now fully upto date.
I've managed to do a backup of my current rom using clockwork mod.
I have also managed to get the phone to boot in to clockwork recovery from within the android app. But only once.
when ever i now try to do a backup, reboot into recovery, or boot to loader menu and select recovery it always fails.
I get the image of a box with the arrow next to android, then after a few seconds the box and arrow turn into a triangle with "!" inside it.
I'm probably making a rookie error here, but I'm having trouble finding the answer.
Thanks in advance for any help you can offer.
Matt
Click to expand...
Click to collapse
Reflash clockworkmod recovery via fastboot.
Sent from my Nexus S using XDA App

Hi and thanks for your reply
well i reflashed clockwork mod and selected to reboot into recovery, and that worked fine
I then booted back to android, selected a rom to DL and install, and got the same issue again
re-flashed again, selected a rom to install and that appears to be working
Do you have to re-flash clockwork recovery everytime? or is mine doing something weird?
Thanks again for your reply
Matt

Yetidragon said:
Hi and thanks for your reply
well i reflashed clockwork mod and selected to reboot into recovery, and that worked fine
I then booted back to android, selected a rom to DL and install, and got the same issue again
re-flashed again, selected a rom to install and that appears to be working
Do you have to re-flash clockwork recovery everytime? or is mine doing something weird?
Thanks again for your reply
Matt
Click to expand...
Click to collapse
You are wwelcome .
You are dowbloading roms via rom manager?
Sent from my Nexus S using XDA App

There is a file you must delete or rename to make cwr stick
Sent from my Nexus S using XDA Premium App

osugsxr said:
There is a file you must delete or rename to make cwr stick
Click to expand...
Click to collapse
Code:
/etc/install-recovery.sh

I'll ask aswell.
Clockwork recovery won't stick for me either. I9023.
I don't have the /etc/install-recovery.sh anywhere. Looked and searched via root explorer. No files whatsoever called install-recovery.sh. On CM7.
Can anyone give me any tips?

Downgrade to older clockwork via Rom manager . I've had that problem it makes no different and it works fine

Thanks guys I think you've managed to sort me out

[Q] Some help for a nub and ICS + Flashing ROM

Got ICS, OTA (download) installed that no problem, downloaded the acer usb drivers and used ICS Root (blackthund3r). Now i want to install LightSpeed 4.4 (i know theres a newer version) I renamed it update.zip and did the power button + V- button but it says invalid image.
Now im a bit confused cause all this android stuff is new to me, I have the acer recovery installed but im not sure what to do with it. Tried renaming it to recovery.img it says it is flashing but nothing happens.
Kinda lost at what to do or how to get this rom working.... if someone could point me in the right direction it would be sweet
Fox

foxorroxors said:
I renamed it update.zip and did the power button + V- button but it says invalid image.
Fox
Click to expand...
Click to collapse
Yep. That was pretty n00b of ya (that little trick only works on signed official roms, and even then, only ify-ify)
Check this thread. It has the tools you need.
http://forum.xda-developers.com/showthread.php?t=1622425
You can skip the part about installing an ICS rom and rooting. You already did that. You need to do steps 1, 2, (partial 4) 5 or 6 basically.
Note after you rooted. Look at step 4 and delete the required file like it says, before going to steps 5 or 6. You have an option on which package to use. Personally, I like the exe package. But your choice.
This installs patched b-loader and CWM recovery so you can flash ICS only Roms.

Easy
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.

urbie47 said:
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
Click to expand...
Click to collapse
Acer recovery is fine if it'll install the patched Bootloader.
However, it doesn't make a user get his UID number, which is essential in case something happens in the future. Without your UID, you're basically toasted Or you're in for the long haul in figuring out how to unbrick a tab.

help
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...

ores992 said:
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).

Moscow Desire said:
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Click to expand...
Click to collapse
Thanks, but that link is dead

ores992 said:
Thanks, but that link is dead
Click to expand...
Click to collapse
Yeah, XDA did some cleaning up overnight. Try it now;
http://forum.xda-developers.com/showthread.php?t=1622425
MD

stuck in recovery

i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,

Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?

http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home

Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250

Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.

i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally

I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.

Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)

jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(

Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good: