yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
I flash with in app without any issues except for fulmics as it must be flashed though twrp as it uses aroma. I do not use ext SD but instead data slots, that may be the issue not sure. Worth it to try with data slots instead maybe? Also, when your flashing magisk, SuperSU or Los su are you patching them first for the slot they are going in? You have to patch every single file that you are going to flash.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
I do patch the zips for every specific slot. I use TWRP to flash them as I was having problems updating secondary roms (I had to wipe system for every rom update). I'll try flashing using the app and create a new slot in data instead of ExtSD and see how it goes.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Okay just wanted to make sure. Then only thing I can think of is is related to using ext SD as I've never had any issues using data slots. Hopefully trying that will work for you. Just another question did you ever update your bootloader to the N bootloader? If not maybe try that too. If I have time tomorrow I'll try and do a couple tests using ext SD and see if it works for me or not too since I've never tried.
[Galaxy S 4 i9505 Original Android Development] abushami:
Enter an ID above?

I don't understand
[Galaxy S 4 i9505 Original Android Development] Hereiwas:
it's just a name, you can write whatever you want For example

when i've patched resurrection remix rom, i wrote rr
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
Give the slot a name, because you can have more than one. I have 3 ROMs on exstd. The IDs are:

14, ld7, line

Have to be lowercase, no spaces.

http://cloud.tapatalk.com/s/58d51fa273ad5/Screenshot_20170324-092711.png?
[Galaxy S 4 i9505 Original Android Development] Eleo:
You can change the names of ROMs afterwards. ID's are only needed when patching a zip. See mine as example
[Galaxy S 4 i9505 Original Android Development] tavocabe:
I've updated the app and tried using the built-in flashing utility but same result. Can't even boot LOS if I just flash it alone without gapps or root package. I have the latest N bootloader. It must be because of ExtSD, can't think of anything else.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Yeah I'd guess because of extsd, try using data slot. Like I said I'm using h830 and run RR, LOS and fulmics all on data slots and no issues whatsoever.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
Weird thing is I can perfectly boot RR on ExtSD prior to magisk root and even the magisk version if I flash previous versions boot.img. Will try a data slot now
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Okay so just tried patching and booting with extsd and it won't boot so that's the issue. Just have to use data slot and it will work.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
Crap. I wonder what the issue is with LOS not working on ExtSD. RR was working perfectly before magisk and even now it works by changing the boot.img (but loosing root)
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Don't know, but you should have never had to even change the boot.img to make it work. If you use data slots none of that is needed, all you'll need to do is patch the rom and gapps and flash (unless using Los or stock or DU, then you need to patch and flash root too). If you notice when flashing to extsd it shows unknown version and unknown build in dual boot patcher app, instead of showing correctly. I've attached screenshot. Also, I've included some of the logs if anyone wants to take a look to see if they can figure out why it's not booting from extsd. Hopefully there's something useful in the logs, but for now I'd just run from data slots as that is working without an issue. I sort of wonder if it may have something to do with the bootloader changes from MM to N though. The location of some partitions were changed and we can no longer even patch the stock N zips as it has an issue with the partition locations, which I included updated logs for the partitions awhile back but don't know if it was updated for the G5 and have no idea how to do myself. Not sure if that could affect ROMs on extsd too or not, but odd data slots would work. Anyways, hopefully something useful is in logs and if anyone needs more logs please let me know and I'll post them.

Device: T-mobile h830 (G5)

Issue: will not boot ROMs flashed to extsd
[Galaxy S 4 i9505 Original Android Development] farovitus:
TRICK to make a ROM boot on EXTSD slot is to flash any custom kernel or any flashable kernel, I've been doing this to make any rom on extsd slot to work. BTW i'm using an s7 edge(G935F).

Hope that this will help some of you to boot rom from external memory.

Hope that [MENTION=4277844]chenxiaolong[/MENTION] can fix this issue later on. Thanks
[Galaxy S 4 i9505 Original Android Development] FlatOutRU:
Any1?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Two methods...OIK

1.decompile the apk on pc or android using apktool, then open the assets folder and you'll find a compressed tar.gz file, open with 7 zip and you'll see a device.json file open this edit or add a new entry...follow one of the many device entries there...KNOW WHAT YOU'RE DOING BEFORE COMMITTING CHANGES....enter the correct paths/mount-points found in logs you've created, the ones you've posted....then recompile and sign, and try the app

Or:

if you're not connecting to MBTOOL then do this....only create a devices.json file with paths for your device, then install any official dualboot patcher, run it and click on the ROM entry you see, it'll tell you that your device "xXxX" is not supported, that's OK, now close it...head to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.1.0.r205.g1dc88ed2/ in this folder you'll find a devices.json file, delete this one and paste the one you've created above...this will enable you to run the app as if your device is officially supported and you won't need root to run mbtool as in method one above.

2.this method involves compiling from source/github you'll need a bit of knowledge to do this...just head to google and type "how to compile from source or git on Windows" this should guide you enough

....I've used this method on multiple devices with total success, switching roms, making backups etc...all functions obviously work...if you're getting errors it means you're not using correct paths...investigate this!

Good luck

"New World Order [NWO]"
[Galaxy S 4 i9505 Original Android Development] Erik1805:
Worked great but can't see the shared apps in my secondary rom. Any tips for me on this? Do I need to install them on the secondary rom?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yes. You need to install app firstly for it to show on list
[Galaxy S 4 i9505 Original Android Development] Erik1805:
Thabks. Does it also work with WhatsApp? When i start the secondary rom WhatsApp says I need to verify again.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I followed these steps; after booting to ROM, install whatsapp, enable data sharing, reboot, and voila:) it will have shared data. I think you forgot to reboot.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
If I flash RR and then LOS root package and then boot.img from previous RR versions it works and with root but every su request gets granted and no root manager works.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Well that's probably because your trying to flash another root package over the root package that RR installs (magisk is installed when you flash the rom now) already and that's probably causing issues with having magisk root and Los su both installed. Even though you're using an older boot.img the magisk files are probably still left over. I also don't recommend using older boot.img just to get it to boot, that just shouldn'tt be needed. I would just use data slots for now and if extsd gets fixed on our device then use it.
[Galaxy S 4 i9505 Original Android Development] Erik1805:
Oké I have tried it in the primary rom but when I select WhatsApp is Freeze's and does nothing. So it wouldn't share
[Galaxy S 4 i9505 Original Android Development] Eleo:
In mine I have shared whatsapp around three toichwiz ROMs and it works on all three without any verification or freeze. I think we need more info like logs to help you
[Galaxy S 4 i9505 Original Android Development] ale5000:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi,

I want to add dual boot compatibility to my flashable script.

Can you please explain what need to be done?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. It seems you missed my post so here I'm again asking if you can please add support for Lenovo P2.
[Galaxy S 4 i9505 Original Android Development] Erik1805:
If I would like to remove the dual patcher how would I do that.?
[Galaxy S 4 i9505 Original Android Development] Eleo:
There was a dualboot cleaner zip shared somewhere on this thread. I used that one
[Galaxy S 4 i9505 Original Android Development] Erik1805:
Thanks, will search for it. Does this remove the primary rom?
[Galaxy S 4 i9505 Original Android Development] Eleo:
No. It should only leave primary ROM
[Galaxy S 4 i9505 Original Android Development] egoiste87:
Please help to make the support of my phone very necessary n7100 t03g :( I do not know very well English I use an interpreter. Kindly help me from Russia
[Galaxy S 4 i9505 Original Android Development] Kippy51:
Please please read a couple of pages before posting. You have to supply a log of your device and then wait, because the boss is real busy with real life at the moment.

And check the list of supported devices, maybe yours already is.

Sent from one of my Sammy devices
[Galaxy S 4 i9505 Original Android Development] egoiste87:
Write please the instruction it is possible brief that it is necessary to make that supported my device
[Galaxy S 4 i9505 Original Android Development] egoiste87:
Many thanks to who helped to win))) samsung gt-n7100
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Is it not enough to wipe all ROMs except primary in app then reflash a non patched primary zip ?
[Galaxy S 4 i9505 Original Android Development] Eleo:
No. It breaks dualboot, but does not erase every trace of it
[Galaxy S 4 i9505 Original Android Development] fmotta:
Please add Xiaomi Mi Mix (codename lithium) to the supported device list.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
Could you please add support for HTC 10 (pme)?

I've seen 2 posts re this device in Dec 2016, but none since, and it's not supported.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] DodoGTA:
https://github.com/chenxiaolong/DualBootPatcher/pull/326
[Galaxy S 4 i9505 Original Android Development] egoiste87:
Chenxiaolong

Add please support samsung gt-n7100 t03g forward with impatience
[Galaxy S 4 i9505 Original Android Development] Mike0505:
Already supported : https://dbp.noobdev.io/supported_devices.html
[Galaxy S 4 i9505 Original Android Development] egoiste87:
There is support for n7105 t0lte and I need n7100 t03g proyval that does not work.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I've seen that also. But when I click on his link, all I get is "Error". How do I get the test build?
[Galaxy S 4 i9505 Original Android Development] DodoGTA:
Ask [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] fmotta:
[MENTION=4277844]chenxiaolong[/MENTION]

Sorry to bother because maybe it's in the works... Please add Xiaomi Mi Mix (codename lithium) to the supported device list.

Thanks in advance.

Inviato dal mio MIX utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Shanks:
Gummy rom 4.4 working good for me as my secondary rom but slim bean 4.4 doesn't work at all
[Galaxy S 4 i9505 Original Android Development] rlorange:
No no GE4.4... And KT gives me unsupported zip error. .. tried manual patching the extracted boot.img but still no love

---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------

Ooops silly me new patcher version since this morning ok now were in business

---------- Post added at 03:26 PM ---------- Previous post was at 03:01 PM ----------

Still not success with GE 4.4 :(
[Galaxy S 4 i9505 Original Android Development] chickentuna:
Same here. Patching and flashing was fine with jamal's GE 4.4 but I'm stuck on the samsung galaxy s4 screen as well
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ok I'm not alone lol! Out of curiosity which Recovery are you using?
[Galaxy S 4 i9505 Original Android Development] chickentuna:
The latest twrp. Think that was 2.6.3.1 or something like that
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Where can I download Slim Bean 4.4?
[Galaxy S 4 i9505 Original Android Development] lukemo:
Sorry Chen, but I've got errors in patching supersu.zip 1.69 for aosp 44...any hint? Using last 3.1.1 android patcher.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Chainfire changed the format of his updater-script files, so once I added support for SuperSU 1.80, the old ones broke. What you can do is either use version 3.0.0 (on PC or Android) or (on a PC) download this file https://raw.github.com/chenxiaolong...e475de81/patches/Other/supersu.dualboot.patch and overwrite the existing patches/Other/supersu.dualboot.patch in the patcher.
[Galaxy S 4 i9505 Original Android Development] `SBR`:
+1. Patched kt kernel is also not booting up
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
If we use the update function out of the secondary Rom like, CM updater it will not correctly patch, because the files aren't patched right?

Isn't it possible to create a patch environment in recovery which automatically redirects custom Cwm files like mods (themes, battery symbols, etc) into the secondary Rom? Couldn't this be done by making an aroma installer?
[Galaxy S 4 i9505 Original Android Development] Lao Mayer:
Hi all!

Reading through here I found out how to patch a MIUI ROM. I wasn't able to find out how to patch a .zip file that I use to record calls on MIUI. Anyone care to help with this one? Its' name is "phone call record multi lang.zip" and I get an Unsupported file message, as I did for the MIUI ROM zip file.

Thank you!
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ok definitely a patch error I flashed a dual boot patched KT AOSP kernel and the boy animation showed plus dual/data folder created properly with the first install Android files
[Galaxy S 4 i9505 Original Android Development] serverless:
No luck with ge rom by Jamal :( patch and flash Ok, but it doesn't boot.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=244141]Chen[/MENTION] - Thanks for the great work. How can I patch your noobdev 4.4 as a multi-slot1 ROM? I know it has a build in dual boot support, but patching it as a 3d ROM throws some errors in the latest 3.0.1 patcher

Thanks!
[Galaxy S 4 i9505 Original Android Development] velayo:
Trying to patch dandroid 4.4 rom, little minions and lightspeed for multi booting. But I keep getting an error. Is manually patching the only way to go?
[Galaxy S 4 i9505 Original Android Development] Shanks:
There you go master chen

http://xdaforums.com/showthread.php?p=47941835 slim 4.4
[Galaxy S 4 i9505 Original Android Development] rlorange:
[MENTION=244141]Chen[/MENTION] ramdisk must have changed in GE 4.4 patched KT won't boot past the splash screen. I flashed a KT patched for AOSP and the ROM booted to boot animation and bootlooped however it did make /data/dual and first-install files. ..

Hope this helps :)
[Galaxy S 4 i9505 Original Android Development] rlorange:
I managed to extract the rm for system of KT GE 4.4 kernel. Going to attempt to manually patch the folder paths
[Galaxy S 4 i9505 Original Android Development] serverless:
Could you please add support for the miui touchwiz based port? http://xdaforums.com/showthread.php?t=2549966

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] brizzol:
I am using Jamals GE rom and mine has been booting fine, however I have been using it as the primary rom, I can't seem to get it to reboot itself though...Is this due to the lack of a reboot option in the power menu?
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
bumped.
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
[MENTION=4277844]chenxiaolong[/MENTION] hi at first thank you for sharing this cool tool with all of us! i have a elephone p8000 wich is supportet by you if i intall aosp 7.1.1 on as primary and as dual both roms work perfect. if i want to install another ported rom for my device based on the same kernel as primary or dual i get error: failed to copy /raw/data.system.img.tmp to/raw/system. what could cause this problem?

thank you !
[Galaxy S 4 i9505 Original Android Development] Eleo:
I see some errors saying no space left in device. Do you have enough space to flash the ROM? Maybe you need to wipe from utilities rather than dirty flashing? Or choose another slot?
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
thx for fast reply! i decompressed the rom and its about 2 GB but only 1,4GB should be free at primary slot!

what slot should i use u think? i would prefer internal storage

Edit: i installed at data partition right now and it boots up! many thanks to you and have a nice weekend!
[Galaxy S 4 i9505 Original Android Development] Eleo:
If you want to have ROM in internal memory, you have two ways:

1. Free primary slot by wiping it. If you have other slots (datalsot, multislot or extsd slot available), go to that slot and wipe primary (cache/dalvik/data/system, including multiboot files) then try flashing ROM into primary. Since I think you tried flashing primary whike you have another ROM already present. Because if you wiped it, you should be able to flash 2GB ROM into 2.4GB free space.

If you dont want to wipe primary, use 2nd way below:

2. Flash to dataslot. Dataslot uses the internal memory. That is only slot that has enough space to flash 2GB ROM in internal memory other than system (which is only for primary and secondary ROMs). You have 5GB storage available there. But behold that you will also have apps. If all of the apps+ROM will be smaller than 5GB, then use dataslot. If not, then you will need to free space on dataslot (internal memory) by either removing unnecessary files or moving them to external, where you have 9GB free space.

P.S. Dont forget to backup (either from dualboot or by nandroid or simply via titanium backup) before doing anything to not lose important data
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
Backup from dual boot app works fine but how to restore? Or Is this not supported yet?
[Galaxy S 4 i9505 Original Android Development] Eleo:
See.

P.S. Please try to read thread before posting. All the info is already present
[Galaxy S 4 i9505 Original Android Development] kosmasgr:
Excellent​ app :) works flawlessly on my moto g4.

Guys how to flash a zip that uses aroma to my second rom (data slot) ?
[Galaxy S 4 i9505 Original Android Development] Eleo:
1. Patch ROM.zip (and any other zips that will be flashed to same slot)

2. Enter to a recovery that can flash use aroma installer (on note 3, twrp 2.8.7.0 can flash via aroma installer, but newer versions of 3.x cannot, so we have to use 2.8.7.0.)

3. Flash ROM zip via that recovery. Enter aroma installer and flash ROM

The keyword here is to find the recovery that can use aroma installer
[Galaxy S 4 i9505 Original Android Development] kosmasgr:
Sorry I forgot to say that it's a kernel zip with aroma installer. I have already installed the second to data slot.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Does not matter. Any zips having aroma installer have to be patched and flashed via recovery that can handle aroma installer. Like for example open gapps with aroma installer. The zip has to be patched and then flashed via recovery that can handle aroma installer.

Aroma installer does not work outside recovery environment
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
So I have a galaxy s7 edge (Exynos) phone and I am trying to install a custom kernel on my secondary ROM which I flashed to extsd-slot, I keep getting error "Unable to find boot partition, abort" and the whole thing fails.

Do I have to edit something in the kernel manually?

Sorry, here's the MultiBoot.log. let me know if you want it uploaded somewhere else. :)

https://drive.google.com/file/d/0B-1vhaBTqFHXR0ZmSHlwdUEwMkU/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] Eleo:
I am reading what is written on logs:

You are flashing a ROM to primary. ROM size is 2.68GB. I see two issues. Can you comment on these?

1. 32-bit instead of 64-bit - Are you using ROM for your phone model?

2. No space left on device - How much free space do you have on /system? Is it enough to handle 2.68GB ROM?
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
1. Yes I am. The second ROM is running alright. I know it's big but I've install it to external SD card which has 50gb free.

2. Again, the ROM installed fine. The only problem I have is that I can't flash magisk or any custom kernel to secondary ROM because it gives me an error "Cannot find boot partition".
[Galaxy S 4 i9505 Original Android Development] Eleo:
I see. But the log that you shared was not about this flashing. It was about flashing a ROM into primary slot. I searched thoroughly but there is not even one keyword with extsd. Did you flash more than one zip on recovery (or in app)? For ex. if you flashed one more zip after exsd fail it will rewrite the multiboot.log file. It only holds info about last flashing.

Please check again and share the multiboot.log file for extsd.ROM flashing with boot partition error. If youu didbt spare it, try flashing again, get that error, get multiboot.log file and share it directly here before flashing any zip file.
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
Here's a brand new log from the same error I was able to replicate.

https://drive.google.com/file/d/0B-1vhaBTqFHXbHJaSEE5a0ZXV0E/view?usp=drivesdk
[Galaxy S 4 i9505 Original Android Development] Eleo:
Ok. This one is right. Checking
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
Alright.
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
hi now i flashed the aosp7.1.1(1GB) to data slot and would like to flash the xos (2.4GB) to primary the flashing runs without problems but it wont create the boot.img into primary folder is this normal? If i flash to secondary it works perfect

thank you very much vor your help and support!
[Galaxy S 4 i9505 Original Android Development] vxkillswitchxv37:
How do we delete a secondary rom?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Not sure why it doesnt. It has boot.img on primary folder in my phone

Wipe from either dualboot patcher or from dualboot utilities
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
for me dualboot utilities freezes direct after flashing what could i do to get it working? should an error be written to a log file for this?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Reboot to recovery from recovery and try again. Never had such issues. I once flashed a wrong ROM to a slot, so I wiped using dualboot utilities right afterward flashing ROM and flashed correct one
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
after more research i think that my twrp 3.0.2.0 could be the reason because it must have problems with aroma if its related on that my only hope is that somebody builds an 2.8.7.7 with marshmallow partition table
[Galaxy S 4 i9505 Original Android Development] Eleo:
I am using twrp 2.8.7.0 with marshmallow ROM right now if you mean that. Any newer build (twrp 3.x) cannot use aroma installer on note 3