Develop Bugs

Boot Loop/No Recovery

Hey all
I tried to flash over a Google Edition Rom from Cyanogen Mod by following a guide and now I am stuck on a google boot loop. Ive tried to enter recovery but it just leads me back to the google boot loop and the same happens when I try to choose factory reset. Ive tried to flash back to cyanogen and I get this error FAILED (remote: 24 parsing android-info fail) I have also tried to flash back to a sense rom and get this error FAILED (remote: 24 parsing android-info fail). So how can I either get my recovery working or getting back to Cyanogen.
Also I changed my model ID when following the guide... So Im guessing that has something to do with it but I am unsure how to change my model ID back without having access to recovery.
Heres what I got from the getvar command
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37MS910651
(bootloader) imei: 990004281021810
(bootloader) meid: 99000428102181
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4090mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
[Edit] I also tried flashing a recovery and got FAILED (remote: not allowed)

Try flashing twrp using ruu mode. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot

cmlusco said:
Try flashing twrp using ruu mode.
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot
Click to expand...
Click to collapse
I do that and get FAILED (remote: 41 model id check fail)

Ok try the same thing only with this file https://www.dropbox.com/s/k52zdjv453isy0h/PN07IMG.zip

cmlusco said:
Ok try the same thing only with this file
Click to expand...
Click to collapse
I got the same FAILED (remote: 42 custom id check fail) error. I reran getvar all and saw that the cidnum changed from GOOGL001 to VZW__001

Ok try this one then https://www.dropbox.com/s/f8vtvu1ahg2uqql/PN07IMG2.zip

That worked! Thank you! I was able to sideload cyanogen back on but now it reboots after a couple minutes of being in the rom...

You may need to flash the latest firmware after changing your mid back if you havent already.

cmlusco said:
You may need to flash the latest firmware after changing your mid back if you havent already.
Click to expand...
Click to collapse
The latest stock firmware? Where would I get that

http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot

cmlusco said:
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
When I try to flash over the file in RUU it gives me this FAILED (remote: 42 custom id check fail)
(bootloader) modelid: PN0731000
(bootloader) cidnum: GOOGL001
That is what shows up when I getvar all

Change your cid back to VZW__001
fastboot oem writecid VZW__001

cmlusco said:
Change your cid back to VZW__001
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
When I run that I get
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.064s]
finished. total time: 0.064s
And when I getvar all my cid still says GOOG001

Try changing it to super cid 11111111 eight ones

That worked and so far Cyanogen is not randomly rebooting!
Thanks again! You are a life saver

cmlusco said:
http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.

disconnecktie said:
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.
Click to expand...
Click to collapse
Not my intention at all. 99.8% of the stuff on that site is not made by me. I do it to make it easier on my self when trying to help others, so i dont have to search all over for links. I also do it as a backup of sorts. I have seen file sharing sites go down (some permanetly), xda members leave or close threads or not maintain them once they move to a new phone or what ever. Then these critical files are lost, or a massive time consuming manhunt insues to find them. It also provides one easy organized place to find the files you need .And just to be clear, the no boot img file you are refering to was not made by santod. It was one i edited my self by pulling the boot img from a firmware zip file. Just because he did it, dosent mean someone else cant do the same. Im not here for credit, im here to help people and to get help. I give santod and any other dev whos files i mirror full credit. If its that big of a freakin deal, i will just shut the site down. I have done the same thing with several other phones i have had, and have never had an issue from anyone like i have had here in the vzw one forums.

Well on several phones I've owned it was rude to mirror devs files without their permission or without them requesting it. It is one thing for the dev to ask for a mirror and someone mirror the file for them. All the links in his op work and they aren't hard to find at all. So other than having a site for your own personal reasons there doesn't seem to be a very good reason to have mirrors of every file that has been posted to this forum.

Well your opinion is yours. I dont see what its hurting. Its not like im mirroring roms or anything. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.

cmlusco said:
Well your opinion is yours. I dont see what its hurting. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.
Click to expand...
Click to collapse
I'm not at all saying you can't help people but how much more difficult would it be to link back to the op where you got the file from? As far as I know all the links are working.

[Q] TMOUS M8 accepted GPE hboot 3.18 - Am I busted?

It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SUREWHYNOT
(bootloader) imei: YESSIR
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

xHighAlert said:
It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Click to expand...
Click to collapse
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu

iRunLinux said:
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu
Click to expand...
Click to collapse
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s

xHighAlert said:
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.

iRunLinux said:
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.
Click to expand...
Click to collapse
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.

xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
Use the same method in which u flashed the black hboot to flash the stock hboot
---------- Post added at 03:47 AM ---------- Previous post was at 03:42 AM ----------
xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
And if not try flashing gpe stock rooted rom which should boot since your still using that firmware, then try and s-off with sunshine.

I'm in pretty much the same circumstance. Tried going GPE - installed GPE ROM, flashed GPE Recovery to get the 4.4.4 update and now neither GPE nor Sense Roms will install or boot. I had S-Off before, but I think the GPE Recovery put security back on and now I'm back to S-On.
I've tried GPE, Stock Sense, and custom Recoveries and Firmware - nothing is working... I'm stuck running CM11 at the moment.
If only there was an S-Off method that would actually work under CM.

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.

I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?

grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.

Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.

grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

Sprint M9 - Can't boot to recovery, can't flash recovery, S-ON, Unlocked bootloader.

I'll try my best to be as detailed as possible.
I have an HTC One M9 from Sprint. Custom rom on it, I believe it was either Viper Rom or BadBoyz. Running a TWRP PRE 3.0 recovery.
My phone had a pattern lock screen.
I had let the phone sit for about a month with out use, after which I attempted to turn it back on to use it, what I got was a continuous HTC loading screen. So I'm thinking no big deal, all I gotta do is boot into recovery and reflash it.
I boot into recovery, It won't format a number of partitions (I.E. data, system, cache) to allow the flash.
I follow instructions in this video:
with no luck, still won't flash.
So after a few hours of research and attempting different versions of twrp and cwm, it no longer has a bootable recovery. any TWRP 3.0 and up wouldn't run at all, no CWM recovery would run.
My understanding is that those partitions were encrypted and pre 3.0 for twrp can't handle the encryption or some such. I flash a few different versions, going from pre 3.0 to post 3.0, with post 3.0 still not booting but pre 3.0 booting.
THEN
After trying to flash back to a pre 3.0 twrp, it acts as it takes it, but when i go to boot into recovery i get:
"Failed to boot to recovery mode"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\PropertyCO\twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 3.063s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.562s]
finished. total time: 5.629s
is what fastboot returns, yet it won't boot to recovery.
So, my next attempt was to run an RUU.
RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.41
I run it, starting with my phone in download mode, RUU sees it just fine, goes to reboot into bootloader. with out assistance when it reboots it just brings up a metalic HTC logo and sits there, so when it reboots i'll hold volume up and down to get it to the boot loader. after some processing from the RUU it gives me the error 170 - USB connection error. Me thinking it's either some drivers messing it up or the cable, i try another laptop, and a series of different cables, no luck there.
I find out that I have to have the bootloader locked to run a RUU, so I attempt to relock the bootloader to see if that fixes the error.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELOCK device
OKAY [ 0.286s]
finished. total time: 0.287s
phone reboots, i force it into bootloader cause it doesn't automatically go to it, still says "*** UNLOCKED ***" up at the top.
fastboot getvar all:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
all:
finished. total time: 0.048s
Thanks in advance!
Edit:
Attempted the ZIP method in this forum and failed too:
https://forum.xda-developers.com/showthread.php?t=1928439

Your nand is corrupt. Dead phone.
Beamed in by telepathy.

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.