Related
Good Morning!
If I am having issues flashing roms, can I rename the actual rom say fresh-evo-3.2.0.0.zip to PC36IMG.zip to see if that works, is there any problems that could happen from this?
I'm thinking no, but I might as well check!
Thanks everyone
Make a nandroid backup before you get started. The worst possible thing I see happening is it doesn't flash and you have to restore. I've never personally tried it. I'll guinea pig myself in a few and see if it works with one of my ROMs.
*Edit* Tried it, it doesn't do anything. Loads just like a normal PC36IMG.zip, but doesn't actually go through the write process. No consequences, just had to reboot. I know it doesn't help, I figured I'd just let you know.
If you change the name of a zip it becomes unsigned. If you used unrevoked forever you should have s-off so shouldn't be as big a deal if not then it wont flash anyway. Either way i do not suggest doing this. what problems are you having with flashing? there may be an easy fix.
Also nand backup before you do anything
omegasun18 said:
If you change the name of a zip it becomes unsigned. If you used unrevoked forever you should have s-off so shouldn't be as big a deal if not then it wont flash anyway. Either way i do not suggest doing this. what problems are you having with flashing? there may be an easy fix.
Also nand backup before you do anything
Click to expand...
Click to collapse
I cannot flash any roms except DC 3.5 and CM6 (including nightlies)
All others just hang on the HTC EVO 4g screen forever, 15+ minutes before I give up.
I think I have tried everything.
what is your flash procedure. you are wiping completely (data cache dalvik) between flashes correct?
If you are installing custom themes,kernels, etc are you booting up the rom fully before going back to flash?
what rom are you trying to flash
omegasun18 said:
what is your flash procedure. you are wiping completely (data cache dalvik) between flashes correct?
If you are installing custom themes,kernels, etc are you booting up the rom fully before going back to flash?
what rom are you trying to flash
Click to expand...
Click to collapse
I am not messing with themes yet,
Yes I do a full wipe/ cache / dalvik between each, I have even tried to do each a few times, I even unrooted/rerooted with no results.
Right now I am trying to flash to Fresh 3.2
are you using clockwork recovery or amon ra? have you tried flashing with the other?
omegasun18 said:
are you using clockwork recovery or amon ra? have you tried flashing with the other?
Click to expand...
Click to collapse
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
hm what root process did you use you are 100% positive you nand is unlocked?
It is very very weird that you can flash dc 3.5 and nightlies but not any other roms. My first thought was you were having the clockwork failure to wipe cache problem but if you tried ti with the latest amon too and still ahve the issue that isnt it.
Have you hooked it up to your pc and run a logcat through adb while it was sitting at the splash screen to make sure it was boot looping?
omegasun18 said:
hm what root process did you use you are 100% positive you nand is unlocked?
It is very very weird that you can flash dc 3.5 and nightlies but not any other roms. My first thought was you were having the clockwork failure to wipe cache problem but if you tried ti with the latest amon too and still ahve the issue that isnt it.
Have you hooked it up to your pc and run a logcat through adb while it was sitting at the splash screen to make sure it was boot looping?
Click to expand...
Click to collapse
I used the simpleroot method when it first came out.
How can I confirm if im 100% nand unlocked? I am able to do a full nand backup/restore if that matters.
I have not done a log cat, anymore info on that?
you should be nand unlocked but if you used simple root you should be able to load your hboot if you have .79 you are not nand unlocked.
to get a log cat have your phone plugged into a computer that you can use adb on. go to the android sd\tools directory type adb logcat
it should then start listing everything your phone is doing watch it and see if you can see it repeating commands. may take a few minutes
I have .76
omegasun18 said:
you should be nand unlocked but if you used simple root you should be able to load your hboot if you have .79 you are not nand unlocked.
to get a log cat have your phone plugged into a computer that you can use adb on. go to the android sd\tools directory type adb logcat
it should then start listing everything your phone is doing watch it and see if you can see it repeating commands. may take a few minutes
Click to expand...
Click to collapse
Ok, I got logcat going - I should try again and watch for activity, or?
yes try again
also after you flash if it freezes and nothing shows on a log cat try pulling the battery abnd then restarting has worked a few times for me.
omegasun18 said:
yes try again
also after you flash if it freezes and nothing shows on a log cat try pulling the battery abnd then restarting has worked a few times for me.
Click to expand...
Click to collapse
It just says -waiting for device-
alright let me think a few and see if i can come up with anything. its very very weird that you can do 2 roms but not the others.
omegasun18 said:
alright let me think a few and see if i can come up with anything. its very very weird that you can do 2 roms but not the others.
Click to expand...
Click to collapse
yea i know, I am stumped!
Defpdp said:
yea i know, I am stumped!
Click to expand...
Click to collapse
Is there anything I need to update/delete before I go forward?
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
OK, I have been testing the Unrevoked rc3.21 that comes bundled with clockworkmod
There seems to be an issue with how it does the nandroid backup. I have tested on my own device and another collegues
We are both running stock 2.2 2.10.508.2 hboot .93
flash went fine, rebooted to recovery, did nandroid backup of rom, reboot from recovery = boot loop
on my friends we did the same but this time reapplied clockwork from rom manager, did nandroid backup from rom manager - boot loop
To resolve the issue you simply restore the very same backup you just created
This leads me to believe that there is something going on where the backup process is actually corrupting system files after it has take a backup of it.
as said this has been duplicated and on top of that other people have reported it on unrevoked's bugreport list
I know you are not part of unrevoked but it seems to be clockwork mod with these new versions of desire that is causing a problem
http://git.unrevoked.com/redmine/projects/unrevoked3-testers/issues
Click to expand...
Click to collapse
Rastaman-FB said:
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
Click to expand...
Click to collapse
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
gosa said:
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
Click to expand...
Click to collapse
was it you i was talking too on freenode yesterday?
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Juggalo_X said:
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Click to expand...
Click to collapse
the very same clockwork and to rule anything out we also reflashed the recovery using rom manager too.
same thing
its to do with the .93 hboots and the ruu version of froyo used i think. clockworks backup borks it lol
Rastaman-FB said:
was it you i was talking too on freenode yesterday?
Click to expand...
Click to collapse
yeah, that was me...
Also on 2.5.0.7 and with recently flashed RUU from HTC.
And btw -
I've seen a lot of incidents ("tickets") on Unrevokeds site about Desires getting stuck in boot loop after backup.
I do not know however we can reach all of them to get more people to verify. Maybe speak with the developers of Unrevoked?
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Rastaman-FB said:
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Click to expand...
Click to collapse
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
gosa said:
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
Click to expand...
Click to collapse
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Rastaman-FB said:
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Click to expand...
Click to collapse
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
gosa said:
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
Click to expand...
Click to collapse
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Rastaman-FB said:
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Click to expand...
Click to collapse
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
gosa said:
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
Click to expand...
Click to collapse
aye, can understand that. its up to you really
im surprised clockwork mod havent passed comment on it though on their own forums.
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
hamdir said:
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
Click to expand...
Click to collapse
thanks for coming here and reporting this, the more info we get to them about it the quicker theyll try and fix it as if this is about on full release there is gonna be some spammage about bricked desires
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
priestnot said:
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
Click to expand...
Click to collapse
yes
10char
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
priestnot said:
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
Click to expand...
Click to collapse
I cant answer that as i dont have .92 and ive not seen anyone report it on .92
Has this been fixed yet??
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.
So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.
MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828
_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.
OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha
Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
BrashL said:
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
Click to expand...
Click to collapse
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
k2buckley said:
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
Click to expand...
Click to collapse
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Lol, I gave him detailed instructions on how to flash it using the bootloader, don't worry. I was pm ing with him.
Sent from my PC36100 using XDA App
r916 said:
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Click to expand...
Click to collapse
He uploaded a recovery image in a PC36IMG, so it NEEDS to be flashed in the bootloader.
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
100proof said:
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
Click to expand...
Click to collapse
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Think we have different problems. Every time I try to flash something new it completes fine, but it still boot loops. Hell, yours might be fixable.
I've tried everything now with no luck. Everything updates and completes but has absolutely no effect on the boot looping. This is really insane and my advice to anyone would be to stop using CM7 immediately as it seems to be confined to that ROM.
If anyone else has had this exact problem please post, I want to get a tally of how many people are affected and try to find a commonality.
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
But my phone ran for a month without any problems except for some random reboots which seem to be common with this phone in general. I didn't add software or flash anything before this happened, it just happened. That seems to be the experience most people are having, the only thing in common is that they were running CM7 or had been running it recently and tried to flash to a different rom.
What software problem wouldn't be corrected by a successfully completed reflash with a stock RUU? That's the major question.
Hmm, that is awkward; at that point, I would just take it in if you're still getting random reboots. Been on CM7 for the longest and no random reboots on my end.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I agree, that is exactly what they should.
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
BrashL said:
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
Click to expand...
Click to collapse
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
teh roxxorz said:
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
Click to expand...
Click to collapse
Already tried it, no dice. Goes through fine but then keeps bootlooping. On a side note, is there a way to get S-On through the bootloader since I can't access recovery?
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
teh roxxorz said:
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
Click to expand...
Click to collapse
Did that buy still S-Off
http://www.shipped-roms.com/shipped/Supersonic/ Did you run the right RUU for your software version?
And I'm heading tot he gym for ~1hr; you can pm me in the meantime and I'll answer when I get back if you still need assistance.
dougjamal said:
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
I'm sorry I wasn't clear . Days of reading every post in any thread I can find has left me running on no sleep. The huge problem is that no matter what recovery rom is flashed it wont let me boot into RECOVERY MODE. It flashes fine whether it is from the sd or through cmd using fastboot (Ive tried almost every version including the newest of both Amen RA and Clockwork). This gets me stuck in the white HTC screen boot loop. If I flash a RUU it will at least hang with a partition error and get stuck in the four triangle error, which will at least let you charge the battery so I can start all over again. Is there maybe a way to wipe the partition or reformat in fastboot as that is really the only thing working (regular adb wont detect). It seems a ton of people have been popping up with this same problem out of the blue the last few days.
Rooted and flashed rom. now when I reboot, it keeps boot looping. I went back to stock, still boot looping. any ideas?
Try flashing the newest radio. I think I read somewhere on here that older radios were causing a boot loop on some of the newer sense roms, although I'm not sure why it's still happening after going back to stock. I'm assuming you wiped data/cache before installing these? Anyway, try flashing the latest radio, worth a shot.
dtbingle said:
Try flashing the newest radio. I think I read somewhere on here that older radios were causing a boot loop on some of the newer sense roms, although I'm not sure why it's still happening after going back to stock. I'm assuming you wiped data/cache before installing these? Anyway, try flashing the latest radio, worth a shot.
Click to expand...
Click to collapse
after i went back to stock no more cwm recovery. do I need to run revolutionary again?
nyccharlie said:
after i went back to stock no more cwm recovery. do I need to run revolutionary again?
Click to expand...
Click to collapse
Yep, run revolutionary again. Once you start it, revo will say something like "what do you think you're doing you're already s-off blah blah" then it asks if you want to install CWM. Hit y and it will download to your phone/install.
Can I flash the newest radio without cwm? when I did the update, and had to activate my phone, it did the bootloop. not sure if i'm screwed at this point.
answered my own question. thanks all for your help!!