yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Eleo:
Again, no issue on note3. I can backup and replace ROM anywhere the enough storage is available
[Galaxy S 4 i9505 Original Android Development] wawa9292:
yeah... i'm really curious too..

SG S3 was supported, so SG S2 (i9100) is possibly supported..
[Galaxy S 4 i9505 Original Android Development] Eleo:
Have you checked supported devices list?
[Galaxy S 4 i9505 Original Android Development] Andruwok:
Lenovo Vibe Shot z90-7

Support Lenovo Vibe Shot z90-7.Please! :angel:
[Galaxy S 4 i9505 Original Android Development] Eleo:
1. Write in english. Only english. At least use google translator to translate your text (!) Even when answering to this post.

2. Check supported devices list

3. If your phone is not listed, share getlogs.

4. Wait patiently and check updates and changelog
[Galaxy S 4 i9505 Original Android Development] mitch_t:
Author please add support for Redmi note 3 Special Edition (Kate). It's about two minutes for you (just make copy strings for Kenzo and replace on Kate in devices.json file), but will save a lot of time for users. I asked you earlier, but you ignored it. I have to use my own patched version of yours app. It is not good. Make it official.
[Galaxy S 4 i9505 Original Android Development] gaww:
Quote:

Originally Posted by gaww View Post

I have not been able to get backups to work. Is there a guide to using the patcher to make and move slot backups?

Let me go back to ground zero:

I have been away from Duelboot from when the S7's frisr came out, as there was not way to do anything with it on the locked bootloader devices.

I now have a 935f, and have 3 ROMs installed (2 on data slots). I have been trying to figure out the new Patcher backup function - and have spent a few hours going back through the thread to try to find the procedures. I found the earlier ADB procedure, but cannot find the same info for the new in-appprocedure.

If you can point me to it I will try to go on from there.

Thanks
[Galaxy S 4 i9505 Original Android Development] Eleo:
I really dont do anything special. Backup ROM. Open ROMs window, click on flash button, choose backup, select other slot and click flash.

Maybe it is still phone model support related issue.

Same as previous example when webmaster33 told that it is impossible to use exFAT formatted ext.sd card ROMs since chenxiaolong didnt include it and said it is not possible that I could ever do that. It took me a long time to take a ROM, patch, flash to extsd and share screenshots at 1-2 a.m. at night because I had to prove it.

I cant do the backup and flash to other slot now, since it is 10p.m. already. Maybe some other time. But believe my word.
[Galaxy S 4 i9505 Original Android Development] стоичков:
hi guys. i just want to thank in the developers forum of super stock kernel, but it coment that i dont have permission. so thanks you that make super stock kernel and continued update super stock kernel.

So said, now i want to tell, i install multiboot patcher.

1-st i had try install lineageos 14.01 on my 16 gb. sd card and every time i try modified lineage os zip it comment me, failed, so i change it and make it on data and it work, now i have dual boot, but from mobile phone memory.

the next day i received gift of 128 gb. samsung evo, 80 mb. and maybe 20 mb. write and when i try again to make lineage os, it get comloleted, but when i flaah modified flash on 128 gb. sd card in multi boot patcher it give unknown, operation syatem on sd card it give unknown operation system and id i remeber kernel ia unknown. so said this. i restart my samsung and it stop on the samsung boot logo and it freeze there i again flaah others old lineagea versions and again in multiboot it display unknown and again it freeze on on boot.

2. i make another lineagesos ans thia time i flaah it on the phone memory space and bingo this time, it show everything, ot display lineageoa 7.1.1, and the new versions and kernel if i remember, so i wipe the new lineage os and again i try it on the sd card, and again it again didn't show nothing everything in multiboot haa unknown and again when i gry boot from sd card it freeze on samaung s7 logo. The next i start see in multiboot directory and i see that in multiboot/sdcard it dont have boot image, in multiboot directory it only has sdcard directory and no boot images and it is empty. So before that i try to run dualboot patcher in windows it comment me, that it cant find libnet-6.1.dll, i try the same from lineageos 14.0.1 ans again it didnt work from sd card. so olease make it work in sd card and make it work with otg usb. otg card is adapter that i can put usb pendrive in my samsung s7, but i told you i try sd card and it flash modified zip but it dont display and it dont write boot image.

Thanks you too for making this real posaible multiboot patcher.
[Galaxy S 4 i9505 Original Android Development] Eleo:
1. Remove quotation of OP. On XDA you never quote OP

2. Provide logs. For each time. When flashing succesful -> logs. Unsuccessful -> logs. Only after reading those we can reach to a point. From what you say it is not a constant, and changes from time to time...
[Galaxy S 4 i9505 Original Android Development] webmaster33:
To be more exact. There is exFAT support included, but there is some problem with booting from it, at least on my Samsung Galaxy S4 i9505 with Samsung EVO 64GB external sdcard.

Formatting the external sdcard to FAT32 finally made possible to boot from.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Today I tried to patch & flash XXUHPK2 bootloader & modem for my Samsung Galaxy S4 i9505.

However ever the flash was unsuccessful from recovery.

Also reported the issue here:

https://github.com/chenxiaolong/DualBootPatcher/issues/432

Anybody had successfully flashed patched bootloader & modem?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Possible. But I remember you said "exFAT boot problem was not fixed" right after I said I had 2 ROMs on my extsd, which would made me a liar, thus I woke up at 2 a.m., flashed and showed those photos. At least I slept relieved and in peace

:victory::angel:
[Galaxy S 4 i9505 Original Android Development] webmaster33:
There was no doubt, extsd booting works at your Note 3 mobile with exFAT format.

I just said, somewhy it is not working on my Samsung Galaxy S4 i9505 & my Samsung EVO 64GB external sdcard.
[Galaxy S 4 i9505 Original Android Development] gaww:
It is the backup part that I can't do with the app.
[Galaxy S 4 i9505 Original Android Development] Eleo:
You still have issues only with backing up extsd slot as you said earlier, right? You have no issue flashing on extsd slot and you have no issue with booting into extsd slot. Only problem is you cannot back it up, right?
[Galaxy S 4 i9505 Original Android Development] стоичков:
wonderfull. how you make it work to work with sd card. becouse i had 16 gb. sd card ans it wasnt work, after that i receive gift 128 samsung sd card and when i flash modified lineageos it make rom but when i reboot it freeze on samsung logo, the thing is that when patch it on sdcard boot.img dont exist and i said it efore i try dualboot patcher windows and it give libnet6-1.dll not found strange becouse in dual boot there is not libnet6-1.dll but there is libnet6.dll the developers need to see what ia happening. but thanks dor the program.
[Galaxy S 4 i9505 Original Android Development] gaww:
Wrong - gave up on that.

Trying to backup primary with the patcher app while booted in a data app. Something is missing.

Have you backed up with it?
[Galaxy S 4 i9505 Original Android Development] Eleo:
I have backed up many ROMs... Let me remember. Oh yes. Only recently. Backed up dataslot from primary and then primary from dataslot
[Galaxy S 4 i9505 Original Android Development] gaww:
Did you use the patchet app only ? That is what I am trying to do.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yes.
[Galaxy S 4 i9505 Original Android Development] malybru:
Mod Edit

Thread cleaned

May I remind everyone that this is a Development Thread

Please keep all discussion on topic

Thank you

malybru

Senior Moderator
[Galaxy S 4 i9505 Original Android Development] gaww:
I think I have an mbtool issue - patcher can't locate it.

///
[Galaxy S 4 i9505 Original Android Development] стоичков:
hi guys

i have time and i will upload the logs that i read they are necesary to dualboot patcher work. i upload all the logs, but therr haa 2 logs that xda developers haa put limit on logs and maybe this 2 logs that has been more than 6xx kb. they didnt upload, xda developers need to do no limit on upload, becouse there have peoples who dont know hkw to edit logs and send them, if xda developers want tge logs to be no more fhan 500 kb. in upload then xda develpers need to speak with developer of dual boot and tell him to limit the program log on 500 kb. but this is inbuman, becouse how you gonna live if governments and militarry limit your life xda developers.

im uploading too what dualboot patcher comment me.
[Galaxy S 4 i9505 Original Android Development] gaww:
I have two patched data ROMs, and when I update them and/or the primary, I always update ramdisk, and then the mbtool status indicates it has been updated. But when i try to backup - I get the a quick failure indicating it can't find mbtool.

I should add, all my ROMs are nougat - have you backed nougats up or only MM?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Only MM:o Sorry
[Galaxy S 4 i9505 Original Android Development] gaww:
That may be the issue.

I think Chen has a 935F, and he has done work with it (A MOD to change 7.0 ROMs to US Tmo CSC - I have used it on some International ROMs on my 935f). I like many others are waiting on his return after he is done with his special project (and hoping it is a success for him).

Has anyone been able to backup 7.0 ROMs with only the Patcher APP ?
[Galaxy S 4 i9505 Original Android Development] Helloworld294:
Hey guys, I get update error:1 when flashing patched secondary ROM. My primary ROM is the latest TW Nougat based.

Galaxy S7 Edge phone.

Logs: https://drive.google.com/folderview?id=0B-1vhaBTqFHXOXVEZ0tKaVRCRU0

Wasn't sure which file is needed so I put all three logs in one folder.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Wow. Just flashed a ROM into extsd and tried to back it up. It is same as you said, no mbtool connection + I cant access sdcard from extsd ROM (this one is possibly ROM issue).

But I swear I did backup my extsd ROM before...

Sorry dude, it is possibly lost somewhere after updates.
[Galaxy S 4 i9505 Original Android Development] gaww:
Was this Rom nougat or mm?

The latter usually works. All the Roms I tried on ExtSD were 7.0 and they couldn't access it so that's why I gave up on them.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Nope. It was MM. I troed even updating app version from 188 to 199 from both primary and extsd slots. But no, on primary slot it force closed dbp, on extsd slot it stayed on dualboot log screen saying mbtool connectin lost (or not found smth like that dont remember)

But I have done it in past:confused: When did it broke?
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
Ok so the dual boot works on my Verizon lg v20 (995s) which is awesome, however I had one small issue. I successfully installed and switched to the secondary rom, however when returning to my primary rom, my 4 digit PIN code no longer worked. I wiped and reflashed everything, this time with no lockscreen security, and everything works fine. Any solution to this odd little quirk? (And I used the same pin code on both ROMs, in case anyone was wondering. )
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Again the extsd support problem...
[Galaxy S 4 i9505 Original Android Development] FlatOutRU:
Please add Mi5s to program!
[Galaxy S 4 i9505 Original Android Development] Eleo:
Please share logs as explained here

Mi5 and Mi5s plus are supported.
[Galaxy S 4 i9505 Original Android Development] gaww:
I couldn't back up 7.0 on data or primary slot - mbtool not found.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I tried backup primary whilst being on primary, it force closed. Will try on dataslot too
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. Please add support for Lenovo P2 (p2a42). Thanks.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Hello. Long time no see:D

Still going for most ROMs flashed record?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hah, may be I changed the phone. Still the DualBoot Patcher is my favorite app on my phone. :p
[Galaxy S 4 i9505 Original Android Development] gaww:
I didn't think backing up a ROM while it as booted up would work ?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Tried to backup data from primary, still force close. Will try to backuo primary from dataslot. That is the last combination/permutation I can make in mind

:D

Edit: Same. It crashes when trying to backup primary from dataslot. Maybe I should try installing older app versions? They are still in my dowbloads folder

:confused:
[Galaxy S 4 i9505 Original Android Development] gaww:
Maybe - or unfortunately it may be a 7.0 problem, although Chen had done a fair amount of work with 7.0. So trying an older version just to check would make sense.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I still am using MM and it was working on MM. That is my concern. I never used Nougat.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
As [MENTION=4277844]chenxiaolong[/MENTION] seems busy these days I successfully modded the app and currently working fine on Lenovo P2 which is not yet supported.

[MENTION=4598795]Eleo[/MENTION] A bunch of custom roms appeared yesterday for my phone, I'm aiming again for the gold medal for most roms installed which I doubt someone took from me. :p
[Galaxy S 4 i9505 Original Android Development] Eleo:
Dont think it is possible to pass 8 ROMs:D

I can have at most 3 ROMs, where 2 of the ROMs are on extsd. TW weights much heavier, but I like it more than AOSP. And I have about 6-10 GB system data per each ROM

:o
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I think there is no need for so many roms installed. I think I'll stick with 3 or 4 max this time.
[Galaxy S 4 i9505 Original Android Development] farovitus:
Please fix s7 edge not booting when installing rom on extsd slot
[Galaxy S 4 i9505 Original Android Development] gaww:
You have any ideas on backups with the APP. You have a data slot 7.x - maybe give it test.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes, I tried backups of 7.x roms in the past , they were working fine. I'll try with that one too.

An Update to my post:

The backup worked fine for LineageOS 14.1, but the restore was problematic.

Using the r201 build it refused to restore to secondary and multi-slot, but succeeded restoring to data-slot. I took a screenshots for you to see the exact errors also captured the successful restore. Log attached as it may be useful for [MENTION=4277844]chenxiaolong[/MENTION].

Legend:

1st shot restore to secondary​ failed.

2nd shot successful restore to data-slot

3rd shot restore to multi-slot failed
[Galaxy S 4 i9505 Original Android Development] gaww:
I have had no luck in even doing data or primary backups at all. I will try the 201 build - latest was 199.

Update

I changed the backup path and it worked
[Galaxy S 4 i9505 Original Android Development] Eleo:
Thanks for update.

Will try 201 too tomorrow
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Are you guys sleeping? You were not using r201 and even this is not the latest build. r205 is the latest. :p

btw I doubt the patcher version has some effect here if you were already using some of the r1xx builds at least. Changing the path is the key.
[Galaxy S 4 i9505 Original Android Development] Bearthquake:
Hey all. I've tried searching for this for a little while and got nowhere.

Is it possible to patch a twrp backup and install it as a secondary? You could do this with multirom I know, but multirom is having lots of issues for my phone right now so I've moved to this.

Anways, can you?
[Galaxy S 4 i9505 Original Android Development] gaww:
I using latest one.

Now I have a backup (on external sd), but the patcher doesn't see it when I select recovery from in app flashing, and it doesn't let me select the location where it is, so how do I access it?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Sounds like a extsd permission issue to me, try to move the backup to internal storage. My backup is also on extsd, but I'm able to select it.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
I was able to backup and restore a Nougat los-based rom from and to data-slot. My backups are stored on my extsd.

Does somebody know if DualBootUtilities is compatible with TWRP 3.1.0 ?
[Galaxy S 4 i9505 Original Android Development] Hereiwas:
What DBP version are you using?
[Galaxy S 4 i9505 Original Android Development] gaww:
For some reason my patched app in flash mod will not open when I select recovery so i can't select anything but it does when I select flash. I may be missing something in settings.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Yeah, forgot to write it down : r185
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
So I was kind of forced to install twrp 3.1 on my klte, and can confirm dual boot utilities flash make twrp reboot. Here is what log I could grab, I read that aroma installers had to be updated, but the issue seems not to be on all devices.
[Galaxy S 4 i9505 Original Android Development] IacobIonut-DW:
I want to Request Official Support for

Allview V2_Viper_X , code name : V2_Viper_X

MTK : MT6753 64BIT

kernel : 3.18.19 MM Base

Base directories:

/dev/block/platform/mtk-msdc.0/by-name

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name

/system block devices:

/dev/block/platform/mtk-msdc.0/by-name/system

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system

/dev/block/mmcblk0p24

/cache block devices:

/dev/block/platform/mtk-msdc.0/by-name/cache

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache

/dev/block/mmcblk0p25

/data block devices:

/dev/block/platform/mtk-msdc.0/by-name/userdata

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata

/dev/block/mmcblk0p26

Boot partition block devices:

/dev/block/platform/mtk-msdc.0/by-name/boot

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot

/dev/block/mmcblk0p7

Recovery partition block devices:

/dev/block/platform/mtk-msdc.0/by-name/recovery

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery

/dev/block/mmcblk0p24

Extra block devices available for flashing:

/dev/block/platform/mtk-msdc.0/by-name/metadata

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata

/dev/block/platform/mtk-msdc.0/by-name/nvram

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram

/dev/block/platform/mtk-msdc.0/by-name/lk

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk

/dev/block/platform/mtk-msdc.0/by-name/logo

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo

/dev/block/platform/mtk-msdc.0/by-name/para

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para

/dev/block/platform/mtk-msdc.0/by-name/tee1

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1

/dev/block/platform/mtk-msdc.0/by-name/tee2

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2

/dev/block/platform/mtk-msdc.0/by-name/uboot

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/uboot

/dev/block/mmcblk1

/dev/block/mmcblk1p1
[Galaxy S 4 i9505 Original Android Development] Dan0v:
removing dual boot patcher with all roms only primary in original condition "nothing patched like kernel also"

using DualBoot Utilities erase data for all other ROMs and then to disable duelboot, then if i kept an nand backup of my primary "non patched" and restore it .. dose it work fine ?

thanks
[Galaxy S 4 i9505 Original Android Development] gaww:
It should if you have a good nandroid
[Galaxy S 4 i9505 Original Android Development] gaww:
I have played around some more, and have done the following:

I mad a backup of a data slot into an ExtSD multioboot/ExtSD-slot-"name" folder. It then showed up in "Add backup" option on In-app flashing. I restored to a different named slot to see how it worked, and it appeared as a new ROM and opened OK.

I tried to then restore it to an ExtSD slot, but the backup no longer appeared in "Add backup"

I backed the ROM up again, and then it again showed up in the above. Tried restoring to ExtFD, but halfway through it failed. Looked for the backup again, and it did not longer appear in "Add backup" - but the file was still there.

So in my case, it looks like I can only use a backup once (strange), and restoring to ExtSD doesn't work.

As it is noted in the APP - it is experimental, and hopefully Chen at some point will find some time to work on it, as it could be very useful tool.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
I'm trying to root secondary ROM (resurrection remix) that recently changed to magisk root. I had to use a boot image prior to this change in order for it to boot but in the process obviously magisk root is removed. I tried patching and flashing the lineage root package but it won't boot that way. Any idea what I can do to regain root?
[Galaxy S 4 i9505 Original Android Development] Hereiwas:
Wich version of rr? i'm using RR Nougat 7.1.1 by LordEko ,just patched Magisk v11.1 ( file zip) and flashed
[Galaxy S 4 i9505 Original Android Development] FlatOutRU:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. Please add support for Xiaomi Mi5s (Capricorn)

Btw how can i do it by myself/ what shouild i modify to make app working?
[Galaxy S 4 i9505 Original Android Development] egoiste87:
Please make support for n7100 dual patcher t03g
[Galaxy S 4 i9505 Original Android Development] tavocabe:
RR 5.8.2 for G5 h830 by [MENTION=5195210]gwolfu[/MENTION]. I already tried that with magisk 11.6 and couldn't boot either, it vibrates 3 or 4 times and boots back to TWRP. I think somehow flashing magisk to secondary messes up the boot.img needed to boot the secondary rom. Couldn't have root in this secondary rom since it change to magisk root. I'm using ExtSD with it but I don't think that's the reason it won't boot.
[Galaxy S 4 i9505 Original Android Development] Hereiwas:
I have RR as secondary rom ( data slot) and as i said i had no problems to flash Magisk. I have also Lineage OS nougat by Christer12 as third rom (ext-sd) in wich i use SuperSu. You can try to flash SuperSu, here is 2.79, instead of Magisk ...
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Something in your setup is messed up it sounds like. I'm on the mobile h830 and use RR, LOS and fulmics stock based ROMs and root works (including magisk) without any issues no matter what rom is first or second. You do not need to do anything with the boot.img. RR for our device had magisk built in. All you need to do is patch your RR zip and gapps, install rom them gapps and all is good. Also, do NOT flash ROMs as secondary. Flash your secondary roms under data slots or ext SD slots (which I posted in the dual boot thread for our device). Pretty much secondary doesn't always work that great on our device mainly due to low space I believe. I personally only use data slots for secondary roms but ext SD would work as well.
[Galaxy S 4 i9505 Original Android Development] tavocabe:
Well I guess something is messed up then as I can't boot LOS neither if I flashed the LOS root zip. I have Fulmics 1.7 as primary and LOS and RR both in ExtSD. They were working perfectly before RR went magisk. Will try to start with a new fresh install I guess and see if it now works. Do you use the app built-in flash utility or flash with TWRP?
[Galaxy S 4 i9505 Original Android Development] gaww:
Flash with twrp unless it is a duelboot backup restore - which I finally figured out.