yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

Thank you very much for your great tool!

My device is Samsung Galaxy S5 SM-G9000F (klte) which is supported by Dual Boot Patcher

But now I use PopWiz Telstra ROM v1.2 (TW 5.1.1) which is which is ported rom from Note 5 and in "Information about device" it looks as Samsung S5 Neo SM-G903F.

I can't update ramdisk ("Failed to update ramdisk").

Could you make possible to update ramdisk on my S5 with this rom ?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Today Lenovo released a new 1548 update for K3 Note and dual boot is working again, yay!

[MENTION=4277844]chenxiaolong[/MENTION] I discovered the root of my issue I described in this post some pages ago. The thing is that on my /root/data/multiboot/ there is a folder data-slot-internal where an old rom (360 OS to be specific) was installed. In this folder there are files and /system/xbin and /bin folders which were relaled to some chinese root app I attempted to install in this rom.

These files are undeletable by any means!

I tried the following with no success:

1)deleting the folder/files via root explorer and x-plore in android mouting the / dir as rw and setting the permissions to 777 as well

2)deleting them in recovery via the built-in file manager in TWRP

3)running terminal commands rm -rf, chmod, chown in built-in terminal in TWRP

4)changing the permissions in recovery

5)flashing the supersu to data-slot-internal in hope it will replace the files

I think the only solution to get rid of these might be some magic command by adb. What these files should be to resist the raw su commands? There are files named .ku found in /data/multiboot/data-slot-internal/system/bin/.usr directory. When I searched the web there are topics related to the kinguser app and how to replace it with Supersu. Thankfully I still have two ways to get rid of the problem:

#just to install my data-slot roms giving them some other name different than internal

##to use the method of brute force formatting the whole /data/media storage. [MENTION=4277844]chenxiaolong[/MENTION] mate, please tell me you know some command I can delete those files. :D I really don't want to use the ## step here, but it might be the only thing I can do.

EDIT: Now I'm thinking for other more elegant method to fix the problem:

To install this rom again in data-slot-internal(if possibly because all other roms are failing to install there) and to try this guide of replacing kinguser with supersu.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Based on your reply to this user, if one needs delete/wipe primary ROM(say logged in secondary ROM) the proper way to wipe but sparing multiboot files will be NOT to WIPE the selected items as seen in attachment, or should there be more items marked not to wipe?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Woot! :)

Ahh yes, some of those root software packages are very evil and set the ext4 immutable bit on their files, effectively making them nearly impossible to delete. You'll need to unset that immutable bit on those files to be able to delete them. You can do that by rebooting to TWRP and running the following command:

chattr -R -i /path/to/delete
rm -rf /path/to/delete

Let me know if that works for you :) I'll see if I can integrate that into the wiping process. I might not be able to if I need to include a bunch of ext4 source code.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, that kernel's ramdisk is compressed with a very old version of LZ4 that libarchive doesn't support. (libarchive is the file compression library I use to read/write zips and other files: https://github.com/libarchive/libarchive). It would take a significant amount of code to be able to support old LZ4 compression. Could you possibly use a custom kernel for that ROM? Or maybe ask the maker of the ROM to rebuild the kernel with a newer version of LZ4?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
All you have to do is add the following to your build.prop file :)

ro.patcher.device=kltetmo # or whatever klte device you have
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Those checkboxes apply only to the particular ROM you're trying to wipe, so it is safe to check all of them.

In the case of the primary ROM:

Checking "System" means /system (excluding /system/multiboot) will be deleted

Checking "Cache" means /cache (excluding /cache/multiboot) will be deleted

Checking "Data" means /data (excluding /data/multiboot and /data/media) will be deleted

Checking "dalvik cache" makes no difference if you're wiping data already

Checking "Multiboot files" means /sdcard/MultiBoot/primary will be deleted

In other words, it should always do the "right thing" and not break your other ROMs :)

EDIT: Not really related, but I usually don't even have a primary ROM. I just install my "main" ROM under the secondary slot so all the ROMs are cleanly separated in their own folders in /system/multiboot, etc. :)
[Galaxy S 4 i9505 Original Android Development] kingknuts:
here is the source of that rom with the comment and the reply:

http://www.htcmania.com/showthread.php?p=20651493#post20651493

In English:

KingKnuts: Hi!, One question:

I use a lot the dual boot patcher because of the data and app sharing between roms and dont need the Titanium Backup every time I change the ROM.

Now I installed the last version of NovaStock and the app isn´t able to patch the ramdisk to add the mbtool utility, ( It stucks in "Please wait" for hours, in others rom is almost instantly).

Could you add that utility??

SergioExtre: I dont know what to tell you, I dont use dual boot because I like a rom for everything, I see it stupid , take a look if anyone helps you.

I will try to use another kernel but the most of the kernels for the G3 are for AOSP based roms and not for the stock.

I don´t feel lucky...:crying::crying:

Now another question:

Is possible to keep the same bluetooth Mac address for all the roms?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Cool!
[Galaxy S 4 i9505 Original Android Development] pc boy:
I have installed the secondary rom to system, but when I share apps accros roms I cant see them in the secondary rom, is it normal?

Primary rom is modded deodexed stock, secondary is cm12.1 device is g900fd

Any help is appreciated.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
You must install the same *.apk you've installed in primary ROM(or which ever slot) then activate the "shared data" as well from other ROMS...they don't appear automatically coz you've shared from primary, you still need them installed in other ROM

New World Order (NWO)
[Galaxy S 4 i9505 Original Android Development] pc boy:
So what the app sharing is intended to do?

Isn't it supposed to share apps and data across roms?

If I'm gonna need to install apps on both roms, why use app sharing?

Plus I've enabled app sharing in both roms but the result is the same!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
That function it's intended to share "data" of the same app across the ROMS, this means that your whatsapp messages, game data/progress, offline email data etc will be synchronised no matter what ROM you're currently using...

If you don't activate data sharing for example(whatsapp) your messages in primary will never be synced with whatsapp messages in other ROMS ever until data sharing for app in question it's enabled!

.....

While your activating sharing, you'll see that you're only actually activating "data folder" not the *.apk file!

.....

New World Order (NWO)
[Galaxy S 4 i9505 Original Android Development] Ashwin Prabhunerurkar:
hi have been using you marvellous work on note 4 and its the best implementation of multiroms i have ever seen

i was thinking would it be possible for you to bring some of this love to the tab s tablets?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
:( :crying:

Wow, I didn't even know it was possible to change the bluetooth MAC address without messing with the bluetooth drivers. Maybe you could try backing up the bluetooth settings from one ROM using Titanium Backup and restoring it in another ROM.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you :D

One of the Tab S tablets is supported already. If you have another one you want me to add support for, just flash the GetLogs zip from https://snapshots.noobdev.io and send me the logs in /sdcard/logs/.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
I found a kernel that support the patcher!! ChupaChups kernel 20E now im enjoying cm11 cm12 and cm13 with all the beauty of the stock XD

Now i gonna try to keep the same mac address of the bluetooth in the other roms:p.

If i success with it i will report.
[Galaxy S 4 i9505 Original Android Development] pc boy:
Qouted from OP:

DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.

Is it right?

Or the OP has mistakenly mentioned apps??? [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
The recent releases by Chen excluded sharing the *.apk option and Continued only with sharing data folder (thank God)!

What the OP it's saying was true with older builds of the patcher application, it had the option to share *.apk or/and data folder!

But none of this really matters, your data folder it's shared, that's the important part of this function, your seTtings/ConFigurations/messages etc are stored in data folder for each app and activating sharing app, that's what's shared and that's what's important!

End!!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Hi

Don't you think think the CM 12.1 I gave the link can help you to fix the problem with this device?
[Galaxy S 4 i9505 Original Android Development] Ashwin Prabhunerurkar:
hi i was planning to get the TM 800 10.5 wifi version so just wanted to check with you

i will surely help you in any way you

will get back to you in 3-4 days once i get my tablet
[Galaxy S 4 i9505 Original Android Development] george stamatos:
[MENTION=4277844]chenxiaolong[/MENTION] is it possible to add "reboot to recovery" option ? Not a big deal , but helps to flash files directly
[Galaxy S 4 i9505 Original Android Development] monkteo:
You can flash from the app after patch ! if you wanted !
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Oh yes, I forgot !
[Galaxy S 4 i9505 Original Android Development] dave7802:
Good morning all.

Quick question, Anyone come across the PIE issue where patching to avoid the error message.

Is it possible to Patch the PIE Patcher.zip to flash on the secondary slot?

Each time i have attempted, the CM build fails to boot.

http://xdaforums.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731
[Galaxy S 4 i9505 Original Android Development] wawa9292:
reporting

Isn't anyone noticed or not..

So, app that doesn't have launcher/gui (ex: plugin, theme, add-on, etc) didn't have any option to share their data across ROM in app sharing section.. they doesn't even listed as an app..

I've tried some.. and a same..

How could i report it using log??
[Galaxy S 4 i9505 Original Android Development] karanpats:
Logs for OnePlus2 on reboot

Logs for OnePlus2 on reboot..
[Galaxy S 4 i9505 Original Android Development] nutpants:
Just picked up a Canadian note 3 (snapdragon)and have tried dual booting with factory oem Rom 4.4.2and w03 slim kat. 4.4.4

For some reason slim kat in dual boot only mounts my 64gb exfat micro sd card to /raw/extsd as read only...

(I also noticed my s4 (Canadian snapdragon) dual is not mounting its 64 gb exfat sdcard also.

(But have not tried that liquid smooth on it's own yet))

It works fine if I flash it by it self and mounts to sdcard1 and the other standard/usual places read/write.

Is this a known bug? As I could not find any info searching the thread.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The patcher specifically requests the external SD to be mounted as read-write ([1]), but the fuse-exfat driver used in most AOSP ROMs might force it to be mounted read-only if it detects some filesystem corruption. TouchWiz uses Samsung's own exfat driver that may not care about these issues. Could you try doing a filesystem repair on a Windows machine and see if that fixes the issue for you?

[1] "rw" @ https://github.com/chenxiaolong/Dua...b06fab466aa2b9e4f/mbtool/mount_fstab.cpp#L353
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Can anyone plz provide commands to use for backing up roms manually...I'm aware that there ain't any gui for this yet!

Even if not properly tested!

Thank you
[Galaxy S 4 i9505 Original Android Development] jroq8400:
+1

Backing up and restoring. Also how about cloning or moving from one type to another...like from extsd to cache and viceversa?

Thank you dev! Enjoying Imperium ROM as primary and cm 12 and 13 on extsd :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've posted instructions on doing backup/restore manually a while back: http://xdaforums.com/showpost.php?p=63505436&postcount=7419 :)

I do not plan on implementing a separate ROM moving feature because it will be very easy to backup a ROM and restore it to another slot.
[Galaxy S 4 i9505 Original Android Development] physwizz:
It might be best to reformat the SD card as fat32
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I am going to apologize right up front. You have gone over this several times for me, but it just may be above my intelligence level. :silly: In what you say above, if the rom I am flashing is f2fs everything, then my system has to be f2fs? My system is ext4 and I thought the rom I was flashing had system ext4, but I guess not.

Let me explain what I am trying to do. My Nexus 7 is a piece of crap. When I first got it, it ran pretty good. Through the upgrades in android it got slower and slower. People say design error with nand memory? I have been trying to find ways to revive it. The best I have found is a rom called optipop (5.1.1). I have system as ext4 and cache and data as f2fs. It runs OK, but noticeable lag. Somebody said that a version of cms11 runs much smoother and then someone else converted to all f2fs which they said was even better. Since my system partition is ext4, I tried converting the cms 11 all f2fs to system ext4 and cache and data f2fs (obviously incorrectly). I flash my convoluted rom and get:

mount: mounting /dev/block/mmcblk0p4 on /cache failed: Device or resource busy
[D] Running command: [ mount, /data ]
mount: mounting /dev/block/mmcblk0p9 on /data failed: Device or resource busy

and on system also.

I am obviously doing something above my pay grade. I have spent considerable time on this, an now am very curious. Am I trying something that just isn't going to work?

Unpatched version of my zip.

Feel free to say, "you are over your head."
[Galaxy S 4 i9505 Original Android Development] nutpants:
I'll do the file system repair today, and test again

But why would it only find an error and not mount when it is insured as dual boot

If I just install the rom all by it self it finds and mounts the micro sd fine and reports no errors.

Fat 32 is not an option,I have a few files larger than 5gb.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Coming soon: ability to queue up files for patching (and they patch simultaneously, not one by one). No more waiting for the nightly to finish patching before patching the Gapps. Also got myself a new S6 Edge+ on Black Friday so expect better support for 64-bit devices. :D
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Sweet. Same processor as s6 Edge. CYAN coming soon.. Will need a trusty dual boot situation :D
[Galaxy S 4 i9505 Original Android Development] todivefor:
Black Friday score! Congrats!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Great!!!

You are always improving.. [emoji41]

But what happened to the new UI?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I originally started with the new UI and reworked a ton of code for that. Then I found out the new code makes other features like this very easy to implement, so I started working on that also. :D

EDIT: Btw, still haven't been able to figure out the Mediatek issue yet.
[Galaxy S 4 i9505 Original Android Development] purist:
Speaking of..., could you please add support for zenltespr Sprint S6 Edge+. Thanks! :)

---------- Post added at 05:54 PM ---------- Previous post was at 05:13 PM ----------

I have a Nexus 6 and 7(2013) and notice this is similar to mutlirom. Are you using this as a base or model? If so, great! I've been waiting for this kind of support on other than Nexus devices. Do you intend to add TWRP support as well for better integration? I love you idea of sharing apps. Perhaps the mutlirom devs can learn a few things from you. Keep up the great work!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I waited for it! ^^

[IMG="Watering eyes^^"]http://i.imgur.com/TqS5I0f.png[/IMG]
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Nice

Can't that CM 12.1 be of any help?
[Galaxy S 4 i9505 Original Android Development] MBariya:
[MENTION=4277844]chenxiaolong[/MENTION] feature request: is it possible to add support to download apk file and aroma zipe within app?

Then that will easy to update your app.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Did a full test of the micro sd card in Windows 7

Zero issues found. So there is not a problem with the micro sd.

Are there any logs I can get you to help trouble shoot this?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
So guys is there any workaround to install system.dat roms in any other slot than primary? I can't get it to work. I can extract the file just fine, but writing the whole updater-script from scratch for every single rom using the new installing method is too much work for me.
[Galaxy S 4 i9505 Original Android Development] Ashwin Prabhunerurkar:
as it turns out only one variant of tab s is supported and that is 8.4 inch

i have 10.5 inch screen TM-800

http://www.gsmarena.com/samsung_galaxy_tab_s_10_5-6438.php

i hope you will give my tablet the support it needs

Here is the log

https://drive.google.com/open?id=0B6dHVx2zEkoXV1A1WkNyMXpNTWc

Thank you
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Just gave v1932 a try but unfortunately noticed that the feature 'app sharing from primary rom' to the others has been removed?? Why is that? Will go back to 1777 for now :/
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Well that's odd!

I'm using 1932 mate and app sharing works perfectly across my tipple boot!

Maybe few concepts need be cleared:

1.data folder sharing (this is all you need)

2. *.apk sharing (this was a feature of old version of the patcher, really not necessary since what's needed it's app data)

......

In short: app sharing works from anyway by simply enabling SHARING DATA of a specific app then boot into your other rom's INSTALL(only) that same specific app you've enabled sharing for, and now enable it to share the SHARED data folder, that's it, and you'll see that the apps share SAME folder)

....
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=6080477]danerrickcuba@gmail.com[/MENTION] Mate did you tried to install "system.new.dat" roms to data-slot or extsd slot? Installing always fails on me. Is it a problem with K3 Note particularly or others have this problem too?

I want badly to try the new November release of CM12.1 but I can't try it as it's compiled as system.new.dat
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
I have no problem to install system.new.dat ROMs on my galaxy s5 (cm12.1 based, cm13). Only I cannot install on ext SD
[Galaxy S 4 i9505 Original Android Development] v00d007:
Sorry, "mate", that's not what I'm talking about! I'm missing the option "share apps from primary rom" to the others, that meant NO CHANGES to the primary rom/kernel_ramdisk/data_folder was necessary. This option has been removed in latest builds. But I asked [MENTION=4277844]chenxiaolong[/MENTION] anyways...
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Okay thanks. At least now I know that it's a problem with my phone. Oh well...
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I was going to say that..

Our device [emoji29] [emoji25]
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Sorry guys
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Bro, don't be so pessimistic. We can always install system.dat roms as primary, the only limitation is that we can't use two or more system.dat roms at the same time, but it's more than nothing. :D May be I'll try to rewrite the updater-script and convert this ROMs to system/app. I'm just lazy it's not so hard. :silly:

BTW One question: Can I have more than one extsd slot giving them a different names?
[Galaxy S 4 i9505 Original Android Development] todivefor:
You could flash it to primary, back it up, and restore to wherever you want it. I've done this several times testing backup/restore.

As to your question, I believe you can do any number just giving different names. Limiting factor is space on extsd. Correct me if I am wrong.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes, confirmed. Just flashed another rom to my extsd slot a few minutes ago. Now I'm having two roms on extsd card. I just don't get what's the purpose of the multi-slots which will attempt to install the rom in the /cache partition?? Who is having 2.5GB cache partition? Mine is 500MB for example. In the other hand I have 1.3GB free space on the /system partition which is unusable because the space is not enough for installing a rom there.

Just to clarify backup/restore via this guide right?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Yes. Works great!
[Galaxy S 4 i9505 Original Android Development] karanpats:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi i am unable to use App sharing feature on my OnePlus 2..

I have attached getLogs logs after the reboot.

It gets stick in recovery loop after updating ramdisk on primary..
[Galaxy S 4 i9505 Original Android Development] gaww:
Sorry to ask this, but could not find it with searching.

With a ROM installed on ExtSD, The External SD files are seen by Root Explorer but not by the ROM (nor Titanium) . There was some earlier posts on how to work around this.

PS - Am trying ASOP 6.0 there, and it is working good - except for the above - lol

Still wondering why it, as well as CM 13, it is so slow. Have read the official 6.0's are faster than 5.0 - but not these (kernel?)
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Could be your SD card is exFAT?

I had to copy all to PC, format SD as FAT32 and now have kushan CM13 on extsd and able to see the SD card.
[Galaxy S 4 i9505 Original Android Development] purist:
I've added this line to my build.props 'ro.patcher.device=zenltexx' to try and get my s6 edge+ (Sprint) phone working with this app and I've been able to get the app to function properly now, however when I reboot, after selecting the secondary rom, my phone hangs on boot and I have to reflash a kernel to the primary rom to get my phone functioning again . is there anything I can do about this or do I just have to wait until official support for zenltespr comes out? If there's any outputs i need to provide to help please let me know.