I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
Greetings.
Thank you for using XDA Assist. Here is the M8 homepage:
HTC One M8 (2014)
Here is where you should ask your questions:
One (M8) Q&A, Help & Troubleshooting
Good luck!
Related
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"?
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
thepenrosesteps said:
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
Click to expand...
Click to collapse
Try Power the Device Up in Safe Mode - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
sd_shadow said:
Try Power the Device Up in Safe Mode[/URL] - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
Click to expand...
Click to collapse
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
thepenrosesteps said:
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
Click to expand...
Click to collapse
It's likely a s720e then, but
I will request that this thread be moved to AT&T One X Q&A, Help & Troubleshooting
Where you should be able to find out for sure.
Next step is likely flashing a custom recovery like TWRP or CWM then you could, mount sd card/storage and copy photos.
see AT&T One X Q&A, Help & Troubleshooting Frequently Asked Questions by Heisenberg
[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 5/8/14) by redpoint73
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
mellobc said:
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Click to expand...
Click to collapse
Greetings and welcome to assist. Can you get into download mode ? If you can does smartswitch emergency firmware recovery work
Regards
Sawdoctor
Hello everyone, I found again my old Nexus 5, I changed few years ago because after changing the OS many time maybe I did something wrong and my phone was stuck.
loop on the ANDROID logo, I can still access fastboot mode.
Today I want to try to restore it to stock, I installed again adb, downloaded the factory img.
Though when I want to use fastboot command, I have a <waiting device> line.
Because I can use my phone, I can't go to developer mod to install drivers. so I try to do it manually by adding legacy drivers, but it didn't seemed to work because I still have the waiting device line ...
If someone can help me to resurrect my good ol' Nexus 5
No one to help me ?
Enterenn said:
No one to help me ?
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
or restore nexus 5 nougat
https://mega.nz/#F!mxhBAKrL!pcsihiNof05gLrv-nY7dJQ
or restore to kitkat
https://mega.nz/#!Ow5DjQCT!vmES1dGhWSc0mxjdl7KyNCzAlHVgUterB6d6gJhh1pE
for these two tools put your phone in fastboot mode and click on recovery nexus 5 bat and see the instruction .
https://forum.xda-developers.com/go...l-06-03-14-one-click-factory-restore-t2513937
The thing is even the tool all in one ask for usb debugging, I don't know if this option on my phone is good, but I can't go on it because it can't boot (bootloop)
And when in fastboot mode, my device doesn't appear in the device list of the all in one
You may try and this ...http://www.wugfresh.com/
No, nothing is working. because my phone is not detected by anything.
You don't need developer mod to install drivers.
1- Boot into fastboot.
2- https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Download and unzip this.
3- Go to your Windows Device Manager, find your phone and manual install the driver.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.