yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Please give the test build here a try and let me know if it works: https://github.com/chenxiaolong/DualBootPatcher/pull/308

I'm not able to download the ROM, so there may be more work that needs to be done to fix the issue:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you attach the /fstab.* file from your current ROM? It looks like /cache is not being mounted, which would cause both problems.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, copy-paste should works just fine and long as the first are on the first partition of the card (assuming you have multiple partitions).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I'm not really sure. My first guess would SecureStorage since the bootloader does not allow access to the secure data if you're using a custom kernel. I saw that you have "ro.securestorage.support=false" in your /default.prop. Can you check to see if every ROM has that set? Maybe the bootloader has some trouble flipping between securestorage and non-securestorage.

Could you also grab a logcat during boot up until a failed unlock attempt?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! Can you give the test build here a try and let me know if it works? https://github.com/chenxiaolong/DualBootPatcher/pull/309
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Looks like you just need to repatch with the latest build. The bug was fixed in 9.0.0.r63.g9def582
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the logs! Unfortunately, with the way the ROM's installer (META-INF/com/google/android/update-binary) is written, there's no easy way for the patcher to handle it. It's checking for the exact paths to the boot, recovery, system, cache, data, hidden, and persist partitions. Many of these are not available when flashing a patched ROM to prevent data loss. The only way to flash this ROM is to manually edit the installer script.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Thanks I will try that and report back.
[Galaxy S 4 i9505 Original Android Development] pehoko:
Patcher stuck long time on verifying patched zip, then gives error that could not read zip file.
[Galaxy S 4 i9505 Original Android Development] Eagle:
[MENTION=4277844]chenxiaolong[/MENTION]

Just so you know the test build backup/restore ROM works fine. Not sure why it supposed to work but there would always be reasons.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that was one of the things I recently fixed. Glad it's working for you!
[Galaxy S 4 i9505 Original Android Development] Eagle:
I am glad it is :D, it is so convenient now. There's no need for me to factory reset , flash a ROM well basically there's no reason of starting from the beginning.

I've a question, it isn't possible let's say I have Number1-primary and Number2-data-slot-1 but I want to change Number2 to primary, how do I go about that? That is unless I've to wipe and flash ROM from recovery to change the partition right?
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
I9505 Dual Boot Show Off

Hi, i made a video to show how dual boot running on TW 4.3 stock as primary ROM and Kitkat 4.4 as secondary ROM,

switch between 2 ROM's in seconds.

[YOUTUBE]Cs1a6uMktS4[/YOUTUBE]

S4 Dual Boot

you can put on the OP if you liked to... :D:D
[Galaxy S 4 i9505 Original Android Development] tylerholbrook:
I put in the script but now seem to have lost root??? So... now I can't restart in my primary rom,, lol dang I really liked this set up only thing missing was the ability to share apps across the roms.. any suggestions??? I'm using chens cm11 as secondary and Wickedv8 as primary..

---------- Post added at 08:56 AM ---------- Previous post was at 08:31 AM ----------

I went to primary using utilities zip. It did work and shared apps, but I think I lost root on secondary rom. Any suggestions? U think it's from putting the script in? Maybe it's sharing superuser from primary and its not set up for 4.4?
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
You can patch the supersu.zip using the latest patcher app, then flash it to root the secondary ROM
[Galaxy S 4 i9505 Original Android Development] tylerholbrook:
I installed it as a system app and now I'm rooted. So I got apps shared, but can't figure out app data to share, if that's even possible
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!

I can't find any TW ROM for international i9505 which is patchable to be used as a secondary ROM.

Does nobody has a solution for this atm? I don't want to delete my primary pack ROM
[Galaxy S 4 i9505 Original Android Development] omnifarious:
FoxHound is compatible. I use it as my secondary on occasion, although it's a slimmed down version with Toggle 2g fix.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Code is committed. It will be released once I update support for the currently broken ROMs :)

https://github.com/chenxiaolong/DualBootPatcher/commit/679b2eb6f572e093284c39577c102b5581275165

https://github.com/chenxiaolong/DualBootSwitcher/commit/7b92e0ddb20e5f4cf95e841c1051053a514ece38

EDIT: The commit also brings with it a pretty resilient (hopefully) dualboot.sh script. The auto-patching process no longer needs to worry about bad updater-scripts that mount partitions multiple times or other stuff like that.

EDIT2: Oops, I just realized all the other ROMs have the "1" icon on them.
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
There is no Foxhound slim version at the new "Diamond" release. I am not sure if a 1.3 GB Rom will have enough space as a secondary rom.

Did you slim your rom by your own by modifiying the CWM file?
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
when i try to pacth cm 10.1 and 11 i have an eroor!!! how can i pacth cyanogenmod ?
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
I don't get this fully yet.. Does this use a shared data partition, so when I update an app on my primary ROM, does it also get updated on my secondary ROM? Or when I get a whatsapp message on my primary ROM, will it also be there on my secondary ROM?

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] Shanks:
No
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
Okay thanks. Do you know a way to keep game/app data synced between the two ROMs?

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
how can i patch the rom ? the progam say unsopported zip. but when i patch kernel it work!! help me please...

i try to re download and change rom but it always say unsupported zip:crying::crying::crying::crying:
[Galaxy S 4 i9505 Original Android Development] gaww:
Search this thread. There are posts on mods to combine data apps.
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
Help me please
[Galaxy S 4 i9505 Original Android Development] gaww:
Be sure you are using the Patcher Android APP (3.0), as the windows patcher has issues. You can download patched CM nightlies from the link below. It had 10.2 through 1110 and 4.4 currently. They work good as secondary.

http://xdaforums.com/showthread.php?t=2383143
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
the last dual boot patcher for android is 2.5.3! when i try to patch the roms don't work but only works with kernel
[Galaxy S 4 i9505 Original Android Development] Bejda:
3.0.0beta1,not on OP for now but a few pages back.
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
Can you give me link for download 3.0.0 beta 1 ?
[Galaxy S 4 i9505 Original Android Development] Bejda:
A few pages back was back to page 97~

http://xdaforums.com/showpost.php?p=47565775&postcount=970
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You can restore backups to any slot. In your case, you can simply boot into any ROM, wipe the primary ROM from the app, and then restore the backup to the primary ROM. There's no need to reboot to recovery for this :)
[Galaxy S 4 i9505 Original Android Development] Eagle:
Oh I've thought about it but the backup wasn't working before (when I was using the old build) so I haven't tried it yet by backing up and restoring through the app using the test build (now)

This is very useful :D thanks again , friend.
[Galaxy S 4 i9505 Original Android Development] Eagle:
Sorry to bother, after restoring it says image checksums do not match. [MENTION=4277844]chenxiaolong[/MENTION]

I've searched the thread and you mentioned it was a bug and will be fixed soon, so that's good news.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I just tried backup. How am I supposed to choose where the backup is saved? And how am I supposed to restore a Rom?I think I didn't see a menu for restore.

Sent from my N910P PH4 on Aurora v4.1 Rom, Ram Kernel v3
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Thanks for this!

I've tested the following with my N9005 hlte successfully,

- backup data-slot-2 and restore it to data-slot-1

- backup primary and restore it to data-slot-2 (interestingly, my primary rom is CM14.1 that is not DBP patchable, but surprisingly, restoring its backup to data-slot is successful and I can boot into it)

I have yet to test backup data-slot-# and restore it to primary but I'm confident it will work :victory:
[Galaxy S 4 i9505 Original Android Development] corsicanu:
That was the problem.. The rom had securestorage on true.. It was so simple [emoji28] . I was thinking that if i make securestorage in the kernel false it will overwrite what's in the build.prop.. Geez thanks! You are awesome! Cheers!
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Using v9.0.0.r159.g03236b9-snapshot, verifying zip takes too long and then failed to flash the zip. I am on oneplus 2 mm. Trying to flash rr 7.1. Log is here.

http://cloud.tapatalk.com/s/583a8fdfa2889/MultiBoot.txt

Tried with stable version too. It flashed fine but phone didn't boot when tried to boot into secondary rom so tried this beta.

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

Compiled by myself
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I tried the latest build and it will not patch the rom zip file (9.0.0.71) it would get an error - 1. so I used 9.0.0.69 which was able to patch the rom but has the same problem were it will boot to recovery. I have uploaded the log for version 9.0.0.69. I have to reboot and get the log again as I cannot copy the log that is first created for some reason. This happened the first time for the other log also. I also uploaded all the logs I could find for multiboot.

this is the ROM I was patching http://xdaforums.com/galaxy-s5/development/rom-superlite-mini-mm-v1-0-361mb-g900w8-t3497158
[Galaxy S 4 i9505 Original Android Development] Eagle:
Flash through a custom recovery for the time being.
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
Here's the fstab.qcom
[Galaxy S 4 i9505 Original Android Development] heisenberg33:
is the patcher working withs f2fs ?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
As you're trying to boot a extsd slot rom I suggest to use the latest test builds where many bugs related to extsd were fixed. r69 was having issues, it would be nice to grab the log for r71 build, I tried lots of roms with the patcher and this is the first time I'm seeing it's refusing to patch a zip.
[Galaxy S 4 i9505 Original Android Development] rifle007:
[MENTION=4277844]chenxiaolong[/MENTION] build r160 verifying too long and when flashing zip file in folder i get error can't read zip file and when i put zip in root directory it can work.

The logs :
[Galaxy S 4 i9505 Original Android Development] pehoko:
Well at least first I need to patch rom.
[Galaxy S 4 i9505 Original Android Development] Eagle:
Patching a zip works fine for me. Using the test build as mentioned from my previous post. Maybe, you can try the latest build from dbp.noobdev.io which has no issues while patching zip except that the backup / restore feature freezes on that build. This is why I am using the test build for the time being.
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

So the problem with /firmware still persists. I have been able to load CM14.1 in a data slot and Tesla, but /firmware fails in each situation. I still have AICP 12.1 as primary, but that requires me to wipe cache and then sideload it before it will successfully install. To get CM 14.1 to work, I patched it, let install with /firmware failure, and then I copy the firmware directory from AICP 12.1 to the CM 14.1 firmware directory. After doing that, CM14.1 can see my SIM card.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
If anyone is flashing rom to extsd slot and it vibrates and reboots to recovery boot to primary and update the ramdisk for the extsd slot rom. Using any build newer than r71 should work 99.9%. Even the r71 should work, but a false "sdcard corrupted" message may appear on some setups. (like mine) :D
[Galaxy S 4 i9505 Original Android Development] pehoko:
I was able to flash patched rom with twrp, well not one that I want but another succeed. How to switch roms without flashing each time boot.img?
[Galaxy S 4 i9505 Original Android Development] Eleo:
I use dual boot utilities from noobdev.io site posted in OP. It is a small zip file that works by flashing it in recovery

Hmm I have flashed two ROMs in extsd slots and both succeeded. But my issue is that when I boot to those ROMs, it takes 8-10GB in sdcard (not external) for each ROM. After booting into first and second ROM there was "system data" in sdcard weighing 20-21GB by decreasing usable sdcard to 5GB from 26GB availabke in sdcard
[Galaxy S 4 i9505 Original Android Development] pehoko:
Well I have missed that program has this option without any other programs.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Of course it's not necessary to have any issues, I was talking to these guys having problems with extsd roms rebooting to recovery or not booting. The space issue you're having is very strange. All my extsd roms are with fixed 2.5GB size of system.img and about twice less in /raw/images/extsd-xx which is the actual size of the system for extsd slots. The free space on internal and external doesn't change if I boot to any other slot. Definitely some problem here.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Problem is not in external sd. In sdcard space (out of 26GB available) I get normally less than 3GB space filled by "system data" for active ROM. But this number gets to 11GB when I boot to second flashed ROM (still sdcard, not external) and 20GB when I boot to third flashed ROM. No system.img or boot.img (boot.img files are 10MB). No change in external sd free space. And since I have only 26GB available space and 20GB is filled with untouchable system data I get no space available to install any app in third ROM. I had to wipe primary and slot 1 of extsd to get usable place. My question is about the space used in sdcard when booting. Does it happen to anybody? I have note3 n9005, and all three ROMs are port marshmallow Touchwiz ROMs (2 note7 ports and one note5 port).

Just in case I backed up all three ROMs in external sd, so that if anytime a fix will be available I can flash them
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Is 9.1 running good?

---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------

When I back up, it freezes. Have to force close patcher
[Galaxy S 4 i9505 Original Android Development] Mike0505:
Thank You for quick replay and build!

It's awesome, working at first try ! :D

Primary rom Miui 8.1.1 from xiaomi.eu second rom - data slot- Resurection remix 5.7.4 from http://xdaforums.com/mi-max/development/rom-resurrection-remix-5-7-1-t3448134 - all good.

In app flashing not working correctly , to long time loading zips and then when flashing get error.

In twrp all good.

Also was trying to install miui weekly from xiaomi.eu 6.11.24 in data slot , patch zip file ok , but in twrp get error and abort.

Thank You ! :)

Logs attached .
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The default save location is in the settings and backups are restored/flashed the same way as any other zips:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, /default.prop is definitely supposed to be loaded first (at least in AOSP). Not sure if TouchWiz changed something, but anyway, glad you got it working!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Any chance you could grab a logcat? Looks like part of the path is being truncated for some reason: "/storage/emulated/0/Oneplus2/Roms and Kernels/ResurrectionRemix-"

EDIT: Found the issue. See my later post.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, looks like the kernel log is missing. Did you flash GetLogs when it autorebooted to recovery?

EDIT: If, for some reason, the log is not accessible, try going to /data/media/0/logs/ with a root file manager.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, yeah /cache is in there. I'm not really sure then. The ROM must be unmounting /cache at some point.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The patcher does not care about the filesystem. As long as every ROM supports f2fs, it should work fine.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
As long as I'm using the latest r160 build yes it is. :)

I previously talked about the backup freeze. Give it time, no matter the app freezes it's actually working in the background. Wait 2-3 mins then kill the process and try to restore - viola, all is there and working.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is fixed in the latest test build (9.0.0.r162.g1398e1c) at https://github.com/chenxiaolong/DualBootPatcher/pull/299
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for testing! Every issue you mentioned should (hopefully) be fixed in the latest helium test build at: https://github.com/chenxiaolong/DualBootPatcher/pull/309
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just wondering, did you ever try flashing from recovery? Could you attach MultiBoot.log after attempting that?

For whatever reason, the MultiBoot.log you attached was truncated so nothing was logged at the point where it tries to mount /firmware.
[Galaxy S 4 i9505 Original Android Development] Eagle:
The test build is working fine as mentioned when backing up and restoring. The freeze issue had been fixed in the test build, for your information.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Strangely phone didn't go to recovery but shut off completely and I had to power it on.

Edit:

Sorry, missed your last post.
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
So how can I solve this for a working Boot UI atleast.

I've been using CM 14.1 as primary.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I was able to grab the log that I could not get before by going to the /data/media/0/logs/, I have attached it. I also tried the latest test builds 9.0.0.r163 and 9.0.0.r168 and they were able to create the patched zip, but when I try to flash it, it just says "cannot read zip" after taking a long time verifying.

I have also flashed the same rom as my primary (without patching) and set ramdisk and kernel, then made a backup via adb and then restored it to the extsd slot, with the same results of booting into recovery.
[Galaxy S 4 i9505 Original Android Development] Mike0505:
This time I only tested miui weekly from xiaomi.eu 6.11.24 in data slot which was failed previous time. :)

In app flashing again to much time to verify zip and on flashing failed. In twrp also flashing failed.

Miui is not ready for cooperation :confused:

Logs attached

Thank You !
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Zip flashed fine but phone shut off while trying to boot into it. Log attached.
[Galaxy S 4 i9505 Original Android Development] gartmann:
I think you should correct the first post. The App-sharing over different ROMs forced me to try Dualboot again after a long time.

No way that this will be ok in next time?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] rifle007:
You need to remove file miui_update in zip ROM , META-INF/com/miui/miui_update then repack the zip again and tried to flash.

[MENTION=4277844]chenxiaolong[/MENTION] i have some problem when flash miui it's stop at this log
[Galaxy S 4 i9505 Original Android Development] pehoko:
I am glad to hear that we can flash MIUI rom. My problem is that I have tried to update my secondary rom from TWRP zip install but not proper rom was updated. Should I must flash my old main rom that was working and if 'yes' then my question is about data and apps that were working will they remain? Now I have two working roms but one wrongly updated and in "semiworking condition" and one secondary not updated ... please explain command "update ramdisk"?

... I have full backup, but not sure that I want to use it in this situation, thanks :)
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION], Here is the MB log after trying to flash CM14.1 in TWRP. /firmware still failed to mount, just as it did in DBP.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Sorry, the App Sharing in the form of using the same apk on different roms was removed a long time ago while the App Sharing in the form of using the same data is scheduled to be completely removed as a feature due to being buggy. Even without the App Sharing ability currently the patcher is better than ever, you can Backup and Restore roms, also running roms from extsd without any issue.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Can you explain a little more of how running rom from extsd works? I tried restoring my primary rom backup to extsd and I got a scare when I saw "make_ext4" appears during restoration process thinking it would format my entire extsdcard! Thankfully (or unfortunately?) the process failed and thankfully my personal data is still intact. The only thing it created was a system image file.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
As your external card is probably formatted with FAT32, and it does not have file permissions, the only way to save a functional rom in it is by creating an ext4 img file containing the rom with its proper permissions. The file is mounted on /system by patched boot.img and any modification is reflected inside system.img
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
As [MENTION=6450691]KaMyKaSii[/MENTION] said the patcher creates a ext4 image named system.img in the /extsd/Multiboot/extsd-slot-xx directory. The system.img contains the /system folder for the rom and the actual files and folders of the system image are located in /raw/images/extsd-slot-xx. Basically you run the whole rom from the extsd saving space on your internal storage. Well some space on internal is still used as every app installed and it's data goes to /raw/data/multiboot/extsd-slot-xx. I can only guess why the restore to extsd slot failed on you. You can provide a log if you're curious about that too. To isolate the problem you can try to patch the same rom zip you now have installed on primary, but this time for extsd slot and try to install it. Make sure you're using the test builds containing new fresh fixes, currently the latest is r168.

Post log if it fails.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Now when booting into one of the extsd-slot roms, I suppose we need to ensure that there's enough space in the internal storage to cater for /raw/images/extsd-slot-xx? It means, let say our extsd-slot rom size is 5 Gb, we need to cater 5 Gb in extsd for the img file and 5 Gb in internal sd for its uncompression when booting into it?