Related
Does anyone know how to setup fastboot on windows 8? I tried to enter the C:\android-sdk-windows\tools in environment variables to get fastboot to work, but there is no such option anymore in the computer settings. ADB works fine, just cant get fastboot to work, keeps telling me "waiting for device" when i try a fastboot command while the phones at the fastboot menu and hooked up to the computer.
That's driver related not fastboot related. It wouldn't even say that if it was fastboot. It would say "fastboot" is not recognized as an internal command. But yeah you're experiencing a driver error. You could try installing PDAnet and have it install its android driver. Otherwise your outta luck since windows 8 won't let you install unsigned drivers.
Sent from my Galaxy Nexus
That worked great! Thanks man!
ÜBER™ said:
That's driver related not fastboot related. It wouldn't even say that if it was fastboot. It would say "fastboot" is not recognized as an internal command. But yeah you're experiencing a driver error. You could try installing PDAnet and have it install its android driver. Otherwise your outta luck since windows 8 won't let you install unsigned drivers.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
The Samsung USB drivers are signed. And actually, you can install unsigned drivers in Windows 8 if you disable driver signature enforcement (DSE).
adrynalyne said:
The Samsung USB drivers are signed. And actually, you can install unsigned drivers in Windows 8 if you disable driver signature enforcement (DSE).
Click to expand...
Click to collapse
Yeah but the Samsung drivers aren't his issue. Those don't include the android driver that is needed for fastboot. At least that was my experience. I had to manually install that. And thanks I didn't know that.
Sent from my Nexus 7
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?
I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)
Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.
KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.
I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
Same here
It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk
Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?
You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs
Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?
superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze
i have same problem
Hi
I have a problem in unlocking my redmi note 5 pro.
I followed every steps which said guide but im stuck in step when i have to turn on xiaomi unlock tool.
After entering fastboot and connecting to laptop, windows recognize my phone as fastboot devices i can use every command possible to use. But if only i run any xiaomi tools fastboot become inactive it shows: "press any key to continue".
I tried almost everything, windows reinstall, drivers reinstall, didnt work. PLZ help me.
It`s because i5-8xxx or i7-8xxx.Try another computer which isn`t these.
Try another port of USB, don't use 3.0 USB port. It's fix mine.
I have intel celeron :x
I tried both on usb 2.0 and 3.0 didnt work.
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
download minimal ADB and Fastboot and turn on usb debugging from developer options. Also accept the popup on screen when you connect phone to PC after this
I have the same problem, have you succeeded ?
Thank you
I have the same issue with my Note 8T
i had the same problem with my note8. try to google around 1 hour. & that's the ones topic about it. unfortunately it has no answer poor me
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
Try downloading the Xiaomi unlocking tool, I didn't have problems with drivers, but I saw a messages about downloading drivers and "Driver already installed" for my phone within the application log.
Give that a try!
But problem with Note 8. I don't remember when it started, but on crDroid 6 it definitely worked.
After that I notice in device manager what it determinate as some SAMSUNG Adb Device with Clock World driver. I had ADB Universal Driver installed, after uninstalled everything start work fine.
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
scarlos89 said:
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
Click to expand...
Click to collapse
Use W7
W10 always have problems with some driver signature
loopypalm said:
Use W7
W10 always have problems with some driver signature
Click to expand...
Click to collapse
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
scarlos89 said:
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
Click to expand...
Click to collapse
you have to wait
i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
aidenskcyu said:
i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
Click to expand...
Click to collapse
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
SubwayChamp said:
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
Click to expand...
Click to collapse
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
aidenskcyu said:
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
Click to expand...
Click to collapse
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Use known good data cable!!!
Does the phone see the connection?
Is it configured properly?!!!
Try another port.
Reboot, reboot, reboot...
Event manager, check for error messages.
Disk management>scan for new disks, open from here!
Device management, update driver, rollback driver... reboot.
Meh, play with it...
SubwayChamp said:
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Click to expand...
Click to collapse
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
aidenskcyu said:
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
Click to expand...
Click to collapse
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
SubwayChamp said:
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
Click to expand...
Click to collapse
i tried it but it has exclamation mark in android bootloader interface.
aidenskcyu said:
i tried it but it has exclamation mark in android bootloader interface.
Click to expand...
Click to collapse
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Try to install ADB and FastBoot drivers for redmi note 8
If Dosent work text here
SubwayChamp said:
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Click to expand...
Click to collapse
yes i did install it
aidenskcyu said:
yes i did install it
Click to expand...
Click to collapse
All is here in this same sequence.
i dont know why i get this error code 10.
aidenskcyu said:
i dont know why i get this error code 10.
Click to expand...
Click to collapse
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
SubwayChamp said:
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
Click to expand...
Click to collapse
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
aidenskcyu said:
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
Click to expand...
Click to collapse
Well, at least you got your device showed, no?
To power off the device you can put it in fastboot mode, after of approximately 10 minutes if the device is not attached to your PC, it'll power off, then you can charge it.
But if your device reacts to the power charger trying to boot to nowhere, then fastboot will charge the battery but very, very slowly.
Do you have bootloader unlocked? Why not flashing it through EDL mode?, you don't need battery power to do that.