Database Develop

[Solved] ADB isn't connecting

Hmmph. Basically, I'm running Windows 7. ADB has worked fine for me for months now, except for tonight. Tonight, I can't connect to my phone VIA ADB. Everything is set up right; not like anything has changed.
Typing "adb shell" returns "error: device not found." Logcat shows waiting for device.
I haven't changed anything on the phone either. Is there a way to "reset" ADB?

open up your task manager, go to processes then select adb.exe and end it. maybe that will help. i had a problem once where it identified my phone twice and i could not use adb and reset it that way

david1171 said:
open up your task manager, go to processes then select adb.exe and end it. maybe that will help. i had a problem once where it identified my phone twice and i could not use adb and reset it that way
Click to expand...
Click to collapse
Worked like a charm, thanks dude

lukekirstein said:
Worked like a charm, thanks dude
Click to expand...
Click to collapse
your welcome. glad it was something that easy to fix

Woops. Delete.

Bootlog with ADB?

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

[Q] ADB device unauthorized, no root, can't figure it out?

Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all

Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.

dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:

Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man

dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:

No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app

dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C

well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.

dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?

Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure

26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?

Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct

dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"

Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X

dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)

Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.

dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:

dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!

I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app

i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?

Trying to do a backup but adb pull isn't working

Hi all
So I'm doing step 1 of this guide but I seem to be having problems..
I did install the ADB drivers on my comp, installed SDK, and set the directories in PATH. ADB is turned on in the Kindle. But when I try to do the backup commands, I get a "remote object xxxxxxxxxxx does not exist"
Anyone have any idea what's going on here? I appreciate your help!

Any ideas?

I think you're on the wrong partition...

Rushead said:
I think you're on the wrong partition...
Click to expand...
Click to collapse
What do you mean? Sorry, I'm total noob with adb in general (and I just got the Kindle like a couple weeks ago )
I should add that when I do the first command the Kindle responds to it (as in the screen turns on when I send the command). Don't know if that helps you.

You need to pull from the correct directory. I think that's your only problem.

Thanks for your response.
How do I pull from the right directory? I'm using the code from the thread that's apparently supposed to work for everyone, don't know what's going wrong on my end :s

Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?

Rushead said:
Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?
Click to expand...
Click to collapse
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s

Hovo said:
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s
Click to expand...
Click to collapse
You can't run cmd as an Admin. You have to actually be using the Admin profile on your PC.

I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.

Hovo said:
I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.
Click to expand...
Click to collapse
The code works. It's just not finding your boot img.
Does your kindle boot normally?

Yep, I haven't installed the second bootloader yet because I wanted to backup the device first.
BTW, for what it's worth, the error happens with all 4 items the code is meant to backup; the system, recovery, bootloader and bootblock.

It sounds like adb is not enabled, though you said it is. Have you tried a factory reset?

Decided to give it another go this morning, and I feel so silly...
The adb shell was asking for root access this entire time, I never saw it until now though...
Thanks for all your help and sorry for makin you run around in circles. :s

ADB commands not working

Has anyone gotten the ADB commands to work? I'm trying to see if I can get by without root, so I want to enable the enhanced battery stats in GSam battery. It doesn't work for me. I'm using the latest platform tools, and I have the USB file transfer checked.
Does anyone have any suggestions that I can try?
Thanks.

Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.

InfX said:
Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.
Click to expand...
Click to collapse
Thanks!
I had already done everything you suggested, but can't get the battery stats to work. I even tried it using wireless ADB, but had the same results. I get no indication that my command was accepted . I've never enabled permissions like this before, just used root, so I don't know if anything is even supposed to come up.

What command are you trying to use exactly?

InfX said:
What command are you trying to use exactly?
Click to expand...
Click to collapse
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
These work for me.
Sent from my Pixel 5 using XDA Labs

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
ridobe said:
These work for me.
Click to expand...
Click to collapse
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed

ridobe said:
These work for me.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Did you get any text after you entered the commands that indicated you were successful? I've tried it multiple times without success. I may try to clear the data on the app and try again.

InfX said:
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed
Click to expand...
Click to collapse
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.

EMcTx said:
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.
Click to expand...
Click to collapse
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?

Tel864 said:
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?
Click to expand...
Click to collapse
Yes, I do see my device, and I got a prompt on my phone the first time I connected.
I have managed to adjust my AOD brightness with ADB, so it must be something I'm doing wrong with the battery stats. I'm still waiting to see if the developer can give me any pointers. If I can't figure it out, I'll find another battery app.

I finally got it to work. The developer emailed me and told me that since I had the pro version, I needed to add pro after bbm.
Thanks for all the input!

I clearly remember you mentioning getting the package name wrong... the forum migration didn't exactly go smooth for xda, i guess :-/
Edit: WTF, now i see that last post, AFTER posting this one.

I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.

AussieNordo said:
I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.
Click to expand...
Click to collapse
fastboot flash boot twrp.img to install twrp, fastboot boot twrp.img to boot twrp

Got it eventually.