Develop Bugs

[Q] ADB not working

Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.

Nerd019 said:
Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.
Click to expand...
Click to collapse
I'm trying to piece together information here. ADB for me is in my C:\, so when opening CMD prompt, I first type "cd/" (without quotes) then "cd AndroidSDK/tools". To get a list of ADB's commands, type "adb help". Maybe you're not using the proper syntax. I base this off the statement you made that when you type adb.exe it shows the adb commands, and command syntax usage.
Also note that changing your splash screen you must first S-OFF your phone. Here's a guide on how to do so
http://forum.xda-developers.com/showthread.php?t=798168
That's the tricky part though, easy part is flashing your custom boot image.
File you will need: View attachment Boot_images.zip
Once you have the 320x480 boot image you want, open "CreateG1Splash", select your boot image, and convert it with this program. Once converted the new file will show in the same folder as CreateG1Splash, named mysplash.rgb565. Move this file to your ADB tools folder. Open CMD prompt and point CMD prompt to your AndroidSDK\tools folder.
Then boot phone into bootloader, then select fastboot. Plug the phone to CPU via USB, and type, "fastboot flash splash1 mysplash.rgb565". Reboot phone to see change.
Hope this helps!

Where Can I learn ADB?

This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?

try here:
http://developer.android.com/guide/developing/tools/adb.html

To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701

Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.

Didn't see your post Mart, ill try that now.

martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.

Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.

Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/

http://wiki.cyanogenmod.com/wiki/ADB

Ohai droidstyle good to see you here
Has anyone seen John Connor?

skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!

I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo

Did you flash a new ROM?

this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM

I have CWM, but all it does bootloop and I can't get it to detect a sd card.

Unsure of where to look for CWM Touch instructions

I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app

neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.

If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.

This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.

Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app

Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.

help me here thanks guys

im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?

I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .

PhazeDelta1 said:
I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .
Click to expand...
Click to collapse
yeap i did that already i open command window and type adb reboot bootloader it gives me that msg

galaxy16 said:
im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?
Click to expand...
Click to collapse
You need to get adb working on your PC. You don't have it installed or you are using it wrong (not in the directory it is in, or it isn't set to PATH as examples).
Side note adb doesn't work in the bootloader.

use gnex toolkit in galaxy nexus android development

Open the CMD and navigate to the folder where ADB.EXE is located and like someone mentioned about adb wont work in bootloader, so instead you'll have to use "fastboot", type "fastboot /?" for help and commands.
also make sure you execute CMD as Administrator.

on the toolkit, adb file's name is different. try "adb-toolkit" instead of "adb"
so: "adb-toolkit reboot bootloader"

errror: cannot load 'recovery.img'

I am in the bootloader trying to load twrp. Typed fastboot flash recovery recovery.img
command prompt says error: cannot load 'recovery.img'

myflyman said:
I am in the bootloader trying to load twrp. Typed fastboot flash recovery recovery.img
command prompt says error: cannot load 'recovery.img'
Click to expand...
Click to collapse
It means it can't find the recovery.img on your PC.
Did you check the file extension?
Windows has ist disabled by default, so you might have renamed it to recovery.img.img

I put the file on the desktop? Why can't it find it? Frustrating

I opened properties and it does have permissions granted. Not sure why it opens with Windows explorer? Can that be right?

I'm lost. Between the proper TWRP version not available and the path not visible, just gotta be an easier softer way.

Is the name of the file you have placed on the desktop recovery.img?
The correct format would be fastboot flash recovery <name of file>.img
Rename the file to recovery (do not add any .img extension) and use the same command fastboot flash recovery recovery.img

You can also flash the recovery by typing in this command:
"fastboot flash recovery" and then drag the twrp.img into your cmd prompt.
Another way is typing the first letter of your recovery name and then hit the 'tab' key in cmd prompt, it will automatically fill out the name for you (make sure you open cmd prompt inside where the recovery img is, thus hold shift in the folder, right click and click open terminal.)
Hope this helps, goodluck.

Wow, thanks a million friend. Having the best days of my life learning and growing in tech experience. It is possible with your and others guidance. Much appreciative. I'll give er a go here shortly and keep you posted.

myflymavn said:
Wow, thanks a million friend. Having the best days of my life learning and growing in tech experience. It is possible with your and others guidance. Much appreciative. I'll give er a go here shortly and keep you posted.
Click to expand...
Click to collapse
For the command in your first post to work, two things are essential. One is naming the .IMG file correctly, as the others have pointed out. The other is to place the .IMG file in the same folder as your adb tools.
If it is in a different folder, then the exact path to the .IMG file has to be typed in the adb command or you can drag the file to the command prompt window as someone pointed out.

Shift right click in the folder where the file is and open the command prompt from there. That way you don't need to mess with the path.

You must place if your image file is recovery.img you must place "fastboot flash recovery.img.img" and done

Same problem when using Windows 10, find that open command prompt pathway to find files is not fastboot that is some other like user/ best , copy your recovery Img to that folder and you can flash now.

Frexx4 said:
You must place if your image file is recovery.img you must place "fastboot flash recovery.img.img" and done
Click to expand...
Click to collapse
Don't confuse people with recovery.img.img and missing the partition to flash.
The correct usage is "fastboot flash recovery recovery.img" if your TWRP is named recovery.img
The clarifications on the prepage are clear.