• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Guide]ROOTING HTC android 2.2.1 or lower with unrEVOked - Windows (updated 20th December 2012)

Right - all downloaded. Installed HTCSync on W7 machine that picked up the phone in Device Manager last night, uninstalled it, booted the phone into HBOOT, plugged it in . . . no reaction from Device Manager. USB debugging ticked.One difference to W8.1 machine - the phone stays saying HBOOT USB PLUG, whereas with 8.1 the USB PLUG disappeared after a short while.
Is this jinxed?
 
OK - uninstalled the HTC driver bit as well, & this time Device Manager saw the phone, & I was able to update the drivers so I've now gt the Android Bootloader Interface. I'll carry on!
 
OK - next question - before running Revolutionary, when I connect the phone, which USB option do I go for - ie charge, disk drive etc? At the moment, with Android running normally, Device Manager is just showing ADB interface with an exclamation mark

Edit - I've reinstalled HTC Sync, & uninstalled it, & now Device Manager shows My HTC under Android USB devices, if I select Disk drive on the phone

Edit 2 - I've uninstalled all HTC Sync stuff again, & have got back to the bootloader interface showing correctly again. Have I missed a step? Should I have installed SDK tools or anything like that?
 
Last edited:
Installed ADB drivers, phone now recognised as HTC Android Interface in Device Manager, but Revolutionary resolutely refusing to see it - just says 'Waiting for device . . .'
Elsewhere (in an EVO 3D thread) I read that the phone should be in charge-only mode when it's plugged in. I've tried that, and Disk drive.
 
No joy, I'm afraid. 3 different USB slots; Windows picks up the HTC Android Interface on each one, so I'm assuming both Hboot & Adb drivers are correctly installed, & then running revolutionary.exe from the revolutionary-0.4pre4 folder that I downloaded - it wasn't in the Dropbox folder. Does that all sound right?
 
OK - tried adb-setup-1.4.2.exe, & though it didn't want to do the fastboot bits (system cannot find the path secified), it did install some Google drivers, & now revolutionary sees the phone, accepts the key . . . & installs! Now got pink Revolutionary & S-OFF.
I might have to have a bit of a lie down. Just as well - I've got to fit a towbar to our van before I attempt the next stage.
 
Great, you got there. Next step is recovery. You can either use command shell as per the guide or fastboot commander. Just follow the instructions in my previous post.
 
Right - success - up to a point. Followed @nicka3200's instructions, thank you; got 4ext recovery installed (doesn't it look nice!), did a nandroid backup, installed the superuser zip from the SD card, which 4ext said was successful . . . but on reboot, there's no superuser in apps, & Titanium says it can't find it either. Uninstalled Co-pilot in case there was a space issue, reinstalled superuser - again, succesfully according to 4ext - but it's sill not there in apps.
So near . . .!
 
If you are going to change your ROM it doesn't really matter about installing superuser. They are all prerooted.

If you're going to try Oxygen your next step should be to back up your sd card then use recovery to partition it. I suggest a 1gb partition. Partitioning will almost certainly wipe the card.

After partioning restore your sd files and place the radio and Oxygen ROM zip files on the sd.

Next you need the updated radio. You can flash that via zip file on the sd or fastboot flash the radio.img in a similar way to the way you did the recovery but obviously using the radio option in fastboot commander or fastboot flash radio in command shell.

Immediately after installing the radio you need to factory reset via recovery and install the ROM via zip file on the sd. Note that it could take several minutes for the ROM to boot first time around as it needs to rebuild the Dalvik cache files.

Enjoy your new ROM.

Health Warning : trying new ROMs can be addictive!
 
On it. SD card 15% through a v slow backup - I suspect I don't need most of what's there, but you never know. The rest of your instructions seem eminently followable, but it might have to wait till the morning. & thanks for the health warning!
I'll keep you posted, obviously.
 
Backup completed, with errors on some strange 'index' files mostly of 1.15GB, supposedly; having said that, the total used size of the card corresponds to the size of the backup, so I'll go with that.
 
OK - sitting down?
It worked. One scary moment when the HTC splash screen wouldn't go away, going into recovery after the radio flash, but I took the battery out in the end, retried, & it turned out I'd been bricking it more than the phone.
So I now have a lovely minimal ROM, Whatsapp's reinstalled & found its backup with all the pictures & chat about our new granddaughter, it's already let me install one app that I couldn't before (Oruxmaps), so I'm a happy bunny. Not sure if I can get my ordinary messages back, (mainly because I can't remember how I backed them up - though I remember doing it!), but there was nothing of great importance there.
So thank you again for your patient help; how on earth you can remember / understand all this stuff I don't know. I'll try & leave you in peace now.
Cheers
Pete
 
Except . . . it's now telling me there's 'insufficient space on the device' to download CoPilot. Internal storage says 117Mb used, 34Mb free, & I've moved Google Play onto the SD card. Orux seems to have downloaded onto it anyway. Do I need anything else, like A2SD?
Plus it seems Maildroid isn't compatible anymore, for some reason - looks like I'd better use a different mail client!
 
You must log in or register to reply here.
Back
Top Bottom