Shift Dual Boot/ TW and CM Kernel
This kernel supports both TouchWiz and ALL of AOSP other than maybe Pac Rom but it is not my fault it isn't supported lol. They use their own name in the framework instead of the one EVERYBODY else does.
CPU GOVERNORS: lazy, smartass, smartassV2, ondemand, powersave, interactive, performance, userspace, pegasusq, zzmoove
I/O GOVERNORS: deadline, cfq, row, sio
default cpu governor: ondemand
default I/O governor: cfq
CIFS & NFS Network FileSystems
F2FS/EXT4
kernel uses LZMA compression
OverClock to 2160
CPU Voltage Control
GPU OC, UC and Voltage Control
Boeffla Sound 1.6.6 (Use the control app from the play store)
Charge Control
TouchWake and Timeout support
Slide2Wake
DoubleTap2Wake
Mdnie HiJack
Dynamic Fsync Control
Kernel gesture support
Latest source updates
Compiled with Linaro GCC 4.9.3
STweaks is included for kernel configuration
Install Instructions: Standard flash in recovery, dual boot instrustions will be listed below. When flashing AOSP flash the addon zip afterwards
Downloads: Shift
AOSP Sensor addon: Starting with build 3.1 this is NO LONGER NEEDED. The kernel will add the necessary sensors when aosp is booted
Shift Lollipop Single boot kernel can bet found here. All features are the same aside from the needed updated for Lollipop to work correctly
Downloads: Shift-LP-5.7
Dual Boot Support will REQUIRE PhilZ Touch Advanced from here: PhilZ
XDA:DevDB Information
Shift-DualBoot-Kernel, Kernel for the Samsung Galaxy Note II
Contributors
rogersb11, ketut.kumajaya
Source Code: https://github.com/rogersb11/android_kernel_samsung_smdk4x12/tree/shift
Kernel Special Features: Dual Boot TouchWiz or Aosp ROM, Aroma recovery boot menus with PhilZ Advanced touch
Version Information
Status: Stable
Current Stable Version: Dual=3.9/Single=LP-5
Stable Release Date: 2015-04-03
Created 2014-08-16
Last Updated 2015-07-20
These are my personal boeffla settings that do not break the earpiece sound so often experienced by some but not by me lol
WARNING, these settings WILL completely change your headphone jack into a BEAST. I'm serious please be careful. Without these I use car stereo at 26, with them I use maybe 14 and it's louder than the 26 so I'm advising to start low.
{
"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"
}
Dual boot Instructions(will be updated)
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest Shift kernel. BIG FAT WARNING: For AOSP Rom flash the Sensor update zip
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/galaxy-note-2/development-n7105/recovery-t2849091
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash aosp ROM as 2nd ROM
v) Flash Shift kernel again
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash Shift kernel again
vii) Reboot into primary recovery
viii) Flash aosp ROM as 1st ROM
ix) Flash Shift kernel again
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms
Sorry I've been basically MIA lately guys but I haven't had a device. Mine broke about three weeks ago when it plummeted to it's death while I stared in horror. I was gonna be forced to stop development or move on when I could afford to. Thanks to and INCREDIBLY GIVING and just flat out AWESOME and REAL @gregsarg I've been resurrected. That guy loves these threads and this N2 community more than anyone I've ever come across in any of device threads I've been in or a part of. Dude helps on like every thread we have I think. He moved on to the S5, put it back in the box and came back here. Saved @eZdubzitmk4 at one point in a similar situation and then months later comes through in the clutch again. Nobody expects someone the donate a device but it happens because users like @gregsarg are around worrying about OVERALL device development for us N2 users. We all probably owe him a thanks because we've all inevitably gained something from him around these areas. So THANK YOU @gregsarg for your amazingly generous and truly sincere donation. I'm rocking a brand new NE5 Loader Note 2 and all because you kick ass. All development going forward from me here is because of him. Thank you man. You're a truly great friend. This will be located in the second post in this forum going forward.
rogersb11 said:
Dual boot Instructions(will be updated)
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest Shift kernel. BIG FAT WARNING: For AOSP Rom flash the Sensor update zip
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/galaxy-note-2/development-n7105/recovery-t2849091
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash aosp ROM as 2nd ROM
v) Flash Shift kernel again
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash Shift kernel again
vii) Reboot into primary recovery
viii) Flash aosp ROM as 1st ROM
ix) Flash Shift kernel again
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms
Click to expand...
Click to collapse
I have no data after I flash the shift kernel
Welcome to N7105 and Thanks! Variety is always great, we'll give it a try later in the weekend.
terpin32 said:
I have no data after I flash the shift kernel
Click to expand...
Click to collapse
More specific? Network? I have lte
terpin32 said:
I have no data after I flash the shift kernel
Click to expand...
Click to collapse
Go to APN Settings and see if it's empty. If it is, add the APN setting for your Network Provider. (If you can't enter APN Settings, try flashing latest modem for N7105 - that's if you're using an N7105, otherwise flash appropriate modem).
Everythings working well for me.
Your rom "SaberKat" for my primary rom and Liquid Smooth as my secondary rom.
Great job...Thank you
Blackfyre said:
Go to APN Settings and see if it's empty. If it is, add the APN setting for your Network Provider. (If you can't enter APN Settings, try flashing latest modem for N7105 - that's if you're using an N7105, otherwise flash appropriate modem).
Click to expand...
Click to collapse
my baseband is unknown
I've been running this myself for about a week testing. I have I317 but that shouldn't matter. Built for t0lte
I did everything it said to do. Do I need to flash the bootloader or some other file maybe?
I have the i317 att version gn2
Stweaks support is not included yet. I have same model, flashed about 20 times without issue. No extra files
Downloaded and flashed again. I'll boot TW too, hold up
Touchwiz
Sent from my SGH-I317 using XDA Premium 4 mobile app
rogersb11 said:
Touchwiz
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im on the new bootloader could that be it?
terpin32 said:
Im on the new bootloader could that be it?
Click to expand...
Click to collapse
Oohhh, that I am not sure about. I'm on my still
Sent from my SGH-I317 using XDA Premium 4 mobile app
rogersb11 said:
Oohhh, that I am not sure about. I'm on my still
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill try again in a bit
MK6 I meant
Sent from my SGH-I317 using XDA Premium 4 mobile app
Well im on http://forum.xda-developers.com/showthread.php?t=2803363
And trying to duel boot this rom
http://forum.xda-developers.com/showthread.php?t=2675066
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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Samsung Galaxy Note II. 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 USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose the ROM to boot. You can see how it looks on the left image below and in gallery. 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 support other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
* Install ROM to external SD card [Newly Added feature]
You can also a video which shows it in action.
Warning!
It _is_ dangerous. 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 and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager - This at present does not have support for n7100, working on getting it enabled.
This is the easiest way to install everything MultiROM needs. Install the 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 (the 3rd party kernel should also have kexec-hardboot patch) here on XDA. You are chosing 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 . If you want, just search for "MultiROM installation" on and 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 (multirom-YYYYMMDD-vXX-t03g.zip) - the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_t03g_YYYYMMDD.img) - the zip file from second post and flash it in recovery.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current ROM will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.4 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
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 and then reboot.
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.
To flash GAPPs for the Secondary ROMS, Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash GAPPS ZIP file.
Installing of Touchwiz as Primary Rom & AOSP ROM as Secondary.
Boot into recovery and flash Modified TWRP Multirom recovery
Next, Flash the Multirom zip.
Next, Flash the Modified Agni Stock Kernel and then flash the Mali blobs zip too and finally reboot the phone
Allow the phone to auto boot into the touchwiz rom. Once booted reboot the phone into recovery again.
Now you can flash any AOSP rom as Secondary ROM. for that follow the below steps
Select Multirom - > Add Rom -> ROM Type & Location to install the ROM -> AOSP ROM ZIP -> start the installation.
After installation is complete, go back and select the AOSP ROM that you installed and select "Remove Boot.IMG".
Reboot the Phone now and in the Multirom Manager Menu, select the secondary rom and allow it to Boot.
Note : Wifi is not working on the AOSP ROM installed as secondary, this needs to be debugged further. I am guessing it is due to the kernel version installed on the stock rom versus the touchwiz roms. Apart from the wifi, all other features are working fine.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/tilaksidduram/android_kernel_samsung_smdk4412/commits/kitkat
MultiROM device tree - https://github.com/tilaksidduram/android_device_samsung_t03g
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
MultiROM, Tool/Utility for the Samsung Galaxy Note II
Contributors
tilaksidduram
Version Information
Status: Beta
Created 2014-10-10
Last Updated 2014-10-11
Downloads
1. Main downloadsMultiROM: Multirom Zip
Modified recovery for Multirom (based on TWRP) : Multirom Recovery zip
Kernel with kexec hardboot patch for AOSP ROMs only : Kernel Zip
Note : Other 3rd party AOSP Kernels like Agni, Plasma & Devil do not have the Kexec Hard-boot patch in them at present, so if you have flashed them on you primary ROM then you will not be able to boot into any of the secondary ROMS. I am working with the kernel owners to have the kexec hard-boot patch added into the kernel.
Kernels for Secondary ROMS : These Kernels are not Kexec Hardboot enabled, install them to fix the WIFI Issue on secondary ROM.
1. Omni ROM
2. SlimKat ROM
3. MIUI ROM
4. CM 11
5. Paranoid Android
Kernel with kexec hardboot patch for Touchwiz ROMs only : Agni Kernel for Stock Touchwiz ROMs
Kernel Developers, please merge this patch into your kernel - https://github.com/tilaksidduram/an...mmit/2c9d9821eaa7e250ffe89b67d0a6c8b1c8219bc4
You need to have kernel with kexec-hardboot patch only in primary ROM
2. Uninstaller
MultiROM uninstaller : Zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed
FAQ and other notes
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.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is 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.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
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.
Great work. @tilaksidduram
:laugh::laugh::laugh: great, I'll try this ! :highfive:
Sounds interesting!
Great work indeed
Amazing, superb, perfect, brillant, excellent You are great man, you are great. I'm waiting for this since I saw this in Nexus 4 forum. Thanks.
Great work.
Finally wait is over?
wow i'm waiting the link for download
Thank you sir, first for bring MultiRom to our Note 2, second for step-by-step instruction. I can't wait for DL and try. Amazing job.
finally multirom for note2... thanks you....
Sent from my GT-N7100 using XDA Premium 4 mobile app
OK Tilak! Thanks for your work! Let's wait a kernel with the patch, I want to try this solution :laugh::laugh::laugh:
FUSIONdev said:
OK Tilak! Thanks for your work! Let's wait a kernel with the patch, I want to try this solution :laugh::laugh::laugh:
Click to expand...
Click to collapse
I already patched the stock kernel and it available for download in my 2nd post. you can flash it against any AOSP based Kitkat Rom for the N7100.
Currently i am running PA as my primary rom and i have installed around 6 other roms (Omni, Slimkat, Miui, Liquid smooth, CM 11, ) as secondary. All of these are working fine.
give multirom a try.
Nice....work
Let's hope the Kernel Devs include the patch so that we can also test/check it with Samsung Touchwiz Kitkat Roms
By the way Thanks @tilaksidduram for bringing this treat to us
Bug? Or problem a part those listed in op?
Inviato dal mio OnePlus One
Thanks @tilaksidduram
Thanks
Thanks bai thanks. You r the great. keep going on......
Looks very interesting definitely gotta check this out...
Thanks for the contribution to the note 2 users :good:
This is only working on aosp roms? Is possible to run a touchwiz rom and an aosp rom?
{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for Moto X Pure/Style. 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 left image below and in gallery. 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.
This is still very experimental!
I've only tested this with stock M as the primary ROM and AICP M as the secondary ROM
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. 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 and you will have to flash factory images again. Make backups. Always.
Installation
The MultiROM Manager app does not currently support the Moto X Pure Edition
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 chosing 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.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_clark_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
MultiROM (multirom-YYYYMMDD-vXX-clark.zip) - download the ZIP file from second post and flash it in recovery.
Your current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
Untested on clark
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
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.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/Hashbang173/multirom/tree/master
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
kexec-hardboot patch - https://github.com/AICP/kernel_motorola_msm8992/compare/41e44cc5e5...a6959bcd07
Device tree: https://github.com/MotoX-2015/android_device_moto_clark/tree/android-6.0-mrom
Thanks
This port is based on the hard work of Tassadar, Geoff Levand, webgeek1234, Mike Kasick, 500 Internal Server Error, and many others. Thank you.
Issues
* Does not yet support encrypted devices
* Please report
XDA:DevDB Information
MultiROM for Moto X Pure Edition/Style, ROM for the Moto X Style (Pure)
Contributors
Hashbang173
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-02-14
Last Updated 2016-02-14
Downloads
multirom-20160214-v33-UNOFFICIAL-clark.zip
TWRP_multirom_clark_20160214.img
Stock M patched kernel
MultiROM uninstaller
List of ROMs/Kernels with kexec hardboot baked in
These ROMs/Kernels can be used as the primary ROM without any modifcation
AICP (starting from 2/15/16 build)
Other CM based ROMs depending if they are upstream to the AICP kernel
Frankenclark in the next release?
One more
#First
Second
Very interesting. Thanks!
@Hashbang173 the way u r doing great things for mx style, we should rename the phone as moto x hashbang edition.. Thanks for great wrk
Thanks @Hashbang173 for the awesome work!
Seems to work great!!! If I install or delete an app from the second rom will the change remain after a reboot?
guraki said:
Seems to work great!!! If I install or delete an app from the second rom will the change remain after a reboot?
Click to expand...
Click to collapse
Why wouldn't it?
OK thanks!!! The only problem I have is that moto display doesn't work in Stock rom ...
guraki said:
OK thanks!!! The only problem I have is that moto display doesn't work in Stock rom ...
Click to expand...
Click to collapse
Hmm, I guess that could be a problem with my patched kernel. Have you tried toggling moto display on and off?
Yes I did..!
@Hashbang173 multi rom this was the only thing remaining
thanks dude for your hard work
Interesting I couldn't get TruPureX to be my secondary rom not sure if I did something wrong
Sent from my XT1575 using XDA Labs
Flashed TWRP-MultiRom, pached Kernel and MultiRom on Dual Sim XT1572.
Primary ROM ( Stock Marshmallow) is working fine. Wifi is not working.
On Secondary ROM , flashed AICP 15/2/2016 build with gapps and did a reboot.
After Reboot, Secondary ROM is stuck in the installation process with AICP boot animation even after 15-20mins... Any solutons? (btw Phone is hot as hell, it has never been this hot)
Wow, I didn't expect to see this on the MXP, now all we need is ports of arm GNU/linux and it'll be just like the Nexus 7 (2012) days.
iNik123 said:
Flashed TWRP-MultiRom, pached Kernel and MultiRom on Dual Sim XT1572.
Primary ROM ( Stock Marshmallow) is working fine.
On Secondary ROM , flashed AICP 15/2/2016 build with gapps and did a reboot.
After Reboot, Secondary ROM is stuck in the installation process with AICP boot animation even after 15-20mins... Any solutons? (btw Phone is hot as hell, it has never been this hot)
Click to expand...
Click to collapse
Try to reinstall the patched kernel!Did the moto display worked for you on stock rom?
---------- Post added at 11:58 AM ---------- Previous post was at 11:31 AM ----------
Moreover after using the second rom and then rebboting to the stock one the WIFI cant be enabled.....
guraki said:
Try to reinstall the patched kernel!Did the moto display worked for you on stock rom?
---------- Post added at 11:58 AM ---------- Previous post was at 11:31 AM ----------
Moreover after using the second rom and then rebboting to the stock one the WIFI cant be enabled.....
Click to expand...
Click to collapse
I Tried to reinstall the patched kernel, did not work. I have disabled all moto apps for battery purposes, cant help you with Moto Display bro.
btw I too have the WIFI problem.
Now Went back to stock kernel and everything is fine.
Noob question, How do we get frankenclark kernel to work with the patched kernel ? does flashing one after another work?
Im not responsible for any damage to your phone
But i'm using this kernel as daily driver so its tested before release
Click to expand...
Click to collapse
It is optimized for battery savings in pmehra rom.
Click to expand...
Click to collapse
SAMUK190'S CUSTOM KERNEL Color OS MultiRom
Compatible Rom(ONLY):
Pmehra Color Os 2.1 (2.1.5i Final) (lollipop 5.0.1) : http://forum.xda-developers.com/oneplus-one/development/color-os-2-1-oneplus-one-rom-t3198594
Download Samuk190's Kernel Stable 3#( read more in the post)
https://mega.nz/#!N8NAmRhS!zUykrAM2VM3ffwMS0BAVmaBu8mXWFvSDSe2F0OlIKG8
ps: this is the first kernel made for oneplus color os rom, that is compatible with multirom ( i spent alot of time fixing errors, :silly
[old]
Download Samuk190's Custom Kernel Stable#1 : https://mega.nz/#!4oVgyJKZ!N17fAeVPdJOSyuP1dfx6kFY02pxKTRyHHyh36x-MgwQ
REBUILT stable#1 : https://mega.nz/#!8ksU2Kpa!a5n6tUogktz0uhp4qbG0wK-0BaEuNUda5ThihOKrhtg (same version, but a lighter version for people that have "bootloop stuck issue") (tested by myself) (same source, just removed some files)
Download Samuk190's Custom Kernel Stable#2
https://mega.nz/#!B8MFyIKb!vx0CAvC-bnV3PhnAUcW3I54w2R7Q6XG1CztXS6YxT2Q
Multi rom support, read more in the post for see how it works in my kernel. (tested, im using color os 2.1 from pmehra+ miui 7 x_s)
tip: you can flash a light rom(like miui) as secondary rom, to use NFC.
How to use multirom(internal ColorOS)
1.1CUSTOM KEXEC ENABLED[
What is?It's a half patch made by myself. you must flash COLOR OS in primary partition, and MUST reflash the kernel everytime you want go back to COLOR OS ( just use flashify in the secondary rom)
Advantages : Work's without bugs, Drivers are working good, and you don't need flash secondary rom kernel.
after flashing samuk190's kernel do this
Now lets make multirom work! #Method 1 (tested by myself)
Download MultiRom Manager
Install everything LESS KERNEL from multirom.
Now go to multirom menu, rebooting it.
Boot Internal ROM
Reboot
Install the rom you want , secondary, etc
Reboot to multirom select rom menu
Boot Secondary Roms(or any rom that is not internal)
If says "Kexec full patch need, blah blah, just enable no-kexec-workaround in twrp multirom"
After that , the phone will reboot to MultiRom Rom list menu
Boot secondary rom again, it will say : Booting with kexec or blah blah..
Profit!
To boot internal rom again(after booting secondary roms or any rom that is not internal)
Go to multirom boot and boot to your internal rom
It will redict to recovery due to the driver incompatibility bug.
Just flash boot.img in recovery(or with flashify inside the secondary rom)
Install > image > boot > samuk190'sboot.img
Inject current sector
Reboot and boot internal.
Easier way to make multirom work.
Download flashify app in your secondary rom
flash boot.img stable#2
reboot and boot internal rom
(do the same thing if you're on secondary rom again)
Instructions to flash kernel in fastboot :
turn your phone into fastboot mode.
do this at prompt(cmd)
fastboot flash boot (boot.img location).img
restart phone and wait.
About me
Hi, my name is Samuel! Im
Brazilian, and im new at the development and
i only have the OnePlus One.
Click to expand...
Click to collapse
What is Samuk190's Custom kernel for Color Os?
It's the kernel from pmehra with some bugs fixed, and some new features,slightly fast and the interactive governor back ( , big feature, it will have more features i promise )
Why you are working in this?
Alot of people complained of bad battery in color os 2.1 and some bugs.
Color os has the best drivers, best camera and sound, so it worth spend time at this project for a long time.
some devs don't like non-cm roms(because source incompatibility), so i'm decided to work with this.
With a better kernel, less lag, and fast phone.
It's for daily use!
What i'm working actually for this kernel :
Custom hotplug ( Missing compatible sources?)
Voltage Control(Problem with CPU_VOLTAGE_TABLE compatibility)
More CpuGovernors(every build i will add one any idea?)
NFC fix (hard to do, driver compatibility missing)
Maybe overclock? (hard to do, different kernel architecture, missing incompatibility with built source, need rework)
Custom Animation Boot(idk)
and alot of fixes that will impact in better battery optimizations
give your opinion
BEST configs for battery:
Battery configs :
ZzMoove min 300 max 840
Profile: 3 or 4
input boost > off
or input boost > 300 mhz
(Search in google for profile list, profile 3 is for battery yank extreme and 4 is for battery plus )
(dont forget to change zzmoove profile at kernel auditor)
Another good battery backup config>
cpu: conservative,min:300 max 840 mhz
cpu:smartmax,min 300 max 840mhz
Gpu : powersave
Changelog :
#Stable1
Fixed CpuFreq_interactive
added cpu interactive
Compiled with linaro 4.9.3 (fast)
Changelog stable #2:
Compiled with Google OFFICIAL NDK 4.7.3 ( better battery, no drains, same performance as 4.9.3)
KEXEC HARDBOOT SUPPORT (must be flashed in first partition) (better than nothing)
Smartmax governor
#Changelog Stable 3#
Added Zzmoove governor with 9 profiles(new!)
Added Adreno idler(200mhz when idle, so battery save)
Updated Adreno_Tz_Governor
4 cores online with low frequency is better than 1 core at high frequency, remember this.
Source:https://mega.nz/#!d4cgSR4R!w2fC5hp_jC8j3QkF-kvfMjGHNllXxPED8AZhQhiL9B8
Source#Stable2 and 3# included:here
screenshots:
{
"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"
}
Thanks(sorry if i forgot someone):
@Lord Boeffla @pradeepsmehra
@acuicultor
@Andy1911
@DespairFactor
reserved
reserved2
Awesome. Keep up the good work bro. :good:
Could this kernel make the ROM compatible witj Multirom?
app kernel setting
which app you prefer to set the kernel?
UKM or KERNEL AUDITOR?
Your source code is missing. Do you want to upload every time 400mb? Github or Gitlab or something like that.
Sent from my A0001 using XDA-Developers mobile app
**** seems awsm ! gonna flash asap ! hope it gives me battery backup !
DerRomtester said:
Your source code is missing. Do you want to upload every time 400mb? Github or Gitlab or something like that.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Source code not missing, just unpack rar in linux (because if you unpack in windows as the windows is not case sensitive, the same files like xt_MARK.h and xt_mark.h will be replaced.)
i tried github, but it fails i will upload 400Mb everytime, no problem.
(but i will try upload to github again):laugh:
hyper_davide said:
which app you prefer to set the kernel?
UKM or KERNEL AUDITOR?
Click to expand...
Click to collapse
Kernel Auditor.
Ukm is good also, but i need release a version of ukm compatible with everything.
Richard20000321 said:
Could this kernel make the ROM compatible witj Multirom?
Click to expand...
Click to collapse
Yes, maybe in future. It's hard.
( i dont promise, but i will take this as a challenge )
Thanks for your wonderful work and effort, I see ur PM today, Sorry for that...
its joyful that u clear the blockage in compiling.
Color OS is amazing project and my first love in android world, but Oppo discontinued it because of so many developers got change and they mess-up everything.
if you need any help in future you can write me directly on my email.
[email protected]
samuk190 said:
Yes, maybe in future. It's hard.
( i dont promise, but i will take this as a challenge )
Click to expand...
Click to collapse
nice?good luck?
no flashable zip?
aliffaminuddin said:
no flashable zip?
Click to expand...
Click to collapse
no yet. just download flashable zip from another kernel,
and replace boot.img. then flash
or
in recovery you go to > flash > img > boot
and flash boot.img
I will make flashable zip in future.
samuk190 said:
Source code not missing, just unpack rar in linux (because if you unpack in windows as the windows is case sensitive, the same files like xt_MARK.h and xt_mark.h will be replaced.)
i tried github, but it fails i will upload 400Mb everytime, no problem.
(but i will try upload to github again):laugh:
Click to expand...
Click to collapse
Please give github or gitlab a try. Without it is impossible to follow your changes you did.
DerRomtester said:
Please give github or gitlab a try. Without it is impossible to follow your changes you did.
Click to expand...
Click to collapse
github problem with large files, so im trying github lfs, but lfs don't track all files.
is it fine that it takes time to reboot after installing this kernel?
samuk190 said:
github problem with large files, so im trying github lfs, but lfs don't track all files.
Click to expand...
Click to collapse
Does NFC work after flashing this kernel now?
Hey felow BR HUE... Please man, if you can do it, give us some Fast USB Charge Settings!
BTW thanks for working on Color OS!
{
"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"
}
To God be the glory, my SlimRoms project finally works!
Sleek, simple, slim, SLIMROMS. This is the lightweight champion of cell phones! Not another CM based rom, SlimRoms is based off of AOSP source, with custom edits for a smoother, simpler interface. If you are looking for every feature, check out AOKP, or PAC ROM, but if you want to step back into the simple life on your phone, then this is the Rom to do it.
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
Downloads :
BASELINE Download: The base rom before any changes such as kernels. Everything works, without extras.
http://www.mediafire.com/file/qmj6z...tmo-xx-6.0.1-UNOFFICIAL-20161108-BASELINE.zip
Gapps link:
http://opengapps.org/
-Which I personally tested Arm 6.0 Pico.
For T-Mobile phones also download this datafix zip:
http://www.mediafire.com/file/sjjtfcsk2me14pv/5.1.1_N910T_and_other_US_variants_DataFix.zip
Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
International Installation instructions (F, G, and FY at this time, possibly others) :
-Put your phone on the 5.1.1 Bootloader and Modem
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personally installed this using Mickey's 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
-Reboot to system and enjoy!
T-mobile Installation instructions :
-Put your phone on the 5.1.1 Bootloader and Modem
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personally installed this using Mickey's 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install datafix zip http://www.mediafire.com/file/sjjtfcsk2me14pv/5.1.1_N910T_and_other_US_variants_DataFix.zip
-Install Gapps. - Optional
-Reboot to system and enjoy!
What works :
Code:
+ Phone calls/receiving
+ Data 2g/3g/LTE
+ Bluetooth
+ WiFi
+ MTP
+ GPS
+ S PEN
etc....
What doesn't :
Code:
- The Camera works, however, the flash often gets stuck on. I recommend using OpenCamera app from the playstore instead, with OpenCamera, this does not happen.
- The edge panel is not implemented at this time. The screen wraps around the edge.
- I have not found any big errors, fault crashes, or problems yet. Please let me know if you find an issue!
This SlimRoms MM ROM was built for the tbltexx and tbltetmo, the International and T-Mobile Samsung Galaxy Note Edge. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK. You will need to edit the META-INF updater script to accomplish this.
Code:
Disclaimer: SlimRoms is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
Device trees: https://github.com/alaskalinuxuser/
There is a new kernel thread for these roms, you can find it here:
http://forum.xda-developers.com/note-edge/development/kernel-marshmallow-kernels-t3488126
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.10.40
Based On: AOSP
Created 2016-10-24
Last Updated 2016-12-20
Change log:
Code:
20161108:
-Due to kernel problems, updated with the original kernel, called BASELINE. Seems rock solid stable, no random reboots.
20161103:
-Added AKLU kernel from kernel thread.
-Fixed RECENTS button, now is a MENU button.
20161024:
-Built with Java 8.
-Added Kernel Adiutor and SELINUX plugin.
-Set kernel to SELINUX permissive by default. (You can use the SELINUX plugin to switch to enforce, if desired.)
-First build release.
The big thanks!
A huge thanks to the SlimRoms team!
Also a huge thanks to @xNNism for figuring out the radio/cellular issues!
And to @Aaren11 for pointing out the T-Mobile data fix!
And all of these great testers (some for other devices) :
@Aaren11
@xNNism
@beany23
@swecon
@1freedude
@lostinlife33
@faizan'
@gavin10
@brainwasher01
@hosny1964
@xcube1
Features and screenshots!
Features and screenshots :
+Status Bar Tweaks
-- Icon settings
-- Clock and Date Appearance
--Battery Status Style
+SlimRecents (Can be reached by holding down the home button)
-- Edit color and display of SlimRecents bar
+Quick Settings
-- Add and rearrange tiles.
+SlimDim Navigation Bar
+RRO Layers Support ( Unofficial - Works, see post #4 for details! )
+Hot Spot
+Edit icons and names of apps! ( Requires icon pack. )
AND MORE!
Notes:
Here are some notes about the rom that I thought might help:
Random Reboot issues?
If you are having random reboot issues with the new kernel, you can adjust the settings as follows:
CPU max freq. 2496 MHz
GPU max freq. 500 MHz
CPU governor interactive
GPU governor msm-adreno-tz
I/O scheduler CFQ
That should solve your issue with the kernel. If you want, you may also flash this baseline kernel:
http://www.mediafire.com/file/bt4qw03m8jko53a/slim-mm-kernel-baseline.zip
This baseline kernel will always work just fine, however the battery life and performance are not as good as the AKLU kernel.
Using Layers:
Yes, this Rom unofficially supports RRO layering! This is not a CM rom, and does not have the CMTE (CyanogenMod Theme Engine).
So, if you go to the playstore, you can download the (depreciated) RRO Layers manager: https://play.google.com/store/apps/details?id=com.lovejoy777.rroandlayersmanager
Note that it is depreciated, but still works. I downloaded the Elixium UI theme here: https://play.google.com/store/apps/details?id=bitsykolayers.Elixium
And installed it. Because of the depreciation, not every RRO layers theme works perfectly, and may not change everything the way you want. However, you can see the screenshots here, the first screenshot is the original settings menu with the Slim Stock colors, and then the second is the RRO Elixium colors. You will have to play with themes to get them to work how you want, but there are lots of options, so have fun!
If the screen looks red-ish, check the settings->display->live display options, you may want to turn them off, it is a low light sensitive display option.
Airplane mode - While switching between WiFi and regular data, on rare occasions, the phone will get stuck where you have data or WiFi with the ! mark and no connectivity. If this happens, you don't have to reboot, just hit airplane mode, give it a second, then hit it again to get everything working again.
T-Mobile users with device model = unknown:
If you are using a N915T (like myself), then after you flash the datazip file, you will notice that your phone reports itself as "unknown" to apps like XDA, TapTalk, About Phone, etc.
The fix is very easy!
-Open /system/build.prop in any text editor
-Anywhere in the file, add this line:
Code:
ro.build.model=SM-N915T
Save and exit, then reboot your phone. You can check "about phone" under settings, you should see yourself as SM-N915T, and apps like XDA should report you as Samsung Galaxy Note Edge.
Setting selinux to permissive: (Now permissive by default.)
See @oscarmaldonado post here for one of the many ways to do this: http://forum.xda-developers.com/showpost.php?p=69235667&postcount=17
Apps:
OpenCamera - The Slim stock camera gets "stuck" with the flash sometimes, so you can either turn off flash on the stock camera, or use a different app. I used OpenCamera successfully, with no issues while using the flash, you can download it here: https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
Side App Bar - This has a semi useful side "edge" bar feel.
https://play.google.com/store/apps/details?id=infamous.apps.appsbarfree
I am unable to install .apk files. How should I fix it??
Sent from my unknown using XDA-Developers mobile app
shahzadhanif said:
I am unable to install .apk files. How should I fix it??
Sent from my unknown using XDA-Developers mobile app
Click to expand...
Click to collapse
Works great here. I am guessing that you mean, how to install an apk without the play store?
Go to settings -> security -> unknown sources.
Make sure that is on. This allows you to install apk files that you have downloaded.
If the apk you wish to install requires root, you can enable root by tapping repeatedly on settings -> about phone -> build number, this will enable developer options. Then you can go to settings -> developer options -> root access, and change it to enabled for apps.
Aptoide is a great Google PlayStore alternative if you want a way to keep your apps up to date without Google.
Sent from my unknown using XDA-Developers mobile app
Thanks for your reply but i did all steps you mentioned above. but i am unable to fix it.
shahzadhanif said:
Thanks for your reply but i did all steps you mentioned above. but i am unable to fix it.
Click to expand...
Click to collapse
Sorry to hear that you are having trouble.
I am using this rom right now, and I can install all the .apk files from my sdcard.
Can you be more specific about the problem? What happens when you try to install them? Does it give you an error?
Here are some generic questions that may help us figure this out:
-Which phone specific model are you using?
-Did you flash 5.1.1 modem/bootloader prior to this rom?
-Did you do a wipe before installing?
-Which gapps did you use? Is it Arm 6.0?
-Have you installed anything else (supersu/xposed/etc.)?
Thanks,
Maybe we can get to the bottom of this.
There is a new kernel thread for these roms, you can find it here:
http://forum.xda-developers.com/note-edge/development/kernel-marshmallow-kernels-t3488126
Now includes the Nightmare governor!
Hello, this ROM is stable or in beta version? Bugs?
pickandrew said:
Hello, this ROM is stable or in beta version? Bugs?
Click to expand...
Click to collapse
Pretty stable, I have been using it as a daily driver for the past 3 days. No issues. The only bug is that the flash for the camera causes problems on the built in app, I have been using open camera without the flash issue. Be sure to grab the kernel from the above kernel thread for better battery life.
By God's grace, I just now figured out how to fix the recents button. I have it working as a menu button on my phone as we speak, and I am building it into another rom update! However, if you can't wait, or want to do it yourself, it is really easy to fix:
Using ES File Explorer or similar, open /system/usr/keylayout/Generic.kl.
Go down past "key 226 HEADSETHOOK"
and add "key 254 MENU"
Save and close that.
Then, open /system/usr/keylayout/qwerty.kl.
Go down past "key 212 CAMERA"
and add "key 254 MENU"
Save and close that.
Then, open /system/usr/keylayout/sec_touchkey.kl.
Edit "key 254 MENU"
Save and close that.
Now, reboot your phone and the recents button will be a menu button!
Another build will be rolled out soon with this built in.
Praise God! A new build is up!
Check out the OP for downloads. The latest build fixes the RECENTS button, which didn't work at all, which is now a MENU button.
I dirty flashed this over my old Slim6 build, be sure to dirty flash any datazips if you are using those too. You do not need to reflash Gapps if you are dirty flashing. As always, be sure to make a backup before proceeding!
thank you so [email protected] for fix recents button
let me flash new slim build rom!
i suggest you can name the rom name like Slime V2.0 when you release new Slim rom.
that's more easy to distinguish.
A while back I made some boot animations for Slimroms. If you are interested, you can check them out here: http://forum.xda-developers.com/slimroms/general/homemade-slimroms-boot-animation-t3377271
Nothing fancy, just some simpler, slimmer boot animations.
AlaskaLinuxUser said:
By God's grace, I just now figured out how to fix the recents button. I have it working as a menu button on my phone as we speak, and I am building it into another rom update! However, if you can't wait, or want to do it yourself, it is really easy to fix:
Using ES File Explorer or similar, open /system/usr/keylayout/Generic.kl.
Go down past "key 226 HEADSETHOOK"
and add "key 254 MENU"
Save and close that.
Then, open /system/usr/keylayout/qwerty.kl.
Go down past "key 212 CAMERA"
and add "key 254 MENU"
Save and close that.
Then, open /system/usr/keylayout/sec_touchkey.kl.
Edit "key 254 MENU"
Save and close that.
Now, reboot your phone and the recents button will be a menu button!
Another build will be rolled out soon with this built in.
Click to expand...
Click to collapse
Should we add or replace with menu 254 ???
Sent from my unknown using XDA-Developers mobile app
The latest build is in the op, you can just download and dirty flash to fix this if you want.
If you do it by hand, the first two files you add that line, the last file you edit 254 to say MENU.
I hope that helps!
Hey all, I edited POST #4 with the following information about random reboot problems, if you experience this, then use these tricks to make them stop, or use the baseline kernel to ensure you don't have those problems ever again.
Random Reboot issues?
If you are having random reboot issues with the new kernel, you can adjust the settings as follows:
CPU max freq. 2496 MHz
GPU max freq. 500 MHz
CPU governor interactive
GPU governor msm-adreno-tz
I/O scheduler CFQ
That should solve your issue with the kernel. If you want, you may also flash this baseline kernel:
http://www.mediafire.com/file/bt4qw03m8jko53a/slim-mm-kernel-baseline.zip
This baseline kernel will always work just fine, however the battery life and performance are not as good as the AKLU kernel.
Great work alaska ! Love your devotion and dedication .
The OP has been updated!
For the group, I am planning to change the way the OP lists the release in the Downloads section of the post.
I have a released a build entitled "BASELINE", in this case, "Slim-tblte-tmo-xx-6.0.1-UNOFFICIAL-20161108-BASELINE.zip". This BASELINE edition has the original kernel, with everything working as it stands. That way, any who want the modified kernel can grab it from the kernel thread, and not have to worry about it being built into the rom.
So, if you have any problems with the rom, give the BASELINE edition a try. It is really rock solid. The other releases will have other kernels and posibly other options in the future.
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Note Edge. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. 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 left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. (Install the attached files) 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 chosing 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: There have been reports that (not only) MultiROM does not work properly with older bootloaders. Update it to version 4.13 or newer in case you have problems.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_tbltexx-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_tbltexx_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
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.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. micky387 kernel), you have to use this option on it, otherwise you would lose MultiROM.
- 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 this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/micky387/multirom (branch mr-7.1)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch android 7.1 mr)
Stock kernel w/ kexec-hardboot patch - https://github.com/micky387/Micky38...r=f1763aec92e75e8faba73801a09d5e896935da4d+69
Lineage 14.1 kernel w/ kexec-hardboot patch - https://github.com/micky387/android_kernel_samsung_tblte_dpc3
XDA:DevDB Information
MultiROM, a Tool/Utility for the Samsung Note Edge
Contributors
micky387 @Tasssadar for your amazing tool
Version Information
Status: experimentale
Created 2017-04-22
Last Updated 2017-04-22
Downloads
1. Main downloads
MultiROM: Zip
Modified recovery (based on TWRP): recovery.img
Kernel with kexec hardboot patch (becareful ,use the borrect kernel for android version): Zip
You need to have kernel with kexec-hardboot patch only in primary ROM
2. Uninstaller
MultiROM uninstaller: Zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
FAQ and other notes
ALL IS IN ATTACHED FILES
**********************************************************************************************************************************************************************
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.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is 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.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, the systems are separated.
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.
The boot animation shows only the last part on primary ROMs, why?
Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.
too
That's another great project @micky387. You are not letting note edge die. Thanks.. Is there any note7 patched kexec kernel?
SM-N930F
catalyst05 said:
That's another great project @micky387. You are not letting note edge die. Thanks.. Is there any note7 patched kexec kernel?
SM-N930F
Click to expand...
Click to collapse
Note 7 ??
You want say note 7 ported rom right ??
If not,you can flash my samsung MM rom or RR nougatd in primary rom with the good kernel and add your rom in secondary.
Only primary Rom need custom patched kernel.
Or,you canflash my kernel V4 because you need a note edge kernel even with ported Rom
Hi Micky, will we get an update from your MickyRom V3 (last Samsungupdate 26.03.17 security update) for our beloved Note Edge? Only times so asked
audiomarko said:
Hi Micky, will we get an update from your MickyRom V3 (last Samsungupdate 26.03.17 security update) for our beloved Note Edge? Only times so asked
Click to expand...
Click to collapse
Hi man,
Yes ,i have DL the last official FW (N915FYXXS1DQC1)
With this MOD, No need to take my head with wipe and install anything :silly: :good:
Nobody have tested yet ??
Any issue ?? something ?
Hello Micky .... am just trying to test your new kernel ... runs until now very liquid and still energy-saving ... great work
Sent from my SM-N915FY using XDA-Developers Legacy app
audiomarko said:
Hello Micky .... am just trying to test your new kernel ... runs until now very liquid and still energy-saving ... great work
Sent from my SM-N915FY using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks.
I will add Stock V4 later but added last update of F2FS filesystem from original source, add new Zcache,sound control and 2/3 another thing
Any user's report ??
micky387 said:
Thanks.
I will add Stock V4 later but added last update of F2FS filesystem from original source, add new Zcache,sound control and 2/3 another thing
Any user's report ??
Click to expand...
Click to collapse
anticipation [emoji4] [emoji4] [emoji4] [emoji4] [emoji4]
Sent from my SM-N915FY using XDA-Developers Legacy app
@micky387
Thank you for your whole work.
Can I use Multiroom if I formated the SD-card as internal storage?
Gesendet von meinem unknown mit Tapatalk
@micky387 did you see this? I think it's gonna be great
SM-N930F cihazımdan Tapatalk kullanılarak gönderildi
---------- Post added at 11:42 AM ---------- Previous post was at 11:38 AM ----------
MultiROM Without Kexec Hardbooting Ported to OnePlus 2
A well-known MultiROM has been ported to OnePlus 2 by XDA Senior Member MZO. Except MultiROM MZO has released a modified version of TWRP 3.1.0.0. With this using the no-kexec workaround, it allows you to use MultiROM without having to flash a kexec enabled kernel. The stock ROM also works on this MultiROM port so you can have the quality camera like in the stock ROM just a reboot away. All OOS, OOS based, the MIUI port, Nougat 7.1 are compatible. If you’re using OP2, give this solution a try and pick up your ultimate ROM combo.
SM-N930F cihazımdan Tapatalk kullanılarak gönderildi
Ram121 from RamKernel https://forum.xda-developers.com/note-4/orig-development/kernel-ramkernel-t3472138 will be adding kexec to his kernel hopefully for v9
Micky .... Thanks for the new kernel ?????????
Sent from my SM-N915FY using XDA-Developers Legacy app
Hi.
I can flash secondary rom like aokp, ressorection, nobel.
I try to flash racerom ver 8.2 or norma and i get message "can't map... Zip rom name".
I have n915f device.
What the problem?
Thank you
Anybody?
micky387 said:
Hi man,
Yes ,i have DL the last official FW (N915FYXXS1DQC1)
With this MOD, No need to take my head with wipe and install anything :silly: :good:
Nobody have tested yet ??
Any issue ?? something ?
Click to expand...
Click to collapse
I have tried to install Noble Note 7 port as the secondary Rom with your MM Rom as primary with F2FS configured. I believe l have followed the steps and Noble is installed and l can select it at boot. But it just boot loops back into recovery after l select it, any clues?
Further to the above, I have been able to get the secondary Rom to boot and it works. Is there anyway to root the secondary Rom? I have tried SU 2.52, 2.65 and 2.73 system less, any clues.
EDT: Reinstalled rom and update now rooted with Magisk all good.
Sent from my GT-N8010 using Tapatalk
yossim66 said:
Hi.
I can flash secondary rom like aokp, ressorection, nobel.
I try to flash racerom ver 8.2 or norma and i get message "can't map... Zip rom name".
I have n915f device.
What the problem?
Thank you
Click to expand...
Click to collapse
Hi Yossi, had experienced this too. I think it's because of the ram. Primary rom is already using high part of the ram, so it won't runnig the Race rom or Norma rom.. Therefore for the secondary rom most probably only small rom will work such as AOKP, Resurrection Remix, Slim om etc..
ufukan said:
Hi Yossi, had experienced this too. I think it's because of the ram. Primary rom is already using high part of the ram, so it won't runnig the Race rom or Norma rom.. Therefore for the secondary rom most probably only small rom will work such as AOKP, Resurrection Remix, Slim om etc..
Click to expand...
Click to collapse
Thank you for your reply, but when i run aokp rom the amount of ram is the same like the primary rom, no less.