I'm having some major trouble with my Evo. I tried flashing from Classic v005 finale to v006 and I wiped everything 3 times. Now, I'm stuck in hboot and my recovery won't start. i have a PC36IMG file (TWRP 2) in my sdcard and says it updates but it really isn't. When I try to restart the phone, I get pushed back into fastboot. What can I do to fix my phone?
Twrp2 may have perm bricked your phone its done it to quite a few ppl hope you have ins cuz you'll need to flash a stock ruu thru hboot and send it in for replacement
ok. how do i push an ruu if i can't boot?
You'll have to put it on root of SD as a pc36img and boot to hboot/bootloader and run the update it should put your hboot back to a stock version so u can return it twrp2 had issues for several ppl and bricked their phones
Edit: does your hboot mysteriously say s-on now?
No, it doesn't. I might be screwed though because the only thing my computer sees when I plug in is the bootloader interface. Won't pick up the sdcard
try flashing a RUU for your phone and then Amon Ra recovery
Sounds like twrp2 borked it some ppl had s-on after but the not reading the phone on USB is a pretty sure sign twrp2 bricked it it was causing problems with bad blocks or something during the flash not sure what exactly it did to the phones but they were unrecoverable afterwards it screwed something up that wouldn't allow it to rewrite to the internal memory or be recognized by fastboot commands or adb
SprintLTE said:
ok. how do i push an ruu if i can't boot?
Click to expand...
Click to collapse
I've never used an RUU, but I believe it's an .exe file. I think you can run it from your PC while plugged into fastboot......from what I've seen posted over the years.
Until someone more knowledgeable gets back to you. Or if you have a SD card reader, do pc36img method, as was mentioned.
sent from xda app on drews ics
Try downloading shipped rom zip file. Load it on your root. Use a card reader if phone won't connect to PC. If it works you should still be s off. Just flash you custom rom back over it after you reflash a new recovery. I use amon.3.11.
See if that will work.
Shipped zip will over write recovery and should fix your problem.
ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?
It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium
SprintLTE said:
ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?
Click to expand...
Click to collapse
Did you flash a new recovery?
If so, wipe everything.
Try mounting via recovery.
Does it mount SD there?
You may try to partition your card again and see if that helps.
Did you already wipe and try custom rom again?
Isubbie said:
It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
It will still be s off even after running ruu I think.
To get s on you will need to flash s on before you take it back.
I would try to partition SD or wipe and flash new rom after amon recovery.
When I run the Factory Resets in Amon RA, it skips over everything on the sd card, saying, "E:Can't mount /dev/block/mmcblk0p1". The phone seems fried to me. Luckily, I have the insurance. lol, "oops I dropped it in the sink"
That sux twrp2 was a pretty neat looking recovery I'm glad I read about it after I installed it and had several failed backup attempts cuz I don't have ins so luckily I didn't attempt to proceed with flashing anything or I'd be in the same boat as you up the same creek only I wouldn't have a paddle lol
When will people check the TWRP thread and realize its a bad product ? Great idea, bad product.
Edit: I mean even after installing twrp, when will they check back to see it's hosed, before they get hosed?. This isn't a comment about you, OP. Just meant, too bad there's not a way to let all users of it know to change recoveries IMMEDIATELY.
sent from xda app on drews ics
After the backup failed twice I figured something was wrong since I had already backed up the same setup in amon ra just fine
If you ran the RUU, then either your SD Card is bad, or you're back to stock, so just take it to Sprint
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
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.
I loaded a backup of CM7 and when it rebooted it went into a bootloop and I cant get into recovery. I've tried everything even flashing CWM again and also the stock ROM image. Still bootloop!
Please help
You didnt brick it, if you bricked it, it wouldnt start. You should still be able to get into recovery, by holding the power button and volume at the same time, and getting into Hboot, then go to recovery. Im also guessing it happened because you didnt whipe cache or data before you did this. First time i ever installed a new rom i got a bootloop,
Thank you for responding. I cant get into recovery it starts bootlooping once I select recovery. I tried loading the PB image of CWM and I also tried flashing the stock RUU. Cant get past HBOOT or initial bootloop. I CAN get into fastboot ADB though. Tried flashing a backup system.img, boot.img, data.img but boot.img said error
Your welcome, im not perfect at all this so excuse me a bit lol. So your saying when you select recovery, it boots up normally to the splash screen, or am i wrong? If your able to flash things them im pretty sure your able to get into recovery. Maybe also try another version of CM7? Transferring it to your phone.
No I select recovery in HBOOT and it goes straight to the white HTC INCREDIBLE screen and begins the bootloop process. I've pushed the CWM 3.0.0.8 in a pb13img file and still wont go into recovery. I cant get the phone past HBOOT
Thats really really weird that it wont go into recovery and it starts the boot. Hopefully someone can come with some extra assistance. It isnt bricked tho, i know that. So did you try formating data and cache then before doing anything either?
No I was busy and messed up. applied a backup without wiping data/cache. Came back to a powered off phone. Tried turning it on and it was bootlooping. I cant do anything now. Even if I can get S-ON i'll just get a replacement
There's a data wipe option in hboot, have you tried that?
Sent from my ADR6300 using XDA App
Goto Doug piston's web site and follow the go back to stock. You should be able to put the stock RUU on the root of your sd card named pb31img (not sure the exact file name but it is on dougs site). When you load in HBOOT, it should recognize the file and install. If I am not mistaken, this will unroot your phone as well.
http://dougpiston.com/?page_id=108
Pb31img file is there.
I tried the stock rom PB31IMG.zip and it continues to bootloop. If I cant get it fixed I want to at least get S-On
Probably aren't gonna be able to get S-ON cause that needs to be done in recovery..
Sent from my ADR6300 using XDA App
There is also the unrevoked forever s-on tool which you flash through recovery
Sent from my DROIDX using XDA App
Yeah cant get to recovery so I'm boned.
I got VZW to send me a replacement and also got Asurion to get my an Inc2. Not sure which to send back. Free replacement with a gamble getting caught S-On, or $99 free upgrade to Inc2
what radio were you running
try flashing alternate recovery?
i also seem to remember there being a way to root through adb isnt there a way to unroot like that too?
I tried amon ra and a another one no difference. I also tried everything I could adb wise to flash different systems and erase everything. Im running the new GB radio
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
CSamson said:
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I got excited thinking there was a way to unbrick because of a step I missed. So I went to make sure the radio was right. I HAD the GB Leak 2.15.10.05.06
Right now in HBoot it shows 2.15.00.07.28
I know its not considered a brick because it still turns on but there is NOTHING I can do to get it out of bootloop or past HBoot
hmm new GB radio this has been happening with thunderbolt users to.....but in greater numbers.....I'd advise against using the GB leaked radio...
Your backup. Rec2.x. and now. 3.x?
Sent from my Optimized Inc using XDA App
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.
I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51
deathvalley1981 said:
I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51
Click to expand...
Click to collapse
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
How do I check the md5? I'm not sure what that is... Thank you for your help, I'm going through this process right now.
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again
deathvalley1981 said:
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again
Click to expand...
Click to collapse
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?
nschiwy said:
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?
Click to expand...
Click to collapse
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.
deathvalley1981 said:
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.
Click to expand...
Click to collapse
yeah, try one of those.
nschiwy said:
yeah, try one of those.
Click to expand...
Click to collapse
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!
deathvalley1981 said:
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!
Click to expand...
Click to collapse
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though
nschiwy said:
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though
Click to expand...
Click to collapse
I'm actually going to try yours, but can you re-educate me on flashing gapps?
deathvalley1981 said:
I'm actually going to try yours, but can you re-educate me on flashing gapps?
Click to expand...
Click to collapse
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.
nschiwy said:
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.
Click to expand...
Click to collapse
thank you so much for all your help and I like your rom already! It's super quick.
deathvalley1981 said:
thank you so much for all your help and I like your rom already! It's super quick.
Click to expand...
Click to collapse
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
deathvalley1981 said:
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.
Click to expand...
Click to collapse
Now see if you can access recovery. If you can wipe everything in the mounts and storage menu except emmc and sdcard, and then restore a known good backup or flash a rom fresh.
deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
No, I've not heard this before. Let me test on my phone and I will get back to you.
deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.
cmlusco said:
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.
Click to expand...
Click to collapse
do you think his file system got borked somehow?
nschiwy said:
do you think his file system got borked somehow?
Click to expand...
Click to collapse
Could be, have to see what he reports back.