yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] rlorange:
It was Siyah kernel for the S3. Remember the image sizes had to be the same when making a dual install and this was done in a custom recovery. I queried as to why the images had to be so large. So i figured out to to shrink them after making them to match the system partition size. I did this by using dd to mount the image and trim the empty end of the img container. Perhaps this somehow cheated by preserving the block count integrity from the original zip while trimming the unused end.

The Dev Def didn't try this. I decided to try and it worked.

I'll dig up the shrinker stuff i did and Siyah S3 dial boot source is on git hub

---------- Post added at 01:02 PM ---------- Previous post was at 12:58 PM ----------

I think to make the blank img container he would do a dd snapshot of the img partition block in recovery then mount it to a folder to install the ROM then copy the partition mounted stuff into the .img container. After this was done shrinking didn't trigger the bug you talk about. I just left 200MB plus beyond the content size in my shrinking commands
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am having a problem backing up dual booted system with TWRP 2.8.4.0 on my Sprint variant. See this. It looks like some problem with a file in dalvik cache in slot-2. I thought I would wipe dalvik cache in dualboot utilities. After doing this, I still see the file that TWRP is failing on is still there. Shouldn't wiping clear all of DC? Anyone have any ideas?

---------- Post added at 03:18 PM ---------- Previous post was at 02:42 PM ----------

[MENTION=4277844]chenxiaolong[/MENTION] are the wipe functions in dualboot utilities wiping the correct directories? When I wipe cache and dalvik cache for slot-2 and reboot, I get a normal reboot for slot-2 and not the optimizing apps that I would expect.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah yeah, if you're using a snapshot, you need this version of the utilities: https://dl.dropboxusercontent.com/u/486665/MultiBootPatcher/DualBootUtilities-4.0-snapshot1.zip

I should probably update the OP...
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am using snapshot. That appears to be the same one I have been using that is in the download link (bullet 1) "Use the preview version of the Dual Boot Utilities and migrate the multiboot ROM data: download link." For slot-1 it deletes /system/multiboot/multi-slot-1 and /system/multiboot/multi-slot-1/cache/dalvik-cache for cache and dalvik cache. Is that correct? Doesn't seem to do anything.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I hate to be a pita, but I know just enough to get myself into trouble. I was trying to do a backup with TWRP. This should backup my primary, dual, slot-1, and slot-2. Unfortunately, it fails backing up data. With these entry's in recovery.log. It fails on E:Error adding file '/data/multiboot/multi-slot-2/data/dalvik-cache/arm/data@app@com.facebook.katana-1@base.apk@classes.dex' to '/usb-otg/TWRP/BACKUPS/081fad3a/2015-04-30--10-19-52-sacs-cm12-gpe-cm12.1//data.ext4.win005'. This looks like it is trying to backup the file in dalvik cache. I figured I could wipe dalvik cache and cache and retry the backup. I wiped cache and dalvik cache slot-2 with dualboot utilities. From TWRP filemanager, I still see the failing file. In dualboot utilities I see deleting /data/multiboot/multi-slot-2/dalvik-cache. Is there a data missing ( ie /data/multiboot/multi-slot-2/data/dalvik-cache? Am I missing something? Sorry for being a pita.
[Galaxy S 4 i9505 Original Android Development] rlorange:
If you delete the dalvik cache fir your multi roms before TWRP backup there should be nothing there to error
[Galaxy S 4 i9505 Original Android Development] todivefor:
That's what I'm trying to do. However, DC doesn't appear to be deleting.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ok go advanced and use the file manager. Navigate to the folder hit select and delete

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

TWRP file manager that is
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're absolutely right. The missing /data/ in the path was a typo.

I've uploaded a new version at https://dl.dropboxusercontent.com/u/486665/MultiBootPatcher/DualBootUtilities-4.0-snapshot2.zip Would you mind giving it a try?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Tested, works great. I had finally gotten the nerve to delete the path I thought was correct and it worked. Tested your fix and it worked. Thank you. I must say you support this better than any developer I have dealt with. Was thinking of going to S6, but for dualboot my S4 has new life. Wish I understood all this better.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Hey [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] rlorange:
Yes Chen you are a true gentleman of a human being. Thank you for be so awesome
[Galaxy S 4 i9505 Original Android Development] gaww:
Ditto - plus you are not bad yourself.

---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------

I had migrated some time back, but without app aharing, my data has grown to 6.6 gb. I do have 2 TW ROMs installed (a TMo 4.4.4) and international 5.0.2), but even after debloating some and moving many apps as possible to SD Cad, I barely have nay free space in 16 gb internal.

I am wondering if there is residual data from the old setup that did not get deleted in the migration by the utility (4.0 from a few months back).
[Galaxy S 4 i9505 Original Android Development] v00d007:
Your latest snapshot still shows wrong information about extsd..In my case there's 1.4gb left on the 32gb card, but it sais 1.4gb used instead.
[Galaxy S 4 i9505 Original Android Development] Suzano-Sho:
Could you detail how you did this? I have a Galaxy Note 4, and every time I install Dynamic Pop (TW based) as my primary and AICP (CM 12) as my secondary, I can boot into the secondary ROM just fine, but when I try to switch back to my primary, I get a bootloop. that doesn't even go past the initial "Samsung Galaxy Note 4" screen...
[Galaxy S 4 i9505 Original Android Development] nds850:
Have you set the primary kernel?

Open the patcher app when you are in the secondary ROM and wipe cache and dalvik cache of the primary. Patch a kernel and flash it to primary. Wipe again and switch ROMs from the patcher app. That's what I did and it worked for me.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Trying to flash latest jfltespr (12.1) nightly (cm-12.1-20150502-NIGHTLY-jfltespr.zip) with 1153. It was recognized by windows patcher and patched successfully (very fast btw). Flashing failed, attached multiboot.log. Patched and flashed with 1112 which I had used before. All worked, but when I tried to switch to it in DB utililities, it said I needed to flash a kernel. Switching from 1153 apk worked and booted. Let me know if you need anything more.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Could you try flashing with TWRP instead? Are you using CWR, right?

Maybe this error could be recovery related:

[E] Failed to mount /dev/block/loop0: Invalid argument

[MultiBoot] Failed to copy /data/.system.img.tmp to /system/multiboot/dual/system

PS: I'm not an expert, but just trying to understand reading the log.
[Galaxy S 4 i9505 Original Android Development] todivefor:
This was flashed with TWRP.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] I'm running 5.1.1 and I tried to flash 5.1.1 to see if it works since I theoretically have enough space. It didn't. Lol no multi boot log. No root either yet.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
S6 Edge Tmobile
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It must be failing really early on then lol. If you don't mind trying again, a TWRP log would be helpful :D

EDIT: You lucky son of... with your 5.1.1... erm.... I mean.... I'm perfectly happy with the 5.0.2 on my Note 4 :p
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I just discovered this app and I was amazed of the idea that I could dual-boot on my Exynos Note 4 but unfortunately it does not work, I have tried using the testing version of the TeamEOS ROM (AOSP/CM-based) for my device as second ROM and also tried flashing that as primary and then Alliance ROM (TW) as the second ROM but none works, as soon as I flash the patched zip file and reboot my phone just loads the Samsung screen twice and then boots into recovery again. Then I tried using WanamLite as the second ROM thinking that it might be cause the ROM's I was using are not supported but I got the exact same result. Can I ask if this has actually been tested on Exynos Note 4 and is there anything I could do to get it working?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
OK. Good thing as I am about to change back to 5.0.2 because of no root but 5.1.1 will be nice to have handy
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
I'm just guessing, but it sounds like those TW roms are too big. Try an AOSP rom in secondary.
[Galaxy S 4 i9505 Original Android Development] GeneticJim:
On my s4 the tw rom was too large. I had to find a debloated near stock tw rom then I had an Cyanogen for my secondary boot. If you have titanium backup it will show you how much space you have left in your system storage.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I don't know if you read the whole post but probably not or you missed it, I did try an AOSP ROM (TeamEOS, the only one we have right now) and same thing happens with either AOSP or TW and I did not try to use 2 TW ROM's at once (that would be impossible without doing a lot of debloat) but instead the TeamEOS one as main and the TW as second, doesn't matter if the TW or the AOSP ROM is second, the same thing still happens.

Just a idea but do I have to be on TWRP to use this (wouldn't make any sense as even if I install the second ROM from the app instead of CWM I still get the same double reboot and then boot recovery)?

EDIT: Forgot to mention I did make sure I have enough space in system before trying to flash the second ROM.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Here you go boss [MENTION=4277844]chenxiaolong[/MENTION] https://mega.co.nz/#!F5UBXThQ!qe_7How5iCDO5T8cF2dS8zaLYdV3mteN7rEJKendxEw
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It looks like this was the issue:

Patching system image unconditionally...
minzip: Error writing 4096 bytes from zip file from 0xffc4911c: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.

I'll have to download the ROM to see where it's extracting stuff.

EDIT: Okay, I know why it's not working. The ROM extracts a system image directly to the system partition /dev/block/platform/15570000.ufs/by-name/SYSTEM. The chroot environment does not allow direct access to the partition, so it creates a new file at that path and extracts to it. Well, that file lives in RAM, so once all 3GB of RAM is used, it just fails. I'll have to update a couple minor things in the patcher to get this supported :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
awesome thanks!! now ill be able to have the best of both worlds.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Implemented in 8.0.0.r1168.g6b04d4b :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The app and data sharing backend code is now completely implemented in 8.0.0.r1168.g6b04d4b. All that's missing is the UI for it now (which I'll get to after my last final tomorrow).

I can't wait until this is done! I can't be the only one who thinks it's cool to see my Chrome tabs show up in every ROM.

Also, I've fixed an issue where booting into the secondary/multi-slot ROMs works until you boot back into the primary ROM, at which point the secondary/multi-slot ROM breaks with a boot loop or frequent force closes. This is something that requires the primary ROM/kernel to be repatched though (or by hitting the update ramdisk button, but a lot of people are experiencing issues with that).
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Hi bro is there any way to add support for the note 3 n900 exynos version please.

And please check my guide which I pm you earlier http://xdaforums.com/showthread.php?t=3091764
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Just finished setting up 5.0.2 now to see how well 5.1.1 dualboots.
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Wait where do we go in the app to update ramdisk lol XD Thanks a lot for your hard work! I have never knew it would be possible to share data too :) Which shows your great potential :good: Maybe you should join Google and implement dualboot in Android officially ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! :D The Update Ramdisk option is in ROM Settings (in the navigation drawer). Make sure you have a backup before trying that because some people have been having issues where the ROM no longer boots after the process.
[Galaxy S 4 i9505 Original Android Development] nds850:
That sounds great! Been using Titanium Backup to backup and restore between ROMs but that's pretty inconvenient. :good:
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I still have been trying to get this to work (even switched to TWRP) and still can't boot the second ROM but looked into the multiboot log created when flashing and it seems to me there are quite a few errors, attaching it here, maybe someone has an idea?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! Don't think I've seen that kind of error before.. How many paid apps do you have installed and (if you're installing from within TouchWiz) how many apps are moved to the SD card? Paid apps and apps on the SD card are stored in encrypted containers which are attacked to /dev/block/loop0, loop1, etc. The log has a few lines with "/dev/block/loop6: No such file or directory".

This shouldn't be too hard to fix I think.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I think I have only 1 paid app installed (have only ever needed to buy 3 apps and 2 of them can't even work on this phone, am not even sure I have the one that works installed because I didn't use it in a long time) but I think there may be a lot of apps moved to the sd card as it seems my phone has the bad habit of installing apps there even if I have space on the internal memory.
[Galaxy S 4 i9505 Original Android Development] pbarakhsan:
note 4 app sharing

Master chen :D

i installed the new app and tried to update the ramdisk for app sharing but after i restarted my phone i went to a boot loop and had to use my back up to restore the system.

do you know if this is just with note 4 or is there any thing i can do to fix it?

thanks and great job master
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I was just about to work on fixing that :D Could you tell me which ROM you're trying to update the ramdisk for and where it's installed (primary, secondary, etc.)? Thanks!
[Galaxy S 4 i9505 Original Android Development] pbarakhsan:
Im using hyperdrive tw rom and currently its the only rom i have installed
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Should be fixed in 8.0.0.r1176.g22848d7. I ran into the same issue with the Stock T-Mobile Note 4 ROM (5.0.2) and it's working for me now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, that would probably be it. I've worked around this by adding more loop devices (from loop0 to loop9) in 8.0.0.r1176.g22848d7. Let me know if it still has trouble installing.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Testing Tmobile S6 Edge. Hopefully we will see something new :D
[Galaxy S 4 i9505 Original Android Development] flexxoo:
I wish you can integrate the note 4 aroma Skipper
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] https://mega.co.nz/#!pgcjXa5A!-Hj0yl5RLy11K27fcxk6nl1CmCk71Jtdg4yt_GSNLXk
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Still same thing, Samsung bootlogo twice and then boots to recovery after flashing second ROM and rebooting, I'm not sure it's related to the loop devices because even on a clean just flashed ROM same thing happens and also even if I have my primary ROM as an AOSP one, it doesn't matter....if I remember right from my old experience with my old HTC Touch Pro 2 the double reboot and then boot to recovery thing happens when there is no kernel flashed on the boot partition so I am thinking perhaps the patched zip doesn't flash the kernel to where it should?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does AROMA actually work on the Note 4 now?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, haven't seen that one before. The issue is caused by it trying to create an ext4 image using the primary ROM's /system/bin/make_ext4fs, which require some functions in the ROM's libc.so library, but the recovery environment will only load its own /sbin/libc.so (which doesn't have that function). That's why it has this error message:

CANNOT LINK EXECUTABLE: cannot locate symbol "is_power_of" referenced by "make_ext4fs"...

I'll make the multiboot installer run specifically /sbin/make_ext4fs instead of any make_ext4fs.

EDIT: 8.0.0.r1177.gf574921
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the info! I've programmed mbtool (responsible for handling the partitions on a multibooted ROM) to reboot to recovery if any step in the boot process fails, so nothing is damaged. I would need to see some more logs to see what is exactly causing the reboot to recovery.

Could you flash the attached zip when it automatically reboots to recovery? It will copy a few logs to the logs/ folder on the internal storage. (It's important to do this when it automatically reboots because the kernel log is lost with a manual boot to recovery).

Thanks!
[Galaxy S 4 i9505 Original Android Development] flexxoo:
No I'm talking about when you patch the ROM to skip the aroma withing multiboot,like that you don't have to use more softwares or process to skip the aroma
[Galaxy S 4 i9505 Original Android Development] sronweb:
[MENTION=4277844]chenxiaolong[/MENTION],

currently I don't have the ramdisk update function on the patcher menu on both primary (TW Echoe ) and multislot1 rom (CM12.1).

I have repatched primary and flashed again but app sharing cannot be enabled currently. Please, do you have any suggestion?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Great zip!
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am using dualboot patcher 1169. I updated ramdisk on slot-2 and rebooted, no problem. I updated ramdisk on primary ( sacs KK 4.4), it bootloops on samsung logo over and over. I am not sure how this works, did not patch with this version, just using apk for updating ramdisk. Is this OK? What can I gather to help trouble shoot? Restoring now.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] https://mega.co.nz/#!xhFU1b6b!N6UBXEy6tohTOzSYpfwx7X-W6o0jejGl6h900bY2b7E
[Galaxy S 4 i9505 Original Android Development] haoyangw:
[MENTION=4277844]chenxiaolong[/MENTION]

I have the same problem as the person above, when I patch Alucard kernel for CM11's ramdisk on my Galaxy S4 it bootloops without even reaching boot animation. It doesn't automatically reboot to recovery though. I am using latest dualboot patcher snapshot 8.0.0.r1177.gf574921 on latest CM11 nightly. If you need any logs can you teach me how to get it? I don't know how to get logs in a bootloop. Thanks!
[Galaxy S 4 i9505 Original Android Development] todivefor:
I know nothing about ramdisk, unfortunately. Restored to my backup prior to updating primary ramdisk. It bootloops also, Samsung logo.
[Galaxy S 4 i9505 Original Android Development] sronweb:
In this case I would reflash the rom. If its the primary it should be re-patched as I understood from Chen previous message. I'm doing some test too.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I patched primary (SACS v4 4.4.2) with r1177 patcher. It patched as custom and was successful. I now gets past the samsung bootloop, but now bootloops in boot animation. My TW rom is so old, I think now that I have my Primary FUBARed, I'll start over. I am including the recovery.log and last_kmsg. I'll test if anyone sheds any light.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the info! This is one I can personally test. Just to be sure, you're using an official CM11 nightly and Kernel-Alucard-V1.4r-[21-10]-[09-12]-AOSPV2-EUR-KK4.4-SGIV-PWR-CORE.zip right?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Flashing any compatible kernel should get your primary ROM booting again. If you get it booting once, make sure to set the kernel in the app, or else switching ROMs will load the bad bootlooping kernel again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Okay, I downloaded https://blck.io/twrp-2.8.6.0v2-zeroltetmo.img (assuming that's the recovery you're using) and it indeed is missing make_ext4fs. Looks like it was something the eousphoros accidentally left out. If you want, you could ask him to add it back in, or else I could edit his build to add that single binary. :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Thanks alot! Either way if you want to add it and ill let him know [MENTION=2346758]eousphoros[/MENTION]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here you go :) I added the make_ext4 program from the official TWRP 2.8.6.2 for the regular S6.

https://noobdev.io/stuff/android/zeroltetmo/twrp-2.8.6.0v2-zeroltetmo_with_make_ext4fs.img

MD5: 6f43449d410d7a9f623a68e5643cb370
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Thanks testing now

---------- Post added at 09:28 PM ---------- Previous post was at 09:13 PM ----------

Flashed it fine but it rebooted into twrp after s6 edge logo. You need recovery log after flashing?
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Here you go, hope you manage to fix it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure that would be great! At least we're making a bit of progress now.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Chen, please what do you think about the fact that I don't have ram disk update option with latest patcher? I have checked from the primary rom. Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Right now, it shows up if the ROM was patched with a version older than 8.0.0.r1118. https://github.com/chenxiaolong/Dua.../multibootpatcher/socket/MbtoolUtils.java#L34

I'll bump that to the latest version so the option will show up.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
https://mega.co.nz/#F!Mxl1nSRZ!ObaBqA0wH4-_mkOjpFQhrw
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is really good. You're running into the exact same issue as [MENTION=2621033]Ranomez[/MENTION] (who also has an Exynos-based device). In both of your phones, it's having trouble reading the "romid=<dual,multi-slot-1,whatever>" parameter from the kernel command line in /proc/cmdline. There's a chance the kernel command line might be too long and parts of it are being cut off. A new build (8.0.0.r1181.gf3d981d) will be up soon that will dump /proc/cmdline to /sdcard/cmdline.txt. I'd appreciate it if you guys could test (yet again) with the new version and send me the cmdline.txt. Thanks!

(To make it easier on yourselves, you could remove everything from the ROM's zip except for the kernel, since it doesn't even boot far enough to start loading the ROM, but it's up to you).

NOTE: The cmdline.txt file might contain the device's serial number (it does on my Note 4) so please PM it to me and don't post the files publicly.