hi again. I am a mac osx user and I was trying to install androidscreencast following the steps from http://code.google.com/p/androidscreencast/ , but it doesn't worked for me. can somebody to give some more details? I got this message...
At which step did you get this message? What happens if you click on the "Details" button from your picture?
Perhaps you need Java Web Start.
this error happens to me as well, before running the screencast. You need to make sure "daemon" is running (what ever that is) by simply running an adb command, such as "adb devices"
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?
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.
Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul
zaaaki said:
Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul
Click to expand...
Click to collapse
You are using linux? If yes, try sudo.....
If not, do not restart device in fastboot and plug it in pc. Plug it when booted in system and type adb reboot bootloader. Be sure to have adb turned on in developer options.
After doing what u said; I've got:
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
I've already done kill/start multiple times. What's more, I have no RSA popup whatsoever.
Paul
zaaaki said:
After doing what u said; I've got:
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
I've already done kill/start multiple times. What's more, I have no RSA popup whatsoever.
Paul
Click to expand...
Click to collapse
Linux ???????
I am using Windows 10 x64,and I have been using it since I got P8 Lite. And I have done copule of things with my device like instaling twrp; but for some reason I cannot do that this time.
Paul
zaaaki said:
I am using Windows 10 x64,and I have been using it since I got P8 Lite. And I have done copule of things with my device like instaling twrp; but for some reason I cannot do that this time.
Paul
Click to expand...
Click to collapse
Go to developers options and click on revoke usb debugging authorizations and conform the prompt.
No reconnect the device to PC and check for RSA prompt in phone and accept it.
I haven't got revoke option, I believe it is due to custom kernel I installed, so the question is if I install custom ROM, the kernel is going to be reinstalled with ROMs one, what should I do tho?
zaaaki said:
Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul
Click to expand...
Click to collapse
This should fix it.
1. Go to the /.android folder and take copy of "adbkey.pub" file.
2. Rename copy as "adbkeys" Without any file extension.
3. Move "adbkeys" into your phone /data/misc/adb
4. Not sure if necessary but set permissions to 640 (-rw-r-----)
5. You might need to restart adb server "adb kill-server"
Now when you try it should work as expected.
It didn't work.
Reinstall phone driver. It may work
Did it and nothing.
zaaaki said:
Did it and nothing.
Click to expand...
Click to collapse
Factory reset your phone it will then prompt for RSA Key.
Did factory reset, but it didn't help, I'm on custom emui with elsa kernel.
What are you wanting to do with ADB?
What is your end goal?
Is there another way of doing it?
Another stupid question have you tried a different cable as I have had the same issue it was the cable
I want to try custom roms, and flash new TWRP, and what if I flash new rom then I'll want to go back, but can't coz I cannot connect to adb.
I was able to make it work; I restored backup.
I mean, fastboot is the one you need in order to flash twrp. Does it not recognise your phone if you plug it in while in fastboot mode?
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.