I've downloaded drivers, sdk, and did everything said to root sprint galaxy 4g. when im in cmd i type "cd c:\android\tools\adb shell" to type commands to its keeps saying its not a path. any help. trying to root phone with major headachs.
Try the oneclick instead, it does all that for you.
Sent from my SPH-D700 using XDA Premium App
Use one click with cwm version2 for rfs or version 3 for ext4
Sent From My Evo Killer!
adb.exe has been moved from "tools" to "platform-tools" in the more recent SDKs...so follow the same steps but just make sure you use the new location. Or as others have mentioned use packages that already include adb.exe and you don't have to worry about it.
Related
I apologize if this is already answered somewhere. I searched everywhere and could not find anything, but I might be using the wrong wording.
Anyways I am attempting to root my G2. I have managed to get adb onto the computer and it recognizes my phone. However, the next step in the wiki says to:
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
However, it gives me error messages such as 'adb' is not recognized. I'm sure I am missing stupid but I cannot figure it out. Thanks in advance.
Just use visionary, it is much easier. Click temp root and when it is done perm root
http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
Sent from my HTC Desire using XDA Premium App
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
o0olove said:
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used visionary and it worked just fine, but you do what you feel best with
Sent from my HTC Desire using XDA Premium App
bradley_e_smith said:
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I checked the path a few times because I thought that was the problem. However, it all looks good. I'm going to try on another computer tonight and see if that helps.
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
I used visionary and terminal emulator and haven't had any problems at all.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app
tazz9690 said:
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
Click to expand...
Click to collapse
Yes it shows my phone when I type 'ADB Devices' That's what's causing my confusion. I've reinstalled all the drivers that are needed. From what I am seeing it SHOULD work.
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
30bushido1 said:
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What version of windows are you on? You followed all of the instructions on setting up adb from that thread in the Shift forums? I also rooted my roomate's Shift, and I read that adb setup tutorial when I was over there. It was pretty solid. I already had adb set up, but read it through to see. When I set up adb, I had someone advise to me to place the adb.exe, and that .dll file (found in platform tools, in the SDK download) in my 'system32' folder of my PC. Once I placed those two files in the 'system32' folder, adb has worked flawlessly.
Also, have you made sure you have all the correct drivers installed? I believe I also had to install HTC Sync, because that installed some drivers that were necessary. Once it installed, I uninstalled it (the drivers will remain installed) because it can interfere with adb communication, apparently. Hope you get it set up. Once you do, rooting the Shift wasn't hard. Just follow the instructions to the t, and just copy and paste the commands, to eliminate the possibility of messing up the commands.
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
30bushido1 said:
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You're welcome, feel free to PM me if you have any more issues.
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Muellersirch said:
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Click to expand...
Click to collapse
By putting the adb.exe and the .dll files in the 'system32' folder, that will allow you to execute adb commands from any directory in the command prompt. I don't have to navigate to my sdk tools to use adb. It saves a few steps, so you can just open up your command prompt and command away.
Or you can put the directory that contains adb in your system PATH. This will let you execute adb in a command prompt anywhere...
Sent from my ADR6300 using XDA App
I'm running wd7. I've gone through it again and installed the drivers then uninstall HTC sync I'm still not able to access sdk through the command prompt. I know its something simple I'm missing how do I move adb to the system path
Sent from my PC36100 using XDA App
C:\user\paul>
Is what the terminal reads any command I enter is not recognized as an internal or external command.
I have got the command list to show up but cannot exicute any of them
Sent from my PC36100 using XDA App
I know this is a noob question but I installed the sdk on my windows vista 32bit PC I've read like everything I could about doing this but I can't seem to get adb working when I run cmd adb it says 'adb' is not recongnized as an internal or external command, operable program or batch file. I'm pretty new to this but want to be able to use this any help would be great thanks in advance..
Sent from my PC36100 using XDA App
Are you running adb from within the /platform-tools directory?
The basics of adb
http://forum.xda-developers.com/showthread.php?t=694250
You have to run the commands from wherever you extracted the sdk ex I put mine on the main c drive so I have to type this first:
cd c:/android-sdk-windows/tools
Sent from my PC36100 using XDA Premium App
bender1077 said:
Are you running adb from within the /platform-tools directory?
Click to expand...
Click to collapse
I tried it from the start menu and that was what it said I also tried it in platform-tools it just flashes the screen for a second and thats all..
Sent from my PC36100 using XDA App
You're getting that error because you're not in the folder where adb is. Look in the platform-tools folder. You can run it from that folder, or just copy it into the tools folder.
teh roxxorz said:
You can run it from that folder, or just copy it into the tools folder.
Click to expand...
Click to collapse
If all you are using from the SDK is ADB, then moving ADB to the /tools directory is not an issue. This will bork the functionality of other tools in the SDK though.
U can also add it to ur command lines so u don't have to always be in ur sdk folder to use it. Google adb and there r instructions on how to do this. Its very easy
I recently purchased a nexus and i am new to this, i have tried everything to root this on a mac and had no success. Has any one else rooted this on a mac? If so could you walk me through it. Thanks in advance!
Are you sure you have ADB and fastboot setup correctly?
What part are you getting stuck at?
I dont think so, i downloaded some things called superboot and i keep messing up in terminal i think...did you use superboot?
Yes sir I did, also on a mac. Here, you might want to checkout this link to make sure you have everything set up properly before you start the superboot process:
http://forum.xda-developers.com/showthread.php?p=9842005
The guide will talk about fastboot towards the bottom, you can download a fastboot file from this page:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Okay, thank you very much, i will try it out and let you know if it wprks
Sounds good, let me know
on the (export PATH=${PATH}: part when your are supposed to drag the folder into text edit im getting just the folder icon instead of (export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools) like the guy said his looked, is that okay, or do I need to start over?
Nevermind, I got it!
Sorry! I was asleep haha if you need more help I'll be checking in
Sent from my Galaxy Nexus using xda premium
Thats fine lol, okay on the Fastboot part when you find SDK/platform-tools in terminal , i type in ls> desktop> SDK > platform-tools and it says its not there and its on my desktop. Am i skipping anything in terminal?
I actually can't get the ls part to work.. I just ignore that part haha but the fastboot file should be in your tools folder of platform-tools I believe
im on the superboot part now...is this a good method? http://www.helloandroid.com/content/root-galaxy-nexus-superboot
Yessir, that is the method I used but I found the instructions in the development forum of the galaxy nexus section.. should be the same method though
Sent from my Galaxy Nexus using xda premium
Okay , last question and ill leave you alone lol, where it says (MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh')
I have the sdk located on my desktop, how would i type that in terminal to find it so i can do this step?
Haha, no worries
To get to that folder in terminal, you want to type "cd ~" without the quotation marks, and then you can drag the folder into the terminal window and it the path to that folder should pop up in the terminal, then just hit enter
Okay, thanks alot man, i really appreciate your help
Anytime! Feel free to PM me if you have any other questions!
i was trying to install a rom,and in the CWM i formated the sd along with the others by mistake,now i can't reach the rom i transfered and the phones won't boot for sure
i tried to flash the google stock with gnex toolkit (using step 9) and i downloaded the file but it fails and what is shown to me is what you have in the attached image,it gets stuck at the "sending radio"
what should i do,i really need urgent help here
please just know that i'm a total noob so please tell me what to do step by step so i could understand
What Nexus do u have gsm or verizon? If it's Verizon you picked the wrong version and it's flashing a gsm radio. If it's gsm it could be a bad download or you picked the wrong version not too sure about that I have a Verizon nexus
Sent from my Galaxy Nexus using xda premium
it's a GSM,and i chose the right version stated in the toolkit thread and the one i installed the drivers and unlocked the bootloader and rooted the phones with it
is there a way to transfer a file in the CWM mode? can i transfer the rom in this mode?
You should do these commands in fastboot instead of using a toolkit.
Here is a step by step guide how to get back to stock. http://forum.xda-developers.com/showthread.php?t=1626895
Edit: to answer you question about pushing a file in recovery, you can. You must use adb. The command is adb push nameoffile.zip /data/media
Sent from my Nexus 7 using xda premium
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Put the zip in the same folder and hold shift and right click select open command prompt here. Then adb push the zip onto your phone.
You got clockwork recovery? If so, you need cwm flashable version of radio, boot loader and ROM
Sent from my Galaxy Nexus using xda app-developers app
rok3r said:
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Click to expand...
Click to collapse
Yes move it to the same directory. Open the command window in that directory. (Shift+right click > open command window here)
Then type: adb push rom.zip /data/media
Sent from my Galaxy Nexus using xda premium
OMG!!! Device not found,same message i got in the toolkit when i tried to push the files (((((((
drivers?
Yes most likely a driver issue. Type adb devices in command. If if returns a device number everything is set up correctly. If not reinstall the drivers.
Sent from my Galaxy Nexus using xda premium
If you are trying to push in bootloader adb won't work. Get in to recovery cwm works fine than do the adB push
THAAAAAAAANNNNKKKKSSSSSS!!!
seriously thanks for the help,i am totally new to this and felt like i killed my phones with my inexperienced self
i was a driver problem and i used the toolkit to uninstall and install again the driver and then used the toolkit to push the files but it said something like adb is already in root access or whatever so i headed to the adb.exe and it did it!!!!
thanks man for the great help again!!!!!:good:
this will make me learn to do a nandroid hahahaha
@atifsh i was in the CWM,it was a driver problem after all,thanks for your reply