I have a KB2005 that was working normally and communicating with my Windows computer when on the A11 version of OxygenOS. It was unrooted and had only the stock applications that came with the operating system. Today I installed the A12 upgrade using the Full-OTA that I downloaded from the OnePlus website (international version). I enabled USB debugging but even so, when I now connect the phone to my computer I don't get the usual message asking if I give permission for ADB. That is, "Allow USB Debugging? This computer's RSA Key Fingerprint is such and such etc. Always Allow from this computer?"
Also, in the Windows Device Manager, the device doesn't show up until I put it into bootloader mode (I have to use the volume + power because ADB commands have no effect). Having run out of solutions, I allowed the phone to install an incremental upgrade to KB2005_11_C33 but that didn't fix the problem. I toggled USB debugging off and on, re-started several times and did a factory reset but still can't use ADB commands. Fastboot commands seem to be working as expected, though. My other KB2005 that is still on A11 is not having this problem with ADB. Any idea what is the source of the problem?
I have never had that problem, so I can't tell you how to fix it.
You might want to try:
- Changing Settings>System settings>Developer options> Default USB configuration and Select USB configuration
- Settings>System settings>Back up and reset>Reset phone: either Reset all settings or Erase all data (backup your data to a PC before doing this)
When I first installed OOS 12 I had a number of problems that all went away after doing a factory reset.
Thank you, Bill. I was most curious to hear from you because I recall you mentioning you had upgraded to A12 and stayed with the stock OS so obviously it was working out for you. I tried both of those things you suggested. I was most hopeful about the factory reset but no luck. I also restarted my PC and re-installed the OnePlus drivers. That said, I haven't noticed a lot people complaining about this so maybe I'll just roll it back to A11, relock the boot loader and take another stab at it.
UPDATE: USB debugging still wasn't working after the roll-back to A11 so I toggled off USB debugging, revoked previous debugging authorizations, deleted the windows drivers, then re-installed them from the copy that is stored on the phone. After that, I toggled on USB debugging and it worked normally again. That's a clue. I'll re-try the A12 upgrade this weekend and report if it works on a 2nd attempt.
I hope it works for you now.
I restarted from scratch and this time the upgrade to A12 worked and I didn't lose the USB Debugging functionality. After installing the full-OTA for my KB2005 (version 11.c.11), I went ahead updated the firmware to KB2003_11.c.33 so I could use TWRP. Everything seems to be working as intended now. I'm happy to report that the rollback app from OnePlus worked flawlessly.
Related
Hi all, a couple nights ago I flashed Lineage 15.1-20180806 to my OPO and everything went smooth. This morning I tried to connect it to my pc to transfer some pics and to my surprise the PC doesn't recognize it.
It looks like the PC is "trying" to establish a connection because the led in the phone blinks really fast for some small periods of time. The phone isn't charging when connected to the PC either.
What I have already tried:
- I already enable USB debugging in developer options
- Set MTP as default usb configuration
- Tried 2 different cables and different usb ports in PC.
I will try again in another computer when I get home but, honestly, this doesn't seem to be a problem with my PC or the cable as those were the ones I used when I flashed the rom and I also used the same cable when I transferred files to the same PC in the past. The phone was running Lineage OS 13 before the flash I think.
Any idea what else can I try to get it to work? I'm afraid I will be attached to this rom forever since I won't have a way to flash another ROM right?
EDIT:
If I go into recovery mode (TWRP) and plug the usb cable the PC recognizes it and I can transfer my files. So I'm 100% sure this is on Lineage OS. Again, when I get home I will see if ADB works while in TWRP but still would like to know if any of you guys has had this issue solved.
Thanks!
do you have anything important on your oneplus one
kallum7 said:
do you have anything important on your oneplus one
Click to expand...
Click to collapse
Nothing so far. It will become a back up phone soon.
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
kallum7 said:
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
Click to expand...
Click to collapse
Thank you, will give it a try and report back later.
adrek09 said:
Thank you, will give it a try and report back later.
Click to expand...
Click to collapse
okay
Is Lineage OS 15.1 supporting VoLTE by any way.
Had the same issue... and had this issue always coming back, currently with LOS18 (some devices worked, others didnt - couldnt see a pattern).
I tried all the triggers like setting File Transfer, disabling USB Debugging - nothing worked...
...until I rebooted my device (a YT703L).
In the end, it should be either (not sure which one actually)
File Transfer - always on (in DevSettings Default USB) or
USB Debugging off (also Dev Settings)
AND reboot.
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.
As the title implies, I'm trying to flash Android 11 to my brother's Pixel 3 because he didn't like Android 12. I've trying manually doing it with the ADB tools and with Google's browser flashing thing. The phone has USB debugging and OEM unlock on as well as the USB behavior set to File transfer as default.
It gets recognized fine at first and is able to reboot into the bootloader using command prompt and whatever Google's website does but once it is there, the phone changes the USB behavior. I hear the little sound that Windows 10 makes when you plug in and remove something and the phone is no longer present in Device Manager. Google's website also has me reselect the phone because it gets disconnected but it is no longer there to be selected. Tried doing it with my own Pixel only with the ADB tools and the same happens. Once it is in the bootloader it is not recognized. Any ideas on how I fix this?
elonmosque said:
As the title implies, I'm trying to flash Android 11 to my brother's Pixel 3 because he didn't like Android 12. I've trying manually doing it with the ADB tools and with Google's browser flashing thing. The phone has USB debugging and OEM unlock on as well as the USB behavior set to File transfer as default.
It gets recognized fine at first and is able to reboot into the bootloader using command prompt and whatever Google's website does but once it is there, the phone changes the USB behavior. I hear the little sound that Windows 10 makes when you plug in and remove something and the phone is no longer present in Device Manager. Google's website also has me reselect the phone because it gets disconnected but it is no longer there to be selected. Tried doing it with my own Pixel only with the ADB tools and the same happens. Once it is in the bootloader it is not recognized. Any ideas on how I fix this?
Click to expand...
Click to collapse
Not sure this will help you, but why not do the firmware transfer via fastboot? All the directions are there with the firmware, you do have to unlock the bootloader, but can relock just after.
I haven't actually done this procedure going from 12 to 11. But have used it to go up, and also to go from lineage back to stock firmware.
cheers, good luck.
Hi! I've been struggling for weeks now and haven't been able to solve this issue so here it goes
Been Using this ROM since release
[ROM][12.1][OOS Cam][OnePlus 8] Project-Zephyrus [12.1_r8]
Project-Zephyrus for OnePlus 8 [instantnoodle] What is this? Project-Zephyrus - Minimal Android Fork Focused on Design and Performance! Fast and Smooth: Project-Zephyrus is more smooth (i.e. less jank) and responds faster than stock. Clean UI...
forum.xda-developers.com
everything was working totally fine until one day suddenly USB data transfer stopped working, I get NOTHING from my pc
-The phone starts charging but I get nothing else, no notification to select default USB behavior
-No sound from pc
-Nothing happens in device manager
-USB options inside developers options on the phone all greyed out
-Uninstalled and Installed Official Oneplus drivers multiple times, as well as every official android/google usb and adb fastboot drivers download I could find
-Was using W10, even did a complete clean install of W11, still nothing, my pc recognizes every other USB device but not my phone.
-ADB and Fastboot commands return nothing "adb devices" and "fastboot devices" I get no response
-Tried with USB debugging on and off multiple times.
-Can't switch to another rom since I cant even sideload anything cause the pc won't "see" my device
-Tried every USB port I have, nothing, tried 2 different laptops I have beside my desktop, still nothing.
I have no clue what else to try, don't want to reset the phone to factory setting since theres lots of stuff to back up, can't even do a titanium backup and get it off the phone beause of the sameUSB issue.
any help? thanks
Cleaning my USB port did it for me...
cjvzla said:
Hi! I've been struggling for weeks now and haven't been able to solve this issue so here it goes
Been Using this ROM since release
[ROM][12.1][OOS Cam][OnePlus 8] Project-Zephyrus [12.1_r8]
Project-Zephyrus for OnePlus 8 [instantnoodle] What is this? Project-Zephyrus - Minimal Android Fork Focused on Design and Performance! Fast and Smooth: Project-Zephyrus is more smooth (i.e. less jank) and responds faster than stock. Clean UI...
forum.xda-developers.com
everything was working totally fine until one day suddenly USB data transfer stopped working, I get NOTHING from my pc
-The phone starts charging but I get nothing else, no notification to select default USB behavior
-No sound from pc
-Nothing happens in device manager
-USB options inside developers options on the phone all greyed out
-Uninstalled and Installed Official Oneplus drivers multiple times, as well as every official android/google usb and adb fastboot drivers download I could find
-Was using W10, even did a complete clean install of W11, still nothing, my pc recognizes every other USB device but not my phone.
-ADB and Fastboot commands return nothing "adb devices" and "fastboot devices" I get no response
-Tried with USB debugging on and off multiple times.
-Can't switch to another rom since I cant even sideload anything cause the pc won't "see" my device
-Tried every USB port I have, nothing, tried 2 different laptops I have beside my desktop, still nothing.
I have no clue what else to try, don't want to reset the phone to factory setting since theres lots of stuff to back up, can't even do a titanium backup and get it off the phone beause of the sameUSB issue.
any help? thanks
Click to expand...
Click to collapse
The build you're on may have broken/missing usb hal
AnierinB said:
The build you're on may have broken/missing usb hal
Click to expand...
Click to collapse
it worked fine for months! and suddenly stopped. telegram group doesn't help much and I found out support for OP8 was dropped so...
Hi everyone
I was just trying to get a banking app to work and turned off developer settings as it seemed to be detecting that, this worked brilliantly except that I needed to restart after making a change to the phone and I had completely forgot to turn it back on and now it's on a bootloop. Windows in device manager does detect it "Android bootloader interface" but ADB doesn't detect it when in the bootloader.
When I did have usb debugging on it was detecting the phone at this stage perfectly and nothing else has changed so I know that the ADB drivers and the cable are working, unless theres been an update since I last installed it around a year and a half ago which would fiix this.
The bootloader is also unlocked too.
Would doing a factory reset help from within the bootloader help at all?
I'm not sure how to fix this and any help would be very much appreciated.
EDIT: Fixed, I could still flash the RAW file.