Database Users

N1 Windows Drivers problems

Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you

http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/Posted Yesterday, 10:17 PM
ATT N1's can run CyanogenMod without any real trouble. The commands and guides remain the same as the Tmo N1
THE ONLY CAVEAT IS: YOU CANNOT USE CM 5.0.5.1 or 5.0.5.2 as your initial install base, as these releases were bugged. Use 5.0.5 here
For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Setup ADB/FASTBOOT
Fastboot oem unlock
fastboot flash recovery recovery-ra-blah-blah.img
Reboot into recovery
NANDROID
WIPE!!!! (if you dont wipe you get boot loops)
Flash CM
Flash Google (optional)
Reboot
Fastboot flash radio radio.img (unnecessary on ATT n1's)

cheloman said:
Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
Try those drivers.

jerrycycle said:
...For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Click to expand...
Click to collapse
jerrycycle said:
fastboot flash recovery recovery-ra-blah-blah.img
Click to expand...
Click to collapse
Thank you by your post, it was very usefull and I could change my drivers, so I have access in debug mode to my n1. Even with this, Ive tried to apply the root with modaco´s files, using the original ERE27 pack, but, it just stucks in "copying...".
Maybe the problem is that I was instructed about I should execute the .bat, in bootloader moder (no in fastboot). I have the adb commands with fastboot mode, but, when I do: fastboot devices in bootloader mode, I dont have any device. Maybe the tutorial that I followed its wrong and should I execute directly in fastboot not in bootloader.
Anyway, Ive quoted your post, because when you say that isnt necessary, the instructions of recovery installation, says about its a "pre-requirement"
You can check it in /showthread.php?t=611829 As new user, i cant put the link to the thread of RA recovery, sorry
I dont want to mess with this, because the consequence of bad procedure.
Thank you by your help and patience.

you might want to make sure you're using the main USB ports, not those extension ones or those that are built into PC cases. I used to have the problem with "unrecognised device" because of that.

Soft brick? (No ROM installed but can sort of boot into recovery)

howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7

Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!

demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.

fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones

I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?

You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed

I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.

Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand

Oneplus 2 Bricked, Help!

Hi!, I have a bricked Oneplus 2 so heres how it happened
My device was running oxygen os 3.0 with TWRP 3.0 and I decided to flash the resurrection remix ROM on my phone through twrp, and when I did flash it I think it gave me some error code, and then I rebooted my phone and now its stuck in a bootloop with no OS installed.
I tried going to TWRP and adb was not working and adb side load was not working, I went to fastboot and my computer wont detect my device through fastboot. I tried first aid kit and my phone was not being detected. I did try this with using 2 other computers running windows 10 and I tried it with a computer running Linux Mint. How ever when I check in Device Manager It shows "communications port (COM1) I tried updating that driver with the Oneplus 2 Qualcom drivers and it gave me a error code 10 and I tried installing an ADB interface driver to that to and I got the same error code 10. I also tried this method below with no luck.
"https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/"
Please help me and the community facing this problem, Thanks!

I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini

SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution

SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
And does your phone get recognized by fast boot? because you were saying that you used first aid to get recovery, and first aid uses fastboot, because you will beable to fix your phone through fastboot

yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom

SirMika said:
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
Click to expand...
Click to collapse
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot

fahad999 said:
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
Click to expand...
Click to collapse
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.

SirMika said:
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
Click to expand...
Click to collapse
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot

fahad999 said:
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
Click to expand...
Click to collapse
not sure but i did similar procedure yesterday. see second post http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 but i had no idea what i suppose to do..all i had was stock recovery..
in adb, running command fastboot device it shows my phone

Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
it seems there is no way to fix it..my skills and knoledge aint high, but i´v done all by the book and nothing. it also goes in fastboot and twrp but thats it. i wish i could help you but were in a same boat

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Danm, that sucks. Later I may try using a virtual machine of Linux Mint on my computer and see if it will detect my phone in fastboot. And the sad thing is that this oneplus 2 is my only phone

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10

fahad999 said:
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
Click to expand...
Click to collapse
I think i need to get in my hands PC with Win7. i also came that conclusion the problem is Windows.
Oneplus drivers (/D) just keep pop-upping asking what todo, when selected nothing happens
EDIT: is it possible install proper softwares via USBstorage?

Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files

Getsuga Tenshou said:
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Click to expand...
Click to collapse
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg

fahad999 said:
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
Click to expand...
Click to collapse
Update! I know why our phones are bricked! when we installed custom roms you wiped the phone right. I was reading that there was a new feature in android in which you wipe the phone with a password, the bootloader gets locked. So I believe that our devices now have a locked bootloader

fahad999 said:
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
Click to expand...
Click to collapse
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)

Guihardrock said:
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Click to expand...
Click to collapse
Sorry to say that this is not working for me and I have no OS installed, I formatted data in twrp and typed yes and still I got no luck. My device is not being recognized by pc in twrp, I installed many drivers (Oneplus Drivers, Google USB Drivers, 15 Sec ADB & Fastboot Drivers, Universal ADB Drivers) Still I got no luck, and nothing shows up in device manager, I tried this in 2 Computers awwell.

i have unlocked bootloader, latest TWRP but no OS. instead zip fils it should be image. adb cant find phone but fast boot does

[HELP]Device not detecting in fastboot mode

I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.

Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?

echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device

Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..

Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine

Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..

____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked

Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?

____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.

Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..

____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.

Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though

echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.

MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help

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