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!
Hello people,are okay?
I'm wanting to downgrade z desire by following these steps:
http://forum.xda-developers.com/showthread.php?t=905261
But cant do the downgrade.I put the PC10IMG.zip I put the SD card, enter the bootloader using "adb reboot bootloader, start applying the RUU, but when finish the aply im get this mensage:
"main version is older!
Update Fail!
Press <Power> button to reboot "
Does anyone have an idea how I can downgrade to 1:34 without this mensage? My main objetive is to apply the root on desire z, but no have a way to apply root in version 1.72. My desire z came with version 1.34 but I did the update OTA to 1.72 without the root. Anyone have a way to I can apply the root? Thanks!
PS.: Sorry by english, im speak portuguese and used google translator to this mensage.
erickBR said:
Hello people,are okay?
I'm wanting to downgrade z desire by following these steps:
http://forum.xda-developers.com/showthread.php?t=905261
But cant do the downgrade.I put the PC10IMG.zip I put the SD card, enter the bootloader using "adb reboot bootloader, start applying the RUU, but when finish the aply im get this mensage:
"main version is older!
Update Fail!
Press <Power> button to reboot "
Does anyone have an idea how I can downgrade to 1:34 without this mensage? My main objetive is to apply the root on desire z, but no have a way to apply root in version 1.72. My desire z came with version 1.34 but I did the update OTA to 1.72 without the root. Anyone have a way to I can apply the root? Thanks!
PS.: Sorry by english, im speak portuguese and used google translator to this mensage.
Click to expand...
Click to collapse
I'm pretty sure that if you don't find the answer within that thread that you referenced then you can ask your questions there.
No, i cant post in my reference, i dont have 10 posts:
Please Read: New members (those with fewer than 10 posts) are not permitted to post to development-related forums. The developer forums are intended for experienced users and developers to discuss ways to improve technical aspects related to ROMs and Software. While you may be an expert, we ask ALL users to avoid posting questions about using or installing ROMs and software in the Development Forums. To encourage this new Users can read but not post in these forums.
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
This is the mensage when i do the reply.
erickBR said:
No, i cant post in my reference, i dont have 10 posts:
Please Read: New members (those with fewer than 10 posts) are not permitted to post to development-related forums. The developer forums are intended for experienced users and developers to discuss ways to improve technical aspects related to ROMs and Software. While you may be an expert, we ask ALL users to avoid posting questions about using or installing ROMs and software in the Development Forums. To encourage this new Users can read but not post in these forums.
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
This is the mensage when i do the reply.
Click to expand...
Click to collapse
I guess I should have know about that, sorry. I wish I could help you, but I have a G-2 and don't have any experience with that method.
I recently used this method successfully, so ill try and help.
I think it may have something to do with the step when you enter in your command prompt:
/data/local/tmp/misc_version -s 1.33.405.5
exit
This step should spoof your version number so you can install the earlier software. You also need to make sure you do have temproot before this step, indicated by the # sign as opposed to the $. I would suggest doing all the steps again, starting with pushing all of the files again. When you get to the above step, check to see that you dont get any errors. If it all works this time round, it should let you install the earlier rom.
Another thing would be to redownload all of the files again to make sure they are all fine, and none of them are corrupt. I actually used the files off the cyanogenmod wiki, which has the same steps as your link, but with a newer gfree. maybe that could be the problem. But definately do the steps again and keep an eye out for any reported errors.
I did all of the steps twice before it worked for me.
I can't get temproot. How you get it?
I can realize the 1-3 steps, but in 4 appears this mensage:
adb push psneuter /data/local/tmp
"cannot stat 'psneuter' : No such file or directory
The desire z without root or temroot no is not read only?
I cant do this step. Where you can get temproot to this?
Thanks!
Sorry by english, im speak portuguese and no english (used google translate)
Thanks to all helps!!
I can get root in my phone, and the problem is in my adb (SDK files).
I downloaded the SDK of android again, configured in my pc and it works fine!
Thanks to all!
Thanks to all helps!!
I can get root in my phone, and the problem is in my adb (SDK files).
I downloaded the SDK of android again, configured in my pc and it works fine!
Thanks to all!
please explain...???
i have the same problem as you, cant solve it..
thanks
helllooo there people of the XDA world.
i've rooted my phone and im using the stock htc ROM.
now i've got a few questions.
1) (although its too late to ask this question) - can i reverse the downgrading and rooting? i had a 1.75 firmware with 2.2.1(froyo). now i have a rooted 1.32 with 2.2(froyo). can i go back?
2) if i install a custom ROM, can i also do what i said in question 1?
3) i have ROM Manager installed, and when one first installs it, (s)he's suppose to choose the 'Flash ClockworkMod Recovery' option. Problem is, i've pressed this option and it says it can't connect to server!
i've tried it with my carriers internet and with WIFI, but it keeps saying it. does the country you're in matter? (maybe they're blocking certain IP addresses).
3.5) if there is no solution to question 3. is there a manual way to 'Flash ClockworkMod Recovery'?
:::::::::::::
awaiting answers
:::::::::::::
You need Eng S-OFF to flash CWM, I'm assuming you only have root. Check this guide.
CodeNameUnknown1 said:
helllooo there people of the XDA world.
i've rooted my phone and im using the stock htc ROM.
now i've got a few questions.
1) (although its too late to ask this question) - can i reverse the downgrading and rooting? i had a 1.75 firmware with 2.2.1(froyo). now i have a rooted 1.32 with 2.2(froyo). can i go back?
YES, just flash an older version, or go back to your backup-rom (also called NANDROID) you should always backup first when installing a new rom, you can do this easily in the ClockworkMod Recovery
2) if i install a custom ROM, can i also do what i said in question 1?
YES, same answer as for question 1
3) i have ROM Manager installed, and when one first installs it, (s)he's suppose to choose the 'Flash ClockworkMod Recovery' option. Problem is, i've pressed this option and it says it can't connect to server!
i've tried it with my carriers internet and with WIFI, but it keeps saying it. does the country you're in matter? (maybe they're blocking certain IP addresses).
Read the post above from Letom, that'll do the trick
3.5) if there is no solution to question 3. is there a manual way to 'Flash ClockworkMod Recovery'?
:::::::::::::
awaiting answers
:::::::::::::
Click to expand...
Click to collapse
Hope this helps, answers are in your quote
@letom: na, i have Eng S-OFF, but i didnt know about that post ... so thanks!
@Enjoy!: regarding the answer to question 1 -> my FW 1.75, and 2.2.1 OS wants rooted ofc, and thus i didnt do a nandroid....and also after downgrading .. i also didnt do a nandroid.
But im not taking about going back to a fresh 1.32 ROM (thats what i'd have if i restored using nandroid), im talking about going back to the stock ROM i had when i first brought the phone! the 1.75 FM with 2.2.1 Android OS. Can i go back to that?
:::another question:::
and say i didnt do a nandroid, and my phone gets damaged, ... , couldnt i just go to the bootloader and install PD98IMG.zip file and go back to my 1.32 non-rooted phone?
i went to the guide #letom gave me, and i downloaded it, went into bootloader, i choose the fastboot and click the .bat file in Windows.
command prompt came up and dissapeared in a flash...the phone restarted, and still, nothing ... although the download is v3.0.2.4, my ROM Manager is v3.0.1.4. so it didnt update ... any ideas?
Hi
Let me open this thread by saying that I have just bricked a DHD yesterday. So I guess I was a bit unprepared. It was nice on part of the repair centre to replace it under warranty. (I dont think they knew, because the bloody thing won't even boot, no matter what you did.)
So, to tell you what I did yesterday, I followed this tutorial to root the Desire HD: http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Rooting
I was already on 1.32.405.6, so I didn't need to downgrade.
I then gained Temp root access and then perma root access, as per tutorial
I DID NOT Flash the Engineering HBOOT (since it said its optional). Should I have dont this if I was installing a custom ROM?
Then, I followed this tutorial for Flashing Cyanongen. http://wiki.cyanogenmod.com/index.php?title=HTC_Ace:_Recovery,_Radio_and_CyanogenMod
Again, I did not Flash the radio. Is this absolutely necessary to flash a custom ROM ?
I successfully installed CM7 and booted. Then I decided to format the microSD card. It returned with a notification as, "Blank SD card" Clicking on the notificaiton would ask me to Format the card.Nothing happens.
I posted in another forum and someone asked if I made partitions ? This got me searching again and I then proceeded to make partitions with Clockwork Recover Manager
Another thing I want answered is if I should have created partitions on the microSD card or not ? At what stage should I create the partitions ?
What is the difference between ROM Manager and Clockwork Mod
Should I install a new kernel during Flashing ROM ?
I did a search via Google, There are hundreds of thousands of posts regarding rooting, but a lot of them use Visionary+ and then flash a ROM. I read earlier that this is not desirable. I can use adb on PC, no problem.
Any comprehensive definitive tutorial for rooting DHD and installing custom ROM
geek7899 said:
Hi
I posted in another forum and someone asked if I made partitions ? This got me searching again and I then proceeded to make partitions with Clockwork Recover Manager
Another thing I want answered is if I should have created partitions on the microSD card or not ? At what stage should I create the partitions ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1043160
http://forum.xda-developers.com/showthread.php?t=1043160
http://forum.xda-developers.com/showthread.php?p=11557769
http://forum.xda-developers.com/showthread.php?t=857537
Those should get you started.
Do not partition SD card, it is what caused your brick. Flashing ENG hboot is your own choice, you can choose to do it later with my one click tool (link in signature). It is not necessary to flash a custom ROM and/or radio. A ROM always comes with proper kernel, so you do not need to flash it separately. ROM Manager is just an interface for ClockworkMod, nothing more.
wnderinguy45 said:
http://forum.xda-developers.com/showthread.php?t=1043160
Click to expand...
Click to collapse
Ouuchhhhh .. came a day too late ....
I was one of the ones bricked
You cannot remove it. Just post something useful to general or discuss here. Koush is working on that recovery problem, but I would advice to stay away from the partitioning feature at all times.
Sent from my Desire HD using Tapatalk
more questions after reading Guide
WOW ,,,, thanks guys ...
Just finished reading the [GUIDE]How to flash a ROM onto your DESIRE HD [COMPLETE]. Wheew....
Now I have more questions . Thanks to anyone who answers.
Here we go
1.) I have a Vodafone branded DHD, with a boot animation splash screen and useless apps. Will I need a goldcard ?
2.) Is it OK to use Visionary+ to perma root for flashing ROM's ? I had read on some forums where they didn't approve of this method. Rather they said, use the adb command prompt. The Cyanongen guide even says that if you have Visionary+ installed, uninstall it before rooting .... /confused/
3.) To put it crudely, Radio S-ON is like a security check to see if the approved apps/software are being installed. Is that correct ?
Then what is ENG S-ON ?
4.) When you do a Permanent root (by Visionary+ or adb command prompt), doesn;t it automatically set Radio S-OFF. If it does, then why do we need to do radio S-OFF as in using the tool ?
5.) I see you are not using ROM Manager for wiping cache etc. Instead you are using Full-Wipe 1.3. Is it better than using Clockwork Recovery for doing a wipe of cache ?
6.) The Radio S-OFF and simunlock tool. Can it lock my handset, since its already officially unlocked ?
7.) Why would I flash the Radio... (last step before Flashing ROM). Is it only for getting a /possible/ battery performance or network strength ? If it is not actually required for the actual Flashing of ROM, I might leave it out. Network is pretty ****ty here anyway
Any help appreciated.
Thanks
1. Yes
2. Sure it is, the guide in Cyanogen is a bit.. Weird.
3. No. S-OFF in general is a setting that allows you to write to the internal memory (read+write rights). It also disables some version checks and so on. ENG S-OFF is a special case which enables fastboot commands. Those allow you to flash radios, splash screens and such easily via USB connection.
4. S-OFF is WAY more serious mod (like god mode) than permanent root. Visionary only gives you root, which basically gives you rights to do more stuff in Android.
5. Nah, I do not personally use that wipe.zip. It is useless in my opinion The feature in cwm does pretty much the same.
6. It does not lock your device.
7. It is not entirely necessary. But if you have crappy network, it is a very good reason to flash a radio, which will improve your signal quality. My advice, flash it.
Some more questions posted in the DHD rooting/flashing thread. If anyone feels to answer them ,,,,,, thanks
over here: http://forum.xda-developers.com/showpost.php?p=13106095&postcount=128
Hello there,
I am new to modding android devices so i just have a few questions to ask about my HTC Desire HD and installing (flashing?) the JellyTime (ROM?) software onto my phone.
I've read through lots of posts but there quite a bit of terminology that gets flung around which im not understanding but i think i know what i have to do.
But my main question are, since I'm running Android 2.3.5 Sense 3.0 rooting my phone has become quite hard for me as every program i look at says I need to downgrade. I read [How to] ROOT without the Hack Kit and I'm guessing "IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:" applys to me.
But when i go to this post i have no idea whats going on or what a gold card is or what its supposed to do.
So as im a complete noob and i have sort of tried on my own i was hoping if anyone could lead me through what im meant to do to get my Stock DHD to the stage where its running JellyTime android 4.2.2?
I also found a download for AAHK which has been removed by its developer as far as i know and i dont know what XDA's rules are if i was to repost the download link. The problem with the AAHK is that its requires a downgrade of my phone and when it tries to do that it needs to download a RUU(???) which was hosted on the developers site which is now removed and it returns errors for the RUU
Kirity said:
Hello there,
I am new to modding android devices so i just have a few questions to ask about my HTC Desire HD and installing (flashing?) the JellyTime (ROM?) software onto my phone.
I've read through lots of posts but there quite a bit of terminology that gets flung around which im not understanding but i think i know what i have to do.
But my main question are, since I'm running Android 2.3.5 Sense 3.0 rooting my phone has become quite hard for me as every program i look at says I need to downgrade. I read [How to] ROOT without the Hack Kit and I'm guessing "IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:" applys to me.
But when i go to this post i have no idea whats going on or what a gold card is or what its supposed to do.
So as im a complete noob and i have sort of tried on my own i was hoping if anyone could lead me through what im meant to do to get my Stock DHD to the stage where its running JellyTime android 4.2.2?
I also found a download for AAHK which has been removed by its developer as far as i know and i dont know what XDA's rules are if i was to repost the download link. The problem with the AAHK is that its requires a downgrade of my phone and when it tries to do that it needs to download a RUU(???) which was hosted on the developers site which is now removed and it returns errors for the RUU
Click to expand...
Click to collapse
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
glevitan said:
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
Click to expand...
Click to collapse
Because the program in your root guide said that my software version is not supported, I have skimmed through the guide and I will read it properly on the weekend.
Why would it brick my device it has worked on all the device that used to use it? as I have read it used the be the go to tool for root and S-OFF. I thought the developer just didn't like the scene anymore are removed all his work i thought i still worked but the downloads where hard to find.
Could you please tell me if i can run JellyTime on my device?
Also reading your guide i didnt understand the information about rooting where you talked about S-OFF wont be needed to run CWM recovery as i read somewhere that CWM recovery needed to have S-OFF to work.
Thanks for your help.
Kirity said:
Why would it brick my device it has worked on all the device that used to use it?
Click to expand...
Click to collapse
It hasn't worked on all the devices. It was the go-to tool for S-Off, but read back through the forums; many people (usually those who did not read well) have run into problems and needed support. And if you post it for others in a responsible manner, you need to support that possibility.
Kirity said:
Also reading your guide i didnt understand the information about rooting where you talked about S-OFF wont be needed to run CWM recovery as i read somewhere that CWM recovery needed to have S-OFF to work.
Click to expand...
Click to collapse
You don't need S-Off to install a custom recovery.
glevitan said:
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
Click to expand...
Click to collapse
____________
My phone says my build(ROM) version is 3.12 but the hboot program says its 3.13
the root kit wants me to update but the ROM updaters says updating from 3.13 to 3.13 but the phone still says 3.12 ????
__________________
I ran the ROM updater outside of the ace root kit. Now it realises that the ROM is still 3.12... But not when i try to update the ROM it returns error 191????
Thanks for the help
I used the HTCDev procedure to unlock the bootloader (updating my hboot to the .29 version going from the .27 version), I then installed CWM. From there I flashed a CM10 ROM selecting the zip from the SDcard in recovery, then the last step was running the command "fastboot flash boot boot.img" after extracting the boot.img file from the ROM file.
I have no real use for root or anything, I just wanted jellybean, and it's well worth it.
Install download oneclick root and your problem will be solved.
Sent from my Desire HD using xda app-developers app
MisterBuggie said:
I used the HTCDev procedure to unlock the bootloader (updating my hboot to the .29 version going from the .27 version), I then installed CWM. From there I flashed a CM10 ROM selecting the zip from the SDcard in recovery, then the last step was running the command "fastboot flash boot boot.img" after extracting the boot.img file from the ROM file.
I have no real use for root or anything, I just wanted jellybean, and it's well worth it.
Click to expand...
Click to collapse
I'm currently running 2.00.0029? But at the top it says *** LOCKED (OOW) *** ??
Do i not need an unlocked bootloader to get jellybean on my phone?
Kirity said:
What defines a unlocked boot loader? how do I find out. I'm currently running 2.00.0029? But at the top it says *** LOCKED (OOW) *** ??
If this is an unlocked bootloader can you walk me through getting jellybean on my phone?
This would be awesome! thanks a bunch.
Click to expand...
Click to collapse
Read the Ace Think Tank linked in my signature. You are not unlocked, but you can use the Tank-linked Easy Ace Root Tool to do so. As for a tutorial on flashing custom ROMs, the Think Tank has links for that too; no need for a separate walkthrough reinventing the wheel.
nothing works....
bananagranola said:
Read the Ace Think Tank linked in my signature. You are not unlocked, but you can use the Tank-linked Easy Ace Root Tool to do so. As for a tutorial on flashing custom ROMs, the Think Tank has links for that too; no need for a separate walkthrough reinventing the wheel.
Click to expand...
Click to collapse
Hi yeah as talked about above and in another post i have use the easy ace root tool but it requires me to upgrade my hboot and/or software. I'm running software 3.12.405.1 but I need to be running 3.13.000 apparently. It automatically downloads HTCDev's RUU but every time i run it it gives me the error 191 ROM not supported.
I have tried all variants of the RUU from the HTCDev website for my phone even for the wrong carries all give the same error.
I read somewhere that i may need a Goldcard since i carried out an OTA update on my phone and its tied to an orange (ee) contract?
However the goldcard generating website is now offline due to hackers and they said they are shutting down and the only person i could find who said they could generate goldcards (geene pool) isnt responding to my PM.
so I'm all out of luck.
Kirity said:
Hi yeah as talked about above and in another post i have use the easy ace root tool but it requires me to upgrade my hboot and/or software. I'm running software 3.12.405.1 but I need to be running 3.13.000 apparently. It automatically downloads HTCDev's RUU but every time i run it it gives me the error 191 ROM not supported.
I have tried all variants of the RUU from the HTCDev website for my phone even for the wrong carries all give the same error.
I read somewhere that i may need a Goldcard since i carried out an OTA update on my phone and its tied to an orange (ee) contract?
However the goldcard generating website is now offline due to hackers and they said they are shutting down and the only person i could find who said they could generate goldcards (geene pool) isnt responding to my PM.
so I'm all out of luck.
Click to expand...
Click to collapse
Ah. Then yes, you are just out of luck. I know that there's a way to generate a goldcard yourself instead of having Gene Poole do it (I believe by using a specific ActivePerl version, a specific Crypt SSLeay module, and the goldcard generating script) but I haven't had the inclination to do it myself. If you really want it you could give that a shot.
bananagranola said:
Ah. Then yes, you are just out of luck. I know that there's a way to generate a goldcard yourself instead of having Gene Poole do it (I believe by using a specific ActivePerl version, a specific Crypt SSLeay module, and the goldcard generating script) but I haven't had the inclination to do it myself. If you really want it you could give that a shot.
Click to expand...
Click to collapse
Erm on the off chance i tried unlock my phone again and i think its worked!!!!! this is amazing!!!
just a question can I change the SDcard in my unlocked phone or will it affect the boot loader?
Kirity said:
Erm on the off chance i tried unlock my phone again and i think its worked!!!!! this is amazing!!!
just a question can I change the SDcard in my unlocked phone or will it affect the boot loader?
Click to expand...
Click to collapse
Yes you can.