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.
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!!!!
Guys i have a question regarding the htc splash screen. I rooted twice today just to test a few things.
When i rooted for the first time i used windows 7 + hboot drivers from unrevoked3 site and flashed/rooted my device (stock rom (froyo)). Everything worked fine but when i run clockwork recovery mode and select the backup option i get something strange.
My device is backing up and it says it's done, when i select the reboot option my device get stuck at the splash screen and reboots, hangs, reboots, hangs, reboots etc. I need to pull the batteries off to get back in recovery mode. This time i select restore and select the backup i created before all this happend. Now it's passing the htc splash screen.
Because i thought i got problems with the windows drivers i decided to root with linux, so i installed the official ruu update over my rooted rom and root it under linux to make sure i am a bit saver.
Now when i do a backup and reboot again i get the same thing ? it hangs at the splash screen. Is the unrevoked recovery tool bugged (clockworkmod) ??? because when i restore with the backup i created it is passing the htc splash screen again.
I don't understand.
(Sorry for my bad English)
PS: I used this rom to root. http://forum.xda-developers.com/showthread.php?t=828519
As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone..nt sure though..wait for a reply from someone who is experienced..i hav been using android since past 3 months only
Sent from my HTC Desire using Tapatalk
What you could try is this.
Use unrevoked again, but in unrevoked select a alternative recovery image.
Then load this image http://forum.xda-developers.com/showthread.php?t=839621
This is the amon-ra recovery. And for the record, you can root with unrevoked as many times as you want
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes
Oo..i thght it is similiar to jail breaking tht needs to be done onl once...lolzz
Sent from my HTC Desire using Tapatalk
lordvoldemort said:
As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone
Click to expand...
Click to collapse
You really didnt read well didnt you ? it already happend the first time i rooted . Secondly, if i root and install a official ruu update over it everything will get wiped and cleaned....so there would be no problems when i decide to root.
Lennyz1988 said:
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes
Click to expand...
Click to collapse
Yeah i am sure....after backup the phone showed me the menu screen that i could select options such as rebooting the phone. When i reboot after backup it doesnt get passed the splash screen and reboots (and those steps gets repeated). If i don't use recover....my phone is dead
- Flash a stock ruu (rom)
- Then root again and use amon ra.
Lennyz1988 said:
- Flash a stock ruu (rom)
- Then root again and use amon ra.
Click to expand...
Click to collapse
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.
MichelN said:
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.
Click to expand...
Click to collapse
This seems to be a documented problem with Unrevoked. The first reboot after rooting and backing up Nandroid seems to hang the system for some, and restoring the Nandroid fixes it. After restoring the Nandroid (as you did) there should be no further problems. And since you did that, your problem should have been fixed. And since you restored to a rooted copy, why did you have to try again with Linux? Your problem was already fixed by the Nandroid Restore..
unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead
EddyOS said:
unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead
Click to expand...
Click to collapse
Thought the 1st Nandroid Restore fixes it..Does Clockwork mod still pose probs?
Clockwork Mod is the issue - flash AmonRA from the start and you won't have this issue (or I never have anyway, use AmonRA as you can partition SD cards in it)
I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...
protuger said:
I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...
Click to expand...
Click to collapse
I didn't have 2 black lines, mine rebooted after it couldnt pass HTC splash...i needed to remove battery or it keeps rebooting.
What i did with clockworkmod is restore (the backup you created before rebooting)....this should fix the problem. If this is not the case then i don't know because i never rooted before. You should ask a expert.
Anyway because i needed to restore anytime i posted this topic, people said i should use AmonRA. So to do this i installed the latest official ruu (posted by EddyOS) (to make sure everything is clean and good again). Then i used linux to make sure it is saver.
When you downloaded the unrevoked3 tool open it and don't plug you phone yet, go to options and select custom recovery. Now select the AmonRA (latest version i used) to flash with unrevoked3. Now plug in your phone and relax.
The only thing i am scared off is to flash hboot to go s-off.
Actually the cause of this problem was when i have tried the method for s-off...sad...
When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.
protuger said:
When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.
Click to expand...
Click to collapse
Try flashing true Linux. Download Ubuntu and this way you can boot your pc in linux.
Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.
protuger said:
Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.
Click to expand...
Click to collapse
You need root rights in ubuntu, use google to find it
thanks hope google stops my sleepless nights...
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
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.
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!