yashsingh1/xdaforums huggingface dataset:
[One (M8s) General] wageslave:
I think so:

Bootloader is relocked, version is 3.19.0.0000.

getprop ro.cid

HTC__001​

getprop ro.build.fingerprint

htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys​

getprop ro.mid

0PKV10000​

Am I missing something obvious? It wouldn't be the first time ;)
[One (M8s) General] burleanu:
Finally found the problem!

Hello back,

I finally found the problem for the OTA and the stock image return.

For the OTA with "update fail due to bla bla..."

It is caused by the ckeck of your system.img during update.

In case you mount one time the system.img "write enable" with the twrp recovery it will CHANGE your system.img from the original state and the update will fail with the known error.

Now for the stock return I followed another approach.

Installed manually the system.img

Installed manually the firmware.zip (in RUU mode)for the corresponding version of system.img.

Then applied the progressive OTA's until MM 6.0 via adb sideload, reboot normally after every OTA.

All the file used are from here.

Firmware.zip extracted from an OTA.

Also during this procedure I found out (in A9 tread) that we can downgrade the bootloader WITHOUT the need of S-OFF.

To be able to downgrade you need to run in the adb shell mode inside twrp to change the curent vers inside partition "misc"

the command was

echo -ne "1.16.401.1\x00\x00" | dd of=/dev/block/mmcblk0p26 bs=1 seek=2208

to make the bootloader think I have 1.16.401.1

I will give more details later, now I go to sleep.(here is 2:00AM)

I will post the system.img and boot with MM 6 when I will have a decent internet conection

LE:

The step 2 from the update does fail to update via the sideload! TAKE CARE!

It did install the firmware but it didn't patch the system, it just reboot and made phone bootloop.

The other where running OK.

So I install like I say stock system image 1.16.401.1 and update now to 1.16.401.10 via official OTA from HTC and wait now a few days to receive the rest.

Fist step it did go via sideload but I returned backwards and I will wait a bit to see how will send HTC the update.
[One (M8s) General] wageslave:
Thanks for the info.

That sounds fairly complex. How can I get the system.img , and how do I install it?
[One (M8s) General] voidzero:
Nothing complex, I think [MENTION=394989]burleanu[/MENTION] is just telling you to flash version xxx.xx.1 and not version .10. Then let the system update itself to version .10 via OTA updates and so on.

[MENTION=6701903]El-Conkistador[/MENTION] can you take the RUU and firmware version .10 offline from your page? I can confirm that it contains a corrupted image and thus does not work.
[One (M8s) General] burleanu:
Try to use 0pkvimg or complete RUU from that version!

Also if U gonna use custom recovery is mandatory to use it in "read-only". Once you load Write-enable it will brake your system file and OTA will fail.

I recommend twrp 3.0.2.0 version

Maybe [MENTION=1162986]Captain_Throwback[/MENTION] can be so kind to make further recovery for our device :D

Respect!
[One (M8s) General] voidzero:
Yeah, to be honest I agreed to take the recovery build over from him too, but haven't done so yet.. *blush*
[One (M8s) General] burleanu:
When you start updating with the OTA's please look at logcat and find the original file location on HTC servers :D

I found that after I updated were it is!

Also for me it don't go Step 2, is not working in sideload and they don't push me the second step, immediately after you receive notification, to be easier to trace.

Good luck!
[One (M8s) General] voidzero:
Actually I was just trying this - i'll write it in full:

Flashed 1.16.401.1

Rebooted and waited for post-flash installation

Rebooted, then forced reboot to bootloader, selected recovery

Flashed 1.16.401.10-1.16.401.1 OTA via adb sideload (no longer available via ruu.lalleman.net?)

Rebooted and waited for post-flash installation

Rebooted, then forced reboot to bootloader, selected recovery

Flashed the OTA "step 1" via adb sideload

Rebooted and waited for post-flash installation

Rebooted, then forced reboot to bootloader, selected recovery

Flashed the OTA "step 2" via adb sideload

Rebooted and waited for post-flash installation

Rebooted to system, fingers crossed

But... I've been waiting for a pretty long time and all I get is a black screen, and the phone becomes very, very hot. Tried to open recovery, but it doesn't work... getting a HTC screen with a red exclamation point in the middle.

Alright so, maybe the "forced reboot and adb sideload" method wasn't smart of me to do. I felt advantageous I guess.

So then I tried to reflash 1.16.401.1 now, and, am getting "large image update failed" there. For version 1.16.401.10 I get this too. So I might be really stuck now until we get a newer RUU.
[One (M8s) General] voidzero:
I'll try to downgrade the firmware version with the 'dd' command you gave [MENTION=394989]burleanu[/MENTION]. Didn't see that before, glad I did now! Recovery did not boot until I flashed it to the recovery partition (fastboot boot ... did not work). That was scary.
[One (M8s) General] voidzero:
Got it all fixed now and am on version 1.16.401.10. But I'm getting "no updates available" so perhaps this version is just not yet released for this variant of the M8s..?
[One (M8s) General] burleanu:
Step 2 update done in twrp!

That's not so scary!

More scary is to update the system in twrp with the step2 OTA update! and remain locked in recovery :D

I remain stucked inside recovery WITHOUT being able to boot in bootloader. Probably I forgot to delete some line in the script. (more detail down).

So what I have done:

I take the step 1 update via sideload (actually I put on sdcard the update with the name "ptt.zip" and call for an update from sdcard via stock recovery).

That went smooth !

Then unlocked the BL and install twrp 3.0.2.0.

Edited the script lines inside the step 2 recovery. Delete all the checks he is doing at the beginning! (both scripts!) plus one request of reboot at the end of "htc-updater-script"!

In the other script (somewhere in the middle) I did leave the check at the end of the patch for system to see if it goes correct!

Than take the file and install like you normally do on custom roms.

So IT DID the patch of the system!

Then now I remain STUCK with some PROBLEM! The phone remain in recovery without the possibility to start bootloader.

Was able to start in BL after I asked for "fix contexts" (or something like that in twrp recovery in advanced page, top wright, Don't remember well because it was 4 am and was tired :) )

Probably I didn't take down correctly the lines from the script and that's why I remain stuck with only recovery, luckily enough I could get out.

That's why I don't post the edited lines in script. Maybe some of you with better skill in reading the code will edit the script better without this error.

After phone was again able to boot in bootloader I relocked it back and rename "firmware.zip" from the OTA to 0pkvimg.zip and updated so the new firmware.

After I remove the sdcard and request for a reboot.

And VOILA the phone booted up in MM!

Good luck!

I can't post the system and boot image because I'm not home and here the internet is disaster! It take me several downloads until I get the files with correct md5.

I can do it in about 1 week when I get back home.

Respect!

LE:

One nice "touch" from HTC!

After it restored the back-up from cloud and updated all the apps I have also Sense 8 together with freestyle theme.

Nice!

Still get hot after intensive use but is extremely fast to use.
[One (M8s) General] matt1257:
hi does anybody have a stock nandroid backup from their m8s please. my cid is vodap001 i cant get any of the RUU to work and would be a life saver if anyone had one thanks
[One (M8s) General] burleanu:
Flash the system.img and boot.img from Firmware Un-crypted (expert) folder, the files with 0pkvimg-.xxx..xx.xxxxx.zip, I repeat the uncryped files.

It will be the same like a stock

After download just check the md5 to be same like is posted.

(system and boot are inside that zip file).
[One (M8s) General] matt1257:
anybody know what would cause this. i flashed the boot.img successfully but the system.img wont flash in either fastboot or twrp. in fastboot i get erasing 'system'...

FAILED (remote: not allowed)

finished. total time: 0.005s

when i try twrp i get E:size of image img is larger than target device /dev/block
[One (M8s) General] burleanu:
Be sure to have correct version selected!

Also you can try to do it in RUU mode.

Also use htc_fastboot and not fastboot file.

All of them of course with bootloaded unlocked of course.

If none work then no idea
[One (M8s) General] OmikronIE:
Would there be any chance someone could post a link for a RUU or a nandroid backup for Three network - CID: H3G__001, please?
[One (M8s) General] marius88cc:
Can someone help ? i applied root, and had some issues, (not working custom kernel, overheat, etc) so i wanted to get back to stock, relocked bootloader and copied original ruu to sd (1.16.401.1, witch i user another time and worked), this time i get: image update fail, "device halted due to Large Image update fail !"

I read somewhere that the reason could be that i updated to 6.0.1 and need that image if so can someone pint me to a link for the 6.0.1 ruu.

I made nand, but still says software status modified
[One (M8s) General] Steef1983:
So, I went back to stock and all was working till the OTA part 2 update started. Now the first HTC logo shows up but, after that the screen goes black (backlight is still on) and the boot sound is played and that's it. The screen stays black. Does someone know what to do next?

I already tried perfrorming the update again by downloading "OTA_M8_QL_UL_M60_SENSE70_MR_HTC_Europe_2.10.401.1-1.21.401.1_release_476671oku0j5qjb9j4g41p .zip" and renaming it to "0PKVIMG.zip" and placed it on SD. The recovery starts the install all goes fine but at the end, the same thing happens again so, I'm a bit stuck. Can't go back, can't go forward :(
[One (M8s) General] Mulcias:
So I did everything like you said in this "tutorial" to repari my phone and again get stock build but my bottom speaker is still not working (i had this problem since newest cya 12.1 update). It's not chrome fault to be clear. Every sound that comes out my phone is played trough speaker on the top.

Edit//Updating now to Android 6.0. Hope this'll solve the problem

Edit2// Nope, still not working...
[One (M8s) General] risyasin:
Hi [MENTION=732043]voidzero[/MENTION], How did you solve this problem?

I had flashed 1.11.401.1 once, just to see MM, had removed your ROM.

then upgraded to MM via OTA. then just bearing a few days switched to your ROM back :cool:.

even without having a final nand backup of MM.

Now I have a new phone. So need to restore the stock rom to give the phone away.

But i can't flash any firmware, none of them.

It seems like upgrade to MM has changed something.

now it blocks to flash any firmware :/

-Relocked-

Hboot: 3.19.0.0000

Radio: 1.0.U20410.1@60201

April 12 2016 (last firmware date?)

Used: 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.11.401.1_Radio_1.0.U20410.1@50311_15.00_016_F_release_430101_signed.zip

this one was the first, i had flashed by your guide. which it worked like charm.

now all of them 1.11 & 1.16 ends up with large image update problem.
[One (M8s) General] voidzero:
Sorry [MENTION=4028951]risyasin[/MENTION], I totally missed your message.

To downgrade a RUU I used the following command, in recovery, via adb shell:

echo -ne "1.03.401.11\x00" | dd of=/dev/block/mmcblk0p26 bs=1 seek=2208

Afterwards, reboot to bootloader and install the RUU of your choice. Hope this helps.
[One (M8s) General] mobilescooby:
Right so heres the story. I get a m8s a few weeks ago and it offers me the ota MM update as nice as it is i think right let's root it and sort a few things out.

I unlock the bootloader and get twrp installed no bother.

On leaving I wipe the cache. I then inadvertently wipe system.

Yea so left with no OS. No biggy CM 12 is out so I get that on my nice shiny m8s.

While impressed I get a few reboots every day and sometimes completely lose mobile data. Which I can fix with a reflash.

I use my phone for work so can't really have my phone offline etc.

I have tried for days and days to go back to stock to no avail.

I have tried all the ruu's to which they always report the same error.

I've also tried loading via opkvimg files on my SD card. To which I get the large file image error.

My details are

Hboot: 3.19.0.0000

Radio. 1.0.U2040.1@60201.

Os is blank ( currently on cm recovery so guess that's why.

My bootloader is relocked every time I try to do this but it never works.

Can anybody give me some advise on how to go stock please?

Many thanks
[One (M8s) General] Ikkuh84:
It you use the build before the latest build, you'll have a very stable one. I'm running that one since release, and have no reboots or whatsoever so far.
[One (M8s) General] mobilescooby:
Thanks for your reply, i would like to get back to stock if possible.

Failing that then I may try your suggestion if I am unable to do so.

Cheers
[One (M8s) General] risyasin:
Hey, [MENTION=732043]voidzero[/MENTION]. Thank you for your response.

i've actually tried that before posting here, i had read [MENTION=394989]burleanu[/MENTION]'s answer.

Did not work out for me. I could able to see the version change in HBoot.

Also tried that with several other version numbers to convince that it was old.

But every time i got that large image update fail.. none worked. :/

Then i have tried something else which worked for the first time.

At that moment when i wrote, phone was unusable (radio was not working, no sound etc.)

Also i've figured out that chainfire's new rooting technic the one without touching system,

was actually the source of problem. That messed up several mmcblocks i guess.

i couldn't confirm, because i have re-flashed it before any backup (as usual)

In case if it happens again, now i took all images of memblocks with dd & md5'd them.

I will compare with the originals. So that i can blame it for certain.

I have solved that re-flashing problem in hard way.

extracted firmware.zip (24mb) in OTA update (1.21.401.1),

started the phone Download mode.

flashed the firmware.zip as it's.

restarted back in download mode.

then flashed the firmware.zip (53mb) in OTA (2.10.401),

and let it update.

Now i have all working re-flashed MM again.

Thank you so much for help. You are really a great guy.
[One (M8s) General] voidzero:
That's great and useful! I'm glad you have got the phone back to a working state. Once again it is proved that a phone with S-ON can't really be bricked by doing this stuff.

Well done!
[One (M8s) General] voidzero:
Additionally, I explained one post before your question how to downgrade a RUU, so in case it is required, that may be helpful.

The reboots thing happened to me too. I may look into it later, but it is a bit more difficult for me to test fixes without having a phone to test it on. What do I mean? Well, I still do have my One M8s, but, I've started work on CM13 now. :highfive:
[One (M8s) General] risyasin:
Cool! New Rom. :)

I really would be happy if i could help you about it. But still can't find enough time for Android & CM internals.
[One (M8s) General] mobilescooby:
[MENTION=732043]voidzero[/MENTION] thanks for all your hard work on CM12 and ultimately CM13 when you get it running. I've finally managed to get back to stock. Been downloading and flashing everything I find and have the right combo now.

Keep up the hard work. I only wish I could help with the development more.
[One (M8s) General] wageslave:
I've been trying to get back to stock system / recovery so that I can update to the latest android. Can you explain what worked for you?
[One (M8s) General] mobilescooby:
I'm do have my notes on me at the moment but I do know I downloaded the latest MM file that was linked on another page. I'll link that in a while.

Also I had a stock recovery file I downloaded from somewhere that I flashed from the boot loader.

Gimme an hour or so and I'll go through my history and do a sort of guide.
[One (M8s) General] mobilescooby:
Right Guys, This is what i did to get back to Stock MM from CM12 ***Havent got to rooting it yet but this will give you stock ***

It may not work for you but it did 1st time for me so i thought i would share my experience.

I was bootloader unlocked and had CM recovery installed at the post i started to do this.

1. First put file 1 on your SD card make sure the filename is 0PKVIMG.zip and reboot to HBOOT (bootloader)

2. Let the file be detected and it will give you the option to flash it, updating the recovery to stock and it will reboot.

3. Go back into FASTBOOT and issue FASTBOOT OEM LOCK from you computer. (This will relock the bootloader)

4. Your device will probably bootloop at this stage! it did me.

5. If you have ADB access, simply issue adb reboot bootloader to get back to HBOOT. or simply use the vol down and power button combo to get back into the bootloader.

6. Check the HBOOT screen and you should now notice that it should say something like OS-2.10.401.1 and ***RELOCKED*** at the top.

7. Now put File 2 on your SD card ***making sure that the file is the same name as file 1*** (simply delete the other file off the SD card) and go back into HBOOT (bootloader)

8. As before the phone should say it found an image and offer to flash the file..... This is where you cross your fingers and go make a coffee or something. The process took me about 10-15 minutes to flash.

9. Simply follow the onscreen options and hopefully you'll get asked to press power to restart. Give the phone a few minutes to do its thing then all being well you'll be back in stock MM. ***Happy Days***

Locations for Files

File 1 - https://drive.google.com/open?id=0Bx1ER04ZdUwYVmtZNTFOeEVfY1E

File 2 - https://mega.nz/#F!2BMExYzD!VqkTATYRF_QWkMSMfQoTvQ

Please note these are not MY files i take no credit for them and accept no liability for any damage these files cause to your phone. If these files are hosted elsewhere or created by anybody else then my apologies i couldnt remember where i got the files from and all credit is due to you.

Right well i think thats about it. Give it a go and let me know how you get on.
[One (M8s) General] fraggz99:
[MENTION=732043]voidzero[/MENTION] You should add a new method, I found out thanks to other members here that using AruWizard LP works 100% for reverting to stock. Im currently on stock MM sense 7 thanks to AruWizard, everything works, no root detection shows in apps and I believe I am on stock recovery (booted recovery and had a screen with red triangle/exclamation mark, had to hard reboot)

It works even if you are on a custom ROM as I was running CM 12.1 beforehand

I downloaded the same zip you said (from Firmware crypted (Original HTC)) and renamed it rom.zip, then placed it in the AruWizard folder, ran AruWizard and it detected it and it worked.
[One (M8s) General] mobilescooby:
[MENTION=732043]voidzero[/MENTION] am i right in thinking that the above code merely puts the version number in the correct place on phone so that the RUU or recovery gets the correct version number?

So effectively we could put what ever version number we wanted? without causing damage to recovery or anything else?
[One (M8s) General] voidzero:
Yes it does appear so. So I just gave the oldest version number I could find.
[One (M8s) General] mobilescooby:
ah great because i noticed that we get the RED HTC warning once we have flashed custom recovery and was wondering if that would effectively disable said warning.
[One (M8s) General] AbbyN:
Thank you so much finaly im back to STOCK.
[One (M8s) General] mobilescooby:
So did my way work for you?
[One (M8s) General] AbbyN:
Yes it did help, 3 times now.

When i unlock it and install TWRP and then SuperSU my phone freeze again and then i have to do your sd thing again.

I cant get SuperSU started.
[One (M8s) General] mobilescooby:
I had that goto the super su beta thread and download that
[One (M8s) General] AbbyN:
Thanks ;) i downloaded UPDATE-SuperSU-v2.76-20160630161323.zip and its working like a shine again :D :good:
[One (M8s) General] mobilescooby:
Am glad it's working for you so do what I do and have that on a SD card just in case.

[MENTION=732043]voidzero[/MENTION] I don't know if perhaps you might want to sticky my solution or just link to it? Seems to work well for some
[One (M8s) General] bilal.fanatic:
QUICK QUESTION.

Will flashing a RUU restore the recovery to stock?
[One (M8s) General] mobilescooby:
Yes it will. If you have problems you can follow my guide a few posts up. That seems to work well
[One (M8s) General] bilal.fanatic:
I did try your guide but while trying to flash file1 it gives some error and doesn't flash the file. Thanks btw.:good:
[One (M8s) General] mobilescooby:
Do you remember or know the exact error? I'll see if I can help
[One (M8s) General] daveog3:
A quick question

My wifes M8s (stock never rooted or modified in any way) got a notification for an OTA update 1.21.401.1 part 1 of 2. When i did the install it failed

with the error below

"Missing bitmap oem_unlock ,find no map for partition , system partition has unexpected content , error in cache recovery block map (status 7)" installation aborted"

I reset the phone to factory and downloaded the update again. It failed on install again with the same error

is the best bet to flash with the

RUU_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@50408_15.00_016_F_release_450409_combined_signed

back to stock and try the OTA again, or to just flash with the

0PKVIMG_M8_QL_UL_M60_SENSE70_MR_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1@60201_20.05_018_F_release_479349_combined_signed

straight to Marshmallow.

not worried about content on the phone
[One (M8s) General] fanys:
Hi can anyone help please? when i flash and go in hboot the green bar finish and after is doing some check and get update fail , Cid incorrect

my htc m8s cid is ORANG001 my radio1 is 1.0.U20410.1@60201... i tried the same radio and i get the cid incorrect my phone is from EE UK and the only radio for that version is EUROPE. help please btw my phone is s-on
[One (M8s) General] ambiente1:
Tried that [MENTION=3029183]mobilescooby[/MENTION] but doesn't work for me. :(

After moved File1 to microSDXC card and renaming to 0PKVIMG.zip, i insert to M8s but i get:

I have this M8s:

Do i need to modify something?

Also checkout my other thread about problems while revert to stock M8s:

http://xdaforums.com/htc-one-m8/one-m8s-general/m8s-how-restore-to-100-stock-t3439429

I really appricate your help. :good:
[One (M8s) General] snelpiller:
So I also have to downgrade because I am on 1.16. When I try and run this command I just get an error. I have never used ADB shell so here is a pic of what I [IMG="did"]https://i.gyazo.com/21412384e201c2a3465e0c5fbcd09402.png[/IMG]

My phone is stock and everything but it cant receive OTA updates, just gets an error during the first 25% and then it keeps asking me to update even though it fails.. So I want to do this in an effort to make it so it can update again. Thanks for all your efforts
[One (M8s) General] snelpiller:
delete ples, misspost