Related
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
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.
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
OK before i get SEARCH.. I did and here is what i have looked at so far (i am 3+ hours into my search)...
http://forum.xda-developers.com/showthread.php?t=838484
http://forum.xda-developers.com/showthread.php?t=842495
http://forum.xda-developers.com/showthread.php?t=905261
ANd a few others that link back to one of those 3.
This is not my phone. I am helping my buddy who attempted to perma-root his phone using Visionary+ 14. I have an evo, and several other android phones and understand the basics of ADB and how to do most this stuff.
After he applied the patch, we are stuck on the white HTC screen. The problem is, it does NOT have the ENG SPL, we are still s-ON and still have stock recovery.
Here is what i have attempted so far:
download and tried to have it reload PC10IMG.zip - Got an error that said the version i was trying to install was older than the one i already had. I downloaded the latest one i could find.
Since i can get into the stock recovery, i downloaded and tried to use update.zip to reinstall things correctly, but that didnt work. It didnt error out and looked like it installed correctly, but still just stuck at the white HTC screen.
I cannot access ADB (at least any way that i know how).
Yes, i have the correct USB drivers installed and ADB is working as i have accessed it for other phones.
Here is the phone stats:
VISION PVT SHIP S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_m
eMMC-boot
Sep 2 2010, 17:59:38
I cannot find the right RUU to give that a try either. I have found a few that MIGHT be right, but i dont want to mess it up more by flashing the wrong thing (if this would even help.. i dunno)
ANY HELP WOULD BE REALLY APPRECIATED!!!!
Anyone?? Help????
frettfreak said:
this is why people post in the dev forum when they arent supposed to.... cause NOTHING happens if you post in q&a...
Anyone?? Help????
Click to expand...
Click to collapse
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
ianmcquinn said:
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
Good point!! Sorry.. just a little anxious. Dont want to tell him his phone is bricked....
Also... maybe no one responded cause i am a tard.... its s-ON still, not S-OFF
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Sorry for the confusion and pushy-ness and thanks for your help!
frettfreak said:
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Click to expand...
Click to collapse
Well, like I said before, this is the type of semi-brick that people seem to be stuck in when Visionary fails and I haven't seen a working solution. When I said to leave it at the HTC screen, it was just something mentioned in the how to recover semi-brick thread you linked to in the original post. Unfortunately, if that didn't work, you might by out of options.
EDIT: And oh, I forgot to mention about fastboot. Although it might seem like fastboot detects the phone properly, you cannot actually use it to flash anything unless you have the engineering HBOOT, so that doesn't help any.
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
lainvalenajr said:
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hmmm how do I do that? Is there a different way other than adb? I will check again but pretty sure I don't have adb access (I think this is what the eng spl does but I am just guessing here) does fastboot allow Me to do anything like that?
The other day my phone just decided it wanted to get stuck on the HTC loading screen without being able to get into recovery and flashing back to a previous point, I had to go back to square 1 and flash back to stock.
So this morning I'm going about re-rooting and re-flashing a rom etc. However I have tried to download unrevoked 3 and it says it can't find the page when i go to download, does anyone have a different download for it.
A second question, I debranded my phone will it still be debranded or re-branded? is there anyway to find out?
Which version has your hboot? Because if it's high enough, you should use revolutionary:
http://revolutionary.io
There you get rooting plus S-OFF in two very easy steps.
SwiftKeyed from dGB with Transparent XDA App
its 0.93.0001 any idea about the debranding issue?
Well unrevoked could do it, but go ahead and use revolutionary instead. You'll get root and s-off.
It's pretty much unrevoked and alpharev combined, and it has been updated to support the newest hboot versions.
mortenmhp said:
Well unrevoked could do it, but go ahead and use revolutionary instead. You'll get root and s-off.
Click to expand...
Click to collapse
Thats the issue, I can't actually download unrevoked but I'll go ahead and use revolutionary. Thanks for the help.
SxcKieranGrr said:
Thats the issue, I can't actually download unrevoked but I'll go ahead and use revolutionary. Thanks for the help.
Click to expand...
Click to collapse
I did get that part and that was why I supplied you with another tool to use instead. I simply wanted to inform you that i case unrevoked would come back up that hboot was supported.
mortenmhp said:
I did get that part and that was why I supplied you with another tool to use instead. I simply wanted to inform you that i case unrevoked would come back up that hboot was supported.
Click to expand...
Click to collapse
Ok thankyou. I've just noticed my phone is resetting itself alot with the stock rom. I always thought this was the rom I had running that it was unstable. I guess this means there's an issue with the phone. I think it's over heating, is this an issue i need to send off to HTC for?
Sounds like a motherboard issue to me
Swyped from my CM7.1 Desire using XDA Premium App