I've just about given up. I downloaded all these programs, drivers, other stuff. I thought I had all the required software. I tried to run adb.exe and it just opens a command prompt and closes right away. I've tried searching and all the guides says download this....this..and this..once you have it all. And it starts from there.
The problem is i downloaded everything and I don't know if its working properly to start adb.
I hate this.
I've even thought about downloaded a whole other OS and running it from my USB drive to see if it's easier.
Anyone know of a good how to video?
I know that's what i'll be making as soon as I get this up and running.
Are you actually running adb through a command prompt or just double clicking the exe?
Sent from my T-Mobile G2 using XDA App
CMP
take a look.
http://www.youtube.com/watch?v=-rTOy5oN0GM
use cmd to run it
Start -> Run -> Type cmd -> Enter
cd whatever/directory/adb.exe/is/in
adb
you should just add the android tools directory to your PATH makes life much easier.
Sent from my T-Mobile G2 using XDA App
Yep editing the path got it to work for me.
Sent from my T-Mobile G2 using XDA App
They are aren't they? The vid shows them in there.
Sent from my T-Mobile G2 using XDA App
if you are having that much issue setting the correct path, just go to your system 32 and copy over the CMD.EXE to the folder you are working in with Android. And then launch CMD from there.
Or just type into command prompt
PATH = %PATH%;C:/Android/Folder/Youre/Working/With/
EDIT:
I just watched your video. You have some problems in there
First, you aren't setting a new path, you are (attempting) to change your working directory in that video, however you are not doing it right.
You have to use the 'cd' command
C:\Current\Work\Space > cd C:\Change\to\this\space
C:\Change\to\this\space > adb devices
bleh bleh bleh bleh
But it would be better to just do the above method.
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
"Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt."
Also, add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android\tools
If you happen to upgrade to Win7 you can easily open the CMD by shift right-click inside the window itself.....applying the path automatically for you.
You will also have too use these drivers located here: http://forum.xda-developers.com/showthread.php?t=802316
or
Use notepad++ to edit that file and add the following lines to the "google.ntxhe "" and the "google.ntamd64" sections:
Code:
;T-Mobile G2 %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91 %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01 ;
Save the file, reinstall drivers, and done...
Click to expand...
Click to collapse
smasraum said:
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
Click to expand...
Click to collapse
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
ddgarcia05 said:
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
Click to expand...
Click to collapse
The G2 isn't included in the current adb drivers that you download separately/with the SDK. You have to edit the inf file to have the G2 recognized. There has been at least 1, maybe a few threads with the lines to add here. I think there's a thread titled something like "I can't get adb to work with my phone" or something like that.
looks like i was doing it right. I was typing "abd" instead of 'adb" it founy device.
Now I guess the have to start sending the files over....
I typed "adb devices" and it picked up my device. with my phone's id number.
I am also about to give up. Some of us are new to Android.. we don't understand SDK and ADB and all these other programs. I do plenty enough reading.. but for some reason can't get these programs to run on Windows 7 x64.
I mean is their a newbs guide for the G2.. for rooting and such?
Yeah there is but you have to read like three guides and watch two videos to fnd everything you need. Ill try to make a quick how to after I finish up mine. I just have to push the apps/install the apps. Did you find the java jdk version. And do the commands on your computers cmp?
Sent from my T-Mobile G2 using XDA App
I always used this guide:
[GUIDE] ADB, Fastboot, and Nandroid for Noobs
Hope it helps
Use the drivers in post 11 in this thread
Unless you rooted your G2.........adb shell will NOT work.
ADB shell needs root access
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
ddgarcia05 said:
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
why not use VISIONary app to root the phone for you?
konoplya said:
why not use VISIONary app to root the phone for you?
Click to expand...
Click to collapse
At the time it wasn't available, but I'm using it now.
Related
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
WE ARE NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE! FOLLOW THE INSTRUCTIONS AND YOU SHOULD BE FINE!
IF YOU HAVE HONEYCOMB 3.1 OR SOME OTHER FIRMWARE OTHER THAN 8.2.3.9 THEN YOU CAN DOWNGRADE VERY EASILY
[HERE IS HOW TO DOWNGRADE]
Some prerequisites to the rooting process:
1) You must have a Windows 7 or XP for this tutorial.
2) You must have a micro SD card in your tablet throughout the procedure. It is safe to remove it AFTER you finish the ALL steps. There's no minimum size requirement but 2gb should be fine.
3) The files needed to root your device from here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) An Asus Transformer (16 or 32gb) running Honeycomb 3.0.1...SEE DOWNGRADE INSTRUCTIONS IF YOU ARE ON HONEYCOMB 3.1
5) Data cable
6) Me guiding you
Alright now that you have everything set, lets begin the rooting process!
1) You need to make sure your device has USB Debugging activated. To do this go to Setting>Applications>Development and make sure there is a check box next to USB Debugging. Leave the other two options unchecked.
2) Check what your Build Number is. Go to Settings>About Tablet>Build Number. Make a note. If it it says 0423 at the end (or anything after) then you use V5. If its anything below (ex. 0421) then you use V4. Got it?
3) Hook up your Transformer to your computer via the USB Cable. Avoid USB hubs if possible.
4) If you are using Windows 7 then the drivers will install automatically. I have provided you with the link to the drivers here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) Download & Install the Asus Sync software. I know its annoying to have to install bloatware that you will probably never use but in this case, your Windows machine will not detect your device without it.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
5) Insert the MicroSD card into your Transformer and make sure that the tablet recognizes it. I have had issues with some cards not being detected.
6) Now we need to download the Android SDK. You can download it here.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
7) Install the Java Developer Kit if you dont have it already. You can find it here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
*Edit*
Even after you install the JDK the SDK installer might say that its not installed. Just click back then next again (or restart the installer again) and it should work-Thanks Codiox
8) Install the SDK to the root of your hard drive and put it in a folder called Android. This means when you click the local disk C: drive the first folder you should see is the Android folder. This will make using the command prompt simple.
9) Go to Start>All Programs>Android SDK and click in the SDK Manager. When you're presented with the option to install all updates (and you have time to do so) let it all install. All you really need though is the Android SDK Provision tools update. You can hit cancel once that is installed successfully.
10) Open up the command prompt
11) Lets being with the terminal commands. Make sure you press the ENTER button after every command line. You can copy and paste the commands if you want; if you do so, you dont need to press enter to go to the next line.
12.
Code:
adb devices
make sure your device is detected
13.
Code:
adb push gingerbreakBB /data/local/
14.
Code:
adb shell chmod 777 /data/local/gingerbreakBB
15.
Code:
adb shell
you will get a $ sign.
16.
Code:
./data/local/gingerbreakBB
nothing will happen at first, but after about 5 minutes, you will see a long list of "vold" commands....let this run its course...go grab a sandwich or something.
If for some reason it says permission denied, try running these commands immediately after running the
Code:
./data/local/gingerbreakBB
command. DO THIS ONLY IF YOU GET PERMISSION DENIED LIKE IN MY VIDEO! If you didnt get the permission denied error, continue to step 20.
17.
Code:
rm /data/local/tmp/boomsh
then type.
18.
Code:
rm /data/local/tmp/sh
then redo step 16 again which is
19.
Code:
./data/local/gingerbreakBB
20. After about 7-10 minutes you will be presented with a # sign. THIS IS GOOD!
21. Open ANOTHER command prompt window; the same way you opened the first one. DO NOT FOR ANY REASON CLOSE THE FIRST COMMAND PROMPT. LEAVE IT OPEN IN THE BACKGROUND!
22. type
Code:
adb devices
23. PAY ATTENTION HERE! Remember when I told you to look at your build number? We need that information now. If your tablet has a build number ON OR AFTER 0423 then use this command
Code:
adb push CWM_BLOB_V5 /data/local
If it has a build number BEFORE 0423 (ie. 0422) then use this command
Code:
adb push CWM_BLOB_V4 /data/local
24. Whatever number you used above, you will continue to use it throughout the installation! REPLACE THE # SIGN WITH WHATEVER YOUR NUMBER ABOVE WAS; EITHER 4 OR 5.
Type
Code:
adb pull /data/local/CWM_BLOB_V# cwmblob_retransfer
then
25. Return BACK to the PREVIOUS command prompt that had the # sign just sitting there.
26. Type
Code:
dd if=/data/local/CWM_BLOB_V# of=/dev/block/mmcblk0p4
Replace # with your number (4 or 5)
27.
Code:
adb shell
28.
Code:
reboot
29. Your device will reboot now. This will take a bit longer than a normal reboot so be patient.
30.
Code:
adb remount
31.
Code:
adb push su /system/xbin
32.
Code:
adb push Superuser.apk /system/app/
33.
Code:
adb shell
34.
Code:
reboot
THAT'S IT! Congratulations! You have successfully rooted your Asus Transformer. I hope this tutorial made it simple for you. Let us know if you have any questions!
Credit Goes To Androidroot.mobi devs for the original rooting process.
Original Thread:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
+1 Thanks!
So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
combat goofwing said:
So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
Click to expand...
Click to collapse
sorry i keep forget that Vista existed at one point ...yes it should work fine on vista
Does anyone know when it will get 3.1 support?
PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
Not until someone updates the modifies blob files for 3.1. However you can use this how-to to root the 3.0.1 build then flash a 3.1 ROM. Unless you're on 3.1 now with no root...then ur SOL for just a but longer
Sent from my ThunderBolt using Tapatalk
damn,!!!!! awsome post should be sticky, thank u for your support and work
Added to ultimate thread. Nice job.
Should be in the dev section as a sticky.
Trouble installing development kit
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka
PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
If you have root already you can update to 3.1 using the modified update that is floating around here. Sorry I don't have a link.
sheureka said:
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka
Click to expand...
Click to collapse
just click on the "back" button, then the "next" button and you'll be fine. its a known bug.
Good write up. There are two problems. You do not give credit to the source of the root method (apache/bumblebee and rayman) and they specifically asked that their method not be reposted, only linked.
If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk
Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
I just saw that someone over on AsusTransform site has exactly the same problem. I did unplug and everything seems to be running fine (though it's obviously not rooted) but it's a little scary.
sheureka said:
Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
Click to expand...
Click to collapse
I have another person on my forum with the same issue. What was your battery life when you attempted this? His was below 20%. Are u using a USB hub? My recommendations are to reboot, try a different usb port, charge the tab above 50% if its low and try again. You most likely need to do steps 17-19 since you pushed the gingerbreak file already. Let me kknow iif that works.
ayman07 said:
If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Video and writeup are 2 different things. Thanks for adding the credit.
Sent from my Transformer TF101 using XDA Premium App
My battery was about 80% and I'm directly plugged into my desktop. - sheureka
sheureka said:
My battery was about 80% and I'm directly plugged into my desktop. - sheureka
Click to expand...
Click to collapse
I apologize, I was mistaken. This will not work on the following firmware
8.2.3.13
There is currently no way to root this and I dont think theres a way to downgrade either. I will adjust my post. Sorry about that :-( your tab is fine though. No harm done.
Sent from my Transformer TF101 using Tapatalk
Never mind.
Well I try to root my phone i installed sdk and I did the adb but the cmd on my pc dose not see my phone all am trying to do is downgrade my phone so I can root how do I get the pc to see my phone it told me it hass adb but when I run cmd it dose not know its there plz help I really want this phone root it I been at this for the last 2 weeks
Sent from my T-Mobile G2 using xda premium
explain what you did and what you do exactly. Based on which instruction.
you're computer is a Windows VP / Vista / 7?
did you reboot afgter installing?
And post the command line you have.
We will without question need to know what you tried before anyone here can help.
Also, check to see if you phone was in USB debug mode. If it was not, no matter what you try it will not work.
I try to to downgrade my phone useing cm fourm on how to doundgrade a g2 well I use the coustom usb and I put it in the sdk folder were it was suppost to go well I try to run cmd and it tells me no such thing sorry not exacly what it says but close to what it dose tell me so now what do I do I really want a rom on this
Sent from my T-Mobile G2 using xda premium
First off, not to knock you, and I apologize if English isn't your first language, but you're posts are very hard to follow. Some punctuation and spelling would help immensely.
Second, you need to give us more detail. Step by step, as to what you are doing (commands entered, what error messages actually say, etc).
Third, some simple instructions are below, see if it helps:
1) Go to Start > Run (or hold the Windows Key and press R) to give you the run prompt.
See picture #1
2) At the command prompt, type in (without quotes) "cd\program files\android\android-sdk\platform-tools" NOTE: This is the path for default install for the google SDK installer with Windows 32bit. If you are running Windows 64bit I believe it is "cd\program files (x86)\android\android-sdk\platform-tools"
See picture #2
3) type in "adb" (again, minus quotes) to see the list of adb commands.
See picture #3
Hopefully you can take it from there.
Ok I have windows 7 well I download the sdk ok I was doing every thing from the cm forms well I all so did the thing with adb were on the cm forms it ask me to download the usb thing in place it in the folder were in extras sorry if miss spell I rann cumman prompt cmd it dose not see my phone that it it says here go this this in the forms look for need help that's my post to
Sent from my T-Mobile G2 using xda premium
Hey mate, I'd be willing to help you if you took your time (slowed down) and worked on your posts a bit. I tried really hard to understand what you're trying to tell us and I just can't get it.
Sent from my HTC Vision using XDA App
Can any one call me in help 614 962 1447
Sent from my T-Mobile G2 using xda premium
I tried to install sdk. Cm told me in their forums to install an adb in usb custom. The cmd does not recognize my phone.
Sent from my T-Mobile G2 using xda premium
Ok, so we will assume the SDK is installed properly. Then you open a command prompt and change the directory to the directory you installed the SDK using the "cd" command. From there you type "adb devices" and what is displayed on the command prompt?
We need to take this one step at a time. Everyone wants to help, but we need to be able to understand what is going on.
Can some one call me and help me plz 614 962 1447
Sent from my T-Mobile G2 using xda premium
Ok now the pc that my phone adb ok but when I put in adb divice cmd dose not see it and what's with this run thing all I do in my pc is run search for cmd
Sent from my T-Mobile G2 using xda premium
I think I understand what you are saying. So, you search for cmd in windows and then click on it to open. Once you do that you enter "adb devices" correct? Do you enter any other commands before "adb devices?" Also, have you gone to settings/apps/development and clicked Enable USB Debug on your phone?
I doubt you will find anyone willing to call you, but if you can clearly tell us what is going on; you will find help here.
Yes you are right I did adb devices but no other commainds but it tells me no external devices and some other stuff it says
Sent from my T-Mobile G2 using xda premium
And debuging good on my phone and sdk is on windows and under device manger it tells me my phone adb
Sent from my T-Mobile G2 using xda premium
This could be your problem. Before you enter "adb devices" you need to change the directory to where you installed the SDK. So, open a command prompt, enter "cd [directory where you installed the SDK]." Once the directory is changed enter "adb devices."
As for the location of the SDK, if you installed it to the hard drive it would be: C:\android-sdk\platform-tools. So you would enter "cd c:\android-sdk\platform-tools."
Try that and let us know what happens.
when I put this in cmd c:\program files (x86)\android\android-sdk\platform-tools it tells me file name derectory name or volume label syntax is incorrect
Sent from my T-Mobile G2 using xda premium
When I run cmd in put adb devices it tells me the system can not find the path specified
Sent from my T-Mobile G2 using xda premium
Can I plz get help
Sent from my T-Mobile G2 using xda premium
ok, these are not the recommended ways of gaining root, but your knowledge seems to be not good enough for the usual guides... (you are sure you want to root?)
here is one tool:
http://forum.xda-developers.com/showthread.php?t=1097977
or contact this guy:
http://forum.xda-developers.com/showthread.php?t=1500370
good luck (or ask for a remote session - i dont have time for this right now)
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Same Problem
I am having same exact issue..windows 7 would love some help on this! Just need root for adblock and I am set this device rocks! +rid bloatware but thats a given.
eadred said:
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Click to expand...
Click to collapse
Well, glad to not be the only one. Let's find what we have in common, maybe we'll find where it comes from. Do you also have windows xp? Have you by any chance windowblinds installed? Have you run as administrator? Anything particular otherwise?
Same Problem
I have Windows 7 and no windows blinds...I have tried different ports and also ran as administrator. I have successfully rooted OG Droid, Droid Bionic , and Galaxy Nexus. I think I got spoiled by how easy the Nexus was to root and change roms. Love the G2 just need to get the root to stick. Every time I hit a key to continue from root bat the command window closes. I was able to read quickly a line that says unknown error has occured. Not sure why this is happening. I have tried two different drivers LG VZW_United_WHQL_v2.11.1.exe and LGUnitedMobileDriver.exe with no luck.
Using the application usbdeview, I can't see the lg driver even though I have installed it. Is it the same for you?
Actually a lg driver is indeed listed
LGE Android Phone AndroidNet Sooner Single ADB Interface Vendor Specific No Yes No No 02231cddcf4eb680 19.10.2013 19:25:05 19.10.2013 23:37:42 1004 631f 2.32 ff 42 01 andnetadb ADB Interface DriverNet lgandnetadb.sys USB Google, Inc AndroidNet Sooner Single ADB Interface 3.10.0.0 USB\Vid_1004&Pid_631f\02231cddcf4eb680
Same Problem
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
maclv said:
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
Click to expand...
Click to collapse
Not sure what you mean. On my side, if I write adb devices in a command prompt, I only get one line of numbers and beside it: 'device'. And that's it. Do you get additonal infos?
When I run the root.bat, I can hardly read the text before it closes, but from what I saw and completing with the text that you can get by editing the root.bat, I tend to think that the following is written before it closes:
Looking for device...
.\adb.exe wait-for-device
Determining carrier...
On a chat before, someone suggested me to right click the root.bat and clic edit to view the content of the bat. And then manualy reproduce in adb by pushing the necessary files and such... But I haven't yet given hope that it works with the bat. But maybe you feel like giving it a shot.
I have ESET as antivirus
Same Problem
No luck manual editing the root bat. When I type adb device it list VS980_4G - and a set of numbers
I was wondering if I should try another root method. I have seen on an italian forum someone who rooted with a chinese method. I have no time right now, but I might test it in a few days.
http://translate.google.com/transla...&hl=en&langpair=auto|en&tbb=1&ie=windows-1252
Btw in which country are you? I bought my mobile phone from digitec in switzerland.
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
maclv said:
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
please let me know if you get through. I'm stuck and willing to return the device. it's killing me
Tried on another computer. Was done within second. It will remain a mystery why it didn't work on mine. But hey, done is done! :good:
I will try on another cpu hmmmm
Sent from my VS980 4G using Tapatalk
hit windows key+r,enter cmd then hit run.
then navigate via cd c:\folder\folderthatcontainsroot.bat
then open root.bat by typing it in cmd.
that should stop tje autoclosing of cmd when opening via windows Explorer.
Sent from my LG-D802
Thank you for the tip. I was able to get root switching to a different cpu. .but glad I will be able to use my main cpu in the future. Thank you both for the help.
Sent from my VS980 4G using Tapatalk
For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?
painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app
alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app
I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)
Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app
Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app