Introducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either. We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!
Warning: we only support anykernel methods of custom kernel installation.
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
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 (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any 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.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU Zip
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
**This uses the 3.4 cm kernel tweaked for gcc-4.8 builds and as such,
follows all the same requirements as CM-10.2. NEWEST FIRMWARE/HBOOT are required. **
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash SuperSU zip
Reboot
Thank you for choosing codefireXperiment - See more at: http://www.codefirex.com/index.php?...htc-one-xl-codefirexperiment-nightlies#latest
CHAT on IRC Freenode #codefirex
PHABRICATOR - review system
GITHUB
Thanks to the CM team for all thier work on this family of devices, especiallly h8rift for his work on evita for all of us to enjoy.
Also thanks to my beta testers for experimenting with me.
DISCLAIMER: I will not be held responsible for any damages caused to your device by flashing this ROM. Your warranty is now void.
By proceeding you accept the risks involved with flashing ROMS. While I test everything on my own device, I cannot garauntee yours will not explode into kittens and rainbows.
KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.
mine too
jrior001 said:
KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.
Click to expand...
Click to collapse
Forgot to say that I didn't get the boot animation bug.
Darknites said:
Forgot to say that I didn't get the boot animation bug.
Click to expand...
Click to collapse
Its possible it's just the larger boot animation, I choose a smaller one for this device as it has a smaller screen than evita/jewel. the m7 devices were having the same struggles with it. It's a minor issues at this point, it will be fixed soon. I just don't want people to panic over it if they see it freeze up.
jrior001 said:
Its possible it's just the larger boot animation, I choose a smaller one for this device as it has a smaller screen than evita/jewel. the m7 devices were having the same struggles with it. It's a minor issues at this point, it will be fixed soon. I just don't want people to panic over it if they see it freeze up.
Click to expand...
Click to collapse
Oh right, oh and is this newer than the one I got already?
Darknites said:
Oh right, oh and is this newer than the one I got already?[/QUOTE
Check the time on it but I think it's the same build I set you yesterday.
Click to expand...
Click to collapse
jrior001 said:
Check the time on it but I think it's the same build I set you yesterday.
Click to expand...
Click to collapse
Ya same one so no need to flash anything lol.
Source?
Sent from my SCH-R970 using XDA Premium 4 mobile app
Zarboz said:
Source?
Sent from my SCH-R970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added link to OP
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
S-on? Did you fastboot flash the boot.IMG?
This is required if you are still s-ON
Edit: added this instruction to the OP.
Sent from my One Xl using Tapatalk 2
jrior001 said:
S-on? Did you fastboot flash the boot.IMG?
This is required if you are still s-ON
Edit: added this instruction to the OP.
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yes i fastboot the boot.img
yooouuri said:
Yes i fastboot the boot.img
Click to expand...
Click to collapse
Have you been able to run other 4.3 roms ? are you sure you are on the latest firmware?
There have been a few other people that downloaded has anyone else had any bootloop issues like this?
This build was tested and confirmed working by Darknites, not that that means it's without any isues, just surprising. Hopefully we can get a few other to confirm if theres an issue as I do not have a One S to test with.
Yes i run the last CM nightly. And some other 4.3 roms ran without problems.
yooouuri said:
Yes i run the last CM nightly. And some other 4.3 roms ran without problems.
Click to expand...
Click to collapse
Sounds like you've done everything right so far so im not entirely sure whats up. Did you attempt to reflash or just jump bacl to another rom after the issue? I'd like to see some more feedback from a few other users as well before I start digging into anything.
Sent from my One Xl using Tapatalk 2
yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
Did you restore any app data? Also did you triple wipe
Sent from my HTC VLE_U using xda app-developers app
jrior001 said:
Sounds like you've done everything right so far so im not entirely sure whats up. Did you attempt to reflash or just jump bacl to another rom after the issue? I'd like to see some more feedback from a few other users as well before I start digging into anything.
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Now im runnig the nightly from 08/30. With no problems.
Just wiped cache dalvik system and data. If you can tell me how to make a logcat from the boot. I can help you tomorrow?
yooouuri said:
Now im runnig the nightly from 08/30. With no problems.
Just wiped cache dalvik system and data. If you can tell me how to make a logcat from the boot. I can help you tomorrow?
Click to expand...
Click to collapse
Your running which nightly from 8/30? You got this ROM up and running or another like carbon or cm?
Sent from my One Xl using Tapatalk 2
yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
Save some time using factory reset in twrp which will wipe all that is need other than system which roms already wipe anyway so try like that instead and also flash the boot.img before the rom.
Related
*******
Download KitKat 4.4.4 KTU84P stock odex All-F2FS rom
(thanks to bshiznit for the base)
(thanks to Legolas93 for all F2FS work)
- To enable busybox run-parts (init.d scripts) flash this zip
(thanks to brainmaster, from Rastakat thread)
- To install Superuser install this zip
*******
AN ALTERNATIVE:
Vanilla by rascarlo
(original thread)
1a. Flash Vanilla by rascarlo KK4.4.4 ALLF2FS- 2014-07-09
1b. Flash Vanilla by rascarlo KK4.4.3 ALLF2FS- 2014-06-10
2. Install PA Mini Gapps:
Android File Host
Dev-Host
3. Enable busybox run-parts (init.d scripts) flashing this zip
(thanks to brainmaster, from Rastakat thread)
4. Install Superuser flashing this zip
***********
SUGGESTION:
If you want to flash an F2FS kernel with only ramdisk (carcosa, faux, oxydo, ...) i suggest to flash latest M-Kernel before, since M-Kernel has an optimized ramdisk (so the new kernel will use M-Kernel's ramdisk).
Anyone install this?
I downloaded this, but was wondering if anyone has installed it and what they thought so far.
The_Engine said:
I downloaded this, but was wondering if anyone has installed it and what they thought so far.
Click to expand...
Click to collapse
It is really smooth, since it is odex.
You will not be disappointed.
So far so Good
Up and running and setting everything up. Nice and smooth so far. Will report back after more use.
Only 273 MB? What did you remove?
edisso10018 said:
Only 273 MB? What did you remove?
Click to expand...
Click to collapse
I removed apps that can be downloaded from Google Play (maps, keep, hangouts, earth, books...)
Otherwise stock odex system is too big for F2FS filesystem.
Now it fits and you have about 15-16mb free.
One thing I am seeing but I think it has nothing to do with the rom is slow charging. I am on the 4.23 boot loader but am still seeing a problem. Saw it on Cm 11 MR7 as well. Is there another bootloader I should be on? Otherwise all is running smooth on this build.
Sent from my Nexus 7 using Tapatalk
just wipe and flash in recovery right?
rayraycarter4 said:
just wipe and flash in recovery right?
Click to expand...
Click to collapse
As long as you already converted to F2FS yes. Minimal G Apps are included, but anything missing can be downloaded.
---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------
No way to install it. All wipe and install ok but don't work.
Don't pass of Google screen.
Click to expand...
Click to collapse
PD.: Sorry, was an error with bootlader
The_Engine said:
One thing I am seeing but I think it has nothing to do with the rom is slow charging. I am on the 4.23 boot loader but am still seeing a problem. Saw it on Cm 11 MR7 as well. Is there another bootloader I should be on? Otherwise all is running smooth on this build.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I have slow charging since I bought this tablet.
For this reason I always charge it overnight...other than changing bootloaders I don't know what can be done.
dpunx said:
PD.: Sorry, was an error with bootlader
Click to expand...
Click to collapse
I am glad you succeeded to enjoy this rom.
Monfro said:
I have slow charging since I bought this tablet.
For this reason I always charge it overnight...other than changing bootloaders I don't know what can be done.
Click to expand...
Click to collapse
It's funny but I never had lag issues. Keep reading about the disc problems and lag and all that but seemed like I was fine. Then one day the device passed some threshold and it came to a creep. That's when I finally rooted it and started with roms but none helped until the F2FS movement started. That's when I started seeing complaints about slow charging. Never had that before. Now I do.
I should stay off these threads. LOL
Sent from my VS980 4G using Tapatalk
The_Engine said:
It's funny but I never had lag issues. Keep reading about the disc problems and lag and all that but seemed like I was fine. Then one day the device passed some threshold and it came to a creep. That's when I finally rooted it and started with roms but none helped until the F2FS movement started. That's when I started seeing complaints about slow charging. Never had that before. Now I do.
I should stay off these threads. LOL
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
F2FS makes this tablet working really good, totally removing the lags that a lot of people experienced.
If slow charging is the price we have to pay, I think is ok.
I had for 5 months a Galaxy Tab 2 (which I sold for N7): compared to it N7 has always been slow on charging.
Anyway is really fun tinkering, flashing and playing with roms. [emoji2][emoji2]
Monfro said:
I have slow charging since I bought this tablet.
For this reason I always charge it overnight...other than changing bootloaders I don't know what can be done.
Click to expand...
Click to collapse
Hi!! I also had this problem after few months of use... Then I realize that the original cable was the reason (was malfunctioning). I changed the cable and Voila! Fast charging again...
How can I activate ART?
Gesendet von meinem HTC One mit Tapatalk
W0WA said:
How can I activate ART?
Gesendet von meinem HTC One mit Tapatalk
Click to expand...
Click to collapse
This is stock 4.4.4 rom released by Google: ART is not available here.
Hmm... I seem to be stuck while booting, I can't get past the 4 colour boot animation.
I have a full-f2fs recovery, full-f2fs properly setup (my previous rom was the full-f2fs version of OmniROM), I've done a factory reset and a dalvik wipe... I don't know what else it could be.
Do I need a specific bootloader version? I think I have 4.13.
GiSK said:
Hmm... I seem to be stuck while booting, I can't get past the 4 colour boot animation.
I have a full-f2fs recovery, full-f2fs properly setup (my previous rom was the full-f2fs version of OmniROM), I've done a factory reset and a dalvik wipe... I don't know what else it could be.
Do I need a specific bootloader version? I think I have 4.13.
Click to expand...
Click to collapse
If you already formatted all partitions to F2FS it should work.
If you have a backup of Omni try a dirty flash, wiping only cache+dalvik.
I don't think latest bootloader is fundamental.
Hey guys,
So here is a straight from source build of Android L, 5.0. I have not done anything beside build it from source and flash it. I have not done extensive testing on it.
So anyways, here is the link:
http://d-h.st/zi0
I have not included gapps or anything else. They will be coming soon. This build is primarily to play around with. I would not consider this a daily driver.
Issues:
Probably a ton, seeing as I have only checked if it boots.
I am not responsible for any issues this may cause or anything else that may happen to your tablet as a result of this.
I also have a ton of schoolwork and other things that keep popping up, so my support may be iffy. Please bear with me or go back to 4.4.4.
Here is a screenshot for proof:
https://www.dropbox.com/s/lnmhdapeemskggi/1743495_10153594576754572_4551962379003400239_n.jpg?dl=0
Future Plans for this Rom:
GApps are not yet possible on Lollipop as far as I can work out, due to the fact that baksmali and smali do not appear to play nicely with ART odex files. I will be rebuild the rom to be odexed and then including a gapps package.
XDA:DevDB Information
[Android 5.0] Straight from source ROM, ROM for the Nexus 7
Contributors
MidnightNinja
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-04
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
cchant said:
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm..let me know if you still have issues, because I was able to sideload on my device
Awesome!!
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Niekhout02 said:
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Click to expand...
Click to collapse
I am missing alot of the google stuff, which is probably why none of that works
That will come shortly, I just need to redo a lot of my vendor files and such to get gapps to be built in.
It worked even though it said no OS
first boot takes awhile but it works!
Confirmed it works.
Sideloading gapps for cyanogenmod 11 and hoping they auto update does not work. Worth a shot though. Time to reflash.
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Working great! I think performance is even better than kitkat
Wi-Fi also working (maybe bluetooth, nfc and gps too)
StardustGeass said:
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Click to expand...
Click to collapse
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
tatazeuz said:
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
Click to expand...
Click to collapse
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
MidnightNinja said:
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
Click to expand...
Click to collapse
Yay!
Works great, now waiting for gapps
thanks
Gapps mostly work fine if you edit updater.script
I've only had issue with the keyboard crashing so I'd suggest removing it from the gapps package before flashing.
Woah
I can't wait for the final version, this one, using 4.4.4 binaries, is crazy smooth. Google outdid theirselves on the optimization department.
Awesome work, think im gonna givebthis a try atbwork tomorrow.
What does work and what doesn't
basuraunak said:
What does work and what doesn't
Click to expand...
Click to collapse
So far, everything seems to be working. Have to check camera yet though.
I cant seem to get much else to go with it, but I will share my findings.
I can get TWRP to install,but then I get a bootloop.
If you use the Nexus Root Toolkit v 1.9.3 and "Root" with custom recovery checked. It freezes after trying to temporarily boot the modified boot image.
Hard reset the tablet and boot normally. The toolkit should reboot your tablet back into the bootloader and into TWRP, but this is only good for one boot.
If you mount /system and run a fix permissions, then it stays installed, but never gets past the boot screen.
It boots far enough to get into ADB.
Not sure what to try next though...
I was thinking if we could get a flashable zip without the stock recovery, then we may be able to keep TWRP, but I am not familiarwith building the flashable zips.
Wait, So how do you flash the google play services after you lose TWRP?! I don't understand..
About the ROM
============
Thanks @HolyAngel for permission to use his superb ROM as the base. As the name suggests as many Google services and apps have been pulled out with tweaks to make things work.
Credits/Contents
==============
SkyDragon
=========
M8 GPE
=======
SystemUI with many enhancements by @lyapota (Note this isn't compatible with GravityBox - check extras for stock UI)
SlimRom
========
SlimLauncher
Open Source
==========
AdAway - https://f-droid.org/app/org.adaway
Amaze (Themable Root File Manager) - https://f-droid.org/app/com.amaze.filemanager
KeePassDroid (KeePass-compatible password safe) - https://f-droid.org/app/com.android.keepass
Kernel Adiutor (Manage kernel parameters) - https://f-droid.org/app/com.grarak.kerneladiutor
Open Camera (Camera App) - https://f-droid.org/app/net.sourceforge.opencamera
QKSMS (Themable Messaging app) - https://f-droid.org/app/com.moez.QKSMS
(Install F-droid for updates)
AOSP/CM
========
Browser
Email
GalleryNext
Keyboard
HTC (best available fit?)
===================
Calendar https://www.apkmirror.com/?s=HTC+calendar&post_type=app_release
Clock https://www.apkmirror.com/?s=HTC+clock&post_type=app_release
Installation
=========
Flash ROM in recovery (at your own risk)
Flash ElementalX (to set wake options)
Boot ROM
Setup
=====
Add Slim Launcher 'All apps' shortcut
Set system language through AOSP keyboard.
Configure APN settings if necessary.
Sync
====
Easy method (keep your Google contacts).
Log in to Gmail on Outlook.
Switch on contacts sync in Outlook.
Contacts will appear in dialer.
Calendar will appear in Outlook.
Note: New contacts can't be added.
Best method
Export your contacts and calendar to another provider.
Log into new account using AOSP email.
Contacts and calendar will be available to any app.
Contacts can be added.
Pro's & Con's
==========
++++++
Near zero Google
Improved battery
More free RAM
-------------
Near zero Google
App management
Paid Google apps won't work.
No Chromecast without GP services. Wrong install BubbleUPnP https://www.apkmirror.com/?s=Bubbleupnp&post_type=app_release
Enjoy the Google Eviction experience.
Downloads
ROM
https://mega.nz/#!PwglnQ7Q!xg1ptszT549P0INOj6JhbPwqWwfsSHty4_IYNbzVGVo
boot.img (for S-ON users only)
https://mega.nz/#!X55UjLSS!q6eYG_6O_KOCp08DEyTTnwp_e0h_x_Zv8WAHRF3kCh8
Extras
https://mega.nz/#F!St4hUQAI!i-8x6oI1P2cmW0DyZfUF9Q
Installer and Build number now updated.
SystemUI mods added to Extras/mods.
V1 - Initial release
Marshmallow?
1. I noticed that in the OP it said M8 GPE so is this ROM a port of sorts of the marshamallow GPE ROM of the M8 or does it just have some inclusions from that ROM? If it's the former then this is freaking amazing!
2. Since this ROM is based on Skydragon does that mean that the installation instructions from Skydragon apply to this ROM? Such as needing to be S-OFF. I am S-ON so that's why I ask.
3. If it does require S-OFF can I just manually flash the boot image like in santod040 M7 GPE ROM to make it work?
It sadly doesn't boot. I'm stucked for 30 mins in boot loading screen.
Mikecosta64 said:
1. I noticed that in the OP it said M8 GPE so is this ROM a port of sorts of the marshamallow GPE ROM of the M8 or does it just have some inclusions from that ROM? If it's the former then this is freaking amazing!
2. Since this ROM is based on Skydragon does that mean that the installation instructions from Skydragon apply to this ROM? Such as needing to be S-OFF. I am S-ON so that's why I ask.
3. If it does require S-OFF can I just manually flash the boot image like in santod040 M7 GPE ROM to make it work?
Click to expand...
Click to collapse
blurhns said:
It sadly doesn't boot. I'm stucked for 30 mins in boot loading screen.
Click to expand...
Click to collapse
It's just this repacked
http://forum.xda-developers.com/showthread.php?t=2400161
In fact installer and build number are unaltered.
Same install methods apply if you are S-ON.
It's lollipop as is the M8 UI which adds the following features:
Lockscreen DT2S
Statusbar DT2S
Clear all recent apps
No search bar in recents
Centred statusbar clock (optional)
Right Quick Settings pulldown
Great work bro nice to see you putting some work out :good: :beer:
liam_davenport said:
Great work bro nice to see you putting some work out :good: :beer:
Click to expand...
Click to collapse
Cheers Liam. Involved me getting some things working and adding good tweaks and apps. I've not built from source and probably never will as I personally couldn't commit that sort of time. Best part has been discovering the great open source apps and alternatives out there, which I still am.
ROM won't boot?
I followed the installation instructions written in the OP but, after leaving my phone for 20 minutes it would not boot. I then forced a restart by holding down the power button as elementalx sometimes get's ROM stuck on a bootloop and after doing that and letting it reboot for 10 minutes nothing happened. I also got a bootloop when I flashed the ROM only no elementalx. When I say bootloop it's the booting animaiton not the htc logo.
BTW in the aroma installer for elemental x kernel I selected the stock voltage instead of "Undervolt (850 min)" or any other one because undervolting could produce some boot failures. Every other setting is selected to stock.
I am using TWRP 3.0.0 recovery could that be the issue? It flashes other ROMs fine so the recovery is not corrupted.
I will attach a logcat later on so you can see what happens. Not at a computer at the moment.
marshmallow or lollipop ?
rerezatrollface said:
marshmallow or lollipop ?
Click to expand...
Click to collapse
The ROM is lollipop but it has addittions from m8GPE. Were you able to get it to boot? Cause I have been having difficulties.
Did you try to flash boot.img? (worked for me)
Sent from my HTC One using Tapatalk
Mikecosta64 said:
I followed the installation instructions written in the OP but, after leaving my phone for 20 minutes it would not boot. I then forced a restart by holding down the power button as elementalx sometimes get's ROM stuck on a bootloop and after doing that and letting it reboot for 10 minutes nothing happened. I also got a bootloop when I flashed the ROM only no elementalx. When I say bootloop it's the booting animaiton not the htc logo.
BTW in the aroma installer for elemental x kernel I selected the stock voltage instead of "Undervolt (850 min)" or any other one because undervolting could produce some boot failures. Every other setting is selected to stock.
I am using TWRP 3.0.0 recovery could that be the issue? It flashes other ROMs fine so the recovery is not corrupted.
I will attach a logcat later on so you can see what happens. Not at a computer at the moment.
Click to expand...
Click to collapse
Can anyone else confirm ROM booting? Not had much feedback.
rerezatrollface said:
marshmallow or lollipop ?
Click to expand...
Click to collapse
Lollipop
alex94ionut said:
Did you try to flash boot.img? (worked for me)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Please confirm you are S-ON.
Maybe others S-ON too.
Extracted boot.img added to second post for S-ON users.
I'm S-OFF. Without flashing boot.img don't work (at least for me).
Sent from my HTC One using Tapatalk
alex94ionut said:
I'm S-OFF. Without flashing boot.img don't work (at least for me).
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Really. Did you flash ElementalX? Any other S-OFF users getting the same?
People who are having issues to boot, Are you using latest GPE firmware? I couldn't boot our rom without it so should be the same case here
12 hour period today. When the screen is off it's really asleep. No greenify or amplify here and 77% left.
mitchst2 said:
12 hour period today. When the screen is off it's really asleep. No greenify or amplify here and 77% left.
Click to expand...
Click to collapse
That's the beauty of not having google play services. Can't believe they actually make a huge difference.
Google please optimize google play services and google apps in general.
ROM Booted!
I flashed the boot image provided through fastboot and then I flashed the ROM only and it booted perfectly. I only waited for around 4 minutes so it was very fast. I am S-On. Flashing the boot image definitely works
I will now try to flash the ROM plus kernel at the same time. Will edit this post in around 10 minutes.
Edit: Ok so I tried to flash kernel and ROM at same time after flashing boot image and the ROM booted perfectly. Weird thing is though that after I wiped data,cache,system,dalvik I flashed the ROM again with and without kernel (before first boot) without flashing the boot image and it worked perfectly as well. I don't know what was going on with my phone last time I tried to flash were it got stuck on bootloops. This is very strange as I haven't changed my firmware on my phone since last time I tried or done anything differently in my flashing procedures.
Well for how weird this experience was, I am very glad that I am able to use your ROM so I can provide feedback and also be able to enjoy it.
LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03
Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1
wow..this device is still alive
hats off
It was my first android ...
paras33 said:
wow..this device is still alive
hats off
It was my first android ...
Click to expand...
Click to collapse
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.
great news!
@mdmower - I was following your GitHub notes over the past while, always hoping there would be something which we could use!
Thanks to all involved - I still have and use my evita, but often with an alternate SIM for travel. It is still a very nice phone. I put new batteries in both my evita, and my wife's, and they keep going. But security... That's where LineageOS, and this build, will be crucial.
I need my evita as a daily-driver for the next couple of weeks, so I'll eagerly read the results from others for now. But I have three other devices using unofficial LineageOS builds, and I'm very happy with them.
Thank-you, everyone!
Dnorris55 said:
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.
Click to expand...
Click to collapse
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen
wlewin said:
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen
Click to expand...
Click to collapse
I'm not sure just what worked, because I tried so many things. I even tried flashing the evita-x twrp, but it didn't work, so I reflashed the twrp in the op. At one point, I thought I was really screwed, because the data partition showed a size of 0. Then I re-did the format data (step 6), and was able to install the ROM and get thru the setup.
You might try reflashing the twrp, and repeat step 6.
Also, I installed the ROM by itself, booted and setup.
Then flashed gapps and rebooted.
Then flashed SuperSU.
Sent from my SM-T800 using Tapatalk
h8rift said:
Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1
Click to expand...
Click to collapse
Great development on the One XL. Thanks guys for the great work. I managed to install the rom. It however seem unstable and apps taking long to open. Also the red box on the edge of the screen. Will try wipe and reflash and see if there will be an improvement
WOW! Nougat on a Five Year-Old Phone!
Thank you so much. You guys are amazing. I can't believe I'm running Android 7.1 on a five year-old phone. Everything works and is running pretty smooth (except for occasional red border flash).
As things turned out, my good old HTC One X has become my primary phone for the time being. And here I am running Nougat. I guess it says a lot about this phone's build quality that it has lasted so long. My deep appreciation to all the XDA developers and their amazing ROMs, apps and troubleshooting tips that have kept this phone, amazingly, at the forefront of Android development all these years.
Well, I couldn't wait. And the summary: I am thrilled
Here are some notes and observations, while installing lineage-14.1-20170226-UNOFFICIAL-evita.zip:
from within TWRP-3.0.N2-1, device always performs a full system-reboot when selecting "Reboot to Recovery". You have to reboot to fastboot (press-and-hold Vol-Down and Power), then enter recovery from the fastboot menu. Later, from within Lineage OS, you *CAN* reboot to Recovery.
cannot flash this ROM and nanoGapps queued together: insufficient memory. Flash this ROM first, then use TWRP file-manager to delete the ROM .zip. Now, there will be sufficient space to flash nanoGapps.
there are plenty of red-border-flashes during setup, and during regular operation It seems like just about every user-input-event, and maybe even every install-decision-point will produce this. It's actually slower than a "flash" - more like a red-border-blink I doesn't hurt anything, and I suspect this will be ironed-out later.
this ROM doesn't include 'su' (SuperUser). For this installation, I opted to use Lineage's 'addonsu-arm-signed.zip'
My roaming SIM won't work where I am now, but I have input my voip details into the provided dialer, and voip/SIP calls work as they should. I added Yahoo as a CM_WeatherProvider, and now cLock looks and works as expected.
a huge THANKS guys, for bringing this ROM to this point - @h8rift, @mdmower, @jrior001 !
Wow, guys this is great!
Thanks for the hard work.
What can we expect from this? Will it be patched to fix bugs or is this a "one build"?
Also, question for the devs: can one realistically hope to use Nougat on evita as a daily driver or is this device simply too old? I'm on CM12.1 and it's not that smooth. Would switching to Nougat better or worsen the experience?
For current testers: what features are currently working (camera, GPS, etc.)?
Again, hat's off!
Device Encryption busted
Device Encryption does not work.
(to be honest, this seems hit-or-miss with other LineageOS 14.1 ROMs; maybe even more "miss" than "hit" :-O . My Nexus 5 will encypt fine; my Nexus 7 (2012) won't).
Camera Works
I've attached an image OF YOUR QUESTION @Luxoboy to show that the camera works. The (exif??) data that I can see in the LineageOS Gallery app shows reasonable information too.
It doesn't seem to crash, nor have weird colors, for still-photos.
HTH,
WiFi stumbles a bit
OK... During setup, the first inkling of a rough-spot for WiFi showed up (for me): finding and displaying WiFi SSIDs took *forever*... Maybe I even skipped past that, and went back to set up WiFi access after the setup was finished and Lineage OS was fully running.
In actual hand's-on usage, I've found that the WiFi connection is both a bit weaker (fewer bars, doesn't reach as far) and lower-throughput than other devices. Both the 5GHz and 2.4GHz bands work; max throughput on 5GHz was 135Mb/s for me, right next to my 802.11n router (running DD-WRT). It's OK though.
Also during use, I sometimes noticed the WiFi icon, and the Settings -> WiFi progress indicating a drop + renew of the WiFi. Right now, my evita is at home while I'm at work - the phone is charging/sleeping but my Voice-Over-IP SIP provider site shows that the evita isn't registered... I suspect that WiFi isn't working, when it was during breakfast when I was playing with it...
The WiFi is certainly usable, but it does stumble a bit here-and-there, it appears.
Does anyone else experience the same, or something different with WiFi?
Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!
wildboarhog0 said:
Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!
Click to expand...
Click to collapse
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
worked like a charm! Thanks!
No More Red Flashing!
kuF3AR said:
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
Click to expand...
Click to collapse
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.
shannester said:
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.
Click to expand...
Click to collapse
I found this file on the lineageos web site as approach to root their ROMs.
h8rift said:
LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03
Click to expand...
Click to collapse
One x or One XL? Can it work on both?
(My Device's SKU - 65383)
DO NOT FLASH GAPPS! untill your second attempt and you have had a "play".
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/crdroidandroid/
I used a working device tree (ie local manifest) from my working LineageOS 14.1 Build machine for an XT897 (for me I use the touch drivers for an XT907, but not in this build)
Basically, I have done no "magic" here, it all just kinda worked. up to a point as its pretty buggy. BUT IT BOOTS!
I also have a ResurrectionRemix 7.1.2 with similar issues.
This is an experimental build of crDroid 3.6, Android version 7.1.2, an experimental build for a non-official device (ie xt897).
I personally do not have an xt897, but an xt907. Since its relatively simple to port xt8907 ROMs to an xt907, I tried building crDRoid (and RR). It looks OK untill i flash GApps (i use Open GApps pico, and also tried a few others to no success)
The good
It's crDroid!
It's Nougat!
It Builds
It Boots!:highfive:
It has all the eyecandy!:angel:
It feels really "snappy"
The bad
If you flash Gapps it falls to pieces in a never ending cycle of crashes!:crying:
It is buggy even without GApps
Since I do not own an xt897, I cannot test this zip (as is) personaly, and hope someone with an xt897 will try the zip (with GApps) and let me know if they too get the same FC's I get on an xt907.
What I hope is that if the same errors occur on an xt897, that either a developer working on crDroid ( @neobuddy89) or the maintainer of the LOS xt897 device @kabaldan) will see this thread and any logcat's posted and be able to easily identify what is wrong and needs to be changed top make it work? And whatever fixes it for an xt897 does the same for an xt907.
Credits: All credits go to @kabaldan (for the xt897 official LOS device maintenance), crDroid contributors (multiple but I often see @neobuddy89 updating the source) & all the many LOS contributors and Cm maintainers before them.
Almost forgot, Flash this ZIP at your own risk, the responsibility is all yours, it is provided as-is, with no garantees or whatever and I will not be held resonsible for any damage to your device or its data etc etc etc
Installation:
1) Download the ZIP
2) Boot into TWRP recovery
3) Make a nandroid (you will definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
4) Wipe system/data/cache/dalvik
5) Flash update package (ie install the zip)
6) DO NOT INSTALL GAPPS! (try the whole process again including the wipes with GApps, if you dare...)
7) Reboot to system
Please get some logcats and post them on hastebin/pastebin etc etc NOT HERE, only the links. Hopefully we can fix it and have some highly customisable nougat ROM's for our devices. And the steps to make it work may also be helpful for the next Android iteration.
Download Link: https://clicknupload.org/yxtmx1ac75pw
And please post how you go with this ROM, I would like to know if its as flakey on an xt897 as it is on an xt907.
For any photon Q users, format /data to f2fs other wise this rom will refuse to work correctly. Otherwise, great work DiamondJohn!
Galaxyninja66 said:
For any photon Q users, format /data to f2fs other wise this rom will refuse to work correctly. Otherwise, great work DiamondJohn!
Click to expand...
Click to collapse
Yeah, forgot I did this thread. Probably because it appears to have had such little interest/response.
DiamondJohn said:
DO NOT FLASH GAPPS! untill your second attempt and you have had a "play".
Click to expand...
Click to collapse
If you format your data partition to fs2fs, then this may actually be usable as a daily, with GApps installed. It cleared all the issues with my xt905/907. I do not have a photon Q to test it on personally.
The Download link seems broken, get it back up and I'll give it a go
Removed
rahimali said:
It has been replaced by XT905/XT907 version which you can find here
Click to expand...
Click to collapse
No, it has not replaced, as the xt905/907 version will not completely work on an xt897 (hardware keyboard being the obvious difference), and even if the screen drivers are replaced, I changed the device tree to align more to an xt907 and moved away from the xt897. The above build was specifically for an xt897. I built it in the days before I knew about formatting the data to F2FS, to see if I could build for an xt897, since it was an official LOS device.
Since I got the RAZR M (ie 907/905) up and running (simply format data to F2F), and at the time there appeared to be VERY little interest in this build, I never really looked back, and don't even know which of my historical builds were the one for this thread. Sorry, but you were a little late to the party. :crying:
Hi does anyone know if this rom or maybe the atrix hd lineage rom could be flashable on the razr hd xt925? I know that radio and storage is different as well as the recovery, so I ask if anyone tried or knows how it be feasible
elbart88 said:
Hi does anyone know if this rom or maybe the atrix hd lineage rom could be flashable on the razr hd xt925? I know that radio and storage is different as well as the recovery, so I ask if anyone tried or knows how it be feasible
Click to expand...
Click to collapse
Unless you specifically have an XT897, you would be better off with an XT907; if it can be modded/flashed onto an xt925.
https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
I think there may even be a post by someone else with an XT925 or 926. If not in that thread then maybe in one of my other XT907 ROM threads.
Any news on those bugs? I'd be especially interested in ResurrectionRemix 7.1.2. @DiamondJohn
Shani Ace said:
Any news on those bugs? I'd be especially interested in ResurrectionRemix 7.1.2. @DiamondJohn
Click to expand...
Click to collapse
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.
DiamondJohn said:
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.
Click to expand...
Click to collapse
Oh I see, thanks for the quick reply though!
DiamondJohn said:
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.
Click to expand...
Click to collapse
Shani Ace said:
Oh I see, thanks for the quick reply though!
Click to expand...
Click to collapse
It did just occur to me, that with some minor changes to any of the ROM zips I created for the XT907 (including RR), you could run them on an XT897. Basically, after you flash the ROM (after changing the assert/check that its an XT907) you need to switch the two screen driver files (atmxt-r1.tdat & atmxt-r2.tdat) and grab the Assanti APK (ie the physical keyboard) from another ROM. Basically a reverse of what I suggested to do for a port from XT897 to XT907 https://forum.xda-developers.com/droid-razr-m/development/how-to-port-lineage-13-0-6-01-to-t3607500
Good luck, and be sure to share if you do it.
DiamondJohn said:
It did just occur to me, that with some minor changes to any of the ROM zips I created for the XT907 (including RR), you could run them on an XT897. Basically, after you flash the ROM (after changing the assert/check that its an XT907) you need to switch the two screen driver files (atmxt-r1.tdat & atmxt-r2.tdat) and grab the Assanti APK (ie the physical keyboard) from another ROM. Basically a reverse of what I suggested to do for a port from XT897 to XT907 https://forum.xda-developers.com/droid-razr-m/development/how-to-port-lineage-13-0-6-01-to-t3607500
Good luck, and be sure to share if you do it.
Click to expand...
Click to collapse
Oh ok, good to know, thanks! I'll save that info for later in case I need it.
Saw an official Lineage 14.1 version for the XT897 so I'll probably try that first once I get a Photon Q again.