Database Info

Manually turn on USB debugging on Nexus 5?

Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)

USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk

rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?

Y is it non bootable?
Sent from my Android 5.0 Nexus 5

You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.

Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.

So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?

[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.

ADB will not recognize my 2015 moto e 4G LTE

I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?

BillyMumphry said:
I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?
Click to expand...
Click to collapse
Ha ha! As soon as I submitted this, I got a notification of a software update to Marshmallow!
The irony...lets hope this irons out the wrinkles.

SOLVED!!!
Well, the OTA update to Android 6 didn't solve my problem, it was my relentless sifting through post after post on XDA and just all over the Internet in general. For anyone else facing this problem here is how mine was solved:
My attempts at unlocking the bootloader were these: I installed everything that I could find on the internet. I installed Android Studio, SDK, all kinds of different drivers, minimal ADB and Fastboot, but nothing seemed to really work. When I plugged my phone into the computer neither ADB nor Fastboot would recognize the device.
USB debugging was ON, OEM was enabled, and for some reason I had MTP set. So after hours of sifting through bug reports generated by a terminal emulator APP, and going over post after post I finally found something useful.
Before I tried it though I wanted to start fresh. So I uninstalled everything from my PC and only download 2 things. Minimal ADB and Fastboot, (found here: http://forum.xda-developers.com/showthread.php?t=2317790, and the official Motorola Device Manager (found here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481.
But the thing that really did it was something I read here on XDA . It was this: switch MTP to PTP! And it was just that simple. Everything else was set the same, USB DEBUGGING ON, OEM ENABLED, and PTP SELECTED. I didn't even boot the device into Fastboot to begin as is instructed, I just started with my phone on and plugged in to my PC as I was just finishing transferring some photos. So I opened ADB/Fastboot, typed in "$ fastboot oem get_unlock_data" and bingo!
Here are the instructions I followed on how to unlock the bootloader: http://freeandroidroot.com/how-to-unlock-bootloader-and-root-motorola-moto-e/
So thank-you XDA forum, you are an invaluable and inexhaustible resource! :thumbup::thumbup::thumbup:
~This thread can now be closed~

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.

Botched Graphene install on Pixel 3A - need help restoring default settings

Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.

Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.

Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.

Ignore

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go

Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?

Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.