Develop Bugs

About to brick my DZ, help! (Solved, backupCID was blank)

So i had custom rom installed by previous owner, but which i did not like, so i wanted to go stock.
After following some guide i managed to flash new rom into my DZ using CWM and all hell broke loose.
My DZ refused to boot, only gives me the white htc screen and vibrates once.
From hboot i tried go back into recovery, which gives me same white screen with htc logo and vibrates once. Same goes for Factory reset option.
After week of browsing xda forums and google, i finally gave up. Thou i managed once to reboot into G2 os after attempted flash trhu PC10IMG method or from recovery as first attempt, not sure. Which i thougt was supposed to be DZ rom, but was not. This rom might have reduced my system partition, i dont know how to confirm this.
Fastboot works, but no adb since i have no OS running atm.
Fastboot getvar all gives me this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>fastboot devices
SH0B5RT09144 fastboot
C:\Documents and Settings\User>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.84.2000
(bootloader) version-baseband: 26.02.01.15_M2
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 1.22.531.8
(bootloader) serialno: SH0B5RT09144
(bootloader) imei: 352212045345548
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: adbd7a75
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\Documents and Settings\User>
At this point i dont want to go solo anymore, so im crying out for help on this one... I want to save this awesome Desire Z
Edit: I am able to flash recovery using fastboot flash recovery recovery.img but recovery option is still useless (does the white screen htc logo vibrating once thingy)

Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010 , 15:56:38
Then i have Fastboot, recovery,factory reset, simlock, system info and image crc in this order.
In image CRC i have:
hboot : 0x2A125CF4
boot : 0xD28A4324
recovery : 0x26A3CD9C
system : 0x0
Then it promts me to press power key to go back

Alright, you are looking good and most likely this isn't a brick, should be easy to recover
Do these steps
Go to fastboot mode and run
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now you want the most recent recovery, probably latest 4ext (see this thread for recovery links - http://forum.xda-developers.com/showthread.php?t=2348266
In second post along with lots of other good links
Now take this image and
fastboot flash recovery nameofrecovery.img
fastboot reboot-bootloader
Now choose recovery
If this gets you there flash ROM of choice (and gapps if needed) in this new recovery
Reboot
If anything fails or you can't find links let me know
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

C:\Documents and Settings\User>fastboot erase system -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'system'...
OKAY [ 0.344s]
erasing 'userdata'...
OKAY [ 0.266s]
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.719s
C:\Documents and Settings\User>fastboot erase boot
erasing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.125s
C:\Documents and Settings\User>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\Documents and Settings\User>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Documents and Settings\User>cd C:\android-sdk_r11-windows\platform-tools
C:\android-sdk_r11-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (5342 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.594s]
finished. total time: 1.484s
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>
Did all that but still cannot access recovery :/ does the white screen thing.
Now im having hard time booting into hboot / fastboot
Edit: Okay, got in after a while Image crc as follows:
hboot 0x2A125CF4
boot 0x0
recovery 0x4C2506F5
system 0x0

http://forum.xda-developers.com/showthread.php?t=2348266
The second post in this thread you will find a section on adb and fastboot, the how to why to link brings you to a guide on fastboot
Flash the dz hboot from there (be sure to check md5sum)
I'm under the impression you have a corrupt partition right now so
fastboot flash hboot hboot.img
fastboot reboot-bootloader
Now start over with the same fast boot erase and flash commands from prior
Sent from my Nexus 7 using XDA Premium 4 mobile app

Still no luck.
I flashed hboot_7230_0.82.0000_100902.nb0, which i got from the PC10IMG.zip mentioned in thread.
Image CRC from hboot did not change after flash, so i guess i had the exact same hboot.
I repeated all the steps you mentioned and it gave me same error messages.
Still willing to help me?

You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that and repeated all again. Did not do anything :/ only recovery crc changed, but flashed recovery did not work so i flashed the 4ext again, still no access to recovery
Any ideas? Maybe im stuck with G2 system size since i flashed G2 rom back then, which i got to boot. Should i try that again? If so, any hints to do it properly?

Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing the hboot from zip changes nothing and for some reason fastboot rebootRUU gives me list of commands
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>fastboot rebootRUU
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\android-sdk_r11-windows\platform-tools>
Should i try to manually format system partition? If so, how and how large?

Sorry, the command is
fastboot oem rebootRUU
Sent from my Nexus 4 using XDA Premium 4 mobile app

Do you mean fastboot update DZPC10IMG.zip since fastboot flash update DZPC10IMG.zip gives unknown partition error.

Sounds right, its been probably at least a year or two since I've worked on this, take a look at my threads and you'll see two comprehensive guides on fastboot which will have all the proper steps
Sent from my Nexus 4 using XDA Premium 4 mobile app

I was able to flash stock rom extracted from RUU.
I used fastboot oem rebootRUU and then fastboot flash zip rom.zip and everything went OK.
However, i still cannot access recovery nor boot my phone.
Atm my hboot is 0.85.0013 SHIP S-OFF
Radio 26.10.04.03_M
Image CRC :
osb1: 0x7EE4ED8C
amss: 0xB7A63815
hboot: 0x887F7ABB
boot : 0x4CB9BC27
recovery 0xCFD60F9D
system 0xC46F8680
Any leads where to go from here?

Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to flash DZPC10IMG.zip from rebootRUU but that did no good either so i tried to flash this rom from this RUU RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Which i believe is supposed to be latest stock rom from DZ... correct me if im wrong

The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no idea where that guide is now, but if my memory serves me well, i flashed PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from cwm recovery. After that i was able to boot into G2 rom for a while, thou my onscreen buttons didnt work (back and home etc) after that, no idea.
Edit: I do have my old DZ with working CWM v3.0.2.4 recovery. Can i use that in my advantage somehow?

Here is some data if its helpfull. My backup cid seems to be blank. Im under impression it should be like y_13 or so.
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is
(bootloader) setting->cid::
(bootloader) serial number: SH0B5RT09144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =456
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.13.04.19_M androidboot
(bootloader) .cid= androidboot.batt_poweron=good_battery androidboot.carr
(bootloader) ier=COMMON androidboot.mid=PC1011000 androidboot.keycaps=qwe
(bootloader) rty androidboot.mode=normal androidboot.serialno=SH0B5RT0914
(bootloader) 4 androidboot.bootloader=0.84.2000 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:657379 msec
FAILED (status read failed (Unknown error))
finished. total time: 222.922s

Which firmware and official ROM to update my AT&T M8 to? (stuck on Android 4.4.2)

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to get the latest android available for my HTC M8 (AT&T). I'm currently on Android 4.4.2. I have an mdnsd battery drain bug, and the bluetooth has a bug that causes it to break whenever I get around too many bluetooth devices.
I've tried flashing to TWRP, flashing back to the factory recovery, multiple RUU files, and a SkyDragon ROM. All either don't update or cause a boot loop, and I end up doing a nandroid restore to my old ROM.
I get the impression that I need the correct version of the boot loader, which is included in the right firmware.zip file. I've tried to find the right file, but when I go to the mike1986 page to download the firmware, I'm not sure which version to try. What is the latest official firmware that will work for my phone, and what is the latest official version of Android I can update to?
Any help is greatly appreciated!

Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5

ckpv5 said:
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
Click to expand...
Click to collapse
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.

kentuckythrash said:
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
Click to expand...
Click to collapse
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader

ahmed.ismael said:
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
Click to expand...
Click to collapse
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.

kentuckythrash said:
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
Click to expand...
Click to collapse
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here

ahmed.ismael said:
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
Click to expand...
Click to collapse
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.

kentuckythrash said:
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
Click to expand...
Click to collapse
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.

kentuckythrash said:
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
Click to expand...
Click to collapse
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.

kentuckythrash said:
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
Click to expand...
Click to collapse
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.

kentuckythrash said:
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
Click to expand...
Click to collapse
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"

kentuckythrash said:
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
Click to expand...
Click to collapse
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
That worked! Thank you very much for your help. These M8s are really hard to update!

kentuckythrash said:
That worked! Thank you very much for your help. These M8s are really hard to update!
Click to expand...
Click to collapse
Not hard but tricky
Glad i helped
Sent from my HTC M8 using XDA Labs

Confused on the upgrade process

Hey everyone,
Its been a long time since I updated my phone.
Here's my configuration:
HTC One M8
Android Version: 4.4.4
HTC Sense version: 6.0
Unlocked, M8_UL, S-On
HBOOT: 3.16.0.0000
Radio: 1.15.2133156.UA13G
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Now I tried to turn to convert to S-OFF using Sunshine but it comes up with this: Debug Kernel/Ramdisk - Your device has a debuggable ramdisk. You need to flash a non-debuggable boot.img
I want to go back to the hassle free official Android version provided by HTC. I have tried to look for a up to date guide, however the download links are dead.
Can someone point me in the right step? It'll be much appreciated.
Thank you

why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ahmed.ismael said:
why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Thank you Ahmed I will follow that post and will let you know it goes.

ahmed.ismael said:
why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
So I reached the following step:
htc_fastboot flash zip RUU.zip (to install RUU)
And heres what happened.
C:\Users\User\Desktop\HTC One M8\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.927 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 4(s)

SamungGalaxyS2 said:
So I reached the following step:
htc_fastboot flash zip RUU.zip (to install RUU)
And heres what happened.
C:\Users\User\Desktop\HTC One M8\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.927 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 4(s)
Click to expand...
Click to collapse
did you relocked the bootloader ??
if yes try another method to flash and check the md5 for the RUU.zip
this is the easiest method to flash a signed RUU.zip https://forum.xda-developers.com/showpost.php?p=67307303&postcount=1748

ahmed.ismael said:
did you relocked the bootloader ??
if yes try another method to flash and check the md5 for the RUU.zip
this is the easiest method to flash a signed RUU.zip https://forum.xda-developers.com/showpost.php?p=67307303&postcount=1748
Click to expand...
Click to collapse
The bootloader is currently unlocked (it says ** UNLOCKED ** in purple).
I just tried to open the ZIP file, in Windows, and it says cannot be opened, so I do think it was corrupt somehow. I am going to download it again and see if it does it again.
If it doesn't work again, I will try your other method.
Thank you buddy.

SamungGalaxyS2 said:
The bootloader is currently unlocked (it says ** UNLOCKED ** in purple).
I just tried to open the ZIP file, in Windows, and it says cannot be opened, so I do think it was corrupt somehow. I am going to download it again and see if it does it again.
If it doesn't work again, I will try your other method.
Thank you buddy.
Click to expand...
Click to collapse
no you can't open the .zip it's signed with htc keys and you can't open it by normal apps
now relock the bootloader as the guide said in the linked post above
it should be relocked to flash a signed RUU.zip on s-on device
no need to download again

ahmed.ismael said:
no you can't open the .zip it's signed with htc keys and you can't open it by normal apps
now relock the bootloader as the guide said in the linked post above
it should be relocked to flash a signed RUU.zip on s-on device
no need to download again
Click to expand...
Click to collapse
You are a star. Thank you so much mate. Just rebooting right now, with the "Android is starting"

SamungGalaxyS2 said:
You are a star. Thank you so much mate. Just rebooting right now, with the "Android is starting"
Click to expand...
Click to collapse
Glad i helped
Enjoy
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
Glad i helped
Enjoy
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
WORKS

bootloop HTC One M9, Original, Locked, S-ON

Good day everyone.
After two weeks of trying and searching the web for an answer I have finally given up and decided to post my question here, perhaps someone has an idea that can help.
I have an HTC One M9 that was stashed away in a cupboard, I decided that I am going back to it as my current phone is just not working for me, however, I LOVE the hardware on the One M9 but I do not like the HTC Sence UI and decided that I will flash it with a custom ROM. Needless to say I completely stuffed it up. (I probably should have S-OFF and unlocked before I tried flashing. (Also didn't enable developer options or USB debugging - stupid stupid me)
Herewith the symptom. I can boot into download mode but not recovery, when i boot into recovery the black HTC logo appears and then disappears, appears, disappears etc etc so ABD does not work.
I have tried the RUU route but as soon as the installer reboots the phone it does the whole black logo loop thing. the get_identifier_token command also returns bank (see output below) so can't even use the htcdev procedure.
I have tried manually flashing zip and img files and get a 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCK also tried flashing stock recovery.img rom.
Rom:
M9_3.35.401.12_FullStock_wipe.zip
M9_3.35.401.12_NoWipe_TWRP2871b1.zip
0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Ra dio_01.01_U11440261_56.02.50306G_2_F_release_42934 0_signed_2_4.exe
Manually flashing with extracted rom in RUU file
hima_uhl_n70_hosd_signed.img
HTC_One_M9_1.32.401.8_recovery_signed.img
twrp-3.2.1-0-hima.img
Used the SDCARD option
I did the fastboot erase cache process
At some point I was able to htc_fastboot flash zip rom.zip and it sent up to 50% but just remained there
Original Software
LOCKED
S-ON
htc_fastboot "works"
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXX
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.143s
flash example:
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe flash zip d:\roms\M9_3.35.401.12_FullStock_wipe.zip
htc_fastboot.exe v3.0.7 (2015-03-30)
target reported max download size of 800000000 bytes
sending 'zip' (134610 KB)...
OKAY [ 8.962s]
writing 'zip'...
(bootloader) HOSD CL#671758
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 10.121s
htc_fastboot finished. total time: 12.576s
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.162s]
finished. total time: 0.162s
htc_fastboot finished. total time: 1.335s
Please help or even tell me I am doing something wrong.
Thank you

The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".

lucyr03 said:
The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".
Click to expand...
Click to collapse
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started

neetekweet said:
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started
Click to expand...
Click to collapse
Neither being S-ON nor not having enabled the USB debugging prevents you from flashing a RUU that has the same firmware version as your phone.
If flashing the RUU that lucyr03 mentioned fails then you need to check whether the MD5 checksum of the downloaded file is correct and whether your SD card is broken.
Sent from my HTC One M9 using XDA Labs

Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.

shivadow said:
Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.
Click to expand...
Click to collapse
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.

neetekweet said:
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.
Click to expand...
Click to collapse
I can tell you now the phone is bricked.

flashing twrp succsess, can not load twrp from recovery

hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you

redstonedudeHD said:
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you
Click to expand...
Click to collapse
It isnt working for you because you have to boot directly into recovery, you can't let the device boot to any other mode, if you boot to any mode other than recovery, a device will revert back to stock recovery. You are rebooting to bootloader mode instead of recovery mode, this is causing the device to revert to stock recovery instead of booting into the TWRP that you flashed.
After flashing TWRP, instead of using the fastboot reboot-bootloader command, use the adb reboot command, enter it as soon as you are done flashing the recovery.
Use the adb command below:
adb reboot recovery
Then you should boot into TWRP.
Sent from my SM-S767VL using Tapatalk

hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.

redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Ok, let's take a couple of steps back. Do you know if your bootloader is unlocked? Flashing TWRP won't work if the bootloader is locked.
@xunholyx, could there be something that is HTC specific that they are overlooking?
Sent from my SM-S767VL using Tapatalk

bootloader is unlocked

redstonedudeHD said:
bootloader is unlocked
Click to expand...
Click to collapse
Try flashing the TWRP using the fastboot flash recovery command
Then try using this command:
fastboot boot recovery (name of your recovery file)
Sent from my SM-S767VL using Tapatalk

flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory

@Droidriven any idea what i can do?

double send

redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Do you have USB debugging turned on in developer options? ADB commands won't work if you don't.
---------- Post added at 11:55 AM ---------- Previous post was at 11:50 AM ----------
redstonedudeHD said:
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
It seems to have flashed properly with htc_fastboot.
Try flashing it again, then
htc_fastboot reboot bootloader
then select boot to recovery from the bootloader menu on your phone from there.
It should take you to TWRP

hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.

redstonedudeHD said:
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
Click to expand...
Click to collapse
It should work with regular fastboot reboot bootloader then selecting recovery from there via your phone
EDIT: I have never had to use HTC's fastboot myself. It is necessary for flashing large files from your PC. I always flashed the large files (eg: RUUs) via the SD card method. But that wasn't for recovery.img s, it was for RUUs
EDIT #2: I'm going to request to the moderators to have this thread moved to a forum where you might find other help. You don't have to do anything about it. It will just get moved. The forum I'm moving it to is for the regular M8 and not the M8s, but people there will be able to offer help that you won't get here. I'll continue to monitor this thread there and offer help if I can.

hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!

redstonedudeHD said:
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
Click to expand...
Click to collapse
Sorry I haven't responded sooner.
I would suggest you run an RUU. The problem is, I don't know of any RUUs myself for your current firmware version, and since you are S-On, you can't roll back to an older version.
If you can find an RUU for 2.11.161.1 download it and flash it. The only ones I can find are from a previous Android version. (1.xx.xxx.x)
Also, there is a newer TWRP version than the one you are using. Maybe that might be the issue? I can't be sure about this, since I'm familiar with the HTC M8, but not the HTC M8s.
You can download the updated TWRP version from here.
I believe it was updated to work with 2.xx.xxx.x firmware. But I'm not positive. It can't hurt to try it out.

hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/

redstonedudeHD said:
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
Click to expand...
Click to collapse
There's two there. I don't know what the difference between "partial" and the other one is. I would assume the partial one has the boot.img and maybe the recovery.img removed?
Use the other one. There are two ways to flash it since it is an RUU.zip.
#1: In fastboot: fastbbot flash zip **drag and drop the zip here**
#2: Rename the zip by deleting everything in the name of it except for 0PKVIMG (and .zip of course) and place that onto your extSD card (must be formatted to FAT32)
Put that into your phone then bot to bootloader. It should find the file automatically. If it doesn't, boot to hboot from boot loader.
From there it's super easy. Follow the on screen prompts. Volume up to confirm the flash. Power button to reboot after the flash is done.
Good luck! I hope you get everything up and running again.