Root Connecting to PC

Thread Starter

Sorry if this has been addressed but I looked around and couldn't find anything. Also I'm kind of a noob to rooting and while I'm alright with technology I'll be the first to admit I'm not an expert by any means.

So i finally took the plunge and rooted yesterday and I'm loving the extra options that are available. However I had a problem rooting on my computer so I did it on my roommates. Since then I have figured out it was a problem with my anti-virus software. So i figured I would be able to connect through my computer after this and deleted everything I used to root on my roommates computer. However after reinstalling Android SDK and unrevoked3 i still haven't been able to connect. Every time i try to do so on command prompt it comes up with a device not found error. Any help would be much appreciated.

Thread Starter

Ok so I guess I didn't have the newest USB driver installed but even after doing that I am still getting the device not found error. I have system, data, and sd card set to mount but still haven't had any luck.

When you reinstalled SDK on this machine, did you place it on the root of the C? Check the location and folders to make sure it's there and the folders are named exactly what you're typing in the prompt.

Also, do you know which version of windows was on each machine in question? Were you using windows in both cases?

So you have the modified driver installed from the Unrevoked3 download bundle now right? The one that has intstructions via an html link? If so, you might try uninstalling HTC Sync if you have it on that machine. I'm not sure if it was only a problem with the root process itself or if it could cause other issues with using the tool.

Also, you didn't by chance forget to re-enable USB debugging? That would most likely cause a lack of recognition.

Are you just trying to get adb shell or have you tried to re-run the unrevoked .exe? I wonder if that would work? Some people that were already rooted the old way ran it to update recovery. Not sure if it would allow itself to be run twice or not but it might be worth a shot.

Worst case scenario you could always unroot and reroot. Seems like there should be an easier way tho.

running unrevoked again now that i'm already rooted won't mess anything up will it?

Click to expand...

I ran it on all three versions to update recovery and twice on the most recent because I accidentally pulled USB before it said done. Worked fine and gave me no issues; however, there is always a first for everything. I wouldn't sweat running it again though.

IN ADDITION: I had to open device manager and DELETE/REMOVE the Driver for the phone then install per unrevoked instructions to the T (Make sure you do driver install while phone is in HBOOT). Worth a shot if you are still having issues with it running.

Not sue why y original driver did not want to go away, but it always stayed and the unrevoked driver would not stick. (WIN7 x64)