Root Downgrade HBOOT .93??

[RhysD]

Is it possible to do this yet? I really want to try the new Desire HD Rom and with the current software i dont think im able to root, therefore i would need to downgrade my HBOOT??

 

[SUroot]

Hboot has nothing to do with whether you can root it not. You can root with unrevoked.

 

[RhysD]

hmm yeah unrevoked worked but superuser kept on force closing and when i tried loading a custom rom it froze and i had to recover with the P98IMG.zip(or whatever the file name was) method in the bootloader, so i dont know if that was just the rom or it was my mistake.

 

[SUroot]

You can just clear cache and data in manage applications for superuser. If you didn't wipe, there may have been data in it from your previous rom.

 

[RhysD]

i couldnt load up superuser, it would just force close every time, and as for loading the rom i did all the clears and more it just froze multiple times.

 

[teppic74]

unrevoked 3.21 is buggy. The best way is to downgrade to Android 2.1 and root with 3.14 instead, as that works perfectly. It does mean a total wipe of course.

 

[RhysD]

i didnt know i could downgrade otherwise i would have(i feel like a n00b) does it matter that im on 2.10.405.2 software version? and just a gold card and 2.1 WWE rom to downgrade. sorry for the hastle guys hope you dont mind

 

[teppic74]

To downgrade you need a bootable phone, I assume you used the PB99IMG to go up stock 2.10.405.2 (that is fine):

[HOWTO] Downgrade Froyo (2.2) to Stock 2.1 (ANY HBOOT | WIN/LINUX/MAC | ROOT) - xda-developers

 

[RhysD]

yeah i used PB99IMG.zip to go stock, i tried your downgrade tool but for some reason(guess im not that familiar with terminal) i couldnt get it to work came up saying that there was a problem with adb couldnt be found, ill try and find a youtube video on it, thanks for the help teppic74 and danfrance

 

[SUroot]

i couldnt load up superuser, it would just force close every time, and as for loading the rom i did all the clears and more it just froze multiple times.

You didn't need to.open it.

You have to navigate command prompt to the directory adb is in for adb to work.

Assuming you have downloaded android-sdk-windows to C:\android-sdk-windows

-On your PC open Command prompt (Start>Run Type "cmd" [without the quotation marks] and press enter)


-In the black window type cd\ and press enter


- Type cd\android-sdk-windows\tools and press enter


- Type adb shell and press enter

 

[droidzone]

Added screenshots..

In a slight variation of the method Dan sugegsted, go to the android-sdk-windows folder,

Right click The Tools folder, holding down Shift key.
Choose>Open Command prompt here

In the new Command window, type:
adb tools
(If this shows a device id, your device is ready)

If this doesnt happen, check that your drivers installed ok. Close HTC Sync if it's running.

 

[droidzone]

Another easy method for doing the same thing..

Navigate to your android-sdk-windows\tools folder..

Right click anywhere, create a New Text Document..
Type the following in it:

explorer .

That is, type explorer followed by a space and then a dot
On the second line, type:

cmd

The file should look like this:

explorer .
cmd

Save the text file as "adbrun.cmd". You need to type the quotes as part of the filename!

Now you can just drag a shortcut of it to your desktop. If you run it, a new Explorer window will open inside the Tools folder, and also a command prompt will open at the tools folder.

It's just a tip of my own!

 

[droidzone]

@danfrance, why're your posts showing "***8220;" etc..?

I had to search and replace these tags on one of the posts you directed me to issue the scripts..

 

[SUroot]

@danfrance, why're your posts showing "***8220;" etc..?

I had to search and replace these tags on one of the posts you directed me to issue the scripts..

I think its related to the database errors the forum keeps experiencing. I keep editing them out but they keep coming back. No idea why.

 

[RhysD]

teppic i got to say that your a genius! it took me some trial and error with working around the MacOSX terminal but i got it figured out and downgraded, its now rooted, on the HD rom and running really good, thanks for the help again guys, couldnt have done it without you!!​