Develop Bugs

HELP!! I broke my root?

I was rooted fine with unrevoked forever. I wanted to try a rom than required me to install the newest version of hboot so I did that. Well I didnt like that rom so I tried to flash a nandroid restore but it didnt take. So I reinstalled the pc36img that I used when I rooted my phone. Then I rebooted my phone. Now it booted like its not rooted! I don't have superuser app and when I try to reboot into recovery I get a red triangle over a phone.
When I boot into hboot it says I have s-off but I have no idea how to get my phone back to the way it was.
Under system info it says I have firmware version 2.1-update1 but I try to look for a froyo update and it says there are none available.
I was going to just unroot with the s-on tool but that requires going into recovery which I can't do.
What do I do?
Please help me get my root back!!!!

Try flashing this PC36IMG. That should bring you up to the latest rooted OTA, radios, hboot, and it will flash clockwork for your recovery.

Will that cause me to loose s-off root? Will I be able to re-root with the simple root method?
I want to be rooted I just screwed something up and need to fix it

Nope, it's already rooted. You will be rooted stock, off the new OTA with S-OFF.

_MetalHead_ said:
Try flashing this PC36IMG. That should bring you up to the latest rooted OTA, radios, hboot, and it will flash clockwork for your recovery.
Click to expand...
Click to collapse
Ummmmm... That file in that link had a trojan virus in it. Thanks!

You're joking right?

Just so you know, that was a rhetorical question.
There's no trojan in that file. Download it or don't, that's on you. I am only trying to help.

I did download that file and my antivirus said a trojan virus was detected. I'm very serious. I will try again and see if I get the same results

I downloaded it again and no virus this time, Weird. Anyways when I flash this I get Boot Fail-pu so I flashed it again and got the same result. Any idea why it would do this?

I think its fixed. I reflashed my rom and now I have superuser again and I just used rom manager to flash ra recovery. Thanks for the help!!!

Novarider said:
I downloaded it again and no virus this time, Weird. Anyways when I flash this I get Boot Fail-pu so I flashed it again and got the same result. Any idea why it would do this?
Click to expand...
Click to collapse
I got the exact same error. It flashed everything but the Boot failed. I restarted and it kept bringing me to the clockwork recovery instead of booting up. It said E: Invalid Argument. I wiped everything and did another restore and got the same error. I did it again and my recovery worked
I would press my luck and try to flash the de-ox rom over this but from the last 3 days, I'll probably get a boot loop again -_-

Oh Boy...Huge Error...Help Requested

Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.

fisheric1 said:
Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.
Click to expand...
Click to collapse
Need any and all information about your phone. I also notice that you are new. The dev section isnt for Q/A there is an entire section dedicated to solving these issues. Please remember that next time. Keeps things cleaner. So please gather anything you can about your phone. Method, Hboot, Version, Radio, Anything that can help anyone here identify something.

Do you have the rom in the root of the usb card? If so try full data wipe and installing the room see if it boots up.

Thanks for the quick reply. Will remember. Desperation has gotten the better of me. I will move over to Q/A if you prefer.
HBOOT-2.10 0001
RADIO - 2.15
Initially rooted via Unrevoked 3 beta RC2 yesterday.

if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)

T3hPWN said:
if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)
Click to expand...
Click to collapse
I agree with this method... the best way to determine the recovery to use would be to go into the terminal and type
Code:
cat /proc/mtd
if you see "400000" then you need to get the clockwork v3.0.0.2 that supports this phone partion layout. If you see "20000" then you should get amon_ra 1,8 from here:
http://forum.xda-developers.com/showthread.php?t=705026
The information I gathered was from this post:
http://forum.xda-developers.com/showthread.php?t=894331
Making sure you have the correct recovery is the first step. Once that is done create a nandroid and save it somewhere to ensure that the wimax partition is saved.

You have to flash the modified version of Amon_ra found in Zikronix thread. You can find my thread that points to it or just search for hboot 2.10 and follow the instructions in that rooting thread. It seems you're already rooted so just flashing the recovery is probably all you will need.

I haven't used unrevoked, and I know there are several versions. But I have seen others who have used unrevoked and couldn't flash anything bc evidently the method they used to root didn't install the flash_image file on their phone.
I know that installing flash_image fixed being able to flash for some people who rooted with unrevoked.
This issue came up and I was able to help some people, if you check near the end of fastRX8 thread. But I was only able help point the right direction, they figured out the rest of the way. The OP there has the flash_image file and tells you what terminal commands to install it.
I don't know how for you to check if you gave it or not, as I can see mine on sd card cuz I put it there when I rooted.
Beyond this suggestion, lithid can probably help much better than I.
But def post your hardware version, root method, and hboot version (you see that when you go into bootloader and read the top line.
Sent from my PC36100 using XDA App

Wow, sorry, theres been several posts since I started tying. Looks like these guys got it for ya
Sent from my PC36100 using XDA App

Was there a resolution for your problem? If so please post so anyone searching in the future can resolve there problem quickly.

you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.

dkdude36 said:
you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.
Click to expand...
Click to collapse
You mean the modified amon ra recovery image?

exactly...

dkdude36 said:
exactly...
Click to expand...
Click to collapse
Ya it worked for someone else in the Amon_Ra Clockwork thread here is the link.
zikronix said:
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to.
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
Click to expand...
Click to collapse
OP flash the PC36IMG in the bootloader to load this new recovery, then you can go into your new recovery and flash a new rom.

i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?

defjef123 said:
i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?
Click to expand...
Click to collapse
Were you restoring a backup or did you stuck on loop on a new rom flash?

i wasnt even trying to flash a rom yet. i was doing the very first nand backup so i could check some roms out. after the backup was complete it gave the option to power off so i did and when i turned my phone back on it was in the bootloader loop. so i went back to recovery, wiped everything, restored nand and i said it restored but when i rebooted it was back in the bootloader loop.so i just search around trying to get help but couldnt find much so i put sprintlovers since it boots up right when you turn your phone on. now it wouldnt even nand backup it said some error and was in the bootloader loop again so i just reinstalled sprintlovers, again

Try downloading an actual rom in zip format (not sprintlovers pc36img) and see if you can flash a new rom fresh. Make sure to wipe everything.
Try using Caulkings format all zip in recovery to wipe your caches.
http://www.mediafire.com/file/ikylelx99c49133/Calkulin's_FORMAT_ALL.zip

put in on my sd card turned my phone off to go into recovery and now my phone wont even turn on

it came on now. gonna try to wipe and flash that rom

Stuck on boot screen! Help!

Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible

Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<

enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.

Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?

I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.

Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.

Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.

Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?

sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.

Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5

Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.

as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo

Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help

erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?

encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.

sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?

oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X

encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?

Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what

Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.

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