yashsingh1/xdaforums huggingface dataset:
[HTC One S] Hauk92:
Cyanogenmod is not updated anymore. Here is a LineageOS build with february security updates. LineageOS is now without root, to get root you need to flash the addon which is provided in the download folder.

Download:

Android File Host (15313 cherrypicked)

Changelog:

Notable new features: https://github.com/LineageOS/android_vendor_cm/blob/cm-13.0/CHANGELOG.mkdn

Device specific: https://review.lineageos.org/#/q/br...project:LineageOS/android_kernel_htc_msm8960)

all: https://review.lineageos.org/#/q/branch:cm-13.0+status:merged

Fixes:

FM Radio workaround:

http://xdaforums.com/showpost.php?p=65085653&postcount=264

Wi-Fi turning off

It seems like Wi-Fi turning off is an aosp problem. I have found various "fixes":

1. In Settings - Wifi - Advanced - Keep Wi-Fi on during sleep > Change the setting to Never

After turning Wifi Off/On change back to Always.

Source: https://forum.cyanogenmod.org/topic/120233-cm13-wifi-dropping/?page=2

2. Another solution that seems to work is to roll back to the Lollipop DHCP Client. Settings-> Developer Options-> Use legacy DHCP client.

Source: https://productforums.google.com/forum/#!topic/nexus/gkPdghmnj_o

3. Install an app: https://play.google.com/store/apps/details?id=com.roy.wifimonitor&hl=en

Possibly faster GPS fix:

GPS should work fine. But if you still have problems you could try to add a supl server in /system/etc/gps.conf:

SUPL_HOST=supl.google.com

SUPL_PORT=7276
[HTC One S] mali_zeeko:
Dirty flashing over CM13. Works fine!

Thanks!
[HTC One S] um.z:
I've installed Navigon's satnav app on an HTC One S running the latest Lineage build (the one from post #410). Sound output seems to work fine in that rom, with the exception that for some reason, the Navigon app doesn't output driving directions, no matter what I do. I'm not sure whether this has something to do with the Navigon app or the rom. Has anyone here experienced the same or comparable issues?
[HTC One S] moozon:
New build CM13 from 10.06.2017. Hboot 2.16.

Changelog for CyanogenMod common

Changelog for ville.

Changelog for msm8960

Changelog for s4-common

#Tested.
[HTC One S] moozon:
New build CM13 from 22.08.2017. Hboot 2.16.

Changelog for CyanogenMod common

Changelog for ville.

Changelog for msm8960

Changelog for s4-common

#Not Tested.
[HTC One S] disiz:
Hi, I've try this rom and it looks good, phone overheating many times, but seem pretty stable, thanks for the job :)
[HTC One S] Cybermachine:
actually ... having quite the problem here

i have an htc one s

hboot 2.15

bootloader unlocked

S-OFF

the CM 13 won t install (error 7 and says it needs hboot 2.16)

i am using CWM recovery

here s the trick tho

when i update to hboot 2.16 and link my phone to my pc i get a message(you need to format the drive before using it) well that s not a problem

the problem is..... the size change from 10GB to 44MB

i found a solution

i installed HBOOT 2.15 again and the storage and files went back to normal

i wanted to install CM 13 since on the CM 12.1 i had several problems

one of them i can t check for updates ... i get check update error

any help?:fingers-crossed: going back to CM 12.1 for now
[HTC One S] Flippy498:
The SKU 401 stands for unbranded devices. You need the correct one with SKU 111 (T-Mobile Germany). You could try flashing the unbranded files with TWRP but I can't guarantee for anything. Besides you could flash a Sense based custom rom and use one of the S-OFF methods afterwards. ViperOneS 2.2 should be fine for example (it's the one I used when I got S-OFF on the One S). Or you try to contact llabtoofer for his RUU service so that he recovers your phone. A link can be found in the google sheet in my signature or with a short google search. Be aware that you will have to pay some bucks if you want his help. Since the One S isn't one of the newest phones the amount shouldn't be that high, though.
[HTC One S] htc-2016:
Sorry, I need to ask again.

Right now I'm realy confused.

Yesterday I had a "untouched" htc one s and I wanted to go the whole way up to cm-13.

For this I

Unlocked the Bootloader

Flashed TWRP 2.8.7.0 and made a Backup of Boot,Data&System (Stock Rom)

Flashed CM 11 (First the boot.img and then the full zip)

Failed twice to get SuperCID

Failed twice to get S-OFF via rumrunner

Tried to get the stock Rom with the TWRP-Backup -> FAILED again

And here I am without internal storage/sdcard partition :rolleyes:

So TWRP is still working but I'm a little afraid now. I read here (http://xdaforums.com/showpost.php?p=25850720&postcount=8) that actually the stock recovery is needed to get my missing "sdcard" (funny enough that this device doesn't has a sdcard) back.

From the decrypted RUU's I also get a

recovery_signed.img

. Is this wise to flash via fastboot? Can It brick my device finally hard? :eek: Or can I flash twrp back if it didn't worked out?
[HTC One S] Bad.Fish:
Are you on a sense ROM? http://xdaforums.com/showthread.php?t=2558334 try reading this

sent from my HTC One S on Marshmallow biyatch
[HTC One S] The Setlaz:
1. Have you tried formatting sdcard in TWRP?

2. Have you tried formatting sdcard from computer? (mount USB storage in TWRP and connect to computer)

3. Have you tried re-flashing TWRP again? (or going to 3.0)

4 Have you tried to do Factory Reset in Fastboot?

Losing SDCard is a common issue and has been solved many times.

Regarding SuperCID, can you post a snapshot of your mmcblk0p4MOD and mmcblk0p4MOD files in a Hex Editor? (black out IMEI number before posting!)
[HTC One S] Flippy498:
As said you can try flashing the files from the RUU, see what's happening and report back afterwards (that's actually how xda is meant to work ;)). I personally wouldn't do so since on the One M9 you could only make things worse if you do so. But I don't know whether it would work with the One S. (Nevertheless I doubt that it would work and/or help in any way.)

The internal storage of HTC phones is integrated into the system as an emulated SD card. So in other words you simply corrupted your internal storage. Normally you would need to flash a RUU to repair broken partitions if there was one you could use. But you can try the tips from The Setlaz. Or as mentioned before you can use llabtoofer's RUU service.
[HTC One S] htc-2016:
I tried 1,2 and 4. A reflash of TWRP or to TWRP 3.0 is still pending.

Here are the shot's you requested: Original & Modification:

I read outside of XDA that for T-Mobile D there is the opossite way to go. First S-Off and then superCID. People the cid of my device also reporting problem's with this method and moonshine.

I tried rumrunner because people reported this one to work. But now I'm sure it was wrong to this while I had CM11 flashed. Now I'm lost without internal storage and scared that i do a hard-brick out of my soft-brick :(

I wonder how I can back the stock-recovery. Does fastboot (the bootloader?) always stays intact?
[HTC One S] The Setlaz:
Your mmcblk0p4 files are correct. P4 must have been write protected by an OTA update then. Forget about trying to push anything there, it will just not work.

Don't attempt Facepalm S-OFF if you are not SuperCID first.

Keep in mind S-OFF is a security exploit. You have to meet all requirements described for the exploit to succeed!

Facepalm S-OFF requires you to be SuperCID so forget about it.

Moonshine requires you to run stock ROM, so it will fail with CM11.

Rumrunner seems to be your best shot at it.

I don't know anyone who have hard-bricked their device by messing with it. As long as there is power and you don't do anything stupid, it is actually difficult to hard-brick it.
[HTC One S] htc-2016:
I wanted to flash twrp-3.0.M4-0-ville via fastboot and figured out that it doesn't work anymore. The phone is fastboot mode (bootloader->fastboot) but no computers are recognizing it.

I now used a usb-stick with usb-otg and mounted it in my twrp-2.8.7.0 recovery. From there I installed the new twrp-3.0.M4-0-ville.img to recovery.

I did a reboot of the recovery but I'm still with twrp-2.8.7.0 ??? I'm lost in a L0OP :eek:

The steps for me are somehow quite clear... but I don't know how to achieve them:

Get the stock recovery back to be able to run proprietary "clear storage" to get my internal storage ("sdcard") back

Flash a Sense Rom or Stock Rom an run rumrunner.us to S-OFF

Now I should be back on track to Super-Cid, Update H-Boot and finally flash CM-13

Long way to the top if you wanna rock'n'roll :angel:

Edit: TWRP-Log with 0MB of sdcard

/sdcard | /dev/block/mmcblk0p36 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent Has_Android_Secure Is_Storage Is_Settings_Storage
Symlink_Path: /sdcard/.android_secure
Symlink_Mount_Point: /and-sec
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: Internal Storage
Storage_Name: Internal Storage
Backup_Path: /and-sec
Backup_Name: and-sec
Backup_Display_Name: Android Secure
Storage_Path: /sdcard
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
[HTC One S] htc-2016:
Finally I was able to flash twrp-3.0.M4.

But still when I use "clear storage" from the bootloader it calls twrp for doing it and the script can't bring back my internal storage.

I now give another try to get the stock bootloader back... let's see!
[HTC One S] htc-2016:
More brilliant news!

I succeeded to flash (a) stock recovery extracted/decrypted from a RUU (which is actually a lower version than the one I had before!)

I now gave it a shot to "clear storage" and "factory reset"....

And! Profit! Got 10GB of internal storage back!!! Hipp Hipp Hurra!! Thank's everybody for the help and advices! Got a lot of knowledge down here at xda!

Now it's time to give rumrunner a second (actually third!) chance ;)
[HTC One S] darkspore:
Why this ROM locate in VilleC2 subforum?
[HTC One S] The Setlaz:
No such issue on 25/05 build

EDIT: Ok, I think I encountered the bug tonight. Actually the flashlight tile even disappear for a second when light goes off..

Didn't notice that either on 25/05.

Regarding the camera, there's been quite a few patches merged (CyanogenMod/android_packages_apps_Snap) but the folks with Samsung Galaxy S3 (msm8960) seems to have issues as well.
[HTC One S] pavel.bosco:
I believe the correct step3 should be flashing HBOOT2.16 RUU.

it not only flashes different system and boot images, it also repartition the device, so you will have 12Gb of storage instead of current 10 (or 8, as far as I recall)

this thread is for HBOOT2.16 only, this is why it called unofficial. the officials downloadable CW are working on HBOOT2.15, as well as stock ROM.

I also believe RUU could be flashed from any step, I mean it doesn't make sence which version of ROM or recovery you are using now, custom or stock, you can try RUU HBOOT 2.16. So start from there is you want to be finally on CM13.

Once you flash HBOOT2.16 RUU you will get stock rom, which run on HBOOT2.16 but pretty out of the date. Still you can run rumranner or whatever the name of exploiter to get su/root then you can do S-OFF, and flash custom recovery (I believe after RUU your recovery will go back to stock one), and then flash unofficial CM13 from this thread.
[HTC One S] Flippy498:
The RUU for firmware 4.05.401.1 (hboot 2.16) is custom made since that firmware never got released officially by HTC but was leaked by llabtoofer. Hence it's not signed correctly and you need S-OFF if you want to flash it.
[HTC One S] htc-2016:
This sound's like the short way! I didn't realized there is a RUU with hboot 2.16! If you could give a Link I will post it in Thread #1 and other people have to suffer less ;)

Anyway I go up further! I flashed ViperOne (thx to Flippy) and managed to S-OFF with rummrunner my HTC One S finally! So now there is SuperCID & Upadte HBoot left before flashing CM13.... It takes a whole weekend in total :laugh: This phone is unpayable!!

Just wondering how I get this tamperd/red warning text away.... It's just a little annoying ;) Found this one [MENTION=3012476]rumrunner[/MENTION].us: http://rumrunner.us/hboots/

Features:

Full set of fastboot flash commands
Full set of fastboot erase commands
Full set of fastboot oem commands (eng-hboot command set)
Removes red banner
Removes tampered text

HTC one (EU)	2.24.401.8	hboot_rumrunner_2.24_401.8.zip

But it's v 2.24.xxx ???
[HTC One S] htc-2016:
Went wrong! Fixed now, thanks for reporting :cool:
[HTC One S] Bad.Fish:
http://xdaforums.com/showthread.php?t=1777223 to get rid of red text [emoji123]

from my HTC One S on Marshmallow biyatch.....
[HTC One S] fax11:
Hi

Are you sure that you need supercid ? My phone is not and I could push CM13 without any problem...

Last build made the phone a little bit hot and slow sometimes but it's ok ?
[HTC One S] The Setlaz:
Don't bother with SuperCID if you are S-OFF and can install CM13... Although, now that you are S-OFF, getting SuperCID should just be 1 fastboot command away :o :

fastboot oem writecid 11111111
[HTC One S] htc-2016:
Oh YEAH! Got it all! Holy sunday! My phones run'S CM13 now.

Got the modded_hboot_2.16 without the red text from here: http://xdaforums.com/showthread.php?p=39216236#post39216236

Thank's everybody!! 3 days of work would have been 30 days work without you! :highfive:
[HTC One S] The Setlaz:
Eventually! Congrats :good:

You're good to write new guide: "CM13 Install from stock: Taking the scenic route" :silly:
[HTC One S] htc-2016:
Tried encryption with the help of the wiki: https://wiki.cyanogenmod.org/w/Known_Issues_page_for_ville

Full Battery

Wall Charger

Flight Mode

-> The Phone worked, rebooted and

say's it's encrypted now

:good: How can I check if it worked out with the encryption?
[HTC One S] moozon:
New build CM13 from 2016/05/29. Only for Hboot 2.16 Changelog
[HTC One S] Jnanadarshan:
USB Debugging by Default

Bro awesome work. Please enable USB Debugging by default.
[HTC One S] leon90xs:
guys if i have another custom rom ([ROM][JB 4.2.2][Sense 5][27.10] ME ROM Classic | Sense 7 Blinkfeed)

i need also flash .zip of this rom? or need another steps?
[HTC One S] Spezi_Ist_Spitze!:
Ahoi!

No root included in this rom? Which SU works for this?

Thanx'a'lot!
[HTC One S] Flippy498:
Did you try enabling root in the developer options?

I'm using SuperSU version 2.65.
[HTC One S] The Setlaz:
Enable root in Developer Options.
[HTC One S] derkleinebroicher:
Is camera working again on latest release?
[HTC One S] The Setlaz:
Unfortunately no. Other camera still work though.
[HTC One S] Bad.Fish:
Use open camera

from my HTC One S on Marshmallow biyatch.....
[HTC One S] Bad.Fish:
I just tested browser and seems to be working now

from my HTC One S on Marshmallow biyatch.....
[HTC One S] LS.xD:
I tried it several times without success. And I'll give it another try :)

Full Battery

Wall Charger

Flight Mode

--> same problem as before :( I'll try a clean installation.

--> Clean CM13 installation: same problem as before :(

--> Spent some more hours without any success

--> I'm back on 12.1 *cry*
[HTC One S] The Setlaz:
Here's a logcat from Snap camera crash:

http://pastebin.com/aFb0UttP

And the same without the DEBUG stuff and what seemed irrelevant:

http://pastebin.com/7nq3Lc47

[MENTION=1815755]intervigil[/MENTION] or anyone taking a look at the code :good:
[HTC One S] pavel.bosco:
seems that battery usage is improved.

maybe it is just some trick with showing battery drain by exponent (slowly at the start and then faster to the end), but phone alive for more than 1 day, and it is only 50% loss of the battery.

but I didn't use it too much. maybe 1 call for some 20 minutes and basically that's it.

still this is quite good for 4 years old phone/battery.
[HTC One S] moozon:
New build CM13 from 2016/06/03. Only for Hboot 2.16. Changelog for ville
[HTC One S] Ganzuas:
What about to use another kernel? Do you think there's any supported?

Thanks in advance.

The ROM is f****** awesome.
[HTC One S] jja2000:
Which partitions can I make f2fs? I can see the instruction in the OP but it's not very clear what partitions to do it with.
[HTC One S] The Setlaz:
/cache partition benefits most from f2fs.

/data and /system partitions can also be made f2fs (that's what I did) although /system is read-only under regular usage (i.e: not updating system) and ext4 format is supposedly slightly better for that but that may not last as f2fs is still under active development.
[HTC One S] qd42:
Is it possible to install SuperSU on this ROM? I'm getting an error when I'm trying to update SU binary in a normal mode and getting a bootloop after flashing in through recovery.
[HTC One S] derkleinebroicher:
Yes! I use the beta version, which I flashed from recovery. You can get it from here:

http://xdaforums.com/showthread.php?t=1538053

Search for the TWRP flashable zip
[HTC One S] qd42:
Worked for me! Thank you for advice.
[HTC One S] Bad.Fish:
New build is awesome... Thanks

from my HTC One S on Marshmallow biyatch.....
[HTC One S] htcones:
drmserver crashes in CM 13.0

In the CM 13.0 build for the HTC One S there appears to be no working DRM implementation. Review of adb logcat shows that the drmserver process repeatedly crashes with the back trace showing issues with /system/vendor/lib/libWVStreamControlAPI_L1.so using libstlport.so. The crashes can be prevented if you take libstlport.so from CM12.1 (a suggestion found for what appeared to be the same issue with another device), but that still does not yield a working DRM implementation as the DRM failure moves to not being able to load the native module for MediaDrm.java. Interestingly enough, if you compare the DRM files in the stock HTC Jellybean 4.1.1 release it contains libWVStreamControlAPI_L3.so which makes me wonder if the the correct versions of the Widevine modules are being used for this phone. I am new to building Android so am trying to dig my way through debugging this kind of issue.

My upgrade to CM 13.0 was via a dirty flash on top of CM 12.1 with an apply of Open-Gapps 6.0 Micro. I have tried with my own builds and that from Moozon

Anyone have any advice on how to diagnose DRM type issues?

I am pretty sure CM12.1 had a working DRM implementation, I will have to restore a backup from pre CM 13 to examine the logs for that release and check the output of apps like DRM Info.
[HTC One S] Hauk92:
It seems like libWVStreamControlAPI_L1.so was recently updated: https://github.com/TheMuppets/propr...ietary/vendor/lib/libWVStreamControlAPI_L1.so Maybe the older version works?

There is a 4.2.2 firmware dump which also only uses libWVStreamControlAPI_L3.so.

libWVStreamControlAPI_L3.so was apparently used in CM once but is not anymore(?).
[HTC One S] ginzo96:
Please do a 2.15 hboot flashable version
[HTC One S] letsurock:
Memory constraint, it might never happen.
[HTC One S] Zoucz:
After like 10+ hours of messing with S-OFF in every possible way and switching to hboot 2.16, I finally booted into this CM 13. I am very impressed so far and looking forward to future updates. Great job, guys!
[HTC One S] Bad.Fish:
Switch to 2.16 its not that hard

from my HTC One S on Marshmallow biyatch.....
[HTC One S] vp1407:
Anyone with a working FM radio? Or anyone who knows how to get it to work?

Mine opens, but toasts "currently not available" when I press the play button.
[HTC One S] derkleinebroicher:
For me, the pre-installed fm radio works.
[HTC One S] vp1407:
Strange, I checked again by doing a clean flash of the latest cm13 version, but it still won't work.

The FM radio worked fine on my previous ROM (SlimLP).
[HTC One S] Hauk92:
Which nightly are you using?
[HTC One S] derkleinebroicher:
It's the one from 2016.06.03 - which is the last one I guess.
[HTC One S] htcones:
FM radio not working for me either

I have the same issue. Seems to fail the power up of the FM hardware. Logcat shows this

android_hardware_fm: FM patch downloader failed: -1

---------- Post added at 01:17 ---------- Previous post was at 01:04 ----------

Are you running an updated wcnss image? If so, which one did you apply, I have tried both the JB4.1.1 version and the one packaged with the 1.20 cel radio package.
[HTC One S] derkleinebroicher:
You're right, concerning the wcnss image. I'm on 1.35 radio, which I flashed a looooong time ago as a package with an updated wcnss. Here is a link - the download links still work, I have tested this. You can get a radio + wcnss + adsp package or flash the updated wcnss separately. As far as I remember, some people seem to have had troubles with their data connection, using the 1.35 radio. So for the first I would suggest to flash the wcnss.zip only.
[HTC One S] Lincoln99:
After a bit of trial and error I managed to get this installed and working. As an added bonus, multi window (mostly) works.
[HTC One S] Bad.Fish:
What is demo mode? I repeatedly pressed build date and demo mode menu opened

from my HTC One S on Marshmallow biyatch.....
[HTC One S] htcones:
Unfortunately the updated wcnss did not change the situation :( I will have to dig through the logs some more to see if I can see where things go wrong.
[HTC One S] IamModeste:
on 20160605 - Flashlight from quick tiles still crashed after some seconds, FM radio was still unavailable and camera was still crashing when taking a picture.

I'm dirty flashing 20160609 right now will report if there is any improvement.

Moozon, your ROM is awesome and so are you !

After flashing the differences i see are: all flashlight apps don't work anymore .

Flashlight from quick tiles disappeared and Open camera doesn't work anymore too, even after reinstall.
[HTC One S] The Setlaz:
Running 20160614, still same issues with Flashlight, FM Radio and stock Camera not taking pictures.
[HTC One S] htcones:
I believe the issue is selinux permission related but I don't know enough about the permission model yet to come up with a solution, every time it fails the following log entry appears

06-11 00:12:22.527 28241 28241 W setprop : type=1400 audit(0.0:29): avc: denied { write } for name="property_service" dev="tmpfs" ino=5701 scontext=u:r:toolbox:s0 tcontext=u:object_r:property_socket:s0 tclass=sock_file permissive=0

Anyone with suggestions on how to deal with this?
[HTC One S] Bad.Fish:
Selinux mode changer apk I have mine set to permissive

from my HTC One S on Marshmallow biyatch.....
[HTC One S] Bad.Fish:
FM radio started working after I force stopped in system settings

from my HTC One S on Marshmallow biyatch.....
[HTC One S] IamModeste:
Thank you bad.fish ! FM radio started working for me too after I force stopped the app !
[HTC One S] htcones:
I can confirm that if I set SELinux to permissive (setenforce 0), I was able to get the FM radio to work. Just need to work out how to use audit2allow to generate the appropriate policy to get a permanent fix for this.

type=1400 audit(0.0:157): avc: denied { write } for name="property_service" dev="tmpfs" ino=5701 scontext=u:r:toolbox:s0 tcontext=u:object_r:property_socket:s0 tclass=sock_file permissive=0
[HTC One S] htcones:
Having worked through the pain of Marshmallow using the new sepolicy db format I was able to use the prebuilt audit2allow to generate the selinux allow rule.

allow toolbox property_socket:sock_file write;

The questions now becomes, which is the correct file to place the statement in, is it overly permissive and is there a more appropriate fix? An obvious file choice is ./external;/sepolicy/toolbox.te
[HTC One S] camilogod:
If I already have cm 11 or cm 12.1 installed, can I just flash the rom like usual? or do I have to go back to stock?
[HTC One S] htcones:
I installed with the updated gapps directly over cm 12.1, wiped davlik and cache and was good to go. Just be sure to choose the gapps package that matches your existing gapps. In other words if you used a mini before, use mini gapps again.
[HTC One S] Lacostenika:
i have s4 2.15 how to upgrade to 2.16 ? help pls :( i want cm 13
[HTC One S] bakmanhans:
Do a search on one of the HTC threads. Been asked many times before.
[HTC One S] camilogod:
thanks, did you have to be s-off and supercid and boot 2.16?