Related
Although I can pair my galaxy S2 with windows (Win 7, x64), and have it show up under Bluetooth devices (and visa versa for my computer within my phone), I can't have MyPhoneExplorer/Kies recognise the Bluetooth connection. Kies throws up a complaint about a missing Bluetooth device driver which is shown in device manager as "Bluetooth Peripheral Device". All Google searches for this device driver have ended poorly. Has anyone else encountered this problem?
Thanks for your help.
For those interested, managed to correct this via starting up MyPhoneExplorer on the phone when initially pairing the phone with my computer. Although the device is still missing drivers within device manager, everything seems to work. Does anyone else have the phone identifying as missing drivers in Win 7 x64? There seems to be a 'solution' to this, mentioned on several forums (for example, here: http://forum.xda-developers.com/archive/index.php/t-430368.html) that involves installing a generic driver from the windows mobility device center - but surely doesn't seem right as it's a device driver for windows mobile, when I've seen the same advice put out for Blackberry's, iphones, etc. People seem to think it works but I can't help but think that there are some consequences here that are unconsidered.
spambot06 said:
For those interested, managed to correct this via starting up MyPhoneExplorer on the phone when initially pairing the phone with my computer. Although the device is still missing drivers within device manager, everything seems to work. Does anyone else have the phone identifying as missing drivers in Win 7 x64? There seems to be a 'solution' to this, mentioned on several forums (for example, here: http://forum.xda-developers.com/archive/index.php/t-430368.html) that involves installing a generic driver from the windows mobility device center - but surely doesn't seem right as it's a device driver for windows mobile, when I've seen the same advice put out for Blackberry's, iphones, etc. People seem to think it works but I can't help but think that there are some consequences here that are unconsidered.
Click to expand...
Click to collapse
Yup, no drivers installed on Win 7 x64, but i have no problem with bluetooth. Successfully paired my SII with my pc.
spambot06 said:
For those interested, managed to correct this via starting up MyPhoneExplorer on the phone when initially pairing the phone with my computer. Although the device is still missing drivers within device manager, everything seems to work. Does anyone else have the phone identifying as missing drivers in Win 7 x64? There seems to be a 'solution' to this, mentioned on several forums (for example, here: http://forum.xda-developers.com/archive/index.php/t-430368.html) that involves installing a generic driver from the windows mobility device center - but surely doesn't seem right as it's a device driver for windows mobile, when I've seen the same advice put out for Blackberry's, iphones, etc. People seem to think it works but I can't help but think that there are some consequences here that are unconsidered.
Click to expand...
Click to collapse
I tried on my Win7 installation just now. Only consequences so far: works. Be sure to download Windows Mobility Center 64bit if you are on 64bit Windows.
I tried that today.
Works like a charm to enable two way file transfers between Windows 7 notebook and Samsung Galaxy S2.
However, the bluetooth stack on this phone is still missing so many features... It's a pity, really.
Thanks for your help.
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Ok I got to the update driver menu by selecting "change settings" of the general tab, not the driver tab. Then selecting driver tab I was able to "update driver...".
I followed the rest of your instructions precisely, and presto..... it almost worked. It tried a lot harder when I attempted to send an image phone -> pc, but still failed... Any extra help?
Right click on Bluetooth icon in notification area and click receive file. Then try sending file from phone
Update: Regarding drivers. I installed Atheros bluetooth Win7 x64 stack. It recognizes all blueooth drivers for SII but I couldn't use files transfer
My fix
I just went into the devices properties and under services, unchecked SMS and no more missing Bluetooth Peripheral Device driver! I don't know what functionality i have turned off (since i don't use that service) but it help to remove the needs troubleshooting icon.:good:
Sweet
:laugh: Worked like a charm thanks bro. File transfer work and all Sending video to my computer as I type this.
cousinit99 said:
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Click to expand...
Click to collapse
Thanks..it worked for me..
cousinit99 said:
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Click to expand...
Click to collapse
Thanks buddy. it worked for me...:good:
cousinit99 said:
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Click to expand...
Click to collapse
Worked great...ty
It worked like a charm. Thanks.
I was wondering about this and trying to figure this out for a very long time, but your answer came like a blessing. Kudos!
cousinit99 said:
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Click to expand...
Click to collapse
No internet connection - Bluetooth peripheral device not found
I was trying to connect my samsung star pro to my computer using bluetooth dongle. it got connected and if i tried to connect internet via access point it gives an error "Bluetooth peripheral device not found". i want to connect to internet with the dongle. can anybody help me out?
cousinit99 said:
Installing Windows Mobile Device Center is not necessary. The peripheral just needs a standard bluetooth COM port driver.
1. In the Bluetooth device window, right-click the phone icon and select 'Properties'
2. Click 'Hardware' tab then 'Properties'
3. Click 'Change settings'
4. Select the 'Driver' tab, then 'Update driver...'
5. Click the second option: "Browse my computer for driver software"
6. Click to choose the option "Let me pick from a list of device drivers on my computer"
7. From the list "Common hardware types", Select 'Ports (COM & LPT)'
8. Two droplists appear. Choose 'Microsoft' in the "Manufacturer" list, then 'Standard Serial over Bluetooth link' in the "Model" list
9. A warning window pops up. Ignore it by clicking 'Yes'
10. Presto, the device functions properly..
Click to expand...
Click to collapse
akfuji said:
I just went into the devices properties and under services, unchecked SMS and no more missing Bluetooth Peripheral Device driver! I don't know what functionality i have turned off (since i don't use that service) but it help to remove the needs troubleshooting icon.:good:
Click to expand...
Click to collapse
Thank you both, now i have no more issues with bt peripheral driver.:good:
Didn't work for my laptop, because when I right click on bluetooth notification area, I don't have "receive file" option on the display which coming on. . .
Give me more advice, please. . .
Excavating. Tried all the above. Still, two components are not installed. Bottom line, can identify speakers and headphones but can't connect - says try again. No problems on android device, but windows 7 64 struggles. Strangely, similar problems were with a previous machine (thinkpad x200, windows 7 32) and different devices. Now I am on x230 thinkpad.
Here are the screenshots
bluetooth incomplete installation 1.png
drive.google.com
bluetooth incomplete installation 2.png
drive.google.com
bluetooth incomplete installation.png
drive.google.com
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller.
Note 2: You will need to have a USB 3.0 and a USB 2.0 ports for this to work. USB 3.0 for the fix and the 2.0 to install the S1Fastboot Driver.
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
EDIT: If the file is corrupted, here's the Mediafire link. Click!
kyzn said:
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
Click to expand...
Click to collapse
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
What if I only have USB 2.0 on my computer?
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
can you re-upload the drivers its corrupted, thanks
nagarjuna93 said:
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
Click to expand...
Click to collapse
nanoleet said:
What if I only have USB 2.0 on my computer?
Click to expand...
Click to collapse
Sorry, but currently the fix I found was for UBS 3.0 only. Did you already try the other fixes here in XDA? Some of them worked for USB 2.0.
In my case it was a combination of this fix, and installing the S1Fastboot driver via USB 2.0.
nosmaster said:
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
Click to expand...
Click to collapse
That did not work for me. ADB drivers installed but not the Fastboot, so I thought I'd share the way that did.
hrashdan said:
can you re-upload the drivers its corrupted, thanks
Click to expand...
Click to collapse
Done.
Work for me!!! Thanks
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
manudo said:
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Yes.
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
For those with intel 8/c220 usb series you may have a look to
http://plugable.com/2012/12/01/windo...#comment-19066
Andrew (thanks) submitted there, in his comment, modified drivers in December 2013 for the Intel 8&7/c series
Be sure to use the right one because it could be a big mess (my experience)
see my post here (i tried to use 7c series drivers given in that link above,and 8 series one with the trick given a the begining by the initial writer
) big mess, only the Andrew modified ones for my 8Cseries worked :
http://forum.xda-developers.com/showthread.php?p=49426792
bountygiver said:
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
Click to expand...
Click to collapse
Those are the modded drivers specifically made to support Intel 7 USB 3.0 ports. Do you even have the specific hardware those drivers were made for?
Thanks.. was trying to flash my old pro after a long time and tried everything.. this was the only thing that worked..
This worked for me on Windows 8.1 x64.
However, I had originally "Renesas eXtensible Host Controller" installed in my device manager so I downloaded the latest Renesas USB 3.0 drivers in stead of the Intel drivers but it worked perfectly afterwards!
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
molnartibor said:
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
Click to expand...
Click to collapse
go to your Bios USB settings and disable xHCI, that worked for me & I was able to do a system restore
Any info of working fastboot driver for Windows 10? Those posted in OP not accepted.
device is rooted and when changing to ptp mode it works just fine, so the cable is good.
device is identified by mtp when using windows 7 pc.
Hey heathenasparagus, you will need the following the access your device storage on mac (I use OSX 10.11.14 El Capitan)
1. Android File Transfer
2. USB Debugging on phone from Developer Settings
3. After installing Android File Transfer, go to system preferences on mac -> Users & Groups -> Current User (should be preselected) -> Login items (tick Android File Transfer)
When you connect your lg v10 to the computer, the android file transfer app may say it can't connect to the phone. Don't worry, this is because lg v10 prevents automatic MTP access. however when you connect your phone, the lg v10 should say 'allow computer to access the storage (yes/no)' or something like that, and just press yes. The Android File Transfer app will open by itself and you can drag and drop files over. This works with my H962 lg v10 on MM.
I have not managed to connect to my Redmi Note 4 (Android 6.0 MRA58K, MIUI Global 8.1 | Stable) via adb from my Windows 7 computer.
With my old SGN4 this was never a problem but I am a noob on the RN4.
I have Android Studio (with adb) installed, then
I connect my mobile via USB cable
I select on the mobile "Use USB for: Transfer files (MTP)", USB debugging is enabled and I can see the phone in the Windows explorer
then I open a command prompt and run adb but "nothing happens":
c:\Progs\Android\sdk\platform-tools>
c:\Progs\Android\sdk\platform-tools>adb.exe logcat
- waiting for device -
^C
c:\Progs\Android\sdk\platform-tools>adb devices
List of devices attached
c:\Progs\Android\sdk\platform-tools>
What am I missing???
Check drivers on control panel, it is correct?
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Gollob said:
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Click to expand...
Click to collapse
You have wrong adb driver (choose manually other from control panel)
dromaczek said:
You have wrong adb driver (choose manually other from control panel)
Click to expand...
Click to collapse
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Gollob said:
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Click to expand...
Click to collapse
You must authorized access and check all ADB options on xiaomi rom to use for example adb density command etc (and log on mi acount)
[Solved] Xiaomi Redmi Note 4 : Connection with ADB
Hi,
As we all know Xiaomi works on its own MIUI, So when you want to connect to adb that is developer mode you need to connect as MIDI,
Enable MIDI
Step 1: Goto settings > Additional Settings > Developer options
Step 2:In developer option, Enable developer options,
Step 3: In same menu go down in side Networking and from the SELECT USB CONFIGURATION, select MIDI
Now check adb devices on your command prompt you can see your Xiaomi is connected.
Happy Coding
Does your phone show up on the terminal with adb devices command when in recovery? Can be stock recovery too.
Also, in fastboot, use fastboot commands
i.e. fastboot devices instead of adb devices
One more thing, go to device manager and manually install a legacy driver and browse to adb and choose Android Bootloader Interface (ABI) look into it, it's possible.
That should do it. Tell me if it helps.
Sorry I don't know how to quote stuff and format commands.
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
hello brother, I'm facing the same issue while unlocking the bootloader.
I think these is prob with the drivers.. pps help me out
DONT END UP REMOVING CORE SYSTEM APPS IT WILL RESULT IN A BOOTLOOP!
You need a PC to do this.
This helps you to select the app you want to debloat and gives you options to restore/backup as well.
It also includes a ton of other features.
You can either download the standalone JAR file or the ZIP file which contains both fastboot and ADB.
All credits go to Saki.
Enable developer options in Android.
MIUI: Go to Settings > About device and tap ‘MIUI version’ seven times to enable developer options.
Enable USB debugging in Android.
MIUI: Go to Settings > Additional settings > Developer options and enable USB debugging.
In order to use the Screen density and Screen resolution modules, enable USB debugging (Security settings) as well.
Connect your device to the computer and launch the application. The device is going to ask for authorisation, which you'll have to allow.
Wait for the application to detect your device. The device info should appear in the top left section.
Downloads:
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases
(Just click on assets for the latest version)
Latest JAR Standalone as of 9-9-2019;
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/download/6.6.1/XiaomiADBFastbootTools.jar