yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Hi [MENTION=4277844]chenxiaolong[/MENTION] I am in a similar situation as dikime - I am using a Oneplus 2 and have 2 ROMs, one stock clean Oxygen OS 3.10 (Primary) for Pokemon GO and another CM13 (Secondary) with in-built root but no Xposed/SuperSU. However since the last Google SafetyNet update on 6th Oct, I haven't been able to pass the SafetyNet checks on the stock clean OOS 3.10. I'd be really grateful if you could suggest a solution to run dual-ROMs and not trip SafetyNet - is there something that I can do on my end or do we have to wait for an update to the dual-boot patcher?
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
+3
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I have problem with cm14 build.
[Galaxy S 4 i9505 Original Android Development] bvlgvr:
Unfortunately I can't get this to work ... goal is: dual boot with 2x CM13 and encryption enabled ... does anyone have any ideas?

Here's what I did:

flashed TWRP_2.8.1.0_serranoltexx_F2FS_22-12-2014 ... I flashed this old version of TWRP because with the up to date openrecovery-twrp-3.0.2-1-serranoltexx-STABLE-signed the encryption function of CM13 wouldn't work ... someone mentioned it's because the new TWRP doesn't set up the data partition correctly for it to support encryption

flashed CM13 ... cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J7-serranoltexx

in CM13, formatted the micro sd card to be used as internal storage

set a screen lock password

enabled encryption with the built in CM13 function (worked fine)

activated CM13 Developer options to enable root (for DualBootPatcher app)

installed DualBootPatcherAndroid-8.0.0.r2709.g554d8f9-snapshot.apk

got message from DualBootPatcher app: The saved kernel is different from the currently running kernel. Would you like to set the kernel now? ... chose SET NOW

patched CM13 zip file with Partition configuration Data slot

flashed openrecovery-twrp-3.0.2-1... because the older TWRP_2.8.1.0... wouldn't accept my encryption password to decrypt

flashed (from TWRP 3.0.2-1) the patched (for use in Data slot) CM13 zip file

... this results in a boot loop ... the boot screen comes up displaying brand and model number (it doesn't get up to the encryption password prompt) ... then the phone vibrates 4 times ... then after some time it reboots.

a wipe in TWRP doesn't help ... boot loop

patching the CM13 zip for the secondary instead of Data slot doesn't work either ... boot loop

flashing the patched CM13 zip via the Dualboot patcher app works fine but then switching to the Data slot or secondary ROM also results in a boot loop.

So the closest I get to a working dual boot configuration is two CM13 ROMs installed ... switching ROMs in the app works fine, but as soon as I try to boot a ROM other than the primary I get a boot loop.

What can I do?

Thanks guys.

Edit: I added the log file from after the failed boot ...

Not sure if this is relevant ... but the dmesg.log suggests that the ext4 partition for data can't be mounted ... now what? :confused:

<3>[ 11.907462] ---------------------------------------------------
<3>[ 11.913352] EXT4-fs (mmcblk0p24): VFS: Can't find ext4 filesystem
<3>[ 11.923851] printing data of superblock-bh
<3>[ 11.926964] print_bh: bh d862ad80, bh->b_size 1024, bh->b_data d8bd3400
<3>[ 11.933862] As EXT4-fs error, printing data in hex
<3>[ 11.933862] [partition info] s_id : mmcblk0p24, start block# : 3899392
<3>[ 11.945307] dump block# : 1, start offset(byte) : 0, length(byte) : 1024
<3>[ 11.951869] -------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] dikime:
I fixed my setup by actually rooting the "clean" ROM with the phh's hidesu zip from the link. For some reason SafetyNet doesn't like dualbooting, even when I cleaned up everything associated with root, busybox, xposed etc. But rooting it with that method fixes the problem, until the next update I guess. Secondary ROM can have anything in it, even xposed and non-"hidden" root.
[Galaxy S 4 i9505 Original Android Development] dikime:
First of all, I'm using Galaxy S4 I9505 (jfltexx). Forgot to mention that, might be relevant.

So I dug around the forum a bit and here's my understanding (as an educated monkey and not a real developer):

Weird modifications to ramdisk will confuse the hidesu.zip - for example trying to install this this on Imperium kernel (for touchwiz) fails, while stock Samsung kernel is OK. That's without any patching, just straight up flashing.

I tried looking at what the script in META-INF is doing, so I can manually replicate it, but (surprise surprise!) it's not as simple as copy-pasting files. It involves modifying the boot image, something both the patcher as well as the new SuperSU are doing. However SuperSU's implementation seems to be different and it actually succeeds going through the patcher.

I've attached the log file of trying to flash this troublesome zip on CM13 nightly as Multi-Slot-2 for testing, as well as the link to the actual zip so you can look at it if you want. But from my limited understanding it's not the patcher's fault.

Thanks for the app :)

P.S. Sorry for the double post, forgot I already replied.
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Thanks for sharing your solution but the only thing I really miss on CM13 is the automatic screen temp changer.. other than that I can always root when I need it (for Titanium Backup etc.) and unroot immediately after, don't really have any apps that require constant root and it'd be too much of a hassle to keep up with the cat-and-mouse game. Honestly, this must be the hardest game I've ever had to work at just to keep on playing it :rolleyes:

Thanks for your solution again though :o
[Galaxy S 4 i9505 Original Android Development] cescof:
Is samsung galaxy S2 i9100 supported?
[Galaxy S 4 i9505 Original Android Development] JensGoro:
********************************************************************************************

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.

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.

********************************************************************************************

But where i can download "DualBootPatcher.exe"
[Galaxy S 4 i9505 Original Android Development] monkteo:
Look in the signature of [MENTION=4277844]chenxiaolong[/MENTION] (the owner of app)
[Galaxy S 4 i9505 Original Android Development] SerJo87:
Thanks. Work fine for Xiaomi Redmi Note 3 Pro(kenzo).

Now will DualBootUtilities work?
[Galaxy S 4 i9505 Original Android Development] physwizz:
Hi Chen. I tried 2842 and I still get recovery on reboot
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=6450691]KaMyKaSii[/MENTION] Really hope that [MENTION=4277844]chenxiaolong[/MENTION] will look more closely at the extsd mount issue you described in posts #9746 and #9760 because I also have very similar problems with the "SD Corrupted" message in MM. My internal storage is also located at /data/media/0
[Galaxy S 4 i9505 Original Android Development] physwizz:
I think the SD corrupted message is ROM related.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
I also hope. If you can also reproduce the error and register with Liveboot app will help dev to "refine" the log and find the problem. If you can, use these following options:
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
It is a problem in mounting external card running dual boot, since the ROM installed normally not have this problem. But it should be related to rom. Since here on CM 12.1 normally works the external card but on CM 13, no
[Galaxy S 4 i9505 Original Android Development] physwizz:
One of my mm ROMs on external USB for nexus 5 running multirom does the same thing. The other roms are fine.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Guess what this is? ;)
[Galaxy S 4 i9505 Original Android Development] ttydy:
Please add support for Oneplus 3. Thx.
[Galaxy S 4 i9505 Original Android Development] monkteo:
S7E ????????:confused::o
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4891276]monkteo[/MENTION] - It's a teaser for working backup/restore function.

[MENTION=4277844]chenxiaolong[/MENTION] - Seeing this gives me hope on 6.0 touchwiz patching issues. Waiting patiently for the update :)

Cheers!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hell yeah! Finally! Cheers buddy! :highfive:

Thanks for taking from your time to implement the backup option to the gui patcher.

---------- Post added at 11:53 ---------- Previous post was at 11:46 ----------

Yup, I think he said he'll get an S7E, but hopefully he gave up on the Note 7, cuz it's dangerous. :p
[Galaxy S 4 i9505 Original Android Development] `SBR`:
It's already patched...so you can just install either as normal or dual...only thing you need to patch gapps manually
[Galaxy S 4 i9505 Original Android Development] rlorange:
Patched latest kt and gapps.

Unzip your original cwm zips

Unzip the patches below and copy over the corresponding installer folders unzipped.

Zip up and flash in recovery

Kt fully patched dual boot

https://db.tt/EqIhe4I0

Noob dev 17/11 dual boot and jftexx patch

https://db.tt/y9LJsZ6i

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

Pa gapps odexed dual boot patch

https://db.tt/ZcMmsYPG
[Galaxy S 4 i9505 Original Android Development] gaww:
OP - will these work on US TMo devices ?
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=3019752]gaww[/MENTION],

Same story as gummy zip,remove assert getprop lines of updater-script.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The old way will still work because not everything can be fully automatic :D Anyway, the next release will have Gummy support (new beta in maybe an hour).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hellybean won't be an issue anymore: https://github.com/chenxiaolong/DualBootPatcher/commit/a513b35c19876a8e2a02ea7083e7a4ee3fb9665a :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you very much for the support! :D:highfive:
[Galaxy S 4 i9505 Original Android Development] Bejda:
Yeah actually chronologically i first manually patched that gummy 4.4 zip.

Then I wanted to add support using 3.0.0Alpha1 version, noticed there wasn't any AOSP ROMs folder but it didn't hit my mind i thought "well, let's create one and push my gummy.dualboot.patch file in it" but had some errors about updater-script.

That's when I checked again your 3.0.0Alpha1 announcement and stupidly start thinking things were now quite different with no need anymore for .patch files or something..

I did had doubts about about my wrong conclusion when I noticed I had same updater-script error whith gummy on 2.5.3 patcher version but well I prefered stop posting ****s/editing stuffs for a moment lol.

Just for info and maybe next time,updater-script error output was:

Detected Gummy zip
--- Please wait. This may take a while ---
Creating boot image--- ERROR BEGIN ---
--- STDOUT BEGIN ---
patching file META-INF/com/google/android/updater-script
patch unexpectedly ends in middle of line
--- STDOUT END ---
--- STDERR BEGIN ---
cygwin warning:
MS-DOS style path detected: c:\users\g3\appdata\local\temp\tmp_sy3ni
Preferred POSIX equivalent is: /cygdrive/c/users/g3/appdata/local/temp/tmp_sy3
ni
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
/windows/hctap: **** malformed patch at line 44:
--- STDERR END ---
--- ERROR END ---
Failed to apply patch

Is it something related to those "set_metadata" lines we have now(?) on 4.4 builds?

It was a "working" updater-script though,only difference i noticed is there's a "script succeeded: result was [system]" message displayed in recovery at the end of gummy zip installation which turned to "script succeeded: result was [0]" with my dualboot version.

Additionally there's some strange (to me) story about updater-script script asserts lines,there was status 7 error on jfltexx devices with gummy jfltexx build which could be solved that way:

http://xdaforums.com/showpost.php?p=47462407&postcount=68

Put jfltexx assert lines on top or remove only the abort output messages.

Meanwhile I've read this from Pawitp, i9000 CM maintainer:

http://xdaforums.com/showpost.php?p=47536418&postcount=346
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Actually, what you did was exactly right. That error is caused from the formatting of the patch being wrong. If you used my patch generator script, it would result in that. I haven't had a chance to fix it yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here is the first beta release for version 3.0.0. Changes:

Add support for removing device check asserts

Update HellyBean patchinfo to remove device check asserts

Simplify patchinfo files by moving auto-patch functions to common.py

Fix bug where the wiping of primary cache is not caught by the auto-patcher

Add support for Gummy

Add support for Vanir

Add support for Dirty Unicorns

Update Negalite patch for r12

All AOSP ROMs are 100% auto-patched now

Added Kit Kat ramdisk support for Kit Kat ROMs that do not mount apnhlos or mdm in fstab

Target Kit Kat for Android GUI (supports new file manager UI)

Still not fixed:

Patch generator in Windows
[Galaxy S 4 i9505 Original Android Development] gaww:
Not sure where we are with gapps - is there a patchable one or do we still need to manually pus the apps?

Answered my question - patched PA Gapps and Gummy, flashed and nooted Ok. Have WiFi also. Have noticed switching ROM's is now rather slow. Ith might be ann aspect of Gummy when booting up, but switching over to primary is also slower than before. Not a complaint - just an observation.

Great job OP !
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
how did u patch the gapps Kitkat odex ?

i got unsupported zip detected?

did u patch it manually ?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Chen, you mentioned awhile ago that the code for a triple boot was already written, just wondering if that's something that we could play around with in the near future, I'm not exactly asking for any eta, just wondering if that got pushed to the back burner since 4.4
[Galaxy S 4 i9505 Original Android Development] gaww:
I used the 20131111 full version of the Gapps from the below link and patched it with the Android patcher (the Windows one doesn't work). Did the same with the Gummy 4.4 ROM. Working real good so far.

http://xdaforums.com/showthread.php?t=2397942
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The auto-patching stuff really set me behind on triple (or more) boot. Now that AOSP ROMs can be completely auto-patched, I just need to modify a few lines in:

https://github.com/chenxiaolong/DualBootPatcher/blob/master/patches/dualboot.sh

https://github.com/chenxiaolong/DualBootPatcher/blob/master/ramdisks/init.dualboot.mounting.sh

to map eg. /cache/triple -> /system instead of /system/dual -> /system

If you plan on triple booting an AOSP ROM, remind me tomorrow and I'll throw together a test version of the patcher :)
[Galaxy S 4 i9505 Original Android Development] rlorange:
Guys I manually patched PA full gapps 4.4 for dual boot.

https://db.tt/ZcMmsYPG

-Unzip your I unpatched gapps

-unzip the patch zip linked above

-copy the contents over replacing the old files

-rezip and flash in recovery over cm 11 installed as 2ndROM

NOTE latest cm11 nightlies will NOT overwrite the gapps when you flash. Nice!
[Galaxy S 4 i9505 Original Android Development] Bejda:
What's up with PA Gapps peoples?

They never ceased to be supported/working for me no matter if it's 4.3 or 4.4 version and this on any android or windows patcher version if that matters.
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
was the gapps odex ?

i need the odex gapps to RUN ART mode on the kitkat.

did you guyz manage to run ART on it ?
[Galaxy S 4 i9505 Original Android Development] gaww:
10 of the 21 apps are odexed.

I am using ART right now on patched Gummy ROM and these patched Gapps. Of course Titanium doesn't work, so I did what I needed to do with it before I tried ART. One minor thing - it has set the CPU to 2.1 GHz and i cannot change it on ART. I think I set it that way on dalvek.

Also, first time I tried ART (on earlier unofficial CM11) I had root issues, so I flashed BETA-SuperSU-v1.72B first on the ROM and had no issues with root this time.

---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------

Good to know about the non-overwrite. Again, the DualBootPatcherAndroid-3.0.0Beta1-signed app patched them OK also.

Now get yourself back over to your duel boot backup and install app and update it - lol.
[Galaxy S 4 i9505 Original Android Development] Kondra007:
When trying to patch latest noobdev's CM11 port (19th November) patcher says:

ROM has built in dual boot support

Unsupported zip

So, what should I do now?
[Galaxy S 4 i9505 Original Android Development] eilex17:
Yess, THANKS YOU!!! :o
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thank you! yeah, I've been waiting for this!

Отправлено с моего SM-A510F через Tapatalk
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Hey Chen have you pinned down the problem on the Oneplus 3? I attached logs in my previous posts.Please check them out, thanks.
[Galaxy S 4 i9505 Original Android Development] dhyah:
Can you surport note5 N9200? （能支持9200吗？我试过sprint 那个不行，打包后刷入，无法启动到刷入系统，主系统也进不去）
[Galaxy S 4 i9505 Original Android Development] physwizz:
Looks great.

Only hope it doesn't give me a recovery on reboot.:)
[Galaxy S 4 i9505 Original Android Development] physwizz:
My log after recovery on reboot after flashing a new rom with a recent patcher.

View attachment MultiBoot.log
[Galaxy S 4 i9505 Original Android Development] agueijo:
Someone installed Imperium Rom G4 for LG h815 on data slot as secondary?

I read that using aroma installer first make the zip patch and then install from TWRP

(I have already installed and running, Stock based Genisys as primary and CM13 on data slot, without any problem)

Someonen with imperium rom on data?
[Galaxy S 4 i9505 Original Android Development] nutpants:
Can you add support for the tab pro 12.2?

Get log info attached
[Galaxy S 4 i9505 Original Android Development] Green soul:
Thanks
[Galaxy S 4 i9505 Original Android Development] Graziano890:
Support n7100 t03g

Please support note 2 n7100 t03g thanks..
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
I've been checking for this update about every other day!! Glad to hear and see you're still on the trail.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
You will never know.
[MENTION=4277844]chenxiaolong[/MENTION] is now ignoring al LG G3 users... I provided also the files for the bootui monts ago but I still have no answer since that...
[Galaxy S 4 i9505 Original Android Development] Sr_psycho:
Hi! Where can I download the build with support kenzo ?
[Galaxy S 4 i9505 Original Android Development] celoxocis:
Do we need an special TWRP version that works with Dual Boot patcher?
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
NO
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. I tried the test 2842 build you pushed for Oukitel K6000 Pro and it seems to work. Now I switched to a 64bit rom and can't use the patcher anymore, I get"could not connect to mbtool". May be that's because I changed the twrp image also, because the previous was not working on 64bit. Meanwhile I succesfully flashed in the new recovery one of the previously patched zips when I was using 32bit rom and the old twrp and they installed fine, but still didn't tried to boot one of these roms. I'm rooted and all that not the problem causing the mbtool issue, also the files in the /data/data/github... are all in place. I even extracted the taz.gz file from the apk to check. I don't have the Multiboot.log, daemon or kernel.log in the /Multiboot dir or any other files created. I uploaded the new files from the 64bit rom in hope you can make it to work again.

Edit: Tried to boot one of the roms previously patched and they don't boot, the phone just boots the primary rom
[Galaxy S 4 i9505 Original Android Development] celoxocis:
Can you point me to an github commit to know what is required for a device to work with the dual boot patcher?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
I don't think a single commit may tell you that, also if you aren't planning on building it yourself, why would you worry about that? Just try it on ur device and if it fails, provide its log to the dev.

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

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] celoxocis:
Before I supply a patch I would like to test it.

And yes I know how to compile it and build my own ROMs, Apps, etc

I'm just not familiar with the dual patcher as I never had to use one. Now that I have a new device with 64GB I consider adding support for it. To boot in the stock ROM whenever I feel like using the stock camera features.

And no it is not supported yet.

As far as I can see those are all the changes needed to add for a device support?

https://github.com/chenxiaolong/DualBootPatcher/commit/1aa788268a9498fbaa1d46a8c64ff146c8cce4d7
[Galaxy S 4 i9505 Original Android Development] Eagle:
"Could not determined boot partition." Please include hlteskt in codenames. [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Fixed the issue "could not connect to mbtool" I was experiencing by reflashing the recovery with SP Flash Tool. Previously I just installed the new twrp over the old release with Flashify. It was refusing to mount the /system rw, no matter I was rooted with SuperSu 2.78. Now all is good, but my question about the patcher working correctly on the new 64bit rom remains. Cheers guys.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
This commit is only for adding boot ui support for specific models, not the actual boot patcher support unless you are looking for that specific feature.

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

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] Sr_psycho:
Not installed GAPS, what's the problem?

https://app.box.com/s/h565kn7z678bjf9451u3yllgeli27m0h
[Galaxy S 4 i9505 Original Android Development] celoxocis:
The first file is bootui support the second file is initial device support.

What do you mean by "boot patcher support"?

Does the device kernel require to be patched for patcher support?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Sorry, missed the second file and yes, ramdisk needs to be patched.

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

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] celoxocis:
Please elaborate on ramdisk needs to be patched?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Boot image needs to be patched to load the rom files of secondary and later from alternate locations.

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

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
https://github.com/chenxiaolong/DualBootPatcher/tree/9.0.0-staging/data/devices

Take one file as base and make the necessary modifications to your device. Only this, the dev does the rest
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
Guys I'm using the latest version on OnePlus 3 and it was working fine two days ago I was booting three roms.

I patch rom for dualboot then install on data cm14 was working but now after reboot phone vibrates three time and goes to twrp.

I don't know what happened?

I installed again but same three vibration and twrp