Related
After selecting "recovery" from HBOOT, all I get is a black screen with a red warning triangle. 20mins pass, and nothing changes.
I got the phone 2 days ago, and have been unsuccessful in rooting it. Every guide has failed at one point or another. Temp root works, via Visionary and rage, but it will not stick. Rom Manager was able to flash Clockwork, but it didn't work either.
Is something wrong with my phone, or am I just doing it wrong?
It is common for the recovery flash to fail. The red triangle is from the stock recovery software, which doesn't do anything.
Flash the recovery again.
HTC Glacier running CM7 #15
You have to reflash recovery
Sent from my HTC Glacier using XDA App
jggimi said:
It is common for the recovery flash to fail. The red triangle is from the stock recovery software, which doesn't do anything.
Flash the recovery again.
HTC Glacier running CM7 #15
Click to expand...
Click to collapse
So, the stock recovery doesn't do anything, and this is normal? That's a relief.
I still can't flash CW because its not rooted. Every proceedure fails. Ill update with the actual output when I get home tonight.
Sent from my HTC Glacier using XDA App
pagnaet said:
So, the stock recovery doesn't do anything, and this is normal? That's a relief.
I still can't flash CW because its not rooted. Every proceedure fails. Ill update with the actual output when I get home tonight.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
i know this isnt the right thread, but i noticed in your signature that your s-on wont turn off...did you try taking a break and doing it again? i have had times when i tried to root my devices and i would sit there for 2 hours redoing the process over and over then take a hour break, and then get it right away.
Have you tried gfree for S-OFF? I have not heard of that failing. Older methods, yes. My phone rooted with an older method 100% first try -- so easy! My wife's phone, however, was a different story. It absolutely would NOT go S-OFF even after it let me flash the eng hboot file! Which is by itself S-OFF!
Grankin suggested the phone may have a bad eMMC controller and to swap it. I did, and her replacement rooted as easily as my phone (this was a few months back, before gfree).
So if things *truly* are not working and you are certain you've tried every permutation of rooting and just don't have success on one phone even when others work -- swap it.
Genocaust said:
Have you tried gfree for S-OFF? I have not heard of that failing. Older methods, yes. My phone rooted with an older method 100% first try -- so easy! My wife's phone, however, was a different story. It absolutely would NOT go S-OFF even after it let me flash the eng hboot file! Which is by itself S-OFF!
Grankin suggested the phone may have a bad eMMC controller and to swap it. I did, and her replacement rooted as easily as my phone (this was a few months back, before gfree).
So if things *truly* are not working and you are certain you've tried every permutation of rooting and just don't have success on one phone even when others work -- swap it.
Click to expand...
Click to collapse
It's starting to look that way. I tried gfree again tonight.
Code:
Attempting to power cycle eMMC... Failed (not fatal)
Module tried to power cycle eMMC, but could not verify write-protect status.
And then it fails:
Code:
Error reading input file.
And then it freezes.
What do I tell Tmob? Other than the root-resistance thing, the phone is solid.
Sorry I didn't see this sooner! I got your PM though, hope it goes well! You may consider posting this over in the gfree thread and see if you can pull some debug info if one of the devs there would like it, as I've never seen gfree fail like that before.
Gfree 0.2 saves the day!
On a last ditch effort to determine if it was my phone at fault, I tried gfree-0.2(as opposed to 0.4) after reading this post: http://forum.xda-developers.com/showthread.php?p=10560636&highlight=eMMC+fails#post10560636
To do it right, I followed Cyanogen's method and files on his wiki, but with the older gfree. Well, eMMC power cycled just fine and everything worked perfectly, S-OFF, and I'm so glad I don't have swap this flawless device for a possible defect.
Thank all of you for your help, and what you do here. XDA is great community.
pagnaet said:
It's starting to look that way. I tried gfree again tonight.
Code:
Attempting to power cycle eMMC... Failed (not fatal)
Module tried to power cycle eMMC, but could not verify write-protect status.
And then it fails:
Code:
Error reading input file.
And then it freezes.
What do I tell Tmob? Other than the root-resistance thing, the phone is solid.
Click to expand...
Click to collapse
You get that error because your not running gfree as root
you need to temp root, then open terminal
type su
the /data/local/gfree -f
then you should be all set.
option94 said:
You get that error because your not running gfree as root
you need to temp root, then open terminal
type su
the /data/local/gfree -f
then you should be all set.
Click to expand...
Click to collapse
I can assure you that I'm not that stupid. Temp root was never a problem. Gfree 0.4 just didn't like my phone.
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...
This may sound stupid, but does anyone know how to root specifically a RED mytouch 4g?? Maybe the color is intimidating or something, but I have successfully rooted 6 mytouch 4g's and not run into any problems.. I spent a week on this one to no avail. Its running 2.2.1, software number 1.17.531.2, build number 1.17.531.2 CL277036. Is there a manual way without using visionary? It wont grant me permissions even after temp root. Thanks.
try using the gfree method which is in the development section. It seems thats the only way to root the newer mytouches.
Update: Tried every single forum that appeared in the first 10 pages of google for 50 different search terms, and frankly, I'm ****ing beat.. I found a few similar topic forums, but only ONE exact build number, and everything with the SAME EXACT SYMPTOMS.. Is there really nobody out there that has tackled this debockle? I'm not sure what to do at this point, am I doomed?? I'm not a noob with this phone, but I'm not a developer or a programmer either. Anyone got any alternative root methods, other that the visionary, or flashboot methods for the exact specs on my phone??
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
tim4w5 said:
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
Click to expand...
Click to collapse
Thats weird, I achieved s=off, using this method: http://forum.xda-developers.com/showthread.php?t=858996
But I can't get superuser permissions to flash the older version of the bootloader, or use gfree. What did you use to root it?
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
gfree issues
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
bvince05 said:
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
Click to expand...
Click to collapse
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
jdkoren said:
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
Click to expand...
Click to collapse
I've tried stock out of the box, used it for a while, got s=off, and it stuck even after factory resetting the phone between trying various different methods.
I agree with you regarding a patch of some sort on the software though. I've found this issue on 2 red htc glaciers now.
And although It's new, and shipped with 2.2.1, a buddy of mine goes through them like candy, and I've rooted every single one of them, no problem. even when they started shipping with 2.2.1 it wasnt an issue. So I think it's the newer manufacture build number etc with the red ones..
mustk1ll20 said:
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
Click to expand...
Click to collapse
I have not tried that yet. Where can I find an older version of visionary? I looked for it on their website, but can't seem to find anything but the current version. (maybe I'm not looking hard enough) but.. Hopefully this will work
think this is the one i used. should be R11. may have been updated though, just got the link from another root method that says it r11.
http://www.megaupload.com/?d=7C2BMH3O
It's definitely r11, I'll try this as soon as I get home. thanks!
No problem, hope it works for you.
Sent from my HTC Glacier using XDA App
I dont think It's working. I installed it, then reboot my phone, then ran the app, and At first It looked really REALLY unstable and kept flashing and doing weird things, so I rebooted again, ran it, and now it looks like it's not doing anything at all. How long did it take for your phone to say root successful, maybe I'm just being impatient.
thats what mine did. Just let it do its thing. If its to unstable to put in your commands use adb. I used adb from start to finish just cuz I find it easier.
Didn't take long. It did flash a black screen things like that. But just follow the guide you were using to a T and once you get temp root it shouldn't be a problem from there
Sent from my HTC Glacier using XDA App
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
****kkkkk man your slacking -______- I was looking forward to the answer I'm going crazy as well I rooted 3mt4gs in like 5min but my brothers is driving me nuts >=O
carlosdavampire said:
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
sh root.sh
Im getting passed everything, but when i try to run sh root.sh it say can't open root.sh Someone please help me.
I had troubles rooting my Red Mytouch until I came across this.. http://forum.xda-developers.com/showthread.php?t=995549
Follow this to a T and then do yourself a favor and downgrade your Hboot to 0.85.2007
I rooted mine. Go here. http://theunlockr.com/2010/12/10/ho...s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ took me a bit to figure it out. But on this link it tells you to update if you arnt 2.21 or higher or if you haven't received the outa update. Well I did but when I tryed this method with out the update it didn't work so update anyways. IT WORKS!
Sent from my HTC Glacier using XDA App
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...
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.