Database Users

HTC incredible endless boot loop

i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?

hard reset may work
Sent from my Incredible using XDA App

i tried hard resetting it. this did not solve the problem.

ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.

Are you root?
When and how did this start happening?

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.

JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App

JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?

RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.

theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App

Try the RUU that was posted.

jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen

theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App

jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html

theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App

jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.

theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App

Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.

I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure

[Q] Does your MT4G reboot by itself?

Hi all MT4G users. I'm going to join y'all real soon. Anyway, I've read several topics about HTC phones (Desire, Desire HD, EVO 4G, even in the difference platform HD7) reboot by themselves. Some say it's because the heat of the motherboard. So, does anybody here get the same result?

I have had my mytouch 4g for 3 weeks and it has rebooted about 3 times total. Nothing major. I would rather it reboot then to fry something internally.
Sent from my HTC Glacier using XDA App

I actually haven't had this phone reboot on me yet... its been just about 3 weeks now and I hardly ever shut down my phone. It was a huge issue with the vibrant though (before rooted)

i just got the mt4g yesterday and it constantly reboots on me sometimrs even locks up and battery removal ness... not sure if my auto install or update has anything to do with it very possible tho because i am comming from a nexus one that was rooted and noticed it loaded several root needed programs anyway just a thought and returning phone for new one

Updating MYNS and BRICKED my phone in the process. Anyone else?

I was installing the new Myn's Warm lastnight upgrading from the previous version. It did not install properly and COMPLETELY BRICKED my phone. It won't turn on, can't connect to computer via USB, nothing at all! Anyone else have this problem? OR any solutions other than taking to Sprint?

I doubt that your phone is bricked. Hopefully you DO have a rooted EVO though. I would plug it in and let it charge. Then take out the battery and put it back in and turn it on while holding down power and volume down keys to boot into recovery. Also hopefully you made a nandroid backup so restore that and go from there. I had no problems with flashing RLS5 at all. Hopefully this helps. Otherwise maybe someone with a little more knowledge can help you...
Sprint is DEFINITELY not the answer...

do a battery pull and try to get it to hboot. then try and run the RUU. if not you may have to take it to sprint.

The phone won't charge, won't turn on, can't hboot. I do have backups if I could get it to turn on I could restore it. Had no problems before. I will attempt to charge it as you have suggested but I even put a different fully charged battery in and the phone does not even make at attempt to turn on. I agree I doubt that Sprint is the answer

did you flash any radio updates? any prls, I've never heard of flashing a rom making a phone brick, but definitely heard of radio updates bricking devices.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk

i really doing think his update bricked your phone

This means that while installing Warm you bricked your phone. Don't give his ROM a bad name.
I would recommend trying to charge it and maybe try a different battery, but then just run the RUU and go from that. I had the same problem with RLS 4.
Sent from my EVO using XDA App

If you used the package to update the pri, radio, etc then that may be the problem, hopefully you aren't bricked.
Sent from my PC36100 using XDA App

Are you sure that you didn't flash the radio? I flashed Myn's rom last night and I didn't run into any issues, in fact I've never heard of a rom bricking a phone, that usually happens when a radio flash goes terribly wrong. Anyhow, you can take it back to Sprint since it's still under warranty and they will replace it for $35.

CheesyNutz said:
i really doing think his update bricked your phone
Click to expand...
Click to collapse
ive heard several people say it has in fact jacked their phones up. hence why i have not upgraded to it yet.

I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.

the radio update isn't included with the rom.
it's also been highly advised in the warm thread itself to flash just the radio, then just the wimax, then perhaps the nv/pri, because so many people have been having trouble with the pri update.
the radio combo pack isn't bundled with anything else and, right now, many think it should be avoided for reasons just like this.
not a solution, just clarification and friendly advice for anyone else who's curious about possible trouble with the upgrades.

I updated my radio/pri/wimax and all that jazz before the last Fresh update, so I had no need to this go around. I simply wiped data/dalvik/cache and flashed the RLS 5, with no problems. I did run into issues after I tried restoring my apps + data, but that was a Titanium Backup issue

arcurtis said:
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
Click to expand...
Click to collapse
Just my 2 cent.. often times we flash before reading the thread and then complain about a kernel,ROM or theme.
After reading what you said I can only come to the conclusion that you and all the others complaining about the radio update are obviously impatience. All who have had problem with the update on the radio all stated their phone sat on the white screen and they did a battery pull.
Yet the radio update thread says it will/can take up to 30 min to flash. The best way to check your phone would be to use another battery. I have never heard a bricked phone that doesn't cut on. That's a battery issue.
What kernel were you using before flashing?
What ROM?
What's your hboot?
Sent from my PC36100 using XDA App

I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.

arcurtis said:
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
Click to expand...
Click to collapse
Does the phone attempt to charge when you plug it in?
Sent from my PC36100 using XDA App

I can confirm brick.
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.

Nope the phone will not even charge. I've changed batteries and chargers. I am assuming I am one person who has just had extremely bad luck with a random flash. I was running Myn release and did a backup and wipe then phone would not reboot and completely shut down. I got the android guy with the arrow and then it went completely dead and won't turn back on.

dth4310 said:
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Click to expand...
Click to collapse
That is almost exactly what happened to me. I considered doing the same thing but don't really want to chance getting busted for a rooted phone

i've never flashed a radio update, i'm too chicken lol.
the quickest way to brick any phone is a f'ed up radio flash. or pulling the battery while flashing a radio.
i would take it to sprint and tell them you accepted a over-the-air update and then your phone shut off and this is what happened.

Help!!! Phone wont power up!

all i did was install CM7 nightly 41 after a full wipe, all went well. then installed titanium backup, restored all apps, then went to recovery and installed gapps, powered back up, and it tried to sync and it froze up, so after a while i pulled battery and pow no power!!! uh oh? any ideas?

Does it light up when you charge it?
Sent from my HTC Desire Z/G2 Using XDA Premium App

nope. i think its a total brick.
when i plugged it into computer the computer did attempt to install software (bubble on lower right of screen near clock that pops up saying new hardware found) but failed to install properly

holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more

tackleberry said:
holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more
Click to expand...
Click to collapse
Yea.. I hate that too. It doesnt really take that long though. You should get it in 5 days the latest.
Sent from my HTC Desire Z/G2 Using XDA Premium App

yea i bought a nokia prepaid X2 as a spare so i can at least get email. my old spare isnt great its a nokia 6310i lol. it works great as a phone but nothing more.
according to ups ground, its 4 days from texas to me, so tuesday i should see my refurb crap again lol.
just irritating, they wanna charge 20 bucks for 3 day shipping....verizon charged 10 for overnight and free for 2 day. unreal. i just dont understand how it failed like that. i did nothing different when changing roms! my phone was running like crap after i wiped and installed virtuous sense on it, so i wiped again and flashed CM back on, and it just bugged the hell out! any idea why it would brick like that?

Holding power+volume down doesn't work?

This may sound silly. But have you tried a battery pull?

You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App

ionic7 said:
You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App
Click to expand...
Click to collapse
And in the process make the cell phones and rate plans cost more for everyone else cause yet another a-hole wants there warranty honored when they knowingly VOIDED the warranty. Getting so tired of this. Between people bypassing paying for tethering and OVERLY taking advantage, and bull**** like returning phones that you KNOWINGLY VOIDED THE WARRANTY WHEN YOU ROOTED AND INSTALLED THAT CUSTOM ROM on it, it is ZERO wonder why they all want to sign the god dam bootloader anymore. These may be evil corporations were dealing with, but there is still a difference between right and wrong. These few on xda will ultimately be our downfall. This thread is all kinda fail.
Edit: sorry for sounding so harsh but you could have waited for at least a LITTLE bit of help first. it sounds like something not that out of our league to have fixed.
Sent from my HTC Vision using XDA Premium App

Edit: double post. Everytime I go to edit on the new xda prem app I accidentally hit quote!

battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.

We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
tackleberry said:
battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.
Click to expand...
Click to collapse

[Q] Full Brick Two Times in a Row?!?

Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!

nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
I'm just trying to learn from experience after all the flashing when you started to get freezing and acting up did you flash that one file on Virtuous Unity 2.35 page that states if you get phone freeze to flash the file

nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
As of now, there is no way to fix it. Strange though, my old one had a dead eMMC as well but I.could still go in CWM
Sent from my HTC Glacier using xda premium

Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.

Flashing that one file? I don't know which one you are talking about. If you saw it, could you point me to it, please?
Also, if your eMMC is bad, you could report it to T-Mobile? How? I was asking them about the eMMC, and they (the tech department) knew nothing about it. -__- Yeah, I had the M4G2DE. Although looking at this thread (http://forum.xda-developers.com/showthread.php?t=1081243) it seems that the SEM04G is still bad, or am I just confused?

Don't get confused. If you get just SEMO4G it is "good"
Try for yourself
Download terminal emulater
Type in:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
__________________
If this replay helped, please hit the "Thanks" button.

If your eMMC is bad, don't try to flash any custom Rom.
If you try to modify the system, the phone will get damaged.

febycv said:
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Click to expand...
Click to collapse
No. Check eMMC before rooting. That way, you will not have warranty problems.
Sent from my HTC Glacier using xda premium

Just to throw it out there though, it's not definitive that your phone will brick when you have the bad eMMC.
I used to have the bad eMMC before I exchanged it out for an unrelated problem. I flashed a ROM on that phone about couple times a week for 3-4 months with no issues. I've even seen some that have had the bad chip since day one and flash almost every CM7 nightly and still haven't had a problem. So my guess is that if your bad eMMC doesn't fail fairly soon and quick then you should be in the clear.

Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems

cowboy2844 said:
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
Click to expand...
Click to collapse
Yeah my point exactly. All of the failed ones are highly documented so every one thinks every "bad" eMMC is going to fail but who knows how many people with that eMMC has actually not failed?

I'm another one with the "bad" eMMC, so far no problems flashing roms.

I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)

_ice_ said:
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
Click to expand...
Click to collapse
Have you tried format the SD card with sdformatter v.2.0 or any other program to fat32 then try gain full root and put CWM on it to see if it stops that unable to mount problem
Sent from my HTC Glacier using XDA App

Just got another replacement, and looked up eMMC chip. SEMO4G!
With good screen as well! Hopefully, no more bricks.

Yeah I have the bad eMMC on a Mobilicity Panache. But so far nobody with a Panache (as opposed to MT4G) has reported failure, even though at least half of them have the "bad" eMMC. And seeing as a thread I started here is the only guide that speaks directly to rooting the Panache, I would expect any bricks to be reported on that thread.