![](/uploads/1/2/7/6/127676930/849647657.jpg)
Continue to hold VOLUME DOWN until the Download mode is displayed. APPLY UPDATE FROM ADB – Enables you to sideload firmware using your. Device Carrier Region Type Kernel Android Size Description HTC Exodus. HTC Asia: AUS: MR 1: 4.9.112: v9.0: 425 MB: 2.37.400.3R.
My phone failed an official update over the air. It won't boot past the bootloader. The phone is carrier unlocked (originally AT&T).Recovery and Factory Default options do not work. They simply go back to bootloader. The most recent RUU does not work. It reboots my phone, and when my phone comes back the RUU says the cable was disconnected.
I have no warranty. I am also concerned by the missing info, shown in the image.I started a similar thread here: I eventually gave up on the phone for a while because I had no time.
I'll move this to the M8 forum, as the place you'll get the best device-specific help.One thought: I would guess this was an ATT update, as the phone's CID would still be ATT, so you could try asking them anyway. You may not have a warranty, but if their update broke the phone you could argue that they have a moral responsibility.Otherwise, your other thread left off with a charge level problem - is that fixed now? And by now there may be newer RUUs (Lollipop) so it may be worth trying that. There is also a trick to extract a zip from the RUU.exe which can be installed from sd via the bootloader (not recovery) if you can't get the USB connection stable, but I'd need to do a bit of research to find the magic filename needed for the M8. RebootRUU does not go well.
I was worried when I saw the output the first time. It does reboot the phone however.Cable is fine. I don't have random disconnects. Directory of C:UsersTylerDownloadssdk-toolssdk-toolsruu 09:02 PM.
![Download Download](http://techtrickz.com/wp-content/uploads/2016/12/htc-one-m9.jpg)
OK, at some point the RUU ought to expose IMG files for boot, firmware and hboot unless they're packing things differently these days. I sincerely doubt it, the rom.zip you have is 1.6 GB, the /system image on a running M8 Lollipop is just over 2 GB.Somewhere I've read how to combine the android-info.txt + rom.zip into a zip payload (probably using 7zip), a 0P6BIMG.zip file - that's what the bootloader is looking to auto install from the sd card.EDIT - here's one - Ignore what it says about not needing hboot or recovery, you need everything.Flashing the rom.zip that way will only tell you if the bootloader isn't corrupted enough to perform an install. And even that you may not be able to trust.It will.not. give you a working phone, not by a long shot.As for making 0P6BIMG.zip files out of the IMG files if you could find them, I could look at what has done for s-off phones and put something together. That's going to take a lot of time for me with no guarantees. Time I'm not sure I have.Without s-off I'd be surprised if you can get any further even if you could get the IMG files.I could be wrong.Anyway - there are your hints.Not sure I can help further or not. At the top of your bootloader screen it says s-on, in the getvar output it says security: on.
You can't get s-off in your present state.And I'm not doing a good job explaining about the rom.I imagine that you have a pc and know that 1) it has a bios on the motherboard, 2) a boot sector on the hard drive, and 3) Windows OS in the C:Windowssystem32 folder.Imagine that your pc won't boot up as combination of the bootloader (2) being scrambled and part of the bios (1) damaged - nothing else wrong.Which areas would you focus the emergency effort on? It wouldn't be (3), the system32 folder.If that all made sense, then the rom is equivalent to the C:Windowssystem32 folder.And your problems are presenting in the areas equivalent to (1) and (2).
It's rare but the download could have been corrupted. Or you could have had a single event upset (electrical thing ok) in RAM just at the right point that didn't recover, or a power systems issue during the update.It's pretty hard (actually very rare) to get that corrupted but it's not impossible, you've got proof.So is the guy I was helping elsewhere this week.I doubt it helps but thought I'd say, you're not alone.Sorry it happened to you.But someone has a reputation to protect.
I'd call both as suggested and scream no fair until someone listened.It couldn't hurt to try.
![](/uploads/1/2/7/6/127676930/849647657.jpg)