i have a MT4G since the day it came out..i didnt know anything about rooting and stuff like that, until a friend told me about it so i came here. i didnt root my phone about 4 months after i got it. i did the visionary method and worked 1st shot thanx to mackster248. im really pissed right now. my sister just bought one a couple of days ago. well i just got done messing with the phone. and no luck..i did everything to the T. i was reading on a couple of forums about this. people have said there is different radios or some crap like that or a chip in the newer MT4G so.. i have no idea. i need help. she is complaining that the battery life sucks on it and i agree.. thats why i rooted mine. so i need help..
well there has been an issue going around lately with a bad eMMC chip, causing fail-pu errors or something of the sort. and there have been rumors of the newer mT4G's released with the bad chip, but not certain about that yet...
If your sister's phone is updated to Gingerbread - then you're out of luck. Might try Gingerbreak for temp-root instead of Visionary, maybe it'll help.
Here's a thread to watch:
http://forum.xda-developers.com/showthread.php?t=1101898
Jack_R1 said:
If your sister's phone is updated to Gingerbread - then you're out of luck. Might try Gingerbreak for temp-root instead of Visionary, maybe it'll help.
Here's a thread to watch:
http://forum.xda-developers.com/showthread.php?t=1101898
Click to expand...
Click to collapse
No she aint on gingerbread she's on 2.2.1 I was going to try the gfree method Idk
Sent from my HTC Vision using XDA Premium App
In that case, there are 2 options:
1) You're messing something up and not following directions 100% / the directions are missing steps.
2) You're trying root.sh method and your phone has a potentially bad eMMC chip, which is why it won't root. Following true S-OFF method with gfree (look in Developers section) will root you, but be warned - your eMMC chip might fail.
Jack_R1 said:
In that case, there are 2 options:
1) You're messing something up and not following directions 100% / the directions are missing steps.
2) You're trying root.sh method and your phone has a potentially bad eMMC chip, which is why it won't root. Following true S-OFF method with gfree (look in Developers section) will root you, but be warned - your eMMC chip might fail.
Click to expand...
Click to collapse
Ok what can I do about the bad emmc chip can i get a replacement phone.. and what happens when i do the gfree method with a bad emmc chip. I know for sure I'm not doing it wrong on doing it the same way I did my.phone and I did my.phone.first shot. But this was.months ago when I rooted my phone
Sent from my HTC Vision using XDA Premium App
concerning the bad eMMC chip, theres not much you can do about that right now. some members are working hard on it trying to figure things out. usually, gfree is the recommended method that works with phones with the bad chip. I would tell you to make a nandroid backup and flash the stock PD15IMG.zip, but seeing as you have the bad chip, I dont want to cause the chance of screwing anything up. you could try downloading the stock nandroid backup and restoring that through clockwork, then try rooting with gfree again. that might work...
This is second myTouch 4G that refuses to get S-OFF via root.sh method. I have a good chip and I followed all the steps entirely several times.
Some said that it is impossible with a good chip. What am I missing?
PS: I'm using the Unlockr guide
Which guide are you following and what exactly happens when you get through all the steps?
I was having the same problem for a long time with mine despite following every step word for word. Whenever I ran root.sh it would only run for like 4 or 5 seconds and then stop itself, rather than the 20-30 seconds that most people seem to say is the usual. After like 20 failed attempts I decided to get rid of my soft root, redownload every file(including visionary) and try again and that seemed to work out for me.
Just saw your edit lol, try using this guide instead:
http://forum.xda-developers.com/showthread.php?t=858021
I feel like it gives pretty good directions. I'd also recommend redownloading your root.sh files from there as well. Perhaps a bad download left you with a dysfunctional script that won't root you properly.
AlanB412 said:
Which guide are you following and what exactly happens when you get through all the steps?
I was having the same problem for a long time with mine despite following every step word for word. Whenever I ran root.sh it would only run for like 4 or 5 seconds and then stop itself, rather than the 20-30 seconds that most people seem to say is the usual. After like 20 failed attempts I decided to get rid of my soft root, redownload every file(including visionary) and try again and that seemed to work out for me.
Click to expand...
Click to collapse
I use this one:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
And then Permroot steps.
It does it quick, and seem to finish without errors.
I just realized, I should've asked you this first because it makes a really big difference. Is your phone on Android 2.3.4 already? If you got the Gingerbread update from t-mobile there's currently no known way to get root.
The thread I linked you to will only work if your phone is still on Froyo
AlanB412 said:
I just realized, I should've asked you this first because it makes a really big difference. Is your phone on Android 2.3.4 already? If you got the Gingerbread update from t-mobile there's currently no known way to get root.
The thread I linked you to will only work if your phone is still on Froyo
Click to expand...
Click to collapse
Nah, Im on latest froyo. Terminal Emulator keeps giving exactly same error: insmod: init_module '/sdcard/root/wpx.ko' failed (function not implemented)
PS: Search seem getting into a dead end. I will probably use gfree again
If I remember correctly, that function not implemented message is supposed to show up when you do it properly. After you get that message you're supposed turn phone off, reboot into hboot and it should say S= Off. Then after that you just have to reboot your phone again, head into Visionary, temproot one more time, and then click attempt PermRoot. Once your phone reboots you should have root.
After you get that "function not implemented" message does hboot still say S= On?
AlanB412 said:
If I remember correctly, that function not implemented message is supposed to show up when you do it properly.
After you get that message does hboot still say S= On?
Click to expand...
Click to collapse
yeap. I just went and did it with gfree. Is it true that gfree causing eMMC to fail? I saw it somewhere in the forum
AntonJart said:
yeap. I just went and did it with gfree. Is it true that gfree causing eMMC to fail? I saw it somewhere in the forum
Click to expand...
Click to collapse
Well I guess that works out for you then. As long as you have the good emmc chip you don't need to worry about the chip failure. Gfree can cause the chip failure for people with the bad chip though.
To revert back to stock after using the gfree method is a bit more annoying than usual though, regardless of what chip you have, because it does something to your radio in order to give you the permaroot. So if you ever do decide to unroot you'll have to take some extra steps to undo the gfree changes.
But that's only a problem if you want to unroot though lol
AlanB412 said:
Well I guess that works out for you then. As long as you have the good emmc chip you don't need to worry about the chip failure. Gfree can cause the chip failure for people with the bad chip though.
To revert back to stock after using the gfree method is a bit more annoying than usual though, regardless of what chip you have, because it does something to your radio in order to give you the permaroot. So if you ever do decide to unroot you'll have to take some extra steps to undo the gfree changes.
But that's only a problem if you want to unroot though lol
Click to expand...
Click to collapse
On the first mytouch unrooting was quite easy. I recovered the back up (s-off still stayed) and then applied stock image. Thanks for your replies
i just sucesfully performed a visionary permanent root on a friends mytouch 4g...now how do i unlock it from here?
i have read on a method call gfree... can i use that method ontop of visionary root i just did or is there another way?
Can't root 2.3.4 but here is an alternative - xda-developers http://bit.ly/oO3CNf
no the device is at 2.2.1
xsessive said:
no the device is at 2.2.1
Click to expand...
Click to collapse
Visionary is just a tool to gain SU access on the phone. Since these devices have a locked bootloader you must take extra steps to unlock that bootloader. That is what we refer to when you see s-on/s-off. ./gfree will turn that security protocol off (s-off). However these phones have a know problematic chipset and a known less bothersome chip set. I would read though the "post your eMMC serial number" to see which one you have/your buddy has. If it's a know "better one" then you can proceed with caution. If it's a known problematic one i would proceed with EXTREME caution almost to the point of not rooting the phone. Either chip has failed but it's happened less time with the good chip. Either way you can find a method to turn off security protocol in my signature.
I got the sdcard update but s-off still but visionary loads black screen but with. 2 .3.4 and s-off should it work
neidlinger said:
Visionary is just a tool to gain SU access on the phone. Since these devices have a locked bootloader you must take extra steps to unlock that bootloader. That is what we refer to when you see s-on/s-off. ./gfree will turn that security protocol off (s-off). However these phones have a know problematic chipset and a known less bothersome chip set. I would read though the "post your eMMC serial number" to see which one you have/your buddy has. If it's a know "better one" then you can proceed with caution. If it's a known problematic one i would proceed with EXTREME caution almost to the point of not rooting the phone. Either chip has failed but it's happened less time with the good chip. Either way you can find a method to turn off security protocol in my signature.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
Okay, here is the deal. I was trying to change around some stuff on my phone, the IMEI number to match the one on my prepaid tracphone. So far, before I changed the IMEI, i had it rooted and everything was slamming. But it would disconnect me after about a half hour. I am changing the IMEI to see if it fixes this, but after all this I had to revert back to a total stock flash of 2.2.1 HTC rom, it updated everything, one of those PBxx.img ones you do during the bootloader.
So now I've rooted it with visionary, and it hardly works, won't permaroot, but I get regular root. So I did another method on a wiki and have permaroot now. Updated SU, clockwork mod, ETC and everything works (well it installs and prompts me to give super user access then doesnt complain.)
HERE IS THE PROBLEM: I CANT CHANGE RECOVERY OR BOOTLOADER TO S-OFF
I have used gfree (multiple versions) to turn s off, and turn off all locks and to change the bootloader the nb0 one. BUT NOTHING gives.
>Clockworkmod from the rooted main screen, when i open the app, it won't install the clockwork mod recovery.
>When booting to recovery, the phone goes to stock recovery with the red triangle and phone. Upon where you have to push VOL UP + PWR button to see any options, and they are just the stock ones, (reboot, apply update:sdcard, etc)
I was wondering if someone had a signed image that they could link to me or send or whatever that has the s-off in a format that I can use with the BOOTLOADER; i.e.: Just put it on SD-CARD, hold "VOL UP+PWR" then it will do the update. U know, like radios are flashed.
If you can help me please, help me. I was so excited with this phone and moving along and now this.... ARG! lol. Thanks guys any and all input is appreciated no matter how irrelevant!
peace
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010,11:12:59
You don't have perm-root.
Gfree can't work without root. Since you don't have perm-root without Gfree, you need temp-root.
While not S-OFF, you can't have perm-root. Period. End of story. Temp-root and execute Gfree.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
help.. tried root explorer, astro, es file..and have had no luck flashing to better roms...help
Sent from my HTC Glacier using XDA Premium App
If you are using Visionary R14, try R11. And f*ck wiki.
Jack_R1 said:
You don't have perm-root.
Gfree can't work without perm-root.
While not S-OFF, you can't have perm-root. Period. End of story.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
Click to expand...
Click to collapse
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
lowandbehold said:
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
Click to expand...
Click to collapse
I guess I wasn't clear enough in my response above, and wrote "perm-root" where just "root" was in order. Edited.
In any case, when was the last time you've read the Wiki? I suggest you look at it again.
I don't know if I am explaining correctly.
I applied the root method using visionary r14 because thats the latest from the site, it temp roots, but does not perma root.
I did a su, and got root, but I have to SU before i get root, it asks for SU permissions and I allow and I have root. (all this is done in a shell). So I know I have root, i can open up the system to read write and even delete some stock .apk and other files that aren't supposed to be deleted. So its all good. I can chmod 777, i know whats up there.
I did all this madness, SU updates to the most current binary, clockwordmod both an older and the newest version open, ask for and allow SU permission, and all that appears to work fine. EVEN with the friggen flash clockworkmod recovery, it says current recovery: clockworkmod x.x.x.x (meaning whatever the version is, tried a bunch).
BUT WHEN I BOOT TO RECOVERY OR BOOTLOADER, S-ON and friggen stock recovery for me. WHAT THE heck. its like its ignoring what I do to flash the bootloader.
Does anyone have a PBxx.IMG they can send, hopefully signed, that I can just use to update? or link to one? also, and update.zip for the stock recovery would work too.
HERE's the thing, its a T-mobile phone, and my TRACPHONE Prepaid sim works on it, but that *MIGHT* just be because TRACFONE = AT&T also T-Mobile=AT&T now also.
But I think the sim is unlocked, I'm waiting on other sim to come in the mail before I can verify for sure.
MAIN thing i need is a signed (or I'll even play with an unsigned) PBXX.img file for either the bootloader or recovery, or an update.zip one. At this point, if you have a lower version of 2.2.1 that has the whole entire shebang, (the radio, bootloader, os, recovery, etc) then I'll appreciate that too.
I just can't find it on here after days of searching and I am needing a push in the right direction. And google's overloaded with the SAME article just in different spam blog formats. Thx guyz
You CAN'T.
Everything you do when you're temp-rooted, DOESN'T GO TO THE eMMC! It stays in memory (eMMC cache), and the next time you reboot - everything is GONE. All your file deletions, chmods, etc - they're NOT REALLY EXECUTED. Reboot and see for yourself.
The only thing that will make it stay - is running gfree and gaining S-OFF.
The link, as everything else you're looking for, is in Wiki. Look in the Downgrade guide, there's a link for 2.2.1 RUU for MT4G. But it won't help you - you're just being stubborn and unwilling to read. YOU DIDN'T EXECUTE PERMAROOT PROPERLY, AND UNTIL YOU DO - YOU WON'T BE ABLE TO FLASH A DAMN THING.
The Wiki links to a Gfree method guide. Read it and execute it STEP BY STEP.
Okay, i did it
Here is what I did. I went in manually and copied the .nb0 to the file several times in a row.
Visionary does not work, the only way I can root this thing, without some type of temproot visionary app that messes up, is this way:
http://wiki.rootzwiki.com/index.php/HTC_myTouch_4G
Also, I am hoping I am correct, but this is how its laid out in the /dev block...
mmcblk0p18: HBOOT DATA (bits) And....
mmcblk0p21: RECOVERY DATA (bits) data or bits, whatever you want to call it. (its not a file)
Okay. So with that being said;
/dev/block/mmcblk0p18 = hboot 'file' and this is what i did.
Using 'dd' which is a unix command that just does low level convert and copy, will take the input file if=hboot_hacked_file.nb0 and then put it to the output device converting it and whatnot, the output file of=/dev/block/device
so it looks like this in example:
Code:
# dd if=/directory/filename.xxx of=/dev/block/output_device_or_file
Oh, and another thing that might just be paranoia... The wifi was on and it wasn't doing what it was supposed to do, I noticed it also being active unusually, I should have put wireshark on and checked it out, but didn't think about it at the time. Now that wifi off, it feels as if its fine now. It was almost like another user was in it. But thats probably just paranoia..... or the t-mob trying to mess me around!!!
This IS the gfree method, and you ARE running an app to gain temp-root there.
Copying the bootloader didn't help you at all, it was only a later step. It wouldn't stick if not for gfree.
Running gfree did.
Oh well, I guess that it's useless to explain. Glad it worked.
naw bro, its good that you explain what you mean, its not useless to explain anything. Here is what I'm saying... gfree -f is supposed to do the S-OFF right? well, it didn't. it also said failed or error or something at the end. Once I did the 'dd' command not just once, but several times and VERIFIED that it was working and different, while having # then I ran gfree again and it said SUCCESS at the bottom and THAT did it bro. SO that, in the end, turned my s-off and gfree unlocked my sim super unlock and cid unlock too.
I've cloned my IMEI because its legal, its my own phone and I'm not doing anything extra other than using it to make calls which I pay for at outrageous prepaid prices.
Does anyone know where that information is located by the way, just for information purposes... I've already done it using a hex editor and a part7.bin file... but I just am not quite sure on EXACTLY what I've done. like, the locations of what file or data that i've flashed. With CDMA, I usually enter QPST programming and all that and just just play till my heart's content... but now I'm trying to learn GSM and I want to know if there is a way to enter that kind of programming also. Or are us fellas forced to dump .bin files, hex edit, then reflash or reflex em...
Just lookin for some pushes in the right direction for programming in the GSM area.
Also if you have links to radios, all of them, previous and what not, I would appreciate it too
Flashing hboot, superuser or not, several times or not, didn't do a thing for unlocking.
For what reason gfree failed initially - I don't know, but when you ran it again and it didn't fail - that did it all. Otherwise you'd still be with S-ON, and the bootloader would still be the same.
You can't really argue against HW. That's how it works.
Radios are here:
http://forum.xda-developers.com/forumdisplay.php?f=796
Look for "Glacier Radios" sticky.
Like I said before as well. There are alot of issues with R14...find and use visionary R11. You are not the first person to have issues with visionary, and with the majority of them, the downgrade solved the problem.
Not true
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
ahernandez646 said:
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
Click to expand...
Click to collapse
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Skipjacks said:
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Click to expand...
Click to collapse
No, that's the froyo bootloader.
What happened when you ran visionary? Did you have usb debugging checked? Sometimes the temp root works on the first try, sometimes on the tenth. If it doesn't work, reboot and try again. If it still doesn't work after several attempts do a factory reset and try again. Sometimes a clean slate helps.
Sent from my HTC Glacier using XDA App
i do have 2.2.1 but i had a mytouch 3g slide and i root it. but for some reason i can't get the mytouch 4g to do it. i will re-try everything again.
Thanks to all that have reply.
I today got my MT4G replaced. It bricked because of that eMMC chip issue. I must carrier unlock it to use it. Now to that one of the options is to root and get the S-OFF.
But, I am worried about the same thing happening again. What will happen if it again becomes a paper weight? Should I use unlockyourphone.com or something?
Plus, it has 2.3.4 preinstalled. so is it possible to root it or do I need to downgrade?
Please check here to determine your eMMC chip type and only if you have the good chipset, will you be alright to root without fear of a brick.
Why pay for someone to unlock your phone when you can do it in 20 minutes even if u have to set-up ADB...?
You will have to downgrade first to Froyo, yes.
**********But first check the link to see what chipset you have***********
And even if you have the "bad" chipset - it'll still be better to root and unlock. Only a small percentage of "bad" chips are actually bad and prone to failure.
Ok. I have a bad chip even after the replacement. wat to do now?
sagarparmar said:
Ok. I have a bad chip even after the replacement. wat to do now?
Click to expand...
Click to collapse
up to you. We cannot answer that. If you do everything correctly you shouldn't have a problem. but if you want to play it safe. get accustom to Espresso.
Don't worry too much about bad emmc chips. not all "bad" chips are bad. it simply means there is a higher chance of you getting a bad uhh phone. But most "bad" chips are able to flash perfectly fine.
Both good and bad chips have been known to brick, but the bad one is slightly more susceptible to bricking.
Mine is bad and I've been flashing non stop since Michael Jackson was still bad
Sent from my HTC Glacier using XDA App
Haha
And one more thing, are there any cases where non-rooted phones also got bricked?
Let's say, I get PIN for unlocking and then it bricks. Is it safe to even own MT4G? I am more worried because I am using it outside the states. If I were a tmo customer, I could always get a replacement.
Bricking should be very rare for stock phones. The only way I can think to brick would be to pull the battery during an OTA update.
Sent from my HTC Glacier using xda premium
I only want Sim unlock. I can do it via gfree. So here is what I am thinking.
First gain temp root with visionary and then push gfree (Follow 9 steps as per guide.) Any idea if ./gfree -f is required? Because I only want sim unlock(without root / s-off), I want to run ./gfree -S directly. Is this possible?
I am currently on 2.3.4 stock image. I will have to downgrade to 2.2 and follow the guide. But will I be able to again update to 2.3.4? Will lose the sim unlock?
THANKS IN ADV
sagarparmar said:
I only want Sim unlock. I can do it via gfree. So here is what I am thinking.
First gain temp root with visionary and then push gfree (Follow 9 steps as per guide.) Any idea if ./gfree -f is required? Because I only want sim unlock(without root / s-off), I want to run ./gfree -S directly. Is this possible?
I am currently on 2.3.4 stock image. I will have to downgrade to 2.2 and follow the guide. But will I be able to again update to 2.3.4? Will lose the sim unlock?
THANKS IN ADV
Click to expand...
Click to collapse
I do believe that that is possible. When I first did got root I used the root.sh method not the gfree method. Afterward I wanted to be able to Sim Unlock too. So a few months ago I did the gfree -S and my phone was fine. Granted I already had root, but I don't think that should be an issue. Also, back up your sd card first. Not sure why, but when I did the gfree it borked my sd card. I wasn't able to restore to my previous backup. I had to start over and reformat my sd.
Lol! Just realized I thanked your post while my computer was being a slow PoS!
I thanked your post and my PC was working fine