Database Info

mtty does not see USB port when in bootloader mode

I am stuck in bootloader mode after trying to update to tomal mobile 6.
The screen on Imate jasjar says USB at the top and V 1.01 at the bottom.
The mobile device center does not allow USB since I checked it off.
When I execute MTTY1.42 usb is not given as an option.
When I execute MTTY 0.01 I get USB as an option However when I click on it I get the message "USB port cannot open"
By the way my screen says serial originally and then USB when I connect to my usb port.
I assume that if my screen says either serial or usb that it is in boot loader mode.
This is the second time that I had this problem after trying to update using Ranju's mobile 6 upgrade.
However the first time I was able to recover by starting with the MTTY 1.42 execution

Mobile device center suggests Vista. Most people would not dare these things without using XP. Suggest you do the same and disable activesync USB connection option before using MTTY

that is my next move. Go tto a computer with XP. although I was able to execute MTTY before this on my 64 bit vista computer.
Both my home computers run Vista 32 or 64.
Could there be a physical connection problem with my USB even if serial changes to USB when I plug my device into the USB port?
It is like I have apart USB connection but not complete. Or is there a software problem in the device with the part that handles the USB port? If so is there a way out?

If your device changes from serial to usb then you can start the upgrade... 8.5 seems to be the best so for with my experience..

Are you aware that I have a non background lit screen? That the device charge light does not come on? That it does not respond to soft reset?
It only reacts to hard reset and to the insertion of the USB cable?
When I try to run MTTY which I thought that I was supposed to to clear something I get the message that it cannot find a USB port.
Given this state can I do the upgrade that you suggested? or are you assuming that my imate jasjar is fully functioning

what do you mean by .......8.5 upgrade

Okay thats sounds good so far, i have been researching about that problem you have. when the serial changes to USB thats good, it means you are ready to run the update just ignore the recognition of the usb pop up message. did you down load the 8,5 Tomal's? if so run it i will do the same this side, i have been testing the 8.71 it tereble do not use it Tomal must try to put some time on it because he forgot some of impotant features. if the device shows usb then no need for MTTY. you just run the update rom. let us know what happens. Its normal that the back light is of just upgrade. Here is the link for the 8.5 upgrade screen shots; http://forum.xda-developers.com/showthread.php?t=454906 The download link; http://vidmes.com/xda/Uni/ROMs/Tomal...WM61_20764.exe

Looks like the download link will not work just scroll down on this link and download the special build rom. (window Mobile 6.1 V8.5 Tomal) http://forum.xda-developers.com/showthread.php?t=454906

Is your memory card slot in use? Remove memory card prior to using mtty or boot loader mode.

Yes the storage card is out
the sim card is out
the device is connected to the pc
the screen on the device shows USB
I run tomal version 8.5
I get the message
error CEROM update error
then I follow the recovery instructions
on recovery I get
RUU has stopped working
eroor 101 connection error
note
someone says
"U must remove the Memory card b4 upgrade, (Very impotant)"
Does that make sense
My problems started with
I had the crossbow Mobile on the system before.
I did a system restore
then tried install tomal 8.5
and from there things went off the cliff
I am now going to try things on a XP loaded computer as a last resort

swiching to my office computer and with active sync I was able to install TOML 8.5
Problem was with vista apparently

Mtty Help me Please..
Guys,
Please help me, every time I try to use mtty, it always like this attachment. What should I do, I allready follow the instruction, but still the same.

I would try on an XP computer

I did it on XP computer.
orb3000 said:
I would try on an XP computer
Click to expand...
Click to collapse

make sure your usb port in uni is not brocken. is active sync can running well?
have you un-check "allow usb connection" in connection setting before running mtty?

When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
indrastrid said:
make sure your usb port in uni is not brocken. is active sync can running well?
have you un-check "allow usb connection" in connection setting before running mtty?
Click to expand...
Click to collapse

irmanpribadi said:
When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
Click to expand...
Click to collapse
Now, there are only two things...
1. USB Sync driver in your PC is not functioning correctly
2. You have physical problem in USB port at your device
just my two cents.

irmanpribadi said:
When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
Click to expand...
Click to collapse
set your uni in bootloader i.e. press power button + backlight and reset using your stylus.
make sure you have disabled USB connections in AS
my two cents

Windows Mobile Device Center doesn't sync

So i got this error with a big "X" inside this red circle and next to it just says the word "Error" then nothing else when i tried sync using WMDC thats what happens. Btw im using a HTC Touch Pro and i tried plenty of solution from the Microsoft website this includes the following:
-Uninstalling the device driver and reconnect the device
-Disabling Advance Network Functionality
-Disabling firewall, antivirus software etc.
-Running WMDC on compatability mode
-Soft resetting device
-Hard resetting device
-Flashing a new ROM
Thanks in advance
[email protected]

[email protected] said:
So i got this error with a big "X" inside this red circle and next to it just says the word "Error" then nothing else when i tried sync using WMDC thats what happens. Btw im using a HTC Touch Pro and i tried plenty of solution from the Microsoft website this includes the following:
-Uninstalling the device driver and reconnect the device
-Disabling Advance Network Functionality
-Disabling firewall, antivirus software etc.
-Running WMDC on compatability mode
-Soft resetting device
-Hard resetting device
-Flashing a new ROM
Thanks in advance
[email protected]
Click to expand...
Click to collapse
what os?
try a new cable, or try plugging the cable into a different usb port.

i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way

wishmaster86 said:
i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way
Click to expand...
Click to collapse
You could just update to the latest HTC ROM from the official website if your phone is still under warranty, btw thats what i did but it didn't help. Note, that i'm running Windows 7 as my OS if anyone want to know this information to help solve the problem. Thanks in advance.
[email protected]

wishmaster86 said:
i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way
Click to expand...
Click to collapse
Settings-->Connections-->USB to PC and Uncheck Enable faster data Synchronization

I have the same problem.
in my situation i tried to recover usb-flash and flash a nokia phone. For both things programs installed their own drivers. Even after I deinstalled the software I probably still have their drivers on my pc. That's why I can't sync my phone...
is there a tool to manage installed drivers?
or the other way out is to reinstall windows 7

anyone willing to help?

This solution worked for me:
Thanks to Scubamike
copy and paste from
http://social.microsoft.com/Forums/...c/thread/7a6516e2-9a46-4e1f-b689-1aa7dc2bda64
I found a different solution that worked for me: On my phone I clicked start/programs/active sync/options and deleted all the old PC connections that were displayed. In fact, you could probably just delete ALL the PC connections displayed and start from scratch. You'll just have set up another sync partnership in WMDC when you plug it in. Let me know if this helps.

it is to easy! should work ALWAYS:
Make sure "Advanced network functionality" is switched off in the USB to PC settings then:
go to activesync, menu, connections, disable "connect via USB" off, press "ok" go back to connections, enable "connect via usb" press "ok" unplug and replug your cable. and all works.
greetings

i had trouble with a 6.5.3 rom i just cooked. had to uninstall, reboot, reinstall wmdc, then i synced okay.

I have the last original rom and win 7 and with removing all remembered connections on the pda, it connected immidiatly. Thank you for the help

i have been all over the microsoft forums to no avail. i recently updated my laptop to win7, and have a fuze running 6.1 mobile. when i connect my fuze to the laptop the laptop recognizes it as it begins to charge, but then nothing. i try to open win mobile device center and this is the error message i get C:\windows\system32\rapistub.dll is either not designed to run on windows or it contains errors. I have uninstalled and reinstalled 3 times and also tried different usb ports on my laptop. If anyone can help that would be awesome

[Q] SK4G not being recognized on PC

I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.

What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.

Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA

Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.

I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.

I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.

More info request.
Can you provide us with the names and links to the drivers you have tried?

DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.

Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.

DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.

Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.

Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?

Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...

Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?

DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.

[Solved] USB suddenly stopped working

I have a Nexus 5 that I have had about a month now and I had the USB on it working before about a week ago. I plugged it in today and neither my desktop or laptop could recognize it anymore. Both computers are running Windows 8.1.1 and the issues seems to be new as I can neither get USB storage or ADB to find it. The closest I can get it to working is to switch the USB mode to PTP and it reads that but I don't want to pull photos off. When I have it in MTP, it makes the sound of it plugging in and my phone shows it is plugged into a computer but Explorer shows nothing and it says it is working normally in device manager. I've tried everything from enabling and disabling debugging, restarted both my phone and computer tried reinstalling the drivers (both by the computer automatically finding them and manually installing them) but nothing seems to work. Is it possible that Windows Update could of broke the drivers since my computer installed updates yesterday? I also have Linux on my laptop and it appears to read fine with Linux.

That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
OK thanks. I'll give it a try because it was showing up as ACER ADB Device under device manager
EDIT: I updated the drivers and used the USB composit drivers instead and it got MTP working again. When I set it to USB composit, it installed Google's ADB drivers and the Nexus 5's USB drivers so everything is working again. Thanks for your help

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
I can´t manually update driver because of this:

when i update the acer adb it says the driver is up to date and everything is all same. what to do?

Thanks! Thought I was going to go crazy. Worked for me...

i set the driver to MTP as mentioned above and the phone started to show up on the explorer but now i couldnt copy any files from my laptop to the
phone. It displays like that and if clicked yes then the copy wouldnt happen.what is the problem.

Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.

wangdaning said:
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
Click to expand...
Click to collapse
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.

Big tree said:
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Click to expand...
Click to collapse
That msg comes when you're in PTP mode I think...Only certain formats are supported.
Check under storage, expansion menu and make sure you are set to the first option...not PTP.
Above guy mentioned to have phone in USB debugging mode when setting up drivers.

If the device is showing then you need to point to the drivers for it (download them from google). I reinstalled windows a few days ago and had the acer issue (device first shows up in device manager as nexus 5 then switches to acer), windows wants it to be an acer device. Stop windows and then install the correct drivers,
For me I had to click the auto install in windows tray and tell it to stop. After a few times it worked.

No I'm connecting in MTP mode. Ahh its gettn irritating.

Question Phone not detected by PC

A couple days ago my mobile data just stopped working. I had a couple updates I had been ignoring because it would remove the root. I finally gave in and ran the updates. Data returned. Root gone. I connected to my home computer to begin the root process, but my phone would not be recognized by the PC and would not show anything related except that it was charging. It's a new cable, barely used. I tried on my work computer with a different cable and still nothing except "charging". To the best of my knowledge, it connected to my computer just fine prior to the updates.
I've checked Developer Options for anything that says "USB". Toggled USB debugging, revoked authorizations, etc. "Select USB Configuration" is a weird one, all I have are: "Charging", "MTP", "PTP", RNDIS (USB Eathernet)", and "MIDI". But in "Default USB Configuration" I have: "No data transfer", "File transfer / Android Auto", "MIDI", "PTP", "USB tethering". I've selected every option, but (again) no reaction from my phone or PC.
My final options are wipe and reset, or take it to a store; I'm wanting to avoid both of these if possible. Does anyone have an idea of what else I can try?

Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?

IamTheBRAVE said:
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
Click to expand...
Click to collapse
I'll take a look at that tonight.
To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.

The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.

IamTheBRAVE said:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
Click to expand...
Click to collapse
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.
Both are Win10

In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?

IamTheBRAVE said:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
Click to expand...
Click to collapse
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.

Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.

Short version: Nothing worked.
I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.
I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?
I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".
I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.

Have you tried clearing out the dust bunny's in the usb port on phone?

Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com

MrSteelX said:
Have you tried clearing out the dust bunny's in the usb port on phone?
Click to expand...
Click to collapse
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.

IamTheBRAVE said:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
Click to expand...
Click to collapse
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds

tconn said:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
Click to expand...
Click to collapse
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.
10.26 MB file on MEGA
mega.nz
You can use this thread as tutorial for root (you don't need all parts of it)
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.
So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.
So try different ports, different computers, something different.
The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).
Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/
Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.
Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.
So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.
Code:
[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"
Good luck.

Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!

tconn said:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
Click to expand...
Click to collapse
Try using a toothpick. Just try not to bend port too much.