Please help me just get on the right track with upgrading rom? - HTC 10 Questions & Answers

I just bought a T-Mobile HTC 10 that has been unlocked through T-Mobile and bootloader unlocked by the last guy that owned it.
This is my first new Android phone since 2013. Since then I've been through a lot, and I've forgotten how quite a bit of this whole modding thing works.
Basically I just want that LeeDroid ROM that everyone seems all excited about. I think it would be really nice on my phone.
I have ADB and the right drivers and everything ready to go on my PC. I understand I need to get the firmware upgraded but that's where I start researching myself into circles.
It seems very unclear to me which firmware I should be using, how to apply it properly, whether I need root or S-ON (are those the same thing?)
Please, I have great intentions, I'm just confusing myself a lot in how to get my phone the way I want it. I really want to LOVE this device but the guides I come across so far are just getting over my head really fast. It is frustrating because this used to come very easily to me.
Can someone just take 5-10 mins out of their day, and very clearly point me in the right direction with maybe a link to a guide that I'd have to be a complete idiot to mess up?

what I've attempted so far
I've looked at the guide for upgrading firmware and discovered I likely need to get my device to S-OFF.
Alright, So i look into that and everyone points to this Sunshine app. Download that. It tries to temproot device and fails.
What next? Do I try to flash superSU in recovery mode? What is the best way to do that? After that, how does one flash a firmware. The "guide" for that just has a bunch of zip files, but not much info on what to do with them.

thebrokn19 said:
I've looked at the guide for upgrading firmware and discovered I likely need to get my device to S-OFF.
Alright, So i look into that and everyone points to this Sunshine app. Download that. It tries to temproot device and fails.
What next? Do I try to flash superSU in recovery mode? What is the best way to do that? After that, how does one flash a firmware. The "guide" for that just has a bunch of zip files, but not much info on what to do with them.
Click to expand...
Click to collapse
If you're still fully stock, just take all the latest OTA updates so you can be on the latest firmware.
Then, install twrp, instructions are on the twrp website.
https://twrp.me/htc/htc10.html
Then, install Leedroid. Instructions are in the Leedroid thread on xda.
You don't need s-off for any of this, only need your bootloader unlocked which you already have.

Tarima said:
If you're still fully stock, just take all the latest OTA updates so you can be on the latest firmware.
Then, install twrp, instructions are on the twrp website.
Then, install Leedroid. Instructions are in the Leedroid thread on xda.
You don't need s-off for any of this, only need your bootloader unlocked which you already have.
Click to expand...
Click to collapse
I appear to be fully stock, but the LeeDroid instructions specifically mention needing to be on the Oreo firmware. I am still on android 7 OS and firmware after performing all OTA updates (there were none available). That was my only hangup. I don't want to break anything. But the more I looked into upgrading my firmware past what was available to me OTA, i started to get very confused about how to go about it.

Which build version do you have on your phone? As far as i know you should be in 2.51.531.32 version. (http://www.htc.com/us/support/htc-10-t-mobile/news/) (you can see version under: All apps > Settings > About and locate the Software version)
If so, then i think you should get S-OFF via sunshine (if i remember correctly) and convert your phone into WWE/US Unlocked version (change CID into super CID, and Flash appropriate RUU). RUU contains firmware and software, so you will have fresh clean system.
It's just my thinking, and i have WWE version from the start, so i have oreo via OTA.
Some info:
Root and S-ON/OFF isn't the same thing.
With root you have access to everywhere in system, and you can give administrative rights to some programs which needs them.
Here's info about S-ON/OFF
https://forum.xda-developers.com/showthread.php?t=1680928

ShadoV90 said:
Which build version do you have on your phone? As far as i know you should be in 2.51.531.32 version. (http://www.htc.com/us/support/htc-10-t-mobile/news/) (you can see version under: All apps > Settings > About and locate the Software version)
If so, then i think you should get S-OFF via sunshine (if i remember correctly) and convert your phone into WWE/US Unlocked version (change CID into super CID, and Flash appropriate RUU). RUU contains firmware and software, so you will have fresh clean system.
It's just my thinking, and i have WWE version from the start, so i have oreo via OTA.
Some info:
Root and S-ON/OFF isn't the same thing.
With root you have access to everywhere in system, and you can give administrative rights to some programs which needs them.
Here's info about S-ON/OFF
Click to expand...
Click to collapse
THANK YOU. You filled in the information gap I still had. I think I've got all that I need to pull this off now. Just gotta pony up $25 through Sunshine to be able to change that CID, eh? I guess there's worse things.

thebrokn19 said:
THANK YOU. You filled in the information gap I still had. I think I've got all that I need to pull this off now. Just gotta pony up $25 through Sunshine to be able to change that CID, eh? I guess there's worse things.
Click to expand...
Click to collapse
Before paying for sunshine boot to download mode and using Fastboot type fastboot getvar all. Post the output here but delete your serial number and imei before posting.

yldlj said:
Before paying for sunshine boot to download mode and using Fastboot type fastboot getvar all. Post the output here but delete your serial number and imei before posting.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 2.51.531.32
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.046s

thebrokn19 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 2.51.531.32
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.046s
Click to expand...
Click to collapse
OK so looks like oreo isn't out yet for T-Mobile then. Like @ShadoV90 suggested the only way would be to S off then Change to US unlocked or WWE. You will most likely lose VOLTE if your on T-Mobile network tho. Or you could wait for them to release Oreo.

Related

HTC One M8 o2 UK Branding - update possibilties

Hello and good evening,
before I start I have to say that I'm actually not a HTC user myself but today I was given a HTC One M8 which should have been resetted and updated to the latest android version. As a Nexus user it shouldn't be that hard but I have some issues, esp. with latest firmware I need some help/advice. I'm pretty sure that 90% of my questions have been answered already but I didn't want to bump old threads from 2014/2015.
Apparently the phone has an o2_uk branding. I was looking on HTC's site but I couldn't find any matching firmware or even info where to download such a file, at least not on HTC UK. HTC US publishes their firmware on their support site for each carrier. The phone still has warranty for a couple of months so unlocking bootloader or s-off are no option as of now. Where does the average joe find all those stock firmware for HTC devices? I'm not even sure if there is new firmware for this kind of branding available. I've have seen plenty of OTAs and RUUs posted on here but you either need to be S-Off or a globel unlocked device.
In case I need to unlock bootloader and go with a custom ROM - is it possible to flash certain radios, basebands from unlocked devices etc.? I've seen that some ROMs require that you update your firmware to the latest version to avoid weird behaviour. But when there is no latest firmeare available what do you do?
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
I'm more than thankful for any idea, tip etc. and appreciate your time helping me out.
maultasche said:
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
Click to expand...
Click to collapse
Don't really understand what your problem is. There is an update and the latest is 6.13.206.5
Have you tried checking software update in settings - about - software update ?
More than once. It only says there is no update available for your phone. Software information says it's on Android 5.0.1.. I installed Sys-I from Play Store which states that the phone apparently has a branding.
O2 is a branding device but it shouldn't stop the OTA even when you are not on their network. I used to have one too as you can see all the files that I have in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I don't know why it says no update when there is one.
As the device is still on warranty, I don't want to advise anything further related to unlocking bootloader.
Have you tried factory reset the device then check the update ?
If it is already bootloader unlocked .. then you can manually update the firmware to the latest.
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
maultasche said:
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
Click to expand...
Click to collapse
If the bootloader is unlocked, you can restore non-rooted 6.13.206.5 stock backup with the latest TWRP 3.0.2-0
then you need to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
then fastboot flash the fw_6.13.206.5.zip (that you can download from post #5)
fastboot oem rebootRUU
fastboot flash zip fw_6.13.206.5.zip
you'll get ERROR
repeat - fastboot flash zip fw_6.13.206.5.zip
done ... but your warranty most probably will be void.
BUT .. can you post fastboot getvar all result without serial and imei no. first.
I need to see the details of your device to make sure these instructions are correct for your device variant.
Wow, thank you for that tip. So S-Off and changing CID is not needed for this operation? Because that was always confusing me. As stated I'm not an expert with HTC and it's the first time someone asked me for help with that device.. Apparently the device has just four months left of warranty. So I guess it should be fine unlocking it.
maultasche said:
....So S-Off and changing CID is not needed for this operation?
Click to expand...
Click to collapse
S-Off is needed when you want to change the device variant from O2 to EU for example (where you need to change CID) but most of the time normal user doesn't need S-Off.
Once it is unlocked, and the firmware is updated ... a user can install any Custom ROM that he like .. not necessarily be on stock O2. If he prefer stock .. he can restore a stock EU ROM ..so no O2 bloatware.
I guess it is alright to unlock bootloader now ... there is no further OTA from HTC, HTC stop support for M8 after two years which already ended end of April.
Thank you so mich for your help. I appreciate it. Now I completely understand what I have to do now. Have a nice day!
@ckpv5
Hey there,
I wanna say thank you once again for your instructions the other day. I haven't spent much time invastigating. You asked me for getvar all so I wanna share the output I got for that device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.0
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(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: d9e7383b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
maultasche said:
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
Click to expand...
Click to collapse
The getvar result show that the device was previously bootloader unlocked and the outdated TWRP 2.7.x.x (that's explain the missing version-main detail).
Just follow the steps .. should work. It seems many variants currently when check for OTA, none available. Not sure what actually is going on with HTC server.
Could probably be. The phone was bought "second hand" with warranty left. The original owner said everything is stock. Looks like it wasn't.
To make things short: I did follow your instructions. Flashed the correct twrp backup, flashed the firmware from your linked thread and everything was fine. OS, baseband etc. all got updated to latest version available.
Thank you again for your help.

Help, my Htc one m9 is bricked from relocking the bootloader.

Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Razor2211 said:
Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Click to expand...
Click to collapse
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
teddy0209 said:
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Razor2211 said:
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: -
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Click to expand...
Click to collapse
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
computerslayer said:
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
Click to expand...
Click to collapse
Thanks for the tip about IMEI.
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Razor2211 said:
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Click to expand...
Click to collapse
Read the ReadMe thread and all you questions should be answered since that's what that thread is made for.

Which version is the M8 I bought ? Tampered/compromised phone ?

Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(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) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14

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.

[SOLVED] Just restore to stock

SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s​
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
I have really no clue how to proceed.
gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards
gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?
First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?
gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:
gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.
Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(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-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.

Categories

Resources