Related
Hi all,
the following roms provide modified versions of Katinatez latest build of Temaseks ext4 rom, specifically for oneplus one f2fs users.
Versions to support ext4/f2fs mixed (2 partitons formatted to f2fs data and cache -2p) are provided.
Each of these roms also has a multirom version that can be installed as a secondary rom. Flashing an incorrect rom for your set up wont work.
To install them you MUST have your data and cache partitions formatted to f2fs and system formatted as ext4. Philz recovery by Katinatez is best for this task, but you can use twrp etc. Be warned, converting your oneplus will:
- zap your data, so backup first. Once you have converted to f2fs, normal rules apply.
- not allow you to flash ext4-all roms, unless you convert them to f2fs. Dont try to flash these. Gapps, scripts will flash as normal, but not ext4 roms.
To first time flash
1. Do a full wipe (dalvik, system, data, cache). Internal storage (post f2fs conversion) can be left alone.
2. flash the downloaded rom (side-load or from internal storage is good)
4. Install gapps of your choice.
5. Install SuperSU latest.
6. Boot - Please be patient. The flash and first boot can take a little time.
Upgrading from an earlier version:
A full wipe is always recommended. It is the least risk option of running into problems with your existing apps and data. However dirty flashing also works generally, so you should be able to just flash a new versions on top of your existing install without problem. To be safe, always take a nandroid first. Some recoveries will insist that you wipe anyway, and will throw an error. If this occurs just wipe dalvik and cache and reflash. Gapps and Super SU should be preserved.
Multirom - not currently available..
The multirom versions are to be used to create a secondary rom in multirom only. These can also generally be dirty flashed over a previous Temasek oneplus f2fs multitrom install without problem, but a clean install, as always, is the least risky method. Take a backup first.
It is usually possible to flash changes to kernel versions dirty with a prior version installed. However, Temasek rom updates have to be converted to be f2fs friendly before flashing so I'll try to be as quick as I can getting f2fs versions ready as soon as a new Temasek version is released.
Thanks and credits to AK, Temasek, Katinatez , YoshiShaPow, RIPng, and DerRomTester for their excellent work for the oneplus one. Please note that these rom pull together many rapidly changing developments, and things can clash, go wrong. It also means you get the best available.
- Standard versions. These will install with any recovery, but will not install as a secondary rom on multirom directly. Use the multirom version for ths purpose. When using multirom to install as a primary, the install may fail initially. If so, wipe cache and re-install. A primary install can be swapped to a secondary with multirom once installed.
- Secondary rom versions. These will only install as a secondary rom only on multirom. Once installed it is possible to swap with the primary.
- Using different Kernel versions
Many kernels available now support f2fs, and use the "any-kernel" method to install. This means they can be installed directly onto a primary or multirom secondary installation of this rom. Some kernels do not use this method, but are still f2fs friendly (i.e they have the necessary f2fs commits implemented). See FAQ as to how to convert these kernels to flash with this rom.
Zaphod-Katinatez SaberMod 9.0 f2fs
Zaphod-Katinatez SaberMod & Linaro 8.8 f2fs
Zaphod-Katinatez SaberMod & Linaro 8.7 f2fs
Zaphod-Katinatez SaberMod 8.6 f2fs
Katinatez 7.7 F2FS linaro and sabermod roms
UPDATE Katinatez 7.4
UPDATE 6/2/15 Katinatez 7.2
UPDATE 5/2/15 Katinatez 7.1
UPDATE 3/2/15 Katinatez 6.9
UPDATE 2/2/15 Katinatez 6.8
UPDATE 24/1/15 Katinatez 5.9
UPDATE 19/1/15 Katinatez 5.5
UPDATE 17/1/15 Katinatez 5.4
UPDATE 13/1/15 Katinatez 4.9 - pulled
UPDATE 12/1/15 Katinatez 4.7
UPDATE 6/1/15 Katinatez 4.6
UPDATE 6/1/15 Katinatez 4.5
UPDATE 5/1/15 Katinatez 4.3
UPDATE 4/1/15 Katinatez 4.2
no 4.1
UPDATE 3/1/15 Katinatez 4.0
UPDATE 2/1/15 Katinatez 3.9
UPDATE 1/1/15 Katinatez 3.8
no 3.7
UPDATE 30/12/14 Katinatez 3.6
UPDATE 29/12/14 - Katinatez 3.5
UPDATE 29/12/15 - Katinatez 3.4
UPDATE 27/12/2014 - Katinatez 3.3.1 AK0.68 - F2FS-All Standard Rom - Secondary Rom - Mixed - Standard Rom - Secondary Rom -
UPDATE 27/12/2014 - Katinatez 3.3.1 - Stock - F2FS-All Standard Rom - Secondary Rom - Mixed - Standard Rom - Secondary Rom -
UPDATE 27/12/2014 - Katinatez 3.3.1 - Tyr56Linaro - F2FS-All Standard Rom - Secondary Rom - Mixed - Standard Rom - Secondary Rom -
UPDATE 27/12/2014 - Katinatez 3.3.1 - Tyr56SaberMod - F2FS-All Standard Rom - Secondary Rom - Mixed - Standard Rom - Secondary Rom
UPDATE 24/12/2014 - Katinatez 3.3 AK0.68 - Standard Rom - Secondary Rom - AK thread
UPDATE 24/12/2014 - Katinatez 3.3 - Stock Standard Rom - Secondary Rom - Katinatez thread
UPDATE 24/12/2014 - Katinatez 3.3 - Tyr55Linaro - Standard Rom - Secondary Rom
UPDATE 24/12/2014 - Katinatez 3.3 - Tyr55SaberMod - Standard Rom - Secondary Rom Tyr kernel thread
UPDATE 22/12/2014 - Katinatez 3.2 AK0.65 - Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.2 - Stock Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.2 - Ty55Linaro - Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.2 - Ty55SaberMod - Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.1 AK0.65 - Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.1 - Stock Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.1 - Ty55Linaro - Standard Rom - Secondary Rom
UPDATE 22/12/2014 - Katinatez 3.1 - Ty55SaberMod - Standard Rom - Secondary Rom
UPDATE 21/12/2014 - Katinatez 3.0 AK0.61 - Standard Rom - Secondary Rom
UPDATE 20/12/2014 - Katinatez 3.0 - stock Standard Rom - Secondary Rom
UPDATE 21/12/2014 - Katinatez 3.0 - Ty55Linaro - Standard Rom - Secondary Rom
UPDATE 21/12/2014 - Katinatez 3.0 - Ty55SaberMod - Standard Rom - Secondary Rom
UPDATE 20/12/2014 - Katinatez 3.0 - Ty53 - Standard Rom - Secondary Rom
UPDATE 20/12/2014 - 2.9.1 - AK0.61 Katinatez 2.9.1 - Standard Rom - Secondary Rom
UPDATE 19/12/2014 - 2.9.1 - AK0.60 Katinatez 2.9.1 - Standard Rom - Secondary Rom - Katinatez 2.9 - skipped
UPDATE 18/12/2014 - 2.8 - AK0.50 Katinatez 2.8 - Standard Rom - Secondary Rom
UPDATE 17/12/2014 - 2.7 - AK0.50 Katinatez 2.7 - Standard Rom - Secondary Rom
UPDATE 15/12/2014 - 2.6 - AK0.50 Katinatez 2.6 -Standard Rom - Secondary Rom
UPDATE 14/12/2014 - 2.5.2 - AK0.50 Katinatez 2.5.2 - Standard Rom - Secondary Rom
UPDATE 14/12/2014 - 2.5.1 - AK0.44 Katinatez 2.5.1 - Standard Rom - Secondary Rom
UPDATE 13/12/2014 - 2.5 - AK0.44 Katinatez 2.5- Standard Rom - Secondary Rom
UPDATE 12/12/2014 - 2.4 - AK0.43 Katinatez 2.4- Standard Rom - Secondary Rom
UPDATE 11/12/2014 – 2.3.1 - Standard Rom - Secondary Rom
UPDATE 10/12/2014 - 2.3 - Standard Rom - Secondary Rom
UPDATE 09/12/2014 – 2.2 - Standard Rom - Secondary Rom
UPDATE 08/12/2014 – 2.1 - Standard Rom - Secondary Rom
UPDATE 08/12/2014 – 2.0 - Standard Rom - Secondary Rom
UPDATE 07/12/2014 – 1.9 - Standard Rom - Secondary Rom
UPDATE 06/12/2014 – 1.8.1 - Standard Rom - Secondary Rom
Additional stuff – to get the best from this rom I recommend using the synapse special edition script for AK kernels, the latest version from this thread for the other kernels along with the synapse app from playstore. Trickster is also good with this rom.
BUG Reports – Please report any bug reports to the relevant xda thread. ROM and stock kernel bugs. F2FS bugs in this thread. Please also remember to SEARCH before posting a bug, state what version of the rom you are using, and if possible steps/data to recreate the problem.
FAQ
more info and video on converting to f2fs
how to produce your own f2fs flashable roms
how to produce a multrom compatible flashable f2fs rom
how to make a flashable rom using the boot.img and updater script in the zip
what kernels are compatible with Temasek's rom
Good evening or the changelog and the Roma? or is the screen? the thanks?
V1.7 already supports F2FS, don't see the point of an extra thread with minor insignificant modifications to the ROM imo.
latenightchameleon said:
V1.7 already supports F2FS, don't see the point of an extra thread with minor insignificant modifications to the ROM imo.
Click to expand...
Click to collapse
Agree completely
jejemc said:
Good evening or the changelog and the Roma? or is the screen? the thanks?
Click to expand...
Click to collapse
For a changelog, screens etc, see Temasek's /AK threads. The only change made to this rom from Temaseks rom is that I have modded the updater script so that it installs onto a F2FS filesystem and modded the boot img to embed the latest AK kernel. No more.
CWick4141 said:
Agree completely
Click to expand...
Click to collapse
Then this thread isnt for you two then. Others may want to install this if they have f2fs, as Temasek's rom doesnt install unless it is modified. I have done this modification for others that dont want to do this for themselves.
zaphodbeeb said:
Then this thread isnt for you two then. Others may want to install this if they have f2fs, as Temasek's rom doesnt install unless it is modified. I have done this modification for others that dont want to do this for themselves.
Click to expand...
Click to collapse
Sorry, absolutely didn't mean to come off as rude, your efforts will definitely be appreciated, even if its by a small number of people:good:
I must admit i wondered as well because in changelog it say F2FS ready. But it failed. . It is a little misleading. Just flashing your rom now without problems. Thank you
zaphodbeeb said:
Then this thread isnt for you two then. Others may want to install this if they have f2fs, as Temasek's rom doesnt install unless it is modified. I have done this modification for others that dont want to do this for themselves.
Click to expand...
Click to collapse
? I definitely appreciate it.
störte said:
I must admit i wondered as well because in changelog it say F2FS ready. But it failed. . It is a little misleading. Just flashing your rom now without problems. Thank you
Click to expand...
Click to collapse
Facts. Hella misleading.
---------- Post added at 06:30 PM ---------- Previous post was at 06:15 PM ----------
Will you ever include multi ROM support
Is there really a big different between ext4 and f2fs or is it just beause f2fs is a "newer"/technology? Please help me i never had any experiances with f2fs ^^ What are the differentes
Wow this combo is unreal together first time I've been able to use ak kernel and cm12 f2fs very slippery and responsive at the same time much alohas to all devs involved
Thank you for this. Was about to modify the ROM myself when I saw this thread. Thanks for saving me the trouble
Looking forward to future updates
thanks for this. ill keep an eye on this thread for updated builds.
Man this thing is super solid this my DD for sure much aloha
1.81 is comming in one hour for ext4
Send by Hyperdrive on one+One
Seem that too bradah storte! something about f2fs that keeps me here on can't explain it lol
Multirom Terasek 1.7, AK 035 F2FS version.
OmegaBlaze said:
? I definitely appreciate it.
Facts. Hella misleading.
---------- Post added at 06:30 PM ---------- Previous post was at 06:15 PM ----------
Will you ever include multi ROM support
Click to expand...
Click to collapse
Hi,
thanks for your feedback. Had a play with a mulirom friendly version today and this seems to be working as a secondary install. This is a further mod on the 1.7 Temasek, AK035 rom I produced previously. I havnt had a chance to check as a primary install yet on multirom but it seems to swap from secondary after install to primary correctly. Any help testing it would be appreciated. I think a new version of Temasek may be available soon so, with positive feedback I'll produce a new version with the multirom changes embedded and update the OP.
Try it here.
störte said:
1.81 is comming in one hour for ext4
Send by Hyperdrive on one+One
Click to expand...
Click to collapse
Thanks for the heads up. I'll try to update the F2FS roms when its released.
Great so i can update after my work
Send by Hyperdrive on one+One
Nice thanks for building and making it less of a headache for the f2fs users and now multirom users too
Starship Kernel is being developed in conjunction with the not yet posted Starship Rom. Like I had done with the KK incarnation of the Starship Rom I am also posting the Kernel separately for anyone who may not like the Rom's Theme. Though unlikely as that may sound because I have spent much time and effort with the Kernel am posting the Kernel separately so it can be used with other Roms and not just Starship.
If you are looking for new features to play with this will not be the Kernel for you. It is designed to improve the overall experience as if it was not there. At this point and probably never you wont find over clocking or voltage controls to play with but rather just a more efficient overall experience.
Each Kernel Download section contains a link to the commit list for both the purpose of following rules about posting links to Kernel Sources as well as serving as a change log. You will find in the main branch all Linux Kernel Increment Updates are grouped into one commit. This is to easily distinguish what commits have been made as part of the Linux Kernel Increment Updates from other additions/optimizations that are not part of the Linux Version Updates. You can find descriptions of each change made as part of the Increment Updates in the staging branch. In other words the second link below the download links will give a description off the changes made in the Linux Version Updates .
Downloads
AOSP/Stock (Android Version 5.1.1)
AOSP/Stock Kernel is compiles using Google's GCC 4.8 toolchain and tested tested on the Stock 5.1.1 Rom as well as AOSP compiled Rom using unmodified pure 5.1.1 Source code. The Kernel may or may not work on custom Roms based on 5.1.1 depending on what changes have been made by the Roms developer and how far the Rom has strayed from the original source code. In most cases if the Rom is AOSP based the Kernel will work but provide no guarantee as am not testing with every ROM available. If you do find a Rom the Kernel does not work with feel free to comment but please include what Kernel was used that did not work as I may be able to shed light on reasons why and provide a workaround if possible. Most of incompatibility will find that the Kernel is not the issue rather what is included inside the boot.img like Ramdisk iinit.rc files that set permissions and create the Rom file-system.
Starship-lollipop-5.1_Kernel-3.4.91_r1
https://www.androidfilehost.com/?fid=24052804347767806
Starship-lollipop-5.1_Kernel-3.4.88_r1
https://www.androidfilehost.com/?fid=24052804347766347
Starship-lollipop-5.1_Kernel-3.4.86_r1
https://www.androidfilehost.com/?fid=24052804347760505
Starship-lollipop-5.1_Kernel-3.4.83_r1
https://www.androidfilehost.com/?fid=24052804347756685
Source / Change-log
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Including individual explanation of changes included as part of Linux version increment update patches.
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop_staging
CM-12.1
CM-12.1 Kernels may be updated more frequently without posting a new date so don’t be surprised to see multiple release number increments. In most cases there has been no change in the Kernel itself but update frequently as development is fast moving. Because of this some of the files that get packaged into the boot.img along with the Kernel may change and cause issues. Because of this will update as frequently as I can to insure everything packaged into the boot.img is up to date.
Starship-CM-12.1_Kernel-3.4.88_r1
https://www.androidfilehost.com/?fid=24052804347766796
Starship-CM-12.1_Kernel-3.4.86_r1
https://www.androidfilehost.com/?fid=24052804347760507
Starship-CM-12.1_Kernel-3.4.80_r1
https://www.androidfilehost.com/?fid=23991606952613802
Source / Change-log
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/cm-12.1_staging
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Just decided to include the CM-11 Kernel for anyone who may be using CM-11. Is a nice Kernel and gave me an extra hour or two battery so recompiling with a few new commits I have been using in both CM-12 & AOSP. Will post in a few. Checking nothing else may have changed on the CM side with the rest of the boot.img and will post in a bit.
I will try out the AOSP kernel tonight or tomorrow, we are under blizzard conditions right now and can't mess with phone because of work (boss & I texting back and fourth)
Thanks for your work
Sent from my rooted RCT6203W46 using xda-dev app
Downloading now!
Sent from my Nexus 5 using XDA Free mobile app
rickballs said:
Downloading now!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry about this then but have uploaded an update. I had intended on holding off until reaching Linux version 3.4.40 as it is the version I had left off with for Kit-Kat and have just been modifying each version increment patch from the Kit-Kat 3.4 Kernel for Lollipop. Anyhow last night before bed had used my Bluetooth Headset with the current version and sounded like I had gone out and bought a brand new higher end set so decided to post the update now. Found in the past Android can have a completely different experience when it comes to different BT devices like for example the same headset had become completely unusable on my N7 with constant skips and pauses on 4.4.4 after working beautifully on 4.4.3 so hope others can hear the same boost in overall audio quality including BT headsets.
Updated Kernels with a few new optimizations and 3.4.36 version update
Ok will try it
Can't download from devhost. Anyone else is having problema?
gengi said:
Can't download from devhost. Anyone else is having problema?
Click to expand...
Click to collapse
Looks to be up and running. Can try direct links though.
updated so links are no longer current.
Well it feels like with all the side track projects been talking Starship L long enogh maybe some of those who have sent PM's asking about the lollipop update are starting to become doubters so decided to post up a few screen shots. Was going to finish a few things then go over the theme image by image and color by color but think instead after finishing up a few things will post and then start going over each apk over again for touching up, fixing and adding missed optimizations including Kernel updating along the way. Once again not for everyone so haters can hate and I just keep doing it because its what I like doing.
Made new boot.img for Stock / AOSP 5.1.0 as old image used in 5.0 - 5.0.2 caused boot loops.
The MultiROM not work with this kernel? :-O
dado70 said:
The MultiROM not work with this kernel? :-O
Click to expand...
Click to collapse
Honestly have been meaning but have not tried MultiROM. Looked over at the thread and see allot of mention about the boot.img and modifications. If I had to guess with the limited knowledge I have would say if not working is not so much the Kernel but the boot.img in the same way that both the Stock / AOSP zips posted are the same exact Kernel inside but changes made to files like the init.rc inside the 5.1.0 boot.img that creates the file system and sets permissions among a score of other things caused 5.1.0 from booting properly after updating and flashing the boot.img. As developers we use the name Kernel but there is much more inside than the actual Kernel. In some cases can be more than a dozen other scripts and other files inside. Will need to try and learn a bit about MultiROM. Out of curiosity was it Stock or CM giving you issues?
Little more reading and looks like not everyone including CM has updated to include new bootloader version checks to include new bootloader from the 5..1.0 update. So for example I needed to change the bootloader version in CM source or nightly builds will not flash in TWRP without errors.
Maybe an update on this if flashing CM version, seems latest CM12 is receiving errors flashing with some recovery versions and must be installed via adb / fastboot. Article was not specific on the reason but may be the cause.
Added updates to version 3.4.42 for both 5.1.0 and under. The 5.0.2 zip should work for all stock and AOSP Roms from 5.0 - 5.0.2. Because of changes in 5.1.0 boot.img 5.1.0 will not boot when used with a lower Android Version.
Slightly disappointed as today had planned on posting full Starship Rom but now updating for 5.1.0 so maybe another week maybe two
So any details on what this kernel does? Or is our just close to stock?
CM12 Kernel is on hold until 5.1.0 version update. No reason testing anything new until can confirm everything will still work next week. Also figures the same week I had planned on posting the full Starship Rom the 5.1.0 update hit so now am back in testing optimizing phase for a bit longer.
3.30.2015 update
Linux version has been updated to version 3.4.55
All MR1 changes added to the 5.1.0 AOSP Kernel have been merged into the Kernel
https://github.com/Starship-Android...mmit/8ed8c47ff15f1c5fdd6707f7a52f76110aed6cbf
4.6.2015 update
Not much on the AOSP/Stock side. Wanted to post a cm12 update so decided to post the AOSP/Stock kernel earlier than I would normally with a few Linux version update patches. With that said updating the Kernel only takes a minute or so and not like asking to flash a new Rom. Kernels are easy and these days faster to flash than g-apps. Also used the 5.1.0_r3 source to compile the boot image for 5.1 instead of 5.1.0_r1 source I had been using. Honestly though did not check if anything changed that is packed into the boot.img along with the Kernel between r1 & r3 so may or may not make any difference what so ever.
Forgot, marked the cm-12.1 kernel as beta just because cm-12.1 is pretty much beta. Otherwise the Starship 12.1 Kernel is the Starship CM12 Kernel merged with the Cyanogen 12.1 Kernel . Not that the two had been far apart to start but the 12.1 CM Kernel merged into the Starship cm12 kernel clean as a whistle with 0 conflicts. Was pretty happy about that so going foreword will just be working on the 12.1 Kernel with the Starship cm-12 Kernel soon going the way of the 5.0 - 5.0.2 Stock/AOSP Starship Kernels.
Now finally since the actual Starship Rom I have been working on since the darn preview release ending as mostly caf based with CM-12.1 coming together can start updating from 5.0.2 into 5.1 as had just finished going over the first draft and was about to post when the 5.1 update hit. Otherwise wanted to post the first draft and then go over the entire Rom a second time looking over the theme images, features and optimizations with a magnifying glass.
Have updated both Stock / AOSP and cm-12.1 Kernels up to Linux 3.4.65 with a few other additions and weeding. Has and been running pretty sweet on both so far.
Stock / AOSP 3.4.65 Kernel boot.img has been compiled using the 5.1.1 AOSP Source and tested on both 5.1.0 & 5.1.1 with no issue and as mentioned above running pretty sweet.
I cant install on aicp 5.1.1
Sent from my Nexus 5 using XDA Premium HD app
Woah,kitkat in 2018? You got to be crazy!
Hello guys, you may have noticed my absence from the forums as of late. 2017 was a really busy year for me. I had some free time during the holidays, and i finally got to bringup up kitkat for the z7 max from scratch, something that was on my mind for a long time. I consider kitkat to be the pinnacle of android as far as UI, performance and efficiency go, and while i use oreo on my redmi note 4x, i object with what google has brought to the table since lollipop in all areas.
My build is not vanilla lineage11/cm11 sources, i have used pac-rom kitkat(best rom ever for me) sources as well and ported all features to lineage11(or rather backported all the security fixes to the pacrom frameworks), therefore the rom has all the customization one could need.
The device tree is a heavily tweaked(almost built from scratch) oneplus one tree with many drivers from the opo(like wifi and bluetooth) ported to our device.
Kernel is pure nubia nx505j kitkat kernel as released from ZTE with the addition of opo wifi prima driver and some fixes to get it to compile and restore features like native panel d2tw, vibrator strength control and keydisabler(thanks to paolow8). Antutu scores about 52000, but the phone feels insanely faster than the heavily customized cm12.1/cm13/nougat kernels and battery life is the best i have ever seen on the device. I may add some features like f2fs support in future as well as upstream it to the latest linux version(3.4.113).
Vendor blobs consist mostly of the latest from nubia 1.64 firmware(last kitkat version), some opo blobs from latest cos11, and some from the latest lollipop 3.89 version.
Without further ado, here is the folder with the rom, newly built recovery by me with decryption support(encryption works fine on the rom) and some camera apps to improve your camera experience(i like oppo cam best): https://mega.nz/#F!10RmSaAJ!NhWzzW_E9Wimxi_LG3KlKA
To install it , you don't have to downgrade to kitkat or anything, the rom has unified partition support, and works fine with the latest 3.89 baseband(may even add the installer to flash it in later builds). Wiping data, cache and system should do(if you come from official lollipop or any of the new roms with unified data partition). Keep in mind that f2fs is not supported yet, therefore you will have to format your data partition to ext4 if you use f2fs.
I built this rom for my usage, therefore since i plan to use xposed and microg, signature spoofing and xposed work out of the box. No need to workarounds, patchers, modules or anything. The (un)official installers work without hiccups.
For the crazy enough to use this rom, have as much fun as i did developing it. Things i have to test yet are 2 sims together(both sim slots work with mobile data, just didnt have a second sim to test them together) and sdcard(should work fine). Everything else is tested and works fine.
Special thanks to paolow8, a great dev and his sources were a huge help.
PS. I will get my sources up on github as soon as i can.
Thank you for your work!
thank you for your work too !
Thanks, this is the most complete 4.4.4 Z7 Max ROM ever.
Are there any roms or custome recoveries for the ZTE Max Blue?
I agree 100% with you: 4.4.4 is state of the art. Questions: IR and screen trasmission works fine?
Edit: CHECK! Screen Trasmission works like a charm! IR says "not supported".
Thx's a lot, you have made an happy man
Edit 2: SDCARD don't work, for me. If you have a fix please share
Edit 3: For more precision: The unmountable partition is Ext Card.
While everything works perfectly (in recovery and in other ROMs) it is impossible to format or unmounting external card from Android-> Settings-> Storage.
The only flaw of an otherwise perfect ROM for me.
Is it a common problem? Did it happen to anyone? Please, if you have a fix share it
I need my settings to know what kind of phone I have
The SD card don't work! :crying:
SD card issue fixed, since it's been almost a year i got in touch with the friend to whom this phone was donated...
Just redownload and reinstall the rom, no wipes needed. It was a simple fix in the kernel ramdisk.
pchatzop said:
SD card issue fixed, since it's been almost a year i got in touch with the friend to whom this phone was donated...
Just redownload and reinstall the rom, no wipes needed. It was a simple fix in the kernel ramdisk.
Click to expand...
Click to collapse
Thx's a lot, pchat. I'm very grateful <3
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Latest information about OREO builds can be found HERE.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash HB bootloader or Bootloader 4.2 attached in Downloads section.
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.
General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.
@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs from O for now. I know already about all major issues.
Thank you!
Great to see some development for the Transformer Prime
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Clamor said:
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?
shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.
Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?
@shinzz TWRP from download section
any update?
shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP
ProtonAOSPAndroid 12 ROM for Pixel 3
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Refer to screenshots here.Installation:
This ROM is distributed as an otapackage, meaning that it can be sideloaded via recovery.
To install this ROM, download the ZIP, reboot your device to recovery, use the command "adb sideload <zip name>", and then format data.
Changelogs:
- Initial build.
- merge aosp r26 tree changes for bluecross
- include active edge and flip to shhh
- switch to vulkan UI renderer (smoother animations)
- use aosp's r26 kernel
Known issues:
- None so far.
Notes:
- ROM ships with minimal gapps.
- Boot image of the ROM is provided for magisk patching.
- This is an unofficial build.
- ROM's features here
Downloads:
ROM | Boot Image
Consider buying me a cup of coffee if the ROM helped, I'll appreciate it
ROM Source Code
Kernel Source Code
Device Tree
Reserved.
Nice to see A12 roms are rolling in now.
Psyched to see this! The ROM runs great so far.
One thing I did notice is that the ability to toggle camera and microphone permissions is missing from both settings and quick-settings. I'll try re-installing and see if that helps, but is this the case for anyone else?
Do I need a stock ROM installed before flashing it?
3XL????
Are this rom will gonna be official soon?
Failed to download boot.img
Is it possible to make this rom vanilla?
Hello, first of all thank you dev for bringing the almighty protonaosp to blueline!
Done sideloading a couple of hours ago. First impression, rom is clean and buttery smooth. There were stutters at first when the phone encounters new animation but after that it is astonishingly fluid. Thanks to the vulkan i guess. Will report more in a couple of days for daily usage scenario.
Pls add more gapps package like message, gmail, drive, map, etc
Everything is working now, please add vanilla build for stable release.
Zulu48 said:
Pls add more gapps package like message, gmail, drive, map, etc
Click to expand...
Click to collapse
The purpose is for a clean, minimal initial package. Just install those from the Play Store or using their APKs afterwards.
Cant flash any gapps due to low system storage.please make a gapps build from
your next build.atleast replace aosp apps with gapps.
Hi thanks for the work.
But none of the download options are working.
Can you please fix and share those links.
Again, thanks for the work.
With a custom rom like ProtonAOSP, will this be recognised by Google Photos still as a Pixel 3 so the unlimited photo upload (in data saver quality) is still working?
Any update of this rom?
Links seem to be broken.