HTC ONE S codefireX

Search This thread

truevision

Senior Member
Feb 5, 2013
793
95
Redmi Note 10
Redmi Note 11
Nope , no md5 on download site. That's something I've asked for before, just never got implemented by our server guy. I'll bring it up again

Sent from my One Xl using Tapatalk

Thanks.
Yesterday I tried to flash codefirex on my ville, no success, still loop on boot.
This rom is for all HTC One S S4 ? I had read all thread and I don't found something about that...
 

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
Thanks.
Yesterday I tried to flash codefirex on my ville, no success, still loop on boot.
This rom is for all HTC One S S4 ? I had read all thread and I don't found something about that...

I had another report on Evita, same issue. Grab a nightly from a few days ago, until I can figure out what's up with the current builds.

Sent from my One Xl using Tapatalk
 

AKToronto

Senior Member
I had another report on Evita, same issue. Grab a nightly from a few days ago, until I can figure out what's up with the current builds.

Sent from my One Xl using Tapatalk

For me bootloops would happen whenever I committed the kernel commit make_config_strict_memory_rwx even stricter... Revert that one commit on the kernel and it all works fine again. It's a security patch but for whatever reason reverting it seems to help. At least in my case. I have kept it reverted in my custom kernel for now.

Sent from my One S using Tapatalk
 

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
For me bootloops would happen whenever I committed the kernel commit make_config_strict_memory_rwx even stricter... Revert that one commit on the kernel and it all works fine again. It's a security patch but for whatever reason reverting it seems to help. At least in my case. I have kept it reverted in my custom kernel for now.

Sent from my One S using Tapatalk

Testing kernel of yours on this ROM? CM is using that commit without issue...

Sent from my One Xl using Tapatalk
 

AKToronto

Senior Member
Testing kernel of yours on this ROM? CM is using that commit without issue...

Sent from my One Xl using Tapatalk

Yes I know it works on cm11 without issue. But when I try booting codefire ROM, it doesn't work unless I revert that commit... Anyways it may be something specific to my custom kernel of course. But take a look at when the complaints started and when the bootloops start... My guess is it will be around the time you added this commit to the codefire stock kernel... It may not be answer but it's worth looking into.

Edit: and by flashing my custom kernel over the stock I have been able to boot the ROM even with some of the more recent nightlies...
Sent from my One S using Tapatalk
 
Last edited:

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
Yes I know it works on cm11 without issue. But when I try booting codefire ROM, it doesn't work unless I revert that commit... Anyways it may be something specific to my custom kernel of course. But take a look at when the complaints started and when the bootloops start... My guess is it will be around the time you added this commit to the codefire stock kernel... It may not be answer but it's worth looking into.

Edit: and by flashing my custom kernel over the stock I have been able to boot the ROM even with some of the more recent nightlies...
Sent from my One S using Tapatalk

Thank you sir, appreciate the info.

Sent from my One Xl using Tapatalk

Edit: this was indeed the issue, still not sure why though. Reverted for now until I find the root problem. Nightly for 3/11 will be goog to go.
 
Last edited:

cannondaleV2000

Senior Member
Mar 24, 2013
1,099
963
I use that commit in my kernel on this rom 2 days ago and it worked fine


Sent from my iPad using Tapatalk

---------- Post added at 03:04 AM ---------- Previous post was at 03:02 AM ----------

I was haveing an issue with uploading to my western digital my cloud server on the 3-08 nightly with the western digital app


Sent from my iPad using Tapatalk
 

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
@rmbq, take a look at the last page or 2 of my CFX thread. That same error message reported in your kernel thread is what I got with with the commit referenced here. Still haven't figured out why though unfortunately.

Sent from my One X using Tapatalk
 
Last edited:

rmbq

Senior Member
Feb 10, 2012
985
1,903
32
@rmbq, take a look at the last page or 2 of my CFX thread. That same error message reported in your kernel thread is what I got with with the commit referenced here. Still haven't figured out why though unfortunately.

Sent from my One X using Tapatalk

i read that icecode kernel can't boot with strict_rwx stuff but i don't think it's the problem because i'm using my kernel with that patch on your ROM (20140305) without issue. a guy had got ramdisk issue also with an older version of my kernel that didn't have strict_rwx patch. atm i dunno where is the problem.
 

cannondaleV2000

Senior Member
Mar 24, 2013
1,099
963
i read that icecode kernel can't boot with strict_rwx stuff but i don't think it's the problem because i'm using my kernel with that patch on your ROM (20140305) without issue. a guy had got ramdisk issue also with an older version of my kernel that didn't have strict_rwx patch. atm i dunno where is the problem.

yeah iv been running my kernel with that commit on this rom with no problem. and i forked cfx ad my bass for my kernel. i just have not released my kernel yet but its running fine on this rom with the strict_rwx commit
 

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
i read that icecode kernel can't boot with strict_rwx stuff but i don't think it's the problem because i'm using my kernel with that patch on your ROM (20140305) without issue. a guy had got ramdisk issue also with an older version of my kernel that didn't have strict_rwx patch. atm i dunno where is the problem.

Appears its a ramdisk offset issue. Something in that commit increased the size of the zimage. CFX stock kernel compiles at -o2 already so with modules included and now this I had to bump the offset up a bit, otherwise the base of the ramdisk is overwritten by the kernel and can't be found. I assume since AKToronto uses -o3 his offset will need to be even higher. I confirmed all of this on Evita both stock and with my custom kernel for Evita as well.

Sent from my One X using Tapatalk
 
  • Like
Reactions: rmbq

cannondaleV2000

Senior Member
Mar 24, 2013
1,099
963
Appears its a ramdisk offset issue. Something in that commit increased the size of the zimage. CFX stock kernel compiles at -o2 already so with modules included and now this I had to bump the offset up a bit, otherwise the base of the ramdisk is overwritten by the kernel and can't be found. I assume since AKToronto uses -o3 his offset will need to be even higher. I confirmed all of this on Evita both stock and with my custom kernel for Evita as well.

Sent from my One X using Tapatalk

What size is your zimage normaly?

Sent from my One S using Tapatalk
 

cannondaleV2000

Senior Member
Mar 24, 2013
1,099
963
I compared on my custom kernel because i had it queued up already...

W/o that commit zimage is 7268560 bytes

With commit its 7272848 bytes.
Its a small change but it definitely an increase

Sent from my One X using Tapatalk

Wow woth that commit the one for my custome kernel is aboit 4.6mb

Sent from my One S using Tapatalk
 

AKToronto

Senior Member
Wow woth that commit the one for my custome kernel is aboit 4.6mb

Sent from my One S using Tapatalk

Yes you are likely using o level optimization to get a small zImage. Thanks for the help jrior. It seems that this may only be an issue on kernels compiled on higher levels of optimization, hence why it didn't affect stock cm11 either...

Sent from my KFAPWI using Tapatalk
 
  • Like
Reactions: jrior001

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    HTC ONE S codefireX

    pre_1390702648__cfxsig1.png

    CodefireX 4.4.3.2.1.000.000 Open Master


    pre_1391201081__hamag.png

    This well established Android distribution treats development differently than any other to further our Android platform as a whole. This is the fastest source built ROM you will find on this forum, and also the only one to utilize our unique build system and a custom LLVM 3.5 suite based toolchain globally.

    Here is our very well supported Issue Tracker.
    pre_1391201054__9l5fz.png

    We utilize a plethora of unique optimizations in a build system unlike any other:

    • Utilizing the LLVM CLANG CI globally, working heavily with upstreams with a goal of furthering our entire Android platform.
    • Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
    • Fully built utilizing Link Time Optimization and Polly optimizations (another custom ROM first). Feel free to google these a bit.
    • Much of our source have code fixes, cleanups, and many minor optimizations to set us even further ahead of the community. These are too generous to even speak of here.
    • Optimizations are toggled on and off based on device for the best experience we can achieve for your device without sacrificing stability
    • Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
    • Fully built utilizing strict aliasing and isognu++11 mode.
    • Utilizing all O4 optimizations (Optimization Level 4) including LTO (with binutils plugins), and additionally LLVM Polly.
    Of course we also have several neat UI features, including but not limited to:
    • T-Mobile Theme Engine.
    • DPI Wizard (no junk like build.prop tweaks).
    • Quick Settings panel customizations.
    • Live network stats in your statusbar.
    • Button backlight customizations.
    • Hardware button customizations.
    • Volume button customizations.
    • Many more being added during the nightly builds.

    pre_1391201067__d92id.png

    Ville Download & Support thread

    pre_1391201095__lpnqc.png

    Our thanks go out to all the open source developers who made our work possible.
    Below is an ever-incomplete list of some of the 'indirect' contributors to our ROMs:
    • The Android Open Source Project
    • LLVM CI
    • Linux Foundation
    • Code Aurora Forum
    • CyanogenMod Inc.
    • Chainfire
    • The entire 8960 CM team for making this device relevant still!!
    • Many more!



    XDA:DevDB Information
    HTC ONE S codefireX, ROM for the HTC One S

    Contributors
    jrior001, http://xdaforums.com/member.php?u=470268, synergye, bigrushdog, anders3408, RaymanFX, ajf64, rlasalle15, Roach, ConnorBaker
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    Based On: AOSP + Win

    Version Information
    Status: Stable
    Current Stable Version: nightlies

    Created 2014-02-01
    Last Updated 2014-02-01
    5
    I have a question, concerning the nightlies - it's just to be sure. For each device there is under "last changes" always "no changes since last build".. Is this reliable, cause if there are no changes, it does not make to much sense for me, to flash the same Rom again and again.


    We'll I'm sure they sync with upstream cm every day

    No its not acurate...Jenkins just hasn't been set up to display the changelogs(some thing for our leader to look into though). I maintain all 4 of our 8960 devices (ville, jewel,Evita,and fireball) and keep a good eye on CM and others for device specific changes that I can incorporate. May not be daily but I don't like to be behind :)

    Today's builds should have fixes for most of the app related issues that have been reported thus far. Only exception is the FC that was reported with email app. That should be fixed in tomorrows builds.

    Sent from my iPad using Tapatalk



    Sent from my One Xl using Tapatalk
    2

    Requires the newer firmware like cm. Not 100% up on which hboot s there are for ville. Just don't use the newest one the messes up sdcard.

    Sent from my One Xl using Tapatalk
    2
    Sad day in the CFX world. CFX as we know it now is dead. Our 2 main leaders have parted ways with a difference of opinion in the future direction of the project. Thanks to all who have participated in this.

    Mods its time to close up shop here.

    Sent from my SCH-i705 using Tapatalk

    It is a real shame indeed. Thx for all your help though in maintaining the Rom for our device too!

    Sent from my One S using Tapatalk
    2
    Having fun with codefire so far. Created a custom kernel off of codefire kernel sources and it's running well. Not too many features yet. But I will post it if people are interested.

    There are a few feature requests I have. In cm you can normally add sound/vibrate/mute toggle to quick settings as well as flashlight... maybe these don't exist yet in the base? Also I don't see advanced reboot menu in dev options...

    Sent from my KFAPWI using Tapatalk

    Right now its hiding under settings/buttons. I may be missing the overlay for flashlight but I'll have to check on the other tiles.

    Sent from my One Xl using Tapatalk