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

Root The PRS Complete Rooting Guide

I think I found out where my problem lies. I'm unable to install the proper drivers for it. When I run the bootloader, before entering recovery mode Device Manager shows Android 1.0 as not having the right drivers, and all my attempts at finding the right drivers have failed.
 
FrozenIpaq said:
I think I found out where my problem lies. I'm unable to install the proper drivers for it. When I run the bootloader, before entering recovery mode Device Manager shows Android 1.0 as not having the right drivers, and all my attempts at finding the right drivers have failed.
Click to expand...

You can get them from the android SDK.

Start SDK Setup.exe

Goto Available Packages and click https://dl-ssl.google.com/android/repository/repository.xml

It may error out and ask Force https:// using http://

Goto Settings and click the first check box at the bottom

You should beable to choose your USB drivers, DL them and then manually install them from the usb_driver folder.
 
Greasy Joe Bick said:
You can get them from the android SDK.

Start SDK Setup.exe

Goto Available Packages and click https://dl-ssl.google.com/android/repository/repository.xml

It may error out and ask Force https:// using http://

Goto Settings and click the first check box at the bottom

You should beable to choose your USB drivers, DL them and then manually install them from the usb_driver folder.
Click to expand...

Already had those and edited the driver file properly. Still not getting any luck. With those that are getting a root, would you mind taking a video of the the phone booting into recovery mode and show your computer's device manager as well, I've gotten past the Android 1.0 driver part (uninstalled HTC Sync, installed PDA Net drivers) and now my computer isn't showing anything while in recovery mode ( the /!\ screen) whereas it would show: "Android Phone" right before launching it.

EDIT: On my desktop I tried installing the drivers for Android 1.0 as directed on the other site and Windows couldn't find the drivers in the specified directory anyways (this computer doesn't have PDA Net installed, only HTC Sync)

EDIT 2: Tried manually installing the drivers, and it's not wanting to accept them on my system configuration (64-bit); seems these drivers are 32-bit only?
 
Woohooo! Used the 2gig PNY card from my WM phone and it worked first time. Didn't let the phone boot normally with that card. It may spike it with something that affects the root process or it may be the make of card.

Try a different card.

run your adb shell loop, go to recovery (obviously not gonna work), take out battery, unplug usb cord, insert new card, wait about 10 seconds, put battery back in, go to hboot (dpad +power), wait about 10 seconds, press volume down, when you press power and AS YOUR PHONE IS DOING THE SHORT VIBRATE plug in the usb cord. recovery comes back up and i get -exec "/system ..." message

try update with nothing in
push busybox and ota
get payload ready on commandline
update and hit enter on pc as soon as yellow text comes up
make it permanant after payload
pull battery DO NOT reboot.
 
I am having the same Android 1.0 driver issue. I have tried editing the files, I have tried on both 64 and 32 bit systems, same problem.
 
Lars said:
Woohooo! Used the 2gig PNY card from my WM phone and it worked first time. Didn't let the phone boot normally with that card. It may spike it with something that affects the root process or it may be the make of card.

Try a different card.

run your adb shell loop, go to recovery (obviously not gonna work), take out battery, unplug usb cord, insert new card, wait about 10 seconds, put battery back in, go to hboot (dpad +power), wait about 10 seconds, press volume down, when you press power and AS YOUR PHONE IS DOING THE SHORT VIBRATE plug in the usb cord. recovery comes back up and i get -exec "/system ..." message

try update with nothing in
push busybox and ota
get payload ready on commandline
update and hit enter on pc as soon as yellow text comes up
make it permanant after payload
pull battery DO NOT reboot.
Click to expand...


why pull battery and not reboot? i reboot it and still got root.
 
Okay I have tried for 2 days no joke----

-With these cards-
2 GB Sandisk (VZW one)
16gb Sandisk class 2

Both no Go....

Went to Walmart and bought a 2GB PNY Class 4
(tried several times - NO GO!

I then connected the cord from the back of my cpu USB 2.0 - to the hub I have connected -

Did recovery and BOOM it caught - no me has ROOT!

Hope this helps you guys!
 
I finally got mine done. I had to completely remove all drivers from HTC and software from HTC, and it worked without a problem using only the edited drivers found at the link below.

Installing HTC Incredible Android SDK Drivers |

With my phone completely booted into the OS I plugged it in with USB debug on, and when it could not find a driver for just one item, i just this edited option. Then I adb reboot recovery and it was a first try from there.
 
Xystence said:
I finally got mine done. I had to completely remove all drivers from HTC and software from HTC, and it worked without a problem using only the edited drivers found at the link below.

Installing HTC Incredible Android SDK Drivers |

With my phone completely booted into the OS I plugged it in with USB debug on, and when it could not find a driver for just one item, i just this edited option. Then I adb reboot recovery and it was a first try from there.
Click to expand...

That's awesome! But... can you explain your last part in a little more detail. I downloaded the USB drivers and edited the .ini file based on the URL (flexjunk) and when "Android 1.0" comes up (in recovery), I point it to the edited .ini file and it says "No compatible driver found."

When in OS, I can adb shell and get the $ prompt but in recovery, no go.

Thanks.
 
I uninstalled all HTC stuff, rebooted pc, then plugged in phone that was booted at OS. Once it initialized I.went into device manager, the first category was Android something. I updated driver to edited one. Unplugged phone. Rebooted. Plugged back in as disk drive, performed adb reboot recovery. I used new method by pushing memory card in and out during restart to recovery. Then it worked on my.first try. Even though mine worked, that Android 1.0 driver error still appeared in bootloader. It's not related in my opinion, as minutes rooted regardless of that error.
 
Just got it rooted my second try today. I used the second method that was posted. I used this video to get the timing right on my update.zip push. Also, I used his commands for the last part to keep your phone rooted, and I pulled the battery out like he did instead of rebooting.

YouTube - Droid Incredible Root PT2
 
Lars said:
Woohooo! Used the 2gig PNY card from my WM phone and it worked first time...

...pull battery DO NOT reboot.
Click to expand...

See it was not us, it was you! I kid! Congrats I know you have been frustrated. However, you do not have to pull the battery. It will keep through a reboot if you follow the steps in the first post. I can attest to it.
 
FrozenIpaq said:
I think I found out where my problem lies. I'm unable to install the proper drivers for it. When I run the bootloader, before entering recovery mode Device Manager shows Android 1.0 as not having the right drivers, and all my attempts at finding the right drivers have failed.
Click to expand...

You shouldn't need the drivers to do this. My comp didn't have drivers, either, I just ignored the error and was still able to root the phone (twice now, since I had to go and do it again to install the SU app)
 
I've tried several times but can't get adb to work. I am using XP.
I've tried the HTC drivers on the htc site, the ones on the phone, and the ones with the android SDK (including the hacked version)

While in the regular phone mode, ADB will work fine. So I think the drivers are ok, at least some of them.

While in the FASTBOOT screen, "Android 1.0" is detected and I can install the SDK drivers successfully

While in the BOOTLOADER screen, "Android 1.0" is detected, but I can't install the drivers, it doesnt take the SDK oens.

If I continue to recovery mode, I hear that the phone is detected, although I can't find anything that looks like the phone in the device manager. never prompts me for drivers

Throughout this whole process "adb shell" never connects.

I'm out of ideas
 
@Prerunnerseth

Just trying to help, here, but I think that most people's problem with rooting their Inc is that they haven't actually installed the SDK drivers... As we know, it isn't the same as the SD card driver, which is auto detected.

If you could put this on your first post, I think it would really help... Maybe instruct people to get the driver working with the phone in debug mode. This should do it (copy and paste freely).

To install SDK drivers for properly rooting the HTC Incredible:

1. On your phone: Home>Menu>Settings>Applications>Development>Check USB debugging.
2. Plug phone into PC (phone on Android home screen), set to Charge Only and hit done.
3. Follow this guide: Installing HTC Incredible Android SDK Drivers |
4. Check PC device manager (right-click "My Computer" or "Computer" and go to Manage>Device Manager.
  • a. Should be under Android Phone>Android Composite ADB Device
  • b. If it is unrecognized and shows up as a driverless "Android 1.0" device:
    • 1. Right Click>Install/Update Driver>Browse my computer for driver software>Let me pick>Have Disk>AndroidSDKFolder\USB_driver>finish
5. Follow root instructions!

Hope it helps,
jakewill
 
For those who are still unable to root using the current methods, please keep in mind that no one understands how to get the device to connect to adb in recovery. I think even the team that first found this method does not know yet. See the original thread on xda.

There are probably twice as many users who cannot root using these methods than those who can. Many folks try and give up and dont bother to post on the forums. While I bet folks who try and are successful post out of sheer joy. I dont blame them.

Dont feel bad, just be patient and all the kinks will be worked out. I guarantee you that in a few weeks or longer the root method that will be used on this phone will look nothing like the current methods, it will be noob proof.

I myself am a noob but smart enough to know when to be patient. If you've tried the process several times, several computers, several sd cards, several methods, several drivers, etc and something still isnt working then there is something simple preventing it. Let smarter folks find a method that makes those simple things irrelevant.

*rant over*
 
The Android 1.0 drivers are NOT the sdk r3 drivers. They are drivers that come with htcsync on the emmc or with pdanet (i think). Two sets of drivers. Again maybe optional but I decided to eliminate that as a stop.

I did a battery pull at the end because my understanding is that htc has some scripts that try to patch stuff back on reboot. See next post for my full set of success instructions.
 
This compiled from many sources and people. Thanks to all. I hope I got everything because some is from memory.

Go to Admin mode on PC Probably turn off firewall and crap like that.
Install r3 ADB drivers with modified inf file
Installing HTC Incredible Android SDK Drivers |
Plug the phone in and use the "have disk" option to browse to the usb_driver directory
Install HTC sync from emmc for Android 1.0 driver by plugging in phone as needed to fully load. (optional?)
Create a tools directory from the Android SDK near root (c:\tools) with ADB and such inside
Place the following three files in the tools directory
http://www.shadowmite.com/temp/payload-update.zip
http://www.unrevoked.com/incredible/ota.zip
http://www.unrevoked.com/incredible/busybox
Create a batch file call loop.bat in the tools directory with the following commands
@ECHO OFF
:TOP
adb shell
goto TOP
Save and extract superuser files to tools directory from http://goo.gl/PYcX
USB debugging must be enabled and disk drive the default mount (not charge only)
Take out battery from phone and unplug usb
Insert fresh SD card that is root compatible, 2gig PNY in my case from WM phone that had never been used in the INC.
Open a cmd window on PC
>cd \tools
>loop.bat
put battery back in,
go to hboot (dpad +power),
select fastboot
wait about 10 seconds for the phone to process,
press volume down for recovery,
when you press power and AS YOUR PHONE IS DOING THE SHORT VIBRATE plug in the usb cord.
recovery comes back up and you should get -exec "/system ..." message (Congrats)
Press volume-up and power at the same time
A menu should appear.
Select update.zip and press power.
It should fail.
On the host, run adb push busybox /sdcard/busybox (not really sure how this is getting used)
On the host, run adb push ota.zip /sdcard/update.zip
On the host, prepare at your command prompt but do not press enter: adb push payload-update.zip /sdcard/update.zip
Select update.zip at the menu again by pressing power. Approximately half a second after it starts as soon as you see the yellow text pop up, press enter to run the payload command!
If the timing was right, it should verify the legitimate update, but update with our hack, printing a message like “unrEVOked for Incredible”. Congratulations!
If not push the OTA again and try again getting the payload ready.
On PC
adb shell
/system/bin/su
/system/bin/rm /system/app/CityID.apk
/system/bin/cat /system/bin/sh > /system/bin/su (to make su stick)
/system/bin/chmod 4777 /system/bin/su
ctrl c to exit shell
Better than the above stick get the superuser gui:
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su
**** Pull battery and usb. DO NOT reboot phone! ****
If you want to Wifi tether (either before or after the battery pull above):
make directory called /sdcard/android.tether on the phone
push the EVO fw_bcm4329.bin to /sdcard/android.tether using adb or any method to copy the file
fw_bcm4329.bin
install wireless_tether_2_0_2-pre14.apk from
wireless_tether_2_0_2-pre14.apk - android-wifi-tether - Wireless Tether for Root Users 2.0.2-pre14 *** EXPERIMENTAL *** - Project Hosting on Google Code=
 
thanks, but still no luck for me.

I've tried my XP pc, a linux box, a laptop with XP and linux. same result for all of them

I can connect in debug mode with no problem.
However, it does not connect in recovery.

I tried booting with track+power, volup+power, adb reboot recovery, all gives the same result.

I also tried pushing in and out the sd card several times while booting, someone suggested that, although I cant really go that fast and I dont want to wear out something.

Any other methods I missed?
 
I can not get this point...... "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"............??
 
I get as far as entering the commands then when i scroll down to apply update.zip and having to press enter in the command prompt with "adb push payload-update.zip /sdcard/update.zip"

I then get --Install from sdcard--
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Instillation aborted.

Any ideas??
 
I finally got it. I used an 8gb Sandisk MicroSD. I tried well over 40 times with the card. Eventually, I ended up making it a goldcard just for the hell of it; and it worked on first attempt.

I used the following method:
  1. Turned on the phone (full boot)
  2. Made sure the USB was unplugged
  3. Pulled the battery
  4. Started the loop (adb shell)
  5. Pressed the optical button and power button, pressed the power button again to get to boot menu
  6. Plugged in the USB cord, selected Recovery (once the USB connection was detected)
  7. Waited for 10-15 seconds, got adb access, then went through normal procedures as described by the OP

For some reason, the goldcard formatting triggered the race condition. That, or I ended up being lucky this time around. O_O
 
4 hours last night, 1 more hour today and I've still yet to gain successful access/recognition of my device. I'm throwing in the towel and will wait for a more stable method. I've tried multiple cards, multiple computers, multiple batteries and all have come up with the same result. For all those saying: Well I rooted, follow my guide - good for you. I've done the various methods posted on this site and others and have come up dry. For some of you it's simple, it works and you make a video. For the rest of us: it doesn't work, stop making videos or guides hoping it will get it to work for us. I know what I'm doing, and I've troubleshooted it to hell and back with no results.
 
You must log in or register to reply here.
Back
Top Bottom