I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....
if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.
josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App
shameless bump - completely changed opening post
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.
Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.
Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....
Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!
Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.
Cleared all the caches?
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell
Related
I've got cyanogen's optimized 1.5r2v3.4, and Recovery Image v1.2. I have read half a dozen threads on how to get your phone back to stock, including this one http://forum.xda-developers.com/showthread.php?t=491350, but I have a unique impediment.
The screen on my fiance's brand new phone completely stopped working after less than a week. I can only interact with the phone via adb connected to the recovery shell, so I have to be absolutely sure it goes perfectly the first time (since the odds of having a working recovery shell after a bad flash are slim). I have not changed the second splash screen, so by what I read, all I need to flash back are the SPL, then the DREAIMG.nbh, correct?
How do I do update.zip for flashing the SPL via the recovery console? I had no problems getting the phone from stock to rooted, followed the instructions step by step. But now that I have to try and figure out how to do EVERYTHING via adb ONLY, I read the most simple instructions and find myself going 'wait, what?', trying to figure out how that would work done entirely without being able to see feedback on the phone screen.
Use the DREAIMG.nbh and recovery.img for rc29 stock its in the rooting thread.......load up the phone in fastboot (camera and power button) the phone will recognize the files and tell u to hit a button....you hit that whopping one button and wait 2 minutes and you'll be back to stock rc29 where then you can reroot or just sit around waiting for Over the air updates from t-mobile to catch u up to cupcake.....honestly i don't use fastboot EVER but i always keep those two files on my sdcard so if i have a problem i just run it and blast back to rc29 and start over......hope u see this before its closed in 5 seconds for not using the SEARCH BUTTON
sorry just use just reread ur post...use the DREAIMG.nbh it has the old SPL built into it
i'm not sure how this would be done, but what iwould suggest is put the original SPL on the SD card as update.zip and the DREAIMG.nbh on the sd in the root of the sdcard, then reboot holding home, give teh phone 5 minutes to boot into recovery then press alt+S wait 10 or more minutes to let it flash and then press home and back to reboot, or in adb shell type reboot bootloader, give it a minute or so and then press power, wait 30 minutes and hit the trackball, if after hitting the trackball the phone vibrates then it went fine, if not then the .nbh didn't flash
tubaking182 said:
i'm not sure how this would be done, but what i would suggest is...
Click to expand...
Click to collapse
Yeah, that sounds like a plan. Thanks, I just really couldn't get my head around how I could possibly do this!
Can I ask why you are bothering? Are you afraid they will hit you with an out-of-warranty fee because it's rooted? They won't, I've returned a first gen G1 that had the issue of the screens ribbon cable coming unplugged (sounds like your problem) and T-Mobile sent us a new one no problem.
GenericNode said:
Are you afraid they will hit you with an out-of-warranty fee because it's rooted?
Click to expand...
Click to collapse
Yeah, actually. *shrug* it doesn't seem to have flashed back to the stock image anyway, so I guess it'll have to go back in whatever form it's in. Hopefully you're right and they don't care about custom images.
heldc said:
Hopefully you're right and they don't care about custom images.
Click to expand...
Click to collapse
They sure didn't care about mine.
And besides, whether or not your phone is rooted isn't in the check-list of questions a CSR is supposed to ask before accepting a return, so how could it be your fault?
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked(which i found odd since the demo phone in my t-mo store is rooted and running dude 1.2). as long as it doesn't have a custom splash screen it should be ok.
also you could always grap the OTA update and edit it in some way(resize a pic and put it back) and then resign with testkeys and rename update.zip then the only thing they'll see if they really look at the phone is a bootloader that's been changed and recovery, but the rest will look like their stuff.
tethering caused double post sorry
tubaking182 said:
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked
Click to expand...
Click to collapse
No way. Sweet. I haven't seen this policy yet, but I never pay attention
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
tubaking182 said:
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
Click to expand...
Click to collapse
When you talk to those people you have to sound as newbish as possible, that's probably why they kept asking if you rooted it.
trust me i sound like a freaking idiot. "they told me on the t-mobile forums to press the homekey and turn the phone on and i got a triangle with an exclamatioin point, and then i pressed alt+w and after a few seconds my phone rebooted but the screen is always sideways when i open apps." i act like an idiot and they replace it. the only problem i had was when the guy asked what my favorite thing about the phone is, right after i told him i didn't know what root was. i just said games cause that's all i could come up with
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
I have to have screwed the pooch pretty bad, I'm caught in a loop at the HTC splash screen and then it reboots. Any helps would be very much appreciated. I know I did something, I just don't know what.
you dont give enough info..i mean what steps did you follow? when did things go wrong? what step was it? what was the last thing you did?
pull the battery and then boot into recovery (hold volume down+hold power)
EVOKeith said:
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
Click to expand...
Click to collapse
Flash the RUU from the "All roms" thread
Everything was fine after the root guide I followed (the idiot-proof one). When I attempted to do the Nand access portion something went wrong because I got an error that the SD card was blank or had an unsupported file system. The only choice I had was to format the SD card.
Now, when I attempt to install a downloaded .zip from recovery it acts like it is going to install but goes right back to the menu after a few seconds. IF I tell it to reboot then I get caught back in the splash screen rebooting over and over again.
do a full wipe and cache wipe, reboot and see if that helps before you go any further. you do that when you boot into recovery. that will likely fix it. If not post what it does then.
What happens:
When I boot into recovery the first bit is that it tried to load PC36IMG.zip, I get the following:
Main version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I selected No and went into Recovery. I wiped all data and cache and rebooted. Once again the white HTC EVO 4G screen comes up for a few moments and then the phone powers off and restarts with the same screen over and over. I'm at a complete loss.
bumping for help
is that pc36img.zip the rom that you initially flashed that worked or is it a different one that was part of the 'nand access portion'? I figured that would be from an 'update.zip', but I barely know what I'm doing outside of the well detailed guides.
If it isn't the rom you flashed, try loading that rom back on there. I hope you have another device you can read/write micro-sd's from.
If it is the rom you flashed try flashing another rom.
...I'm a noob here too, but I'm on my second rooted/custom recovered phone so I'll help as I can.
Did you make a nandroid backup?
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
EVOKeith said:
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
Click to expand...
Click to collapse
Lucky for you that none a single rep I've ever spoken to in any Sprint store has any idea about anything whatsoever. I returned a Samsung Moment that I never bothered to restore to stock...hey turned it on, it booted up with a "Hacksung, XDA developers" screen, proceeded to load up a (then hours old) 2.1 lock screen and said "Okay, it still works", didn't check to see if I had kept the memory card in or even re-packed the charger and gave me a refund for everything on the receipt, even things I didn't have in the bag.
...another time before that I was asking about the Android 2.1 update and when it was being rolled out to which the sales rep stood up, turned around and yelled "Bobbyyy....what's an android and when do we get one in?"
Though I'm sure there is a way to bring your phone back...perhaps check in on the thread where you got your rom and see if anyone else has had such issues, give all the details you can in the order in which they happened.
If you can still get to the hboot screen try the zip posted here using the instructions here
My EVO doesn't charge anymore. Guess my port got broken. My phone is rooted, and I dont have PC syncing capabilities. Is there a way to restore my phone back to the stock sprint rom so i can take it in for service or get a new phone? Does a hard reset restore the stock sprint rom? Im running the MIUI rom As u can tell im sort of a newb
Find a PC36IMG file of a stock, unrooted ROM and flash it through the bootloader.
Get a cheap standalone battery charger on ebay. While you're at it, get a microSD card adapter that you can load into a SD card reader. Charge your battery that way since the micro-usb doesn't work. Pull out your microSD card from the phone and load into adapter. Put an RUU file onto the microsd through your comp then put the microsd back into phone with the charged battery and you should be back to stock.
Another option, just bring to Sprint store and have them fix the micro-usb port. Their policy has changed and they should repair your phone even if it's rooted.
Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!
plainjane said:
Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!
Click to expand...
Click to collapse
I had the same problem you had. This method worked best for me.
where do i get the most recent RUU in PC36IMG.zip form? I have the stock sprint radio file but its exe.
"RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
Do i rename this to PC36IMG.zip or do i need to download something else.
edit:
Or i download this file and rename to PC36IMG.zip?
PC36IMG_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444-signed.zip
Use the one I'm going to link you to. Rename it to PC36IMG.zip, leave the .zip intact - don't add it again. Then follow the directions I posted earlier.
http://goo-inside.me/evo/stock/ruu/...0.09.01_NV_1.77_003_release_154209-signed.zip
Sent from my PC36100 using Tapatalk
ok thanks!
Another thing for future refrence . I personally keep a folder on my SD card named "Emergency restore" Just in case . It contains the PC36IMG.zip and the Unrevoked S-on tool . Granted in the event the screen was broken or something to that extent and I still had some control over the phone I can still restore back to stock if I am away from my computer at home . Just an idea
ok i turned on the s-on via the "unrevoked-forever-son" tool. I put the image into the sdcard root and it checked the zip file but it didnt ask me to update
loading...PC36D1AG.zip.....no image
loading...PC36D1AG.nbh .....no image or wrong image
then it loads the PC36IMG.zip and checks it, but no update.
Whats wrong?
@SouthernEvo, thats a good idea, thanks
Try downloading again, then booting into the bootloader and letting it scan. You can always try letting the bootloader scan your current one again as well. It doesn't say "no image or wrong image", correct?
I almost recommended running an RUU from your computer, but you can't connect... duh. If it still won't work after redownloading, try a different one.
Sent from my Evo using Tapatalk
im thinking its not updating because im not flashing the latest radio maybe? my version says:
Radio-2.15.00.11.19 do i need to get one after this version in order for it to update?
im downloading another RUU file. Hopefully it may work. As it looks, my phone is already running the latest. Idk...i actually dont know wth im talking about anymore lol
EDIT: Figured out it was my SD card causing the problems. Switched to the stock 8gb card and now it works. Flashed back to Stock. New phone comes Friday
I've been ROM-hopping, trying Synergy, Alliance, Myn, and several others. On the last one, MikG 2.3, I had it loaded up and working fine. I started installing apps from the Android Market. That, too, was going fine, until it suddenly rebooted in the middle of an app download/install.
It went to the white screen with HTC EVO 4G on it, and then went black, then back to the white screen, over and over.
Six hours later, I'm still stuck in the loop. To make matters worse, I accidentally lost root (I see "S-ON" at the top). So now I'm stuck without root until GB is rooted successfully, which hopefully isn't tooooo far off in the future.
But that's the least of my concerns. I would be extremely happy with a stock install of any sort at this point, but I can't get anything to load. No recovery, no ROMs, but I can get into HBOOT so I'm able to try to load any PC36IMG.zip files. The last one I tried was the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed.zip" (renamed to just PC36IMG.zip, of course). It appears to load just fine and in the end says "Update Complete... Do you want to reboot device?"
I choose yes, it reboots... and we're back in the loop. I have no idea what to do or try at this point. Any help anyone can provide would be greatly appreciated! My next step is to take it to the Sprint store, but that's over an hour away and will have to wait till the weekend.
Thanks everyone!! If you need any more information, let me know. Believe me, I'll be monitoring this thread closely!
/Kevin
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Papa Smurf151 said:
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Click to expand...
Click to collapse
Yeah, I tried. I have several SD cards of varying sizes (4GB, 8GB, and my primary 16GB). Formatted the 4- and 8GB ones and tried from each, but no go. Thanks for the try though!
/Kevin
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
trim81 said:
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
Click to expand...
Click to collapse
Just did it and the process went well, said it was successful... but it's still stuck in the same loop. I'm thinking the phone is beyond repair. Thanks for trying, though. It really looked like it might work for a second.
/Kevin
what was the app?
That's what I want to know and how do you get accidentally to S-On?
Put the phone in a refrigerator ... as crazy as it sounds, it might be the infamous overheating issue.
Put in refrigerator, for about 5min
The app was "Kid Zone" (Zoodles), but I'm not blaming the app by any means. I've used it for a long time, it's highly-rated in the market, etc. I'm sure it's just a coincidence.
As far as getting back to S-ON, I think it must have been when I flashed the stock recovery. I was flashing so many things out of desperation that I can't swear to that, but I'm pretty sure that's what did it. Now that it looks like I'm heading to the Sprint store tomorrow, I guess it's a GOOD thing it's back to S-ON. Heh.
Pretty sure it's not heat-related. My phone was off all night (since it's not usable) in an air conditioned room, so it's cool to the touch. I tried the RUU process again with the same results. (I'm not sticking it in the refrigerator, because I'm afraid of activating the water-damage sensor -- I don't want any excuses from Sprint when I bring it in tomorrow!)
Appreciate the help!!
/Kevin
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
HipKat said:
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
Click to expand...
Click to collapse
I hear ya. I haven't run into any techs at my local stores that are knowledgeable about this kind of stuff. (I know others have, so you never know, but I have yet to see one.)
/Kevin
To conclude this: I went to the Sprint store today where they assured me they would reload the software but it would take 1.5 hours. I came back 1.5 hours later... and they handed me a new (refurb) EVO. They said they weren't able to load anything on the phone.
So, no surprise with the outcome there. I was fairly certain they were going to have to replace the EVO, and they did.
Thanks to everyone who tried to help, but it was just beyond help!
/Kevin
I had that same problem with my phone back in November. Continues boot loop. Finally, having boot loop for 8hrs, I took it to Sprint and they replaced my phone. They called it a power cycle issue. $35 new refurbished phone works well. Never had a problem since.
search has not been my friend these days - Long story short, I eneded up with a new to me evo 4g. I replaced the screen and started her up. A few freezes and I did a factory data reset from the settings menu. Decided to root.
used the supertool method here :http://www.goodandevo.net/2011/12/new-htc-evo-rooting-method-now-available-htc-supertool.html
ran step 1(prep) and had success.
ran step 2 (attempt root) and it was unsucessful - I figured it was because I didn't have an sd card in, so powered down
re-ran step one and phone froze.
Half the time I could get to the bootloader, so I tried an RUU. Went to fastboot usb, had it registered with the computer as and HTC... and ran the ruu. Either my windoze machine froze or the phone did. It failed.
Now I can get to the bootloader 1 out of 25 tries. Otherwise the screen stays blank. Then the buttons don't work every other time I do get in. I have to leave the battery out about an hour(?) or more for a chance at success. IF the buttons work, it stays active for about 3 minutes. Then the phone freezes.
The phone does have charging lights on it, but that's about it.
What can I do here?
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
wasilvers said:
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
Click to expand...
Click to collapse
If your phone comes on and you see lights its not bricked. Once you cant get it to do anything then thats when you worry. I would find one of the the PC36IMG.zip files and when you get it to go into bootloader you can install the zip.
Does your bootloader say unlocked? Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Dowload the PC36img file from this thread and go from there..
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
playya said:
Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Click to expand...
Click to collapse
If I recall, I was forwarded there by an xda thread. It's my fault for not checking my build first and making sure it was an acceptible root method for it. This phone is a year old, I assumed the method would work - I was wrong - and am now paying the price for the assumption.
wasilvers said:
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
Click to expand...
Click to collapse
Yes. I believe you can install a signed stock ruu directly from HBOOT even with s-on. install the sd card with the ruu.zip directly on the root of the sd card (name must be pc36img.zip). When HBoot loads, it will scan the sdcard and find the zip and automatically run it. format the micro sd card first... maybe its corrupted or something.
Update
Update:
All options were a nogo- I got a pc36(whatever) file to read and a progress bar that paused (paused till the battery went dead). No RUU file would work. I read that some of the memory modules must have been written bad in the root and it would need jtag service. So I'm putting the screen on ebay and cutting my losses.
Moral of the story: Stick with XDA - search under your operating system, don't be lazy like me.
Now I am root shy, only rooted one phone in the last 2 weeks, and none for my friends. Glad this was mine and not a friends - that's probably why I got lazy.