Database Info

[Q] ADB error device not found OSX

Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.

Forgive me for asking the obvious, but do you have USB Debugging enabled?

distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.

Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?

distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try

Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.

distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac

kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).

Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.

distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.

Fastboot devices gave me this output:
serial# fastboot

kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.

distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.

kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.

distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe

kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).

Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck

[Q] please help using heimdall

hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob

saketh91 said:
hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob
Click to expand...
Click to collapse
How exactly did you try to flash it with Heimdall? In his [KERNEL][UVKJ6][BETA3.1] Subtly Modified Stock with CWM5 + Voodoo Lagfix [1/14/2012] thread he has instructions on how to flash the kernel via Heimdall & the command prompt. I have not tried it with this kernel yet, so I'm not 100% that's what you're looking for.

thanks for the kind concern and sorry for the late reply.my problem is that i installed the drivers in heimdall as given in post and then i put my phone my phone to download mode and then when connected to pc heimdall says no device compatible download mode detected i tried reinstalling the drivers,installing kies,restarting laptop and nothing worked for me please help

I just tried this and it works fine. Win7 64bit
I'll post my steps in a minute.
======================================
Install Heimdall - C:\Test\heimdall-suite-1.3.1-win32
Unzip “kernel-sms-kj6-v0.2.0-bml”
Copy "zImage" from \kernel-sms-kj6-v0.2.0-bml\kernel_flasher to C:\Test\heimdall-suite-1.3.1-win32
Put phone in download mode
Install driver “zadig” at “C:\Test\heimdall-suite-1.3.1-win32\Drivers”
Option list all devices – select Samsung and install driver
Open Command prompt “Run as administrator”
cd C:\Test\heimdall-suite-1.3.1-win32
heimdall flash --kernel zImage --recovery zImage
Phone boots with new kernel

so you say you have to copy the zimage file in heimdall suite folder itself?
when i load the file into heimdall firmware package or pit file i get either "tar header contained invalid file size" or "invalid pit file" error message
and also i am sure i installed drivers for my phone in heimdall as stated in the post
but still heimdall is not detecting my phone it says "failed to detect compatible download mode device"
please help me if you know anything abt this
thanks for the reply

Attached are two jpgs, first is device with Hiemdall driver (libusb) and the second is with Samsung driver in device manager screen. To change driver just un-install the device in device manager and then let computer scan for hardware changes, this will get you back to Samsung driver. You must use Heimdall to install driver for libusb. Hope this helps... Are you trying to use the Heimdall frontend? I'm not using frontend just command mode, try it...

actually i used frontend first i found it not detecting my phone and so i used heimdall cmd no luck there too
i tried uninstalling samsung usb drivers from the system and installed it again
today morning i found a samsung composite usb device option list(which i was not getting it before)
so the changes i made is changed the compatibility to windows xp and tried it worked fine but still its not detecting help me please please

this is what it looks like after i install heimdall driver
when i go to cmd go to heimdall and flash kernel image it says device not detected

From off
I press both up volume and down volume together
then connect the usb cable to my phone ("Warning!!" screen displayed)
then press the up volume to get download mode ("Downloading" screen displayed)
I enter at the command prompt: heimdall detect
the system returns: device detected

If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.

Racing19969 said:
If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.
Click to expand...
Click to collapse
Stop racing and smell the roses. The OP has a problem where heimdall does not see his device. Have you seen this type of error? Read the entire thread, maybe. Thanks for the help and look out for that tree!

i hope changing the os to windows xp will help i installed drivers for heimdall as instructed in the forum i followed every step suggested by some other devs but still no luck i dont know wt to do now

You can wait for them to finish CM7. You can make sure you are using the correct Heimdall Suite for your computer. You can look at Juls guide in the general section for additional help with Heimdall.

i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly

saketh91 said:
i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly
Click to expand...
Click to collapse
If you still have the Samsung USB drivers installed, then I suggest uninstalling them. They don't seem to get along with the Heimdall drivers.
Next, put your phone in download mode & plug it into a USB port on the computer.
Run Zadig again. Try to reinstall the drivers from there if you can.
Run the Heimdall front end. See if it recognizes your phone now. If so, you should be able to open a command prompt and run the command:
Code:
heimdall flash --kernel zImage --recovery zImage
Let us know if it works.

as i stated earlier that i am gonna use windows xp for doing this i shifted to my pc which has windows xp in it.i followed all the instructions and it worked pretty fine in that now i am able to install cm7 but i dont know wt has happened to windows 7 as it dint allow me to properly work with it
anyways thanks to all of you guys for supporting me and for spending your time for me
i defenitely owe you guys thanks a lot

nothing works
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw

undetectedcriminal said:
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw
Click to expand...
Click to collapse
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.

bhundven said:
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.
Click to expand...
Click to collapse
Better yet go see a counselor. Will someone report this I'm mobile. Thanks

[Q] root gt-p3110 Heimdall method

Hello,
I have a Samsung Galaxy Tab 2 7.0 GT-P3110 and I tried to root the Android via the Heimdall method. I followed all the steps.
Once everything was set, I pressed the Start button to begin the Heimdall to root and my tablet was automatically reboot successfully.
After the tablet reboots, I opened the command prompt from Windows XP and I tried to type the commands to detect the tablet (Android SDK and samsung kies are installed).
I noticed that my PC can not detect my tablet (I think I have not the driver and can not install it).
What can I do? Please help me…
Thanks

nobody can help me?
edy2005 said:
Hello,
I have a Samsung Galaxy Tab 2 7.0 GT-P3110 and I tried to root the Android via the Heimdall method. I followed all the steps.
Once everything was set, I pressed the Start button to begin the Heimdall to root and my tablet was automatically reboot successfully.
After the tablet reboots, I opened the command prompt from Windows XP and I tried to type the commands to detect the tablet (Android SDK and samsung kies are installed).
I noticed that my PC can not detect my tablet (I think I have not the driver and can not install it).
What can I do? Please help me…
Thanks
Click to expand...
Click to collapse
nobody can help me?

What guide did you use? The one on the CM wiki?
Posted from my Galaxy Tab with CM10
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
A few more questions:
Do you have Kies installed?
Does the tablet boot up or is it softbricked?
What happens if you reboot into recovery?
Posted from my Galaxy Tab with CM10

Heimdall Method
MultipleMonomials said:
What guide did you use? The one on the CM wiki?
Posted from my Galaxy Tab with CM10
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
A few more questions:
Do you have Kies installed?
Does the tablet boot up or is it softbricked?
What happens if you reboot into recovery?
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
What guide did you use? The one on the CM wiki?
I used the following guide (from www . androidauthority . com )
Heimdall Method
1. Download and install Heimdall Frontend to your computer for Windows users, + Microsof Visual C++.
2. Download gt-p3110.pit
o NOTE: If you have downloaded gt-p3110.pit.txt, rename the file into gt-p3110.pit.
3. Download boot-bjr.img
4. Switch off your tablet.
5. Reboot your Samsung Galaxy Tab 2 7.0 GT-P3110 into Download Mode. You can do that by pressing and holding the Volume Up key (right key on the Volume rocker) and Power button. When a warning message appears, press the Volume Down key (left key on the Volume rocker) to continue.
o NOTE: To avoid confusion, the Left Volume key is the button nearest to the Power button. On the other hand, the Right Volume key is the button farthest from the Power button.
6. Open Heimdall Frontend on your computer.
7. Connect your tablet to the computer via USB cable.
8. To check if your tablet has successfully connected to the computer, go to the Utilities tab in Heimdall. Click the Detect button and the message “Device detected” will appear in the message box at the bottom.
9. Go to the Flash tab.
10. Under Options, go to “PIT” and attach the gt-p3110.pit file.
11. Under Partitions (Files), click the Add button.
12. Under Partition Details, select Kernel as “Partition Name” and attach boot-bjr.img.
13. Once everything is set, click the Start in Heimdall to begin. Your tablet will automatically reboot.
14. After the tablet reboots, open a command prompt or terminal and type the following commands:
adb shell
./su
./gtab2-root.sh
Do you have Kies installed?
Does the tablet boot up or is it softbricked?
What happens if you reboot into recovery?
Yes, I have Kies installed, I connected the tab to PC via usb, I have installed the drive with ZADIG
At this moment when pressing and holding the Volume Up key and Power button, the display shows just logo: Samsung Galaxy Tab 2.7.
I can not get into download mode
I followed all the steps described above and I stopped at paragraph 14.
I opened the command prompt and you type “adb devices” and my PC does not detect the tablet.
Thanks

One thing I would mention, as it was something I learned in my SGP 4.0 days, the USB port you install the heimdall drivers on with zadig will OVERWRITE the samsung drivers (that you need for adb) on the USB ports in that "stack", basically on a laptop use USB's on one side for heimdall and the other side for odin/adb/kies.
Also, is Kies really necessary? can't you just install the samsung drivers from here http://forum.xda-developers.com/showthread.php?t=961956 it works for my SGP 4.0?

If you're using a PC, there's no reason not to use ODIN simply because it's what at least 80% of people use and you'll get better support.
Posted from my Fascinate using XDA Premium

[Tutorial] Use ADB (very basic, for Windows PC)

A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.

I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.

Well ok then..
I finally tried a different version of adb.exe than the one I originally used (was about 400kb), and now it's all working as expected..Yay
Maybe the version I tried was a bit dated ? not even sure where that is now, lol
done too much since, being a new pad owner and all.
Now I am able to make use of "Right Click APK" >> install via Wireless Connection.
No wires, no prompts.
Just wanted to post a follow up in case anyone thought I inferred 'rooting' somehow cost me ADB functionality
Very happy
:good:
(OP get's a +one for making me revisit the issue)

The best and most simple guide
it`s just what you need

Oxyandy said:
I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.
Click to expand...
Click to collapse
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.

calden74 said:
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.
Click to expand...
Click to collapse
I guess you missed Post #3 just after that one, I have it working no problem, I had to use a different version of ADB.EXE
Cheers and thanks for the kind offer of help
Oxyandy

cant get into recovery
gr8nole said:
A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
Click to expand...
Click to collapse
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom

misterwright said:
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom
Click to expand...
Click to collapse
Flash the recovery all over again
Brought to you by SM-T210R

Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom

misterwright said:
Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom
Click to expand...
Click to collapse
Try to reflash rom, firmware and else
Brought to you by SM-T210R

darn
Ripshock said:
Flash the recovery all over again
Brought to you by SM-T210R
Click to expand...
Click to collapse
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom

misterwright said:
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom
Click to expand...
Click to collapse
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R

Ripshock said:
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R
Click to expand...
Click to collapse
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom

misterwright said:
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom
Click to expand...
Click to collapse
Well navigate through the forum
Brought to you by SM-T210R

I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom

misterwright said:
I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom
Click to expand...
Click to collapse
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R

Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
Thanks...
If I find a md5 file that works I will post a link
Tom
this worked THANK YOU gr8nole http://forum.xda-developers.com/showthread.php?t=2433853

misterwright said:
Thanks...
If I find a md5 file that works I will post a link
Tom
Click to expand...
Click to collapse
What version of the Tab 3 do you have?
Sent from my SCH-I605

gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom

misterwright said:
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom
Click to expand...
Click to collapse
Glad it worked
Brought to you by SM-T210R

USB debugging not working properly (on Ubuntu)

Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).

Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!

Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:

I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk

drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution

spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.

microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.

My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?

spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.

File transfer and fastboot don't work on my Ubuntu either.

spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).

microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked

I have same problem with Windows 10 64Bit.

All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?

I have solved my problem. I have install Windows 10 new and now all working.

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!

I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.