Database Users

[Q] Trouble when installing TWRP on Kindle

So I was following the tutorial HERE to install TWRP, after successfully installing root via the previous tutorial.
I got to the step where you have to hit "reboot" on the kindle screen, and then press any key in the CMD prompt. I waited till it was on the yellow triangle screen, with text at the bottom stating I can press power button for recovery. I hit "space" to progress my installation, and it got stuck at "activating normal <4000>" as the video said might happen.
Following the instructions, I opened Device Manager and sure enough, the kindle was displaying a missing driver icon (although mine was still called kindle, in the video it was called something else.) I told it to reinstall the drivers, and this is where it got strange. It claimed the driver was up to date, but still displayed the yellow driver error symbol. Now, when I plug in the kindle, it shows up as "unknown device" and when I try to install the driver, it claims my driver for unknown device is up to date.
Meanwhile, the kindle itself it chilling on the yellow fire/triangle screen.
wat do

It says your drivers are up to date? You shouldn't be trying to auto install drivers, you have to do it manually, or are you trying but its just not letting you?

I am manually selecting the folder in the Device Manager dialog, and it tells me that the driver for "unknown device" is up to date

I have found that if I turn the kindle off by holding the power button down, then plugging it in(while off) it will show up as "ADB Device" (not ADB Composite Device), but nothing works, and if at this point it is unplugged and re-plugged in, it returns to Unknown Device giving an error code 43

Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally

googlelover said:
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
Click to expand...
Click to collapse
well, I got it to display "ADB Composite Interface, but when I run the KFU, it says ADB Status: Offline.
Furthermore, when I run "adb devices" my kindle does not show up

What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery

SirVilhelm said:
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
Click to expand...
Click to collapse
I added the 0x18D1 to adb_usb.ini, and I beleive it was already in the other .inf file. Now, my kindle is connected, and device manager sees adb composite device, but adb devices says nothing is connected. Im feeling a reboot might be necessary, which sucks because my computer doesnt reboot well (long story)

You can try adb kill-server and try again

Trouble
Having trouble getting TWRP to install on my Kindle Fire, I had no problems getting it Rooted and getting the Market installed, but trying to run the TWRP program it just hangs at the waiting for device and the Kindle hung at the KindleFire logo. I'm running Window's 7 64 bit is this suitable for TWRP
Thanks for any help.

SirVilhelm said:
You can try adb kill-server and try again
Click to expand...
Click to collapse
it is still not seeing the kindle connected. Anyway, how do I use KFU to restore the device?

I fixed my device using the info I found in a thread: http://forum.xda-developers.com/showthread.php?t=1431785
fastboot oem idme bootmode 4000
fastboot reboot
Unplug your Fire from USB, turn it off (hold the power button ~30 sec), run the first fastboot command above, then plug it in. If the first command completes, do the second.
Click to expand...
Click to collapse

[Q] Kindle Bricked no adb, not recognized

I am stuck with this headache and have stressed my self for hours trying to fix this so now I turn to you guys for help.
My Situation:
I had kindle to 6.2.1 then I rooted it, installed CM7.
after using it for 7+ days there is an update of CM7 by another dev. which had sound in the CM7 so I tried to flash it.
I put it in the SD card and renamed it CM7.zip from Update.zip so I flashed on Custom Recovery to flash the Update.zip later finding out that I renamed it to CM7.zip so I was stuck at Customer recovery bootloop so I enter the command to flash stock recovery to boot as the CM7 required.
so after stock recovery flash on Kindle the Kindle got stuck on the "kindle fire logo"
I think it was stuck in Fastboot.
I tried with KFU and Kindle Fire Unbrick software but the thing is NONE of them detect my kindle
I have tried soo many ways to Get my kindle detected to unbrick it but still no luck
Any help would be greatly appreciated.
Thanks

BUMP!
Still need help with a bricked kindle

BUMP!
Any1?
Kindle Still Bricked and not working >.<

Have you tried Kindle Fire Utility 0.9 to install the latest drivers? After that install Kindle Fire Unbricking Utility 0.1 to unbrick. If that doesn't work, reply with a detailed explanation of what you're seeing and what you have already tried.
This post has links to both and a good alternative option: http://forum.xda-developers.com/showthread.php?p=21232193
Good luck.
Sent from my rough sketch of a Vibrant on a brick.

Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up

First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(

umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?

umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
In my case, KFU also stated
status: offline
bootmode: unknown
adb root: No
but it still worked when I tried to change bootmode to 4000.
Also, are you sure your KF is charged enough to start? Try plugging it for a while, then recheck in windows.

b63 said:
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
Click to expand...
Click to collapse
I am running Windows 7 64bit on two of my laptops and windows 7 32 bit on my desktop.
the Kindle logo is not glimmering or flashing so it is in fastboot, I know that much.
I have tried the drivers that came with the KFU 0.9.2 (Newest, I believe)
and Yes the Kindle Fire is fully (if not mostly) charged as I had it on the charger for 6 hours last night.
and No I have not placed it or renamed to c:\kfu
I will let you know in a minute about the results

If it keeps saying Waiting for Device then it's not really in fastboot. I had a similar issue and got it solved through this thread:
http://forum.xda-developers.com/showthread.php?t=1430515
It was stuck in a boot loop and appeared like it was in fastboot, but it would hang up and not respond. You may need to install the fastboot package manually and force it into the right mode. Then you can load TWRP and put it all back together.
If ADB isn't working though, you will need to start by getting that to work. It sounds like a driver issue even though you said you worked on that. You should try the Ubuntu boot method and Firekit to install the fastboot package through ADB. Those are outlined in the link above.

got it ?
if you have a 32 bit machine available that is the better choice cause you don't have to hassle with the 64 bit drivers too
here some information that should clarify the driver things:
in normal boot the device is "android composite adb interface"
in fastboot the device is "android adb interface"
here again all the possible commands to change bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !

Still no results
I connected my brother's kindle and the computer immediately recognized it and when I connect mine, it doesnt work! :'(
apparently still having the driver issues :'(
any help?
I have tried the KFU driver and that didnt work

I had a similar problem while trying to install TWRP the first time via KFU except I was stuck at the yellow triangle and not the Kindle Fire screen.
First I replaced run.bat in the KFU folder with the one from this post because my Kindle was 6.2.2. Next I installed the drivers for my uknown device in device manager both by pointing the unknown device to where I saved android_winusb.inf and also ran the install_drivers.bat. I got an error saying they could not install.
Next, I followed the steps here
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
Click to expand...
Click to collapse
and when I rebooted my Kindle, it booted normally and appeared as Kindle in Device Manager. So despite KFU not detecting my device, and the drivers giving me problems, I was still able to issue the command in KFU for normal boot mode and held the power button for 30 seconds and it was back to normal. This is on a Windows7 64bit machine. I hope this helps.

Make me the third. Here is my story.
I have lots of rooted and rom'd devices so I'm agreeing that this might be device related and not the drivers? Or maybe specifically the Kindle driver? Since all my other devices work fine.
I bought my kindle and rooted it on day one 6 weeks ago using TWRP. things have been perfect on my KF. I decided to install CM7.1 yesterday morning and it was working great. I just realized I never rebooted it so what Im going to say shortly may have been bound to happen.
So last night I decided to add a google Market update per a link on XDA that stated this can be updated to my current CM7 install. After this my KF just kept going into TWRP automatically. I then decided to load my backup rooted stock room and still my KF just boots into TWRP.
Next I decided to use rootkindlefire's unroot/stock rom to 6.2.1 (drop the bin renamed to update.zip to the SD) and got a TWRP logo screen. I powered off a couple times and now I get a KF logo screen. I tried the 20 second reset and it flashes (Windows XP see the request for a USB device also), but no KF OS loads. Windows is showing Android Phone > Android Composite ADB Interface but the SDcard does not mount files.
I tried:
Kindle Fire utility and it says: Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on. Press any key to continue . . .
SuperOneClick 2.1 says device isn not found
SuperOneClick 2.3.3 just sits at * daemon not running. starting it now on port 5037 * * daemon started successfully *
Stuck on logo option for Kindle Fire unbrick says: Kindle unbrick in progress... adb server is out of date. killing... * daemon started successfully * error: device not found error: device not found Congratulations, your Kindle should be unbricked!
My Sonxy Xperia, Eris, Vibrant and LG470 all work fine when connected.
At a loss here..
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
scrols said:
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
Click to expand...
Click to collapse
I went to another site and was able to get my kindle recognized by my PC (manually edited the drivers and reinstalled) and now Kindle Fire utility sees my device but KFU keeps saying these two lines when attempting to recover and root
adbd cannot run as root in production builds and
- exec '/system/bin/sh' failed: No such file or directory (2) -

[Q] Kindle Fire stuck at firefirefire bootloader.

So i installed C7 with clockworkmod then when i rebooted i was stuck at the firefirefire loader. I dont have a computer availible AT THE
MOMENT, i hope to be getting my laptop soon. But how can i fix this error??

can you boot into recovery? Sounds to me like you need to reinstall ROM.

No, nomatter how many times i press the button, nothing happens, but how can i mount the usb/install fresh update.zip?

To fix this you will need a computer... I don't know any other way atm... use KFU to install update.zip (aka stock) and try again.

Well by no computer i meant no windows, i have a mac with virtualbox, can that work

Ethanzh said:
Well by no computer i meant no windows, i have a mac with virtualbox, can that work
Click to expand...
Click to collapse
i think you are stuck in fastboot mode
if you have a mac try the mac version of kfu to set the bootmode to normal or any other task you want to do:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

How do i setup KFU on vista?

- download http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.3.zip
- extract to c:\
- rename to "kfu" (it don't like spaces in pathname)
- if you want to use the drivers from kfu read http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
btw do you have vista in a virtual box ?
hope you don't try to flash the original rom from amazon - you will loose fff, twrp and root
would recommend a prerooted stock rom instead:
http://forum.xda-developers.com/showthread.php?t=1569298

Yes i am using vista in virtul box and i extracted the fku to C:\fku , but how do i install the drivers, Windows isnt recognizing the fire because its stuck on fireifrefire, or does that not matter?

Ethanzh said:
Yes i am using vista in virtul box and i extracted the fku to C:\fku , but how do i install the drivers, Windows isnt recognizing the fire because its stuck on fireifrefire, or does that not matter?
Click to expand...
Click to collapse
you have to install the drivers because windows is'nt recognizing
please read the linked in post about the drivers from my last post - there is everything in there
also read this one - that should clear things up:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
for some it worked in a virtual box and for some not - good luck !

Thanks but im just curious, how can windows detect thr kindle even with thr drivers, if itsnt fully turned on yet, just stuck at boot? And also does adb have anything to do with this??

Windows will probably not recognize your kindle fire... KFU should though.

Ethanzh said:
Thanks but im just curious, how can windows detect thr kindle even with thr drivers, if itsnt fully turned on yet, just stuck at boot? And also does adb have anything to do with this??
Click to expand...
Click to collapse
I think your confusion stems from your belief that if it's "stuck" at the FFF logo, the device is malfunctioning. In most cases when the KF appears to stop working at this point, it's just in fastboot mode. In this state, you are able to issue fastboot commands to the KF and do many useful things. I believe fastboot utilizes the drivers that are packaged with ADB, so you'll see "Android Phone -> Android ADB Interface" in the device manager when Windows sees it in this mode. However, the command "adb" is entirely separate from fastboot. The device must be booted to recovery or the main OS to issue adb commands. To use fastboot, the device must be booted into fastboot mode for fastboot commands to be issued.
fiddlefaddle said:
Windows will probably not recognize your kindle fire... KFU should though.
Click to expand...
Click to collapse
This isn't meant to be a flame, although it might come off like one, but that doesn't make much sense. KFU is just a Windows batch file. All it does is shield the user from having to type a series of complex fastboot and adb commands (and performing some other menial tasks) in the proper sequence to get the desired effect. Without the hidden fastboot and adb commands, KFU is powerless to do anything meaningful on the Kindle Fire. Since fastboot and adb need the proper drivers in place to interface with the KF, Windows must first recognize the KF through those drivers.

Whenever i do Normal boot on kfu, it stays on waiting for device, as it obviously isnt recognizing the device.

And also would o have to install the drivers manually? I ran the install_drivers.bat...

Ethanzh said:
And also would o have to install the drivers manually? I ran the install_drivers.bat...
Click to expand...
Click to collapse
If you're still using Windows in a virtual machine, you're also going to have to make sure that the virtual machine has control of the device and not the Mac OS. Then see what the Windows device manager shows for the device. I posted up above what it should show when the KF is in fastboot mode. If it doesn't show that specific device when in fastboot mode, you need to remove whatever driver it's currently using, remove the device from the device manager, disconnect the KF and then try installing the drivers again. The KFU driver installer "should" work and it works for me, but YMMV. b63 also gave you directions on alternate ways of installing the drivers in a previous post if the KFU's installer doesn't work.

When i setup the vista machine. I told it to run windows by itself, and not share files with OsX, so i assume ill have to check the devic manager, i am at school for 4 more hours so ill try then, im 12 but im not stupid

Ethanzh said:
When i setup the vista machine. I told it to run windows by itself, and not share files with OsX, so i assume ill have to check the devic manager, i am at school for 4 more hours so ill try then, im 12 but im not stupid
Click to expand...
Click to collapse
nobody says you'r stupid - there are a lot much older people having problems with the drivers !
and allthrough i'm a win admin with 30 years of experience sometimes i don't understand what windows is doing ...
so back to your problem - found this post:
http://forum.xda-developers.com/showpost.php?p=24161305&postcount=11
maybe it's helpful for you ...
and you'r right - would check the device manager for the right driver for fastboot mode - it should be "android adb interface" - not the one with "composite" - if everything is right the command "fastboot -i 0x1949 getvar product" should return "kindle"

b63 said:
nobody says you'r stupid - there are a lot much older people having problems with the drivers !
and allthrough i'm a win admin with 30 years of experience sometimes i don't understand what windows is doing ...
so back to your problem - found this post:
http://forum.xda-developers.com/showpost.php?p=24161305&postcount=11
maybe it's helpful for you ...
and you'r right - would check the device manager for the right driver for fastboot mode - it should be "android adb interface" - not the one with "composite" - if everything is right the command "fastboot -i 0x1949 getvar product" should return "kindle"
Click to expand...
Click to collapse
OK, but when I check the device manager, there is no ADB references or such, this may mean I have to uninstall whatever the install_drivers.bat did, and manually install the drivers, and that may have also caused KFU to return '<waiting for device>' when i entered fastboot -i 0x1949 getvar product. So I'm guessing this MUST be done on windows? I sortof need to fix this by Saturday morning, because I am going on a trip without any computer!

I assume i must also download the androidsdk and extract that to C:\? I just dont realize how a computer let alone virtual machine can detect a fastbooted device.

cant bring up bootloader again

Hey guys,
So I'm attempting to root the nexus. I was following the instructions and put it into bootloader mode. I accidentally hit the power button while it said start at the top of the screen and it restarted. Now every time I power off and try to enter bootloarder mode it wont display the android guy. How can I bring that back up?
thanks,
Mike

try adb reboot-bootloader?

opticaldh said:
try adb reboot-bootloader?
Click to expand...
Click to collapse
my phone also isnt getting recognized by my computer now as well

hkdflip2 said:
my phone also isnt getting recognized by my computer now as well
Click to expand...
Click to collapse
try adb devices. If nothing shows up, then I think you should reinstall your driver. I used the Nexus Root Toolkit to install the driver.
After you uninstall the driver and plug in your device again, if Windows keeps installing autimatically the driver, then you should disable the Automatic Driver Update (or something named like that). I used to stuck with this Driver Update for 2 days. After I disable it, uninstall driver, then install again through Device Manager. Everything is OK now.

Cross check if USB debugging is enabled before connecting via adb. I have never used that Start option so don't know what it does apart from booting your phone.
---------- Post added at 04:23 AM ---------- Previous post was at 04:19 AM ----------
I reproduced the actions that got you the bug (selected Start from boot loader screen). But my boot loader still shows up.

Try adb bootloader
sent from my nexus 4; cat on lap, beer in hand

So i figured out most of it, im following the instructions from http://www.youtube.com/watch?v=g88PPZyvfDI however i get to the part about 11 1/2 minutes in where my phone should be rebooting once i put usb debugging on however i put it on and my phone doesn't restart and the nexus toolkit just says waiting for usb debugging to be enabled. Any suggestions

Need help - OP 6t not recognized in fastboot

Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.

Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.

I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.

And just to be certain, do you have USB Debugging enabled in developer options?

Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.

I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.

Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.

lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now

lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com