Develop Bugs

[FIXED] Help!Cant flash any recovery images

Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....

It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!

I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...

coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.

Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good

timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now

so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...

If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4

I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA

topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App

Nevermind I got the Su command to work
Sent from my PC36100 using XDA App

you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.

Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!

hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?

Build number 1.47.651.1 CL195459 release-keys

yea same here......and what is it that your trying to do...go back to stock ROM?

I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.

OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!

[Q] What do I do for today's OTA update?

I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?

fuzzynco said:
I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?
Click to expand...
Click to collapse
Applying the ota will make you loose root, but as long as your s-off you can root again easily.
Not sure exactly whats updated. If your rooted the update will not go thru anyways. It checks to make sure you have the stock recovery, and that all of your original stock apps and system files are there and unchanged. To install you would have to go complete stock other than still being s-off.

it does nothing if you have a custom recovery file.
if you click install, it'll do the count down, but won't reboot.
when you manually reboot, it'll still be what you had.
my setup is:
S-ON
HBOOT: 0.92.0000
CWM: 5.0.2.0
Baseband: 2.15.10.07.07
GingerTiny v2
GingerSense 3.5

So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?

So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
PS:
Is there a way to stop the prompting for
OTA installing?
thanks

yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.

orphicone said:
yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.
Click to expand...
Click to collapse
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? I've been trying to narrow this down also since it's worked in the past. So far I see one user that claims the build is 210690.
So in the build.prop I'd be looking for the line that included "/XXXXXX:user..." and replace the old 6 digit number with the new.

iowabowtech said:
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? .
Click to expand...
Click to collapse
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?

orphicone said:
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?
Click to expand...
Click to collapse
Check this out, hopefully I explained it a little better here. Maybe you could give it a shot or confirm if this is how you did it and if that's the number you edited?
http://forum.xda-developers.com/showpost.php?p=19371024&postcount=58

Open build.prop with the text editor and look for:
Code:
ro.htc.checkin.url =http://andchin.htc.com/android/checkin
Change the url to something else but dont leave it blank. This will prevent the phone from contacting thr update server.

fuzzynco said:
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
Click to expand...
Click to collapse
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.

yeah me too

Chernyi said:
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347044

The above linked thread is to an entire ROM and requires wiping. Is it possible to create an update.zip to bump me up (and keep me rooted) if I am rooted and have CWM? I know this has been done for previous updates.

This method helped me turn off the annoying install reminders. I used it with Nils' Business Gingersense.
http://forum.xda-developers.com/showpost.php?p=19370543&postcount=993

I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
Make sure you have S-OFF.
Boot into Clockworkmod and Backup your phone just in case.
Download the following:
Stock Recovery: http://www.multiupload.com/86N0CZ8NO0
Clockworkmod Recovery: http://www.multiupload.com/UQ3Q5ZI0HO
SuperUser: http://androidsu.com/superuser/ (use binary only if you already had SuperUser app installed)
Copy OTA update in /cache to SD card and name it update.zip.
Copy recovery zip files and SuperUser zip (su-bin-3.0.3-efgh-signed.zip) to SD card.
Rename stock_recovery_PB31IMG.zip to just PB31IMG.zip.
Hold VOL-, press POWER to boot into bootloader.
Press VOL- to update recovery to stock. At this point, it may automatically install the update. If not (red exclamation), press VOL+ and POWER to get to the stock recovery menu and select "Apply update.zip from SD" to update manually.
When update completes and you're booted into Android, go to Settings, Applications, and turn off Quick Boot.
Rename or delete existing stock recovery .zip on SD card.
Rename Clockworkmod recovery, cwm_PB31IMG.zip, to PB31IMG.zip.
Shutdown or reboot phone and get into bootloader again, and this time flash Clockworkmod recovery.
Get into Clockworkmod and use it to flash su-bin-3.0.3-efgh-signed.zip.
Once it reboots, you will be updated and rooted.

GnatGoSplat said:
I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
1. Make sure you have S-OFF.
2. Copy OTA update in /cache to SD card and name it update.zip.
3. Copy stock recovery to SD card and make sure it's named PB31IMG.zip.
4. Hold VOL-, press POWER to boot into bootloader.
...
Where is the stock recovery file? There is nothing in /cache or /cache/recovery. For a brief time, the OTA update file for Gingerbread 4.08 was in /cache, but nothing in recovery. the update file has since disappeared, but not before I copied it to my sdcard, so I have that.
Also, I noticed after installing that version of Gingerbread on another phone that was not rooted, that once I did that the hboot menu did not appear when holding down the vol key while powering on. Maybe that is an S-off thing only.
Thanks.
Click to expand...
Click to collapse

I had to search Google for quite some time before finding the stock recovery and when i searched just now, all I found were broken links.
I won't be home for awhile, but let me know if you can't find the stock recovery and I'll upload it somewhere.
Oh yeah, you have to go into Settings, Applications, and turn off Fast Boot or Quick Boot in order to be able to get into bootloader when rebooting.

shoot
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.

jonduncan99 said:
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.
Click to expand...
Click to collapse
Are you wanting to go back to stock?
If so, are you S-OFF? If yes, it's pretty easy, you can just install the full Gingerbread RUU (the .exe file that installs from PC) to go back completely to stock and it'll boot for sure.
What I would do is do a backup with clockworkmod to SD.
Then install the RUU.
Flash clockworkmod back into it (this is why you need to be S-OFF).
Use clockworkmod to restore only your /data partition from SD.
Re-root by installing su.zip.
You should now be rooted, stock, and all your apps and settings should still be intact.
I don't know for sure the backup and restore will work from one ROM to the next, but it did work when I bricked my wife's Incredible and had to restore from RUU (though it was on stock ROM before and after).

Bootloader Relocks Automaticly

I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.

Is this a GSM GNex (i9250)?

i9250

To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.

When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.

This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.

BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.

aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange

There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2

DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.

j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.

DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html

If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.

I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2

Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc

Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.

DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.

NEED HELP cant access CW Recovery

I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.

cyaiphone said:
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
Click to expand...
Click to collapse
Nexus line.
have you tried reflashing cwm recovery via fastboot?

flash CWM via fastboot.
and why do you need a backup of stock? You can always re-flash the stock images to go back to completely stock. Restoring a rooted nandroid backup won't put you back to stock anyways...

OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?

cyaiphone said:
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
Click to expand...
Click to collapse
Similar, except you put it in a folder on your PC and flash it over USB with the command line.

martonikaj said:
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
Click to expand...
Click to collapse
Crap is there a how to any how to do this? I've never used adb or command prompts.

cyaiphone said:
Crap is there a how to anywherebonnhow to do this? I've never used adb or command prompts.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1529058
And look for the "Setting up ADB for our device:" then "Obtaining Root Access and Custom Recovery:".

Can you boot into the OS? If you can, download Rom Manager from the Play Store and use that to install CWM Recovery.

Did you delete recovery-from-boot.p from /system? I had to do this to "permanently" install the recovery. My first Samsung phone, my first Nexus device, so not sure if this has been a regular thing ... never had to "permanently" install a recovery up until then. That fixed my issue as my recovery was only sticking once per boot ... was blowing my mind for a couple hours.
Not sure if root via toolkit solves this, but I did a manny root and had to do this. Hope it helps.
edit-
- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
Click to expand...
Click to collapse
Could also, apparently, rename it. I just reinstalled recovery, deleted, and haven't had a single problem since.

What bleedblue said; now go into fastboot, and reflash cwm.
Sent from my i9250

update to jelly bean lost root and cwm

hi guys last night i had my phone rooted and had recovery after flashing koush rom i lost my root and i dont have my cmw when i try go to recovery there is a pic of robot laying down with his stomach open and red. please help me what do i do?

sofia-captivate said:
hi guys last night i had my phone rooted and had recovery after flashing koush rom i lost my root and i dont have my cmw when i try go to recovery there is a pic of robot laying down with his stomach open and red. please help me what do i do?
Click to expand...
Click to collapse
Push volume up and select recoveryon the screen with the robot

daman215 said:
Push volume up and select recoveryon the screen with the robot
Click to expand...
Click to collapse
i did it doesnt work i have lost my cwm loook like it

As with any stock update, the JB update disables root access and replaces whatever recovery you have with the stock recovery.
The only way to root is with an unlocked bootloader. So:
1) Unlock your bootloader;
2) Flash CWM using fastboot;
3) Flash a superuser zip to get root;
4) Boot into Android;
5) Use a file explorer with root access to delete these files: /system/etc/install-recovery.sh and /system/recovery-from-boot.p
6) Re-flash CWM;
7) Done.

efrant said:
As with any stock update, the JB update disables root access and replaces whatever recovery you have with the stock recovery.
The only way to root is with an unlocked bootloader. So:
1) Unlock your bootloader;
2) Flash CWM using fastboot;
3) Flash a superuser zip to get root;
4) Boot into Android;
5) Use a file explorer with root access to delete these files: /system/etc/install-recovery.sh and /system/recovery-from-boot.p
6) Re-flash CWM;
7) Done.
Click to expand...
Click to collapse
You must be pretty sick of posting this!
You're a martyr for the cause!
Sent from my GT-I9300 using xda premium

Please search before creating any new threads.
http://forum.xda-developers.com/showthread.php?t=1737899