Related
OK so I downloaded the original 2.1 leak.
It changed the boot loader (I believe that's the reason after the 2.1 update why people weren't able to rollback to 1.5, yes I know 2.1 rooted rom's can roll back now) and then installed 2.1 OTA "official"... guess it was the second attempt at 2.1 since VZW canned the first test ROM.
Anyway... so now I am running the latest OTA non-root ROM and if I hit power + volume up to enter recovery mode (or install other ROMs like EvilEris1.1.zip, Legend.zip) I get an Exclamation point.
Hitting Power and Volume down gets me into hboot where I could install the PB00IMG.zip (it checks for a few other names like this as well).
Is there anyway to restore that recovery functionality?
Also, which I am assuming because I'm running non-root ROM, when trying to use adb I cannot run "adb root", "adb mount", or "adb shell" and remount /system as rw. Complains can't do this because it's official rom?
Any help here getting me to the point that I can recover if necessary, install EvilEris, Legend, etc for testing purposes, even recover to rollback and start all over... would be greatly appreciated.
Thanks
Chris
nemish13 said:
OK so I downloaded the original 2.1 leak.
It changed the boot loader (I believe that's the reason after the 2.1 update why people weren't able to rollback to 1.5, yes I know 2.1 rooted rom's can roll back now) and then installed 2.1 OTA "official"... guess it was the second attempt at 2.1 since VZW canned the first test ROM.
Anyway... so now I am running the latest OTA non-root ROM and if I hit power + volume up to enter recovery mode (or install other ROMs like EvilEris1.1.zip, Legend.zip) I get an Exclamation point.
Hitting Power and Volume down gets me into hboot where I could install the PB00IMG.zip (it checks for a few other names like this as well).
Is there anyway to restore that recovery functionality?
Also, which I am assuming because I'm running non-root ROM, when trying to use adb I cannot run "adb root", "adb mount", or "adb shell" and remount /system as rw. Complains can't do this because it's official rom?
Any help here getting me to the point that I can recover if necessary, install EvilEris, Legend, etc for testing purposes, even recover to rollback and start all over... would be greatly appreciated.
Thanks
Chris
Click to expand...
Click to collapse
it sounds like you installed an official non root image over root, replacing everything including the recovery img. We have no current way of rooting your phone.
Nope,
As I said I have downloaded and installed the following
Beginning of March --
HTC 2.1 Leak Rom
Verizon test rom, REJECTED. Do not Install if you want root.
Rom: http://www.sendspace.com/file/frqze0
March 30 Installed --
HTC 2.1 Release Candidate (AKA OTA) Leak Rom
Verizon test rom, possible OTA leak. Do not Install if you want root.
http://www.megaupload.com/?d=RHNAWUR0
Never downloaded or installed any other ROM. Never installed a root ROM.
nemish13 said:
Nope,
As I said I have downloaded and installed the following
Beginning of March --
HTC 2.1 Leak Rom
Verizon test rom, REJECTED. Do not Install if you want root.
Rom: http://www.sendspace.com/file/frqze0
March 30 Installed --
HTC 2.1 Release Candidate (AKA OTA) Leak Rom
Verizon test rom, possible OTA leak. Do not Install if you want root.
http://www.megaupload.com/?d=RHNAWUR0
Never downloaded or installed any other ROM. Never installed a root ROM.
Click to expand...
Click to collapse
sorry dude
well, you are not going to be able to install other roms since you do not have root. i believe you should be able to get into recovery, but only able to do basic functions such as data/wipe. you wont be able to install new roms via recovery. the only real function you will have is to go into hboot and flash the current build version or a higher build version of the pb00img.zip file.
like jcase said, there is no way to root your phone, unless you have the official build version 1.5.
ECLIPS3 said:
well, you are not going to be able to install other roms since you do not have root. i believe you should be able to get into recovery, but only able to do basic functions such as data/wipe. you wont be able to install new roms via recovery. the only real function you will have is to go into hboot and flash the current build version or a higher build version of the pb00img.zip file.
like jcase said, there is no way to root your phone, unless you have the official build version 1.5.
Click to expand...
Click to collapse
I can do hboot (Power + Volume Down) but I can't do recovery at all (Power + Volume Up). Just get Exclamation Point.
So one of these Verizon Test Roms erased the "stock" recovery mode as it is no longer there and there is no way I can figure out how to restore that, forget a modified recovery.
just a question , what if someone backed up the files off the card to their computer or somewhere? i was just wondering cuz a lot i have been readin , people have downloaded the wrong file and lost root .if they have it backed up ,couldnt they just replace the files on the card with the ones saved and be able to do a recovery? i dont know much about how this works so dont rip me to bad lol just asking
HTC?!?!?!?
So someone from HTC needs to post a signed "su enabled" ROM...
Hello? HTC employees... help here like you did for the 1.5 "su enabled" leak that got us root... PLEASE!!!
nemish13 said:
So someone from HTC needs to post a signed "su enabled" ROM...
Hello? HTC employees... help here like you did for the 1.5 "su enabled" leak that got us root... PLEASE!!!
Click to expand...
Click to collapse
Doubtful it will happen for the eris again.
jcase said:
Doubtful it will happen for the eris again.
Click to expand...
Click to collapse
yeah but we can hope here... someone working for HTC has to be nice enough to take the OTA, enable root, sign it (most important) and post it...
I can't think people at HTC wouldn't share if they had the ability to help the community out now... LOL
More than likely only a hand full of people have the ability to sign the roms. We didn't get a release rom with root, we got a engineering rom.
Odds are in the favor or a root exploit, go see what Paul O'Brian has done with the HTD Desire and Legend . Hopefully that can help us.
i run unrevoked and nothing happens. this a new problem with the new update? this is my replacement phone anwaysy so.
anyone know anyways to root? i can't downgrade to old version. please help..
if you have s-off you just need to flash a custom recovery.
if you don't then i have no idea if the updated rom is rootable.
that would have been something to look for before upgrading
Good luck!
Having custom recovery is not the same as rooting (Superuser acess). Unfortunately, at the moment, Unrevoked won't work on the new OTA and if you install SU pack after the OTA it will just hang during boot up and you'll be in reboot hell. You can have Clockwork with the new OTA, just not root access.
downgrading to stock then s-off and upgrading work?
update. i tried downloading the super back to stock thread and the hboot says the file is older and i can't by pass it.. so hmm
I am in the same boat. Just got the phone and the f-ing salesman decided to install the OTA for me while he was setting it up. So do I return this thing in the hopes of getting one without the OTA or is it likely it will be rooted?
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
dadsterflip said:
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
Click to expand...
Click to collapse
Nope, can't downgrade...I'm out of ideas. Pretty pissed off actually to the point where I'm ready to take it back and get one that doesn't have the god damn OTA applied. I HATE owning devices that I don't really own.
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
caleris said:
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
Click to expand...
Click to collapse
press Volume Up + Power I think when you see the triangle
magneticzero said:
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
Click to expand...
Click to collapse
But???????????? This will only work if you are already s-off, correct?
blackwolf77 said:
But???????????? This will only work if you are already s-off, correct?
Click to expand...
Click to collapse
if you have clockwork mod installed with S-On and updated the ota already, you can flash unrevoked forever through clockwork recovery... that will take S-Off to off. I was messing around earlier and did that..
I am not sure how you got clockwork installed. Everytime I try it recognizes the PB31IMG and then just skips over it. It never asks about installing it.
The file name has to be PB31IMG.ZIP right? Also the LCD works different right?
SLCD PB31IMG.ZIP
Sent from my ADR6300 using XDA App
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Nitrogenus said:
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Click to expand...
Click to collapse
in for answer
tried it out, didn't work. the su trick with rageagainstthecage-arm5.bin does not work.
how to see page 3
Standing by!!!!! Will it work with s-on?
It shouldn't matter s-on or off. I have the SLCD screen don't know if it will make a difference. Just FYI
Sent from my ADR6300 using XDA App
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
Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.
Try this worked perfectly for me. also make sure you have ADB installed and working properly before attempting root.
http://forum.xda-developers.com/showthread.php?t=858996
lancer123 said:
Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.
Click to expand...
Click to collapse
if you want to go back to stock follow the downgrade thread (linked in the thread about forcing the update) then follow the one linked above me here... it's faster than my forcing the update method (once you get radio s-off and the eng boot loader you can actually just flash the update.zip from my thread....)
EDIT: and in the future please post in the proper section or reply in the thread of the guide you're having problems with.
Thank you for trying to quickly help me. I started to follow the instrucions for downgrading and got stuck at the ADB Shell command. Within the Shell, I typed SU and got the following error "must be usid to work properly". Can you please offer any advice to get around this error?
Thanks,
Lance
to be suid you have to have temp or full root access. my sugestion would be to start the process from scratch. have you tried the visionary method?
i cant post the link to the other forum but its readily availible if you google it.
i didnt see the download link in the site i found so if you need the file PM me your email and ill send it back to you
Hello,
Yes, I did try Visonary and will not get SU working. The S=off is already showing. However, no matter what I do, I can't get SU to work. The device appears to be rooted but won't allow any advanced permisson comands to be used such as SU. I have tried re-installing superuser. that didn't help either.
launch the current version of SU you have on your phone and select settings scroll to the bottom of the page and under "superuser Information" you should see "Su binary Vx.x.x-xx) what is the version #?
Click on that and see if it updates the version if it does update try rebooting launch terminal and retry SU
Hello,
I checked the version of SU and did find there is an update. I tried to install and got the followng error 'An error occured and su was not updated. a zip file has been placed on your sdcard. please reboot into recovery and flash it".
The problem is that I can't get into recovery as I get the red exlimation mark. I can't find a way to install a recovery program because of permission issues.
Any further suggestions?
Please post questions in Q&A section.
Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
How in the first place you get the s=off. In order to get s-off you need root! Is also known that to boot into recovery thou need to try several times before its locks! The better way to deal woth it is reading! The root method in the dev section help a lot! Read, read! That's the better way to learn! If you are in eng hboot and s= off there's a possibility that you only need to reboot into recovery several times! Other than that just read with patience!
Sent from my HTC Glacier using XDA App
lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
My advice (without trying to hurt feelings too much) is DON'T ROOT. You obviously don't really know your way around Android too well at this point. I would familiarize yourself with everything before diving in head first.
Despite popular belief, having root does NOT in fact make you cooler.
WAAAY too many new users are trying to root because they think it's cool or heard it's cool. You need to learn your device first.
deviusdragger said:
Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
no... you fail
lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
lancer... get on IRC I will help you
EDIT: or AIM, or yahoo, msn, or gtalk.... my info is in my profile
If you have S=Off on your phone already, your best bet would be to flash Clockwork recovery through FASTBOOT.
If you are unsure of how to do this, refer to this link from the Cyanogen Wiki:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
The page will point you in the right direction for everything that you need.
Have the ROM that you want to install on your SD Card because FASTBOOT will probably not allow you to directly flash all the other partitions, but it will at least allow you to flash recovery, then boot into Clockwork and Install a new ROM.
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
geronimo711 said:
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
Click to expand...
Click to collapse
What is the end result you are trying to get to?
If you are wanting S=off so you can flash custom ROMs.
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/; do that and it will lead you to perma root the easy way.
if you are wanting s=off so you can have complete control over your phone, which will enable the possibility of a brick. including SuperCID, ./gfree and some other goodies...... But this will give you the option to severally screw up your phone including up to a 500.00 paper weight.
http://forum.xda-developers.com/showthread.php?t=858996
If you haven't screwed up the HBoot and the bootloader you can use this to get back to a factory spec.
http://forum.xda-developers.com/showthread.php?t=863899&highlight=level
But if this is your first android, and your first time rooting i would HIGHLY suggest doing alot of reading before you jump in head first. There are alot of people who have tried to do and get stuck. This phone is confusing once rooted with 2.2 ROMs and 2.3 ROMs and different recovery images you need to read and make sure you understand everything before jumping in feet first.
Temp root with visionary is the easiest and safest way, but gfree is pretty simple as well. The hardest bit is getting the drivers and ADB to work, and thats not overly difficult. (remember to use the command "ADB devices" to know if the drives are working) It just matters what you plan on doing, stock root or custom ROM.
There is really only two points that risk a hard brick, flashing the radio or hboot.
The gfree method does not require either, but you can flash the engineering hboot as optional.
The biggest thing with recoveries and ROMs is know that gingerbread based ROMs (like CM7) use ext4 file system and froyo ROMs use ext3. So it is important to use the right version of Clockwork recovery. Use v2.5.1.2 for froyo ROMs and v3.0 for gingerbread ROMs. Soon clockwork mod will support both on the same version.
Just read the instructions well and have all files downloaded and ready to go.
If you want to use gfree and a custom ROM, there is no need to get perm root on the stock ROM first. After the steps that get s=off, just run visionary as temp root with system r/w access and install ROM manager from the market, then use ROM manager to flash a new recovery. Reboot into recovery backup your stock ROM then flash a new ROM.
If you never touch the hboot or radio firmware, then at worse you can bootloop or soft brick the device. That can be fixed with varying amounts of work, depending on the exact issue.
Read and learn how the different parts work, learn how to use ADB and you will be better prepared.
newbie here
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
ibnird said:
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
Click to expand...
Click to collapse
Temp root is just that, temporary. It creates a copy of the essential files in the system partition that it runs from rather than the actual system partition. If you allow it r/w access, (an option you can choose when using visionary) it can uninstall apps that normally can not be. (and more, but causing big changes would require more work on your part)
Because it is temporary, there is no need to get nervous. Unless you are doing some major changes, ones that need a root explorer app or terminal emulator, then you can't really hurt the phone. Download terminal emulator from market and run it, then type in the super user command "su" (no quotes) then hit enter, if the cursor changes to a # symbol then you have root. (you may get a popup asking for root permission, choose to allow) If it works after a fresh reboot, you either ran perm root in visionary, or you have the option checked to temp root every reboot.
S-ON means that the bootloader security is still in place. You need it off to install custom software. While you can root the stock software with S-ON you can not install any software that has potential to brick your phone, so no need to worry at all. If you are really that worried, keep a copy of the stock software on your SD card. Make sure it is named PD15IMG and at any time you get nervous, you can boot into hboot (the bootloader) and it will run automatically. It will wipe your phone and return it to complete stock. The irony is, that flashing this stock image file does things that can brick a phone if it goes wrong. It flashes more than just the OS, it also flashes hboot and recovery as well, and if the process is messed up in anyway like loosing power at the wrong time, it can brick the phone.
Really as long as you make sure you have the phone charged and you follow instructions you should be fine. The only times you can brick a phone to the point it can not be brought back is when flashing hboot and the radio firmware. Both of which you would rarely flash. Hboot only needs flashed to the engineering version once (OEM testing/DEV version) and only if you choose to, as it is not required. The radio will only need flashed if an update for it comes out, and that isn't often, and it is rarely mandatory.
The chance of truly bricking your phone is not very high, unless you just can't follow the directions. Now you can put it into a bootloop or soft brick it. (bootup stuck on mytouch screen) But if you can boot the phone into hboot (vol down + power on) then you can fix it. Even if you can not boot into recovery (an option in the hboot menu) you can even fix that with a good hboot.
theres a video on youtube by mackster its awesome and it gives you all the links very easy to use.
it wont let me post the link but just search root mytouch 4g on youtube and it should be the first or second one.
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
ibnird said:
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
Click to expand...
Click to collapse
Uninstalling an app will not hurt anything. OTA updates will still work fine. You can temp root and then perm root the stock ROM and revert easily. Heck, even perm rooting stock doesn't break OTA I believe.
Voiding the warranty is one of those grey areas. As long as you can revert to stock, then they will never know. Temp root does not void warranty at all, because you do not alter the system files. (unless you want to, and enable the ability to read/write system) Just uninstall terminal emulator and super user apps and there is no evidence.
The only time you might get caught, is if say the screen stops working, and you can not see to revert back. Though even then, just putting the stock OTA image on the sd card then booting up the phone in hboot will restore without needing to actually see anything. It does ask for confirmation to restore, just wait several minutes then hit the power button and it would do it on its own.
The set of circumstances needed to prevent you from restoring to stock, are rare. Basically a borked hboot or radio firmware, and you never need to touch those to get full root and custom ROMs. If you never touch them, the chance of issue is almost zero.
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
goldfish524 said:
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
Click to expand...
Click to collapse
You dont need apps2sd, as the mytouch 4g has Froyo installed, and you can move some apps to the SD card. Just go into settings-Applications-chose the applicaiton you want on your SD card, and look for "move to SD". If it's grayed out, then you cant move it.
Also download appfreezer from the market, and just "freeze" the bloatware. That's what I do, and it gets rid of those annoying looking apps they installed.
Question about clockworkmod
OK i just rooted my phone, flashed the rom, and installed all the goods... it works perfectly and looks great.
Ty for all the guides/ instructions.
My only question is about the clockworkmod. When I turn off my phone and plug it in to charge the recovery screen always appears when off and connected. Is this suppose to happen? Or is there a solution to this?
If there is a solution can some one post a link or provide instructions so it doesn't constantly boot to clockworkmod recovery.
Thanks.