I had previously posted to the forum about unrooting my Evo 4g and was referred to this thread. http://forum.xda-developers.com/showthread.php?t=780141 I have followed all of the steps and I still have root access. On the recovery it told me that the PC36IMG was outdated. My phone goes in for repairs in the morning and i desperately need to remove root access and all traces of root. Any suggestions. I can use all the help that I can get.
Try a newer PC36IMG from here : http://goo-inside.me/evo/stock/ruu/
If that doesn't work you can always try an RUU.
what is a RUU?
sevenpillars said:
what is a RUU?
Click to expand...
Click to collapse
Another way to unroot, but you run it with your phone connected to your computer. Not to be rude... but if you don't know what it is I probably wouldn't recommend running it. If your going to there are directions near the top of that page that tell you how to use it.
Okay, what would you recommend?
http://j.mp/ruuevo4g
Follow this tutorial, enjoy.
READ. EVERY. DAMNED. INSTRUCTION. Do not skim, do not skip. READ IT. Failing to do so may result in a bricked phone which will eat your cat.
I have followed all the instructions and it is telling me that my phone is not connected properly to my pc. what do i do?
Did you install the hboot driver, and connect your phone via fastboot from the bootloader?
What OS? Did it work previously? DId you download the drivers from htc's site? When you plug it in, what step are you on?
What......? I am a first time rooter. Can you be a little more specific than that?
sevenpillars said:
What......? I am a first time rooter. Can you be a little more specific than that?
Click to expand...
Click to collapse
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Download those drivers, simply follow the instructions
To get to the bootloader:
Power off device
-While powering back on, hold vol+down
-After it scans, use the volume keys to navigate to fastboot, press the power --button to select
-Connect the phone to the pc via usb cable, when the phone displays fastboot usb in blue, run the RUU exe on the pc.
Do i run the fastboot?
Yes you need to select fastboot, connect to the pc, then run the ruu exe on the pc.
I tried that and it still is telling me that my Evo is not connected. I am able to access the files on the SD card through my computer but the program is not seeing it.
Try rebooting both the computer and the phone after you install the drivers.
What......? I am a first time rooter. Can you be a little more specific than that?
Click to expand...
Click to collapse
This is exactly why people should NOT root their phones if they don't know what they are doing. Unrooting the phone is 5 times easier than rooting it, so if you dont know how to unroot, I dont know how you were able to root.
The only reason that I rooted my phone is because of programs like unrevoked3. and the only reason that I am unrooting is because of the need to have it repaired. I love my root access and the freedom that it gives me to install custom roms and be able to do with my phone what i wish instead of only being able to "rent"my phone because the service provider only wants to truely sell me part of a phone instead of the whole thing. I have to look at the programs that they deen acceptable because thats what they want. I have to look at advertisements that they disguise as apps because I dont have the power to modify the phone that I paid for to suit my needs. This is why I root. Because I bought it and I want the whole phone not just the party that they want me to have. This is just like upgrading your computer to W7 then deciding that you like XP better. You upgraded because it was easy, you put in a disk and use a couple of mouse clicks. Now you decide that you dont like it. For me its easy to backstep. For other people it may be a little more complicated. It can still be done all someone needs to do is point them in the right direction.
Try redoing it the first way you tried. It seems you tried to flash the PC36IMG in recovery, not the bootloader.
I came to this conclusion because you said:
'On the recovery it told me that the PC36IMG was outdated."
Instead, put the PC36IMG.zip on the root of your SD card (not in any folders), boot into the bootloader & when it asks you to update, choose yes.
Be sure to flash the unrevoked s-on zip in recovery FIRST.
Sorry if this has already been said, I just skimmed the thread. If you need the correct PC36IMG, let me know.
sevenpillars said:
I had previously posted to the forum about unrooting my Evo 4g and was referred to this thread. http://forum.xda-developers.com/showthread.php?t=780141 I have followed all of the steps and I still have root access. On the recovery it told me that the PC36IMG was outdated. My phone goes in for repairs in the morning and i desperately need to remove root access and all traces of root. Any suggestions. I can use all the help that I can get.
Click to expand...
Click to collapse
I would like to thank all that helped me in this thread and i did click the thank you button as well. I returned my Evo and they didnt see that it was ever rooted. I found out that the problem was that I heeded to have my HTC Sync driver installed on my computer so in the device manager my Evo showed up as My HTC instead of android phone 1.0 or something to that effect. After i installed that I ran the auto RUU found in the first thread of this post http://forum.xda-developers.com/showthread.php?t=780141 it was a long and frustrating process but it paid off. Again thank you to all that helped. @ Sitlet I already replied to your concerns about people rooting that dont have a complete understanding and I agree to a point but we all have to start off somewhere. So now I have to root my new Evo and I go into it with a better understanding.
Root and be free
sevenpillars
sevenpillars said:
I would like to thank all that helped me in this thread and i did click the thank you button as well. I returned my Evo and they didnt see that it was ever rooted. I found out that the problem was that I heeded to have my HTC Sync driver installed on my computer so in the device manager my Evo showed up as My HTC instead of android phone 1.0 or something to that effect. After i installed that I ran the auto RUU found in the first thread of this post http://forum.xda-developers.com/showthread.php?t=780141 it was a long and frustrating process but it paid off. Again thank you to all that helped. @ Sitlet I already replied to your concerns about people rooting that dont have a complete understanding and I agree to a point but we all have to start off somewhere. So now I have to root my new Evo and I go into it with a better understanding.
Root and be free
sevenpillars
Click to expand...
Click to collapse
Told ya that ya needed the drivers.
But glad you got your evo rooted; now you can enjoy it.
Related
I have the 47.651.1 build. This is a new evo from my insurance claim. My last phone before it got messed up was on the same build. Been trying to root for like 2 months. Read all the threads and tried both the toast and unrevoked method. Even went on youtube to follow along on the tutorials there. I'm starting to think maybe its my computers os. I have windows 7 ultimate 64 bit on both my laptop and my desktop. I really dont have access to a 32 bit system at the moment to try. Anyhow, when I try the unrevoked method. The phone reboots the first time into the bootloader and the phone scans the card. It says no file found or wrong file, something like that. Then when I go to the hboot usb plug. The computer makes the usb error noise. Going into the device manager I see that I have an android 1.0 device that has no driver. Yes, htc sync and .net are installed on both my systems. I searched high and low for this driver. I saw a thread about this where someone said this driver isnt needed. I donno but thats where i always get stuck on the unrevoked method. Now on the toast method I get stuck also on the bootloader screen. This time though, i get a message saying something like "main version is older" and it gives me the option to rebot back to the phones desktop. I looking forward to tethering again and trying out new roms as well as helping others that may be in my same situation and can't find the answer they need. Have any of you guys rooted with 64 bit version of windows 7? Please help..
You need to do a manual install of the htc sync drivers. Goto device manager and right click on the one with an exclamation point and select install driver. Go manual with everything (sorry I'm on a bus replying from memory, can't remember the specifics). Find where the htc sync installed to and select the drivers from there. If all goes well, this will install your adb drivers so that your phone can talk to your pc.
The main version older issue has to do with having the wrong PC36IMG.ZIP file loaded on the sd card. Toast's is old. I think the one whitslack posted is good. "How to start over" in the development forum.
Sent from my PC36100 using XDA App
so this android 1.0 needs an adb driver? When the phone is hooked up with usb debug on it shows an adb device in the device mngr. Well i'll try that and get back to you. Thanks for the reply.
Just tried, none of the drivers in those folders work for the android 1.0 device. Any other thoughts? If I update to froyo, do you think the new root method will be easier?
Don't update via OTA from Sprint. There is currently no way to root Froyo.
Did you look at whitslacks root method? I never used Unrevoked since it is not a full root (no nand unlock).
Sent from my PC36100 using XDA App
I gained root access with Windows 7 64 bit using the link in my signature.
unrevoked3 will give you root access and nand unlocked.
if you're going to use unrevoked3 go to their web page and download the usb drivers from them, just follow their directions. i had no trouble, widows 7 premium 64 bit. i'm sure you will be able to root just fine with your computer(s).
after you get root access, run unrevoked forever.
Jim M said:
unrevoked3 will give you root access and nand unlocked.
if you're going to use unrevoked3 go to their web page and download the usb drivers from them, just follow their directions. i had no trouble, widows 7 premium 64 bit. i'm sure you will be able to root just fine with your computer(s).
after you get root access, run unrevoked forever.
Click to expand...
Click to collapse
How sure are you unrevoked unlocks NAND?
It only unlocks it long enough to flash a recovery then NAND relocks
Without a real full NAND unlock a lot of custom ROM's wont run right and cause issues.
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.
I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App
I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App
android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.
Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.
Ok so im tryin to root my htc evo. Ive watched sooo many videos and read so many forums about how to do it. And i cant figure it out... Ive tried with a mac with unrevoked. It says I dont have to download anything to the phone,and when it runs it goes good till it reboots, and on the unrevoked screen it says waiting for root.. Phone restarts like normal.. Ive tried with windows, downloaded hboot. But im not sure I know how to install the boot drivers to my phone... But they say its updated. I run unrevoked and it ends up on the same screen. Waiting for root. Then ive read u need to replace a file on your phone but other people have said it will brick ur phone.. Im totaly lost. I need help tryin to figure this out.. Also had a question. Could it be because of the update sprint put out with all that extra bs like blockbuster and kindel and that stupid game nova on the update the reason why i cant root my phone?? Pls if some one can help me like step by step or the best way to go about it... I am a newbi... Help pls
theres a very good well written thread in the dev section that covers every software version and how to root.
to root in windows with unrevoked (i think there is a new version) you will need to install the updated hboot drivers in windows, linux requires no extra drivers to install
krazyfoo said:
Ok so im tryin to root my htc evo. Ive watched sooo many videos and read so many forums about how to do it. And i cant figure it out... Ive tried with a mac with unrevoked. It says I dont have to download anything to the phone,and when it runs it goes good till it reboots, and on the unrevoked screen it says waiting for root.. Phone restarts like normal.. Ive tried with windows, downloaded hboot. But im not sure I know how to install the boot drivers to my phone... But they say its updated. I run unrevoked and it ends up on the same screen. Waiting for root. Then ive read u need to replace a file on your phone but other people have said it will brick ur phone.. Im totaly lost. I need help tryin to figure this out.. Also had a question. Could it be because of the update sprint put out with all that extra bs like blockbuster and kindel and that stupid game nova on the update the reason why i cant root my phone?? Pls if some one can help me like step by step or the best way to go about it... I am a newbi... Help pls
Click to expand...
Click to collapse
Umm have you checked to see if you have a modified recovery? If you ran unrevoked you are probably rooted you just don't realize it. Root is just a certain access to the phone - nothing visual. Hold down the volume down key when you are booting and do you get into a greenish recovery menu? If so - you are rooted and can install custom roms.
Just look thru your Apps and if you see an App called SuperUser, you are rooted (this is if you used Unrevoked 3)
i think you might have the upgraded hboot, which unrevoked doesnt work on. i am in the process of writing a mac tutorial. pm me or email me and i will try to help you...
Dude you answered your own question. I'ma super noob and i know that if you accepted that OTA (over the air) 3.70 update that installs all that extra nonsense you cant root by unrevoked right now. You can do it using adb shell but i wouldnt recommend it. Its a lil confusing.
Check your phone. Hit menu>settings>about phone and look at your software number. If it says 3.70 your currently out of luck...
BTW find out which hboot you have too. Power off then Hold the power and volume down button til a white screen appears. The second line should say Hboot 0.97.00 or 2.02 or 2.10.
A 2 anything means you have to wait.
Simple...
Phillysphinest1 said:
Dude you answered your own question. I'ma super noob and i know that if you accepted that OTA (over the air) 3.70 update that installs all that extra nonsense you cant root by unrevoked right now. You can do it using adb shell but i wouldnt recommend it. Its a lil confusing.
Check your phone. Hit menu>settings>about phone and look at your software number. If it says 3.70 your currently out of luck...
BTW find out which hboot you have too. Power off then Hold the power and volume down button til a white screen appears. The second line should say Hboot 0.97.00 or 2.02 or 2.10.
A 2 anything means you have to wait.
Simple...
Click to expand...
Click to collapse
doesnt mean you have to wait. just takes a bit more work to root.
I am getting a G2 in the next few weeks and I'm coming from a rooted G1. I have been reading about the G2 and root ever since the first way to root it was available with VISIONary, but now it seems that we(the community) have found out that the old way to root was unsafe and "fake" and now every one uses GFree. I am planning to root the phone the INSTANT that it is out of the box, just gonna enable debugging in the settings then root it with GFree. Is there anything I should know before rooting with GFree? And how safe is it? Has anyone had any bricks with it? I'm not really a noob to cell phone modding if anyone is wondering, I used to mod Motorola's back in the day before Android was around, and I rooted my G1 the manual way. I already have ADB set up for my G1(the whole Android SDK rather,) so I'm guess that all I have to do is plug in the G2 to the computer and if needed, Windows will install the correct drivers automatically then I can root it with rage and GFree?
And thank you for anyone that helps me!
If you already have ADB set up you will just have to load the drivers for the G2 onto your computer, they easy way would be to just download HTC Sync to your home computer and when you hook the phone up the first time it will install the correct drivers, although the HTC Sync program wont actually work with the G2 because its sense based and the G2 is not it will still install the proper drivers for you. As far a gfree it is the safest way to root your G2, although I havent seen any bricks from the gfree method I have seen a few phones stuck in boot loops but usually theres a fix for it because gfree will usually get the phone to S-off stage before any problems arise.
For more info read this:
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
and this:
http://forum.xda-developers.com/showthread.php?t=855764
Read the entire thread even if its long it will benefit you in the long run, if you run into any problems more than likely they have already been solved somewhere in the thread. I always read the enitre thread before trying any mods to my phone.
Not to be a debbie downer but you may want to consider waiting a little bit before rooting, unless there is something about the phone that makes it unsuitable for your use out of the box. You may have a problem with the phone, a result of manufacturing problems or damage during shipment that may not show up until you've used it for a bit. My original G1 died a week after I got it, I had to take it back to the store where they gave me a replacement right away (That G1 still works after >2 years of daily use). If your phone is unmodified you will have a much easier time returning or exchanging it if you need to. BTW I waited about 3 weeks before I rooted my G2.
The gfree method is indeed safe, the problem most people seem to have with it is getting ADB working. I have not heard of any bricks with the method, I personally used it on two different G2s (mine and my brothers) and my wifes MyTouch 4G.
If you are already familiar with ADB you are already ahead of the curve. Though even if you have ADB up and running you may well need a different driver before ADB can connect to the G2.
The process is pretty solid and there is a lot of info here in case you run into issues but I don't think that's likely.
BTW when you are at the point where you want to install a recovery you might want to look at this thread: http://forum.xda-developers.com/showthread.php?t=902493 if you are a G1 user you are probably already familiar with flash_image.
joemm said:
If you already have ADB set up you will just have to load the drivers for the G2 onto your computer, they easy way would be to just download HTC Sync to your home computer and when you hook the phone up the first time it will install the correct drivers, although the HTC Sync program wont actually work with the G2 because its sense based and the G2 is not it will still install the proper drivers for you. As far a gfree it is the safest way to root your G2, although I havent seen any bricks from the gfree method I have seen a few phones stuck in boot loops but usually theres a fix for it because gfree will usually get the phone to S-off stage before any problems arise.
For more info read this:
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
and this:
http://forum.xda-developers.com/showthread.php?t=855764
Read the entire thread even if its long it will benefit you in the long run, if you run into any problems more than likely they have already been solved somewhere in the thread. I always read the enitre thread before trying any mods to my phone.
Click to expand...
Click to collapse
raitchison said:
Not to be a debbie downer but you may want to consider waiting a little bit before rooting, unless there is something about the phone that makes it unsuitable for your use out of the box. You may have a problem with the phone, a result of manufacturing problems or damage during shipment that may not show up until you've used it for a bit. My original G1 died a week after I got it, I had to take it back to the store where they gave me a replacement right away (That G1 still works after >2 years of daily use). If your phone is unmodified you will have a much easier time returning or exchanging it if you need to. BTW I waited about 3 weeks before I rooted my G2.
The gfree method is indeed safe, the problem most people seem to have with it is getting ADB working. I have not heard of any bricks with the method, I personally used it on two different G2s (mine and my brothers) and my wifes MyTouch 4G.
If you are already familiar with ADB you are already ahead of the curve. Though even if you have ADB up and running you may well need a different driver before ADB can connect to the G2.
The process is pretty solid and there is a lot of info here in case you run into issues but I don't think that's likely.
BTW when you are at the point where you want to install a recovery you might want to look at this thread: http://forum.xda-developers.com/showthread.php?t=902493 if you are a G1 user you are probably already familiar with flash_image.
Click to expand...
Click to collapse
Ah thanks guys! I'll just follow the instructions in the wiki.
Ok, I have some more questions, if I get stuck in a boot loop when I first root it with GFree then I should be already S-OFF so all I have to do is boot into fastboot and flash CWM to the phone then do a wipe and flash a good ROM? And if so, do I have to flash that new HBOOT that is optional in the XDA Wiki in order to flash the recovery via fastboot? And when I root my phone, I want to jump strait into CM7, so for my first recovery that I flash, can it be the new 3.0+ recovery? Also if I get stuck in the boot loop, can I flash the 3.0+ one then then wipe it and flash a new ROM or does it have to be with the old 2.0 recovery? Sorry for all the questions, I have looked some stuff up myself, but I just want to double check with someone that knows what he's doing or has done it before.
KoolKidsKlub said:
Ok, I have some more questions, if I get stuck in a boot loop when I first root it with GFree then I should be already S-OFF so all I have to do is boot into fastboot and flash CWM to the phone then do a wipe and flash a good ROM? And if so, do I have to flash that new HBOOT that is optional in the XDA Wiki in order to flash the recovery via fastboot? And when I root my phone, I want to jump strait into CM7, so for my first recovery that I flash, can it be the new 3.0+ recovery? Also if I get stuck in the boot loop, can I flash the 3.0+ one then then wipe it and flash a new ROM or does it have to be with the old 2.0 recovery? Sorry for all the questions, I have looked some stuff up myself, but I just want to double check with someone that knows what he's doing or has done it before.
Click to expand...
Click to collapse
Yes you need to have the engineering HBOOT to use fastboot to flash your recovery.
raitchison said:
Yes you need to have the engineering HBOOT to use fastboot to flash your recovery.
Click to expand...
Click to collapse
Alright, then how would I recover from a boot loop if I just rooted with GFree? Because if I just rooted with GFree, I would have to reboot and it would then get stuck in a boot loop before I could even flash the new HBOOT, right?
raitchison said:
BTW I waited about 3 weeks before I rooted my G2.
Click to expand...
Click to collapse
LOLz, I rooted my G2 the night it was shipped to me, probably within the first hour after playing around with the stock setup.
How would I recover from a boot loop if I just rooted with GFree? Because if I just rooted with GFree, I would have to reboot and it would then get stuck in a boot loop before I could even flash the new HBOOT, right? Or with GFree, do you not get a boot loop? From what I have seen, people are getting boot loops if they tried with VISIONary or an older tutorial that uses Rage, as in not the one thats on the Wiki.
All I can say to this thread is that the following guide worked flawlessly for me:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
dustrho said:
All I can say to this thread is that the following guide worked flawlessly for me:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
Yes, that is the tutorial that I am going to use to root my G2 when I get it, I just want to know if anyone has bricked with it or had a boot loop with it. Has any one? And when it says to install ROM Manager to get the CWM on the phone and do a backup, I just wanted to install the new 3.0+ version of it that DOESN'T come with ROM Manager so I can jump strait to CM7 as my first ROM, can I? I was just going to flash the new 3.0+ recovery with the one here: http://forum.xda-developers.com/showthread.php?t=902493
KoolKidsKlub said:
And when it says to install ROM Manager to get the CWM on the phone and do a backup, I just wanted to install the new 3.0+ version of it that DOESN'T come with ROM Manager so I can jump strait to CM7 as my first ROM, can I? I was just going to flash the new 3.0+ recovery with the one here: http://forum.xda-developers.com/showthread.php?t=902493
Click to expand...
Click to collapse
Yes, after you successfully root your phone you can install CWM 3.0+ and then install CM7 if you want.
dustrho said:
Yes, after you successfully root your phone you can install CWM 3.0+ and then install CM7 if you want.
Click to expand...
Click to collapse
Ah alright, thank you! Sorry for all the questions, but I just wanted to be sure; I search everything I want to know before I ask questions. I'm coming from a G1 which is pretty old, you have no idea how excited I am to have a current Android phone that will actually run stuff smoothly, I just don't want to brick it when I first get it.
KoolKidsKlub said:
I am getting a G2 in the next few weeks and I'm coming from a rooted G1.
Click to expand...
Click to collapse
I am in the same boat. The new phone is sooo much faster!
joemm said:
the HTC Sync program wont actually work with the G2 because its sense based and the G2 is not it will still install the proper drivers for you.
Click to expand...
Click to collapse
Can we uninstall HTC Sync afterwards? Will the drivers stay around?
dustrho said:
Yes, after you successfully root your phone you can install CWM 3.0+ and then install CM7 if you want.
Click to expand...
Click to collapse
Cyanogenmod has their own instructions for rooting. Which is safer or more recent?
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting#Gaining_Temporary_Root_Access
endolith said:
I am in the same boat. The new phone is sooo much faster!
Can we uninstall HTC Sync afterwards? Will the drivers stay around?
Cyanogenmod has their own instructions for rooting. Which is safer or more recent?
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting#Gaining_Temporary_Root_Access
Click to expand...
Click to collapse
Use the XDA Wiki, I've seen issues with people using the Cyanogen Wiki.
Sent from my HTC Vision using XDA Premium App