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.
Related
So I am new to the posting aspect of xda but have been around checking out other peeps info for a while. Basically I've gotten into a weird situation, and have no idea now how to fix it. Sorry if there is already a thread for this issue, but I have been looking for 2 days, and decided I was in over my head.
I have a HTC One M7 Verizon (blue Best Buy model) which I got AFTER HTCDev had locked Verizon from unlocking bootloader via their website.
One a exploit was found to unlock the bootloader and gain root, I jumped and ran through the process using a CWM recovery and a Cyanogenmod as my ROM. Everything was peachy until a few days ago when an update, auto updated over night, and created a problem where my phone would reboot show the lock screen, but when I swiped up to unlock it, the green HTC came back up and eventually the thing would reboot.
So I started looking around to see what other ROM's were out there at the moment and flashed ViperOne, all was well, updated my radio, firmware, and such. However, every-time my phone would go into a regular boot after setting up the ViperOne ROM, it would freeze.
So desperate for a fix I hurriedly wiped the system, used CWM recovery to reinstall the stock rom.
Upon doing this I decided I should take advantage of the stock status of the phone and get the OTA's. This is where I became stupid!!!!!
Apparently doing such a thing re-locks your bootloader. Since I wiped the system SU was not longer installed and I lost root as well. Now I cannot issue ANY fastboot FLASH commands from my adb/fastboot CMD.
HELP, pretty, pretty please!!!
I really don't like sense at all, and think that Blinkfeed is the largest piece of #[email protected]*&^% I have ever seen.
Thanks in advance for even reading!
***Edit***
Forgot to mention what's currently running on my phone:
Build/OS: 4.3 JB CL278010 2.10.605.1
Kernal: 3.4.10-g40851b1
[email protected] #1
Baseband v. (Radio) : 1.12.41.1112_2
Basically stock jelly bean, used a stock RUU version flashed via fastboot flash command. Once phone rebooted with stock then applied the 2 previous OTAs I had missed coming from 1.10.605.10 (4.2)
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
cmlusco said:
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
Click to expand...
Click to collapse
Yes I am still s-off, thank goodness!
I just can't get any flash commands to work, even in oem rebootrRUU.
I can try going through the process your suggesting and see if it works, will update with results.
What errors do you get when trying fastboot cmds?
"What errors do you get when trying fastboot cmds?"
Once I am in bootloader and go into fasbootusb this is what I have tried:
fastboot oem rebootRUU (phone flashes and comes up with the silver HTC on the screen)
Send the command for recovery:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8786 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.199s
If I try to flash a zip:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip superuser.zip
target reported max download size of 1526722560 bytes
sending 'zip' (4538 KB)...
OKAY [ 0.697s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.972s
It will respond (obviously) when I give it:
fastboot reboot-bootloader
But am not able to enter any adb commands as there isn't a recovery installed!!
Here is the info from the phone:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxx
(bootloader) imei:xxxxxxx
(bootloader) meid:xxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
The fastboot system will let me do things like, change my CID from VZW_01 to a super CID11111111 and back again, no errors, but not sure how much help that is...
I worry about trying to flash a new RUU because I can't back anything up right now....also just to be sure I heard I shouldn't upgrade further to Kit-Kat as there isn't a unlocked bootloader exploit yet...correct? (Obviously if I was still unlocked, and not relocked it wouldn't be an issue)
Click to expand...
Click to collapse
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot. 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
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
cmlusco said:
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
Click to expand...
Click to collapse
YAY!!!! That worked
:good:
Thank you for all of your help!! I really appreciate it, I knew there was probably a way to get a custom recovery installed, I just had run out of plays in my own knowledge book!!
I will now be able to do a nandroid b/u and get rid of the stupid sense Blinkfeed, belch! lol
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(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: FA446WM02874
(bootloader) imei: 352628060329457
(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
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
twill1987 said:
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(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: FA446WM02874
(bootloader) imei: 352628060329457
(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
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
Click to expand...
Click to collapse
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
twinnfamous said:
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
Click to expand...
Click to collapse
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
twill1987 said:
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
Click to expand...
Click to collapse
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
twinnfamous said:
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
Click to expand...
Click to collapse
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
twill1987 said:
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
Click to expand...
Click to collapse
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
x714x said:
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Edit: found one
http://www.htcdev.com/devcenter/downloads/P00
Just select T-Mobile as carrier and USA as region then you Wil see the latest ruu to download.
twinnfamous said:
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Click to expand...
Click to collapse
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
twill1987 said:
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
Click to expand...
Click to collapse
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
twill1987 said:
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
twinnfamous said:
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
Click to expand...
Click to collapse
I'll try to flash the latest Viper. The 1.6.0 it says everything flashed correctly, but gets stuck at the HTC boot screen.
I just flashed the 1.8.0 OTA update and everything installs but it sticks at the boot screen.
I see the 2.2.0 update is out so I'm downloading that now, I'll flash and see how it goes.
I'll update, thanks for your help!
Ruu requires the bootloader be locked
Sent from my HTC One_M8 using XDA Free mobile app
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.
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.
So, like I found in another threads my old phone, has not sound at all. I tried to fix it years ago, with not luck, but I wanna give it another chance since still it's a great phone.
This is my getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing. It's UNLOCKED.
If anyone would give me a hand with this, would be awesome.. since my actual phone is broke, like my wallet. :crying:
Thanks! :fingers-crossed:
Stranyer said:
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing.
Click to expand...
Click to collapse
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
redpoint73 said:
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
Click to expand...
Click to collapse
Hey thanks for replying!
I tried that, I keep getting this error
Code:
target reported max download size of 1826418688 bytes
sending 'zip' (1734001 KB)...
OKAY [ 49.344s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 112.683s
I tried doing a reboot and reinstaling.. but still getting error 12 :/
Any clue?
Stranyer said:
I tried that, I keep getting this error
Code:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
redpoint73 said:
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
Click to expand...
Click to collapse
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Stranyer said:
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Click to expand...
Click to collapse
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
redpoint73 said:
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
Click to expand...
Click to collapse
Sorry I took long time to reply.
I tried flashing the firmware, using htc_fasboot and fastboot. Both will give me this error.
Code:
c:\adb>htc_fastboot flash zip fw.zip
sending 'zip'... (53849 KB) OKAY
sending time = 2.408 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 5(s)
And still, won't flash RUU.zip
----
I retried a few more times, and it worked! It flashed firmware and ruu
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Stranyer said:
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Click to expand...
Click to collapse
Hard to tell exactly what you tried to do here, since you didn't include the actual command, name of the file you tried to flash, etc. Always include as much specific info as possible. "install a rom" is not sufficient info.
You tried flashing a custom ROM over fastboot? If so, that isn't the proper way to flash a custom ROM. You need custom recovery (TWRP) to do that. So that is the reason for "not allowed" (since it isn't).
But before doing so, we should look closer at the RUU (why it isn't booting) first. Since installing TWRP requires unlocking the bootloader, etc. Better to eliminate the RUU as a solution first, so we don't have to keep going back and forth unlocking/relocking bootloader.
Did the RUU finish successfully without any errors? If there were errors, what did it say specifically? If you don't know the answers to those questions, you can run the RUU again. Even cut/paste the output so we can look at it.