Related
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Shaihalud9 said:
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Click to expand...
Click to collapse
Should have posted this in the q&a but try THIS post and we'll go from there.
I should have, but thanks, I will try that.
Shaihalud9 said:
I should have, but thanks, I will try that.
Click to expand...
Click to collapse
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Yellowcard8992 said:
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Rebooting the bootloader doesnt help, still getting Error 170, so hopefully flashing a new recovery from HBoot will.
Okay so copying the PC36IMG to my SDcard, the bootloader recognizes it, and reads it, and I get a progress bar on the right.... but no option to flash the image, and booting into recovery does nothing.
Im going to try an HBoot run of the PCIMG36 RUUs I found on another page... I dont mind going back to stock, I just want the damn phone to work.
Double post.
So I used the latest PC36IMG Signed zip from here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu&page=7, and it went through, did all the updates, but when asked to reboot, which I did, I get a blinking yellow LED that goes solid, boots up, get the EVO 4G white splah for a few moments... then nothing.
Im hoping its just a dead battery. =\ Gonna try it again in a bit.
Nope. Still getting bootloops, even with the new PCIMG flashed. What the f*cking hell.
Now, This may have been answered or tied into the post by neidlinger, however I've found my problem to have some strange symptoms and was wondering if anyone could help me out.
I had my Glacier working just fine using the ice Glacier ROM, decided to try out some new ROMS including a couple Gingerbread roms. I updated Clockwork Recovery to 3.0.2.4 and flashed the roms, they seemed fine, but they weren't my cup-o'-tea. So I flashed back to IceGlacier 1.1.6. Ever since then My phone has had a boot loop issue that seems to be effected or triggered by power management. Not always, but sometimes If I plug my phone into the stock charger or otherwise, it'll reboot and sit there looping at the MyTouch splash screen until I pull the battery. Same happens on occasion when unplugging the phone. I can get it to boot into Android by letting it sit off for a while then come back to it a couple minutes later and power it on. Is there anything totally wrong with my device outside of what neidlinger posted?
Any help or advice will be greatly appreciated, Thanks!
Update!
Update: I found some time finally to look through some roms and flashed "Royal Panache" using CWM recovery 3.0.2.4. I still get the boot loops described above, still related to power, seemingly. If I plug the phone in while it's off, often it will start up on its own. Any help is still greatly appreciated . Please tell me if I'm just being stupid and/or blind.
try changing charger, or use pc charge and see if that happens
Thanks! I'll give it a whirl. Though I will say, it happens when using my car charger which is just a usb port.
Sent from my HTC Glacier using XDA App
You keep mentioning the cwr version as part of the flash process. Have you been reflashing recoveries each time you flash a new rom or something?
eqjunkie829 said:
You keep mentioning the cwr version as part of the flash process. Have you been reflashing recoveries each time you flash a new rom or something?
Click to expand...
Click to collapse
I have not, it's just added information. From what I've heard some recoveries only support froyo or only gingerbread.
atifsh said:
try changing charger, or use pc charge and see if that happens
Click to expand...
Click to collapse
It still happens when plugging into my pc.
Try restoring your phone to stock using PD15IMG, and see if it takes care of the problem.
If you have engineering bootloader - remember to reflash it after PD15IMG (it'll restore 0.86 stock bootloader when flashed).
If the problem won't be cured - it means that somewhere in your flashes you've probably damaged/overheated something in the phone, and now it needs replacement.
Jack_R1 said:
Try restoring your phone to stock using PD15IMG, and see if it takes care of the problem.
If you have engineering bootloader - remember to reflash it after PD15IMG (it'll restore 0.86 stock bootloader when flashed).
If the problem won't be cured - it means that somewhere in your flashes you've probably damaged/overheated something in the phone, and now it needs replacement.
Click to expand...
Click to collapse
Thank you very much for that bit of info. As soon as I get some time, I'll try that out.
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App
Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.
You're bricked
Sent from my Desire HD using telepathy...
I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?
I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER
If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Lol least its on
Sent from my Desire HD using XDA Premium App
HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it
marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.
Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App
So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
invasion2 said:
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
Click to expand...
Click to collapse
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
tradejak66 said:
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
Click to expand...
Click to collapse
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
k hold up let me try
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
do this: wipe data/factory reset
wipe cache
wipe dalvik
flash the original ROM (the one you have a backup of, but not the actual back up)
THEN restore the backup, it shouldnt get stuck at system anymore
i had a similar problem and this helped. hopefully it works for you
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
I've tried twice and it still boots :0
tradejak66 said:
I've tried twice and it still boots :0
Click to expand...
Click to collapse
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
lol. start looking now just in case.
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
tradejak66 said:
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
Click to expand...
Click to collapse
I think you're fine honestly. Good luck matey!
Get a 12v power supply, cut the end off and strip the wires. Take the battery out and touch the wires to the phones battery contacts a couple times. Replace battery try to power on. If it doesn't turn on your done, if it does try again. Tell them it was on the charger and shut off when you unplugged it and wouldn't turn on.
Sent from my HTC Glacier using Tapatalk
tradejak66 said:
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Click to expand...
Click to collapse
I had a similar problem when the splash screen got stuck last night flashing a new radio. I took the sdcard and plugged it in the netbook, accessed the root rolder and renamed the PD15IMG.zip so the HBOOT wouldn't read the file. It stopped the HBOOT from reading the file so I could access Recovery then reflashed my recovery file. I forgot to do the data wipe/dalvik before I flashed the radio lol.
This is an AWESOME how to brick your phone on purpose guide good job guys
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
tradejak66 said:
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
Click to expand...
Click to collapse
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Where there's a will (and a hammer) there's a way.
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Yea its hard to permabrick unless you don't want to brick it from what I hear...
Sent from my HTC Glacier
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
your assuming that it was software that broke >.> it was most likely hardware since it broke in this manner and no flashing, resets, anything helped. and its 2 weeks btw lol.