Related
Ok, I know I am a noob to android phones and to this forum, but I already spent many hours online researching the problem and didn't find anything that helped.
So, here's what happened:
I got my MyTouch 4G about 2 weeks ago unlocked. I wanted to get rid of a lot of the garbage that came with it, so I followed the steps and successfully rooted it and then removed several of the preinstalled apps with Titanium backup. So far, no noticeable problems.
Then I wasn't happy with how quickly my battery was draining, so I installed Advanced Task Killer, and set it to automatically kill certain apps periodically.
A few days later when I was trying to add a widget to the desktop, I got the familiar to some message "Sorry, com.htc.launcher has stopped working". Everything else was still working fine on the phone. I researched the problem and the first proposed solution to clear the data for the process from Settings/Applications, did not help. The second proposed solution was to do a factory reset. So, I rebooted with volume down + power pressed together and chose factory reset.
After 4-5 min, I got into the welcome screen where I did the initial setup. After this was complete, the phone checked off that everything was setup correctly (apps, widgets, etc). Then it started loading the desktop and the message "loading..." appeared. This is where it froze.
Basically, I can't get past the "loading..." message on the home screen, no desktop ever loads, and I have access to nothing other than the camera key.
I let it stay for hours to see if it will eventuall load, but nothing happened. I also rebooted and tried factory reset many times and it always get stuck at the same point. I tried all of the above with and without a SIM card, with and without a memory card - basically I exhausted all possible combinations but I always get the same frozen "loading..." screen.
Has anyone experienced this problem? I feel helpless rebooting or reseting the phone from the phone itself because it always get stuck. Is there a way to factory reset from a computer?
Thank you so much if you can help me with any advice and Happy New Year!
Vess
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
esincho said:
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
Click to expand...
Click to collapse
Hi, thank you for your message. I think you are correct about deleting the launcher and factory reset not fixing it.
But I don't know how to do "nandroid backup, flash iced glacier rom". Could you point me to instructions on that? Sorry, I'm really new to android phones.
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
esincho said:
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
Click to expand...
Click to collapse
I did what you suggested but from what I understand to flash a rom I need to be able to boot into Recovery mode, which I can't do either. Every time I choose Recovery I get the "!" screen and I'm stuck. Am I doing something wrong?
Thank you.
vess22 said:
so I followed the steps and successfully rooted it
Click to expand...
Click to collapse
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
shlongwoodian said:
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
Click to expand...
Click to collapse
No sir, I didn't do any of the above unfortunately. From what I understand had I done that, I wouldn't have a problem booting into Recovery mode, correct?
I believe you might still be able to get to what you need via adb. That's not my specialty though, even though I can mash out a few commands and comprehend what I'm doing. It would be remiss of me to guide you any further, but I don't think all hope is lost for you. Search the forums for 'adb' and 'recovery' and let's also see who replies back with some better advice.
Find the raw .img of cw recovery then adb flash_recovery /location/of/recovery.img
If that doesn't work you'll need to use fastboot assuming you updated to eng spl.
Sent from my HTC Glacier using XDA App
sounds like your boot.img is borked.... try flashing one of the many available kernels (make sure it will work with your rom first... if you haven't flashed a rom or flashed a sense based rom then use an HTC kernel if you're running CM or MIUI use a CM based kernel) and then when you get it running read this and understand why task killers are bad FAQ: You shouldn't be using a task killer with Android
Yes, I'm starting to realize that now my only option is to do flash recovery through adb. So, I've spent all night last night trying to understand what adb is. I installed and updated the sdk, but my adb shell doesn't see my phone as a listed device, so I'm stuck at this point. And yes, I read probably 5 tutorials on installing various usb drivers/ modifying sdk ini files/etc to make your computer recognize the phone as an adb device. I tried everything that was suggested but no luck so far.
I've spent nearly 30 hours so far since this whole disaster started and although I haven't made much progress, I've learned quite a few things.
And, no, I won't mess with Advanced Task Killer or Titanium Backup any more, just give me my phone back and working
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
ESKIMOn00b said:
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
vess22 said:
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
Click to expand...
Click to collapse
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Phateless said:
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Click to expand...
Click to collapse
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
vess22 said:
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
Click to expand...
Click to collapse
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Phateless said:
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Click to expand...
Click to collapse
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
vess22 said:
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
Click to expand...
Click to collapse
You make an appealing case for Iced Glacier.
Stock tends to be the most stable and reliable, plus you get OTA updates. Other than that, not much reason. I can tell you from recent experience that my phone gets a gps lock much quicker with stock than with cm6, but I'll do further testing to see if that's really the case.
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
GLACIER PVT SHIP S-ON
HBOOT 0.86.0000
MICROP-0429
RADIO 26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
sending 'recovery' (8701 KB)... OKAY [471.891s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 473.125s
Click to expand...
Click to collapse
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
RedDonkey said:
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
Click to expand...
Click to collapse
The instructions above only pertain to a rooted phone. Your phone is not rooted and you dont have eng bootloader. Without superuser access you cant even flash recovery like you were trying. A factory reset didnt fix your problem?
Side note, im an opponent of doing the whole temp rooting only thing cause if you screw something up you dont have access to tools to fix anything, your just screwed if something happens like this.
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.
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
EVO 4G rooted with Unrevoked. Right now I can only boot into bootloader and fastboot. There is no ROM and It will not let me load ROM or recovery from fastboot or sdcard. I can fumble around fastboot and adb but most of the time I get an error.
sending 'recovery' (209 KB)...
OKAY [ 0.273s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.274s
Here is the bootloader info:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041F
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Any help greatly appreciated! If I am in the wrong place, very sorry
Which recovery are you trying to flash and how?? via PC36IMG?
Thanks for the reply!!! recovery-RA-supersonic-v2.3.img. and update-cm-7.1.0-Supersonic-signed.zip I tried both as pc36img from HBoot and via fast boot. neither worked. I also tried to install to change boot.img via fastboot. same message.
Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.
i wish there was odin for htc devices
Will try that again first thing in the a.m. Been working on it all day and the brain is mush! I'll post the result as soon as I'm done. Thanks!
Sent from my PG86100 using XDA App
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Well this happened to me once, what i did was i put on my sd card any other rom (i was using cm7 nightlies so i put another nightly in) and then i wiped cache and flashed it, however it might also help if from this link http://forum.xda-developers.com/showthread.php?t=1295702 you get the format all zip and use that to wipe everything. once you have flashed another rom and your phone turns on wait a little bit and then try once again to flash the first rom you were trying to flash.
[email protected] said:
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!
Click to expand...
Click to collapse
can you go to the recovery? if you can try to do what i told johnnyboy1409
HipKat said:
Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.
Click to expand...
Click to collapse
Holy Cannoli!! Ok that .zip worked for the recovery (I tried several different downloads!) Now I have to see if I can copy an image. Wish me luck!
Thanks for the info. I totally though the phone was bricked. Actually the phone would load in HBoot and Fastboot but I couldn't get a recovery on or a ROM. In other words there was no ROM to boot to. In addition to that, wether I tried from SD card or fastboot, I couldn't get any .img, .zip etc to install. So here I was with an HBoot - S-off and no way to get a recovery or ROM on the puppy. I am still working on this and still jammed up but the recovery gives me hope. Please stick around in case I have a meltdown. (hasn't happened yet but I can feel it getting closer!) LOL
Stick around for the detail of what I did If I can get this ROM onboard! Maybe this will help someone else.
Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.
You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens
HipKat said:
You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens
Click to expand...
Click to collapse
That's Funny, I just did that and everything is fine. I just reloaded the ROM and looks like something just got corrupted and all I needed was a little help from my friends to figure things out
[email protected] said:
Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.
Click to expand...
Click to collapse
np ^_^ hope i helped, whenever i think my phone has an issue booting or something i just automatically assume that it's fixable, i haven't had my phone die on me yet and i'm not planning on it... *cough cough* Screw Apple *cough cough*
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Johnnyboy1409 Did you ever get this fixed?
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
when you go to boot loader and it loads, it then should ask if you want to update splash - hit no, then to reboot - hit no, then you should be able to go one down and hit recovery. do you get those options?
I get those options but when I click recovery it goes to the white htc Evo 4g screen and stays there no matter how long I wait.
johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
I know I sound like a broken record but try formatting your SD card or using a different known good card and also use the link in my post above to re-download the pc36img.zip Amon RA Recovery. Then you know all the components are "clean and without erro". Then you can start to figure out the problem.
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium
This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.
Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...
Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.
TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.