Related
got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??
Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?
Nothing is working!!
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?
I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before
This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip
playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..
Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.
Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok
Hi all. I am a noob at this rooting and flashing business, and I probably did something stupid so bear with me.
The other night I rooted my Evo with Unrevoked. That same night I flashed Baked Snack 1.9 using ROM Manager. Prior to the flash, I backed up my phone using ROM Manager. It was fast and everything but I decided I wanted Gingerbread (a la Salvagemod). I backed up my phone in a similar fashion, and flashed the ROM once using ROM Manager. When rebooting, my phone became caught in a boot loop. After searching through Google for a few minutes, I learned that I simply needed to clear my cache and my dalvik cache. After clearing cache, flashing, and attempting to boot several times (all in clockworkmod... or recovery... or whatever it is called (yeah i suck)...or whichever one is orange!), I gave up and decided to restore to my second ROM Manager backup - that of Baked Snack. Error! "No files found!" I tried my previous backup. Same message.
Looking back on that, I chose "install zip from sdcard" instead of "nandroid". That was a fail.
So I decided to re-use unrevoked. Everything went fine on the PC end, but the only thing that changed on my phone, is that when it boots, it gets stuck on "htc evo" in the white screen. That and clockworkmod is now teal. I disovered the nandroid option on the recovery menu. I navigate to that, then to restore, then to my Baked Snack backup. This gave me the message "Error while flashing boot image". I tried it one more time, except instead of picking recover, I accidentally picked backup (stupid stupid careless, i know). It failed and said "Can't mount /data/!".
Then I decided to go onto xda-developers and here I am now. If you are through facepalming, I would appreciate it if anybody could help me recover my data. I believe I can still flash a completely new ROM (But what do I know? I haven't proven to be the smartest Android guy), and I don't know about you guys, but I like keeping my data.
So, uh, yeah. That's that. Help please.
I'm sorry to hear you are having issues with your phone. It looks like you still have a nandroid backup, unless you formated your SDcard. Clear data, dalvik cache, and cache then run do a restore. When using clockworks recovery clear out the data, dalvik, and cache three times.
Hope this helps.
I have performed all three wipes. After that it reads
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Same as before... Any thoughts? Could the boot.img file be corrupted?
***bump***
Edit: Ive read around some more and heard 2 things. 1) If I just try recovering over and over again, nandroid will eventually give in. 2) the battery has to be 70% or higher or nandroid will just keep giving error messages.
Either way, I'll juice up my battery and report back later.
Have you tried to just do a wipe and reflash the ROM.
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
bccbryan said:
Have you tried to just do a wipe and reflash the ROM.
Click to expand...
Click to collapse
Yes. I tried it again just now because I was feeling lucky. Salvage Mod went smoothly, except it got stuck on the white htc screen when I rebooted. Baked Snack gave me an error message:
Code:
E:Can't open /sdcard/download/BakedSnack1.9.evo.zip
(bad)
Installation aborted
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
I'll try that tomorrow morning. Right now I'm gonna get some sleep before I do any more damage to my phone lol. Expect more questions from me about WiMAX and what to do with that .img file (if anything at all).
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
I believe if you don't update your radio and are running a certain kernel you will get a bootloop, but don't quote me on that.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
bccbryan said:
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
Click to expand...
Click to collapse
I'm 95% sure that I do, I got my EVO in December.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
Click to expand...
Click to collapse
It says S-OFF, so that's good news.
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
When I try to recover, it givese me an error saying that the nandroid directory could not be found. I have my backups in a folder called /sdcard/clockworkmod/backup/NameOfTheRecoveryFolder/. Should I just copy the files in the backup folder to a folder on the root of the card called "nandroid"?
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
Click to expand...
Click to collapse
Yep...just need the PC36IMG.zip and boot to the bootloader.
Since you got your phone last December I think you need to run a rom that is based off the latest code. If you are running htc sense it should be based off 3.70.651.1. For ASOP run the lastest ones.
Here is a nice wiki of the ROMs for the EVO http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
bccbryan said:
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
Click to expand...
Click to collapse
This would be the file called "nandroid.md5"? I'm confused.
OK so I boot into recovery, go to Nandroid restore > BackupName
I am presented with a list of options:
boot.img
recovery.img
wimax.HT0CRHL08393.img
system.img
data.img
cache.img
nandroid.md5
Do I just run each of these individually or am I doin it wrong?
Don't do a nandroid restore. Flash a ROM onto your phone.Fresh EVO or Myn’s Warm TwoPointTwo are good ones to try.
Works great! I lost all my data but I'd rather have a wiped phone than a dead one!
Thanks!
When you used Unrevoked to root your phone it also downloaded Clockwork Mod recovery v. 2.6.0.1. This is what you probably used to do your original backup right after you rooted your phone (http://forum.xda-developers.com/showthread.php?t=895208). You need to go back to this version so you can restore any backups you may have made right after you rooted your phone. Here is an article by Koush explaining why you may be having problems. At the bottom he has v.2.6.0.1. Install it on your phone and then proceed restoring your backup.
Also, I'm going to suggest to you that you read the articles below to get you familiar with rooting, and then I suggest you read some more on these and other forums. Learn the rooting vocabulary and processes involved (rooting, nandroid backup, recoveries, flashing ROMs, kernels, etc.). Also, try and read up on problems people have rooting, flashing ROMs, and troubleshooting should something go wrong. You want to be able to get yourself out of a mess should problems arise. Most importantly, you want to know what you're doing so you don't brick your phone.
http://forum.xda-developers.com/showthread.php?t=865204
http://forum.xda-developers.com/showthread.php?t=790427
http://forum.xda-developers.com/showthread.php?t=881747
http://htcevorooting.x10.mx/wiki/ind...itle=Main_Page
http://androidforums.com/evo-4g-all-...g-dummies.html
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.
So my phone now will only reboot up to the HTC Incredible white screen. I'm not even sure what the issue is, all i did last before it got stuck was erase data on an old sd card i had in the phone. Then I just did a reboot and it froze on the white screen.
I'm running GB evervolv 2.3.2 with 2.6.37.4 incredikernel.
I can get into HBOOT but when i click on recovery it takes me into fastboot everytime.
What can i do to fix this????
Sorry please move this thread to the Q&A section, i thought that's where I was posting it, my bad.
Go to the Clockwork Recovery thread and download the update for a different version and try getting that to flash via bootloader. That way you can at least get into recovery if you need to flash new. Just to clear it up, did you use your phone to delete stuff off the old card, by using Astro or ES file explorer? I know ES file explorer has root access so is there a chance you could've deleted a system file on accident? All it takes is a click of the SD card icon and you're in root instead of SDcard. Also this is probably a thread more for the Q&A subforum, just an fyi
i deleted an old sd card that i don't even use for my phone, i was just putting it in there to clear out whatever was left on it. so i could use it new.
And it still bootloops even when you put your normal SD card back in?
yup, i dunno what it's deal is.
I remember an older version of cm7 on the nook color warned against formating sd cards because it accidentaly formats the boot partition, this may be a bug that exists in the rom your using.
at least you can get into hboot, you should be able to download ruu image and flash it in hboot. this would get you back to stock, then root and install clockwork, and then restore your latest nandroid.
Flash this recovery in hboot
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
It should at least give you a working recovery.
i have to rename things as update.zip in order for hboot to flash them right??
facedown41 said:
i have to rename things as update.zip in order for hboot to flash them right??
Click to expand...
Click to collapse
NO leave it PB31IMG.ZIP.
hboot can only see that name. if you rename it hboot will not see it at all.
also make sure your card is formatted as FAT32
got it into recovery so i'm just wiping and restoring, thanks for the help!
ok now i'm getting a bootloop on the cm7 boot screen...i just went to flash that new instead of my nandroid because the nandroid was from an older rom.
Did you wipe everything? Davik, Cache, Data, etc?
wiped data and cache...didn't do davik because i've never had to in the past. but i'll give it a try.
would i need to update CMW from version 2.0+ to 3 in order for cm7 to work? because it's still bootlooping
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
JWorth said:
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
Click to expand...
Click to collapse
Are you getting errors when you wipe?like when you wipe data does it say error can't mount or anything like that.... I have a feeling you may have to flash an Ruu and then reroot
Sent from my Incredible using XDA App
no, no errors. but i flashed the RUU and rerooted and everything works just fine. I flashed MIUI again and it worked perfect
thanks!
I figured that's what you would have to do glad you are back running
Sent from my Incredible using XDA App
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
rynosaur said:
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
This tends to be things go as far as ROMs partitioning my sd, always back it up externally and format/partition before transferring stuck back over to it while in phone.
I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks
Honestly you should stop flashing roms as PC36IMG because you'll forget what they are eventually. Download the rom you want, place it on your sd card, then do a full wipe, and flash it in recovery, boot up, and you should be fine.
That is what I do. but after flashing yesterday's miui rom from the zip file my system wouldn't let me do a nandroid backup. In desparation I used my pc36img update and now a I am screwed
pc36img probs
yesterday I flashed a bunch of roms from the sd card but something happened after the miui zip file
pc36img
in desparation I used the pc36img update. Now I am looking for a way to fix the system update part of the pc36img update which doesn't work. I only use the pc36img when nothing else works.
can anyone point in the direction of some good pc36img files. I am very desperate here. I have tried everything
Take it to Sprint, tell them it just broke. They will happily load stock GB, then you can start over.
KJ
it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot
Did you try wiping everything except sdcard 3 times in recovery than flashing a .zip rom in recovery
Sent from my PC36100 using XDA App
pc36img probs
I will try that. It will have to wait until monday bc I am on call this weekend. I can't lose my phone. thanks for the tip. I will post the results on monday. I hope it works. btw should I wipe with the sdcard removed?
pc36img
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?
The only PC36IMG's you should ever flash, really is recovery and RUU. Everything else you should do in recovery with a flashable zip.
jjdellorusso said:
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?
Click to expand...
Click to collapse
You hav to flash in {recovery} not bootloader
Download file (click link below) Keep as is go into bootloader let it scan hit no if it ask to update then hit recovery then click wipe then wipe everything except sdcard 3 times then hit flash zip from sdcard then go to this file that you downloaded and select it
http://link.geekfor.me/freshevo431
Sent from my PC36100 using XDA App
pc36imgprobs
tried wiping 3 times
now I can use roms but when running pc36img (sprint lovers) it always sais fail-uz (failure unzipping) should I just ignore this and move on??? I don't really know the significance of this. I can flash working roms now but something makes me feel uncertain. Why can't I update the system with the ruu? any other ideas?
pc36img probs
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?
jjdellorusso said:
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?
Click to expand...
Click to collapse
ok this is all i can think of:
1 - get the original pc36img.zip file and put it in your sd
2 - delete the amon ra pc36img.zip that you have
3 - go into bootloader and when asked to update hit yes
4 - when asked to reboot hit yes
5 - if your phone reboots fine (i will give it a pretty good amount of time) download rom manager
6 - in rom manager flash Clock Work Mod (CWM)
7 - Then make a back up (optional).
8 - scroll down in Rom manager and flash alternate recovery (this will give you amon ra w/o having to put the pc36img.zip into your sd card.
9 - do what you wanted to do at first.
jjdellorusso said:
I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks
Click to expand...
Click to collapse
You guys are talking about PC36IMG.zip as if its a ROM that is being flashed. Sprint Lovers, if I am not mistaken, is a ROM that should be flashed via recovery like all ROMs should be. You should not be flashing PC36IMG.zip files through Bootloader unless you are updating radios, RUU back to stock, splash screen updates, etc. It sounds like you are spending a lot of time flashing things via bootloader and that is what got you in this mess to begin with. Can you get into recovery? If so then download any ROM, enter recovery, wipe cache/dalvik cache/data, flash ROM, and then quit using the bootloader before you permanently screw up your phone. This problem should be able to be fixed without the use of a PC36IMG.zip file. Because you've gotten flash happy in your bootloader and as of right now you can't tell us exactly what you've flashed.
If you cant get into recovery then just download Amon Ra v2.3, flash it, and then do the steps I mentioned above. It's not difficult. Just stop getting flash happy with your bootloader.
There is a version of Sprint lovers that can be flashed thru bootloader
And for jj that might just mean the pc36img is corrupted you can download a new one but I say just nice on and use recovery instead of bootloader
Sent from my PC36100 using XDA App
jjdellorusso said:
it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot
Click to expand...
Click to collapse
"Warranty's" can be restored
pc36img probs
hmmm? I have tried everything as described above. maybe my sprint lovers pc36img has been corrupted. but I really don't think so bc I saved it in many different sdcards and in my computer. Should I try another .zip? can anyone point me to other pc36img files that may help. I must say that I do not flash anything by pc36img, but after I flashed hybrid I couldn't do anything. In desperation I tried my sprint lovers pc36img assuming I could go back. I had to many backups saved and it told me that I didn't have enough space when I tried to do a nandroid backup. I guess the take home message is to save nandroid backups to the sd card also. unfortunately mine is lost.