• 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

Don't know if it helps or not, but my comp didn't recognize the phone when in recovery, either (thought it was Android 1.0 and wanted to install new drivers) I just hit cancel on the pop-up and continued and adb worked fine. Using XP 32 bit.
 
how do i find and then install root explorer? will these apps help delete unwanted apps? I already removed city ID, want to delete htc sense, teeter, peep, etc. Thanks for any assistance
 
akvtiger said:
I am with you on this one. My computer doesn't even recognize my phone when in recovery.
Click to expand...

Mine shows up under disk drives, like it's mounting the internal storage, which makes sense. Just wanted to see if others had this happen or had something different.
 
necosino said:
Mine shows up under disk drives, like it's mounting the internal storage, which makes sense. Just wanted to see if others had this happen or had something different.
Click to expand...

I can't even get mine to do that. It just doesn't see it. It works fine in normal mode.
 
Does anyone have any advice about the drivers? All I seem to be getting is "error: device not found" over and over and over.
 
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 deal here is that you're performing a switcheroo, you're substituting the ota update, which has a valid signature, for the payload, which doesn't, at the last second. If you're getting a signature failed message you're injecting the payload too soon and it's failing the signature check. Let it verify the signature and as soon it does, hit enter to replace the ota zip with the payload zip.
 
Can anyone quickly tell me why when I in the cmd prompt and I try to open adb shell I get what looks like a "$"? What is it and what am I doing wrong?
 
blw1230 said:
Can anyone quickly tell me why when I in the cmd prompt and I try to open adb shell I get what looks like a "$"? What is it and what am I doing wrong?
Click to expand...

$ means you don't have root permission. If it changes to #, you have root access.
 
You shouldn't need the loop.bat file anymore if you follow the instructions in the first post of this thread.
 
0tter said:
You shouldn't need the loop.bat file anymore if you follow the instructions in the first post of this thread.
Click to expand...

Followed all the instructions to a t. Even used a stop watch.. Tried 2 diff cards. Plus many many other things. ADB shell does see my phone when it is turned on. Devices show up when phone is on. But nothing I have tried has got me into recovery.
 
i got in but, when i typed

adb push busybox /sdcard/busybox

i got this "cannot stat 'busybox': No such file or directory"

i put all those files in the tools folder already.

everything i push got that message.
 
zeke88 said:
i got in but, when i typed

adb push busybox /sdcard/busybox

i got this "cannot stat 'busybox': No such file or directory"

i put all those files in the tools folder already.
Click to expand...

because its looking for busybox in the tools folder, if you have busybox on the sdcard you can skip that step, but you cant put ota.zip on the sdcard, you need to follow the steps listed in the first post to get that to work correctly, if you need video help check out my videos
http://androidforums.com/all-things-root-incredible/98236-incredible-root-video.html
 
DiegoMejia said:
because its looking for busyboy in the tools folder, if you have busybox on the sdcard you can skip that step, but you cant put ota.zip on the sdcard, you need to follow the steps listed in the first post to get that to work correctly, if you need video help check out my videos
http://androidforums.com/all-things-root-incredible/98236-incredible-root-video.html
Click to expand...

i put all those file in the C:\android\tools folder with adb right?

i used a clean sd card. do i need to create any folders in the sd card before pushing?
 
CAP201006111018.jpg
 
prerunnerseth said:
I DID NOT MAKE THE ROOT PROCEDURE ALL PROPS GO TO THE TEAM AT
UNREVOKED. I just tacked on the perm procedure and regurgitated it in my own words. \

************DISCLAIMER**********
I nor anyone else is responsible if you break your phone. try this at your own risk!!
***********END DISCLAIMER**************

Original procedure here:
public:adb_in_recovery [RootWiki]

donate here:
https://secure.eff.org/site/Donatio...OXY_ID=1570&PROXY_TYPE=22&1840.donation=form1

I am just compiling the Current procedure here.

Install the android SDK
Android SDK | Android Developers

Install HTC Sync From your internal storage.

Download these three files and place them into your android sdk/tools folder (wherever you installed it)
http://www.shadowmite.com/temp/payload-update.zip
http://www.unrevoked.com/incredible/ota.zip
http://www.unrevoked.com/incredible/busybox

Download this file and extract su and Superuser.apk from it
http://bit.ly/brI0EV

Move su and Superuser.apk to your Android SDK/Tools folder



Click on start
then on box at the bottom of your start menu
type cmd

a command window will pop up

navigate to the android SDk Tools directory

type edit loop.bat

in edit enter the following

Code: 
@echo off
:TOP
adb shell
GOTO TOP
press alt-f then x

hit enter for yes


***********ADDED BOTH METHODS for shell in recovery*****************

credit to you_eeeeeediot @ XDA for the new procedure

type loop in the command window and press enter

the screen should fill up with "Error - Device not found"

Unplug the USB

Press and hold the optical Trackball and press power

Once in the menu press power again

Wait 20 seconds for it to do its bit

Plug USB in and wait another 10 seconds for your computer to detect the phone

press menu down to highlight "recovery"

Press power

wait 20 seconds

the screen should change from "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"


If you do not get this message within 10-30 seconds pull the battery and do it over again.

Once you get the above message then click on the cmd window and press ctrl-C to stop the batch file.

If It works skip the method 2 part.

If this doesnt work ... try method 2

*****************Method 2*************************

Shut the phone off

plug the phone into USB

in the command window and type loop

the screen should fill up with "Error - Device not found"

Press the and hold the volume down button then press and hold power

once in the menu press volume down to highlight "recovery"

Press the power button

the screen should change from "error: device not found" to "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"


If you do not get this message within 10-30 seconds pull the battery and do it over again.





*****************end method 2**********************


now you should still be in the triangle with the ! screen. press vol up and power to go back to the menu. DO NOT REBOOT.

Press vol down to highlight "apply: update.zip" and press the power button

It will fail at this.

Go back to the CMD window and type the following commands.

Code: 
adb push busybox /sdcard/busybox
adb push ota.zip /sdcard/update.zip
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
Now type the next command but DO NOT PRESS ENTER YET

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.

If successful you should see
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom