Develop Bugs

Verizon HTC one stuck in bootloader with s-on

So I'm fairly new to the rooting scene. I had clockworkmod installed and I was unlocked and s-off. There were some weird google sync issues that popped up and I tried a factory reset. It still didn't fix the issues, so I decided to take it back into verizon, but I wanted to get it relocked. so I installed the stock recovery got relocked and s-on. I tried once more for a factory reset and I got stuck in the bootloader with the locked and security warning flags showing. Am I completely out of luck or is there a way that I've missed to get s-off again?

Unlock the bootloader again, then flash twrp or cwm recovery, then flash a rom. Then use firewater to get s-off. Alternativley you could do an ruu, and then use firewater to get unlocked and s-off.

cmlusco said:
Unlock the bootloader again, then flash twrp or cwm recovery, then flash a rom. Then use firewater to get s-off. Alternativley you could do an ruu, and then use firewater to get unlocked and s-off.
Click to expand...
Click to collapse
I appreciate the reply but I just need a little more direction on the first step. I believe rumrunner won't complete because when it tries to reboot the phone to run adb commands it can't since the phone is stuck in the bootloader. When I try to flash a new recovery (be it cwm or twrp) in fastboot the flash fails @ the bootloader signature check. I'm not really sure what that means, but I get it everytime.
Also, I have't found any RUU that is for a Verizon phone. I'm not sure that others will work.
Reading over your reply one more time I think I just need to get that bootloader unlocked, then I can try out everything else but I'm hitting a wall. Any more insight into that?

When you originally unlocked it did you use htcdev to do it? If so they gave you and unlock_token.bin file, do you still have it on your pc somewhere, possibly where fastboot is? If you didnt use htcdev you can try to now http://www.htcdev.com/bootloader. Select all other supported devices in the drop down box on the side, then follow the instructions to try to unlock the bootloader again.

Unfortunately I didn't use htcdev, and the One isn't a supported device anymore. Or at least doesn't seem to be - I get an error:
Error Code: 160.
Error Reason: MID Not Allowed.

Ah that sux. Well you need to try to ruu then, but im having trouble finding the right one. Do me a favor and type this using fastboot
Code:
fastboot getvar all
and post what it outputs here.

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 1.12.41.1112_2
version-cpld: None
version-microp: None
version-main: 2.10.605.1
version-misc: PVT SHIP S-ON
serialno: ***
imei: ***
meid: ***
product: m7_wlv
platform: HBOOT-8064
modelid: PN0731000
cidnum: VZW__001
battery-status: good
battery-voltage: 4264mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-3c88cdd7
hbootpreupdate: 11
gencheckpt: 0

Ok let me look for the rigjt ruu. Also remove your serial ime and meid from that post. Not something you want people to know.

Ok well i got some bad news. I cant find a 2.10.605.1 ruu. I can find older ones but that dosent help, since a s-on hboot wont allow you to downgrade. Im stumped at what to do at this point. Hopefully the correct ruu will be available soon. Mabey someone smarter than me has some other ideas.

Ah, well... hopefully they can come out with it soon I really appreciate you looking into it!

I'm in the same boat. Unsure what to do as I need a phone.

I found a decrypted one, but that wont work with s-on. ?
But if there is a decrypted one, that means there must be a signed one somewhere. I will keep looking.

If you still need the signed 2.10.605.1 RUU.... PM me.. I'll get santod to add link to his thread

Yea you need an encrypted version of the same software build you were on. You can't ruu to a lower version since you are s on. But if you are boot loader locked you won't be able to flash anything.
If you can get the encrypted signed ruu from somewhere you could possibly boot to ruu mode and flash that. Then use firewater to unlock and get s off.
Sent from my HTC6500LVW using Tapatalk 2

Where might i find the correct encrypted signed ruu?

As far as I know only HTC has them and they used to be available here but not any more. See if flyhalf has it somehow.
If you are s on though I'm unsure if you can flash it. But it's worth a try as long as it's the encrypted version and signed...that way all the stock files match the partitions and files on your device currently.
Sent from my HTC6500LVW using Tapatalk 2

Flash a rom in an unlocked bootloader with an on the go external sd card.
Sent from my Galaxy Tab 10.1

Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed

cmlusco said:
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed
Click to expand...
Click to collapse
Nice, thanks for this. I can flash this too right even if I'm s off? Going to download it and keep it in case I ever need to ruu.
Sent from my HTC6500LVW using Tapatalk 2

Yes even if your s-off.

[Q] wifi issue with 3.28.401.7

Hi,
version-bootloader: 3.18.0.00
version-baseband: 1.19.213311
version-cpld: None
version-microp: None
version-main: 2.26.73.2
version-misc: PVT SHIP S-ON
CID: ORANG202
I tried to install the One_M8_3.28.401.7_odexed.zip, but now I lost the wifi.
I can't update the firmware because I can't s-off, or maybe I don't know how.
What can I do to fix this issue ? install an old version or the orange version ?
Thank you for your help,
Regards,

k4mik4zi42 said:
Hi,
version-bootloader: 3.18.0.00
version-baseband: 1.19.213311
version-cpld: None
version-microp: None
version-main: 2.26.73.2
version-misc: PVT SHIP S-ON
CID: ORANG202
I tried to install the One_M8_3.28.401.7_odexed.zip, but now I lost the wifi.
I can't update the firmware because I can't s-off, or maybe I don't know how.
What can I do to fix this issue ? install an old version or the orange version ?
Thank you for your help,
Regards,
Click to expand...
Click to collapse
Your version-main is your firmware. You are still on 2.26.xxx. The 3.28.401.7 that you see in settings > about phone is the ROM base (software version). You need to either update your firmware to 401.7 or later (actually 401.6 will work too, but I don't want to be confusing), or use a 4.4.3 based ROM for your wifi to work. There are tutorials all over XDA, but since you are S-On, you will probably have to run the 4.4.4 RUU in fastboot.
You can download the RUU here.

xunholyx said:
Your version-main is your firmware. You are still on 2.26.xxx. The 3.28.401.7 that you see in settings > about phone is the ROM base (software version). You need to either update your firmware to 401.7 or later (actually 401.6 will work too, but I don't want to be confusing), or use a 4.4.3 based ROM for your wifi to work. There are tutorials all over XDA, but since you are S-On, you will probably have to run the 4.4.4 RUU in fastboot.
.
Click to expand...
Click to collapse
Hi,
I relocked the phone, but now I have the error : Error 131 customer id error.
CID: ORANG202
Thank you,

k4mik4zi42 said:
Hi,
I relocked the phone, but now I have the error : Error 131 customer id error.
CID: ORANG202
Thank you,
Click to expand...
Click to collapse
Go to this thread.
Find the stock ROM and recovery backups there for your phone. The thread explains how to find them.
Once you get back to stock you can take the OTAs to update your firmware.

xunholyx said:
Go to this thread.
Find the stock ROM and recovery backups there for your phone. The thread explains how to find them.
Once you get back to stock you can take the OTAs to update your firmware.
Click to expand...
Click to collapse
Hi,
The wifi is back.
Thank you for your help and your time,
Regards,

Problem with htc one m8 ota

I tried upgrading my HTC one m8 by RUU but keep getting this error 155 wrong RUU used....
my phone is:
S-off
bootloader locked
CID version supercid 1111111
I tried using fastboot method,.zip method but nothing works

BruceWayne16594 said:
keep getting this error 155 wrong RUU used....
Click to expand...
Click to collapse
In order to troubleshoot this, we need to know what RUU you are trying (exact file name).
SuperCID is not enough, you need to also match MID in order to run RUU.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also, your title says "OTA" but your post says "RUU". Confirm its RUU you are talking about? RUU and OTA are 2 very different things, with very different requirements, so you need to clarify here.

redpoint73 said:
In order to troubleshoot this, we need to know what RUU you are trying (exact file name).
SuperCID is not enough, you need to also match MID in order to run RUU.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also, your title says "OTA" but your post says "RUU". Confirm its RUU you are talking about? RUU and OTA are 2 very different things, with very different requirements, so you need to clarify here.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.08.20.0916
version-cpld: None
version-microp: None
version-main: 2.16.654.4
version-misc: PVT SHIP S-OFF
meid: 99000499079516
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 8a0f02ff
hbootpreupdate: 11
gencheckpt: 0
Yeah i'm talking about RUU
Ruu version (tried both)
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4

BruceWayne16594 said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
Click to expand...
Click to collapse
Since you have the Sprint version, you should not try to use this RUU. The Sprint version has different partitioning than other M8 versions. Trying to flash any firmware or RUU besides Sprint can result in a radio brick.
Error 155 is common when trying to flash MM RUU on any device that is currently on LP (or in your case KK) firmware. Fastboot flash the 6.20.651 .3 firmware from the following thread, then try the RUU again: http://forum.xda-developers.com/showthread.php?t=2729173
Also, it looks like you have the Harmon Kardon variant (654 version numbers, versus 651 for non-HK Sprint). But I think 6.20.651 should still work. Otherwise, use the 6.20.654.3 firmware, then the 6.20.654.3 RUU.

redpoint73 said:
Since you have the Sprint version, you should not try to use this RUU. The Sprint version has different partitioning than other M8 versions. Trying to flash any firmware or RUU besides Sprint can result in a radio brick.
Error 155 is common when trying to flash MM RUU on any device that is currently on LP (or in your case KK) firmware. Fastboot flash the 6.20.651 .3 firmware from the following thread, then try the RUU again: http://forum.xda-developers.com/showthread.php?t=2729173
Also, it looks like you have the Harmon Kardon variant (654 version numbers, versus 651 for non-HK Sprint). But I think 6.20.651 should still work. Otherwise, use the 6.20.654.3 firmware, then the 6.20.654.3 RUU.
Click to expand...
Click to collapse
I already have the .zip version of the Ruu used , should i use that??

Thanks,
i succesfully flashed the firmware and rebooted but then the phone got stuck at splash screen.... pls help

BruceWayne16594 said:
I already have the .zip version of the Ruu used , should i use that??
Click to expand...
Click to collapse
Firmware and RUU are not the same thing; which is the very reason I've advised to flash the firmware, then the RUU.
Firmware is a small but critical zip package that contains several modules, including hboot, radio, and a few others. Once you install the firmware, the RUU should run properly to update all the remaining partitions.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
BruceWayne16594 said:
Thanks,
i succesfully flashed the firmware and rebooted but then the phone got stuck at splash screen.... pls help
Click to expand...
Click to collapse
You didn't follow my instruction, to flash the firmware, then try the RUU again. As I just mentioned above, RUU and firmware are not the same, and are 2 very different things.

Solved
redpoint73 said:
Firmware and RUU are not the same thing; which is the very reason I've advised to flash the firmware, then the RUU.
Firmware is a small but critical zip package that contains several modules, including hboot, radio, and a few others. Once you install the firmware, the RUU should run properly to update all the remaining partitions.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
You didn't follow my instruction, to flash the firmware, then try the RUU again. As I just mentioned above, RUU and firmware are not the same, and are 2 very different things.
Click to expand...
Click to collapse
Thanks,
I flashed the firmware follwed by the RUU as mentioned by you, this time following each thing very carefully and ................IT WORKS!!!!!!!!!!!
Thanks a lot

You're very welcome. Happy you got it sorted out.

Lineage & Rooted HTC 10 - Cellular/LTE Radio broken

Hi All,
Here's hoping someone can help as I've made no progress in solving this issue in the past few hours.
So some background, I've installed TWRP on my HTC and have been using Lineage OS. I unlocked the bootloader via HTC dev, it is still S-ON. All has been well until recently when I decided I'd like to try out the stock rom again - mostly I wanted the HTC camera features back. So I downloaded the TWRP backup for my phone from XDA (CID: HTC_039). I run the restore via TWRP but it will not boot, so I followed the rest of the guide and flashed the stock recovery then relocked the bootloader. But to no avail... now it's in a very quick boot loop.... Managed to get out of it and unlock the bootloader again and flash TWRP once more.
So at this point I'm happy to return to Lineage with the backup I made before starting. But after restoring my pin doesn't work... so I followed another guide and deleted some files in TWRP which solved it. But I can't get any signal now. Apparently this is an encryption issue. I've also tried 'format data' in TWRP which apparently removes encryption. But following this installing lineage OS from zip or restoring stock or lineage results in the same error.
I'm just about at my wits end... I'd be super grateful for any input
Thankyou

Hope fully not to soon to *bump*
I have no idea what to do, surely someone know more about this than I do?

debatingrooster said:
Hope fully not to soon to *bump*
I have no idea what to do, surely someone know more about this than I do?
Click to expand...
Click to collapse
Have you tried running an RUU for your device?
Try looking here:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page118

Tarima said:
Have you tried running an RUU for your device?
Try looking here:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page118
Click to expand...
Click to collapse
Hey Tarima I'm having a look at the link from the post at the top of that page, but how do I choose the right RUU? there's no CID mentioned in any of them?
Thanks

debatingrooster said:
Hey Tarima I'm having a look at the link from the post at the top of that page, but how do I choose the right RUU? there's no CID mentioned in any of them?
Thanks
Click to expand...
Click to collapse
You can go by your software version. Do
fastboot getvar all
from download mode and you'll know what yours is. You can only flash a version that's same or higher than your current one.

Tarima said:
You can go by your software version. Do
fastboot getvar all
from download mode and you'll know what yours is. You can only flash a version that's same or higher than your current one.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: Apparently should remove this
(bootloader) current-slot:
(bootloader) imei: Apparently should remove this too
(bootloader) version-main: 2.42.710.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__039
Is version main the one I'm interested in? 2.42.710.2?

Seems there's no RUU for my case, so I downloaded sunshine, thought I could s-off and run an older RUU. But apparently sunshine can't run on non-stock ROMs...

debatingrooster said:
Seems there's no RUU for my case, so I downloaded sunshine, thought I could s-off and run an older RUU. But apparently sunshine can't run on non-stock ROMs...
Click to expand...
Click to collapse
Sorry not sure how else to help. I don't think you're screwed though.

Tarima said:
Sorry not sure how else to help. I don't think you're screwed though.
Click to expand...
Click to collapse
No worries, Thanks for your help! I might try viper rom and see If I can run sunshine on that...
Hopefully not screwed, hardware should all still be fine in any case. Hopefully someone else can chime in with some ideas??

Happy days!!
Installing Team Venoms Viper ROM Fixed it. Good ROM too. It also remained working when Lineage OS was installed again.
It seemed to reenable encryption - I'm being prompted once more to enter my password in TWRP
Hopefully this helps anyone who might find themselves in the same situation

help me fast please! cannot install RUU.EXE OR ZIP (stucked on white screen logo)

hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
when i set up ruu.exe after two steps of the setup by click (next)..nothing happen!(although my htc m8 in the black and grey screen logo)
can you help me friends ?what can i do?by the easiest way.
thank you

audi19844 said:
hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
Click to expand...
Click to collapse
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.

redpoint73 said:
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.
Click to expand...
Click to collapse
Thank you for your importance,
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong

audi19844 said:
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong
Click to expand...
Click to collapse
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?

redpoint73 said:
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?
Click to expand...
Click to collapse
sorry for missing information .
- i tried to install ( [ROM][UNOFFICIAL] LineageOS 15.1 for HTC One M8 )
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
-my big fault also was not making backup for my stock rom.
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
the rom utility cannot update your android phone please get the correct rom utility and try again)
i tried to flash the ruu.zip by htc fastboot,and after many times it was succeeded to be flashed by htc fastboot
so this is my htc info
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4*********
(bootloader) imei: 3591970********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
thank you for your patience.

audi19844 said:
sorry for missing information .
Click to expand...
Click to collapse
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
audi19844 said:
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
Click to expand...
Click to collapse
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
audi19844 said:
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
Click to expand...
Click to collapse
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
audi19844 said:
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
Click to expand...
Click to collapse
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?

redpoint73 said:
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?
Click to expand...
Click to collapse
I would like to thank you for your big help, thank you very much
I successfully used Marshmallow RUU
and my phone is now ok.
I learned now what i shoud do next time before installing a custom rom.
Thank you again.