yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's normal if you didn't perform a ramdisk update on your primary ROM. Since the extsd slots are stored as ext4 image files, there's no way to access the build.prop files inside of them without mounting the images. When you do a ramdisk update, your primary ROM will run the same multiboot code as a patched ROM, which includes mounting these image files. Then the app will be able to show the version and build name for all the ROMs :)

EDIT: I don't know if I mentioned this before, but a ramdisk update from your primary ROM is exactly the same as flashing a patched primary ROM. It just avoids the reflashing process.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Very good point. Rebooting from AROMA will cause a bunch of steps to not run. It will certainly result in a broken ROM.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for figuring this out! I had completely forgotten that other parts of the app besides the patcher part also need to access the internal storage. I'll add the Marshmallow permissions request dialog to the remaining parts of the app.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
In most cases on android M, it does require permission to access internal storage , but if it doesn't prompt for permission toggling storage buttons as shown below fur the patcher does the trick!!

Like if app sharing settings don't stick after reboot, this must checked to make sure the patcher does really have rw permissions!!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Yea, I didn't update a ramdisk on primary ROM. Now I will know :)

Thanks for help again :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Haha, he's my older cat :) More pictures:

And some pictures of my younger cat :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Would it make sense for flasher also rely to this string for operation?

The reason why I'm asking is below.

The flasher must know correct partition layout for my device, but if I have custom ROM (Note 5 port) on my Note 4, I have to switch to correct string for my real device each time before flashing like this:

#ro.product.name=nobelltedt

#ro.product.device=noblelte

ro.product.name=trltedt

ro.product.device=trlte

, and then, after flashing, switch it back to Note 5 strings for the ported apps to function correctly.

It would be much easier to have only one ro.patcher.device string to rely on for patcher and in-app flasher....

Just a suggestion.

__________

Edit:

Really nice cats you've got there :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Based on logs that [MENTION=5048731]911-Future_Maker[/MENTION] and [MENTION=5207461]Salman A.[/MENTION] provided, this issue is specific to Mediatek devices. If you guys can find an open-source ROM for the K3 Note (or a similar Mediatek device), it would help tremendously in fixing the issue. Otherwise, I'll have to reverse-engineer the update-binary to figure out what it does, which may take a long time.

Specifically, I need to know how the write_raw_image() function in the updater-script differs from the one for all other devices.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The in-app flasher actually uses ro.patcher.device already for it's own checks. It's usually the ROMs (especially CM-based) that do their own checks based on ro.product.device. I wish I could change ro.product.device temporarily during the flash, but any prop value beginning with "ro." are read-only and cannot be changed.

Thanks :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1928.g2bf214d :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hey, thanks for helping discovering our issue my friend! There are many roms for this phone, but I think Mediatek never ever provided kernel sources or any other resources. that can help the developers. That's why many people doesn't like them and especially the devs. There are a number of pure stock Android 5.1 and 5.1.1 for K3 Note, is it going to be useful for you to extract the update-binary from these roms?

Meanwhile I made some progress dealing with system.new.dat as I managed to correctly extract the containing files using the SystemExtractor tool from this post - thanks to [MENTION=5672788]Anmol9808[/MENTION] and all the other guys involved in the project:

Credits :

[MENTION=5361113]xprit[/MENTION]

[MENTION=4896512]Alexey71[/MENTION]

[MENTION=4842205]BrateloSlava[/MENTION]

Now I "only" need to modify the updater-script adding numerous lines for all the apps. Some help would be great guys. The goal in the end is to be able to "convert" a system.new.dat ROMs into /system/app ROMs. :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm sorry, I'm quite sure I understand the question. Installing the new CM13 ROM (even if patched with a newer version) should not affect your other two ROMs. Your other two ROMs will not be updated to the new multiboot code that drops apk sharing support unless you manually do a ramdisk update.

What partition are you looking to delete? To wipe an extsd slot, you can either do it from the app or delete:

(assuming you installed to extsd-slot-cm13)

[External SD]/multiboot/extsd-slot-cm13/system.img (The large 3GB ext4 image you mentioned)

/cache/multiboot/extsd-slot-cm13

/data/multiboot/extsd-slot-cm13

/sdcard/MultiBoot/extsd-slot-cm13

The only thing created on the external SD is that 3GB ext4 image. That file is not included in the TWRP backups because TWRP does not backup the SD card. As far as downgrading the app, you shouldn't have to do anything special, just make sure the app sharing settings are still enabled.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, looks like I overlooked this because I was compiling with the assert macro disabled. This should be fixed in the master branch now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thankfully, the update-binary file is part of AOSP/CM/etc. (which is open-source) and not something that Mediatek has to provide :) The ROM developers made some changes to it so that it would work on Mediatek devices. I just need to figure out what their changes are.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Thanks for uploading latest r1928, looking forward test added features!!

Marvelous!!

.....

Lol, I thought this features were already in r1928, guess a lil waiting still needed:

Good work!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Not yet haha. There are a lot of new under-the-hood improvements that are not quite stable yet, so it'll still be a little while before this is released :)
[Galaxy S 4 i9505 Original Android Development] Alexey71:
http://xdaforums.com/showpost.php?p=57742855&postcount=40
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Thanks :good:, will test and let you know if there are any issues.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Here's the link to CM 12.1 ROM: https://mega.nz/#!KVVAjTSZ!H_RfpTbcn7qX6GdfVY1wUFosJqNANOUyIwnSFJupLdU - CM 12.1

Thank you so much for taking so much interest in this [emoji4] [emoji5]
[Galaxy S 4 i9505 Original Android Development] pc boy:
Hey all!

Sorry if this is a noob question but since I read the OP like 10 times and did not find what I needed I have to ask for a more clear step-by-step guide.

1.Do I have to patch both roms? Or just the secondary rom?

2. On my primary rom I can not set the kernel,it fails! What to do now?

3.do I have to flash Utilities from recovery?! Or simply installing the app will do the work?
[Galaxy S 4 i9505 Original Android Development] monkteo:
1.just secondary (it's my choice)

2.what rom do you have as primary

3.tha app will do the job (utilities is for some thing else like when you can't change the rom from app you go to recovery flash the utilities an change the rom or delete secondary rom, etc.)
[Galaxy S 4 i9505 Original Android Development] GioBasi:
cm13

[MENTION=4277844]chenxiaolong[/MENTION]

Hi. just trying to install cm13 for s4 mini duos

so when I installed as secondary or as multi 1 or data slot rom in rom menu was not add. only as exsd slot can be add but can't be switched.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Really funny cats :)

Btw what have you been doing these pictures? Quality and details are very good. Do you used Note 4?

And the second question, is it possible to make a backup of /data/multiboot folder? Because I wanted to flash other ROM as primary and wipe /data partition :/ And now I don't know what can I do to save my settings and apps of ROMs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The pictures come straight from my Note 4 without any editing :)

If you want to replace the primary ROM, the easiest way would be to:

Perform a TWRP backup, which will include every ROM

Wipe the primary ROM from either the app or DualBootUtilities

Patch your new primary ROM and flash it

It is possible to backup and restore multibooted ROMs, but there is currently no UI for that. You'd have to do it from the command line.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Samsung's smartphones have good camera, very detailed, but are lagged and have some problems with RAM management. I don't know, what next phone will for me. Samsungs are funny, have amazing screen, good camera and other components. Now we can't use MicroSD cards, this is a disadvantage for me. I would like to have a removable battery too :)

Ok, now I flashed new ROM and wiped /data. Multiboot folder on /data is saved :) /data/media/0 too :D

I needed to flash new ROM because Darklord N5 wasn't updated so long and I had some problems with SMS messages (I haven't received some).

Have a nice day! :)
[Galaxy S 4 i9505 Original Android Development] majid.a505:
hi. no one can help me, i want dualboot for my Galaxy s4 i9500 ja3g… its not find in dualboot patcher, help , thanks,
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Hey mate, it's not on the list coz not yet supported.

Download getlogs.zip from here https://snapshots.noobdev.io flash it in recovery then upload the logs from "internal memory"/logs and ask [MENTION=4277844]chenxiaolong[/MENTION] to add your device, that's the procedure mate
[Galaxy S 4 i9505 Original Android Development] majid.a505:
i did amd upload logs here http://www18.zippyshare.com/v/MFhVEogc/file.htm

please help me [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Can you please help me?

I install the Secondary ROM to external SD (extsd-slot).. So the Patcher creates a system.img in /sdcard2/multiboot /extsd-slot /. But when it fails, I delete this img but I can't regain the space.. So, every time I install a ROM I lose 2.5 GB of my sd card and it stays as system data in DiskUsage.. I had to format my SD the last time when it used 10 GB!!

Can it be the problem of the Patcher??

Because when I delete other files, I get space back but not with Patcher..

It's so annoying

Please help me
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you try deleting from the TWRP file manager to see if it makes a difference?
[Galaxy S 4 i9505 Original Android Development] gaww:
I had to update the patcher app on the primary to switch over to the ExtSD ROM, and then I let it update ramdisk - would that have dropped the sharing? If so, and I restore the Primary ROM, update the duelboot app but don't update ramsisk - will I be able to use it to select ROMs to switch them?
[Galaxy S 4 i9505 Original Android Development] Bradl79:
"If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img."

where is this located in TWRP, i don't see Images anywhere and never had, i don't quite understand this, i am using a Oneplus One on TWRP 2.8.7.0

Nevermind, i had a theme applied, which did not show it
[Galaxy S 4 i9505 Original Android Development] majid.a505:
hi deer i need your help [MENTION=4277844]chenxiaolong[/MENTION]

i want dualboot for my s4 i9500 ja3g and i upload log here , please help me http://www18.zippyshare.com/v/MFhVEogc/file.htm im really need your help, thank you very much im waiting your respond
[Galaxy S 4 i9505 Original Android Development] physwizz:
I found that you lose this space if you wipe ROMs from within the app and you don't lose the space if you wipe from the dual boot utilities zip flashed in twrp.

I had to remove my SD card, copy the files, format the card and reinstall the files to get the space back.

Ever since then,I only use twrp to wipe ROMs.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
One more strange issue with K3 Note dude..:silly: Surprisingly it seems it's working fine on me, I used to flash roms to my extsd-slot a couple of times and when I wiped them the system.img is gone and the 2.5GB space is gained. It's worth to note that I'm sticking with the 1778 build.

There is a small arrow located right next to "Install .zip" text. Tap on it and you will see a drop down menu where you can choose to "Install .img".
[Galaxy S 4 i9505 Original Android Development] Bradl79:
thank u so much, that worked
[Galaxy S 4 i9505 Original Android Development] majid.a505:
no one help me why ???? can't make dualboot for my s4 i9500 ja3g, i send many post here ?
[Galaxy S 4 i9505 Original Android Development] sronweb:
have you tried to enter in recovery and flash the rom again?
[Galaxy S 4 i9505 Original Android Development] majid.a505:
ya bro, it say failed your device ja3g not add to list,, so

they told me to make logs file via getlogs,, so i uploaded it to

http://www18.zippyshare.com/v/MFhVEogc/file.htm

and wait who will help me.. my device galaxy s4 ,, ja3g model
[Galaxy S 4 i9505 Original Android Development] sronweb:
For my understanding with your log should be possible to correct the "patcher" to enable it for your phone model and install a patched rom but if you like to restore your device and you cannot wait (we don't know how long it take, when Chen has time to do it, etc.) you can flash a stock rom via recovery or connecting to pc.

When we play with the phone I recommend to make a backup with the recovery (TWRP i.e.) so if something fail you can restore easily your previous condition.

I have the feeling that if you have flashed a wrong version you should start from clean phone wiping everything.
[Galaxy S 4 i9505 Original Android Development] majid.a505:
bro i know everything about backup and restore, , you can

start patch to enable for my device, and like how many time take to finish???
[Galaxy S 4 i9505 Original Android Development] Blackiisky:
Is it possible to get the dual boot patcher supported for the nexus 6p? I loved using this on my note 4.
[Galaxy S 4 i9505 Original Android Development] gaww:
Thanks. With respect to this last item, he app sharing on primary only shows now it is sharing data. The actual app sharing is gone. I looked at the manage apps list and they only show shared data.

I am assuming hat I will have to downgrade to go back to an earlier ramdisk.

Update - went back, but had to go back into each app again to reset app sharing. Rebooted and its back.
[Galaxy S 4 i9505 Original Android Development] ViAlexSt:
Hi, chenxiaolong!

Can we hope for an appearance in your project to support two more devices: Note 10.1 (p4noterf, Exinos) and Tab 10.1 Pro (picassolte, Qualcomm)? I add the necessary data.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] majid.a505:
hi dear [MENTION=4277844]chenxiaolong[/MENTION] i upload log here . i hope you will help us , to add to our device, galaxy s4 i9500 ja3g ,,,
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes to both questions. You should also be able to downgrade the ramdisk by downgrading the app and then tapping the update ramdisk option 7 times (similar to how Developer Options is enabled in the Android settings).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1932.ga5b4ef1 :)

[MENTION=6091240]majid.a505[/MENTION]: This build also supports ja3g. Please don't repost so many times. I saw your request the first time, but I don't always have time to work on this project.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) Could you flash the GetLogs zip from https://snapshots.noobdev.io and attach the log archive it creates in /sdcard/logs/?

Also, does the Nexus 6p have a way of disabling the forced encryption yet? (And by disabling, I mean having the partition unencrypted instead of encryption with no password.) DualBootPatcher currently doesn't support encryption and probably won't in the foreseeable future because I would have to start providing device-specific builds, which would be far too much work for me.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Since I updated to 5.0 I cannot update the ramdisk, it is stuck in Please Wait for more than 4 hours. I have a LG G3 D855 and stock 5.0 lollipop. Could you take a look? Installing my primary patched rom also fails, here I provide my logs. Thanks
[Galaxy S 4 i9505 Original Android Development] majid.a505:
sorry dear, but i was waiting, and thank you for help. thank you
[Galaxy S 4 i9505 Original Android Development] Blackiisky:
Thanks for the reply and the instructions on how to get you the info you need to help me. Yes to disable forced encryption a custom kernel is needed and available for it.
[Galaxy S 4 i9505 Original Android Development] nds850:
Is it possible to move the secondary ROM from internal storage to the SD card?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It is possible to do this by backing up the secondary ROM and restoring it to an extsd slot. Unfortunately, that has do be done from the terminal right now. I probably won't be able to finish up the interface for backup/restore until mid-December.
[Galaxy S 4 i9505 Original Android Development] nds850:
Thank you. Looking forward to the new functionality :)
[Galaxy S 4 i9505 Original Android Development] Tunasty:
Has anyone tried to patch ViPER4Android Audio mod? I just tried that it didn't work.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
You don't need to flash bro, just install the apk :P

---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------

Thanks man, you're awesome :)
[Galaxy S 4 i9505 Original Android Development] shremi:
Sorry to bump this i am about to try this again tonight any suggestions ????
[Galaxy S 4 i9505 Original Android Development] Tunasty:
Blonde moment ;) :p
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I can't patch loki'd kernels right now, so there's Kangabean can be the secondary ROM only on devices with unlocked bootloaders. Even then, a custom kernel is needed because loki stuff can't be patched yet.
[Galaxy S 4 i9505 Original Android Development] shremi:
Thanks for the answer man .... You really saved me some troubles tonight :good:

So maybe i can flash another GE rom that doesn't have the loked kernel ????

I am going to try unwizzed and report back
[Galaxy S 4 i9505 Original Android Development] RK:
[MENTION=4277844]chenxiaolong[/MENTION], I patched and flashed this:

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

and this:

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

touchwiz 4.3 kernels. Both wont boot past samsung screen! Which 4.3 touchwiz kernel did you get working? Ill just use that one :)

EDIT: Just FYI I am on JFLTEATT.

EDIT: Nevermind.. I had the wrong dualboot.sh. My ROM was not getting installed..
[Galaxy S 4 i9505 Original Android Development] hemmie:
What you can do though have the loki script run either with google_script or run loki_doki after patching the second rom. I can confirm this is working as I'm running two roms on ATT I337 where both kernels need to be loki'd.

As chenxiaolong states you should NOT patch the loki first and then patch with dualbootpatcher until a fix surfaces.

Huge thanks for chenxiaolong and other hard working devs to getting this patcher script up.

---------- Post added at 03:51 PM ---------- Previous post was at 03:37 PM ----------

With my setup after countless number of tries finally did the trick with 2.4.3 android apk patching.

I tried the patcher on computer with Windows x54/ OSX/ Cygwin. does not Work for me. Even ramdisk patcher does not work, I do not think it is dues to my ROM I tried PAC Man offcial and Matallica Roms. they didn't work. I guess python execution on this environments are faulty.

I assume 2.4.3 would work on if you run it in a supported Linux flavor, and understandably so chenxiaolong is releasing these working patches they should work for him.

Other version that had actually made successful dual patching for was 1.8.1. Worked all the time including ramdisk patcher we well. Unfortunately though it did not do a good kernal patching and did boot with 2nd ROM, only upto boot animation screen.

So the winner for me is 2.4.3 Android app not the PC version since I only used Win x64/OSX and Cygwin not good Native flavor like ubuntu/redhat.

Can someone confirm at least 2.0 -2.4.3 works in Windows 7 x64/ The famous error I'm getting is Windows Incorrect Function.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, I should have mentioned that I'm trying to get pre-loki'd kernels to work. The ones that are loki'd during the flashing process are awesome and are already supported, but I've seen many TouchWiz ROMs that don't do that.

I've wrote a program that can find and extract the gzip'ed ramdisk data from a loki image. Now I just need to figure out how to incorporate the new ramdisk.

For the issue on Win7, that's really strange. I test the patcher pretty regularly on my Windows 8 x64 installation and it works just fine. Are you able to open python.exe from the pythonportable folder? Could you also post a screenshot of where you see Windows Incorrect Function? I haven't seen that before.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Dan Rosenberg is a genius. Loki doesn't even touch the actual kernel or ramdisk. It messes with the file structure of boot.img to make aboot execute his code stored at the end of the file.

In other words, I just got unloki'd an AT&T kernel and booted it on my T-Mobile S4. Pre-loki'd ROMs, like Kangabean, will be dual-bootable soon.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
I can't patch Slim_minimal_gapps.4.3.build.2.zip says unsupported?
[Galaxy S 4 i9505 Original Android Development] razorj7:
Hey everyone!

I'm trying to patch the latest version of IOKP (10.29 release) with the latest version of the patcher, but it's not patching. When I run the command via terminal in OS X, I get this:

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 5: ordinal not in range(128)

Tried the app for Android as well, can't patch there either. Any ideas?

Thanks!
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
All in one gapps work fine!
[Galaxy S 4 i9505 Original Android Development] gaww:
I have only been flashing the patched 10.2 ROMs as secondary since I set up duel boot (nice work) , but going to want to update my primary TW ROM.

I believe all I have to do is modify its script so it does not format /system, that flash it with recovery when I have been in the primary ROM. It has Aroma installer - will that cause any issues?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you post the full output? It looks like it's failing to convert some binary data into ascii text

Thanks!