Unlocking HTC ONE M9 Bootloader *S-OFF - Android Q&A, Help & Troubleshooting

I accidentally deleted my OS while trying to factory reset my HTC One M9 and now i am having a really hard time trying to flash a custom ROM. My bootloader is locked and i would like to unlock it, however, i am finding this task to be really hard especially being new and all to flashing custom ROMs.
The command "adb devices" successfully identifies my phone when it is in TWRP recovery but when i run the command
"fastboot oem get_identifier_token", i am stuck in "waiting for device"
I am getting really frustrated, someone kindly assist me.

Related

Can't unlock again to flash new recovery or rom

So,
I wanted to install a new recovery because i want to try out multirom (http://forum.xda-developers.com/oneplus-x/orig-development/mod-multirom-v32-t3316937).
But when i wanted to flash the recovery I found out that the bootloader is again locked.
I tried to unlock if again but the fist problem was, that it said "error: device offline" every time i did "adb reboot bootloader".
So i just bootet into fastboot myself and did "fastboot oem unlock". Then the program said that it finished and my phone launched TWRP.
I heard that you need to press "Yes" in your recovery but nothing showed up. The phone is still locked and i can`t figure out what to do/ what i do wrong.
I hope you guys can help me,
Andy

Stuck in bootloop after flashing custom recovery. Please help.

I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.

How do I find out whether I fried the bootloader?

Hello,
as I said in another thread, I bricked my tablet while trying to root it, and made it worse while trying to fix it: it's in a bootloop.
Fastboot mode works still, but no recovery I tried does anything. So I might have fried the bootloader by doing something stupid like "fastboot flash boot <file.img>". I can't remember whether I did this during my desperate attemps of getting out of the bootloop, but if I did, how would I find out?
As far as I understand the boot process (now ), there is a piece of code that initializes the device and then loads the actual bootloader into memory. When I'm in fastboot mode, am I already within the bootloader or still inside that piece of initial code?
When I chose "recovery" or "normal boot", is it first then that the bootloader is started? Or is it already the bootloader that shows those options ("recovery", "normal boot" and "fastboot")?
When I do a "fastboot getvar all" I do get a lot of variables all starting with "(bootloader)", mostly "partition-size" and "partition-type". So is my bootloader still ok and if not, how do I find out whether it's the bootloader broken or the recovery I'm trying to flash, and which one is causing the bootloop?
Thanks for any hints.

ZTE Z820 (Obsidian) Cant boot fastboot/bootloader bootloop

I tried using the Tool All In One to unlock the bootloader and manually through the adb and fastboot terminal. ADB recognizes the device even though every time i reboot to bootloader through adb or manually through the phone recovery and manual buttons it never sends me to the bootloader. i was able to flash the stock firmware with SP flash tool. I really just want to install TWRP. i have been able to root this device with Wondershare dr.fone root program. I wanted to get it to work with the All in One tool so i can install TWRP to install custom firmware. If anybody can point me in the right direction on why the bootloader never works and fastboot? Maybe this model the bootloader is unaccessible? And if i cannot get to fastboot to unlock the bootloader can i still install twrp somehow. Also when using fastboot command it shows the device id it just says waiting for device everytime and cannot get it to recognize past that point. Not being able to get past this phone problem has been really bothering me and irritating me lately so hopefully i can get it resolved. I will be back later to see if anybody knows a solution to this. it seems like i have been trying to do the same thing and maybe im right and fastboot mode and the bootloader is locked and currently not possible.

Kyocera Dura XE Root

Hi there. Hope someone can help me.
I have a Kyocera Dura XE (flip phone running a build from Android 5.1.1?) that I'm trying to unlock the boot loader & root.
I've installed the proper drivers from Kyocera's site and it seems like the device is recognized by windows in device manager now. But am having trouble to boot the device into fastboot. I can reboot the bootloader with ADB, but all it gets me to is a reboot of the device. Fastboot just keeps waiting on the device, which reboots to normal.
Any advice on how to get this decive into Fastboot to unlock the OEM bootloader?
Thanks!

Categories

Resources