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] manual OTA-update on revoked-root-desire

hi,
as far as i found out today it was recommended not to install the OTA-update that has been provided by HTC because I would lose my Root-rights.
Since this is not a problem for me I wanted to install it - but it fails everytime with messages like
E:failed to verify whole-file signature
[...]
Would it make sense to install it maunally? the download over the air was no problem, so i could easily put it into root-folder, rename it and install it manually. but do i have any other negative side effects except losing rootrights?
regards,
andre

Bootloops for one..
The cleaner way to run it, is to run the RUU (Do create a goldcard before you do), then run the OTA as update.zip, as Nature intended..
And why on earth would you need an OTA on a rooted phone. Just get the latest rooted ROM which would be more uptodate..If you just dont want root, do as above..

Well, no in this case it's just run the 2.29.405.2 RUU then you've not got to bother about the OTA!!

First i try to install as "zip from sd" with clockwork. But I become bootlooping phone.
Then I try to install with goldcard. All was ok. But when am try to install an app from market, my phone restarted at the point of installation.
Is any other way to update without RUU with clockwork?
Sent from my HTC Desire using XDA App

In a word, no. You can try a hard reset but best way is to flash the RUU. Gold card only needed if you have a branded hendset

droidzone said:
Bootloops for one..
The cleaner way to run it, is to run the RUU (Do create a goldcard before you do), then run the OTA as update.zip, as Nature intended..
And why on earth would you need an OTA on a rooted phone. Just get the latest rooted ROM which would be more uptodate..If you just dont want root, do as above..
Click to expand...
Click to collapse
the major disadvantage is loosing all information. or is titanium backup able to restore everything? i don't believe so.
regards,
andre

Titanium works on rooted phones, so you could flash stock, root it and then restore

does someone know why installing this OTA-upgrade is failing with signature-message?

Don't flash it if you're rooted - simple as that!!!

understood that. but i want to get some more infos on that.
beside this, since i have to flash a new rom anyway: which is a very good rom you are using? will everything be restored by titanium backup, or will the screens e.g. not be backuped and restored?

I'm on stock 2.29.405.2 and not rooted. It's a good ROM. You'll need to obviously root your phone again to restore the backup

bad loop... ;-)
get back to official rom with OTA but without restoring the backup... or stay on root... i think i will stay on root now. i will try the update this evening and check for the restore how far it works...
thanks for your effort.

HELP!!!
i tried now several times to install a shipped rom (2.10.405.2, 2.29.405.2), but it is not working! it restarts my desire, and it stays with the black screen and white HTC letters... error 171 is displayed afterwards... how can i resolve it? i tried already to download a rom as zip and tried to install it via unrevokedrecovery 2.5.0.7 via "apply update.zip", but it didn't work as well.
can someone help me???
regards,
andre
edit: after installing htcsync it worked again...

YOU CANNOT DOWNLOAD A STOCK ROM AND FLASH IT VIA CLOCKWORK MOD!!!
How many more time does it have to be said????
If you wanna try flash a custom ROM you don't select 'apply update.zip' - you go to flash ROM from SD card and choose the ROM you want to flash. If you don't know how to use CWM why the hell ahve you rooted?!!?

astrakid said:
HELP!!!
i tried now several times to install a shipped rom (2.10.405.2, 2.29.405.2), but it is not working! it restarts my desire, and it stays with the black screen and white HTC letters... error 171 is displayed afterwards... how can i resolve it? i tried already to download a rom as zip and tried to install it via unrevokedrecovery 2.5.0.7 via "apply update.zip", but it didn't work as well.
can someone help me???
regards,
andre
Click to expand...
Click to collapse
I honestly didnt understand what you're trying.
If you want to get the system unrooted, back to stock, then:
Read FAQ 5 and get the PB99IMG.zip
After getting PB99IMG.zip, put it in root of sdcard/goldcard,
Switch Off
Switch on with Back and Power. Keep it pressed.
The system will detect the file and prompt
Press Vol+ to start the RUU
To install a custom rom, "Install zip file" from Clockworkmod.

4. Volume down + power, not back. Back will take you to FASTBOOT

EddyOS said:
4. Volume down + power, not back. Back will take you to FASTBOOT
Click to expand...
Click to collapse
You're right..From Fastboot, it's one additional key..

[Q] Rooting gone wrong/ I've made a big mistake

Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.

tjmarchand said:
Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.
Click to expand...
Click to collapse
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
su
flash_image recovery recovery-clockwork-3.0.2.4-vision.img
reboot recovery
Click to expand...
Click to collapse
Post the results in here.

blackknightavalon said:
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
Post the results in here.
Click to expand...
Click to collapse
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
Do you have the engineering bootloader? If not, you may have to try it with ADB.

blackknightavalon said:
Do you have the engineering bootloader? If not, you may have to try it with ADB.
Click to expand...
Click to collapse
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)

tjmarchand said:
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)
Click to expand...
Click to collapse
Maybe it's a bad recovery. You said you flashed 2.5.1.3, so ROM Manager should work. Try flashing 3.0.2.4 through there now. If not, I suggest downloading Fastboot.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493

raitchison said:
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493
Click to expand...
Click to collapse
Thanks for the guide! I followed it with no issue, I rebooted into recovery; it first hung on the HTC screen, rebooted, vibrated and then booted back into the OS. So anyway, instead of 2.5.1.3, I'm on 3.0.0.5 now.
I went down to 2.5.1.3 and downloaded cm6.1 via rom manager. It told me this : E: can't open '/sdcard/..location (bad) installation aborted. tmp/recovery.log was copied to sdcard
I tried enom's froyo themed rom next, heres what recovery tells me:
Installing update...
Formatting cache
Copying files
Formatting SYSTEM
Copying files...
E Can't symlink /system/bin/su
E Failure at line 19:
symlink /system/xbin/su SYSTEM: bin/su
Installation aborted.
I also tried to download an updated superuser from the market, it says installation unsuccessful package file was not signed correctly.

Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.

blackknightavalon said:
Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.
Click to expand...
Click to collapse
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)

tjmarchand said:
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)
Click to expand...
Click to collapse
If this is the Gingerbread OTA, you'll need everything as stock. If it's the "OTA" with Superuser thrown in, you'll need CWM Recovery 3+ (2.5* formats the system in yaffs, 3+ formats it in EXT).

This is just the ota update with wifi calling still 2.2, Im unrooted and stock recovery again
Sent from my T-Mobile G2 using XDA Premium App

[Q] Phone didnt install Gingerbread when I told it to and now no update shows up.

Ok this is weird...i got a notification that an update was available...i didnt read about it, because Im assuming it was the Gingerbread update.
Anyway, I clicked install and it told me my phone would reboot in 10 seconds and it never did...now when I go to about phone>system updates it tells me my phone is up to date and its still on Froyo
What do I do?...has anyone posted the RUU or update.zip, i cant seem to find either one

Are you rooted?
There are a couple 4.06.605.3 links floating around in the Dev. section. I have no experience flashing them so read the thread.

Same thing just happened to me. I used root explorer to find the update in the cache folder. I've tried moving it to the root of the sdcard and renaming it PB31IMG.zip but it doesn't run. Not sure what to do now except just wait for the update prompt to come up again.
Okay so I tried to renamed the file update.zip and it looked like it was installing it, green triangle with a green exclaimation point and a greem progress bar, then about half way thrun it all turned red and stopped. Had to take the battery out to reboot and nothing new on the phone.
I'm doing this with the stock recovery in place and maybe I should just flash CWM and try again.

Something is wrong with how the stock recovery image is flashing as everytime I flash it I look in ROM Manager and the recovery hasn't changed. So I just downgraded to Froyo by downloading the file from dougpiston.com then put the OTA from my cache directory on my sdcard as update.zip and now it installed correctly.

I had the same problem trying to run the ota. I had to reflash the stock recovery from dougpiston.com being sure to use the PB31IMG.zip method and not merely selecting the .zip file in Clockwork to install it. When I tried putting the stock recovery back on using clockwork I ended up with a sort of hybrid recovery that appeared stock but had pieces of clockwork still there. After I reinstalled the stock recovery properly, everything worked.
Todd
Sent from my ADR6300 using XDA App

kzoodroid said:
Something is wrong with how the stock recovery image is flashing as everytime I flash it I look in ROM Manager and the recovery hasn't changed. So I just downgraded to Froyo by downloading the file from dougpiston.com then put the OTA from my cache directory on my sdcard as update.zip and now it installed correctly.
Click to expand...
Click to collapse
First of all to everyone, I was rooted(not when I did this though)...I got the update prompt and then I decided to root my phone...i turned s-on went back to stock 2.2 and stock recovery...and then i got the update prompt again...then thats when all this happened
but anyway kzoodroid...if you have the update.zip...please share it with all of us

It should be on your phone already if you got the notification. Use root explorer and look under cache in the first directory that opens and it should be there. And its the exact same OTA file as has already been posted elsewhere on here since Friday.

I got the same prompt and tried looking in the cache folder but don't see anything.

tmoney468 said:
I got the same prompt and tried looking in the cache folder but don't see anything.
Click to expand...
Click to collapse
then either it didn't download the file or your not looking in the right place. i'm assuming you are rooted as you have to be rooted to look in the cache folder which is in the root diectory of the phone. there also should be a couple other folders in there lost+found and recovery.

[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).