[NOTICE] Gingerbread Related Bricking - May 27th 2011 update - Thunderbolt Android Development

There is no way to rule out GB as the cause of this failure right now. All we have is theories and the best fitting one is an emmc chip failure. Until we can find a user with a brick, who is still s-off, we can not learn more.
DO NOT FLASH OVER BRICKS, We need you to have s-off for trouble shooting.
UPDATE
We need info from brickers and non brickers please see
Please see here http://forum.xda-developers.com/showthread.php?t=1098363
--old post--
It has came to our attention, over the last few days that the recently leaked Gingerbread radios maybe causing a oddly large number of bricked phones.
This can affect any Thunderbolts running Gingerbread (except CM7 users), even after running fine for several days.
The cause at this point is not completely understood, and AndIRC as a whole recommends you revert back to Froyo until we understand it, or have a new leak.
When bricked, the phone is sent into an endless bootloop, no matter if you are booting into Android itself, or into the recovery. Trying to revert after the bootloop does not fix this issue.
Theories:
GB Radio causing corruption on the emmc:
Undisclosed chipset issue (Sorry no details will be coming unless verified)
GB miss reporting battery stats, aka just dead battery (Debunked by ryan2600 and I)
"Not sure if its the radio, i got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later the phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Good thing i have a 2 extra battery and an external charger from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%" http://www.reddit.com/r/Android/comments/hk54l/if_youre_using_the_leaked_gingerbread_build_or/

Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App

I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!

Awww fiddlesticks! Well at least I get my baby back. Landscape Rosie is the girl for me.

swimminsurfer256 said:
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Click to expand...
Click to collapse
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.

Wow this sucks, I don't really wanna go back to froyo

Thanks jcase and Team AndIRC! I nearly flashed the latest BAMF GB update. I'm glad that I stuck with 1.6.3

Wow, mine just started 2 mins before this thread went up. I was sitting at my desk and saw it reboot and now it won't stop. It actually loads up Android entirely, gets to Lockscreen and then restarts.

zskate311 said:
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone using the GB Radios (ie everyone on GB but CM7 users)

jcase said:
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Click to expand...
Click to collapse
Ah didn't see that. Does bootloader not work?

Well crap, back to froyo I go then, just to be safe.

*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.

I actually think I read about this somewhere else in the forums. I don't know if he was running gb but I'm guessing so. Thanks for this, I'll be reverting back later.
Sent from my ADR6400L using XDA Premium App

adrynalyne said:
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
Click to expand...
Click to collapse
It's all your fault.
Sent from my ADR6400L using XDA Premium App

reverting now... can I just flash a froyo radio and rom or do I have do the whole process in OP?

Thanks for looking out for us
Sent from my ADR6400L using XDA App

Thanks for the heads-up!

Might as well Nandroid my Ginger builds so I have them for when we get a more stable radio release. Curses Verizon! I will miss my Sense 3 elements!

This sucks! Thanks for the heads up, though, Justin!

Bootloader works. I ran into this problem once. Have a backup of the ruu handy. It will get you back to a stock rooted froyo state
Btw...I'm staying on gb. Ill take a risk.

Related

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

[Q] MyTouch 4G Boot Loop

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.

Help please!!!

hey guys. im trying to be a good guy and help out a friend who is currently working on his phone. ok now lemme get in every detail as much as possible as you guys can fully understand what we're doing and what we've been done.
his phone is rooted. with s-off. now we tried flashing cm7 last night. did everything right. full wipe and all of that. so.. cm7 did finish the installation. it went thru the white mytouch4g screen, then onto the cm7 blue circle splash screen. after that it asked him all of his info to login to google. it was working for a good 2 hours. later that night, he told me he took out the battery to restart his phone. when he restarted.. white screen finished loading. but on the blue cm7 circle, it stayed there forever.
now im not sure what he did wrong since he told me he just wanted to restart his phone. we cant even go back since it gets stuck on the blue cm7 splash screen. i really really really need your help guys. maybe you guys can private message me or hit me up directly on my email. i would greatly appreciate all the help. i tried searching and searching and all i got was to go thru rom manager, but how are we gonna do that if we cant even get the phone to boot up correctly. thanks in advanced guys.
Sent you a pm
Sent from my HTC Glacier using XDA App
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
What's the point in searching for it it means you bricked
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
tvotony said:
Sent you a pm
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ok i will try and see what he says. ill pm you back tony. thanks a lot.
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
my bad i forgot to answer your question. ok we tried reflashing everything. nothing of that kind of error showed up. it just said complete. then when we tried booting up the phone.. it just got stuck on the blue circle thing.
tony, i sent you an email. anyone else willing to help?
i was thinking.. maybe the cm7 that we downloaded was corrupt? he said he has clockwork version 5.X.X.X
not sure if thats gonna make a difference but yeah. also since we cant go to the phone since it gets stuck on the blue circle, we tried flashing cm7. in the end, the last line says "installation aborted"
so right now, im completely clueless. i have searched everywhere and tried other methods to see what will work. my phone is rooted with royal ginger and everything is fine with it. i have already restarted maybe 10x the last couple of hours trying to help my friend.
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
zelendel said:
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
Click to expand...
Click to collapse
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
beryenbeh said:
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
Click to expand...
Click to collapse
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
zelendel said:
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
Click to expand...
Click to collapse
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
Best bet would be to redownload the rom, boot into recovery and mount it so you can copy the new rom zip to the sd card. Do a full wipe and then reflash the rom. Other then that his only chance maybe going back to a stock rom and doing a clean rom flash just in case
help
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
underyourskyn said:
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
Click to expand...
Click to collapse
i followed everything correctly and accurately. i even had him double check what i was doing to make sure. we rooted perfectly and flashed cm7 without a problem. i am not sure what happened when he restarted his phone.
can any of you guys speak to me directly? maybe via aim or any kind of instant messenger? i really wanna help him fix this problem but im not sure what else to do.
how did you root the phone to begin with?
neidlinger said:
how did you root the phone to begin with?
Click to expand...
Click to collapse
this way..
http://forum.xda-developers.com/showthread.php?t=858996
tvotony said:
What's the point in searching for it it means you bricked
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Cause me & a couple other people were able to recover frm those errors with the pd15 zip file... Some people were lucky..
Sent from my HTC Glacier using xda premium
beryenbeh said:
this way..
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Please look at the Glacier Wiki, Troubleshooting section. Link in my signature.
thanks a lot. hopefully his emmc isnt the problem. i checked his hboot and it says 0.86.0000 not sure if that rings a bell to any of you guys. ill keep reading more information and a possible solution. i read one that says to update the PDIMG file or whatever.. and then re-flash RG3.0. will try this one, hope itll work. once again, thanks for all the help guys. really appreciate it.
Rillusion08 said:
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Click to expand...
Click to collapse

It finally happened...dead eMMC

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.

Help PLEASE random disaster

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.

Categories

Resources