yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I think this should be fixed in 8.0.0.r2451.gc1196b9 (fingers crossed).

I overlooked the mount options when you posted this a while back: http://xdaforums.com/showpost.php?p=65902937&postcount=8890 When your primary ROM was unpatched, the SD card was mounted with the following options:

rw,dirsync,nosuid,nodev,noexec,relatime,[b]uid=[u]1023[/u],gid=[u]1023[/u],fmask=[u]0007[/u],dmask=[u]0007[/u][/b],allow_utime=0020,namecase=0,errors=remount-ro

When mbtool mounted the filesystem, it didn't provide any additional mount options, so it effectively became:

rw,dirsync,nosuid,nodev,noexec,relatime,[b]uid=[u]0[/u],gid=[u]0[/u],fmask=[device dependent],dmask=[device dependent][/b],allow_utime=0020,namecase=0,errors=remount-ro

making all files on the SD card appear to be owned by root. This would cause all of the Permission Denied errors from your log files.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! 8.0.0.r2454.ga9ac657

Done! 8.0.0.r2454.ga9ac657

Done! 8.0.0.r2454.ga9ac657. There's a good chance that there will be issues and we'll need to make further changes, but this should hopefully get the flashing process working.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn.... Others seem to have run into the same issue with 128GB SD cards as well, though I'm not sure why. Unfortunately, I don't know how to fix this as it's more of a kernel issue. The kernel is detecting the card, but it refuses to mount. Maybe the card takes longer to initialize?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think that was hidden due to a bug in my old code (oops) :p
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please flash the GetLogs zip from https://snapshots.noobdev.io and send me the log archive it creates in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Lol. :D So I can expect you'll remove the ui_print in the future builds?
[Galaxy S 4 i9505 Original Android Development] Killerdog:
Hi,

I try a 64gb exfat and it's working good.

Reformat my 128gb to fat32 and it's working good.

It seem to be a problem with texfat for card bigger than 64gb.

Just one more thing, I can't have root access on any of my secondary rom, aosp, candysix, or cm13.

I patch the latest supersu (2.71) for each rom and flash it, supersu app is present but inactive.

Supersu app ask me to update su in normal way (doesn't work) or via recovery (don't try it but I think it can't work because it try on the primary rom).

Should I need to flash a special package?

Envoyé de mon LG-H815 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Well it seems to fail at flashing preloader with stock MIUI ROMs so at least that part of the flash script will need to be removed probably (if not the uboot and others as well).
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
But if I am not wrong, backup and restore a normal dualboot installation is also not possible (work in progress) yet as I get WIP toast when clicking on Backup.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=427477]chenxialong[/MENTION]: Hi chen, does booting from ext sd work? I think there was an open issue some time ago and the last time I tried on my S5 Snapdragon I landed in Recovery.
[Galaxy S 4 i9505 Original Android Development] SamuelBegui:
For some reason when updating mbtools it appears as though it updated successfully however when I reboot my device the Dual Boot Patcher app says I never updated mbtools.

Anyone else experiencing this?
[Galaxy S 4 i9505 Original Android Development] Russiamen:
[MENTION=427477]chenxiaolog[/MENTION]

Sorry I forgot to mention that there is multi rom for all versions of 3100/3110 and 5100/5110 all and they are so,espressowifi,espressorf.Could you add the support for individual devices is terminated,only together.(espresso10wifi and 10rf leave)Thanks for the reply,I hope for a speedy addition
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
The error when trying to install a second ROM on Moto G 2014, I hope it is resolved
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Got some issues while flashing with anything newer that build 2360. It seems that its not able to backup the gapps, resulting in nothing but force closes. Luckily I made a backup before flashing. Attached are the TWRP recovery logs for 2360 and 2442.
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
http://imgur.com/O8DIiw3

The error when trying to install a second ROM on Moto G 2014, I hope it is resolved

---------- Post added at 05:57 PM ---------- Previous post was at 05:24 PM ----------

https://mega.nz/#!vEcUjBDa

Moto G 2014
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] it also seems like updating the ramdisk on the Redmi Note 2 broke access to the microSD card on CM12.1

How would I log that?
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi there! Now because appear some new custom rom's on S7 Flat area, I want to ask if the patch for S7 Edge working for S7 Flat ?

I want to try dualboot some rom's !

If not please [MENTION=4277844]chenxiaolong[/MENTION] can you added ?

THX
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi ,

this is because your specific version of the Moto G 2014 isn't included in the patcher.

Add the following line to your build.prop file in the primary Rom:

ro.patcher.device=titan

Reboot your phone and then try again. It should work.

Regards!
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
This is a problem with the new SuperSU. While flashing, it reads the content of your boot partition (kernel), patches it and write it back. So if you are on your primary ROM and in-app-flashing it will read the kernel of your primary ROM and patch it.

You have to flash your secondary rom + gapps, boot it once so that it is your current kernel in boot partition and flash the patched SuperSU in TWRP.
[Galaxy S 4 i9505 Original Android Development] ewangw:
I used Chainfire's Liveboot app to capture logs of my boot process when I had a similar issue. Install it and go into settings and check the Save Logs box, then reboot. You should find a file in /cache called liveboot.log which contains the information [MENTION=4277844]chenxiaolong[/MENTION] will need.
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
I did what you asked and appeared to me to set the kernel and I set, but still missing something appeared that two errors ~>

I hope you can help me
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi,

you are installing as "dual' and apparently you don't have enough space in /system or /data partition.

Try to install as ext_sdcard

If that is not the case and you have doubts about how to obtain logs to inform errors or problems to this thread to obtain help, read the OP carefully. Or PM me and I will help you, you can write me in Portuguese if you want [emoji1]

Regards.
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
The installation of the ROM was successful, but the error has GAPPS (was incompatible) and that the version of GAPPS is 6.0 and the ROM which is the RR 5.6.7 is also 6.0.

I do not understand why this error
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Mmmmm... try an older version of GAPPS. I'm using the one from March 7 and don't have problems at all in whatever MM Rom I install. Newer versions had given me uncountable issues.

Don't worry, Google programs will update by itselves. Also, install the Pico version, it's the tiniest and the one that causes less problems and incompatibilities.

Well, as you can see you are almost there. This issue here is not related with the patcher!!!!

Hope it helps you.

Regards.
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
O erro com os gapps ainda continuam mesmo depois de eu ter baixado uma versão mais antiga, mas eu te agradeço muito por ter me ajudado a resolver o problema do Dual Boot, se algum dia precisar de ajuda conte comigo (:
[Galaxy S 4 i9505 Original Android Development] coldgin_:
pt: vc tentou com alguma outra Gapps q não seja a Open Gapps, tipo a Banks por exemplo?

en: did you try with some other Gapps instead of Open Gapps, eg the Banks one?

Regards, saudações! :good:
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
I've tried to Banks GAPPS, OpenGapps of 05 and 07 and still appears the error.
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
Could you pass me the apps you're using on your second ROM? as much as I download an older version of the error when installing the GAPPS continue.
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi,

as I already told you, I use Open Gapps Pico 07.03.2016

I have installed CM13 as second Rom in /data (first Rom is Stock 6.0) and didnt have any problems till now.

My phone is pretty much the same as yours, its a Moto G 2015 dual sim (codename = osprey) the brazilian model with tv ...

Everything is working flawlessly ... por enquanto [emoji14]

I also have a Samsung S4 Mini with Bliss 6.0.1 as second in my external sdcard , using the same Gapps with no issues. Primary AICP 10, same Open Gapps but for LP.

My advice: be patient and keep trying, and if you face issues post the logs here, you certainly will get some help.

Read the OP to know how to obtain the expected logs from recovery, or PM me and I will guide you.

Regards!
[Galaxy S 4 i9505 Original Android Development] monkteo:
No it's not working (tried any way)

So please [MENTION=4277844]chenxiaolong[/MENTION] add S7 Flat G930F

THX
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Been extremely busy with a recent motor vehicle accident, lawyers and insurance companies. Not fun.

Was their a recent update to fix compatability with the s7 edge?
[Galaxy S 4 i9505 Original Android Development] monkteo:
No but I try, nothing wrong can happen!

Now we wait !
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
I tried last week ended up having to recover my phone. Can install the Rom but no way of switching between roms. I did contact the developer to add support the other week. He added support but switching between roms themselves does not work at all for me. So close but so far in a way
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Just wanted to say thanks for the update. So far, I am not having any issues in primary or in my data-slot ROM!
[Galaxy S 4 i9505 Original Android Development] mike2nl:
[MENTION=4277844]chenxiaolong[/MENTION]:

Your link in 1st post is no longer working, Please fix it.

Link: (https://github.com/chenxiaolong/Dual...ADME.jflte.txt)
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
I'm already giving up, I tried all GAPPS, Open GAPPS, GAPPS and The Bank - GAPPS and always the same mistake. You could check this log to identify what error is that?

https://mega.nz/#!KEFWWLRB!rQyh9tE6-8SjxkBkg55t90CQEyY895Q7Vp9PdOporpg
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, so you manage to patch (my to) install (I can't) but you can't switch between rom ?

(I remember I have a port rom, primary from G9305F Echoe) so I will modify the prop.build and try again

THX

PS. Not working
[Galaxy S 4 i9505 Original Android Development] Gerxp:
What is a good app/system cleaner that does not mess up your installed ROMs and that I can safely use in each individual ROM installed?

I ask this because a few days back I used SDMaid which accidentally deleted cache and apps used in another ROM.
[Galaxy S 4 i9505 Original Android Development] ewangw:
I would think that the DualBoot Utilities would be best since it allows you to clean Dalvik, Cache, System, or Data for the specified ROM. You just need to run it in TWRP.

https://snapshots.noobdev.io/files/...es/DualBootUtilities-8.0.0.r2454.ga9ac657.zip
[Galaxy S 4 i9505 Original Android Development] amagnien:
Hi,

I can't find the dual boot switcher app. Can someone help please?
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi !

well, I looked at the logs and doesn't seem something related to the patcher per se, but a conflict between the RR_r24 patched and Gapps.

Look, in Multiboot.log appears the same error you already informed via screenshot :

*** Incompatible Android ROM detected ***
This GApps pkg is for Android 6.0.x ONLY
******* GApps Installation failed *******

so I looked for this compatibility check inside Open Gapps installer scripts (updater-script/update-binary that at some point run a script called installer.sh) and I found the check part inside installer.sh :

# Check to make certain user has proper version ROM Installed
if [ ! "$rom_build_sdk" = "$req_android_sdk" ]; then
ui_print "*** Incompatible Android ROM detected ***";
ui_print " ";
ui_print "This GApps pkg is for Android $req_android_version.x ONLY";
ui_print " ";
ui_print "******* GApps Installation failed *******";
ui_print " ";
install_note="${install_note}rom_android_version_msg"$'\n'; # make note that ROM Version is not compatible with these GApps
abort "$E_ROMVER";
fi;

being $req_android_sdk defined before in the script as "23" (Android 6) and $rom_build_sdk taken from ro.build.version.sdk that should be in your RR_r24's build.prop file

So, you maybe can solve this issue this way: you already have your RR Rom patched. So boot it without Gapps. Once inside the new Rom do not configure anything but just edit its build.prop file and look for "ro.build.version.sdk" inside it. If it's already there and it's not set as "23" change this value to "23". If it's no there, add the property.

Reboot into Recovery. Install your already patched Gapps (please be carefull, it has to be already patched!!) as a normal zip file installation, it will be installed by TWRP in the slot where you set the Gapps when you patched it.

If all works as expected, the Gapps will be installed correctly and TWRP will then boot into RR ROM with now having Gapps installed. Configure your new Rom and enjoy ;)

If it doesn't work please send screenshots and/or logs, and I will take a look at them.

Note: regarding to ro.build.version.sdk, if it was already there and set as "23" you are f** up :( Then I'd ask you to try the procedure from the very begining but using another MM ROM but RR_r24, could be CM13, just for testing purposes.

Hope it helps. Let me know if it works.

Regards!
[Galaxy S 4 i9505 Original Android Development] Eliminater:
I try the patched again on my I9506 with arter kernel. a wonder it works fine with arter kernel.

Amazing developer job thank you very much [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Mussels84:
It's been a while since i used this tool and i'm aware its changed a bit.

I'd like to try and set up a dual boot situation, and would love some advice/guides.

I'd like to run a stock rom (MM 6.0.1 just hit the 910G) and CM13 together as dual boot.

1. Is it possible to delete one ROM and go single boot later?

2. Is it possible to backup my primary CM13 rom now, and move it to ROM 2 after installing a stock rom?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Yes and yes...
[Galaxy S 4 i9505 Original Android Development] gaww:
Over on the US TMo 935T versus international thread, there is a post with the attached image that looks like Lte band 12 may work?

http://xdaforums.com/attachment.php?attachmentid=3719088&d=1460689323
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Lately having same problem with all MM ROMs and only gapps I've been able to use is this one from Vanir ROM. Works on aicp, synergy and crdroid

http://www.emccann.net/dho/5-Gapps/
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just a heads up before you try this: currently Marshmallow TouchWiz will not work in a dual boot environment. There are some SELinux issues I haven't had a chance to fix yet because the only device I have with TW MM has a locked bootloader.
[Galaxy S 4 i9505 Original Android Development] minhas729:
Addition of widget to switch ROMs is possible?
[Galaxy S 4 i9505 Original Android Development] Gerxp:
Can I alsof use TWRP manager to flash Dualboot Utilities?
[Galaxy S 4 i9505 Original Android Development] ewangw:
I would think so, but it would just send you to recovery so that the file could be flashed in TWRP. The Dualboot Utilities, when flashed, will provide you with options to select the ROM you wish to work on, additional options to wipe System/data/cache/multiboot files/dalvik, and to switch between ROMs.

---------- Post added at 18:57 ---------- Previous post was at 18:53 ----------

The patcher has an option to add a widget to your phone's homescreen. Under ROMS, Select the 3 dots to the left of the ROM you would like add to your home screen, and at the bottom of the next screen (and above Wipe ROM) is the 'Add to home screen' option. When you click it, it will add a widget that will allow you to switch ROMS and then reboot your phone.
[Galaxy S 4 i9505 Original Android Development] gaww:
maybe sell on eBay and get an FD ?
[Galaxy S 4 i9505 Original Android Development] minhas729:
Can anyone explain , can i clean install a primary ROM, means completely wiping the present primary ROM and install a new one in its place, in such a way that my second ROM is not effected. What should i do in such case.

Bcz without dual rom patch as we know we just wipe data delvik cache and system and install new ROM. But in dual ROM if wipe data delvik cache and system in twrp.second rom will be gone too right? (Assuming i was on primary and reboot into recovery and do above thing).

How can i install a completely new primary.

Your kind words will be very hellful.

(Just for info using patcher app on lgg3 which this app officially supports, and asking here bcz you ppl are more skilled here as its almost new there so trying to get an expert opinion)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], can you please check, because I think that this feature is broken.

I copied modem.img and apnhlos.img files to my dual rom installation, bit nothing happened.

Отправлено с моего SM-N910G через Tapatalk
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Yes but you have to install a patched file using the patch utilities. I've done that on my S4 m919

Make a backup first :)

Another option is install new ROM on external and tweak it to your liking, then make a backup and restore it to primary. Did that to reduce size and make sure it fits
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope, this still hasn't been fixed yet. The S5's card reader is abnormally slow at detecting that an SD card is inserted and the patcher currently doesn't wait for that during boot.
[Galaxy S 4 i9505 Original Android Development] minhas729:
So i first patch my new desired ROM then go to dual patch utility. Wipe data delvik cache system for primary and flash the patched file of new rom (as primary) and it will replace primary? Is that what should be done?

And if u can tell how to completely delete secondary ROM?

Is there any easy way to remove secondary ROM so i can change it.

Or i should wipe data delvik cache system for secondary in patch utility and hit reboot system to go back to primary (only ROM at that on cell)?

Or any easy way to wipe secondary so that i can change it completely like for moving from cm based to aosp based
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added in 8.0.0.r2455.g2a629aa :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the file it creates in /sdcard/logs/?

Note that dual boot currently does not work with any Marshmallow TouchWiz ROM so it is effectively broken on all the S7 devices right now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try switching to a ROM that has modem.img and apnhlos.img files and then immediately send me a copy of /sdcard/MultiBoot/daemon.log? Make sure you don't reboot in between since the file will be overwritten. That should hopefully contain some hints as to what's going on. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Should be fixed in 8.0.0.r2456.gdb2b8a3.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn... Can you post the update-binary and updater-script files for the ROM? There's a good chance I'll have to reverse engineer the update-binary file to see what partitions it's trying to flash.
[Galaxy S 4 i9505 Original Android Development] Andycar:
OK, so I used dual boot utilities in TWRP to switch to dual CM13, and it reported that additional .img files were found... But nothing happened upon reboot to it.

Daemon.log contents below, but there are just two lines:

2016/04/16 23:35:08 MSK][D] Initialized daemon
[2016/04/16 23:35:08 MSK][D] Socket ready, waiting for connections
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try switching ROMs in the app before looking at daemon.log? Thanks!

Btw, the Snapdragon Note 4 has a limitation where the modem cannot be flashed unless the device is booted into recovery or download mode. There's a chance this may apply to the Exynos Note 4 as well and cause this feature to break.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Here you go, I will also upload the logs needed for the microSD card not working problem tomorrow, had that in my mind for the last week but things are quite crazy with college (tests, projects, homeworks, etc) and right now the phone is dead.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Oh, then it must be my case, since I'm using Note 4 Snapdragon (N910G) model...

Here is the link to the log right after switching to dual in the app:

https://drive.google.com/file/d/0B-WWoHMICGTgRDg3cnZuNDBKQjg/view?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Yes you can do all these things from the secondary ROM using the patcher app or better yet with the utilities zip flashed from recovery
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I can't seem to reproduce this. I just tried flashing CM 13 (20160409), OpenGapps Full (20160410), and CM 13 again and they went through without issues. I tried both flashing from recovery and from the app.

EDIT: This is on a jfltetmo (T-Mobile Galaxy S4)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh whoops, for some reason, I thought the N910G was Exynos.

The log confirms what I suspected. The modem and apnhlos partitions are indeed flashed, but the changes are being discarded by the device. Unfortunately, it's impossible for this to be fixed :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, I know that feeling :) It's been pretty hectic for me as well.

Thanks for the files. The flashing issues should be resolved in 8.0.0.r2457.g7fd3e3c.
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
OnePlus X Onyx

[MENTION=4277844]chenxiaolong[/MENTION] Hey iv'e sent you the logs per pm. I hope you got it :) When can we calculate for a support for this device? Sorry i don't want to stress you but i need it really much :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Here is the log generated by liveboot, didn't yet test flashing a MIUI rom as I just woke up.

EDIT: If the log from an other app is what you need just tell me from where.
[Galaxy S 4 i9505 Original Android Development] kykint:
My SM-G930K(heroltektt) won't boot after patching ramdisk. Maybe there was an error with my commit? https://github.com/chenxiaolong/DualBootPatcher/commit/2367eaffe484dfccfd2ac8d6a26a0e6e0231b07f (Sorry, I only checked whether it compiles well and forgot to do some testings before making pull request.)

Stuck at Galaxy S7 boot logo with Kernel is not SEANDROID enforcing message, then automatically reboots into recovery right away. Attached logs.