Related
This project has been discontinued. See https://github.com/chenxiaolong/DualBootPatcher/blob/master/README.md for more details.
I'm proud to present the first dual boot project for the Qualcomm-based Samsung Galaxy S4! This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here: https://gist.github.com/chenxiaolong/3f3fb485cbd0cb77c4281941433ec54d
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Donations:
Donations are not required, but are greatly appreciated Donators will have their names listed in a nice big font on this post and will also be listed in the README file of the patcher.
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy S 4
Contributors
chenxiaolong
Version Information
Status: Testing
Created 2013-09-17
Last Updated 2014-07-29
XDA:DevDB Information
[DISCONTINUED] Dual Boot Patcher, Tool/Utility for the Samsung Galaxy S4
Contributors
chenxiaolong
Source Code: https://github.com/chenxiaolong
Version Information
Status: Testing
Created 2013-09-17
Last Updated 2019-05-17
Reserved
EDIT: Funny how people are thanking this reserved post
Reserved
Changelog:
Version 8.0.0
See http://forum.xda-developers.com/showpost.php?p=54487957&postcount=3589
Version 7.0.0
See http://forum.xda-developers.com/showpost.php?p=53360600&postcount=2901
Version 6.0.0
See http://forum.xda-developers.com/showpost.php?p=53109676&postcount=2828
Version 5.0.2
Fix bug in regex that may cause "errors=remount" to become "errwrs=remount" for my noobdev ROM leading the init binary to fail
Version 5.0.1
Fix issue where the mount script would not be executed in the init scripts of ktoonsez's kernels
falcon is the Moto G, not the Moto X
Version 5.0.0
Please see http://forum.xda-developers.com/showpost.php?p=52864036&postcount=2717
Version 4.1.3
Add support for EHNDROIX
Add support for WanamLite
Sort ramdisks and presets in GUI
Version 4.1.2
Add support for Echoe v20
Version 4.1.1
Add support for Echoe v18
Version 4.1.0
See here: http://forum.xda-developers.com/showpost.php?p=51482274&postcount=2503
Version 4.0.4
Update to version 1.7.28-2 of the cygwin library (for Windows)
Add support for OctOS
Add support for NamelessROM
Add support for Tquetski's MIUI
Automatically comment out check_icd in init.rc of TouchWiz 4.4 ramdisks (initial work to make stock init binary dual-boot capable)
Version 4.0.2
Remove generic boot.img support. Use the GUI patcher or patch-ramdisk script instead.
Add support for patching unsupported boot.lok files by unifying the file type detection code in the CLI and GUI programs
Add support for BlackBox 2.2
Add support for Echoe v14, 14.1 (untested)
Add support for jamal2367's Google Edition version R1.1 final
Add support for jamal2367's old Android 4.2.2 build
Add support for LiquidSmooth Kit Kat
Add support for AOSB
Add support for Bobcat Google Edition
Add support for SHOstock (TW4.4 tested)
Fix bug where the newly flashed kernel for devices needing loki is not saved properly
Fix modem partition mounting in TouchWiz 4.4 ROMs -- Fixes unknown baseband bug
Version 4.0.0
Too huge to list here
See my post for this release: http://forum.xda-developers.com/showpost.php?p=49645612&postcount=1904
Version 3.2.2
Added support for:
Carbon's Kit Kat ROM
Omnifarious's ROM
Kangakat
BAM-Android
Infamous Google Edition
Echoe Google Edition
Echoe TouchWiz
Official MIUI (TouchWiz-based)
Moto X's optimized bionic and dalvik libraries installer
Version 3.2.1
Fixes this error when a zip is unsupported:
Code:
AttributeError: 'NoneType' object has no attribute 'configs'
Add support for VirginROM (4.4 Kit Kat)
Add support for Dandroid (4.4 Kit Kat)
Add support for faux's Google Edition 4.4 jgedlte kernel
Add support for Gummy's Google Apps package
Version 3.2.0
Google Edition ROMs have the ugliest ramdisk by far (err...I mean Google Edition 4.4 ROMs will now boot)
chmod.exe from Cygwin's coreutils in now included in the Windows build so the patcher can set the necessary permissions on the init binary in Google Edition 4.4 ROMs
Disable SELinux by default globally
Fix mediaserver crash caused by the removal of /system/etc/snd_soc_msm/snd_soc_msm_2x_Fusion3_auxpcm in jamal2367's Google Edition 4.4 ROM
Version 3.1.1
Add support for Ktoonsez's Google Edition 4.4 kernel
Add support for Hell(y?)kat
Version 3.1.0
Add support for multi-boot patching in the Android GUI
Version 3.0.1
Update SuperSU patch to support version 1.80
Switch to CyanogenMod 11's mkbootimg and unpackbootimg sources
Add support for Google Edition 4.4 ROMs (ie. stop trying to patch the missing MSM8960_lpm.rc in the ramdisk)
Hack to allow the file chooser in Android 4.4 Kit Kat to work properly (in the Android version of the patcher)
Version 3.0.0
Separate many functions into common.py to make patchinfo files simpler
Set compile target for the Android GUI to Kit Kat (API 19)
Add support for debug builds of the Android GUI so I don't have to sign test builds
Add support for removing those pesky device check asserts
Add support for using multiple patches (can combine auto-patcher with manual patch)
Fix broken patch generator in Windows (hopefully, we won't need it anymore though)
Removed by default for HellyBean
Add auto-patcher
Searches through updater script to find mount, unmount, format, and delete lines and replaces them with the multi-boot equivalent.
Finds line that flashes the kernel and inserts line that takes a backup and stores it in the appropriate place for the dual boot switcher
All partitions will always be unmounted after installation so the phone is not in a weird state when flashing the next zip.
Auto-patched ROMs
GoldenEye
CyanogenMod
HellyBean
PAC-Man
ProBAM
AOKP
IOKP
AOSP
SlimBean
Paranoid Android
AICP
Carbon
JellyBeer
Omni
Gummy
Vanir
Dirty Unicorns
jamal2367's Google Edition
Ktoonsez AOSP, TouchWiz, and Google Edition kernels
Faux kernel
Ausdim kernel
Adam kernel
Infamous kernel
Triforce ROM
Paranoid Android Google Apps
BaNkS' Google Apps
CyanogenMod's Google Apps
doomed151 Google Apps
SlimBean Google Apps (standard and aroma)
task650's AOKP Google Apps
MIUI's Google Apps
MIUI ROM
Foxhound
HTC Sense 5 port
MaKTaiL's Google Edition
Kangabean
Triple boot! (and quadruple and quintuple and ...)
Any auto-patched ROM is automatically supported
Requires version 2.0.0 of the Dual Boot Switcher app
Dual Boot Switcher supports up to 10 ROMs in addition to the primary and secondary
Patcher supports 3 ROMs in addition to the primary and secondary (unless someone wants more)
The Android GUI only supports dual booting for now
Partition configuration (where things are installed): https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/partitionconfigs.py
Introduced a new dualboot.sh script that keeps track of what has and hasn't been mounted
Terribly written updater-scripts aren't a problem anymore
Note: using the script outside of the patcher will cause the ROM to be installed as secondary
Note: I don't want to rewrite SELinux rules and compile a modified version of vold, so for now, the target /system must be on a different physical partition than the target /cache. Other dualboot solutions have worked around this by installing the ROM files to a loop mounted ext4 filesystem image
Installing ROMs to /data should work in theory, but will not be supported
What else?
Version 2.5.3
Catch exception when file cannot be extracted
Add support for loki'd ChronicKernel
Version 2.5.2
Add support for OmniROM's Kit Kat ramdisks
Add support for Paranoid Android 4.4 Google Apps
Fix syntax error in scripts/gendiff.py
Version 2.5.1
unlokibootimg: struct can convert little-endian bytes to integers in Python 3.0 and Python 3.1 too
Don't use backslashes for filenames when generating patches from Windows
Add rushi.1986's patches for GoldenEye AT&T: http://forum.xda-developers.com/showpost.
php?p=46950654&postcount=801
Update Sample.py for bootimg variable
Add support for Ktoonsez's non-AOSP kernels
Version 2.5
Add support for extracted loki'd boot images: https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/unlokibootimg.py
Add support for Loki'd ktoonsez's AOSP 4.3 kernels
Fix crash when script is run with Python 2 due to the code trying to encode a "UTF-8" string as "UTF-8"
Flush stdout when printing status messages because Python 2's print() doesn't do that automatically
Fix general patch for Kangabean and enable Loki ramdisk patching for it
Version 2.4.3
Add support for IOKP
Version 2.4.2
Use custom-compiled tar to fix extraction on ROMs that don't have tar with xz support
Fix status messages in patcher so the app doesn't appear to pause with no activity
Clean up app cache as soon as it's not needed anymore
Add support for GoldenEye (TouchWiz 4.3) for T-Mobile
Version 2.4.1
Add support for loki'd Slim Bean
Version 2.4
Switch to GNU patch because busybox's patch can't handle fuzz. There's no way in the world we could ever have 100% perfect patches, so busybox is not an option.
Version 2.3
New Android app for patching files directly on the phone
Version 2.1
Add script for generating patches
Version 2.0
Add support for automatic ramdisk patching https://github.com/chenxiaolong/DualBootPatcher/commit/c8b63aa32ec0fc1c88b28ef76e335167c1e2f47e
Version 1.18.1
Add LiquidSmooth ramdisk
Add support for LiquidSmooth
Version 1.18
Add munchy_cool's 64-bit OS X unpackbootimg and mkbootimg binaries
Add support for OS X
Version 1.17.5
Add support for Metaiiica's PAC-Man
Version 1.17.4
Fix regular expressions for HellyBean and AOSP
Version 1.17.3
Add rushi.1986's fix for the ramdisk replacement script: http://forum.xda-developers.com/showpost.php?p=46319181&postcount=458
Version 1.17.2
Add support for ProBAM
Version 1.17.1
Add support for HellyBean
Windows: Allow zip files to reside on a drive other separate from the patcher
replaceramdisk.py: Bug fix in variable name
Version 1.17
Add support for Vertigo's AOKP
Add generic AOKP ramdisk
Version 1.16.2
Add support for TriForceROM
Version 1.16.1
Add support for iNTriNsiC (20130806 version)
Version 1.16
Add support for Negalite
Version 1.15
Add support for geiti94's Sense 5 port
Version 1.14.2
Add support for Kangabean
Version 1.14.1
Add support for Paranoid Android Google Apps package
Version 1.14
Add support for Broodplank's AOSP
Add support for doom151's AOSP Google Apps package
Version 1.13
Add support for Evil UnWizzed
Version 1.12
Add support for ComaDose
Add support for JellyBeer
Add support for jamal2367's Google Edition ROM
Version 1.11
Fix critical bug in the repacking of boot.img that may cause secondary ROM to not boot (duplicate files w/same name in zip)
Version 1.10.1
Add support for AROMA Slim Bean Google Apps package
Version 1.10
Optimize patcher script so only one full zip read and one full zip write is required
Add support for BaNkS's Google Apps
Version 1.9
Add support for Carbon ROM
Add patched Carbon ramdisk
Version 1.8.1
Use 0 context diff for paranoidandroid.dualboot.patch so it can apply properly to AOSPA's updater-script
Version 1.8
Add support for FoxHound ROM
Add generic TouchWiz ramdisk
Update README with notice about free disk space
Bind mount /data/media during installation. It is bad practice for an updater-script to touch /data/media, but some ROMs do this, so we need to handle it
Add support for mounting secondary /cache in dual boot helper script
Update replaceramdisk.py to support version 1.7's change in ramdisk compression
Version 1.7
Rework compression of ramdisks (cuts down size of patcher from ~15 MB to ~6 MB): https://github.com/chenxiaolong/DualBootPatcher/commit/bf6cea2254bcfe346436ebb1618c1975a66b1bcc
Version 1.6.3
Add support for Adam kernel (UNTESTED)
Version 1.6.2
Add support for Ausdim kernel (UNTESTED)
Version 1.6.1
Add support for Slim Bean ROM
Version 1.6
Add new script for replacing the ramdisk in boot.img
Version 1.5
Add support for MIUI
Version 1.4.2
Add support for ParanoidAndroid
Version 1.4.1
Experimental Infamous kernel support (UNTESTED)
Version 1.4
Initial support for Google Edition ramdisks
Add support for MaKTaiL's Google Edition ROM
Version 1.3
Minor fixes in preparation for public release
Update README with supported files and convert line endings to rn (thanks Windows!)
Version 1.2.6
Add SuperSU support
Version 1.2.5
Add AOKP support
Version 1.2.4
Add ChronicKernel support
Version 1.2.3
Add support for Vertigo's PAC-Man
Version 1.2.2
Add support for CyanogenMod's Google Apps
Version 1.2.1
Add support for official CyanogenMod nightlies
Version 1.2
Add faux kernel support
Version 1.1
Add Windows support
Newly compiled mkbootimg.exe and unpackbootimg.exe to support Windows' separate text and binary file I/O modes
Add a portable, minimal version of Python 3 for Windows
Use newer GNU patch from MSYS for Windows
Version 1.0
Initial release (Linux only)
Supported kernels: ktoonsez AOSP 4.3
Awesome work!
Is it possible to add support for the google edition 4.3 ROMs?
For example
http://forum.xda-developers.com/showthread.php?t=2395030
Also, the loke-doki zip so that us att users can flash roms that are not lokied!
rushi.1986 said:
Awesome work!
Is it possible to add support for the google edition 4.3 ROMs?
For example
http://forum.xda-developers.com/showthread.php?t=2395030
Also, the loke-doki zip so that us att users can flash roms that are not lokied!
Click to expand...
Click to collapse
Thanks! I'll add support for the ROM you linked right now.
loki-doki actually doesn't need any patching
I wish we could patch the files from android Dx
_____________________________________
If I actually did help, how bout a Thanks
Could you also enable the patch for miui rom avail in the i9505 Android section. .
Sorry in mobile can't link you the thread
Sent from my SGH-M919 using Tapatalk 4 Beta
regarding this dual booting, is there any possibility that the /data partition can be shared across both roms?
Sent from my GT-I9505 using Tapatalk 2
hisname said:
regarding this dual booting, is there any possibility that the /data partition can be shared across both roms?
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
+1 this would be awesome
Sent from my Galaxy Nexus using Tapatalk 4
hisname said:
regarding this dual booting, is there any possibility that the /data partition can be shared across both roms?
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
chickentuna said:
+1 this would be awesome
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
It depends on what you mean by /data. Currently, the internal SD is shared. It's possible to share /data/app and /data/app-asec without too much trouble (so apps aren't downloaded twice). If you're looking to share /data/data (app settings), I don't think I'll implement that, as least not for all apps. I don't think it's a good idea to have to have a blacklist of apps that can't have their data shared, such as launchers.
I'm considering adding a new section to the dual boot switcher app so that you can choose which apps' data should be shared between the two ROMs
rushi.1986 said:
Awesome work!
Is it possible to add support for the google edition 4.3 ROMs?
For example
http://forum.xda-developers.com/showthread.php?t=2395030
Also, the loke-doki zip so that us att users can flash roms that are not lokied!
Click to expand...
Click to collapse
That Google Edition ROM is now supported
The GE ramdisk (which is actually written by Samsung) was a huge convoluted mess with lines duplicated everywhere. I finally got that done though, so it will only take a couple minutes to add support for other GE ROMs.
`SBR` said:
Could you also enable the patch for miui rom avail in the i9505 Android section. .
Sorry in mobile can't link you the thread
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sure, I'll do it as soon as I get out of school tomorrow
Hi chenxiaolong,
this looks promising. I am going to give it a try. Btw, could you add support for Infamous Kernel 2.0? That's the only kernel I have found so far which allows smooth dual camera on custom TW roms..
Thanks!
Thanks for this! However, can you please add support for Paranoid Android? Or is it supported? Would really love the features of it together with some TouchWiz features! Thanks again!
I would love to dual boot sense 5 and touchwiz when the Sense ROM is more stable
_____________________________________
If I actually did help, how bout a Thanks
im having trouble dual booting i got amegle rom as main but then i reboot into recovery after setting primary rom kernel i flash ur cm10 rom then wipe cache and flash dual gapp n then reboot unfortunaly my phone goes past splash screen then it just hangs on a black screen really unsure where im goin wrong
daddyspud said:
im having trouble dual booting i got amegle rom as main but then i reboot into recovery after setting primary rom kernel i flash ur cm10 rom then wipe cache and flash dual gapp n then reboot unfortunaly my phone goes past splash screen then it just hangs on a black screen really unsure where im goin wrong
Click to expand...
Click to collapse
After you set the primary kernel and before you flashed the secondary rom, did you flash the dual boot_enable.zip file from the helper section?
_____________________________________
If I actually did help, how bout a Thanks
i select primary rom then reboot to recovery enabled then reboot back to main rom then bk to recovery n install cm 10
edit :::: as when i select cm 10 rom it tells me that dual boot is enabled
edit x2 :::: dont matter all booted and working fine seems the latest cm10 from chenxiaolong dosent have a bootanimation hence the reason i just got a black screen
Has anyone done this yet on the ATT version. I saw a post about it earlier. I'm just curious if it works correctly without throwing an unofficial status or soft brick since the app is essentially switching out the kernel.
Edit: I went ahead and tried it out. Its working great thanks @chenxiaolong
chenxiaolong said:
It depends on what you mean by /data. Currently, the internal SD is shared. It's possible to share /data/app and /data/app-asec without too much trouble (so apps aren't downloaded twice). If you're looking to share /data/data (app settings), I don't think I'll implement that, as least not for all apps. I don't think it's a good idea to have to have a blacklist of apps that can't have their data shared, such as launchers.
I'm considering adding a new section to the dual boot switcher app so that you can choose which apps' data should be shared between the two ROMs
Click to expand...
Click to collapse
This would be awsome if you could include the same apps that you downloaded on one rom on the other...good job chenxiaolong youve done well with this
Sent from my GT-I9505 using XDA Premium 4 mobile app
I have been sharing my CM7/CM9/CM10/CM10.1/CM10.2-based builds for some time in several thread, which culminated in the MackayROM. I continue now with KK4.4 from where I was for JB4.3. MackayROM is based on CyanogenMod sources, with several performance enhancements.
About Cyanogen: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Disclaimer: I am 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.
If you run into errors, I may not be able to solve it!
If you know a solution to a problem, either upload it yourself to Gerrit Code Review or contact me through pm.
The ROM is based on Cyanogen sources with the following changes:
-Mackay Kernel:
-Set of cherries picked from gerrit (differing by the day)
-Some additional patches I did myself to the source code
Feature request are OK, but remember:
1. I try to stay close to stock
2. I will not include additional apps, unless they can be build from source
3. The time I spend on features depends on how much I like them myself
Although it is possible to enable ART, this is not advisable:
-Takes long to convert from Dalvik to ART on first boot
-Needs more RAM
-Can cause soft reboots
But off course, YMMV -> light users may have better luck
Changelog of 4.9.14 - 5-Nov-2014
-CM11.0 codebase of 3-Nov-2014
-TWRP updated to 2.8.1.0
Full changelog of 4.9.14 compared to stock CM11.0:
CM11.0 sources of 3-Nov-2014
Mackay kernel:
Separate kernel thread: http://forum.xda-developers.com/showthread.php?t=2532813
TWRP (2.8.1.0):
-Themed orange
-Run recovery-apps (zip files should be present in /system/mackay, launch them through advanced->run app)
Removed apps:
-VideoEditor & demo VideoFiles
vendor/cm:
-Adapt for custom MackayROM building (bootanimation, ROM&file name)
-Custom bootanimation (Thanks to Malcho)
vendor/samsung:
-Added scripts for Mackay Settings
hardware/samsung:
-F4k 720p patch for bigmem kernels
AriesParts (“Mackay Settings” in Settings menu):
Add mackay kernel settings options:
>WiFi PM mode selection
>BLX settings
>BLN activation
>Navbar selection
>Low RAM mode selection
For other projects (frameworks/base & Settings, check my github for the latest patches)
Coming from stock Samsung ROM/CM7:
-The safest way is to flash CM9 first and then flash Mackay ROM. Going directly from Samsung ROM/CM7 to Mackay ROM may lead to loosing IMEI.
Fresh install:
Can be flashed on top of any CyanogenMod build:
-Do a factory reset
-Flash ROM
-Flash gapps
-Reboot your phone
Update:
-Flash ROM
-Reboot your phone
(no wipes or other things needed, just flash & reboot)
-Custom kernels can be used only if specific for KK4.4
Credits:
-teamhacksung/pawitp for making CyanogenMod work on our ancient phone
-stratosk/DerTeufel/Mialwe for the inspiration I got from their kernels
-rootax for providing a high-speed server for high quality downloads
-Malcho for his kernel splash & bootanimation
Downloads:
Basketbuild
Google Apps
Nano Gapps
For those who want to theme it even further, Bejda made a Mackay splash screen!
http://forum.xda-developers.com/showthread.php?t=2214468
To download the same kernel, but then with voodoo colour, or with CWM:
Basketbuild
XDA:DevDB Information
[KK 4.4.4][ROM]Mackay ROM, ROM for the Samsung Galaxy S I9000
Contributors
kasper_h
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2013-11-16
Last Updated 2014-09-21
Reserved
10 seconds after posting this thread I notice something went wrong with the uploads. Please have a bit of patience, the links will be updated ASAP.
kasper_h said:
10 seconds after posting this thread I notice something went wrong with the uploads. Please have a bit of patience, the links will be updated ASAP.
Click to expand...
Click to collapse
Ok, Thansk for the rom. I will instal today. In it there is CWM or TWRP?
marcinowozniako said:
Ok, Thansk for the rom. I will instal today. In it there is CWM or TWRP?
Click to expand...
Click to collapse
Kernel is TWRP-only at the moment.
Download link on XDA fileserver has been restored. Download link on rootaxbox will take quite a bit more time, needs a full re-upload & uploadspeed is very slow ATM.
Oh.
When will Galaxy Vibrant get this, same device, but still, no 4.4 ROM
Good job
Galaxy3HELL said:
When will Galaxy Vibrant get this, same device, but still, no 4.4 ROM
Good job
Click to expand...
Click to collapse
I think this will come soon, but I won't work on that
kasper, you compiled cm11 by yourself or you got the sources from cm, because there is no cm11 build in get.cm site yet
limnaln said:
kasper, you compiled cm11 by yourself or you got the sources from cm, because there is no cm11 build in get.cm site yet
Click to expand...
Click to collapse
I always build these ROMs myself from CM sources + my own additions to CM sources, so no need for "official" CM11 builds to enable my own ROMs to be build.
kasper_h said:
I think this will come soon, but I won't work on that
Click to expand...
Click to collapse
Can I install your kernel on CM11?
marcinowozniako said:
Can I install your kernel on CM11?
Click to expand...
Click to collapse
I have no separetely flashable kernel yet...
this is awesome... was waiting for this.... one quick question though... can we use officail paranoid android gapps with this rom?
rajeshbabushrestha said:
this is awesome... was waiting for this.... one quick question though... can we use officail paranoid android gapps with this rom?
Click to expand...
Click to collapse
Yes, in principle every gapps KK4.4 package should work. However, I only tested the package which I linked in OP.
thank you for this:good:
kasper_h said:
Yes, in principle every gapps KK4.4 package should work. However, I only tested the package which I linked in OP.
Click to expand...
Click to collapse
Thanks for KK rom :good: :good:
OP's link to Gapps contains five different builds- some with ART compatibility. Is there a preferred one? ART works/tested, or better stick to delvik for a little while?
A few things I noticed:
- If I select Performance settings from Mackay app, Settings force closes.
- Orientation tile is buggy, sometimes it seems to work, sometimes not.
The ROM is very snappy, thank you very much for your work!
Kasper_h installed this rom and I have a bug. When I want to enable high-speed data connections settings crashes me the error: com.android.systemui and closing forces. Framework to overloads.
Thanks for the rom, There isnt any bug list?
Installed on CM11 and works fine.No forced closure and fast enough to be a test.
so no separate kernel 0.600
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and install a compatible recovery
3. Wipe data & cache partitions and flash firmware
4. Optional: install the Google Apps additional package
Known Issues
Everything shoud work
History
19: New cm build 20150209: latest code + fix keyboard height
18: New cm build 20141124
17: New cm build 20141104: latest code + allow physical keyboards fix + enable xpad in kernel
16: New cm build 20141031
15: New cm build 20141027
14: New cm build 20141025
13: New cm build 20141022
12: Back old boot from bonuzzz (freezes with native cm).
11: Fix virbate (big thanks for bonuzzz) - CyanogenMod 20141015.
10: Finally we (I and bonuzzz) made it. CyanogenMod 20141014, fully builded from sources, no more ports.
9: Merge with original CyanogenMod 20141010 + latest kernel from bonuzzz (cover now working, all working)
8: Merge with original CyanogenMod 20141008 SNAPSHOT-M11
7: Merge with original CyanogenMod 20141007 + back SPen functionality
6: Item 5 + bluetooth fix - finally it's fully work
5: Merge with original CyanogenMod 20141004 - lcd density changed from 320 to 270 - it's look more frendly.
You can play with density - edit ro.sf.lcd_density value in systembuild.prop
In stock - 320,
Now - 270,
Phisicaly - it's about 248, but it's too small to me
See attached screenshots with diff density.
4: Merge with original CyanogenMod 20141003
3: V2: MTP fix - big thanks for bonuzzz, he made new kernel with mtp fix
2: V1: Fix SPen in vertical mode
1: V0: initial version
Links
CyanogenMod Build:
19: New cm build 20150209: https://drive.google.com/file/d/0B-6nm7Jks0W5R2NVanBKTkZlcDA/view?usp=sharing
18: New cm build 20141124: https://drive.google.com/file/d/0B-6nm7Jks0W5QVRzQnBEaFZLRm8/view?usp=sharing
17: New cm build 20141104: https://drive.google.com/file/d/0B-6nm7Jks0W5TW4xTlhIR0RkTFE/view?usp=sharing
16: New cm build 20141031: https://drive.google.com/file/d/0B-6nm7Jks0W5eFFhSmhZTzBGODA/view?usp=sharing
15: New cm build 20141027: https://drive.google.com/file/d/0B-6nm7Jks0W5Vk5KcW9sU1RpM0k/view?usp=sharing
14: New cm build 20141025: https://drive.google.com/file/d/0B-6nm7Jks0W5a1JXczYxNDJ5RzA/view?usp=sharing
13: New cm build 20141022: https://drive.google.com/file/d/0B-6nm7Jks0W5QUtKLXFpRWxSVkU/view?usp=sharing
12: Back old boot from bonuzzz (freezes with native cm): https://drive.google.com/file/d/0B-6nm7Jks0W5NHktYUROOTVSNFU/view?usp=sharing
11: Fix vibrate - CyanogenMod 20141015: https://drive.google.com/file/d/0B-6nm7Jks0W5QU0wUHpNUGJqdk0/view?usp=sharing
10: CyanogenMod from sources (require full wipes): https://drive.google.com/file/d/0B-6nm7Jks0W5Z25IWDZCeFBudlE/view?usp=sharing
CyanogenMod Port:
9: Merge with original CyanogenMod 20141010: https://drive.google.com/file/d/0B-6nm7Jks0W5OElZRmRGLTluYms/view?usp=sharing
8: Merge with original CyanogenMod 20141008 SNAPSHOT-M11: https://drive.google.com/file/d/0B-6nm7Jks0W5blpPRVFpX1hNNzg/view?usp=sharing
7: Merge with original CyanogenMod 20141007: https://drive.google.com/file/d/0B-6nm7Jks0W5WGJYUFd1dWF5emc/view?usp=sharing (link updated)
6: Merge with original CyanogenMod 20141004 with bluetooth fix: https://drive.google.com/file/d/0B-6nm7Jks0W5d2l2LW56QlV0LXM/view?usp=sharing
5: Merge with original CyanogenMod 20141004: https://drive.google.com/file/d/0B-6nm7Jks0W5OVYxU1Z1NWtKRms/view?usp=sharing
4: Merge with original CyanogenMod 20141003: https://drive.google.com/file/d/0B-6nm7Jks0W5OGpYb21SZEZWd28/view?usp=sharing
3: V2: https://drive.google.com/file/d/0B-6nm7Jks0W5NmY5V29PNVFadm8/edit?usp=sharing
2: V1: https://drive.google.com/file/d/0B-6nm7Jks0W5aE1sa0NfVDdXa28/edit?usp=sharing
1: V0: https://drive.google.com/file/d/0B-6nm7Jks0W5dUlTc3lfLWtTaUk/edit?usp=sharing
Google Apps additional package
(use latest kk gapps: gapps-kk-20140606-signed.zip): http://goo.im/gapps
or (set of packages - full, mini, micro, nano): http://forum.xda-developers.com/showthread.php?t=2397942
TWRP:
http://forum.xda-developers.com/showthread.php?t=2706982
Kernel:
Kernel with enable VT (big thanks for bonuzzz) : https://drive.google.com/file/d/0B-6nm7Jks0W5VldRNGdqYld3TEE/view?usp=sharing
Sources:
device
kernel config for P900
kernel for exynos 5420
vendor
Thanks
Thanks to CyanogenMod team and special thank to crpalmer, his hard work on fix all problems for original SM-T520 finally allow create the port for SM-P900.
Special thank for bonuzzz.
Additional:
Multi-Windows:
1. Install Xposed framework: download apk from http://forum.xda-developers.com/xpos...gelog-t2714053
run apk, launch it, go to framework and press installupdate, then reboot. Alow root if ask.
2. Install XHaloFloatingWindow module: open Xposed framework, go to download section and search XHaloFloatingWindow (just type Halo), open XHaloFloatingWindow, swipe to left - and press download on latest version
3. Activate XHaloFloatingWindow module: open Xposed framework, go to Modules and check XHaloFloatingWindow, then reboot. Allow root if ask.
4. Open XHaloFloatingWindow - you can leave all by default, but:
- Popup WindowPopup Dim set to 0
- Popup Behavior - check "Force New Windows in Halo"
5. Install MultiWindow Sidebar: download apk from http://forum.xda-developers.com/show....php?t=2729450
6. run MultiWindow Sidebar:
- Check "Start on Boot"
- In "Select Apps" - add your apps
- In "Drag Launch Mode": select ParanoidAndroid Halo
- In "Tap Launch Mode": selecrt ParanoidAndroid Halo
then reboot and enjoy.
It's a bit buggy in rotate, but it's work.
S-Pen:
CM S Pen Add-on: https://play.google.com/store/apps/details?id=com.tushar.cmspen
Note Buddy: https://play.google.com/store/apps/details?id=com.tushar.spen_helper
INKredible - Handwriting Note: https://play.google.com/store/apps/details?id=com.viettran.INKredible
XDA:DevDB Information
CyanogenMod 11, ROM for the SM-P900, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
Valera1978, bonuzzz, arcadia2uk
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 20141104
Stable Release Date: 2014-11-04
Created 2014-11-05
Last Updated 2014-11-05
Finally, thank you so much.
Do we need to update to latest TWRP or should 2.7.1.0 work? Had issues on other devices using ver 2.8.0.0.
** After testing everything works fine, great work !!!
I'm on 2.8.0.0 - it's working correct for me. But it also should work on 2.7.1.0.
Valera1978 said:
This port based on official CyanogenMod for SM-T520 (http://download.cyanogenmod.org/?device=picassowifi)
It's for SM-P900 (Exynos) only.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and install a compatible recovery
3. Wipe data & cache partitions and flash firmware
4. Optional: install the Google Apps additional package
Known Issues
1. MTP
Links
CyanogenMod Port: https://drive.google.com/file/d/0B-6nm7Jks0W5dUlTc3lfLWtTaUk/edit?usp=sharing
Google Apps additional package (use latest kk gapps): http://goo.im/gapps
TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Thanks
Thanks to CyanogenMod team and special thank to crpalmer, his hard work on fix all problems for original SM-T520 finally allow create the port for SM-P900.
Click to expand...
Click to collapse
cool...
does it keeps the s-pen ability ?
snir2 said:
cool...
does it keeps the s-pen ability ?
Click to expand...
Click to collapse
pen works but no pointer on screen.
Also having trouble mounting device on my laptop.
Yes, pen working - i checked in INKredible, button work too.
Mounting on pc - trying fix it.
nice to see CM coming.. been a while since been able to use em
From my Fired-up Note Pro 12.2!
Sweet! I sort of feel like this tablet has now arrived If possible, could someone who has it up and running give us a quick overview of things like spped, responsiveness, battery etc?
I just flashed this ROM it is running very smooth I am running it with art and nova launcher and very impressed so far, I can't comment on battery yet will test it out tomorrow I have been waiting a very long time for a cm11 ROM for this tablet and would also really like to see a slim or carbon ROM as well
Update header: add V1 version - now SPen working correct in vertical mode.
Hi, thank you for this ROM. Is app to sd working?
Now there is a chance to actually use it. I ll wait for the mtp to get fixed though. Thanks!
First of all, thank you for the port.
Installed V1, full wipe using TWRP 2.8.0.0
Everything seems to be working fine so far. The only issue I'm concerned about is how the Interactive governor is tuned. The CPU spends most of it's time pegged at 1900MHz across all four cores even when just scrolling through Facebook or Chrome. Changing the governor to Ondemand makes it behave much better. Battery life would be an issue on Interactive.
Edit: also, on first boot I couldn't see my 5GHz access points. Changed the WiFi Region code in settings to my country (Canada), rebooted and could now see/connect to 5GHz channels.
I've only been running it for a couple hours, so I'll give more feedback as I get more data.
New V2 version: mtp fixed.
Noooooooooo
I want it but i have p905
Inviato dal mio SM-P905 utilizzando Tapatalk
Hi Valera1978,
This is not for my device, mine is a 905, but thanks for bringing some movement to this forum and of course, thanks for your hard work supporting this tablet. I believe some more months and we'll see more ROMs posted here.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Dirty flashed V2. Can confirm MTP working with Win8.1 (only internal storage mounts, but not external sdcard)
Works really well, nice and smooth. I'm surprised to see such a great ROM, thanks.
Ahh! Finally some movement on this device! I will flash this as soon as i get up tomorrow and post some feedback.:good:
This Rom is huge, after testing 2 days, I can say it s fast,smooth,better battery life,even gaming performance is better than Samsung stock crap installation.And look.... we got more free space.I kinda miss the pointer under the pen but that just a matter of time . Great work.
This is a clean and fast version of the current ARK4 Firmware. Most of the Samsung bloat has been removed while maintaining a stable system.
Features::highfive:
Based on latest ARK4 Firmware
Latest Modesty kernel with enhancements
December security patch
Zipaligned
Deknoxed
Disabled RMM
Lots of bloat removed
Latest Nova Launcher
Using Cloudflare DNS servers
Buildprop tweaking battery and performance
iOS 12.1 emojis & GoogleSans font
Goodlock Multistar, Lockstar and Taskchanger
Other included apps: YouTube Vanced and Activity Manager
Rooted with latest magisk by Ianmacd
Enabled Doze for Google Play Services and Play Store
Naptime for improved deep sleep (enable in app)
AdAway as adblocking solution, but also preinstalled Goodbye Ads hosts file
All added apps can be uninstalled
ADB enabled by default
Changelog
V6
- Rebased to new firmware ARK4
- Switched to iOS emojis
- Updated all apps
- Latest Modesty Kernel (23/12)
- Adblock hostfile default now
Download it now
Quick notice:
To change the Goodlock apks settings get an activity launcher and launch the main activity! In V6 Activity Manager will be included to serve this purpose.
To restore Netflix functionality you have to flash this module via magisk.
When running custom kernels on newer samsung devices bluetooth pairings are bugged. Flash this module as a fix!
If you are interested in controlling the kernel options install the excellent MTweaks app!
Credits going to
SuperR for his linux kitchen
Geekydroid for his tutorial
Ianmacd for his magisk builds and modesty kernel
foobar66 for his googlewiz script and buildprop
yash92duster for tutorials
Samsung for firmware
dr460nf1r3 said:
Hi guys,
I recently started learning about cooking own custom rom builds and since there was no rom available for our tabs i created one myself. Im gonna share my builds here as well since there are probably guys here who want to flash a custom rom and update but dont know how.
V1 is a basic build created out of the latest AJR3 Firmware with some very basic modifications thus being almost stock. I plan on debloating further and adding more mods but that takes time to learn and test. For now enjoy the first build! :fingers-crossed:
As im only in possession of the LTE variant of the tab i cant tell if it also works on the wifi version. It might work if you flash the rom and modesty kernel afterwards, but again, i cant test this so go ahead, test and tell me afterwards.
Features:
- Based on latest ARJ3 Firmware
- October security patch
- Firmware fixes ghost inputs while gaming
- Zipaligned
- Deknoxed
- Disabled RMM
- Safe debloated
- Few buildprop tweaks
- Includes Adaway and Multistar
- No root, gotta flash magisk afterwards, but i integrated Ianmacds own Magisk build into the rom so you can download the latest zip via the installer
I was thinking about integrating a modified host file for adblocking but since i use one that breaks the facebook app by default i only included Adaway. If you want to have even better adblocking though, take a look at this thread!
Also, Modesty kernel will be based on the latest firmware soon, so i advise you to flash it afterwards.
Im by no means experienced with cooking roms and this is my first rom ever so this is probably going to be all about debloating and basic mods. :silly:
Download:
Version 1
Credits going to
- Androdev for classy kitchen
- Geekydroid for his very nice tutorial
- Ianmacd for his magisk builds
- foobar66 for his googlewiz script
- Samsung for firmware
Click to expand...
Click to collapse
Does deknoxed mean it does not trip the Knox counter. I don't want to root due to the fact my mobile device manager on the job may not let me use this tablet for work. Is root necessary? Also is this based off of the Korean model or another english speaking country? I'm trying to get alot of the korean defaults out of my tablet. Thank you.
gradynyc said:
Does deknoxed mean it does not trip the Knox counter. I don't want to root due to the fact my mobile device manager on the job may not let me use this tablet for work. Is root necessary? Also is this based off of the Korean model or another english speaking country? I'm trying to get alot of the korean defaults out of my tablet. Thank you.
Click to expand...
Click to collapse
No, it means that the knox apk files have been removed from the rom. Knox counter is triggered when you flash a custom recovery and root the device and has nothing to do with the rom you are flashing.
This is based on the latest firmware i found, which is from malaysia, but universal for the T835 model which is not the korean version.
In order to flash this rom you have to get TWRP working which trips knox but the rom itself is unrooted.
Sent from my dream2lte using XDA Labs
I love you
gradynyc said:
Does deknoxed mean it does not trip the Knox counter. I don't want to root due to the fact my mobile device manager on the job may not let me use this tablet for work. Is root necessary? Also is this based off of the Korean model or another english speaking country? I'm trying to get alot of the korean defaults out of my tablet. Thank you.
Click to expand...
Click to collapse
Download a firmware from an English speaking country and flash it via ODIN. Look on sammobile for firmware and instructions. Official firmware doesn't trip the knox bit.
So im currently working on safe debloating the rom i googled every app i removed one by one to avoid making the system unstable. However whenever i try to sign in to google account the google play services crash and i cant find the error thats really unfortunate
Edit: so appearently it was because i removed chrome.. now i still have to get dex working
Edit: Dex also working seems to be the samsung keyboard..
Sent from my dream2lte using XDA Labs
Im happy to announce the second release of my rom!
Changelog:
- Safe debloated all of the useless samsung apps
- Added YouTube Vanced and Goodlock Taskchanger
- Nova Launcher by default
- Pixel Sounds
- Pie Emojis
- GoogleSans Font
Download V2 here
Edit: This release accidently killed GPS just fyi. Fix already done but cant upload until tomorrow evening. If you want to do it yourself take V1 and copy FusedLocation folder from priv-app to the corresponding location in V2.
Sent from my dream2lte using XDA Labs
Release of rom version 2.1 :victory:
Changelog:
- GPS fixed
- Few more buildprop tweaks taken from googlewiz oreo credits to foobar66
- Modesty kernel by default credits to Ianmacd
Dirty flash is always fine.
Im thinking about replacing samsung apps by google ones however there wont be tooltips on spen hovering like on the samsung ones and no splitscreen while being not being in portrait mode.
Any idea on what else to add/debloat/whatever?
For T830 users im pretty sure that this rom will work fine If you flash the Modesty kernel after rom installation.
Download 2.1 here!
Following is release 2.2!
Changelog:
- Now prerooted with latest Ianmacd magisk!
- Cloudflare DNS servers used
- Enabled Doze for Google Play Services and Playstore
- Naptime app for improved deepsleep
Download 2.2 here!
Release 3
Changelog:
- Samsung Pie keyboard
- Switched to Ruthless Launcher
- Updated Google & Samsung apps to the latest so no more Galaxy Store needed
- Updated Pie Emojis
- Removed Samsung account & Experience service
- Switched to GCam
I'd include more of them pie apps but they are still rather bugged so here we go.
Download removed.
Release 3.1
Changelog:
- Removed Samsung Camera & its unneeded apks
- Removed Gallery as im only using Google Photos
- Reverted to latest oreo Samsung keyboard as Pie one was too unstable
A few notes:
- If you want to change DeX background download Samsung Gallery from playstore as the app points towards it. You can uninstall it afterwards.
- For Gcam you have to install this apk after setting up rom, somehow this fixes the crash if only installed in /apps and I sonst know how to fix this by default. After this its fully working though. https://forum.xda-developers.com/showpost.php?p=75675455&postcount=209 credits to cstark27
- To change the Goodlock apks settings get any kind of activity launcher and launch the main activity!
Download here https://mega.nz/#!zI8yGQrK!lV85-Aplo42VtdfhzSm3qZcgMGu1peG9ziNOCxI8gdM
Sent from my dreamlte using XDA Labs
v3.1 - File no longer available
EggZenBeanz said:
v3.1 - File no longer available
Click to expand...
Click to collapse
Im currently rebuilding the rom as the rom wasnt 100% stable in longterm use.
The process will result in a bigger yet more stable rom which is fine i guess.
Also, all of the apps including the launcher will be updated and all of the added Apps can now be removed.
Magisk and kernel will be updated to the new release too.
Rom will be up tomorrow as im busy today.
BTW V4+ will be called Slim Tab :fingers-crossed:
dr460nf1r3 said:
Im currently rebuilding the rom as the rom wasnt 100% stable in longterm use.
The process will result in a bigger yet more stable rom which is fine i guess.
Also, all of the apps including the launcher will be updated and all of the added Apps can now be removed.
Magisk and kernel will be updated to the new release too.
Rom will be up tomorrow as im busy today.
BTW V4+ will be called Slim Tab :fingers-crossed:
Click to expand...
Click to collapse
Awesome, thanks. My tab will arrive today so good timing. Will your next upload be v4 or v3.1 again?
Thanks for this wonderful rom. It would be even better if you could add 3minit battery.
Sent from my SM-T835 using Tapatalk
EggZenBeanz said:
Awesome, thanks. My tab will arrive today so good timing. Will your next upload be v4 or v3.1 again?
Click to expand...
Click to collapse
It will be V4 of course
sbluescab said:
Thanks for this wonderful rom. It would be even better if you could add 3minit battery.
Click to expand...
Click to collapse
Personally I really dislike 3minit so I wont include it, sry.
Im using AccuBattery as battery indicator since its more clean.
dr460nf1r3 said:
Im currently rebuilding the rom as the rom wasnt 100% stable in longterm use.
The process will result in a bigger yet more stable rom which is fine i guess.
Also, all of the apps including the launcher will be updated and all of the added Apps can now be removed.
Magisk and kernel will be updated to the new release too.
Rom will be up tomorrow as im busy today.
BTW V4+ will be called Slim Tab :fingers-crossed:
Click to expand...
Click to collapse
Looking forward to your rom I should have my tab in a few days.
Sent from my SM-T820 using Tapatalk
Alright guys, here as promised V4!
Changelog:
- System is now less debloated but everything works
- Samsung gallery and camera are back
- Activity Manager and Linux on Dex are now included too
- All added apps can now be uninstalled if you dont like them
- All apps updated (e.g. Ruthless launcher 3.0)
- Modesty kernel updated to latest version
Notice the following before flashing:
- T830 users have to flash Modesty kernel since i only included T835 boot.img
- To change the Goodlock apks settings start Activity Manager and launch the main activity of the apk
- To restore Netflix functionality you have to flash this module via magisk
- Flash this module to restore the persistent saving of bluetooth pairings (cuz of running custom kernel)
- Skip setting up a liebe security in the setup process and setup later!
Finally, here the download :victory:
Thanks for this ROM, got my S4 this morning the timing is perfect
thanks for the v4 man. Stupid question: Do we flash this in TWRP? Do I wipe everything if coming from stock rom?
I'm new to samsung stuff so not familiar with the steps
Here is Jaguar Pie. In addition to familiar Pie features (all of them), you have:
Official Telegram Link: https://t.me/jaguar_Rom_Official
The main thing: Non-treble! So, your vendor is located in system partition, which is NOT available to the entire world, like in treble roms.
1. Hardened/fortified bionic (over 150 commits) to prevent bad behavior by system and third party apps
2. Most runtime processes are read only, which means they can't be exploited to take over the device. I am trying to attack the cause, rather than the symptoms (a specific exploit)
3. Many kernel security features activated, such as 'configuration_integrity', randomization; hardened user copy, etc. Impulse governor added
4. Yama security in kernel
5. Working msm hotplug, which actually plugs/unplugs CPU based on load
6. Wakelock blocker, Alarm blocker etc
7. Gestures, Omni Theming
8. Smart pixels
9. Offline charging
10. Utouch
11. AOD
12. No response to 'type zero' SMS
13. Boot time on a fully settled rom is about 4-5 seconds after Zuk logo
14. Qualcomm's boost framework
Many more features, which I am tired to list.
This is beta, because I don't have the device - relied on @Dr.07 @The.Night.King and @benedict97 - thanks for testing
INSTRUCTIONS:
1. Format System/Vendor (if you have it)/Data/Dalvik/Cache. If you are encrypted in Oreo or encrypted with FBE, you also need a format with factory reset to get rid of encryption. ALSO: FORMAT FACTORY partition, otherwise, you will have 2 sets of vendor blobs, which would create a mess on boot
2. Flash the rom, flash Gapps, reboot and let the rom run, then
3. Back to TWRP to flash Magisk (18.1 is working)
Rom download V1: https://forum.xda-developers.com/devdb/project/dl/?id=31427
This is the initial release. All future updates will be in post #3, as usual.
Credit: MrHacker (I used his device tree as a base) and many others who work on device tree and kernel and obviously AOSP, OMNI, DU, CopperheadOS, Carbon Rom, Xtended and Benzo
Also, credit for a Jaguar bootanimation to @Ashish9 and @The.Night.King who made a logo and header icon
If anyone is interested in Afwall with administrative option restored (app can't be uninstalled, unless confirmed by you): https://forum.xda-developers.com/attachment.php?attachmentid=4739733&d=1554836212
XDA:DevDB Information
[ROM] JAGUAR PIE NON-TREBLE 3.18 KERNEL OFFICIAL, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/optimumpr/kernel_zuk_msm8996
Sources for new (May 29) kernel: https://github.com/optimumpr/android_kernel_zuk_msm8996-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.1.x
Based On: AOSP, DU, Lineage
Version Information
Status: Beta
Current Beta Version: V1
Beta Release Date: 2019-04-05
Created 2019-04-05
Last Updated 2019-08-07
Screenshots
Some screenshots:
Updates in this post
Those who are coming from treble roms: you need to format Factory partition too, otherwise, you will have 2 sets of vendor blobs, in other words, MESS
August 7. New release.
1. August security patches
2. Google r46
3. Camera should have level 3 now + more
Dirty flashing is fine, if on the previous release. Otherwise, clean flash - wipe Vendor/Factory/System/Data/Cache/Dalvik
Download rom V6: https://forum.xda-developers.com/devdb/project/dl/?id=31753
July 30: New release V5.2 with fixed installation problems:
You could try dirty flash, but I installed clean, then flashed Opengapps, and Firefox installed without any problems, while it didn't on V5.1.
Download rom V5.2: https://forum.xda-developers.com/devdb/project/dl/?id=31733
July 27. New release, v5.1.
This will fix encryption.
The reason it didn't work was the official TWRP. The maintainer (a known pro) put in the wrong size of userdata partition. So, if you ever formatted data on official TWRP, especially with factory reset, your data partition is screwed for the purposes of encryption (no place for crypto footer). I had to install another version of TWRP, and after I did format there, encryption worked. So, I am attaching both the rom and unofficial TWRP by handibuddy. This is also a signed version (as well as the rom itself), so you can re-lock bootloader on this rom: I have been doing this for ages and long before Lineage came up with the idea (you can check my signing guide in Oneplus 5 thread).
Download Rom V5.1: https://forum.xda-developers.com/devdb/project/dl/?id=31727
Download signed TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=31728
Instructions: Rom could be flashed dirty over V5. TWRP could be flashed as image (to recovery) in your existing TWRP or via fastboot.
Just remember, if you want to relock bootloader, encrypt after locking.
July 25. New release, v5
1. July security patches
2. New Night Screen with configurable tint and brightness
3. Support for level 6-6.2 for AVC codecs
4. Option to disable proximity sensor during calls
5. In-CallUi is now themeable
6. Aggressive battery saving mode
7. Latest Lawnchair
Clean flash is required over V4 or if coming from a different rom, in which case you will also need to format vendor or factory partition.
DO NOT ENCRYPT YET!
Instructions:
1. Dirty flash, if already on Jaguar Pie
2. Clean flash, If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Download rom V5: https://forum.xda-developers.com/devdb/project/dl/?id=31725
________________________________________________________________________________________________________
June 6. New release, V4:
1. June security patches
2. Pie r41
Dirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
ps, reboot, then back to TWRP to flash Magisk
Download rom V4: https://forum.xda-developers.com/devdb/project/dl/?id=31621
______________________________________________________________________________________________________________________
June 2. Lawnchair update to the latest. Flash in TWRP.
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4770317&d=1559500522
May 31. Rom updated, V3:
1. Major kernel improvements - there is no reason to use my Oreo kernel or any other kernel
2. Flashlight works regardless of 'always on' or 'ambient display' (that required a clean flash)
Instructions:
1. Clean flash recommended - wipe system/data/cache/dalvik
2. If coming from a different rom, also format vendor/factory
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
Download rom V3: https://forum.xda-developers.com/devdb/project/dl/?id=31612
_____________________________________________________________________________________________________________________
May 30. This is an updated version of the new kernel I posted earlier. This one contains my commits + reversed 'power saving' commits. Sometimes, you get things better by reversing.
Unzip, put on internal SD and flash either with TWRP (as image onto boot partition) or via fastboot.
Download new kernel: https://forum.xda-developers.com/attachment.php?attachmentid=4768179&d=1559177914
May 28. Lawnchair update. Flash in recovery:
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4767269&d=1559060237
May 27. Updated release:
1. Fixed toggling flashlight in ambient display
2. Improvements in Qualcomm's boostframework
3. Contactsprovider updated (disappearing contacts)
Could be dirty flashed over V2. Otherwise, clean flash.
Download rom V2.1: https://forum.xda-developers.com/devdb/project/dl/?id=31602
May 25. New release, V2:
1. May security patches
2. Android Pie r37
3. Big changes in frameworks: exec spawning function is severely restricted to all apps, i.e., only one instance is allowed
4. Most resources preloading for exec spawning is disabled. As a result, boot time is shorter, fewer background resources are loaded in ram, which translates into an overall smoother experience.
5. Aggressive battery saving
6. Status bar burn protection
7. Media cover art filter (on lockscreen)
8. Switched to Bromite system webview V74
9. Redone auto-brightness and ambient display: ZukDoze removed, as Customdoze and Amibientdisplay are now builtin (Settings/Display)
10. Lawnchair upgraded: many fixes including Pie recents
11. MusicFX/Equalizer is now themeable
12. Zukparts removed, as spectrum profiles simply don't work, and KCAL could be done via Kernel Adiutor
13. Battery icon Q style
14. Wifi randomization working (Developer Settings)
15. Captive portal detection toggle (Settings/Wifi/Advanced - disable network connectivity check). You can now uninstall Captiveportal and have no 'x' in Wifi and Mobile icons
Instructions:
1. Clean flash required
2. Format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps or Nano Gaps, reboot. Then back to TWRP and flash Magisk
If your provider's APN is not on the list, set it up and enable. If data doesn't work, then change CDMA subscription in Mobile network to the alternative.
Download rom V2: https://forum.xda-developers.com/devdb/project/dl/?id=31591
__________________________________________________________________________________________________________________
April 9. New release. Lots of changes, mostly in kernel:
1. Inteli-thermal
2. Thermal-engine ported from Jaguar Oreo, so the rom runs about 3 degrees cooler
3. Substantially improved fluidity: according to testers, virtually no lag
Instructions:
1 If on a previous release, flash dirty and wipe dalvik/cache
2. if new, format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps, reboot. Then back to TWRP and flash Magisk
Download rom V1.1: https://forum.xda-developers.com/devdb/project/dl/?id=31467
_____________________________________________________________________________________________________________________
April 5. Here is the first update, kernel only. Speed improvement.
Just flash boot.img on top of the first release.
Download kernel: https://androidfilehost.com/?fid=1395089523397933955
Finally ?
@optimumpro Thank you. Respect?
Thanks for the work! ?
Woh!!!!...... Waiting for a detailed review by someone.....
Wow finally
vinay069 said:
Woh!!!!...... Waiting for a detailed review by someone.....
Click to expand...
Click to collapse
your prediction turned out pretty accurate about the release date lol
All right, boys and girls. First update: kernel only - speed improvement . Download (in post #3) and flash on top of the first release
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
GopalKaul said:
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
Click to expand...
Click to collapse
Screenshots posted. Stereo sound - not yet.
optimumpro said:
Screenshots posted. Stereo sound - not yet.
Click to expand...
Click to collapse
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Shubhi singhal said:
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Click to expand...
Click to collapse
Just flash rom
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Kernel only.
venom0207 said:
Just flash rom
Click to expand...
Click to collapse
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
@optimumpro animations r fekked
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
It is non treble, factory or vendor have nothing to do with it, you can straight away flash the rom
Flashed the ROM.
It took a lot of time to boot.
Swipe up home screen is not showing any options
Recents is not pie recents
Very fast ROM
In some themes, the notifications are invisible