Database Info

[Help] Several problems with my N5

Solved,
if your story sounds similar to mine(Go to TL;DR) Refer to post 4
ok, where to begin
my N5 was A-OK just 3 days ago running the Dev Preview of Lollipop. by A-OK i mean that it worked but with a few
bugs
(its the dev preview i know, its got bugs) like when i stayed on an app, e.g spotify, and exited to the home screen it
would take like 15 sec for all the apps on the home screen (like 6) to appear. There is not where the problem lies.
Again 3 days ago. i poked around both ROM sections to find a Lollipop based on that was to my liking, found one and
directly downloaded it to my phone (in hindsite it would of been better to do it on my comp) and being no stranger
to flashing ROMs i went on auto-pilot adn begun the wiping of cache and factory resetting, setting up for the move to
more stable ROM. When it was time to flash the ROM I completely downloaded was no where to be found, a bit
panicked i went to a backup i had on the device, it did its thing and i booted it up but it went back to Clockworkmod
recovery screen That's problem No. 1 . I rebooted it still the same thing. Scouring through
the web for help on setting ADB to sideload the ROM. The thing is that when i hooked up my phone to my desktop
it didn't recognize the device, The correct drivers are installed but it doesn't recognize the device its labeled as
unknown USB device. That's problem No. 2
*update i plugged in my N5 and the comp read it as a N5 but when i selected the option to sideload it it doesn't
recognize it anymore
and problem No. 3 is USB debugging might be turned off
TL;DR? 1. Boots into Clockworkmod
2. my computers don't recognize the device
3. USB debugging might be off
-Q: Can USB Debugging be enabled some other way.
Any help is appreciated
why is it double spaced? i find it a bit eye-straining reading that much all bunched together

Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.

Lokke9191 said:
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Click to expand...
Click to collapse
ok, used a different cable and it now recognizes it.
tried fastboot devices and nothing
tried ADB devices and numbers appeared and what state the device is in, recovery.
thank you thank you thank you sooo much

all is good
My Nexus 5 is alive,
i tried to upgrade to 5.0 directly and kept getting errors e.g archive does not have boot.sig/ system.sig. That lead me to look up Boot.sig/System.sig, that lead me to a blog saying i could fix the problem if i added something to the directory, forgot how to get to environmental variables, i went and watched the vid that helped my set up adb/sdk and thats when it clicked..
What if i tried flash-all with KitKat and voila it started running the process of flashing. Since it was basically a new phone unrooted and everything it had the system update to lollipop.

Lost TWRP and ADB/Fastboot can't see phone to sideload. What can I do?

Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac

rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk

sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.

rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs

sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.

Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."

Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.

USB not working after flashing Lineage OS 15.1

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.

Phone unrecognized in download/recovery

So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.

chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.

While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.

Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.

bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.

Updated to KB2005_11.c.11 and now USB Debugging malfunctions

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.