yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
mbtool doesn't give two craps about Android's settings. Just kidding :D As long as the internal partitions still exist and are formatted correctly, they will be used by multiboot. It will not read the Android settings database to find out where the storage really is.
[Galaxy S 4 i9505 Original Android Development] GioBasi:
too many problem with extsd. and patching cm 11 . error 13. and can't getlog with your Getlog.zip

I'll try older versions like 193x was ok, not sure.

And I'll try getlog somehow.

anyway thank your for your work ;)
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Hi :)

i tried attached zip again and it didn't work.

[MENTION=7111568]say99[/MENTION] told me that he can enable last_kmsg in stock kernel
[Galaxy S 4 i9505 Original Android Development] andybelloasis:
clear
[Galaxy S 4 i9505 Original Android Development] htb2050:
[MENTION=4277844]chenxiaolong[/MENTION] can you please add nexus 7 2013 DEB version too. The WiFi only version FLO is already supported.
[Galaxy S 4 i9505 Original Android Development] bhushan2k:
lot of confusion.. can someone plz answer these noob questions..

1. what does update ramdisk do?

2. what does set kernel do?

3. how to flash abc and xyz custom kernels for primary and secondary rom respectively??

4. can i flash xyz kernel for secondary rom from currently booted primary rom? and vice versa?

5. patched zip file when we select to flash, it searches slot where /system partition does present.. but kernel has to be flashed on /boot partition... so when i select patched xyz kernel zip to flash, how does boot.img file from xyz patched kernel zip file go in internelstorage/multiboot/data-slot-secondary/ ??
[Galaxy S 4 i9505 Original Android Development] karkasss:
[MENTION=4277844]chenxiaolong[/MENTION]

With 2102, in case of specific rom, patching & flashing was succeeded but not booted.(rebooted to recovery automatically)

But with old version(Test version is 2015), booting OK.

It seems patching problem since new version.

Please check below log!

Log:

https://mega.nz/#!59E3gBzB!YygyOkyJU1W8xhnnX8FZU6XNmbDGKE9tWHqd8JclRJM
[Galaxy S 4 i9505 Original Android Development] Eliminater:
some progress or news boss?
[Galaxy S 4 i9505 Original Android Development] ksigit:
Anxiously waiting for oneplus x support...:)
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
You have to patch the gapps zip file for secondary and then go to rom menu and click on the icon to flash a zip/rom and pick the update zip file and press the check mark at the top. And watch it install. I think you have to be on a different rom when doing this, so boot into primary and do these steps.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Just use patcher app (or windows) and select secondary. Flash patched zip in app or recovery.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Updated to 2102 patcher my s4 and note 3 Canadian phones both on oem tw 442

Both booted to recovery after updating mbtool

S5 Canadian updated fine and I can report that my 64 g exfat sdcard is mounting properly half the time when I boot to the dual rom.the other half the time it mounts read only to raw on the aosp rom)

Log from note 3 attached
[Galaxy S 4 i9505 Original Android Development] gaww:
Same as you did the ROM - patche it as secondary and flash it.
[Galaxy S 4 i9505 Original Android Development] Richardvinyard:
I want my secondary rom to be my primary so... What happens if i delete my primary to make a clean install? Any risks?
[Galaxy S 4 i9505 Original Android Development] todivefor:
If you only have 2 roms, primary and secondary, wjping and flashing your secondary rom without patching will get you to secondary rom in primary position. Better way. Backup your secondary rom as outlined here. Restore backup to primary and then delete secondary.
[Galaxy S 4 i9505 Original Android Development] Richardvinyard:
Yes but my secondary rom was in the cache partition so it won't become automatically primary. Anyway i wiped primary and made a clean install, shared the apps from the secondary rom installed cache and everything is working good...so good for me! :D
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, can you check if the rom with problem after patching don't boot have aroma in ?:confused:

Because almost all rom with aroma don't boot (in my case) !:p

THX
[Galaxy S 4 i9505 Original Android Development] nutpants:
Is anyone else having failed boots after updating mbtool with the latest 2102 update?

I've got force closes when trying to patch a Rom with my Canadian note 3 (snapdragon) now also.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
There is a new version out... 8.0.0.r2115.g279e1b2 check https://snapshots.noobdev.io/
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I gave this a try on the latest version (8.0.0.r2115.g279e1b2) and it had no trouble booting on my Galaxy S4 (flashed via TWRP to data-slot-miui). When the ROM boots, however, no boot animation appears, but that may be because I have the T-Mobile S4 variant (SGH-M919). I could only tell that it was booting by looking at the logcat on my computer.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2115.g279e1b2 fixes a bug introduced in 8.0.0.r2058.g141474d where some TouchWiz ROMs and other ROMs with restrictive SELinux policies are unable to boot (automatically reboots back into recovery).

Technical details @ https://github.com/chenxiaolong/DualBootPatcher/issues/39
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
I should give a try, Right ? [emoji12]

Thanks

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try again with 8.0.0.r2115.g279e1b2? It fixes some booting issues in ROMs with restrictive SELinux policies. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I ran into the same issue on my old T-Mobile S4 with TW 4.4.4. This should be fixed in the latest version. Please see my posts above.

The fuse-exfat driver I use will mount the card read-only if it detects any sign of corruption (eg. unclean shutdown, which may occur if you frequently use the reboot option from the DualBootPatcher app). I don't believe there is any way I can override this.
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Hi

I tried latest version and it didn't work also ?

But this time uevent dump works fine ?

Logs + uevent log

https://drive.google.com/file/d/0B0ODjuZvMeEveV9pemNxTldHbms/view?usp=docslist_api

BTW I only updated ramdisk and after reboot it stuck at Asus logo then automatically rebooted to recovery without any vibration

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] kingknuts:
android 6.0 error 14

Hi buddy! I have another problem with my lg g3 d855.

I want to try the new android 6 stock MarshMallow and I am unable to patch the zip. The patcher says error 14.

What does this mean??
[Galaxy S 4 i9505 Original Android Development] karkasss:
Now it is working. Perfect!! Thank you so much
[Galaxy S 4 i9505 Original Android Development] bnwg:
I've been using this for awhile and it's working great! Amazing implementation!

But I do come across the data loss when using sharing apps feature at first time.

For example:

Select whatsapp from sharing app in primary rom first time. After reboot data from whatsapp is gone. Need to restore from backup. After that it is fine. Not sure if I did something wrong.

And if multi selection can implemented for sharing app it would be great.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Did you reboot to a different ROM after selecting share data?? If so, that is the reason. You can always get it back by disabling share data, though.. Here are the steps for proper app data sharing:

1. Boot to the ROM which has the app and data you wanna share.

2. Select "Share data" and reboot in the SAME ROM (very important).. If you reboot to a different ROM, data will empty and the app will have no data and it will act as new app. Restoring backup does the trick, though.

3. Boot into the ROM you want the shared data and do the same steps. Then reboot to same ROM again.

4. Repeat the steps in the ROMs you want.

5. Voila!! You now have the data of that app shared across all ROMS!

[MENTION=4277844]chenxiaolong[/MENTION] Is there any way to completely remove an app's shared data?? Will just deleting its folder in /data/multiboot be enough? I no longer want to share the data of some apps and now there are simply using up space.

Also, a feature request, can a feature be made to copy the shared data to the data of the app in the current ROM??

Thanks.
[Galaxy S 4 i9505 Original Android Development] bnwg:
This is the procedure I did. The pop up message "The changes will take effective after the next reboot" makes it very clear too.

Rebooted in the same ROM after selected the share data for the apps. Right after boot up the data for the app is gone, or reset to its first installation stage.

I've tried several times and they came up the same result.
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Chen may confirm but what I see is that "sharing" only points the ROMs app data to the shared folder /raw/data/multiboot/_appsharing/data/app and it does not copy your "non shared" data so you have to set up your app from scratch on the first ROM. Once you have that setup other ROMs will be able to use that data. (After the respective reboots)

If you "unshare" the app you will see the original data

Once you longer want to share that data for any ROM you have to go and manually delete the shared app folder.

By the way also noticed that data sharing does not work for all apps and usually not at all for different android versions.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
After "sharing data" and having rebooted ...you MUST restore that apps data back using your previously made backup, say for whatsapp as example!

Use TBu , 3Ctoolbox pro or what ever you prefer,

....

Bottom line: RESTORE BACKUP OF THE APP UPON REBOOT after ENABLING DATA SHARING, and then reboot to your other roms and install the same apk and activate sharing, reboot at your preferred time from here, or immediately if you want to!

.....
[Galaxy S 4 i9505 Original Android Development] nutpants:
I was having crashes every time I tried to patch a new Rom on the newer versions

It would crash as soon as add I hit the plus button

Then I tried it on my s3

And noticed it never gave the option to use my file manager of choice

It went strait to the documents ui built in file manager

Which I have removed from almost every Rom I use as some times it will not even recognize my external sd.

So it crashes.

Is using the built in documents ui now required for some reason?

I'm booting fine with the mbtool on the newest patcher now.

So I should be using the standard shutdown and reboot over reboot in the patcher and I might get better results in mounting the exfat card?

I can give that a go

Thanks fit all the hard work.
[Galaxy S 4 i9505 Original Android Development] monkteo:
HI, any idea whay can't boot an MIUI AOSP on S5 , data-slot (last patch v2115) ?

patch OK, flash OK (from app or recovery but not but remain at first screen Samsung.

THX
[Galaxy S 4 i9505 Original Android Development] bnwg:
So it means after the app is selected for "sharing data" for the first time and rebooted the app data will be reset and lost?

Just want to know if it is normal.

Thanks.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Yes it's normal , but data it's not lost, it's just in diff path(read the scenario by Chen on the OP about this, you'll understand The concept better).....when you activate app sharing, the app uses a new directory path(that'll be accessible by other apps from other ROMS) to store data!

Ex: whatsapp data path before sharing activated>>>> /storage/emulated/0/WhatsApp

And whatsapp after enabling sharing>>> /raw/data/multiboot/_appsharing/data/Whatsapp

This means after sharing an app , it's using new path, as if installed for first time ever" on the device and thus a need to restore the data of the app!!

Make backups of the app you're interested in sharing then restore it after rebooting!!

NB: your old app data(original path ) after sharing the app does not get deleted but outdated!!
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Ha ha I also found that it shutted down way too quick to be honest ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Important: Starting from 8.0.0.r2118.g9801105, for in-app flashing, mbtool will no longer use the system properties in the installation environment. This means the contents of /system/build.prop, etc. will be ignored. It will instead load the properties from the recovery image.

This means for in-app flashing, it is no longer necessary to hack around "ro.product.device" if you're flashing weird ROMs--as long as you know that it works if flashed from recovery :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
AhOra sí!

Muy bien amigo....

Just one comment: the patcher since after 2058, on my x86arch while attempting patch files it FC, even with 2118, so I patch files from my arm arch environment and all of them boot to recovery again if they're secondary but work okay when patched with earlier versions before 2058...I'll provide logs later!!
[Galaxy S 4 i9505 Original Android Development] peppet:
Hi i use this fantastic app but i've problem to flash patched 6.0 gapps in secondary rom. Is it my problem? Thanks

Inviato dal mio SM-N920C utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What the data sharing does is redirect where Android loads the data from. Normally, Android loads the app data from /data/data/[app]. When data sharing is enabled, the data is loaded from /data/multiboot/_appsharing/data/[app] (which is accessible to every ROM). That's why you appeared to have lost your old data. Actually, if you uncheck data sharing, Android will use your old data again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that'll do the trick :) There are no leftover files anywhere else.

Created issue here: https://github.com/chenxiaolong/DualBootPatcher/issues/48 That will take quite a bit of work as the app currently does not communicate with the app sharing code at all. As you know, right now, all of the app sharing settings are saved to config.json in /sdcard/MultiBoot and is loaded at boot. There is no way to make changes while the system is booted yet and I hope to fix this in the future.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, DocumentsUI is required starting from 8.0.0.r2058.g141474d because it is the only way to access files on the external SD without requiring root (or system modifications in the case of custom ROMs). It's one step towards one of the long-term goals of the project to drop the requirement for root. Many people, like myself, cannot access work email or VPN on rooted devices, so having an unrooted secondary ROM would be beneficial.

Yes, that would be better. The app tries its best to unmount all partitions before rebooting, but it may still cause issues since it is not able to call the Android framework's shutdown procedure.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Haha, yep, there's no way for me to call the Android framework code to close all apps and the framework itself, so it just unmounts all partitions and reboots :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The uevent dump log is extremely helpful. I know exactly why it's failing now: Android normally creates paths, like "/dev/block/

SOMETHING

/by-name/system", for the partitions. Your device is missing the "

SOMETHING

" portion in that path. I might need to add some ugly workarounds to make this work.

I may need you to try a new uevent dump zip later :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, the boot.img might not be getting flashed. Could you post a link to the zip you're flashing?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Where is it failing? Could you post your /sdcard/MultiBoot.log file after the failure? Thanks!
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Im really sorry my device requires many changes, Intel & Asus always done things in different way

I'm always ready to test [emoji14]

Thanks [emoji16]

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thanks :) You are very helpful. But you should ignore these feature requests until you fix the bugs/issues. I just asked because it'll be reduce two steps of backing up and restoring with TitaniumBackup, etc so it is not at all important.

The issue I have submitted seem to hard right? Should I try using any of the latest versions? Have you inserted those patches in the debug version you gave me to the snapshot versions? Will that be of any help?

One more feature request ;). As I can ignore these till you wish. But, this is a bit more useful feature. I've always wanted to ask you this.

I and another member have been talking about this a while ago on this thread.

As you can see, at present, only system is placed in SD card when a ROM is installed on an extsd-slot. The UI prints show data and cache are not image files but system is. So, is there any way to make data or cache into image files on the SD card at present? If no, can this feature be added?

Thanks again for all your hard work. :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, this one MIUI AOSP

http://xdaforums.com/galaxy-s5/development/rom-miui7-aosp-5-12-4-beta-t3270677

THX
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Maybe ASUS and Intel aren't doing anything wrong. I think I may have found a bug causing the issue that occurred because of a hack I added for an LG device. :D Will create a uevent dump zip later.
[Galaxy S 4 i9505 Original Android Development] apna.suresh0305:
Awesome work!

Is it possible to add support for the CM13 ROM ?

Here is the link:

http://xdaforums.com/mi-4i/development/unofficial-cyanogenmod-13-t3247399
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=4648515]AL_IRAQI[/MENTION]: New uevent dumper to try :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem :D I agree, bug fixes first.

I have not made any changes regarding mtk devices yet :( I won't add the patches from the old debug version because it gives the ROM installer full access to the device (so it could wipe your other ROMs by accident). However, if you would like me to compile a new debug version, let me know.

You might be on to something with https://github.com/chenxiaolong/DualBootPatcher/issues/42 when you said that the partitions aren't being flashed. Maybe that's why everyone is using the crappy closed-source update-binary instead of the open-source one. It must be doing something special to make the partitions writable.

EDIT: Do you have a link to your primary ROM? If you're willing to, I'd like to try this: I want to modify the unpatched primary ROM zip file and have it run everything through the strace program. This will log all the calls to the kernel (eg. opening a file, reading a file, etc.). Hopefully, this way, we can find out exactly what the update-binary is doing.

Technically, it is possible, but there are a couple reasons why I haven't implemented this yet. 1) I no longer have a device with an SD card slot. (Well, my Tab S2 does, but I can't check my work email anymore if I trip KNOX) 2) I actually tried implementing this way back in December 2014 (around 8.0.0.r378.gfef269b). I had just gotten my Note 4 and also a $180 USD SD card (really dumb idea lol) because putting the entire ROM and data on the SD card was something I planned to do for a while. Well, long story short, Android managed to kill the card within a week. Just from general use, the OS makes bunch of random writes to the SD card and ext4 with journaling enabled just kills the card faster. Sure, workarounds can be made, like disabling ext4 journaling, but then you're basically guaranteed data loss with an unclean shutdown. On top of that, the OS is really, really slow when everything is on the SD card... and that's putting it nicely. (40+ minutes to flash a ROM with a 15GB data image)

That's why even though it's possible, I don't really have the motivation to implement the feature and maintain the code. My thinking is that if the experience is so crappy on a flagship device with a high quality SD card, it could only be worse for other devices :)

(However, if a lot of people really want this feature, I may let people manually add an option to the config file at /sdcard/MultiBoot/extsd-slot-blah/config.json to enable a data image on the external SD. But please don't ask me to do this lol...)
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Here you are [emoji16]

https://drive.google.com/file/d/0B0ODjuZvMeEvUWZmRm5kNFFpZFE/view?usp=docslist_api

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thanks for your interest. :o

Here's the link to my primary ROM (Vibe UI 2.8: https://cloud.mail.ru/public/Cvj7/3U5rjvc6s/ST/VIBEUI_V2.8_1544_5.192.1_ST_K50-T5_WC66.zip

Here's a newer dev version of it: https://cloud.mail.ru/public/Cvj7/3U5rjvc6s/DEV/VIBEUI_V3.0_1603_7.416.1_DEV_K50-T5_WCB43A66EA.zip

I only use stable versions.

Thanks.

$180 SD?? Lol :D

Oh, that's dangerous. I've heard these kinda hacks reduce SD card's life. So, having system alone as image file will no side effects, right? Is it because there's no change in system apps? Just curious.

Yeah, you should be right.. If Note 4 with its SD805 can't handle it, what can?? :)

P.S.: Don't tell me you were awake till 3 AM :D
[Galaxy S 4 i9505 Original Android Development] peppet:
Argghhh i was using an old version of your great app. At this moment, with last release i can install 6.0 gapps:) [emoji111]

Inviato dal mio SM-N920C utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Nothing??

[MENTION=4277844]chenxiaolong[/MENTION] This is nothing?? :eek:
[Galaxy S 4 i9505 Original Android Development] gaww:
90-100

128 gb are around $90-100 -did you get a 256 gb ?
[Galaxy S 4 i9505 Original Android Development] kykint:
Hi. I'm experiencing a boot failure with my custom kernel after updating the ramdisk.

My device is SM-G906K with stock touchwiz 5.0.1 installed as primary ROM.

I introduced an unique partition mount method in my ramdisk, which seems to be the cause: https://github.com/kykdev/lolliwiz-releasetool/commit/70c52d8

When I reboot after updating the ramdisk in the app, it gets stuck at Samsung boot logo (not bootanimation) and then automatically reboots into recovery.

Attached the logs. Hope you could find out what's causing the error.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that is exactly the cause. The multiboot code parses fstab to determine what partitions to mount. At the partition mounting stage, Android's /init has not been launched yet, so none of the init.*.rc files will be read and no scripts will be run.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Man, I must be blind lol. The issue wasn't in uevent at all. It turns out there's this line in the ramdisk that I overlooked before:

symlink /dev/block/pci/pci0000:00/0000:00:01.0/by-name /dev/block/by-name

I just need to do the equivalent in mbtool (and hopefully in a universal way that doesn't break other devices).
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
I thought that you already added this before, i noticed it in paths.

so its even more complicated now ? ?

Sent from my ZF²