• 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

this is correct?
 

Attachments

  • Capture.JPG
    Capture.JPG
    42.5 KB · Views: 184
So I'm still getting nothing :( anyone have an idea?
I installed the SDK, HTC Sync, tried method one and two but nothing!
 
prerunnerseth said:
Barnacle seems to work now with the new SU... but never shows up in my laptops wireless list.
Click to expand...

DiegoMejia said:
lol i just tested that myself, wifitether at least shows up on my wireless list.but never connects
Click to expand...

I've heard in the ##incredibleroot chat that if you toggle the wifi off and on and ping the computer/device from the phone then it starts working.

Update: Yea there are more than one report of people getting tethering to work. Some people it works right away, some people have to do some tweaking.
 
I am having no luck. All I get is the device not found error. It never changes for me. Any words of wisdom somebody can pass along?
 
Ruggar said:
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.
Click to expand...
This doesn't seem to be a very time critical way of doing it. Did you use the looped adb shell? How does it go from "device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -" by only running adb shell once??? Did you need to load the 1.0 Android drivers as well? I notice that using this startup causes a different set of drivers being needed than the ADB r3 drivers.
 
DiegoMejia said:
i know, because i loaded it correctly, just reread the steps on this thread or follow my video. Either way will work
Click to expand...

Method 1: How do I get loop to run correctly. When I enter loop, it puts me in "adb shell".

Method 2: I never finds the device.

Any suggestions?
 
Lars said:
This doesn't seem to be a very time critical way of doing it. Did you use the looped adb shell? How does it go from "device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -" by only running adb shell once??? Did you need to load the 1.0 Android drivers as well? I notice that using this startup causes a different set of drivers being needed than the ADB r3 drivers.
Click to expand...

To answer in order:
1: No using the FASTBOOT menu you do not have to use the looped adb shell method.
2: It doesn't go from "device not found" to "exec ....". There is no transition, With this method you only need to run the command once. When you type adb shell if you get the "device not found" message just pull the battery and try it again. If you get the other message, it worked, and continue on with the process. Like I said, I had about 50% luck with it.
3: All of the pre-setup steps, downloading the SDK, drivers etc were done normally per the instructions.
 
Ruggar said:
To answer in order:
1: No using the FASTBOOT menu you do not have to use the looped adb shell method.
2: It doesn't go from "device not found" to "exec ....". There is no transition, With this method you only need to run the command once. When you type adb shell if you get the "device not found" message just pull the battery and try it again. If you get the other message, it worked, and continue on with the process. Like I said, I had about 50% luck with it.
3: All of the pre-setup steps, downloading the SDK, drivers etc were done normally per the instructions.
Click to expand...
Something has to be missing. I recall the fastboot method tripping something on the PC asking for other drivers. ADB works under a normal boot. It doesn't sound like you are particularly concered of the timing as to when to issue the adb shell. Just roughly 20 seconds after the recovery ! screen after a fastboot. I looped the hell out of the adb shell on that screen multiple times and nothing.
 
Lars said:
Something has to be missing. I recall the fastboot method tripping something on the PC asking for other drivers. ADB works under a normal boot. It doesn't sound like you are particularly concered of the timing as to when to issue the adb shell. Just roughly 20 seconds after the recovery ! screen after a fastboot. I looped the hell out of the adb shell on that screen multiple times and nothing.
Click to expand...

I was never prompted for other drivers I can promise you that. You are correct in that I issued the adb shell command roughly 20 seconds after the recovery screen. I used the audible que from my computer that I assume means the USB is recognized and shortly after issue the command. You either get device not found and simply pull the battery and start again or you don't and you're in. Then you get to play whack a mole with pushing the payload at just the right time to slip it in. I'd make a video but others have already so it seems pointless.
 
Lars said:
That's the normal adb operation and not adb running in recovery mode.
Click to expand...

So what would you do from here? I thought it needed to be looping before the phone goes into recovery or am I totally missing something which is totally possible?
 
I FINALLY got it to work!!

I tried every little trick and here is what I noticed.

- unplug your phone from your USB cable
- turn your phone on normally...like you would every day. so you can use it.
- then don't power it down...just pull the battery out
- then press the optical jotstick & power button
- then follow the rest of the instructions listed in previous posts

i think for some reason...rebooting the phone into recovery from various states does not work (it did not for me). i think when you just kill the phone from it's normal state and then boot into recovery it works (it did for me).

i hope this helps!!!
 
stanfna said:
I FINALLY got it to work!!

I tried every little trick and here is what I noticed.

- unplug your phone from your USB cable
- turn your phone on normally...like you would every day. so you can use it.
- then don't power it down...just pull the battery out
- then press the optical jotstick & power button
- then follow the rest of the instructions listed in previous posts

i think for some reason...rebooting the phone into recovery from various states does not work (it did not for me). i think when you just kill the phone from it's normal state and then boot into recovery it works (it did for me).

i hope this helps!!!
Click to expand...

When do you plug your usb cable back in and did you get loop running correctly while your phone was still powered on?
 
stanfna said:
once the fastboot screen was up

loop had been running from all the previous attempts.
Click to expand...

Ok I've noticed that when I plug my usb cable in before I go into recovery, and loop is running, I don't get the "normal" usb sound. I get 3 quick tones instead of the "normal" long then short tone a normal usb cable makes...

Any idea on that one???

Screw it. Hopefully someone will get the one-click method sooner rather than later. (Big frustrated sigh)
 
You must log in or register to reply here.
Back
Top Bottom