yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
do not send me any error, just does not change ROM, I thought it might be because, have not patched the ramdisk, when I try to say it is not possible.

I attached the log

http://www.mediafire.com/download/otwlcxd4ifwmf07/patch-file.log

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're welcome! Ticking the shared apk box will cause the apk in every ROM you have it checked to become hard links to each other. This saves space because there will only be one copy of the app and as a side effect, if the app is updated in one ROM, it will be updated in the rest.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, sorry! I must not have seen your message earlier. :o
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Thanks

Well it runs fine it appears even with bits missing :confused:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I think you meant to upload ramdisk-update.log, not patch-file.log :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! Was the original boot.img bumped? Right now, the ramdisk update function will bump the new boot.img if the old one was bumped (or at least it tries to). Could you send me the /sdcard/MultiBoot/ramdisk-update.log file?

Regarding the ".nomedia" file, good idea! I'll implement that right now.

EDIT: .nomedia implemented in 8.0.0.r1679.g7f97cdd
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Yes the original is bumped. Just when I try to "Update ramdisk" it give a boot cert error (meaning boot.img is not bumped)

Here is the log.
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
http://www.mediafire.com/download/6c2adz8drjqq272/ramdisk-update.log

it is true, sorry

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] nilesh.remo:
3.5 gb space On internal
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], so it turns out that if we use app sharing on per-app basis, there is only one .apk copy in /raw/data/multiboot/_appsharing , and the respective .apks in other ROMs' folders are just hardlinks to it?

Wow... I also just want to understand the system better!

Also, if we only /raw/data/multiboot/_appsharing/data for apps with shared data, and delete their respective folders in each ROM /data/data dir (to save space), will it work like this? Thanks!

Nevermind. You responded to that, but maybe the real issue was not quite well understood or explained that time... :o

P.S. I really feel like you are the most supportive, kind and attentive developer here on xda... Thanks again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Could you send me the original boot.img in /sdcard/MultiBoot? I'm pretty sure there's something wrong with my bump detection code if the original was indeed bumped.

The log says it detected:

08-30 08:44:55.307 16926 17138 D RomSettingsUtils: Original boot image type: 1

and type 1 is an unpatched boot image: https://github.com/chenxiaolong/Dua...bae9d2c585c987fb550784/libmbp/bootimage.h#L63
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Aha! There we go:

09-01 12:32:33.635 7079 7135 W libmbp : libarchive: Unrecognized archive format
09-01 12:32:33.637 7079 7135 E RomSettingsUtils: libmbp error code: 12
09-01 12:32:33.638 7079 7135 E RomSettingsUtils: Failed to patch file!

That means it couldn't read the boot image because the ramdisk is compressed using an unsupported algorithm (ie. not gzip, lzma, lzo, or lz4). Could you send me the boot.img file for your current ROM?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Your internal storage is in the /data partition (specifically /data/media/0). /system is a separate partition and that's where you ran out of space (you can check using the "free space" section of DualBootPatcher). If you want to install to the internal storage, you need to use a data-slot instead of secondary.
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Here is the boot.img from primary CM 12.1 backed up from app.
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
http://www.mediafire.com/download/90tj65u7r6q6l71/boot.img

thank you very much for your interest, the weekend I send for a pack of beer

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
All of that is correct! You can delete app data dirs in /data/data, but you have to delete it through the corresponding path in /raw (eg. /raw/data/data for primary, /raw/data/multiboot/dual/data/data for secondary, etc.). This is because the shared paths (/raw/data/multiboot/_appsharing/data) are mounted to /data/data, hiding the original directory. If you deleted directly from /data/data, the shared directory would also be deleted. I plan on adding some sort of a button to the App Sharing settings to handle this.

Thank you! I wouldn't give myself that much credit :D The community here in this thread is what makes this project so great. When I'm busy with school or work, everyone is so happy to help each other out. The fact that everyone is as nice, supportive, and helpful today as since the first day two years ago is what makes me love working on this project so much!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you! Found the bug. Might take me until tomorrow to fix because I will need to make some changes to my boot image parser code.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It looks like MediaTek adds some weird headers to their boot image files. It might take me a few days to figure out the differences they made. I'll let you know once I fix DualBootPatcher to handle these files.
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
It is a small token of gratitude.

56552687PA8603535

thanks for everything

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmmm.... that's very strange. What happened was: mbtool created a copy of /system (excluding /system/multiboot) into a temporary image. The zip file is flashed into that temporary image. But, for whatever reason, the temporary image could not be mounted. Then, when the flashing completed, it was supposed to wipe /system and copy the temporary image back to /system. Of course, since the mount failed, it copied back an empty folder.

I'm not sure what would cause this to happen. Nothing has changed in the installer code since Aug 25th, which was before you originally reported issues. Does this happen every time you try to flash that zip?
[Galaxy S 4 i9505 Original Android Development] Ranomez:
It acrually happens with any TW ROM/Kernel zip (tested 3 kernels and 6 ROM's) and I did report for the first time on Aug 25th because I have been using the AOSP ROM for about a month without switching back to a TW ROM even once, the problem might have been introduced earlier.

EDIT: I think I've been using AOSP since 18.07 as that is the first nightly I still have on my SD Card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=2449563]Chevelle1768[/MENTION], The boot image parser has been fixed in 8.0.0.r1682.g2980fe6. It should properly detect bumped boot images now.

https://github.com/chenxiaolong/DualBootPatcher/commit/c7eee98cf67bf297c0765e2a94fdb003fb534410
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi,

Thanks for the explanations chenxiaolong!

regarding the poll here:

http://xdaforums.com/showpost.php?p=62446051&postcount=6700

I wonder.... Method 1 makes a 4GB image file in /data? I wonder how this is possible as my phone only has 4GB internal mermory but still flashing to extsd works fine. I wonder what i need to choose now. :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION],

It would be nice to implement the following:

- A GUI to command mount -t ext4 -o loop /raw/extsd/multiboot/mysdslot/system.img <-- nevermind the exact syntax

This way we could manually change some system apks, etc when system.ing mounted on primary ROM. Directly updating nightlies, gapps, other things could be so much easier this way, IMHO.
[Galaxy S 4 i9505 Original Android Development] nilesh.remo:
i try to install multi slot 1 but failed also
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
i have a problem with my note 3 sm-n9005...i have note 4 rom (darklord v2.2) with audax kernel as primary rom..i tried to patch a lot of rom (aosp based and miui (touchwiz based)) and if i select HLTE devices i can't install secondary rom because the different devices (my phone is seen as TRLTE)...and if i select TRLTE device, i install my rom with success but my phone stuck on bootloop...how to fix this??
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
I wish soon will have data on external SD!!
[Galaxy S 4 i9505 Original Android Development] Andycar:
Maybe try to check and edit your primary TW ROM's build.prop to correspond to your REAl ro.build.product values... I think, that for your Note 3 it is hlte, but I'm not sure.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Tried flashing again meliusltecan with the 1682 build, started fresh and wiped everything and it works with oem 442 and a older cm build 444. Ram disk updated, flashed fine and switches between roms fine.

So far so good

Thank you for all your hard work.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
I have a question regarding app-sharing.

Do the already existing data get copied over when i activate app-sharing or do i have to copy the data myself?

Just asking because i tried app-sharing for the first time. I tried with whatsapp, activated apk and data-sharing and rebooted. After the reboot i opened whatsapp and it was like it was newly installed, no chats and asking for my phone number for inital setup.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That issue should be fixed in 8.0.0.r1685.gaa6724f now :)

Thank you very much for the support! :highfive:
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Hlte and miui in data-slot-miui doesn't boot..

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I actually switched to method 3 because it had the most votes :) I've optimized it a tiny bit so it creates an image the size of the /system partition instead of a massive 4GB file.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The ROM actually flashed successfully. It's the kernel that had an issue this time:

dd: writing '/dev/block/platform/msm_sdcc.1/by-name/boot': No space left on device

That means after mbtool (multiboot helper tool) has been added to the kernel, it no longer fits on the boot partition. Unfortunately, there's not much I can do about this because I've already made mbtool as small I can (~492 KB).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You can workaround the trlte issue by adding the following to your build.prop:

ro.patcher.device=hlte

This value is only recognized by the patcher and does not affect anything else. By the way, does the flashing work from recovery? (when patched for hlte of course) I assume it failed with in-app flashing.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I plan adding a option for copying/moving the data, but I haven't found the time for that yet (it requires quite a few changes to the app). Right now, the easiest option is probably to backup the data with TiBu, enable shared data, reboot, and restore with TiBu.

EDIT: You probably figured this out already, but disabling shared data will use the original data from the ROM again. The original data is always preserved (unless the app is uninstalled).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What do you mean by doesn't boot?

Hang at Samsung logo

Reboot at Samsung logo

Reboot into recovery at Samsung logo

Hang at ROM's boot animation

Reboot at ROM's boot animation

Reboot into recovery at Samsung logo

When it runs into the issue, could you reboot into recovery (without shutting down completely) and flash this zip? https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150827.zip It will dump a bunch of logs into a tar archive in /sdcard/logs/ which should contain more information about why it failed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I don't think I'll add something to the GUI because I don't want to duplicate mounting code in the app (because everything is handled "in-house" and doesn't rely on any commands, like "mount"). Would it be good enough if I modified mbtool so all extsd-slot images are mounted to /raw/images/[ROM ID] on boot?

EDIT: Just a little thought: automounting would allow the ROM versions and build strings to be shown in the ROMs list instead of just "Unknown"
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Very weird how it only affects TouchWiz ROMs and kernels (especially weird that it happens during installation). Could you give me links so some of these problematic files? I'll try flashing them and doing some debugging. Thanks!
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
It would indeed be nice to have an easy way to open these img files. Was looking for an easy way on pc but its not so easy after all. :)
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Here:

ROM's:

http://xdaforums.com/note-4/development/glamour-s6-rom-t3136786

http://xdaforums.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266

http://xdaforums.com/note-4/development/rom-simplrom-v2-t3034419

http://xdaforums.com/note-4/development/rom-sweet-rom-v2-nj4-4-4-4-t2923953

http://xdaforums.com/note-4/development/n901c-dr-ketan-custom-rom-t2944354

Note: For the ROM's that already got a 5.1.1 version use the 5.0.1 one not the 5.1.1 one.

Kernels:

http://xdaforums.com/note-4/development/kernel-googymax-n4-coming-t3126636

http://xdaforums.com/note-4/development/kernel-perseus-halaszkuniversal5433-t3084220

Note: The 3rd kernel is banned from XDA because the developer didn't share the sources, it is on 4pda (Ultimate Kernel)

Also the fact that now the problem is at install time is new, it was installing fine but wouldn't boot.
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
thanks for the replay...i tried to change the build.prop but the problem is the same..now i'm on miui7 so i can't try to addind the line on build.prop...but when i go back to note 4 port rom i will try....ps: with miui7 NO problem with dualboot patcher ;)
[Galaxy S 4 i9505 Original Android Development] blagginspaziyonokip:
Any method of completely removing any trace of this from my LG G3? I tried updating CM12.1 and just kept getting a black screen and I've decided to just use my main ROM.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Yes, this sounds like a perfect solution for me...

Also, displaying version of on-sdcard ROMs as an "added value" is like "killing both hares with a single shot" (an old ? [emoji1] Russian proverb)
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

What happened to the LP5.11 compatibility? With patcher v16xx up to v1685 neither cm12.1-0904 nor cm12.1 optimized-0817 flashing works. Cache mounting fails. ??
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you send me /sdcard/MultiBoot.log?
[Galaxy S 4 i9505 Original Android Development] v00d007:
Here it is, hope its not too chaotic... I forgot to tell, I tried to install the cm12.1 roms as secondary with 1st rom is echoe rom v49.
[Galaxy S 4 i9505 Original Android Development] -MaD-:
This is the last post I found on sms sharing. I don't understand exactly how to do this. Do I need a second partition on the SD card? And should I install a 3rd party sms app?

Sorry for these noobish questions, I just want to share sms data.

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] I just installed the latest patcher and it managed to update the ramdisk on my TW ROM and I can now dual boot with AOSP, will try patching a TW ZIP file (kernel) and flashing it to see what happens.

EDIT: Once again ended up with an empty system partition and an error about can't execute zip update binary, tested 2 kernels this time, don't have time to try a full ROM zip.

EDIT2: It seems I can't actually switch ROM's to a TW ROM using the app or Utilities zip, doing that once again gets me stuck at the Note 4 logo for a while and then boots to recovery but if I flash the kernel img files using TWRP everything works great.
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
first of all, again, thank you. the application works but there are some details that I will try to explain.

I do not think with all kernel functions, which is send you a ROW version and some that have been tested with the PCR VibeUi it does not work and I think that is the kernel.

if it works for me but gave me the updater-script has some reference to a file that does not exist, the installation aborts, even that same ROM is installed very smoothly without patching the .zip

I hope I've explained myself well, the problem is that use google translator

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Implemented in 8.0.0.r1688.gd9ec2fe :D You'll need to update the ramdisk for the changes to take effect.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
https://drive.google.com/file/d/0B2ftBoBlBHTIZ3lnaWk0emtZT0E/view?usp=docslist_api

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] really, REALLY strange thing: I patched and installed a 5.1.1 TW ROM to the ext sd and as always it rebooted in recovery at the Note 4 logo and then I flashed the boot image for the primary ROM (TW, S6 Edge port, 5.0.2), booted and patched the kernel zip for a 5.1.1 TW kernel and flashed it. After reboot surprisingly it did boot in 5.1.1 TW (and I don't even have the right bootloader for 5.1.1) and now I can switch ROM's normally with the patcher (even to TW ROM's) but don't yet know if I can successfully flash a TW zip or use the utilities zip to switch (and can't test ATM) so at least a part of the problem solved itself for me but I saw a few people having similar problems with the patcher in the N4 Exynos forums.
[Galaxy S 4 i9505 Original Android Development] Andycar:
This is so great! It works! Thank you![emoji1]
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Does it mean that now we can have data in external sd??

Thanks in advance!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Would you mind trying again with 8.0.0.r1689.g731ec0e and posting the log? Apparently, I got a little sloppy with the logging before and it didn't say what caused the failure, just that some failure happened when chmod'ing /cache.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, either the device was completely shut down or the MIUI kernel doesn't support saving previous boot's kernel logs (/proc/last_kmsg). Either way, there isn't much debugging I can do without being able to see that log unfortunately.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you post a link to the kernel that fails to install? I'll take a look and see if I can find out why it says that the file doesn't exist. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The mbtool code for flashing ROMs and booting ROMs supports putting data on the external SD already, but it's currently unused for two reasons:

How big should the data image on the SD card be? If we use a fixed size, like 10GB, that may be enough for some people, but not others. We can't ask the user before flashing with something like AROMA because that doesn't work on every device. But lets say that we create 10GB data images for extsd-slots. You would lose 10GB of space on the external SD because that's how big the image file is, even if you're only using a small fraction of it.

App sharing currently can only handle ROM data being in the /data partition.

So, the code is all there, but I can't think of a good way to make this work in a simple and user friendly way.
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
thanks for the reply but what about if you can add those options in the windows app and like that the people that cannot use aroma can use it in the pc and patch the rom in windows.

is that possible??
[Galaxy S 4 i9505 Original Android Development] blagginspaziyonokip:
How do i remove this from my device??? Someone answer
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think I was able to reproduce the issue where /system is wiped. I'll let you know how that goes. We can work on fixing the other bugs once that's fixed so you don't have to constantly reinstall your ROM ;)

EDIT: 8.0.0.r1695.g49d5a41 should (hopefully) no longer wipe /system.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You can wipe all the ROMs from the app and then uninstall the app. If you want to do it manually, switch to your primary ROM and delete the following directories:

/sdcard/MultiBoot

/system/multiboot

/cache/multiboot

/data/multiboot

[External SD]/multiboot
[Galaxy S 4 i9505 Original Android Development] v00d007:
Look at the screenshot, that maybe shows what happened.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You ran into the same issue as [MENTION=4728213]nilesh.remo[/MENTION] (http://xdaforums.com/showpost.php?p=62653930&postcount=6929), same ROM version actually. Unfortunately, the kernel for that ROM is simply too big. Once mbtool gets added to the kernel (an additional ~532 KB), the kernel no longer fits on the boot partition. The author of the ROM will need to make his/her kernel a little bit smaller.
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
http://www.mediafire.com/download/gb80gv2dcl1ousc/boot.img

Thx bro

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] XDA_h3n:
I'm not sure if this has been asked before as I cannot seem to find it.

How would you switch roms when you cannot boot one stored in the external sd card (e.g. to primary).

Miui just seems to bootloop to recovery on my S5 ; a s6 ported rom did work. Most likely I had a corrupt download

EDIT* I have just wiped all the partitions and installed a rom again and its booting from primary.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
So you couldn't do anything..

I'll continue to try with the new versions of your app and i'll let you know if something is going to change

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] v00d007:
But it's all the same with the official cm12.1 nightly. Never had such a problem before. What's the workaround? I can't go and tell the cm team to modify their kernel, they usually don't react to any suggestions...
[Galaxy S 4 i9505 Original Android Development] todivefor:
In the future flash DualBoot utilities from recovery, select primary, and switch rom.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Here last log with 1697 version and miui kernel

https://drive.google.com/folder/d/0B2ftBoBlBHTIWnpiS3ZOUGQ3eVk/edit
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Hi,

just wanted to report an issue with multibooting Aurora Rom Note 4 S6 on my Galaxy Note 3 N9005. I can successfully boot it initially but after I choose the app sharing option in the patcher it hangs indefinitely on Samsung logo screen. I can only manually reboot to recovery and flash another kernel to boot into another slot. The issue has happened so far only with that Rom. Thank you very much.