Develop Bugs

Please help me

Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:

ben33891471 said:
Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:
Click to expand...
Click to collapse
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.

xunholyx said:
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.
Click to expand...
Click to collapse
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0

ben33891471 said:
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime, flash this in recovery. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.

xunholyx said:
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime,flash this in recovery[/URL]. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.
Click to expand...
Click to collapse
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..

ben33891471 said:
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..
Click to expand...
Click to collapse
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery

xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
I'll use my sister gs4 to copy the rom to the SD card. Back to you soon with answer

xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
omg its says failed right away when i do "swipe to confirm flash".. what should i do?

ben33891471 said:
omg its says failed after 2 sec.. what should i do?
Click to expand...
Click to collapse
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
ben33891471 said:
omg its says failed right away when i do "swipe to confirm flash".. what should i do?
Click to expand...
Click to collapse
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.

xunholyx said:
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.
Click to expand...
Click to collapse
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?

ben33891471 said:
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?
Click to expand...
Click to collapse
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.

xunholyx said:
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.
Click to expand...
Click to collapse
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?

ben33891471 said:
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?
Click to expand...
Click to collapse
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.

xunholyx said:
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.
Click to expand...
Click to collapse
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?

ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8

ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..

xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
Allright thanx, this one is for AT&T, right?
Listen the download of the viperone rom just stop in 695 MB
I really dont know what to do, you think after ill put this TWRP recovery you just bring me, and try to flash revolution rom or used the backup it will work?
Even if i dont have s-off ?

xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
ahsan64 said:
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..
Click to expand...
Click to collapse
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this

ben33891471 said:
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this
Click to expand...
Click to collapse
what's not working.. ?
Or any error while installing rom .
Can you please show the commands how you are flashing recovery .

ahsan64 said:
what's not working.. "
Or error while installing rom .
Can you please show the commands how you are flashing recovery .
Click to expand...
Click to collapse
I type fastboot boot and then paste the file its done and restart but stock on the logo with the red words and when i tap on the screen there is vibrate but thats all
please help me bro i dont know what to do

[Locked Bootloader] [S-ON] twrp Recovery. Tester needed.

Update: don't do this!
Hei,
As I found out while flashing Firmware.zip and OTA Updates the whole signature verifying is done before flashing the 2PS6IMG.zip
While I cannot Flash unsigned/modified Firmware.zip on my Unlocked BL S-On device I could easily Flash any 2PS6IMG.zip even twrp.
So.... as this is the official way to update a phone(? Or not) (Yes, the Firmware.zip is renamed to 2PS6IMG.zip and placed onto the ext_sd) this might even work on a locked Bootloader?
Or at least it's worth a try.... right?
WARNING: This might Brick your device.
Don't do it if you are not ready for the consequences.
The file structure of the 2PS6IMG.zip is pretty easy....
Partition.img files and an android-info.txt
In this case I took the android-info.txt from an OTA and removed all except Recovery.img and replaced this with twrp.
There are 3 important lines you need to change in the Android-info.txt
Code:
modelid: 2PS620000
cidnum: HTC__621
mainver: 1.55.709.5
These need to be the same as your current ROM/CID/MID or else you can Flash the file.
Download file here:
Removed.
(It's TWRP 3.0.2-4 renamed as recovery.img, there was only one twrp for all devices yeah?)
You simply put the 2PS6IMG.zip in the root of your external SD Card and Boot Into Download Mode. A message Pops up "press volume up to flash" and then you wait
AntiBrickering:
Take an official Stock Recovery.img which you can extract from any ruu oder OTA.zip files Firmware.zip as a backup and create a second 2PS6IMG.zip on your computer so if your phone has bootloop or won't Boot Into recovery you can take out microSD Card and replace the file, and flash the original Recovery back.
Make sure an ruu.exe exists for your device as a last instance. You might still lose all internal data.
Why all this?
Well... if it works We have a recovery on Locked Bootloader. This would also mean superuser could be flashed
Afaik that's not yet possible.
So.... good luck.

That would be great as we should get OTA the official way while rooted, but I would be surprised that it works, TWRP needs access to the bootloader

Haldi4803 said:
Why all this?
Well... if it works We have a recovery on Locked Bootloader. This would also mean superuser could be flashed
Afaik that's not yet possible.
So.... good luck.
Click to expand...
Click to collapse
Is it possible to boot with the TWRP recovery (not flash it, just boot with it) like this:
Code:
fastboot boot twrp.img
Then flash SuperSu.zip
Does it work and does it give root on a locked bootloader and stocked ROM?

I thought fastboot Boot command would not work on m10 ???

Haldi4803 said:
I thought fastboot Boot command would not work on m10 ???
Click to expand...
Click to collapse
Looks like it
What are the other options to root without unlocking the bootloader then (just root, no custom ROM)?

You can't flash unsigned zips on an S-ON/LOCKED device. Even if you magically could (you can't), an S-ON/LOCKED phone will refuse to BOOT an unsigned boot or recovery image.
--beaups

Can someone please tell Darwin to come home when he's done?

beaups said:
an S-ON/LOCKED phone will refuse to BOOT an unsigned boot or recovery image.
Click to expand...
Click to collapse
Knew there had to be a check somewhere... so its at Boot. Thx.

Haldi4803 said:
Knew there had to be a check somewhere... so its at Boot. Thx.
Click to expand...
Click to collapse
And also at flash. Like I said, you can't flash unsigned zips.

I surely can with S-On Unlocked Bootloader.
Tought the check would be from S-On Feature which prevents flashing unsigned stuff and not locked Bootloader?

You cannot flash unsigned zips with locked/s-on.

beaups said:
You cannot flash unsigned zips with locked/s-on.
Click to expand...
Click to collapse
There's a disconnect here. He thinks packing recovery and boot images in a zip and flashing it is the same as flashing unsigned zips...

It is. You can't flash "your own" zip on a device that is s on and locked.

beaups said:
It is. You can't flash "your own" zip on a device that is s on and locked.
Click to expand...
Click to collapse
Yes. I missed the "locked" part in your post.
He's unlocked though and flashing bits of firmware in homemade zips rather than just flashing the complete signed packs from HTC. Which doesn't make a whole lot of sense to me, but to each their own, I guess.

I'd like to STRONGLY suggest that no one flashes this zip, holy heck. If those commands work, that phone will never boot again.
Code:
Jons-Mac-Pro:10twrp jcase$ cat android-info.txt
modelid: 2PS620000
cidnum: HTC__621
mainver: 1.55.709.5
hbootpreupdate:1
nohardreset: 1
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: slpi
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: xbl
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: rfg_2
eraseonflash: rfg_3
eraseonflash: sp1
eraseonflash: cota
eraseonflash: devcfg
eraseonflash: cmnlib32
eraseonflash: cmnlib64
eraseonflash: keymaster
eraseonflash: lksecapp
eraseonflash: apdp
eraseonflash: msadp
eraseonflash: venus
Haldi4803 said:
Hei,
As I found out while flashing Firmware.zip and OTA Updates the whole signature verifying is done before flashing the 2PS6IMG.zip
While I cannot Flash unsigned/modified Firmware.zip on my Unlocked BL S-On device I could easily Flash any 2PS6IMG.zip even twrp.
So.... as this is the official way to update a phone(? Or not) (Yes, the Firmware.zip is renamed to 2PS6IMG.zip and placed onto the ext_sd) this might even work on a locked Bootloader?
Or at least it's worth a try.... right?
WARNING: This might Brick your device.
Don't do it if you are not ready for the consequences.
The file structure of the 2PS6IMG.zip is pretty easy....
Partition.img files and an android-info.txt
In this case I took the android-info.txt from an OTA and removed all except Recovery.img and replaced this with twrp.
There are 3 important lines you need to change in the Android-info.txt
Code:
modelid: 2PS620000
cidnum: HTC__621
mainver: 1.55.709.5
These need to be the same as your current ROM/CID/MID or else you can Flash the file.
Download file here:
https://drive.google.com/file/d/0BwqG3liwGXQHdWpycHp0S2hyZEU/view?usp=drivesdk
(It's TWRP 3.0.2-4 renamed as recovery.img, there was only one twrp for all devices yeah?)
You simply put the 2PS6IMG.zip in the root of your external SD Card and Boot Into Download Mode. A message Pops up "press volume up to flash" and then you wait
AntiBrickering:
Take an official Stock Recovery.img which you can extract from any ruu oder OTA.zip files Firmware.zip as a backup and create a second 2PS6IMG.zip on your computer so if your phone has bootloop or won't Boot Into recovery you can take out microSD Card and replace the file, and flash the original Recovery back.
Make sure an ruu.exe exists for your device as a last instance. You might still lose all internal data.
Why all this?
Well... if it works We have a recovery on Locked Bootloader. This would also mean superuser could be flashed
Afaik that's not yet possible.
So.... good luck.
Click to expand...
Click to collapse

jcase said:
I'd like to STRONGLY suggest that no one flashes this zip, holy heck. If those commands work, that phone will never boot again.
Click to expand...
Click to collapse
That's the original android-info.txt taken from the OTA....
But as people are saying it SHOULD not be possible to flash this.

Haldi4803 said:
That's the original android-info.txt taken from the OTA....
But as people are saying it SHOULD not be possible to flash this.
Click to expand...
Click to collapse
Right, but its directing it to erase partitions that are not included in the zip, lucky HTC is wise enough not to follow through.
No they are saying it is possible, however not if S-ON. Even if it were possible when s-on, your phone wouldnt boot it.

Is my HTC 10 another Brick for the USA-MEX wall?

Hi Guys! I appreciate any help or orientation to find out how should I proceed,
I don't know why my phone just got Brick yesterday, it was running fine for two months since the last Room's flash, suddenly I notice an estrange behavior of the system, then the capacitive buttons were not responding nor its backlit appear when I touch them, the home button and the fingerprint and everything else was working fine, so I think that with a simple Reboot it will be back to normality. For my disgrace, it enter in a Bootloop in the HTC logo screen and for my surprise when I manage to get to the Bootloader and try to enter to the Download and Recovery mode get me to the same HTC logo Bootloop!!
The principal suspect for me is that like 15 days ago a installed the TotallyFreeVPN app to see some Japanese Netflix
To complicate the things I want to make my phone thefts proof, so I disable usb debugging and OEM unlocking and installed Cerberus with the option of block usb debugging and also in security I enable the encrypted data option for every reboot or when enter in recovery.
My only hope is that you know if something can be done from the Bootloader to unbricked?
I attach the only two screens I have access right now
HTC 10
Firmware 2.41.401.4
Leedroid V3.6.1
Unlocked Bootloader
S-OFF
TWRP 2.8.4
I manage to run some fastboot commands from Bootloader, getvar all give me the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT64EBN02616

flash a stock ruu

If your phone will still power on, it's not bricked.

BrianKuo1853 said:
flash a stock ruu
Click to expand...
Click to collapse
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:

ALOMAJEMO said:
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
Click to expand...
Click to collapse
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on

Yeah and use the full version, not the NoWipe...

I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.

j to the 4n said:
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Click to expand...
Click to collapse
Sneakyghost said:
Yeah and use the full version, not the NoWipe...
Click to expand...
Click to collapse
Thank for your tips guys,
I follow exactly the order you suggest my good j to the 4n, and I download the firmware from your useful thread Sneakyghost, but still, I can not get it out of the Bootloop my friends
Dont you think my case is very strange?
If it serves for any other suggestion, I I add the following details
-The only image that is not flashing is rcdata, everything else is flashing OK
-I buy a microsd card class 10 of 32GB only to discard that the old microsd card of 3GB was not reading the RUU zip file.
-I optained the zip file, from the RUU.exe with the same version of the firmware 2.41.401.4 (the full version) and I copying it from the Temp files in Windows.
-With the microSD in FAT32 format I put the RUU zip file with the 2PS6IMG.zip name
-After flashing all the img files and rebooting to bootloader, then I inserted the card and select Download mode, where is supposed should appear the screen that jichuan89 mention to flash the RUU, but again nothing happen.
-Also I should say that I try also with the firmware and RUU version 2.41.617.3 (the corresponding for my model 2PS6500 in the back) but the last I have was the 2.41.401.4 with superCID and cidnum change it to HTC-001.
-And also among the hundreds of attempts I have executed fastboot erase userdata, erase cache, erase system, to try to clean any corrupt file.
Do you think there is any hope yet?
Once again thank you for your support guys!:good::good:

singlemalt said:
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
Click to expand...
Click to collapse
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL

ALOMAJEMO said:
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
Click to expand...
Click to collapse
Haha...we have two bricks for the wall now...do you know if Donald would cover shipping costs from Argentina?

curious if anyone know how to view the firmware if cannout access downlad mode

venom55521 said:
curious if anyone know how to view the firmware if cannout access downlad mode
Click to expand...
Click to collapse
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........

Mr Hofs said:
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Click to expand...
Click to collapse
my bad,i was looking around for info and ideas and just had a question when i was reading it

venom55521 said:
my bad,i was looking around for info and ideas and just had a question when i was reading it
Click to expand...
Click to collapse
Please pick up a sledgehammer and smash your device....... it's the best for all of us.

Mr Hofs said:
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Click to expand...
Click to collapse
i realize you help a lot people out which is appreciated ,but being rude is pointless

venom55521 said:
i realize you help a lot people out which is appreciated ,but being rude is pointless
Click to expand...
Click to collapse
Your interpretation of the situation. I'm honest, not rude.

Bricked boot loop HTC M9 - Help me XDA developers you're my only hope!

I have an HTC One M9. It used to have Venum's Viper OS installed. Then about a week ago it began to update all the google apps, consequently they would then regularily but randomly close. It was annoying but I was living with it until I had the time to google what the cause/solution may be.
However the other day I was forced to reboot my phone and discovered that it would not boot. I got the initial white HTC screen with the red build notice at the bottom as usual then it would start the boot animation but would then freeze and reboot. Essentially it was stuck in a reboot loop.
I tried booting into TWRP and clearing the Cache - No change
I tried a full factory reset - No change
I tried flashing the viper rom again - It appeared to go well but when it came to the reboot I was back at sqaure one.
Ok getting desperate now I tried flashing the system.img and boot.img from TWRP - The behavior remained.
Then I made what I believe to be a real mistake and flashed what I think was a stock recovery.img
This left me in a real mess.
I can boot into the bootloader. It is unlocked and S-ON.
If I select reboot to download mode it fails with a nice red message.
I can select recovery mode but it will slip back into the reboot loop.
To actually get into recovery I have to select reboot to bootloader and once it's rebooted and back on the bootloader screen I can the select recovery mode.
Once in recovery mode I have some very limited options.
Apply update from ADB - I've been unable to get this to work
Wipe data/factory reset - This works but doesn't fix anything
Wipe cache partition - This works but doesn't fix anything
Reboot to bootloader - This works
Power Down - Also works
View recovery logs - Yep loads of technical gumf I don't really understand
Apply from phone storage / Apply from SD card
At the bottom of the recovery mode screen in yellow I have a number of error messages. Something like
E;missing bitmap oem_unlock_bg
(code -1)
E;missing bitmap oem_unlock_bg_yes
(code -1)
E;missing bitmap oem_unlock_bg_no
(code -1)
handle_cota_install: install cwpkg to /cota/cwpkg.zip
handle_cota_install: install cwprop to /cota/cw.prop
E:Fail to open file /sys/devices/platform/android_usb/host mode
Write host_mode error
handle_cota_install: no CW files. Skip cw installation.
I have ADB/Fastboot however...
Fastboot oem lock fails as does fastboot flashing lock
Attempts to fastboot flash the TWRP recovery back fail due to the S-ON state.
Fastboot getvar all shows the following but no CID or MID info
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA5B5YJ01037
all:
finished. total time: 0.133s
htc_fastboot finished. total time: 0.351s
I've tried connecting the device to laptop and running RUU update utility from HTC but it either cannot connect or it reports a battery state of less than 30% (when I know it's fully charged).
I read somewhere that you can flash an RUU by putting it on the SD card and rebooting into the bootloader but I've not had any luck with this yet. It maybe that I'm not using the right RUU without being able to gather the CID or version numbers it's just guesswork.
I'm currently researching if it would be possible to get the recovery partition mounted to my Kali Linux laptop and use DD to flash the TWRP image back on but so far I've found nothing suggesting that this would be possible.
Apologies for such a long post but I wanted to paint as detailed a picture of my current hell as I could. I suspect this maybe a case of NAND death. If so does anyone know if replacing the mainboard will resolve the issues?
I'm running out of options here but I'm determined. I just need help with my next move. Any suggestions are welcome.

You dont have "allow oem unlock" enabled in settings/developer. If you got that fastboot result from download mode then the phone is dead.
S-on is restricting you from flashing system.img.
You need to flash back to stock following flippy's thread in the general section stickies. As flippy will tell you, you've saved yourself a lot of pain by staying s-on but it could also be your undoing.
Good luck!.
Beamed in by telepathy.

@shivadow
According to the OP the bootloader is already unlocked. And as already written in the S-OFF thread here in the Q&A section you don't need S-OFF for restoring a system image. Aside from that, the shown fastboot getvar result is the normal result that you get if you use that command while the phone is booted to the bootloader instead of the download mode. (The OP states that booting to the download mode isn't possible.)
All in all the whole situation has nothing to do with being S-ON or S-OFF since it's simply a hardware failure ("the dead nand issue"). Even with S-OFF you couldn't save this phone. And no, this issue has nothing to do with the custom rom that got used on the phone since it can happen on a stock, never modified phone, as well. There just seem to be some units that suffer from bad hardware.
@mikegrimwade
Your assumption is correct, as far as I can tell. Your issue seems to be a dead nand. Changing the mainboard is probably the only solution for the problem since I haven't seen anyone being successful with repairing such a dead phone just by flashing some files. All repaired phones that I've heard from got sent to HTC and they all came back to their owners with a replaced mainboard.
A little sidenote: The SD card method requires a working download mode not a working bootloader that's why you couldn't use that method. (That requirement actually applies to all RUU flashing methods.)
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
@shivadow
According to the OP the bootloader is already unlocked. And as already written in the S-OFF thread here in the Q&A section you don't need S-OFF for restoring a system image. Aside from that, the shown fastboot getvar result is the normal result that you get if you use that command while the phone is booted to the bootloader instead of the download mode. (The OP states that booting to the download mode isn't possible.)
All in all the whole situation has nothing to do with being S-ON or S-OFF since it's simply a hardware failure ("the dead nand issue"). Even with S-OFF you couldn't save this phone. And no, this issue has nothing to do with the custom rom that got used on the phone since it can happen on a stock, never modified phone, as well. There just seem to be some units that suffer from bad hardware.
@mikegrimwade
Your assumption is correct, as far as I can tell. Your issue seems to be a dead nand. Changing the mainboard is probably the only solution for the problem since I haven't seen anyone being successful with repairing such a dead phone just by flashing some files. All repaired phones that I've heard from got sent to HTC and they all came back to their owners with a replaced mainboard.
A little sidenote: The SD card method requires a working download mode not a working bootloader that's why you couldn't use that method. (That requirement actually applies to all RUU flashing methods.)
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy498 it is as I feared. I'm not afraid to open the device to replace the mainboard but I'd hoped to avoid it. Can anyone advise where I can get replacement mainboard for the M9? Also will it matter which board I get as I understand there are different boards US, Europe etc?

Look at the bottom of the backside of your phone. There should be a small engraving which states the Model ID of your phone (0PJA***). Compare that one with the MIDs that are mentioned in the first post of the ReadMe thread and you'll know which hardware variant you own. Just be aware that the engraving lacks two zeros if you compare it with the MID that you get from fastboot getvar. You should at least avoid trying to use a CDMA mainboard with a GSM phone or vice versa. I'm not sure whether you can use a US GSM mainboard with a European device or vice versa (c.f. the next paragraph).
Fortunately for me/unfortunately for you, I didn't have to replace any parts of my M9 or my older One S, yet. Therefore, I can't recommend any sellers because I don't have any experiences with them.
Sent from my HTC One M9 using XDA Labs

Htc one m8 bootlooped after flashing SuperSU v2.02 on TWRP v3.0.0-0

Help me , I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access(it wasn't the pro version), so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop. the phone is rooted/unlocked, access to recovery, no access to adb/fastboot because my phone wont connect to the pc.
does anyone know a fix to this? Pretty desperate because this is the only phone I got.

also I was stupid enough not to have a backup saved :/ I tried everything... formatting from bootloader, wiping phone in recovery.. nothings working.

You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.
braydenp said:
so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop.
Click to expand...
Click to collapse
In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.
Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).
braydenp said:
I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access
Click to expand...
Click to collapse
Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.
The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/

redpoint73 said:
You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.
In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.
Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).
Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.
The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/
Click to expand...
Click to collapse
I slight had a feeling that's why firewater wasn't working xD. I guess sunshine is the only way... well,.. i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things. I gotta somehow find a 4.20.666.2 backup zip to flash(if there's even any on the internet) :/

braydenp said:
I guess sunshine is the only way
Click to expand...
Click to collapse
No guesswork here. Sunshine is the only way.
Unless you count spending $150+ on a javacard. Which of course makes no sense, when sunshine costs $25.
braydenp said:
i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things.
Click to expand...
Click to collapse
If you wiped "system" in the TWRP "Advanced" wipe section, then you wiped the OS, and therefore (somewhat obviously) have no OS to boot.
If you were wiping things, without knowing what they are, or what the result would be; then that behavior needs to stop immediately!
Also, another good basic rule of thumb (good common sense on any Android device) is not to do any mods (root, custom ROM, etc.) without first knowing how to return to stock.
You can return to stock by using the guide and files in the following thread. Important to note, that these are not flashable zips. You need to follow the instructions carefully, extract the files and save them to the proper location on the phone, then boot TWRP and Restore (not Install like a ROM or other flashable zip): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

I did give that a try earlier.. my only problem is, I Haven't been able to connect to adb/fastboot ever since I got into the bootloop(probably because I can't get past reboot), not even mount usb storage, nor does adb sideload works, how can I get adb to work so i can return to stock?

braydenp said:
i tried that kind of... my only problem is, I cant connect to adb/fastboot(adb devices wont work in cmd) ever since I got into the bootloop. mount usb storage doesn't work, nor does adb sideload, how can I get adb to work so i can return to stock?
Click to expand...
Click to collapse
Make sure you are in the correct mode:
Fastboot only works in bootloader-fastboot mode.
adb only works in OS (not an option, in the current condition) or in TWRP.
You should also be able to access the phone's internal storage (and SD card, if you have one) on your PC, when phone is booted to TWRP. In which case, you can copy the needed TWRP stock backup files to internal storage or SD.

i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?

oh wait nvm found it, it was in barcode

braydenp said:
i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?
Click to expand...
Click to collapse
You mean, for the purpose of putting the TWRP backup folder in the right place?
If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.
It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.

redpoint73 said:
You mean, for the purpose of putting the TWRP backup folder in the right place?
If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.
It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.
Click to expand...
Click to collapse
Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it, & ty for pointing out that the boot stuff goes into the recovery.img folder

nvm about the extra folder i just added the system 'n data stuff in the recovery folder and its working now. thank you for helping me
:victory: on step 11 now pretty much done, ty )

huh... :/ the fastboot flash recovery x.xxx.xx.x_recovery.img command ain't working in fastboot

i got the fastboot flash recovery to work, ran it, rebooted to get ota's but nothing came, still no OS i guess because its still stuck in bootloop and after doing all of that, twrp is gone.

yeah, no OTA's, installed twrp again and it gets rid of twrp when i run the flash recovery file in fastboot then no ota's afterwards... i wonder if its because im running the recovery.img file from the sdk/adb file location instead of twrp/backup/serialno./... on the device, is that where I'm going wrong or is it something else? the boot, system and data files installed nicely though

braydenp said:
Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it
Click to expand...
Click to collapse
Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.
braydenp said:
ty for pointing out that the boot stuff goes into the recovery.img folder
Click to expand...
Click to collapse
The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img
Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).
recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).
---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------
braydenp said:
i got the fastboot flash recovery to work . . . and after doing all of that, twrp is gone.
Click to expand...
Click to collapse
The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.
Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?

redpoint73 said:
Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.
The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img
Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).
recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).
---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------
The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.
Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?
Click to expand...
Click to collapse
When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's.
fastboot wont reach my phones internal storage twrp/backups/SerialNO./Recovery.img when i try flashing with the recovery.img in my phones storage. i got all the paths set up properly for fastoot/abd.. why wont it reach unless i have the recovery.img in sdktools folder on my pc? after i flash the recovery.img from sdkfile no OTA's are popping up after the phone reboots

error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img

braydenp said:
When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's, fastboot wont reach the twrp/backups/SerialNO./Recovery.img on my phones internal storage when i try flashing it. i got all the paths set up properly for fastoot/abd.. why wont it work unless i have the recovery.img in sdktools folder on my pc?
Click to expand...
Click to collapse
Fastboot is for flashing a file from your computer, to your phone. I've never seen anyone try to fastboot flash a file that resides on the phone's SD or internal storage; I don't think you can do that, nor is there a reason to do so.
Not receiving OTAs is not a problem with how you have stock recovery installed. If you have the right recovery (matches the TWRP, and it's installed, and matches the firmware) then the problem is somewhere else. Might just be a bug in the OTA system.
I'd like to verify you are restoring the right version number TWRP backup, and the right number recovery. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------
braydenp said:
error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img
Click to expand...
Click to collapse
Not a valid way to run the fastboot command, as already mentioned. The file should be on the computer, not on the phone.
Let me try to explain it in simple terms:
TWRP: Makes backup files of the ROM and kernel (boot.img), and can restores those. These backup files are saved to the phone's internal storage or SD. By moving/copying the files from the stock backup collection, you are "tricking" TWRP into thinking it is a backup that you made with TWRP. Everything is done by the phone, the computer is just used to move the files to the phone.
Fastboot: Use fastboot to replace TWRP with the "stock" recovery, which is required for OTA. The file and tool (fastboot) reside on the computer.

(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: 4.20.666.2
(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: BM___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: c7c8c7ac
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
alright, well my only problem now it getting the OTA's, everything is setup like in the tutorial proper versions for my OS...