yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] fanfzero:
Ok, so I've tried JDC rom (AOSP) as secundary and it works perfect, but I need a TW rom, I've tried with Astra 2.5, Imperium L and Hulk rom, they all have AROMA installer and make the 4 rumbles thing, I've tried setting kernel on primary rom and updating ramdisk, but no luck, don't know if it happens because of aroma installer or what
[Galaxy S 4 i9505 Original Android Development] jroq8400:
http://xdaforums.com/showthread.php?t=3259562
[Galaxy S 4 i9505 Original Android Development] Gerxp:
Anyone?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is a bug in OxygenOS. They probably implemented their file manager using DocumentsUI, but didn't disable the zip browsing functionality when opening files. I've added a workaround in 8.0.0.r2315.ga23b041 :)

--------------------------------------------------------------------------------

8.0.0.r2317.gd923057 :)

--------------------------------------------------------------------------------

Just bought myself an S7 Edge :) While I'm probably not going to root it (because of Samsung Pay...), I will definitely add support for it.

--------------------------------------------------------------------------------

Thanks for the logs! However, if it automatically reboots to recovery, I'll need to see /sdcard/MultiBoot/kernel.log to see what's going on.

By the way, if you flash /sdcard/MultiBoot/[Your ROM]/boot.img.before-ramdisk-update.img, it will restore the original kernel before the ramdisk update happened.

--------------------------------------------------------------------------------

Oh well... It's not too big of a deal compared to our huge pile of hacks and workarounds :)

--------------------------------------------------------------------------------

In this case, that custom kernel can't be used. With the multiboot code added to the ramdisk, it no longer fits in the boot partition (too large by 366KB). Unfortunately, there's nothing I can do about that.

--------------------------------------------------------------------------------

Should be fixed in the latest version now :)

--------------------------------------------------------------------------------

Unfortunately not, if you don't have a custom recovery yet. The app doesn't fully emulate the recovery. What it does is takes all of the files from the recovery partition and uses them to create an environment very similar to the recovery. If you don't have a custom recovery installed, then the in-app flasher won't work either.

--------------------------------------------------------------------------------

Added support in 8.0.0.r2318.g6004801 :)

--------------------------------------------------------------------------------

8.0.0.r2319.gf1fc747 :)

--------------------------------------------------------------------------------

8.0.0.r2320.gdd41a25 :)

--------------------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added support in 8.0.0.r2321.ge43117f :) Mediatek devices have traditionally had many issues with DualBootPatcher, but hopefully this device is a little better.
[Galaxy S 4 i9505 Original Android Development] Gerxp:
[MENTION=4277844]chenxiaolong[/MENTION]

I don't have the option to update ramdisk in the 3dotmenu.

I did flash the kernel.

See my message above yours

*
[Galaxy S 4 i9505 Original Android Development] alahkel:
OMG already?!! you are the best, thank you so much, I really appreciate it and a donation will come, thank you!!

EDIT: I have an issue, kernel is set correctly but when I try to patch a zip in-app the app fc, don't know if thats an issue with miui (I have miui.it version, based on china developer 6.3.3) or else, log is this (great thing that miui gives you the exact log when an app crashes).

android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CREATE_DOCUMENT cat=[android.intent.category.OPENABLE] typ=*/* (has extras) }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1776)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1613)
at android.app.Activity.startActivityFromFragment(Activity.java:4382)
at android.app.Fragment.startActivityForResult(Fragment.java:1111)
at android.app.Fragment.startActivityForResult(Fragment.java:1095)
at com.github.chenxiaolong.dualbootpatcher.patcher.PatchFileFragment.selectOutputFile(PatchFileFragment.java:724)
at com.github.chenxiaolong.dualbootpatcher.patcher.PatchFileFragment.onConfirmedOptions(PatchFileFragment.java:844)
at com.github.chenxiaolong.dualbootpatcher.patcher.PatcherOptionsDialog$1.onClick(PatcherOptionsDialog.java:137)
at com.afollestad.materialdialogs.MaterialDialog.onClick(MaterialDialog.java:336)
at android.view.View.performClick(View.java:4811)
at android.view.View$PerformClick.run(View.java:20136)
at android.os.Handler.handleCallback(Handler.java:815)
at android.os.Handler.dispatchMessage(Handler.java:104)
at android.os.Looper.loop(Looper.java:194)
at android.app.ActivityThread.main(ActivityThread.java:5549)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:964)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:759)

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] messi2050:
Thx alot for adding support for j7elte

https://github.com/chenxiaolong/DualBootPatcher/commit/f1fc7470434d82d86ba8b3bc1295fa15096f1cca

Sorry for requesting again but I'm using the 3g model Can u add support for it too, it's using exactly the same j7elte fstab , but the device name is j7e3g & j7e3gxx instead of j7elte& j7eltexx

Regards
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION], hello sir!

I've attached logs from my bootloop into recovery after installing secondary rom,AOSP!

I hope you can find something useful!

Thank you

https://www.dropbox.com/s/q9varq93p4rl7j2/20160313.023642.tar?dl=0

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
squashfs? HA! I accept this challenge!

In all seriousness, could you link to a ROM that uses squashfs? I'll need that to do some testing, but I don't think we need to add any hacks to make this work. I'll probably just have to disable the secondary slot so nothing gets installed to /system (since squashfs is not writable).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, the kernel logs are missing in there. Could you link me to the AOSP ROM? I'll take a look and see if I can find anything unusual.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
ROM

http://duckbox.info/android/lt03lte/aosp-6.0/latest.php/lt03lte

Thread

http://xdaforums.com/showthread.php?p=63958833
[Galaxy S 4 i9505 Original Android Development] alahkel:
ok it's definitely a miui issue, I just tried flashing as primary an aosp rom and the zip patching worked perfectly from the dualboot patcher app on the aosp rom

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] alahkel:
Since I cannot use the in-app patcher on miui rom, I was trying the latest win app to do that but it gives me that error.

I suppose I can't use the 20th feb build since only latest build has hennessy support :(

EDIT: I've replaced the 20th feb win32 build's libmbp with the one in the latest win32 build, now I'm patching my zips, dunno if I need to replace other files..
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done :) https://github.com/chenxiaolong/DualBootPatcher/commit/217eba99bfd379be30c0461fc5a834f87235494a

8.0.0.r2322.g217eba9
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're welcome :)

It looks like your version of MIUI is missing the DocumentsUI component of Android (which shows the file chooser for saving files). Which version of Android is the ROM based on?

Anyway, I've added a workaround in 8.0.0.r2323.g2bb105f that should hopefully fix the problem.
[Galaxy S 4 i9505 Original Android Development] alahkel:
Omg you're right, I did notice in that log something DocumentsUI related but didnt actually "see" it[emoji14]

It is miui v7 based on android 5.0.2, it is the versione from miui.it which is based on latest china dev. Actually if I remember well the official miui.com china dev/stable has documentsUI.. I believe..

Btw graphically it lacks the classical aosp android file-chooser and it sends you directly to the open-with overlay window (on miui) so that I can choose es file explorer for example.

Didn't notice at first.

I'll try your latest version, but hey you're really fast! Your dev skills are great and you are a really nice and gentle person ?

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You should copy:

Qt5Core.dll

Qt5Gui.dll

Qt5Widgets.dll

platforms/

from the old Feb 20th build to the new one instead of copying libmbp.dll (that will almost certainly break at some point). I cross-compile the patcher from Linux to Windows and unfortunately, a new update of the Qt libraries provided by my Linux distribution is broken.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's at the bottom of the ROM details screen:

[youtube]kd_8N3Sh20g[/youtube]
[Galaxy S 4 i9505 Original Android Development] alahkel:
[MENTION=4277844]chenxiaolong[/MENTION] Installation of patched zip gets aborted, I'm attaching here the multiboot log file. Thank you for your time and sorry for the bother :(
[Galaxy S 4 i9505 Original Android Development] Gerxp:
When I click on the 3 dot-menu I see a white screen. The screen shown by you is out of sight. It is way below. So I have to scroll up for the screen to show up. And between each option there is another white screen. So for each option I have to scroll up almost 1 page.

Really weird.
[Galaxy S 4 i9505 Original Android Development] ShehabElkhaligy:
Hi

Can you add support for Samsung galaxy grand 2 g7102 please

I attached the log file thanks for your time and hard work

http://www.mediafire.com/download/9rt3qfvltb09qx4/20140101.023057.tar
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks, fixed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should be fixed in the latest version now (anything newer than 8.0.0.r2315.ga23b041). Could you upgrade to the latest version of the app and see if you still have that issue?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2326.gfa65209 now lets you set the number of files to patch in parallel in the settings. You can set that to 1 to have it patch files one by one. I'll take a look at the issue with renaming ROMs.

(And yes, a dark theme is coming soon now that the Android support library has support for that)
[Galaxy S 4 i9505 Original Android Development] Gerxp:
Latest version is fine :) thanks
[Galaxy S 4 i9505 Original Android Development] gbakeriv:
I have this running with two versions of the latest 5.1.1 firmware on my n920T note5.

If I want to install xposed on the primary, is it just as simple as patching Wanam's module for Samsung 5.1.1 devices, flashing in TWRP and rebooting?

Kinda just wondering how best to update the primary app, I've been digging in this forum a while. Took some lucky tinkering in the build.prop to get dual booting to function properly in the first place and am a bit nervous about diving in and having to redo it all!

Also, how do nandroid backups function with this?

Huge thanks ahead of time!
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I am at it again. Now I am trying to install Marshmellow odin tar OTA. I am installing in data-slot. I first tried with what worked before 2265. It successfully patched, but failed in flashing. I thought it flashed successfully, but the logs don't show that (attached tar.zip). It booted to recovery after several failed attempts. I got logs. Next I tried with latest patcher 2326. It fails right away in flashing. I included multiboot.log. It appears to be something with efs again. Let me know if you need anything else.
[Galaxy S 4 i9505 Original Android Development] gaww:
I accidentally hit the Primary ROM's kernel in Set current kernel as... while in the secondary ROM.

Of course, that set the secondary kernel as the primary one also, so no way to get back into the primary ROM. Rebuilt from recent TWRP backup plus same day secondary ROM backup.

Just thought having a step after hitting the set kernel to confirm it might be a good idea to avoid this situation.
[Galaxy S 4 i9505 Original Android Development] gaww:
updating primary

I just tried for the first time to update the primary with Wicked v8. The install script did not have a formatting of the system partition, so I dirty flashed flashed it as is.

It booted up fine, but the secondary ROM did not show up in the duel boot switcher. This is where the separate secondary ROM backup/restore tool came in handy - was back up in a few minutes.

Great job all.
[Galaxy S 4 i9505 Original Android Development] jova33:
I did this too. Just went into recovery and reflashed the kernels. Flawless victory.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] Bejda:
Hello all,someone told me latest (20131105) nightly gave error when he tried to patch it.

I can confirm this on my side,output is:

Detected Cyanogenmod based ROM zip
--- Please wait. This may take a while ---
Extracting ramdisk--- ERROR BEGIN ---
--- STDOUT BEGIN ---
patching file init.target.rc
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file init.target.rc.rej

--- STDOUT END ---
--- STDERR BEGIN ---
cygwin warning:
MS-DOS style path detected: c:\users\g3\appdata\local\temp\tmprg3j3a\extracted

Preferred POSIX equivalent is: /cygdrive/c/users/g3/appdata/local/temp/tmprg3j
3a/extracted
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

--- STDERR END ---
--- ERROR END ---
Failed to apply patch

I had 1.18.1 patcher tool at hand (version just before automatic ramdisk patching then) and it worked fine with same nightly.

Only previous nightly i could test with 2.5.3 patcher version that worked fine is 20131030 one.
[Galaxy S 4 i9505 Original Android Development] omnifarious:
You can also use the Dual Boot Utilities zip to switch to secondary, set kernel and switch to primary.

---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------

Next time just flash the primary roms kernel.
[Galaxy S 4 i9505 Original Android Development] Brandroid28:
Can someone share how to run the init.d script for sharing apps? I created a new script in SManager. Does it need to be stored in a certain folder or run a certain way?
[Galaxy S 4 i9505 Original Android Development] Bejda:
I guess editing primary rom updater-script before flashing a new one for it doesn't delete whole /system never worked anyway, don't know why..

If I remember well (been a long time I didn't try) no matter what edits I've made to primary rom zip before flash i always ended up with secondary system deleted (i guess i never seen a report saying it worked since the thread started btw).

So now I don't pay attention and always use alternative method which is just flash new primary rom as it is and flash again secondary later.

It's ok,as stated in OP we don't loose any secondary data but if you made some system mods to your secondary rom it brings you back to "stock"...so yeah this is where rlorange app may come in handy,especially for peoples like me who often mod some system stuffs.

I didn't really followed rlorange app development for now , don't know if it's possible but in that specific context it could be useful (regarding backup speed and storage space used) to have option to only backup secondary system (without secondary data then as,still in that updating primary rom context,it stays untouched).

Of course if meanwhile someone managed to update primary rom without loosing secondary system let us(me if I'm saying **** lol) know :)
[Galaxy S 4 i9505 Original Android Development] royredman:
Is there a way I can make a nandroid backup of the dual boot roms onto one file? So, if I were to wipe and do a nandroid restore, I would have my two roms available again?
[Galaxy S 4 i9505 Original Android Development] Shanks:
Yeap if you make a nandroid backup it will backup your 2 roms, so when you restore a backup you will restore the 2 roms
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Somehow the latest version is not patching the pac, iokp rom...but version 1.14 is working....due to the outdated ramdisk it's fc/boot looping....

Is that issue is for me? Any solution to it
[Galaxy S 4 i9505 Original Android Development] royredman:
can i use the automatic patcher for installing gaps onto the secondary rom?.

Edit: Nevermind. Found it out myself
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I think they did something to the latest pac nightly that makes it not patch well... Idk, is there a way to get a log from the patcher app?
[Galaxy S 4 i9505 Original Android Development] Bejda:
The app has a better log support since first versions (gives more infos on logs), I'm not sure it will be of great help here but to get logs from a specific app/process a monitoring app can be of great help (at least to reduce log's size lol when like me you don't really master logcats commands).

I use OsMonitor since a long time for such cases,once the app running and some settings activated like root permission,status bar icon/shortcut under notification panel and such you can try to patch PAC. As the app doesn't fc it will still be there under OsMonitor running processes list (that you can sort to your liking (ram usage,cpu,pid,..),just long press patcher.apk process>watch log and you'll see also an export option.

Probably many others apps that can achieve this but i really appreciate that one + open source ..here ends that infomercial post,sorry :laugh:
[Galaxy S 4 i9505 Original Android Development] royredman:
Does anyone know if dirty Unicorns for the Verizon Galaxy S4 work as a secondary? It's considered an AOKP rom
[Galaxy S 4 i9505 Original Android Development] royredman:
can I do a factory reset in order to just get back to having one rom again?
[Galaxy S 4 i9505 Original Android Development] traicer:
anyone got Wicked V8 for tmobile patched up? i tryed patching it myself but i failed =(
[Galaxy S 4 i9505 Original Android Development] Bejda:
You can but if you want to keep your primary rom as it is you better use dual-boot utility zip to wipe secondary stuffs.

Only thing left would be /system/dual-kernels folder that you can just delete manually (won't hurt to let it there anyway and will disappear next time you'll flash a rom).

---------- Post added at 01:07 AM ---------- Previous post was at 12:55 AM ----------

Can I ask what's your intention? :) You're aware that only secondary rom needs to be patched yeah?

You want to dual-boot two Touchwiz rom's? If not why not using this big zip one as primary and flash a more easy to handle (and maybe already supported) zip as secondary?

By easy to handle I mean the zip is 1.5gb..if someone wanted to help you or Chenxialong to add support for that rom himself we would have to download that big thing.

You may have reasons huh,i just wonder and want to make sure you know only secondary rom and others zip needs to be patched ;)
[Galaxy S 4 i9505 Original Android Development] traicer:
well i wanted to use the TW ROM as my secondary since i have cm10.2 running nicely right now. i think ill do what you mentioned ;)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Ha yeah but.. be aware of latest nightlies then :o

See my report on previous page + `SBR` and HearMeWhisper ones after,it's about the same thing i guess.

(only pre-automatic ramdisk patcher [1.18.1] version will work but it seems the patched zip won't be functional ..)
[Galaxy S 4 i9505 Original Android Development] traicer:
so i wont be able to auto patch the latest CM10.2?
[Galaxy S 4 i9505 Original Android Development] alahkel:
It looks like it was something in the zip file, I tried flashing the intended secondary rom (aosp 5.0.2 android) as primary (in place of miui rom), then patched the miui zip and flashing it as secondary/data slot was giving me an error (assert preloader command wasn't "working") so I modified the patched zip (removing that command, I thought it was used on mtk devices through spFlashTool way of flashing roms, not via flashable recovery zip :/ ) and it flashed just fine. See pic attached below.

Now I'm gonna try to boot it, fortunately I've downloaded the dualboot utilities[emoji14]

Previous multiboot log was about the other rom zip file, the aosp one, which now I'm running as primary (it flashes just fine as primary via twrp, just as fine as the miui zip flashes as primary via twrp). What do you think could be the problem?

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, it looks like the check I've added to disable /efs mounting on non-Samsung devices isn't working. It currently checks the "ro.product.manufacturer" property, but your recovery sets "ro.product.manufacturer=unknown" in its /default.prop. I've just added an additional check in 8.0.0.r2327.gd5c4139 for "ro.product.brand=Samsung", which should hopefully fix the issue.

Relevant line in MultiBoot.log:

[D] Not mounting EFS partition because this is not a Samsung device

Another thing to note is that SELinux may prevent a multibooted TouchWiz 6.0 ROM from booting. If Samsung brought the SELinux changes from the S7 to the S6, then we'll definitely run into issues. Unfortunately, I can't work on fixing this right now because I upgraded from an S6 Edge+ to an S7 Edge on launch day, not knowing that the bootloader is locked on all US variants.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that's the way to do it! I always recommend patching any zips you want to flash in the primary ROM since it prevents the zip from accidentally modifying files of other ROMs (such as by wiping cache). This however causes the installation to take significantly longer because the current primary ROM will be copied to a temporary folder and then copied back when the flashing completes. This shouldn't be too bad on devices, like the Note 5, that have really fast storage.

Nandroid backups will backup all of your ROMs. However, it will not backup the kernels since /sdcard is never backed up by TWRP. To make a complete backup of all ROMs, I recommend making a regular system/cache/data/boot backup from TWRP and then simply making a copy of the /sdcard/MultiBoot folder.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you link me to the ROM so I can take a look at what the preloader command you mentioned does? The last MTK device I added support for (Lenovo K3 Note) also did some weird things in the updater-script, but I could never figure out why it didn't work properly since it would always crash if I ran the flashing process in a debugger. Hopefully your device will be a little better :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Good day [MENTION=4277844]chenxiaolong[/MENTION], did you find anything to explain my bootloop from my previous post(http://xdaforums.com/showthread.php?p=65806735)

Oh, by the way the dev made an update of that ROM and here's the link, it's still looping though http://duckbox.info/android/lt03lte/aosp-6.0/latest.php/lt03lte

---------------------------------------------------------------------

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------