yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Thanks, [MENTION=4277844]chenxiaolong[/MENTION], great work really, it works perfect with Mokee like a primary rom, just an answer to a thread, I never got luck in any device with Miui roms like secondary, I think that it`s normal, probably for the kernel, no?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
5 vibrations after extsd booting, no /system mount points of ROMs.

Greetings!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
extsd-slot ROM not booting..

[MENTION=4277844]chenxiaolong[/MENTION] Can you please look into these logs and see why this isn't booting? I'm attaching the logs and the boot.img of that ROM.

Link of the boot.img: https://drive.google.com/file/d/0B20JfVIKCreWdUdubVVuTlpFQ0k/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] 1981sebas:
Im on g900w8 using gerisrom and also try with xxx 5.7 but i never was able to pass boot . It automaticly go to twrp. Ive added ro.patcher.device=klte into the patched rom. Tried all sd , secondary ... Any idea ?:confused:
[Galaxy S 4 i9505 Original Android Development] mike13ftw:
Hello I just tried the dual boot for xiaomi mi max but it gives me an error. Here is the log if you could take a look:

https://drive.google.com/file/d/0ByuC_SlfPgdEUS1OdUJHQkU3SWc/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=5207461]Salman A.[/MENTION]

The problem is the rom is trying to mount the whole extsd instead of the partition.

mblog: Failed to mount /dev/block/mmcblk1 (ext4) at /raw/extsd: Invalid argument

This is an error Chen explained a few pages back in the thread. Are you sure you're using the latest build? Currently the test r64 build seems to work fine and the extsd roms are booting fine again. Not sure if he merged the changes in the latest snapshots may be that's why it's still not working for you. I was having the same error on K3 Note. Even existing extsd roms were refusing to boot. Installed r64 updated the ramdisk and all is fine. Too bad the corrupted issue is unfixable for extsd slot roms, but at least it's now working on data slot.

r64 build:

https://github.com/chenxiaolong/DualBootPatcher/pull/268?

I suggest to repatch the rom with this build, delete the old system image and reinstall.

[MENTION=5048974]mike13ftw[/MENTION] This is only the patch-file.log, you need to flash the GetLogs.zip from the snapshots page right after the problem occurs.
[Galaxy S 4 i9505 Original Android Development] mike13ftw:
Here it is:

https://drive.google.com/file/d/0ByuC_SlfPgdEY0NqcnNqQThpMzQ/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] awaisa123:
hi there iv got a Samsung galaxy note 4 on original 6.0.1 software and I'm trying dual boot cmremix but it's saying failed to copy /data/.system.img.tmp to/system/multiboot/dual/system how do I fix this
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it looks like recovery still uses the old paths. Can you post the output of the "mount" command and also upload the /fstab.* file? (You'll need a root file manager for that.)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like you are both running into the same issue and it is specific to CM 14/14.1 ROMs. The cache partition is no longer mounted and instead /cache is a symlink to /data/cache.

Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/277. You'll need to repatch and reflash the ROM.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
9.0.0.r63.g9def582 should fix this :)

This might not be fixable easily. The patcher now waits 20 seconds to detect the SD card if booting an extsd-slot. For other slots, the external SD is not mounted by the patcher anymore or else the boot would hang for 20 seconds if there's no SD card inserted. The app currently can't determine the ROM version and build if the patcher doesn't mount the card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5207461]Salman A.[/MENTION] What [MENTION=5048731]911-Future_Maker[/MENTION] said here is correct. I've just merged changes so 9.0.0.r67.g33be691 or newer should work for you.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Working good with r67 (from extsd). I try to test miui8, cm14.0 and cm14.1 from data-slots :)
[Galaxy S 4 i9505 Original Android Development] agueijo:
Perfect…! with r64 I can boot cm 14.1 :)

Thank you very much!

Agu
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Wow! Miui8 and cm14 (on temasek's kernel) work good on data-slot. On cm14 kernel BootUI doesn't show up but booting works. Cm 14.1 don't work because boot.img is too big (11,42MB). I will try on extsd-slots but not now (I need sleep :D).

Good job! :)
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Succeeded to boot on a data slot cm 14.1 by trader (latest build) but only with the test build of the patcher (r64), not with r67. Booting of cm14.1 by christer still fails on all DP builds... Thanks y lot for your hard and brilliant work!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Chen, with r67 TW 6.0.1 works fantastic (data slot) ;)
[Galaxy S 4 i9505 Original Android Development] Mike0505:
[MENTION=4277844]chenxiaolong[/MENTION] , nice tool for dual boot , thank You for development ! :)

Can be added Xiaomi Mi Max Helium to supported devices ?

Thanks.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Flash GetLogs.zip and attach logs ;)
[Galaxy S 4 i9505 Original Android Development] Mike0505:
Will try , and report, Thanks :)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Me too. 5 vibrations and reboot to recovery in r67 but cm14.0 was booted correctly :)
[Galaxy S 4 i9505 Original Android Development] yfriday14:
I installed successfully the MIUI V5 on ext-sd slot for Samsung Galaxy S4 i9505.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Galaxy S7 and TW 6.0 support update:

I got it to boot to the point where I can start debugging things! The patcher is able to mount all the partitions and prepare the system for booting, but, as expected, it chokes as soon as the SELinux policy is loaded.

As far as the SELinux policy patching goes, I've just finished adding support for stripping out auditdeny/dontaudit rules for easier debugging. Now, all that's left is figuring out all the rules that need to be added to make the patcher work.

Btw, /proc/kmsg on the S7 is amazing. A full 2MB log that contains the kernel messages for the last boot and as many previous boots that can fit. This is so much better than most devices I've seen, many of which don't even have a way of seeing the last kernel log (ahem.... Note 3).
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
:laugh: :laugh: :laugh:

Because Note 3 is unique :D

Btw I have a problem with my ArayaMod 5.0 ROM:

[V] Finished cleanup
I:Legacy property environment disabled.
I: operation_start: 'Flashing'
Installing '/external_sd/Rom/N9005XXUGBOJ6_AryaMod_V8.1_data-slot-arayamod81.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: mmap(1815875505, R, PRIVATE, 34, 0) failed: Out of memory
sysutil: Map of '/external_sd/Rom/N9005XXUGBOJ6_AryaMod_V8.1_data-slot-arayamod81.zip' failed
E:Failed to sysMapFile '/external_sd/Rom/N9005XXUGBOJ6_AryaMod_V8.1_data-slot-arayamod81.zip'
Error flashing zip '/external_sd/Rom/N9005XXUGBOJ6_AryaMod_V8.1_data-slot-arayamod81.zip'
Updating partition details...
I: Data backup size is 13002MB, free: 4442MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I: operation_end - status=1
I:Set overlay: ''
Screenshot was saved to /external_sd/Pictures/Screenshots/Screenshot_2016-11-03-04-06-46.png
I:Set page: 'clear_vars'
I:Set page: 'install'

Do you know where is a problem? Other ROMs are flashed successfully :)
[Galaxy S 4 i9505 Original Android Development] buddhatrip:
Now I can access developer option cm14 patched with dualboot patcher release version 67 . Thanks
[Galaxy S 4 i9505 Original Android Development] pc boy:
Can anyone shed some light on this?

Does the patcher support tw 6.0..1 roms now? As reported here it supports but chen says he is workin on it:eek:
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
He worked on it ;) Now from version r67 Marshmallow TW ROMs works very well :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
I just tried to flash 6.0.1 on extSD using r67 and it failed.

Logs attached. Thanks for the great work Chen.
[Galaxy S 4 i9505 Original Android Development] fmotta:
Same here: failed to extract busybox wrapper

(but I'm on S7 ??)
[Galaxy S 4 i9505 Original Android Development] yfriday14:
It seems there is an out of memory problem.

Is it enough space on external sdcard partition?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Nope :p,

I flashed to data slot from extsd so I think, this is impossible :p
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Anyway, your log says, out of memory.

If you flashed to /data then it is the internal memory.

How much free space do you have on the internal & the external sdcard?
[Galaxy S 4 i9505 Original Android Development] robcore:
Hey man, hope you're well!

Fyi I fixed my kernel for gs4 universality, and it includes the workarounds I've made for your patcher! Feel free to try it out if you ever have the spare time...lol given your projects' rapid commit history, I can't understand how that would be possible...but I digress...

Anyway also heads up I just picked up a used note3(my DREAM device!) and have started the long process of backend upstreaming, so when the time comes I will try and build something that makes retrieving the logs (ahem, no last_kmsg is a crime) much less of a headache. : ) take care my friend!
[Galaxy S 4 i9505 Original Android Development] chavdar:
You are trying to patch an aroma ROM - I don't thin the will work... The aroma script is failing
[Galaxy S 4 i9505 Original Android Development] ShAdOw NiNjA:
I don't understand why it won't work though. It is listed as one of the ROM's supported. Any ideas?
[Galaxy S 4 i9505 Original Android Development] gaww:
I think the OP is a bit dated with respect to supported ROMs and kernels. Would help it it were broken into 4.3 and 4.4.

Separate issue - 1111 PA-GOOGLE APPS patched and worked fine. Tried to patch 1119 version, and errors intermediately (using 3.0 app).
[Galaxy S 4 i9505 Original Android Development] ShAdOw NiNjA:
Is it possible to boot a 4.3 rom and a 4.4 rom? PacMan is my 4.3, gummy is my 4.4. Not sure how to flash the Gapps because the file isn't supported by the patcher.
[Galaxy S 4 i9505 Original Android Development] VillainDivine:
Hey guys,

I am having a problem patching the 11-18 IOKP build for use as my second ROM on my S4. . Whenever I drag the IOKP .rar file to the "patch-file" batch file to patch it, it gives me an error. When the batch file is extracting the ramdisk, it says " ---ERROR BEGINS--" Ive included a screenshot of the entire error its giving me. Ive even tried to manually patch with no luck. Any help will be greatly appreciated. Thanks!
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes. Primary ROM, kernel,etc. do not need to be patched.

I patched Gummy 4.4 and PA 1111 4.4 Gapps with android 3.0 patcher as secondary ROM - worked fine (note - could not patch PA 1119 Gapps for some reason). I did not use new Gummy Gapps (may not be patch compatible). I did it before latest Gummy releases - you may loose their reverted 4.3 camera with PA Gapps but they work.

Just follow OP installation instructions carefully.

---------- Post added at 01:52 AM ---------- Previous post was at 01:47 AM ----------

Try it using Android patcher app 3.0 - as Windows patcher has issues.
[Galaxy S 4 i9505 Original Android Development] VillainDivine:
Thanks man Ill give it a shot

BTW, when you say android patcher app 3.0, do you mean the android app chen made?
[Galaxy S 4 i9505 Original Android Development] ShAdOw NiNjA:
Yeah the patcher app. The 3.0 beta can be found on page 97
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes - but I see you got it.
[Galaxy S 4 i9505 Original Android Development] VillainDivine:
No luck man. I am still getting the same error pertaining to the ramdisk.

EDIT- Nevermind, I mistakenly used 2.5.3 instead of 3.0. Thanks a lot guys!!!!
[Galaxy S 4 i9505 Original Android Development] gaww:
Great - enjoy.
[Galaxy S 4 i9505 Original Android Development] respider:
I've tried patching PA Gapps 1111 and it fails extracting (?) boot.img

any ideas?

I cant patch any Gapps :(
[Galaxy S 4 i9505 Original Android Development] ShAdOw NiNjA:
I did get PA Gapps 1114 to patch for me yesterday. If you want the regular or patched file let me know and I can link you to my dropbox.
[Galaxy S 4 i9505 Original Android Development] respider:
I've managed to patch, thank you! I was trying mini pa gapps. The full was successfully patched. Thanks!
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
I have touchwiz 4.3 stock as primary.

And dual boot with kitkat by gummy as secondary ROM.

I tried to activate the ART mode, and I think it bootloop.

Anyone had this?
[Galaxy S 4 i9505 Original Android Development] Sushibagel:
ART is super unstable and can take a long time to boot. Most devs don't support ART issues. I would just revert and not use ART. I'm running Gummy as a daily driver on my secondary with no issues.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Can someone hook me up with 4.4 Gapps patched that I can use with GummyBear?
[Galaxy S 4 i9505 Original Android Development] Sushibagel:
You should be able to patch the full PA gapps

http://xdaforums.com/showthread.php?t=2397942
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If something is not patching, I recommend trying my 3.0 beta on page 97. It is mostly stable, but there are a couple things I want to fix before pushing the full release. Version 2.5.3 is quite dated and does not work with many newer ROMs.
[Galaxy S 4 i9505 Original Android Development] gaww:
Patched earlier one but 1119 errors - usin3.0 beta
[Galaxy S 4 i9505 Original Android Development] pc boy:
Is there any way to run utilities on twrp recovery?

Actually I was wondering if it is possible to wipe cache or dalvik/ART of secondary roms in twrp recovery. If it is possible through twrp without using utilities, please let me know:)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I have ~5GB on /data and /external_sd. This looks like a memory problem but other ROMs are flashed correctly so I think it isn't a memory problem.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Do you you have 5Gb free on internal and 5Gb free on external?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
You can use DualBootUtilities.zip. Flash this from recovery, you can switch between ROMs and wipe other ROMs.

---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------

Yeah, so I think it isn't memory problem.
[Galaxy S 4 i9505 Original Android Development] pc boy:
Dude, I know what utilities.zip does, but twrp does not support aroma installer and whenever I try to install utilities it reboots, so simply flashing utilities is not an option on twrp recovery.

Any Ideas?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
What version of TWRP do you use?
[Galaxy S 4 i9505 Original Android Development] pc boy:
I'm on 3.0.2-1
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
So flash 2.8.7 and use DualBootUtilities. TWRP 3 has problems with Aroma.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
I use the same, and works without problem.
[Galaxy S 4 i9505 Original Android Development] pc boy:
:eek::confused: So the problem should be different devices! Since I'm using SM-G900fd and you're on GT-I9505

---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------

Will test and report back.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I had this same issue.
[Galaxy S 4 i9505 Original Android Development] pc boy:
Dude you were right about working aroma on v2.8.7 of twrp, but in my case, mounting usb storage does not work on this version.:(

Don know what to do:rolleyes:
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I had this same situation. TWRP 3 has a few adventages but it doesn't support Aroma. More important for me is the ability to use Aroma. Your phone, your choice ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wow. It's running out of RAM. I've never seen that happen before. Can you link to the ROM so I can take a look?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm actively working on it, but it is not ready yet :) Custom ROMs that explicitly disable Samsung's security features may work, but the majority of the TW 6.0 ROMs will not.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll definitely do so!

You would be doing me (and Note 3 users) a huge favor by implementing a way to retrieve the logs from the last boot :)
[Galaxy S 4 i9505 Original Android Development] robcore:
On it!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
ROM is here http://xdaforums.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920 .

I used version 8.1 but 9.0 is available. I had a version 5.x of this ROM and this worked well. I'm downloading now version 9.0 :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
Thanks Chen. The ROM I was flashing was a LP 6.0.1

It flashed but didn't boot.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
I've been running AryaMod v9.0 at data-slot-1 without a glitch here in my N9005.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I will test v9.0 now. Maybe v8.1 had error.

#EDIT: Ok, ArayaMod v9.0 flashed without problems :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
And my S7 is dual booting stock unrooted TW 6.0! Now to turn this garbage pile of hacks to something good...
[Galaxy S 4 i9505 Original Android Development] robcore:
I am officially stealing and using that line as my personal mantra for all of my projects going forward :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
Ever since I started using TWRP 3 the backups of my primary have stopped working. They no longer restore successfully.

Going back to 2.8.7
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
TWRP 3 has new design, supports more languages, is a little smoother than TWRP 2.8.7 but it contains errors, which exclude the use (at least for me).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've managed to multiboot my S7 Edge (TW 6.0) in a non-hackish way with a stock rooted ROM. The next step is to fix booting a stock unrooted ROM without ugly hacks and ensure SELinux does not prevent the app or in-app flashing from working. With luck, I might be able to make a test build with these changes this weekend :)
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Good to hear that. Man you are simply awesome! Meanwhile i managed on my a500f to make a permissive kernel, also managed to flash touchwiz 6 as secondary. Works flawless!! Thank you for your kindness! Cheers!
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
I'm sorry if it's been asked before but is there's any chance of fixing pin/pattern errors while booting between roms without every time deleting locksetting files from data/android in twrp
[Galaxy S 4 i9505 Original Android Development] dedq:
Maybe someone asked this question already before and in that case I am sorry for repeating it.I just don't have time to read 1000+ pages (I have to study).

Is there a way to multiboot stock Touchwiz (i9505,International LTE ROM) and CM 13 (or 14 even better).
[Galaxy S 4 i9505 Original Android Development] Guroff1974:
Many thanks! Added a line "ro.patcher.device=zerolte" and everything normally earned. Now it is possible to put the second and third ROM. 128Gb to internal memory allow.

I still have a problem with start of the second ROM on Galaxy Note 10.1. I will try to describe a problem and to put log.
[Galaxy S 4 i9505 Original Android Development] Guroff1974:
Hello! Please help to solve a problem. I have a tablet Samsung Galaxy Note 10.1 N8000 ro.product.device=p4noterf. It is impossible to stitch a custom kernel to data-slot-1. This kernel without patching is established on Primary Rom and works. To check on other kernels there is no opportunity, this only custom kernel for N8000. Patch a kernel on tablet v9.0.0 r69.
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
I installed now miui custom rom Angels & Daemons in secondary rom, I did it in secondary slot, thanks, just no sucess with data share, the shared app don`t run in miui and in the other rom simply data is missing.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
You have to install the app on both roms, then enable the data sharing.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
boot.img size is too large after patch. You have only 8MB on /boot partition.

/boot | /dev/block/mmcblk0p5 | Size: 8MB

Before patch boot.img has 7.83MB and after 8.47MB.

Flashing Boeffla-Kernel 3.2-Samsung-n8000
minzip: Error writing 32768 bytes from zip file from 0xbeeb4c44: No space left on device

---------- Post added at 02:28 AM ---------- Previous post was at 02:24 AM ----------

Your S4 is also supporetd. If you have stock TW ROM flashable via recovery, you can try to boot.

---------- Post added at 02:33 AM ---------- Previous post was at 02:28 AM ----------

Maybe this is a problem with your ROM? I think, it isn't the fault of DBP app.
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Yes, I installed apps in both rom then share from primary, reboot to primary, then reboot miui secondary, share app from miui, then reboot to miui to take effects, I ever did of this manner but no luck
[Galaxy S 4 i9505 Original Android Development] dedq:
Your S4 is also supporetd. If you have stock TW ROM flashable via recovery, you can try to boot.

So You are basically telling me that there is a way to find stock i9505 ROM as zip file and that I could manage to have both stock TW and CM 14?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The new S7 Flat/Edge and TW 6.0 changes are working extremely well! Just have a few things left to test: https://github.com/chenxiaolong/DualBootPatcher/issues/90 I should be able to make a test build some time this week.

There are no drawbacks so far from what I can tell. Everything in TW 6.0 works the same as other ROMs (eg. no need for root in patched ROMs, in-app flashing works, backup/restore works).
[Galaxy S 4 i9505 Original Android Development] Andycar:
I just stepped by here to say Thank you very much!

Finally I'm able to boot TW / AOSP (both 6.0.1) on my Note 4 trlte without any problems. Nice!
[Galaxy S 4 i9505 Original Android Development] jjcaraso21:
Sony Xperia Z5 Premium E6853 Satsuki

Hi Id like to inquire if its possible to add my device on the patcher - Sony Xperia Z5 Premium E6853 Satsuki? Many thanks...
[Galaxy S 4 i9505 Original Android Development] dave7802:
Waiting patiently

If you want any tests carrying out, let me know.

Thanks
[Galaxy S 4 i9505 Original Android Development] welder73:
One question guys:

What would happen if I flash the second rom,boot to Twrp and then from there flash something,another rom,xposed...

Where would that go?To the second rom?

Or my primary (stock) rom will be messed up?

Thank you in advance :)
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
To whichever rom or slot that you patch it for.
[Galaxy S 4 i9505 Original Android Development] welder73:
So,if I patch the rom for the second slot and flash it with Twrp,my stock will be intact?

Great,that's what I wanted to hear!

Tnx man :svetius:
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
No u can only flash via dualboot patcher aap don't flash from twrp it'll brick ur device
[Galaxy S 4 i9505 Original Android Development] kopitalk:
I see that you're confused. Read OP again especially the How-to portion.