Related
I used visionary to temp root/root. followed all the instructions in visionary and terminal emulator. when I restarted the phone it showed S off, I went to visionary to perm root and it say's I have to temp root my phone?? I rooted my other mytouch 4g the same way and it worked so I don't know what's wrong Im pretty sure i'm not doing anything wrong
Once you get s off and boot up you don't have su permissions so you need to temproot and then permroot immediately after to complete the root process
Sent from my HTC Glacier using XDA App
I got S off, rebooted in the mode, did everything in terminal emulator and when i went to visionary to perm root it said i had to temp root my device first, when i try to temp root with visionary the program keeps flashing for a few minutes, then nothing... anything I can do with the S being off already? The "super user" program is in my programs already also... can't figure it out
King350z said:
I got S off, rebooted in the mode, did everything in terminal emulator and when i went to visionary to perm root it said i had to temp root my device first, when i try to temp root with visionary the program keeps flashing for a few minutes, then nothing... anything I can do with the S being off already? The "super user" program is in my programs already also... can't figure it out
Click to expand...
Click to collapse
When you try to use root access is it not allowing it? Open up something like root explorer that asks for root access and see if it works. If it does then it sounds like it worked.
No it's not even though I have S off and did all the commands in terminal, I tried using Rom Manager, Titanium etc.. other root programs it says I need to root my phone first...
King350z said:
No it's not even though I have S off and did all the commands in terminal, I tried using Rom Manager, Titanium etc.. other root programs it says I need to root my phone first...
Click to expand...
Click to collapse
Do you have the SuperUser icon?
bootloader? Here's the root guide
What bootloader do you have?
0.86.0000 seems to make some rooting methods difficult if not completely ineffective.
Follow these instructions:
http://forum.xda-developers.com/archive/index.php/t-995549.html
It was seamless for me.
**I am not responsible for any consequences of you playing with your phone.**
thepza said:
What bootloader do you have?
0.86.0000 seems to make some rooting methods difficult if not completely ineffective.
Follow these instructions:
http://forum.xda-developers.com/archive/index.php/t-995549.html
It was seamless for me.
**I am not responsible for any consequences of you playing with your phone.**
Click to expand...
Click to collapse
All phones come with the .86.xxxx bootloader, you cannot load the .85.xxxx bootloader to the phone till after one has rooted and s-off'd the phone.
as quoted from here
http://forum.xda-developers.com/showpost.php?p=14573409&postcount=15
there are two ways to root our phones.
1) root.sh, regardless of what VISIONary or root.sh package you use. This will only root phones with good eMMCs. If your phone doesn't root via this method, then you have a bad eMMC and shouldn't root your phone.
2) ./gfree, regardless of what VISIONary or ./gfree package you use. This will root your phone regardless if you have a good or bad chip. you are setting yourself up to be royally screwed down the road, if you use root.sh it fails multiple times. Then use ./gfree to root it.
you are correct in the assumption that ./gfree will root your phone no matter what. But it will brick you phone if you have a bad eMMC. It might not happen right away, it might not happen in a week, or a month. But it's coming. There are thousands of threads all over the webs of people with bricked phone who use ./gfree to root their devices with a bad eMMC. there are significantly less threads of people who use root.sh and have bricked their phones.
advising someone to use ./gfree after they've admitted that root.sh didn't work, multiple times, w/o a fair warning is ignorant and not really helping anyone. a rooted phone is nice, a bricked device is totally different....
Yes I do and s off, but no root access and visionary wont root it after I successfully temp rooted, then booted did terminal emulator, wen I went to perm root it said I had to temp root first
neidlinger said:
Do you have the SuperUser icon?
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
King350z said:
Yes I do and s off, but no root access and visionary wont root it after I successfully temp rooted, then booted did terminal emulator, wen I went to perm root it said I had to temp root first
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
settings > applications > all > search for super user > delete the icon > reboot the phone > try visionary again.
Try that, it should help.
neidlinger said:
1) root.sh, regardless of what VISIONary or root.sh package you use. This will only root phones with good eMMCs. If your phone doesn't root via this method, then you have a bad eMMC and shouldn't root your phone.
[/SIZE]
Click to expand...
Click to collapse
Not true. Visionary doesn't permaroot for all of the good eMMCs. Verify which eMMC you have. If you don't have ADB set up, then temp root (although you're having problems with that currently) and then in Terminal Emulator:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That will report out the name of the chip you have. SEM=good.
delete the icon or uninstall the program, then try to temp root again with visionary and go through the steps?
King350z said:
delete the icon or uninstall the program, then try to temp root again with visionary and go through the steps?
Click to expand...
Click to collapse
delete Super User from the Application menu, via the settings. Then try to temp root / perma root again.
thepza said:
Not true. Visionary doesn't permaroot for all of the good eMMCs. Verify which eMMC you have. If you don't have ADB set up, then temp root (although you're having problems with that currently) and then in Terminal Emulator:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That will report out the name of the chip you have. SEM=good.
Click to expand...
Click to collapse
you have no clue what i'm saying.
VISIONary will not perma root a phone at all. You must manually turn s-off. You need to do that one of two ways. Either with the root.sh or the ./gfree method. both of which use VISIONary in their independent process. root.sh will not root bad eMMC phones. ./gfree will root either or without a problem.
will try it thanks, I don't know if it makes a diff but wheni open visionary now while temp rooting it just flashes for a few minutes?
neidlinger said:
delete Super User from the Application menu, via the settings. Then try to temp root / perma root again.
Click to expand...
Click to collapse
King350z said:
will try it thanks, I don't know if it makes a diff but wheni open visionary now while temp rooting it just flashes for a few minutes?
Click to expand...
Click to collapse
That's why i said earlier to reboot after you delete the superuser.apk. It will clean all of the current cache out.
Thank you for the help, will try it out when i get a chance later tonight or tomorrow, hope it works
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
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.
so...i finally got my phone rooted, i think. i used visionary after downgrading to 2.2.1, and i went into terminal, typed in su, and it gave me #. Just wondering, does this root stick? ie. if i start flashing, I'm not suddenly going to "lose root"...like is this as valid a root as using gfree?
regards
trev
rockr4Christ said:
so...i finally got my phone rooted, i think. i used visionary after downgrading to 2.2.1, and i went into terminal, typed in su, and it gave me #. Just wondering, does this root stick? ie. if i start flashing, I'm not suddenly going to "lose root"...like is this as valid a root as using gfree?
regards
trev
Click to expand...
Click to collapse
if you only used the visionary app to root and not root.sh or gfree, then yes, you will lose root after a reboot. this kind of root is called a TEMP ROOT and that is all visionary.apk can give you if you haven't acquire S-Off with either the root.sh or gfree method.
I used the perm root, and i have rebooted it twice, and still have root... thats why I'm asking .
I would check s-on, or s-off, but I can't get into recovery (shows little red triangle). Should i flash an engineering boot loader if Im just going to flash CWM anyways?
Regards
Trevor
Ps, thank you for patience and helping a self admitted n00b out
rockr4Christ said:
I used the perm root, and i have rebooted it twice, and still have root... thats why I'm asking .
I would check s-on, or s-off, but I can't get into recovery (shows little red triangle). Should i flash an engineering boot loader if Im just going to flash CWM anyways?
Regards
Trevor
Ps, thank you for patience and helping a self admitted n00b out
Click to expand...
Click to collapse
it shows if you have S-off in the bootloader
just power off your phone, and turn it on using the Power and Volume DOWN buttons.
IMO, i would flash the engineering bootloader, just to be on the safe side. who knows? someday it might save you
if i have helped, please hit thanks!
weird. i got it into hboot...and s'on. any ideas?
regards
trevor
rockr4Christ said:
weird. i got it into hboot...and s'on. any ideas?
regards
trevor
Click to expand...
Click to collapse
which method of perm root did you use? root.sh or gfree?
i did the visionary perm root. isn't that the root.sh? i followed the guide here on the forums..
trev
rockr4Christ said:
i did the visionary perm root. isn't that the root.sh? i followed the guide here on the forums..
trev
Click to expand...
Click to collapse
visionary and root.sh are two different things.
visionary only gives you root access while the root.sh script is the one that actually gives you the S-Off so that you can perm root.
here, try this link
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