Hello there fellow Glacier owners.
Let me start off by saying I have rooted 2 Glaciers very recently, and I am very familiar with the process. One of them was swapped at the store because I had one of the Taiwanese screens, and it was driving me nuts. I have been trying to root the new one.
I've gone through the gfree, adb, and Visionary+ methods already, and now an issue has cropped up.
Now, when I run Visionary, pop open the terminal, and type 'su' I get an 'unknown user root' error.
When I try to use the adb/gfree method and run 'rage', I now get a 'rage: applet not found' error.
During my previous attempt, I did not get this error. I have tried a reset to factory through stock hboot, I have tried loading the 2.2.1 PD15IMG.zip, through stock hboot (didn't help, wasn't expecting it to). I've even tried switching out and formatting mSD cards on the off chance it might help.
If anyone has any advice or help they can offer me, I would greatly appreciate it.
Thanks
Any way you can post a video of your step by step? I've always used grankin's guide and I've never had an issue, not once, on 6 HTC Glaciers.
Thus far, I've only seen a few reasons why people can't root their phone:
- They aren't on 2.2.1
- They didn't put files in the correct location/follow directions to the T
I don't think I've ever seen a legit, "your device is defective" post, but it's been suggested.
I use visionaryplus.r14.apk each time and my employee has rooted a handful of HTC Glaciers using the same.
I think a video would really help expose any possible oversights. It's either your steps or the device is just "bad" and I'm thinking video footage would help reveal which it is.
Here is a link to my video using the Visionary+ method. I can upload a video for the adb if you want as well.
www.youtube.com/watch?v=qb3HIvXiF74
Replace DOT with .
I should also note that I was able to run the 'su' command at one point successfully, but this is no longer the case.
Awesome, great vid and thanks for that. Can you get a screen shot (or pic) of your About Phone > Software Information?
Thanks! Here is the requested pic...
I should note that this phone came with 2.2.1, where the other two I have rooted did not.
Awesome, thanks for the quick pic. I've had six Glaciers, two of which came with 2.2.1 pre-installed, the rest came with 2.2 and then 2.2.1 came down once I checked-in. So that alone (2.2.1 pre-installed) shouldn't be an issue.
The difficult part is, there have been multiple "processes" attempted on this device, so I can't attest to the state of the device/ROM. Is this attempt with Visionary coming from a clean install/factory reset? I'd sort of like to "take it back to basics" and have a factory reset device THEN try ONLY the Visionary method.
I saw someone mention that a dev though there could be a hardware issue causing this (I can't remember which thread or which dev mentioned it), but it was only speculative.
It seems pretty clear you know what you're doing and you're quick AND we're not even to the .sh portion (where a lot of people end up with /root/root directories).
Keep me posted...
If you could, please supply me with some detailed factory reset instructions.
I want to make sure we are troubleshooting this appropriately, and I may not be wiping it correctly.
Please let me know.
Thanks.
It should just be Menu > Settings > SD & phone storage > Factory data reset...
Ok, it's running through now.
What would my next step be?
EDIT: Wipe finished. I installed Visionary, ran Temproot, still get the 'su: unknown user root' error.
May be heading to my local T-Mobile to replace the device.
K, so once it's finished you'll get to the TMO setup wizard where you enter your Google account info, etc. Once you get through that and get to the home screen, stop and don't do anything else. That's our home base.
Let me know once you get to the home screen for the first time after factory reset and we'll go from there...
I appreciate your patience and willingness to go through everything in baby steps.
Youch, k, there we go. That's exactly what the next step would've been and it sounds like you're truly not missing anything.
Does anyone else out there have anything to offer? I think you're probably best at cutting your losses and just getting another device. It really should be a very simple process, as you've seen before.
Keep us posted on the new device!
Woops, went a little too far then. I'll re-wipe.
What's the next step?
EDIT: Didn't do this, nevermind.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Ok, unless there's some silly oversight, I think we might have a different issue here. Anything 'special' about these newer HTC Glaciers? All the specs you posted look identical the devices I've had from November, December, etc.
I hope there's no issue with me posting a link to Visionary.
Visionary R14:
http://deancasey.net/android/apps/visionaryplus.r14.apk
Just for giggles, can you try that APK? I know you said you have the same version, but there's obviously some difference between what you have (hardware, software, etc.) Other than that, it's either process or device. You seem pretty knowledgeable and it's not some silly mistake like not finding the .sh script.
Has anyone else tried to root using Visionary R14 on a newly-acquired MT4G? I'm just wondering if ANYTHING is different about the newer devices.
Still not working.
Should I try the gfree method? I will also note, that the last 2 I did gave me a real hard time rooting them. I bounced around a bunch of threads/methods before I got it to work, and I really don't recall what I had to do.
Yeah, it's just something that's really weird to me. I've been a "tech," professionally, for nearly 15 years. I worked as a Project Manager for a software company for 7 years, so I was solely responsible for testing our new releases. I also did all the 'lite' work like the database patches, installer scripts, etc.
Working closely with a smart developer, you start to get really good at testing and removing your own opinions from the loop. So there's pretty much always a finite reason why something isn't working as expected.
So that side of me wants to know what the variable is. Six of these devices and I've rooted them all without issue, using that .apk and Grankin's .sh script. So it's like, ok, I know this works. I've seen it not work for people who weren't on 2.2.1, who didn't follow the directions, etc. It looks like we can rule out the user with you so now it's a matter of what is unique about your device(s)?
Try the gfree method and report back, but I'd definitely like to see if anyone smarter than you and I has any input on what could be different about the newer devices you have.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Click to expand...
Click to collapse
I was under the impression that you had to turn S off before you can perm-root this device. The way I did it is here: http://forum.xda-developers.com/showthread.php?t=858996
I used only Gfree and Visionary (both can be obtained in the link). No separate rage exploit. If I follow you correctly, I don't see where you used gfree after temp-rooting, which is what actually turns S on or off from my understanding. Visionary is what puts the binaries in place and executes the exploit to do so. I only used these two tools and I have S off with perm-root verified. Try it this way:
1. Fresh MT4G, stock bootloader, recovery, etc.
2. Ensure USB debugging is on
3. Install a terminal emulator
4. Install Visionary
5. Temp-root with Visionary
6. Push gfree to your phone as described in the link above using adb
7. Open your terminal and run gfree as described in the link above
8. Reboot
9. Run Visionary again, but this time ensure you check the box to have it mount system R/W after temp-root
10. Temp-root through Visionary
11. With Visionary still open, attempt to perm-root the device; it should reboot
These are the steps that I remember following and it worked perfectly. The key was using gfree to turn S off in order to get it to stick, then going back to Visionary and rooting. I think it is possible to get perm-root with the engineering bootloader and not really turning S off, but I am not %100 sure about the new stock bootloaders and having to turn S off or not. But, this method worked on more than one MT4G on which I tried it. Hope it helps.
The method outlined in Grankin's post gets you S-Off.
totalentropy is getting stuck before we can even get to the next steps. He's just trying to get Temp Root and then get su. You won't have S-Off at this point in the process and you don't need to have it off at this point. You won't get S-Off until you run the root.sh script...
*Crappy iPod Touch camera
total, have you tried the 'Alternative Root Process' outlined in Grankin's post? He wants you to remove the Visionary and Super User apps before proceeding with that method.
kmdub, that didn't work for me.
schlongwoodian, I did try that, and it seemed to be working. After the last rage, it soft reboots to the MyTouch logo, 5 seconds later flashes back to the MyTouch logo, then boots normally. I checked S after that, and it is still on. This is the same behavior that my other two exhibited when I was trying to root them.
Here is some additional info that may be helpful.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally. I could only push them right when the phone booted with the USB plugged in, right after the USB debugging mode message appears. Any other time and I get access denied.
When I run gfree, with the -f switch, I get an error with input file, sometime a different error that I cannot remember off the top of my head. On one Glacier, I could run gfree with the -s off switch, which did work. I tried that on this current one, and it did not help.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally.
Click to expand...
Click to collapse
Push via? ADB? Why is Superuser.apk being pushed to the phone? That's part of another root process I'm guessing? That's not part of Grankin's root process. Now, the Superuser.apk does get installed (Visionary), but never does Superuser.apk have to be manually copied over.
Those are good points that you mentioned. Can you clarify if you pushed Superuser.apk to your phone earlier? The process should be:
- Factory reset or start with clean device
- Copy visionaryplus.r14.apk to your microSD card (I put mine in a folder named _appz)
- Copy Grankin's 'root' folder to the root of your microSD card
- Run Visionary to gain temp root
- Run Terminal and type su
It's interesting that you're getting the 'unknown user' error right when you type 'su' and you also have manually copied over a Superuser.apk. Can you start the process over again - factory reset - and do nothing once you boot the phone for the first time? Wait and don't copy a thing over, nada. Just wait and post back here. And make sure there truly is nothing on your microSD card - nothing that you've put there that is, not until we can start this over again.
I hope we're onto something...
Related
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on
vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.
mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.
Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...
Please post questions in Q&A section.
just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.
Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App
Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark
I attempted to perform a perm root + S-OFF via BlackPrince' video.
Everything seemed to work like a charm. The only thing I did different was type 'sync' twice at the end of the terminal process. Didn't really think that would hurt.
Downloaded Rom Manager and attempted to flash ClockworkMod, but it gave me errors, said something about su not being found in the right place.
typed su into my phone terminal and got the 'access denied', which leads me of course to believe that my root isn't permanent.
I would love to use both the CM and Sense ROMs, but not sure if that's smart seeing as how the root isn't permanent.
One thing different from BPs video
I have searched all over these intraweb and found a bunch of topics with no definite solution for the G2.
Any help would be greatly appreciated
Use the gfree method from the wiki.
wileykat said:
Use the gfree method from the wiki.
Click to expand...
Click to collapse
This. If you follow the instructions, it's almost fool proof.
Wiki says if you have S-OFF (I've checked and I still do): "Then you can use the psneuter procedure to get temp root at 1.72, and then follow that up with the usual methods to get permanent root from there."
I can get the # on the PC, but how do I then 'lock it in'? - I've spent a fair while looking round, but can't seem to find out.
I assumed I could go to the terminal emulator, but it was $.
[EDIT] Found it:
http://forum.xda-developers.com/showthread.php?p=10600074#post10600074 page 30ish
Thanks for the replies, people. I will definitely use the gfree method when I get home. Two questions though:
Is there a way I can run both sets of commands in terminal?
Can I still perm root while running CM6?
So over the past few days I have been doing alot of research on rooting my phone. I have watched videos and read almost every thread concerning it. I understand the advantages and disadvantages of it. I have never done this before, but I am more than competent enough to follow the directions. I have taken it as far as using visionary and temp rooting my phone. I have a file manager downloaded, and a terminal emulator downloaded. If I go through with it I plan on following the directions in the thread using the gfree method. Ok, with that being said, my only real question is..if I follow the directions, obviously making sure my phone is charged as well, what are the chances of me bricking my phone? Is it incompetence that will create a brick? Or is it something that following the directions correctly will easily avoid?
just do it. -nike
follow directions and youll be fine. thats what i did
Yeah, it's pretty hard to brick your phone. One word of caution though: if you decide to flash the engineering bootloader, screwing up that command WILL brick your phone. Check it, re-check it, and do it over again just to be sure you've typed it properly.
Yea, not trying to get that in depth into it, just want to run some STABLE custom ROM's. I have spent the past 2 hours setting up adb and getting my phone to accept commands. Starting to get comfortable with that. I am really new to all of this, so I am trying to learn as much as I can before I jump into it.
UPDATE: Just need a couple more people to chime in on this. Like I said, I have ADB setup, my phone is accepting commands (rebooted over adb to test) I have visionary, I can temp root with no problem. I have read over the instructions, and understand them fully. I am not going to flash the engineering bootloader, just want to permroot to flash custom rom's and delete bloatware and such. So just doing permroot, is there a chance I can brick my phone?
as long flash a revovery image. And dont mess with the radio file you should be okay.
Cyanogen Powered; Android designed
Alright, thanks for the help, I am obviously a noob...Flashing the recovery is done right on the ROM Manager App right? And there is no way to accidentally mess with the radio?
lowandbehold said:
Alright, thanks for the help, I am obviously a noob...Flashing the recovery is done right on the ROM Manager App right? And there is no way to accidentally mess with the radio?
Click to expand...
Click to collapse
yes it can be done with clockwork ROM manager.
And no the radio has to be done on purpose.
Cyanogen Powered; Android designed
Thanks for the help, It took me 2 days but I grew a pair and did it. Followed the directions on the guide and worked perfectly. Deleted Visionary, rebooted into hboot and have S off, went into my terminal emulator and still have superuser access. Thanks again!
lowandbehold said:
Thanks for the help, It took me 2 days but I grew a pair and did it. Followed the directions on the guide and worked perfectly. Deleted Visionary, rebooted into hboot and have S off, went into my terminal emulator and still have superuser access. Thanks again!
Click to expand...
Click to collapse
You really should flash the Engineering bootloader. It makes it harder to brick your device in the future.
It took a bunch of reading, but I rooted my phone and my wife's phone using the gfree method, and installed the engineering bootloader.
Then, a month or so later, I upgraded to CM7. CM7, while still beta, is tons better than the stock firmware. I was going to do Ice Glacier, but developement stopped on it, and ultimately I wanted to be on CM anyway.
Better battery life, tons more features, no reason to complain.
Just do it. TMO should make CM stock on these phones.
I am trying to root my phone and am running into trouble early. I have watched the videos & followed instructions. Somehow I am either missing something or my phone is jacked somehow.
I made sure it's not in fast boot, USB debugging & unknown sources are on. I have tried visionary r14 & r11. I have also tried multiple factory resets.
OK, I use visionary with set system r/w after root checked. I go from there to Term. Emulator & when I type su it shows "unknown user root" without the quotes. I've tried to continue but it gives me other errors and S is always on when I check.
I've searched Google & the forums and haven't found much that's been able to help me.
If anyone has seen this I would appreciate the help. Thanks!
Visionary (r11 & r14) are only temp root tools. You must use one of the two methods (both are in my signature) to turn s-off. As long as your s-on you will not be able to permaroot your phone.
Once you turn off the phone, and turn it back on you've lost Root Access. and that's why it's given you that error. If you pull the battery wait about 30 seconds, put the battery back in. Then temp root you should see a "superuser" icon appear. Once you see that try your SU command from terminal emulator. The other thing you can try is setting up your ADB (link in signature). Navigate to the c:/adb folder then typing in ADB shell. You should see a $ sign appear. Type SU from the Command Prompt and it should ask you to approve the SU access on the phone. once you've gained temp SU access you can proceed with one of the two methods i've got posted to finish turning s-off.
It's the temp root I'm getting stuck at. I do get the superuser icon after I do the temp root. I go directly to emulator and type in su and that is when it tells me "unknown user root". I will try the ADB method when I get home from work if nothing else is figured out before that.
Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1
You may have a newer chip set and may only be able to root with s-off by using the gfree route. It was the only thing that worked for me.
In my situation I had visionary installed, root folder in the root of my sd card, and followed the unlockr method for root access.
I temprooted and checked temp root on boot and rw one too.
I ran terminal emulator, typed in the commands and the process ran and looked like a success.
I powered my phone down and boot into hboot and s-on showed up.
I tried the same process and factory reset between tries.
I then found out there was another way to get perm root with s-off using a similar process.
I factory reset and placed visionary apk and gfree folder on the root of my sd card.
I went on the android market and installed root explorer (there plenty others you can use it only need to be able to access your root) and also terminal emulator.
I installed visionary and temp rooted (using same temproot method from unlockr.com) my phone I downloaded the gfree file and extracted it on my cpu then moved it to the root of my sdcard.
Then using your root explorer go into gfree folder and copy the file called "gfree" and only this file.
The go into the root of the phone and your going to paste that into the local folder in /data/local/
From there you type in a few commands in terminal emulator. It will run thru a process then power down.
Boot into hboot and verify it shows s-off
If so reboot phone. When your phone boots up visionary should have temp rooted your phone.
If so Open up visionary and uncheck temproot on boot and click attempt perm root. Your phone will reboot and you have perm root. Verify by typing su in terminal emulator and then if you get # your good to go.
If you dont get s-off try factory reset and repeat process, you should be able to find the instructions if you search gfree and it should come up but if im not mistaken its a stickie on the developement forum
Hope this helps!
HTC Glacier
Perm-rooted S-off
If root.sh method is not working, use gfree + visionary method. Worked for me as a charm.
People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
corollatercel said:
Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1
Click to expand...
Click to collapse
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.
Jack_R1 said:
People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.
Click to expand...
Click to collapse
Thanks, this is the answer I was looking for. An alternate method of temprooting. I will try this and post results. Thanks Jack.
Ok you guys may think i'm kidding but I tried both methods outlined
Here:
SuperOneClick trying both psnueter AND gingerbreak options
http://forum.xda-developers.com/showthread.php?t=803682
And
Here:
RageagainsttheCage
http://forum.xda-developers.com/showthread.php?t=792016
and even after superoneclick says its rooted AND says says success when it asks if I want to test root by sending su command, whenever I go into terminal Emulator and type in su I get permission denied or unknown user root whenever I tried su through adb shell through Dos on my machine. I dunno what is it with my device. I did all of this after fresh factory resets just so you all know. I dunno my MT4G must have a newer chipset that's not vulnerable to the current exploits is all I can say. I've follow these instructions to the letter more than twice each time factory resetting just to make sure things are fresh. Still no dice.
I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.
dbharr said:
I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.
Click to expand...
Click to collapse
Yeah unfortunately am not in that same position. It sucks. Guess i'm stuck with it for the moment. Only reason I really wanted to root and upgrade was so I could download netflix. I went from the G2 to the MT4G and had NO idea it was just compatible with certain devices. I've tried different versions of the netflix app on here too but they all require you to have root. Hopefully they make the app compatible soon.
Here's an update everyone. I was FINALLY able to get everything working. I had to use a tool called Z4root to gain temproot. You can imagine my relief AND also frustration after I installed z4root and things just started running just the way it was supposed to. I gained temp root in a matter of minutes and after doing so I was able to use the gfree method to perform all other functions that are a part of the rooting process. And for the record ALL other tools did not work for me:
- Both versions of visionary + 11 and 14
- SuperOneClick using psnueter AND rageagainstthecage exploits
Just thought I'd share. Thanks a lot guys. I had already put my mytouch on cl for sale or trade for a G2 because I thought my device could not be rooted or anything. until about 1 o clock in the morning I got it workin...ha.
Thats sweet man im glad you got it done, only difference I was avle to use visionary
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.