Related
Hello,
I was trying to flash a new Rom onto my phone (Superfly) and installed the .zip file from clockwork, however, when I try to boot the phone, it sticks at the Mytouch slide screen.
I cant load into the card nor the phone.
Is there any way to reverse this?
Thanks in advance!
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
sandpaperback said:
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
Click to expand...
Click to collapse
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
dion20 said:
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
Click to expand...
Click to collapse
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
wipe everything on the phone, find the thread that walks you through that
cursexcore said:
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
Click to expand...
Click to collapse
As was noted previously, if you haven't flashed the ESPRIMG rom, you're basically looking at re-rooting your phone every time you want to install a different rom. This means going through the whole process again and again and again.
falken98 said:
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
Click to expand...
Click to collapse
thats weird, cause before I could get into clockwork after 2 tries max, not I tried repeatedly for 10 mins and it didnt work, so I should just keep tryin to get into clock work then?
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
sandpaperback said:
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
Click to expand...
Click to collapse
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Now I know theres something that makes it so I dont have to go thru the pain of rooting to get into clockwork I'm def gna use it..
what method should I use? Ive been doing the following and no luck so far
1 - cd to android sdk tools folder
2 - vol down + power for recovery
3 - highlight recovery
4 - run loop in cmd
5 - plug usb into phone
6 - plug usb into pc, and before it changes to HBOOT from USB i hit power to select recovery
7 - adb devices sees it as an offline device for a few cycles, then it disappears.
after step 7 I've tried running update.zip
unplugging and plugging back in
ctrl+c to stop the script when its offline
unplug when its noticed as an offline device
whats the best way to get into it now?
======
EDIT - finally got it into recovery, i loaded up htc's recover with it plugged it to the pc so it loaded up HBOOT from USB
normally your are not bricked if:
1. you can boot into recovery
2. you can not boot into recovery yet you can boot into bootloader [HOLD (power + volume down) to boot]
Don't worry I got a black/blank screen of death the other day for flashing the wrong boot.img fortunately I was able to boot into bootloader and start from scratch using the ESPRIMG.zip
dion20 said:
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Click to expand...
Click to collapse
I agree to an extent, but if you take the time to read through things thoroughly (as in every post in the How To Root or Engineering Build or even Rom Bible thread), you'll be okay. This is my first Android device as well. I put off rooting for a solid couple of weeks while I read through everything I could. I was completely paranoid about bricking my phone. Eventually, I went for it. Even then I had a couple hiccups along the way (including have to re-root two more times), but all the information is here.
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
cursexcore said:
[blah blah blah....] My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
My question: did u search here?
http://forum.xda-developers.com/forumdisplay.php?f=660
And found items about the champion build and this little file named ESPRIMG.zip?
U can also check out the ROM BIBLE stickie post.
u can try this:
http://forum.xda-developers.com/showthread.php?t=713507
or you can try this:
http://forum.xda-developers.com/showthread.php?t=713507
now if you really searched you would of found your own question:
http://forum.xda-developers.com/showthread.php?t=744709&highlight=unroot
cursexcore said:
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
I had the same problem you did, and fixed my phone, so its possible. refer to my post on the first page and then refer to this post and use the mirror that Wes himself posted.
http://forum.xda-developers.com/showpost.php?p=7001053&postcount=7
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....
Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.
If you can still access the bootloader, you should still be able to run an RUU through fastboot.
It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.
I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.
My Evo is hardware version 003 for what it's worth.
Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?
I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.
This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?
teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
My God, another one. It's weird these seem to be happening more and more...
Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
By some awkward chance, have you tried a full wipe, and then flash a sense rom?
teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.
So I just rooted using the latest unrevoked, but now my phone locks up after about 30 seconds or so, then vibrates 5 times. More troubling: It cannot see an SD card, will not mount or format.
Hoping someone can help me get back to stock.
I did not take the gingerbread OTA, FWIW.
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
HipKat said:
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
Click to expand...
Click to collapse
It says S-ON
dsf3g said:
It says S-ON
Click to expand...
Click to collapse
Boot into the bootloader, then select clear storage, then try to boot up normally.
OK, so I managed to flash PC36IMG.zip. So now I'm back to stock and the EVO runs fine without rebooting. Wheeew! I was already scanning eBay for a replacement, LOL! Only issue I have now is that my Evo does not recognize the SD Card (won't let me mount, format, nothing.) I'm seeing some threads on this sort of thing, but if anyone has a quick fix I'd love o hear it. I've got a 16 GB card full of music that's just sittin' there.
Oh, now this is bad: the battery does not seem to charge after restoring... at least the charging symbol is not coming on!
UPDATE: OK, the red light is coming on now when I plug in, but battery status shows "discharging." I don't know at this point whether it's charging or not.
OK, just verified. Phone isn't charging. Down to 50%. Shutting off so I'll have enough juice to fix ti when I figure our what needs to be done. I don't have a separate battery charger, so I'm SOL if I can't get this thing working again.
Any help would be much appreciated!
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
teh roxxorz said:
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
Click to expand...
Click to collapse
Thanks, I'll give it a try this weekend. Right now I've got a spare battery charger on order with Amazon. Should be in this Friday. Don't want to mess with anything until I can start with a fully charged battery.
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
HipKat said:
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
Click to expand...
Click to collapse
I don't have the new update on my phone. It's still showing Android 2.2 and I never approved the OTA.
One suggestion that seems to work for some people is to flash a new radio. I wonder if someone could help me with this:
1) What do I need to know choose the appropriate radio to flash?
2) Do I need to be rooted to do so, because it seems I'm not.
I'm browsing eBay for cheapie Oprimus S phones... please help me not have to buy a used $100 Optimus S because I murdered by Evo :-(
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
HipKat said:
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
Click to expand...
Click to collapse
I can't be sure I rooted. I'm just going by what Unrevoked reported. Superuser was installed, but the phone would die before I had much time to verify that I was actually rooted.
I've never installed HTC Sync, BTW. According to the unrevoked instructions you shouldn't have it installed on your PC because it causes problems.
OK, so I got home and the phone says battery is 100% charged. So that's good. It appears to charge when turned off, at least.
Sadly, it does not recognize USB at all. The computer beeps when I plug the phone in, but the phone shows no popups or anything.
I tried running "unrevoked" again, but unrevoked just kept waiting for me to plug in the phone. I did not install HTC Sync.
The phone does not recognize micro sd cards from within Android, but I can flash signed ROMs. I did that today, flashing what I think is a newer ROM than I had before, but alas it did me no good. The phone still does not see the micro SD card or realize that I'm plugged in and charging.
The ROM I sintalled this time was the third link on this page:
http://forum.xda-developers.com/showthread.php?t=884060
It corresponds to the software version I was running before running UNREVOKED the first time.
I'm getting pretty worried here. I don't see how I'm supposed to fix this phone if I cannot communicate via USB.
Installing HTC Sync will install the drivers on your computer, which you need for unrevoked to work, but then, you need to uninstall the program (not the drivers).
Ugh, now I've discovered another problem. With this latest stock ROM I've lost bluetooth!
I'm losing hope here. My last best hope seems to be to accept the Gingerbread OTA, and if that doesn't solve the problem throw myself on the mercy of our local Sprint repair store. Anyone know what their policy is on this?
Will they repair something like this for a fee if it's not under warranty? I imagine even completely brcked Evos can be repaired with a new motherboard, right?
Should I try telling them that the OTA screwed it up? Will they be able to tell what I've done to the phone?
At this point I just want to get back to stock. No longer interested in rooting. I need a cell phone just for daily living.
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
PhxkinMassacre said:
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
Click to expand...
Click to collapse
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
evo4gnoob said:
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
im downloading a 2.2 ruu. ill get back to you as to if it works or not
ok. i try to run the ruu and it gives me a main-version ERROR so i hit close and disconnect my phone. but then a window pops up saying update. so i plug in my phone again go to fastboot but then fastboot freezes and i cant navigate up and down with the volume keys. i then hit update but it just hangs at rebooting to bootloader and wont do anything...
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
HipKat said:
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
Click to expand...
Click to collapse
i tried the sdcard ruu for the latest gb update. it goes through. installs everything ok. but then when it reboots it goes back to the same 5 vibrates and black screen with flashing light.
after i did the sdcard ruu the windows ruu was able to go through unlike before. so i plugged in my phone it did its thing successfully. and again to no avail its still got the 5 vibrate etc.
and other options such as a block remap? i was running decks at the time which is based off cyanogen and i heard that cyanogen had been screwing blocks lately...
edit: i have no idea how a block remap would work... i just saw it in a thread that i believe you posted in like 3 days ago or so...
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
HipKat said:
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
Click to expand...
Click to collapse
He can't get sd to mount
Sent from my PC36100 using XDA App
ok. i went to a friends house and just let my evo chill out on my desk and when i got back it booted right up since i got 1 successful ruu in. now that being said it only stays up for about 3 minutes and then shuts off and goes into the vibrate and blink stage so im gonna try a logcat and see if i can get anything useful out of it. there is some hope here boys
ok. i have tried ruu 2 more times. i tried to root a few times. all to no avail. nothing works. i still turns on for only 3 minutes at a time and then goes blank and vibrates.
my device is less than year old but i didn't get a warranty so does anyone know what the deal is with getting a replacement? my bootloader says s-on and its on a stock rom due to the 934759345734 ruu's i did so they won't know i was rooted. so is there like a 1 year manufacturer warranty for this without having to break out $100?
Best bet is to just call Sprint and find out. They may just offer you a trade in.