yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] monkteo:
I discover something related to patching a TW on secondary, (Data-slot, SD)

It's not working if it has it's Aroma system included for installation, if it's simple ROM TW, it WORKS.
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi [MENTION=4277844]chenxiaolong[/MENTION] ,

I found in your sources in Git (libmbp/patcherconfig.cpp line #338 in latest commit) that my model is already supported as a variant of the serranods, what it's just fine!! The only thing I noticed is that one of the 3g variant's codenames is missed: "serrano3gxx" . It's not a problem at all, because my model is correctly being recognized as serranods, tho that was what made me mistakenly ask you for adding the 3gxx version 'cause nothing what I tried using your tool worked for me yet, but watching the codeflow I see that this is not the actual problem, so I will just keep trying to make dualboot work in my phone (e.g changing the primary rom, updating the bootloader, etc) .

So just ignore my original petition.

Best regards and thank you again for this fantastic and unique piece of software!!!

//
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Backup and restore is getting close to being usable! By the end of this week, it should be possible to backup and restore a ROM via adb from recovery. :)

I spent nearly 10 hours today trying to figure out why libarchive had trouble converting an already UTF-8-encoded path to UTF-8.

[W] /data/media/0/Piano/童年的回憶.pdf: Can't translate pathname '/data/media/0/Piano/童年的回憶.pdf' to UTF-8

Well, it turns out the Android NDK has very broken (read: non-existent) locale support, which was tripping up libarchive's string conversion functions. So, for any developers using libarchive on Android, you'll need to force the default locale to be UTF-8 because setlocale() is completely useless: https://github.com/chenxiaolong/Dua...s-the-default-charset-on-Android-since-.patch
[Galaxy S 4 i9505 Original Android Development] gaww:
10 hours = you are a trooper!
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi,

My problem is that, after flashing the rom, I always boot in recovery. With Dualboot utilities, I manage to switch back to my primary rom and boot on it. If I try to switch one more time to the dual rom, I boot one more time in recovery !

I've tried to patch another rom (AOSP from JCDTeam) in ext-sd (with PC Tool), after installing it the pb is exactly the same.

Thanks for any help !
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
i reaLLy don't know how to fix that. there is something wrong with the scripts on your dualboot. do you have some screenshots when u flashed the patched rom or logs? logs are needed for debugging purposes. http://snapshots.noobdev.io
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I can not boot resurrection remix unless I don't flash anything with it.

What is the problem?
[Galaxy S 4 i9505 Original Android Development] Darkwing_X:
I have ressurection remix 5.5.8 running in Multislot 1.
[Galaxy S 4 i9505 Original Android Development] chavdar:
Hi [MENTION=4277844]chenxiaolong[/MENTION], could you please add support for the international Samsung Galaxy S3? I think it is called m0. I am attaching a log from GetLogs.

https://www.dropbox.com/s/cw51lelsh5urgl0/i9300-20151021.212046.tar?dl=0

I would like to request support for 1 more device - picassowifi ( galaxy tab pro 10.1). I already saw that mondrianwifi is supported.

https://www.dropbox.com/s/239yq1b7tgdwzu6/picssowifi-20151021.202223.tar?dl=0

Thank you in advance! And you have done a really great job.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Here I am again, so I tried with another SD (Samsung evo 16gb formatted in FAT) and I could flash in app on it and boot. I formatted my first Samsung evo 128gb which was in exFAT to ext4, but it did not work either. So is there a problem with the SD size ? What partition types does the dual boot patcher handle ? Thank you
[Galaxy S 4 i9505 Original Android Development] ade_k012:
Hi Chen, i'm a big fan of your dual boot patcher

currently i have a problem to patched MIUI 7 for i9505 (Rainbow) TW based as Multiboot

it said "Failed to Patch file"

attached is a log file

hopefully you may have time to check it..

thanks
[Galaxy S 4 i9505 Original Android Development] physwizz:
Do you know of one for the Samsung Galaxy Tab S t700?
[Galaxy S 4 i9505 Original Android Development] emelsk:
Do both ROMs need to be rooted for dualboot to work?

Sorry if I'm asking obvious, but do both ROMs need to be rooted for dualboot to work? I understand I need to root primary ROM at least temporarily to set dualboot up, but even after searching through the entire thread, I'm not clear whether or not both ROMs have to be rooted at all times.

What I'm looking for is a dualboot solution with one ROM stock (say it's primary) and the other one can be rooted if needed. The reason for one ROM w/o any root is corporate rules - the device has to be under MDM management and that will refuse to run/install anything corporate (let's say e-mail) as soon as root is detected. MDM (Maas360 in this case) is quite good at detecting root, so any attempts to somehow hide root itself are not viable.

TIA for any help on this.
[Galaxy S 4 i9505 Original Android Development] gaww:
The phone needs to be rooted in order to flash any ROMs with a non-stock recovery (TWRP, etc.). If you later ODIN a stock ROM, you loose root.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Sorry Man , right I am at work and I have S5, but if you read in the treat of the TW rom you will notice who have Aroma.

good luck
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
I don't think so boot roms need be rooted. only the primary needs be rooted for flashing purposes.

I used a deodexed stock on my primary and cm12.1 nightly for my secondary and last time I checked my secondary is not rooted.
[Galaxy S 4 i9505 Original Android Development] :
I booted for the first time into the secondary and set it up. but no matter what I do I can't bootback. I select primary as default and when I reboot, it boots back into secondary. And I think the app has a problem. I select primary and it tells Mr that it was selected. I closed the app and reopened it and it switched back to secondary
[Galaxy S 4 i9505 Original Android Development] chavdar:
Have you saved the primary kernel when you were in primary? If not then you have overwritten the primary kernel when you booted in secondary and now you can't boot back to primary because the kernel is missing
[Galaxy S 4 i9505 Original Android Development] :
I see primary, when I boot into recovery I have the original system dir and inside is multiboot and inside that the secondary

---------- Post added at 02:17 PM ---------- Previous post was at 02:04 PM ----------

I set to primary and refresh the page... It says secondary again
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=244141]Chen[/MENTION] I just got the note 3 and I was wondering if you could make one for me to test :P

Sent from my SM-N900T
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Hey Chen, I was hoping you could add support for IOKP? I'd do it manually but we update it A LOT so it'd be a pain to patch manually every time lol http://xdaforums.com/showthread.php?t=2295547
[Galaxy S 4 i9505 Original Android Development] nicholi2789:
Has anyone been able to get any PACman roms to boot as secondary? I'm running Beans 7 as my primary and I followed the instructions and still can't get PAC to boot at all. Tried the last three latest nightlies. I also tried Liquid 2.1 and I can't get that to boot either. What am I doing wrong? Here's what I do: install the dual boot switcher app. Set primary kernel, then reboot. Then on my desktop I drag the rom and Gapps I wanna flash as secondary onto the patcher. When It's done I transfer the patched zips to my sd card and boot into recovery and flash them. Then reboot. Every time I do it, I just get stuck on the Samsung boot screen. It says I have over 600 mbs of free space in /system BEFORE I install the secondary rom so I don't think space is an issue..
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Hey chenxiaolong, I have tried dual booting Kangabean and it does not start patching. It gives me a whole list of errors while I try to patch it. I am using the latest version of Kangabean, and version 2.1 (latest so far) of the patcher. Do you know why this would be so?

And thanks! I'm working on patching some other ROMS. Thanks for helping me understand how to do it! :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
EDIT: Please download version 2.4. I've switched to using GNU patch on Android, which fixes the patching issues

Version 2.3 is released. This version (and 2.1 and 2.0) include quite a few changes :)

Ramdisks are now patched directly. Thanks to RedHat with their Cygwin libraries, this is now possible on Windows, not just Unix based systems.

Framework for adding support for devices other than the Galaxy S4 (not complete yet)

An easy-to-use patch script for generating patches from your edited files (see OP for more details)

And.....................what you've all been waiting for................patching files directly from Android :D
[Galaxy S 4 i9505 Original Android Development] Tunasty:
OMG! you just made my dayyyy!! Thanks a lot for your goodies bro!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're welcome :D It's not perfect yet because it uses busybox's patch tool instead of the standard Linux GNU patch tool. I'll fix that tomorrow and then all supported ROMs should work without problems :)

EDIT: Version 2.4 which fixes the issue is released.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Tried new version tried to patch slimbean weekly for S4 Verizon and get a ton of errors.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you patching on Android or Windows/Linux? And are you on version 2.3 or 2.4?

EDIT: Loki was causing the issues. It's fixed in version 2.4.1 :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=4277844]chenxiaolong[/MENTION]

...erm..just...wow! :)

I wanted to give a try to Android dual boot patcher 2.4.1 apk with SuperSu zip (just to make a quick test) but it fails.

[Tested on Touchwiz primary rom with SuperSu zip on sdcard and sdext but same log it seems]

Here's SuperSu zip on sdext fail log:

https://db.tt/NloshTTJ

http://pastebin.com/h6hgXA0s

2.4.1.tar.xz is well installed under data/data/com.git.../cache

I just woke up, saw your update post and jump on it lol, maybe I'm just missing something obvious ;)

Edit: fail on miui also but went fine for others users with Slim and Carbon.

Edit again: went fine for someone else with SuperSu zip so it's probably me but I can't see why..
[Galaxy S 4 i9505 Original Android Development] Mr_Q:
Can you please support the following GE rom from janjan?

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

20/10/2013 - Android 4.3 v.2.3

I tried patching it from Windows using Patcher 2.4.1 but it states "Unsupported zip".

Thank you in advance!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm... does it work if you put the file on the internal SD? My external SD card died so I didn't get a chance to test that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does /data/data/com.github.chenxiaolong.dualbootpatcher/files/DualBootPatcherAndroid-2.4.1 exist on your phone? If not, does /system/bin/tar exist? I'm thinking maybe the files aren't being extracted.
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
Task's AOKP failed to patch on app

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

also getting error on latest gapps from Task using v2.4.1 of patcher on mac

MacBook-Air:patcher munchy$ ./patch-file.sh gapps-jb(4.3)-10.7.2013.zip

-bash: syntax error near unexpected token `('
[Galaxy S 4 i9505 Original Android Development] RK:
[MENTION=4277844]chenxiaolong[/MENTION], I tried manually patching this ROM:

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

Did not boot past boot animation. I have tried other TouchWiz 4.3 (MJ5 base) ROMs and kernels too. For example, the KT touchwiz 4.3 kernel and the ausdim touchwiz 4.3 kernel and they do not boot past the boot animation as well..

There might be something different between 4.2 and 4.3 touchwiz ramdisks.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Sweet I can now patch slimrom very easily. Questions any idea why I can't patch Ktoonz kernel it's the only thing stopping me from perfection :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Yeah I meant sdcard and sdext, I tested on both with same result on both Touchwiz primary and miui secondary rom.

I have DualBootPatcherAndroid-2.4.1.tar.xz but under /data/data/com.github.chenxiaolong.dualbootpatcher/cache/

Reinstalled the app many times.

/system/bin/tar is present yep.

I could only test SuperSu and miuiandroid zip for now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the report. The error you're getting on your Mac is from the parentheses in the filename. They mean something in the command line. Try this instead:

./patch-file.sh "gapps-jb(4.3)-10.7.2013.zip"

The quotes will tell the command line that there is nothing special about the filename you typed.

I'll check the patch once I get home to make sure it's not broken.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm I don't think the ramdisk would cause that but if touchwiz 4.3 has selinux in enforcing mode, that would definitely cause issues (incorrect file contexts leading to broken selinux rules). I'll see what I can do about that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome :)

Could you post the filename and the error? Ktoonsez aosp 4.3 should work without issues.
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
There's an app called Swap Roms .. see if it helps
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
What chavdar wrote is your primary ROM is still there but not the boot.img because you have not set the kernel of the primary in patcher app when you were in your primary ROM before booting to secondary.

You just have to flash the boot.img of your primary ROM to get it to start, then set your primary kernel in patcher app
[Galaxy S 4 i9505 Original Android Development] gaww:
This is the correct response - I have done this a few times when I forgot (senior moments) to set primary.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi [MENTION=4277844]chenxiaolong[/MENTION]Thank you.

I have installed 3 roms on my S5.

One on ExtSD and it does very well.

Could you add support for Samsung Galaxy S3 mini GT-I8190N golden ?

Thanks for your great patcher
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Hello, how to install rom on ext sd? I have s4 mini and every time I get error not enough space for creating system.img / I have phiz touch recovery and extsd_slot patched aicp rom on sdcard and have installed blisspop as primery.

haven't problem when installing as secondary and data slot but it's always installed on internal memory

---------- Post added at 09:03 PM ---------- Previous post was at 09:03 PM ----------

Hello, how to install rom on ext sd? I have s4 mini and every time I get error not enough space fro creating system.img / I have philz touch recovery and ext sd slot patched aicp rom on sd card and have installed blisspop as primary
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Please.. Help

Just tries Optimized cm 12.1, and it works perfectly, I suppose because it has a proprietary kernel, it doesn't use the original cm's one
[Galaxy S 4 i9505 Original Android Development] mabuan:
Hi [MENTION=4277844]chenxiaolong[/MENTION],

Thank for you hard work! Hope next version support Note 4 N910S/L/K bootloader 5.1.1. At this time, only bootloader 5.0 or lower can't have dualboot, bootloader 5.1.1 will have error "kernel is not seandroid enforcing", boot loop and can't start.

Thanks & best regards!
[Galaxy S 4 i9505 Original Android Development] Y3dx:
Please add support for the s6 G920F

Thank a lot
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
With hlte and stock rom (4.4.x) in data-slot-stock i'm not able to use internal sd card without root permission. How can i (or you) fix this?
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
if I am not mistaken. you need root access for this app to flash the patched zip. so root your phone and try again.
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
maybe you really don't have enough space. when flashing the patched rom for extsd it will need aleast 2.5gB on external storage for the system.img. and I think you also need at least the same space available on your internal storage upon booting the device.
[Galaxy S 4 i9505 Original Android Development] droidblitz:
Guys im running ManuProN5 Note5 port rom to my i9505

and i would like to dual boot sabemod cm12.1 or any cm12.1 rom.

Will this dualboot thing will work with the said rom's above?

Thanks.

First time to do this.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Yes 100% !
[Galaxy S 4 i9505 Original Android Development] droidblitz:
should i patch gapps.zip? or just the rom that i will be installing as secondary rom?
[Galaxy S 4 i9505 Original Android Development] Darkwing_X:
You need to patch also the gapps
[Galaxy S 4 i9505 Original Android Development] droidblitz:
thanks
[Galaxy S 4 i9505 Original Android Development] droidblitz:
Failed.

Sent from my SM-N920F
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
is that rom compatible with your device? since that rom is jflte and your device is noblelte. may be it is not compatible. or may be your device is not supported yet. you have to ask the developer to support your device.
[Galaxy S 4 i9505 Original Android Development] droidblitz:
i am using note5 port rom to my i9505

and im trying to dual boot sabermod cm12..1

---------- Post added at 07:24 AM ---------- Previous post was at 07:18 AM ----------

noblelte is not supported :/
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
did you download the lastest dualboot patcher app? from here https://snapshots.noobdev.io/

you can always ask for support. but right now it seems [MENTION=4277844]chenxiaolong[/MENTION] is too busy. as the last support he added is for nobleltespr. im not sure if that is compatible to your device.

you just have to download the GetLogs-20150919.zip from the same site above. and follow the instructions on how to get logs.

then ask for support and wait for the dev.
[Galaxy S 4 i9505 Original Android Development] droidblitz:
Okay thank you :D
[Galaxy S 4 i9505 Original Android Development] Andycar:
You are running N5 port with the changed build.prop

If you will manually change you product line from noblte back to jfltexx (I think). then it will flash normally.

Cheers!
[Galaxy S 4 i9505 Original Android Development] droidblitz:
When patching the zip file of the rom i want to install as secondary, should i choose note 5 as my device since i am running a note 5 port?

Or should i pick s4?

Sent from my SM-N920F
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
can you build it for him? I want to volunteer but I don't know how to do that.

it wont work either.

ask [MENTION=1111850]Andycar[/MENTION] if he can help you in what he suggested.
[Galaxy S 4 i9505 Original Android Development] Andycar:
No, you should still choose your physical device (s4), since it corresponds to the real partition enumeration scheme.

Also, the product line in your build prop should correspond to your real device, otherwise the flashing will fail.
[Galaxy S 4 i9505 Original Android Development] droidblitz:
Okay thanks again.

Noblelte is in my buildprop

Sent from my SM-N920F
[Galaxy S 4 i9505 Original Android Development] monkteo:
Yes you need an explorer for root device

than go to system-build.prop(open with text editor)and modify (ro.product.device=noblelte to jfltexx ) save and reboot
[Galaxy S 4 i9505 Original Android Development] droidblitz:
This is what i need to change right?

Sent from my SM-N920F
[Galaxy S 4 i9505 Original Android Development] monkteo:
Yep !:good:
[Galaxy S 4 i9505 Original Android Development] droidblitz:
there it worked just flash the 2ndary rom :D

thanks guys.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
With hlte and cm11 (latest official snapshot) in data-slot-cm11 the phone stucks in kernel logo Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Help

How install on ext sd ?

any tutorial link?

i9192
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
I see this happens when you do not have extra space in you internal storage. during boot the system.img that dual boot patcher created will be expanded somewhere in your internal storage. thus you need at least 2.5gb in your external storage just for your secondary to boot. I suggest to install your secondary on your extsd and it will leave you more internal storage space. you can switch back to your primary rom by using the dualboot utilities or just restore the boot.img of your primary rom using custom recovery. then set the kernel after successfully booting.

your logs says you do not have enough space.

I will assume that you have enough extsd storage cause you need 2.5gb available space in your extsd.

I can only think of two possible problems here. first I think it is because of the filesystem format. format your sd card to ext4 or fat(im not sure about this). the second problem that cause unrecognition of available space in your ext sd may be it is too large. I read somewhere in this thread that 128gb extsd is not recognize by the app(atleast for now).
[Galaxy S 4 i9505 Original Android Development] GioBasi:
Hi thanks for replay.

I have empty 8gb sandisk class 4

I used mini tool for formatting all as primary.

first partition to 2.5 gb as fat32

second partition 2gb ext4,

third partition 2gb ext4

and 4 partition 780 mb ext4

then patching CM rom as extsd-slot, ID-2.

then copying to internal storage.

reboot to recovery philz touch install from sdcard and error.

I haven't problem when installing on internal storage as secondary or data-slot

but I have just 1.5 gb free memory on internal storage.

it's first time trying to install on extsd, so maybe I missed something important...
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
Mind if I ask why there are so many partitions on your ext-sd? make atleast one partition greater than 2.5gb or 3gb with ext4 or fat32. because upon flashing the app will create a 2.5gb system.img on your extsd. your really don't need to go to recovery to flash the patched rom. you can always flash from your primary rom using the dual boot patcher app. but I will not mind if that is your preference. just saying. and btw your 1.5gb space on your internal memory might make your secondary not booting. as I said above that during boot the secondary rom will expand on your internal storage. so try to clear up some space if you are stuck on boot logo.

edit: try other filesystem format. I think you don't need 2.5gb or above because upon seeing your logs it only need 1.75gb. so it is maybe it is the filesystem or the partitions. I suggest that try to reformat your sd card only one partition. then patch the rom again and flash it. then repartition your sd card after you successfully flashed and booted your secondary.