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...
Related
Hi !
I would like to warn everybody that the use of the permanent root option of visionary can lead to an unrecoverable brick!
Lately we are facing an increasing number of bricked phones that have been created by an attempt to permanent root the G2 (or Desire Z) using visionary.
While there is still cure for Desire Z phones (even if it is a complicated procedure) there are certain conditions for the G2 where nothing can be done to rescue the phone.
These are the conditions:
- the phone is S-ON and not SuperCID
- the hboot and the recovery are still stock
- the main software version is 1.22
When visionary corrupts the system partition (which it does some times) the phone can not boot anymore. And as there is no original stock rom (PC10IMG.zip) for the G2 that has software version 1.22 or higher the stock rom can not be installed from hboot.
And with the stock recovery there is also no chance to cure the system partition or change the main version in the misc partition.
But even if the brick can be cured for other phones (Desire Z, Desire HD) this is totally unnecessary because the phones can be rooted and freed by methods that do not have any risk at all (even if you do some steps wrong).
The method that I highly recommend to use is the one described on the XDA-wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD.
This method is constantly maintained and is the most up to date method.
If you really are not able or willing to use adb I would recommend the method described by ianmcquinn in the thread "[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)" at http://forum.xda-developers.com/showthread.php?t=928160
It is less up to date but it uses visionary only to gain temporary root and it uses scripts for the necessary commands so that the risk of bricking the phone by typos in important commands is minimized.
Scotty2 and I (and a lot of other people) tried our best to make the rooting process as easy and risk less as possible and therefore it is very frustrating to see people who bricked their phones by using an unnecessary, outdated and risky method.
Thanks and have fun - Guhl
Update 05/15/2011:
Since football dropped the new gingerbread T-Mobile ROM (see http://forum.xda-developers.com/showthread.php?t=1074391) a G2 bricked by visionary can be cured. (which is a complicated procedure of course)
I think this is/should already stickied however no one seems to read stickies... Thanks for posting the warning again though.
Sent from my HTC Vision using XDA App
On my first G2 I used the visionary method and it messed up after about 2 weeks.
It wouldn't connect to the wireless network.
On my second G2 I used the gfree/rage method and, it has worked just fine.
I'm sure with all the visionary problems people are having, it probably had something to do with mine going bad.
I am waiting on an insurance replacement G2, glad I found this. I rooted mine the very first method that was posted. So does Visionary have a checkbox in the app or something to permanent root? I was using the first release of it.
:edit Just got my G2 from UPS at 1:20, and now at 1:50 I am already flashing CM7 Visionary is great, glad I saw not to do Perm Root attempt though haha
dumb? question
i rooted my g2 a few weeks back, installed the cyanogenmod 7(which seems solid btw) & honestly dont remember the method i used (it took multiple tries over multiple posts/guides/websites) but i recall visionary was involved at some point.
anyhow should i be worried about this thing becoming useless? should i be reinstalling/uninstalling something? are there any precautions i should be taking? is there a way to tell what method i used?
sorry if im cluttering this thread up, i really try not to post if possible(searching usually answers my dumb questions) THANKS! tho
If you're already rooted you should be good. The method that uses VISIONary/Gfree was posted in January, the latest thing that said it could cause any problems was an update on December 23rd, and from what I understand is that you'd have to downgrade a Desire Z... Didn't say anything about a G2. I'm sitting here waiting for UPS then I'll be doing this.
hmm ok, thanks, ill continue to slowly set it up for use than & keep an eye out for additional posts/info on the subject. i sure would hate to doorstop the thing before even using it.
thanks again for the reply
The only issue I've encountered with the way I did was that it says phone number unknown. Quick xda search found you go into Call settings, additional settings, and you can set the phone number in there
Well, I used the Visionary + gfree way to permanent root today, and it went smoothly, on the 1st try, no problems, as of yet. I ran root check and noticed that busybox isn't installed. Is it supposed to be? It was when I was using temp root. Is it ok, to install busybox from the app from the Market?
I got busy box through titanium backup "problems" button
Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Thank you!
one2345shutup said:
Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Click to expand...
Click to collapse
It should be no problem to root your phone on a Mac. The guide to setting up adb in my signature has a section on how to do so on a Mac.
I perm rooted with visionary method the day it came out (I think this was November or October?). Was on cm 6 and now been on cm 7 for a while. No issues at all. Guess I was lucky or people are doing it without being careful.
My friend's G2 seems to be bricked under these conditions. Failed Visionary root. He's counting on me to fix it.
The recovery is stock and it has S-ON. How can I check the version?
Electrodeath0 said:
How can I check the version?
Click to expand...
Click to collapse
You can't.
Just try to install the 1.19 PC10IMG.zip using hboot and you will see. If it installs you'r good if it tells you that you version is to high you are 1.22
Sent from my HTC Vision using XDA App
Whats up everyone?
OK real quick because this has had a little more insight to my situation than what i have been able to find. a guy called me up yesterday and wanted to know if i could root his g2. well apparently.... he attempted to do this on his own and used visionary and messed up his phone. bootscreen heaven. stuck on htc.
Hboot. 0.82.0
radio 26.03.02.26
SHIP S- ON
I have no control over adb.... says device is offline but at least recognized. and shows devid. is this phone a lost cause or can someone toss me a bone without telling me to read this and go here or there?
i have been searching since 5pm yesterday and it is now 1030am.
I have been able to load an update through the stock recovery and it shows that it went well. when it reboots to the screen with the grean circle arrows over the phone, it doesnt seem to take enought time to be loading image or other software. and when its done and reboots, its still stuck on htc screen.
any help would be greatly appreciated and sorry if i cluttered up this thread.
RELEVANCE::::: Visionary
SErooted,
Xperia X10
2.2 Xperia BLISS
2gig data2sd
998mhz
sysctl
2780 Quad
Wish i would have read this 3 hours ago.Tried to perm-root with vision bout 4 months ago and didnt brick, But 3 hours ago tried it again and i semi bricked/bricked it?
This blows i already miss my android .This is definitley a FML post
FMLLLLL!
well new g2x or just a New G2 here i come
I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%
Rooting a new G2
wrong post, mods please delete
I AM VS4 said:
I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%
Click to expand...
Click to collapse
If you used Visionary, and it worked, then you don't need to worry about unrooting and rooting again. If there were going to be any problems, it would have happened as you were rooting. If you didn't run gfree, and are not Super-CID, S-Off, then you might want to do that (you still can). But otherwise, you are good to go.
So, I tried to read up on how to start rooting my mytouch.
I see these options:
1. TRUE PermaRoot and the ULTIMATE S=Off!!! Check this out even if you're rooted!!! (Posted By grankin01)
2. Guide to permaroot, s=off AND s=on!!!!! (Posted By grankin01)
3. VISIONary+ permaroots MT4G (Posted By allen099)
4. [GUIDE] How to s= off with "su" and how to flash rom---Noob's (Posted By topgun303)
I'm not understanding how or why there are 4 ways when clearly, from my reading, there are people who say "gfree" (whichever that is) is not the preferred method?
This is confusing, isn't it? I can't be the only one confused by this??
tinpanalley said:
So, I tried to read up on how to start rooting my mytouch.
I see these options:
1. TRUE PermaRoot and the ULTIMATE S=Off!!! Check this out even if you're rooted!!! (Posted By grankin01)
2. Guide to permaroot, s=off AND s=on!!!!! (Posted By grankin01)
3. VISIONary+ permaroots MT4G (Posted By allen099)
4. [GUIDE] How to s= off with "su" and how to flash rom---Noob's (Posted By topgun303)
I'm not understanding how or why there are 4 ways when clearly, from my reading, there are people who say "gfree" (whichever that is) is not the preferred method?
This is confusing, isn't it? I can't be the only one confused by this??
Click to expand...
Click to collapse
There are only one method to root our phones. VISIONary.apk. That is the only rooting tool we have.
People feel they need to re-post what has already been posted several times. I know i am guilty of it as well, but here is the short and sweet of it.
Now there are two different ways that turn the Security Protocol off. One is the ./gfree method, which can be found here http://bit.ly/rm19ii. And the root.sh method, which can be found here http://bit.ly/nC4zmL.
now with that being said our phones have two eMMC chipsets in them. One is a known good one, and one is a known bad one. The root.sh method will only root phones with good eMMC chips. so if you try that one and it fails. Either one of two things are going on. 1) you are doing it wrong or 2) you have a bad eMMC. If you use the ./gfree method it will root the phone regardless of the eMMC chip. That is why they say the root.sh is the "preferred method". It will not mess up your phone. A rooted phone with a bad eMMC chip is bound to go bad, don't know when, nor do we know how it will go. But it's going to go.....
Wow, in just a few sentences you cleared up pages and pages and pages and posts of confusion. Thank you SO MUCH. Maybe I'm just an idiot but I wasn't understanding it at all.
Ok, my next questions are...
1. What is accomplished when you "turn the Security Protocol off"?
2. How do I know which eMMC chipset I have? I rooted my mytouch 4G months ago and can't remember the process I used. How can I tell which one I did? Although I don't think I did anything with security protocols?
tinpanalley said:
Wow, in just a few sentences you cleared up pages and pages and pages and posts of confusion. Thank you SO MUCH. Maybe I'm just an idiot but I wasn't understanding it at all.
Ok, my next questions are...
1. What is accomplished when you "turn the Security Protocol off"?
2. a) How do I know which eMMC chipset I have? I rooted my mytouch 4G months ago and can't remember the process I used. 2b) How can I tell which one I did? Although I don't think I did anything with security protocols?
Click to expand...
Click to collapse
1) that is turning the s-on to s-off .
2a) http://bit.ly/nDEuuP That thread has alot of useful information in it.
2b) Given you haven't reformatted your card since you rooted your phone. If you used the ./gfree method you should have a file on your SDCard that looks unfamiliar. "Part7_something". If you have that, and have never reformatted your SDCard then you used ./gfree. If you don't have anything then chances are you've used the root.sh method. But i cannot answer your question honestly since it's nearly impossible for me to know how you rooted your phone
1. If I don't deal with security protocol, and ONLY worry about rooting my phone to get a ROM on there, can I address it after rooting?
2. Ok, I DO have that part7backup file on my sd card. Therefore, I must have done the gfree method and therefore I might have a bad eMMC but we can't be sure, correct? Ok, well in that case should I re-root (if that's even possible) my phone with the root.sh method?
3. The whole security protocol on or off controls the ability to unlock your phone for use with any SIM card correct? Anything else it does?
I was once confused as weel but i used gfree because it was the only way i could root because of the 86 bootloader. but the reason gfree is not preferred is because of the root.sh file
tinpanalley said:
So, I tried to read up on how to start rooting my mytouch.
I see these options:
1. TRUE PermaRoot and the ULTIMATE S=Off!!! Check this out even if you're rooted!!! (Posted By grankin01)
2. Guide to permaroot, s=off AND s=on!!!!! (Posted By grankin01)
3. VISIONary+ permaroots MT4G (Posted By allen099)
4. [GUIDE] How to s= off with "su" and how to flash rom---Noob's (Posted By topgun303)
I'm not understanding how or why there are 4 ways when clearly, from my reading, there are people who say "gfree" (whichever that is) is not the preferred method?
This is confusing, isn't it? I can't be the only one confused by this??
Click to expand...
Click to collapse
tinpanalley said:
1. If I don't deal with security protocol, and ONLY worry about rooting my phone to get a ROM on there, can I address it after rooting?
If you did the ./gfree method you did infact truly root your phone. You have to turn that off prior to flashing anything.
2. Ok, I DO have that part7backup file on my sd card. Therefore, I must have done the gfree method and therefore I might have a bad eMMC but we can't be sure, correct? Ok, well in that case should I re-root (if that's even possible) my phone with the root.sh method?
1) unrooting and rerooting with root.sh will not change the fact that you might have bad eMMC chip. Those are bad regardless of the rooting method you used. And i posted a link to tell you how to verify if you have a bad chip. Or you can look for the "post your eMMC serial number" in the General Section
3. The whole security protocol on or off controls the ability to unlock your phone for use with any SIM card correct? Anything else it does?
The Security Protocol is the control that allow your phone to say in the rooted mode. It has nothing todo with the SIM lock on the phone.
Click to expand...
Click to collapse
all of my answer and in blue and bold.
"unrooting and rerooting with root.sh will not change the fact that you might have bad eMMC chip."
Ok, I was under the mistaken impression that doing it the wrong way could somehow ruin the chip later on.
"It has nothing todo with the SIM lock on the phone."
I thought I had read in one of the instructions that this also unlocked the phone. So I guess SIM unlocking is a whole other process then?
tinpanalley said:
"unrooting and rerooting with root.sh will not change the fact that you might have bad eMMC chip."
Ok, I was under the mistaken impression that doing it the wrong way could somehow ruin the chip later on.
"It has nothing todo with the SIM lock on the phone."
I thought I had read in one of the instructions that this also unlocked the phone. So I guess SIM unlocking is a whole other process then?
Click to expand...
Click to collapse
one of the fringe benefits of the ./gfree method is a CID unlock but it's not synonymous with rooting phones
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 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
I just read a thread about eMMC chips and I'm nervous now. Apparently I have the bad M4g 2.10 GiB chip. It was said that this chip can die with gfree root, causing bricked phones. I'm kind of confused as to what method I used though. (yes I know, I'm kind of nooby ) I reviewed what I did using the wiki http://forum.xda-developers.com/wiki/HTC_Glacier
I used visionary. In the wiki sections it shows two methods. Root.sh and gfree. Now I've check threads for both and some for both required visionary. I'm pretty sure I used gfree, but that only gave me s-off. Not root.
I've searched a lot of this stuff but im pretty confused. People are saying you dont have to be rooted or anything for your phone to get bricked from the bad eMMC. Its just a hardware problem. People are also saying the "good" chip can also die like the "bad" one. And then some people say its only if you have the bad one AND you've rooted using gfree.
Thnx for the info
Gfree and visionary are 2 different root methods. In my opinion bad ships dying because of rooting is a myth to me. I've rooted 5 mt4g with bad ships and they all still running great, well except my girls mt4g. That one I ran over with my car lol. Reason for ships dying, I believe is user error. So read, read and read some more, comprehand what you're doing then do it and take your time doing it and you should be OK.
I've used visionary root.she method to root all the mt4g I've rooted.
for the sake of safety though, I believe in it, as I am 15, and don't have the money to replace it myself lol. So are there 3 methods? root.sh, visionary AND gfree? root.sh wouldn't work because of my chip. It stayed s-on no matter what. so I did gfree to s-off and then visionary to root apparently. I'm not sure
And Im hoping theres a case of this happening with unrooted phones. That way I can blame t-mobile for bad hardware, but I'm probably gonna have to change my boot animation and splash screen back to stock if i want it took look real.
tradejak66 said:
for the sake of safety though, I believe in it, as I am 15, and don't have the money to replace it myself lol. So are there 3 methods? root.sh, visionary AND gfree? root.sh wouldn't work because of my chip. It stayed s-on no matter what. so I did gfree to s-off and then visionary to root apparently. I'm not sure
And Im hoping theres a case of this happening with unrooted phones. That way I can blame t-mobile for bad hardware, but I'm probably gonna have to change my boot animation and splash screen back to stock if i want it took look real.
Click to expand...
Click to collapse
There are actually three...
Official HTC Unlock
Root.sh
Gfree
VISIONSARY isn't a perm root method, its only a TEMP root.
Sent from my Infernalized Glacier!
-Team Inferno
From what I hear all bad chips die early regardless of the phone being rooted or not. Just root via visionary and enjoy awesome roms until your phone dies...
Sent from my HTC Glacier using XDA App
saranhai said:
VISIONSARY isn't a perm root method, its only a TEMP root.
Click to expand...
Click to collapse
That's not really true. After you've temp rooted via Visionary, you run the root.sh script, and then use Visionary again to perm root. Selecting "perm root" in Visionary is the last step which completes the rooting process.
tradejak66 said:
So are there 3 methods? root.sh, visionary AND gfree? root.sh wouldn't work because of my chip.
Click to expand...
Click to collapse
"Visionary method" and "root.sh method" are referring to the same thing. That method uses both the script and the app to perm root the device.
TeeJay3800 said:
That's not really true. After you've temp rooted via Visionary, you run the root.sh script, and then use Visionary again to perm root. Selecting "perm root" in Visionary is the last step which completes the rooting process.
"Visionary method" and "root.sh method" are referring to the same thing. That method uses both the script and the app to perm root the device.
Click to expand...
Click to collapse
+1 this visionary and root.sh work hand in hand.
cjwebb said:
From what I hear all bad chips die early regardless of the phone being rooted or not. Just root via visionary and enjoy awesome roms until your phone dies...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Like I stated on my first post. All 4 mt4g I rooted all have bad ships. They are all over a year being rooted. All going strong.
saranhai said:
There are actually three...
Official HTC Unlock
Root.sh
Gfree
VISIONSARY isn't a perm root method, its only a TEMP root.
Sent from my Infernalized Glacier!
-Team Inferno
Click to expand...
Click to collapse
Visionary has option to perm root, and I used that as instructed.
TeeJay3800 said:
"Visionary method" and "root.sh method" are referring to the same thing. That method uses both the script and the app to perm root the device.
Click to expand...
Click to collapse
OK i used this method http://forum.xda-developers.com/showthread.php?t=858996. Is this gfree or root.sh since it uses visionary?
When I tried root.sh myself manually my phone stayed s-on. So I'm assuming this is gfree cause it worked.
Yes, obviously, if you had to execute "gfree something" - it's gfree.
That's definitely gfree. I used the 2 steps below to root all the devices I've rooted. All within the device, no PC needed. It took me about 10 to 15 minutes the first time doing it.
STEP 1
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
STEP 2
http://theunlockr.com/2010/12/10/ho...s-off-on-the-t-mobile-mytouch-4g-htc-glacier/
I believe the current consensus is that it doesn't matter which method you use to root. It has more to do with the amount of flashing you do. The "bad" chip seems to fail more often. How many it can handle varies wildly between phones. The "good"chip has been known to fail, though rarely. Bottom line is that flashing is a risk, but the reward is often worth it. Are you feeling lucky?
Sent from my HTC Glacier using Tapatalk