Related
I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason
Go to start -> run -> type in CMD
Navigate to the folder where adb is located.
Then type in adb devices to see if it finds ur device.
If not then make sure you have it plugged in and USB debugging is turned on in the phones settings under Development.
Also download the usb drivers/or the whole SDK if you havent yet.
nosaj13 said:
when i try to run adb, it open very briefly and closes.
Click to expand...
Click to collapse
If you try to execute a text mode executable in windows, it will close the terminal window as soon as the program finishes. If you run adb without any arguments, it will print the arguments out terminate. I could say the solution is to open run as and type cmd, but the true answer is to install Linux
nosaj13 said:
I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason
Click to expand...
Click to collapse
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun
when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?
nosaj13 said:
when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?
Click to expand...
Click to collapse
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"
Datruesurfer said:
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun
Click to expand...
Click to collapse
i did all the above steps with no problem at all till i got to number 7. when i typed in fastboot devices it just goes to the next prompt without my phone showing up.
If i plug in my g1 in normal mode i see it at the top under adb and in the usb section as a mass storage device.
In bootloader mode with fastboot on the screen it doesnt show up anywhere in the device manager.
Also when i follow the above quoted steps and type in the "adb shell reboot bootloader" and hit enter i hear the ding you hear when you unplug a usb device, and all instances of the phone then leave the device manager.
i have also uninstalled and reinstalled all drivers for the phone and all drivers that have to do with the usb ports on my win xp machine.
Anyone have any ideas i could try?
I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.
I7oobie said:
I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.
Click to expand...
Click to collapse
thats not it. i have that in the sys 32 folder and also on desktop
Fastboot mode not recognized
I'm having the same problem. I've installed all the correct drivers and in normal mode, I see the Android Composite Device (or something similar) in Device Manager.
As soon as I go into SPL mode (the 3 skateboarding androids screen), the device does not show up.
Anyone have any ideas? Thanks!
Datruesurfer said:
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"
Click to expand...
Click to collapse
When I'm in the Command Prompt and I type C:, the directory still reads C:\Documents and Setting\Reids. It won't change to only C:
Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.
bestwebs said:
Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.
Click to expand...
Click to collapse
Ok, thanks a lot. Got it working now.
I need help trying to flash my cupcake images that I have stored in my fastboot folder. I attached the pictures below. I will accept any help I can get.
EDIT: Doh, I thought I was in another topic.
My bad.
Are adb & adb's dll files located inside the same folder as fastboot??? They are suppose too be.
Is your usb cord directly plugged into your system or thru a hub??
Your phone, i bet is under usb mass....to check, expand your device manager window.
Expand your USB-Mass storage list.
With your phone in fastboot mode, click on the camera key and the back key. With enough time inbetween for your system to recognize that there might be a device hooked up.
Notice any change in the list??
Anyone wanting good instructions
http://androidcommunity.com/forums/f28/nandroid-v2-0-full-nand-backup-and-restore-tool-9336/
Read post 2 and go!
this seems like the most easiest thing to do but i still cant get it to work
i have downloaded everything needed and see ADB Interface on my device manager with a yellow mark on it when i try to update the dirver it fails and i got the drivers and point them to it but seems not to work
my phone is on the fastboot screen with the android skateboards guys
i dont know whats going on if someone know what am also doing wrong can tell me please...
This is what i get
Linux users please go HERE (thanks to bloodychaos)​Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
UPDATE: Not necessary for Windows 7 is installng adb drivers automatically after plugging the device and fastboot ones after rebooting the connected device to bootloader. To get the HTC USB Drivers on different Windows version download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
fonpacific said:
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Click to expand...
Click to collapse
Method 3:
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Good Idea!
Have put a link to this within the GUIDES section of [INDEX][22 SEP 11] ROMS/RECOVERY/ROOT/HBOOT/RADIOS/TWEAKS/GUIDES/etc
I believe that the guide would be more useful if you put in a link to a URL for the HTC Drivers and moved the advice about enabling USB Debugging to the top!
I can now point people at this guide rather than manually instruct them, Thank's you probably just saved me loads of time and aggravation!
Nice Work, Great Help
Excellent! Exactly what I needed. Thanks for showing us this.
Hi an thank you. Good guide.
I believe one important information is missing in the guide:
Before installing the HTC drivers (or HTC sync) it is necessary to temporarily disable AntiVirus software on Windows machines. If you don't do that, Windows won't recognise your phone. After the installation is finished, enable AntiVirus again.
I got this advice somewhere and it was true for me personally. I'm using Windows 7.
Sent from my HTC Desire S using XDA App
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
mimirom said:
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
Click to expand...
Click to collapse
It's very useful, Thanks!!
Doing all this the phone has to be turned off, on, or power button and volume down?
Desire S said:
Doing all this the phone has to be turned off, on, or power button and volume down?
Click to expand...
Click to collapse
You do not need a phone for this guide It is setup for PC
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
This is exactly the purpose of point 4 of the guide (global path setup)
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
bonesy said:
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
Click to expand...
Click to collapse
Agree, added to the first post.
Sent from my Desire S using Tapatalk
Instructions for Linux users???
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
On my Linux system I have installed Java and the whole Android SDK and the set the path of course. If you are a Linux user you should know how to do this. Also there are guides for other devices that are basically the same
amidabuddha said:
Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive (Mirror @MediaFire) or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
Method 3:
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Click to expand...
Click to collapse
Nice work mate
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
OP edited - there is a link to a guide for Linux users
fonpacific said:
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
Click to expand...
Click to collapse
Thank you for the remark, I hope it will help the users with the same problem
Hey Guys, I need help!
after an installation of adb all I get is error:device not found
i entered a code adb shell and hit enter, than i entered
dmesg | grep mmc0, since you cannot put two lines of code at once (I'm a rookie)..
where did I put it wrong?
I can get to recovery of my device, but I get error like:
/I]E:Can't open /cache/recovery/command
I made revolutionary S-OFF..
Thanx for a help!
Rocks
You have to enable USB debugging in the settings.
And while in recovery it should work too
Sent from my HTC Desire S
Problem getting adb installed.
Installed the JDK.
Installed the Android SDK, revision 15.
Now I am stuck, not sure how to install ADB, don't know if it's done from within the SDK manager.
I've got a Rogers i727R. It's running 2.3.5. It's the stock ROM, rooted. I was figuring that I would have to tick the checkbox in Android SDK Manager for 2.3.5 and download those components, and that would give me everything I need.
But there is no 2.3.5. There is 2.2, and 2.3.3, and of course Android 4.
I do have drivers for my phone installed through Kies if that matters. Any pointers in the right direction would be appriciated.
Harry
Thanks goes to Silver<<<<<<
1- Like always enable your Debugging. you can enable that by going to your Settings -> Application -> Development
2- Install the android SDK . you can download it Android SDK
3- Extract the SDK to any folder, Example : C:\Android
4- Make sure you have the drivers installed- In that way your OS can talk to your phone!
now that everything is installed we can go ahead and perform a command :
1. Open the 'run' dialog by pressing the 'Windows' + 'r' buttons on your keyboard (minimize the browser & other non-windows programs) 2. cmd (this will open a DOS prompt) 3. cd c:\Android\tools (go to the directory where you extracted the SDK) 4. adb shell 5. Now you'll see just a '$' 6. logcat
You can now just press the power button on your phone to see what happens. It displays everything the device is doing.
So the thing is: leave your device connected for a while and see what is actually going on when you're not using it. Boom
__________________
OP,
Just install the 'Tools' listed there in the sdk downloader. you dont need to worry about anything else
It seems to also want me to install the Google USB Driver package. Any reason to do that?
harry_fine said:
It seems to also want me to install the Google USB Driver package. Any reason to do that?
Click to expand...
Click to collapse
just do it, it wont affect anything negatively
By the way, it worked great. I can now talk to my phone using the emulator on my PC. I see the list of adb commands, lots of stuff. Seems I can even install apk files, run a remove shell. Very cool.
Lol good luck
Hi after reading through the post on GitHub on how to simply root your shield I have a few questions that the tutorial doesn't make clear:
1)There are a ton of files at the top and not sure what to do with them...
2) There is a bit where it explains "On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz"
But it doesn't say that after you open the directory what you do with it?
Do you keep the window open and that's fine?
Do you type in it's location into command prompt before you type in: fastboot boot zImage_dtb ramfs.img.gz?
Just a bit confused as to what all the files are and where I put them and how they have to be utilised etc
Just need clarification for peace of mind
wanted to post the link but forum won't let me yet
Root explanation
Hi here is the main walkthrough from github but as I said there are a few plot holes for people who are new.
If your SHIELD is already unlocked, you can skip this section.
SHIELD ships with an unlockable bootloader. The bootloader is locked by default, which prevents anyone (including yourself) from booting custom OSes and changing system partitions to potentially obtain extra privileges. This is a significant security feature: in the event that your device gets stolen, an attacker will not be able to retrieve your personal data or use your device if your lock screen has a password set.
By unlocking the bootloader, you allow anyone with physical access to your SHIELD to boot custom images and flash system partitions. This opens the way for an attacker to access your personal information or physically damage your device. For this reason, unlocking the bootloader will erase all your personal data like a factory reset does (so a potential thief cannot get it) and will also void your warranty.
If you know you really, really want to take these risks, here is how you unlock SHIELD's bootloader.
Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable.
On your computer, enter the following command:
fastboot oem unlock
This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting SHIELD
Now your bootloader is unlocked, but you still don't have root access. For this, we need to install SuperSU, and we will do so by booting a custom Linux image that will do this for us.
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable
On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz
The kernel and ramdisk will be downloaded and started. You will see 4 penguins on your screen, and the message ROOTING SHIELD will appear. Shortly after, your device will reboot. Congratulations, you are rooted!
For some unknown reason USB debugging in Developer options might become unchecked after rooting. You will need to re-check it if you want to use ADB.
It is safe to perform the rooting operation as many times as you want (e.g. after an OTA). Your user data will not be erased by rooting itself, it is the act of unlocking the bootloader that does.
Is there anyone who can add a little to this to make it more simple for a noob like me?
I understand there is a file set that is at the top of the page and I downloaded the files which include zImage_dtb ramfs.img.gz
but don't know how to utilise them etc
There are no videos on youtube of how to do it and if anyone can add just a few more steps so that I know where I'm going with this (don't want to brick my system).
I just want controller support installed like Tincore or gamekeyboard so I can unlock the potential of the games library on GooglePlay.
Thanks for reading.
you copy those two files "zImage_dtb" & "ramfs.img.gz" to the same directory your adb and fastboot executeables are (same directory you issued the oem unlock command from)
then navigate to the same directory you did the oem unlock from via command line then issue the command "fastboot boot zImage_dtb ramfs.img.gz"
it's pretty simple but I can run you through a simple example of what I did
1)download android sdk
2)copy platform tools folder to a directory on c drive (exp c:\tools\ )
3)copy the 2 files above to the same folder along with cwm recovery(optional)
4)boot shield into fastboot mode (home+back+power)
5)navigate to the folder with adb, fastboot, and the above files in it.
Code:
cd c:\tools
6)detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection
7)issue oem unlock command and follow the onscreen prompts
Code:
fastboot oem unlock
8)restart device, after a full boot cycle(wipes data), power back into fastboot
9)issue the "rooting image" command, device with automatically reboot
Code:
fastboot boot zImage_dtb ramfs.img.gz
*10) optionally reboot back into fastboot and install cwm recovery
Code:
fastboot flash recovery recovery.img
pretty simple
thanks for fast reply.
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
If your confused by my instructions you need to wait for a "one click" installer, sorry.
gogul1 said:
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
Click to expand...
Click to collapse
Step by step instructions like that would take quite a long time to write. Its basically assumed that navigate is a straight forward instruction, namely, open My Computer, click C:\, click something else, etc etc. 32 bit vs 64 bit, again, you should know what your computer is running and use the correct one respectively.
The reason they dont issue novice instructions is for 1 reason only. People who such as yourself claim to not understand the "jargon" are also those who are more likely to make a mistake when rooting. This can lead to a completely bricked device, ie one that will no longer turn on and load up android, totally dead device. As far as the manufacturer is concerned, a bricked device unless bricked by one of their own updates on a non rooted shield installed correctly, is not covered by warranty. This leads said novice to accuse the tutorial writer of having something wrong in the tutorial when in reality they have clicked the wrong thing etc.
Either way, end result: dead device.
Rooting is not aimed at the novice. It is aimed at the advanced user.
Thank you
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Sorry for being so abrupt, it wasn't my intension, you are trying to learn. I will not give a step by step which I feel would be the best, yet potentially more dangerous option for you though.
The parts written in the "code" blocks are what you copy and paste into the command line. When I say navigate I mean by changing directory via command line. You can copy files with a graphical file manager as it's quicker but navigate could also mean graphically.
Google search how to tell if you are running 32 or 64 bit windows, there are better guides and videos than I would be able to describe in a few lines. I was assuming you had already unlocked your bootloader as it is required before root, I covered it as point of reference only.
Platform tools is a folder in the SDK, if you install the SDK you will see that folder where you install it.
Fastboot is the utility also in the SDK that you run from command line that's in the code blocks I posted. If you run the command it will either give a result saying a device is detected or it won't show anything (no result) and you have an issue. If you have a driver issue then that's a whole other problem with a specific forum topic for, but I also assumed you unlocked your bootloader which would require you have fastboot and driver issue resolved.
Main cause of my snappiness is it says the requirement (first line of what you quoted) is unlocked bootloader and you are asking questions about rooting (step two after unlocking bootloader) didn't realize you were stuck in step 0, trying to figure out where to start.
gogul1 said:
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Click to expand...
Click to collapse
Download 64 bit software for 64 bit windows and 32 bit on 32 bit windows. Only notable exceptions are where a guide explicitly says to get 32 bit for some particular reason (in my case the only time I have come across this is MSI afterburners screen recording facilities only functioning on a 32 bit program for some reason, no 64 bit version) or if you are running 32 bit windows and physically cannot run 64 bit software even though a guide says "use 64 bit java etc etc".
rather interested in installing a graphics card in a laptop seeming as laptops use graphics cards that are soldered down to the motherboard not on a seperate removable card in all with very few (but existant) exceptions.... I think asus, dell and someone else did offer them at one point, its actually what the MXM connector was invented for (but its used for a few other things now instead).
Anyway. Its always good to have clarification. I think the post above me gives a few starting points and as always: google is your friend (so are bing and yahoo, but they are those friends where once you leave your job or school or whatever you probably wont ever see again).
boot achieved
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So I restarted everything and the device is now showing up in the Andriod Device driver list.
I am using minimal adb and Fastboot application. It opens the command menu
I type in
adb reboot bootloader and I get the reply "error:device not found"
any ideas?
Sigh!
gogul1 said:
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So the shield is now showing up in my computer manager under Portable Devices and not under the Android Devices like it did when I installed the custom drivers the first time.
Will this be an issue when I come to root?
Sigh!
Click to expand...
Click to collapse
the MTP driver is for plugging the shield in and viewing the file system. If the device isn't under android devices in device manager then you may need to reinstall the ADB drivers or just double check that the ADB can see the device (it may).
Open a command prompt. type "cd [path to the android sdk]\platform-tools"
Then type "adb devices".
It should list all the android devices it can make a debug connection to. If the Shield is in that list your good, otherwise don't proceed any further until you can rectify that.
The other solution is that you dont need ADB drivers on a linux system for some reason. Don't ask why. I havent a clue. But that would necessitate installing linux.
And something that is useful for finding the adb on the command line again in future for windows. You don't want to "cd" into the correct folder every time (the command line equivalent of opening folders). Sometimes you just want to be able to open the command prompt, type "adb devices" and it to just work. That's doable by altering your system PATH variable.
Open my computer. Right click > Properties, should open the System window.
Left side there should be a button saying "Advanced system settings".
It will open the "System Properties" window to the "Advanced" tab (if it isnt on that tab just switch).
Bottom of the window should be a button saying "Environment Variables...". Click it.
Now the window that appears will be split in 2. User variables and System variables. There is a PATH entry in both, it is best that you only change 1. If you are the only user or you only want your user to be able to access the adb, you can change the User variable. Otherwise you can change the system variable for the adb to work on all users. For me I had to add python to my path once but I wanted to do this for all users so I changed the system one, the PSP SDK I installed however altered the User variable by default. Make your choice and find the variable "PATH" in either one.
Click Edit. A window will appear with Variable name and Variable Value. At this point what I recommend doing is copying the entire contents of value into a notepad file and saving them as a backup. Then cancel and go back into it.
Code:
C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Lua\5.1;C:\Program Files (x86)\Lua\5.1\clibs;C:\Python27;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
That is my Path variable.If you look the path variable is mostly a series of filepaths (or other variables too) which are seperated with ";". When you type a command such as "adb" into a command prompt what windows does is searches the current command prompt directory for a file it can execute which is called "adb" (it ignores extensions unless explicitly given one), if it doesnt find it in the current directory it searches each folder in the system path variable for the same executable (it ignores sub directories, it will only search the folders above on my system). So if we want to be able to type adb from any folder, we need the folder the adb is in to be added to the system path variable.
Simply add this to the end of it
Code:
;[whatever the path to the adb folder on your system is]
It will be whatever you had to add after "cd" to get to the adb earlier (must not leave out the C:\Users etc etc if its stored in your documents, cd will let you get away with ignoring that, the variable requires the FULL filepath).
Save the variable. Open a command prompt. Type adb, should work. If not, QUICKLY RESTORE THE BACKUP BEFORE WORKING OUT WHAT WENT WRONG. Should be safe with the broken variable to be fair, but you don't want to risk anything. If you dont think your going to use the adb often then simply dont bother updating the path variable rather than taking the (minimal) risk.
Wow my path variable is beginning to get a bit long now I only manually added python and lua to it. The rest will be the default entries and the SQL server stuff appears to be from installing visual studio. Yours probably wont match.
hehe you're going to hit me in a minute...
message deleted as I was being a moron....
ok I should be entirely clear as you guys are trying to help
ok I should be entirely clear as you guys are trying to help me so it's best i let you know what I have done up until this point.
Ok so I boot loader my shield.
I downloaded minimal ADB and Fastboot. I also downloaded the drivers you recommended in the forum.
I installed the drivers:
My shield showed up in the computer Manage list as a Portable device.
I chose to install the new drivers, it asked if I still wanted to go ahead as the drivers could not be verified and I said yes.
The drivers installed and the Shield changed from being in the portable list to showing up as an Android device.
Success I believe.
I then opened ADB BOOTLOADER and booted my Shield Manually.
I then typed in the relevant prompts in the command and a list of options showed up on the shield.
It showed my device number in the command prompt which was the one on my shield screen.
I then command the unlock function and the shield offered me the option to lock or unlock.
I chose Unlock and it then rebooted.
When it restarted, my computer reinstalled the device drivers and my shield had reset to factory settings (as it should).
I then looked in the Computer Manage list and my Shield had reverted back to being in the Portable Devices list.
I restarted both again and the Shield then showed up under Android Devices like it did when I installed the custom drivers the first time.
But the name of the device is Nvidia Shield - not Nvidia Shield ADB like in the tutorial video... not sure it that helps.
I enabled USB Debugging,
put the Superuser.apk and Su bin file into the minimal AADB and Bootloader folder.
I then put the Thor-insecure-boot.img in the Minimal ADB and Bootloader folder too.
I started up the command prompt from the minimal ADB and Bootloader.
I then saw this
C:\Program files <X86>\Minimal ADB and Fastboot>
I then typed in adb reboot boot loader and pressed enter
I got
error: device not found
So I decided to take the above advice and opened a command prompt
I typed in cd C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools
and pressed enter:
It repeated what I typed and I then put in adb devices.
It then came back with:
List of Devices attached
but nothing was listed....
doh!
Progress!
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
Do I have to choose one of these in order for it to begin the thor img command?
C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools Just incase you didnt get it earlier. That would be the path required for the variable change above. Just whack a ; on the end of the existing variable and throw that new path on the end and done.
But yes, adb devices not listing shield is not a good thing. Try reinstalling the ADB driver for the shield manually (you cant do it via device manager etc).
cool
I'm past that and now <waiting for device> problem to rectify. Am looking online now but there isn't much on there so far...
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far
picture
ok so here is a pic of my devices list fastboot is there
before boot
This is the devices it can see before I put the shield in boot mode
devices seen after shielf in boot mode
the are the devices seen after I put the Shield in boot mode. It can't see any devices
waiting for devices
This is the screen on the shield in boot mode. The CMD screen says "Waiting for Devices"
There are servel cmds which we can use
But I post only top 10 cmds to help that ones who need
###############
If I make a mistake so please reply with your suggestions
And if you want a cmd in the list .submit your reply with cmd and features ( full detail as you know.).
########cmds###########
For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands. That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.
The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time. The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.
Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!
1. The adb devices command
The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK. Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.
Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!
Now that we have everything set up, let's look at a few more commands.
2. The adb push command
If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.
I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.
3. The adb pull command
If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.
In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.
5. The adb reboot-bootloader and adb reboot recovery commands
Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.
Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.
6. The fastboot devices command
When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating. That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.
7. The fastboot oem unlock command
The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness. Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.
Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device
8. The adb shell command
The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS.
The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.
9. The adb install command
While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.
And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.
10. The adb logcat command
The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.
To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.
You also have to specify the cmds properly.
Hope it help you .
Like my work hit thanks button.
$$$$$$$$$$$$$$$$$$$$$$$$
Any suggestions most welcome.
$$$$$$$$$$$$$$$$$$$$$$$$$