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: "Validation error: Backup CID is missing" Unrevoked issue

hboot 2.02
hardware 003
Software 3.30
I tried on 2 pcs without luck. Ihave double checked everything but no luck after numerous tries. I have rooted 2 other phones so this isnt my first root. Anyone else been able to get around this issue?
hmmm I booted into hboot and it says S-Off (although its not off) but there is no recovery.

Looks like im up!! My s was off so I manually backed uped my RSA keys just to be safe and proceeded to flash Amon_RA recovery PC36IMG.zip and then I flashed superuser zip and that got me where I needed to go.

bizdady said:
Looks like im up!! My s was off so I manually backed uped my RSA keys just to be safe and proceeded to flash Amon_RA recovery PC36IMG.zip and then I flashed superuser zip and that got me where I needed to go.
Click to expand...
Click to collapse
hey..
even iam experiencing same problem..
but i really could not get what you did to make it work.. lol
it would be of great help if you can help me with it.
hboot 0.93

So your s-off now when you boot into boot loader?
I just flashed the recovery and got back up manually with superuser and busy box. You can download superuser from the market or flash a zip as for busy box I installed through Titanium Backup.
I used this method to get my recovery fixed.
http://forum.xda-developers.com/showthread.php?t=829045
zikronix said:
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
==========================================
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. It installs amon_ra 2.2.1
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

is unrevoked CID issue fixed
Hi..could you fix this issue, I wish know how fix it but I only found really old post without solutions...thanks!!!........

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.

SOFT BRICK please help

Hey, I got a soft brick so I'm going to use the unroot method here but I just wanted to make sure it would work.
S-OFF, Hboot 2.1
Also, I'll still be able to root and go back to an old nandroid if this all works out, correct?

It should work. Yes, you will be able to re-root and restore a nandroid once you have completed everything again.
Might throw out your issue first, to see if someone can help you fix without having to go through all that work of unrooting and re-rooting again.

Let's hope so. I'm knocking on wood that I won't have to throw my EVO down some stairs and go get a new one.

Firstly, it is unclear (at least to me) what you mean by "soft brick". Secondly, the link you posted is to a thread that is outdated and was retired by the OP. Or did you mean this thread?
http://forum.xda-developers.com/showthread.php?t=838448
To answer your second question, with S-off you can just go into recovery, do a wipe and then restore your NAND back-up from there. Try just wiping the cache and dalvik cache before restoring. If your phone still gives you problems, you may need to do a full wipe and do a fresh install of your favorite rom.

Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?

tubazeppelin said:
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
Click to expand...
Click to collapse
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb. Worse case scenario would be to run the RUU and start over.

rugedraw said:
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb.
Click to expand...
Click to collapse
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would download Amon recovery and flash that via adb; I recommend staying away from clockwork - read about too many users running into issues with it, especially that 3.0.0.5 version.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would suggest using Amon Ra recovery. I like it better, and personally have had far less issues with it. Attatched is a PC36IMG of Amon Ra 2.3. Put it on the main directory of your SD card, name it exactly PC36IMG, and boot to bootloader, and select yes to update. That should flash Amon Ra's V2.3 recovery for you. If it's successful, see if it works. The only problem with this, that I see, is you wouldn't be able to restore your previous clockwork backups. However, if that did go successful, and you were able to boot into a rom, you could use ROM manager to flash clockwork back, then you could restore your backups. Hope you get it booted up.
EDIT: If you do end up needing to unroot, just remember that if you initially used unrevoked to root, or used unrevoked forever at any time, you're not going to be able to turn S on without having a custom recovery. Becase as far as I know, you need to flash the Unrevoked S on tool in recovery if you used unrevoked to begin with. Otherwise S is permanently off.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
Yea, try the recovery fix. If unsuccessful getting CW to flash, remember you can always try to flash Amor RA recovery just to be able to wipe and flash a working rom. Once you get the phone to boot, you can download ROM manager, flash clockwork and then restore to your CW NAND that is stored on your SD card. I've had to do this in the past.

Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that

tubazeppelin said:
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
Click to expand...
Click to collapse
Really not sure. That goes beyond my scope of trial and error knowledge.

Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.

tubazeppelin said:
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
Click to expand...
Click to collapse
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.

k2buckley said:
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
Click to expand...
Click to collapse
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.

tubazeppelin said:
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
Click to expand...
Click to collapse
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.

k2buckley said:
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
Click to expand...
Click to collapse
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.

tubazeppelin said:
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
Click to expand...
Click to collapse
Awesome. Thats the way to go, just manually flash everything using RA and you'll be good to go.

HTC Evo Goes to FASTBOOT Instead of Recovery

Hey guys so I have been messing with my Evo trying to get S-off and trying to get it to start with clockwork recovery but I have had no luck after at least 6 hours of trying. So I have decided to seek some expert advice so anything will help.
About my evo
Purchased day it came out and rooted it the following night with a tedious method I don't remember at all.
HBOOT- 0.79.0000
Radio - 1.39.00.04.26
Rom Installed - Cyanogen 7.0.3.1
My initial problem
I was trying to get my phone to boot to recovery (latest clockwork recovery and Amon RA 2.3) but every time I tried I would see the red triangle with the exclamation mark. So to fix this I tried running the latest unrevoked and that would get hung up at rooting... so then I wiped my phone and tried again and still nothing. I would get stuck at either rooting... or firmware too new then I tried using an older version of unrevoked (3.21) and it seemed to get further. It ended up getting stuck at reboot.
New problem
Now I cant enter recovery at all. Whenever I try entering through rom manager it takes me to FASTBOOT and even if I try entering recovery through bootloader it does the same. Any suggestions will help! And if you need any more information I will be glad to help.

http://dl.dropbox.com/u/19699565/PC36IMG.zip
Place that on the root of your sd card. Turn your phone off, boot into the bootloader while holding vol+down as you turn the power on. Let it scan, apply update, reboot, reboot into recovery, from the bootloader, and you'll be on amon_ra 2.3 recovery.

Jeez, please stop using ROM Manager to boot to recovery, or to do anything else and explain how you can be using CWM AND AR??

Okay it booted and recognized the file PC36IMG. As for the update, how do I apply it? I click recovery and it still takes me to FASTBOOT.
@HipKat and I tried both recoveries at different times. First clockwork, the amon ra.

Kingcoke said:
Place that on the root of your sd card. Turn your phone off, boot into the bootloader while holding vol+down as you turn the power on. Let it scan, apply update, reboot, reboot into recovery, from the bootloader, and you'll be on amon_ra 2.3 recovery
Okay it booted and recognized the file PC36IMG. As for the update, how do I apply it? I click recovery and it still takes me to FASTBOOT.
@HipKat and I tried both recoveries at different times. First clockwork, the amon ra.
Click to expand...
Click to collapse
It should have asked you to apply update, which you would have used the volume keys to navigate to yes, then pressed the power button to make the selection. If ya didn't get it, do the process again.

It doesnt ask me that and I have tried 5 times already. All it does is return to the bootloader screen.

The script in my sig should be able to recover it, just flash cm7 again once it's done and you should be good to go. You will be able to get to the recovery afterward by holding down power and selecting reboot

So I have been trying to use AutoRoot and was following the video on the thread but I keep getting hung up at "ERROR Could not access the SD card!" Also I was trying to use flashzip as suggested in this thread with your response. And I noticed that it was notifying me my nand was locked. Does that matter at all?

Kingcoke said:
So I have been trying to use AutoRoot and was following the video on the thread but I keep getting hung up at "ERROR Could not access the SD card!" Also I was trying to use flashzip as suggested in this thread with your response. And I noticed that it was notifying me my nand was locked. Does that matter at all?
Click to expand...
Click to collapse
It sounds like you never got fully rooted if your nand is locked (s-on) and the sd card not being recognized could be caused by unrevoked not undoing something. Flashing the 3.29 PC36IMG will most likely fix the sd card error, but if not you'll need to use the OpenShell script from the autoroot folder and type the following:
Code:
adb reboot bootloader
fastboot oem enableqxdm 0
fastboot reboot
If you could attach the autorootlog.txt file to a post that will also give some more information about the condition of your phone.

xHausx said:
It sounds like you never got fully rooted if your nand is locked (s-on) and the sd card not being recognized could be caused by unrevoked not undoing something. Flashing the 3.29 PC36IMG will most likely fix the sd card error, but if not you'll need to use the OpenShell script from the autoroot folder and type the following:
Code:
adb reboot bootloader
fastboot oem enableqxdm 0
fastboot reboot
If you could attach the autorootlog.txt file to a post that will also give some more information about the condition of your phone.
Click to expand...
Click to collapse
Yeah im pretty sure my phone doesn't have a full root and okay im currently downloading 3.29.651.5_PC36IMG.zip. (by the way how do I install it with flashzip? do I just move it in the res folder or what?
attached is my autorootlog
thanks for all your help thus far I hope we get this figured out soon.
edit: I flashed as you suggested, ill see if it solved sd card error.

Kingcoke said:
Yeah im pretty sure my phone doesn't have a full root and okay im currently downloading 3.29.651.5_PC36IMG.zip. (by the way how do I install it with flashzip? do I just move it in the res folder or what?
attached is my autorootlog
thanks for all your help thus far I hope we get this figured out soon.
Click to expand...
Click to collapse
Anywhere in the autoroot folder will be ok. It can't get your firmware version either so there is definitely something weird going on there, but you should be good once 3.29 is flashed.

Its currently flashing my firmware. Everything seems good so far! I will keep you updated.
edit: It says
congratulations! Your phone is now rooted with a customer recovery capable of flashing ROMs!
Unrevoked Forever was not required to root your phone but you must flash it if you plan on using a production hBoot. The ENG hBoot that is currently installed is unlocked by design and has extra features that can not be used on newer version.

WOW! Amazing, thanks so much! S-off, I can enter a custom recovery, and installing cyanogen as we speak. Finally a full root. I have been trying to achieve this forever. Any suggestions on roms? I have been using cyanogen forever.

Kingcoke said:
WOW! Amazing, thanks so much! S-off, I can enter a custom recovery, and installing cyanogen as we speak. Finally a full root. I have been trying to achieve this forever. Any suggestions on roms? I have been using cyanogen forever.
Click to expand...
Click to collapse
Glad to hear that, you'll want to remember not to use any RUUs or upgrade your hboot though. Unrevoked forever can be used to permanently unlock it but as is flashing a RUU will completely unroot your phone and flashing anything newer than 3.29 will prevent you from downgrading your hboot again.
I'm currently using aamikam's sense 2.1 rom from here but have been looking for another, I can't lower brightness with any of the GB sense ROMs so my battery gets murdered when the screen is on. I'm digging the new sense though.

xHausx said:
Glad to hear that, you'll want to remember not to use any RUUs or upgrade your hboot though. Unrevoked forever can be used to permanently unlock it but as is flashing a RUU will completely unroot your phone and flashing anything newer than 3.29 will prevent you from downgrading your hboot again.
I'm currently using aamikam's sense 2.1 rom from here but have been looking for another, I can't lower brightness with any of the GB sense ROMs so my battery gets murdered when the screen is on. I'm digging the new sense though.
Click to expand...
Click to collapse
What exactly is hboot? I want to make sure I don't foolishly upgrade it.

Kingcoke said:
What exactly is hboot? I want to make sure I don't foolishly upgrade it.
Click to expand...
Click to collapse
hBoot stands for hardware boot, it's just another name for the bootloader. Flashing a RUU is guaranteed to upgrade it but aside from that you shouldn't really have to worry about it.