Develop Bugs

[Q] adb will not work for me...what gives???

To start off, yes I am a complete noob to this, so bear with me. I have been trying for hours to get the adb info to install on my computer so I can root with the new 2.2 method. I have Vista/32 bit and I have tried multiple ways to install, from guides here and you-tube and nothing will recognize the adb in cmd.exe. I have copied the sdk info into a tools folder like I'm supposed to, I think, and followed the instructions and all I get is that it is not recognized or not an executable file or whatever.... Can someone please offer some help here?? Thanks in advance

did you try to run abd from the /android-sdk/tools folder in the command prompt? and did you add the path to the enviroment variables?

I have tried to run it from the folder, and I thought I had it added but I'll double check...

OK, it's in the path now, but I still get a 'not recognized as an internal or external command, operable program or batch file.' I'm stuck in the mud, spinning my wheels....

I get the same thing with win7 I can get the command prompt android tools folder hit enter and it said 'not recognized as an internal or external command, operable program or batch file

Ooooh...I got it...had the cmd info in wrong folder...needed it in the same tools folder...thanks folks

Yeah, getting adb into your path is kinda hard the first few times. I add it to both of my Paths and then reboot. If you follow the documentation on the Android site, it usually works after a reboot.
To make sure its just a path issue, you go to your sdk folder and navigate to tools (in the command prompt, of course, which is done by "cd \path\to\sdk\tools\") and then typing adb. If that works, then you type adb devices and make sure your phone is found. If that works, then all you need to do is finish the path installation and reboot. That's usually how I get it. Once on your path, you can adb shell from any location on your computer, which is nice when you want to push files to your phone.

[Q] ADB help!!

So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?

HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?

DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.

Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!

OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?

mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".

ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!

steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'

DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.

steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!

Kindle Fire Brick Utility not working

So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.

What version of Windows are you using?

Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.

Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!

roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?

When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.

roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?

nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....

Any other suggestions or help?

roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.

I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.

kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?

roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns

When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple

roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.

It works, I got to mount the SD card and everything. Thank You everyone for all of your help!

[Q] KFU noob searched and nothing is working.

So i installed the drivers and everything went fine with that. Now im stuck with the "'findstr' is not recognized as an internal or external command, operable program or batch file". So this is whats wrong every answer i find for it is about adding the system32 folder as a path in environment variables and i also tried adding it in cmd and i still get the same thing is there something else im missing?

For your findstr error, check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32
Try This. Worked for me
Sent from my SAMSUNG-SGH-I747 using xda premium

adb reboot bootloader (Unlocking the Bootloader)

on the box my hpone came it it says H815, Made In Korea, I talked to LG they say it's registered in Hong Kong but it shows it's a LG-H815, No T or anything after the 8. So I have a H815. Not sure what the Hong Kong thing means...but I need to unlock the boot loader.
Following this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
On the 'adb reboot bootloader' command it says in CMD, 'error: device 'null' not found'.
I've tried it many times. I can clearly see it as G4 in My Computer, I can go into it and see the folders on the internal memory.
http://i.imgur.com/fZ4t6Rj.png
http://imgur.com/5UBg6dB
I downloaded installer_r24.3.4-windows.exe from here: http://developer.android.com/sdk/index.html#Other
I installed the SDK Manger and installed the Google USB Drive and the Platform Tools, got the 3 files, did the cmd as you see in my image...
I never had to installed the G4 drivers or anything, it just installed it when I plugged it in and always worked.
So...?
Wish someone could help via Team Viewer..

Sounds like you need to install the drivers.... it is not so it just works for you to see the files... it is so that the computer will see the phone as an ADB and fastboot device
Install the drivers like it says to do, and test it by hooking the phone up to the computer and in a DOS box type "adb devices" without quotes, it should give you a device id.

Milimbar said:
Sounds like you need to install the drivers.... it is not so it just works for you to see the files... it is so that the computer will see the phone as an ADB and fastboot device
Install the drivers like it says to do, and test it by hooking the phone up to the computer and in a DOS box type "adb devices" without quotes, it should give you a device id.
Click to expand...
Click to collapse
tried that, got this:
C:\>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
So tried the other thing (adb reboot bootloader):
C:\Users\Owner\Desktop\tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
Just to make sure I got the right drivers, can you link me to the latest drivers for the H815?
I tried: http://www.lg.com/uk/support-mobile/lg-H815 - makes me install that support program first, but once it starts up it tells me to select my carrier, which mine isn't there and lists models, which mine isn't there.. So that didn't help. The daemon thing is new though...
EDIT: It works now and I get this... doesn't list it... someone link me good drivers or?
C:\Users\Owner\Desktop\tools>adb devices
List of devices attached
Click to expand...
Click to collapse
EDIT 2: Now it's back to the original null message only. I need some good drivers...

Broth3rz said:
C:\>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Start your DOS box from the directory you installed ADB to. If you do not know where that is, just search for adb.exe on your computer.
When you find where it is installed, just go to that folder and shift+right click and select "open command window here"
Run your commands there and it should work.

Milimbar said:
Start your DOS box from the directory you installed ADB to. If you do not know where that is, just search for adb.exe on your computer.
When you find where it is installed, just go to that folder and shift+right click and select "open command window here"
Run your commands there and it should work.
Click to expand...
Click to collapse
Just shows 2 empty lines, I need some real drivers or something. I don't know where to get them.

Read the thread about unlocking your boot loader. Everything you have asked is in it. Your phone needs to be in the right mode, adb, fastboot, download.

Don't know what thread your talking about and I've installed the best drivers I could find. It's not seeing the phone.

I opened CMD and did"
adb kill-server
adb start-server
Plugged it in and did the adb devices and got this:
C:\Users\Owner>adb devices
List of devices attached
LGH81567593392 device
Guess I'll try the next step in unlocked when I wake up. Any reason it has all those numbers after H815?

On the 'adb reboot bootloader' command it says in CMD, 'error: device 'null' not found'.
Normally, when it says "null" not found, you haven't accepted the connection on your phone, you wont see it if the screen has blanked.
Try again and accept connection from computer on your phone.
Oh, and if you;'re having problems getting the adb.exe etc to work, try downloading minimal drivers here ( http://forum.xda-developers.com/showthread.php?t=2317790 )and install to desktop with shortcut as well. When you click the shortcut, it will create a dosbox and most commands will work from there.

Sounds like it is working. The numbers are your device id. Just proceed with your unlocking or rooting now and it should be fine.

What should be my next step in rooting after unlocked BL?
In the end I want to update my firmware and install stock Android, that is if it's just the OS, no installed apps or anything, apart form Camera, Play Store, etc.

Broth3rz said:
What should be my next step in rooting after unlocked BL?
In the end I want to update my firmware and install stock Android, that is if it's just the OS, no installed apps or anything, apart form Camera, Play Store, etc.
Click to expand...
Click to collapse
IF you have the H815 EU version, and were able to unlock the bootloader from the LG site....
http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
Finish up on that page what you have not already done......
Install TWRP (recovery) and Root.
After that, its up to you, there are a few RoMs out that are stock and or debloated, pick the one you like.
Remember to check that it is for the H815 not a carrier version.