Develop Bugs

[Q] HTC Desire Z Rooting Problems

Hello together
First of all i searched to solve my problem already. But after spending several hours by searching and trying I thought i better ask the community.
Well my problem is, that I can't root my phone. I tried diffrent ways and there was always the same result. If I use Visionary+ r14 and press temp root now (usb debugging activatet) it loads for a while and then it hangs on a black screen. Seems to freez always.
If I try it with the terminal emulator and the manual found http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD here, it hangs in the terminal emulator. I don't know the reason but i couldn't find another possibility to root my device.
sorry for my bad english and thank you

Which version of the stock rom are you on? 1.34 or 1.72 or 1.85?? If its 1.72 you need to downgrade your version number to 1.34 in order to root using the Psneuter Method found Here. If its the new 1.85 update, im not sure if that version is rootable or if the psneuter method works on it also.

I've got the 1.72 version of the rom. Well this exactly is my next problem. I tried to downgrade using your method some time before. When i enter the bootloader and it checks the sdcard it just prints CID incorrect.
I know that I have to create a goldcard to make the downgrade possible. To create a goldcard I fallowed also different manuals.
here are two i've tried:
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
http://forum.xda-developers.com/showthread.php?t=572683
there are always the same steps. I tried different manuals and tools. But in the end i got always the same cid which looks something similar to this: 1501004d344732444503ad020c67ade0 then i need the reverse string and the hexeditor and overwrite the first sector of the sdcard. but no matter which method i try, in the end I get always CID incorrect.
anybody already had a similar problem?

nobody had a similar problem?

well solution found... in all the manuals there was written about the "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" command.
because this method didnt work for me i searched and found the solution to change the command to "adb shell cat /sys/class/mmc_host/mmc0/mmc0:*/cid". With this command i got a CID.
The problem was that I didnt search further in this direction because I had a CID. with the command "adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid" everything worked and i got another CID.

im hving th same problem....im on 1.72 rom and get stuck at wrong cid part like u.. ive tried everything...no joy

You tried all the mmc methods?
with mmc1 i got no cid, with mmc0 i got the wrong cid and with mmc2 it worked.

I will try again tomoz ..actually im gona try everything again...and then wait foor my hair to grow back so i can pull it out again
Sent from my HTC Vision using XDA App

[Q] Have I managed Perm Root with this much ease? Visionary+ Question

About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?

Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App

I should have mentioned that I did that and got the # symbol, am I good to go?

Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).

redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.

That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.

Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?

OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.

Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?

Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?

There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App

Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.

shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.

Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.

New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?

Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.

Excuse my ignorance, but what exactly do you mean by that? What should I do?

[GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread

This guide is now obsolete. Please use this guide instead.
For Gingerbread Phones, Please use this guide.
Hey guys, this is probably the easiest guide to follow for rooting a branded desire Z. The reason why this can sometimes be hard is cause it uses a unique identifier (INFOCID) and the companies that brand the phones ONLY want roms from their company on them. This stops us from using a WWE rom like every else to downgrade and then root.
But ultimately, the reason I'm making this is because every other guide I've read constantly links you to other guides or other pages and it sorta annoyed me. So after I figured it all out I posted one concise guide that doesn't redirect you 50 times.
Now I’m gonna run you through EVERYTHING so you won’t get stuck anywhere.
This guide will work with:
Device: Desire Z or G2
Firmware Version: Any Firmware version will be fine (All you need to do is downgrade using step 1)
Android Version: Froyo or any previous variation of Android (Absolutely no gingerbread device will root with this method)
Btw, I take no responsibility for any damage taken by using these procedures. Sorry =P
Also if you don't have ADB and Fastboot set up then go ahead and follow the guides on the first two posts here. -Thanks nephron
g4b4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Which can be checked by typing the following two commands:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
If your CID matches one of the CID's above then you can skip Step 1.
1. Creating a Goldcard:
Prerequisites:
ADB Set up and running fine (to check if it is working just connect your phone and have USB debugging enabled. Then type adb devices in your CMD Prompt)
HxD Hex Editor (see attachments of post 1)
USB Debugging enabled on your phone
1.Firstly we need to mount the memory card on a windows PC.
2. Format the memory card as FAT32 using all the default options.
3. Mount the memory card on your Phone. Then give it a couple of seconds.
4. Remount the memory card on your PC.
5. Find your CID by using the follow command in your cmd prompt (YOU NEED ADB)
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
6. Use the excel sheet provided to reverse the CID (see Attachments)
7. Goto this website and send yourself a goldcard.img
http://psas.revskills.de/?q=goldcard
8. Run HxD hex editor AS AN ADMINISTRATOR! (I can’t stress how important having admin rights is)
9. Go to Extras > Open Disk Image. Then select your goldcard.img
10. Go to Extras > Open Disk. IMPORTANT: Select your memory card UNDER the Physical Drives category. DO NOT open the logical drive.
11. Switch to your goldcard.img tab. Go to Edit > Select All. Then Edit > Copy.
12. Go to the physical drive tab and select the lines 00000000 until you get to the one with 00000170.
13. Go To Edit > Paste Write.
14. You should have a huge block of red characters now. This is good btw.
15. Mount your SD card on your Phone and let it detect it. If it comes up with a corrupt SD card error you have done it wrong and you may have to start over.
16. You are done with the goldcard.
2. Downgrading and Debranding
Before you start this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file) -Thanks g4rb4g3
ii. If you are a BELL User. Please download this RUU instead.
1b. Run the setup until you get to the screen with the tick boxes (Some Users may have to run this as an Administrator)
1c. Leave the setup running and go to C:\Users\<your account name>\AppData\local\temp ( Or Try %AppData%\Local\Temp\ ). Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its then into its one folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip (Make sure it is exactly the same as the way I've typed it there)
1e. Mount your sd card back onto your phone.
2. Download the attachments (misc_version & psneuters) and extract them in a folder like C:\RootVision\
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
4. After the last command you should have a # and a flashing line for you to enter text. This is good. (If you get a $ you have done it wrong and should try typing the commands out again)
5. Now you have the # type the following command in: (This will spoof the radio version)
Code:
/data/local/tmp/misc_version –s 1.33.405.5
Then go ahead and type:
Code:
exit
6. Type this command into your cmd prompt (btw you should be back with the normal C:\RootVision>)
Code:
adb reboot bootloader
7. Once on your white screen with colourful text you can go ahead and press the power button ONCE
8. Now just wait for the rom to install and verify. If you get INCORRECT CID your gold card doesn’t work or your CID doesn't match and you'll need a goldcard. (Go to Step 1. and make a goldcard for your phone)
9. Go ahead and install the rom when it asks you.
10. You are done downgrading and can now begin the Rooting process.
See Post 2 For Rooting

Assuming all as gone well and you now have a rom without superuser but you have a baseband version that is 1.34xxxx.
Alright, let’s begin.
Prerequisites:
Download psneuter
Download gfree 0.5
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
3. Root your Desire Z!
Before you start:
Enable USB Debugging and Allow Unknown Market Installations again.
Also delete the PC10IMG.zip on your phone if you downgraded.
Okay lets go:
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f -b hboot-eng.img
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID, secu-flag off & an Unlocked HBOOT-ENG.
If gfree 0.5 doesnt work for you then this section is for you:
Prerequisites:
Download psneuter
Download gfree 0.2
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID and secu-flag off.
4. Installing your own custom ROM
This section is just in case you don't know how to install a custom ROM.
Note: Always make sure the ROM you are installing is FOR YOUR PHONE! If you install a ROM meant for another phone you could potentially damage it or brick the phone itself.
1. Download the ROM you want and copy it to your SD Card. (Try to keep it in a folder that is easy to get to)
2. Turn off your phone.
3. Hold down the volume down button and then press the Power Button. This should take you to a white screen with lots of colourful text. One of which says FASTBOOT or FASTBOOT_USB.
4. Press the power button ONCE when BOOTLOADER is selected(BLUE)
5. Navigate using the volume buttons until you get to RECOVERY and then press the Power Button again.
6. The HTC Logo will come up then you will get a black screen with text.
7. From here you should Always do a NANDROID Backup so you can restore a working ROM if something fails.
NANDROID Backup
7a. Navigate to 'backup and restore' and then select it by pressing the trackpad button.
7b. Select 'Backup' and then let it finish. Once done you have a backup of your android.
8. Now you want to do these before you start installing:
a. 'wipe data/factory reset
b. 'wipe cache partition'
c. Go into 'advanced' and select 'Wipe Dalvik Cache'
9. Now you can install the ROM itself. This is done by selecting 'install zip from sdcard' in the main menu. Now you can select 'choose zip from sdcard' and just go ahead and select the ROM you copid to your sd card earlier.
9a. If the phone says verification failed then just toggle the signature verification option.
FAQ - For Anyone with any issues.
1. My version is 1.7xxxx or higher. Can I use this method?
Yes you can. This method will downgrade your phone to 1.34 so your radio is no longer locked thereby allowing you remove the secu-flag, add superCID and allow you to install a custom recovery (like ClockWorkMod)
2. My CID is XXXXXXXX and isn't on that list, will this method still work?
Yes it will. The reason why it will work is because a goldcard is essentially a manufacturers way of bypassing the CID checks used by ROMs. Therefore, by creating our own unique goldcards we can also bypass the CID check.
3. My CID is on the list that you mentioned. Do I need this goldcard?
No, you can skip the 1st step because when the ROM checks your phones CID it will match up perfectly and the phone will install the older radio without issue.
4. What Benefits does rooting a phone grant you?
Simply, it allows you to install any ROM of your choosing onto the phone as well as use custom kernels and certain applications that access locked functions on the phone. This can ultimately lead to; a longer battery life; more stable roms and more frequently updated roms; and finally an overall faster Android experience.
5. What is root access?
Root access essentially gives you access anything locked by the manufacturer on the phone. This most importantly means that you can read and write to any system partitions on the phone that would normally be locked.
6. Whats psneuter?
psneuter is an application used to grant temporary root access. This is done through an exploit in the android system and will give us a window to further exploit the system and ultimately grant us Permanent Root Access.
7. How do I find my CID?
To find your CID you run two commands. Firstly, in your CMD prompt you type 'adb reboot bootloader' when your phone is connected and USB debugging is active. This will restart your phone into its bootloader. Then once you see the words FASTBOOT_USB you type 'fastboot oem boot'. Then look for the words CID and then just read the 8 character CID.
Also there is a post with a screenshot here.
8. My phone will not find PC10IMG.zip
You will need to double check that the PC10IMG.zip is the correct ZIP file from the RUU that has been linked. It should be roughly 250mb in size and should be placed in the root folder of your SD Card. Also your SD Card must be compatible with your device (able to be read/written to). If you cannot access your SD Card from your Desire Z or G2 then there is probably something wrong with your SD Card. It should probably be reformatted.
9. Can I use this on the Desire Z/G2 running Gingerbread?
So far no one has been able to root the gingerbread version of android on the Desire Z/G2. Unfortunately, this guide still cannot root gingerbread desire Zs or G2s.
If there are any more, feel free to post them and I'll add them
10.I'm Missing my AdbWinApi.dll? What now?
espentan[U said:
][/U]
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse

will this work if i have 1.84.666.2?

anyone? thought?

Should work fine as long as you've got a Desire Z or G2 lol.

hi, manageage to root the DZ sucessfully, however on step 5 you say
"5. Type in:
Code:
Reboot"
i got an Reboot: error not found
i retried with with "reboot" and was sucessful

Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..

jmpcrx said:
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
Click to expand...
Click to collapse
It is pretty difficult to go back to stock updates from your carrier for example Vodafone. This is because of the unique CIDs used and the fact that it is extremely hard to find a stock ROM since no one can give you a NANDROID backup.
Anyways, there are numerous benefits to rooting your phone included with most ROMs. These benefits include longer battery life, faster ROMs & various other things depending on each chef.

Ok, thanks, but are the roms buggy at all, will some of the hardware not work properly, or will i have freezing probs etc, as i found this always to be the case with win mo roms?.. have you personally found a rom that works perfectly that includes htc sense? As i do like the UI..
My goal is to have all security off, full perm root, with a perfecly working sense rom that i can then overclock to a speed that works well with my particular phone, and to underclock when idle etc..
Thanks..

I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?

Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?

Vader™ said:
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Click to expand...
Click to collapse
Firstly, to root the phone just follow the steps and once you've finished them all you will be done.
Second, it should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
forceOnature said:
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
Using this method you don't have to worry about your CID. If you make a goldcard it will completely bypass the need for one of the CID's listed in the first post. So to put it simply, you don't need to worry about your unique CID if you create and use a goldcard to downgrade.

Aegishua said:
It should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
Click to expand...
Click to collapse
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here

Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..

Everything goes fine until
mmap() failed. Operation not permitted
when I put in
adb shell /data/local/tmp/psneuter
Any help?

Also I can only put su and Superuser.apk on my sdcard if I manually transfer them.

Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Click to expand...
Click to collapse
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy

chevy2410 said:
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
Click to expand...
Click to collapse
You should get a line that says INFOt.cid=XXXXXXXX or any of the lines that say your 8 Digit CID. However, as you can see there are multiple lines that say it and they should all be the same.
If your CID does match one on that list then you will not need a goldcard.
I've attached a screenshot to make things easier.
forceOnature said:
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Yeah, you can only have a NANDroid backup of 1.34.xxx because there is no way to get clockwork onto a 1.72+ rom.

Hi, I'm new to rooting the G2. Iv'e been trying to follow this tutorial, but I'm having some trouble. After renaming Rom.zip to PC10IMG.zip I booted into the bootloader and it says 'no image found' or something like that. What am I doing wrong? Am I not supposed to put the zip file on the root of the SD card? Is it possible to just use the RUU to downgrade?
And regarding the downgrade, the build number on my G2 shows 1.22 . Isn't that lower than 1.34?
Any help is appreciated!

I followed the instructions twice and both times I get to
"/data/local/tmp/misc_version –s 1.33.405.5"
I get
/
Patching and backing up partition 17
Error opening backup file.
#
The first time around I iqnored it and went through hboot, the rom PC10IMG.zip was checked and verified and finally failed prompting "the main version is older"
what am I missing?
EDIT: checked SD card, unmount and remounted phone/sdcard no avail.
Will try 1.33 Bell rom next.
EDIT2: Patching and backing up sucessful, problem was I couldn't get my phone to stay in debugged mode without being in DISK DRIVE, had to start HTC Sync to mount the phone in that way to relieve the sd card, allowing adb to patch the file. Now running through PC10IMG.zip with fingers crossed.
EDIT3: Everything went smooth after that! Thanks. Now I will attempt to update to 2.3 and Sense 3.0
EDIT4: Now running on 2.3.3 and Sense 3.0 Virtuous port. Testing...probably going back to more stable gingerbread and sense 2.1

[Q] Cant Root 2.3.3 unbranded htc desire hd

Originally Posted by ruben_swing
1st you will need the following files
GingerBreak from http://c-skills.blogspot.com/2011/04...ngerbreak.html
misc_version from http://www.multiupload.com/A9PNGVBWBE
Default rom http://forum.xda-developers.com/showthread.php?t=905003
and Android SDK http://developer.android.com/sdk/index.html
Also you will need a clean SD card 1 gig or more should be fine (smaller is better)
Unzip GingerBreak and misc_version into a folder say c:\Downgrade (I normally use 7Zip)
You should have:
c:\Downgrade\GingerBreak with 5 Files
c:\Downgrade\misc_version with 4 Files
Make sure you installed Android SDK's Platform tools and updated your path to reflect this
IE: run SDK Manager and install Android SDK Tools and Google USB Driver pack if you don t have HTC Sync driver running.
Format the SD card and copy the rom.zip into the base of the card, not a sub directory. (Do not unzip)
Now: Plug in the phone to the USB and make sure Debugging is on and the phone is set to charge only.
Then open Command prompt ie: run cmd.exe
Go to your Downgrade directory and test if your adb command is in the path. ie: run it and make sure it lists switches and not say file not found
Then run as follow
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
if you fail to get root ie: prompt does not return to # or get a endless sendmsg() failed? Error, reboot the phone and repeat the commands above. The phone I used, took 3 tries to get this right.
at the # run the following
cd /data/local/tmp
./misc_version -s 1.31.405.6
When its done exit cmd and goto your phone, Reboot it while pressing volume down.
It will come up with a menu and follow the update instructions.
You should then be on Android version 2.2 when done.
Please note the rom that is supplied works with unbranded phone only if you have a branded phone you will need to make a goldcard. If you want to know how to make one, google is your friend sorry.
Hello Folks,
I have the same software as mentioned in the first post above:
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
and tried the solution as given to the reply to the post. I have an unlocked unbranded HTC Desire HD. The cmd window looks like below.
c:\Htc>adb push misc_version /data/local/tmp
adb server is out of date. killing...
*daemon started successfully*
410 KB/s <16830 bytes in 0.04s>
c:\Htc>adb push GingerBreak /data/local/tmp
adb server is out of date. killing...
*daemon started successfully*
410 KB/s <16830 bytes in 0.04s>
c:\Htc>adb shell chmod 777 /data/local/tmp/misc_version
adb server is out of date. killing...
*daemon started successfully*
c:\Htc>adb shell chmod 777 /data/local/tmp/GingerBreak
adb server is out of date. killing...
*daemon started successfully*
C:\Htc>adb shell
adb server is out of date. killing...
*daemon started successfully*
$su
su: permission denied
$
I would appreciate if anyone could help me out. One other thing is the I was a bit lost about the installation of the Android SDK Platform etc...as mentioned, I presume it is required if you don't have HTC sync/drivers installed! Or is still needed?.

Just follow jkoljo method, worked for me.
http://forum.xda-developers.com/showthread.php?t=905003
I think you need to run GingerBreak in you method instead of typing su
Hope that will help.

naailalzuhir said:
Just follow jkoljo method, worked for me.
http://forum.xda-developers.com/showthread.php?t=905003
I think you need to run GingerBreak in you method instead of typing su
Hope that will help.
Click to expand...
Click to collapse
Thanks for the reply mate. It's my mistake, I was actually typing the cmd window in the forum so might have omitted the line actually. So yeah, I did run the gingerbreak following
adb shell
./data/local/tmp/GingerBreak
after which it again returns to $. I read in the same thread below
http://forum.xda-developers.com/showthread.php?t=905003
that you have to get a # instead of $. So if you get $ then type su to get super user. It is said that a window will pop up on phone after typing su in cmd asking for permission. But I don't get any such pop up on my phone screen. Also, after running Gingerbreak, the cmd just returns the same $. Gingerbreak does not even run as far as I can say.
I wonder why after each adb command it returns:-
adb server is out of date. killing...
*daemon started successfully*
Any thoughts...

Use the adb that comes with jkoljo downgrade pack, and install HTC sync on your PC.

hello.. i have a desire hd with build number 2.37. based on gingerbread 2.3.3 .. i have a unbranded desire hd with s-off.. is it possible for me to downgrade to 2.2.. i followed ur guide using dhd in charge only with debugg mode but every time it gives me erroe that adm is out of date killing deamon started succesfull.. pls help i m fed up with the stock rom .. gingerbread ota is full of bugs and with connectivity problems.. thankz in advance

As far as I know, you cannot temp root 2.37 and hence downgrade is impossible at present
But you mentioned that you have S-off... how is that possible? Because if it is S-off, I am sure you can flash a custom recovery and then flash a custom Rom.

naailalzuhir said:
Use the adb that comes with jkoljo downgrade pack, and install HTC sync on your PC.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I am using the adb that came with the xda thread to downgrade. It's a folder that contains the adb and other stuff like GB........Yes, I do have HTC Sync installed on the PC as well.....so far I tried both my notebook and home desktop...same results. So confused...

I have s-off because when I was on froyo with build number 1.32 I rooted my dhd.. and now I updated it 2.3.3. Check the last post they say u can try downgrading if u have dhd with s-off
Sent from my Desire HD using XDA Premium App

If you have S-OFF you should be able to flash CWM and install another ROM as naailalzuhir says. If you go to the CWM thread in the development section, it will tell you how to flash CWM from fastboot. When that is installed you should just be able to install a different ROM without downgrading. I think, but lets wait for soebody else's opinion on that.

Petronoid said:
Thanks for the reply. Yes, I am using the adb that came with the xda thread to downgrade. It's a folder that contains the adb and other stuff like GB........Yes, I do have HTC Sync installed on the PC as well.....so far I tried both my notebook and home desktop...same results. So confused...
Click to expand...
Click to collapse
Do you have anything from SDK running in background? Check your task manager, if you have adb.exe running, terminate it before running adb shell command.
I am assuming that you closed HTC sync software on your PC, plugged with USB debugging mode and charge only.
Hope that can help.

gagan01 said:
I have s-off because when I was on froyo with build number 1.32 I rooted my dhd.. and now I updated it 2.3.3. Check the last post they say u can try downgrading if u have dhd with s-off
Click to expand...
Click to collapse
Hmm interesting You can indeed flash a custom Rom then and forget the hassel to root.
See these two posts in the forums for guidance.
http://forum.xda-developers.com/showthread.php?t=1017364 and http://forum.xda-developers.com/showthread.php?t=948304
NOTE: try to download 3.0.2.6 instead of 3.0.0.5 for EXT4 support.
Cheers

U want to say that if I Ve s-off I can flash custom Rom directly .. irrespective of temproot and that stuff... Guyz do temproot those u Ve s-on.. if this is soo I m on the top of the world

Also one thing does flashing from cwm is different than flashing custom Rom from rommanager.. I installed Rom manager but the option to flash cwm is not clickable .. pls help
Sent from my Desire HD using XDA Premium App

That should be because you're not rooted so you do not have access to the recovery directory whilst booted into Android. You can also flash CWM from fastboot, bypassing the Android system completely. Instructions how to do that and the CWM files are here: http://forum.xda-developers.com/showthread.php?t=1003723
Please wait for somebody's confirmation before attempting that though.

There is one more question if sumthing goes wrong while flashing then my phone ll be dead or get reverted to stock Rom.. if any unfortunately phone becomes dead then is there any chance reviving it back again.. I know its a dumb question but matters to me most cuz I can't spend again 30grands buying it...
mechanical engineer

Pls answer me.. I ve downloaded the pd918.zip file and I ve put it in root of SD card... Now I ve s-off. And when go into bootloader screen it analyses the image ask me to update... So am I eligible to do the downgrade process without having temproot...
mechanical engineer

[How To] Root New Evo4g Hboot 2.18 without Unrevoked Without HTCDEV.com Windows Only

So... I recently had my evo replaced. As a result i found that i can no longer use Unrevoked to root, nand unlock and S-off my new phone. The current guides all point to using htcdev.com/bootloader however it seems rather unreliable because i attempted to access it, and the site kept reporting it had an incorrect .php file or some stuff. Google Searches proved that this site goes down frequently.
So with some google searching i have pieced together an Offline way to root an Evo4g. From the sounds of it, i think this method will root, Nand Unlock, S-off, and push a recovery to any device. At least from what i am understanding. Also apparently this method WILL NOT void your HTC warranty because you do not need to use HTCDEV.COM/Bootloader
Soooooo... My disclaimer.. I am not a dev, i have no idea what the first thing a dev does. I give ALL credit to the people that put in the hard work to allow me to achieve root. I will also post credits and the origional thread i pulled this information from. Also, if you mess things up, i cant help you. I probably wont even be able to answer any of your questions.
This method uses a hack provided by SimonSimon34 on these forums for his HTC Wildfire, but it WILL work on our Evo's.
First things first.
1. Turn on your phone
2. Go To Settings->Apps->Development Enable Usb Debugging.
3. Visit Simonsimons34 Wildfire Unlock Thread
4. Download the V2 Universal Rar he has
5. The instructions for this zip are easy. once downloaded, i suggest moving it to the Desktop. Extract to a Folder on the desktop and name it root.
6. Once extracted open your folder you just named root. There will be a file in there called Simonsutility.bak double click on it.
7. You are presented with 4 options.
1. Bootloader Unlock and Root (Universal)
2. Custom Recovery (Unlocked or S-Off)
3. S-Off
4. Install Drivers
Connect your phone to the computer, Choose Charge only. Choose 1 and press enter
8. The phone then does alot of stuff. not exactly sure what any of it means, but if you watch the Simonsutility window it kind of explains as its going what it is doing. when its finished choose option 2 and press enter.
9. You should now be staring at your bootloader screen. Now you need to choose a recovery. I reccomend Amon_Ra's as i have yet to have any catastrophic issues using it. This can be downloaded Amon_ra Recovery Current version is v.2.3 just make sure you download it.
10. Once downloaded i suggest moving it to the folder we created earlier called Root and renaming it to recovery.img because its going to make things easier in the next step.
11. Now you have all you need to push the new recovery. Open up the root folder and shift+right click on fastboot and choose open command prompt here. If you do not have that option, click on your start menu, type CMD, and then navigate to your C:/users/*username/desktop/root folder (*username is obv your user profile name).
12. Once you are in the fastboot folder/directory type
Code:
Fastboot flash recovery recovery.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once it is finished you can select reboot recovery and you will now be in the Amon_ra Recovery.
From here you can flash a Rom of which for first time rooters, i would reccomend Fresh Evo 4.3.3 just because of its stability.
Below are the paypal accounts and origional threads i ripped off all of this information from. If there is enough interest i will update everything with pics. As i know the resources for this information is very low.
Thanks To
-==-=-=-=-=-=-=-
SimonSimon34
Simons Paypal
Simons Wildfire Thread
Amon_ra
Amon_ra's Paypal
Amon_ra's Origional Thread
Captain Throwback
Captian Throwbacks Thread
Im Placing Captain Throwback up here because his thread was the origional thread i was following, however since the HTC site was down i wasnt able to do anything, but i stole his Picture of the Amon recovery push.
Anyways, if i missed something feel free to flame me incessantly.

ACTUALLY THIS THREAD IS IN THE WRONG SECTION.
It does appear to work without going to the Htcdev site.
Well, someone had to test this method besides Hamspiced (Thanks for the tip). To summarize the method and give a brief description of what was done: I first S-ON and unrooted the phone back to 4.67 with the bootloader LOCKED (OWW). Dowloaded the file from
http://goo.im/devs/simonsimons34/HTC_Universal/Htc_Utilityv2Windows.zip
and unzipped it to a folder called root. Then,
1. Went to Setting/Applications and turned off Fastboot, then Settings/Applications/Development and enabled USB debugging.
2. Went to the root folder and ran the Drivers.exe program (to install the MYHTC drivers).
3. Connected the phone to my computer.
4. Ran the simonsutility.bat file, and was given the set of options:
1. Bootloader Unlock and Root (Universal)
2. Custom Recovery (Unlocked or S-Off)
3. S-Off
4. Install Drivers
and chose option 1.
5. After following a series of instructions, the phone finally rebooted into the bootloader and then read UNLOCKED, to my surprise. Also I tried options 2-4, but none of them seem compatible with the EVO 4g. So, the phone is now unlocked, but S-ON, but as long as the bootloader is unlocked, I can still do anything to the phone that I want, including installing the custom Recovery and turning it back S-OFF (I've done this many times).
So based on the experiment, there does seem to be an alternative right now to going to the Htcdev site to unlock the bootloader. It should work on other phones with the same type of bootloader (LOCK OWW) as well. I see that this takes advantage of a known vulnerability which I am not going to detail here to flash to the bootloader. I'm sure HTC knows about it and will patch it on future phones.

Well awesome! Im glad that my only mess up was that i posted it in the wrong section.
I was tired of the HTCDev site consistantly not working properly. I always had issues accessing it.

It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.

shortydoggg said:
It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.
Click to expand...
Click to collapse
Isn't this the same thing TacoRoot does, essentially?

Captain_Throwback said:
Isn't this the same thing TacoRoot does, essentially?
Click to expand...
Click to collapse
It does use tacoroot, but instead of running a PC36IMG file or RUU to downgrade, it uses some file called bool to unlock the bootloader almost directly. The main syntax after Tacoroot (once the files are given the chmod 755 command from the /data/local directory):
dump_image misc /data/local/misc.img
bool /data/local/misc.img unlock
flash_image misc /data/local/misc.img
I'm typing the commands from the top of my head, so there may be a spelling error. Reboot the phone, and the bootloader goes from "LOCKED OOW" TO "UNLOCKED".

Will this method reformat your phone or no?

This response is a little late because l'm on another phone now, but for those that want to know;
It unlocks the bootloader without wiping your phone, unlike the HTCdev site.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
So, the phone is now unlocked, but S-ON, but as long as the bootloader is unlocked, I can still do anything to the phone that I want, including installing the custom Recovery and turning it back S-OFF (I've done this many times).
Click to expand...
Click to collapse
Hamspiced, thank you for this method, I was having the same problem (had to get a replacement evo with the new software, and htc dev crashes every time I loaded the token)
I have a question for shortydoggg, how were you able to achieve s-off using this method? And were you able to remove the watermark?

wjHarnish said:
Hamspiced, thank you for this method, I was having the same problem (had to get a replacement evo with the new software, and htc dev crashes every time I loaded the token)
I have a question for shortydoggg, how were you able to achieve s-off using this method? And were you able to remove the watermark?
Click to expand...
Click to collapse
The method is just an alternative to going to the HTCdev site (and wiping the phone) to unlock the bootloader. It only unlocks the bootloader so that you can flash a custom recovery and flash superuser to obtain root access without wiping data. The phone will still be S-ON. You would then need to follow Captain Throwback's guide to obtaining S-OFF to remove the watermark and obtain S-OFF afterwards.
Sent from my SAMSUNG-SGH-I747 using xda premium

You can also show it as locked boot loader and send back to HTC leaving your warranty intact. That's in my next update
Sent from my One V using Tapatalk 2

This looks cool.I am trying to root my brother-in-law's EVO. I tried HTCDev and had no luck what so ever. I'll report back as well once I get his phone charged up.
10:35 pm est
Looks like Goo.im is down or something.Unable to download any of the links for the Utility.
Does anyone have the file laying around?

shortydoggg said:
It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.
Click to expand...
Click to collapse
It seems that when goo.im went down SimonSimon34's source code was lost with it.
If you would be so kind as to detail the manual version of this method it would be helpful to me, and I'm sure others, until SimonSimon34 finishes rewriting his utility, unfortunately, from the ground up.
Thank you much,
J.

jackfrost909 said:
It seems that when goo.im went down SimonSimon34's source code was lost with it.
If you would be so kind as to detail the manual version of this method it would be helpful to me, and I'm sure others, until SimonSimon34 finishes rewriting his utility, unfortunately, from the ground up.
Thank you much,
J.
Click to expand...
Click to collapse
I'm going to detail the method as much as possible here, since some want to see it. I have added links to the original SimonSimon34 source code, as well as a zip file with the necessary files for a manual method. I have walked through the manual mode step by step and have provided as much step by step proceedure as I have time for. Just remember 2 things here:
1. This method was originally made by SimonSimon34.
2. Any attempt at unlocking your bootloader and rooting your phone is at your own risk, so if you brick your phone, it's nobody's fault but your own.
Links:
SimonSimon34 original source code:
https://dl.dropbox.com/u/38127313/Htc_Utilityv2Windows.zip
Shortydoggg's breakdown and additions to SimonSimon's file for Manual Method.
https://dl.dropbox.com/u/38127313/Root 2.3.5.zip
(YOU NEED TO UNZIP THE FILES TO A FOLDER OF LIKING.)
NOW FOR A DESCRIPTION OF HOW THE ROOT METHOD WORKS (MANUALLY). YOU COULD ALSO JUST RUN THE Htc_Utilityv2Windows UTILITY (simonsutility.bat) SINCE IT IS PROBABLY EASIER, ALTHOUGH I FOUND SOME ERRORS AND MADE MY OWN CORRECTED VERSION WHICH I'M NOT GOING TO POST DUE TO MOST OF IT IS NOT MY OWN WORK. ALSO, THE WAY I ENTER MY COMMANDS IS SLIGHTLY DIFFERENT THAN THE WAY SIMONSIMON34 DOES HIS INSIDE HIS PROGRAM.
1. THE PHONE SHOULD BE IN CHARGE ONLY MODE WITH IT PLUGGED INTO YOUR COMPUTER'S USB.
2. RUN THE DRIVERS.exe file
3. TURN OFF FASTBOOT UNDER SETTINGS/APPLICATIONS
4. ENABLE USB DEBUGGING UNDER SETTINGS/APPLICATIONS/DEVELOPMENT
5. NOW YOU WOULD OPEN A COMMAND PROMPT AT THE FOLDER WHERE YOU UNZIPPED THE FILES, THEN TYPE:
adb push tacoroot.sh /data/local <ENTER>
adb push flash_image /data/local <ENTER>
adb push dump_image /data/local <ENTER>
adb push bool /data/local <ENTER>
adb push Superuser.zip /sdcard/ <ENTER>
adb shell
cd /data/local
chmod 755 tacoroot.sh
chmod 755 flash_image
chmod 755 dump_image
chmod 755 bool
./tacoroot.sh --recovery
(HOLD VOLLUME UP +VOLUME DOWN + POWER BUTTONS WHEN THE RED TRIANGLE APPEARS, THEN HIT THE POWER BUTTON TO REBOOT THE PHONE.)
(ONCE IT REBOOTS, TYPE
adb shell
/data/local/tacoroot.sh --setup
(HOLD VOLLUME UP +VOLUME DOWN + POWER BUTTONS WHEN THE RED TRIANGLE APPEARS, THEN HIT THE POWER BUTTON TO REBOOT THE PHONE.)
(ONCE IT REBOOTS, TYPE
adb shell
/data/local/tacoroot.sh --root
(IF AT ANYTIME THE PROCESS IS MESSED AFTER THIS POINT, YOU MUST REBOOT THE PHONE THEN TYPE:
adb shell
/data/local/tacoroot.sh --undo
IN ORDER TO RESTORE YOUR PHONE BACK TO WORKING CONDITION)
adb shell
cd /data/local
./dump_image misc misc.img
./bool misc.img unlock
./flash_image misc misc.img
./tacoroot.sh --undo
(ONCE THE PHONE REBOOTS, THEN BOOT INTO THE BOOTLOADER BY TYPING
adb shell
reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
(WHEN THE PHONE REBOOTS, HIT THE POWER BUTTON, USE THE VOLUME DOWN BUTTON THE THE POWER BUTTON TO GO INTO RECOVERY, THEN FLASH THE SUPERUSER.ZIP APP WHICH SHOULD BE ON THE ROOT OF THE SDCARD. REBOOT THE PHONE AND IT SHOULD NOW BE ROOTED.)

bool misc.img lock will lock it back how it was before, locked. Not relocked. But full blown locked
Sent from my One V using Tapatalk 2

If anyone has a copy of the Htc_Utilityv2Windows can you please post it, since it was lost from goo when they crashed.
Thanks

gadgetdaddy said:
If anyone has a copy of the Htc_Utilityv2Windows can you please post it, since it was lost from goo when they crashed.
Thanks
Click to expand...
Click to collapse
I already posted a link in this thread.
Sent from my SGH-I747M using xda premium

Mention github has utility 2 please
Sent from my One V using Tapatalk 2

simonsimons34 said:
bool misc.img lock will lock it back how it was before, locked. Not relocked. But full blown locked
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Not sure what you mean by "full blown locked" as opposed to "relocked"
Do you mean it will go back to s-on even if you went the full way to s-off, our are you referring to something else?
Sorry for the noobish question.
Thank you.
Sent from my PC36100 using Tapatalk 2

jackfrost909 said:
Not sure what you mean by "full blown locked" as opposed to "relocked"
Do you mean it will go back to s-on even if you went the full way to s-off, our are you referring to something else?
Sorry for the noobish question.
Thank you.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I mean like how the phone was when you bought it. If you need to send it in for warranty you would flash the stock hboot, send the son command, run bool lock command, and flash the ruu then your phone will be exactly like when you bought it was
Sent from my One V using Tapatalk 2