yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Sorry about not being able to get logs earlier busy with holidays. Anyways when I tried to flash stock ROM now it always is failing saying tmp/laf.img had failed verification. Not sure if am older version would work because it used to allow me to flash stock as a secondary ROM (data slot) but just would boot back into primary rom, now it won't flash stock at all. But flashing cm based Roms work without issues. I do know that when three g5 was updated to Android 7.0 the bootloader was changed and maybe positions as well? So, I included the multiboot.log and the getlogs output. If you get a chance to take a look at this, thank you.

[MENTION=4277844]chenxiaolong[/MENTION]

Edit: After reviewing the multiboot.log file and device paths some device paths and names were changed after upgrading to android 7. Instead of just "/dev/block/platform/624000.ufshc/by-name" it's now "/dev/block/platform/soc/624000.ufshc/by-name" and some fine names have also been changed. If everything is not in the log files I uploaded please key me know and let me know what exactly you need and I'll get it for you.
[Galaxy S 4 i9505 Original Android Development] aditia581999:
anyone know how to flashed xposed for secondary rom?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
can you please provide me a link for the 158 version? that version works best for my device. tyvm

nice job btw!!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I found out that the hang at boot on various roms was caused by SuperSU System Mode. I have no problem with the systemless version. It was scary, all my roms refused to start due this issue. Thankfully I flashed the normal SuperSU to primary and now I'm good.
[Galaxy S 4 i9505 Original Android Development] GianNet:
Hello [MENTION=4277844]chenxiaolong[/MENTION]

Can u add the codename 'hero2lte' in Samsung Galaxy Note 3 (Snapdragon) ?

When I try to click on "Set kernel" it says: "could not determine the boot partition because this device's codename 'hero2lte' is not recognized". I already tried to change the values in build.prop without effects..

Thank u so much for your work! :)

View attachment 20161228.134400.tar.gz
[Galaxy S 4 i9505 Original Android Development] Eleo:
Note 3 is present. Hero2lte is s7edge :rolleyes: change your device model back to note 3 in build.prop.
[Galaxy S 4 i9505 Original Android Development] GianNet:
Eleo, I'm actually using a custom rom on my note 3, based on s7edge (Darkwolf 8.5v)

What should I do to have no problems with my rom?

Thank u for your help!
[Galaxy S 4 i9505 Original Android Development] Eleo:
I have used s7edge port and note7 port ROMs (on MagMa note7 port right now) with dualboot and havent had any such issues. It works as expected and my device is accepted as note3 in dual boot patcher app.
[Galaxy S 4 i9505 Original Android Development] Antidote03:
hello there

first thing i want to thank the dev for this awesome app its really sweet

just have 1 question hopefully some one can help me

Device: International lg g3 model(D855) 32GB

custom recovery :TWRP 3.2.0.0

primary rom : stock based rom (FULMICS 6.7 )

secondary rom : t ResurrectionRemix (cm13)

Installed latest version of DBP & Updated the ramdisk everything went fine

patched the second rom in data slot ResurrectionRemix (cm13) flashed fine too

Boot-UI working fine

my problem started here when i want switch from secondary to primary I see secure boot error like this picture

i fixed this by flash the image inside multiboot folder boot image before ramdisk update

log attached View attachment 20161228.102602.tar.gzmaybe this can help

thanks in advance
[Galaxy S 4 i9505 Original Android Development] aditia581999:
Hey, have some question

If i want to flash something, that should be patched right? So my question is , is it required to patch supersu or some mods to install it on my primary rom? Thanks :laugh:
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Yes if your zip has wipe command. Not necessary if otherwise.
[Galaxy S 4 i9505 Original Android Development] aditia581999:
Thnks for the answer ! But maybe im feel a liittle safer by just patching it :silly:
[Galaxy S 4 i9505 Original Android Development] Araltd:
Well obviously I don't know what I'm doing? I can't get to step 1. After installing the app and clicking primary rom, it says can't identify kernel or anything.

I looked for a log file, but didn't find one? But on the other hand the app didn't do anything except launch. Clicking anything I see that popup.

Edit: I'm on a Tmobile N910T running a note 7 ported rom

Sent from my Samsung Note 6
[Galaxy S 4 i9505 Original Android Development] clewis.it:
Add this line to the end of /system/build.prop

ro.patcher.device=trlte
[Galaxy S 4 i9505 Original Android Development] Amh00200:
Hello , thanks dev for this useful App

I face a problem i tryed to install Cm14.1 on data slot and External Sd card , but it failed

The App pached the zip file successfully but it failed to install it

The primary Rom is TW 5.0.2 Custom rom

Device Note 3 : ha3g

I attached a screenshot and multiboot log

Sorry for my bad English ?
[Galaxy S 4 i9505 Original Android Development] kevinseeger:
Just a quick thanks!

Ive been wanring to dual boot since way back when, when i had my HTC Incredible! So much work, so many features and so many devices supported!

Dev, you're awesome. Thanks

(Donation link or page?)
[Galaxy S 4 i9505 Original Android Development] Killerdog:
same here. with your test build i can patch and flash the rom, but when i try to switch to new rom it can't set me the permission to boot it.
[Galaxy S 4 i9505 Original Android Development] :
Plz add Lenovo k4 note support if possible??? it's already out for k3 note running on mtk6752
[Galaxy S 4 i9505 Original Android Development] Eleo:
Did you provide logs? No logs no support. If you have already provided them, wait for response from developer.
[Galaxy S 4 i9505 Original Android Development] :
No i am talking about k4 availability Dual boot patcher is not available for k4 for now can the Dev add Dual booting for k4 too means a new device in compatibility list
[Galaxy S 4 i9505 Original Android Development] Eleo:
If you dont provide logs dev cannot support your device. To know how to provide logs at least read last 10 pages of thread for all the hard work that dev does and the users who help maintaining the thread. Dont wait for spoonfeeding.

Cheers
[Galaxy S 4 i9505 Original Android Development] :
Deleted
[Galaxy S 4 i9505 Original Android Development] :
I think now the Devs will able to make a test build for my Lenovo k4 note ???

Logs attached [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Eleo:
Try to edit your early post with gdrive link as "deleted" or "..." to not have double posting.

Cheers
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
Anyone able to backup up ROMs loaded on Extsd slots? I can get all partitions except for system.

Roms in the Primary and Data slots are backed up OK.

Here's the error I get when trying a ROM on Extsd...

View attachment 3988468
[Galaxy S 4 i9505 Original Android Development] Sachuan:
I patched a Dirty Unicorns 7.1.1 zip for Xiaomi Mi5 (Gemini) and when I tried to flash it it just failed

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] Sachuan:
Here's a picture it you need.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hi, here is a problem with /cache and /system partitions.

[MultiBoot] - /system: /cache/multiboot/multi-slot-1/system

[MultiBoot] - /cache: /system/multiboot/multi-slot-1/cache

[MultiBoot] - /data: /data/multiboot/multi-slot-1/data

So you need to wait for chenxiaolong :)

Btw HAPPY NEW YEAR ALL :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Back from vacation! Hope everyone had a happy New Year :)

I will be getting back into the DualBootPatcher stuff sometime this week.
[Galaxy S 4 i9505 Original Android Development] Sachuan:
OK thanks you for the response :)

Happy new year!

(Maybe it's related to my /data and /cache being f2fs?)
[Galaxy S 4 i9505 Original Android Development] kopitalk:
I think it's due to the fact that you're using multi-slot which is trying to install your rom /system in cache partition. Try using data-slot instead. Read OP for explanation.
[Galaxy S 4 i9505 Original Android Development] Sachuan:
I'll try and report.. Thanks:good:
[Galaxy S 4 i9505 Original Android Development] Sachuan:
Didn't work..
[Galaxy S 4 i9505 Original Android Development] kopitalk:
I'm sorry I don't know what's wrong, maybe the dev can look into this. Btw is your phone even rooted?
[Galaxy S 4 i9505 Original Android Development] Sachuan:
Yeah, lol

But app never asked for root permissions...
[Galaxy S 4 i9505 Original Android Development] CaioFerreira:
I can't install gapps on secondary CM rom... flashed the dual.zip, but no success. Any help?
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
If you have done by TWRP, send recovery.log. If by the app itself, send /sdcard/MultiBoot.log
[Galaxy S 4 i9505 Original Android Development] mattan1999:
Is it possible to install the Boot UI on SM-G935F (S7 Edge)? :)
[Galaxy S 4 i9505 Original Android Development] haax:
I can't flash RR on S7 as secondary, could someone tell me what Im doing wrong?

Multiboot log file, cant attach it through Tapatalk:

http://www31.zippyshare.com/v/OSbgu1FG/file.html
[Galaxy S 4 i9505 Original Android Development] mattan1999:
This is a bug with s7, you can only install it to the Data or Extsd slot :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
It's not a bug, it's the space (not enough space)
[Galaxy S 4 i9505 Original Android Development] Eleo:
Secondary flashes to /system

Multislot to /cache

Before flashing anything check the free space available from within the dualboot patcher app. It needs 2.3GB free space for system image in that location. If you dont have enough space it won't be able to flash it. Use data slot (into internal storage) or extsd slot (into external sd card) if you have enough space there.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. I'm having hard time trying to restore a backup to extsd-slot. It's not working for me. If I use the 9.1.0.r69 it's failing with error "/mb_mnt: Failed to create directory: Read-only file system". Looking at the log it says:

01-05 11:27:23.506 30023 13049 W GetRomDetailsTask: mbtool command error
01-05 11:27:23.506 30023 13049 W GetRomDetailsTask: com.github.chenxiaolong.dualbootpatcher.socket.exceptions.MbtoolCommandException: Failed to get directory size for /raw/cache/multiboot/extsd-slot-sd5/cache: Success [errno = 0]
01-05 11:27:23.508 30023 13049 W GetRomDetailsTask: mbtool command error
01-05 11:27:23.508 30023 13049 W GetRomDetailsTask: com.github.chenxiaolong.dualbootpatcher.socket.exceptions.MbtoolCommandException: Failed to get directory size for /raw/data/multiboot/extsd-slot-sd5/data: Success [errno = 0]

If I use the old 9.0.0.r71 build the restore is successful, but then it just hangs on the logo at boot. Tried to update the ramdisk, but nothing changed. By default the patcher creates 2.5GB system image, but when restoring 1.5gb is created. One rom is failing due to insufficient space on the restored img, but for the most of my roms 1.5gb is enough for the /system. If I try to flash the zip for the same rom over the restored backup e2fsck fails to check the image and according to the log it's complaining that double the inodes present on the actual system image were expected.

The strange thing is that I successfully restored a backup for some 7.1.1 rom the same way and it works. Now I have 1.5gb system.img for that rom.
[Galaxy S 4 i9505 Original Android Development] farovitus:
I flashed rr as secondary rom , you only need to have enough space in system ( i think 1.2 gb free space is enough )

Tw & rr working great !
[Galaxy S 4 i9505 Original Android Development] gamesz2:
Yes its possible works for me
[Galaxy S 4 i9505 Original Android Development] honey216:
secondary rom not boot

:crying::crying: please anyone help me to solve my problem i am using redmi note 3 sd variant and i want to patch rr rom but i am faicng some problem after install the secondary rom i done every steps perfectly to install secondary rom i also choosed data slot and space not a matter phone have enought space but after succesfully patched secondary rom when i rebbot on my secondary rom a mi logo appears and after that phone vibrates five 5 times and automatically goes into recovery i also tried utilities and flash boot img but nothing happened then i go back to my first rom using utilities please solve my issue its my my humble request to all of you how can i install my second rom
[Galaxy S 4 i9505 Original Android Development] Eleo:
If you are sure that you phone model is supported,

Did it say successfully flashed? Did you flash from in-app or recovery?

I had that 5 time vibrate thing when I wiped data slot 1 and tried to boot into data slot 1. So it seems it wasnt flashed successfully.

:confused:
[Galaxy S 4 i9505 Original Android Development] welder73:
Hi guys,I would like to try one rom with f2fs support but I'm using Dual Boot Patcher to try roms on the second slot,I wanna keep my stock intact.

But then I can't format data&cache to f2fs with Twrp because it will be applied to stock rom,right?

Is there some way to do it? :confused:
[Galaxy S 4 i9505 Original Android Development] honey216:
Thanks bro for your reply offcourse bro my device codename kenzo is supported dualoot patcher and i flashed sucessfully my secondary rom through app the probelms start only when i reebot my phone into secondary eom
[Galaxy S 4 i9505 Original Android Development] guraki:
Can we make twrp work again without data format after uninstalling dual patcher?
[Galaxy S 4 i9505 Original Android Development] clewis.it:
Hi. I am trying to install a touchwiz rom on my note 4 in an ext slot, but it keeps failing. I know the device can support it because AOSP roms install to ext slot just fine. The rom installs and runs in a data slot just fine also. Can anyone tell me what is needed to successfully install it in an ext slot?
[Galaxy S 4 i9505 Original Android Development] cheuri:
was working perfectly but now it's giving me a errors

device redmi note 3

I have installed 3 to 4 custom roms before. didn't got any problem switching the roms . but yesterday I updated my phone but after that also it was working but later while installing the new rom it was not installing was stucked on the same installing screen for more than 15 mins and gave the error. and about installed roms while select the rom and restart it's not booting to the rom which I want to switch .it's vibrating 4 times and booting to recovery.

log file is attached
[Galaxy S 4 i9505 Original Android Development] :
Any test build's ??? [MENTION=4277844]chenxiaolong[/MENTION] I am still waiting...

Logs are at page 1095
[Galaxy S 4 i9505 Original Android Development] honey216:
PLease anyone solve my problem i request to all of the expert expert here
[Galaxy S 4 i9505 Original Android Development] ~N.A.W.Y~:
Is there anyone managed to dualboot AOSP with MIUI as primary rom?

I tried so many ways but all I'm getting is 5 vibration bootloop.
[Galaxy S 4 i9505 Original Android Development] Eleo:
It maybe the issue that [MENTION=7939424]honey216[/MENTION] is having... maybe miui should not be primary:confused:
[Galaxy S 4 i9505 Original Android Development] ~N.A.W.Y~:
I never tried that. Gonna try it tomorrow and report back :good:
[Galaxy S 4 i9505 Original Android Development] Gadhavi1010:
Plz add support for Lenovo k4 note (Lenovo A7010a48) it is an mtk 6753 running device and about logs i attached it plz plz plz... Even k3 note has support then why k4 can't have

Anyone plz reply
[Galaxy S 4 i9505 Original Android Development] Russiamen:
[MENTION=4277844]chenxiaolong[/MENTION]

There are some issues with Asus Zenfone 2(Z00A/Z008).Because of the transition to the new bootloader 6.0 we have gone the way of unlocking ,and we use the kernel signature ,and since you need to update the ramdisk ,this signature flies,could you add this functionality to Z00A/Z008,or tell us how to do it.If the archive signature will attach to the post.
[Galaxy S 4 i9505 Original Android Development] bolt1502:
How to add Doogee x5 Max Pro project?
[Galaxy S 4 i9505 Original Android Development] Mulham82:
Dears,

I have a problem while booting as second ROM "5 Times Vibration & then Boot into TWRP".

Note, the device is Mi5. The primary ROM is MIUI 8 v6.0 and the second ROM is custom ROM such as (Lineage, AOSCP ..).

Thanks.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Have you tried it? If yes, that should be what these guys are missing.
[Galaxy S 4 i9505 Original Android Development] monkteo:
did you update ramdisk (both rom primary and secondary) after patch rom and install but before to change rom ?
[Galaxy S 4 i9505 Original Android Development] yfriday14:
I also have the "can't boot" & 5 vibration TWRP problem since 2016. december. I saw from the logs, that the latest version of the Dual Boot Patcher doesn't find the external sdcard on my Samsung Galaxy S4 i9505 jfltexx. I posted earlier the logs about it:

https://xdaforums.com/showthread.php?p=70092925

The problem arised around version 9.1.0r56 or r65.

Earlier versions had no such problem. Maybe [MENTION=4277844]chenxiaolong[/MENTION] will be able to debug the problem based on the earlier posted log.

Reflashed stock rom until the bugfix.

There are too much 5 vibration TWRP problems nowadays, so maybe they are all related to the same bug.

Waiting for fix.
[Galaxy S 4 i9505 Original Android Development] sbcrumb:
I patched and installed ktoonz which is the lokied kernel. I tried to patch Loki doki to flash but said it is not a valid file. Where can I get a patched Loki doki?
[Galaxy S 4 i9505 Original Android Development] coolnessQ:
Lol, have patched probamrom, installed correctly and now it reboots secondary and primary into samsung stock -.-' have the dualboot switcher and tried the recovery one.
[Galaxy S 4 i9505 Original Android Development] Addiso:
Just flash, no need to patch and I've had problems with the latest ktoonsez aosp kernel; try the 11-8 one.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll need a couple hours at least until I can work on fixing the issues in 3.0.0. T-Mobile just released the MK2 update (which I half-upgraded to) and unfortunately, the bootloader is locked :( I need to revert my phone back it how it was earlier.

EDIT: Those having issues with SuperSU 1.80, just download this file https://raw.github.com/chenxiaolong...87b4c2de/patches/Other/supersu.dualboot.patch and replace patches/Other/supersu.dualboot.patch in the patcher.
[Galaxy S 4 i9505 Original Android Development] Tunasty:
Hopefully you can revert your phone back bro
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
You have to flash the loki dokie zip after the patched kernel
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Got it back :) Good thing I didn't update the bootloader. I odin'ed MDL to get back the other partitions and everything is good now.
[Galaxy S 4 i9505 Original Android Development] gaww:
Great to hear Chen - having you dealing with a locked bootloader would have been bad for everyone.

I was anticipating this based on the international devices - guess you were too, as you stayed away from the bootloader. Samsung can take their knox and put it where the sun doesn't shine !

Unlike the EU, where consumer laws prevent voiding warranties only due to flashing custom software, the US laws have tended to favor the manufacturers over consumers - just goes to show you what some well targeted campaign contributions and lobbying can do.

Thanks to the development community, we can experience most of the benefits of updated software without having to put up with the locked down factory software. Even with all the options on the international side, seeing most of the issues being (just go the Omega thread) dealing with modems and other firmware issues, who needs it? I fail to see much benefit with the updated OTA software. Even with the now ancient unlocked 4.2 factory firmware and modem - have had good radio reception and good WiFi performance and very few problems.

So back to work Chen - lets see how much fun we can have with multiboot while this OTA crap is getting sorted out.
[Galaxy S 4 i9505 Original Android Development] coolnessQ:
Can someone help me?

I have stock 4.3 MJ7 TW rom rooted philz recovery etc.

Patched Probam Rom via the patcher apk. Installed the rom and when switching to second it boots up TW primary TW also... but the files are correctly done have followed the OP tutorial, etc but it still dont work. When trying the dualboot app and choose to switch to the second rom it shows that i have to reboot when done it reboots to TW, also when using the recovery one its still keeps rebooting to TW, idunno if i can remove the rom now since it keeps rebooting to TW...

Anyway to fix this?
[Galaxy S 4 i9505 Original Android Development] Bejda:
What I would do first is set (again?) current kernel as primary with dual-boot switcher app while on your TW primary rom>flash again your patched Probam zip,reboot system now should boot to secondary (as it did the first time you flashed your patched Probam zip yeah?) and then maybe once under secondary rom set its kernel as secondary just in case of before trying to switch rom's.
[Galaxy S 4 i9505 Original Android Development] Gotcher:
I have a pretty strange problem with losing the rooting rights when booting into my secondary ROM. Even re-installing with SuperSU doesn't work anymore (it did work one time, but not anymore)...

My first ROM is OMEGA 16 (http://xdaforums.com/showthread.php?t=2253528)

My secondary ROM is the latest nightly of vertigo's PAC man ROM (http://xdaforums.com/showthread.php?t=2295673)

What is the problem here? Can someone help me?
[Galaxy S 4 i9505 Original Android Development] Bejda:
SuperSu 1.80 seems to be under discussions at the moment,see thread there: http://xdaforums.com/showthread.php?t=1538053

Not sure if it's of any help for anyone but yesterday i had to flash SuperSu cwm zip on my i9000 running CM11 build and loosed root,the first easy way I found to get root again was to go under SuperSu app settings untick/tick again enable SuperSu (never had such issue before,always installed SuperSu through cwm).

One having SuperSu problems on secondary Rom may try to reproduce about the same steps:

First patch it using the additional file given by Chenxiaolong a few posts before.

Flash it for secondary system.

Do the untick/tick trick if root issue.

[MENTION=2121449]Gotcher[/MENTION],

I guess such issue happened before or at least was reported by someone using Slim rom in the past maybe the issue (if exists) occured again now on PAC dunno..you may find some infos searching thread with keywords like "lost root,secondary,Slim" and such.

You installed SuperSu through market or cwm (which version btw)? If through market you may try to patch 1.80 like I said above or flash this 1.65 secondary rom version https://app.box.com/s/eg12ywh4sj7012ijndsi
[Galaxy S 4 i9505 Original Android Development] coolnessQ:
It somehow dont work but thnx for helping me :(
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
if I want to change the second ROM how do I do a full wipe?
[Galaxy S 4 i9505 Original Android Development] Shanks:
Hi, does anybody know how to switch to the 3rd rom? Thanks in advance guys.
[Galaxy S 4 i9505 Original Android Development] respider:
anyone here using omega as primary?

to update it only thing I need to remove from updater script is this line?

delete_recursive("/system");

leave all the rest, including mount sysyem etc?
[Galaxy S 4 i9505 Original Android Development] Bejda:
That's about it yeah, don't forget to wipe primary system using dual-boot utilities zip just before.

You could upload the updater-script by here so all could have a look if you want.