Related
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy Nexus Verizon (toro)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
There may be a newer build here as well: (I'm putting up a .zip and .img variety for each build) :: Note: I've got no device to test this build with (the latest one), so I hope it works. It was just built using latest source.
6.55.0 - libtouch_gui 1.40
- support faster transfers through USB storage for voldmanaged devices
- fix compiling for devices with custom recovery key or ui files
- add option to disable md5 from edify restore_rom command line
- this fixes restore of custom roms
6.50.6 -
- fix potential failure for TWRP backups (cause scan_mouned_volumes() not called)
- loki_recovery code clean up
- fix potential failure to reboot when checking config file
- never confirm wipe in ors scripts
- always show text in sideload mode
- support wipe_cache and clear_display edify script commands
6.41.6 - Stable & perhaps Final
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable - Change log and download
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
6.40.6 - Stable - Change log and download:
- immediate error on missing needed flags for touch version
- add function to find a file name in a given path
- libtouch_gui 1.21:
* auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
6.40.1 -
- proper libtar implementation: support backup/restore of selinux context inside archive
- dedupe: support backup/restore of selinux context by @Chenglu
- libtouch_gui 1.20: support custom key files (BOARD_CUSTOM_RECOVERY_KEYMAPPING)
- v6.55.0: toro: img: http://d-h.st/CNW and zip: http://d-h.st/QDe
- v6.50.6: toro: img: http://d-h.st/SWU and zip: http://d-h.st/NqP
- v6.41.6: toro: img: http://d-h.st/SrA and zip: http://d-h.st/l9w
- v6.41.5: toro: img: http://d-h.st/NpH and zip: http://d-h.st/2Dp
- v6.40.6: toro: img: http://d-h.st/prG and zip: http://d-h.st/9i1
- v6.40.1: toro: img: http://d-h.st/i4I and zip: http://d-h.st/ZY0
Click to expand...
Click to collapse
XDA:DevDB Information
[toro][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Verizon Galaxy Nexus
Contributors
Phil3759, hachamacha
Version Information
Status: Stable
Created 2014-05-06
Last Updated 2014-08-14
Removed warnings since it was tested on maguro and reported to be ok
Since it is just a repack, no issues are expected here
So if I read the link correctly, this has the ability to switch where your sd partition is located to easily switch to jb 4.1? If it is that would be sweet
nitsua98 said:
So if I read the link correctly, this has the ability to switch where your sd partition is located to easily switch to jb 4.1? If it is that would be sweet
Click to expand...
Click to collapse
Yes, you can set it to use /data/media/0 or /data/media for sdcard
Needs a reboot to take effect
OK so to flash this I would do fastboot flash recovery in adb right? Because the file is a .img and in your linked post it just has instructions for zip and the Odin files
wooohoooo.... thanks it's really cool
sent from my sexy Nexy
nitsua98 said:
OK so to flash this I would do fastboot flash recovery in adb right? Because the file is a .img and in your linked post it just has instructions for zip and the Odin files
Click to expand...
Click to collapse
Yep, fastboot. I used galaxy nexus toolkit, worked like a charm!:good:
Does screen shot work with swipe left?
Sent from my GT-I9100 using Tapatalk 2
Phil, I put this in a flashable zip if you want it.
Edit: tested it on my phone already.
very nice. I think ill be using this from now on.
Very nice UI!
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
Phil, I put this in a flashable zip if you want it.
Edit: tested it on my phone already.
very nice. I think ill be using this from now on.
Click to expand...
Click to collapse
I want it
Sent From My Miui Powered Galaxy Nexus
Esteway.619 said:
I want it
Sent From My Miui Powered Galaxy Nexus
Click to expand...
Click to collapse
+1 me too please
Sent from my Galaxy Nexus using xda app-developers app
mysterysauce said:
+1 me too please
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Me three, please.
I will be releasing the new version + zip installer
Just wait as devhost is down
Phil gave me the OK for now. I'll take this down as soon as dev-host is back up and he gets his links up.
Phil has links in the op now.
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
so let me get this straight, i'm on TWRP and if i used this new CWM that Phil made, i can still use my TWRP backups and actually make backups like TWRP does?
t1.8matt said:
so let me get this straight, i'm on TWRP and if i used this new CWM that Phil made, i can still use my TWRP backups and actually make backups like TWRP does?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
nice, thanks for the answer. will be giving this a go. thanks Phil.
This recovery is so awesome and elegant I love it. Thanks Phil
Sent From My Miui Powered Galaxy Nexus
v5.03.7
5.03.7 (19.05.2013)
- merge cm-10.1 changes: add getprop
- HTC One (m7) support
- i9505 fix graphics, date and cache/wipe issues (Big thanks to Chenglu for that)
- Samsung Nexus S (crespo) and Nexus S 4G (crespo4g) support
5.03.2 (16.05.2013)
- fix scroll down on touch issue when in double tap and highlight only modes
- support Galaxy Nexus GSM (maguro), Verizon (toro) and Sprint (toroplus), i9500 and i9505 Canada/Bell (jfltecan) and T-mobile (jfltetmo)
- merge cm-10.1 changes: add getprop
Click to expand...
Click to collapse
Download from link in OP
This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).
If you consider to thank me, please also consider to thank him http://forum.xda-developers.com/showthread.php?t=1927852
This kernel only supports roms of android version 4.3.x (sammy and aosp) and 4.4.x!
You can dualboot any of those roms
if you were using this kernel on aosp based roms, and want to use another kernel, you need to reflash the rom, of course without any wipe, it's just to restore modified files
Features (changes compared to Perseus):
- merges samsung open source update12
- dual sound engine
- compiled with linaro gcc 4.8.3
- updated Linux Kernel base to 3.0.101
- updated block subsystem (i/o schedulers) to linux 3.4
- updated memory management subsystem to linux 3.4
- partial updated kernel main system to linux 3.4 (current work in progress)
- zram, zsmalloc and lowmemorykiller updated from 3.9
- DevilQ cpu governor (default)
- fiops v2 i/o scheduler
- working for Aosp and Sammy at once (Big thx to Gokhanmoral for making this possible)
- Portet Ezekeel's Touchwake Feature (from nexus s)
- Oc up to 2.0 Ghz
- Backport from Linux 3.5 smp driver parts
- Wifi driver updated from note3
- backported zswap from linux 3.13 (this replaces zram now)
- backported cpu-boost driver
- possibility to set high/low power mode for wifi when screen is off
- LulzactiveQ cpu governor (from siyahkernel, thx again to Gokhanmoral)
- Hotplug Cpu Governor
- Proportional Rate Reduction for TCP
http://kernelnewbies.org/Linux_3.2#head-1c3e71416a9fdc2f59c1c251a97963f165302b6e
- improve memcopy/memmove
- Using Voodoo Sound and Boeffla Sound
- LED Control by yank555-lu
- ExFat support (thx to samsung for opensourcing the driver)
if your rom is based off PAC, Bam, Fusion, ... :
IMPORTANT: As per notice of 01.11.2013, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you will receive a boot loop. Do not cry about this here but advise your Custom rom cooker to fix this. I will not change this ever again.
The most prominent custom kernels for CM will follow the same approach (aligned between Yank555, Googy, LordBoeffla, Psndna, Temasek and me).
So please do pass this message along to your favorite ROM devs.
If they don't fix their rom, it won't be compatible with custom kernels any more!
Kernel app http://forum.xda-developers.com/showthread.php?p=41346443#post41346443
How to post bugs:
http://forum.xda-developers.com/showthread.php?t=1520508
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Dualboot Faq:
For more detailed instructions, please take a look at this thread from RichMd (thank you for it):
Dualboot Faq thread
Important: if you want to use this kernel for dualboot, i highly recommend flashing my recovery as well.
General information about the recovery:
dualboot menu.
in this menu you can:
* create the secondary system partition (needed to be run once, if you want to install a second rom)
Install-zip menu:
you'll notice there is a new menu, where to select what you want to flash.
if you select kernel, rom or recovery, the zip gets installed as it is.
if you select zipt to pri./sec. filesystem, it is selfexplanary
if you select rom to secondary fs, the zip gets modified to install to the sec. fs. IF YOU WANT TO INSTALL IT TO PRIMARY FS LATER SOME TIME, YOU NEED TO REDOWNLOAD THE FILE!
if you select rom to primary filesystem, it gets installed there, and you can use the same zip later again.
How to install a second rom:
make sure you have already created ssecondary system partition! if not, go to dualboot menu and create it now (this may take some minutes)
The savest way is the way by using nandroids: if you don't have a nandroid already, create one now. Then just select your backup, and restore it to secondary filesystem.
you now should already be able to boot into primary or secondary rom (which are both the same now).
now you can install any other rom as primary.
if you want to install a new rom directly as secondary,
make sure there are no spaces in the filename!,
then just go to install zip. you'll notice there's a new menu at some point.
in this menu you can select where you want to install, and what type of file it is.
if you choose rom to sec. fs, your zip files itself gets modified to be installed to secondary fs. this may take a minute, because the files needs to get zipped again. Imporant: this file is permanently modified. if you think you need it later again, you should redownload it, because the modified one would always install as secondary.
installing a rom as primary, a zip to primary or zip to secondary fs, does not modify the zip.
Additional information:
roms coming with an aroma installer are hard to handle, as every dev can place own commands into it. It's impossible for me, to take care of every possibility. Because of this, it should be the best method, to flash a rom with aroma installer as primary one (and then move it to secondary, by using the nandroid method, if you want it to be secondary).
Click to expand...
Click to collapse
Many Thanks to:
- RichMD
- Gokhanmoral
- Andreilux
- DAGr8
- simone201
- ptmr3
- Stratosk
- RolloS
- kasper_h
- Philz (for his recovery source, although i had to implement my own touch )
- all the others mentioned in the changelogs
reserved
could someone please upload sammy 4.3 stock kernel? i want to build a seperate kernel for sprint, but i need the stock kernel for extracting some files before. thanks
My links to current devil stuff
New devil recovery with f2fs support for system and cache (data partition to come later). Note you dont need f2fs to use the recovery or kernel but you do need the kernel and recovery to use f2fs. If you convert to f2fs and want to use a different recovery then you must format file systems back to ext4 before changing. Bad things will happen if you do not convert before changing recoveries. Also the rom you are flashing must have an installer script setup for f2fs. I will be updating all my roms to support f2fs when I do their next releases.
Recovery link
https://www.androidfilehost.com/?fid=23622183712470601
MD5sum 1f15bb6c56d1fc65b00c8af188a37cda
Devil tools 1.1.2
https://www.androidfilehost.com/?fid=23622183712470603
MD5sum bcb3e3b4d7ec969b43bd68e47e6b556f
May post a current kernel if approved.
Thank you thank you thank you! Been hoping someone would make us a custom mk4 kernal
Thanks DerTeufel980.... we all really appreciate this.
So I can use this with a Samsung mk4 ROM? I'm on digiblur.
Sent from my SPH-L900 using xda app-developers app
krobinso2295 said:
So I can use this with a Samsung mk4 ROM? I'm on digiblur.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Once it is done.
Sent from my SPH-L900 using XDA Premium 4 mobile app
kernel is up
dualboot coming in the next days. i need to compile my recovery for you...
Sweet!!
Sent from my SPH-L900 using XDA Premium 4 mobile app
So the kernel posted will work on twiz 4.3?
From My Classic 4.3 n2/3
Chaz187 said:
So the kernel posted will work on twiz 4.3?
From My Classic 4.3 n2/3
Click to expand...
Click to collapse
It's in the first post... Working on Android 4.3 and above...
Gesendet von meinem Note II mit Tapatalk 2
DerTeufel1980 said:
It's in the first post... Working on Android 4.3 and above...
Gesendet von meinem Note II mit Tapatalk 2
Click to expand...
Click to collapse
Just flashed and it wont boot past splash screen. Button backlights flash on but that is all. What extra info do ypu need?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Will this work on cm 4.3 4.4 or have to wait for the dual boot
Sent from my SPH-L900 using Tapatalk
It should but it is untested. Dual boot is just a special recovery that allows you to run two roms without flashing or nanding between the two.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Just flashed and it wont boot past splash screen. Button backlights flash on but that is all. What extra info do ypu need?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does the screen turn black after splash? Or does it sit with my kernel logo all the time?
Is adb shell working?
sliverr7x said:
Will this work on cm 4.3 4.4 or have to wait for the dual boot
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
It should work already... But as written above, it does not work on sammy currently.
Please report if there are same issues with cm.
Gesendet von meinem Note II mit Tapatalk 2
OK I just read about pac roms so I see It won't work according to the op
Sent from my SPH-L900 using Tapatalk
Can't wait for this to be working.... will it support stweaks
From My Classic 4.3 n2/3
Chaz187 said:
Can't wait for this to be working.... will it support stweaks
From My Classic 4.3 n2/3
Click to expand...
Click to collapse
The older version stweaks workes sort of but there is a devil tools in the market that works.
DerTeufel1980 said:
Does the screen turn black after splash? Or does it sit with my kernel logo all the time?
Is adb shell working?
It should work already... But as written above, it does not work on sammy currently.
Please report if there are same issues with cm.
Gesendet von meinem Note II mit Tapatalk 2
Click to expand...
Click to collapse
Sits on devil logo. Not sure about adb not around pc. Anything specific just list it and will try later.
Sent from my SPH-L900 using XDA Premium 4 mobile app
I would need someone to try on cm11 or omnirom (generally any aosp rom), to know if the issue is caused by sammy initram files, or the main init file.
Gesendet von meinem Note II mit Tapatalk 2
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
[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
[updated 20140411]
version v2.11
ubuntu touch support ( http://www.androidfilehost.com/?w=files&flid=13392 )
Important recommandations and details of working features can be found in this thread : http://forum.xda-developers.com/showthread.php?t=2702692
[updated 20140316]
version v2.0
qcow2 support ( https://www.youtube.com/watch?v=LGoTb0u5oX0 )
[updated 20140311]
version v1.2
migration to twrp2.7.0.0
sizing of system/data/cache now possible
real internal/external sd mounted ( respectively in /storage/intsdcard and /storage/extsdcard )
new way to boot roms
new link to download : http://www.androidfilehost.com/?w=files&flid=12801
Hi all,
WARNING : This recovery image has not yet been tested on your device. So be very carefull and wait report of power users
This recovery image is based on twrp with multiboot feature on Galaxy S3.
I did it on my Bell model (d2att) but has ben reporter to work also on Tmobile model (d2tmo).
Original post and recommendations are here : http://forum.xda-developers.com/showthread.php?t=2577211
If you want to test it on your device, please read carefully original post and follow all warnings.
Download link : http://www.androidfilehost.com/?w=files&flid=12801
Thank's for your feedbacks.
Philippe,
Nice...I was actually looking into doing this when I came across it in the m7 forum
didnt have d2spr on filename on xda app. Does on taptalk.
Hi,
Not sure if this multiboot feature is used on your model.
If you want to try new version, it is here : http://www.androidfilehost.com/?w=files&flid=12801. Change log in first message.
Philippe,
Testing now, thanks for the hard work :thumbup:
Been meaning to go back to TWRP and this makes it all that much sweeter :beer:
@Phil_Suz
It seems like you uploaded the wrong file? The d2spr folder contains a zip for the d2tmo, and that file matches the file in the d2tmo folder...
http://www.androidfilehost.com/?fid=23329332407578047
CNexus said:
Testing now, thanks for the hard work :thumbup:
Been meaning to go back to TWRP and this makes it all that much sweeter :beer:
@Phil_Suz
It seems like you uploaded the wrong file? The d2spr folder contains a zip for the d2tmo, and that file matches the file in the d2tmo folder...
http://www.androidfilehost.com/?fid=23329332407578047
Click to expand...
Click to collapse
Hi CNexus, you are wright, wrong file. thank's for the information. Just uploaded the good one.
Philippe,
Thanks for the quick response, downloading now
Working great here. Have 3 roms installed (including internal)
CNexus said:
Working great here. Have 3 roms installed (including internal)
Click to expand...
Click to collapse
Hi CNexus, thank's to give feedback :good:
For All,
Version v2.0 is now ready with qcow2 support.
I opened a dev thread in d2att sub to continue discussion about this projet and to start to speak about how it works and how to use this new feature. If you wish, you can go there now. http://forum.xda-developers.com/showthread.php?t=2684052
Philippe,
@Phil_Suz, you probably already know this, but your modified v2.7.0.0 TWRP for the d2spr fixes the "official" release's problem of not seeing any partitions on some newer S3s.
I was wondering if you would mind if I, or you yourself, whichever you like, post links to here (or you tell me where you'd like the links to point to) in the TWRP and the all recoveries threads since this makes v2.7.0.0 usable for the rest of us who had problems with the official release?
Thank you for this!
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 2/25/2014 and TWRP v2.6.3.0.
roirraW "edor" ehT said:
@Phil_Suz, you probably already know this, but your modified v2.7.0.0 TWRP for the d2spr fixes the "official" release's problem of not seeing any partitions on some newer S3s.
I was wondering if you would mind if I, or you yourself, whichever you like, post links to here (or you tell me where you'd like the links to point to) in the TWRP and the all recoveries threads since this makes v2.7.0.0 usable for the rest of us who had problems with the official release?
Thank you for this!
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 2/25/2014 and TWRP v2.6.3.0.
Click to expand...
Click to collapse
Hi roirraW "edor" ehT,
No I did not know that you had this problem and that this version was working. Yes, you can post link to here but as a temporary solution, I don't manage at all twrp code, my add-on does not touch twrp code so it's a bit weird that this correct a problem on twrp side.
Philippe,
Phil_Suz said:
Hi roirraW "edor" ehT,
No I did not know that you had this problem and that this version was working. Yes, you can post link to here but as a temporary solution, I don't manage at all twrp code, my add-on does not touch twrp code so it's a bit weird that this correct a problem on twrp side.
Philippe,
Click to expand...
Click to collapse
Absolutely, I won't expect you to provide anything and I will explain and encourage others not to either. Thanks again for this. I love the idea of multi-boot although for myself I probably won't be curious enough to try it until a new x.x version of Android drops and won't be provided in a TouchWiz version, so just guessing 4.5 or 5.0 although I hope we get one of those too.
Kudos!
Edit: Do you take donations?
Oh this is funky
Can this be used on the s4?
Sent from my SPH-L720 using xda app-developers app
fabzbear said:
Can this be used on the s4?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
No. One would need to be built for the s4 specifically.
Hi All,
Multiboot v2.11 is now ready.
This version adds feature to multiboot ubuntu touch 14.04 on galaxy S3 ( img format only, external sdcard strongly recommanded).
I did this ubuntu port on my d2att model but it could possibly work on your device.
If you want to test, I prepared a d2lte test version (0.13) here : http://www.androidfilehost.com/?fid=23329332407583872
Important recommandations and details of working features can be found in this thread : http://forum.xda-developers.com/showthread.php?t=2702692
multiboot v2.11 is at same usual location.
Note : Please let a feedback message in this tread or original one if you tested it. if you report that it is not working, I will remove download link.
Philippe,
As cell features don't seem to work on verizon devices, I removed lte version and created specific versions.
Maybe this will fix cell problems ( because working well on d2att )
Download links are there : http://www.androidfilehost.com/?w=files&flid=13392
Philippe,
S3 TWRP back in business
Thought my new "Best Buy Black Friday" Sprint special was not going to be as cool as it could be since I couldn't get 2.7 TWRP working - but thanks to your modded version I am back in business.
Been running just pac rom for so long forgot there were other sections to this forum. Noticed this today thanks for the work it's nice being able to preview and have multiple roms for ultimate compatibility. Running 5.0 and 4.4 which really helps the transition in my case.
I've been trying this for the past couple days. I can't get it to boot into Ubuntu or any 5.0 ROM. Ubuntu just stays on the boot screen. 5.0 Roms hang while installing.
Sent from my 306SH
First things first.
***I AM NOT BY ANY MEANS an ANDROID or C DEV*** in fact I am a QA however I do have development experience in other languages.
That being said I do own and daily use a SM-G925W8 and this is currently very stable, now onto the details.
This is a port/merge of AndreiLux's Perseus7420 Kernel for the north american s6 Edge.
I did not write this Kernel, all I did was adapt the kernel from the G920F to the G925W8 version.
more specifically I merged the changes present from G920F -> G925F and applied them to the source code from G925W8
then merged that into AndreiLux's ref-3.10 branch https://github.com/AndreiLux/ref-3.10.
Built the kernel, applied the same ramdisk changes that AndreiLux's kernel has and repacked the boot.img
So here you go.
The Perseus7420 kernel that was previously only available for the non edge F variant is now available to use on the canadian variant.
I have tested it all day and this thing is very very stable.
What works:
Call Audio (w8/t have a secondary sound chip ES705 which needs to be explicitly enabled in the defconfig)
Everything else AndreiLux implemented, including full voltage control for all cpu cores,gpu,memory,internal busses please see his change log here: https://github.com/AndreiLux/ref-3.10/releases
What doesnt work:
-nothing?
-you tell me
-still testing
-****I have no idea if this actually works on SM-G925T but it verymuch should... I only have the W8 variant***
I will attempt to keep this up to date and merge in any new changes Andrei releases's as this phone is my dd and I like awesome battery life and stability.
Please note. DO NOT FLASH THIS zip!!!! YOU MUST EXTRACT IT
This image file must be flashed with either:
1) dd if=/path_to_image/boot.img of=/dev/block/sda# <- your boot sector
2) or in twrp you can flash an image instead of a zip by clicking images in the bottom right corner of twrp, then selecting boot.img then the boot radio box before hitting flash.
3) flashify
Updated kernel, can boot s6E+ rom, fixed call audio, now this is a flashable zip.
in all cases backup your current boot image first.
and of course im not liable for anything you break.
thanks for checking out my merge of AndreiLux's kick ass kernel
gundal
of course special thanks to AndreiLux for authoring a lot of these awesome changes and give us this wonderful kernel.
1st reserve
2nd reserve
3rd reserve
4th
Will try it out brother... thanks for the contribution
Trying now
---------- Post added at 05:58 AM ---------- Previous post was at 05:51 AM ----------
Booted on note 5 port.
No call audio even after flashing fix. Had to switch. Kernel is great though so far
really no call audio? and you are g925w8 or T? @ktetreault14
gundal said:
really no call audio? and you are g925w8 or T? @ktetreault14
Click to expand...
Click to collapse
G925T. And S6E+ rom located in Galaxy S6 Edge forums
ktetreault14 said:
G925T. And S6E+ rom located in Galaxy S6 Edge forums
Click to expand...
Click to collapse
Finally got around to installing that e+ rom, it broke my call audio too, merged in some commits from arter and andrei and call audio is back and this is working on Sixperiencev2.0 rom
updated the main thread with a zip file that can now be flashed directly from recovery.
test it out of you can @ktetreault14
re: S6E+ rom
ktetreault14 said:
G925T. And S6E+ rom located in Galaxy S6 Edge forums
Click to expand...
Click to collapse
Are you saying that this rom is compatible with the Galaxy S6+ with the G928T phone?
Have a great day!
@Misterjunky
No I am saying this KERNEL is compatible with the s6E+ rom that was ported to the S6 Edge.
its a rom called SIXPERIENCE v2.0
it will run on Sm-G925T/W8 and this kernel will boot it or normal 5.1.1 for G925
gundal said:
Finally got around to installing that e+ rom, it broke my call audio too, merged in some commits from arter and andrei and call audio is back and this is working on Sixperiencev2.0 rom
updated the main thread with a zip file that can now be flashed directly from recovery.
test it out of you can @ktetreault14
Click to expand...
Click to collapse
Awesome! Downloading now. Any other changes?
Wow, I'm in love with this. For those who don't know, the kernel has an awesome 8-band EQ that can be independently configured for right/left channels as well as the capability to modify the voltage of the CPU, GPU, and various busses. It also allows for fine-grain color calibration. All of the settings are available via Synapse. Installed and working great on my g925t.
Forgot that system and cache are formatted to f2fs. i can't test until new rom comes out when I do clean wipe.
I have a 925T T-Mobile variation edge with S6 edge+ V2.0 Port ROM running with no call issues or any other issues. However I was wondering if your kernel will give me back WiFi Calling or is that not kernel related?
GodfatherSadri said:
I have a 925T T-Mobile variation edge with S6 edge+ V2.0 Port ROM running with no call issues or any other issues. However I was wondering if your kernel will give me back WiFi Calling or is that not kernel related?
Click to expand...
Click to collapse
That will only come back if/when that rom is based on t-mobile firmware.
Sent from my SM-G928F using Tapatalk
Can't get it to boot at all with either philz nor twrp. Won't make it past kernel not enforcing screen. I switched back to ext4 and the Note 5 rom
I'll flash now im on crash v2.1 I'll let you know if it works for me
---------- Post added at 06:39 PM ---------- Previous post was at 06:24 PM ----------
Worked just fine on my 925t on crash rom 2.1 but why are my colors like dull now...... Does this have some type of color fix ? or fade of some type ? lol
call audio works fine