• 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

When you get to this part, this is what took me about 30 tries

Code:
adb push payload-update.zip /sdcard/update.zip
Now press the power button on Apply: update.zip within 1/2 second press enter on the command window to execute the above command.

Timing is key, you have to hit it at the correct time, your window is tiny! like throwing a pea into a straw, across the room.

After a few tries i got it, it just needs to be timed right.
 
Jakaro said:
When you get to this part, this is what took me about 30 tries

Code:
adb push payload-update.zip /sdcard/update.zip
Now press the power button on Apply: update.zip within 1/2 second press enter on the command window to execute the above command.

Timing is key, you have to hit it at the correct time, your window is tiny! like throwing a pea into a straw, across the room.

After a few tries i got it, it just needs to be timed right.
Click to expand...

the last time, when i finally got it to work i waited more like a second, not a half a second. i think every time i was trying before i was hitting enter on my laptop to quickly.

now all i need it a kernel for wifi tethering. i tried the tethering apk and it's a no go.
 
Im sure this is a dumb noob question but...are we supposed to extract:

these zip files and place them in the sdk tools dir? Or leave them as is and put them on sdk tools dir?

I know its prob a dumb question but i have done so much reading and trial and error today. When I get to the "adb shell" step it always says error: device not found, but i never get the - exec '/system/bin/sh' failed: No such file or directory (2) - message. Can anyone see where my mistake can be? or is that how its supposed to be untill you get lucky that one time it works?

Thanks,
J
 
Also i forgot to ask...are you guys getting a pop-up from the "found new hardware" wizard? Everytime i plug it back in before typing adb shell it pops up and i just ignore it. I dont know why it appears. I have htc sync installed
 
Droidizzle said:
did anyone get the message:
adb server is out of date. Killing.....
* daemon started successfully*
Click to expand...

I also got that message, it was the first one i got.

I have also achieved root!

4 battery pulls and I seen "exec '/system/bin/sh' failed: No such file or directory (2) -" pop right up.

When applying update.zip I pressed power, said "one" in my head and hit enter. Chmod, City ID, reboot, done.

Thanks all you awesome devs and testers out there!

Win 7 64bit
SDK Drivers manually installed and the .inf was modded with paste bin 323174
Old moto droid 16gb card :D
 
guys, when y'all do the last step, wait till you see the yellow text pop up, as soon as you see it pop up hit enter on your keyboard to send the command adb push payload-update.zip /sdcard/update.zip

that will time it perfectly.. everytime.
 
I've tried over and over last night and for the last 30 minutes this morning. I'm using Windows 7 64 on a Dell E5500, HTC USB cable, 16gb class 6 card, and get error: device not found.
 
Tried this method and finally worked today, unfortunately I won't make it stick yet 'cause I have a replacement phone coming in the mail on Monday, but it does definitely work. Have a Sandisk 16GB card, probably class 2. Worked the second time around after a battery pull. I did not use any loop batch file, just waited 20 seconds after boot in recovery.

I did this on a Win7 64 box, installed the android 1.0 driver using the pdanet files and the addition of the bootloader driver in the .inf, as in:

http://forum.xda-developers.com/showpost.php?p=6765908&postcount=227
 
If you are having trouble with the payload push and getting that 1/2 second perfect you are probably doing it too fast. I tried for 30 minutes and it didn't work. Then a person in the IRC channel suggested to wait until you I saw yellow text on the screen to hit enter and do the push. It worked the first time. Just a tip that might help some.
 
Xystence said:
how are you rebooting into recovery from fastboot? I do not see that option there. I have to go back to bootloader for recovery. Please explain further. I tried now a forth memory card, a 2gb that came with the phone, and I got nothing.
Click to expand...

This worked for me.

Plug in your USB
Press and hold the optical Trackball and press and hold the power button
Once the white menu appears press the power button
Wait 20 seconds. A loading screen will appear with random SD card stuff and then return you back when it is done wait for the usb to be detected.
Press volume down to highlight "recovery"
Press the power button
This will reboot your phone and display a DInc with a red trianlge and ! mark.
Wait 20 seconds
Type adb shell it should say "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"

If it doesn't... pull the battery and try again.

This worked 5 out of 10 times for me. I kept having to go through these steps because I would hit reboot and not apply the update on the next steps lol. It was late and I was tired.
 
AWESOME!!!! I got rid of city ID. now how do I remove other apps like teeter, htc sense, peep, search people, etc. Is there a way to automatically envoke su?

Great job to all those involved in rooting the inc.
 
Is it possible that it's not because of a certain card, but only because it's just a different card? Maybe a different card causes some extra indexing or something causing a different load time.

From the Incredible Drooooiiiid.
 
ShortBusHEMI said:
guys, when y'all do the last step, wait till you see the yellow text pop up, as soon as you see it pop up hit enter on your keyboard to send the command adb push payload-update.zip /sdcard/update.zip

that will time it perfectly.. everytime.
Click to expand...

Yes, I tried about 10 times last night. Called it quits, woke up this morning, tried that, and got it on the first try.
 
Could someone look in their device manager and see what the phone is listed as when its in recovery mode (And adb is working)? I have a feeling that it's a device recognition/driver issue more than anything else.
 
Did it on the first try :p Thanks for the write-up, Prerunnerseth, and thanks to others for the tip about waiting until the yellow text starts.
 
necosino said:
Could someone look in their device manager and see what the phone is listed as when its in recovery mode (And adb is working)? I have a feeling that it's a device recognition/driver issue more than anything else.
Click to expand...

I am with you on this one. My computer doesn't even recognize my phone when in recovery.
 
You must log in or register to reply here.
Back
Top Bottom