Related
Edit: This guide is for EXPERIENCED users ONLY! For less experienced users please check UBERROOT easy full Root, S-OFF, SuperCID AND SIM UNLOCK for DZ/G2/DHD inc Voda .
Remember to always read and research before rooting! Discussion can be found starting on post #101 - #118 ~TheRomMistress
__________________________________________​
Please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
To get full write access to the Desire Z, we now have an Engineering HBOOT which was posted by MrPaveL (Thanks for that!).
To get your device to the engineering hboot stage [this is not full radio S-OFF, but 99% of people won't need radio S-OFF], please follow the guide below.
If you want full Radio S-OFF, SuperCID or want to remove the simlock on your phone, please follow this guide on instead. Once you have full Radio S-OFF you can use any Desire Z HBOOT and still have access to flash ROMs etc.
Credit goes out to scotty2, and all of the wonderful folks at #G2ROOT!
Donate to scotty2 (for root): [email protected] (PayPal)
This guide was derived from the guide for the G2, created by unrevoked512 on http://forum.xda-developers.com/showthread.php?t=833965. Also many thanks to vro25 for improvement suggestions.
You will need the following files:
VISIONary r14
wpthis-Z.ko MD5 c73c5e77c91d306c418983c002b60b93
hboot_7230_0.84.2000_100908.nb0 MD5 2ce1bdd5e4c1119ccfcecb938710d742
Step 1
Download and run VISIONary r14
Leave everything uncheck and click "temp root" now.
Once that's done click "Attempt Permroot Now!"
You now have permaroot.
Step 2
Push the files wpthis-Z.ko and hboot_7230_0.84.2000_100908.nb0 to /data/local/
Note: You might want to verify the MD5 sums, particularly for the hboot file, as if your download was corrupted, the file will brick your phone.
Step 3
Open a terminal on your phone, or open an adb shell from your computer.
Step 4
Code:
$ su
# insmod /data/local/wpthis-Z.ko
Note: make sure your screen is on before doing this as it will raise a root request on your phone (if you haven't previously granted it) - click ok on your phone to grant root.
It should return:
Code:
init_module 'wpthis-Z.ko' failed (Function not implemented)
That is good.
Step 5
FINAL WARNING: THIS STEP COULD SEVERELY DAMAGE YOUR PHONE. USING THE INCORRECT FILE COULD CAUSE IRREPARABLE DAMAGE, MAKING YOUR PHONE NOTHING MORE THAN A BRICK.
That noted, if you would like S-OFF, go ahead and run this command in your terminal.
Code:
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Step 6
I think this is optional, but there are controversial opinions at the moment. In any case it will not hurt to run
Code:
# sync
to make absolutely sure everything will be saved.
Now reboot your phone gracefully and check that everything sticks.
Step 7 (optional)
This step is optional, if you want to install Clockwork Recovery.
Download ROM Manager from the market and install Clockwork, telling it that you have an HTC G2 when it asks. It will work without problems on the Desire Z.
Step 8 (optional)
This step is optional if you want to install an overclocked kernel. You might want to do a nandroid backup first, in case you want to go back later (just restore boot).
This overclocked kernel seems to crash the phone after Youtube videos are played in fullscreen. This issue is being investigated, but could take a while to resolve, since HTC hasn't released the actual DZ kernel source...
I have now recompiled the overclocked kernel for the Desire Z (all credit goes again to coolbho3000 for publishing the source!), to get the FM Radio to work as well. To get it to work please follow the guide on http://forum.xda-developers.com/showthread.php?t=834219, but instead of the zImage posted there (which breaks FM Radio on the Desire Z), get the one from http://www.opencodes.org/node/14 . You still need to use the bcm4329.ko file from the other thread. Also note that this will change your kernel version to 2.6.32.17 (instead of 2.6.32.21 stock). Please blame HTC for not releasing the newest kernel source. In any case I have not spotted any disadvantages...
So far I have not spotted any problems with this kernel, but if you do, let me know.
PS Bacon-bits by cyanogen do not fully work on the DZ. It won't boot with that ramdisk and the lights hack seems to fail as well. It is probably safest to wait for a full CM release, but this guide gets you 90% of bacon-bits.
stridger said:
Hi all,
I have just managed to get clockwork recovery work on the Desire Z. It's a bit hacky at the moment, and will probably get much easier in the due course. I am not going to post every little step that you can find out by googling, and please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
The reason it is this hacky is that we do not have an engineering bootloader for the Desire Z yet.
Download wpthis-Z.ko and wpthis-pre-OTA.ko from
http://content.modaco.net/dropzone/wpthis-Z.ko and
http://unforgiven512.udderweb.com/downloads/wpthis-pre-OTA.ko and put them in /data/local on the phone.
Download newest version of ROM Manager
Disable write protection via wpthis-Z.ko
Flash clockwork recovery from ROM Manager
Reboot into recovery
Make a nandroid backup !!!!!
Mount /data in Clockwork
Use wpthis-pre-OTA.ko in recovery to disable write protection.
You now have a fully working recovery. (note you will need to use wpthis-pre-OTA.ko step everytime you boot into recovery and want to write something from recovery [not needed for nandroid backups])
Click to expand...
Click to collapse
Your a genius dude Keep up the good work
We need quality devs like you to get this party started
JD
As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.
schriss said:
As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.
Click to expand...
Click to collapse
I urge you not to do anything in this direction, if you haven't even got permroot yet. Look at the G2 permroot forums, where all of these things are answered. The error is supposed to appear. Please be very careful if you don't want to end up with a brick.
I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
I guess I wait...
Sent from Desire Z
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
schriss said:
I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
Click to expand...
Click to collapse
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.
stridger said:
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.
Click to expand...
Click to collapse
Exactly, that's what the logic sugests.
I was hoping to:
Temp root with Visionary (already done)
Disable write protection via wpthis-Z.ko
then try "sync" command to write changes.
Then, after reboot, I should have perm root and nand on read-only.
But I got scared by the errors I got after I disabled write protection.
g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
amazing,
thanks for reporting,
good news
g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
You've probably still got a G2 hboot, right ? Like the G2 eng hboot ? If so, then it's still really a G2 running a Desire Z ROM. But I can't answer your main question, I'm sure someone else will be able to though.
g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...
I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.
fastludeh22 said:
I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.
Click to expand...
Click to collapse
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked
Sphaerophoria said:
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked
Click to expand...
Click to collapse
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...
stridger said:
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...
Click to expand...
Click to collapse
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?
stridger said:
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...
Click to expand...
Click to collapse
i tried the G2 method for obtaining clockwork and it didn't work it says it flashed from the app but when i try to backup rom im still on the stock recovery.. would u recommend i try the D-Z method?
fastludeh22 said:
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?
Click to expand...
Click to collapse
wp is definately off in recovery but the problem is probably "your update-binary or updater-script (don't use update-script)" in koush's own words. Anyways i hope we find a way around this soon
FYI: Method updated to reflect the fact that we now have an ENG hboot.
stridger said:
Follow G2 guide on http://forum.xda-developers.com/showthread.php?t=833965, but instead of wpthis-*.ko use the file http://content.modaco.net/dropzone/wpthis-Z.ko. ALSO DO NOT FLASH THE hboot-eng.img INSTEAD USE THE FILE ON http://www.multiupload.com/4U9P14R86Y. IF YOU FLASH THE WRONG FILE IT COULD POTENTIALLY BRICK YOUR DEVICE! .
Click to expand...
Click to collapse
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.
steviewevie said:
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.
Click to expand...
Click to collapse
Yes, I agree and would like to do that, but wanted to ask unforgiven512 first to integrate it into his guide, as it seems to much overhead to maintain two guides of essentially the same procedure...
Now both devices have a fully working eng bootloader, we really need to merge these two forums into an "HTC VISION" one!
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
im on redux 1.1.2 and wanted to make the keyboard manager (found here working.
however moving the .apk from /data/app/ to /system/app doesnt work for whatever reason. i tried root explorer and super manager as well.
cutting out the file and trying to past it in the other folder it seems to work, gives no error message but i cant see the file being moved and when i navigate back to /data/app its still sitting there.
of course, root access is enabled, so that cant be the problem here.
does anyone know how such a basic and simple function continously fails? im absolutely by this and need a solution asap.
Do you have write access to /system?
Year nothing is wrong with root explorer. To test try moving a file from /data/app to sdcard.
But in order to write to /system you need your bootloader to be s-off, and it's surprising how many people don't know this and just try using such apps without thinking.
check that you have enabled "remount as R/W"
mortenmhp said:
Year nothing is wrong with root explorer. To test try moving a file from /data/app to sdcard.
But in order to write to /system you need your bootloader to be s-off, and it's surprising how many people don't know this and just try using such apps without thinking.
Click to expand...
Click to collapse
you are onto something. checked my bootloader and that thing is s-on
i could swear it used to be s-off when i checked last time, but yes that was some time ago.
so now its s-on and i need it to be s-off.
found http://alpharev.nl/ and there a hboot reflash utility but ... well i download on ubuntu and all it gives me is an very useless .iso file. extracting contains no file i actually can run.
the website guide couldnt be any worse, black background and small white font, its not what im looking for on a lazy sunday
so in short: is there an easy + fast way to get a s-on device s-off. easy and fast means no nandroid backup, no normal backup, no factory resets or whatever.
mclaren2 said:
you are onto something. checked my bootloader and that thing is s-on
i could swear it used to be s-off when i checked last time, but yes that was some time ago.
so now its s-on and i need it to be s-off.
found http://alpharev.nl/ and there a hboot reflash utility but ... well i download on ubuntu and all it gives me is an very useless .iso file. extracting contains no file i actually can run.
the website guide couldnt be any worse, black background and small white font, its not what im looking for on a lazy sunday
so in short: is there an easy + fast way to get a s-on device s-off. easy and fast means no nandroid backup, no normal backup, no factory resets or whatever.
Click to expand...
Click to collapse
.iso is an image file, so you need to burn it onto a cd/bootable use-stick and then boot from it.
Tillus said:
.iso is an image file, so you need to burn it onto a cd/bootable use-stick and then boot from it.
Click to expand...
Click to collapse
and for what reason? will it boot me into some cmd prompt kinda thing where i have to enter some command lines?
and if so which ones? wil i be able to keep all my data on the desire?
mclaren2 said:
and for what reason? will it boot me into some cmd prompt kinda thing where i have to enter some command lines?
and if so which ones? wil i be able to keep all my data on the desire?
Click to expand...
Click to collapse
First of all, do a nandroid backup, then you keep your data.
It won't give you a command line, it will automatically start the s-off-program. You basically connect your phone, hit Enter, then wait a few minutes and dont touch anything.
But I really recommend some reading about in this forum about this. You might need to get fastboot running on your computer to flash a new recovery, so make sure you have all needed drivers and the recovery image (of the same recovery you are using now, otherwise you probably can't restore nandroid) handy before you start.
But I really recommend some reading about in this forum about this. You might need to get fastboot running on your computer to flash a new recovery, so make sure you have all needed drivers and the recovery image (of the same recovery you are using now, otherwise you probably can't restore nandroid) handy before you start.
Click to expand...
Click to collapse
i looked arround a bit but found nothing really usefull. googling for fastboot even brings up wrong results things which have definitely nothing to do with htc desire or s-off.
is fastboot that adb thingy i need to get to work and which is said to not work properly on ubuntu 10.10? then i ditch all that stuff and will forget about it.
the lack of answers seems to suggest that no one is really sure if it will work or not.
seems to be a big risk and not worth wasting any more time.
thanks for your help nevertheless.
Well, search for the S-OFF guide in the Developmenet section.
Basically, you just wait. That's it.
davebugyi said:
Well, search for the S-OFF guide in the Developmenet section.
Basically, you just wait. That's it.
Click to expand...
Click to collapse
no its just difficult to find a s-off guide in this forum if the search function wont accept s-off entered
anyway found me a nice guide there:
http://www.addictivetips.com/mobile/gain-s-off-on-htc-desire-gsm-with-alpharev-1-8-custom-hboot/
thats how a guide should be written imho. now im gonna give it a try as it sound simple ennough there.
success
now lets see if i can move the keyboard manager apk to /system/app
works as well.
mortenmhp said:
Year nothing is wrong with root explorer. To test try moving a file from /data/app to sdcard.
But in order to write to /system you need your bootloader to be s-off, and it's surprising how many people don't know this and just try using such apps without thinking.
Click to expand...
Click to collapse
You just answered to my question which bothered me for q while now. Thanks a lot. Thing is you can't know these things unless someone answers or you just stumble upon it, just like me now. Thanks again matey.
Sent from my HTC Desire using XDA App