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
Anyone working on porting MultiRom to our note 2? Multi booting is already possible but multirom is much easier to use.
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
Kernel w/ kexec-hardboot patch - https://gist.github.com/Tasssadar/6733940
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
jobankler said:
Anyone working on porting MultiRom to our note 2? Multi booting is already possible but multirom is much easier to use.
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
Kernel w/ kexec-hardboot patch - https://gist.github.com/Tasssadar/6733940
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
Click to expand...
Click to collapse
I would love to have this capability for the note 2 too..I love it on my Nexus 7 2013..one can flash and use any ROM as needed..
I agree but is anyone even working on it? If not we should try!
Bumping this old thread because I saw that tilaksidduram ported MultiROM to the Note 2 (N7100). Can this be used with the AT&T variant (i317)? It's basically the same phone except the modem right and this recovery zip doesn't touch the modem?
Link here: http://forum.xda-developers.com/galaxy-note-2/orig-development/multirom-v28-t2900858
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
Hi all,
This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/showthread.php?t=2577211
With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827).
I adapted this method to be able to apply it quite easily on any android device.
This method includes few pieces of software ( sources will be published) :
kexec-hardboot : kernel patch from mkasic
hardboot-reserve : new kernel patch
kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.
Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.
Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )
Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.
You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ
Main advantages of using qcow2 :
thin provisionning
snapshots
compression
liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/showthread.php?t=2226889
Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
- standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
- livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
- liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
- fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
- livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
take dkp kernels for tw43 and kk4.4.2 : http://forum.xda-developers.com/showthread.php?t=2226889
or kernels I compiled
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.
Downloads : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
reserved
First
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.
Sent from my SCH-I535 using Tapatalk
Totally forgot about this, I'll have NBD included in my next kernel so this can work
this is awesome ! i been looking for muilt-boot since i got an S3 !
it's working great!
Awesome!
Now does it matter what bootloader you're on for this?
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.
Do these videos have audio? kinda hard to follow... or it just my laptop?
Restore
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
PwnCakes193 said:
Totally forgot about this, I'll have NBD included in my next kernel so this can work
Click to expand...
Click to collapse
I will add a link to your kernel in first message when it becomes compatible with qcow2 support.
vbetts said:
Now does it matter what bootloader you're on for this?
Click to expand...
Click to collapse
There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )
stanguay said:
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
Click to expand...
Click to collapse
As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?
Philippe,
ubuntu touch trusty in progress
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I remember the last time someone built Ubuntu Touch to the d2att S3, but we ran into the same issues as you previously mentioned. Will there ever be a way to get the data to work?
codemonkey98 said:
Will there ever be a way to get the data to work?
Click to expand...
Click to collapse
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Phil_Suz said:
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Click to expand...
Click to collapse
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
shekinahsmoke said:
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
Click to expand...
Click to collapse
Hi shekinahsmoke, no it is not necessary at all. It's better to install all zip in one shot, but I did this demo to show that you can come back to multiboot, select an already created rom and apply another zip ( gapps in this example ) even after first installation.
codemonkey98 said:
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
Click to expand...
Click to collapse
rani9990 said:
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Phil_Suz said:
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Click to expand...
Click to collapse
I'm glad to hear. I appreciate you shedding some light towards us with Ubuntu Touch and your support for multiboot. :good:
Hi All,
Multiboot v2.1 is now ready on same download link ( http://www.androidfilehost.com/?w=files&flid=12801 )
This version add support for unbutu touch 14.04.
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I would love to try your touch port I have been using your recoveries for a few weeks now and just flash the touch wip Rom that is on the site but to have a simi-working port to play with would be awesome.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
WELCOME
Miustone is Presenting
The XperiStock ROM. Based on the latest Xperia Firmwares. Optimized with Love.
The XperiStock ROM Contains 8 Years of research and testing on Android. Aiming on a open and Pixel like Expierence, is the XperiStock ROM coming with the barely minimum of Apps. Including Google App replacements without loosing the best Features of the Xperia Firmwares. Optimized on many Edges under the Hood, but still delivering the default Stock Feel and Look of the Original Firmwares. If You want to know what's included, check out the Features List..
FEATURES
Rooted by Magisk
Busybox included
DRM Fix included
Fully De-Odexed
Heavily Debloated
Google App Replacements
DM-Verity disabled
Forced Encryption disabled
SafetyNet Passing
All default Stock Features
Optimized booting Times
Optimized Performance
Optimized UI Handling
Optimized Audio Handling
Pixel Exclusive Features
Credits to:
-sToRm// (DRM FIX)
-shoey63 (DRM FIX)
-SuperR. (KITCHEN)
XDA:DevDB Information
XperiStock ROM, ROM for the Sony Xperia XZ Premium
Contributors
Miustone, Miustone, Miustone, Shoey63
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: .145 Custom DE (G8414)
Version Information
Status: Testing
Current Stable Version: V1848
Stable Release Date: 2018-04-08
Created 2018-04-07
Last Updated 2018-04-08
Infos:
Instructions
-(Coming from AOSP or older Firmwares)
-Flash the latest Official Firmware for Your Device
-Boot into the System (Setup Wizard)
-Flash TWRP with Fastboot
-(Coming from latest Stock Firmwares)
-Full Wipe (Data, System and Caches)
-Flash XperiStock ROM
-(G8142 Users have to replace the Kernel)
Changelog
V1
-Based on 47.1.A.12.145
-Deodexed
-DM-Verity Disabled
-Forced Encryption Disabled
-Zipaligned
-Signed
V1848
-Changed Installer UI Print
-Changed Version Naming (Dates)
-Changed default DPI to 400 (From 480)
-Optimized ROM Installer Script
-Optimized ROM Installer Directions
-Added first Optimizations from the Snappatch
-Removed Third Party Bloat Apps
-Removed many SONY Apps
-Removed Stock Google Apps
-Added Optimized Super GApps Pack
-Added Android for Work Support
-Added First Optimizations (W.i.P.)
-Added Magisk Root
-Added Rootless Pixel Launcher
-Added "DRM Fix"
-Added Shoey63's Kernel (Thank him)
-Reduced ROM Size by ~500Mb
-Removed Bootanimation
-Disabled Bootanimation Preloading
-Disabled Bootanimation
-Added Busybox
-Added Pixel Features (First Set)
-Added Freeform Windows (Recents)
V18410 (Soon)
-Merged more Snappatch Content
-Added more Pixel Features
-Added new Xperia Assistentin
-Added new Xperia Camera App
-Added better Microphone Handling
-Added Security Handling Optimizations
-Added Audio Handling Optimizations (Output)
-Added Rendering Handling Optimizations
-Added better Camera Image Quality Profiles
-Added better Camera Audio Quality Profiles
More coming soon...
Download:
GOOGLE DRIVE
Missing Apps?
Check the Play Store for Your Favorite Apps or visit apkmirror.com
Hello Folks! Looking forward to support My new XZ Premium with great Work! Stock has changed over the Years and there is a lot to learn again. So please let Me know if You have something to contribute like a Camera /DRM FIx or something like Support for more Variants of one Phone Model...
Hope You will enjoy what i deliver! Happy flashing :highfive:
wow great job! cant wait to try it out
madshark2009 said:
wow great job! cant wait to try it out
Click to expand...
Click to collapse
Added a Changelog If You prefer to have something special should You just wait for V2. V1 is very basically to proof that i'm able to produce working Bases for My Work. Looks like i stop doing My Snappatch and switch back to Stock ROM Creations again. To bad that AROMA isn't working on the XZ Premium, otherwise would i include Tons of Options...
Maybe can we get that also fixed in the Future. First Things first
Miustone said:
Added a Changelog If You prefer to have something special should You just wait for V2. V1 is very basically to proof that i'm able to produce working Bases for My Work. Looks like i stop doing My Snappatch and switch back to Stock ROM Creations again. To bad that AROMA isn't working on the XZ Premium, otherwise would i include Tons of Options...
Maybe can we get that also fixed in the Future. First Things first
Click to expand...
Click to collapse
I like how you work! Very orginized and promising
So camera is not working at all? Not even on alternative apps?
madshark2009 said:
I like how you work! Very orginized and promising
So camera is not working at all? Not even on alternative apps?
Click to expand...
Click to collapse
Glad to hear that You appreciate that! Hope i can provide a clean and good Working ROM over the next Years, with Useful additions and Optimizations. Something You will never see from Me are old, obsolete or non working "Tweaks", copied Audio Mods or included Xposed. That's stuff Users can add if they Think they miss it...
Quality over Quantity!
And to answer Your Question: No, it's not working at all. You can open it and all that but taking Pictures outputs Green Results (Think the Noise Reductions has a mailfunction without DRM)
XperiFix would be the Way to get around this, but it doesn't allow or support newer Firmwares (As long as the Master isn't giving it Free). I will try to find a Fix for this without the need for a PC, but for now do we have to wait or to use the following Way)
You can:
-Flash XperiFix supported Firmware to Your Device
-Boot into the System (Skip the Setup)
-Shutdown
-Flash the XperiStock ROM (Don't boot the System)
-Use XperiFix
And that should be it. Can't say if this really works but i heard it does...
I go to home sooner and test your rom it's stock yeah just flash able I'm fix camera by flashing that old kernel and drm fix so easy but I think the stock kernel is super fast and this is just fast(old kernel).
Blackghosthm said:
I go to home sooner and test your rom it's stock yeah just flash able I'm fix camera by flashing that old kernel and drm fix so easy but I think the stock kernel is super fast and this is just fast(old kernel).
Click to expand...
Click to collapse
Wow, thank You for letting Us know! We know it's a old Kernel, but better as a non working Camera for now! BTW. Is the Kernel for the Dual SIM Version only or also for the G8414 Version!?
EDIT1: Next ROM comes soon! Changelog grows :angel:
EDIT2: Testing some last Changes. Think i'll upload the next ROM Version very soon...
Maybe you could have a look at getting this working on oreo for v2. Used to work fine on nougat. The font tab is added to settings, but hangs then reboots when you press it.
https://forum.xda-developers.com/crossdevice-dev/sony/root-font-selector-igor-eisberg-t3367521/page1
Miustone said:
Wow, thank You for letting Us know! We know it's a old Kernel, but better as a non working Camera for now! BTW. Is the Kernel for the Dual SIM Version only or also for the G8414 Version!?
EDIT1: Next ROM comes soon! Changelog grows :angel:
EDIT2: Testing some last Changes. Think i'll upload the next ROM Version very soon...
Click to expand...
Click to collapse
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working? AndroPlus Kernel V11 Cause WiFi and data settings to be invalid,as my test on g8142.
oneheart said:
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working?
Click to expand...
Click to collapse
Xposed isnt working, since the last two Sony updates.
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
@Miustone
Here is a patched services.jar from .145 firmware, using the method from here.
https://forum.xda-developers.com/showpost.php?p=68001053&postcount=2
Beetle84 said:
Maybe you could have a look at getting this working on oreo for v2. Used to work fine on nougat. The font tab is added to settings, but hangs then reboots when you press it.
https://forum.xda-developers.com/crossdevice-dev/sony/root-font-selector-igor-eisberg-t3367521/page1
Click to expand...
Click to collapse
Interesting, i will take a look! Thanks for sharing!
oneheart said:
does the xposed working?
---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------
does the xposed working? AndroPlus Kernel V11 Cause WiFi and data settings to be invalid,as my test on g8142.
Click to expand...
Click to collapse
I'm not sure if i go with AndroPlus Kernel on the Release since someone told Me he is working on a new Kernel including the DRM Fix. At least is My Camera working with this Kernel (G8414) besided no other Bugs (Except for Lags after flashing but that is gone now). Hope i can deliver a ROM that works also for Your Device well...
Beetle84 said:
Xposed isnt working, since the last two Sony updates.
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
@Miustone
Here is a patched services.jar from .145 firmware, using the method from here.
https://forum.xda-developers.com/showpost.php?p=68001053&postcount=2
Click to expand...
Click to collapse
Thanks for Your efforts! I'm not going to include Xposed by default since not everyone is using it (Including Me), but i could include Your Edited Services.jar for Xposed Users if it helps!?
EDIT: Is the Services Jar comming with disabled Signature Verification? If so, should it be easy to include the Font Selector from the Link up here...
I'm currently almost done with the new Version. Just waiting for the Kernel and i'm about to Optimize the Camera Config (Trying to enable 4K Recording on the Front Cam besides 1080p @60fps and such). Maybe do i find some more Things to play with...
I'm also thinking the Audio Quality could be better at all. I will also work on this without using any Pseudo Audio Mods or such...
Can't wait to upload the next ROM. I was also thinking about another Name (XperiStock was a just quick Idea for the Release). How Sounds PiXeria? Think it would fit well to the Pixel Look the next ROM comes with... Let Me know!
BR
Miustone said:
Interesting, i will take a look! Thanks for sharing!
I'm not sure if i go with AndroPlus Kernel on the Release since someone told Me he is working on a new Kernel including the DRM Fix. At least is My Camera working with this Kernel (G8414) besided no other Bugs (Except for Lags after flashing but that is gone now). Hope i can deliver a ROM that works also for Your Device well...
Thanks for Your efforts! I'm not going to include Xposed by default since not everyone is using it (Including Me), but i could include Your Edited Services.jar for Xposed Users if it helps!?
I'm currently almost done with the new Version. Just waiting for the Kernel and i'm about to Optimize the Camera Config (Trying to enable 4K Recording on the Front Cam besides 1080p @60fps and such). Maybe do i find some more Things to play with...
I'm also thinking the Audio Quality could be better at all. I will also work on this without using any Pseudo Audio Mods or such...
Can't wait to upload the next ROM. I was also thinking about another Name (XperiStock was a just quick Idea for the Release). How Sounds PiXeria? Think it would fit well to the Pixel Look the next ROM comes with... Let Me know!
BR
Click to expand...
Click to collapse
hey can you also see if you can enable native 4k screen? or 120hz? or recording [email protected]?
PiXeria sounds nice , you can try XpiXel, or any unrelated name that sounds strong, like venum or cobra or viper like some other rom names
but PiXeria sounds nice too.
@Miustone
I notice you are directing users to use one of my old kernel repacks with this rom, and that's fine but it's time for an an update!
Here is my repack of the latest .145 stock kernel for G8141 single sim https://www.androidfilehost.com/?fid=890129502657596596
I assume you have baked the drm fix libs into the rom, but if not , here is sToRm//'s drm fix zip https://www.androidfilehost.com/?fid=673956719939833470 (zips tested by me and verified as working on pure stock 47.1.A.12.145 rom)
- Camera with no green pictures working straight out of the box.
- Safetynet passes without flashing Magisk.
- DMverity disabled.
- Patched to eliminate lag on deodexed roms. (Works fine on odexed as well)
- Flash kernel.zip and drmfix.zip in TWRP recovery and you are done.
madshark2009 said:
hey can you also see if you can enable native 4k screen? or 120hz? or recording [email protected]?
PiXeria sounds nice , you can try XpiXel, or any unrelated name that sounds strong, like venum or cobra or viper like some other rom names
but PiXeria sounds nice too.
Click to expand...
Click to collapse
Great Ideas! XperiStock sounds so copied for Me
I will think about it till the Third Release. Well, native 4K shouldn't be the Problem, but 120Hz for sure. Maybe can we do more on Stock when the 120Hz Option on AOSP finally works (To see how it works). 4K on 60FPS with Back Cam on Stock is in the testing Phase right now...
Let's see what i can manage to do in the next Time, but i'm already really satisfied with the Quality of Stock. It's for sure beyond the most Flagship when it comes to Quality and Features...
Only the Audio could be really better like said before. Think i can make this baby a lot better in this view. There is a lot to merge from My Snappatch, and i'm finally not longer handicapped by the DAC in My Axon 7 (Snapdragon ftw!)
Hi Miu stone I'm glad to see you working on camera and audio (specially camera because no one does) just don't delete xreality, I think native 4k can be good, but native 2k can be great because dialer doesn't work on 4k, phone goes hot on 4k,battery drain faster, and phone getting slow on games.
Hope you adding cool features to it and thanks for great work.
How's xperibeast for name. ?
Blackghosthm said:
Hi Miu stone I'm glad to see you working on camera and audio (specially camera because no one does) just don't delete xreality, I think native 4k can be good, but native 2k can be great because dialer doesn't work on 4k, phone goes hot on 4k,battery drain faster, and phone getting slow on games.
Hope you adding cool features to it and thanks for great work.
How's xperibeast for name.
Click to expand...
Click to collapse
well at least there should be the option of switching you know? when you gaming you can simply switch to 1080 or 2k and when you just browsing, instagram, youtube , chrome, etc its nice to have 4k as an option to enable, plus there is an alternative phone app that works with 4k (the reason it doesnt work in the first place is because some apps arent adjusting to the VIRTUAL density but if it was physical it wouldnt cause such problems) I tried it and it works perfectly, and dont worry, i dont think native 4k is as much power requiring as virtual so overheating isnt gonna be a big issue like on virtual 4k using adb commands.
Miustone said:
Great Ideas! XperiStock sounds so copied for Me
I will think about it till the Third Release. Well, native 4K shouldn't be the Problem, but 120Hz for sure. Maybe can we do more on Stock when the 120Hz Option on AOSP finally works (To see how it works). 4K on 60FPS with Back Cam on Stock is in the testing Phase right now...
Let's see what i can manage to do in the next Time, but i'm already really satisfied with the Quality of Stock. It's for sure beyond the most Flagship when it comes to Quality and Features...
Only the Audio could be really better like said before. Think i can make this baby a lot better in this view. There is a lot to merge from My Snappatch, and i'm finally not longer handicapped by the DAC in My Axon 7 (Snapdragon ftw!)
Click to expand...
Click to collapse
hope the [email protected] work, and if 120hz is a problem how about 4k option? is it possible you might consider it in the next version?
and yah actually the sound quality on the device is superb and on a high level compared to other devices when it comes to everything about sound engineering, I actually work in the music field and I work a lot with sound stuff and i can tell you it delivers pretty good accuracy and has a high dynamic range of frequencies and its very rich, the only issue here is that its very low, could be to maintain really good quality sound, but I would rather a higher volume even if it means a little less quality (unless if it starts to distort in that case id rather keep it low)
and again, on be half of the XZP community I cant thank you enough for you efforts and energy to get this baby up and running on the level it should be
keep it bro much love
shoey63 said:
@Miustone
I notice you are directing users to use one of my old kernel repacks with this rom, and that's fine but it's time for an an update!
Here is my repack of the latest .145 stock kernel for G8141 single sim https://www.androidfilehost.com/?fid=890129502657596596
I assume you have baked the drm fix libs into the rom, but if not , here is sToRm//'s drm fix zip https://www.androidfilehost.com/?fid=673956719939833470 (zips tested by me and verified as working on pure stock 47.1.A.12.145 rom)
- Camera with no green pictures working straight out of the box.
- Safetynet passes without flashing Magisk.
- DMverity disabled.
- Patched to eliminate lag on deodexed roms. (Works fine on odexed as well)
- Flash kernel.zip and drmfix.zip in TWRP recovery and you are done.
Click to expand...
Click to collapse
True Hero! Thank You very much for Your Contribution! I just got the DRM working with My ROM and the right Kernel, but it's really Time for a Update. Next Version of My ROM will come with Your Kernel! Also great to hear that there will be no Lags and to have also other Additions like DMverity disabled besided passing SafetyNet!
I could with AROMA create a lil Pack containing the DRM Fix, Magisk (Or no Magisk) and Your Kernel, but sadly is our TWRP buggy and doesn't works with AROMA right now. But when People want to flash My ROM with a working Camera and without Magisk do they just have to remove the Magisk ZIP out of the ROM and all will be fine. Really great!
Buy this Man a Beer! Next ROM Update will come in the next Hours with new Kernel <3
Hello there!
this mod will make an originally not compatible kernel with miui (Like, for example, Okita) compatible! And everything works! (Camera, FoD, Audio... )
it uses AOSP drivers to interact with the kernel, and make everything work. It's based on the work of a guy who originally shared in the Global general group for MI9SE. I simply updated it to support MIUI 11.
INSTALLATION:
- Install the mod via Magisk
- Reboot to TWRP
- Install your custom kernel (Kowalski Kernel confirmed to work)
- Wipe cache/dalvik for security reason
- Reboot
- Enjoy
Let me know if it works for you! Have a nice day!
Changelog:
V1 - First release of the mod
V2 - Rebased on latest Bliss, Supports latest Q MIUI roms
Known issues:
- Lantern app doesn't work (Flash through toggle works though...)
- Nothing else here...
if you install another kernel for MIUI, will it be possible to install another file system on MIUI& e.g. F2FS?
stupid question, what does the mod do?
Grahaman27 said:
stupid question, what does the mod do?
Click to expand...
Click to collapse
android 10 support?
how create backup stock kernel?
backup boot and dtbo.
Doesn't work music and mobile data after installing this mod and regular reboot
Does anyone uses it with Kowalski kernel and MiuiEu 11.2 dev?
Hi guys!
Just updated the lib to support latest MIUI Q Roms.
IT'S NOT COMPATIBLE WITH PIE!
Just to warn you. Has been tested successfully on RevOS by an user that I sent it, so you should be good to go!
Enjoy
Zero_One said:
Hi guys!
... tested successfully on RevOS...
Enjoy
Click to expand...
Click to collapse
Kowalski? Which version?
Zero_One said:
Hi guys!
Just updated the lib to support latest MIUI Q Roms.
IT'S NOT COMPATIBLE WITH PIE!
Just to warn you. Has been tested successfully on RevOS by an user that I sent it, so you should be good to go!
Enjoy
Click to expand...
Click to collapse
Can you confirm which build of Kowalski that works? i'm using latest Rev OS and tried new lib with latest Kowalski and got reboot after got into homescreen
zenaufa said:
Can you confirm which build of Kowalski that works? i'm using latest Rev OS and tried new lib with latest Kowalski and got reboot after got into homescreen
Click to expand...
Click to collapse
My tester tried the faust' one. I think latest r2.0.1.0 should work just fine. If you didn't used either of the one i just told you, test them out and let me know!
does it stil works?