yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I actually did this exact thing but still unsuccessful. Flashing was successful but the Imperium ROM didn't show up. I mean there was like an "Unknown" something like that written in the Multi tab.
[Galaxy S 4 i9505 Original Android Development] gaww:
I m not sure where things are with this situation now - I never had trouble flashing/booting up Imperium - several versions.

Maybe generate a logicat and send it to the OP - he should be able to see what is happening.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Galaxy Tab S

I got this dual boot patcher to work on my Galaxy Tab S t700:D

I found that sharing app data won't retain the original data but it starts sharing fresh data. Is it possible to restore the original data with titanium backup?

---------- Post added at 08:48 PM ---------- Previous post was at 08:42 PM ----------

Zarchiver will let you do it on android.
[Galaxy S 4 i9505 Original Android Development] xdasree:
Problem with patching kernel.

Everything works fine except I can't flash new kernel.

I'm trying to patch arter 7.1 kernel.

It says:

Failed to patch file

Failed to open archive for reading.

Attached screenshot
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Missed my own ETA again (what a surprise!). 8.0.0.r1506.gacad6f0 is probably one of the biggest releases in a while. It comes with a whole bunch of low-level changes as well as UI changes.

Bug fixes and changes

If you had issues booting a ROM before, chances are that it's fixed now.

General changes:

Fixes issue where ROMs will hang indefinitely at the boot animation (notably in AOSP-based ROMs when the primary ROM is TouchWiz 4.4.x).

Fixes boot loop in ROMs installed to a data-slot via in-app flashing (notably when flashing from within TouchWiz).

Fix issue where flashing a custom kernel with SELinux set to permissive was necessary to boot CM under certain conditions.

Automatically sets ro.patcher.device in /default.prop so the patcher recognizes the correct device on ported ROMs.

Fixed reboot to black screen issue on the Note 4, which required a battery pull or holding Vol-Down + Pwr for 10-seconds to recover.

Technical changes:

The biggest change is that we now mount all the partitions before we execute a single piece of Android code in /init. This allows the environment to be properly set up the way Android wants it before Android actually starts booting. As a consequence of the new init-wrapper:

Charger mode (battery display when powered off) will now work no matter which ROM is selected.

Updating the ramdisk is now a safe operation (!!) that should no longer break future boots.

The Note 4 audience es705 driver will no longer crash the entire device and reboot into a black screen (grr.. crappy driver not checking return values).

Adding boot-related features and bug fixes no longer require the ROM or kernel to be repatched.

Removed more than 3000 lines of device specific code that's no longer required.

Fixed potential security vulnerability with world-writable fstab.

Fixed potential security vulnerability with world-writable /file_contexts

Fixed potential partition mounting failure when ROM expects one partition to be eg. ext4 and another to be f2fs.

Properly copy attributes and xattrs when copying /system trees. Fixes issue where ROMs installed in a data-slot via in-app flashing permanently stop working unless /data/multiboot/data-slot-<id> is deleted.

Defer attribute and xattr copying to the end of the copy operation when copying /system trees to ensure that directory traversal is possible during the copy process.

Copy SELinux avtab allow rules from media_rw_data_file to the type on /data/media/0 (or /data/media if it doesn't exist). Fixes installd crash due to SELinux denials leading to an indefinite hang from the inability to create the dex caches.

UI changes

The app is now a bit more materialized ;) We have a brand new navigation drawer and some other changes, like showing messages in a snackbar and rearranging the patcher options. The app will also try to stop you from setting the kernel for the wrong ROM. Anyway, screenshots are worth 1000 words.

I'm open to suggestions on how to make the app more materialized! Also, feel free to let me know about any lag, frame drops, or other performance issues in the app.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Downloading now!! Can't wait to test on the lovely S6 edge from t-mobile
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thank you, thank you, thank you! I could hardly restrict myself from asking for ETA during the last two days or so... ;)
[Galaxy S 4 i9505 Original Android Development] sronweb:
installed and working fine on S4 I9505. Thank you!!!
[Galaxy S 4 i9505 Original Android Development] bnevets27:
Great update chenxiaolong! Small request/suggestion. Could you make it possible for the app to be updated within the app?

Thanks for all your hard work!
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Great update! Thank you!

I would like to ask you for add some more tools for management of shared application list, like:

- filters (shared apps, apps with shared date, shared apps with shared date

- select/unselect all apps on list

- share/unshare selected apps

It would really help a lot in testing
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I don't know if this is impossible to get done but I hope there would be a way to add a rom from NANDROID BACKUP. That would be great.
[Galaxy S 4 i9505 Original Android Development] xxhaimbondxx:
Maybe I've missed this while searching this thread, however, I would like to update CM12 nightly, which is located currently on my secondary. I downloaded the zip and patched it as previously however, everything went haywire and I had to reflash the stock rom and the previous version of nightly. Any help would be appreciated.
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I've had that happen to me a number of times, I think going on 3 or 4 now. It's not too much of a big deal, just quite annoying lol

Sent from my dual boot PAC'd/touchwiz S4
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Can we please get support for Beanstalk on AT&T please?

http://xdaforums.com/showthread.php?t=2304815
[Galaxy S 4 i9505 Original Android Development] ahoslc:
And Slimbean S4 Verizon please :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Should be already supported :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If everyone could make the ROM requests using the "Feature Requests" tab at the top, that would be great :) That way, I can track all the ROMs I still need to add support for.

Support most of the ROMs you guys have been asking for done (in version 2.0), but I haven't released it yet because a bunch of recent AOSP changes to the ramdisks, like adding framework libraries to BOOTCLASSPATH and disabling the mounting of some partitions to help with the Samsung logo hanging. Once I get that sorted out, version 2.0 will be released :)

EDIT: I have a solution to avoid always having to update the ramdisks :) Might have a solution for loki'd kernels too, but not 100% sure.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can someone post the output of:

cpio --help

on OS X? I want to make version 2.0 Mac-compatible from the start.
[Galaxy S 4 i9505 Original Android Development] Netuser:
Hi,

Is data sharing now supported ? Do i have to install an App 2 time in both rom ? Also SMS/email are synched between 2 Roms? I read the change log and didn't found it, sorry if it was already answered

Also can you add support of ice cold ROM here : http://xdaforums.com/showthread.php?t=2492021

Thanks :)
[Galaxy S 4 i9505 Original Android Development] Sushibagel:
cpio(bsdcpio): manipulate archive files

First option must be a mode specifier:

-i Input -o Output -p Pass

Common Options:

-v Verbose

Create: cpio -o [options] < [list of files] > [archive]

-J,-y,-z,--lzma Compress archive with xz/bzip2/gzip/lzma

--format {odc|newc|ustar} Select archive format

List: cpio -it < [archive]

Extract: cpio -i [options] < [archive]

bsdcpio 2.8.3 -- libarchive 2.8.3
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Sir I'd love to add to the list but I'm on mobile :/ lol
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
Hey [MENTION=4277844]chenxiaolong[/MENTION] anything on this
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Does not work on the nightly for S4 Verizon I accidentally downloaded the slimbean for Tmobile and that patched fine. However that will not work since I am on VZW.
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
also wanna update for the new release of foxhound? :)
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Hey [MENTION=4277844]chenxiaolong[/MENTION] here is a beautiful S4 android 4.3 ROM.

Please make sure to support the XXUBMJ5 4.3 release (Vision X 2). This rom is amazing! Thanks for the hard work btw!

---------- Post added at 11:27 PM ---------- Previous post was at 11:25 PM ----------

Oh and almost forgot to post the link to that Vision X 2 ROM! :)

XDA link: http://xdaforums.com/showthread.php?t=2391142
[Galaxy S 4 i9505 Original Android Development] mapobean:
Weird solution to no boot

I was having issues getting the newest task650 AOKP 4.3 10-22. I had no problem patching the ROM with your patch but i could not get it to boot. I tried several different Kernels but they gave me the blue tint and color issues. What i did was copied a boot.img from a previous Dual ROM into the zip and it flashed although still with the color distortion. I then flashed the unmodified patched ROM over that without clear cache and everything is working fine. By the way awesome work i was trying to dual boot this similarly to how you dual boot the Atrix prior to your work. :eek:

Oh im on an ATT s4 with the new Echo 5 as primary ROM but found no matter what the primary ROM it did not matter.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Man... Some of you guys should really try manually patching. Seems like you guys are just flooding his thread with requests, give the man some room to breathe!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem at all :) I add them if no one else did it already.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The patcher now has intelligent ramdisk patching on Mac and Linux. I still have to get it working on Windows. This means dual boot from now on is just a matter of modifying the updater-script. A ROM should never be unbootable because of ramdisk changes again :)

EDIT: This is really my work a whole lot easier (and faster :)).
[Galaxy S 4 i9505 Original Android Development] gaww:
That sounds great for us and for you - looking forward to v2.0.

Have been trying Omega v13 and was considering it as a base (no way to have 2 TW ROMs - even unbloated duel booted I assume), but as it is based on 4.3 leak and we on US TMo have badly out of date firmware - especially modem, it is causing more issues then earlier 4.2 Omega versions.

So back to Wicked base. Besides your patched 10.2 I have been using, wondering what other posters would suggest as a second 4.3 ROM (I weight basic Features working over themes and new features)
[Galaxy S 4 i9505 Original Android Development] GhiGo65:
Hy chen

I have Always used your patcher with carbon and it worked Always well, but with last builb the system ui fc continuoslly...

With other build of carbon is ok but wit build of 23 october no.

I download two times to verify the zip but is ok... And i flash without patch it and is ok too.

Has Probably The team changed something that made your patcher not to work?
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
I just installed Jamals 4.3 google edition rom as secondary rom over Omega V13.

Is there any way to sync whatsapp between the two? And also maybe sync all the apps? Because now I have to install them on both roms.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Working on it :) That kernel uses LZO compression of the ramdisk. I just need to rebuild the copy of the libarchive compression library I use to enable LZO. If all goes well, I'll make a release tonight that fixes this.

EDIT: Fixed in 8.0.0.r1515.gf3c310a
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does anyone have any objections to temporarily dropping Intel x86 and x86_64 support from the patcher until there are more Intel-based devices around? Right now, every single line of code is rebuilt 5 times (Android: arm, arm64, x86, x86_64; and Windows: x86). The build are really killing my old server with the build times ranging from 19 minutes to 55 minutes. https://jenkins.noobdev.io/job/DualBoot_Patcher/buildTimeTrend

If anyone is actually using an Intel device, let me know and forget I even mentioned this :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
No objections ;)

So far, no use of x86 or x86(_64)

P.S. I'm actually using Samsung XE700T1C (IA-64 based device) as you can sign from last line in my signature, but dual-boot is based on simple GRUB there.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Hello

Running this on HTLE (Note 3)

And am really confused, Installing a TW Rom as Prim, Normally uses up the full /System storage 2GB limit.

So when it comes to installing a CM base rom as Secondary., it always runs out of space and fails.

I have tried to install the patched files to DATA and selected 5 as the ID. but it never boots, Just boot loops before OS is loaded?
[Galaxy S 4 i9505 Original Android Development] xxhaimbondxx:
Anyone? Bueller?
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Checkout this post http://xdaforums.com/showpost.php?p=62030012&postcount=6546

It's because the patcher reads something in the install script and converts it to format data

You will have to edit the script once you have patched the original file to you choice of install location.

I've not bothered with either way currently because I'm tired of keep setting my phone up again and the AntaresOne 12.1 Cyanogenmod is supposed to be clean flashed.
[Galaxy S 4 i9505 Original Android Development] gaww:
App Sharing

I am still fiddling around trying to optimize individual app sharing (for some reason global gets tangled up with Play services and store - which are system apps), and am not sure of the requirements for the setup.

Can we do both - move apps to SD and share them (the remainder plus data), or do they have to be only on the device memory only and not on the SD to share?
[Galaxy S 4 i9505 Original Android Development] nutpants:
Is there any way to switch roms other than going into the app?

A widget or icon that sets a different rom then reboots with a singer tap and maybe a confirmation?

If not then consider this a feature request.

( no I'm not using this to hide certain phone usage from an extremely hot but noisy woman in my life)
[Galaxy S 4 i9505 Original Android Development] sronweb:
Hello [MENTION=4277844]chenxiaolong[/MENTION],

I suppose its' not my fault :) but I have an error trying to flash the patched zip to install Xposed module on CM12.1 on Multislot 1:

http://xdaforums.com/showthread.php?t=3034811

http://xdaforums.com/attachment.php?attachmentid=3427354&d=1438626996

Patching was ok but I get an error while flashing with TWRP. Please, could you take a look to my log?

Or perhaps it's not compatible with CM.12.1...

PS: it was my mistake. This is the correct version for CM12.1 and patching was ok now!

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
[Galaxy S 4 i9505 Original Android Development] xdasree:
Wonderful...It's working now. Thanks a ton.

I have one more issue. On Primary rom I can't update ramdisk to app share, It says Failed to update ramdisk. I can update ramdisk on secondory rom. But I want to share apps from primary rom.

Thanks again.
[Galaxy S 4 i9505 Original Android Development] xxhaimbondxx:
that should do it, although, I don't get why doesn't it work when I download ROM directly from the web and install on clean secondary partition. Only the original ROM form 7/28 works.

Well, it didn't work anyway. I can't find the line in the script they're talking about. I have LG G3, but the issue is still the same .
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
I remember mentioned thus long time ago but I guess the dev have other priorities right now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Apps on the SD card are encrypted and can't be easily shared. You might be able to get the apps on the external SD to show up in another ROM by copying /data/misc/systemkeys/AppsOnSD.sks from primary, but I've never tried that and don't know if it works.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Anyway you could wrap that log in [code]...[/code] tags? For some reason XDA's vbulletin formatting is making it unreadable. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you update to 8.0.0.r1519.gceac661 and try updating the ramdisk again? This new version will log everything to /sdcard/MultiBoot/ramdisk-update.log, which should be able to tell me what's going wrong. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since a switcher widget seems be to much requested, I can try working on that this weekend. As I have no troubles programming, but completely suck at designing, I have a few questions:

How do you expect the widget to work? For example, do you want a separate widget for each ROM? (This would be kinda like Chrome where you would click "Add to home screen" in the menu and get an icon labeled "multi-slot-1" on the home screen). I rarely use widgets, so I don't know what would be useful and provide a good experience. All suggestions are welcome (and mockups would be fantastic!).

Thanks!

EDIT: (Shameless laziness: if everyone is happy with the method I described above, it'd probably take me less than 30 minutes to implement ;))
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You ran out of space on the system partition, so you won't be able to install as secondary. On the Note 4, the cache partition is extremely tiny, so I'd wouldn't use the multi-slots either. Your best bet is to install to a data-slot as those use the large data partition where your internal storage is.
[Galaxy S 4 i9505 Original Android Development] xdasree:
No luck on r1519 too. attached screenshot and ramdisk-update.log for your reference.

And also one more thing. As I mentioned in earlier posts while I'm having problem with patching kernel, I can path the kernel with next release but I can not flash it. Error saying "Failed to load boot partition image". Also attached MultiBoot.log if that helps.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], someting went wrong with ramdisk update on my N910G (Note 4) Primary TW-based 5.0.2 ROM on 8.0.0.r1519.gceac66.

It was working before, but after manually renaming the /sdcard/Multiboot folder and flashing original boot.img from recovery, it went broken.

App doesn't update ramdisk. It was like that with the previous snapshot as well...

Here is the link to ramdisk-update.log, maybe it'll help:

https://goo.gl/DFZVJ6

EDIT: pastebin link might be a better option.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Or better attach a file or provide a pastebin link...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! The two issues are actually the same.

From ramdisk-update.log:

08-06 12:58:35.994 8698 8789 E libmbp : Device tree image exceeds boot image size by 151552 bytes

From MultiBoot.log:

[E] Device tree image exceeds boot image size by 342016 bytes

The device tree image the logs refer to is at the end of the boot.img file. When it throws an error message like that, it means the boot.img was bigger than the boot partition and part of the device tree at the end of the file was chopped off. Since your primary ROM seems to boot OK, I'll can make the patcher ignore this error. I'll do that after work tonight.
[Galaxy S 4 i9505 Original Android Development] xdasree:
OK..understand that.

Thanks for great work and support.
[Galaxy S 4 i9505 Original Android Development] gaww:
Thanks - I removed a big shared one from SDcard on both ROMs, and after it setttled down, total available space on both ROMs close to where it was before. So app sharing saves close to the space saved by just putting apps on both ROMs on SDcard.

Would be nice to have my cake and eat it too (save space both ways), so may try above once after I make an updated backup.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], here is another log with error when trying to update ramdisk: http://pastebin.com/raw.php?i=rcw1zjTm

Now, something related to mbtool binary shows up in log... Trying to solve it.

Previously, I solved mysterious issue with read-write permission suuport for /Multiboot/primary/config.json (just copied that file with all subfolders from backup in TWRP), so your tool can read config.json and folders now. (EDIT: maybe that issue was because SupeSU didn't granted it's right to the app)
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
please help me understand:

assume i have the same app on two roms. then i would have the data on my sd card twice, right?

assume now i want to share the data between roms. would i now only have one copy in /data/multiboot/_appsharing or three copies, twice for each rom and a third one for sharing?

problem is that i am running out of space on my sd card...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! Would you mind trying again with 8.0.0.r1521.g32a1fa4? This new version doesn't fix anything, but just improves the logging. It looks like the app might have stopped logging before the error happened because I'm not seeing anything wrong in there.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! Could you check your root settings to make sure the app isn't blocked? The log says:

08-06 16:27:17.788 14185 14758 W System.err: java.util.concurrent.TimeoutException:
08-06 16:27:17.798 14185 14758 W System.err:	at com.stericson.RootShell.execution.Shell.<init>(Shell.java:203)

which means either root was denied or it waited too long at the popup.

(By the way, the app should automatically fix permissions on /sdcard/MultiBoot/ whenever you switch ROMs)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, if you are sharing data, you will have 3 copies. I simply haven't gotten around to implementing something to manage that yet. As a temporary workaround, you can clear data for the app before enabling data sharing. That way, the /data/multiboot/_appsharing copy will be the only copy.
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
thanks for the info. thing is though that this data will have to be recreated. for example if you take a navigtion app you would have to redownload the maps