Database Info

I forgot to enable usb debugging before flashing

Hey guys I really hope you can help me out because I have a bricked N5. So this is my first time attempting to flash anything to my phone and I decided to check out the android L preview. I watched a bunch of videos and got everything set up (SDK, unlocked bootloader). After I unlocked the bootloader, I forgot to enable usb debugging before I booted into fastboot and attempted to flash L. When I try to flash L I get "writing bootloader... FAILED (remote: invalid bootloader image)" every time. So I said screw it I'll just flash 4.4.4 and be done with it but I get the same FAILED msg in cmd. I'm assuming this is the issue that's preventing me from successfully flashing anything to my phone but not 100% sure. I've tried to get my phone into recovery mode but can't seem to make that work either. What can I do to fix this? keep in mind that just today was the first time I've ever used the command prompt =/ Thanks in advance for giving this a read and I really hope its just some simple fix *fingers crossed*

USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads

Lethargy said:
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Click to expand...
Click to collapse
well turn's out all I had to do was restart my laptop and now everything has decided to work. Thanks for the response Lethargy

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~

[Completed] HTC One Remix from Verizon I think it's soft bricked?

Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
Am I screwed?
Thanks for any assistance.

Thread closed.
OP posted in the correct section
http://forum.xda-developers.com/one-mini-2/help/htc-one-remix-verizon-soft-bricked-t3416396

Stuck at bootloop after update, can't access ADB.

Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error

Question Bootloop after turning off developer settings

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.