Database Info

fastboot questions

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

Completely unable to boot into download mode

As the title says i am completely unable to boot into download mode. I gave tried every method other than adb (I can't for the life of me figure out how to use adb) and my device simply WILL NOT boot into download mode. This is a rather discouraging issue for me, since it disables me from flashing kernels with odin3...
I have tried booting while plugged in and turned off with Odin open, tried with the phone unplugged and turned off (volume down + power) and every method simply starts the phone as normal, or loops boot animations until I release the buttons. And both volume buttos +power simply leads to recovery mode.
Please help >.

you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.

1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons

Even easier than navigating is shift clicking on the tools folder and opening the prompt that way.
Sent from my SAMSUNG-SGH-I897 using XDA App

masterofthebass said:
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
Click to expand...
Click to collapse
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App

rkorzuch said:
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Click to expand...
Click to collapse
You're my hero. Thank you.

djgleebs said:
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)

Please next time when you have questions, post in the general. Unless you are helping with development, post it in the general with all your questions. Please also learn how to read and learn how to use the search button.
Sent from my GT-I9000 using XDA App

Why doesnt anyone read the stickies anymore??

I think the easiest way is (from rooted phone):
Open Terminal Emulator
>su <ENTER>
>reboot download <ENTER>

Easiset way is to google Android SDK. Open the folder, then open the tools folder. In there you will see adb. Drag adb onto your command window that you've opened to run commnads and then type in what you want it to do, ie: reboot recovery, reboot download then hit enter.

masterofthebass said:
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Click to expand...
Click to collapse
Step 3 is not necessary unless you are using adb push or adb pull.
Open command prompt, type command. Using ADB is not a skill. There are a whole 5 commands. adb shell, adb pull, adb push, adb reboot, and adb remount.

Trying to sideload, error message. Help!

Says my phone is connected fine and everything, but when I click on install (android central sideloader app) I get this:
adb is not recognized as an internal or external command, operable program or batch file.
How do I fix this?

download sdk from google place the apk in the tools folder shift+right click on tools open command prompt.
adb devices (make sure your phone is connected with charge only and debugging on)
adb remount
adb push ./(apk name) (space)/system/app

mudknot2005 said:
download sdk from google place the apk in the tools folder shift+right click on tools open command prompt.
adb devices (make sure your phone is connected with charge only and debugging on)
adb remount
adb push ./(apk name) (space)/system/app
Click to expand...
Click to collapse
Can you put that in noob wording? lol

brian85 said:
Can you put that in noob wording? lol
Click to expand...
Click to collapse
Download Android SDK from here: http://developer.android.com/sdk/index.html
Extract it
Find Tools Folder in SDK Directory - copy/paste apk file in this folder.
click tools folder - press shift + Right to open command prompt
in command prompt type: adb devices then enter (this will make sure your phone is recognized and in the right state so you can continue)
in command prompt type: adb remount then enter (for lack of better terms...this prepares your phone)
in command prompt type: adb push ./(apk name) (space)/system/app then enter (this will transfer the apk to your phone.)
Ok I think that's right...I'm still learning adb and all involved. If I'm wrong, one of you more experienced guys correct me.

the phone also needs to be in charge only and go to settings>applications>debugging, debugging will have to be on.

mudknot2005 said:
the phone also needs to be in charge only and go to settings>applications>debugging, debugging will have to be on.
Click to expand...
Click to collapse
Already did that.

brian85 said:
Says my phone is connected fine and everything, but when I click on install (android central sideloader app) I get this:
adb is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
let me guess: Is the Ac_SWM folder on your desktop?
It needs to be in the root directory of your C: drive since the batch files are looking there.
In other words, it needs to be c:\AC_SWM, not "c:\documents and settings\<yourname>\desktop\ac_swm"

Cannot find run command line in ADB.

Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App

RPK925 said:
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.

kam333 said:
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
Click to expand...
Click to collapse
Then you have to go to folder where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)

I
pigeonaras said:
Then you have to where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App

pigeonaras said:
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
Have you done this .....??????

RPK925 said:
I
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before you can use adb command, you have to direct the terminal to the location of the folder where adb is located.
If the location of the file adb is at C:\\windows\androidsdktools\tools\adb
In your terminal type
cd \
Press enter, then type,
cd windows\androidsdktools\tools
Now the terminal should be in the folder where adb is located.
adb devices

A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
"On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path."
Click to expand...
Click to collapse

tmspyder said:
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
Click to expand...
Click to collapse
This Works!

install adb driver first£¬turn your phone in ¡°charge only mode¡±£¬then find the adb floder£¬hold ¡°shift¡±and right click the floder.choose ¡°run in cmd line mode¡±£¬yeah£¬you done it

How to fix a soft bricked device from a flash that failed due to missing files

This guide is meant to less techie people, and written in detail. Please don't mind me if I overexplain. If you have any questions, feel free to comment them.
Also, I am not responsible for anything you do to your phone; you assume your responsibility for anything you do because of this guide.
Scenario:
So, lets say that you tried to flash an zip file on your android using sideload, but the zip required another file to be in the same directory as it, in order to work.
After flashing the zip and getting an error, your phone may not get pass the logo of the brand and be soft bricked.
Also, you formatted your external sd as internal, and cant access your usual location with files in the recovery.
In this case, don't worry, as I'm here to help you unbrick your phone without reinstalling the rom.
Things you will need:
your phone
a computer connected to your phone with an usb cable
the proper drivers for your phone
a custom recovery like cwm or twrp installed on your phone
probably root, although I'm not sure
and finally the adb (android development bridge) utility
Where to get a custom recovery?
- https://www.xda-developers.com/how-to-install-clockworkmod/
or search on xda under at your device's forum
Where to download adb from?
- https://forum.xda-developers.com/showthread.php?t=2588979 (this one comes with the drivers)
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip (just the adb files)
So lets get started:
First, get your phone into Recovery mode (on samsung hold power button volume up and home button), and connect it to your pc with a usb cable.
Open ADB by shift + right clicking the folder platform-tools in witch it is located. Click on "Open Command Prompt window here" or "Open Powershell window here" (depends on your windows settings).
You need to find a location on your phone that is accessible through the flash zip menu from your recovery. (from sdcard / from sdcard1 or whatever your external sd is called)
In my case, i could get to see folder 0 and obb from "flash zip from sdcard".
To find a suitable folder:
In the window, type
Code:
adb.exe shell
if you opened cmd, or
Code:
./adb.exe shell
if you opened powershell.
This will open a terminal that will run commands on your phone.
(Now you can type commands in the cmd window that will be run on your phone.)
Type in
Code:
cd /sdcard/0
to go to the main sd card location that is accessible in recovery when you go to flash a zip from there. (if you can get to another folder where you could a flash a zip from, change the location to that place)
You can use here the command
Code:
ls
to view objects in the folder you are in.
After you are done, type
Code:
exit
to exit.
To solve the soft-brick, you need to reflash the zip, but with the files it needed in the same directory.
Type in the ADB window
Code:
./adb.exe push "location of the file you are sending" "location of the folder you are sending to (eg. /sdcard/0)"
if you are in powershell, or without the ./ if you are in cmd.
Use this until you have sent all the files needed for a successful flash.
Then just use the "flash zip" utility from your recovery with the location you have sent the files to, on your phone, to complete the flash, and solve the half-brick.
Restart your phone and you should be good to go.
Thanks to the following threads, that helped me put this together, and solve this problem on my phone:
https://forum.xda-developers.com/showthread.php?t=1927198
https://forum.xda-developers.com/showthread.php?t=2588979​