yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Definitely not. Knox only trip if you try to flash anything unofficial from odin.
[Galaxy S 4 i9505 Original Android Development] bnwg:
I heard it will trip knox if either kernel or recovery is modified (i.e. Custom kernel or recovery like twrp). If both of them stay unmodified (i.e. Stock) it won't get into the knox trip even with custom rom/mod.

Update ramdisk might modify the kernel hence I want to double confirm.

If it will not trip knox i'm really looking forward to the new feature (boot menu) with nice UI that OP just posted.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
I think you should wait for more replies from more experienced members before trying anything. But my knox is counting at 4 and i switch roms aevery day countless times and it never go up. It only goes up when something unofficial is flashed via odin. But still please make sure. Good luck
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes it will. KNOX is tripped when flashing any kernel (boot image) or recovery that's not signed by Samsung. DualBootPatcher will change files in the ramdisk, which is part of the boot image, making it no longer officially signed. Thus, KNOX will definitely be tripped.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
Thanks for making it clear. [emoji4]
[Galaxy S 4 i9505 Original Android Development] bnwg:
Thanks for the info and advices.

IMHO if updating ramdisk really would trip knox then knox counter would only go up when applying update ramdisk as this is the process modifying the kernel that flags knox trip and counter. Changing ROM itself would not make knox counter going up as it just boot up different ROM with the same kernel.

My case is that Note 3 rooted at 4.4.2 without knox trip and then upgrade to 5.0 by flashfire (bootloader and modem by odin) with xposed installed via flashfire as well.

If updating ramdisk would not trip knox then I would play around other custom ROM with new feature boot menu implemented in case something goes wrong I can switch back to the primary ROM. Of course the next question may be if stock kernel would be fine with custom ROM that I want to play around. Or even if I get bootloop can I still get to boot menu, the new feature that is coming soon.

---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------

Thanks for clarifying.

I just finished posting before I saw your explanation.
[Galaxy S 4 i9505 Original Android Development] andrei7radu:
Is there a way to revert the ramdisk update procedure?

Thanks,

a7r
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes.

If you can still boot, simply copy /sdcard/MultiBoot/[Your ROM]/boot.img.before-ramdisk-update.img to /sdcard/MultiBoot/[Your ROM]/boot.img in any file manager and switch to the affected ROM again.

If you cannot boot, from TWRP, go to Install -> Images (Bottom Right button) -> Flash /sdcard/MultiBoot/[Your ROM]/boot.img.before-ramdisk-update.img. This should let you boot once. Then, follow the steps above.
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Hi bro please check this. And guide me if I'm not on the right track.

http://xdaforums.com/showthread.php?p=67163160

http://xdaforums.com/showthread.php?p=67198156
[Galaxy S 4 i9505 Original Android Development] khaoticking:
Thank you so much for this tool I am a huge flashaholic and this saves me from having to restore from backups or reset everything every time I switch ROMs
[Galaxy S 4 i9505 Original Android Development] andrei7radu:
Hey, thanks for your reply. And what if the restoration would be for the primary ROM? Same procedure should be followed?

Thanks, again

a7r
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yup, it's exactly the same process, no matter if it's the primary ROM or any other ROM. DualBootPatcher, in general, does not treat the primary ROM differently from other ROMs. Usually, if a feature or procedure works for one ROM, it will work for the rest.
[Galaxy S 4 i9505 Original Android Development] Benrap:
I see you made a TW rom in a data slot. HOW??!?!?! TW doesn't come in a zip, so how do you get it in a zip? Can i get it too for my gs5?
[Galaxy S 4 i9505 Original Android Development] corncobman:
It could be a TW based custom ROM.
[Galaxy S 4 i9505 Original Android Development] timz1313:
Yeah good job thanks..
[Galaxy S 4 i9505 Original Android Development] ComputerNmyPocket:
Add Support for Samsung Galaxy Tab S2 9.7 Please

Hi chenxiaolong,

Would you please add support for the Samsung Galaxy Tab S2 9.7" (T810 WiFi Model)?

I'm trying to attach the getlogs file.

Thanks for your work. I've been using it on my S4 for a long time. Thanks! :D

Edit: I just tried the latest snapshot and it already works! Guess you already added the device at some point. Thanks again, life is good!
[Galaxy S 4 i9505 Original Android Development] vitaly51370:
Hi chenxiaolong, Thanks for your work, add support for LG G3s D724 please:
[Galaxy S 4 i9505 Original Android Development] skezza:
I'm trying update the ramdisk but get please wait and no response. Subsequently when I try switch Rom it's complaining about the ramdisk being too big for the boot img.

Any suggestions?
[Galaxy S 4 i9505 Original Android Development] skezza:
----- beginning of main

06-16 22:03:48.340 6176 15047 D UpdateRamdiskTask: Starting to update ramdisk for primary to 8.0.0.r2468.gad0b0d3-SNAPSHOT

06-16 22:03:48.877 6176 15047 D libmbp : Boot image is a plain boot image

06-16 22:03:48.878 6176 15047 D libmbp : Found Android boot image header at: 0

06-16 22:03:48.878 6176 15047 D libmbp : - magic: ANDROID!

06-16 22:03:48.878 6176 15047 D libmbp : - kernel_size: 7651728

06-16 22:03:48.878 6176 15047 D libmbp : - kernel_addr: 0x80208000

06-16 22:03:48.878 6176 15047 D libmbp : - ramdisk_size: 2994176

06-16 22:03:48.878 6176 15047 D libmbp : - ramdisk_addr: 0x82200000

06-16 22:03:48.878 6176 15047 D libmbp : - second_size: 0

06-16 22:03:48.878 6176 15047 D libmbp : - second_addr: 0x81100000

06-16 22:03:48.878 6176 15047 D libmbp : - tags_addr: 0x80200100

06-16 22:03:48.878 6176 15047 D libmbp : - page_size: 2048

06-16 22:03:48.878 6176 15047 D libmbp : - dt_size: 0

06-16 22:03:48.878 6176 15047 D libmbp : - unused: 0x00000000

06-16 22:03:48.878 6176 15047 D libmbp : - name:

06-16 22:03:48.878 6176 15047 D libmbp : - cmdline: console=null androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3F ehci-hcd.park=3

06-16 22:03:48.878 6176 15047 D libmbp : - id: a1c91113a29460b28d807acf93e3851e95c8d504000000000000000000000000

06-16 22:03:48.894 6176 15047 E libmbp : Ramdisk image exceeds boot image size by 163840 bytes

06-16 22:03:48.899 6176 15047 E UpdateRamdiskTask: libmbp error code: 150

06-16 22:03:48.900 6176 15047 E UpdateRamdiskTask: Failed to patch file!

Edit:

Gone back through the thread and had a read. Seems you think it's because the kernel is bigger than the boot img. OK. What's the best way of going about fixing it? Flashing via Odin from scratch?
[Galaxy S 4 i9505 Original Android Development] skezza:
By the way, what I'd like to do, is simply have a TW ROM and CM13 ROM. I don't mind which is primary whatsoever. I just would like to keep the features such as the TW camera for when I need them, but have the lovely speed of a CM ROM. Unfortunately, I can dual boot, but I simply cannot get it to app share due to this ramdisk issue. Is the issue with my kernel or my partition table or what? I'm going to try aurora kernel to see if I can fix this issue, but I'm totally at a loss here. Would flashing from scratch with Odin fix the issue?
[Galaxy S 4 i9505 Original Android Development] dave7802:
[MENTION=4277844]chenxiaolong[/MENTION] Any news on support for the S7 edge?
[Galaxy S 4 i9505 Original Android Development] skezza:
Right, I've reflashed the entire stock ROM via Odin. Flashed on TWRP 2.8, will update to 3.x. Let's see if I can get this working :(

Might download an older version of the patcher, maybe that'll help?

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

Flashed stock ROM, flashed TWRP, flashed Imperium 13.1, installed the latest dual boot patcher, and once again we have Please wait when trying to update ramdisk :'( Same issue.

I guess I can try with an old version as I said earlier, just don't know why I'm having these problems when others aren't :(

Is there a guaranteed safe ROM to use with this?

---------- Post added at 03:20 PM ---------- Previous post was at 02:33 PM ----------

Update:

Working fine with Kushan it seems, although the APK isn't injected into the secondary ROM. I assume you have to install each app twice? Once per rom?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Yes, then you must set up each rom to share data for each app you want to share.
[Galaxy S 4 i9505 Original Android Development] rkrohan:
[MENTION=4277844]chenxiaolong[/MENTION] can you please add Oneplus 3 support for dualboot?
[Galaxy S 4 i9505 Original Android Development] jjh2811:
Hi, [MENTION=4277844]chenxiaolong[/MENTION]

I have a question to ask..

Isn't it technically possible for installed roms to have their each modem.img?

As far as I know, all of the installed roms use primary's modem, right? (please correct me if I'm wrong.)

My device is LG G2 and I installed CM13 as primary rom and MIUI 7 as secondary.

For your information, MIUI 7 works properly only with kitkat modem. (not sure in the case of other device's MIUI)

If I flash LP modem for CM13, then MIUI 7 can't boot system(miui boot logo loop).

If I flash KK modem for MIUI 7, then both MIUI 7 and CM13 can boot but CM13 becomes unstable.

Is there any suggestion or do you have any update plan for this?

Would it be possible for the installed roms to have and use separate modem?
[Galaxy S 4 i9505 Original Android Development] turbopas:
How to Flash Gapps ...

Hi all, how to flash gapps on secondary rom's....
[Galaxy S 4 i9505 Original Android Development] bnwg:
Patch and flash
[Galaxy S 4 i9505 Original Android Development] hankching:
[MENTION=4277844]chenxiaolong[/MENTION] can you please add Jiayu S3 support for dualboot?
[Galaxy S 4 i9505 Original Android Development] cornelha:
The modem is flashed to a specific partition on your device. The amount of work it would take to load the modem using a looped image might not take much but could be problematic on most devices and there are way to many devices with different configurations to make this feasible inless devs from every device pitches in
[Galaxy S 4 i9505 Original Android Development] Andycar:
Hey, check this:

So, as you see [MENTION=736370]cornelha[/MENTION] it's already implemented.
[Galaxy S 4 i9505 Original Android Development] Benrap:
Flashing Dualbootutilities using TWRP 3.0.2-2 causes the device to reboot. Using 3.0.2-1 works. Can you fix this?
[Galaxy S 4 i9505 Original Android Development] jjh2811:
Thanks for your opinion.:)

I've tried. but That doesn't seem to be the solution for my problem.

Thank you for your interest in my problem anyway :)
[Galaxy S 4 i9505 Original Android Development] hankching:
awesome work! [MENTION=4277844]chenxiaolong[/MENTION]

Can you please add Jiayu S3 support for dualboot?

I tried using K50 device setting, it can install but it can't switch between roms.

Would you mind adding following information to this app?

Device: h560

Codenames: h560, s3_h560, Jiayu_S3

Name: Jiayu S3

Thank you for supporting this model.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Provide the logs from GetLogs.zip so that Chen can add support for your device.
[Galaxy S 4 i9505 Original Android Development] rkrohan:
I have updated the Oneplus.cpp and initiated the pull request. Please check it. I'm flashing the getlogs.zip right now

Thanks
[Galaxy S 4 i9505 Original Android Development] rkrohan:
Here is the result from getlogs.zip

You probably won't be able to see the attached file in Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Thank you for replying this message.

Here is the result from getlogs.zip.

There are two rom recovery, so i created two.
[Galaxy S 4 i9505 Original Android Development] hankching:
awesome work! [MENTION=4277844]chenxiaolong[/MENTION] [MENTION=5207461]Salman A.[/MENTION]

Would you mind adding new device to this app?

Thank you for supporting.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Sorry. But I'm not the dev. I meant that the dev, Chen, will need the logs to add support for your device.
[Galaxy S 4 i9505 Original Android Development] rkrohan:
Oh. Well I have uploaded the logs. I hope that he sees them
[Galaxy S 4 i9505 Original Android Development] hankching:
Thank you for answering.

I have uploaded it.
[Galaxy S 4 i9505 Original Android Development] DevGeo16:
Support for the Honor 5X

Can you add support for the Huawei Honor 5X? I used Multi-Boot on my Mate2 and it worked great. I just needed an upgrade, so I got the unsupported Honor 5X.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION]: really miss the backup feature implemented into Patcher GUI or TWRP Patcher in recovery.
[Galaxy S 4 i9505 Original Android Development] skezza:
Yeah worked it out now. Not sharing many apps. I use my primary ROM as a clean TW for Camera and not much else. CM13 is my secondary ROM and is my primary ROM. Loving how smooth it is :)
[Galaxy S 4 i9505 Original Android Development] Benrap:
Eta for the bootup ROM choice?
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION]: Is it normal, that flashing Resurrection Remix v5.7.0 zip file from CM13 takes more than 10 hour, when flashing to external sdcard (extsd-slot-rr270)?

Usually (if I am very patient) it finishes within 1-2 days (successfully), but I think this is not really a normal working way...

Using Dual Boot Patcher on Samsung Galaxy S4 i9505.
[Galaxy S 4 i9505 Original Android Development] bnwg:
Did I read it correctly that it is hours and days to finish flashing?
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
I own a i9505,and it takes a few minutes to flash a rom.In marshmallow, you cannot flash roms to ext sdcard,I tried myself. Nothing that Chen can do about it.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Yes, flashing from CM13, I stopped flashing after about 22 hour.

It stays at "Patching system image unconditionally".

Now trying from TWRP, but after about an hour still says "Patching system image unconditionally".

This slow flashing happens when flashing to external sdcard.

---------- Post added at 07:57 AM ---------- Previous post was at 07:52 AM ----------

Perhaps I should use the external sdcard fix on CM13, which made me possible to write to external sdcard under Marshmallow:

http://xdaforums.com/showthread.php?p=67381443
[Galaxy S 4 i9505 Original Android Development] Bejda:
I did the same (KT jb4.3 aosp 11/08 kernel boot.img + system/lib/modules files from its zip pushed in 20131110 nightly before patch) and it went fine.

Another way that may help you is to push nightly 20131030 boot.img before patch:

https://app.box.com/s/m3t7j0kkla57sloo9oog

I bet it will work (patch will be ok I tested but didn't flashed it) but you can also, once latest nightly patched that way , patch KT kernel zip and then push its boot.img + files in your «patched using older boot.img» 20131110 nightly zip,I made it that way too both worked.
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
Please add cm11 support

http://xdaforums.com/showthread.php?t=2520972

[ROM] CyanogenMod 11.0 | Android 4.4 KitKat [UNOFFICIAL] [Nov-11]
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Chen is already working on it..as per his comment it will dual boot but wifi and network will be off due to some binaries..

So we need to wait till it fixed by Chen
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Anyone want to help me manually patch Liquid Smooth 2.3.7 for VZW ?
[Galaxy S 4 i9505 Original Android Development] mega00:
Finally have access here~

Dear dev, could you please add support for this experimental kitkat rom?

http://xdaforums.com/showthread.php?t=2521384

would like to try it, but don't wanna make it my primary rom as it's not stable, dual booting may be a good choice.

Thank you for your help.

well, saw posts above, just wait for your good news.
[Galaxy S 4 i9505 Original Android Development] gaww:
OP is not able to make a patched secondary out of 4.4 yet - being worked on. So far, his 4.4 (noobdev nightly) can be sued as a primary only
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I will be making a new release once I get my Kit Kat ROM to dual boot :D

EDIT: So I need to:

Fix the horribly broken (on Windows) patch generator

Fix IOKP patching

Fix PAC-Man patching

Fix Liquid Smooth

Fix mounting of apnhlos and mdm in Kit Kat ramdisks

Update Foxhound EDIT: didn't find anything wrong with it

Update Negalite

Add support for Vanir AOSP [LINK]

Add support HTC One port version 1.5 [LINK]

Add support for Dirty Unicorns [LINK]

Anything I missed?

--
[Galaxy S 4 i9505 Original Android Development] brizzol:
Add support so the secondary rom can install it's APK in separate folder than the primary? I need two separate accounts and currently when installing APK on second rom it loads the Primary data...If this is possible it would be great.

Anything I missed?
[Galaxy S 4 i9505 Original Android Development] Phk:
Hi,

Whats the difference between this and Multirom?

thanks
[Galaxy S 4 i9505 Original Android Development] Shanks:
Yes share apps between roms, that would be awesome, or if possible tell us how to do it ourselves so we don't give you many troubles, thanks boss I really enjoy your project
[Galaxy S 4 i9505 Original Android Development] jova33:
The way it was explained to me is multi-ROM uses the same kernel, where this one uses separate kernels.

Also, the multi-ROM kernel thing doesn't work with the VZW S4.

There's some opinions on switching back and forth between kernels being bad for the device, but I haven't noticed any degraded performance in the month I've been using this.

Someone correct me if I'm wrong.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 3.0 Alpha 1 is now released :) This version introduces automatic patching for the updater-script (similar to how the ramdisks are automatically patched). Supported AOSP ROMs should patch without issue now. I'd appreciate it if someone would test the patching of AOSP-based ROMs on both PC and Android.

Note: Kit Kat is *not* supported yet.
[Galaxy S 4 i9505 Original Android Development] gaww:
Duel boot 4.4 will be great.

Is the broken patch generator in windows why I have not been able to get recent patched kernels to work?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The patch generator is the script in the "useful" folder. It's only used when some add support for a ROM and wants to create a patch for me to include in the next release.

What issues are you having with the recent kernels?
[Galaxy S 4 i9505 Original Android Development] jova33:
This is all done by you? Great work. Donated.

Having problems making an info file to contribute. Both in Windows 8 and Ubuntu.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] Bejda:
Latest CM10.2 nightly (13/11) got patched fine with version 3.0 alpha 1 APK.

"Issue with recent kernels" is something like this:

http://xdaforums.com/showpost.php?p=47164828&postcount=864&nocache=1&z=776029780972749

There's a lot of such ramdisk/init.target.rc fails reports on last pages of this thread,pushing older or some custom kernels boot.img into rom's zip before patch was a possible workaround to get rom to boot fine as secondary. Using patcher versions from before automatic ramdisk patching support like 1.18.1 wasn't giving errors also but flashing the patched zip was giving issues (com.android.phone process fc,maybe bootloops or such... better check others reports for a better overall view of the story lol).

But I guess (again better check others reports) for some rom like PAC(?) the issue disappeared at some point and latest PAC builds were finally ok to patch with same previous 2.5.3 patcher version.

So,and as latest nightly went then fine for me under android (couldn't test on windows for now),it was maybe due to some changes on rom's side that were reverted meanwhile dunno..
[Galaxy S 4 i9505 Original Android Development] Shanks:
Difference between this and multirom is that on this you can only install 2 roms and with multirom you can install as many roms as you can fit in your internal storage,I'm on sprint but even if multirom is for the i9505 IT'S BEEN A working flawlessly for me
[Galaxy S 4 i9505 Original Android Development] gaww:
Beginning in mid-October, KT 4.3 kernels that I "patch" will not boot up in your nighties (before you moved to 4.4 of course).
[Galaxy S 4 i9505 Original Android Development] RK:
Worked great for cm nightly. Patched and booted..
[Galaxy S 4 i9505 Original Android Development] Phk:
Has anyone tried omega + cm nightly?
[Galaxy S 4 i9505 Original Android Development] T-REX-XP:
Dear contributor, could you please add support dualboot patcher for device Xiaoping redmi note 3 pro (snapdragon edition) , device code name: kenzo. Logs is here https://drive.google.com/file/d/0B3PSh7kqwgIVZi1maC1OdnByZ3M/view?usp=drivesdk. Thanks
[Galaxy S 4 i9505 Original Android Development] bnwg:
I flashed Purify CM13 to ext sdcard using Phronesis 6.0.1 MM port as primary ROM. It took awhile but definitely not hours.

I use TWRP 2.8.7
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Well using TWRP 3.0.x, but since about 3 hours flashing still

says "Patching system image unconditionally".

Strange, that why does it need about 2760 Mb size system.img file on external sdcard, while the rom file is just around 300 Mb???
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
WTH?? 1-2 days?!? :eek::eek: Does it real finish after that?? Maybe that's something to do with the ROM. Or it could be something to do with your SD card. What class is it? My MM ROM flashes within almost 10 minutes.

It's the size of your device's real system partition. It is set that way otherwise ROMs and mods will have problems while flashing. Chen explained it once.

300 MB is the ROM's zip's size. It'll have system.new.dat or system.img that is usually bigger when extracted. But it should be small for AOSP based ROMs. But since your original system partition is 2760 Mb, that's how big file the Patcher will make will be. Making it small causes issues as Chen said.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
The sdcard is Samsung EVO 64 Gb Class10.

I tried to flash Resurrection Remix v5.7.0.

Sent from Samsung Galaxy S4 i9505 using Tapatalk

---------- Post added at 08:59 AM ---------- Previous post was at 08:50 AM ----------

On my 64 Gb card, I have only 5 Gb free space available, while I have just 5 roms flashed.

Just the rom system.img files are taking almost 15 Gb space :( And the data (including dalvik files) also takes a lot gigabytes.

Sent from Samsung Galaxy S4 i9505 using Tapatalk
[Galaxy S 4 i9505 Original Android Development] bnwg:
It seems just not correct.

Mine is 2.2G
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Mine is also Samsung's Class 10. But it's EVO+ 32 GB claiming to have 25 MB/s write speed. But I don't that's an issue.

That's normal and nothing anybody can do. If each of your ROMs take above 2.6 GB , then 5 ROMs will take more than 13 GB. And yes a ROM's data and caches take up a good amount of your storage. They are stored in the internal storage. Apps use more storage that you might think. You can know how much your apps take in Settings>Storage. (Mine use 8.29 GB) So, when you have apps in different ROMs, then all their data is stored in your internal memory. My internal is usually under 1 GB, and mostly near 500 MB. :fingers-crossed: