yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
So weird that doesn't work with my method cited before?! :confused:
[Galaxy S 4 i9505 Original Android Development] dicko101:
I know, I'm no dev but I don't get it either, I currently have Echoe as primary and CM11 in multi 1, I had PA in dual but wiped it not long ago, CM is my daily, I'm trying to put this CM12 rom in dual, I thought maybe the zip didn't download properly but I downloaded twice and the patcher works fine on both so it should be fine, I have around 1GB free in system so there should be no problem there either. I don't suppose anyone knows of any other stable lollipop roms I could try? TW or CM would be good.
[Galaxy S 4 i9505 Original Android Development] gaww:
Echo just came out with a 5.0. Hasn't tried it as I don't have that much room anywhere as opposed to CM12. Even with GAPPs, you have plenty of room in secondary for CM12.

Did you wipe secondary system (only) and the caches before flashing CM12. Also, did you use app or PC zip to patch ?
[Galaxy S 4 i9505 Original Android Development] monkteo:
Man I am so upset because I manage to patch Antares CM12 before multislot 1(03.12 version) on my phone with an GUI-debug patch , and now I can't.

It patch but after installation remain on Samsung window.

I can't use the pc version because I have 64 and not working.

Help what to do ?
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I have this every time I patch a rom with the debug version:(
[Galaxy S 4 i9505 Original Android Development] dicko101:
Im using the app. I just tried the echoe one and got status 7, was using philz touch recovery cwm 6.0.4.5 just tried cwm 6.0.4.7 and got the same result with both echoe lollipop and cm12 lollipop as I did before, don't know what to do with them,I'll try the pc program.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
If I understood well, you have:

Echoe as primary

PA as Dual

CM11 as Multi-Slot-1

You want to install CM12 like Dual, so instead of PA. Maybe, it can have an issue to install CM12 in the same partition than the system partition, I don't know. :confused:

Do you do with the same Debug version? Personnaly, I've never successful with the Debug version! :p The only time where I've successful to patch it, I've got the same issue like you.

A last thing, unlike those who don't have the DualBoot or are with MultiROM, I have to wipe the system at each time, since the build of Nov 27.

Debug version has never worked for me... at least to patch.

---------- Post added at 12:34 PM ---------- Previous post was at 12:28 PM ----------

Philz's recovery isn't recommended for Android 5.0, in more if you add a semi-compatible app, then I'm not sure the whole works. I use TWRP 2.8.1.0.
[Galaxy S 4 i9505 Original Android Development] monkteo:
[MENTION=231423]franz[/MENTION]roy , yes with the same Debug version(I don't know what happening)

Now something new , the rom is installing (and start) but gapps not , and my primary rom (SHOstock-i) not working I can't se the rom in romchanger (so I restore my save)

Strange ?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For my primary, I've got the same issue as you, I've due to re-install my Echoe rom (primary which is in system partition), no matter, I should update it, I think that's due to the latest CM12 of [MENTION=5464206]AntaresOne[/MENTION] where he said to have fixed the issue of compulsory "Wipe system". I believe that the issue comes to there! :(

For Gapps, what are the Gapps that you took? What settings did you do in "preset" of DualBoot?

---------- Post added at 02:36 PM ---------- Previous post was at 02:33 PM ----------

I forgot, no issue with DualBoot Patcher for PC and Windows 8.1 64b!!!

---------- Post added at 02:51 PM ---------- Previous post was at 02:36 PM ----------

For this issue, I think to know a way to fix that! ;) I'll take a look and tell you later.
[Galaxy S 4 i9505 Original Android Development] monkteo:
The gaps it's the last you posted in CM12 Antares.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Those one are good for the DualBoot! But how did you choose to patch them? What settings?
[Galaxy S 4 i9505 Original Android Development] gaww:
The fix for the 64 bit PC issues is contained in an earlier post not long ago. You have to put two .dll files in the GUI patcher folder. The link to them is there - I had the problem and subsequently used them to patcher latest CM 5.0.1 and flash successfully

I would post them here, but I want users reading this and wanting them to go back and get them from the original poster - don't forget to thank him or her. It was by lukas77 in post number 4538.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
University finals are finally over! :D

I'll be able to help out and post here every day now (not every 2 or more weeks anymore :p)

Announcement regarding CM 12 and Google Edition 5.0 ROMs coming up.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Great! :good:
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Santa Claus is coming to town ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Screenshots first :)

Google Edition 5.0 ROM:

CyanogenMod 12

EDIT: These were the ROMs I used:

Google Edition: http://xdaforums.com/showthread.php?t=2557353

CM12: http://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934

Major changes:

Initial material design changes, of course :)

Behind the scenes is the introduction of the new 'mbtool' (MultiBoot tool) I mentioned a month or two ago. This is one of the biggest changes to the patcher since the first release. This tool handles all of the dual boot operations during bootup (after the ROM is installed). It mounts the partitions and sets up the environment in a way that Android expects. Every single ramdisk/kernel hack used before is no longer needed now. This means:

No ext4/f2fs/whateverfs checking. If the ROM supports a file system, then the patched ROM will too.

No custom init binaries, as such the ones that caused camera, sound, and vibration motor issues in TouchWiz 4.4 ROMs before (and also the severe lagging in some TouchWiz 4.3 ROMs).

/data/media is actually /data/media. If you use the FolderMount app, you no longer need to use the old /raw-data/media path.

No more setting SELinux to permissive. This was previously needed so partitions could be mounted in the correct locations on some ROMs. This broke many Android 5.0 ROMs because stock Android no longer allows SELinux to be turned off or set to permissive. The patcher now modifies the SELinux policy during boot to allow itself to perform the operations it needs to (similar to how SuperSU works).

The patch no longer cares if the ROM is AOSP, Google Edition, or TouchWiz. They can all be treated the same way now.

It non-technical words, any ROM that successfully installs will be able to boot, whether it's supported or unsupported. And because the patcher does not need to modify critical parts of the ROM, dual booted ROMs should works just as well as if it was installed as primary. This is certainly something I could not guarantee before. :)

Another plus side is that it makes supporting new devices ridiculously easy. 30 lines of code and now my Moto G, Nexus 7, Note 4, and a friend's OnePlus One are now dual booted.

--

Now that mbtool is complete and Android 5.0 is supported, I'll be focusing all my efforts on getting app and data sharing working properly. Looking back at my old code, it's written so poorly, it's no wonder that apps mysteriously disappeared after a reboot.

--

The patcher should be stable enough, at least as a beta, so I've turned on the snapshot builds again (as a few of you have already noticed :)). Any build earlier than 8.0.0.r406

will not work

(because I was an idiot and hardcoded the version "9.0.0Alpha6" in some of the code).

As usual, snapshot builds are available here: https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] peppe130:
Good work mate ;)
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
Great work! About to dualboot Danvdh's GPE 5.0 now, but I wanted to let you know beforehand that rom settings in the patcher force closes for me.
[Galaxy S 4 i9505 Original Android Development] gaww:
Ditto -

I see that primary patcher is no longer in choices - is it no longer need if primary is reinstalled ? That was done to prevent ROM install scripts from wiped tot al /system and wiping secondary ROMs.

Should all current ROM s installed to partitions be repatched with the and reflashed ?

WILL app sharing as-is work the same as currently until your new one is released ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Fixed in 8.0.0.r408 (should be uploaded in about 10 mins)
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
Chen, you da best.
[Galaxy S 4 i9505 Original Android Development] peppe130:
[MENTION=4277844]chenxiaolong[/MENTION] Italian translation is ready :) Tomorrow I will check it once again

---------- Post added at 01:28 AM ---------- Previous post was at 01:20 AM ----------

Chen using the latest snapshot (DualBootPatcherAndroid-8.0.0.r407.g99ac4eb-snapshot.apk), when I go to settings, the app crashes
[Galaxy S 4 i9505 Original Android Development] gaww:
This up yet ?

Update

409 is - no more fc
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, looks like I missed a file. 8.0.0.r409 should be up now.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Hi Chen

Like usually, we have to patch again the others rom with the latest app, at least theirs kernels, no?

Great work! :good::highfive:

---------- Post added at 08:06 AM ---------- Previous post was at 07:54 AM ----------

Is it normal that rom settings still do FC?
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
I can confirm that there's no more FC in rom settings. I do, however, get a failure message when I try to update ktoonsez' 4.4.4 GPE kernel ramdisk for app sharing.

One more thing. I'm not sure if this has been addressed before because I've read a lot of this thread and don't recall seeing anyone post about it, but even after having no more dual or multiboot roms as well as the patcher installed, I still get an extra long boot time when I finally do install the patcher and boot into the second rom for the first time and discover that apps are still being shared from from when I did have it set up.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I get ramdisk upadate error with the new snapshot
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I always have FC(s) in rom settings.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, I didn't make no modification I just leave the setting standard , and you now what I notes ? the installation of the gapps make in primary rom (SHOstock-i) !

what modification should I make ?

(preset - gapps-cyanogenmod) it's the only one !
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

In the last roms of AntaresOne, there is a script (/system/bin/format.sh, I think) which deletes the system partition when we install CM12, I install it like Multi-Slot-2 but I think it's same for another dual. Do you think that you could do anything to avoid that?

---------- Post added at 09:12 AM ---------- Previous post was at 09:09 AM ----------

Yeah, preset - gapps-cyanogenmod.

I never install Gapps with SHOstock, neither TW, no need!
[Galaxy S 4 i9505 Original Android Development] monkteo:
neither I , but the installation of the gapps for cm12 Antares (patch multislot1)go to the SHOstock-i partition

PS. with the last patch posted by [MENTION=4277844]chenxiaolong[/MENTION] working OK, no more erasing primary partition (tested by me)(patch 8.0.0.r409)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Maybe if I patch at least the kernel with this patcher, rom settings will work again! :silly:

---------- Post added at 09:38 AM ---------- Previous post was at 09:26 AM ----------

It's because you take the PA Gapps, the team has changed the way to install them, and I think that @chenxiaolong perhaps doesn't still have the time to see that.

---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------

Weirdly, impossible for me to patch anything with the r409! :crying: on CM12

---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------

Edit:

I'll try it in another rom

Done

---------- Post added at 10:27 AM ---------- Previous post was at 09:51 AM ----------

Good new! :laugh:

The patcher r409 works on Spirit rom, I've successful to patch C12... however, no success with Alucard kernel. :rolleyes:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Still more a good new!!!

The patched CM12, I installed it, no need to wipe now, all works fine and finally DualBoot Patcher 8.0.0 r409 works, I can access at all.

Thanks Chen! It's really a great work.

Just one thing, if you can do that Patcher works for Alucard kernel, it will good! ;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

It's good for me, all works fine in the latest DualBoot Patcher, even the Alucard kernel, I should just choose /JFLTE/kernels/Alucard in preset.

Thanks! ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
One more time - to avoid wiping duelboot when installing primary ROMs, will that option be added back to the patcher menu ?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What option???
[Galaxy S 4 i9505 Original Android Development] gaww:
Besides duelboot thru multiboot3 as patch locations, it also had an option to select primary.

When chose, it looked to see if there as a script that wiped system and,or cache. If not found - primary was not patched. That is all it did - but not present in new snapshots.

---------- Post added at 08:54 PM ---------- Previous post was at 08:46 PM ----------

Is anyone else finding that when flashing 5.0 GAPPs (with all the ROMs in app sharing mode). that the flashed 5.0 apps like play services wreak havoc with the 4.4.x ROMs Google apps - as they are apparently not compatible ?.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
In the new snapshot, there isn't "primary rom upgrade".You would mean that, right? There's not anyway. Why? It's useful.

I don't understand for the Gapps 5.0. If you flash them for Android 5.0, they are shared with all roms, except, they aren't compatible with others versions than 5.0.
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes - primary upgrade. That was only to avoid wiping out secondary by wiping /system and all the MultiROMs by wiping cache. Ii was very useful and I will continue to use the old patcher for upgrades, Don't know why it was dropped,

Correct on 5.0. these google apps are not compatible with 4.x.x , so when in my case I when flesh them as duelboot with app sharing set up, they knock out the 4.x.x google apps that are not system apps (and it appears they might affect these also for some reason)

This definitely an app sharing issue that needs to be addressed.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You can use the old snapshot for the primary and the new for the others, i continue like that, it works.

OK for the Gapps. Otherwise, you those one for CM12, no issue!
[Galaxy S 4 i9505 Original Android Development] omnifarious:
Sent from my SGH-M919
[Galaxy S 4 i9505 Original Android Development] franzyroy:
How we could miss it! :good:
[Galaxy S 4 i9505 Original Android Development] sronweb:
Today I have tested r409 release and it's working fine. No issue accessing to on "Rom settings" and I have patched and installed succesfully last CM11 nightly as secondary.

Thanks to the great job Chen!!!
[Galaxy S 4 i9505 Original Android Development] Ovegik:
Good work!

Quick question: if i format system/data/cache to f2fs for my primary rom but my secondary isn't compatible with it, would it work?

Or do i need to keep the ext4 format for both to work? I'm talking for the same roms mentioned in the update (danv's and and antares' ; antares' is f2fs compatible

while danv's isn't).
[Galaxy S 4 i9505 Original Android Development] jotade:
Hi thanks for the link but in my windows 7 says im missing this file MSVCP120.dll is that normal? Thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You have to download it on the web!

---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------

Otherwise, use rather the new apk, it works fine! ;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
dll files
[Galaxy S 4 i9505 Original Android Development] jotade:
THANKSSSSSS!!!!! I just installed XtreStoLite_ROM_v1.5 as primary and Fusion-v5.0 as second using DualBootPatcher9 Windows Version (Mobile Version NEVER worked for me) Both ROMS are rooted and everything is great so far!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I wouldn't recommend using app sharing on the snapshot builds for now because I'm rewriting the code to make it much more robust. The ramdisk updating actually fails because I disabled it so it won't break anything.

The second issue will also be fixed soon. I'm planning on adding a dialog box that pops up on first boot with a message like: "Do you want to share the same apps as the previously installed ROM?"
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great news, thanks! I'll update the patcher so it recognizes the new files :)

EDIT: Could you tell me which version had an issue?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks!! Glad to hear it's working well :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, that setup won't work. Both ROMs have to support f2fs.

The update fixed an issue where even if every ROM supported f2fs, the secondary may not boot because the patcher changed the f2fs detection code.
[Galaxy S 4 i9505 Original Android Development] illikkalshahid:
where do i get DualBoot Patcher alpha6? i couldn't find it
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There, but well, you will do better to take the latest snapshot, all works with it!

---------- Post added at 11:05 AM ---------- Previous post was at 10:56 AM ----------

Alucard kernels for Android LP5.0 aren't recognized, but if you change custom in preset by /jflte/kernels/AOSP/Alucard-kernel, it works.

Otherwise, there are PA-Gapps (New way to install them), if you set this issue, it will be cool! :good:

If I see others, I'll say you! ;)

---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------

New version of DualBoot Patcher Snapshot 8.0.0 here!

Thanks to [MENTION=4277844]chenxiaolong[/MENTION] !!! ;)

Edit

:

There also was an issue to patch supersu, the 2.16 worked but not the others after.

---------- Post added at 11:49 AM ---------- Previous post was at 11:11 AM ----------

[MENTION=4277844]chenxiaolong[/MENTION]

With the latest apk (r415), IMPOSSIBLE to patch the Alucard kernel!!! :( Even with my way cited above. :crying: I came back to the r409.
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Hi all,

I've manually patched SuperSU 2.37 flashable zip for Secondary ROM(patched the update-binary), and personally tested this on CM12 by AntaresOne. It works perfectly, so feel free to download and use it! Do remember to go and thank Chainfire! Cheers! :) If anyone needs help patching flashable zips with update-binary, feel free to pm me and I'll try my best and help!
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Hi all,

Here's a modded version of DualBootPatcher v8 apk that uses set_metadata instead of set_perm for compatibility with newer recoveries(like the newest version of Philz Touch that doesn't recognise what's set_perm :( ). Do note that this apk is signed differently from official one from [MENTION=4277844]chenxiaolong[/MENTION], so uninstall the official one before installing this!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Finally fixed SuperSU and PA Gapps (latest December releases) in snapshot release 8.0.0.r423.g736a5cf.

The build should be up within 15 minutes (you can check my server's status here: https://jenkins.cxl.epac.to/job/DualBoot_Patcher/261/console)

As usual, unstable snapshot builds are available here: https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html

EDIT: Might be more like half an hour. Time Warner Cable doesn't want to let me upload faster than 30KB/s today for whatever reason lol
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Thanks! ;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
My report for DualBoot Patcher Snapshot 8.0.0 r423

:

Impossible to patch PA Gapps 5.0 (tested with "pa_gapps-modular-full-5.0.1-BETA4-20141218-signed" in automatic)

Still impossible to patch Alucard kernel for LP 5.0 (with the 2 ways)

Sorry!

Can you add this?

My second report for DualBoot Patcher Snapshot 8.0.0 r423

:

Successful to patch PA Gapps 5.0 with in preset:Google_apps/Gapps-paranoidandroid (Installation doesn't work)

About of INSTALLATION FAILURE to PA GApps

:

The reason is written in the PA-Gapps log, maybe I should follow the council, format the system and try again, I'll make to the next build of CM12.

# Begin PA GApps Install Log
--------------------------------------------------------------------------------
ROM Android Version | 5.0.2
ROM ID | cm_jflte-userdebug 5.0.2 LRX22G f6cac5007c test-keys
ROM Version | 12-20141222-OPTIMIZED-jflte
Device Recovery |
Device Type | jfltexx
Device Model |
Device CPU | armeabi-v7a,armeabi
armeabi-v7a,armeabi
getprop Density | 480
default.prop Density | 480
build.prop Density | 480
Display Density Used | 480ppi
Xposed Detected | undetermined
Install Type | Dirty[Data NOT Wiped]
Google Camera Installed¹ | false
Google Keyboard Installed¹ | false
FaceUnlock Compatible | true
Google Camera Compatible | true
Current GApps Version | NON PA GApps Currently Installed (FAILURE)
--------------------------------------------------------------------------------
¹ Previously installed with PA GApps
# End PA GApps Install Log

INSTALLATION FAILURE: PA GApps can only be installed on top of an existing
PA GApps installation. Since you are currently using another GApps package, you
will need to wipe (format) your system partition before installing PA GApps.

# Begin User's gapps-config
*** NOT USED ***
# End User's gapps-config
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Could you also add this please: http://xdaforums.com/showthread.php?t=2953375
[Galaxy S 4 i9505 Original Android Development] amieldl143:
Does this support latest gpe lollipop from Dan 12/17.. Says not compatible.. I patch it and flashed it and it updated my prim. ROM instead.. Thanks
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
where are the unstable zips? (for windows)

Could you add the unstable downloadlinks to 1st post?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There are none, it was said! ;)
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Sorry, I didn't notice it. I usually patch on pc and send the patched zips to my phone with webpcsuite
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For the moment, you should patch it with your phone! ;)
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
For note 3 I was able to successfully patch roms only with the pc version 9 alpha6. When I patch roms with phone it always fails
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
No problem, Got that 16GB SD card for a reason :D

But I've found somewhere months ago something about app sharing over 2 roms. Is there any link to that thread? I can't find it anywhere.