Related
I have two droid 3's and I rooted them both and went to install a blue theme on one of them from the rom manager app and it worked great, so I did it on my second one, too. When it was in the reboot process it never finished bootoing and it stopped at the red M. All it shows is the boot logo, not the boot animation. I have tried flashing it with rsd lite, but it always fails. Is there any other ideas as to what I should do?
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there. Check this thread on users with the same issue.
Willis111 said:
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there.
Click to expand...
Click to collapse
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
RaTTeDH said:
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
Click to expand...
Click to collapse
I meant rsdlite, have you ever used it with either phone without having an issue? I edited my previous post, added a link you might want to check out.
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
I have never used RSDLite before. So I do not know if it works. But when I am flashing it with the stock 5.6.890 it fails at step 5. It reboots the bootloader. But it fails always at step 5. Let me try the other replys...
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
Click to expand...
Click to collapse
I have downloaded this and tried this. When I run the application moto.fastboot.exe it takes like 30 seconds and when I run the batcch file it immediately finishes and says moto fastboot is not recognized as an internal or external command, operable file or command. And finishes immediately. Sigh.
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
Click to expand...
Click to collapse
The unbrick script will flash a vzw rom to your xt860 and have you stuck at the M logo anyways so I wouldn't suggest trying that. If you haven't used rsdlite before and are having trouble with it now you probably need to install the drivers from the motohelper software.
1./ download the drivers (from motorola)
2./ shutdown phone and turn it on by hold m + power
3./ select ap fastboot mode, enter and plug your phone into the computer ignoring any add new hardware
4./ start the driver install and follow it through
5./ unplug and replug your phone with computer leaving it fastboot mode.
Rsdlite should show your device under listed devices when you start it up at this point and allow you to flash w/e rom. I would suggest using the iucell or brazil retail fastboot files from the xt860 fastboot thread to get your phone up.
I fixed it using CMD in Windows flashing some stuff. Thanks guys!
I'm struggling to install Beanstalk on my 4X HD and I'm just so tired right now...
I somehow managed to unlock bootloaer via lock-relock app (in hidden menu, BL test shows "unlock" so I guess that's ok?)
I have root - well, I wouldn't be able to unlock BL without it...
And now, to install Beanstalk I need to flash CWM - http://forum.xda-developers.com/showthread.php?t=2523732
But to flash CWM I need to set up fastboot drivers and there's the problem :/
With the simple app - http://forum.xda-developers.com/showthread.php?t=2588979 - adb works ok, with "adb devices" it shows my device, but "fastboot devices" doesn't work at all. And I've read that there's this way to make fastboot working on Windows 8.1 - http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ - but it doesn't work as well...
There's too much things... Dis I miss something? Maybe there's a faster and easier way to install Beanstalk? What do I have to do to get KitKat flavour on my O4X? :laugh:
You can flash recovery via adb or terminal emulator
I have the same problem, you should try this, http://forum.xda-developers.com/showthread.php?t=2230934....
I updated drivers while i unlocking bootloader by toolkit, you start toolkit, go unlock bootloader before that you check usb debugging, than follow instruction in toolkit, than phone will reboot and enter in donwloading mode(for bootloader unlock) go right click on This PC, Properties, Device manager, and you will see fastboot. And than just update driver... Right click on fastboot and Update Driver Software, navigate to the file and thats it....
Fastboot driver Download: http://www55.zippyshare.com/v/67020672/file.html
You will need winzip for this.
You can install cwm via this rootkit and later you just update with rom manager https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
I flashed recovery straight from my phone using a terminal emulator, no need to connect it to a computer. I can't remember the command though.
Sent from my Nexus 5 using Tapatalk
Ok, Kitkat is now powering my phone :victory:
Thanks for all the advices, but I used little app from GP called Flashify. It flashed CWM_6.0.1.1 with no problems at all.
I'm so happy to finally have Beanstalk ^.^
Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?
here you are
firespitta said:
Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.
as far as your fastboot issue, try re installing the htc and fastboot drivers.
I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?
These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.
@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.
Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?
LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.
LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.
Yup, flash the .img files individually, the batch command doesn't work.
Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)
[GUIDE]HOW TO INSTALL CUSTOM RECOVERY, UNLOCK BOOTLOADER & UPDATE FIRMWARE IN Dec2019
I SOLVED THEM MYSELF, GUIDE WILL BE POST WHEN I CAN POST A THREAD
*i posted them here
INITIAL POST
Unable/failed to unlock bootloader/fastboot
It's been 8 hours and I have literally tried everything even to my own method but none of them worked (I follow all tutorial and guidance perfectly on both xda and from a article and youtube). When I click the unlock.cmd, it just flash quickly (probably open command prompt in split second) and do nothing (I had checked with a command; fastboot oem device-info). Then I tried click again and it just stopped at support all device. The folder location is on C aka main storage, I have installed all the required stuff and I'm on 6gb variant. I even wipe clean my phone and it is on Android Pie. Trying to unlock this bootloader is driving me insane. Official TWRP app does not have my variant (M1) instead they have M2 so I doubt I can use flash recovery from there. I just wanted to install TWRP and Havoc OS with Magisk and root. My phone is legit, I have warranty and all that. I just want to unlock my bootloader and able to relock it for future warranty use.
To clarify things further, I have no issues with ADB displaying on Device Manager and I can see Bootloader on Device Manager without any warning sign. I even switch the cable (both are data cable) and for some reason it only worked on usb 3.0 port. I also had tried all connection mode (PTP (no MTP), USB Tethering, File Transfer and nothing). I had make sure I had installed the driver too and my PC already have ADB but I installed them thrice anyway.
EDIT1: I just noticed my warranty had expired so I decided to officially unlock the bootloader and it was a success but I still can't use fastboot command to flash TWRP (fastboot flash recovery twrp bla bla.img) and it does run the command just failed.
EDIT2: Alright it was solved!
I had already written a guide on how to solve it but I couldn't post it.
I AM POSTING THIS HERE BECAUSE XDA SUCKS, I COULDNT POST A NEW THREAD SO HERE WE GO.
HOW TO INSTALL CUSTOM RECOVERY, UNLOCK BOOTLOADER AND INSTALL FIRMWARE IN LATE 2019
*last update 8 december 2019
#I AM NOT RESPONSIBLE FOR HARD BRICK OR SOFT BRICK OF YOUR DEVICE SO TRY AT YOUR OWN RISK AND FOLLOW WITH CAUTION
*this is based on my personal experience of my continuous effort in reading, researching, testing, tweaking all for the past few weeks
*note this is a guide specifically for these problems
-my post on how I failed to unlock bootloader
-command write failed
-phone not detected in bootloader
-adb or bootloader driver showing error on device manager
-other guides not working on amd rig
-unable to flash recovery
-phone not detected in adb
-etc
CUSTOM RECOVERY
#DO NOT INSTALL ORANGE FOX, YOU WILL GET ERROR 7 UPON FLASHING VARIOUS CUSTOM ROM
TWRP
*you can install orange fox later on by dirty flashing it (install without wiping your data)
*lastest one is 3.3.1.0
ADB & FASTBOOT
15 seconds ADB
*this is a system wide adb, there is no need for 'cd' command and you can just use straight up use adb or fastboot command and uninstall other adb along with their drivers because other adb wouldn't work and use outdated client and driver
HOW TO UNLOCK BOOTLOADER
#THIS IS AN UNOFFICIAL WAY TO UNLOCK YOUR BOOTLOADER, I HAVENT TESTED THIS MYSELF
Download this
1. Do not use your stock charger, get data cable or third party one
2. You may need to connect your cable to USB 3.0/3.1 port (blue one)
* if it didn't work, you may need to use USB Hub (even cheap one will work)
3. Open up your CMD (search cmd or use powershell if you like on windows search)
4. Type adb reboot bootloader in cmd or .\adb reboot bootloader in powershell
5. Extract the rar you downloaded
6. Go to unlock folder and double click on unlock.cmd
*if these didn't work then you can officially unlock it (if you unlock it officially, your warranty is really now voided and can't lock back bootloader)
#OFFICIAL WAY TO UNLOCK YOUR BOOTLOADER (two ways)
Method 1
1. Open your cmd or powershell
2. Type adb reboot bootloader in cmd or .\adb reboot bootloader in powershell if you haven't enter fastboot or bootloader
3. Type fastboot oem unlock in cmd or .\fastboot oem unlock in powershell
Method 2
1. Download this on your phone
2. Run it and done
##CHECK TO SEE IF IT SUCCEED OR NOT BY TYPING FASTBOOT OEM DEVICE-INFO IN CMD OR .\FASTBOOT OEM DEVICE-INFO IN POWERSHELL AND MAKE SURE THE COMMAND IS IN LOWERCASE
HOW TO INSTALL CUSTOM RECOVERY
1. Boot to bootloader by either using command or power off then hold both power button and volume up button then release power button when phone vibrate
2. Open your cmd or powershell
3. Copy your custom recovery img name with .img
*it should look like this; twrp-3.3.1-0-X00T-20190526.img
3. Type fastboot flash recovery [paste it here]
*wait 1 minute or longer
4. Boot into recovery by holding both power button and volume down button then release power button when the phone vibrate
TROUBLESHOOT
Use command fastboot fastboot devices (when in bootloader) and adb devices (when device is on systemui/not in bootloader)
A: If the device shows random alphabet or number like JADSHFE2849 then your device is detected
B: If it doesn't, try changing usb port and wires
*remember to put .\ at the front of every command when using powershell
*cmd is command prompt
HOW TO INSTALL FIRMWARE (two ways)
#WARNING THIS OFFICIAL WAY WILL REVERT YOUR CUSTOM RECOVERY INTO STOCK ONE
*doing this will wipe out your internal data
OFFICIAL WAY
1. Download latest firmware here to your sd card
*remember to set your region first by scroll down to bottom left near the language otherwise it wouldn't work or worse, may brick your device
2. Wipe clean your rom (wipe system, data, etc but not vendor)
3. Boot into system even when no OS is available
4. Complete the setup
5. Boot into recovery
6. Apply update from external storage
7. Browse to your download location and tap it
8. Wait around 10 minute - 15 minute for it to finish
9. Congrats, your firmware has been updated and you can proceed to flash custom recovery again
UNOFFICIAL WAY
Flash this on your custom recovery
*direct link if you prefer but may be outdated as time goes on {Mod edit: Link remove}
Looks like you need to use windows 7 with USB 2.0 port. Or wait till warranty runs out and unlock using official app.
What processor does your system has?
Ryzen? Goodluck with that then.
Fastboot driver doesnt work on amd ryzen builds
Same problem here...
Not even on usb 2.0 ports
gdarshan said:
What processor does your system has?
Ryzen? Goodluck with that then.
Fastboot driver doesnt work on amd ryzen builds
Same problem here...
Not even on usb 2.0 ports
Click to expand...
Click to collapse
Ah shoot, yeah I have Ryzen 3 2200g paired with GTX 1050 Ti and Windows 10 Pro.
Vysair said:
Ah shoot, yeah I have Ryzen 3 2200g paired with GTX 1050 Ti and Windows 10 Pro.
Click to expand...
Click to collapse
Ooooooo...... I have ryzen3 2200g(my new pc) and i tried to flash fastboot rom on azmpm1 but after trying almost 3hours i can't abale to flash it, before i have intel pentium and i flashed fastboot rom without a single problem
---------- Post added at 06:20 PM ---------- Previous post was at 05:56 PM ----------
Read this for quick work arround>>
https://www.reddit.com/r/Amd/commen..._source=amp&utm_medium=&utm_content=post_body
Rommaster94 said:
Ooooooo...... I have ryzen3 2200g(my new pc) and i tried to flash fastboot rom on azmpm1 but after trying almost 3hours i can't abale to flash it, before i have intel pentium and i flashed fastboot rom without a single problem
---------- Post added at 06:20 PM ---------- Previous post was at 05:56 PM ----------
Read this for quick work arround>>
https://www.reddit.com/r/Amd/commen..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I still don't know how I did it but I use platform tools from google and it worked because the platform tools use the very latest adb client (around 60 or something). I do install something else like sdk tools and twrp 3310 but i had no idea why it worked which is why i havent post link for guidance. I suspect it was only because of my platform tools. (also for windows 10, i doubt you need those adb drivers bull****)
EDIT: I found a better solution, install 15 seconds adb. This is universal ADB and can be use on any directory but I recommend you to delete the drivers and older ADB beforehand.
Hi. Thank you very much for posting this, I'd been frustrated trying to install drivers but somehow I couldn't get it right. I found this and installed the 15secondADB thing, tested a few commands and everything seems to work. I'm just wondering whether I'll need to install any more drivers in order to start flashing staff through Fastboot.
Thank you in advance
Kevo0h said:
Hi. Thank you very much for posting this, I'd been frustrated trying to install drivers but somehow I couldn't get it right. I found this and installed the 15secondADB thing, tested a few commands and everything seems to work. I'm just wondering whether I'll need to install any more drivers in order to start flashing staff through Fastboot.
Thank you in advance
Click to expand...
Click to collapse
I'm glad it helped. For the driver, there's no need for it because 15 seconds ADB should have installed the required driver or update it. However, I recommend you to try do windows update check to install any missing driver just in case. (I haven't tested this myself though since there's no driver to install from there)
Moderator Announcement
Thread cleaned from download links via pling.com!
pling.com is a paid-per-download website, as such violating rule no. 13 of the XDA Forum Rules and therefore not accepted as file host on XDA. Please refrain from sharing those links in future! Thanks for your cooperation.
Stay safe and stay healthy!
Regards
Oswald Boelcke
Forum Moderator