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.
Related
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.
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
I am aware that the questions i am about to ask might have been asked 1000 times, but the search feature didnt help this time, so i am sorry if i am bugging out somebody. So here is what happened.
I got a mytouch 4g phone today, and i rooted it using gfree as it was the first sticky on the forum. i did a bit of research about bricks on mt4g (have been playing with androids since a long time) and didnt find anything about the emmc problem. then i tried gfree and it was easier than i thought. so i unlocked it (s-off), changed cid and unlocked sim (all using gfree -f). and i installed cwm and installed a rom. everything is working perfect.
but i discovered all the threads about bad emmc and bricks and stuffs like that. so i checked my emmc name and it came out to be the bad one. and i figured out that i did a big mistake. so i thought about restoring gfree backup and using the other root method (hboot s-off not radio). i was just about to restore the backup using gfree, then i noticed that my backup file (.bin file) was not present on my sd. i was shocked at first. then i found that i could s-on the phone using gfree without using backup bin file. but if i do that, will my phone not get emmc bricked like others? or do i need my backup file? can i use someone else's bin backup file? if yes, can you give me yours? any help would be really appreciated. i am worried that i might get a brick anytime. i was planning to make some tools for mytouch 4g (like i did for hd2) but i guss i will not be able to do that anymore cuz i might get a brick anytime. thanks for reading.
Edit: do all bad emmc phones using gfree get bricked? and what is the average period before it gets bricked (yea im too worried ) and is there anythign i could do now? (except for sending it for replacement since i bought it off craigslist)
This gfree and bad eMMC is just a correlation. Nothing has been proven to be a fact just yet. I've rooted my phone via gfree about 3 months ago now and I flash at least 2-3 times a week and nothing happened so far (I have the bad eMMC by the way). Everything seems fine for now.
I've also came across people that have the bad eMMC and have bee rooting and flashed hundreds of time for 6 months and going, so it's not a definite that your phone with the bad chip will die soon, so just keep that in mind.
But yes, it has happened to numerous people with the bad chip. Honestly, I would just ride it out and see what happens. If it dies just exchange it through T-Mobile.
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Jack_R1 said:
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Click to expand...
Click to collapse
I used this method on mine with the "bad chip" and had no problems.
tooter1 said:
I used this method on mine with the "bad chip" and had no problems.
Click to expand...
Click to collapse
You used g-free previously.. or root.sh wouldn't work on bad eMMc.
Please refer to the guides.
root.sh is guaranteed not to work on bad eMMc's unless g-free had previously been used.
Also not all "can't open /cache/recovery/log" errors in recovery are due to a dead eMMC chip. It can happen if your cache partition gets corrupted. Earlier this week, I had a bad flash--forgot to verify the md5sum before flashing, and after things started messing up, wifi not working, force-closes, etc...
So I went back to restore a nandroid backup I had made prior to the bad flash and got the dreaded "can't open /cache/recovery/log" error. I plopped the PD15IMG.zip on my sdcard and flashed it through hboot without any fail-PU errors.
So no, a M4G2DE eMMC chip doesn't always mean you'll have a brick. And cache partition errors in recovery don't always mean the eMMC chip died. What it means is that the "bad" eMMC chip has a much higher failure rate than the "good" chip. So if you have a "bad" chip, judging by the numbers, you have a much higher chance of ending up with a brick at some point.
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
3p4145 said:
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
Click to expand...
Click to collapse
Any file that has to be flashed through the bootloader (such as the stock RUU, radio files, etc) has to be named PD15IMG.zip for the bootloader to recognize it. There are two threads in the dev section that have the stock RUU you're looking for. A little searching should locate them.
Hi,
I'm a newb, and was thinking about rooting my phone and installing a different rom, but I read about this bad eMMC problem. I was wondering, if I have the bad eMMC and I don't root and install roms, will I still have the same problem that my phone might just die? Or is it only if I flash roms onto my phone?
Thanks,
Andy
Yes, if the "bad" eMMC in your phone is really bad - it'll die no matter if you flash ROMs or not. Just slower if you don't.
For what it's worth, I've had my phone with the bad emmc since December ... rooted since January & flashing roms ever since... no dead emmc. (Yet, if ever).
Sent from my HTC Glacier using XDA App
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
+1
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
good question. i don't have an answer to that. i've warrantied my phone, got another bad emmc around april? & have rooted & been flashing roms. phone hasn't died.
M4G2DE is just a regular chip. It's used for at least 3 other phones (G2, DHD, DS). I have one in my wife's Desire S, and it's rooted and running VU.
All the hype of the "bad" chip has gone WAY out of proportions.
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Teo032 said:
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Click to expand...
Click to collapse
Interesting info...
Sent from my HTC Glacier using xda premium
HTC Mytouch 4G EMMC
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Nice how much was that
Sent from my HTC Glacier using xda app-developers app
bramz said:
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Click to expand...
Click to collapse
I almost had the JTAG service done too. Before I did I did my research and come to find out that when I explained my situation to one of their techs I was emailing, he said that my situation was folly and there was nothing they could do. He stated it was the dreaded "bad eMMC chip problem" yet all i had was cache and recovery errors just like what was mentioned above. Formatted my sdcard, put the stock T-Mobile GB PD15IMG.zip on there, flashed, and booted right up. Lost root of course, but able to get it back to rooted state and been flashing custom roms ever since. Pretty sure just like what was stated above... Blown WAY out of proportion. Hope this helps some people with their anxiety about this issue.
Hello all. I am hoping I can get some advice as to what to do about my wife's phone(epic 4g). Her phone is completely stock and has never had any custom rom or anything flashed to it. Over the last three months, the phone has semi-bricked itself 3 times. The phone will just power off by itself and when it is rebooted, it gets stuck at the "samsung" screen. The only way I can get the phone back to normal is by flashing DI18 with Odin v1.85 (no other versions work). Anyway, my wife obviously does not want an unreliable phone. I should also note that about 8 months ago, my 2 year old son took my wife's phone and threw it in the toilet. After taking the phone apart and drying it, the phone worked perfectly for the following 5 months. For that reason, I do not think it is a good idea to have sprint look at it because the water damge indicators will be colored. I have seen a thread here that talked about calling sprint and complaining about the epic and in turn getting a new nexus s. I am not sure what to do. I cannot afford another phone. my wife uses her phone as the house phone as well. The phone bricked itself yesterday so I flashed the stock DI18 rom. I then tried to flash EC05 and it bricks itself again. Even the OTA update bricks the phone when ran. I really appreciate any help/suggestions the community can provide.
Thank you
Sent from my SPH-D700 using XDA App
Interesting problem you have there. I barely remember Di18.
I would use Odin to flash the EC05 stock rom. QBKing77 has an awesome video showing exactly how to do that. That would not brick your phone unless you are using the stock cable. Get a new one. First boot will take a little bit. Here is the link, the description includes all necessary downloads. I would fresh download everything even if you think you already have it. http://www.youtube.com/watch?v=YQ2g6J1JgjU
There is no reason it will Odin to DI18 and not EC05. Water damage doesn't force the phone to like one rom over another. If the others are "not working" as you said, then you are doing something wrong. Follow the video to a T and it will work.
If you want more I would the one click root it with CMW 3101 and remove all of the sprint bloat. Not necessary, but will help the phone a bit.
If the water indicator has already changed, what is stopping you from using a custom rom that is more stable? You might not have as many issues.
Thank you both for your replies. I am using the stock cable, so I will try a different cable. It may be possible that I am doing something wrong as far as flashing roms. It has been a while since I have flashed anything to my phone. Again, thank you very much for the help!
Sent from my SPH-D700 using XDA App
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Arion02 said:
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Like I said, water damage will not cause your phone to only be flashed to DI18. Now the random reboots may have something to do with the water damage, without more info as to what is happening when it reboots I have no idea. Maybe a custom stable ROM with voltage control set correctly would help with that?
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...
friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.
I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium