Cyanogenmod 13 for the HTC One M8s (m8ql_ul)

Status
Not open for further replies.
Search This thread

WildfireDEV

Senior Member
May 1, 2013
858
1,801
I started work on it again after I heard about the OTA as well, but the problem is there is no way to access the inside of OTA dat files. If you want you can look at the work I have done on here https://github.com/BackupWildfireDEV. The new work I will be doing should appear on the repos in my personal account. I am yet to start pushing my new commits but will do soon.

Therefore we need to wait for a RUU or stock dump from someone running it to come out before doing anything else more.
 
  • Like
Reactions: voidzero

root-expert

Inactive Recognized Developer
Sep 28, 2014
471
504
Greece
I started work on it again after I heard about the OTA as well, but the problem is there is no way to access the inside of OTA dat files. If you want you can look at the work I have done on here https://github.com/BackupWildfireDEV. The new work I will be doing should appear on the repos in my personal account. I am yet to start pushing my new commits but will do soon.

Therefore we need to wait for a RUU or stock dump from someone running it to come out before doing anything else more.

Hello, you can actually access dat files. Search for the binary sdat2img. THis will help you create an img file and you can sudo mount it anywhere :)
 
  • Like
Reactions: Free-Jee

burleanu

Senior Member
Jan 8, 2007
175
48
Cluj-Napoca
hello all,
Does anybody know if S-off is possible for this device. I can't find any RUU to make it work, always give some kind of errors. Maybe I have corrupted something trying all this RUU's. Don't know.
Yes, I have done all the steps correctly, relock-bootloader, use stock image saved during recovery at first time, but was always failed, was something related with signature, now is too late. I can fix only with RUU for MM or S-OFF.
CID MID are all ok, HTC__032 and 0PKV10000

So from what I read on the other from M8 (real one, not this clone :) ) it looks like to be able to return full stock we gonna need S-OFF.
@El-Conkistador At one of your uncrypted image I see something wrong (0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1%4050408_15.00_016_F_release_450409_combined_signed_UNCRYPTED).
I think the file is corrupted, because I can't take out system.img. Also your md5 point to other file. If you want I have also an OTA received at 1.16.401.1 to 1.16.401.10 release 448030. Don't know if it did came without errors, but at his verification it pass, and I also can extract all zip from it, can't installed because of my problems. @voidzero Congratulation for your CM12.1 rom. Is going very good.
I hope you succeed to make this CM13 same good if not even better.
Keeping an eye on the process ;)
Respect
 

voidzero

Inactive Recognized Developer
Dec 11, 2007
343
553
The Netherlands
hello all,
Does anybody know if S-off is possible for this device. I can't find any RUU to make it work, always give some kind of errors. Maybe I have corrupted something trying all this RUU's. Don't know.
Yes, I have done all the steps correctly, relock-bootloader, use stock image saved during recovery at first time, but was always failed, was something related with signature, now is too late. I can fix only with RUU for MM or S-OFF.
CID MID are all ok, HTC__032 and 0PKV10000

So from what I read on the other from M8 (real one, not this clone :) ) it looks like to be able to return full stock we gonna need S-OFF.
@El-Conkistador At one of your uncrypted image I see something wrong (0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1%4050408_15.00_016_F_release_450409_combined_signed_UNCRYPTED).
I think the file is corrupted, because I can't take out system.img. Also your md5 point to other file. If you want I have also an OTA received at 1.16.401.1 to 1.16.401.10 release 448030. Don't know if it did came without errors, but at his verification it pass, and I also can extract all zip from it, can't installed because of my problems. @voidzero Congratulation for your CM12.1 rom. Is going very good.
I hope you succeed to make this CM13 same good if not even better.
Keeping an eye on the process ;)
Respect
There simply is no s-off for this device. The ruus are all valid. Maybe you're doing something wrong.

But most of all you are asking this is in wrong place. It's off topic for CM13 development. Did you see my 'return to stock' thread?

Sent from my HTC One M9 using XDA-Developers mobile app
 
  • Like
Reactions: Free-Jee

El-Conkistador

Senior Member
May 21, 2015
99
102
Lille
hello all,
Does anybody know if S-off is possible for this device. I can't find any RUU to make it work, always give some kind of errors. Maybe I have corrupted something trying all this RUU's. Don't know.
Yes, I have done all the steps correctly, relock-bootloader, use stock image saved during recovery at first time, but was always failed, was something related with signature, now is too late. I can fix only with RUU for MM or S-OFF.
CID MID are all ok, HTC__032 and 0PKV10000

So from what I read on the other from M8 (real one, not this clone :) ) it looks like to be able to return full stock we gonna need S-OFF.
@El-Conkistador At one of your uncrypted image I see something wrong (0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1%4050408_15.00_016_F_release_450409_combined_signed_UNCRYPTED).
I think the file is corrupted, because I can't take out system.img. Also your md5 point to other file. If you want I have also an OTA received at 1.16.401.1 to 1.16.401.10 release 448030. Don't know if it did came without errors, but at his verification it pass, and I also can extract all zip from it, can't installed because of my problems. @voidzero Congratulation for your CM12.1 rom. Is going very good.
I hope you succeed to make this CM13 same good if not even better.
Keeping an eye on the process ;)
Respect

I friend ! My girlfriend have my old HTC M8S (I've the HTC 10 now). But for this problem you must use this RUU : https://ruu.lalleman.net/HTC_M8S(QL...1_15.00_016_F_release_434462_combined_signed/

The bootloader version are identicale. You have just use initialy the 1.11.401.1 with the OTA 1.11.401.10. It's not a problem. You lock the bootloader, you use this RUU. Your phone reboot with a stock ROM and you can flash the OTA (1.11.401.2), and the next OTA's (1.11.401.10 -> 1.21.401.1 -> 2.10.401.1).

El-Conkistador.
 

burleanu

Senior Member
Jan 8, 2007
175
48
Cluj-Napoca
I friend ! My girlfriend have my old HTC M8S (I've the HTC 10 now). But for this problem you must use this RUU : https://ruu.lalleman.net/HTC_M8S(QL...1_15.00_016_F_release_434462_combined_signed/

The bootloader version are identicale. You have just use initialy the 1.11.401.1 with the OTA 1.11.401.10. It's not a problem. You lock the bootloader, you use this RUU. Your phone reboot with a stock ROM and you can flash the OTA (1.11.401.2), and the next OTA's (1.11.401.10 -> 1.21.401.1 -> 2.10.401.1).

El-Conkistador.


Here a part from log from RUU

T101944><DEBUG><CMD>htc_fastboot -s FA56BYS01436 -d flash zip "C:\kituri\htc m8s\RUU[email protected]50408_15.00_016_F_release_450409_combined_signed\rom.zip"</CMD>
</DEBUG></T101944>
<T101949><DEBUG><OUT>sending 'zip'... (99781 KB) OKAY</OUT>
</DEBUG></T102047>
---------------------------------------------
<T102047><DEBUG>=====Sending zip OK=====
</DEBUG></T102047>
<T102047><DEBUG><OUT>writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
</DEBUG></T102047>
<T102047><DEBUG><OUT>(bootloader) signature checking...</OUT>
</DEBUG></T102047>
<T102116><DEBUG><OUT>FAIL12 signature verify fail</OUT>
</DEBUG></T102116>
<T102116><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>

Congrats for the new phone.

---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------

Only if someone wants to get it officially supported, and personally I'm not interested in doing that anymore.

Sent from my HTC One M9 using XDA-Developers mobile app

Please man don't quit, don't leave us on CM12.1. Please quit after you make it :D
Officially supported will never get, look how silent is here....
Other phones with more roms didn't get officially supported, how to get this one :(


Respect!
 

voidzero

Inactive Recognized Developer
Dec 11, 2007
343
553
The Netherlands
Here a part from log from RUU

T101944><DEBUG><CMD>htc_fastboot -s FA56BYS01436 -d flash zip "C:\kituri\htc m8s\RUU[email protected]50408_15.00_016_F_release_450409_combined_signed\rom.zip"</CMD>
</DEBUG></T101944>
<T101949><DEBUG><OUT>sending 'zip'... (99781 KB) OKAY</OUT>
</DEBUG></T102047>
---------------------------------------------
<T102047><DEBUG>=====Sending zip OK=====
</DEBUG></T102047>
<T102047><DEBUG><OUT>writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
</DEBUG></T102047>
<T102047><DEBUG><OUT>(bootloader) signature checking...</OUT>
</DEBUG></T102047>
<T102116><DEBUG><OUT>FAIL12 signature verify fail</OUT>
</DEBUG></T102116>
<T102116><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>

Congrats for the new phone.

---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------



Please man don't quit, don't leave us on CM12.1. Please quit after you make it :D
Officially supported will never get, look how silent is here....
Other phones with more roms didn't get officially supported, how to get this one :(


Respect!
You need to flash from an SD card. Please move this part of the topic to my 'return to stock' thread!!

And who said anything about quitting? I'm not going to quit hehe no worries, all I'm saying is that I'm not going to try and make this version officially included by CM. I'm an outsider [emoji16]

Sent from my HTC One M9 using XDA-Developers mobile app
 

Grinninga

Senior Member
Apr 21, 2016
71
5
Good news, everyone: people are reporting that Android 6 has been released for the One M8s. And after giving it some thought, I decided to work on the CM13 port!

First thing I need is the RUU, preferably the unbranded one with Android 6 for the M8s. Does anyone know if this is available somewhere?
If you need some help, tell me. I have a m8s running the 12.1 cyanogen mod. No issues, nothing. This is a masterpiece. :)

Sent from my HTC One M8s using XDA-Developers mobile app
 

burleanu

Senior Member
Jan 8, 2007
175
48
Cluj-Napoca
I'm uploading now the system image and boot for MM.
The sha1 check for system image match with the sha1 expected by the OTA step2, so it must give official stock system.
That can be sufficient for any of you to make your phone back to stock in MM this time.
The CID is for European version HTC__032 but it does have inside also HTC__001, HTC__102, "HTC__002, HTC__M27, HTC__A07, HTC__031, HTC__Y13
I will post a link to my Gdrive when the upload will be completed, I hope successful, I add a md5 of complete zip file to check if goes full.
Use it with caution and if you know how to.
Is extracted from twrp back-up, so you can easy full the recovery to restore this.
Probably it wants also the last firmware.zip installed to be able to start it, not sure.

Respect!

LE:
Here is the link
https://drive.google.com/open?id=0Bw7YuZIXOkSTZGd6SzdVZjYzTU0
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    I'm gonna leave this here.....
    11
    Good news, everyone: people are reporting that Android 6 has been released for the One M8s. And after giving it some thought, I decided to work on the CM13 port!

    First thing I need is the RUU, preferably the unbranded one with Android 6 for the M8s. Does anyone know if this is available somewhere?
    11
    Another small update.

    My phone is at bootanimation of cm13 at this moment. Actually it's very weird to me that it stuck there without anything printed on the console.

    At least now SurfaceFlinger and HwComposer are loaded just fine!

    -Chris
    8
    Audio is finally fixed! Now we have to fix RIL and some bugs.

    -Chris
    7
    Hey @voidzero and @root-expert.

    I hope you guys are keeping well. It's been a few weeks and I thought you guys could give us an update on how things were going (whether it's good, bad or simply stuck in limbo). As always, I have a deep appreciation for your work and wish you (any anyone else helping out) the best of luck! :)

    Heya, it's about time we give you an update on this indeed.

    Basically development has taken us all over the place. We tried stuff time and time again, without good results.

    Recently - basically after the switch from Cyanogenmod to LineageOS - I got so fed up that I'd decided it would probably be better to just start from scratch. Which we, well, I this time, did. Very time consuming, I can tell you that!

    Though I do have to give @root-expert lots of credit because that guy did a lot of useful work that made this part a whole lot easier. Hat tip to him!

    This time we got most of the stuff working, but there is one huge issue that we got stuck on: audio. It's very odd. A clean install would give us audio, but not for long. One reboot later and all audio is gone. In fact, even just waiting for a few minutes is enough to make it disappear completely and permanently.

    And when that happens and I go into the audio (notification) settings, it doesn't even open. The whole settings subsystem just locks down until it finally is force closed by Android.

    So basically this problem is a huge blocker and we don't know what to do next. @root-expert and I both don't exactly have much time either, he needs to focus on his final year graduating, and as for me, I only have little time because being a stay at home parent takes up most of my time and energy.

    For as far as we're both concerned, the project isn't abandoned - we still take a stab at it every now and then - but the audio subsystem is one hard nut to crack.

    To make matters worse, it's hard if not downright impossible to find help - we kept hearing that there's no plan to officially support this phone with LineageOS, so basically we're stuckity stuck!

    Wish I had better news, that goes without saying. The whole routine of 'make an adjustment, wipe the device (which we have to do, a dirty flash doesn't get us anywhere because audio gets permanently lost after just a few minutes), install the update, go through the new install routine, rinse and repeat' is very annoying and time consuming.

    So, that's where we're currently at. Hope it answers your question. :cowboy::good:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone