yashsingh1/xdaforums huggingface dataset:
[myTouch 4G General] bballcat03:
how do I get passed "device offline" when doing adb shell?

I don't have another USB I can try...
[myTouch 4G General] netter123:
Looks like I have the 'good' chip...used gfree method (followed the steps in "TRUE PermaRoot and the ULTIMATE S=Off!!! Check this out even if you're rooted!!!" thread), but I've only flashed a few roms since rooted.

My wife has an unrooted one, but was thinking of rooting it and flashing roms for her at some point. Is there any way to tell what chip she has prior to root? I tried just doing the same adb commands, but rebooting to recovery just leads to the red triangle on her phone and a device offline error when trying to load "adb shell".

I'd definitely like to know the easiest way to determine her chip prior to root, if that's even possible...?
[myTouch 4G General] jimbo11883:
I have SEM04G as well. Thank you for this thread, very informative!
[myTouch 4G General] saranhai:
so it seems as if this is an issue with the eMMc chip correct?

if so, then wudnt that mean it is now a hardware issue?
[myTouch 4G General] jdkoren:
Are the USB drivers installed properly? I've noticed that more drivers get installed when your phone connects without actually being booted up (like when you try to use fastboot USB the first time).
[myTouch 4G General] Mathato:
hit the lotto....

got a "good one"

<6>[ 6.525939] mmcblk0: mmc0:0001 SEM04G 2.17 GiB
[myTouch 4G General] rabryant152:
I've got the bad one (M4G2DE 2.10 GiB).

I ran the diagnostics at <http://xdaforums.com/showpost.php?p=13895268&postcount=48> and mine hasn't failed yet.

I'm currently just running rooted stock.
[myTouch 4G General] lowandbehold:
i can't vote twice, but my wife also has the "good one"...rooted gfree
[myTouch 4G General] Phateless:
So can anyone confirm that the "bad one" ONLY roots with gfree?
[myTouch 4G General] gixer2000:
I have the bad chip and there was another method that worked for me but most of them would not.when I get to my laptop ill post the method I used
[myTouch 4G General] tw39515:
I guess I have the so called bad chip. temp rooted with visionary and went straight to gfree. flashed all the radios and and all the recoveries. Im also a rom tester and flash different roms every night. Havent had any issues at all. ill keep my fingers crossed hope the info helps.

C:\android-sdk-windows\platform-tools>adb reboot recovery

C:\android-sdk-windows\platform-tools>adb shell

~ # cat /proc/kmsg | grep 'mmc0:0001'

cat /proc/kmsg | grep 'mmc0:0001'

<6>[ 7.917083] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

C:\android-sdk-windows\platform-tools>adb shell

~ # dmesg | grep mmc0

dmesg | grep mmc0

<3>[ 7.761596] mmc0: No card detect facilities available

<6>[ 7.762023] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8

<6>[ 7.762237] mmc0: Platform slot type: MMC

<6>[ 7.762329] mmc0: 4 bit data mode disabled

<6>[ 7.762542] mmc0: 8 bit data mode enabled

<6>[ 7.762664] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz

<6>[ 7.762847] mmc0: Slot eject status = 0

<6>[ 7.762969] mmc0: Power save feature enable = 1

<6>[ 7.763092] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x0bc36000

<6>[ 7.763275] mmc0: DM cmd busaddr 0x0bc36000, cmdptr busaddr 0x0bc36300

<6>[ 7.915374] mmc0: new high speed MMC card at address 0001

<6>[ 7.917083] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

~ #
[myTouch 4G General] Phateless:
According to the poll, nobody with a bad chip rooted using visionary. Let's see how this plays out.
[myTouch 4G General] gixer2000:
I have the bad chip and visionary would not work. I could temp root all day long but a perm would not stick
[myTouch 4G General] Phateless:
I tried a phone that would not root with visionary. Temp root worked fine but S-OFF just never stuck.
[myTouch 4G General] gixer2000:
this is the method I used.

http://xdaforums.com/showthread.php?t=1035278

I seems like it came from gfree but i don't think its the same thing but i could be wrong. Ive been flashing a ton of stuff the last few weeks. not really sure what i should vote for
[myTouch 4G General] Mathato:
I have a good chip and couldn't root using visionary. I had to use gfree

Sent from my doped up HTC Glacier.
[myTouch 4G General] vqt:
I have the bad chip. I rooted with gfree initially. I did not try the visionary method first. This thread made me unroot according to the guide in this forum. Everything was back to stock and s-on. I then rooted with the visionary method without a problem. I don't know of this helps. My phone is working fine.
[myTouch 4G General] Phateless:
Thanks!
[myTouch 4G General] neidlinger:
i cannot vote correctly i've used both the ./gfree and the root.sh method.
[myTouch 4G General] PermROOT:
UPDATE: I just got hand on another MT4G for testing but it seem to be the MT4G-SEM04G and I rooted via VISIONary+ but some folks ran in to issues on Q&A section with hboot so ATM I am helping them get S=OFF as they try to foolishly revert back with stock PD15IMG.zip (rom/radio) and due to having new radio locked out. Let me find fix and then ill get back to this emmc issue once it for all and see if I can replicate it if not I need to get my hand on another MT4G-M4G2DE.

PS to fMOD's: Keep banning it you panzy uneducated mod. Maybe you should stick to iPoney and leave the real hacking to the bigboys so you feel safe.
[myTouch 4G General] Phateless:
So you're saying if I PD15IMG back to stock an OTA update will come through with the new radio that will prevent me from re-rooting?

Good to know, because I've been thinking about going back to stock lately just to start fresh.
[myTouch 4G General] PermROOT:
Hello Phateless do you remember me? lol I am always on diff name so ya.

But yes PD15IMG.zip is not the golden solution to everything. It all depends on how you originally rooted your MT4G as VISIONary+ (TempROOT) and root.sh (PermROOT). In that case your S=OFF security off flag is dependent on the eng hboot which was pushed to /dev/block/mmcblk0p18 during PermROOT.

Now since its not true security off once you have newer radio. You try to run PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M) after the first update which is stock hboot you would be locked due to it changing S=ON thus on next step it will fail due to the image being older than originally on which is currently flashed which would be the radio. In this case your in a point where you shouldn't be as you can be locked out and no way to reroot. which I am working on finding. This also goes for gfree radio s=off.

If you do want to go back download PD15IMG.zip (stock radio 26.03.02.26_M) and then flash it once that is done then you can revert back to stock rom/radio using standard PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Keep in mind unless the new PD15IMG.zip is out you can't revert it back if your locked out due to source being outdated than current image.
[myTouch 4G General] Phateless:
Lol I recognize your avatar, good to see you. :)

I rooted with visionary and Eng hboot, no gfree for me. The idea of cid unlock never sat well with me in the first place.

I see. New radio causes pd15img to fail because it trips the newer version check AFTER pd15img flashes hboot and then you're stuck with locked down hboot and basically ****ed. Lol, that would suck, thanks for the heads up.

I went back to stock radio due to GPS issues but if I feel like wiping I'll just use fastboot.
[myTouch 4G General] vqt:
Thanks for this piece of advice for people who rooted via visionary. Is there a way to make this a sticky or maybe add it to the Bible in the development section so people won't run into this problem in the future trying to revert to stock.
[myTouch 4G General] _ice_:
engineering bootloader is essential, incase you get fail to mount /cache or /data, if you DO NOT have the engineering bootloader, then you would be screwed since you cannot use the pd15img to revert to stock and attempt to fix the corrupt partitions caused by switching from ext 3 to ext 4 roms.

also engineering bootloader allows you to flash radios from within the bootloader, and splash screens :D why not?
[myTouch 4G General] PureH2O:
Woooo hoooooo I got "SEMO4G".....TIME TO CRACK FLASH. :)
[myTouch 4G General] tempaznx:
<6>[ 7.547698] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Boo, bad one. ):
[myTouch 4G General] carrrnuttt:
I guess I have the "bad" chip as well. :mad:

I'm no tester, but I rooted my phone from the first day I got it using the gfree method, and have been on CM7 RC's, stable, and nightlies ever since, including a few restores, as well as kernel flashes. I have also switched between the available radios a few times to find which one I wanted to stick with. I'm on stock right now.

Here's my output:

C:\AndroidSDK\platform-tools>adb shell

~ # dmesg | grep mmc0

dmesg | grep mmc0

<3>[ 9.558563] mmc0: No card detect facilities available

<6>[ 9.559112] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8

<6>[ 9.559234] mmc0: Platform slot type: MMC

<6>[ 9.559448] mmc0: 4 bit data mode disabled

<6>[ 9.559570] mmc0: 8 bit data mode enabled

<6>[ 9.559692] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz

<6>[ 9.559875] mmc0: Slot eject status = 0

<6>[ 9.559997] mmc0: Power save feature enable = 1

<6>[ 9.560211] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x0bc7b000

<6>[ 9.560333] mmc0: DM cmd busaddr 0x0bc7b000, cmdptr busaddr 0x0bc7b300

<6>[ 9.717773] mmc0: new high speed MMC card at address 0001

<6>[ 9.719177] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

~ #
[myTouch 4G General] damnoregonian:
no.

the rate is higher because more people used gfree.

anything you do on your phone modifies the "mmcblk".

gfree and visionary both use wpthis to power cycle the emmc.

the *only* difference is that gfree also goes through and sets the flag for s-off on the phone.

there is simply no logical assessment you can make if even a single of them that has failed used visionary.

if there is some bug that makes the phone's emmc stop being writable because of radio s-off, then it would be limited 100% to that alone.

when using sensationalized statistics, please make sure to understand them.

scotty2
[myTouch 4G General] PermROOT:
I am aware gfree/visionary both uses wpthis.ko but since we have no reports of VISIONary users dying so far from it. At this time it does not mean its gfree/visionary as it could just simply be defective chip. When I was doing this 4months ago I didn't even know G2 faced same issue but due to the community push we now have cross linked it as G2/MT4G both uses those same emmc. I was able to replicate fail-pu few months back on SEM04G based chip and recover. Just 2nigths ago I did get can't mount also on test MT4G also SEM04G. As I said this could just simply mean M4G2DE is inferior as reported by few folks the stats are higher they are unable to disable write protection thus unable to push the eng_hboot using VISIONary+. I still need to do more work and see what happens.
[myTouch 4G General] damnoregonian:
g2, mt4g, desire hd, desire z, and thunderbolt all use the same sandisk parts.

g2, mt4g, desire hd are confirmed to also use the suspected defective parts.

g2, mt4g, desire hd, desire z, and thunderbolt users have all had failing emmc parts.

waiting for confirmation if the thunderbolt failures are the weird off-brand emmc chips.

getting the "can't mount" error is easy. cwm has problems at times if the filesystem gets corrupted.

the trademark of this problem is when you see the failed controller resets in dmesg.

again, whether gfree or visionary is used is completely irrelevant.

the problem occurs on both radio s-off phones as well as radio s-on phones, as confirmed by talking to people who have experienced the failure first hand.

the stats you have are highly slanted based on your poll group.

assuming that the failures are limited to gfree *only*, the percentage of failures in the poll is 10.2%

given the poll includes 8 people who have used visionary, extrapolating the failure rate to include potential visionary users gives you an estimated amount of visionary failed devices of <1.

my point is, it's impossible to even speculate about a correlation with a statistical significance that low.

i have third-party information that an employee at a hardware repair shop dealing with a few thunderbolts with this issue has noticed that they all have "unmarked" emmc chips instead of sandisk ones.

i expect we will soon find out that the failed thunderbolts also have the oddball chip.
[myTouch 4G General] PermROOT:
Nice update on the issue related outside MT4G as the issue is bigger as it seems. In that case HTC will never officially admit it as faulty or they have to take responsibility and replace it under manufacture warranty. Technically as we know just by checking the boot stats they can deny the whole warranty claiming it was caused by the rooting procedure as outlined by their TOS/AUP and void it.

Far as I know MT4G/G2 shares same chips as you folks already know from being in G2 world. But the issue for us surfaced here first just about 5months ago or so. Now I can't say the capacity of DHD but don't TB have 8GB emmc? If so and if they are faulty are they coming from same vendor? Are they using full storage? or emmc formatted same as our chips using SLC-EUDA? I don't own those device so I can't say but my SEM04G device's mmcblk0 output is below.

Now I myself know the data pool is flawed but the thing is we have to take it as is and account for "available" data we have which would be from our XDA users who already submitted feedback. What happens outside in wild we won't know as its subjective. So far we can't confirm that:

1) User who has M4G2DE who is not rooted is effected by it. As they can't even verify they even have it so its moot point. But since we speculating here how does it effect long term data integrity compared to SEM04G chips in its life cycle comparing it duration. Now this can also be subjective based on users operation do to wear and tear level degrading the memory cell. Now as they can share same controller does not mean it is sharing same partitions. So user views it as system intact and not worry about it. But user even if effected won't notice as its operational for time being unless in the future the chip dies completely.

2) Has any SEM04G chips died or faced same issue in G2? as you from G2 world you would have stats on that. In MT4G so far as of now I can't say we heard of any.

3) Why is M4G2DE users unable to apply root.sh using VISIONary+? its using your modified wpthis(wpx)? Now you would know more about this as you made it. So where does it fail during power cycling while in write protect being disabled disabled or verify it was disabled.

Only time will tell but for now the user pool effected for us is very small which may grow given the time. How many folks effected by it in your G2 world? or other DHD even.
[myTouch 4G General] irrelephant:
I have the bad one and only gfree would root it the first time... But since then I've unrooted and rooted using many methods to help ppl troubleshoot
[myTouch 4G General] saranhai:
few questions...

u mentioned that someone had an unrooted MT4G but had the M4G2DE chip and the phone still died?

also, u said M4G2DE users cudnt use the root.sh using VISIONary+ method.. i cudnt root it that way.. so wuz it becuz of my chip?
[myTouch 4G General] damnoregonian:
tbolt uses the 8GB variant of the SEM04G (SEM08G)

1) i believe the problem to be related to the write hardware itself (the dc/dc converter for the flash writing voltage [typically 15-30 volts, when the chip runs at 3.3]) since any and all write attempts to the emmc cause the chip to lock hard.

2) in the g2/dz world (as well as what i've dealt with from the dhd guys), not a single SEM04G has failed yet. they've all been the funky chip.

3) i don't know exactly why, but i can speculate. i think most people use psneuter instead of rage to break into the phones these days (as all shipping firmwares are patched against rage now, making visionary non-functional for temp-root)
[myTouch 4G General] damnoregonian:
also, yes, the tbolt is SLC formatted.

i wonder if the M4 chip is...
[myTouch 4G General] irrompible:
Is there any known correlation to the manufacturing date of the phone and the emmc it comes with or is it pretty random? Mine is from january '11 and I have the bad chip. I'm reluctant to try a warranty exchange if they are putting the m4g2de into the majority of new phones.
[myTouch 4G General] lowandbehold:
My wife and I got ours in March and we both have the good chip.
[myTouch 4G General] saranhai:
hm.. wonder if HTCs having the good chips in the newer phones.. or is it just random?

i got mine in february, i got the bad one
[myTouch 4G General] vqt:
For mines in March. Bad chip. Working fine
[myTouch 4G General] saranhai:
hey guys wassup

so i got my replacement phone from t mobile today, n i checked my emmc chip n guess wat? its SEM04G WOOT!!

soo does this mean im safe to root and do all that fun stuff that killed my M4GDE chip phone from before?
[myTouch 4G General] Ace42:
Yeah your free to go on all the flash spree all day if you want to ;)
[myTouch 4G General] saranhai:
so that means that it has been confirmed that the issue happened becuz of the "bad" emmc chip dying?
[myTouch 4G General] BelowTheHeavens:
I got mine the day it came out and I have the good chip.

Sent from my HTC Glacier
[myTouch 4G General] Phateless:
My understanding is that the "good" chip is safe, HOWEVER, there's a correlation between gfree and failed chips. Every "bad" chip so far requires gfree to root, whereas the "good" chips root just fine with root.sh. Check the poll results.

So this doesn't mean that gfree causes the failures, but I would definitely use the root.sh method instead just to be on the safe side.

Correlation does not represent causation. Just because things are RELATED does not mean they are CAUSED BY each other.
[myTouch 4G General] lowandbehold:
I think the only reason there is a correlation between the recovery errors and the g-free method is because if you have the "bad" chip, you cannot root using any other method..until someone with the "good" chip has the same issues, I think it is safe to say it is the chip and not gfree.
[myTouch 4G General] aznprodgy:
mmcblk0: mmc0:0001 SEM04G 2.17 GiB

1st and only mytouch Ive had since purchase in December, rooted fine initially with both gfree and visionary
[myTouch 4G General] saranhai:
noob question but if i root with visionary can i still change my hboot to eng hboot?
[myTouch 4G General] Phateless:
Yup, that's what I've been saying.
[myTouch 4G General] Sproket123:
Used Visionary root.sh

have SEM04G 2.17G

eng_hboot (0.85.2007)

Root success and using CM7.0.3 build 85 nightly
[myTouch 4G General] acsi007:
Both methods root with visionary. You used gfree or root.sh.
[myTouch 4G General] mr mystery:
Rooting with visionary and root.sh changes your hboot to eng hboot.
[myTouch 4G General] aznprodgy:
I rooted with both gfree and root.sh. I tried root.sh method first and worked on the first try. about a week later I started off fresh on stock and then attempted the gfree method and worked on the first try also
[myTouch 4G General] saranhai:
rly? so if i do the root.sh way itll automatically change my hboot to eng hboot?

sweet
[myTouch 4G General] PD15IMG:
Yes Saranhai as I stated here before. But as you know the useless mod's nuked my posts even when it was informative to the users. But when you attempt the PermROOT (root.sh) and run the script in terminal first thing it does is disable the write protection and then engineering hboot (0.85.2007) is pushed though terminal on "/dev/block/mmcblk0p18".
[myTouch 4G General] mustk1ll20:
got mine in March and have the SEM04G. Rooted first try with gfree/root.sh
[myTouch 4G General] saranhai:
oh thanks man

dude ur awesome.. u actually read b4 posting :D

y do u keep getting banned...? O__o

probably gonna try to root my replacement MT4G after skool ends

tell u guys how it goes
[myTouch 4G General] aznprodgy:
I also have a replacement being shipped to me, should be here on monday...thanks for the advice (you know who you are lol ;)). will post results when it comes in
[myTouch 4G General] svan71:
It seems I cant find anyone else with this

:confused:

SEM08G 4.17 GIB

I just got this phone 2 days ago.
[myTouch 4G General] saranhai:
how do u have it show the #.## GIB? :confused:
[myTouch 4G General] crawler9:
adb shell cat /proc/kmsg | grep 'mmc0:0001'

while in recovery
[myTouch 4G General] saranhai:
oh... but u need root and a recovery image... lol
[myTouch 4G General] aznprodgy:
just got my replacement yesterday. SEM04G 2.17GIB....good chip!:D just rooted on the first try using root.sh method, a little skeptical to try gfree
[myTouch 4G General] acsi007:
clarkenick. Did you have to pay the insurance deductible? What was you shpiel on the phone to them?
[myTouch 4G General] aznprodgy:
nope I didnt have to pay anything because the phone would not turn on at all, shipping was included
[myTouch 4G General] saranhai:
whoa.. howd u get it to not turn on at all..?

i mite still have to pay..lol cuz my can still boot into recovery/hboot and stuff
[myTouch 4G General] dementor123:
Just thought I would mention this-

I got my replacement phone yesterday which is a M4G2DE and I couldn't root using SuperOneClick. SuperOneClick worked fine on my earlier phone which was SEM04G.
[myTouch 4G General] aznprodgy:
SuperOneClick? never heard of that one...do you have the HTC Glacier(US) or HTC Panache(CAN)?
[myTouch 4G General] dementor123:
MT4G aka Glacier
[myTouch 4G General] thepza:
where/when was replacement shipped from

chem.manish,

Where was your replacement phone shipped from? And when did it ship out?
[myTouch 4G General] irrompible:
Got my replacement today and it's the bad chip and bad screen. Sending it back and keep my good screen/bad chip phone.
[myTouch 4G General] silentsnow31802:
Mine has the "bad" chip but I dont remember how I rooted it. Should I unroot it and reroot it using the visionary method to make sure it does not die on me??

EDIT: I do not have the engineering bootloader. Does that mean I used the Gfree method? From my reading Visionary replaces your bootloader with the engineering one.
[myTouch 4G General] acsi007:
Visionary does no such thing. The grankin01 root thread has a root.sh file that you run and it puts you on hboot 085, and with visionary run after that, gives you root. The gfree method also uses visionary after, gives you root, but leaves you on hboot 086, and you have to do an added step if you wish to get the modified bootloader.
[myTouch 4G General] silentsnow31802:
Oh okay. So then I still have no idea how I rooted lol. I could have sworn I read that it replaced your bootloader in a previous post in this thread. Then again I could have read it wrong.
[myTouch 4G General] saranhai:
oh dang that sucks...

ive got the good chip, bad screen

but id take the good chip over the bad screen anyday lol
[myTouch 4G General] saranhai:
just wondering.. but who is the manufacturer of both the SEM04G and the M4G2DE chips?
[myTouch 4G General] mr mystery:
Ditto
[myTouch 4G General] umsteveo:
I have the "bad chip" and failed eMMC. Exchange shipped out today. Hope I don't get the bad screen and bad chip.

<6>[ 6.155303] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
[myTouch 4G General] mackster248:
So basically if you have the bad chip then you're basically one flash away from being bricked? Like you only have a limited amount of flashes before your chip gives out on you?
[myTouch 4G General] lowandbehold:
I don't think it is the flashing that causes the chip to go bad. There have been cases on here where it has happened on the first or second flash. And there have been cases where it didn't happen during a flash at all, the ROM they were running just went into a bootloop. I have probably read every post dealing with the subject and my take on it is that gfree corrupts the chip, and when the chip decides to fail, it fails.
[myTouch 4G General] TeeJay3800:
So there's never been a case of a bad eMMC failing after rooting with root.sh and Visionary? My impression was that a bad chip will likely eventually fail no matter what rooting method was used.