"Allow USB Debugging" to allow computer's RSA Keyprint not popping up (Windows 10)
Hey all,
I recently got a new Windows 10 laptop and tried connecting my Pixel 3 to it today. The internal storage of the phone shows up no problem when plugging in. However, I cannot get ADB to work with the laptop. I have USB Debugging selected on the phone but when my phone connects to the laptop, there isn't any popup where it says "Allow USB Debugging?" and it also says the computer's RSA Keyprint.
On my old Windows 8.1 laptop, when it connected to my phone for the first time, a popup asking for permission to "Allow USB Debugging" would popup and I would allow it and things would work. I've opened a CommandPrompt window where my SDK platform tools are to check "adb devices" and it doesn't show up. Anybody able to help?
Have you gone into developer options and turned on USB debugging manually?
I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.
Exokan said:
Have you gone into developer options and turned on USB debugging manually?
Click to expand...
Click to collapse
Yep, under developer options I have USB debugging turned on.
fury683 said:
I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.
Click to expand...
Click to collapse
I've revoked authorizations and plugged the phone into my old Windows 8.1 laptop and right away on the pixel the popup asking to authorize USB debugging popped up. I will try later with the new laptop to see if it'll start working. I downloaded the newest SDK tools yesterday via downloading Android Studio and have the latest platform tools as well during the first time I tried. Will try with a different cable and port also to see if that's the issue, same with fastboot mode.
EDIT: OK, I've tried using 2 different cables now to try and connect the phone to the laptop, one more USB-A to USB-C and a direct USB-C to USB-C connection, both sense the phone but no authorization popup to allow USB debugging on the Pixel. I've also tried to switch different USB mode on the Pixel to different options like PTP, charging only etc. but nothing. No popup.
Toronadian said:
Yep, under developer options I have USB debugging turned on.
Click to expand...
Click to collapse
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...
Exokan said:
I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
It's this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usually comes up the first time you use a given machine to connect via ADB but sometimes gets goofed and you have to remove and reauth it.
Exokan said:
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.
Toronadian said:
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.
Click to expand...
Click to collapse
Awesome! And yeah, that's tripped me up before as well!
Related
So I can't get my M8 online in order to use the firewater exploit. USB debugging is enabled, I do have temp root with WeakSauce, USB debugging is enabled, I've authorized my computer, yada, yada, yada. Every time I enter "adb devices" in the command prompt, it's recognized but shown as offline. Removed all HTC sync software and started over twice now, each time, same result.
Any suggestions?
Toggle USB debugging before you connect the device, try to check for devices and see of that works. If it does, start from the reboot command and try it again.
Sounds like you have old version of adb.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
The drivers are installed correctly?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
You have an older version of adb that won't ask for the rsa key and therefore will show offline. Google adv 1.0.31 and you should find a small package that has it.
Reboot computer and phone and try again
Sent from my HTC6525LVW using xda app-developers app
Try adb kill-server then try again.
Sent from my HTC6525LVW using Tapatalk
I thing this is an older version.
someone else had this issue, try these drivers hope your 64bit
Yeah! Was old adb and there was something weird happening with my drivers. Had to install three times. It's always the something simple! Thanks, all! Time to start tinkering...
HoboJr said:
Yeah! Was old adb and there was something weird happening with my drivers. Had to install three times. It's always the something simple! Thanks, all! Time to start tinkering...
Click to expand...
Click to collapse
I still cant get past after the script starts to s off. My device always disconnects from ADB, then i have to start over again. I can not get my device to stay connected.
On my phone USB debugging is enabled, but for some reason the phone shows up as offline unless I disable and reenable USB debugging. After that it comes up fine until the phone is removed. Is there a way to fix this?
I have tried everything that I know. My device is always offline. Ive reinstalled everything several times, restarted my phone, computer, etc. Anybody know why this is or what I can do to fix this so I can s off and root?
Have you tried putting the adb directory on the c drive that worked for me..
faded03cobra said:
I have tried everything that I know. My device is always offline. Ive reinstalled everything several times, restarted my phone, computer, etc. Anybody know why this is or what I can do to fix this so I can s off and root?
Click to expand...
Click to collapse
update your adb. Device offline means you havent accepted the authorization key on your phone and you will not see this prompt unless your adb is up to date.
adb 1.0.31
Resurrecting this thread because it helped me resolve the "device offline" issue.
I'd been using an old version of adb.
Updating to 1.0.31 gave me the authorization prompt, and the device now works as it should.
adb device offline
I had update my adb to 1.0.31, htc one m7 with debug usb enabled, but still device offline :crying:
Can anyone help me???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Having issues as well. Updated ADB to 1.0.32. Downloaded latest HTC Sync for drivers (Mac). adb devices shows:
List of devices attached
HT35ZW911892 offline
Tried disabling and re-enabling USB debugging but no luck
internetname said:
Having issues as well. Updated ADB to 1.0.32. Downloaded latest HTC Sync for drivers (Mac). adb devices shows:
List of devices attached
HT35ZW911892offline
Tried disabling and re-enabling USB debugging but no luck
Click to expand...
Click to collapse
Adb kill-server
Reboot phone
Then
adb devices
See what you have now. You may need to unplug your phone and go into dev options and revoke auths before trying again.
I'm still having issues trying to get ADB to work for me. I previously had an HTC Droid DNA which I had ADB working on this computer, so I suspect there's something lingering screwing me up. I've gone through and removed any trace I could find of HTC drivers, HTC applications, ADB, etc.
I installed the latest HTC drivers, and uninstalled the Sync Manager. I verified my ADB version is 1.0.31. I have enabled developer options and unknown sources. When I plug my phone in, it says 'USB debugging connected" but I have NEVER been able to get it to prompt me to authorize my computer or anything like that. 'adb devices' shows nothing every time. I'm still running 4.4.2 everything stock (no OTAs) and have S-OFF via Sunshine.
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone point me into the right direction?
Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?
I am using 'fastboot oem unlock' but
Erorr shows me
'fastboot (remote : unknown command)
How to solve this problem
???
Please help me
Download the latest version of fastboot & ADB.
You can see what version adb and fastboot you have installed, just open a command window and type: sudo adb --version (then hit enter) sudo fastboot --version (hit enter key) that will show your installed version of those tools. I believe right now the latest is 31.02 but I could be wrong. It is updated often and using an older release of adb and fastboot can and will cause issues..
Go here to download adb and fastboot. https://developer.android.com/studio/releases/platform-tools
Just download the android sdk for whatever OS you use on your computer, unzip...
What is the device you are trying to unlock? Have you enabled developer options on the phone and changed usb settings to file transfer instead of the default which is charging? Also have if that was done did you keep a close eye on your device because there will be a small box that pops up that must be immediately checkmarked so that your computer can communicate with your device. Have you selected "allow oem unlock"Also in the developer options? it might be good idea to set your lock screen to "none" instead of having a lock set for it. Any time anything is installed on a computer it almost always needs to be rebooted. If you have not done any of that I would suggest doing it all.
Also depending on what device you are attempting to unlock the bootloader on, the wording could be slightly different. My Pixel 4XL uses: fastboot flashing unlock , to unlock bootloader. So keep that in mind as well. If you use Windows OS on your computer some day when you have a minute check out Linux. You can make a "live USB" burn a copy of a Linux distro to a USB drive and boot from it and or install it along with your Windows OS, aka dual boot... The very first time I used Linux, it was Ubuntu and quite a few years ago and I would never return to Windows!! Can't stand it! Linux is made for doing what we do to our phones.
If you need more any help with this some other time and still cannot get it installed message me on here or should I say "start a conversation" with me here on xda. Same thing with the new layout.. My user name is the same here on XDA as it is on telegram. Feel free to shoot me a message any time. It may take a some time to respond depending on what day it is and what time and all that but I will respond.
Here is one of the best guides in my opinion on how to get and setup adb and fastboot tools on MAC, Linux and Windows OS. https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
(Edited)
flash713 said:
it is not working, same error after update.............
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MBF_9802 said:
View attachment 5323891
Click to expand...
Click to collapse
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast...
Okay idk how you installed adb & fastboot but this guide in my opinion is the best!!! https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Try using different ports, reboot your computer..
Did you already have the pop up on your device once connected to computer or no? If not your it won't work at all.
Enable developer options
USB debugging
Now plug in to a different USB port.
Now scroll down on phone to default USB configuration and change it from the default which is "charging" to "file transfer" but keep your eyes on your device screen because the pops up will only show itself for a few seconds. When it does checkmark the box. You should be good then. Windows has driver issues alot of the time!! I switched to Linux years ago and I have no driver issues. Or anything else far as that goes.
flash713 said:
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast. Brb
Click to expand...
Click to collapse
MBF_9802 said:
View attachment 5323897
Click to expand...
Click to collapse
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
All try but reason only command not found
Please help......
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
How to solve
MBF_9802 said:
Same error in updated version
How to solve
Click to expand...
Click to collapse
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
flash713 said:
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
Click to expand...
Click to collapse
yes but same problem in universal usb drivers
Hi there,
I had reboot my Redmi note 5 pro in fastboot mode, (shown in capture4 picture). Then i tried to read the fastboot devices connected to my system using the command- "fastboot devices". Then, in the devices it showed a devices but with "??????" like id. After that it got disconnected. Now when I am trying to connect my phone to the system, then "USB device not recognized" error is coming.
I tried to connect my mobile in another system, but there also same error is coming. The problem is not getting solved. I even made factory reset by going to settings, to try to make the phone read in system as earlier. But it is not getting recognized now. What should I do. Please help.. I am attaching screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Xiaomi's USB driver ( ADB & Fastboot ) suitable to your phone to PC and install it on PC, if not already yet.
Xiaomi Driver.zip - Devdrive - File Hosting For Publishers
Download file - Xiaomi Driver.zip
devdrive.cloud
jwoegerbauer said:
Download Xiaomi's USB driver ( ADB & Fastboot ) suitable to your phone to PC and install it on PC, if not already yet.
Xiaomi Driver.zip - Devdrive - File Hosting For Publishers
Download file - Xiaomi Driver.zip
devdrive.cloud
Click to expand...
Click to collapse
It's installed, it's not working. The phone is not getting read in the system altogether. the USB device is getting recognized, neither in ADB devices nor in device manager or in my computer.
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB server got started.
jwoegerbauer said:
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB got started.
Click to expand...
Click to collapse
Do you think I don't know this? I know how to view ADB devices very well. The phone is not showing anywhere. Please try to understand fully.
jwoegerbauer said:
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB server got started.
Click to expand...
Click to collapse
The phone is connected, ADB drivers and Xiaomi drivers are installed, still the phone is not showing in device manager. The phone is altogther not recoginzed by system. It's a different issue. The phone is even not shown in my computer or anywhere, just not recognized USB device.
USB debugging enabled?
xXx yYy said:
USB debugging enabled?
Click to expand...
Click to collapse
yes, it's enabled.
Brother, I am facing this problem too. Did You solve this problem ? Please tell me the solution.
@amitrajhello did you find any solution? I am facing the same issue with Poco m2 pro.
Hey I got Same Error in RN5 Pro, Any Fix???
Have you tried a different USB Cable?
amitrajhello said:
yes, it's enabled.
Click to expand...
Click to collapse
Or, https://softwarekeep.com/help-cente...uest-failed-unknown-usb-device-in-windows-10/
See if that works for you.
Creepergames360 said:
Have you tried a different USB Cable?
Or, https://softwarekeep.com/help-cente...uest-failed-unknown-usb-device-in-windows-10/
See if that works for you.
Click to expand...
Click to collapse
Hey, if you own a RN5 Pro Please drop the Hardware Id's like this (https://xiaomi.eu/community/attachments/fastboot-jpg.33150/) while phone is connected to pc in fastboot mode
because maybe by using this (https://forum.xda-developers.com/t/...r-request-failed-fastboot-windows-10.3375320/) I can Fix my Driver Issue!!
I flashed the GSI version's Havoc OS into my devices, but its adb connection always reports unauthorized. It didn't pop up any dialog to ask me confirm.
That's strange.
If there's a problem with the socket for talking to the framework you won't get a popup.
Does /dev/socket/adbd exist?
If you're rooted you can manually add your desktop's public key to /data/misc/adb/adb_keys
Edinoro said:
I flashed the GSI version's Havoc OS into my devices, but its adb connection always reports unauthorized. It didn't pop up any dialog to ask me confirm.
Click to expand...
Click to collapse
Revoke the ADB authorizations, then turn USB Debugging off and unplug it from your computer.
Next, open a command line in your ADB Platform Tools folder. Run adb --kill-server to stop the ADB daemon, then run adb --start-server to start it again.. Turn USB Debugging back on and plug your phone into the computer and see if it requests authorization.
Renate said:
That's strange.
If there's a problem with the socket for talking to the framework you won't get a popup.
Does /dev/socket/adbd exist?
If you're rooted you can manually add your desktop's public key to /data/misc/adb/adb_keys
Click to expand...
Click to collapse
I didnt root my device
V0latyle said:
Revoke the ADB authorizations, then turn USB Debugging off and unplug it from your computer.
Next, open a command line in your ADB Platform Tools folder. Run adb --kill-server to stop the ADB daemon, then run adb --start-server to start it again.. Turn USB Debugging back on and plug your phone into the computer and see if it requests authorization.
Click to expand...
Click to collapse
There is no "revoke the adb authorizations" in my device's dev options
Edinoro said:
There is no "revoke the adb authorizations" in my device's dev options
Click to expand...
Click to collapse
Right under the USB Debugging toggle, there should be "Revoke USB debugging authorizations"
Edinoro said:
There is no "revoke the adb authorizations" in my device's dev options
Click to expand...
Click to collapse
Older Androids didn't have that. Do you have it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, there is no revoke the USB debugging authorizations
When I connected my device to my computer, the notification of USB debugging said it is enabled. But my computer's adb reported the device was unauthorized
This device is running Android 10, Havoc OS 3.12
My device said USB debugging connected but my computer reported unauthorized
V0latyle said:
Right under the USB Debugging toggle, there should be "Revoke USB debugging authorizations"
Click to expand...
Click to collapse
So you flashed this custom "Havoc". Does it have a ramdisk? If so, you can just add your key to the root directory.
You could also change ro.adb.secure if it's there.
You could install Magisk temporarily, write your key to /data/misc/adb/adb_keys, then uninstall Magisk.
I'm still wondering. Did you check for /dev/socket/adbd ?
Renate said:
So you flashed this custom "Havoc". Does it have a ramdisk? If so, you can just add your key to the root directory.
You could also change ro.adb.secure if it's there.
You could install Magisk temporarily, write your key to /data/misc/adb/adb_keys, then uninstall Magisk.
I'm still wondering. Did you check for /dev/socket/adbd ?
Click to expand...
Click to collapse
Yes, I checked for /dev/socket/adbd, and it exists. I use fastboot to flash the system.img, and it doesn't have a ramdisk. And my device cannot boot into fastboot or recovery by holding post button and vol down, only by adb works.
Well, you should be able to get to fastboot with:
Code:
C:\>adb reboot bootloader
Presuming that you disabled vbmeta to flash Havoc, you can either Magisk the image or just add a ramdisk.
(What kind of custom image doesn't have root?)
Renate said:
Well, you should be able to get to fastboot with:
Code:
C:\>adb reboot bootloader
Presuming that you disabled vbmeta to flash Havoc, you can either Magisk the image or just add a ramdisk.
(What kind of custom image doesn't have root?)
Click to expand...
Click to collapse
But my adb reports my device is unauthorized...
Edinoro said:
But my adb reports my device is unauthorized...
Click to expand...
Click to collapse
Duh! I'm being stupid.
Can you load a terminal program and try that.
You should still be able to get to fastboot with buttons, your Havoc shouldn't have changed that.
Edinoro said:
But my adb reports my device is unauthorized...
Click to expand...
Click to collapse
Read here:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Hope a solution posted there works for you too.
Renate said:
Duh! I'm being stupid.
Can you load a terminal program and try that.
You should still be able to get to fastboot with buttons, your Havoc shouldn't have changed that.
Click to expand...
Click to collapse
My device manufacturer banned this way to get to fastboot
@Edinoro Thread closed as you've already created a subject matter related thread:
[MediaTek/MT8788] baseband unknown and cannot be written
I have a tablet with MT8788(or MT6771). It supports dual-SIM, and I am sure it is worked before. But after I flashed it by SP Flash Tool, it reports the baseband is unknown and IMEIs are unknown too. I tried to drop the APDB and MDDB by MTK META...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5, post only once and post in existing threads before creating new ones. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator