[Q] USB Debugging: Repeatedly being asked to trust device - Android Q&A, Help & Troubleshooting

I am using a Nexus 5 running Android 5.0.1, with adb version 1.0.32, on OS X 10.10.1.
When I reboot the device, on the initial screen I see:
USB debugging connected
Touch to disable USB debugging​
I swipe up to unlock and then see the dialog:
Allow USB debugging?
The computer's RSA key fingerprint is: <....>
[] Always allow from this computer​
I check always allow and tap OK.
If I reboot the device, I see the exact same thing again. I assume I should not be asked again and again to trust the same computer after a simple reboot.
Can anyone point me to a detailed description of how this system works so I can determine what is going wrong?
I believe the key identifying the computer is stored in the device in the data directory. I assume that a key would be stored on the computer as well. What is this location?
Is there anything else I can check?
Has anyone seen this before? If so, what was done to resolve the problem?

Related

[Q] Remove USB Mode Notification While Connected through ADB

Hello All,
This is my first post so here goes.
I simply need to get rid of the USB Mode notification when Nook Tablet is connected via USB to my Windows 7 PC so I can navigate device.
I have done a ton of research to get ADB working on the Nook and was having tons of problems with Windows XP and drivers. Moved to Windows 7 32-bit PC. Now I have Nook Tablet provisioned for USB Debugging and ADB sees the device. Now all I need to be able to do is plug the Nook Tablet into my PC via USB and not have the USB Mode notification appear. I need to be able to navigate the device while it is connected to PC via USB and recognized by ADB. Does anyone have any insight on how to remove this USB Mode notification when I plug my NT to my PC?
What I have:
NON-ROOTED Nook Tablet Software version 1.4.3
Provisioned for USB Debugging
ADB recognizes device and I can see it with no problems.
Thanks,
Maybe you can try this?
Well here goes a reply, since a lot of the questions are answered with rooted nt and that is why there is not a hole bunch of replies.
You could try sshdroid app, it said root is optional. No usb needed for this one. Hope that works for ya.:fingers-crossed:
p.s. Use terminal in winscp and type or paste your commands in the field. Make sure you exit the app corrrectly, you don't want the ssh service to be running when you are not using it.
zero2toy said:
Hello All,
This is my first post so here goes.
I simply need to get rid of the USB Mode notification when Nook Tablet is connected via USB to my Windows 7 PC so I can navigate device.
I have done a ton of research to get ADB working on the Nook and was having tons of problems with Windows XP and drivers. Moved to Windows 7 32-bit PC. Now I have Nook Tablet provisioned for USB Debugging and ADB sees the device. Now all I need to be able to do is plug the Nook Tablet into my PC via USB and not have the USB Mode notification appear. I need to be able to navigate the device while it is connected to PC via USB and recognized by ADB. Does anyone have any insight on how to remove this USB Mode notification when I plug my NT to my PC?
What I have:
NON-ROOTED Nook Tablet Software version 1.4.3
Provisioned for USB Debugging
ADB recognizes device and I can see it with no problems.
Thanks,
Click to expand...
Click to collapse
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Jedi mind reading
Something that my significant other is still trying to teach me that I haven't fully grasp yet. I'm still at if you tell me to get you a "German Poodle" then I will get you a "German Poodle"
liquidzoo said:
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Click to expand...
Click to collapse
liquidzoo said:
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Click to expand...
Click to collapse
Yes I have tried pressing the n Key, no dice. I am trying to use screencast.jnlp to project my nook onto my PC monitor. Then show people how to use the Nook on a big screen. But when I am plugged into my PC USB port, this notification prevents me from doing anything on the device until I unplug the USB cable.
So I rooted my NT with Brianf21's root process. Thank You Brianf21! I thought these rooting processes were going to get rid of the BN operating system and turn it into a standard tablet. It did not and I was able to keep the BN modified OS and have another OS that looks just like a phone.
So I Tapped the Home icon in lower left hand corner(looks like 4 houses), selected Quick Switcher, then Selected ADW Launcher. This brought up a typical Android phone type home screen. I then pressed apps, scrolled to NT Hidden Settings and tapped it. I then selected Run ADB Daemon As Root/Turn Off Auto Mount For Session. This turned on USB Debugging and allowed me to get rid of the USB Mode notification while USB is connected to PC.
Issues with displaying nook screen on PC:
Trying to display nook screen on my PC with screencast.jnlp:
I'm trying to screen cast the nook's display screen with screencast.jnlp, I am connected via ADB and ADB sees the device. When I start screencast.jnlp is sees the devices but all I get is a white screen? I can click on the White screen and it selects whatever app or icon is in that part of the screen on the device and I can control my nook from my PC. I just cannot get the display from the nook to show on my PC. :crying:
Trying to display nook screen on my PC with Android Screen Capture:
ADB starts and sees device. I start Android Screen Capture and it sees device but I get nothing, just a Android green guy icon. :crying:
Is there anyone out there that has successfully displayed a Nook Tablets screen on their Windows 7 or XP machine? Any help is greatly appreciated.

[SOLVED] Unable to access with ADB/No RSA Fingerprint Key Window

--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.
For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.
I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:
-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.
When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.
What am I missing?
I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")
I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.
Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
Problem finally fixed!
Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
markfm said:
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
Click to expand...
Click to collapse
... no dice.
Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.
Thank you markfm for the extra drivers.
I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.
Done and done!
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
scooterd said:
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You'll have to bear with me because I'm not familiar with Mac file structure.
I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).
I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.
If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.
Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
scooterd said:
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Click to expand...
Click to collapse
No problem at all, happy to help! It sounds like you have everything set up properly, however the terminal doesn't open automatically (you need to do it manually). But you shouldn't need to open the terminal to get ioroot to work, after you've unzipped the ioroot.zip file, simply navigate to the ioroot folder, right-click on ioroot.bat and choose Run as Administrator. That should run through the entire process for you.
If you want to test your adb connection (testing not required for ioroot to work) you'll need to open the command prompt manually. Press Windows Key+R, in the run window, type cmd and press enter, this will open the command prompt. When you're in the command prompt, you'll need to change directory to the location of adb.exe in the bts folder inside the ioroot folder. Mine was in a folder named android on my C drive so the address looked something like this: C:\android\ioroot\bts the command you'll type in command prompt would be: cd C:\android\ioroot\bts then press enter. Then you can type adb devices and see if you're connected properly.
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
---------- Post added at 04:33 PM ---------- Previous post was at 03:46 PM ----------
scooterd said:
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
Click to expand...
Click to collapse
You sir are a genious. After changing my USB cord, I'm rooted and all is well in the world. It's always the little things that matter
My Pleasure! It's the little things that matter and the little things that kill!! I'm glad you're finally victorious!:laugh:
EDIT: Nevermind, I got it to work through Internet>Ethernet.
postal302 said:
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Click to expand...
Click to collapse
Hi, hope this thread is somewhat still alive. sorry for the late add on... please help.
Sorry I'm a complete moron when it comes to rooting and ADB / RSA stuff and have no idea what exactly i am doing but for some reason my macbook won't allow me to authorize my oneplus. the authorize computer dialog box never pops up however i get a notification when my phone is plugged in that debugging is active. developer options have been reset, multiple usb cables have been used, and authorization has been revoked multiple times as well.
Im not sure how to access my adb settings on mac and when i attempt to go into terminal and try kill-server / start-server commands i get error messages as commands are not recognized.
Any help is appreciated as i can no longer use stock rom on OPO and i can't go about rooting my device
Wrong forum area -- this is for the Verizon LG G3 smartphone.
Same here! WITH NEXUS 7
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Jesusmaryqueen said:
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Click to expand...
Click to collapse
It is also possible to overcome the situation, by installing Mobilego software on your PC and follow the instructions accordingly (connecting your android using usb & debugging etc,.). You will get a RSA fingerprint request.. Easy Once it's done, u can close the mobilego software in the PC and open someother software for example Bacon root toolkit for oneplus one etc etc.. Hope this helps
adbkey doesn't exist
I don't know what i did wrong before, but my computer just DOES NOT have adbkey and adbkey.pub anywhere! First, i thought it was my phone's fault. Then, i tested in a different pc, and it worked. How do i generate those keys? There are no helpful answers in the internet yet...

adb Unauthorized except in 5.1.1

I currently have 5.1.1 installed on my honor 5x and am able to use adb automatically without accepting an RSA prompt (have installed twrp, rooted, etc.) but when I dload a MM stock rom and use usb debugging it is unauthorized and I get no RSA prompt I've even gone as far as to delete /data/misc/adb from my device and adbkey.pub from my desktop but there is still no pop up authorization in MM
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
ShadySquirrel said:
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
Click to expand...
Click to collapse
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Tsunetoma said:
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Click to expand...
Click to collapse
Tried toggling the debugging switch? I had issues like these on one of my previous devices, but usually these were fixed with a simple port change or debug off/on switch, if revoke->replug didn't work.
Have you checked drivers, or if dmesg says something about the device, if you're on Linux? Sometimes even running multiple adb instances (like one from terminal and one from Android Studio, for example) can cause this behviour.
Enable rsa key authentication

Force unlocking an encrypted android 9 device

Does anybody know of a way to gain access to a password encrypted android 9 device? It is an Alcatel 5033D, locked bootloader and stock recovery, and I have no access to the virtual keyboard from the lockscreen after force uninstalling Gboard; which apparently the device was relying on for the lockscreen, even though other virtual keyboards work just fine after unlock. I am aware that USB OTG might be usable to enter the passphrase, using a physical keyboard, but I do not have the requisite USB OTG hub for that job and would like to try every other alternative before buying one as a last ditch effort.
I have tried to boot into recovery and sideload stock open Gapps, which contains google's keyboard, but it will not pass the signature verification phase and thus aborts the install. I do have USB debugging enabled and I can see the device when executing 'adb devices' but it is not authorized so I cannot actually interact with the device directly using adb. I have tried killing the server and starting it again with root (on my host machine) and this changed the device status from 'insufficient permissions' to 'unauthorized' which did not help at all. I do see an option for 'Enable adb' in the stock recovery screen, but I when I run that it prints the following; "Enable adbE:Failed to mount /persist: No such file or directory. /persist not yet mounted!"
Anyone got any ideas? Thanks in advance for any support

Unknown USB Device (Android Device)

I was wondering if anyone could help me with an issue I am having with Windows 11.
I have an old Samsung Galaxy Tablet (2013), the MicroUSB port had to be replaced as the port had broken. Before the repair, the tablet could connect to my Windows 11 PC with no problem, it showed up in Device Manager and File Explorer fine. After the repair, the Tablet will no longer connect and shows up as an "Unknown USB Device".
All methods I have tried, including installing new Drivers, have failed.
If anyone can help, I will really appreciate it!
Who did the repair? It seems whomever did the repair either didn't use the correct parts or installed them improperly.
A friend of mine did the repair. They are quite good at soldering, I will ask them to have another look at the port.
I know the correct part was used as we got the Port from another tablet of the same model.
Check for hardware issues
There’s a possibility that you’re unable to use your USB device due to a hardware issue, meaning that the problem lies within your computer and not the operating system. Here are two easy ways to test if this is the case, which can easily prove whether you need to look into getting your computer restored or can proceed with the methods below to fix system-originated issues.
Plug out your power supply
For some reason, temporarily unplugging your power supply and then connecting the problematic equipment into your computer may fix the Unknown USB device issue on Windows 10. Simply disconnect all charging cables from your laptop until your computer is only running on its integral battery. Then, plug in the USB device to see if your system recognizes it.
Uninstall the USB Driver in Device Manager
Press the Windows + R keys on your keyboard at the same time to bring up the Run utility.
Type in “devmgmt.msc” without the quotations marks, then hit the OK button. This is going to launch the Device Manager in a separate window.
Expand the Universal Serial Bus controllers section, then select the Unknown USB Device (Device Descriptor Request Failed) from the list.
Right-click on the selected USB device and choose Uninstall from the context menu. Follow any on-screen instructions to remove the device.
When the uninstallation is complete, reboot your system. It’ll automatically reinstall the drive correctly, which may help you get rid of the error you’ve been receiving.
Regards,
J Wick

Categories

Resources