[Q] Where is the adb whitelist? - Nexus 7 Q&A, Help & Troubleshooting

After upgrading to Android 4.2.2, a new secure feature is introduced to adb. The first time a computer wants to connect to an Android device, a popup window will appear on the screen of the Android device.
I've already upgraded my /opt/android-sdk/platform-tools/adb and I mis-pressed the "No" button on the screen when the popup shows to let me confirm the RSA key! Now there are no more popup windows! No matter how I adb kill-server or even restart my computer and Nexus 7, the popup will not show for the second time, not giving me a second chance to confirm the RSA key...
I tried another Linux computer and the popup window shows correctly. How can I somhow edit the whitelist/blacklist file in Android and let the popup windows show for the second time for my computer? Where is the adb whitelist/blacklist file in Android?

If I recall correctly it doesn't have remember autolocked so it should show up again.
Maybe restart the machine itself or the device.
And this goes without saying but make sure USB debugging is on

There is a "remember" setting when choosing. I know a factory reset will fix it or flashing a new rom if rooted, but that might be a little extreme. But I cannot figure out what app would hold that data, so that might be your only choice if you need adb.

Related

Can't get windows to recognise my DHD...

Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
wakers said:
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
Click to expand...
Click to collapse
Have you got Android SDK installed on your PC, Im sure the driver is in there...android .1.0 driver I think..
Without Android SDK you cant use fastboot flash for clockwork image..
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Did you install and launched HTC sync? It should install all the necessary drivers.
f.
Sent from The Galactic Empire using the Dark Side of The Force
wakers said:
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Click to expand...
Click to collapse
Ok try this.... shut phone down, boot (volume down and power button) selected fastboot so it turns red, put the files into android-sdk-windows\tools. i-e the clockwork image and fastboot files
Plug usb cable in.
In "windows search program files" type cmd
now type cd c:\android-sdk-windows (unless you placed the android sdk somewhere else!!)
type cd tools
Type fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img
When done type fastboot-windows reboot
You should now have CWM.
Now I know you may have tried this but It would help to find out what happens if you haven't already do so.
EDIT ...I also ask this because my laptop doesn't do anything either when I plug in usb cable in fastboot mode..im on windows 7....
Just trying to help...
Really appreciate the reply.
I got a "cannot load" Error.
I think its down to a driver for my phone when in the fastboot mode.
Whats might shed some light on something for someone with a bit more windows/android knowledge than myself is
When the phone is in Fastboot USB mode in Device manager the phone is listed as Android Bootloader interface but when i type into cmd "adb devices" nothing is listed.
When the phone is switched on normally and syncing with HTC sync in device manager the phone is listed as "my htc" and when i type adb devices in cmd, the message adb server is out of date killing...
then daemon is started and the device shows in my list ?
But HTC sync stops working ?
And the internet on my laptop stops working bizarrly.
I'm really scratching my head now lol
I'm thinking it must be something to do with not having the correct driver for Fastboot USB mode ?
Finally sorted it, had to remove the phone from device manager and delete the driver.
Then went into programs and features and removed everything to do with HTC.
Re-Installed HTC Sync
which also reinstalled HTC drivers
Plugged the phone in let windows select the driver and instead of showing in device manager as Android Bootloader Interface it showed as My HTC Sync and worked first time, not sure what happened but sure glad thats finally sorted..
Rixsta really appreciate the advice...
Cheers

[Q] Controlling Nexus 4 on the PC after breaking screen, possible?

Hey guys,
Haven't been here for a while. Okay, so I have a bit of a dilemma and every solution I've found requires something I just can't do. Here's the situation: my screen is broken, it has a lock screen, not in developer's mode, not unlocked.
This means:
I won't be able to transfer my files over, as I have to get past the lock screen
I can only install applications from Play store on my computer, but can't launch them
No use for any method that requires phone to be rooted
Can't even activate any USB options to transfer files some other way
Still need to be able to control it to create backups and such of important SMS messages, get files off
Does anyone have any suggestions at all? I don't want to have to resort to replacing the screen, as that'll end up costing me enough time and money where it's more cost-effective to purchase a new phone; however, I really need what's on my phone as soon as possible. Thanks in advance.
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key​11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
machoman1337 said:
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
Click to expand...
Click to collapse
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
ikarma said:
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
Click to expand...
Click to collapse
where did you get the screen for $79???
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
michaeliang said:
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
Click to expand...
Click to collapse
1. It means that if you have the SDK Manager installed on your computer, somewhere between the last packages at the bottom of the list, you'll see "android drivers" (or something similar). With those drivers, your device will show up in "Device manager"(the Windows' one) as an adb device.
2. But if you don't want to get the SDK Manager and be quicker, you can download only those drivers, directly from the "Google developers" page and install them manually by going to "Device manager", right clicking on the Nexus 4 (it will appear with a yellow triangle on it, maybe), then "Update driver", "...BROWSE computer...", then click again on "Browse", then go to where the drivers have been downloaded and select the entire folder by highlighting it and clicking ok (or something). The folder with the driver would look like this "latest_usb_driver_windows" and inside you'll see another folder called "usb_drivers". That's what you need to select and install.
So that's what you need to do to make your phone appear as an adb device in "Device manager". And, of course, adb let's you do a lot of stuff to your phone through your computer, but probably you already knew that.

[Q] ADB error: device unauthorized and device offline

I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto

OnePlus 5 fastboot won't recognize in Windows 10

Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
trulane said:
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
Click to expand...
Click to collapse
Hello, please use the drivers provided here if not tried yet https://forum.xda-developers.com/on...k-bootloader-flash-twrp-t3624877/post72748916
Thanks that's the guide I used 2 flash, n install magisk. I jus used one of the options that was listed on the computer, I was a random Google drivers. Then it lit up. Thanks 4 the guide, it was very helpful
Done

Motion Sense Radar Bypass

Hello everyone! I'm looking some advice from the wise about bypassing the region restrictions for the Soli Radar (Motion Sense) in my Pixel 4. I am pretty new at running ADB (Android Debug Bridge) from my Windows PC. That said, I'm sure I overlooked something very simple. I can't get the commands to work at all. I followed the XDA YouTube video step by step on how to install and setup the SDK Platform tools on my PC. As well as how to prepare my device to receive commands from my PC. But it fails every time. I'm pretty sure that I'm just running the ADB incorrectly, but I don't know. I have only been able to find instructions on how to install and setup the SDK package. But no clear instructions on how exactly to utilize it. Again, I've never done this before. I am running the latest version on Android 10 on my phone and my PC is running Windows 10. And before running any commands, I verified that the device is in fact attached to the PC by running "adb devices" first. I wish there was an option to attach a screenshot of failure message I'm getting. But it says:
setprop: failed to set property 'pixel.oslo.allowed_override' to 'true'
I get this same failure when I run the alternative command line as well. And I have tried both command prompt and Power Shell and receive the same failure message. Anything advice that can be shot my way would be greatly appreciated. Thanks!
First check the windows 10 device manager to confirm that your device and computer are successfully connected.
Then try to replace with a new data cable, a USB 2.0 cable may be better.
Is the phone bootloader unlocked or have you rooted it yet? Honestly I am not sure if either of those are required for the changes, but I suspect they are. If you haven't rooted the phone yet, then I bet you don't have the correct privileges to make those kind of changes to the phone.

Categories

Resources