Rooting with Visonary 14 killed me phone - G2 and Desire Z Q&A, Help & Troubleshooting

Rooting with Visonary 14 killed me phone - G2 and Desire Z Q&A, Help & Troubleshooting

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.

Related

[Q] need help installing gingerbread keyboard

i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused

Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this

just done the hboot hing and at the top of screen it says
vision pvt ship s-on

hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?

steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.

steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.

im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems

hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685

OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1

try wiping all the caches...

Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

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.

[Q] Is rooting a G2 with GFree safe?(And what should I know before rooting?)

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

How do I get S-Off

I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.

ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.

What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z

steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside

I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z

steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...

schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App

Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul

Confirm that I bricked my phone please?

... before i shell out for another phone because I'm an idiot.
Anyway, I'd been doing some reading and had a thin history of rooting with my G1 which went rather well.(in that I never bricked it)
I did the same with my phone now, the G2. I got it when it first came out, got comfortable with it and finally decided to root it. I guess I didn't do enough research because I used Visionary to root and I believe I am now bricked. I have been up and down the forums for a solution or even a confirmation that I'm bricked for the last 4 hours. I kid you not. I even went into different phone sections in case I found something that could help but zilch.
So yell at me for not doing enough research and reading before i started rooting, but don't yell about this same question being asked over and over again.
Anyways, I can only get to the first white "HTC" screen and freezes.
I can get to HBOOT and that says:
Vision PVT SHIP S-ON
H-Boot-0.02.0000
Microp-0425
Radio-26.03.02.26_M
cMMC-boot
HBOOT
If I try to go to recovery it goes to that little black phone with the red traingle.
If I try to go to factory reset it goes to a green circle with a load bar that just looks like it's working but then it goes back to the white HTC screen and stays.
I have SDK and even though my computer recognizes that an Android 1.0 device is attached, when I "adb devices", nothing is listed.
So what's my diagnoses pros?
Thanks for any help or any response at all in advance.
Dea.

Its not looking good my friend, what exactly have you done to your phone so far?
If it is stuck in a boot loop and you have S-on the only possible thing you can to do fix it is flash the stock PC10IMG, but this will only work if you had the pre-OTA rom on your phone 1.19 and I really doubt that you did. If you had the wifi calling app you had the OTA 1.22 rom not the 1.19 rom. Trying to flash the stock PC10IMG onto your phone if it had the OTA rom 1.22 will cause it to do exactly what is happening now.

There's a file called "pc10img.zip" (the default firmware) that can be placed in the root of your SD, and should automatically be detected and offer to start flashing. I think this is how I recovered my phone which was in a similar state. Someone here could probably link you to the proper file (I'm sure there's different versions for DZ and G2). Good luck...I think you can probably save it.
I'm pretty sure mine was doing the same thing yours is, and I'm happily rockin' CM7 now, and loving it more than ever.

@joemm, Well I had 1.22 on there since I remember having wifi calling. I know you advised me not to but I might look into the PC10img.zip just because it can't get much worse than this honestly.
@hexapus, thanks for the advise. I'll have to look for my sdcard adapter first though. can't seem to find it at the mo'.
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"

dealunae said:
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"
Click to expand...
Click to collapse
Thats because its looking for the file named PC10IMG.zip, this is the only file name it will load and it must be on the root of your sdcard.
Check your PM i will message you right now.

This is a link to a page containing instructions for a manual update to 1.22 and a link to the update.zip. Maybe this will work if all else fails by applying the OTA update again.
http://www.talkandroid.com/20232-tutorial-manually-update-t-mobile-g2-remove-google-goggles/

You might be able to hex edit the pc10img.zip so it thinks its version 1.22.
Sent from my T-Mobile G2 running Cyanogenmod.

I also had this same issue, in that I tried visionary and had the same issue. I took mine to the tmobile store and let try to fix it, which they couldn't, and when they asked me what happened I said I was uninstalling an app that was a live screen because it was acting werid. Because I was still under warrenty they help me get a new one sent to me.
Worked out for me, now I read and read and read more. I am rooted via rage and gfree but still run stock.
Good luck
Sent from my T-Mobile G2 using XDA App

Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)

dealunae said:
Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)
Click to expand...
Click to collapse
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!

It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App

joemm said:
It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?

EdKeys said:
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?
Click to expand...
Click to collapse
At this point for him I don't see how its gonna hurt to try, but in my experiences in this forum I have not seen anyone able to flash the update 1.22 .zip after being stuck in a S-On Bootloop. Its either gonna work or it wont let him flash it at all, so I really cant see how it could hurt to try. As far as the 1.19 rom it wont let him flash it because it will give a error that the main version is older.

EdKeys said:
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!
Click to expand...
Click to collapse
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!

dealunae said:
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!
Click to expand...
Click to collapse
OK, good luck! I hope that it, or something else, eventually works for you. Keep us updated....

So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.

dealunae said:
So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.
Click to expand...
Click to collapse
Lol... no need aha. If you have the basic concept of rooting you should be fine. Of course u just follow each step for rooting. Wish u luck
Sent from my HTC Vision using Tapatalk

You didn't fix the old one? The pc10img fix almost certainly would have cleared it all up.
Sent from my HTC Vision using XDA App

Develop Bugs

welcome