yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Thanks for all your help so far!

So, I can confirm that the data slots are working with the v.2361 of DBP and they can see and interact with /storage/*** without any major issues. My primary slot which is running on Stock MM6.0 (and not a ROM of MM6.0) is where the problem still exists. While it can see the contents of /raw/extsd, it still can't interact with /storage/***. I've been trying to upgrade my primary by patching a zip I made from my nandroid backup (just system files), but it constantly fails in TWRP with "can't load real update-binary." The patching of the zip works just fine, just the execution is the problem. Without primary being able to see the storage location, I can't load ROMS and GApps to External (from Primary), since it tells me that I don't have sufficient storage available in the system partition of /raw/extsd. In fact, my use of the external sd is limited in Primary while it is looking at this location. For example, I can't delete files in /raw/extsd.

I think the code you included in MB to look for /system/bin/vold worked for the ROMS, but no such location exists in Primary which is why I think it can't see the /storage/***. Is there a way to update this so that when you update the Ramdisk in Primary that it also creates /system/bin/vold. I'm guessing this could fix the issue. Thanks again!

---------- Post added at 14:32 ---------- Previous post was at 14:31 ----------

[MENTION=6998726]rabby38[/MENTION]

This is the link to the utilities for v2361

https://snapshots.noobdev.io/files/...es/DualBootUtilities-8.0.0.r2361.g4e0ba6c.zip
[Galaxy S 4 i9505 Original Android Development] Gerxp:
Some browser apps in Dual rom have no write access to SD card after installation of Dual Patcher.

They are fine after Uninstalling DP.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Has anyone managed to get MM running as a secondary?

I've tried it on extSD and I just get a blank screen.
[Galaxy S 4 i9505 Original Android Development] rabby38:
OP Member48 posts Thanks: 2

bro i am cwm recovery user but How to boot into other rom if you have boot loop with the current rom ?
[Galaxy S 4 i9505 Original Android Development] twint14:
thanks man,
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
I tried. Mm Roms work everywhere, except sdcard :D
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] I am still trying to log the issues on the Exynos Note 4 but I still get empty files, do you have any idea why both the multiboot log and the logs generated by the getlogs zip are empty files?

Also when I get myself into the bootloops it seems like adb doesn't get initialized so I can't get a log using adb either.

Also this is unrelated to that but as I bought a Redmi Note 2 Prime and still waiting to receive it (will have it in the weekend) would you consider adding support for that device (if possible at all as it has a Mediatek SOC) if I sent all the needed files once I get it (IIRC fstab but please inform me if anything else) and would do as much testing and logging as needed (as long as I can actually get logs)?

I really love your patcher and it would be so awesome to be able to have it on that as well (mostly to be able to keep using MIUI for the camera and AOSP for most other things).
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Hey [MENTION=4277844]chenxiaolong[/MENTION] , did you deal with the squashfs read only???
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry, I won't be able to answer questions or work on anything until the weekend (and it'll probably be like this until the end of the semester). I'm getting swamped with school stuff :(
[Galaxy S 4 i9505 Original Android Development] gaww:
Good luck - and remember only 4.0's are acceptable !

Looking forward to you getting a 935F and getting this to work on it.
[Galaxy S 4 i9505 Original Android Development] lukas77:
Hi,

When I trying to set kernel from primary rom I have this message:

Failed to set kernel

This error lasts for a long time already but I didn't have time to report it.

Device: LG G4 H815 International

ROM: Stock MM 6.0

Logs:

https://onedrive.live.com/redir?resid=4AD46D2DE15DBE47!5053&authkey=!AMxpCASEhxZ8NQI&ithint=file,gz
[Galaxy S 4 i9505 Original Android Development] alahkel:
Then have a nice weekend :) good luck with school ?

Oh I forgot to tell that latest build fixed the preloader and write Raw Image bugs.

App sharing between miui and aosp gets the shared apps to crash on miui but it actually works and I found a workaround for it.

I simply tried copying the app data dir (eg /data/data/com.whatsapp) to the multiboot's _appsharing folder and enabling appsharing for whatsapp on the aosp rom only.

It works pretty good, I mean obviously data isnt shared from the miui side but I simply have to copy whatsapp data dir between the 2 dirs.

Actually is there a way to do it manually? (configure on Android manually e. g. via terminal emu an app to use data on another directory).

Also is there a way to access the /data/data/multiboot dir from secondary/dataslot roms?

well the last isnt a big deal.. ?

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
would like the Moto G 2014 were included, I use two roms on it, do it please
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
When you are back again, could you please tell me whether I can encrypt my Touchwiz Primary Partion, of not? And whether I can encrypt my CM13 Data slot partition, or not (at the same time?)? And if it helps to have an encrypted phone when rooted?
[Galaxy S 4 i9505 Original Android Development] ewangw:
Just so you know, he will ask you to send the logs generated when you flash the linked file in TWRP: https://snapshots.noobdev.io/misc/getlogs/GetLogs-20160315.zip
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
Is it just me install this ZIP file by TWRP and dual boot application is compatible with the Moto G 2014?
[Galaxy S 4 i9505 Original Android Development] MagicHero):
Add z008 pls) :good:
[Galaxy S 4 i9505 Original Android Development] ewangw:
No.......

When you flash the file in TWRP, it will create some log files that you will send to [MENTION=4277844]chenxiaolong[/MENTION]. Then he will be able to add support for the G 2014
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
I obtained the necessary file, now only the developer add Moto G 2014

https://mega.nz/#!LcUkABrC!HvWWJE8OxI1ivxv1VG4I8w3xTVn4__hB6oLlxjXUweI
[Galaxy S 4 i9505 Original Android Development] adarshprakash:
I think you can get it worked. patch the zip file for data slot. I don't think system memory have enough space. Then open the patched zip and edit the file /multiboot/info.prop , change

mbtool.installer.ignore-codename=false to

mbtool.installer.ignore-codename=true

"This value is useful when the device is

# a variant of a supported device (or very similar to one)" in our case z008 is very much similar to z00A:o

I have installed stock as primary and cm13 in data slot. Just worked fine, But I don't know for sure.

Take a complete back up for safety.
[Galaxy S 4 i9505 Original Android Development] MagicHero):
No longer relevant [MENTION=7111568]say99[/MENTION] already did commit.But thanks for the tip
[Galaxy S 4 i9505 Original Android Development] Jason761:
Im trying to dual boot cm-13.0-20151219-UNOFFICIAL-zerofltexx on my s6e but it always fail at flash. This is my multiboot.log

[V] ROM ID: data-slot-secondary
[D] [Installer] Chroot set up stage
[D] Boot partition SHA1sum: f7c5bfaf54f03653d93ca54eaf0f305dc0596727
[E] /etc/fstab: Failed to stat: No such file or directory
[E] /etc/recovery.fstab: Failed to stat: No such file or directory
[D] [Installer] Filesystem mounting stage
[E] Failed to create /chroot/cache/recovery: File exists
[D] /data/.system.img.tmp: Creating new 3879731200 ext4 image
[D] Running command: [ make_ext4fs, -l, 3879731200, /data/.system.img.tmp ]
[V] Copying system to temporary image
[D] Assigning /data/.system.img.tmp to loop device /dev/block/loop1
[D] Clearing loop device /dev/block/loop1
[D] [Installer] Installation stage
[V] Running real update-binary
[V] Here we go!
[D] update-binary is AROMA: 0
[D] Property 'ro.bootloader' does not exist in recovery's default.prop
[D] - 'ro.bootloader'='G925W8VLU3BOJ7' will be set in chroot environment
[D] Original properties environment: 8,0
[D] Switched to legacy properties environment: 7,32768
This package is for device: zeroflteskt,zerofltektt,zerofltelgt,zeroflte,zerofltexx; this device is zeroltetmotmo.
[D] Child exited: 7

[E] /mb/updater returned non-zero exit status
[V] Failed to run real update-binary
[D] Running command: [ /update-binary-tool, mount, /system ]
[D] update-binary-tool: Mounted /mb/loop.system at /system
[D] [Installer] Filesystem unmounting stage
[D] Running command: [ /update-binary-tool, unmount, /system ]
[D] update-binary-tool: Unmounted /system
[D] Running command: [ /update-binary-tool, unmount, /cache ]
[V] update-binary-tool: Ignoring unmount command for /cache
[D] Running command: [ /update-binary-tool, unmount, /data ]
[V] update-binary-tool: Ignoring unmount command for /data
[V] Copying temporary image to system
[D] Assigning /data/.system.img.tmp to loop device /dev/block/loop1
[D] Clearing loop device /dev/block/loop1
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/efs: Invalid argument
[E] /efs is not mounted
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4400216]Jason761[/MENTION],

I believe this is your problem:

This package is for device: zeroflteskt,zerofltektt,zerofltelgt,zeroflte,zerofltexx; this device is zeroltetmotmo.

Not an expert and don't have the S6 Edge, but did download the CM file you mentioned and looked at the updater-script. Your device, zeroltetmotmo, is not supported in this ROM which is why I think it is failing. You could edit the updater-script to include your device, but

I would not recommend it

since it could lead to other complications ( see [GUIDE] Dualboot CM13 and TouchWiz on Samsung Galaxy S6, where someone had a similar problem: http://xdaforums.com/showpost.php?p=64382067&postcount=75.)

From Updater-Script (This code tries to validate that your device is one of the supported devices before trying to install. If it doesn't validate your device, it fails so that you don't donk up your phone).:):

assert(getprop("ro.product.device") == "zeroflteskt" || getprop("ro.build.product") == "zeroflteskt" || getprop("ro.product.device") == "zerofltektt" || getprop("ro.build.product") == "zerofltektt" || getprop("ro.product.device") == "zerofltelgt" || getprop("ro.build.product") == "zerofltelgt" || getprop("ro.product.device") == "zeroflte" || getprop("ro.build.product") == "zeroflte" || getprop("ro.product.device") == "zerofltexx" || getprop("ro.build.product") == "zerofltexx" || abort("This package is for device: zeroflteskt,zerofltektt,zerofltelgt,zeroflte,zerofltexx; this device is " + getprop("ro.product.device") + "."););
[Galaxy S 4 i9505 Original Android Development] Russiamen:
Add p5110(Samsung Galaxy tab 2 10.1 wifi)
[Galaxy S 4 i9505 Original Android Development] nutpants:
Is there any way to use a different file manger other than documentsui?

I've just updated to the latest patcher and found my documents ui file picker crashes whenever I pick internal storage.. I don't use it for anything else and have no idea why it's now acting like junk(other than it being junk to start with)

I hate to have to wipe everything because of this.

Thanks for any info
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I use Root Explorer, doesn't your documentsUI list all the file managers installed on the side menu where you can select your storage?

Mine does in both TW 5.1.1 and CM13.
[Galaxy S 4 i9505 Original Android Development] Minilad:
Add sm-t310
[Galaxy S 4 i9505 Original Android Development] nutpants:
It will when launched from other apps but from the patcher I don't show any alternative.. maybe it's time to update from 4.4 and redo the 200 plus app installation.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Has any support been added for the S7 Varients yet?

Picked me up a Edge 7 :))
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
S7 edge I was able to install a secondary Rom but booting into it was not possible
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Having problems with anything cm13 based on note for trltetmo

http://hearmewhisper.ddns.net/owncloud/index.php/s/SmuUL4N85o1P0qC

I saw also wondering Chen, any chance on nexus 9 support?
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
When the Moto G 2014 will be added to Dual Boot?
[Galaxy S 4 i9505 Original Android Development] mrjoy:
Getting error on n900 stock 5.0 rom, it says failed to load boot partition image

failed to flash zip file.

getting same error on every rom. Plz help
[Galaxy S 4 i9505 Original Android Development] Harjito:
can not access the app sharing

is there a solution:

when click the app sharing, always ask for an update ramdisk , but primary ROM always bootloop if update ramdisk .

..

galaxy s4 i9500.

primary rom = arrow rom v.16

secondary rom = cm i9500 6.0.1
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Resurrection Remix 5.5.9 stuck on bootanimation

[MENTION=4277844]chenxiaolong[/MENTION] Hi dude, I hope we can debug the problem I'm facing. I'm trying to install Resurrection Remix 5.5.9 on my K3 Note on extsd-slot, it installs just fine no errors and also no vibrations on boot that can indicate an issue. But the rom is simply stuck on bootanimation. What it can be? Logs attached.
[Galaxy S 4 i9505 Original Android Development] gaww:
What S7E version did you use - 935F ?

There is a snapdragon model 9350 that has bootloader unlocked and CF root setup - would that be a better alternative ?
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
935w8 Canadian exynos version
[Galaxy S 4 i9505 Original Android Development] gaww:
Guessed it was exynos - that is why I am curious about the 9350 snapdragon. [MENTION=4277844]chenxiaolong[/MENTION] had outlined the limitations of the exynos versions on TMo and was hoping this one might be a better match.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm actually more interested in the G935FD (dual SIM) since it seems to run the same firmware as the G935F. I personally wouldn't get the Chinese SM-G9350 even if there's a chance that the TMO firmware could run on it because I'm not very fond of the SD820 chip. My S7 Edge runs far hotter than my old Exynos S6 Edge+ for day-to-day tasks (especially in Google Maps).

I'm just waiting for someone to confirm that the device will connect to the data-only LTE band 12. If not, there wouldn't be much point in buying it and trying to port TMO's VoLTE code.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Hurray! You are back.. Did your exams finish?

Please look into this log and see what's causing the error.

https://drive.google.com/file/d/0B20JfVIKCreWZWJZTlpoSnZBMjg/view?usp=docslist_api

I think it is due to the crappy updater-script of these stock ROMs, but I want to confirm.

Thanks in advance. :)
[Galaxy S 4 i9505 Original Android Development] gaww:
I was looking at the duel SIM version also, but I have never had heating issues. I was hoping you or someone would see if TMO firmware would run on the 9350. Stupid question time - if the bootloader on it was unlocked, would ODINing the TMo firmware lock it back up ?

PS - hope you Aced the finals.
[Galaxy S 4 i9505 Original Android Development] RomanSkyline:
Please help me, from where can I get ID of data slot or extsd slot?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
The "ID" of data and extensive slots are whatever you name them. The only restrictions are for extsd slot must be only lowercase letters and numbers, no spaces or special characters.
[Galaxy S 4 i9505 Original Android Development] MrHellRider:
Can i flash this secondary rom in my extsdcard
[Galaxy S 4 i9505 Original Android Development] Andycar:
Yes you can. Just patch it for the last option: extsd-slot-yourname. It will be flashed to extSdCatd\multiboot\extsd-slot-yourname\system.img

The data of your ROM (let's call it secondary, if you wish) will go to raw\data\multiboot\data\extsd-slot-yourname\ in this case.

Отправлено с моего SM-N920G через Tapatalk
[Galaxy S 4 i9505 Original Android Development] MrHellRider:
Ya i flashed it yesterday it worked but i forgot to flash the gapps so i patched the gapps n i selected the the slot which was created after the rom was created in my case (aokp ext-slot) this was the name given in the configuration so i selected it n patched the gapps but when i flashing it said storage out of space use small package of gapps but i have the pico package only n i have 2.8gb free in my extsdcard any sol
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I get this error with flashing to extsdcard : (see picture)

Any idea what went wrong?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm back and 8.0.0.r2427.gf896239 is out! :)

This is another one of those releases that bring a massive amount of behind the scenes changes. Starting with this release (and after performing a ramdisk update), the app no longer requires root for anything! This means you can dual boot an unrooted ROM without loss of any functionality. Even in-app flashing will work. This is great for people like me, who have to use the phone for work email or VPN and are either not allowed to root or the app simply won't run if rooted.

In order to safely implement the new root-free operations, all of the DualBootPatcher code is now signed. This means the app will refuse to flash or boot any ROM or zip where the mbtool binary has been modified. This doesn't affect anything unless you use a custom build of DualBootPatcher. Files patched by custom builds of DualBootPatcher can no longer be flashed by my official builds (and vice versa).

The extsd-slots issues with Marshmallow where in-app flashing was broken or ROMs were missing from the app should now also be fixed. These were caused by changes in the way Marshmallow handles SD cards. If anyone uses a USB SD card reader, make sure it is unplugged when using the app since there is currently no way to differentiate between an internal and USB-connected SD card.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Since you don't need root does that mean this will run on an S7 lol or does it still need recovery.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is now implemented in 8.0.0.r2429.g6f652d1 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Still needs a custom recovery lol. We owners of the T-Mobile S7 are a screwed bunch :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ouch, looks like this bug was introduced with this commit from Feb 19th: https://github.com/chenxiaolong/DualBootPatcher/commit/3db9f18336542b795b156d5057efadd6efec214d

Whenever a file patched for primary is flashed, the following happens:

Creates a temporary ext4 image in /data

Copies /system (excluding /system/multiboot) to the temporary image

Flashes zip

Wipe /system (excluding /system/multiboot)

Copies temporary image back to /system

This prevents ROMs from inadvertently wiping the secondary ROM. The commit above caused the second step to be skipped, so when it got to the end, all that was remaining in /system was just SuperSU (with no ROM). This should be fixed in 8.0.0.r2430.ged3ebd7.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is caused by some more restrictive SELinux policies on your device. It should be fixed in 8.0.0.r2435.g9613ee1.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added in 8.0.0.r2436.g1385c77 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does the device support anything newer than Android 4.2? That is the minimum required version for the app.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added in 8.0.0.r2437.gb1f9a00.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
All of the multi-slot locations are installed to the /cache partition and it looks like it ran out of space trying to install the ROM (there are a bunch of "No space left on device" errors in the log). I'd suggest installing to a data-slot (which goes in /data) or an extsd-slot (which goes on the SD card).

For Nexus 9 support, just flash the GetLogs zip from https://snapshots.noobdev.io and send me the file it creates in /sdcard/logs/. Note that encryption is currently not supported, so you'll have to disable that on your tablet if you want to dual boot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, the only way we can debug that is to make a logcat while it's booting since the multiboot code has already finished and exited. Hopefully the ROM developer enabled ADB by default.

Try running this from your computer right when the device starts to boot:

adb logcat
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, midterms are done and all went well :D

Can you post the updater-script and update-binary files for this ROM? This might be an easy one to fix this time :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Ok thanks, I'll try.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
While trying to patch Liquid-JB-v2.37-OFFICIAL-jfltevzw

Detected Official LiquidSmooth ROM zip

--- Please wait. This may take a while ---

Extracting ramdisk--- ERROR BEGIN ---

--- STDOUT BEGIN ---

patching file init.target.rc

Hunk #1 FAILED at 39.

1 out of 1 hunk FAILED -- saving rejects to file init.target.rc.rej

--- STDOUT END ---

--- STDERR BEGIN ---

cygwin warning:

MS-DOS style path detected: c:\users\brandon\appdata\local\temp\tmpnjyfbq\extr

acted

Preferred POSIX equivalent is: /cygdrive/c/users/brandon/appdata/local/temp/tm

pnjyfbq/extracted

CYGWIN environment variable option "nodosfilewarning" turns off this warning.

Consult the user's guide for more details about POSIX paths:

http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

--- STDERR END ---

--- ERROR END ---

Failed to apply patch

---------- Post added at 05:38 PM ---------- Previous post was at 05:38 PM ----------
[Galaxy S 4 i9505 Original Android Development] Bejda:
Frankly i have doubts..

The error others reported about latest PAC is the same i had with 11/05 nightly (same output,i tested [edit:and same output as above]).

`SBR` reported he could patch latest PAC using a previous version (from before auto-ramdisk patching support)..just like me with 11/05 nightly again...but he had issues with the zip produced so..

I'm in a good situation right now to test 11/07 nightly as secondary,let me about 30 mn max and i'll let you know what happened ok?
[Galaxy S 4 i9505 Original Android Development] traicer:
yea i just tried patching the latest tmobile nightly and it didnt work, ill have to wait till a fix is out .
[Galaxy S 4 i9505 Original Android Development] royredman:
Hey, apparently this rom isn't supported :(

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

Is there any way I can Get it supported? (would it work if I did it manually?)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Hm,and 11/07 jfltexx build patched with 1.18.1 patcher version gives the well known com.android.phone fc at boot so frequently that you can't navigate (i've made my way to settings>apps>all but can't click on phone or phone storage lol),sorry.
[Galaxy S 4 i9505 Original Android Development] traicer:
yea hopefully its not too hard to fix