yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If the latest bootloader doesn't fix the issue, there's not much I can do about it, unfortunately. All the app does is tell the kernel to reboot. There's no way to customize or control how a device reboots (besides choosing whether to boot to download mode or recovery).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What issues are you seeing and which device? Can you post the logs?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! This is an interesting and weird issue.

The /raw/data/multiboot/$romname/system/xbin/su should be ignored because SuperSU is flashed in systemless mode. The su binary will be located inside of /data/su.img.

Can you try:

Flashing the ROM and SuperSU with in-app flashing to a data slot (eg. data-slot-test1)

Flashing the ROM and SuperSU from recovery to a different data slot (eg. data-slot-test2)

And then upload:

/data/multiboot/data-slot-test1/su.img

/data/multiboot/data-slot-test2/su.img

/sdcard/MultiBoot/data-slot-test1/boot.img

/sdcard/MultiBoot/data-slot-test2/boot.img

I will also test this on my own device.

Thanks!
[Galaxy S 4 i9505 Original Android Development] fishersfish:
Here they are.:)

su.img: from /raw/data/multiboot/data-slot-test*/data/su.img

boot.img: from /sdcard/MultiBoot/data-slot-test*/boot.img

PS:

/raw/data/multiboot/data-slot-test1/system/xbin/su exists.

/raw/data/multiboot/data-slot-test2/system/xbin/su exists.
[Galaxy S 4 i9505 Original Android Development] Gobis:
DualBootPatcher.exe for v9.1.0?

Hi,

The last available download of DualBootPatcher.exe that I can find is for version 8.0.0.r2616.g784e86e from July 2016. I assume that we should not use this old exe to patch the latest AOSP Android N 7.1.1 ROMs?!

Can you please update the nightly build engine to release win32 version too?
[Galaxy S 4 i9505 Original Android Development] monkteo:
check the signature of the developer (on a pc version)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
AFAIK the version for Windows was discontinued due to some serious bugs.
[Galaxy S 4 i9505 Original Android Development] Gobis:
The developer's signature shows "DualBootPatcher snapshot builds: https://snapshots.noobdev.io", which is where I already looked for updates.

---------- Post added at 05:33 PM ---------- Previous post was at 05:23 PM ----------

You're right. I searched the thread again and found post #9832, where the developer states "I am no longer making Windows builds until a compiler bug is fixed." I hope this compiler bug is fixed soon.
[Galaxy S 4 i9505 Original Android Development] umuturunc:
Thanks for help. But I don't understand how to check how much space I have from the app. Free space tab is blank all the time even if I refresh it. Am I missing something?

I'm using 9.1.0.r63.g5da8137-snapshot version
[Galaxy S 4 i9505 Original Android Development] buddhatrip:
Thanks for your response. Log file and screenshot attached.
[Galaxy S 4 i9505 Original Android Development] buddhatrip:
Thanks for your response. My device is Armani. Multiboot log, recovery log and screen shot attached
[Galaxy S 4 i9505 Original Android Development] smitharro:
Huh? It should be looking like this:

Is your phone supported?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Thanks, link below:

http://xdaforums.com/sprint-htc-10/development/rom-bad-boyz-sprint-htc-10-6-0-1-1-24-t3379781
[Galaxy S 4 i9505 Original Android Development] gaww:
I patched Gummy 1114 and PA 1111 and installed as secondary with no issues. I either used the 2.5.3 windows setup or the 3.0

android

patcher app (I switched over about that time and don't recall). In any case, I did NOT use the 3.0 windows application.

From the posts back a few, I was not able to patch the newer PA Gapps and have not tried the latest Gummy.
[Galaxy S 4 i9505 Original Android Development] lukemo:
I was able to patch jamal cm 11 but not Gummy and with windows beta 3.0. No way absolutely to have android patcher working, I don't know why. I have to solve now the gapps problem (I would like to patch the 19/11 version).

Thanks anyway for your kind help
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 3.0.0 is now released! Changelog:

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? :p

Remember, triple boot (and more) is experimental!

I can't be held responsible if for wiped data or bricked phones, so make sure to create backups before trying this feature :)

To try out the triple boot, drag the zip file onto useful/multi-boot.bat instead of the normal patch-file.bat

If you're on Linux or Mac, run:

./useful/multi-boot.sh /path/to/file.zip

Enjoy!
[Galaxy S 4 i9505 Original Android Development] blondbond:
Amazing!!
[Galaxy S 4 i9505 Original Android Development] mega00:
Just getting even better
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
That sounds great! Anything in works for a new dual boot utility zip?

And how can you choose what partition to install the patched rom onto?
[Galaxy S 4 i9505 Original Android Development] Shanks:
Ok,I managed to install roms on slot 2 and 3 but not on 1, anyways,I can only switch between primary and secondary rom, can't switch between roms on slot 2 and 3 and I'm using dual boot switcher v2.0, anybody knows how to switch between all roms, thanks in advance guys
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you tell me which ROMs you are using for each slot and which ROM doesn't let you switch to the others?

I tested with a bunch of ROMs, but it's impossible to me to test all combinations since the possibilities are exponential :p

EDIT: It might be a permissions issue. Could you run the app attached to this post and take a screenshot of what it says for the slots?
[Galaxy S 4 i9505 Original Android Development] Bejda:
Maybe the problem was that now it's mandatory on all devices to "set kernel as.." for any rom/slot?

All seems perfect for me :victory:

My initial config is CM10.2 24/11 as primary and your 25/11 jfltexx CM11 as secondary.

I patched miui and its gapps for slot1 on windows 7 without issue,flashed it,reboot into miui/install 2.0 dualswitch apk and set kernel as slot1.

I guess my error (yeah there was one actually lol) was I didn't set secondary rom kernel before cause after that when i choosed primary or secondary rom through 2.0 dualswitch apk it always booted to primary.

Switch to secondary via dual-boot utilities gave same story so I reflashed noobdev CM11 rom,boot into it fine and set kernel as secondary and now all seems ok and great.

So dunno,maybe initial error was that I didn't set secondary kernel as first step or maybe i just made a mess with "set kernel as.." option (which is possible btw..the more I get used to dual-boot the less I'm concentrated sometimes lol).

Anyway it works perfect (for)now,thank you!
[Galaxy S 4 i9505 Original Android Development] taxi333:
Running infamous (primary) , cm11 (secondary ) , carbon (multi slot 1) no option to switch to multislot 1 rom in both roms
[Galaxy S 4 i9505 Original Android Development] Bejda:
Mine (working prim/second/slot1 config) with TestPerms app runned on primary Rom.
[Galaxy S 4 i9505 Original Android Development] gaww:
Is it possible that after using multi-boot that (based on the ROMs used) it will run out of space and fail (I have a US TW as primary as occasionally I really need WiFi calling) ? If it only just fails to flash the last attempt, no problem, but wondering if this has been tested or if it is not an issue.

If for whatever reason you want to revert to duel-boot (or tri-boot if all tree slots have been used), how does one clear out the extra slots (as will the slots now show up in duelboot utilities) ?

Finally figured out my trouble with patching/flashing KT 4.4 kernels.

I had been using the US TMo kernels on patched 10.2 up to a point and then started to have issues - ditto with all 4.4. I tried international version and it booted fine and seem to be working OK. I had been using TMo KT's on other international ROMs and was surprised to run into this here - especially since they worked initially.

So far, this new system looks real impressive - plus some issues have been fixed with the basic patcher - patched PA 1119 with no issues. Great work OP !

Question to other users - with 4.2 TW and noobdev CM11, what are some interesting ROMs on the list that are worth taking a look at (and why)? Chen has really opened up the toy box with this release - lol.
[Galaxy S 4 i9505 Original Android Development] Shanks:
Hi, thanks for your answer,I am running touchwiz stock on primary,gummy kit kat on secondary, then I patched cm 10.2 2013/11/19 for slot 1 and gapps as well,probam 4.5.0 for slot 2 and finally pacman for slot 3,well...first I try installing cm 10.2 first but recovery failed to install(something about installation aborted),I patched 10.2 3 times but still the same results, ok, so I went and flash probam and everything went good, but when I install dual boot switcher 2.0 I don't see any option to set kernel as slot 2, just as primary and secondary, so I redownloaded dual boot switcher again and still the same, then I went and install pacman and everything went good but the same thing happened to dual boot switcher, my guess is that I have to install a rom on slot 1 first and then the second and then the tried third in order for the switcher to work properly,I don't know, you tell me boss Chen, thanks.
[Galaxy S 4 i9505 Original Android Development] `SBR`:
do anyone have the patched SuperSu 1.75.. i tried but it's not patching..

i need it to have AOSP KK (brood version) as dual boot, but root is not working
[Galaxy S 4 i9505 Original Android Development] sbcrumb:
Verizon S4

Does this not work with verizon? I installed a touchwiz ROM Hyperdrive 10.2 in primary, then tried to do carbon 4.3 patched the gapps the rom and ktoonz kernel. I can boot the first rom but the second slot tells me

System software not authorized by Verizon Wireless has been found on your phone.

Please turn off your phone and go to the nearest Verizon Wireless store for help

Is there a catch? I have an unlocked bootloader on mdk loki install not safestrap.
[Galaxy S 4 i9505 Original Android Development] Shanks:
Alright,I finally install cm 10.2 on first 1, but I still don't get any option to set my current kernel as first slot
[Galaxy S 4 i9505 Original Android Development] RK:
Patch ramdisk in: C:\Users\rkamalapurkar\Downloads\AndroidTools\boot.img

Which type of ramdisk do you have?

1: jflte\AOSP\AOSP

2: jflte\GoogleEdition\GoogleEdition

3: jflte\TouchWiz\TouchWiz

Choice: 3

Replacing ramdisk with jflte\TouchWiz\TouchWiz.def

Extracting ramdisk--- ERROR BEGIN ---

No stdout output

--- STDERR BEGIN ---

b'/windows/cpio: premature end of archive\n'

--- STDERR END ---

--- ERROR END ---

Failed to extract ramdisk using cpio

Traceback (most recent call last):

File "C:\Users\rkamalapurkar\Downloads\AndroidTools\DualBootPatcher-3.0.0\usef

ul\\..\scripts\patchramdisk.py", line 92, in <module>

new_file = patchfile.patch_boot_image(filename, file_info, partition_config)

File "C:\Users\rkamalapurkar\Downloads\AndroidTools\DualBootPatcher-3.0.0\scri

pts\patchfile.py", line 336, in patch_boot_image

clean_up_and_exit(1)

File "C:\Users\rkamalapurkar\Downloads\AndroidTools\DualBootPatcher-3.0.0\scri

pts\patchfile.py", line 146, in clean_up_and_exit

shutil.rmtree(d)

File "C:\Users\rkamalapurkar\Downloads\AndroidTools\DualBootPatcher-3.0.0\pyth

onportable\lib\shutil.py", line 285, in rmtree

onerror(os.remove, fullname, sys.exc_info())

File "C:\Users\rkamalapurkar\Downloads\AndroidTools\DualBootPatcher-3.0.0\pyth

onportable\lib\shutil.py", line 283, in rmtree

os.remove(fullname)

WindowsError: [Error 32] The process cannot access the file because it is being

used by another process: 'c:\\users\\rkamal~1\\appdata\\local\\temp\\tmpwriiqw\\

boot.img-ramdisk.gz'

Press any key to continue . . .

got this patching a kernel with 3.0.0 on windows
[Galaxy S 4 i9505 Original Android Development] RK:
[MENTION=4277844]chenxiaolong[/MENTION], also, chainfire changed his supersu update zip. The updater script is now just a dummy file, and all the code is in the update binary attached. How should I patch this?
[Galaxy S 4 i9505 Original Android Development] respider:
anyone able to patch MaKTaiL's untouched kitkat rom?
[Galaxy S 4 i9505 Original Android Development] Sushibagel:
It should.. You will just need to flash Loki Doki or a lokied kernel after.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
[MENTION=4598795]Eleo[/MENTION]
[Galaxy S 4 i9505 Original Android Development] umuturunc:
Yes it is supported. I have S4 Mini serrano3gxx
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Started search. 1st pic...then went inside that folder. 2nd pic, and found appropriate build.prop
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
This is where the prop needs to be modified. Thanks again Eleo.
[Galaxy S 4 i9505 Original Android Development] Eleo:
It should give smth like this. Maybe you didnt give storage or root permissions?
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
Is it possible to integrate this patching system into Kodi?
[Galaxy S 4 i9505 Original Android Development] kdnmobile:
Link to the 7.1 Rom you used,pls. I have cm 14.1 successfuly flashed to Secondary slot but it cannot boot.
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
[MENTION=4277844]chenxiaolong[/MENTION] did you remove support for the T-Mobile LG v20 in the latest build? I'm just not seeing it unless I'm making a mistake
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
lol Do you have K3 Note?

---------- Post added at 16:36 ---------- Previous post was at 16:28 ----------

Just quick checked and no support for t mobile lg v20 in r65.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
The

DualBootPatcherAndroid-9.1.0.r56.g4da7622-snapshot.apk

release says error

Can not update mbtool.

I had no such problem with earlier releases.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Newest is r65. Try and report back please. Some issues were solved
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Thanks! I've been just read about the fix.
[Galaxy S 4 i9505 Original Android Development] jimbo77:
Do you have any plans to include the ZTE Axon 7 (US version) as supported? I'm looking forward to be able to dual boot on that phone, it has a SnapDragon 820. If you need any type of information i'll be glad to provide it :)

Thanks!
[Galaxy S 4 i9505 Original Android Development] Eleo:
Just flash the GetLogs zip from https://dbp.noobdev.io/downloads/ and share the tarball it creates in /sdcard/logs/ (file extension is tar.gz) here in attachment of a post with your phone model.

This will aid developer to support your phone for dualboot if it is not supported yet :)

Cheers
[Galaxy S 4 i9505 Original Android Development] jimbo77:
Alright. I'll do that ASAP. Thanks!
[Galaxy S 4 i9505 Original Android Development] jimbo77:
Tried to use the "Update Ramdisk" button and it didn't work. O was able to catch the log it created, also when trying to backup the kernel it couldn't locate it. See logs and screenshot attached, hope this can help if the tarball is needed I'll have uploaded as well later on today.

Thanks!
[Galaxy S 4 i9505 Original Android Development] mbr007:
Same here.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Your phone model is not supported yet. Before using the dual boot patcher app please wait for developer to build a snapshot version on jenkins for you to test. Right now it is unfunctional on your device. Tarball created by getlogs will give the required information for developer to produce a snapshot version for you. Use that version of app since right now it is not useful for you and may even damage the system of your phone if you try on using it. Please be cautious.

Cheers

Then same to you too. Please share the tarball explained above so that your phone can use the app too :)
[Galaxy S 4 i9505 Original Android Development] jimbo77:
I know I just wanted to see what it would do and as you mentioned my decide hasn't been added hence it can't find the partition layout. Anyways, attached is the tarball with the logs. Hopefully the Axon 7 can get support. (fingers crossed)

EDIT: it seems the tarball was incorrectly uploaded. I've added a google drive link for it here:

https://drive.google.com/file/d/0Bx2cksW3bCBCVU93cUtUWi0ya2M/view?usp=sharing

Thanks!
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION]: I'm in a big trouble. Neither of the roms are booting, they are ending in recovery. Using Samsung Galaxy S4 i9505.

The following steps were done:

- I started DBP r56, but got mbtool update error

- installed r65, updated mbtool in all installed roms, without rebooting

- patched Resurrection Remix M 5.7.4

- tried to flash to a new extsd slot, but at the middle of the process, the screen became locked, and likely the DBP crashed as it disappeared when I unlocked the screen

- I wiped the bad slot completely

- rebooted

- boot ui appears, but after continuing, ends with recovery.

Attaching the logs grabbed after first recovery.

All other roms are not booting anymore, they end with recovery.

I tried to rename the boot.img to boot.img.old and copy the boot.img before patch to boot.img, but same result.

How can I make again to boot into at least one of the roms?
[Galaxy S 4 i9505 Original Android Development] add_pl:
[MENTION=4277844]chenxiaolong[/MENTION]

Still i cant flash MIUI rom
[Galaxy S 4 i9505 Original Android Development] pehoko:
Try modified miui rom, official never works this way.
[Galaxy S 4 i9505 Original Android Development] umuturunc:
Thanks. Data-slot works without error.
[Galaxy S 4 i9505 Original Android Development] mbr007:
Thanks. It works now.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Just tried some recent MIUI 8 release and indeed it's not mounting /cache after updating the ramdisk for some reason. I'm not sure I patched the rom with the latest build. If I don't update the ramdisk it's just hangs at the bootanimation. May be the log won't be very helpful as I manually rebooted after the bootloop, but still.
[Galaxy S 4 i9505 Original Android Development] pehoko:
So I have manualy created miui cache and rom boots again but "com.android.phone not responding"
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4277844]chenxiaolong[/MENTION] investigated more the problem with external sd restore. In last 9.0.0 (r71) external is mounted from /storage, while in all 9.1.0 mounts the sdcard from /media_rw. Need to mention that the problems are only when trying to restore being data-slot. From primary to any slot works as should. I'm keeping 9.0.0.r71 around for restoring :) Cheers!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Due to how the zip references the partitions, you'll probably need to flash the patched file from recovery.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Which Kodi are you referring to? The media center software? https://kodi.tv/
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just merged the changes. It will be available in 9.1.0.r67.g7a8cb25 and newer.
[Galaxy S 4 i9505 Original Android Development] jimbo77:
[MENTION=4277844]chenxiaolong[/MENTION] Did you have the chance to take a look at the logs I provided from the Axon 7? (crossing fingers)

Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/341
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try doing the highlighted part above again and grab the logs when it autoreboots to recovery? The kernel logs were somehow corrupted.

EDIT: To rule out the Boot UI causing issues, you could try deleting/renaming /cache/multiboot/bootui.zip.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Looks like you ran out of space:

[W] /data/multiboot/data-slot-123/system/lib64/libTrafficRadar.so: Failed to copy data: No space left on device
[W] /data/multiboot/data-slot-123/system/lib64/libWnnEngDic.so: Failed to copy data: No space left on device
[W] /data/multiboot/data-slot-123/system/lib64/libWnnJpnDic.so: Failed to copy data: No space left on device
[W] /data/multiboot/data-slot-123/system/lib64/lib_fpc_tac_shared.so: Failed to copy data: No space left on device
[W] /data/multiboot/data-slot-123/system/lib64/libadvanced_crypto.so: Failed to copy data: No space left on device
[W] /data/multiboot/data-slot-123/system/lib64/libadvanced_crypto_jni.so: Failed to copy data: No space left on device
....

I don't see any issues in the logs. You probably just need to free up some more space.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Did you wipe /cache by any chance? Looks like it can't mount /cache because /raw/cache/multiboot/data-slot-data7/cache does not exist. I'll fix mbtool so missing directories are created if they don't exist during boot.

EDIT: This should (hopefully) be fixed in 9.1.0.r69.g37c4fa9