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.
I am stock at tmobile screen, it doesnt go any further
i went in recovery it returns as
E:Can't Mount /cache/recovery
all the way down
the "fastboot erase recovery" returns with "FAILED (remote: not allowed)" and the "fastboot flash recovery recovery.img" returns the same thing. Any other suggestions???
I tried to restore pd15img and
it works little bit, and it asked me to upgrade, i pressed the volume up
1 BOOTLOADER - Fail-PU
partiton update fail!
update fail!
This has happened to quite a few people lately and I don't think they have been able to come back from it. Out of curiosity though, what caused this? Were you flashing something and this happened? Do you have the engineering bootloader? Attached is a thread of someone with the same problem, and like I said, there are a couple more out there.
http://forum.xda-developers.com/showthread.php?t=984790
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
I had the same fastboot errors when trying to flash from 3.0.0.5 to 2.5.1.2 after i mistakenly flashed 2.5.1.2 when i had cm7. You may need to update your sdk. I had to install my HTCdrivers on a new box and Download the tools folder from here http://forum.xda-developers.com/showthread.php?t=928370 to get it working.
theghazi said:
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
Click to expand...
Click to collapse
First, there is only RoyalGlacier v 1.2 as of the latest for now. Since you used that CWM 3.0.0.6 while battery charge off, there is a chance it might have reverted back to CWM 3.0.0.5 and RoyalGlacier requires 3.0.0.6 and stock restore requires 2.5.1.4 but your recovery may be 3.0.0.5. Try flashing a ROM that just requires 3.0.0.5. For future reference, use this version of CWM 3.0.0.6 from here (http://forum.xda-developers.com/showthread.php?t=944681). That sticks and never reverts back to .5.
Thanks for replies, n advices.
I have tried every which way possible to put the recoveries, and all failed.
I have had 3.0.0.6 modified for a while. was not going back and forth with 2.5.1.4
anyone else come out of this mess,
if not is there a way to get it to even at s - on and unroot?
I dont think so, but worth to ask
thanks
I'm having the same issue where it gets stuck at the Tmobile spash screen and when i boot into clockwork, it gives me the cache error. Formatting it through clockwork doesnt work, and when i try to restore it it also give me an error. I tried to format through adb but that hasn't worked either, unless I'm typing in the command wrong
I dnt believe there is a way to fix that issue,i had that issue awhile back on my 1st mytouch 4g,i had cm7 & made the mistake of tryin to nandroid restore a backup which I forgot was stocked froyo & everythin flashed ok but got stuck in bootloop,so battery pulled went to recovery & had all those errors u mentioned & never found a fix.....called tmobile,got a replacement no problems 2 mnth later & warranty still there..... Now I have clockwork 3.0.0.6 & havent ran into that issue yet,goodluck let us knw if u find a fix....
Permrooted s=off-MyTouch 4g-White
Eng-0.85.2007
Rom-RoyalGinger
I like balls
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
theghazi said:
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Im not really to sure,a friend of mine had the same issue & went thru HTC & got a replacement so want im guessin is they dnt care but dnt hold it against me,it could of been 1 of those lucky times. All he said was that the phone wnt boot & they just sd it was a known issue & sent him another one...
well I think I've successfully bricked my mt4g. It was working fine until I installed the latest clockwork version and RoyalGinger, tried to restore some applications + data with mybackup root but it froze. Then it was stuck on a bootloop, went back into clockwork and started getting the "can't mount cache" errors. Now it's stuck on the T-Mobile splash screen if I try to do a normal boot, bootloader works and it also goes into clockwork, but it's not able to do any factory resets/wipe. Tried the factory image file and it fails on the first 5 or 6 items, skips another item and hangs at flashing the radio. Now it needs to be replaced and T-Mo is out of stock of the red mt4g's, so I have to wait until they have stock of red ones, then it's going to suck if I get one with a bad screen. I got offered a black one, but I just like my red one too much.
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
darinmc said:
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
Click to expand...
Click to collapse
That part7-xxxxx.bin file is created when u root with the gfree method,it doesnt come stock on the sd card... what method did u use to root...dnt use unlockr.com methods,its old & doesnt give true oerm root...
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
darinmc said:
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
Click to expand...
Click to collapse
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
cmdmilitia13 said:
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
Click to expand...
Click to collapse
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
darinmc said:
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
Click to expand...
Click to collapse
My fault I should of double read,i have an issue with just skimmin thru things & look what happens lol...
Has anyone found a fix for this? Same issue.
Isubbie said:
Has anyone found a fix for this? Same issue.
Click to expand...
Click to collapse
nope nothing yet,not that I knw off...
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.
So i rooted my phone, had a custom rom on it, erased it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
tongtaihuo said:
So i rooted my phone, had a custom rom on it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
Click to expand...
Click to collapse
Go to the bootloader. Then go to system info. What does it say on the eMMC line? Does it say Samsung or Sandisk?
Sent from my HTC Glacier using xda premium
hboot-0.86.0000
microp-0429
Radio-26.11.04.03_M
Radio-26.11.04.03_m
emmc-boot
tongtaihuo said:
So i rooted my phone, had a custom rom on it, erased it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
Click to expand...
Click to collapse
You erased the rom? How in the world you that? There's no way to erase the rom.
Sent from my HTC Glacier using xda premium
i deleted it through CW and tried to install a new rom, but it aborted before it could finish
flash the PD151IMG.zip file through bootloader, THIS WILL ERASE ALL OF YOUR DATA, AND RETURN YOU TO STOCK MT4G 2.2.1. this is so you can root again.
download link here: http://www.megaupload.com/?d=V4NAODYZ
once you have it downloaded:
1) move to ROOT of sdcard (not in any folders)
2) make sure fastboot is OFF
3) reboot phone into bootloader by holding power and volume down buttons.
4) the phone should find the file, and ask if you want to "update"
5) select yes, and let it do it's thing. BE PATIENT
6) hit the thanks button (IMPORTANT )
7) after returning to stock, get the phone rooted again and flash a rom on there.
WARNING: IF IT SHOWS FAIL-PU, THE PHONE IS BRICKED.
Fail-PU means that the partition update has failed, due to the fact that the phone cannot write to the eMMC chip anymore, because the chip has died.
it shows fail on everything, but when it gets to TP it says bypass and its still updating radio_V2
tongtaihuo said:
it shows fail on everything, but when it gets to TP it says bypass and its still updating radio_V2
Click to expand...
Click to collapse
ok, tell me if radio fails or not...
it vibrated like 6-7 times and its still updating
tongtaihuo said:
it vibrated like 6-7 times and its still updating
Click to expand...
Click to collapse
ok, pull the battery, and try again. if it gives Fail-PU again, then the phone is bricked.
I have an EVO 4g that is stuck in an infinite boot loop. When it boots up it goes to the HTC EVO 4G white splash screen, goes black, and then goes back to the white splash screen over and over. I'm at my whit's end with this one. I have tried:
- RUUing it
-flashing different recoveries to it (Amonra and Smelkus)
If anyone has had a similar experience with theirs could they please point me in the right direction.
HBOOT 6.16.1002
Radio-2.15.00.07.28
S-OFF
It still loops if I go to recovery through the bootloader.
Thanks
mook_ said:
I have an EVO 4g that is stuck in an infinite boot loop. When it boots up it goes to the HTC EVO 4G white splash screen, goes black, and then goes back to the white splash screen over and over. I'm at my whit's end with this one. I have tried:
- RUUing it
-flashing different recoveries to it (Amonra and Smelkus)
If anyone has had a similar experience with theirs could they please point me in the right direction.
HBOOT 6.16.1002
Radio-2.15.00.07.28
S-OFF
It still loops if I go to recovery through the bootloader.
Thanks
Click to expand...
Click to collapse
Didn't mean to double post - I could not find my original post this morning for some reason.
You're S-OFF. You'll be fine.
Have you tried a different ROM other than a RUU? Like a recent stock or stock-ish ROM?
Also, now that you have a good recovery on there, use it to wipe data, cache, system, and boot. Don't erase all your pictures and music, but nuke everything else.
The symptoms you are describing happen to me all the time when I have not adequately wiped between flashing different ROMs . It could also be a bad download (always check md5's )
Sometimes flashing a ROM that is way too old for your radios or bootloader could cause this, but it sounds like you're pretty up to date.
Get a different ROM (such as Captain Throwback's 5.67 stock ROM) and try again.
After trying all the obvious stuff, then *maybe* we can talk about bad SD cards, corrupted partitions, whatever..
Sent from my PC36100 using xda app-developers
mook_ said:
I have an EVO 4g that is stuck in an infinite boot loop. When it boots up it goes to the HTC EVO 4G white splash screen, goes black, and then goes back to the white splash screen over and over. I'm at my whit's end with this one. I have tried:
- RUUing it
-flashing different recoveries to it (Amonra and Smelkus)
If anyone has had a similar experience with theirs could they please point me in the right direction.
HBOOT 6.16.1002
Radio-2.15.00.07.28
S-OFF
It still loops if I go to recovery through the bootloader.
Thanks
Click to expand...
Click to collapse
Go here and read everything,then format your sd card,make sure to back it up first,then install DT's a2sd and a stable rom,like Tommy's Classic or Miks 3.0.
Wait - you said it loops in recovery also?
That's not good.
Is this the same issue as the thread you started over in Q&A?
Now I'm not so sure there is an easy fix for this issue.
That radio is a little old and may be preventing your RUU from succeeding. Try updating?
After that, you might have to start looking at some kind of corrupt NV partition or something..
Sent from my PC36100 using xda app-developers app
Something that helped me-
Recently recovered from an infinite boot loop myself- my condolences. Have you tried booting while the phone is plugged into the PC or an outlet?
I have hope
Im hoping to see that you are able to resolve this problem. Recently did a RUU update myself.
Turns out that everything updated minus the boot.
Which recieved a partition update. This was coming back from a bad kernel.
The phone is S-On sits on the 4 corner escalmations of death..
.. no further than the bootloader. which displays specs and ruu where the options should be.
Be interested to see if you find something. In the mean time Ill be hunting form info as well and if I find a possible resolve Ill try and throw it your way. :/ miss my evo...
Best of luck.
You can try one of my guides, it can help you get a recovery back. Just use the command fastboot flash recovery recovery.img
http://forum.xda-developers.com/showthread.php?p=31515005
--------------------------------------------------------
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.