[ROM][4.4.3] CyanogenMod 11 for HTC One S

Search This thread

rootrider

Senior Member
Aug 21, 2010
854
387
Starnberg
I actually upgraded it some days ago, but to be safe I ran a diff on the newest and the one I'm using.

There was one about two days ago, if I remember right. So it is possible you caught that already.

If the problem still exists, delete everything from inside the 'out/target/product/ville' directory and restart compiling. Or simply delete the ville directory... :)
 

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
Blacklist

Anyone have a trick for blacklisting whole area codes? I almost never use my phone as a phone, so much of my call log is dominated by numbers from Grenada and Caribbean islands...scammers who hang up after one ring in the middle of the night, hoping for a return call they can charge you for. I can blacklist individual numbers, but it's never the same number twice.
 

eabinsan

Senior Member
Sep 24, 2009
78
26
So, as a workaround I built myself a kernel with accessory detection disabled. I can boot the zImage just fine, but i can't flash it with fastboot flash zimage (permission denied)

I also tried to build a boot.img, using the current nightly as a base for unmkbootimg and mkbootimg

Code:
mkbootimg --kernel arc/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' -o new_boot.img

unfortunately, this just leads to a boot loop :( any advice?

found the solution, i needed to add ramdiskaddr:

Code:
mkbootimg --kernel arch/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' --ramdiskaddr 0x81a00000 -o my_boot.img
 

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
Bone city. Here's the final chunk of a last_kmsg I pulled, if it's any help.

Code:
[  340.838241] [PS][cm3629] psensor_disable 0
[  340.842331] [PS][cm3629] psensor_disable: already disabled
[  340.849259] [PS][cm3629] psensor_ioctl cmd 1
[  341.035403] [BATT][CHG] eoc_worker: eoc_count: 0, eoc_count_by_curr:0, pj_chg_full: 0
[  341.064245] [COMP] Compass enable
[  341.066870] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  341.073889] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  341.080817] [COMP][AKM8975] [COMP] Compass disable
[  341.087227] [COMP][AKM8975] AKECS_GetCloseStatus:
[  341.087257] [GSNR] Gsensor enable
[  341.087257] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[  341.102945] [GSNR] Gsensor disable
[  341.105539] [GSNR][BMA250] BMA_set_mode: mode = 0x01
[  341.120860] [COMP][AKM8975] AKECS_GetOpenStatus:
[  341.274256] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  341.279322] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  341.286738] [PS][cm3629] psensor_ioctl cmd 2
[  341.290218] [PS][cm3629] psensor_disable 0
[  341.295559] [PS][cm3629] psensor_disable: already disabled
[  341.301113] [PS][cm3629] psensor_release
[  341.884968] request_suspend_state: wakeup (0->0) at 341870883244 (2014-02-02 02:40:09.385495951 UTC)
[  345.655424] [LS][cm3629] lightsensor_open, calibration:1
[  345.659758] [LS][cm3629] lightsensor_ioctl LIGHTSENSOR_IOCTL_GET_ENABLED, enabled 0
[  345.667785] [LS][cm3629] lightsensor_release
[  345.804272] [PS][cm3629] psensor_open, calibration:1
[  345.809583] [PS][cm3629] psensor_disable 0
[  345.814161] [PS][cm3629] psensor_disable: already disabled
[  345.818892] [PS][cm3629] psensor_ioctl cmd 1
[  346.005585] [COMP] Compass enable
[  346.008240] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  346.018098] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  346.019441] [COMP][AKM8975] AKECS_GetCloseStatus:
[  346.028444] [COMP][AKM8975] [COMP] Compass disable
[  346.033236] [GSNR] Gsensor enable
[  346.036532] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[  346.043857] [GSNR] Gsensor disable
[  346.046299] [GSNR][BMA250] BMA_set_mode: mode = 0x01
[  346.053654] [COMP][AKM8975] AKECS_GetOpenStatus:
[  346.194262] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  346.199328] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  346.206073] [PS][cm3629] psensor_ioctl cmd 2
[  346.210224] [PS][cm3629] psensor_disable 0
[  346.214161] [PS][cm3629] psensor_disable: already disabled
[  346.219655] [PS][cm3629] psensor_release
[  346.636838] request_suspend_state: wakeup (0->0) at 346622752616 (2014-02-02 02:40:14.137365323 UTC)
[  350.594201] [LS][cm3629] lightsensor_open, calibration:1
[  350.598565] [LS][cm3629] lightsensor_ioctl LIGHTSENSOR_IOCTL_GET_ENABLED, enabled 0
[  350.606744] [LS][cm3629] lightsensor_release
[  350.734259] [PS][cm3629] psensor_open, calibration:1
[  350.738287] [PS][cm3629] psensor_disable 0
[  350.742316] [PS][cm3629] psensor_disable: already disabled
[  350.749549] [PS][cm3629] psensor_ioctl cmd 1
[  350.975736] [COMP] Compass enable
[  350.978116] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  350.983732] [COMP][AKM8975] AKECS_GetCloseStatus:
[  350.983763] [GSNR] Gsensor enable
[  350.983763] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[  350.997070] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  351.004455] [COMP][AKM8975] [COMP] Compass disable
[  351.008576] [GSNR] Gsensor disable
[  351.011902] [GSNR][BMA250] BMA_set_mode: mode = 0x01
[  351.029024] [COMP][AKM8975] AKECS_GetOpenStatus:
[  351.035403] [BATT][CHG] eoc_worker: eoc_count: 1, eoc_count_by_curr:0, pj_chg_full: 0
[  351.214283] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[  351.219380] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is  times.
[  351.225942] [PS][cm3629] psensor_ioctl cmd 2
[  351.230062] [PS][cm3629] psensor_disable 0
[  351.234243] [PS][cm3629] psensor_disable: already disabled
[  351.239615] [PS][cm3629] psensor_release
[  351.643674] request_suspend_state: wakeup (0->0) at 351629558658 (2014-02-02 02:40:19.144171365 UTC)
[  352.009430] resout_irq_handler PMIC Initiated shutdown
[  352.013642] PMIC Initiated shutdown cpu_power_off cpu=0
[  352.013642] PMIC Initiated shutdown cpu_power_off cpu=1
[  352.024050] [K] Powering off the SoC
[  352.027559] Calling scm to disable arbiter
[  352.031649] SCM returned even when asked to busy loop rc=-4
[  352.037234] waiting on pmic to shut msm down

16 Corrected bytes, 621 unrecoverable blocks
 

epsiblivion

Senior Member
Mar 31, 2010
138
21
Los Angeles

same. and the one time I didn't do a backup. hopefully data is intact (should be) and I can just flash the old nightly

edit: now I'm getting the old no backlight in recovery issue again...

so I reverted to the cwm 6.0.4.5 linked in OP and backlight issue is gone. now reflashed to 1/26 I was running previously. does anyone know if 1/31 is safe to flash? 2/02 is the one that didn't boot. since I didn't wipe, thank god my apps and data still there. I'm on 2.15 hboot
 
Last edited:

rootrider

Senior Member
Aug 21, 2010
854
387
Starnberg
Same thing with serranoltexx (Galaxy S4 mini, my daughters device) and maybe all/many other devices. Doesn't/don't boot. And maybe it's already fixed. I'll see...


--- edit
The ugly: nightly 2014/02/02 doesn't work
The bad: Next nightly will be working again - but you'll have to wait.
The good: You can download the fix already here: cm-11-20140202-UNOFFICIAL-ville.zip (contains all commits from 'power: Fix locking and reference passing' down)
 
Last edited:

maluus

Senior Member
Dec 26, 2010
483
69
Ankara
02/02 did not boot for me too. There is also another strangeness happening since the nightlies later than 27/01 (27/01 is the latest without problem). sometimes I could not find out the reason the phone becomes completely inresponsive. screen is off and cannot be switched on, hardware button lights are also off doesn't light up in any case. if enabled notification leds are active. and the phone is actually on. when called from other phone it appears to be ringing but actually it doesn't. And only option to get it off this state is powering down holding power button pressed and power on afterwards. this happened to me all the roms I tried after 27/01. Anyone else is experiencing something similar?

PS: as an another side note although 02/02 did not boot up it seems like somehow switched the phone from ART to Dalvik. When I reverted back to an older nightly noticed it was back to Dalvik.
 
Last edited:

F-L-Y-E-R

Senior Member
Jan 15, 2011
682
1,313
London
02/02 did not boot for me too. There is also another strangeness happening since the nightlies later than 27/01 (27/01 is the latest without problem). sometimes I could not find out the reason the phone becomes completely inresponsive. screen is off and cannot be switched on, hardware button lights are also off doesn't light up in any case. if enabled notification leds are active. and the phone is actually on. when called from other phone it appears to be ringing but actually it doesn't. And only option to get it off this state is powering down holding power button pressed and power on afterwards. this happened to me all the roms I tried after 27/01. Anyone else is experiencing something similar?

PS: as an another side note although 02/02 did not boot up it seems like somehow switched the phone from ART to Dalvik. When I reverted back to an older nightly noticed it was back to Dalvik.
Read the comments above, there's already fixed 02/02 uploaded.
 
  • Like
Reactions: rootrider

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
02/02 did not boot for me too. There is also another strangeness happening since the nightlies later than 27/01 (27/01 is the latest without problem). sometimes I could not find out the reason the phone becomes completely inresponsive. screen is off and cannot be switched on, hardware button lights are also off doesn't light up in any case. if enabled notification leds are active. and the phone is actually on. when called from other phone it appears to be ringing but actually it doesn't. And only option to get it off this state is powering down holding power button pressed and power on afterwards. this happened to me all the roms I tried after 27/01. Anyone else is experiencing something similar?

PS: as an another side note although 02/02 did not boot up it seems like somehow switched the phone from ART to Dalvik. When I reverted back to an older nightly noticed it was back to Dalvik.

I had all of these, no boot, black screen after reverting to 1/31, revert to dalvik flashing 1/31 over 2/2
 

RiffyDivine

Senior Member
May 14, 2010
907
35
Magical Land of Ponyville
I just flashed this onto my old unit to let my dad use as a replacement for his, but I forgot he had AT&T and not Tmobile. So I put in his sim and now when his sim is in the phone won't connect to anything but if I put mine for tmobile in it will work but both times it asks for the pin unlock code. So I put it in and it will error out on the tmobile network and with the AT&T sim it just won't do anything. Can you not unlock on a custom rom or was there a different radio I needed to flash alongside CM?
 

el_smurfo

Senior Member
Oct 21, 2009
3,956
1,316
I just flashed this onto my old unit to let my dad use as a replacement for his, but I forgot he had AT&T and not Tmobile. So I put in his sim and now when his sim is in the phone won't connect to anything but if I put mine for tmobile in it will work but both times it asks for the pin unlock code. So I put it in and it will error out on the tmobile network and with the AT&T sim it just won't do anything. Can you not unlock on a custom rom or was there a different radio I needed to flash alongside CM?

You probably need to call T-Mobile and ask them for the SIM unlock code.
 

nicknc

Senior Member
Dec 10, 2009
1,156
331
I just flashed this onto my old unit to let my dad use as a replacement for his, but I forgot he had AT&T and not Tmobile. So I put in his sim and now when his sim is in the phone won't connect to anything but if I put mine for tmobile in it will work but both times it asks for the pin unlock code. So I put it in and it will error out on the tmobile network and with the AT&T sim it just won't do anything. Can you not unlock on a custom rom or was there a different radio I needed to flash alongside CM?

Sim unlock is completely separate from the ROM.

Luckily, the instructions for sim unlock are well documented in a couple of threads in this forum. Pretty easy process with three options to achieve it.

If the unlock prompt is preventing you from using the device itself (it should not be), just boot without a sim.

Sent from my One S using Tapatalk
 

Aduck79

Senior Member
Dec 12, 2010
177
51
Hillerød
Hi,
I recently got hold of a used htc one s.
I immediately rooted and s-off'ed it. I flashed CM11 nightly and bubba kernel. Then I noticed that the accelerometer didn't work. Tilting in games and launcher doesn't do anything. Do you got a suggestion for what I could do, or is the sensor possibly dead?

Best regards
Anders

Sendt fra min One S med Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 112
    logo.png

    CyanogenMod 11 is a free, community built distribution of Android 4.4.3 (KitKat) which greatly extends the capabilities of your phone.

    Index:
    1st Post: Official Nightlies for HBOOT 2.15
    2nd Post: Unofficial Builds for HBOOT 2.16
    3rd Post: Changelog


    Installation Instructions (These are all required)
    • Download or Build from Source
    • Download Gapps
    • Wipe Data
    • Flash ROM in Recovery
    • Flash Gapps in Recovery
    • Incase you don't have S-OFF, fastboot flash boot boot.img

    Not Working:
    • You tell me

    Downloads (HBOOT 2.15):
    Official Nightly Builds HBOOT 2.15 Only.
    Google Apps

    Recovery (HBOOT 2.15):
    Beginning with nightly 20140501, several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires kernel support in recovery for CyanogenMod packages to install. Your current recovery is almost guaranteed to not support this change, yet... welcome to bleeding edge!
    Please read THIS
    TWRP | Mirror


    Credits:
    intervigil, h8rift, xkonni, toastcfh, deck, rohan32, flemmard and all the HTC-MSM8960 Team Members.

    XDA:DevDB Information
    CyanogenMod 11, ROM for the HTC One S

    Contributors
    RockR172, intervigil
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Hboot 2.15.xx, S-OFF, Unlocked Bootloader, Custom Recovery
    Based On: CyanogenMod

    Version Information
    Status: Stable

    Created 2013-11-15
    Last Updated 2014-06-09
    49
    CyanogenMod 11 for HBOOT 2.16

    CyanogenMod 11 is now available for HBOOT 2.16

    NOTICE: Due to lack of free time and also not owning an HTC One S anymore, I can no longer compile builds for HBOOT 2.16.
    Worry not, @cikoleko does Nightly builds for HBOOT 2.16 which can be found HERE
    25
    Changelog:

    Latest, more accurate Changelog for Nightlies/Unofficial Builds can now be found HERE.

    cm-11-20131207-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Android 4.4.1

    cm-11-20131206-UNOFFICIAL-ville.zip

    cm-11-20131202-UNOFFICIAL-ville.zip
    • Latest CM Source
    • Hardware Button Configuration is now back

    cm-11-20131129-UNOFFICIAL-ville.zip
    • Latest CM Source

    cm-11-20131125-UNOFFICIAL-ville.zip
    • Latest CM Source - New boot animation and more stuff!

    cm-11-20131122-UNOFFICIAL-ville.zip
    • Latest CM source - Re-introduces Quick Settings and Notification drawer settings
    • Other misc changes to device and kernel sources
    • AOSP release 4.4_r1.2 KRT16S

    cm-11-20131119-UNOFFICIAL-ville.zip
    • Can now be flashed on regular recoveries like TWRP
    • Cherry picked new Audio patches
    • Latest CM source

    cm-11-20131117-UNOFFICIAL-ville.zip
    • Camera App now actually works
    • Some other fixes

    cm-11-20131116-UNOFFICIAL-ville.zip
    • Audio Fixed
    • Bluetooth Works
    • Video Playback

    cm-11-20131115-UNOFFICIAL-ville.zip
    • First Release
    • Fixed SD Card
    • Fixed WiFi
    19
    Okay, with a heavy heart I have to say that I can no longer do builds for hboot 2.16.
    I have too much college work, assignments, practicals n stuff and can't afford to spend time compiling builds in Linux.. :(
    I did try to do builds past few days, but couldn't..
    My advice is, downgrade your hboot to 2.15 and get daily official builds from CyanogenMod. It is not really that difficult/scary to downgrade. I have done it a couple of times when i wanted to test my hboot 2.16 builds when i was on hboot 2.15.
    Also, if anyone wants to do builds for 2.16 feel free to post it in the thread..
    Sorry guys, I tried my best. :)
    Big ups to intervigil and rest of the CM team, you guys rock! \o/ \m/
    18
    Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.

    It's kind of disheartening to see so many people ascribe so many shady ulterior motives to the company (we have no plans for world domination, and it really is discouraging to see so many people knee-jerk react negatively), but ville support hasn't been so great lately, so I figure I owe you an explanation.
    CM Inc is my day job, device support mostly remains a side project for me. The company and open source organization (which are two separate things) has little to do with deciding which devices get support, and to what degree. Device maintainers are largely responsible for the kernels and device trees that actually determine how well most of the device hardware is supported.
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