I recently rooted my EVO and made a backup using rom manager. While I was rooted I was able to enter recovery mode after holding the volume down and pressing the power button. Today, I unrooted my EVO and cant seem to get back into the recovery mode. When I try to do enter recovery mode, I get a symbol of the phone with a red triangle (or something like that). IS there anyway to enter recovery mode (so i can restore my phone to my backup) while unrooted? Thanks
That is recovery... if you want to access the commands hold power then vol up once you are inside that screen, you should get a blue menu with the recovery options.
Oops didnt read the 'unrooted' part... yes once you unroot you lose custom recovery. Ideally you should root your current stock then install your preferred custom recovery and then restore your backup.
When rooted you were using a custom recovery. The only way to get this back is to root the evo. You also can't use nandroid on unrooted phones.
Sent from my PC36100
Thanks alot. That did get me in. I was wondering if there is anyway to access my sd card so that i can restore the backup i had made when I was rooted?
Thanks rafroelich. I tried to re-root my phone (after i did the ota update today) using unrevoked and it didnt work.
I was hoping there was a way access my backup from the recovery screen.
Thanks fenixjn. Would you know if it is possible to flash ur backup from the sd card using the computer?
Its just kind of annoying because I can see my backup on my sd card and i was wondering if there was any way to restore it even though I am not rooted right now?
To restore a backup made while rooted, you need to be rooted. To user your backup, you would need to root again, and install a custom recovery.
However, if you have s-off, you should be able to flash the pc36img of the recovery you want (used previously) and restore from there.
Sent from my HTC SuperSonic 4G using the XDA app.
If your bootloader still shows S-OFF then you can flash a custom recovery and restore, otherwise you are SOL.
xHausx said:
If your bootloader still shows S-OFF then you can flash a custom recovery and restore, otherwise you are SOL.
Click to expand...
Click to collapse
^^ What he said. ^^
If you have unrevoked forever installed, you should still be s-off.
Damn. My bootloader shows S-On after I unrooted the phone. I went back and tried to root the phone after i installed the OTA 3.70 but unrevoked didnt work.
would you know of any programs that allow me to enter into a custom recovery so I can do a nandroid backup restore.
Nucs said:
Damn. My bootloader shows S-On after I unrooted the phone. I went back and tried to root the phone after i installed the OTA 3.70 but unrevoked didnt work.
would you know of any programs that allow me to enter into a custom recovery so I can do a nandroid backup restore.
Click to expand...
Click to collapse
What are your hBoot and Radio versions? You may be able to re-root and install a custom recovery. Even if you unroot as long as you keep the custom recovery it should retain full functionality to do nandroids.
Nucs said:
Damn. My bootloader shows S-On after I unrooted the phone. I went back and tried to root the phone after i installed the OTA 3.70 but unrevoked didnt work.
would you know of any programs that allow me to enter into a custom recovery so I can do a nandroid backup restore.
Click to expand...
Click to collapse
AFAIK there are no other programs other than unrevoked to flash a custom recovery in automated mode from the computer. As an earlier poster said: your best chance is to check your hboot version and see if it is possible to root again using the manual methods like the one for 2.02.
If not them you must wait until someone checks a way to root 3.70 and use stock in the meantime.
Sent from the iPhone Assassin
It's possible to restore the backup, I don't suggest doing it. If you follow the 2.02 manual root method you can do everything except S-OFF. Since you are HBOOT 2.10 it is slightly more a pain in the rear because you have to do a lot of the steps in terminal emulator on your phone instead of cmd prompt on the computer. In short you can run the rage exploit to get su on terminal and then use terminal to flash the mtd-eng.img. Reboot into bootloader and go to recovery and wait for it to fail out to the red triangle screen. Then you can use your computer command prompt to push recovery, install busybox, and get recovery started. I don't think recovery will stay on after a reboot though because you are S-ON.
It would at least allow you to restore the nandroid backup. However, you are on the new radio files, which means you would have to also flash the new stock kernel or you will get stuck in a boot loop.
You also will not be able to get S-OFF because unrevoked forever is not compatible with the new radio file. And people are having trouble downgrading the radio right now it seems.
xHausx...my hboot version is - 2.10.0001
my radio is - 2.15.00.11.19
Is my best bet to wait until a root comes out for this new version that I installed yesterday?
Its so annoying because I can see my backup there but cant access it. My main issue was that when I unrooted I realized that my contacts where saved on my phone a little bit too late. Now it seems that I cant restore them from my backup until a root is available for this OTA.
I got some great help with this issue on other forums. I was advised that maybe getting an older hboot will help. Does anyone know if it is possible to return to an older hboot so that i can root and enter recovery to restore a backup?
Related
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!!!!
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
Hi folks,
For some reason my Amon Ra recovery is now refusing to flash zip files and it look as if I'll have to reflash the recovery itself. Can I do this via ADB on an S-ON phone, and if so, how? If not, is there an alternative method? Unrevoked isn't working at this point as I have already wiped my old ROM.
Background: I think I b*ggered the recovery by having the USB cable connected at boot time. There is a mention somewhere of Clockwork mod misbehaving in these circumstances, and I think the same may apply to AR. The phone will boot into AR, but AR won't load/flash any zip files.
Please help!
Via ADB? No.
S-ON? No.
You have to be s-off to flash another recovery via FASTBOOT.
Try taking out the battery and re-enter AmonRA, see if that works. Also what error you get?
Thanks Davebugyl!
Sorry, no joy. There is no error at all, just AR refusing to flash the zip. I've had this once or twice before, and usually by shutting the phone down and restarting I got AR to work again. Not now.
I'm happy to S-OFF the phone with Alpharev, only I'm not sure you can do that with no ROM installed. Any thoughts?
Well the phone must be booted to use AlphaRev's S-OFF method. Do you have any nandroid backups? You can use one to boot up, then S-OFF.
If not, then the only thing what comes to my mind is to flash a RUU and root/S-OFF again.
I have a nand backup but I can't get it to boot. Can you flash an RUU to an S-ON phone or would you need a Goldcard for that - which I don't have..
If you are unlocked (HTC_WWE) - then it should go without a goldcard.
Alternative solution in second link:
http://forum.xda-developers.com/showthread.php?t=619153
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/644-super-noob-guide-unlocking-bootloader-modacos-rom-amon_ras-recovery.html
The latest is for the Nexus one, but should be working on the Desire.
Many thanks for your help! Will try that shortly, and let you know how it went. The phone was a German T-Mob when I bought it but it's not locked to any network (I bought it and am using it in Switzerland). Fingers crossed!
Update: I found an old Nand backup which did work, and successfully re-rooted with Unrevoked to install a fresh copy of Clockwork recovery, and went S-OFF with Alpharev. Great stuff, ŧhanks for your advice!!
Hi,
I have a TELUS HTC Desire that was already rooted when I got it.
It has HBOOT 0.93
I didn't know that my phone was SLCD so when I used ROM Manager to flash recovery, it messed up my recovery.
If I go into hboot, and press down arrow to boot into recovery, I get the black screen with the little phone and the red triangle with the exclamation mark.
I was desperate enough to try the ClockworkMod Recovery for the HBOOT 0.83 (ClockworkMod Recovery v2.5.0.1 SLCD)
from hxxp://forum.xda-developers.com/showthread.php?t=748618
flashed that on with UnrEVOked but didn't work. Recovery is still messed up.
I googled and searched for a week to find something for HBOOT 0.93 but I never find anything. Everything is for 82, 83 and 92. There are other people who asked about 0.93 in other threads but there are never answers to them.
Does anyone know of a proper ClockwordMod recovery img or ANY recovery img I can flash for my HBOOT 0.93
My phone is already android 2.2 but i would really like to flash to LeeDroid
Should I reflash my phone with the RUU to get rid of any dmg done? The only thing i'm afraid of is that my phone will be unrooted because of the RUU reflash and I can't find a way to root it.
If it's not possible to use UnrEVOked or Rom Manager to install LeeDroid because of HBOOT 0.93, I'm willing to manually do it.
But will the LeeDroid flash properly onto my phone if it's HBoot 0.93?
Does the flashboot thing when i boot into the HBOOT work for installing custom ROMS if I can't get into recovery? I noticed it will load images...but not sure exactly what the fastboot thing is suppose to do.
Thanks!!
HBOOT 0.93 is not the problem, neither is your SLCD. Use fastboot to flash your recovery, I suggest use either AmonRa 2.0.1 or CWM 2.5.1.8.
CWM from ROM Manager isn't the best recovery for your HBoot as I think it flashes 2.5.0.7 which is no good on your HBoot.
You can't flash a ROM from fastboot, you need recovery. Once you've done that, LeeDrOiD will work fine on your setup, but I would suggest you study up a lot more before proceeding, for one thing, it's easy to find a lot of info on HBoot 0.93 on this forum, secondly, get to know fastboot etc as you needs to know this for when things go wrong with cheat/easy methods like ROM Manager.
Take your time, be confident you know what you are doing it before you do it, you don't want to brick your phone.
Both of you need to know quite a bit more, but especially the OP...
But no he can of course not flash an unsigned recovery from fastboot without being s-off, and from the sound of the first post I'm confident he's not.
ghalalb is right though when he states that this has nothing to do with your bootloader version or slcd, and i really can't imagine how you can get the simple instructions on here wrong, but please simply use unrevoked via usb. It comes preloaded with a perfectly fine recovery for you, and also i believe you should really reconsider the decision to hack your phone with this little knowledge on the subject.
Also 2.5.0.7 vs 2.5.1.8 has nothing to do with hboot versions.. Both will work fine if flashed correctly, but the problem with just making rom manager flash the recovery is, that it is not quite up to date, so it does not actually flash anything. It just downloads an update.zip file, which loads the recovery when flashed. This fixed the problem of not being able to flash a custom recovery back before unrevoked came around. And to correct you on another thing you got wrong, yes you can actually flash a zip file containing something like a rom from fastboot if you are s-off. It will probably just not work exactly the same way, as the recoveries does.
That's interesting that you say hboot version and slcd has nothing to do with the ClockworkMod when other threads are very specific about which clockworkmod version you should use depending on your hboot and if your phone is slcd or not.
Also last time I did an update to the phone, it just used the fastboot. Didn't go into recovery.
I followed the exact instructions for unrevoked but an error occurrs when it tries to unroot...All I wanted to do was flash the recovery and not unroot the phone since it's already unrooted. So probably that's why it was having problems. But the recovery was still messed up after unrevoked did it's work.
I wonder if part of the problem is because I'm using a test image and not the actual production image for the phone. Which is probably another reason why the phone was already unrooted.
I'll try to reflash my phone using the RUU for a production image and try Unrevoked again just so everything is clean from the start
Trust me it doesn't matter. The only problem was on slcd phones back when they first came out, where cwm didn't contain the drivers for the new screen.
That is why it says it's for 0.83, as back then 0.83 was equal to slcd and all amoled models had come with 0.75 or 0.80. But now after the newer updates everyone is on 0.93 or so, and all newer cwm recoveries will work for both amoled and slcd. So no there is not a specific recovery for every bootloader, and there is no way a flash from rom manager messed your recovery up, as it never flashes anything.
And i think you might need to slow down and think about what you are doing? Because you talk about unrooting with unrevoked, and unrevoked will probably try to root your phone If you use unrevoked correctly you will have it working fine.
Also you say last time you updatet it, it used fastboot? updatet it officially? As then there is a reason you have the stock recovery. But try using the ruu and then go back to rooting using unrevoked or just keep it stock, as it might not be a good idea trying something without knowing what it does.
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.
mortenmhp said:
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.
Click to expand...
Click to collapse
Thanks for your response I thought that the triangle screen was bad since I tried the volume stuff and I couldn't get to the screen.
But if that's the stock htc recovery, then that means the clockworkmod recovery wasn't flashed properly?
I will try the keys again when i get to the recovery state later.
Actually I was having problems with UnrEVOked because my phone was ALREADY rooted. So it was trying to do something that was already done which is probably why it failed. I only needed unrevoked to flash the recovery...I didn't need it to do anything else but the recovery.
What I have on my phone right now is not the official load. It has test keys and crap in it....
Anyways, I'll see if I can get into the recovery menu properly before doing the RUU flash to have a clean start.
Ok Unrevoked should work fine anyway though. It just flashes a recovery and the su binary plus the superuser app. So if you are rooted it will just overwrite them. Your problem is far more likely to be a driver problem.
I rooted the old way as well(the one only allowing test keys signed roms) and then i used fake flash from rom manager until alpharev s-off came along, and now i just flash everything but roms from fastboot, it's far easier.
driver problem?
I followed the unrevoked instructions and my computer recognizes the phone while it's in bootloader
i can also adb shell into it when it's just normally powered on etc
oh and to answer previous question, yes i updated to 2.2 using fastboot
i put IMG99.zip onto my sdcard
powered on while holding the volume down for fastboot
it went and found the image on my sd card and grabbed it...and asked if I wanted to update...and viola...2.2
my phone was...2.0 or 2.1 when i first got it i think...i forgot what it was before 2.2
that's why i asked if anyone just stuck a custom rom into their SD card and tried using fastboot before....seems like everyone these days use things like rom manager, unrevoked etc >_<
I would think that the fastboot would find the zip file and can unzip and load it just like how it did the testkey one i did before....but i thought i would ask before i tried....maybe i should wait next week until i'm at home and have sd card readers in case anything goes wrong so i can recover the phone easier lol
There is a reason why people don't do that.. When you flash that way via fastboot, it only allow zip files signed by HTC, if you are s-on, and those write everything on the system to stock, which means you lose root and custom/modified recovery.
You could potentially do it that way if you were s-off, but the bootloader flashing utility does not allow as sophisticated commands as the custom recovery does, so everything in the original roms is actually packed in .img files for every partition.
All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!
Yep new page size will require the modified cwm for it, but it still has nothing to do with hboot version. However the other recoveries should flash ok as well, they just won't work well for installing roms(gave some error), which he hasn't come to yet
ghalalb said:
All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!
Click to expand...
Click to collapse
I found the same thing that only unrevoked 3.2 would work with my device.
I finally managed to flash the custom rom and is what i did to make it all work >_< Maybe it'll help someone else
I started with a fresh official load by flashing the RUU.
Then I used unrevoked that you can download from their website
I still got an error. CID missing. I go searching for it and it seems like a common enough error that the unrevoked team had addressed it
Because of the error, it was not able to unroot and flash recovery properly. The only thing it did was s-off.
So 2 ways to get root/recovery on your phone
1. Manually....find a PB99IMG.ZIP file that has root in it and flash that, then you can either use rom manager to flash the recovery or do it manually as well.
I created my own PB99IMG.zip with the recovery image of clockworkmod for desire using the android info .txt file I had in my other PB99IMG that contained the root access. Put the PB99IMG.zip into your SD card, go to Flash boot and let it do it's magic.
2. Easier way, get unrevoked 3.2 ... There was a warning for using it. Apparently you should only use the 3.2 version if you get the CID error.
But with unrevoked 3.2 it will give you superuser and the recovery image without you doing anything so it's easier.
So after I finally got Root, I backed up my sd card onto my comp.
Then I partitioned my SD card using ROM manager.
Once that was done, i flashed into recovery to do a backup.
After that I tried using ROM manager to flash leedroid...
it looked ok but it never managed to get past the splash screen after 20mins so I pulled the battery and rebooted
Same problem so I decided to flash manually.
Went into recovery and cleared everything then flashed the rom from SD.
Now I'm on leedroid
So far it looks exactly the same as the stock rom. It has everything I need so I'm happy.
I hope this helps anyone with similar problems.
Sometimes you just can't take the easy way out and have to do things manually
Okay, so here's the deal. I have an Evo. I rooted it using unrEVOked, updated the Clockwork and all was well. Well I started having a few issues so decided I wanted to RUU back to stock. Well then I noticed it still said S-Off and had the Revolutionary thing at the top in the Fastboot menu. I then tried running the Revolutionary Root and it said it had the S-Off already. It asked me if I wanted to download install Clockwork so I did. Now I currently have no recovery and don't believe I have root. The phone still powers on and works functionally. I am just wondering how to regain my root and recovery. Any ideas?
You have s-off correct but no recovery? Is that right?
Sent from my PC36100 using XDA App
Yes, and I used root checker and it says I have no root.
Have you tried flashing a recovery like amon ra
Sent from my PC36100 using XDA App
You need the two attached files.
Place the PC36IMG file (after you change the name to PC36IMG) on the root of your SD card. Then run the update through your bootloader (power off, then volume down + power button).
Then flash the su file from your new custom recovery.
Root access is a combination of S-off and the superuser app within whatever ROM you are running. If you had a stock rooted ROM or a custom ROM loaded onto your phone then you dont need to flash the superuser file as these already include superuser.
If I'm reading your original post correctly, and please correct if I am mistaken, your phone was/is already rooted. The only thing that seems to have changed was the fact that you somehow do not have a recovery. Instead of getting flash happy, try loading the recovery first via shorty's attached copy of Amon Ra. Then try to boot up into Android. Then you'll have three options.
1. The phone boots up and you have Superuser in your app drawer: Enjoy your rooted phone.
2. The phone boots up and you do NOT have Superuser in your app drawer: flash Shorty's attached Superuser file.
3. Phone does not boot into Android: Reflash a rooted stock ROM or a custom ROM of your choice.
I suggest doing it this way because you seemed to screw up your phone by doing what most would call a simple flash. It would be counterproductive to risk your phone's functionality by flashing something you don't absolutely need to flash.