Develop Bugs

[Q] I want to go back to stock to catch the HTC lollipop OTA but not sure how

I updated to the 3.x firmware to run the latest Viper ROMs and have recently been running CM12. I'd like to go back to stock to catch the upcoming HTC Lollipop roll-out OTA.
HTC has an RUU (2.22.531.5 RUU) available but I can't downgrade from the 3.x firmware to 2.x. They also have a CRC (3.32.531.2) which is a zip file (m8ul-3.4.0-g2c0a258.zip) but I'm not familiar with CRCs. Is there any way to get back to stock with 3.x firmware?
UNLOCKED
S-ON
HBOOT 3.19.0.000
OS 3.32.531.2
T-Mobile US
TWRP 2.8.0.3

Flash a stock rom and recovery and then don't root it or modify it. That should pretty much do it.
Or you could just wait for someone to dump the stock lollipop rom when it comes out and just flash that.
That's what I am going to do. You don't actually need to take the ota to get the update after all.
Also, if you do asearch in this or the general forums for the m8 you should find several threads on going back to stock if you really want to go that route.
kidquantum66 said:
I updated to the 3.x firmware to run the latest Viper ROMs and have recently been running CM12. I'd like to go back to stock to catch the upcoming HTC Lollipop roll-out OTA.
HTC has an RUU (2.22.531.5 RUU) available but I can't downgrade from the 3.x firmware to 2.x. They also have a CRC (3.32.531.2) which is a zip file (m8ul-3.4.0-g2c0a258.zip) but I'm not familiar with CRCs. Is there any way to get back to stock with 3.x firmware?
UNLOCKED
S-ON
HBOOT 3.19.0.000
OS 3.32.531.2
T-Mobile US
TWRP 2.8.0.3
Click to expand...
Click to collapse

kidquantum66 said:
I updated to the 3.x firmware to run the latest Viper ROMs and have recently been running CM12. I'd like to go back to stock to catch the upcoming HTC Lollipop roll-out OTA.
HTC has an RUU (2.22.531.5 RUU) available but I can't downgrade from the 3.x firmware to 2.x. They also have a CRC (3.32.531.2) which is a zip file (m8ul-3.4.0-g2c0a258.zip) but I'm not familiar with CRCs. Is there any way to get back to stock with 3.x firmware?
UNLOCKED
S-ON
HBOOT 3.19.0.000
OS 3.32.531.2
T-Mobile US
TWRP 2.8.0.3
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
3.32.531.2 RUU for T-Mobile US

BerndM14 said:
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
3.32.531.2 RUU for T-Mobile US
Click to expand...
Click to collapse
where the hell are all these RUUs coming from?? lol
i will add to my collection

exocetdj said:
where the hell are all these RUUs coming from?? lol
i will add to my collection
Click to expand...
Click to collapse
http://www.htc.com/us/support/rom-downloads.html#unlocked

BerndM14 said:
http://www.htc.com/us/support/rom-downloads.html#unlocked
Click to expand...
Click to collapse
thanks mate. i am going to add a further (yes further) section to the awesomeness that @Mr Hofs started

exocetdj said:
thanks mate. i am going to add a further (yes further) section to the awesomeness that @Mr Hofs started
Click to expand...
Click to collapse
Unfortunately it doesn't look like Verizon is there and no European ones

BerndM14 said:
Unfortunately it doesn't look like Verizon is there and no European ones
Click to expand...
Click to collapse
pretty sh#t i know. but we have a few plus theres a euro RUU zip floating around so its worth an addition i guess

BerndM14 said:
http://www.htc.com/us/support/rom-downloads.html#unlocked
Click to expand...
Click to collapse
Right on, that's exactly what I'm looking for. :victory: All this time I've been looking at HTCdev. I wonder why it's not there?
No need to relock bootloader for this correct?

kidquantum66 said:
No need to relock bootloader for this correct?
Click to expand...
Click to collapse
Since you are s-on, you do need to relock the bootloader to RUU.

redpoint73 said:
Since you are s-on, you do need to relock the bootloader to RUU.
Click to expand...
Click to collapse
I'm glad I asked! lol

same problem here, tried numerous times and nothing seems to work, someone said I should post my getvar all info stuff and people will help, don't see point in starting a new thread when question I want has already been asked and latest reply was today, anyways, info below.
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.022s

[Q] AT&T M8. Worst case scenario, basically. Phone recoverable?

****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!

Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.

redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.

BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432

Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.

BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.

redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.

Updating from an old KitKat based ROM? Do I need to be on stock?

I have a HTC One M8, that is running a very old version of Android Revolution (7.0, which is KitKat based). I would like to update to the newest version, but I'm getting conflicting answers on how should I do this. Some threads say I have to revert to stock, and some say I have to install the official OTA updates first, otherwise I might end up with non-working wifi, and some say I should use the RUU from the official HTC site.
Details of the phone:
S-ON
Rooted
Has TWRP installed (some old TWRP, can't update it because newest version get's stuck at entering recovery, I read that it is related to me having an old HBOOT version)
Current ROM is android revolution 7.0
CID is TMOB-101
Bootloader unlocked
I heard the easiest way to do it is to use the official HTC site to download a RUU, and use that, but in order to use that, you must relock your bootloader, but that can potentially brick the device if it was tampered with?
Can anyone clarify what should I do, and what should I look out for, to make sure I don't brick (like relocking the bootloader)?

You will need to restore a nandroid backup then do OTA to the latest.
Post fastboot getvar all result without serial & imei no.
Someone will be able to guide you.
Or I check tomorrow as I already in bed now.
Note : unlocking/relocking bootloader will not brick a device.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: hidden
(bootloader) imei: hidden
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s
I found a nandroid backup link here on XDA (http://forum.xda-developers.com/showthread.php?t=2701376) but the link for my CID is broken. Any other place I could get it? Googling just turns up more dead links.

whcv said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(bootloader) security: on
I found a nandroid backup link here on XDA (http://forum.xda-developers.com/showthread.php?t=2701376) but the link for my CID is broken. Any other place I could get it? Googling just turns up more dead links.
Click to expand...
Click to collapse
That if still available, not for your hboot version.
What you need to do is to restore 1.57.111.2 and its stock recovery then do multiple OTA up to the latest 4.19.111.3 or maybe 4.19.111.4
Download 1.57.111.2 TWRP backup - https://www.androidfilehost.com/?fid=95747613655045642
Download 1.57.111.2 stock recovery - http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
To understand more on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(read post #1)

ckpv5 said:
That if still available, not for your hboot version.
What you need to do is to restore 1.57.111.2 and its stock recovery then do multiple OTA up to the latest 4.19.111.3 or maybe 4.19.111.4
Download 1.57.111.2 TWRP backup - https://www.androidfilehost.com/?fid=95747613655045642
Download 1.57.111.2 stock recovery - http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
To understand more on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(read post #1)
Click to expand...
Click to collapse
Thanks a lot, going to try it soon. Out of curiosity, how did you figure out I need 1.57.111.2? I don't see that number mentioned anywhere in my getvars output.

whcv said:
Out of curiosity, how did you figure out I need 1.57.111.2?
Click to expand...
Click to collapse
Your hboot is 3.16.0000
and baseband is 1.16.2133156.UA10G

ckpv5 said:
Your hboot is 3.16.0000
and baseband is 1.16.2133156.UA10G
Click to expand...
Click to collapse
Sorry I'm thick, I still don't see the relationship between the numbers :/
One more question, I have read that I need to relock the bootloader, for the OTA updates to work, is that correct?

whcv said:
Sorry I'm thick, I still don't see the relationship between the numbers :/
One more question, I have read that I need to relock the bootloader, for the OTA updates to work, is that correct?
Click to expand...
Click to collapse
Where do you read you need to relock bootloader ? I asked you to read my thread post #1, there is a note on bootloader matter. No need to relock bootloader.
How do I see the relationship ? That come from observation and experience ... the outcome that I learnt from my own thread ....
See all those software version no. in post #2 in my thread
hboot 3.16.0000 - software version no. is 1.xx.xxx.x
hboot 3.18.0000 - software version no. is 2.xx.xxx.x
so yours is hboot 3.16.0000 and CID T-MOB101 so the software version no. is 1.xx.111.x
and the precise version no. is 1.57.111.2
That's all that I can help ... as this way off-topic from your original problem.

Okay, I managed to install all the OTA updates, but I'm only on android version 5.0.1, and now it says there are no more updates for my system.
I thought the OTA updates were supposed to update me to 6.x?

whcv said:
Okay, I managed to install all the OTA updates, but I'm only on android version 5.0.1, and now it says there are no more updates for my system.
I thought the OTA updates were supposed to update me to 6.x?
Click to expand...
Click to collapse
The update to Android 6.0 not yet available for your device variant/region.
So far only 4 device variants received the update :
Developer Edition
Taiwan
Bell Canada
Rogers Canada
If you want to taste Marshmallow ROM, you install TWRP 2.8.7.0 and install any customized Marshmallow ROM that you like. Just make a nandroid backup of your current stock non-rooted ROM before you install other ROM. You need this backup for next OTA.

I see.
Are there no caveats, like my wifi not functioning if I install a marshmallow rom now, without waiting for the OTA update first?

I would not suggest that if there are problems in doing so.

Htc M8, confused, want to update to marshamallow

Hello I bought M8 from somebody, it is unbranded European model i think, phone is rooted and carrier unlocked as im using it in asia. it comes with android 5.0.1, I want to update to stock marshmallow for this variant. I have been trying to do on my own but it only confused me more. Im not sure if i have custom rom or if because im rooted, because At the time moment it doesnt offer any software updates from the main menu.
Some info abt phone.
Its model id at back is Op6B100,
Android version 5.0.1
Software number 4.18.708.12
Build number 4.18.708.12
In the bootloader menu I have
Software status: Official
Locked ( i think it means bootloader)
M8_UL PVt SHIp s-off
Cid-11111111 (but if I check with cidgetter it says t-mob010). So it confused me because according to its model its supposed to be european model but in fastboot it says 11111111.
HBoot 3.19.0.0000
I dont have twrp installed.
So please tell me where to go from here. I want to either from here go direct to stock android 6 for this M8 variant or go back to stock condition and get ota update. I prefer to lose the root. So please tell me which stock firmware I need, and do I need to change cid, remove root, before that? Also i would like not to brick my device in process.. Thanks.
Also my device is carrier unlocked at the moment so Im hoping this shouldn't affect that. Thanks

.??

Post fastboot getvar all result (delete serial & imei no. before posting) then someone will be able to help.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000 ( on the back its 0P6B100)
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I would like to install htc marshmallow update, kindly tell me how I can do that.

First you need to change MID to EU
Then install EU marshmallow RUU
Follow this guide - https://forum.xda-developers.com/showpost.php?p=70575580&postcount=12

Do i need twrp to change MId? And do I need to unlock bootloader before flashing RUU.

Kashi88 said:
Do i need twrp to change MId?
Click to expand...
Click to collapse
Yes as said in the guide unless you're running a rooted ROM.
Kashi88 said:
And do I need to unlock bootloader before flashing RUU.
Click to expand...
Click to collapse
No

ckpv5 said:
Yes as said in the guide unless you're running a rooted ROM.
No
Click to expand...
Click to collapse
ok thanks , I keep getting this error in the adb fastboot when flashing ruu zip . target reported max download size ( shows some big number bytes) .

Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.

ckpv5 said:
Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.
Click to expand...
Click to collapse
thank you so much i installed it with the micro sd method, and everything worked out smooth. just one last question, if in future i have to reset my phone from settings menu or from bootloader menu (volume down key), will I go back to android lollypop version or remain on this 6.0. thanks again

remain on this 6.0

ckpv5 said:
remain on this 6.0
Click to expand...
Click to collapse
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?

dr.estiack said:
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. It clutters up the forum, and makes it confusing for those trying to help you. Your post is also not related to the topic of this particular thread.

Need Help with HTC m8 Demo Unit *Stock Rom* - Wants to Flash Custom ROM

Hey everyone!
I just got HTC M8 from a friend, and figured out it is a demo unit. It comes with a demo app, which I am unable to get rid off. It was firstly rooted and mistakenly I removed the internal storage. After all the mayhem, researching for hours on this forum, I am finally able to get my device back running but still the demo app is there. I am unable to make any changes in developer options or through control center. I am new to all modding, HTC, Android and custom / stock roms.
I have few questions after reading a lot. After accidentally deleting the OS, and wiping internal memory - I was able to get it back, but now wants to run a custom ROM on it but not sure if I am able to do it with current status of my device.
Information about device:
HBoot: 3.16.000
S-ON
HTC__002
Unlocked Bootloader
TWRP installed (but throws error whenever I try flashing a zip file)
The question: Can I install a custom rom without getting S-OFF and if yes, which custom ROM can I use on my device? I understand there is some limitation to HBoot version, but I am unable to figure out how to update it to latest version. I would like to update my device from Android Kitkat to Marshmallow or some custom ROM which doesn't have a demo app.
P.S: A noob!
Update:
After reading lots of threads, I finally bought Sunshine license and activated S-OFF, now, I am with SuperCID 11111111 on my demo unit. Now, I want know about which Custom ROM I can run, and how can I update my Hboot to latest version?

You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
If you still need help contact me on :
[email protected]

HamzaSheikh said:
[*]HBoot: 3.16.000
[*]TWRP installed (but throws error whenever I try flashing a zip file)
Click to expand...
Click to collapse
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
Hero_elmehrik22 said:
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
Click to expand...
Click to collapse
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.

Yes, Hboot version is too old. I had a long fight with getting it restored. I had to try every other TWRP version and suddenly TWRP 2.8.0.0 worked for me!
Here is the output from getvar all:
Hamzas-iMac:~ hamza$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.203s
Click to expand...
Click to collapse
Problem I face:
- Current TWRP is old, I am unable to make most out of it. (v2.8.0.0)
- Hboot is like hanging in stone age, I need to update it - but I have a demo unit (it comes with annoying demo app!)
- I want to run Custom ROM or at least a newer Android version.
redpoint73 said:
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Click to expand...
Click to collapse

You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.

Thanks @redpoint73 for the help. Here is an update:
I finally able to get rid of demo app using SuperCID - means, now I have S-OFF device. I used Sunshine apk. Now I would like to update my device to latest Android (Marshmallow) - so should I follow the instructions on the thread you pointed me or is there something else I can try instead of locking the bootloader again?
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse

Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse

HamzaSheikh said:
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
Click to expand...
Click to collapse
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.

Lots of love man! I finally got it. It worked like a charm through HTC_fastboot.exe. I was on macOS earlier and tried flashing ruu.zip through it, but after your message. I tried on Windows with HTC fastboot and wow!
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Latest Getvar All:
(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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Anything else I should be doing to make it work awesome and fast?
ckpv5 said:
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Click to expand...
Click to collapse

HamzaSheikh said:
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Click to expand...
Click to collapse
Honest mistake. Relocking the bootloader is mandatory to run an RUU with s-on. So it's easy to miss the fact that the requirement (to relock the bootloader to RUU) is bypassed with s-off.
As you said, you can always unlock the bootloader again, if you want to install custom recovery, root, flash custom ROM, etc. Alternately, if you want to stay stock with no root, you can just leave it relocked.
HamzaSheikh said:
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Click to expand...
Click to collapse
You're very welcome. I wasn't sure if you wanted to pay for sunshine, so that is why I was suggesting some possible solutions with s-on. But glad to have pointed you in the right direction, regardless.
HamzaSheikh said:
Thanks [MENTION=830797]
Anything else I should be doing to make it work awesome and fast?
Click to expand...
Click to collapse
That is a very open-ended and subjective question. It's completely up to your preference, if you want to do any more mods. You can try custom ROMs, root, custom kernels, and much more. There really isn't much limit on what you can try.