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

Root lost on rooting

kobel1up

kobel1up

Android Enthusiast
Hey guys need some input. I have leakv3 and want to root with the new way that was found. I installed everything I needed to install the hack the sdk. I updated my usb port and my phone is connected. I read the how to tell if your phone is communicating with my computer and still nothing. I have my phone in charge only. I read for 4 hours last night on installing the programs to root. I put the hack in tools of sdk, and evileris.

Now I know that many of you will get mad and make comments, but I did as much reading and searching as I can. If you can point me in the right directions or a different direction. Not away from root. lol I will get it one way or another, just hope the smart people can give some advice.
 
"..get mad.."

I doubt that.. some might get frustrated; those of us who rooted non-leaked devices..

..I'll have a look at the leak instructions.

Hang in there. ;)
 
from what I read it needed to be in charge only to root the leak way. I tried both ways, I even uninstalled everything on my computer and started over after I read even more about it just to see if I missed something.
 
kobel1up said:
from what I read it needed to be in charge only to root the leak way. I tried both ways, I even uninstalled everything on my computer and started over after I read even more about it just to see if I missed something.
Click to expand...

You read right.. I had a look at the XDA instruction thread for rooting leaks.. (never read it as most rooters were doing it off of 1.5 then 2.1 OTA ;)).
 
As I read through the instructions the only thing that comes to mind (so far) wrt the non-communication between your Eris and computer, is that the USB driver may not be installed or may be corrupted.

I'd check in device manager (I take it you're using a Windows OS on your computer) to see if the USB ports are all correctly installed.
 
Frisco I have double checked my device manager and my htc is usb port is up to date and connected. it says that my device is working properly. I tried going to sdk then tools and in the search bar typing " adb shell" they said it would respond with a $ sign or a # cant remember which one for nonrooted.
 
Can you tell me exactly at what step you get stuck?

I to had issues at every step of the way. I am actually putting together a doc with pics on how to step by step install and get the android sdk working the way it is supposed to.

Please tell where you are stuck in the process.
 
kobel1up said:
Frisco I have double checked my device manager and my htc is usb port is up to date and connected. it says that my device is working properly. I tried going to sdk then tools and in the search bar typing " adb shell" they said it would respond with a $ sign or a # cant remember which one for nonrooted.
Click to expand...

Unfortunately, 99% of the instructions that I have seen on this forum and xda is missing some step that turns out to be critical.

I was not able to get the # in adb shell after rooting but I installed a terminal program onto my phone and can get root that way.

Where are you stuck?
 
the very first step. the cd C:\android-sdk-windows\tools. I put that in and nothing. I have tried uninstalling all the stuff and redownloading it, after I read more on it. I still get nothing.
 
kobel1up, what exactly is the problem you are having? It's not really clear to me after reading your posts...

I had the absolute worst time getting my USB connection to work. It would work fine for charging, and work fine for mounting the SD card, but I could not get adb to work for the life of me. It just kept saying it couldn't find the device, or something along those lines. Is that what is happening to you?
 
kobel1up said:
the very first step. the cd C:\android-sdk-windows\tools. I put that in and nothing. I have tried uninstalling all the stuff and redownloading it, after I read more on it. I still get nothing.
Click to expand...

By "nothing" are you saying the terminal does not give you an error message or anything, "no such directory," etc?
 
DDustinn, that is the same place I am having my problem. My phone won't connect to my pc. Once I get that I think I can do it, but until then I am stuck.
 
kobel1up said:
the very first step. the cd C:\android-sdk-windows\tools. I put that in and nothing. I have tried uninstalling all the stuff and redownloading it, after I read more on it. I still get nothing.
Click to expand...

That just refers to the directory where you unzipped the Android SDK to. It may or may not (most likely not) be the same.

I don't know how familiar you are with command prompt, but cd = change directory. So you are basically using that command to open your tools folder, within your Android SDK folder.

If you don't want to type it all in, you can just go to the folder using regular Windows Explorer, then click in the address bar on top, select the whole path and copy it. Then go to the command prompt, and to paste you can not use ctrl-v, you have to right-click and then click paste.
 
In the comand promt on my computer, when I type cd C:\android-sdk-windows\tools, it says " the system can not find the path spesified.

sorry for not being more clear. I am watching my 14 month old.
 
went to windows sdk tools and copied that and pasted it to the cmd prompt. Now it says it is not recignized as a internal or external command.
 
Right, just like I said... you probably don't have it in that location.

Did you download and unzip the file android-sdk_r06-windows.zip? Once you do, you need to cd to wherever you unzipped it to. If you unzip it to C:\ then the above command will work. If you unzip it somewhere else, you need to modify the command to reflect that.

For example, if you unzipped the file to your desktop, then you need to do cd c:\users\kobe\desktop\android-sdk-windows\tools (replacing kobe with whatever your user name is on your computer) or something along those lines.

Is that making sense?
 
kobel1up said:
the very first step. the cd C:\android-sdk-windows\tools. I put that in and nothing. I have tried uninstalling all the stuff and redownloading it, after I read more on it. I still get nothing.
Click to expand...

ok.
First when you goto start / run / cmd

just type cd.. then cd.. again until the command prompt says C:\>

the type dir and hit enter

you should see a list of folders on the c drive.

Here is what mine looks like.
Code: 
C:\>dir
 Volume in drive C has no label.
 Volume Serial Number is 9856-AE79
 Directory of C:\
07/15/2010  03:13 PM    <DIR>          android-sdk-windows
06/10/2009  02:42 PM                24 autoexec.bat
06/10/2009  02:42 PM                10 config.sys
07/13/2010  02:08 PM    <DIR>          Program Files
06/07/2010  01:14 PM    <DIR>          Users
07/08/2010  09:12 AM    <DIR>          Windows
               2 File(s)             34 bytes
               4 Dir(s)  29,534,396,416 bytes free
C:\>

now type cd andr and hit the tab button on your keyboard then hit enter. You should now see something like this.

Code: 
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Users\Haxcid\>cd..
C:\Users>cd..
C:\>dir
 Volume in drive C has no label.
 Volume Serial Number is 9856-AE79
 Directory of C:\
07/15/2010  03:13 PM    <DIR>          android-sdk-windows
06/10/2009  02:42 PM                24 autoexec.bat
06/10/2009  02:42 PM                10 config.sys
07/13/2010  02:08 PM    <DIR>          Program Files
06/07/2010  01:14 PM    <DIR>          Users
07/08/2010  09:12 AM    <DIR>          Windows
               2 File(s)             34 bytes
               4 Dir(s)  29,534,445,568 bytes free
C:\>cd android-sdk-windows
C:\android-sdk-windows>

Code: 
C:\>cd android-sdk-windows
C:\android-sdk-windows>cd tools

now do another dir

Code: 
C:\android-sdk-windows\tools>dir
 Volume in drive C has no label.
 Volume Serial Number is 9856-AE79
 Directory of C:\android-sdk-windows\tools
07/15/2010  03:04 PM    <DIR>          .
07/15/2010  03:04 PM    <DIR>          ..
05/07/2010  11:48 AM           578,611 adb.exe
05/07/2010  11:48 AM            96,256 AdbWinApi.dll
05/07/2010  11:48 AM            60,928 AdbWinUsbApi.dll
05/07/2010  11:48 AM             3,394 android.bat
05/07/2010  11:48 AM             1,565 apkbuilder.bat
05/07/2010  11:48 AM             2,129 ddms.bat
05/07/2010  11:48 AM           302,823 dmtracedump.exe
05/07/2010  11:48 AM             1,491 draw9patch.bat
05/07/2010  11:48 AM         8,596,234 emulator.exe
05/07/2010  11:48 AM            17,976 emulator_NOTICE.txt
05/07/2010  11:48 AM           921,075 etc1tool.exe
05/07/2010  11:48 AM           336,613 fastboot.exe
05/07/2010  11:48 AM             1,528 hierarchyviewer.bat
05/07/2010  11:48 AM           216,987 hprof-conv.exe
07/15/2010  03:04 PM    <DIR>          Jet
05/07/2010  11:48 AM             1,680 layoutopt.bat
07/15/2010  03:04 PM    <DIR>          lib
05/07/2010  11:48 AM           212,741 mksdcard.exe
05/07/2010  11:48 AM           205,851 NOTICE.txt
05/07/2010  11:48 AM                33 source.properties
05/07/2010  11:48 AM         1,627,623 sqlite3.exe
05/07/2010  11:48 AM             1,982 traceview.bat
05/07/2010  11:48 AM           628,727 zipalign.exe
              21 File(s)     13,816,247 bytes
               4 Dir(s)  29,534,445,568 bytes free
C:\android-sdk-windows\tools>

Now I know I dont have the files for the root in there, i am at work and in this vlan I cannot access msg boards to download the hack files, I am currently remoted into my office server and surfing the site over remote desktop.

ANYWAY, if you can get that far you should be able to just run the runindos.bat IF the adb drivers are installed correctly in windows and you have your phone plugged in via usb set to charge. I also recommend you use the usb cable that came with the phone and not an aftermarket. I can never get it to work correctly with an after market cable.

Let me know how you are doing so far.
 
kobel1up said:
went to windows sdk tools and copied that and pasted it to the cmd prompt. Now it says it is not recignized as a internal or external command.
Click to expand...

Okay, you need to put cd before it. Remember that cd = change directory.

So you're saying, "change my current directory to c:\blahblahblah so I can see what's in there" just like when you click on a folder in Windows.
 
If I know his file structure I could write him a batch file to run his batch file.

I have to go home now. I will check back in once I get settled in. We will get you through this kobel.
 
I think it really depends on what the prompt is he is seeing when he goes to the command prompt.

For instance, I have seen instances where a user who has several mapped network drives will default to a network drive (i.e. a drive that is not C: )

I'm not sure what the behavior is when you do "cd c:\android-sdk-windows\tools" on a prompt that isn't in c:


In other words, I might break down the command even further like this:

Code: 
c:
cd \
That way when he is in the command prompt, he is at the absolute root of the c: drive.

Then, I would recommend doing a

Code: 
dir
command as recommended a few posts up and see if he can find that folder.

@kobel1up

Type these commands after you open up a new command prompt, one at a time in this order exactly as shown

Code: 
c:
cd \
dir
What we are hoping to see is something like this (pasted from above, note the bold section)

Code: 
C:\>dir
 Volume in drive C has no label.
 Volume Serial Number is 9856-AE79
 Directory of C:\
07/15/2010  03:13 PM    <DIR>          [B]android-sdk-windows[/B]
06/10/2009  02:42 PM                24 autoexec.bat
06/10/2009  02:42 PM                10 config.sys
07/13/2010  02:08 PM    <DIR>          Program Files
06/07/2010  01:14 PM    <DIR>          Users
07/08/2010  09:12 AM    <DIR>          Windows
               2 File(s)             34 bytes
               4 Dir(s)  29,534,396,416 bytes free
C:\>
Do you have anything that resembles android-sdk-windows after you do a "dir" command?

If so then you will want to type these commands in this order

Code: 
cd android-sdk-windows
cd tools
 
I've helped a couple of folks root the old-fashioned way :D and they were stuck because they downloaded and installed the Android SDK and couldn't find it. If this is kobel1up's issue, here's how to find it:

HOW TO NAVIGATE TO THE ANDROID SDK'S TOOLS DIRECTORY

You'll be instructed at some point to use one of the programs / utilities in the Android SDK's tools directory. Can't find it? Here's how to:

1. First, make sure that you have downloaded and installed it (don't forget the USB drivers too).

2. Startup Windows Explorer (Start button, Programs, Accessories, Windows Explorer)

3. Select (left-click) on the "Local Disk (C "in the left-pane of Windows Explorer to set your search focus

4. Enter "adb.exe" (without the double-quotes) in the search box of Windows Explorer (top, right-hand side of the window)

5. Press enter or click on the magnifying-glass icon to start the search

6. When the search finds "adb.exe" file, right click on the file name and note (and/or copy) the value listed to the right of "Location:"(this is the location of the Android SDK's tools directory).

This is what you'll use to "cd" (change directory to) in the Command Prompt.

7. For example, if your search reported that the file was found in

"Location: C:\android\android-sdk-windows\tools"

then you would need to type this in the Command Prompt:

cd C:\android\android-sdk-windows\tools

P.S. this was excerted from http://androidforums.com/all-things...oot-troubleshooting-guide-htc-droid-eris.html
 
thankyou so much for the help you guys are the best.


C:\android-sdk-windows\tools>dir
Volume in drive C has no label.
Volume Serial Number is 9856-AE79
Directory of C:\android-sdk-windows\tools
07/15/2010 03:04 PM <DIR> .
07/15/2010 03:04 PM <DIR> ..
05/07/2010 11:48 AM 578,611 adb.exe
05/07/2010 11:48 AM 96,256 AdbWinApi.dll
05/07/2010 11:48 AM 60,928 AdbWinUsbApi.dll
05/07/2010 11:48 AM 3,394 android.bat
05/07/2010 11:48 AM 1,565 apkbuilder.bat
05/07/2010 11:48 AM 2,129 ddms.bat
05/07/2010 11:48 AM 302,823 dmtracedump.exe
05/07/2010 11:48 AM 1,491 draw9patch.bat
05/07/2010 11:48 AM 8,596,234 emulator.exe
05/07/2010 11:48 AM 17,976 emulator_NOTICE.txt
05/07/2010 11:48 AM 921,075 etc1tool.exe
05/07/2010 11:48 AM 336,613 fastboot.exe
05/07/2010 11:48 AM 1,528 hierarchyviewer.bat
05/07/2010 11:48 AM 216,987 hprof-conv.exe
07/15/2010 03:04 PM <DIR> Jet
05/07/2010 11:48 AM 1,680 layoutopt.bat
07/15/2010 03:04 PM <DIR> lib
05/07/2010 11:48 AM 212,741 mksdcard.exe
05/07/2010 11:48 AM 205,851 NOTICE.txt
05/07/2010 11:48 AM 33 source.properties
05/07/2010 11:48 AM 1,627,623 sqlite3.exe
05/07/2010 11:48 AM 1,982 traceview.bat
05/07/2010 11:48 AM 628,727 zipalign.exe
21 File(s) 13,816,247 bytes
4 Dir(s) 29,534,445,568 bytes free
C:\android-sdk-windows\tools>
I may see the problem. I don't see android-sdk-windows\tools in my comand prompt.
 
You must log in or register to reply here.
Back
Top Bottom