yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] aarush.chaurasiya:
Does it work on all phones devices like samsung ,lenovo
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Currently exactly 120 devices are supported. [MENTION=4277844]chenxiaolong[/MENTION] I think it's a good idea to add a tag Supported Devices in the reserved post and to continuously update it when needed. It would be easy for everyone to see if his device is supported.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Tested to patch and flash devbase 3.8 by alexndr (TW 6 zip) for S5 klte on primary. Flash failed. Dbp r107 saw later that during patch mbtool version was not correct
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Supported Devices [21 Nov 2016]

All 120 supported devices by now. If anyone is interested trying to dual boot first check if yours is between them. If it's not ask for adding support providing a logs. Grab the logs by flashing the GetLogs zip from https://snapshots.noobdev.io/

[color=lightgreen]ARK Benefit A3
ASUS ZenFone 2
DEXP X LTE 4.5
DEXP M LTE 5
Elephone P9000
Google Android One
Android One 2nd Gen - LAVA Pixelv1
Huawei Ascend P7
Huawei Ascend Mate 2
Jiayu S3
Jiayu S3plus
Lenovo K3 Note
Lenovo Vibe Z2 Pro
Lenovo ZUK Z1
Lenovo Vibe P1 Turbo
Lenovo Vibe P1
LG G2
LG G2 (d802)
LG G3
LG G3 S
LG G4
LG G5
LG Optimus L5
LG Optimus L7
LG Optimus L1 II
LG Optimus L3 II
LG Optimus L7 II
Motorola Moto G (2013)
Motorola Moto G 4G (2013)
Motorola Moto G (2014)
Motorola Moto G (2015)
Motorola Moto E (1st gen)
Motorola Moto E 3G (2nd Gen)
Motorola Moto E 4G (2nd Gen)
Motorola Moto X (2013)
Motorola Moto X (2014)
Motorola Moto X Pure Edition
Motorola Droid Turbo
Google/LG Nexus 4
Google/LG Nexus 5
Google/LG Nexus 5X
Google/Motorola Nexus 6
Google/Huawei Nexus 6P
Google/ASUS Nexus 7 (2012 Wifi)
Google/ASUS Nexus 7 (2013 Wifi)
OnePlus One
OnePlus 2
OnePlus 3
OnePlus X
Oukitel K6000 Pro
Pantech Vega Iron 2
Pantech Vega Iron
Quantum GO 4G
Quantum MUV PRO
Samsung Galaxy S 3 Neo (Qcom)
Samsung Galaxy S 3 (Qcom)
Samsung Galaxy S 3 (i9300)
Samsung Galaxy S 3 (i9305)
Samsung Galaxy S 3 Mini
Samsung Galaxy S 4 (Qcom)
Samsung Galaxy S 4 (Exynos)
Samsung Galaxy S 4 LTE-A
Samsung Galaxy S 4 Active (SKT Variant)
Samsung Galaxy S 4 Mini
Samsung Galaxy S 5 (Qcom)
Samsung Galaxy S 5 Mini (Qcom)
Samsung Galaxy S 5 (Exynos)
Samsung Galaxy S 5 Mini LTE (Exynos)
Samsung Galaxy S 5 Broadband LTE-A
Samsung Galaxy S 5 4G+
Samsung Galaxy S 6 Flat/Edge
Samsung Galaxy S 6 Flat/Edge (Sprint)
Samsung Galaxy S 6 Edge+
Samsung Galaxy S 7 Flat/Edge (Exynos)
Samsung Galaxy Note 2
Samsung Galaxy Note 3 (Snapdragon)
Samsung Galaxy Note 3 (Exynos)
Samsung Galaxy Note 3 LTE-A
Samsung Galaxy Note 3 Neo
Samsung Galaxy Note 4 (Snapdragon)
Samsung Galaxy Note 4 (Exynos)
Samsung Galaxy Note 5 (Sprint)
Samsung Galaxy A5 (2015)
Samsung Galaxy J7 (Exynos)
Samsung Galaxy Ace 3 LTE
Samsung Galaxy V (Ace 4 Lite)
Samsung Galaxy Mega 6.3 (Intl)
Samsung Galaxy Mega 6.3 (Canada)
Samsung Galaxy Tab 2 7.0/10.1 (Wifi/3G)
Samsung Galaxy Tab 3 8.0 (Wifi)
Samsung Galaxy Tab 3 10.1
Samsung Galaxy Tab 4 10.1 (Wifi)
Samsung Galaxy Tab Pro 8.4 (Wifi)
Samsung Galaxy Tab Pro 10.1 (Wifi)
Samsung Galaxy Tab Pro 10.1 (LTE)
Samsung Galaxy Tab Pro 12.2 (Wifi)
Samsung Galaxy Tab S 8.4/10.5
Samsung Galaxy Tab S2 8.0/9.7
Samsung Galaxy Note 8.0 (Wifi/3G)
Samsung Galaxy Note 10.1
Samsung Galaxy Note 10.1 Wifi (2014 Edition)
Samsung Galaxy Note 10.1 3G (2014 Edition)
Samsung Galaxy Note 10.1 LTE (2014 Edition)
Samsung Galaxy Grand 2 (Qcom)
Samsung Galaxy Star
Samsung Galaxy Alpha (Exynos)
Sony Xperia Sola
Sony Xperia E1
Sony Xperia Z1
Sony Xperia T2 Ultra
Sony Xperia SP
Wileyfox Swift
Wileyfox Storm
Xiaomi Mi3W
Xiaomi MI 5
Xiaomi HM 1S
Xiaomi Redmi Note 2
Xiaomi Redmi Note 3 (MTK)
Xiaomi Redmi Note 3 Pro
Xiaomi Redmi Note 4G DS[/color]
[Galaxy S 4 i9505 Original Android Development] aarush.chaurasiya:
reserved

Ok bro thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This will be part of the upcoming new website :) The page will automatically be updated for every new build.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Why not a tool inside the app where if the device is not officially supported the user can enter with a custom device where he informs the boot, recovery, system, cache, and userdata paths? Of course with a warning that should be done only by "advanced" users and that will do at your own risk

What about the multiboot folder, could it be moved from /data/multiboot/ to /data/media/multiboot/? I do not know about the other users, but I particularly prefer to make modifications in the primary rom by TWRP itself without needing to patch the zip (if a new boot.img is installed I have knowledge that it should be patched again by the app) and so the secondary roms would also not be affected by a wipe data
[Galaxy S 4 i9505 Original Android Development] pehoko:
Why nobody helps people who have a problem with patcher in this topic?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Maybe because most of the time the answers can be found in the first few posts?
[Galaxy S 4 i9505 Original Android Development] pehoko:
No answers to many question in first few posts as everyone received some error on his device and no one want to help and is not described in title page. I am tired from googling all over the net to find no solution.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Be patient, the developer doesn't have enough free time to look into all the issues people are reporting. I didn't read these posts, but I'll check the logs if provided.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I have an issue selecting zip from usb otg on MM while it works fine on LP. Probably related to the weird way Android 6 is threading the usb drives. The patcher is always crashing when selecting zip from usb otg on MM. I will test and report the behavior on Android N 7.1 too.
[Galaxy S 4 i9505 Original Android Development] pehoko:
Ok, tnx, I am watching tread for some useful information.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
The new website is awesome! :good:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Looks like a potential SELinux issue. Does it flash correctly from recovery?

Could you also attach /sdcard/MultiBoot/daemon.log after flashing from the app?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yup, you got to experience the problem first-hand :D Using Linux to do the resizing is probably your only option.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry, I removed those originally because ROMs really shouldn't be writing to the bootloader partitions.

Anyway, the paths have been re-added and the codename fixed. A new test build is available at: https://github.com/chenxiaolong/DualBootPatcher/pull/301
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll consider it. This seems like a pretty useful feature.

I originally intended to have the files stored in /data/media/multiboot/, but due to how Android handles /data/media/ specially, it can't be used without disabling SELinux in every ROM (which is no longer possible without a custom kernel in Android 5.0+).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you link to the zip you're trying to flash? It's trying to mount the /cust partition, which is not allowed by the patcher by default.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Would you mind grabbing a logcat? Also, is it crashing when you select a zip for patching or when you select a zip for flashing? The reason I ask is because patching can use the Android API for accessing the file, but flashing can not.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It's not quite done yet. My best friend is working on making it a lot better :)
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Would this patch work also with recovery back ups?
[Galaxy S 4 i9505 Original Android Development] pehoko:
I have deleted all roms and data as my phone unfortunately goes to bootloop and buckup doesn't work. This was maybe official miui global rom 8.1.2.0, I will try again on new rom as everything was lost, thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope, recovery backups currently cannot be patched.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I have a s5 g900w8 and I can patch a rom file and install it to the extsd (just like I did with me s4) but when I reboot to the extsd rom it starts and then beeps a couple of times and then reboot to recovery. What file do I send you to see what is going on?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
I tried. Hehe
[Galaxy S 4 i9505 Original Android Development] ayed78:
working great.....n7 rom port and nougat beta 2
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
[MENTION=4277844]chenxiaolong[/MENTION]

Could you please add support for LG G5 h830 (T-Mobile)? I attached logs as well, also I'm guessing it should be pretty much same set up as the h850 but not sure. Anyways, thanks for your hard work.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes, the patcher is crashing when selecting zip for flashing, while I can long press on zip and select for patching no problem. Logcat is coming.
[Galaxy S 4 i9505 Original Android Development] monkteo:
3 different rom on S7E

all possibly because ......................

THX@chenxiaolong
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
When going back and forth on roms, do the roms load the way the were... Or are they "clean flashed" each time you go to a diff one?
[Galaxy S 4 i9505 Original Android Development] monkteo:
The rom change and load exacly way the are (exacly how I left it)

Sent from N7Echoe
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Retried to patch and flash TW 6.0 then beanstalk 7.1 (cm14.1 based). Here is the patch log. I do not understand why, I deleted daemon.log but it is not recreated nor written into after I recreated it manually.
[Galaxy S 4 i9505 Original Android Development] mbr007:
tmobile note 4 won't boot after install zip patch. No idea? log file attached.
[Galaxy S 4 i9505 Original Android Development] ayed78:
i try make again now secondary not boot...forgot way to do it
[Galaxy S 4 i9505 Original Android Development] monkteo:
quick version !

install dualboot - set kernel - patch rom - install patch rom - update ramdisk for primary rom and update ramdisk for secondary rom - switch roms (probably you will receive a message [I received to] but ignore it.

secondary rom - install dualboot - set kernel

good to go
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Tried flash in recovery, TW went further but failed too, Beanstalk succeeded. Retried in app, here is daemon.log. Forgot to save recovery log, will test again. By the way it is with rev109
[Galaxy S 4 i9505 Original Android Development] fmotta:
I'll give this a try but I have the feeling that it will not work in my case (Nougat as primary)
[Galaxy S 4 i9505 Original Android Development] monkteo:
if you follow the steps will work
[Galaxy S 4 i9505 Original Android Development] ayed78:
yes...rom that has aroma patch rom but cant flash and if flash in recovery phone not boot
[Galaxy S 4 i9505 Original Android Development] fmotta:
Yes yes yes. Thanks
[Galaxy S 4 i9505 Original Android Development] pehoko:
[MENTION=4277844]chenxiaolong[/MENTION] here is official stable rom 8.1.2.0 which I tried to flash with dualbootpatcher:

http://en.miui.com/download-302.html

which gives same error:

http://imgur.com/AX2VbF9

tnx
[Galaxy S 4 i9505 Original Android Development] ayed78:
if use normal rom no aroma works but if has aroma nkt working even flash via twrp phone not boot
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Here is the flash in recovery log

mount: mounting /dev/block/mmcblk0p24 on /cache failed: Device or resource busy

[D] Running executable: mount

mount: mounting /dev/block/mmcblk0p26 on /data failed: Device or resource busy

[D] Running executable: mount

mount: can't find /efs in /etc/fstab

[D] This is a Samsung device; mounting EFS partition in chroot

[E] /efs is not mounted

[D] Found /etc/recovery.fstab

[D] Looking for /efs entry in TWRP-format fstab

[D] Found /efs fstab entry

[D] [Installer] Environment set up stage

[D] [Installer] Device verification stage

[D] libmbp version: 9.0.0

[D] ro.product.device = kltexx

[D] ro.build.product =

[D] ro.patcher.device =

[D] Target device = klte
[Galaxy S 4 i9505 Original Android Development] monkteo:
After flash go with utility zip back to primary and update ramdisk. (I test and work)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When it autoreboots to recovery (and only then), please flash the GetLogs zip from https://dbp.noobdev.io/downloads/ and send me the file it creates in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I didn't realize a second beta was out. Time to do some flashing today :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure. Can you give the test build here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/304
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like you ran out of space on /system. You'll probably need to flash to a different slot.
[Galaxy S 4 i9505 Original Android Development] xdamami:
Hey everyone. Known bug after app sharing bootloop? Oneplus3?

Or we have an fix?
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Yes I tested and it works no problem. Thank you so much. Would it be ok for me to post this link for others with h830 to use or just wait until you release it officially? I don't want to share anything without your permission. Thanks again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No bugs related to app sharing will be fixed anymore. The feature has not been developed for more than a year and will be removed in a future release.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad to hear it's working! I have merged the changes, which will be available in the upcoming 9.1.0 release.

Thanks for asking for permission to share. I will never restrict where and how DualBootPatcher is shared (as long as the GPLv3 license is respected), so feel free to share the test build wherever you like. However, I would prefer if you linked to the test/beta builds for 9.1.0 here since they will be more up-to-date: https://github.com/chenxiaolong/DualBootPatcher/pull/299
[Galaxy S 4 i9505 Original Android Development] rifle007:
[MENTION=4277844]chenxiaolong[/MENTION] thanks for support redmi 2 and redmi 3. I have tested in test build r110 for both phone and no problem till now, miui in secondary can be installed too. Now i can use cm13 as primary and miui as secondary ?. Wait for officially release and thanks for your hard work.
[Galaxy S 4 i9505 Original Android Development] blowy666:
First of all, thanks for this great idea of this app. And sorry for my noobish question. I've read the description and understood it that way, that if we have for example 2 different ROMs installed, then apps that are installed on BOTH ROMs wouldn't need double the storage, cause they are only ONE TIME there and both ROMs would use that files. Is that correct? I'm asking cause I had already installed one ROM and now flashed a second one to my micro SD card (the primary is an Android 5.1.1, the second ROM an Android 6.0.1) and tried to install the same apps now also for the second ROM using Titanium Restore. I thought that Titanium now would overwrite the existing files, so that they would only be there once and will not use adittional internal storage. But while restoring process I got the message that my internal storage is full? Did I understand something wrong?

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I should probably correct the first post. The feature to have APKs shared by multiple ROMs has been removed a while ago due to it being incredibly unstable. There is still an "App Sharing" feature, but all it does is share the data for apps. It is also unstable and will be removed in a future release.

By default, every ROM is completely separated except for files in /sdcard.
[Galaxy S 4 i9505 Original Android Development] blowy666:
Ah okay, I see...thanks for your quick reply. So it would be best to use this feature if I would use the different ROMs for example for different apps... :)

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ayed78:
Where can I get utility zip
[Galaxy S 4 i9505 Original Android Development] kopitalk:
It's exactly where you get the dual boot patcher apk.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
[MENTION=7651201]LitDesign[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Eagle:
Actually you don't need to patch primary ROM twice.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Primary ROM isn't patched. I patched the same ROM zip, so that I can have a secondary ROM. I did that as the tw ROM won't boot after flashing.

---------- Post added at 04:29 AM ---------- Previous post was at 04:27 AM ----------

And even so...I need to flash the DL 1.9 kernel so that pronesis ROM will see my sim.

---------- Post added at 04:31 AM ---------- Previous post was at 04:29 AM ----------
[Galaxy S 4 i9505 Original Android Development] Eagle:
I was just confused on why you have two same version and ROM and your quotation below answered my question.

Well, currently my primary ROM is RR and Phronesis N7 is patched under data slot 1, it works well though. We should PM, do not want to disturb the rest here if you know what I mean.

You should always flash the patched one, if you flashed the non-patched zip it will mess up your primary kernel, which means that it will affect your primary ROM kernel and you cannot boot your primary ROM even when flashing boot.img through TWRP recovery.

So let's say, you patched for example: kernel-data-slot-1 but you have kernel.zip and you flashed kernel.zip it will count that you're flashing kernel.zip over to the RR kernel, which will mess up everything.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The backup/in-app flashing hang issue is now fixed in the 9.1.0 test/beta builds at: https://github.com/chenxiaolong/DualBootPatcher/pull/299 :)
[Galaxy S 4 i9505 Original Android Development] Eagle:
Been waiting for this to be fixed. Excellent work!
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Thanks, here is the log file.
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4277844]chenxiaolong[/MENTION] i have a little problem and don't what is causing it. If i set pin/pattern to unlock the phone, and i switch the rom, when i switch back to it, the pin/pattern doesn't work anymore.. Isn't recognized. I think is a kernel issue but don't know what to look for in the kernel. Same thing happends when i restore a backup with twrp - pattern won't work - but only with (my) permissive kernel.. A5 2015, Stock MM touchwiz deknoxed, data not encrypted. Btw here is my kernel source. Also here is my default.prop. Any help will be apreciated. Cheers!
[Galaxy S 4 i9505 Original Android Development] ayed78:
thanks got it and all working great now

---------- Post added at 06:17 AM ---------- Previous post was at 06:13 AM ----------

thanks bro all working now....
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I'm planning to buy a new larger extsd card. My hopes are that the roms I have installed right now on extsd slot will be intact and still there after a simple copy paste all the files from the following directories:

/extsd/multiboot/extsd-slot-xx
/raw/images/extsd-slot-xx
/raw/data/multiboot/extsd-slot-xx

Is that realistic? I think my best bet is to backup the roms on external and restore them to the new card. Even then I think there is a chance something will go wrong and I must start from scratch again.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yup, the best thing all we can do is to forget about the app sharing, because it will go away. btw I never used it.
[Galaxy S 4 i9505 Original Android Development] Mike0505:
Mi Max pro support

[MENTION=4277844]chenxiaolong[/MENTION]

Kindest request for adding Xiaomi mi max Pro support :)

logs attached

Thank You
[Galaxy S 4 i9505 Original Android Development] ShuppaGail:
Which last miui version is supported ? I do it with this and some russian tutorial with pictures, but god damn i cant find the thing with enabling documents or something... Error when im on ress trying to flash miui and on miui i cant even get it to patch the ressurection remix... Im just lost, please help
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! They were very helpful. A little background on why the crash happened:

Android apps are not supposed to access files directly via a normal Linux path (eg. "/sdcard/blah"). When you select a file, the app actually sees a URI like this:

content://com.android.externalstorage.documents/document/6AC5-1711%3Ablah.zip

which corresponds to

/storage/6AC5-1711/blah.zip

By using these URIs instead of paths, an app can support opening files not just from local storage, but also from cloud providers, like Google Drive.

The in-app flasher is the last part of the app doesn't fully support these URIs yet, so instead, it tries to translate the URI to a path. Since the URIs for USB-OTG drives are a little different, it could not be translated and caused a crash. I'm working on properly fixing this so no hacks are required.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks for the great insight! :)
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
I'm running on A870 Pantech vega iron and Boot UI is not showing

Can you help me solving the problem

---------- Post added at 12:58 PM ---------- Previous post was at 12:22 PM ----------

Apps not flashing zip from In-App flasher

Logs:

[D] Initialized installer for zip file: /storage/emulated/0/ROMs/Resurrection-Remix-LP-v5.5.9-20151204-ef52l_data-slot-rr5.zip
[D] [Installer] Initialization stage
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running executable: mount
mount: bad /etc/fstab: No such file or directory
[D] Running executable: mount
mount: bad /etc/fstab: No such file or directory
[D] Running executable: mount
mount: bad /etc/fstab: No such file or directory
[D] Running executable: mount
mount: bad /etc/fstab: No such file or directory
[E] /cache is not mounted
[V] Failed to create chroot environment
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to unmount /chroot/system: No such file or directory
[E] Failed to unmount /chroot/cache: No such file or directory
[E] Failed to unmount /chroot/data: No such file or directory
[E] Failed to unmount /chroot/efs: No such file or directory
[E] Failed to unmount /chroot/dev/pts: No such file or directory
[E] Failed to unmount /chroot/dev: No such file or directory
[E] Failed to unmount /chroot/proc: No such file or directory
[E] Failed to unmount /chroot/sys/fs/selinux: No such file or directory
[E] Failed to unmount /chroot/sys: No such file or directory
[E] Failed to unmount /chroot/tmp: No such file or directory
[E] Failed to unmount /chroot/sbin: No such file or directory
[E] Failed to unmount /chroot: No such file or directory
[E] /efs is not mounted
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is fixed in the latest 9.1.0 test build :) https://github.com/chenxiaolong/DualBootPatcher/pull/299