Related
Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.
Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .
Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)
Glad I could help .
OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???
Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .
Hi.
I don't know what happened, but I cant access my phone via adb anymore. I've used adb for months with no problem so far.
The Device is shown in windows xp as "Android Composite ADB Device". I uninstalled an reinstalled the drivers. But ADB and other apps like ddms don't recognize the device anymore.
I'm not sure, but perhaps the problem exists since I installed the modem-driver to use USB-tethering.
USB-Debugging is enabled too...
Does anyone have an idea?
I'm using cyan 4.3.2.1.
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
If none of that works, try to re-root using this;
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Make sure to backup and stuff, etc. etc.
Hope I helped!
Exodeity said:
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
Click to expand...
Click to collapse
thx a lot for the quick answer, but I tried all of this. In the Recovery (Amon Ras' I recognized the first time, that adb doesn't work)
I can't believe, that I have to re-root... Recovery and SU are still working.
Any other experience with the problem?
p.s.: I unchecked the USB-Tethering and already uninstalled the modem-driver without success...
That's weird, you sure your in the right area on your cmd prompt?
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Exodeity said:
That's weird, you sure your in the right area on your cmd prompt? ( Assuming your on windows, the Terminal in linux, I'm sure you know xP )
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Click to expand...
Click to collapse
you gave the right advice...
it's weird. I set adb as variable in windows environment and it worked till today.
Now I started a command prompt in another folder with adb in it and started adb... and it works. weird. I already uninstalled the drivers with usbdeview, restarted etc. a several times and it didn't work. Just use another adb-command finally worked...
thx
Code:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT852KV04159 device
Yeah, that happens to me sometimes, where it says the device didn't ACK, or something, but I just unplug it, plug it back it in, and wait a good minute it works flawlessly.
I guess our G1's just get moody sometimes, I know I would if someone changed my innerds and outterds on a regular basis xD
Hey guys,
I'm just trying to port a Rom...
I changed some settings and it installs clearly now, but it has a bootloop...
I'm trying to port the paranoid android rom from HTC One X, I think it's V3.10...
I just googled and searched around and I know that I should get a log via ADB...
The PC finds my device, in device manager it is in "portable devices" as "P880", but doesn't show it in "Computer"... There is just my HDD and my cd burner shown...
I start CMD before debugging phone on PC and type "adb logcat", ADB starts and the message "Waiting for device" appears...
I plug the phone in, boot it and the computer finds the device in device manager... But ADB still "waits for device"... When I open another CMD Window and type "adb devices" it shows a device which is "offline"...
I have installed the latest ADB drivers (needed them for unlocking BL) and LG Software drivers...
Is there any other way to show a log while booting or at least turn the device to "online"?
Thanks in advance!
The phone should be detected as adb device in device manager do you see any driver contains adb in it - you can try droid explorer for log cat but I think it depends on working adb too
Thanks, I will try it later!
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
Thanks for your reply, I have the newest SDK so I think newest ADB, too, so that's not the problem...
thank you for this hint, I will look into it and will search that string....
I'll report when I find it
Since you have SDK, use ddms.
Tested and.... Nothing -.-
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
Paulo87 said:
Since you have SDK, use ddms.
Click to expand...
Click to collapse
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
BlackDuty said:
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
Click to expand...
Click to collapse
you can stay with ddms, it's better IMO
now you can try to change "ro.secure=1" to "ro.secure=0", compile and try again now adb should start as soon as possible, even on kernel level
Argghhh
Why didn't you tell it earlier?
Just joking, thank you!
Will try and report...
Another try went wrong...
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
BlackDuty said:
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
Click to expand...
Click to collapse
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
laufersteppenwolf said:
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
Click to expand...
Click to collapse
Unfortunatly I can't use linux, just with a terminal over cygwin :|
I will try that method tomorrow, now I have to sleep
Thank you again, you make me feel a little bit smarter then I am atm
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Paulo87 said:
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Click to expand...
Click to collapse
As you can see in the attached picture in my previous posts, there is already the "ADB Interface" on device manager, or is there any difference between "Android ADB Interface" and "ADB Interface"?
I will try to reinstall it and look into the link to install USB-Drivers you wrote here, later!
Thank you for that many tries to help me! I hope we will find the right way...
Hey, some news:
@Paulo87 : I tried to reinstall the google drivers and use the device as Android ADB Interface and it worked when I am in recovery...
Looked at monitor and ddms, they found a device but there was no "online" or "offline", but a "??"
I flashed the files and rebooted, plugged data cable in and... There is still this MTP-Device shown, no Android ADB Interface...
Tried the same steps there but it told me that in the folder google drivers are no drivers for this MTP device...
I think I will kill me in the next hours
Nah, just joking, but this is really annoying...
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Paulo87 said:
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Click to expand...
Click to collapse
I already tried, but it hangs on the last step, it says that "last_kmsg" wasn't find... So if it doesn't exist , it's logical that you can't move it... Something like this
And you really don't want to know how near I am to do that thing what the guy in your picture did... :silly:
Any other suggestions?
BlackDuty said:
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Click to expand...
Click to collapse
this seems like the rom wasn't flashed?! or the rom has no su binary included...
and when it says, that last_kmsg wouldn't be found, it's most likely that you've got a serious problem with your kernel...
what kernel source are you using?
Honestly, i have no more ideas mate...
Good luck.
Glück
I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
lurenja said:
I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
Click to expand...
Click to collapse
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
samwathegreat said:
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
Click to expand...
Click to collapse
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
lurenja said:
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
Click to expand...
Click to collapse
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
6719
samwathegreat said:
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
Click to expand...
Click to collapse
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
lurenja said:
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
Click to expand...
Click to collapse
I suggest asking the person who wrote the guide that you quoted. Good Luck!
Remember to always hit the thanks button under any post where someone helped you, or that provided useful information. :good:
i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.
You have turned adb on on the Fire?
Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.
ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse
ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse
for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again
ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".
I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk
I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be