Develop Bugs

No OS, OTG not recognized. Am I bricked?

Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it

I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.

Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562

Tried it on a full battery, still no luck.

tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here

Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.

Have you tried adb/fastboot?

Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.

-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.

CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.

DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?

Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.

I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1

CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4

The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?

Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1

The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.

Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.

zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.

MTP Not Working Windows 10

I am unable to get Windows to mount my Pixel XL in MTP mode. I have the Pixel's screen turned on and unlocked, and the connection option on the phone's pull down menu is set to transfer files. Windows is able to mount the phone when it is in picture transfer mode, but not in MTP mode.. When I look in Window's device manager I can see that the MTP device is connected but I'm getting a yellow triangle exclamation, as in the driver is no good. I uninstalled the driver and tried letting Windows reinstall to no avail. I have searched the web for MTP drivers for Windows, but I can't really find anything. The specific version of Windows that I am using is Windows 10 Education 64.
The main reason for my concern is that I am about to attempt to apply the new root method that is available, and I wasn't sure if I needed to be connected successfully via MTP before I get the ball rolling with ADB. I do have the ADB drivers installed, along with ADB and fastboot and that seems to be working fine. When I run the command 'adb devices' the console shows that my Pixel XL is connected. I am assuming that I should be good to go on that front, but I still want to know why MTP is not working on Windows, and how I can fix it. Any suggestions would be greatly appreciated.
Here's a screen shot of what Window's device manager is showing me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

norcal61 said:
I am unable to get Windows to mount my Pixel XL in MTP mode.
Click to expand...
Click to collapse
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.

Scott said:
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.
Click to expand...
Click to collapse
I tried that already. I stumbled across it while searching for a solution. The adb and fastboot parts worked well but not the regular mtp drivers. I think maybe the problem has to do with Windows itself.

I had a similar issue with my Pixel C tablet. I don't remember which driver that I had to use but I eventually got it to work. I believe that I ended up needing PDANet to resolve. I am using the same computer for my Google Pixel phone. I have successfully been able to use MTP on my Google Pixel phone and have access to all the files via file explorer.

I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.

plug your phone to your computer then check the notifications,tap on the USB charging this device for other options...just tick the usb to transfer files ....

Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI

defens23 said:
I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.
Click to expand...
Click to collapse
Believe it or not have seen / owned many devices that exhibited this behavior.
Switching back and forth always fixed.

awesome thanks for that video!!
peejayw said:
Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI
Click to expand...
Click to collapse

This was from Microsoft's site, is a little quicker. It would be nice if this got fixed.
(1) Go to C:\Windows\INF
(2) Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
(3) Once you found it, just right click on it and select install. It will take a very few seconds.
(4) Connect your device to the pc.

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
bobby janow said:
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:

i'm running an ASUS MB too...perhaps there are more variables to this equation than we want to believe.

Jammol said:
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:
Click to expand...
Click to collapse
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.

bobby janow said:
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.
Click to expand...
Click to collapse
Windows! Lol.

No more usb access on windows 10

Hi all,
I have a Oneplus 3 with the last update (OxygenOS 5.0.4) and I can't access to my files with an USB cable.
I try on 3 computers with differents cables, and the OTG parameter on ON but nothing works.
Drivers are normally ok.
Do you have a solution?
Best regards,
Jckbrtn

jckbrtn said:
Do you have a solution?
Click to expand...
Click to collapse
Try to turn on usb debugging in developer options

mar.ur said:
Try to turn on usb debugging in developer options
Click to expand...
Click to collapse
Hi,
Thanks but it doesn't work and I never need to do that before.
I don't understand why it doesn't work anymore.
I hadn't try nothing new on my phone.
I think I will try to reset it...
Best regards,
Jckbrtn

@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands

mar.ur said:
@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands
Click to expand...
Click to collapse
I just try to connect my Oneplus with USB cable like I always use to do.
ADB drivers are installed on my PC and I only have the original recovery.
I never try to root this smartphone.
With a OneplusX on LineageOS, no problem. See screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Looking at your photo, have your tried to tap the second option...?

150208 said:
Looking at your photo, have your tried to tap the second option...?
Click to expand...
Click to collapse
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.

jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Oh i see
Try developer options, if i remember it right, i believe there is a setting about USB access in OOS.
Other than that i don't know except factory reset, re-install the PC, or bad usb port (in either of phone/pc).
I have this issue once, but it because my bad usb port on my PC motherboard.

jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.

zelendel said:
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.
Click to expand...
Click to collapse
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....

jckbrtn said:
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....
Click to expand...
Click to collapse
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.

So I try a factory reset: don't work
I downgrade to oxygen 5.0.3 and 5.0.1: don't work
I try on an other laptop where I never plug my oneplus or install drivers/adb: don't work
I also try with different cables (original from oneplus include): don' work
With otg option on, usb debugging on, ... or without, don't work!
And best is I can't install LineageOS as I have no access on my PC

zelendel said:
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.
Click to expand...
Click to collapse
Yes, I think it's hardware. USB-C don't work with OTG adapter (USB-C to USB and USB key).
Log cat? How to?

I just bought an used 3T and have the same problem. I have tried every possible software solution I guess I have to try to replace USB port but if it doesn't help I don't know what I'll do...

I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you

stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
Problem is I don't have this menu anymore since my usbc port is not working

stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.

jckbrtn said:
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.
Click to expand...
Click to collapse
So after 2 weeks of mail contact, my smartphone was sent from Belgium to Poland monday.
I received my repaired smartphone on wednesday.
Technical support very good! Mail support very complicated...

Hardbricked, msmtool gives error 258

hello there guys, im new here and also desperate
unfortunately im struggling revive my beloved op3. i am getting a strange error, cant really seem to find many thing about it. so what happened is i was about to switch profile on the phone when it froze and stuck in bootloop, so i decided since nothing else worked to wipe everything off the phone. so it all went great, it was wiping data for atleast an hour when i decided to plug in to charge just in case, but the cable i used was fauilty so i ended up drained battery. ince then i am not able to recover it unfortunately.
in msm tool, it stucks at downloading chace.img, then afetr a couple of seconds i get an error:
firehose check rsp failed, errno:258
downloading chace.img failed
iam very out of ideas what to do from here. only thing is after this the led glows light green-yellowish
any suggestion?
other thing what i realised:
when it sais hold the volume up button and connect to usb, nothing happens. unless i press volume up+power button. could it be the reason? no matter how long im holding only volume up and connect it to pc, nothing will happen.
thanks for reading,
Tomi
and aslo this is what i get in the log
Device Arrival: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
m_ImageHwId 16: 009470E12A703DB9
m_PhoneHwId 24: 009470E12A703DB9
UFS Inquiry Command Output: SAMSUNG KLUCG4J1CB-B0B1 0800
UFS info Vendor = samsung, TotalLogicalBlocks = 124993536
[7] HANDSET_TYPE_64G:
[7] Downloading rawprogram0 Label: cache FileName: cache.img
Device Remove: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

Maszkos said:
hello there guys, im new here and also desperate
unfortunately im struggling revive my beloved op3. i am getting a strange error, cant really seem to find many thing about it. so what happened is i was about to switch profile on the phone when it froze and stuck in bootloop, so i decided since nothing else worked to wipe everything off the phone. so it all went great, it was wiping data for atleast an hour when i decided to plug in to charge just in case, but the cable i used was fauilty so i ended up drained battery. ince then i am not able to recover it unfortunately.
in msm tool, it stucks at downloading chace.img, then afetr a couple of seconds i get an error:
firehose check rsp failed, errno:258
downloading chace.img failed
iam very out of ideas what to do from here. only thing is after this the led glows light green-yellowish
any suggestion?
other thing what i realised:
when it sais hold the volume up button and connect to usb, nothing happens. unless i press volume up+power button. could it be the reason? no matter how long im holding only volume up and connect it to pc, nothing will happen.
thanks for reading,
Tomi
and aslo this is what i get in the log
Device Arrival: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
m_ImageHwId 16: 009470E12A703DB9
m_PhoneHwId 24: 009470E12A703DB9
UFS Inquiry Command Output: SAMSUNG KLUCG4J1CB-B0B1 0800
UFS info Vendor = samsung, TotalLogicalBlocks = 124993536
[7] HANDSET_TYPE_64G:
[7] Downloading rawprogram0 Label: cache FileName: cache.img
Device Remove: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Click to expand...
Click to collapse
When you hold volume up and connect to the PC, it should be recognised. If not, it is either of two things viz. the required drivers are not installed or the phone is really DEAD. So follow the steps given in the Unbrick Guide scrupulously and check. I have used it and revived my phone successfully.

tnsmani said:
When you hold volume up and connect to the PC, it should be recognised. If not, it is either of two things viz. the required drivers are not installed or the phone is really DEAD. So follow the steps given in the Unbrick Guide scrupulously and check. I have used it and revived my phone successfully.
Click to expand...
Click to collapse
Okay thanks for that. I'll redo everything step by step, and I'll let you know if it worked out which I hope so.
One more question: since I had the phone bricked while restoring it to factory and ran out of battery, can it cause hardware failure? Or any idea what is the meaning of the this 258 error code? I tried to look up on the internet but didn't find anything about it.
Cheers
Tomi

Maszkos said:
Okay thanks for that. I'll redo everything step by step, and I'll let you know if it worked out which I hope so.
One more question: since I had the phone bricked while restoring it to factory and ran out of battery, can it cause hardware failure? Or any idea what is the meaning of the this 258 error code? I tried to look up on the internet but didn't find anything about it.
Cheers
Tomi
Click to expand...
Click to collapse
Did you charge the phone subsequently? Does it take the charge? If the battery is completely dead, the phone may not revive unless the battery gets some charge. You may try to charge it or with another battery if that is available.

tnsmani said:
Did you charge the phone subsequently? Does it take the charge? If the battery is completely dead, the phone may not revive unless the battery gets some charge. You may try to charge it or with another battery if that is available.
Click to expand...
Click to collapse
So I installed a fresh windows today did the whole thing from the a-z but the same issue occurs. I think the battery should be alright never had any problems with it. All I get is this man errno:258 nothing seems to work unfortunately..

Maszkos said:
So I installed a fresh windows today did the whole thing from the a-z but the same issue occurs. I think the battery should be alright never had any problems with it. All I get is this man errno:258 nothing seems to work unfortunately..
Click to expand...
Click to collapse
I hope that you are running a regular Win 10 PC that too Intel (not AMD) and not through VM. Also I hope that you disabled the check for driver signing BEFORE installing the drivers. Your issue seems to be the drivers. May be re-download the drivers. Read the entire page. Use another PC or Laptop and different USB ports especially v2.0 and not v3.0. Repeat until you succeed.

tnsmani said:
I hope that you are running a regular Win 10 PC that too Intel (not AMD) and not through VM. Also I hope that you disabled the check for driver signing BEFORE installing the drivers. Your issue seems to be the drivers. May be re-download the drivers. Read the entire page. Use another PC or Laptop and different USB ports especially v2.0 and not v3.0. Repeat until you succeed.
Click to expand...
Click to collapse
Cool I will, it's a regular win10, signature should be ok, I tried it on 3 different laptops, 2ofthem were older ones but no success. I really hope it is just a driver issue since my problem occured while formatting the phone in bootloader. I'm not sure about the usb ports I'll check that out aswell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll let you know if there's any update!
Ps I get a greenish light after the man tool fails to upload the cache.img
Sometimes it turns orange aswell. Is that a good sign?
Thank you tnsami for your time and effort, really appreciate it

Maszkos said:
Cool I will, it's a regular win10, signature should be ok, I tried it on 3 different laptops, 2ofthem were older ones but no success. I really hope it is just a driver issue since my problem occured while formatting the phone in bootloader. I'm not sure about the usb ports I'll check that out aswell.
View attachment 4716364
I'll let you know if there's any update!
Ps I get a greenish light after the man tool fails to upload the cache.img
Sometimes it turns orange aswell. Is that a good sign?
Thank you tnsami for your time and effort, really appreciate it
Click to expand...
Click to collapse
Did you ever solve it?

Baxter777 said:
Did you ever solve it?
Click to expand...
Click to collapse
Noo not yet unfortunately I was carried away by other things, I am about to look into it now again, might find a solution for it. Any luck over there?

Have you tried another computer

Baxter777 said:
Did you ever solve it?
Click to expand...
Click to collapse
kallum7 said:
Have you tried another computer
Click to expand...
Click to collapse
I did, but they all had usb 3.0 as far as I can remember, so ill try it with usb 2 soon, maybe next week or so. That is my last resort.
I checked the battery it takes the charge, even tough it only had approximately 3volt in it instead of 3.8v would you think a new battery is essential?

What I would do is buy another charging cable and then try and charge it up and then try and unbrick the phone

kallum7 said:
What I would do is buy another charging cable and then try and charge it up and then try and unbrick the phone
Click to expand...
Click to collapse
Yeah, did that too original cable, charger. So is this a communication error between the phone and PC is it?

Try going into the device manager on windows and go to ports and uninstall OnePlus com port drivers and reinstall them

Question ADB not seeing the 9 Pro

Okay, this is getting kind of ridiculous. I cannot get any computer to see the 9 pro via ADB devices.
This is my 4th Oneplus phone I currently own. So I know what I'm doing. All my other phones have bootloaders unlocked and rooted. No issues, until now. I just bought this one. Been waiting for the unlock bin file because it's the T-Mobile variant, but found out that I don't need the bin file to unlock the bootloader, but need ADB to see it !
Fastboot devices will see the phone but not ADB. I even just reformatted my laptop and started from scratch. Followed all of the guides I could find, and I STILL cannot get ADB to see this phone. Why is this phone different ?
Anyways. Anyone have any ideas cause I'm out of them.

Install all the proper drivers. How are you connecting the OnePlus 9 pro to your PC?
Are you using windows or linux?
If you are using linux, I can't help you out.
Enable USB debugging via developer options and go to USB configuration:
Select usb debugging as the default.
When you want to transfer files, select file transfer.

Also, do you have access to another usb cable?

rogerrulez said:
Okay, this is getting kind of ridiculous. I cannot get any computer to see the 9 pro via ADB devices.
This is my 4th Oneplus phone I currently own. So I know what I'm doing. All my other phones have bootloaders unlocked and rooted. No issues, until now. I just bought this one. Been waiting for the unlock bin file because it's the T-Mobile variant, but found out that I don't need the bin file to unlock the bootloader, but need ADB to see it !
Fastboot devices will see the phone but not ADB. I even just reformatted my laptop and started from scratch. Followed all of the guides I could find, and I STILL cannot get ADB to see this phone. Why is this phone different ?
Anyways. Anyone have any ideas cause I'm out of them.
Click to expand...
Click to collapse
Fix: ADB Devices Not Found
With smartphones being present everywhere, the need for transferring files from your personal computer to your smartphone and vice versa arises. Not only
appuals.com

luarpc said:
Fix: ADB Devices Not Found
With smartphones being present everywhere, the need for transferring files from your personal computer to your smartphone and vice versa arises. Not only
appuals.com
Click to expand...
Click to collapse
Hi and thanks for the link. I have tried all of that except the universal drivers which I just installed. No difference. When the phone is booted it shows up as USB composite device. And when I try to update the driver, even after disabling driver verification, it will accept the driver but will show a small yellow icon over the newly installed driver.
In bootloader mode ADB does not see the phone but fastboot does. It looks like this could be a driver issue but the only Oneplus drivers I've found are from 2012.

rogerrulez said:
Hi and thanks for the link. I have tried all of that except the universal drivers which I just installed. No difference. When the phone is booted it shows up as USB composite device. And when I try to update the driver, even after disabling driver verification, it will accept the driver but will show a small yellow icon over the newly installed driver.
In bootloader mode ADB does not see the phone but fastboot does. It looks like this could be a driver issue but the only Oneplus drivers I've found are from 2012.
Click to expand...
Click to collapse
Disable Driver Signature Enforcement in windows - google this
then reinstall oneplus 9 drivers from manufacturer
OnePlus messed up the signature of their drivers for the Oneplus 9 pro and windows doesn't install it properly.

immortalwon said:
Disable Driver Signature Enforcement in windows - google this
then reinstall oneplus 9 drivers from manufacturer
OnePlus messed up the signature of their drivers for the Oneplus 9 pro and windows doesn't install it properly.
Click to expand...
Click to collapse
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks

rogerrulez said:
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks
Click to expand...
Click to collapse
Hi,
Try this drivers.
OnePlus USB Drivers | Official
Download the latest version of OnePlus USB Driver for your OnePlus smartphone. OnePlus USB Drivers helps your OnePlus smartphone to communicate properly with your computer.
oneplususbdrivers.com

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rogerrulez said:
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks
Click to expand...
Click to collapse
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.

immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb connector port.
Click to expand...
Click to collapse
I have always used a regular USB a to c charge/sync cable. No USB c port on laptop.

immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
It's connected with a USB A - C cable. In device manager it says kedacom USB device. After installing the drivers from the link @TheGhost1951 sent me. It now set itself up as a Universal Serial Bus Device - ADB interface.
In bootloader mode it shows up in device manager with whatever driver I had chosen from before. ADB still can't see the device on either my desktop or newly formatted laptop.
So a pic of the device manager will show basically that. Whatever driver I have chosen. But any driver I chose, ADB still won't find the phone. Regardless what I do on either computer.

luarpc said:
Hi,
Try this drivers.
OnePlus USB Drivers | Official
Download the latest version of OnePlus USB Driver for your OnePlus smartphone. OnePlus USB Drivers helps your OnePlus smartphone to communicate properly with your computer.
oneplususbdrivers.com
Click to expand...
Click to collapse
Thanks for the link. That was perfect. I had seen that website during a search yesterday, but I didn't think at the time if it was real and could be trusted.

TheGhost1951 said:
I have always used a regular USB a to c charge/sync cable. No USB c port on laptop.
Click to expand...
Click to collapse
And that's what I'm using. I've tried 3 different cables. Even just opened a brand new one. A quality cable.

immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
Oh. And after installing the new drivers. When the phone is booted ADB can see the phone. But not in bootloader mode. Or down mode.

rogerrulez said:
Oh. And after installing the new drivers. When the phone is booted ADB can see the phone. But not in bootloader mode. Or down mode.
Click to expand...
Click to collapse
I don't have any free slots for an additional card in my computer. But is that what it's needing you think ?

rogerrulez said:
I don't have any free slots for an additional card in my computer. But is that what it's needing you think ?
Click to expand...
Click to collapse
Nah, it is a matter of getting the right cable and drivers....it has never been that completed for me even with a Qualcomm crashdump!

TheGhost1951 said:
Nah, it is a matter of getting the right cable and drivers....it has never been that completed for me even with a Qualcomm crashdump!
Click to expand...
Click to collapse
Can you tell me what should be the proper name of the driver that should be installed ?
And do you think that this might be a hardware issue ?
Also, I've noticed that debugging is randomly getting turned off.

rogerrulez said:
Can you tell me what should be the proper name of the driver that should be installed ?
And do you think that this might be a hardware issue ?
Also, I've noticed that debugging is randomly getting turned off.
Click to expand...
Click to collapse
If driver is correct, your device should show up in device manager on PC as a port with description as 9008.....ex:Qualcomm USB hub 9008 or something similar. Google latest Qualcomm USB drivers... Make sure driver signing is turned off on PC, there should be a watermark in bottom right hand corner stating test mode. One the correct drivers are installed, reboot PC and then you are ready to start the MSM tool process.

immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
It's connected with a USB A - C cable.
TheGhost1951 said:
If driver is correct, your device should show up in device manager on PC as a port with description as 9008.....ex:Qualcomm USB hub 9008 or something similar. Google latest Qualcomm USB drivers... Make sure driver signing is turned off on PC, there should be a watermark in bottom right hand corner stating test mode. One the correct drivers are installed, reboot PC and then you are ready to start the MSM tool process.
Click to expand...
Click to collapse
Okay thanks for that info. But I have yet to see that qualcomm port yet on either of my computers. No matter what I do it doesn't seem to change anything. Certainly nothing near having a qualcomm port in device manager.
I would be willing to completely reformat my laptop and install the recommended drivers from this post if I knew it would definitely work.
But I'm starting to think at this point that this might be a hardware issue.