Hello all,
Newbie to the forum. I bought a refurbished HTC one M8 (European version), the phone was already rooted with super SU. I managed to install GPE 5.1 rooted version from GraffixNYC, though however when I checked for OTA update via software updates in the phone, there was an incremental update waiting for 23 MB (LMR1). When I tried to install to update, phone goes to the regular android update screen and goes into error (with the android logo). I tried a few times in vain.
Need your advice how do I get the OTA update back and running
Cheers.
Root, custom recovery (TWRP), and wrong ROM (not the ROM for your CID, MID) will all make the OTA fail.
Basically, your current setup is not suitable for OTA. You would need an unrooted stock (Sense) ROM that corresponds to your CID/MID, and stock recovery for OTA.
If your intent is to stay with GPE, your choices are:
1) Flash GPE ROM that incorporates the update, if/when that is available
2) S-off and "fully convert" the phone to GPE by RUU.
redpoint73 said:
Root, custom recovery (TWRP), and wrong ROM (not the ROM for your CID, MID) will all make the OTA fail.
Basically, your current setup is not suitable for OTA. You would need an unrooted stock (Sense) ROM that corresponds to your CID/MID, and stock recovery for OTA.
If your intent is to stay with GPE, your choices are:
1) Flash GPE ROM that incorporates the update, if/when that is available
2) S-off and "fully convert" the phone to GPE by RUU.
Click to expand...
Click to collapse
Thanks for the response.
I am quite new to all this. Sorry about it. But I know that I want to stay with GPE. My phone is S-OFF and I also unlocked the bootloader. Also changed the CID to GOOGL01 already. Only then I went ahead to flash the GPE ROM. Would you be able to help me with the steps of what should I be doing next to get regular OTA updates?
Perhaps is it something like this?
1. Change CID and Flash stock sense rom?
2.Change back CID to GOOGL01 and flash GPE non-rooted ROM this time?
3. With this I can check if OTA is successful?
Forgot to add I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything. Am I missing something?
Thanks again
My responses below in red font:
deeepraveen said:
I am quite new to all this. Sorry about it.
The absolute best thing to do when you are new to this, is to read and research, and read and research some more. Learn and understand, and gain a basic level of knowledge before modding the phone, or you can really get yourself into trouble. Especially with s-off, you can easily brick the phone if you do something wrong!
But I know that I want to stay with GPE. My phone is S-OFF and I also unlocked the bootloader. Also changed the CID to GOOGL01 already. Only then I went ahead to flash the GPE ROM.
Meaning you flashed a ROM zip in TWRP? Or you ran an RUU application from PC? If you flashed a ROM in TWRP, the steps you describe are odd, expensive, and unecessary (you don't need s-off or Google CID to flash a GPE ROM).
Would you be able to help me with the steps of what should I be doing next to get regular OTA updates?
Perhaps is it something like this?
1. Change CID and Flash stock sense rom?
2.Change back CID to GOOGL01 and flash GPE non-rooted ROM this time?
3. With this I can check if OTA is successful?
No, don't do this. Its overly complicated, and won't work, for a variety of reasons. Now that I understand you want to stay GPE (and with OTA updates) what you (in brief) want to do is:
a) Make sure you model ID (MID) is one of the acceptable ones listed in the thread: http://forum.xda-developers.com/showthread.php?t=2708589
b) RUU to "fully" convert the phone to GPE. You may need to flash the (MM GPE) firmware first (then RUU again) if you get Error 155. Flashing firmware is described in the same GPE RUU thread.
c) You should then be on official GPE Marshmallow; and get OTA update, if there is one.
Forgot to add I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything.
Again, I'm confused about whether you are trying to install a ROM or an RUU. ROM and RUU are very different things. A ROM isn't installed from the computer, you flash it in TWRP. What is the exact name of the file you are trying to install?
Click to expand...
Click to collapse
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.
redpoint73 said:
My responses below in red font:
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.
Click to expand...
Click to collapse
Thanks so much for that detailed explanation.
Please see my response below.
Meaning you flashed a ROM zip in TWRP? Or you ran an RUU application from PC? If you flashed a ROM in TWRP, the steps you describe are odd, expensive, and unecessary (you don't need s-off or Google CID to flash a GPE ROM)
---- I ran RUU from PC, basically the refurb phone was running 5.0.1 with some mod and rooted when it arrived. I went ahead and ran RUU from my PC and flashed 5.1 from graffix website after unlocking the bootloader thats all I did.
Please see my getvar all results and advise me further on what to do.
C:\Users\One M8\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.122s
C:\Users\One M8\platform-tools>
deeepraveen said:
---- I ran RUU from PC, basically the refurb phone was running 5.0.1 with some mod and rooted when it arrived. I went ahead and ran RUU from my PC and flashed 5.1 from graffix website after unlocking the bootloader thats all I did.
Click to expand...
Click to collapse
Okay, now I better understand what you did. Installing RUU is completely different from flashing a ROM, so avoid using the terms interchangeably, to avoid confusion:
Flash ROM: 2 partitions (system and boot.img) flashed in TWRP custom recovery
RUU: Complete system re-image, around 40 partitions, done by PC fastboot RUU mode or SD card method (again, in fastboot RUU mode). Cannot be installed by TWRP.
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
You can't OTA with root, so that is probably your main problem.
Installing the unrooted RUU 4.04.1700.6, then OTA is probably your best bet. And your current configuration looks okay to RUU.
deeepraveen said:
I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything.
Click to expand...
Click to collapse
This is a somewhat common issue. Try killing the process, and starting again. If the problem persists (stalls at "sending") try a different USB port or cable. Or try the SD card method (if you have an SD card) described in the GPE RUU thread as "Method 2".
You can also try one of the Marshmallow RUUs 5.07.1700.x, but if you get Error 155, you may need to flash the 5.07.1700 firmware first (also described in the GPE RUU thread) then run the RUU again.
redpoint73 said:
My responses below in red font:
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.
Click to expand...
Click to collapse
redpoint73 said:
Okay, now I better understand what you did. Installing RUU is completely different from flashing a ROM, so avoid using the terms interchangeably, to avoid confusion:
Flash ROM: 2 partitions (system and boot.img) flashed in TWRP custom recovery
RUU: Complete system re-image, around 40 partitions, done by PC fastboot RUU mode or SD card method (again, in fastboot RUU mode). Cannot be installed by TWRP.
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
You can't OTA with root, so that is probably your main problem.
Installing the unrooted RUU 4.04.1700.6, then OTA is probably your best bet. And your current configuration looks okay to RUU.
This is a somewhat common issue. Try killing the process, and starting again. If the problem persists (stalls at "sending") try a different USB port or cable. Or try the SD card method (if you have an SD card) described in the GPE RUU thread as "Method 2".
You can also try one of the Marshmallow RUUs 5.07.1700.x, but if you get Error 155, you may need to flash the 5.07.1700 firmware first (also described in the GPE RUU thread) then run the RUU again.
Click to expand...
Click to collapse
Thanks again, that did it. Flashed the 6.0 firmware, but still was unable to flash 6.0. However though I managed to flash non-rooted 5.1 instead and bingo. I got the OTA for 6.0. Works great.
Cheers.
Related
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.
Hi there, recently i bought used m8 and its android version is 4.4.3, it is made in ireland as htc said. It is s-off and has supercid 11111, It means previous owner customized this device. I need to know its orignal Cid and Mid so i will update it to marshmallow( since i am not receving ota updates), so please help me out what should i do...I also dont know it has stock rom/ recovery. Bootloader is locked. I guess it has stock recovery. I want any stock upgrade because this rom has many bugs like delaying messeges e.t.c. Thanks in advance
worgamerx said:
Hi there, recently i bought used m8 and its android version is 4.4.3, it is made in ireland as htc said. It is s-off and has supercid 11111, It means previous owner customized this device. I need to know its orignal Cid and Mid so i will update it to marshmallow( since i am not receving ota updates), so please help me out what should i do...I also dont know it has stock rom/ recovery. Bootloader is locked. I guess it has stock recovery. I want any stock upgrade because this rom has many bugs like delaying messeges e.t.c. Thanks in advance
Click to expand...
Click to collapse
Power off your phone, then boot it up by holding both the power button + vol down. This will take you to the bootloader. Post here what it says there. To navigate in the bootloader, use the vol keys to change selections, and the power button to select. You'll need to know that to select reboot.
xunholyx said:
Power off your phone, then boot it up by holding both the power button + vol down. This will take you to the bootloader. Post here what it says there. To navigate in the bootloader, use the vol keys to change selections, and the power button to select. You'll need to know that to select reboot.
Click to expand...
Click to collapse
Already mentioned:
CID:111111
S-Off
Bootloader is locked and i guess it have stock recovery.
Software number is: 2.11.708.2
I think rom is stock because it matchs with stock software number. But i want to upgrade so suggest me what should i do.
worgamerx said:
Already mentioned:
CID:111111
S-Off
Bootloader is locked and i guess it have stock recovery.
Software number is: 2.11.708.2
I think rom is stock because it matchs with stock software number. But i want to upgrade so suggest me what should i do.
Click to expand...
Click to collapse
Already mentioned where? Certainly not here. That CID means absolutely nothing.
And the ROM is stock because it matches with what? You have matched the OS version in bootloader, or the version-main number in you getvar with the software version in settings > about you mean?
If that is your software number, then you probably are stock, since I don't know of any ROMs that use 708 as a base.
Do you have TWRP recovery still installed? You can tell if you boot to bootloader and then boot to recovery (you need to select hboot to get the recovery option in bootloader). If the TWRP logo comes up, then you do, and this will be an easy fix by going to this thread to find a stock ROM backup and stock recovery for you to flash back to stock so that you can get OTA updates on your device.
Twrp is not installed.....its still on stock recovery....i matched the software number from the settings in about section with other device running this OS.
The main prob is its supercid is changed so i dont know which rom is compatible with it.
worgamerx said:
Twrp is not installed.....its still on stock recovery....i matched the software number from the settings in about section with other device running this OS.
The main prob is its supercid is changed so i dont know which rom is compatible with it.
Click to expand...
Click to collapse
Well, almost any new ROM isn't compatible because your firmware is too old. You need to update that first. That's what I'm trying to help you with here.
Also, that phone isn't Irish. None of them are. UK yes, Ireland no. It's an Asian model. Specifically, from Hong Kong.
The only way I could offer help is if you were to unlock the bootloader again. Instead I will mention @ckpv5 here (he'll get a notification because of the mention) because I'm pretty sure he has a link to the RUU you need to update.
He's a really helpful guy, and will respond here when he sees the notification. He's not logged in now, so just be patient.
Good luck!
xunholyx said:
Well, almost any new ROM isn't compatible because your firmware is too old. You need to update that first. That's what I'm trying to help you with here.
Also, that phone isn't Irish. None of them are. UK yes, Ireland no. It's an Asian model. Specifically, from Hong Kong.
The only way I could offer help is if you were to unlock the bootloader again. Instead I will mention @ckpv5 here (he'll get a notification because of the mention) because I'm pretty sure he has a link to the RUU you need to update.
He's a really helpful guy, and will respond here when he sees the notification. He's not logged in now, so just be patient.
Good luck!
Click to expand...
Click to collapse
Thank you so much. You are really kind person. I am waiting
Post fastboot getvar all result (without serial & imei no) to see what is best for you
ckpv5 said:
Post fastboot getvar all result (without serial & imei no) to see what is best for you
Click to expand...
Click to collapse
thank you for replying
here is the result:
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.16G
version-cpld: None
version-microp: None
version-main: 2.11.708.2
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
batter-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c802cb02
hbootpreupdate: 11
gencheckpt: 0
worgamerx said:
thank you for replying
here is the result:
version-bootloader: 3.18.0.0000
version-main: 2.11.708.2
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
security: off
Click to expand...
Click to collapse
Your device has Hong Kong firmware but the MID is EU.
You won't get OTA with this combination.
I suggest to install EU RUU as this is easier, no need to change MID to Hong Kong.
You can follow this, direct update to the latest Marshmallow
Link : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ckpv5 said:
Your device has Hong Kong firmware but the MID is EU.
You won't get OTA with this combination.
I suggest to install EU RUU as this is easier, no need to change MID to Hong Kong.
You can follow this, direct update to the latest Marshmallow
Link : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I am going to install RUU.....its my first time that i am doing such a thing..Thank you so much God Bless You
thank you so much "ckpv5", i just followed your instruction and i successfully installed marshmallow, thanks again you helped me out . i am also thanks full to "xunholyx".
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone, now the only thing I have is an s-on unlocked bootloader and twrp. All the roms I tried installing using TWRP keep saying that the updater binary failed or something. When I try to do RUU, it just doesn't work. Can anyone help me restore functionality to my phone?
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
TheOnlyLite said:
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone
Click to expand...
Click to collapse
Did you think that would return your phone to stock?
redpoint73 said:
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
Did you think that would return your phone to stock?
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(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: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I just tried a bunch of random ones online tbh. I can't find any that match my phone's CID or MID even thought my CID is 1111111.
I have twrp 2.8.1.0 right now.
I am just trying to get the os working for now because everything I tried flashing didnt work.
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
redpoint73 said:
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
TheOnlyLite said:
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Click to expand...
Click to collapse
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
TheOnlyLite said:
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
Click to expand...
Click to collapse
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
TheOnlyLite said:
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
Click to expand...
Click to collapse
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
redpoint73 said:
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
Click to expand...
Click to collapse
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd? The exe keeps saying "The Firmware Update Utility cannot update your Android phone." and when I flash using adb or fastboot, it just fails.
edit: Actually I don't even know. I'm pretty dumb when it comes to this kinda stuff. What do you suppose I do step by step? I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
TheOnlyLite said:
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd?
Click to expand...
Click to collapse
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
TheOnlyLite said:
when I flash using adb or fastboot, it just fails.
Click to expand...
Click to collapse
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
TheOnlyLite said:
I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
Click to expand...
Click to collapse
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
redpoint73 said:
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
Click to expand...
Click to collapse
Sorry for being so vague about everything. So I guess all the RUUs that I tried flashing failed because of bootloader. I just relocked it and it worked. It was giving me error: 99 or unknown error when I tried any RUU including stock ones. And right now I just want my phone to work again haha. Now that I have that, I would like to return my phone to non-rooted, because some apps/games I have detect root somehow and I would like to use my phone to access them. After getting a working OS on my phone, how would I be able to return it to stock, and maybe install cyanogenmod?
Thanks for the help.
edit: Actually nevermind. My phone is unrooted now lol. Again thanks for the help
So you were able to successfully RUU? If so, which one?
TheOnlyLite said:
Again thanks for the help
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
So you were able to successfully RUU? If so, which one?
There's a button for that.
Click to expand...
Click to collapse
So I flashed the 5.0.1 rom on that first link you provided with the official stock roms, but I'm sure the other ones would have worked. I was severely outdated with the one I flashed and had to update like 10 times to get back to the most recent ota lol.
Morning,
I've been into this phone for two days now, the phone would not Update OTA to Android 6 it was on stock 4.4.4 so I figured I'd install the RUU from HTC's site, I unlocked the bootloader and acquired S-OFF, I tried several RUU's (GEp, UNlocked/dev, android 5, 6, even tried to go back to stock 4.4, I know I'm doing many things wrong so I now ask for direction) since I knew nothing about CID and MID, the exe's did not work and the zips would flash via fastboot oem rebootRUU I even (regrettably) flashed several firmwares as it stands now with most hopes lost my phone has this values:
Bootloader is "relocked" since it was said to be required for RUU.
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, I can no longer unlock the bootloader using my Unlock_code.bin file, nor can I install a recovery image I get a "FAILED (remote:" error each time.
Thanks.
This is really bad. This looks to be a result of improper research by your part, and I hope the damage is not permanent (although it may possibly be).
Reason I say this, is that your product ID (m8_whl) indicates you have the Sprint version M8. This version is fairly unique (along with Verizon M8) in that its designed to work on the Sprint CDMA network (along with GSM networks). Due to this, the Sprint version has different partitioning and different radios from most other "GSM" M8 versions. And one should never attempt to convert a Sprint M8 to any other version; by flashing another version's RUU or firmware.
I also do not recommend ever changing the MID on the Sprint device (from its original MID), as there is no valid, safe reason to do so (for reasons mentioned above).
Mods with s-off can be extremely dangerous, as they can result in bricking your phone. You may already have a permanent radio brick (as we've seen happen after folks have flashed another version's RUU or firmware to a Sprint M8). The moment you started having trouble flashing an RUU, you should have backed off, and come here for help. Guessing, and trying multiple random things (like RUUs/firmwares) on these devices, especially with s-off, is a recipe for disaster.
When you say "boot loop" do you mean the phone is actually restarting itself over and over to fastboot? Or it simply can't boot to OS, and goes to fastboot (and if you manually reboot it, it goes again to fastboot)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
Herzchell said:
Bootloader is "relocked" since it was said to be required for RUU.
Click to expand...
Click to collapse
This is only a requirement when s-on. Relocking the bootloader to RUU not needed when s-off. With s-off, you can RUU with the bootloader unlocked.
---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------
Herzchell said:
nor can I install a recovery image I get a "FAILED (remote:" error each time.
Click to expand...
Click to collapse
You can try it a million times, and it won't make a difference. You can't install custom recovery with bootloader locked or relocked. That is the exact reason to have a locked bootloader, to prevent custom recovery from being installed.
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Herzchell said:
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Herzchell said:
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Click to expand...
Click to collapse
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Herzchell said:
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
error 24 means one of the following
1- the .zip is corrupted
2- the .zip is an OTA package ( and it can't be flashed in fastboot mode )
3- android-info.txt have something wrong ( if this is the meant error you will need to change the cid and mid )
so you can tell which one of those is the meant error
about cid it's correct that it eliminate the needs of a specific cid ( and in some cases it passes the mid check )
ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
Click to expand...
Click to collapse
Since the OP is SuperCID, I believe he can pick either. Same model hardware, the only difference is software.
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Herzchell said:
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
Most US carriers, you can only OTA update if connected to that specific carrier (in this case, Sprint).
That being the case, your best bet is to RUU to latest Marshmallow image, as ahmed instructed.
And since RUU is a fully image (not just an update "patch") it doesn't matter the current configuration (as long as CID, MID checks pass or bypassed). Meaning you don't need to install any "older" RUUs before the current MM one.
Thanks,
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
You have both been very helpful.
Herzchell said:
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
Click to expand...
Click to collapse
Did this phone have an issue with the speaker before you started messing around with it?
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.