yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Guimenez:
First of all, thanks for such perfect tool :D

I can't install DualBootUtils.zip in recovery, i'm using TWRP 2.8.

It stuck in opening Aroma.

Is there anything i can do?

Thank you
[Galaxy S 4 i9505 Original Android Development] ewangw:
I believe that is a known issue with previous versions of TWRP. You would need to upgrade to 3.0.1 or 3.0.2.
[Galaxy S 4 i9505 Original Android Development] Guimenez:
Try latest version, but it's the same thing, hang at starting Aroma :(

Is there anyway to install the tools? I'd love to have rom option at boot.

Thank you
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION] If I want to update boot image, is it enough to overwrite the boot.img with the with the aboot.mbn file (from PF3_LL_bootloader.tar)?

I also need to flash new modem for this rom.

This bootloader is available to download for Imperium rom 15.0.

http://xdaforums.com/showthread.php?t=3046889
[Galaxy S 4 i9505 Original Android Development] Guimenez:
Is there anyway to modify the zip to remove aroma installer?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Didn't chenxiaolong add support for tar files at some point ?

---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------

My twrp 2.8 on klte can install DualBootUtils. Nevertheless you can use the patcher without it.
[Galaxy S 4 i9505 Original Android Development] Guimenez:
OnePlus one doesn't like aroma installer :(

I'd love to choose rom without booting inside one
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Well, doesn't accept tar files as file selection.
[Galaxy S 4 i9505 Original Android Development] ascila:
Hello. Is there any way to use this application with the Galaxy note 10.1 GT-N8013. I Know thath works with the Galaxy Note GT-N8010 , but i want to use it on the 8013. Somebody can help me?
[Galaxy S 4 i9505 Original Android Development] dedq:
Is there a way to install cm 13 next to Touchwiz this way ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, there's nothing I can do about this. When the multiboot components are added to the ramdisk, it becomes too large. This is partly because the Imperium kernel includes a bunch of their own files/programs in the ramdisk, such as busybox, which is around 1.9 MB. In comparison, the multiboot code is only ~850 KB.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2709.g554d8f9 is going to be the last of the 8.0.0 series :) Version 9.0.0 will be released in the next few days following some last minute testing. Several long-standing bugs, especially those related to flashing have been fixed (see: https://github.com/chenxiaolong/DualBootPatcher/issues?q=is:issue+is:closed). Those who have ran into the Error Code 11 bug (especially with Mediatek devices) when using in-app flashing should no longer run into that problem.

The reason for the major version bump is because of the new way of adding support for devices: https://github.com/chenxiaolong/DualBootPatcher/tree/9.0.0-staging/data/devices It's no longer necessary to recompile the entire project to add a devices; you can simply edit a config file now.

Windows builds will still be disabled for 9.0.0 due to this bug: https://bugs.archlinux.org/task/49860. Until that is fixed, any Windows builds I make will simply crash open opening.

---

On another note, if anyone wants me to add Boot UI support (allows switching ROMs during boot) for your device, please link me to the following:

TWRP XDA thread

TWRP device tree (ask in the TWRP XDA thread if you don't know it)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I apologize for being off XDA for long periods of time. Working on DualBootPatcher combined with my new job has been quite taxing on me.

As some of you may know, outside of work, all I work on is DualBootPatcher. I frequently take on large features (such as Boot UI and encryption) that are so time consuming that when combined with my day job, I really don't have the energy to do anything. Part of this is due to how I've been handling the development of DualBootPatcher. When there's a feature I'm interested in, I tend to drop everything else and focus only on that feature. Then I dive headfirst into the implementation without thinking of how I want it implemented. I inevitably get sucked into rewriting things over and over again until I get to the point I'm happy with it. Unfortunately, this is a very frustrating way to work for me and diverts my attention away from other important things to the point where sometimes, I don't even want to come to XDA to read about them. (And that is completely my fault.) Sometimes, I have to put the entire project aside for a while because I lose sleep over it and it feels like unfinished work instead of simply having fun.

Anyway, for the past week, I've been trying a different approach: I've been working on small changes that may or may not lead up to big features. The process of making small changes, creating test builds, and receiving feedback seems to work a lot better for me. At the end of the day, I don't feel like there's a lot of unfinished work that I haven't gotten to and that really helps. After all, the "getting feedback" part is one of the reasons why I love the community here and enjoy working on the project anyway :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
[MENTION=4277844]chenxiaolong[/MENTION], Let me express my wish that you'll stay with us and we all have this possibility to test your product.

I personally would follow any approach you may take.

In any case, there is no more advanced multi-boot tools for Android... Thank you for your work on the DBP project!
[Galaxy S 4 i9505 Original Android Development] gorthon:
I have a question: this looks like an awesome tweak, but the title and the initial post say it's for the galaxy s4. From what I read it may work on a whole lot of phones. Wouldn't it make sense to change the thread subject or even move the thread? Right now I'm a little bit confused.
[Galaxy S 4 i9505 Original Android Development] :
Will this work on other devices like J5 or is it strictly for galaxy S4 only???I want this feature on my phone also
[Galaxy S 4 i9505 Original Android Development] JhonnK:
My rom RR 5.7.3 my GT-I9500 error of couldn't determine the boot partition because this device's codename universal_5410? Help! Please!
[Galaxy S 4 i9505 Original Android Development] MuhammadBilal:
How do I select which ROM to boot into? Is there a key combo or something?
[Galaxy S 4 i9505 Original Android Development] smartman_ru:
I have a problem with dual boot patcher and the rights to a folder by sdcard / android / obb, can not see the insides and write either a single application, but in / data / media / obb folder is in place, the device OnePlus 3 and OnePlus one
[Galaxy S 4 i9505 Original Android Development] GayCasper:
Will this work for s6 edge
[Galaxy S 4 i9505 Original Android Development] Technical:
Stop working on Asus Zenfone 2 (ZE551ML) with MM (Android 6) bootloader.

Ramdisk seems to be incompatible and the phone does not boot or, better, it boots directly on recovery.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Hi mate,

Please add support of BootUi to op2.

Xda TWRP thread.

https://xdaforums.com/oneplus-2/general/official-twrp-2-8-7-0-oneplus-t3207889

Twrp device tree

https://github.com/TeamWin/android_device_oneplus_oneplus2

Thanks.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
[MENTION=4277844]chenxiaolong[/MENTION] : there is a bunch of writings on development organisation and methodology. You might be interested in agile methodology (if you don't already know it at work), even though a great part of it is about team work, there still might be principles you can use alone.

And don't be too harsh with yourself, we all begin with the same straightforward approach to development and you have already done so much with DBP.
[Galaxy S 4 i9505 Original Android Development] R3dDr4g0n:
[MENTION=4277844]chenxiaolong[/MENTION] I got "Ramdisk image exceeds boot image size by 4... bytes" when I am trying to install newest [JDCTeam][6.0.1] AOSP MOB31E as second rom. Is there a solution?
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
First off I really think the dual-boot utilities tool is pretty slick and looking forward to seeing the boot-UI feature also.
[Galaxy S 4 i9505 Original Android Development] Guimenez:
Thank you for such a great app.

Please can you make the dualbootools setup without Aroma?

Thank you.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the links! Please give the test build at https://github.com/chenxiaolong/DualBootPatcher/pull/186 at try.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, that means your ROM's kernel is too large to fit on the boot partition after the multiboot components have been added. You will not be able to use that ROM (unless you flash a custom kernel that is smaller).
[Galaxy S 4 i9505 Original Android Development] edyny1:
I have 925T running marshmallow and also running into problems.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Superb. Working perfectly. Thanks again.

I checked out the app/utility to backup and restore secondary roms but it doesn't support data partition and looks like it is abondoned now so can you suggest any method if I want to swap my primary and secondary (made on data partition) roms or take backup of secondary rom and restore it as primary from recovery?

Thanks.
[Galaxy S 4 i9505 Original Android Development] dtalwar14:
can not switch back

installed 6.0 rom as secondary rom over 5.1 as primary rom

now i cannot switch back to primary rom

after doing switching it reboots to secondary rom

how to solve this ?
[Galaxy S 4 i9505 Original Android Development] Anunay.j:
Error

When I try to flash this ROM I got this

Maybe it is not mounting EFS partition which my rom wants
[Galaxy S 4 i9505 Original Android Development] Red89:
I have a lollirom and i would instal s4 google edition rom in dual boot, i can this without wipe my rom?

And how?
[Galaxy S 4 i9505 Original Android Development] danarputra:
Can you make app for Asus (Z00L)?
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Can we delete the patched zip after flashing it or is it being used for the secondary ROM?
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Hi all, thanks to the developer for this great app, I've been using for a long time in various devices, but now I got one with mediatek processor, a HomTom mt6735 and it's don't work, is it posible to make it work? Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Yes and read first page

Yes you can, it's not use for secondary (it's use only when you flash)
[Galaxy S 4 i9505 Original Android Development] _Negan_:
I've a custom rom as primary that make the app think that my phone is a galaxy S7 (G935F). In order to make the application works correctly, edit build.prop with correct phone model is needed?
[Galaxy S 4 i9505 Original Android Development] Gawd:
Please add Boot UI support for the OnePlus One.

• TWRP XDA Thread : http://xdaforums.com/showthread.php?t=2766186

• TWRP device tree : https://github.com/TeamWin/android_device_oneplus_bacon

Thanks!
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Please add Boot UI support for the Samsung S5 SM-G900F klte

• TWRP XDA Thread: [RECOVERY][klte] TWRP 3.0.2-0 touch recovery [2016-04-05]

• TWRP device tree: Github

• TWRP for klte: Download

Thanks!
[Galaxy S 4 i9505 Original Android Development] jupstejuho:
Hello.

I used to have this working on my Note 4 on Android 5.0.1. Now I have Marshmellow and I installed this, updated ramdisk and now my phone can't see my SD card. I crypted my SD card before install and it worked fine. Any ideas? I can see the SD card in recovery and see the files although they are useless. I also tried to decrypt SD in system settings but didn't seem to start decrypting.

Is there any way to remove mbtool? I uninstalled the app but mbtool remained installed. I think installing mbtool caused the problem.

If not: I have my passphrase, is there any way to recover the data from the SD card? Key files should still be there somewhere in the phone and internal storage decrypts fine.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hello, [MENTION=4277844]chenxiaolong[/MENTION] :)

I have two problems. There are my posts:

http://xdaforums.com/showpost.php?p=68270861&postcount=9613

http://xdaforums.com/showpost.php?p=68352195&postcount=9619

Thanks you in advience! :D
[Galaxy S 4 i9505 Original Android Development] Andycar:
Hey, to remove mbtool just flash

/storage/emulated/0/MultiBoot/primary/boot.img.before-ramdisk-update.img

TWRP can flash boot .img directly.

Regarding crypto fs in 6.0 read the chen's last post or before it. I think, he is working on it now.

Отправлено с моего SM-G935F через Tapatalk
[Galaxy S 4 i9505 Original Android Development] navcar:
The JDCTeam AOSP roms all run a script to do loki bootloader patching. This conflicts with dual boot patcher, which I gather also does loki bootloader patching already. So installing these roms don't complete 100% under dual boot patcher.

Here's a screenshot

Taking a look at /system/etc/loki.sh, you can see that their script skips the bootloader step completely if it detects Multiboot.

#!/sbin/sh
#
# This leverages the loki_patch utility created by djrbliss which allows us
# to bypass the bootloader checks on jfltevzw and jflteatt
# See here for more information on loki: [url]https://github.com/djrbliss/loki[/url]
#
#
# Run loki patch on boot.img for locked bootloaders, found in loki_bootloaders
#
# Update for MultiROM by Mattia "AntaresOne" D'Alleva

# MultiROM environment recognition
MROM=$(ls /tmp | grep "META-INF")

# Run Loki tool
LOKI() {
egrep -q -f /system/etc/loki_bootloaders /proc/cmdline
if [ $? -eq 0 ];then
echo '[*] Locked bootloader version detected.'
export C=/tmp/loki_tmpdir
mkdir -p $C
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=$C/aboot.img
echo '[*] Patching boot.img to with loki.'
/system/bin/loki_tool patch boot $C/aboot.img /tmp/boot.img $C/boot.lok || exit 1
echo '[*] Flashing modified boot.img to device.'
/system/bin/loki_tool flash boot $C/boot.lok || exit 1
rm -rf $C
else
echo '[*] Unlocked bootloader version detected.'
echo '[*] Flashing unmodified boot.img to device.'
dd if=/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot || exit 1
fi
}

# Start
if [ "$MROM" == "" ]; then
echo "Installing primary ROM. Flashing kernel in boot partition..."
LOKI
else
echo "Installing ROM in MultiROM. Skipping kernel flash..."
exit 0
fi

Would there be any similar easy way to detect flashing under a Dual Boot Patcher environment? No real problem if there isn't a way, as right now it aborts right before installing SuperSu and Busybox, so it has actually finished placing all the system files - so it actually still boots ok!

Also, the Dual Boot Patcher android app has issues connecting to mbtool under Android N (probably due to Android N changes), but I'll let you get on with your 9.x release first :)

[url]http://pastebin.com/HrUjhETj[/URL]

Update: The old ramdisk image exceeds boot image size error is back with AOSP 7 Alpha 2. I guess I was just lucky that the stock(?) kernel was small enough in the Alpha 1 release. I guess I could keep using that particular boot.img

Now I remember that their AOSP 6 roms had the same problem too.
[Galaxy S 4 i9505 Original Android Development] jupstejuho:
Hey thanks a lot I didn't know about that, now my SD card is all working again! Maybe I'll stick to using one rom at a time :).
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hey anyone knows if this app supports the Android N yet? I tried some Nougat 7.0 build and it failed with message "EMULATED STORAGE PATH" or somerhing like that
[Galaxy S 4 i9505 Original Android Development] Guimenez:
Yes, I'm using it ;)
[Galaxy S 4 i9505 Original Android Development] shantam3108:
Weird when I used it, it successfully flashes n and dual boots it but on the Android n side the mbtool wouldn't connect so couldnt jump back to primary ROm
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Read the first post.. you can also flash the boot.img of primary ROM from recovery to boot into primary if mbtool method doesn't work.
[Galaxy S 4 i9505 Original Android Development] shantam3108:
Did that but primary ROm started but hung on starting apps
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
As secondary?
[Galaxy S 4 i9505 Original Android Development] Guimenez:
You must have root in N to mbtool to work

---------- Post added at 08:30 AM ---------- Previous post was at 08:30 AM ----------

Yes
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, assuming you did not delete /sdcard/MultiBoot, you can undo the ramdisk update (thus, removing mbtool) by flashing /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP. If you did delete that directory, you just need to flash the stock kernel (or whatever kernel you had before) again.

EDIT: Whoops, just saw that [MENTION=1111850]Andycar[/MENTION] already answered this.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post the /sdcard/MultiBoot.log file it creates? It most likely ran out of space while flashing.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! This was just added today and will be part of version 9.0.0. If you want to try it out now, you can use the test build at: https://github.com/chenxiaolong/DualBootPatcher/pull/191
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please give the test build at https://github.com/chenxiaolong/DualBootPatcher/pull/104 a try. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
DualBootPatcher actually requires that the ROM installer perform the Loki patching. After the installation part is done, the boot.img will be modified to add some multiboot components. If it detects the the boot image was patched via Loki before, it will redo the Loki patching after the modifications are made.

This should be fixed in 9.0.0 :) The reason it has the connection to mbtool issue is that mbtool service cannot start. Android 7.0 includes a change where services in the /init.*.rc files will not start if they're missing the SELinux label line ("seclabel"). If the ROM is rooted, the app should be able to manually start the service.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I won't be able to fix these until at least next week. Currently, TW 6.0 ROMs are not supported due to some SELinux changes that Samsung made and I have no way of testing anything because my previous S7 Edge had a locked bootloader. I will be getting an SM-G935F next week and also a Note 7 soon, so I'll be able to work on this :)
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Could you give me direct link to this test? I can't find this :(

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] hankching:
HERE: https://jenkins.noobdev.io/job/Dual...tcher-builder && fast,target=android-all-gcc/
[Galaxy S 4 i9505 Original Android Development] edyny1:
Here you go.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Thank you! I will be waiting for it! ;) Thanks for reply and don't forget to buy a phone without defective battery :P
[Galaxy S 4 i9505 Original Android Development] SerJo87:
Please Add support for Xiaomi Redmi Note 3 Pro(kenzo)

TWRP(Official): http://xdaforums.com/redmi-note-3/development/official-twrp-3-0-2-0-recovery-redmi-t3352966

TWRP device tree: https://github.com/TeamWin/android_device_xiaomi_kenzo
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, your system partition ran out of space during the flashing process:

minzip: Error writing 12288 bytes from zip file from 0xfffea56c: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.

You'll have to flash to another slot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the links! However, those are only needed for adding Boot UI support to an already-supported device. For me to add support for a new device, please flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the file it creates in /sdcard/logs/.
[Galaxy S 4 i9505 Original Android Development] SerJo87:
chenxiaolong, Now I have install Custom TWRP, but if you need oficial TWRP I will instal his.

Sorry for my English
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Thank you very much for your support.

I've tried version r2810

I could "Install Boot UI" but I had problem with boot after restart.

Boot was suspended just before lock screen. After reboot I was able to see wallpaper byt not unlock soft.

How to provide you logs ?

I use twrp-3.0.2-0-klte
[Galaxy S 4 i9505 Original Android Development] edyny1:
Oh ok, i will try data slot 1 next time, was doing it on secondary slot

---------- Post added at 02:40 PM ---------- Previous post was at 02:17 PM ----------

How exactly do you install (Boot UI) and how to use it? I have G925T Samsung Galaxy S6 Edge
[Galaxy S 4 i9505 Original Android Development] hankching:
BootUI for Samsung Galaxy S6 Edge isn't enable, so it's not install function.

Pls provide TWRP info as same of above mentioned.

Which chenxiaolong will update it.
[Galaxy S 4 i9505 Original Android Development] edyny1:
Ok i flashed the Getlogs zip for TWRP info
[Galaxy S 4 i9505 Original Android Development] edyny1:
Ok i made more space on my S6 edge and now is flashing ok with no errors but when i reboot i get "Kernel is no SeAndroind enforcing" i have patched many different kernels for my device and i still get that message and just won't boot. It created a log so here it is.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Flash Getlogs.zip and upload file.
[Galaxy S 4 i9505 Original Android Development] nachomagic:
Hi mates. I've installed the patcher and before setting primary rom I wonder, do I have to uninstall multirom or both system can live together?

Thanks in advance

Enviado desde mi A0001 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] edyny1:
OK here is the Getlogs. zip attached. Also I patched a different Rom got the same kernel message and this time instead of going into recovery It booted automatically the primary rom.

Here is also screenshot that is flashing OK with no errors.

Also once you figure out what's going on with that log can you be able to see if I can install "bootUI" I believe that's how you call it (to chose rooms at boot) Thank you.

I have 2 devices:

Samsung Galaxy S6 edge (925T)

Samsung Galaxy S6 Flat (920T/W8)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I have this same problem. We need wait :)

http://xdaforums.com/showpost.php?p=68751402&postcount=9687
[Galaxy S 4 i9505 Original Android Development] Allexandre09:
Dual Boot

Há alguma esperança para o Xperia Z3?
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Hey. I have a one plus 3 so I was wondering , can I use dual boot if my device is encrypted? Decrypting is a pain and I d rather avoid it. Thank you.
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Is it possible to copy hosts file from secondary ROM to primary without any errors? My hosts file is generated by AdAway in secondary ROM but I can't root the primary ROM to install AdAway because of Pokemon Go and I need an adblocking solution. Any help much appreciated!
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
For Xperia Z3 you have Multirom.apk in the Play Store, you can try but Dualboot should work.
[Galaxy S 4 i9505 Original Android Development] Gawd:
Never quote the OP. Please, it hurts.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Have you take a look into this??