SkyHigh Kernel -- Ported to SM-G920P (Sprint Galaxy S6).
This is, unquestionably, the most up to date kernel for the S6 devices. That includes upstream kernel (vanilla) additions bringing it to the latest (3.10.108) publicly released. This project started as a port of the SkyHigh kernel, originally by @UpInTheAir, to the G920P kernel. this kernel, however, has a great deal of further enhancements and optimizations relevant to Sprint Galaxy S6 device. The boot image build is not embedded in the kernel sources, as it is in the original, rather is an automated build in a separate project.
Donations:
I do accept donations, you are by no means required to, it just invigorates me to do more stuff in the kernel . With that said, apparently some devices fail to show the donation link next to posts, so you can click here to donate.
DISCLAIMER
Always READ THE DISCLAIMER before engaging in modifications to your phone.
Thread Rules
This thread is for the development and furtherance of kernel features. There are a handful of rules to this development forum with which you must comply or you'll likely get ignored:
This is not a general Q&A thread, it is a development thread. Please use the Q&A thread for general questions.
Do not ask @UpInTheAir for support, this port is not one he maintains;
Do not post anything without first searching the forums, if your issue has been discussed before, you will get no response;
Do post anything relevant to the development and furtherance of the kernel. Please use the Q&A forums for questions and general discussions.
Features
Based on the latest available official Samsung source: Samsung OSRC
Base sources upgraded to Linux 3.10.108
A ridiculous number of optimizations and kernel bug reparations see all commits here;
Extensive Synapse app support for many kernel configurations;
ktoonservative Hotplugging CPU Governor (default, others available);
ktoonservative tweaks (e.g., overrides standard cpufreq screen-off handling);
Over/Under Clock and Voltages;
Wakelock control;
Multipath TCP Support (use Synapse to enable and select desired congestion algorithm);
F2FS support built in to kernel;
exFAT (OTG works), CIFS, NTFS, CIFS as modules (use Synapse to enable);
Permit FULL (auto)ROOT: ramdisk patched to support SYSTEM-LESS SuperSU or MAGISK;
Tether / Hotspot Fix Built In (N Kernels)
Auto-Install busybox & Sqlite3 to /system/xbin (on flash);
ramdisk base: per Sprint ROM releases;
KNOX WARRANTY VOID: 1;
SELinux PERMISSIVE (default) or ENFORCING (optional);
OTG support
DEEP SLEEP FIX;
init.d script support (place scripts in /system/etc/init.d & set permissions to 755 or 777 and reboot);
stock dt.img;
Mali GPU DVFS disabled for min/max frequencies;
Secure storage = false (prevent WIFI settings & passwords wiping on reboots);
Many descriptions are in the Synapse Application. If you require more info, follow the thread rules above.
Flash Descriptions:
Note that there are two downloads: an Update and Full boot image.
The Updates are for currently running ROMs. If you just want to update the kernel and related utilities (startup scripts, busybox) and have no other modifications to your boot image, download and install the Update version. The Update injects the kernel update into your existing boot image, it does not touch the remainder of the boot image. The update is also useful in cases when folks dirty flash ROMs just to change features or have older ROMs and want to try the latest kernel, therefore do not have the ROM flash install the kernel at all. The issue with that is the ROM flashes generally do not know to keep the kernel modules, so those get deleted. This updater will reinstall those as well. In brief, it is an update of the kernel and its important files only, it does not root the ROM as does the full version.
The Full boot image flash is a complete boot image, which is the normal flash. However, some ROMs install other systems (e.g., my hotspot fixes) which also modify the boot image, specifically files in the ramdisk. For initial, or clean installs of this kernel, download and install the Full flash. It will also root the ROM for you if not already rooted (SuperSU is installed). You will want to add other boot image modifying flashes after that (though there are not that many flashes that actually modify the boot image).
The general rule is this: if you are installing this kernel on a ROM and have never installed this kernel, use the full version. If you are already running tdhite SkyHigh on a ROM, download and flash the Update version of the kernel.
tdhite SkyHigh v7.30, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: a0b362bf71767cc4418d800ded163850
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.9.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.9.20180424:
Magisk Module AFH Mirror
MD5: b4f841be0f5881e0fbbd97152c714e0d
Memory leak fixes (no known/reported leaks remain).
Updated embedded Magisk to v18.00 and roots the phone therewith.
Passes SafetyNet Checks!
Recovery Flashables for based on latest MM kernel sources and firmware (PL3 through QB1) ROMS
Dramatic boot up time improvements (impressively fast)..
Ramdisk (boot image) will work with PL3 through QB1 Firmware.
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . . subsequent boots are smoking fast.
Kernel Update (updates only the kernel in your existing boot image and utils)
XDA Downloads: tdhite SkyHigh v4.10 on XDA
AFH Mirror: tdhite SkyHigh v4.10 Update Only;
MD5 Hash: 23ebe23c2c1a326f9b9970a2c1746457
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v4.10 Full;
MD5 Hash: 60982a190838f7cb5dedd749821bc93e
Instructions
Make sure you are running a MM 6.0.1 or N 7.0 (Stock is fine);
Make sure you have TWRP 3.0.1-0 (or higher version) loaded as your customer recovery;
Download the TWRP flashable zip for your specific version of Android and firmware, placing the flash on your phone for subsequent 'Install' in TWRP;
Reboot into TWRP Recovery;
The smart user will perform a backup in TWRP;
Flash the zip'
Reboot System;
Use the Synapse App to configure the many options as you deem desirable, of course pursuant to the DISCLAIMER.
The first boot will take a while, give it some time. A couple minutes is not unlikely at all, possibly more.
Credits
@UpInTheAir - early, initial base Synapse support and kernel optimizations
@topjohnwu - root & Magisk app
@Chainfire - root & SuperSU app
@AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
@halaszk88 - patches and some Synapse code @UpInTheAir adapted to many of his kernels
@dorimanx - BusyBox and various ramdisk tweaks/ideas
@apb_axel - @UpInTheAir and @tdhite (for this port) adapted and used many of the Synapse controls
@arter97 - various source fixes/patches
@ktoonsez - ktoonservative hotplug governor
XDA
Samsung OSRC
and many others!
check gitHub source credits
Users that provide proper bug reports with an element of self-troubleshooting. Constructive feedback is always welcome.
IF ANYONE WAS FORGOTTEN, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
Older Versions are in Post #3 below.
As a final note, the sources are pulled by a Google repo manifest, which is within the "teamspr" project in link listed in the 'Source Link' below. The manifest shows the various github repositories for the project. If you need help with repo, let me know and we will get you setup with the code and how to view it.
XDA:DevDB Information
SM-G920P SkyHigh Kernel Port, Kernel for the Sprint Samsung Galaxy S6
Contributors
tdhite, @UpInTheAir (for initial base)
Source Code: https://github.com/TeamSPR
Kernel Special Features: Synapse ++ | EXT4 | F2FS | exFAT | NTFS | CIFS | Linux 3.10.108 | many optimizations and bug reparations | ktoonservative hotplugging governor | Optional SElinux permissive | Deep sleep fix | init.d support | See above for more.
Version Information
Status: Stable
Current Stable Version: 7.30 (v1.8.20190119)
Stable Release Date: 2019-01-19
Created 2016-04-02
Last Updated 2019-01-21
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Disclaimer of Title Warranty
THERE IS NO WARRANTY OF TITLE FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING ANY CONVEYOR OF THE PROGRAM MAKES NO WARRANTY OF ANY KIND THAT HE OR SHE HAS ANY TITLE OR THE RIGHT TO TRANSFER ANY TITLE TO THE PROGRAM TO YOU. YOU ACCEPT THAT, IN FACT, YOU RECEIVE NO TITLE TO ANY OF THE PROGRAM.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Reserved
Older Versions
tdhite SkyHigh v7.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 71996970885feb2cddf6cfa101891793
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.9.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.9.20180424:
Magisk Module AFH Mirror
MD5: b4f841be0f5881e0fbbd97152c714e0d
Added SmartAssV2 Governor.
Nexus governor should now be visible (but is very unstable, do not use this for now).
Updated embedded Magisk to v16.40 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
tdhite SkyHigh v7.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
XDA Project Mirror
MD5 Hash: 8d02f4698df1a7ed54673209b9aae01a
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.8.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.7.20180101:
Magisk Module AFH Mirror
MD5: e533e7b90202beba93df462bc945f9c8
Rebased all commits onto latest Samsung released kernel sources.
Updated embedded Magisk to v16.30 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
The sky-high module now supports calling a script every time the cortex tuning script executes (appx. every five seconds). Just place a valid script in "/sdcard/SkyHigh/scripts/user.sh" and that will get called by the /system/xbin/cortexbrain-tune.sh script each time it executes in the background. Be very careful, the user.sh script has full root access!
tdhite SkyHigh v6.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 6126ec42eea993398a08a205d514e5e2
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.7.20180101. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.7.20180101:
Magisk Module AFH Mirror
MD5: e533e7b90202beba93df462bc945f9c8
Updated embedded Magisk to v15.10 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
tdhite SkyHigh v6.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 646af6e2cbe63224d116595e1eec3597
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.6.20171210. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.6.20171210:
Magisk Module AFH Mirror
MD5: 91a0eb89329f25bab6aab6f656b04745
Updated to Linux v3.10.108.
Additional optimizations and security additions.
Passes SafetyNet Checks!
Roots the phone with Magisk v14.5(1456).
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
Remember that when you try to update the MagiskManager app manually, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
tdhite SkyHigh v5.02 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 8d049afab573d9e20ab65c1c73a6af31
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.50.201709729. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.5.20170929:
Magisk Module AFH Mirror
MD5 Hash:e3f90a6e80c239add1803a78911018be
Passes SafetyNet Checks!
Roots the phone with Magisk v14.2 (MagiskManager will request that you update as appropriate)
Remember that when you try to update the MagiskManager app manually, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
Kernels for Nougat 7.0:
tdhite SkyHigh v5.01 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
AFH Mirror
XDA Downloads
MD5 Hash: 0e3eb7b60276c4ce05049b517a23fd7c
Passes SafetyNet Checks!
Many new optimizations (even more than beta 4.99b).
Roots the phone with Magisk v12.0
Places the MagiskManager 4.3.3 in /sdcard/MagiskManager-4.3.3.apk for easy installation after flashing the kernel. Just open your file browser and click on the file, then select install.
If you are SuperSU or Magisk v13 rooted, you should uninstall your root manager app and unroot. The kernel flash will re-root you. If you are Magisk v12.0 rooted, no work needed, just flash the kernel and profit!
Both Magisk and SuperSU provide for uninstall applications. If you don't know how to do that, read the SuperSU or Magisk pages. It is not difficult -- basically for SuperSU, you need to: 1) delete the SuperSU app while in Android ROM; 2) boot into TWRP (recovery); 3) delete /data/su.img and /data/stock_boot_*.img; and finally 3) flash this kernel, but not before). For Mgisk, just use the Uninstaller module.
Note, you need to update the MagiskManager app after booting up. The app, as installed by the Magisk installer, will tell you to update from the App store -- your phone is rooted, you just need to update the app. The app installer (apk) is placed by this kernel flash in /sdcard/MagiskManager-4.3.3.apk for easy access (see above).
Remember that when you try to install the manager app, using your file manager, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
After you install the Magisk Manager, Synapse will obviously request root access, grant it 'forever' so it will work on boot thereafter. On first time running, Synapse might (rarely) fail and quit or complain there is no root or uci access. To fix that, just open your 'Recents' list and swipe away Synapse. Restart it and it should now have root and work properly. Setup the kernel as you like from there.
The kernel startup scripts are now part of a Magisk module. If you reinstall Magisk by your self, it may clobber that module. I'll post the zip for that if folks have trouble. DO NOT DELETE THE SKYHIGH MODULE in the MagiskManager app.
tdhite SkyHigh v5.00 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
AFH Mirror
XDA Downloads
MD5 Hash: b28ea6ad870ba849ba442b96700348a1
Many new optimizations (even more than beta 4.99b).
Roots the phone with Magisk v12.0
Places the MagiskManager 4.3.3 in /sdcard/MagiskManager-4.3.3.apk for easy installation after flashing the kernel. Just open your file browser and click on the file, then select install.
If you are SuperSU or Magisk v13 rooted, you should uninstall your root manager app and unroot. The kernel flash will re-root you. If you are Magisk v12.0 rooted, no work needed, just flash the kernel and profit!
Both Magisk and SuperSU provide for uninstall applications. If you don't know how to do that, read the SuperSU or Magisk pages. It is not difficult -- basically for SuperSU, you need to: 1) delete the SuperSU app while in Android ROM; 2) boot into TWRP (recovery); 3) delete /data/su.img and /data/stock_boot_*.img; and finally 3) flash this kernel, but not before). For Mgisk, just use the Uninstaller module.
Note, you need to update the MagiskManager app after booting up. The app, as installed by the Magisk installer, will tell you to update from the App store -- your phone is rooted, you just need to update the app. The app installer (apk) is placed by this kernel flash in /sdcard/MagiskManager-4.3.3.apk for easy access (see above).
Remember that when you try to install the manager app, using your file manager, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
After you install the Magisk Manager, Synapse will obviously request root access, grant it 'forever' so it will work on boot thereafter. On first time running, Synapse might (rarely) fail and quit or complain there is no root access. To fix that, just open your 'Recents' list and swipe away Synapse. Restart it and it should now have root and work properly. Setup the kernel as you like from there.
The kernel startup scripts are now part of a Magisk module. If you reinstall Magisk by your self, it may clobber that module. I'll post the zip for that if folks have trouble. DO NOT DELETE THE SKYHIGH MODULE in the MagiskManager app.
Kernels for Marshmallow 6.0.1:
Recovery Flashables for based on latest kernel sources and firmware (CPL3 and QA2) ROMS
Ramdisk (boot image) updated to QA2 (though will work on CPL3 as well).
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.70 Update Only;
MD5 Hash: c6432dbcb67a15f0663c11c5132eb0d1
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.70 Full;
MD5 Hash: 0e8f7450cf9b01d4173b64cd50afc55c
Recovery Flashables for based on latest kernel sources and firmware (CPL3) ROMS
Ramdisk (boot image) updated to CPL3 (there are many security context changes)
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.60 Update Only;
MD5 Hash: 1e98841a76aea39146cd27b478c2e5bc
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.60 Full;
MD5 Hash: 153506f01cb2355b54d70c467a10ebff
Recovery Flashables for based on latest kernel sources and firmware (CPJ1 and CPK1) ROMS
Ktoonservative governor defaults to allow additional screen-off CPUs
Reduced polling for cpufreq info when screen is on
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.50 Update Only;
MD5 Hash: a4c68f1a7e03da40795d8abd56586f4e
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.50 Full;
MD5 Hash: b1c590f644a4023f3bf53ff330c38c80
CPJ1 and CPK1 base
Ktoonservative governor now overrides default screen-off clock speed handling
Fixed shell access for crond (crontabs will now work properly)
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image)
AFH Mirror: tdhite SkyHigh v3.40 Update Only;
MD5 Hash: 528f0e317c93bd7d645b16b47727e56f
Kernel Full Boot Image (installs entire boot image)
AFH Mirror: tdhite SkyHigh v3.40 Update Only;
MD5 Hash: c4c811233f016ab555adf06c86739721
CPJ1 and CPK1 base
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.36a;
MD5 Hash: 6cea4a864da3991142f899525e1375d2
Changes:
Rebuilt specifically to fix the kernel modules (they were not loading in previous PJ1 builds when enabled in Synapse).
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Previous Downloads for Latest (PJ1) ROMS
PJ1 Previous Versions Download links removed due to bad module builds.
Ramdisk based on (PJ1) Stock ROM.
Cron service repairs (many).
ADB support fixed, now uses standard (secure) access from Stock ramdisk.
SuperSU: @Chainfire v2.78-SR1
Download for PI3 ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.34;
MD5 Hash: 2253a78d5d5ae4413d63ebf424f3034d
Changes:
Ramdisk based on G910PVPS4CPI3 (PI3) Stock ROM.
SuperSU updated to: @Chainfire v2.78-SR1
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PF4 Based ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.3;
MD5 Hash: 47eb72636cf66e9a6c720b8ab141027d
Changes:
Ramdisk based on PF4 Stock ROM.
Busybox installation reparations for Stock ROMs.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PD3 Based ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.22;
MD5 Hash: 8d6b47c2b9c73b8f23b26a893880154f
Note: This is likely the last update for PD3 and below ROM bases. PF4 and above will get further updates.
Changes:
Busybox installation reparations for Stock ROMs.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PD3 and Earlier Based MM ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.21;
MD5 Hash: 8c3deedc7d1acb2ee19657dc6ecff00e
Changes:
SuperSU updated to 2.76
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.2;
MD5 Hash: 1d9ac4781019de75e33ac5b86259dc4e
Changes:
F2FS Support updates and backports from upstream (kernel.org) kernel (built-in)
Multi-path TCP support with matching TCP congestion algos
Many minor optimizations and bug fixes from upstream -- see sources for further details.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.84;
MD5 Hash: 57dc34e5b2f6142255b0e003f94290b2
Changes:
F2FS Support (built-in)
exFAT Support as module (use Synapse to enable); works with OTG
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.83;
MD5 Hash: 9c0cf7d66b362e7a54b6b9872a935e8b
Changes:
SuperSU 2.71 updated
Boot time optimizations
Busybox install support
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.82;
MD5 Hash: 08f14d05999aa23a75a4aace5ce1e18b
Changes:
Flash installer fixes broken ROMs (mistaken selinux contexts on telephony services);
Incorporates all prior updates as well.
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.81;
MD5 Hash: 0bb4ddaed59c188b084dc498a1fb1db7
Changes:
Fixed Synapse display errors (all known);
Sensor wakelock support (required to fix Synapse display error)
NOTE: THIS IS A BETA VERSION AND SUBSEQUENT VERSIONS PRIOR TO RELEASE WILL NOT BE CHANGE LOGGED;
AFH Mirror: tdhite SkyHigh v2.8;
MD5 Hash: d93fa401ee23f3b689edaa0614cedefa
may i ask about the battery life of this kernel?
is there any known issue list that i should read before flashing this?
thank you very much for this first kernel for our G920P.
tdhite said:
Port of the SkyHigh Kernel, originally created by @UpInTheAir, to SM-G920P (Sprint Galaxy S6).
This port is rebase of the SkyHigh kernel commits onto the G920P kernel base sources, as well as other and modifications relevant to Sprint Galaxy S6 device. The boot image build is not embedded in the kernel sources, as it is in the original, rather is an automated build in a separate project.
DISCLAIMER
Always READ THE DISCLAIMER before engaging in modifications to your phone.
NOTE: This Thread is Under Construction and will be Completed by End of Evening, 04/03/2016, not before. Please honor good 'dev thread' etiquette and do not post anything until you 1) have the kernel; 2) have installed it; and 3) have a problem or feature request related to it.
This is a healthy effort to both create the port and build the content in this thread so give fair time as we all have important life duties outside XDA. Also, this is not a general Q&A thread. That is why we have multiple forums, please use the Q&A thread for general questions. That forum will autogenerate soon enough.
Thread Rules
This thread is for the development and furtherance of kernel features. There are three rules to this development forum with you must comply:
Do not ask @UpInTheAir for support, this port is not one he maintains;
Do not post anything without first searching the forums, if your issue has been discussed before, you will get no response;
Do post anything relevant to the development and furtherance of the kernel. Please use the Q&A forums for questions and general discussions.
Features
A ridiculous number of optimizations and kernel bug reparations see all commits here;
ktoonservative Hotplugging CPU Governor (default, others available);
Permit FULL ROOT: ramdisk patched to support SYSTEM-LESS SuperSU v2.70 (RC);
Based on official Samsung source: Samsung OSRC;
ramdisk base: G920PVPU3CPB6;
KNOX WARRANTY VOID: 1;
SELinux PERMISSIVE (default) or ENFORCING (optional);
DEEP SLEEP FIX;
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash);
Linux 3.10.101;
init.d script support (place scripts in /system/etc/init.d & set permissions to 755 or 777 and reboot);
adb insecure;
stock dt.img;
Mali GPU DVFS disabled for min/max frequencies;
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots);
Synapse app support for many kernel configurations;
Many descriptions are in the Synapse Application. If you require more info, follow the three rules above.
Synapse Feature Support
Many! -- details coming soon . . .
Download
TWRP Flashable:
NOTE: THIS IS A BETA VERSION AND SUBSEQUENT VERSIONS PRIOR TO RELEASE WILL NOT BE CHANGE LOGGED;
AFH Mirror: tdhite-G920P-SkyHigh-16-04-02.zip;
MD5 Hash: 3209035090a6c207596321e91882b4ca
Instructions
1) Make sure you are running a MM 6.0.1 ROM (Stock is fine);
2) Make sure you have TWRP 3.0.1-0 (or higher version) loaded as your customer recovery;
3) Download the TWRP flashable zip and place on your phone for subsequent 'Install' in TWRP;
4) Reboot into TWRP Recovery;
5) Flash the zip
6) Reboot System
The first boot will take a while, give it some time. A couple minutes is not unlikely at all, possibly more.
Credits
@UpInTheAir (and his family :angel
@Chainfire - root & SuperSU app
@AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
@halaszk88 - patches and some Synapse code @UpInTheAir adapted to many of his kernels
@dorimanx - BusyBox and various ramdisk tweaks/ideas
@apb_axel - @UpInTheAir and @tdhite (for this port) adapted and used many of the Synapse controls
@arter97 - various source fixes/patches
@ktoonsez - ktoonservative hotplug governor
XDA
Samsung OSRC
and many others!
check gitHub source credits
Users that provide proper bug reports with an element of self-troubleshooting. Constructive feedback is always welcome.
IF ANYONE WAS FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SM-G920P SkyHigh Kernel Port, Kernel for the Sprint Samsung Galaxy S6
Contributors
tdhite, tvm2487, @UpInTheAir (for many of the commits picked into this kernel).
Source Code: https://github.com/teamspr/kernel/tree/skyhigh
Kernel Special Features: Synapse ++ | EXT4 | exFAT | NTFS | CIFS | Linux 3.10.101 | many optimizations and bug reparations | ktoonservative hotplugging governor | Optional SElinux permissive | Deep sleep fix | init.d support | See above for more.
Version Information
Status: Beta
Current Stable Version: v2.8
Stable Release Date: 2016-04-02
Current Beta Version: v2.8
Beta Release Date: 2016-04-02
Created 2016-04-02
Last Updated 2016-04-02
Click to expand...
Click to collapse
Excellent job Tom! You worked extremely hard on this and it paid off sir.
Sent from my SM-G925P using XDA-Developers mobile app
If i flash this kernel,can i have mobile hotspot menu?
mahdi72 said:
If i flash this kernel,can i have mobile hotspot menu?
Click to expand...
Click to collapse
Please use the q&a thread for questions, as stated in the OP, in the future. That said, a kernel has nothing to do with menus.
Sent from my SM-G920P using Tapatalk
I flashed this on my S6 and man I sure miss getting to use this kernel and synapse on my Sprint Note 5 but at @UpInTheAir is taking some time off till the end of April until he updates it to work on 6.0.1. I have a couple of java string errors when it comes to the wakelock controls but that might be due to the issue I'm having with the stock ROM. For some reason after I ODINed the 6.0.1 firmware on my phone won't activate and it says it is on Samsung Network but hotspot and everything else works so I wasn't going to mess with it. Great job with the kernel. I cannot wait till my note has it again.
Sent from my SM-N920P using XDA-Developers mobile app
Here are the screenshots of what it says. I know you probably need a logcat but I'm pretty sure I know what the problem is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G920P using XDA-Developers mobile app
Love this kernel as it doesn't give you that warning "kernel not seandroid enforcing" but I still benchmark slower than stock even with everything set to performance. I don't understand!
Any feedback would be greatly appreciated! Thank you!
Eric
For some reason my phone won't boot up with this kernel :/
my S6 didnt bootup after flashing TWRP 3.0.1-0 actually
i had to use the old TWRP 3.0.0-1 and flashed this kernel after, and it works.
Bobthahog said:
Here are the screenshots of what it says. I know you probably need a logcat but I'm pretty sure I know what the problem is. View attachment 3707387View attachment 3707388
Sent from my SM-G920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Ugh. I know the issue. Will rev a fix. Not sure how i missed that, but adding tests to cover this issue as well.
Sent from my SM-G920P using Tapatalk
tdhite said:
Ugh. I know the issue. Will rev a fix. Not sure how i missed that, but adding tests to cover this issue as well.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Thanks man. U did a magnificent job porting this over to the S6. I just figured it was the issue I was having with phone not wanting to activate on Sprint network.
Sent from my SM-N920P using XDA-Developers mobile app
Updated -- 04/09/2016
The flash, kernel and synapse support was updated to fix reported errors.
See the OP for download and flash instructions (no different instructions, they are just in their normal place).
tdhite said:
The flash, kernel and synapse support was updated to fix reported errors.
See the OP for download and flash instructions (no different instructions, they are just in their normal place).
Click to expand...
Click to collapse
Phone still won't boot up! -__- but now it gets stuck at the "Sprint LTE Plus" splash screen (instead of the Samsung splash screen).
I honestly don't know how to help you. I've asked for logs, rom info yet get nothing. How long did you wait for boot? OP says can take a while. You cannot send a logcat?
Seriously, I'd love to help, but it takes more info when one phone out of many, many others that work fine has an issue. There is clearly something about your rom or apps or whatever, but I have nothing to go on to help you.
Sent from my SM-G920P using Tapatalk
I flashed the updated kernel and it's working great. No errors in synapse. Awesome job.
Sent from my SM-G920P using XDA-Developers mobile app
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
I flashed the updated kernel and it is working great. No errors in synapse. Awesome job man.
Sent from my SM-G920P using XDA-Developers mobile app
tdhite said:
I honestly don't know how to help you. I've asked for logs, rom info yet get nothing. How long did you wait for boot? OP says can take a while. You cannot send a logcat?
Seriously, I'd love to help, but it takes more info when one phone out of many, many others that work fine has an issue. There is clearly something about your rom or apps or whatever, but I have nothing to go on to help you.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
OK so I feel like an idiot bro... I didn't know that your kernel script wiped cache/dalvik cache lmao -__-
THAT'S why it was taking so long to boot. Sorry bro! -__- Anyways this thing is smooth as hell!
Nevermind... Had to uninstall this kernel. My phone kept turning off & rebooting itself. No problems what-so-ever with the stock kernel. This kernel was causing some major hiccups with my phone.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM for the Samsung Galaxy S4 (Qualcomm variants)
Brought to you by AntaresOne
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S4. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel - Download the ZIP file and flash it in recovery or keep stock kernel (only for CM11-based ROMs after 6 August 2014 & CM12-based ROMs)
You current rom will not be erased by the installation.
Download links are in the third post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
3. Other systems (once ported to device)
Firefox OS and Sailfish OS are just another Android ROM under MultiROM's point of view, so add them as if it were Android.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Alucard Kernel w/ kexec-hardboot patch - https://github.com/Alucard24/Alucard-Kernel-jfltexx
Googy-Max3 kernel w/ kexec-hardboot patch - https://github.com/googyanas/Googy-Max3-Kernel
Hulk kernel w/ kexec-hardboot patch - https://github.com/Tkkg1994/Hulk-Kernel
Imperium kernel w/ kexec-hardboot patch - https://github.com/Slim80/Imperium_Kernel_TW_4.4.2
KT kernel w/ kexec-hardboot patch - https://github.com/ktoonsez/KT-SGS4
CM11 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-11.0
CM12 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.0
CM12.1 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.1
MultiROM device tree - https://github.com/AntaresOne/multirom_device_samsung_jflte
Big thanks to Tasssadar for this awesome utility.
Thanks a lot to @daveyannihilation for the S4 template.
XDA:DevDB Information
MultiROM, multiboot for Galaxy S4 (Qualcomm variants) (GRUB-like), Tool/Utility for the Samsung Galaxy S4
Contributors
AntaresOne
Version Information
Status: No Longer Updated
Current Stable Version: 20151029-v32b
Stable Release Date: 2014-09-01
Created 2014-09-01
Last Updated 2017-05-19
Changelog
15/6/2015 - v32a
Update after 6 months!! read post #669
Modified TWRP:
Base updated to 2.8.6.0
Sacrificed crypto and embedded SuperSU installer to get an image that fits 10.5MB recovery partition size
Detailed changes here
MultiROM:
Base update to v32
Added support for 5.1.x Lollipop ROMs
Better support for 5.0.x Lollipop ROMs
Detailed changes here
16/12/2014 - v30c
Modified TWRP:
Base updated to 2.8.2.0
Better support for primary/secondary Lollipop ROMs install/update
MultiROM:
Better support for Lollipop-based ROMs
Fixed the ghost update found in previous build
26/11/2014 - v30
Modified TWRP:
Add partial support for block_image_update in secondary ROMs ZIPs (Lollipop's default flashable zip format)
MultiROM:
Assume fstab version 2 by default
Fix klog saving and text size on emergency reboot screen
Write fstab for fw_mounter as version 2
12/11/2014
Device source:
Disable TWRP event logging
Modified TWRP:
Build an updated image without event logging
4/11/2014
Modified TWRP:
Add back "Share kernel" option (same behavior can be obtained by pressing "Remove boot.img" under MultiROM>List ROMs>*rom name*)
30/10/2014
Modified TWRP:
Update to v2.8.1.0
25/10/2014 - v29
MultiROM:
Minor updates
Full MultiROM Manager support (this fixes the ghost update)
Modified TWRP:
Full MultiROM Manager support
Uninstaller ZIP:
Add support for other jf variants
2/10/2014
Add support for MultiROM Manager app
1/10/2014 - v28c
Device source:
Add MicroSD Card to init devices
Fixed device autoboot in recovery after a reboot/shutdown
30/9/2014 - v28b
MultiROM:
ROM boot from external SD (MicroSD card) is now supported
TWRP Recovery:
General update (branch master)
Removed "Share kernel" option
ROM Installation to external SD (MicroSD card) is now supported
Uninstaller ZIP added back and now working
16/9/2014
TWRP Recovery:
Better MTP compatibility
12/9/2014
TWRP Recovery:
Merge twrp28 branch (now has MTP connection inside to transfer files between PC and device)
6/9/2014
Device source:
Clean and update init devices
Add volume keys init (now you can select ROM/tabs also with volume keys)
3/9/2014
Fixed installation on other jflte devices
1/9/2014 - v28
Device source:
add power button init (needed to reboot device when "an error occurred" and to exit from pong game, available by clicking on Miri)
Downloads
1. Main downloads
MultiROM EXT4 (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849558
MultiROM F2FS (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849563
Modified TWRP (20151029-v2.8.7.0): https://www.androidfilehost.com/?fid=24052804347849556
MultiROM Manager App: Google Play Store (by default it will install the EXT4 version!)
2. Kernels for primary ROM (Internal) based on Android 5.1.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.1 ROMs:
AOSP 5.1 & Optimized CyanogenMod 12.1 from JDCTeam: Alucard is embedded and always up to date
Alucard AOSPv2 5.1 v1.3ba
Stock CM12.1 kernel (included in ROM's zip)
3. Kernels for primary ROM (Internal) based on Android 5.0.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.0 ROMs:
Optimized CyanogenMod 12 from me and @alucard_24: Alucard is embedded and up to date
Alucard AOSPv2 5.0 v1.1a
Googy-Max3 v1.3.0
Hulk Kernel v1.3.1
KT-SGS4-LP5.0
Stock CM12 kernel (included in ROM's zip)
Kernel with kexec-hardboot patch for Google Edition 5.0 ROMs:
Alucard GE5 v1.1a
Hulk Kernel GE5 v1.3.1
Googy-Max3 GE5 v1.2.3c
Kernel with kexec-hardboot patch for TouchWiz 5.0.1 ROMs:
Hulk Kernel TW5 v1.3.1
Imperium LL v2.0
4. Kernels for primary ROM (Internal) based on Android 4.4.x KitKat
Kernel with kexec-hardboot patch for AOSP/CM 4.4 ROMs:
(builds up to 6 August, including CM11 M9)
Alucard AOSP v2.7.2a
(builds after 6 August, including CM11 M10)
Alucard AOSPv2 v1.4r
Googy-Max3 CM v1.2.5
KT-SGS4-KK
Stock CM11 kernel (included in ROM's ZIP) - All CM11-based ROMs after 6/08 with this android_kernel_samsung_jf source
Kernel with kexec-hardboot patch for Google Edition 4.4.x ROMs:
Alucard GE v2.4d
Googy-Max3 GE v1.2.8
Kernel with kexec-hardboot patch for TouchWiz 4.4.4 ROMs:
Googy-Max3 v1.3.0 TW 4.4.4
Hulk Kernel v1.2 TW 4.4.4
Imperium v1.14 TW 4.4.4
Kernel with kexec-hardboot patch for TouchWiz 4.4.2 ROMs:
Alucard TW v2.3ga
Googy-Max3 v1.3.0 TW 4.4.2
Hulk Kernel v1.2 TW 4.4.2
Imperium v1.14 TW 4.4.2
5. Uninstaller
MultiROM uninstaller ZIP: https://www.androidfilehost.com/?fid=95747613655050515
Just flash this to disable MultiROM and delete all secondary ROMs.
Alucard-PWR-CORE dev thread by @alucard_24: http://forum.xda-developers.com/showthread.php?t=2590246
Googy-Max3 dev thread by @googy_anas: http://forum.xda-developers.com/showthread.php?t=2741181
Hulk Kernel dev thread by @Tkkg1994: http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
Imperium dev thread by @slim80: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/kernel-imperium-kernel-v1-0-t2910801
KT-SGS4 dev thread by @ktoonsez: http://forum.xda-developers.com/showthread.php?t=2297379
Useful tips
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
What storage for ROMs is supported?
Internal memory (/data/media-/sdcard) is supported as well as MicroSD card (/external_sd).
How many ROMs can I have and where are stored?
You can have as many ROMs as you can fit in internal memory and MicroSD card. All the ROMs are stored in /data/media/0/multirom/roms (in case of internal memory) and /external_sd/multirom/roms (in case of MicroSD card) drive. These folders are unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
I'm a F2FS user. Can I still enjoy MultiROM?
Yes, you can. Just flash F2FS version of MultiROM zip. NOTE: it is compatible only with full F2FS (so cache, data and system both at once), if you use a custom layout like F2FS for cache/data and EXT4 for system just edit the mrom.fstab file inside the MultiROM zip before flashing the first time or after with reflashing.
Can I have different versions of Android working alongside?
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, systems are separated.
Can I flash TouchWiz-based ROMs as secondary ROMs?
You can, but it's strongly unrecommended and not all the TW ROMs work if installed as secondary, plus are very bigger than other ROMs. I suggest to flash them only as primary ROM.
Can I configure boot menu to be showed only when I want?
You can. Boot in TWRP recovery, go under Advanced>MultiROM>Settings>Configure autoboot and set Keypress-based, then select a ROM to autoboot. In this way, if you power on your device boot menu isn't showed and the ROM you choose to autoboot is booted, but if you power on and rightly when you see "Samsung Galaxy S4" bootlogo you press and keep pressed Vol+ or Vol- button, boot menu is showed.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
nds850 said:
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
Click to expand...
Click to collapse
Alright I tried beanstalk like you mentioned and it rebooted into recovery the first time I tried booting in to it. It worked fine the 2nd time however. Currently have dirty unicorns, pa, and now bs. Sometimes when I click reboot on either one of these ROMs, it automatically reboots to recovery instead of multiboot. Don't know of this is a bug or not.
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 256 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
AntaresOne said:
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 128 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Cool. Thanks for the explanation. This multiboot is really awesome
I'm not sure I understand how you mean. I completely shut the phone off and wait for the RAM to reset. I then start the phone and in the MultiROM menu choose the ROM I want to use. The phone restarts and load to recovery. Does the RAM need to be cleared after choosing the ROM? If that is the case how do I do that?
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
BakaB said:
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
Click to expand...
Click to collapse
I would assume so. It should work on all jflte's. It works fine on my jflteusc.
@BakaB @bdog2015
Yes, it works on all jflte devices.
I337, I545, L720, M919, R970, I9505, I9507, I9508
Inviato dal mio GT-I9505
I have been trying to flash the MultiROM zip through TWRP Recovery and I keep getting the following errors:
Code:
assert failed: getprop("ro.product.device") == " jflte" | | getprop("ro.build.product") == " jflte "
But what's weird is that both the lines that script is looking for (ro.product.device & ro.build.product) both say jflte in my build.prop so I'm very confused. I'm running Alliance ROM v2.0 I9505XXUGNG2 with stock permissive kernel and TWRP 2.7.1.0
Any help/advice would be appreciated.
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Ok MultiROM is installed. After installing MultiROM I flash TWRP_multirom_jflte_20140901.zip through TWRP and then reboot recovery. When TWRP reboots, I don't have any options under Advanced for MultiROM. Recovery is now showing 2.7.1 in the top left whereas before it was showing as 2.7.1.0 so I know that the recovery has changed.
Have I done something wrong? When I reboot the phone I get the MultiROM boot screen coming up asking me to either let it boot into the internal ROM or touch to change, but when I boot into recovery I have no options for MultiROM. I am happy to upload any logs that might help to decipher the issue I am having.
Thanks for your help mate.
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Dude... I'm just an idiot. I had twrp holofied which wasn't showing the menus and buttons. This mod is AMAZING!!! Dude I have been looking for this forever, you are a king. I'm definitely gonna be using this from now on, thank you so very very much! [emoji4]
Alliance I9505
@daveyannihilation
Hahaha don't worry
Now just remember this
Inviato dal mio GT-I9505
Is the new build recommended or am I fine if everything is working for me?
bdog2015 said:
Is the new build recommended or am I fine if everything is working for me?
Click to expand...
Click to collapse
The only change in new build is the fixed installation on other jflte devices. If you installed the previous build without errors, no need to update [emoji1]
Inviato dal mio GT-I9505
Vanilla-ish AOSP 6.0.1_r9 ROM (MMB29S) for WiFi Nexus 9
This was created by building from MMB29S source and adding SuperSU/BusyBox... Plus customizations (advanced power menu, ART optimizations) borrowed from @GROGG88 on Nexus 5 forum and @craigacgomez. Also WebView commits from @craigacgomez.
Featuring:
Vanilla AOSP 6.0.1_r9 (MMB29S) for WiFi Nexus 9
v0.16 and up work with OpenGapps
ROOT and permissive kernel based on https://android.googlesource.com/kernel/tegra/+/android-tegra-flounder-3.10-marshmallow with added features!
Busybox v1.22.1 bionic now included
All future Marshmallow builds will all be based on this table - https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
I included RIL during building MMB29S so LTE (volantisg) should work WILL NEED A TESTER
UBERTC 5.2.1 arm64 compiled 3.10.40-marshmallow kernel
Decrypted device supported!
Can use f2fs for cache now! Thanks @xiaolvmu
Fast charge fix plus Force Fast Charge toggle added (Force Fast Charge off by default). Thanks @USBhost and @Captain_Throwback!
FSYNC toggle @franciscofranco
Use Kernel Adiutor from Play Store to toggle Force Fast Charge/toggle FSYNC - Fast Charge will disable media sharing with your PC to get a faster charge on low amperage USB ports...
I/O schedulers added - SIO, deadline FIOPS and cfq - SIO to default
OTG native support ( @craigacgomez) - use your favorite file manager
Advanced TCP congestion - cubic still default
File system support added for NTFS, EXFAT and CIFS - thanks @Captain_Throwback - also EXT4 for EXT3 support to optimize size a bit more
SELINUX to permissive
SuperSU 2.52 ( @Chainfire) - VERIFIED working
MiXplorer 5.4.6.BETA-B1509012 @HootanParsa (http://forum.xda-developers.com/showthread.php?t=1523691)
Reboot Menu with submenu for Reboot, Recovery and Bootloader respectively (from Nexus 5 forum THANKS @GROGG88)
Setup wizard crash fix (prefer Google WebView over AOSP fix from @craigacgomez)
MUST Flash a GApps (see Downloads) EVEN IF UPDATING from prior version(s)
***NOTE if using minimal GApps download any additional Google apps you might need that are missing from the Play Store!
Source:
https://github.com/bshiznit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please use TWRP 2.8.7.0. Must be at bootloader 3.48.0.0135 and have flashed the latest MMB29S vendor image (linked under downloads)!
Please wipe data and both caches (in TWRP got to Wipe --> "Swipe to Factory Reset") if not coming from my LMY48M ROM (I need to test) - otherwise please wipe
Downloads
Before flashing scroll down and read NOTES!
ROM
ODEX (faster initial boot and overall performance potentially):
MEGA https://mega.nz/#!7IdQETSL!aKO6ZwMSs1OoxRg6ECkEqLZDZYXH12cVa-HcQLZ46Q8
Dev-Host http://d-h.st/dlZF
md5 - 921aed6769acb63539bc0a3c752ee2af
DEODEX (for Xposed/GravityBox, theming, etc.):
MEGA https://mega.nz/#!zV0GQQhS!B0NjHyyzcxIj2IMgA6G0vZnv9lwywef3ckliMBEc2Nk
Dev-Host http://d-h.st/r8bu
md5 - 23b5b5483dc27778233419617fe54126
3.48.0.0135 bootloader and MMB29S vendor.img
WIFI:
MEGA https://mega.nz/#!mAs1zSrR!SNLB9nyfezzTMGFyh1yLaohP1Dv1w3kNcbCzZAszuW0
md5 - 11c6f1d2466b1be2eac66b99e9398213
LTE:
MEGA https://mega.nz/#!qV0SSSSB!BcaxZa_9NbGWWSBgY9lKb5C_ZV1OYwTmE0THSBI906U
md5 - f0eda5063e884f9ff5951e1449de919f
NEED fastboot
In fastboot:
WIFI:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
LTE:
fastboot flash bootloader bootloader-flounder_lte-3.48.0.0135.img
Both:
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Then ROM
Open GApps (closer to STOCK - choose ARM64 for Platform, 6.0 for Android then pick Stock for Variant)
http://opengapps.org/
I FLASHED:
MEGA https://mega.nz/#!fZFGxCxT!6k-DGsrmA3N_ATNJ3Odt2FBSgS-4go48r5ZGjcqXk3o
Dev-Host http://d-h.st/D4Jb
md5 - 3df13b1c7b666828bc0c2c03933f4f15
BaNkS Dynamic GApps
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
I FLASHED:
MEGA https://mega.nz/#!WNd3hAbB!DhcVL0Sfohyvg0-IyaZL8lLobzO7h7dgX5vl50OVSoY
Dev-Host http://d-h.st/S3zV
md5 - 857829d0e0d076b717cbb6c6355e229b
NOTE takes a WHILE (5-10 minutes) to boot up on first boot! ART is optimizing applications and it is set to EVERYTHING as we have sufficient system partition storage - for SPEED. There is no more dalvik-vm (no REALLY now - not even included in AOSP now)!
If you like it hit thanks! Donations are appreciated but never expected
I do this for a hobby and to keep my tablet running like new
Coming soon:
6.0 GApps links
Busybox inclusion
3.48.0.0135 bootloader and MRA58N vendor image downloads
NOTES:
ALWAYS flash GApps even if updating from a prior AOSP 5.1.x/6.0 release! ALL ROMs format the /system partition as part of the installation process and this is where the GApps are kept!
BACKUP using TWRP and/or Titanium - save those files off the device to a USB stick external HDD or whatnot! Not responsible for lost data!
WIPE Data in recovery unless coming from another Vanilla AOSP 5.1.x ROM!
Be sure you are at bootloader 3.48.0.0135 and have flashed latest vendor image (steps in this post)
ONLY TESTED USING TWRP 2.8.7.0
MUST FLASH a GApps zip after the ROM for Play Store, etc.
If you like it consider donating! A nice big solid state hard drive will let me build faster and for more devices! (YAY my build box now has 411GB free even after all this developing - thanks to all who donated)
Thanks:
@Chainfire for SuperSU and keeping it updated!
@Snuzzo for github familiarization and being a great dev and resource!
@GROGG88 - for the power menu and other patches (even though it was from Nexus 5 it worked great)!!!!
@craigacgomez for reboot submenu and OTG commits @Captain_Throwback and @USBhost for fast charge and additional file system commits, busybox
@dankoman and @Deltadroid for helping us in trying to get arm64 Gapps
@sykopompos for the sepolicy file and kernel instructions to allow root as well as the ART build.prop tweaks.
@scrosler great dev and good resource
Google for Android
AOSP for source!
Changelog:
MMB29S v0.51
Compiled from 6.0.1_r9 MMB29S source (ROM/kernel)
MMB29K v0.50
Compiled from 6.0.1_r1 MMB29K source (ROM/kernel)
MRA58N v0.16
Commits for OpenGapps compatibility (should also fix GMail issues, etc.)
MRA58N v0.15
No more AdAway as system app
MRA58N ROM and kernel
Busybox static included
MRA58K v0.12
SuperSU working now v2.52
AdAway working now v3.1
Stock sounds
Re-enabled gesture typing in AOSP keyboard - not sure if I will keep this setting
Allow unknown sources by default
Extras/Additions:
Other kernels
FIRE-ICE @USBhost http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451
NaHCO3 @xiaolvmu http://forum.xda-developers.com/nexus-9/orig-development/kernel-s-nexus-9-kernel-t3168833
ElementalX @flar2 http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
Apps
AdAway 3.1 (55) built 2015/11/13 (attached to this post)
Keyboard FC
Well I tried the BaNkS-Dynamic-GApps-5.x.x-9-22-15 and I get setup wizard BUT keyboard FCs... Stay tuned all! Look for a v0.11 soon...
@bshiznit Can you post the apk of AOSP keyboard built from the lastest sources?
Cata98 said:
@bshiznit Can you post the apk of AOSP keyboard built from the lastest sources?
Click to expand...
Click to collapse
Try the attached
bshiznit said:
Try the attached
Click to expand...
Click to collapse
v0.11 UP - no using the old 5.1.1 BaNks Dyanmic GApps does not work - still get the AOSP Keyboad FC, so stay tuned for a GApps we can use!
Can you add the support for the LTE model.
Envoyé de mon HTC One M9 en utilisant Tapatalk
Thanks for this ROM. It's working fine so far. I only have to flash bootloader and vendor, then boot in TWRP (2.8.7.0), format /data, flash ROM and it boots.
Any news about a working gapps package for this baby?
Gapps
jolinnard said:
Thanks for this ROM. It's working fine so far. I only have to flash bootloader and vendor, then boot in TWRP (2.8.7.0), format /data, flash ROM and it boots.
Any news about a working gapps package for this baby?
Click to expand...
Click to collapse
Did you see those in this link
Max128 said:
Can you add the support for the LTE model.
Envoyé de mon HTC One M9 en utilisant Tapatalk
Click to expand...
Click to collapse
Try it should work
GApps - still in work (esp. for Arm64)
BOSSPDA said:
Did you see those in this link
Click to expand...
Click to collapse
GApps:
http://files.oceighty.co/gapps/ - TRY benzo-gapps-M-20151006-signed.zip seems to hang on screen after connecting WiFi and hitting next - could try flashing after connecting to Wifi and rebooting after intial boot...
OR the other ones linked above Slim_mini_gapps.BETA.6.0.build.0.x-20151007.zip
BOSSPDA said:
Did you see those in this link
Click to expand...
Click to collapse
arm64 is disabled in Slim build. We have to wait:
https://github.com/dankoman30/slimlp_gapps/commit/1741f61a034d280e3b8613c84dfffe3fe950fbb7
bshiznit said:
GApps:
http://files.oceighty.co/gapps/ - TRY benzo-gapps-M-20151006-signed.zip
OR the other ones linked above Slim_mini_gapps.BETA.6.0.build.0.x-20151007.zip
Click to expand...
Click to collapse
benzo gapps are for ARM64?
Edit: ok, still in work
jolinnard said:
arm64 is disabled in Slim build. We have to wait:
https://github.com/dankoman30/slimlp_gapps/commit/1741f61a034d280e3b8613c84dfffe3fe950fbb7
benzo gapps are for ARM64?
Edit: ok, still in work
Click to expand...
Click to collapse
YUP no arm64 GApps (yet)...
What about the ones found here, http://opengapps.org/?
try to flash the vendor got an error...
hboot 3.44.1.0123
Those gapps don't support arm64 so they aren't usable for the Nexus 9. Just tried to use them and they failed.
---------- Post added at 12:07 AM ---------- Previous post was at 12:05 AM ----------
spotmark said:
What about the ones found here, http://opengapps.org/?
Click to expand...
Click to collapse
They don't have 6.0 gapps available yet which means they won't work either. We need ARM64 6.0 Gapps, specifically.
bshiznit said:
Vanilla-ish AOSP 6.0.0_r1 ROM (MRA58K) for WiFi Nexus 9
This was created by building from MRA58K source and adding SuperSU/(BusyBox coming ASAP)... Plus customizations (advanced power menu, ART optimizations) borrowed from @GROGG88 on Nexus 5 forum and @craigacgomez. Also WebView commits from @craigacgomez.
Featuring:
Vanilla AOSP 6.0.0_r1 (MRA58K) for WiFi Nexus 9
ROOT and permissive kernel based on https://android.googlesource.com/kernel/tegra/+/android-tegra-flounder-3.10-marshmallow with added features!
Still need to get busybox to compile and include it - meantime if you have a need try https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
BLEEDING still - may be bugs. My future Marshmallow builds will all be based on this table - https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
I included RIL this time building MRA58K so LTE (volantisg) should work WILL NEED A TESTER
UBERTC 5.2 arm64 compiled 3.10-marshmallow kernel
Decrypted device supported!
Can use f2fs for cache now! Thanks @xiaolvmu
Fast charge fix plus Force Fast Charge toggle added (Force Fast Charge off by default). Thanks @USBhost and @Captain_Throwback!
FSYNC toggle @franciscofranco
Use TricksterMod or Kernel Adiutor from Play Store to toggle Force Fast Charge/toggle FSYNC - Fast Charge will disable media sharing with your PC to get a faster charge on low amperage USB ports...
I/O schedulers added - SIO, deadline FIOPS and cfq - SIO to default
OTG native support ( @craigacgomez) - use your favorite file manager
Advanced TCP congestion - cubic still default
File system support added for NTFS, EXFAT and CIFS - thanks @Captain_Throwback - also EXT4 for EXT3 support to optimize size a bit more
SELINUX to permissive
SuperSU 2.50 ( @Chainfire)
AdAway 3.0.2 compiled and packed to signed apk by me
MiXplorer 5.4.6.BETA-B1509012 @HootanParsa (http://forum.xda-developers.com/showthread.php?t=1523691)
Reboot Menu with submenu for Reboot, Recovery and Bootloader respectively (from Nexus 5 forum THANKS @GROGG88)
Setup wizard crash fix (prefer Google WebView over AOSP fix from @craigacgomez) - I HOPE is still fixed awaitig GApps
MUST Flash a GApps (see Downloads) EVEN IF UPDATING from prior version(s)
***NOTE if using minimal GApps download any additional Google apps you might need that are missing from the Play Store!
Source:
https://github.com/bshiznit
Please use TWRP 2.8.7.0. Must be at bootloader 3.48.0.0135 and have flashed the latest MRA58K vendor image (links soon)!
Please wipe data and both caches (in TWRP got to Wipe --> "Swipe to Factory Reset") if not coming from my LMY48M ROM (I need to test) - otherwise please wipe
Downloads
Before flashing scroll down and read NOTES!
ROM
MEGA https://mega.nz/#!yNtnABCK!6hdSJ2um01BnbDC82bdxIYkkkE7pfDHQ1uTfgMvR628
Dev-Host http://d-h.st/g0NS
md5 - 3401acf14f0b43e9b4c289474dfd4815
3.48.0.0135 bootloader and MRA58K vendor.img
MEGA https://mega.nz/#!7ckxiRCJ!y-wtY8Sn4Q68IM2H6j8vjtIcwVPzyUlIupSe7IzmOU4
Dev-Host http://d-h.st/0zAT
md5 - cbe0fc8b60a30d84861c51e7b4c90286
Open GApps (PENDING) (closer to STOCK - choose ARM64 for Platform, 6.0 for Android then pick Stock for Variant) - http://opengapps.org/
Minimal Dynamic GApps (SITE DOWN at time of writing) (from http://fitsnugly.euroskank.com/?rom=banks&device=gapps)
MEGA https://mega.nz/#!aJNwAKjI!KFqN9LEWbhg2UvW6R_QuRKqMnoyZ7VXsuV17cAy0mw0
Dev-Host http://d-h.st/HPyP
md5 - 5f8c184424112a265f76681618b92f08
NOTE takes a WHILE (5-10 minutes) to boot up on first boot! ART is optimizing applications and it is set to EVERYTHING as we have sufficient system partition storage - for SPEED. There is no more dalvik-vm (no REALLY now - not even included in AOSP now)!
If you like it hit thanks! Donations are appreciated but never expected
I do this for a hobby and to keep my tablet running like new
Coming soon:
6.0 GApps links
Busybox inclusion
3.48.0.0135 bootloader and MRA58K vendor image dowloads
NOTES:
ALWAYS flash GApps even if updating from a prior AOSP 5.1.x/6.0 release! ALL ROMs format the /system partition as part of the installation process and this is where the GApps are kept!
BACKUP using TWRP and/or Titanium - save those files off the device to a USB stick external HDD or whatnot! Not responsible for lost data!
WIPE Data in recovery unless coming from another Vanilla AOSP 5.1.x ROM!
Be sure you are at bootloader 3.48.0.0135 and have flashed latest vendor images (link soon)
ONLY TESTED USING TWRP 2.8.7.0
MUST FLASH a GApps zip after the ROM for Play Store, etc.
If you like it consider donating! A nice big solid state hard drive will let me build faster and for more devices! (YAY my build box now has 411GB free even after all this developing - thanks to all who donated)
Thanks:
@Chainfire for SuperSU and keeping it updated!
@Snuzzo for github familiarization and being a great dev and resource!
@GROGG88 - for the power menu and other patches (even though it was from Nexus 5 it worked great)!!!!
@craigacgomez for reboot submenu and OTG commits @Captain_Throwback and @USBhost for fast charge and additional file system commits
@sykopompos for the sepolicy file and kernel instructions to allow root as well as the ART build.prop tweaks.
@scrosler great dev and good resource
Google for Android
AOSP for source!
Click to expand...
Click to collapse
do you have deodexed binaries for arm64 from volantis factory image? i can add to slim gapps if you do. i can't extract volantis factory image on my piece of crap work PC because it's over 2gb in size.
specifically, i'm looking for:
Code:
/system/app/FaceLock/*
/system/priv-app/HotwordEnrollment/*
/system/priv-app/PrebuiltGmsCore/*
/system/lib64/libfilterpack_facedetect.so
/system/lib64/libjni_latinime.so
/system/lib64/libjni_latinimegoogle.so
dankoman said:
do you have deodexed binaries for arm64 from volantis factory image? i can add to slim gapps if you do. i can't extract volantis factory image on my piece of crap work PC because it's over 2gb in size.
specifically, i'm looking for:
Code:
/system/app/FaceLock/*
/system/priv-app/HotwordEnrollment/*
/system/priv-app/PrebuiltGmsCore/*
/system/lib64/libfilterpack_facedetect.so
/system/lib64/libjni_latinime.so
/system/lib64/libjni_latinimegoogle.so
Click to expand...
Click to collapse
Sure one sec - API23 cross your fingers... I do have the SDK pieces in place.
@dankoman - kitchen doesn't seem to be deodexing... Any tips?
This rom is tested and working on SM-G930F/FD/K/L/S/W8 variant only! Do not try this on other variants without any backup!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why I did another rom for you on XDA? Many people asked me to do a basic version with some nice adaption because they actually really like stock. So along with my SuperStock Kernel I decided to make the SuperStock-Rom for a very stock near feeling. It features Odex apps and framework for max battery and performance! If you want something more customizable I recommend you to go for SuperMan-Rom and if you really like the grace UX features of the N7 there is also my HydraRom. I hope one of this roms fits your needs!
Rom Features:
V1.2 Marhsmallow:
- BPLB base
- Latest BPLB kernel, superstock kernel or superkernel
- November security patch
- SuperSU V2.79, Phh superuser r275 or magisk phh r266-2
- Magisk v9
- Xposed v86.2 or v87.1
- Stock emojis, ios emojis or android n emojis
- Rom is full ODEX for better speed
- Fixed googles overlay issue
- Gear VR working
- OTA support
- Sound mod included in aroma
- Aroma installer
- Debloat menu in aroma
- sd card rw
- system mounted as rw
- dm-verity disabled
- init.d support
- wakelock fix for google services
- csc features included
- Applock supported
- Advanced wifi settings
- private mode working (with permissive kernel)
V2.11.0 Nougat:
- DQJ1 base Nougat
- Latest DQJ1 kernels
- October security patch
- SuperSU V2.82 SR5, Phh superuser or MagiskSU
- Magisk v14.3
- Rom is full ODEX for better speed
- Fixed googles overlay issue
- Gear VR working
- Aroma installer
- Debloat menu in aroma
- sd card ro
- system mounted as rw
- dm-verity disabled
- init.d support
- csc features included
- Advanced wifi settings
- Auto model choose in script to flash right files
- Auto update BL/CP for F/FD model in you choose in aroma
- iOS emojis
- Sound Mod V19
Bugs:
- You tell me
Rom review by @shark jungle:
HOW-TO Install the rom:
0. Make sure you have ticked OEM Unlock in Developer settings!
1. Download latest bootloader and modem from here:
Bootloader/Modem
2. Download latest odin
3. Flash BL in BL tab and CP in CP tab of odin. Then follow the steps on this side until you get a working custom recovery: TWRP
4. If you are done with bootloader, modem and recovery we can move on, boot into twrp holding power, home button and volume up while phone is powered off
5. This will delete all your personal data! Click on wipe, format data and type "yes"
6. Wait until it is finished then click reboot, reboot to recovery
7. Now connect your phone to PC and copy the rom file inside your internal or external sd card
8. Flash the rom and wait until it is finished
9. Reboot your phone and enjoy !
Downloads:
V2.11.0 available on AndroidFileHost
Thread on Grifo Development
V1.2 on Androidfilehost (latest MM version)
SM-G930F/FD Modem and Bootloader
SM-G930W8 Modem and Bootloader
CSC Selection V2.3.5
Telegram:
If you wish to ask me some questions, join my telegram chat about SuperStock-Rom. You can also join if you just want to have a quick chat with me anyway just click on this link: Telegram invite link
Saying thanks:
If you enjoy and appreciate my work, I would be very pleased if you hit thanks on this post here, then I'm a very happy guy! If you say you want to do more about it, you can donate me with paypal using this link:
PayPal
I already say thanks to all of you! :highfive:
Credits:
- SuperR for his great unpack kitchen
- of course samsung for their firmware and source
- topjohnwu for his magisk and xposed systemless
- rovo for xposed
- chainfire for his root
- topjohn for xposed
- phh for superuser
- amarullz for aroma installer
- and last but not least the great XDA community for making me better and greater each day!
XDA:DevDB Information
SuperStock-Rom for herolte, ROM for the Samsung Galaxy S7
Contributors
Tkkg1994
Source Code: https://gitlab.com/Tkkg1994/SuperStock-Rom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Custom Recovery
Based On: Stock Based
Version Information
Status: Stable
Current Stable Version: V2.11.0
Stable Release Date: 2017-10-27
Created 2016-11-08
Last Updated 2017-10-27
Changelog
Changelog for MM versions (1.X):
SuperStock-Rom V1.0:
- Initial release!
SuperStock-Rom V1.1:
- Rebased on BPJG release
- November security patch
- Kernels updated with BPJE source drop and BPJG ramdisk
- Magisk phh updated to r266
- Phh updated to r266
SuperStock-Rom V1.2:
- Rebased on latest BPLB release
- December security patch
- Updated magisk to V9
- Updated Magisk apk to V2.5
- Updated busybox to V1.25
- Updated busybox app
- Updated SuperSU to V2.79
- Updated phh superuser to r275
- Updated phh apk to latest beta 10 material
- Updated phh magisk to r266-2
- Updated Xposed to 87.1 version
- Updated Xposed app
- Updated host files
- Added ablocker app as user app
- Added Aroma choice about default adblocker enabled/disabled
- Updated StockKernel to BPLB
- CSC updated to XEF BPL2
- SuperKernel updated to 1.9.6
- SuperStock updated to 1.6
Changelog for Nougat versions (2.X):
SuperStock-Rom V2.0 Beta:
- Based on latest G935FXXU1ZPKK base
- Android Nougat 7.0 update!
- november security patch
- Full nougat stock kernels included
- magisk updated to V9
- phh magisk updated to r266-2
- supersu updated to SR4 helios (all credits to @lyapota)
- removed csc selection as there is only 1 csc for now
- updated adblocker app
- csc features included as on V1.1
- kept ODEX as previous V1.1 version
- Busybox updated with a new app
- Many new things due to android N in general
- I must remove some debloat option as aroma only supports zips till 2 GB
- Model is kept G935F so you can enjoy all edge panels and edge features!
- of course no force encryption
- multi user support
- modem will be auto updated during rom flash! (If you have a F/FD model)
SuperStock-Rom V2.1 Beta:
- Rebased on latest ZPL3 base
- December security patches
- SuperSU update to SR5
- Added option to enable or disable adaway in aroma
- Updated adaway hostfile
- Updated all kernels to ZPL3 base
- Updated the included modems
- Private mode now working fine
- Some more bloatware removed
SuperStock-Rom V2.2 Beta:
- Fully rebased to latest ZPLH release
- Both edge and flat kernel updated to ZPLH base
- Updated modem to ZPHL release
- New: included auto update bootloader on F/FD models as well to ZPLH release
- CSC updated to ZPLH release
- SuperSU updated to V2.79
- Samsung Music app updated
- Phh superuser apk updated
- adblocker hostfile updated
- No more version choose in aroma, everything will be flashed automatically (depending on which s7 version you got)
SuperStock-Rom V2.3 Beta:
- Rebased on latest ZPLN release
- Updated CSC to ZPLN
- Updated kernels to ZPLN
- Updated Modems to ZPLN
- Updated SuperSU to official SR1 update (should fix all issues we had with supersu before)
SuperStock-Rom V2.4:
- Now based on latest official DPLT release!
- Stock kernel updated to official DPLT
- CSC updated to DPLT
- Bootloader updated to DPLT (and now selectable in aroma as well)
- Modem updated to DPLT (also selectable via aroma)
- CSC countries are selectable (those available in BTU csc)
- SuperStock-Kernel V2.0 included
- SuperKernel V2.0 included (busybox needs to be at /sbin for synapse!)
- init.d tweaks added
- build.prop tweaks added
- Recovery is now included and can be updated via aroma
- ios emoji added
- Sound mod added (needs testing)
- Viper4android added, magisk viper4android as well
- ARISE sound mod added
- Magisk updated to V10.2 (if you choose stock kernel it will flash V9, otherwise it won't boot)
- Magisk app updated
- Phh magisk updated to R2
- Phh app updated
- host file updated
- SuperSU updated to V2.79 SR3
- Busybox updated to 1.26.2 (with magisk support now!)
- Secret tab working in sbrowser (credits @mwilky)
- Private mode working fine on both kernel
- Aroma is most likely same as SuperMan (no more model choose, all handled in scripts)
- Backup/restore of aroma selections added
- AppLock added for N (csc feature) credits to @Repulsa
- All variants have now the proper model number (SM-G930F/K/L/S/W8 etc)
- Some other things I may forgot
SuperStock-Rom V2.5:
- Rebased on DQB7
- February security patch
- Updated included BL to DQB7 and modem to DQB1
- BTU multi csc included (DQB3 version)
- Updated all kernels with ramdisk to DQB7
- Magisk updated to V11.1 (no need for superuser apk anymore)
- Updated MagiskManager to V4.1
- Busybox updated
- Adblocker updated
- Sound mod updated to V19
- Camera mod added (V8.1)
- Arise sound mod removed (they got their own aroma installer now)
- All previous features included
SuperStock-Rom V2.6:
- Based on DQCG
- March Security patch
- Magisk Manager updated
- Bootloader/Modem updated to DQCG
- W8 Bootloader/Modem added
- Additional fonts added in aroma
- Knox added to choose in aroma
- New build.prop tweaks added
- CSC updated
- All kernels updated to 2.4.2 version
- Magisk updated to V11.6
- Many bloat apps added to choose from (like on SuperMan)
- Aroma updated to latest mods (like Superman)
SuperStock-Rom V2.7:
- Based on latest DQD2 firmware
- April security patch
- BL/CP both updated to DQD2
- SuperKernel/SuperStock-Kernel and stock kernel updated to DQD2
- Magisk updated to V12
- Phh root updated to r310
- Magisk Manager updated
- All extra apps (such as snapchat, telegram etc) updated
SuperStock-Rom V2.8:
- Rebased on DQEF base
- includes latest bootloader and modem in aroma
- updated included TWRP to 3.1.1
- updated kernels to v2.6 (with new linux and source)
- May security patch
- OTA is now choosable in aroma too
SuperStock-Rom V2.9.0:
- Updated base of the rom to most recent DQFM
- Updated all kernels to DQFM including ramdisk and latest kernels from earlier today
- Updated Magisk to V13.1
- Updated SuperSU to 2.82 SR1
- Updated included BL/CP of F/FD/W8 to most recent versions
- Includes June security patch
SuperStock-Rom V2.10.0:
- Updated base to DQHY
- Updated all included kernels to latest DQH8 base
- Updated Magisk to V14.0
- Updated SuperSU to 2.82 SR3
- Updated included BL/CP of F/FD/W8
- Includes August security patch
- Updated Samsung Fonts app
- Removed OTA update, this wasn't working anymore
- Removed viper4android due to problems with sound, please use ARISE or similar mods
- Updated busybox to most recent v1.27.2 version
- Added a new busybox to the selection
- Added some more apps into debloat options
SuperStock-Rom V2.11.0 FINAL:
- Updated to latest DQJ1 base
- Includes latest October security patch
- Fixes blueborne
- Updated all kernels to DQJ1
- Updated SuperSU to SR5
- Updated Magisk to latest V14.3
- Added Magisk Xposed V88.1 into aroma selection
- Added Oreo emojis into aroma selection
- Updated modded camera
- Updated included bootloader/modems
- Updated the adblocker host file
- Updated modded fonts app
- Fake system state to official
Useful posts and links
Odin:
Find all latest odin and samsung tools on this link: Samsung-Tools
In case you need help:
Try to take a look at my Q&A Thread where hopefully some general questions are already answered.
TWRP links:
TWRP S7 Thread
Official TWRP website for s7
Bootloader and Modems:
SM-G930F/FD BL and CP
SM-G930K BL and CP
SM-G930L BL and CP
SM-G930S BL and CP
SM-G930W8 BL and CP
Xposed Threads:
Wanam Xposed V87
Systemless Magisk Xposed V86.6
Official Xposed V87 (DOES NOT WORK ON SAMSUNG DEVICES) visit this website only for changelogs and infos from rovo!
Material Xposed Installer
General Xposed Discussion
Magisk related Threads:
Magisk V9
Magisk Discussion
How-To create a Magisk module
PHH magiks superuser
Magisk module collection
Root related Threads:
Sound Mod V18
How to encrypt on custom rom
Phh's superuser
Phh's hidesu
Phh's official apk
Phh's material APK
Stable SuperSU releases
Beta SuperSU releases
Chainfires suhide
Kernels Threads:
Kali Nethunter
TGP Kernel
SuperStock Kernel
Prometheus Kernel
SuperKernel
Voltaqe kernel
Roms made by me:
SuperMan-Rom which you are currently on its thread
HydraRom which is a full note 7 rom compatible with our s7.
SuperStock-Rom which is as close to stock as possible with some nice additions. Android 7.0 Nougat Beta is available for it!
Samsung Links:
Sammobile Website
Latest samsung apks
Samsung Opensource Center
Live samsung updates
Fast firmware downloads
Good Lock:
Latest Good Lock APK can always be found on Apk Mirror.
Thread about CSC:
Download latest CSC from CSC Selection V1.9
All CSC's ever released
How to donate:
Donation via normal PayPal
Donate via PayPal.me
Best StockROM experience. Running smooth with superstock kernel. Best I tried so far!
Will try this the upcoming week.
Sounds very promissing ty as always
Thanks ! I will be test ! I love rom custom with stock, just little modification :3
abe2912 said:
Best StockROM experience. Running smooth with superstock kernel. Best I tried so far!
Click to expand...
Click to collapse
Thank you
roba93 said:
Will try this the upcoming week.
Sounds very promissing ty as always
Click to expand...
Click to collapse
No problem
Drice81 said:
Thanks ! I will be test ! I love rom custom with stock, just little modification :3
Click to expand...
Click to collapse
Yeah then this is exactly for you
This is super. Best battery life. Thanks
Inviato dal mio SM-G930F utilizzando Tapatalk
Security patch date?
Thanks a lot
Holy S.... Nice dude. I downloading and testing this thing. Big Thanks man. This is what i whant
PopaStefanx said:
This is super. Best battery life. Thanks
Inviato dal mio SM-G930F utilizzando Tapatalk
Click to expand...
Click to collapse
Nice and no problem!
amtomio2004 said:
Security patch date?
Thanks a lot
Click to expand...
Click to collapse
October
Jazz2000 said:
Holy S.... Nice dude. I downloading and testing this thing. Big Thanks man. This is what i whant
Click to expand...
Click to collapse
Enjoy!
Sent from my SuperMan powered SM-G930F
Installed,maybe it is space for more debloating
king118 said:
Installed,maybe it is space for more debloating
Click to expand...
Click to collapse
If you send me a list of additional removable apps without breaking any features I am waiting
Tkkg1994 said:
If you send me a list of additional removable apps without breaking any features I am waiting
Click to expand...
Click to collapse
Hmm Voice Wake/S voice ,Weather,Edge Panel(maybe a option to install or not in aroma).Now the question is how many people use the Gear Vr on S7 in order to remove or not.
king118 said:
Hmm Voice Wake/S voice ,Weather,Edge Panel(maybe a option to install or not in aroma).Now the question is how many people use the Gear Vr on S7 in order to remove or not.
Click to expand...
Click to collapse
Everything is in aroma except edge panel. svoice, weahter and gear vr as well
Thanks Tkkg1994 for another awesome work altough i have a doubt,why the Nougat folder on the BT/CP folder?
pbls said:
Thanks Tkkg1994 for another awesome work altough i have a doubt,why the Nougat folder on the BT/CP folder?
Click to expand...
Click to collapse
Because I uploaded nougat BL and CP
Sent from my SuperMan powered SM-G930F
SuperStock-Rom V1.1:
- Rebased on BPJG release
- November security patch
- Kernels updated with BPJE source drop and BPJG ramdisk
- Magisk phh updated to r266
- Phh updated to r266
Download V1.1 (or through OTA)
Does this rom have rom control?
bax-gold said:
Does this rom have rom control?
Click to expand...
Click to collapse
No...
Sent from my SuperMan powered SM-G930F
NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. At the moment this means this build is optimized for oneplus3t - and it runs only on oneplus3t.In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps). Since LineageOS lacks a theme engine this rom comes with OMS patches applied and is Substratum ready.
NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty isn't void: we are on an oneplus device.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 14.1 builds for oneplus3t - it is not for oneplus3. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano (read this.)
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps bigger then opengapps-nano)
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the ROM below in the downloads section (or from a mirror; see posting #2)
If you have downloaded a build with "firmware" in it's name, the needed firmware is included and installed while flashing. If you have downloaded a build without "firmware" in it's name, you need to flash the needed firmware BEFORE flashing the rom. You'll find the firmware flashable zips near the end of this posting. New files are added on top of the list.
Download exactly Beans Dynamic Mini Gapps (Note that any other version of Google Apps are known to have wide spread side effects - see posting #4; section "gapps' known issues"
Install exactly this TWRP.
Reboot into recovery.
Backup your current ROM and make sure you have backups of your data you want to keep.
Flash firmware if not using a build with "firmware" in it's name.
Wipe system, data and cache. (Before flashing anything, make sure the system partition is NOT mounted: TWRP-home->mount->uncheck system)
Flash LineageOS
Flash Google Apps (see posting #4; section "gapps' known issues") If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery and flash a newer LineageOS zip. Settings, apps and even google apps should be preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/14.1/
Since my time is quite limited till end of October, the update frequency is reduced to 7 to 10 days.
Build 20180309
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
This is most propably the last NLOS-14.1 build. I want to say "Thanx" to all users. Please feel invited to to use NLOS-15.1!
EOL.
Changelog:
Sync to upstream: March Security Patch.
boeffla_wl_blocker: defconfig: enable wl_blocker. — nvertigo
wl_blocker: add more wakelocks to the default block list — Francisco Franco
boeffla_wl_blocker: update to wakelock blocker driver v1.1.0 — andip71
boeffla_wl_blocker: update to wakelock blocker driver v1.0.1 — andip71
boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0 — andip71
WG: squash WireGuard-0.0.20180304. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20180214
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
Changelog:
Sync to upstream: Feb. Security Patch
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180206
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
I have reintroduced lineageos Snpdragon Camera (Snap), because of it's new implemented QuickReader - the issue with crashes on one of the first ff-cammtaken pics is still present. Wiping system and reflashing BeansGapps-Mini-7.1.x-20170725.zip is highly recommended!
Changelog:
op3: Address SELiunx denials — dianlujitao
op3: Unbreak perfd — dianlujitao
Revert "Drop LineageOS/CAF SnapCam aka Snap." — nvertigo
qcacld-2.0: Update to LA.UM.5.5.r1-06700-8x96.0 — dianlujitao
Merge tag 'LA.UM.5.5.r1-06700-8x96.0' into cm-14.1 — dianlujitao
ANDROID: xattr: Pass EOPNOTSUPP to permission2 — Daniel Rosenberg
ANDROID: sdcardfs: Move default_normal to superblock — Daniel Rosenberg
ANDROID: sdcardfs: Fix missing break on default_normal — Daniel Rosenberg
f2fs: Reset to v4.14-rc1-3.18 — dianlujitao
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180131
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Mantainance: synced to los.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
P.S.: chagallwifi build is updated as well - f2fs for cache and data fixed.
Build 20180120
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Revert "Track our own version of android_vendor_codeaurora_telephony." — Nvertigo
Update WireGuard to 0.0.20180118.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20180116
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Xtra Fixes - https, version check & version 3 — Wyatt Riley
January security update.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
P.S.: chagallwifi build is updated as well - aptx enabled.
Happy flashing!
Build 20180109
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Some new fs, fs-crypt and sdcardfs patches has been merged upstream. Perhaps these also solve the remaining issues with bootloops, though I have only very little hope these will avoid the necessity of reformatting the user-data partition.
Changelog:
fscrypt: move to generic async completion — Gilad Ben-Yossef
crypto: introduce crypto wait for async op — Gilad Ben-Yossef
fscrypt: lock mutex before checking for bounce page pool — Eric Biggers
fscrypt: new helper function - fscrypt_prepare_setattr(
fscrypt: new helper function - fscrypt_prepare_lookup(
fscrypt: new helper function - fscrypt_prepare_rename(
fscrypt: new helper function - fscrypt_prepare_link(
fscrypt: new helper function - fscrypt_file_open(
fscrypt: new helper function - fscrypt_require_key(
fscrypt: remove unneeded empty fscrypt_operations structs — Eric Biggers
fscrypt: remove ->is_encrypted(
fscrypt: switch from ->is_encrypted(
fs, fscrypt: add an S_ENCRYPTED inode flag — Eric Biggers
fscrypt: clean up include file mess — Dave Chinner
fscrypt: fix dereference of NULL user_key_payload — Eric Biggers
fscrypt: make ->dummy_context(
ANDROID: sdcardfs: Add default_normal option — Daniel Rosenberg
ANDROID: sdcardfs: notify lower file of opens — Daniel Rosenberg
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
P.S.: chagallwifi build is updated as well.
Happy flashing!
Build 20180106
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
I've done some testing with toolchains: I couldn't find any advantage using Snapdragon llvm, so I decided to stay with laos stock clang. I also found that using a gcc-6 based cortex-a53 toolchain on the kernel (instead of 4.9) makes the resulting kernel a very little bit more bat friendly. But I did NOT found any advantage of UBERTC/Linaro compared to plain (no Linaro patches and enhancements) gcc-6 build for cortex-a53.
Considering those observations, I decided to use:
kernel: cortex-a53 optimized gcc-6.4.1 (crosstool-ng, config: https://bitbucket.org/nvertigo/aarc...og.bz2?at=master&fileviewer=file-view-default)
All other c- and c++-code in the rom: stock laos llvm/clang
Your milleage may vary, but to me this combination is CURRENTLY giving the best ballance of performance and bat life. Let me know your impressions.
Changelog:
Remove Snapdragon LLVM. — Nvertigo
Add aarch64-linux-android-6.4: stock gcc version 6.4.1 20171215 (crosstool-NG crosstool-ng-1.23.0-288-gadaa3a5d
Remove aarch64-linux-android-6.x. — Nvertigo
Remove aarch64-linux-android-5.x. — Nvertigo
Remove aarch64/aarch64-linux-android-4.9. — Nvertigo
Remove aarch64-linux-android-4.9-kernel. — Nvertigo
Fix derp in opting in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Opt in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Use GNU gcc 6.4.1 for kernel building. — nvertigo
gcc-6.4.1: disable unused-const-variable warnings. — nvertigo
gcc-6.4.1: remove unsed variable fsm_en. — nvertigo
gcc-6.4.1: fix a bunch of (misleading) indents. — nvertigo
bluetooth: hci_sock: Fix warning detected by gcc 5.3.1 — NewEraCracker
tfa9890: tfa_container: Fix warnings detected by gcc 5.3.1 — NewEraCracker
treewide: Fix code errors detected using Linaro GCC 6.3.1 — Sultan Alsawaf
treewide: Properly fix use of uninitialized variables — Sultan Alsawaf
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Build 20171230
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
mcpu: use cortex-a53 with stock clang/llvm. — nvertigo
Revert "msm: camerav2: isp: Reserve rdi ub based on image size" — nvertigo
Revert "msm: camera: Synchronize v4l2 subscribe and unsubscribe event in camera.c" — nvertigo
Revert "msm: camera: isp: Allocate kernel page and map to userspace" — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
May the source be with you and yours in 2018!
Build 20171223 (xmas-firmware)
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Firmware requirementsnhave not changed, but to avoid unneseccary hussles during Xmas I included the firmware (with nlos bootlogo) again for this build.
disable SDCLANG and UBERTC for now (to minimize any issues).
Bootlogo: add NLOS bootlogo. — nvertigo
net/wireguard: add wireguard importer — nvertigo
Revert "msm: mdss: Do not attempt to request TE irq again if already requested" — dianlujitao (laos/cm-14.1
op3: Regen defconfig — dianlujitao
ANDROID: ion: Fix uninitialized variable — Daniel Rosenberg
drivers: staging: Update qcacld-2.0 driver — Luca Stefani
Merge tag 'LA.UM.5.5.r1-06400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into cm-14.1 — dianlujitao
sepolicy: allow apps to stat processes. — nvertigo (nvertigo/nlos-14.1, github/nlos-14.1, nlos-14.1
sepolicy: allow cameraserver to search mpctl socket directories. — nvertigo
sepolicy: add a bunch of denials need for different apps. — nvertigo
sepolicy: allow hostapd to access diag_device. — nvertigo
gps: update to LA.UM.5.5.r1-06400-8x96.0. — nvertigo
Revert "IMS: fix derp: remove some test settings again." — nvertigo
sepolicy: allow time_daemon to connect to unix_stream_socket. — nvertigo
sepolicy: allow mediacodec to search mpctl. — nvertigo
sepolicy: allow system_server to use setsched. — nvertigo
init: set downmigrate after upmigrate. — nvertigo
init: remove some artefacts from eas. — nvertigo
oneplus3: Enable framework sched boost — Sultanxda
BoardConfig.mk: remove out-commented SDCLANG. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
Renamed blobs (for use with custom kernels build for unified roms)
NVertigo's UniBlob Archive
TWRP
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Google Apps:
Beans Dynamic Mini Gapps
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/cm-14.1 (If you want to build this rom yourself, consult the file named README)
Aytex, who made all of the banners on this post.
team-exynos5429 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
@m0d hipp¥ for mirroring.
@mad-murdock for first testings.
The microG Team
Nathan Chancellor for LineageOMS, especially for this wonderfull piece of software.
@joshuous for introducing and explaing EAS to me and making VoxPopuli public. Last and not least for running EAS-Project.
@RenderBroken for providing EAS patches for EAS-Project's LineageOS based kernel.
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
...and everybody I forgot.
Happy flashing!
I will be putting the latest mirror's of nvertigo67's rom on here.
Additional FilesOxygenOS - ob8 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob8-firmware.zip
OxygenOS - ob7 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob7-firmware.zip
OxygenOS - ob6 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob6-firmware.zip
OxygenOS - ob5 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob5-firmware.zip
OxygenOS - ob4 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob4-firmware.zip
4.0.3 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-4.0.3-firmware.zip
TWRP 3.0.4-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.0.4-1-oneplus3.img
TWRP 3.1.0-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.1.0-1-oneplus3t.img
Open Gapps Nano 01-20-2017 - http://x-null.net/xda/nvertigo67/Other/open_gapps-arm64-7.1-nano-20170120.zip
Newest will be on top
June 6 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170606-UNOFFICIAL-nvertigo-oneplus3t.zip
June 6 2017http://www.x-null.net/xda/nvertigo6...06-UNOFFICIAL-nvertigo-gps-test-oneplus3t.zip **GPS TEST**
June 2 2017http://www.x-null.net/xda/nvertigo6...02-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170524-UNOFFICIAL-nvertigo-oneplus3t.zip
May 18 2017http://www.x-null.net/xda/nvertigo6...18-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 15 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170515-UNOFFICIAL-nvertigo-oneplus3t.zip
May 9 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170509-UNOFFICIAL-nvertigo-oneplus3t.zip
May 3 2017http://www.x-null.net/xda/nvertigo6...03-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Apr 26 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip *Experimental with OMS*
Apr 22 2017http://www.x-null.net/xda/nvertigo6...NOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip *Experimental*
Apr 18 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170418-UNOFFICIAL-nvertigo-oneplus3t.zip
Apr 11 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 7 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170407-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 4 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170404-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 1 2017http://www.x-null.net/xda/nvertigo6...01-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 30 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170330-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 28 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170328-UNOFFICIAL-mad-murdock-oneplus3t.zip
Mar 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170324-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 20 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170320-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 16 2017http://www.x-null.net/xda/nvertigo6...16-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 12 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170312-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 7 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170307-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 4 2017http://www.x-null.net/xda/nvertigo6...04-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 1 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170301-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 25 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170225-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 24 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170224-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 18 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170218-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 14 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170214-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 10 2017http://www.x-null.net/xda/nvertigo6...10-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Feb 6 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170206-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!aYNkERIb!QyFzj6IZAchSL0TqIn-ZDIrsZulStkbDZi0RF1oyJcg - credit to @t-shock
Feb 3 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 1 2017http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170201-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!jRdB1aRZ!-QzqNBaP_7QWZPxpuFQz1X3a7IghVy21xLDqyTlJew8 - credit to @t-shock
3T only - why that?
Since the latest changes in init and overlay, I don't think this posting is true any longer.
I don't like to publish a rom for a device I have not my hands on. So this is still 3t-only.
I completely understand all devs doing unified builds. I completely understand it was so annoying, that oneplus launched 3T half a year after 3, and devs wanted to preserve their work, or don't want to buy just another device. So if you think unified builds are your way, I understand and appriciate that!
For me, on the other hand, it looks like this: I've come from bacon to 3t, I have no 3 and my personal policy is building only for devices I have my hands on. I like OOS - indeed for me it's one of the best stock roms I've ever seen - but it lacks some features I learned to love in cm times, like privacy, app-ops, automatic do not disturb rules and much more.
I lurked some time around in the threads, build OSS from source and tried to dig in the sources. I tried hard to understand the differences of 3 and 3t. What I found in most of the sources was @Sultanxda's and @Graraks patches to load different adreno firmware.
Then I pulled blobs from OOS-4 for 3t and ran diff against the onplus3 blobs from themuppets. I don't say they were completely different, but they differed in about 4/5th of the files (as you can see in this commit: https://github.com/nvertigo/proprie...mmit/17c7609f79167c02041736306b18f52bca5b9ac6). Then I compared the specs of 3 and 3t - surprise: they are different...
Let me give you an example: the battery is different. That means power_profile.xml has to be different for 3 and 3t, too. If you got traped by the hoax, that the 3t comes with a 3000 mAh battery read this.
So I decided to build a rom with all blobs beeing native and configuration optimized for 3t. To my surprise my first attempt ended in a build so smooth with all features I missed, that I fell in love instantly. So I spent even more time on this, added busybox (not as toybox' replacement, but just as binary in /system/xbin/busybox) and used native qcom SnapDragon llvm for CLANG and UBERTC/linaro for kernel.
At this point @mad-murdock tested the build. I wasn't sure about my own perception, because it was my own rom. He ensured me though, it was stable and smooth. So I was happy with the build.
I don't say it's not possible to achieve all this with an unified build. But I'm absolutely sure, that 3 and 3t differ in more aspects then graphic blobs. These differences need to be addressed in unified builds (RR seems to be a step ahead compared to laos). This is far behind my scope (and to stick to my personal policy to build only for devices I have hands on, I would need to get a 3 and a second sim), so here we are: LineageOS for 3t only.
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
Known Issues
General known issues
If you want to report an new issue provide logs. If you don't know what logcat is or how to deal with it this posting is for you.
The following stroked isaues may or may not be present on Snap - to avoid all Snap hazards, NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam:
camera: continuous shot not working select sports mode[/STRIKE]
camera: HDR on front camera just produces a green picture
camera: front camera in HAL1 mode: one of the first two or three shots, let the camera server crash - following shots are perfectly ok til next reboot.
Workarounds:
The ugly one: use OnePlusCamera or Snap and take pictures (mostly one to three) til camereserver crashes, wait 7 seconds and use your prefered HAL1 cam as usual.
The more elegant one: use a cam app that supports HAL3 (api2) like opencamera by @mdwh (recommended: it's opensource and free of charge - don't forget to donate, if you decide to use it on a regular basis) or one of the closed source apps.
camera: first still while taking a video is broken.
sRGB-Mode is not setable from Settings; workaround: https://forum.xda-developers.com/showpost.php?p=70799426&postcount=53You find sRGB as color mode in LiveDisplay
encrypting an unencrypted data partition is currently NOT working - no matter if ext4 or f2fs. Workaround: restore your oos nandroid, encrypt your phone by setting pin or password to something new, and tap on "secure phone on startup" (might not be the accurate phrase, but you know, what I mean when you see it.)
Gapps known issues
You can easily avoid all of this - and propably much more - if you stick to the recommended gapps package!
The notification slider isn't working.
webview is stuttering and lagging
first time setup can't be completed.
dialer is not working as expected
unpredictable behavior of UI
random (or not so random) fc's of system components (apps and/or services)
I did not flash the correct Google Apps version!
Some Google App versions overwrite critical system components, which leads up to all kind of random issues. One of the most obvious issues, is gapps preventing Lineage setup to start, and will instead guide you through the AOSP Setup Wizard. This will cause issues, amongst others the Alert Slider on the left side of the phone will not work. If you encounter this or other problems, you need to wipe system, data and caches, before you reflash the ROM and the suggested version of Google Apps linked in the download section of OP. After initial setup, the google apps will update via playstore so don't worry about that. With this package installed, you can install all your missing gapps from playstore. The great advantage is, that the added gapps from playstore will be installed as user-apps and therefore won't mess up your system.
HOWTO: build this rom from source
See the README in
https://github.com/nvertigo/local_manifest
UPDATED: Camera Mods
To give the user more freedom of choice, OnePlusCamera and onePlus Gallery are removed from the rom. In this posting I provide additionally installable apks, to allow the user to install them as any other apk.
@kxzxx's mod (use to get the same cam setup we use for four months - callbacks removed):
https://drive.google.com/open?id=0B_f72wz8rwc6SV9VTXRXMVdfeFk
This should work on all laos based roms. Recommended, if you want the very same setup as before.
Update Version 1.5.0 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6dEpHUGVlQ2hYY28/view?usp=drivesdk
Plain stock OOS gallery - op3/t (dng support):
https://drive.google.com/file/d/0B_f72wz8rwc6QWNWUDhpQWhJa3M/view?usp=drivesdk
This should work on any rom without OnePlusGallery not installed.
Update Version 1.8.4 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6S2VkV1VsaHNNYzA/view?usp=drivesdk
Some candy:
Plain stock OOS 4.5.x cam - op5 (sometimes glitchy, flash not working reliable - raw working [set iso and shutter manually in pro-mode]):
https://drive.google.com/file/d/0B_f72wz8rwc6UzBoUlNhT0NabWs/view?usp=drivesdk
Outdated and obsoleted - just for reference: If you want to check this out on our current rom, needs to remove OnePlusCamera&Gallery first. Flash this in recovery:
https://drive.google.com/file/d/0B_f72wz8rwc6b2xUSUZQMXNuck0/view?usp=drivesdk
@homebuilders and all interessted people:
This is neither a HOWTO, nor a script (op3t/op5 is hardcoded, because I havn't parsed arguments), but gives at least an impression on what is needed to make a other roms system app an user installable app. As you can see, I sign the apk with laos test keys. The key does not really matter, as long as the apk is signed at all.
Code:
cat build.sh
#!/bin/bash
S1="-decompiled"
S2="-unaligned-unsigend.apk"
S3="-unaligned.apk"
S4="-v1.4.0-op3-nvertigo.apk"
for i in $*; do
apktool d -f -v -t oxy -o $i$S1 $i.apk
cp -av lib $i$S1
apktool b -f -o $i$S2 $i$S1
../.signing/sign.sh $i$S2 $i$S3
zipalign -f -v 8 $i$S3 $i$S4
done
cat sign.sh
#!/bin/bash
java -Xmx2048m -Djava.library.path=/mnt/export/data/src/cm14/out/host/linux-x86/lib64 -jar /mnt/export/data/src/cm14/out/host/linux-x86/framework/signapk.jar -w /mnt/export/data/src/cm14/build/target/product/security/testkey.x509.pem /mnt/export/data/src/cm14/build/target/product/security/testkey.pk8 $1 $2
@kxzxxx: if you still read here and if you have plenty of (spare-)time, would you be so awesome to look into op5 cam for callbacks on flash? I tried based on op3 cam, but failed. No need to hurry. Thanx in advance.
You should also checkout these:
MI5 camera mods (by @Arnova8G2): https://forum.xda-developers.com/mi-5/themes/app-collection-camera-modded-t3591177
OxygenOS Camera Mod (by @siankatabg): https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
Pixel Google Camera: https://www.xda-developers.com/google-camera-hdr-ported/
nvertigo67 said:
Since my time is quite limited till end of October, @mad-murdock is providing you with new builds.
Click to expand...
Click to collapse
I build these ROMs from source for quiet a while for myself. So I am the build slave or OP now. I use nvertigo's sources unchanged. Using the 141-work branch - in case you want to build yourself.
Mirror: posting #2. I assume @m0d hipp¥ will update it like usual.
Build 20170522
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I am a bit confused about changes. This part will be updated soonish.
Updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 7 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 7 firmware first. It was included for users having flashed lineage-14.1-20170518-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170522-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 4f6208f56b4a1fce39a34830f03ec294
Mirror: posting #2
Happy flashing!
Experimental Build 20170426
This is an updated experimental build with OMS. See nvertigo's post of last build for details.
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I don't have changes. Shame on me. Rebooted Windows for gaming.
Of course updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 5 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 5 firmware first. It was included for users having flashed lineage-14.1-20170422-UNOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip
MD5: 8aa8df7ed35999ec47c8ea23d659f78e
Mirror: posting #2
Happy flashing!
Build 20170411
It's that time again to update your ROM. No side-effect reported from last test-build, so we consider it stable.
Changelog
No changes, except updated to latest LaOS sources
Note on firmware: This build requires OOS beta 4 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 4 firmware first. It was included for users having flashed lineage-14.1-20170401-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 6b76cd3366c9beb3df1aa30d6a8deb2a
Mirror: posting #2
Happy flashing!
Thanks!!
your rom is best!!
Thanks guy ! Great
Great to see you started your own thread afterall. Going to flash this today, also because @mad-murdock approves this rom so much . Can't wait!
edit: found a small typo in the instructions. Check the year @nvertigo67 :
"Install the Google Apps addon package (Optional. Use opengapps nano package from 20160120)"
Update: Wipe before you install.
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
Just flashed your Rom. Fluent and feels natural! Thanks Developer
Glad to see you posting a thread on XDA
mad-murdock said:
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
Click to expand...
Click to collapse
I like experimenting, I like dirty flashing, I like custom kernels (indeed I'd love to see Boeffla cm/laos-14.1 kernel) and I want to encourage everybody to home-build, experiment, dirty flash, try mods, kernels or what ever: he, who never bricked an android device, has not flashed hard enough.
The only problem with that is support: I can't test any combination, reproduce issues and so on. Also if everybody reports on his very own combination, the thread becomes unreadable/unundestandeble.
So I kindly ask you to try whatever you want; but if reporting an issue, stick to OP rules, please.
HOWTO: build this rom yourself
The "homegrow"-howto is here in the file named README.
nvertigo67 said:
break for me now.
Click to expand...
Click to collapse
Well deserved. Take care.
Has anyone installed this ROM after formatting system and cache to F2FS?
System and cache as f2fs is rare. No idea which Roms support this. I would say, just try, if it won't work, format system and cache. It's no extra effort.
Just make sure not to reboot recovery while system is blank, since TWRP pulls crypto lib from system
nvertigo67 said:
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
Click to expand...
Click to collapse
Hi. I like the way, that you chose. Hope you will doing it in future. Like and you, I came from oneplus one.
Btw. What about sRGB mode? Is it here ? I'm hate oversaturated colors. After opo it's looks so ****ty..
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
hassan_1000 said:
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
Click to expand...
Click to collapse
it depends on how many apps you had installed. still, 15 minutes sounds pretty long. did you dirty flash without wiping? if so, you should probably go and wipe now.
CRUEL KERNEL S10 V2.3
The development moved to this thread. From V3 kernel supports multiple devices.
Introduction
This kernel is based on BTA8 samsung sources. Only G973F device for now. It is possible to use it on BSKO, BSL4, BTA8 firmware. All sources are open on GitHub.
Continuous integration with GitHub Actions is set up. This means you can customize the kernel from browser and build the version suitable for you without leaving the browser (see сustomization section).
Features
Customizable build with config presets
Only part of samsung security features disabled (DEFEX, Process Authentification, root restrictions)
Switchable SELinux (by default it's locked in "always enforcing" mode in samsung sources)
Built-in in Magisk
Wireguard for VPN
CIFS for SMB
Iptables TTL and HL editing modules for bypassing tethering restrictions
Build commands (configuration presets) used for V2.3 kernel:
Code:
$ ./build mkimg name=CRUEL-V2.3-BTA8 +magisk +nohardening +wireguard +ttl +cifs
$ ./build mkimg name=CRUEL-V2.3-BTA8-CANARY +magisk+canary +nohardening +wireguard +ttl +cifs
Installation Instructions
First of all, TWRP Recovery + multidisabler should be installed in all cases. This is a preliminary step. Backup your existing kernel. You will be able to restore it in TWRP Recovery in case of any problems.
Dowload an *.img file and
With TWRP: Reboot to recovery. Install > Install Image > CruelKernel.img > BOOT.
With Heimdall: Reboot to Dowload mode.
Code:
sudo heimdall flash --BOOT CruelKernel.img
With FK Kernel Manager: Flasher > Manual Flasher.
ChangeLog
V1 is based on BSKO sources and was privately used. You can find V1 by the link.
V2 is based on BTA8 sources. nohardening, nohardening2, cifs configuration presets added.
V2.1 is for internal use only (testing release) +nohardening preset activated by default
V2.2
Canary Magisk updated to 20305 version
MALI_KUTF kernel driver removed (it's required only for kernel developers)
Pin code problem fix (thanks geiti94)
+nohardening (disable samsung protections)
V2.3
Canary Magisk updated to 20306 version
Small fixes for image format
Downloads
CruelKernel-G973F-BTA8-v2.3
CruelKernel-G973F-BTA8-v2.3-CANARY
Sources
How to customize the kernel build
It's possible to customize the kernel and build it from the browser. First of all, create and account on GitHub. Next, fork this repository. Switch to the "Actions" tab and activate GitHub Actions. At this step you've got your own copy of the sources and you can build it with GitHub Actions. You need to open github actions configuration file (.github/workflows/main.yml) and edit it from the browser. For example, to alter the kernel configuration you need to edit lines:
Code:
- name: Kernel Configure
run: |
./build config name=CRUEL-V2-BTA8
+magisk
+ttl
+wireguard
+cifs
You can change the name of the kernel by replacing name=CRUEL-V2-BTA8 with, for example, name=my_own_kernel. You can remove wireguard from the kernel if you don't need it by changing "+" to "-" or by removing the "+wireguard" line and "" on the previous line.
Available configuration presets can be found at kernel/configs folder. Only the *.conf files prefixed with "cruel" are meaningful. For example:
magisk - integrates magisk into the kernel. This allows to have root without booting from recovery. Enabled by default.
magisk+canary - integrates canary magisk into the kernel.
ttl - adds iptables filters for altering ttl values of network packets. This helps to bypass tethering blocking in mobile networks.
wireguard - adds wireguard VPN module to the kernel.
cifs - adds CIFS (SMB) support.
nohardening - removes Samsung kernel self-protection mechanisms. Potentially can increase the kernel performance. You can enable this config if you face rooting or some other kind of restrictions. Other kernels usually use settings from this config by default. It's safe to enable this config, it just makes your system less secure.
nohardening2 - removes Android kernel self-protection mechanisms. Potentially can increase the kernel performance. Don't use it if you don't know what you are doing. Almost completely disables kernel self-protection. Very insecure.
nodebug - remove debugging information from the kernel.
300hz - increases kernel clock rate from 250hz to 300hz. Potentially can decrease response time. Disabled by default, untested.
1000hz - increases kernel clock rate from 250hz to 1000hz. Potentially can decrease response time. Disabled by default, untested.
For example, you can alter default configuration to something like:
Code:
- name: Kernel Configure
run: |
./build config name=CruelCanary
+magisk+canary
+wireguard
+nohardening
After editing the configuration in the browser, save it and commit. Next, you need to switch to the "Actions" tab. At this step you will find that GitHub starts to build the kernel. You need to wait about 25-30 mins while github builds the kernel. If the build is successfully finished, you will find your boot.img in the Artifacts section. Download it, unzip and flash.
To keep your version of the sources in sync with main tree (following updates), please look at this tutorial.
Support
This thread. Feature requests accepted.
Telegram (testing and intermediate releases).
GitHub Pull Requests if you want to contribute.
Credits
Samsung for kernel sources
topjohnwu for Magisk
geiti94 for showing that it's possible to built-in Magisk into the kernel. Initially I experimented with ASIG kernel, but ASIG+Magisk on ASIG firmware just stucks on boot with an SELinux initialization problem. At that time I doubted that built-in Magisk will work.
geiti94 for his help and advices
franciscofranco for FK Kernel Manager
XDA:DevDB Information
CRUEL KERNEL S10 , Kernel for the Samsung Galaxy S10
Contributors
evdenis, evdenis
Source Code: https://github.com/CruelKernel/exynos9820-beyond1lte
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: v2.3
Stable Release Date: 2020-02-12
Created 2020-02-10
Last Updated 2020-03-16
Reserved
How to build the kernel locally on your PC
This instruction assumes that you are using Linux. Install: mkbootimg, heimdall (if you want to flash the kernel with it).
Next:
Code:
$ git clone https://github.com/CruelKernel/exynos9820-beyond1lte
$ cd exynos9820-beyond1lte
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout samsung-g973f-bta8-cruel
# Install compilers
$ git submodule update --init --recursive
# Compile (install mkbootimg first)
$ ./build mkimg name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img
# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash
# Or in a single command (compilation with flashing).
# ./build flash name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening
Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f
gillim74 said:
Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f
Click to expand...
Click to collapse
What ROM are you using? I tested it mostly on samsung BTA8 firmware.
evdenis said:
What ROM are you using? I tested it mostly on samsung BTA8 firmware.
Click to expand...
Click to collapse
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first
gillim74 said:
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first
Click to expand...
Click to collapse
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.
evdenis said:
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.
Click to expand...
Click to collapse
Same thing with version 1.could it be the twrp im using?
gillim74 said:
Same thing with version 1.could it be the twrp im using?
Click to expand...
Click to collapse
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.
It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.
evdenis said:
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.
Click to expand...
Click to collapse
Data wipe or format data
gillim74 said:
Data wipe or format data
Click to expand...
Click to collapse
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!
hello installation successfully the nikel kernel market for now
evdenis said:
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!
Click to expand...
Click to collapse
Worked with data wipe
evdenis said:
It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.
Click to expand...
Click to collapse
write me on telegram so i can say you why all get the pin code problem so you can fix it
Does this work with BSL7? Or know of kernel that will. Need my su permission to work
Paulturn84 said:
Does this work with BSL7? Or know of kernel that will. Need my su permission to work
Click to expand...
Click to collapse
Hi, no it will not work on BSL7. This kernel is for S10 (G973F) device. This device has only BSL6 firmware. BSL7 is for other devices. Try to look at nemesis kernel.
Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?
vomad said:
Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?
Click to expand...
Click to collapse
Download: https://cruelkernel.org/release/special/CruelKernel-G973F-ASJG-v1.1-LOS.img
This version is based on Android 9 (ASJG) sources and should work on ASIG firmwares. I've included some patches from ivanmeler LOS tree specifically for LOS. Features: Magisk v20.3, wireguard, ttl modules and cifs. Not tested
will he s10+ every be supported with this kernel?