yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Android Development] acsi007:
But I think the other important open question is what about people like me who have the 'bad' chip, but don't display the subsequent negative results on that second set of shell commands. What then, can we also breathe a sigh of relief?
[myTouch 4G Android Development] kimbernator:
Sorry, I dont have a definitive answer for that. It seems to happen to people who have flashed some roms already, so i wouldn't throw caution to the wind.
[myTouch 4G Android Development] TeeJay3800:
I'm going to run these tests tonight, but lets say I'm unlucky and have the bad M4G2DE chip. Does that mean any day now I'm going to start getting those cache errors in recovery mode? My MT4G has been rooted for 5 months now and I've never had a single problem. For those of us with the "bad" chip, what can we expect going forward?
[myTouch 4G Android Development] kimbernator:
I think there must be at least one more variable causing this. If you could take the time, would you just list everything software and hardware related about your device you can think of? Purchase date as well.
[myTouch 4G Android Development] tilt4life2:
Is this step only if we have already experienced the problem to verify the cause of the problem?
[myTouch 4G Android Development] TeeJay3800:
I hadn't run the test yet when I posted that, but after getting home, it turns out I have the "good" chip. As I said in the other thread in General, there is something really wrong with this situation. A known faulty chip is a manufacturing defect that is the manufacturer's job to rectify. No one should be paying for shipping or insurance deductibles...HTC should be shipping new phones for free.
[myTouch 4G Android Development] kimbernator:
Hmmm... well I've heard that some of these were made in China and others in Taiwan. Do we have any connection there?
[myTouch 4G Android Development] neidlinger:
in the screen - yes.
[myTouch 4G Android Development] kimbernator:
Oh. Never mind.
[myTouch 4G Android Development] petrochemicals:
So it looks like I have a M4G2DE and I can not root the regular Visionary way, so the only way to root is with gfree.
[myTouch 4G Android Development] kimbernator:
This is something to consider as it seems the visionary method won't work for a lot of people. Maybe it has to do with this chip and only gfree works with it = defective chip. basically doomed from the beginning.
[myTouch 4G Android Development] guhl99:
Yes, only if you already are experiencing the problem to make sure that the emmc chip ist the source of the problem.

Cause in all threads about this issue there are people showing up with a similar problem that is caused by a corrupt partition table (i.e. by visionary+) that can be cured by reflashing the stock rom or repairing the partitions.
[myTouch 4G Android Development] acsi007:
guhl99 - I posted my shell output from the second couple of tests you prescribed (I have the chip in question). (see earlier in this thread)

While I have the M4G2DE, my output from the subsequent shell commands didn't exhibit bad result that you told us to look for-- does that mean my M4G2DE will be ok then? Can it be a non-defective revision of the chip?
[myTouch 4G Android Development] Freek91:
Just wanted to say that my phone has the M4G2DE and has the same info i linked above...i also rooted using gfree...basicly the post im quoting is identical to mine

so like others have asked...what do we do now?

ive flashed my phone 2 dozen times since i got it in Feb and never ran into any problems that werent user error
[myTouch 4G Android Development] dcwiker05:
I have the defective M4G2DE chip:

http://i278.photobucket.com/albums/kk107/dcwiker300zx/Untitled.png

I recovered from this issue once before (SEE HERE) but have since gotten the error again. Looks like I'm SOL
[myTouch 4G Android Development] xdviper:
Yup its done. Get a replacement. So its the same exact issue as the G2, the eMMC dies and won't start. Now we gotta figure out why.

It also sucks to know that, I have a ticking timebomb in my hand, it could die anytime.
[myTouch 4G Android Development] tilt4life2:
Can we get a warranty replacement on this?

I don't want the phone do die on me in a year after the warranty. This thing sucks.
[myTouch 4G Android Development] kimbernator:
It might not be easy but the case could be made for warranty for defective hardware.
[myTouch 4G Android Development] NovoRei:
Could this be clock/overclock related? Could emmc be in sleep mode rather than dead? Could emmc address be corrupted?
[myTouch 4G Android Development] guhl99:
Hi!

clock/overclock related?

- don't know might be

in sleep mode rather than dead?

- no. It is active in boot for read but at the first attempt to do something in read/write mode (in the boot process when cache should be mounted in read/write mode) it disappears an does not reinit again.

emmc address be corrupted?

- not very likely but it might be everything also i.e. a defective dc/dc converter that can/does not supply the voltage for write anymore

It is not necessarily the case that all M4G2DE chips are effected by this problem. It could also be just a defective production batch. Our possibilities to diagnose this issue are very limited cause we only know that it is this problem if the phone has a non-stock recovery. A phone that is stock just would not boot one could never know why.

It seams plausible that people that root their phones and flash roms more often will experience this problem more then others simply because they write to the emmc a lot more.

Have fun - Guhl
[myTouch 4G Android Development] darinmc:
Doubt it's related to clock. All of the custom kernels here have voltage tables under or at stock, so while the system might fail, the possibility of hardware damage (short of long term heat issues) is pretty slim.

Considering all of the failures seem to have the same emmc serial, I have a hard time believing it could be a dc converter supplying incorrect voltage or we would see it in other serials. Still I agree that there are far too many factors to solve the problem. Then again the idea is to make people aware of risks.

Your final point is the most important in my eyes. It's a lot like solid state disks in PC's, the more you write to them the faster they fail. 80% of the problems I've seen with macbook airs are bad hard drives. Gathering the info just helps people to understand that flashing with that emmc serial is more dangerous than with any other. Not exactly a perfect situation, but it's better than nothing.
[myTouch 4G Android Development] guhl99:
Hi !

Just for info. There is a confirmed case of a Vision that had this problem but never used gfree.

Have fun - Guhl
[myTouch 4G Android Development] |Melvin|:
i was rooting a mytouch 4g and i always use gfree but the damm phone have the cache problem...... hboot scans but never finds pd15img.. .recovery dont flashes sense roms... the phone is totally unstable ..... useless .. .keeps bootlooping all the time. .. the recovery is just a mess .. i wanna know how to fix cuss i was trying to open rom manager but it fcs
[myTouch 4G Android Development] eunkipark92:
This happened on my HTC g2. The only difference was that I flashed mini on top of it got suck on HTC logo. Yanked out battery and the phone was bricked for good. No adb no hboot no recovery.
[myTouch 4G Android Development] saranhai:
hi so it seems like my eMMc chip is dead...

is there anyway to fix that? or has the issue become a hardware problem?
[myTouch 4G Android Development] Phateless:
This is what I've been asking. I don't know if it's gfree that causes the damage or if the bad chips require gfree to root but there seems to be some kind of correlation.
[myTouch 4G Android Development] moto211:
HUGE sigh of relief! After seeing this thread and discovering that I have the good chip I'm sooo glad that I didn't make a warranty claim on the bad screen. Without side-by-side comparison, the screen doesn't look bad (IMO) and it would have sucked to exchange over a cosmetic issue and end up with a ticking time bomb piece of hardware. I'm implying that there's any connection between screen and emmc, only that it would be my luck to exchange a bad screen with good emmc for a good screen with bad emmc.
[myTouch 4G Android Development] theANDROIDosX:
Warranty Claim NO GO!

So I just went threw T-Mobile and ultimately threw Assurion to do an insurance claim for defective hardware for my girlfriends MyTouch 4G! I explained the issue and that the phone has a hardware defect and she asked me how I was able to pinpoint issue and asked a LOT of questions about altering the firmware! After about 30 minutes speaking with her, she transfered me to her supervisor and they rejected my claim!!!!! GRRRRRR just a heads up! Good Luck to anyone else! Too bad for my GF...I have the good eMMC lol
[myTouch 4G Android Development] acsi007:
theANDROIDosX, that's retarded. So I guess they'll cover it if you step on it or drop it in the toilet, that's you're typical claim I imagine. But if you try to make it better by upgrading the phone to suit your needs, then you lose 500 bucks. Wow.

So they wouldn't even let you pay the 129 deductible and send it in? They just told you to take a hike on that phone, even though you (I assume) paid the insurance (or your girlfriend did)?
[myTouch 4G Android Development] Doogitronix:
One thing I have found helpful when dealing with them or with standard warranty claim is to not sound like you know what your talking about. The standard excuse of " Touch screen never functions correctly" always works.
[myTouch 4G Android Development] elry567:
Just out of curiosity how do u know if u have the bad screen
[myTouch 4G Android Development] phaino00:
Check this thread out.

http://xdaforums.com/showthread.php?t=863679
[myTouch 4G Android Development] dcwiker05:
I think he is saying that they wouldn't let him warranty it, if he is saying that they wouldn't let him file it through insurance and pay the deductible, that is complete and utter bull ****!! I can see them not doing a warranty replacement because the device is rooted but insurance is there to do just that INSURE your device regardless of how it broke you pay the premium and the deductible so they can shut up and send you a new phone, period!

I hate the damn insurance company after they gave me the run around when I dropped my MyTouch and the screen shattered. They sent me a replacement that wasn't even put back together correctly and tried to argue with me about replacing it for me. My case ended up pulling the screen off within a week, then they finally sent me another.
[myTouch 4G Android Development] eunkipark92:
Yay good screen good emmc chip
[myTouch 4G Android Development] PureH2O:
I just bought the mt4g and I had the 0.86.000 bootloader and visionary worked 100% along with the root.sh method to turn s=off. My wife's mt4g was the exact same. It took 3 times for my wife's phones to turn s=off. That 0.86 bootloader is just more stubborn. Keep at it and visionary will work. Gfree is not a good way to get s=off. You will get the recovery error. Its happened to three of my friends. All used gfree method.
[myTouch 4G Android Development] acsi007:
Would be so good if grankin01 or Scotty of the gfree thread fame could make an appearance and comment on all the new unexpected problems since they posted the gfree method. There's a lot of valuable field data now for their method that I'm sure would interest them...
[myTouch 4G Android Development] cal3thousand:
I've only had good luck with using the GFree method.

Is everyone that is having issues checking their MD5Sum before extracting gfree?

This is a most critical step and should never be taken lightly. I don't care if you downloaded from your personal NAS from the next room, you should check your MD5Sum
[myTouch 4G Android Development] guhl99:
Hi!

This is absolutely untrue.

First of all there are already documented and known cases of phones with the M4G2DE chip that have this issue and never used gfree.

Scotty2 and me (beeing the authors of gfree) can rule out any relationship between using gfree (or radio S-OFF in general) and the dying emmc issue.

On the contrary it can be dangerous to use visionary+ for permanent root. This can and does lead to corrupted system partitions which can be complicated to repair.

Have fun - Guhl
[myTouch 4G Android Development] guhl99:
Hi !

Scotty2 and me (being the authors of gfree) are well aware of this problem with the dying emmc chips of the type M4G2DE. We spent days and nights in the last 2 month to analyze the problem.

And we are certain that there is not correlation between radio S-OFF (which is achieved by the gfree method) and the dying emmc chips.

We are convinced that this really is a hardware issue that effects all phone with this chip (maybe only a certain production batch).

As already said in my other posting, there are documented cases of HTC Vision (G2/DZ) phones with the same (verified) issue that never used gfree. So we can definitely falsify the theory that it only happens to phones rooted using gfree.

The pretended correlation between the usage of gfree and the emmc issue is a statistical effect caused by the fact that most phones have been freed using gfree.

This also applies to the effect that only rooted phones seam to be affected. First on a phone that is not rooted you could not even tell that you have this issue because it can only be diagnosed if the phone is rooted. And second people with rooted phones write a lot more to the emmc (flashing roms, restoring nandroids, ...) then people with unrooted phones. So it is simple and easy more likely that this issue with the M4G2DE chip effects rooted phones.

Have fun - Guhl
[myTouch 4G Android Development] PureH2O:
That's totally false. Gfree is the source of the issue. Of course the maker of the root method will talk **** about other root methods and of course you the author of gfree will deny any wrong doing...General motors has done that for 16 years with all the dex cool coolant issues...but that proves my point...until someone somewhere proves its the gfree method causing the issue then the authors will deny deny deny....so ultimately if I was the author I would deny deny deny as well.
[myTouch 4G Android Development] _ice_:
okay. weird because I have the sem04g chip, good screen. yet I have had cannot mount cache or data issue before (recovered using pd15img)

also when I issued the dmesg command in shell I compared the output

I didn't get any failed to get card ready etc... errors.

then why did I still encounter this issue. and I am afraid I may have this issue with a failed PU in the near future too?

btw I was one of the few that was able to recover from it as I have stated my methods before.

my theory is that: clockwork mod recovery failing to mount partitions especially when you switch back and fourth from ext 3 and ext 4 roms. and those with a m4g2de chip are SOL.

Also, it would be nice if when you post you would list these things:

1. what method of rooting you used: visionary + with gfree super CID unlock

2. which version of hboot do you have: eng 8.0.2007

3. which emmc chip serial do you have: sem04g

4. have you encountered this issue before: yes
[myTouch 4G Android Development] phaino00:
The logic here is fallacious. Consider what Guhl stated about falsifying.
[myTouch 4G Android Development] guhl99:
Hi !

I understand that you are concerned but this totally not the same issue. We have to be very careful not to mix this two issues that show the same symptom (recovery or other partitions can not be mounted) but are not the same problem at all.

The problem you have is caused by corrupted partitions tables or wrong file systems. As you stated already this can i.e. be cause be switching from ext3 to ext4 and back. It can be cured by recreating the partitions or recreating the filesystems and the easiest way to cure it is flash the stock rom PCxxxxx.zip

The problem that shows the same symptom but is caused by a dying emmc chip is a totally different issue. Please see my posting here http://xdaforums.com/showpost.php?p=13895268&postcount=48 in this thread on how to diagnose if you have the dead emmc problem.

Have fun - Guhl
[myTouch 4G Android Development] guhl99:
Hi !

I don't even know why I answer to this posting but I somehow believe in communication leading to positive things in general.

On the contrary to you (or a least what you say about you) I would not deny, deny, deny.

If I had the slightest suspicion that gfree really was the cause i would warn people (and that's what I general also do here) not to use gfree until we know more or sorted it out.

The reason why I do not warn form using gfree is mainly that the theory that it is caused by gfree has been falsified by documented and analyzed cases of phones having this issue but did not use gfree.

I do not want to go into detail because you obviously don't even know what S-OFF is and how it is achieved, but in all the discussions that we had about this cases in the #g2root channel we where not able to come up with a not contradictions theory how radio S-OFF could cause it.

But if you are able to come up with one I welcome you to join us at the irc channel #g2root on freenode and discuss it.

It can be very misleading to draw a conclusion on a very small sample of cases in your personal environment. We have an average of 110 downloads of gfree per day from the original site alone not counting the downloads from sites where it is mirrored as i.e. the cyanogen site. If radio S-OFF really was causing this how many cases would we expect? A lot more for sure.

Thanks for your attention - Have fun - Guhl
[myTouch 4G Android Development] JDV28:
Have there been any reported issues with the SEMO4G (good) emmc chip?

I have a year warranty from tmo on my glacier and i have the reported "bad" chip, wondering if i should exchange mine just to be safe?
[myTouch 4G Android Development] guhl99:
Hi!

I (or in general we at #g2root) do not know of any reported cases where the issue with the dying emmc chip happened with an SEM04G.

But I think you will not be able to do a warranty exchange based on a potential future problem.

It is a tricky situation: I you stay rooted and the problem happens you will not be able to unroot or wipe the phone cause nothing can be written to the emmc anymore. And T-Mobile might not do an exchange because you rooted and thereby voided the warranty.

If you unroot you might experience the problem or not but you probably wont have fun with your phone.

Of course you could try to do an exchange based on a different reason.

Have fun - Guhl
[myTouch 4G Android Development] JDV28:
No, No, I paid the extra $50 or whatever it was for a full warranty, if i crush this thing with a hammer, theyll take it back, so i figure ill drop it nice and hard and get a new one, not try to explain all of your guys' work to someone who thinks "rooting" has to do with the weeds in their backyard.
[myTouch 4G Android Development] PureH2O:
Ok so I typed that in terminal emu and I got "SEMO4G" so I guess I am free and clear of this cache error then. Thank God.
[myTouch 4G Android Development] JDV28:
You contributed SO much with this post. I'm sure no one will thank you.
[myTouch 4G Android Development] PureH2O:
Your welcome JDV.
[myTouch 4G Android Development] PureH2O:
If I can be of any help to u in the future just let me know. :)
[myTouch 4G Android Development] irrompible:
Is this a problem that only rears its head while attempting to flash a ROM or can it pop up at any time?

I have the bad emmc but I'm on a ROM that has been working fine and I don't plan on changing anytime soon so do I have anything to worry about?
[myTouch 4G Android Development] JDV28:
Read the OP................

"Now it looks like while the phone is being used, or booting up and or trying to read or write from emmc the chip suddenly dies."
[myTouch 4G Android Development] Towle:
Such negativity.. This is exactly what is making xda less enjoyable for everyone.

Sent from my Royal Ginger powered Glacier
[myTouch 4G Android Development] JDV28:
It annoying when people dont use the resources right in front of their faces. My posts moral is the exact same as what every (competent) person on XDA is saying, USE THE SEARCH FUNCTION. But in this case, he was already in the thread with the answers, just chose not to read...

XDA is a resource if I'm not mistaken, not a hang-out.
[myTouch 4G Android Development] Towle:
I agree, it does get annoying when people decide not to read, and yes, search is your friend. But this is also a community where we can all get together and help each other out. I guarantee you will have questions, and will expect another xda member to help you out and politely answer your question. That is what is so great about these forums. As long as Android is open source, everyone will be joining together here at xda asking and answering questions so everyone can have the best experience possible with their rooted Android device. But before asking a question, please take the time to do a little searching and reading. I promise you, most questions have already been asked and answered, and by searching you can probably get a more helpful answer than what someone will tell you, as well as all the helpful information you will read along the way.

Sent from my Royal Ginger powered Glacier
[myTouch 4G Android Development] JDV28:
Answer me this, did i say a SINGLE thing sarcastic or suggestive? No, I suggested a useful hint for his/her future here, then answered his/her question.
[myTouch 4G Android Development] mark manning:
+1000

Jdv or what ever your name is, didn't your mom teach you that if you can't say anything nice. Its better to day nothing at all?
[myTouch 4G Android Development] PureH2O:
You are very negative JDV or whatever your name is...PCV, ADA, blah blah...anyway mark is right. We are all here to help people not degrade people.
[myTouch 4G Android Development] JDV28:
I answered his question without even hinting at an insult. Stop trolling now, kids. I actually helped him by answering his question, instead of you guys trying to get your post count up by bothering a helpful member of xda, me.

edit: h2o right now you are degrading someone and not helping, so hold your tongue. I CONTRIBUTE here, unlike you two obviously.

Anyways, both of you stop talking now. Stop taking up this thread with your quest to create internet drama.
[myTouch 4G Android Development] Phateless:
I'm with jdv. He wasn't rude, he just reminded the poster where to find the info.
[myTouch 4G Android Development] mark manning:
"Read the op..............."

Comes off very sarcastically and rude. Its just unnecessary to state it the way he did. It makes people who are not on here much feel like they did something wrong to the point they may not want to come back. Sometimes its not what you say but how you say it. Especially in writing.
[myTouch 4G Android Development] irrompible:
For the record, I wasn't insulted at all by JDV's post. I had infact read the op but must have overlooked that part of the quoted text. Thanks again.
[myTouch 4G Android Development] mark manning:
Thanks even tho you weren't offended (which is good) you made my point by saying you had already read the op.
[myTouch 4G Android Development] neidlinger:
I see both sides of the coin. JVD did have a good point in stating "read the op". The information was laid out in black and white. And i see the other side of the coin, it does look to be sarcastic.

But this is the internet and these are read words. WE have not clue how the poster meant them. You can said "Your looks will cause time to stand still" or "you have a face that will stop a clock". Basically the same exact phrase with two completely different underlining meanings.
[myTouch 4G Android Development] JDV28:
I apologize if there was any sarcasm in my...words? lol I'm glad you werent offended and glad I helped. now lets give these nice people their thread back, eh? ;)
[myTouch 4G Android Development] neidlinger:
Where is the fun in that?

FYI : i didn't take as sarcastic either. ;)