Alright, Im having an issue when using adb shell. Anytime i run an adb shell whether during normal operation, recovery, or bootloader the shell only allows me to run one command then refuses anything after. Even if i just su it will not respond to any other commands. It does not disconnect me or say device not found or return any type of error, just sits there waiting. Any help would be greatly appreciated.
also just realised if i try to run an adb backup it opens up the backup screen on my device and when i click backup my data it shows it is backing up but nothing gets pushed to my computer.
So no one has any ideas?
Related
Why am I getting the following?
I'm trying to run the 32B Hero (pure black) ROM Runme.bat and it is erroring because it is seeing multiple devices?
C:\android\tools>adb devices
List of devices attached
XXXXXXXXXXX offline
XXXXXXXXXXX offline
XXXXXXXXXXX device
Click to expand...
Click to collapse
At least yours see's some devices..... Mine won't recognise anything!
Roy_Drage said:
At least yours see's some devices..... Mine won't recognise anything!
Click to expand...
Click to collapse
Be sure you have the lastest USB Driver found in SDK's folder installed..
Well if you are playing with the emulator, more devices will show up. To select a specific device you have to run it with -s SERIALNUMBER like:
Code:
adb -s 123ASDQW111 shell
dev kit USB driver is loaded.
Not aware that I am playing with the emulator? I'm not, at least I don't think I am?
easiest way to resolve this is to issue two commands in the command prompt
adb kill-server
adb devices
this should restart the adb service and only show one device, at least this worked for me when I had this problem, good luck
thanks man that helped alot!!!!!!!
I was going to reflash my rom and start all over!!!!!!
after installing rom bootloader loop
I finally was able to sideload a ROM after wipe out my OS, then installed a android revolution rom seems ok but when I restarted after showing a few seconds htc logo reboot and goes to recovery menu, what should I do? please help
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
I can't connect to ADB, at all... All i get is this message
List of devices attached
LGH918 ect. unauthorized
When i connect USB debugging, i never get the finger print prompt.... I have all the proper drivers installed, I installed ADB and Hotboot. I already cleared the contents in the .android folder.
Can someone please help. I don't know what else to do.
type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.
me2151 said:
type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.
Click to expand...
Click to collapse
Nothing unfortunately :/ the prompt never shows, no matter what i try.
Bump
Bump. Im in the same boat
Try
1) unplug v20
2) go into developer options then click Revoke USB debugging authorizations
3) plug v20 in, unlock v20 screen
4) type adb devices
5) authorize the popup you see on the phone
You should be good.
Hi guys, hope you are all okay.
I've been having some issues with using adb shell commands with Adb tools windows, for a Galaxy S8 SM-G950U (T-Mobile Variant).
Everytime I try using an ADB shell command, my phone just starts acting crazy: Making me use 2 fingers to do stuff, it gets laggier, and basically unusable. This ends up with me having to do a factory reset (it doesn't even lets me make backups) so I can recover functionality.
Has anyone experienced this before? If so, How can I solve this to use any adb command without breaking up my phone?
Thank you guys so much for taking the time to read this case.
Have a great day y'all.
Germán.