yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Leone/kyleproxx:
I just saw you on the s7 forums and I wanted to ask if you were able to unlock the bootloader
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
Only one person has responded to that thread. But it appears I did. However a few hours later I severely broke the screen so I can't do anymore testing until I get it fixed...if I can.
[Galaxy S 4 i9505 Original Android Development] Leone/kyleproxx:
Can you tell me the process you used to get it to say bootloader is already unlocked
[Galaxy S 4 i9505 Original Android Development] greeneyez15o:
Anyone get this working on Nexus 6, or 1Plus5t ? I must b doing something wrong, and I followed step by step directions... Thanx
[Galaxy S 4 i9505 Original Android Development] royeiror:
I'm a total noob, but I'd like to give it a go to make a port for the Moto Z2 Play, does anyone know where I could start reading up?
[Galaxy S 4 i9505 Original Android Development] cd716:
https://xdaforums.com/android/software-hacking/guide-dualbootpatcher-build-source-t3663076
[Galaxy S 4 i9505 Original Android Development] royeiror:
Thank you. It looks like a mildly complex process, but nothing extreme. I'll give it a go ASAP
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
Hi. Ive just installed a second rom (viperOS) to xiaomi mi5s. Primary rom is Masik UI 2.3 based on miui 10. The problem is I can not share apps between roms, also i can't install any large games that store their cache in android/obb. When downloading from play store it reaches 100% and begins again. Also tried to backup with titanium and restore on second rom, but it doesnt allow to copy/paste cache to android/obb. Any ideas how to solve that issue? Thanks a lot.

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] consumimur:
hello every one . i have a meizu m6 note device running MOKEE custom rom . i want to dual boot RR rom .i sucecfully patched the rom and gapps for installation into the system patition.the problem is you have to select your device model inside the dual boot patcher app and device is recognised as "VINCE" aca Redmi 5 Plus because the mokee rom i have is obviusly ported from Redmi 5 Plus . so when i select m6 note flashing fails . is it safe to select vince as my device or i will f@ck everything up badly???
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
Edit build.prop.

Ro.product.device="your device"

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] consumimur:
thanks . that seems to do the trick . flashing aborted but it is due to the lack of space needed to create /data/ . system.img.tmp . phone is 16gb and tight in space . i have to free some space and try again
[Galaxy S 4 i9505 Original Android Development] royeiror:
Just an update. With the help of [MENTION=6084385]yshalsager[/MENTION], I got to build the app for the Moto Z2 Play. If anyone is interested I used the Travis CI method Then used the .travis.yml provided by [MENTION=6084385]yshalsager[/MENTION]. Plus edited the repo in line 8 to " - git clone --recursive https://github.com/royeiror/DualBootPatcher -b master DualBootPatcher/ "

If anyone is interested my generated files are here:

https://transfer.sh/WaYq/Android_GUI-debug-290818-00h33m.apk

https://transfer.sh/znxow/DualBootUtilities-9.3.0-290818-00h33m.zip

https://transfer.sh/1zw4z/DualBootPatcher-9.3.0-290818-00h33m-Linux.zip
[Galaxy S 4 i9505 Original Android Development] deeplyyoung:
Hi Guys..

Tried earlier also but failed ...

Now again getting error (SS attached)

Whereas my device is Shamu only ..

Can anyone put some light and help me out to get rid ... (This package is for device: shamu; this device is - )

Log attached as well

Thanks in advance
[Galaxy S 4 i9505 Original Android Development] deeplyyoung:
Can you confirm what error you were getting on Shamu...
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
I have received that error today. But after repatching the rom it disappeared. Try to patch and flash again.

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] deeplyyoung:
Tried thrice repatching... Getting same error buddy....

Edit: tried 2 different roms and patching number of times... But still getting same error....
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
Try this way.

- after you patch rom, use x-plore and go to "your rom"/meta-inf/com/google/android - long tap on updater-script - edit.

- then delete the first line which starts with "assert". (Watch screenshot)

- save and flash via dualbootpatcher.

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] deeplyyoung:
Thanks a lot man.... At least have crossed first step.... Now have successfully flashed patched Rom.

But not able to even boot primary as well...

I'll get some solutions for that... But main thing is that I'm able to flash secondary on My Shamu..

Once again heartily thanks buddy....
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
Dear friends. Help needed. When trying to flash floppy kernel to secondary rom it says:

https://drive.google.com/file/d/1qrfhdyx39ertmquLjb7G6QAM5fdJaxd_/view?usp=drivesdk

Thanks

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] marcdw:
Have you tried flashing from TWRP? If not, do so. If it still fails then check the generated log file to find out why.

Moto G5S Plus XT1806, Validus 8.1.0, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] fatalhuss:
Thanks. Flashing via twrp works:)

Отправлено с моего MI 5s через Tapatalk
[Galaxy S 4 i9505 Original Android Development] pokey7701:
I get a similar error when trying to flash in any of the methods. I can't seem to get it to work. My primary rom is lineage 14.1. I am using philz as my recovery and I have about 2gb free on internal and 10gb free on my 128gb card.

If I need to change my recovery, will my backup/restore of my current rom still work?

The error is the same like deeplyyoung's screenshot.
[Galaxy S 4 i9505 Original Android Development] lanbluue:
Hi guys,really need help here,every time I flash Oreo 8.1 ROMs, I always got the "failed to update vendor image"

warning.
[Galaxy S 4 i9505 Original Android Development] deeplyyoung:
Have you tried 13431 way??
[Galaxy S 4 i9505 Original Android Development] pokey7701:
My file only has

assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" ||
[Galaxy S 4 i9505 Original Android Development] ecrum:
Guys any success on redmi note 5 pro(whyred)??

Its officially supported but could not get to work by any means..

Updating ramdisk gets bootloop with any primary rom. And not secondary/data slot works. :(
[Galaxy S 4 i9505 Original Android Development] deSSy2724:
I receive an error : 1 attempt , 0 succesful on my Galaxy s5 mini while trying to patch magisk on my data 1 rom... how to flash it?
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
[MENTION=4277844]chenxiaolong[/MENTION] or someone else who is firm with that... I've got a Redmi Note 5 pro which is officially supported by dual boot patcher. My question is could dual boot patcher cause a brick on devices with anti rollback protection or should there be no risk? I would let stock Miui untouched and test with other roms. Thank you
[Galaxy S 4 i9505 Original Android Development] alfredxyz:
Hey have you solved it?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
This app seems like abandoned [MENTION=4277844]chenxiaolong[/MENTION] any plans adding support for pie roms?
[Galaxy S 4 i9505 Original Android Development] Eleo:
I think even oreo has not been fully fixed. Am I wrong? Oreo kernels were still not be able to be patched as far as I recall...
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
Hello. Been testing this app out on my Galaxy S4 and can't get it to work no matter what. I can complete the entire process step by step and flash the secondary ROM, but when i reboot after flashing, I get the normal splash screen follwed by 5 vibrations and im thrown into recovery (TWRP). I then reflashed a boot.img and started over by flashing the patched ROM in TWRP, and the result was the same. Yes I did update the RAM disk on both ROMs. I had a problem with other things unrelated and decided to flash to stock and start over with a fresh OS. I was on CM13, and now on LineageOS 13. Maybe this will be different? Any advice is appreciated.
[Galaxy S 4 i9505 Original Android Development] marcdw:
Last update was in July. Not so long ago to start claiming abandonment. Let people have the summer off. Hopefully we'll get something soon.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I hope it wasn't abandoned :( If so, it always seems I am late to the party...more like I totally missed it.
[Galaxy S 4 i9505 Original Android Development] klorinczi:
I hope [MENTION=4277844]chenxiaolong[/MENTION] is well and will return to his project.

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] gaww:
Other people had been maintaining it, but looks like they have packed it in.
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I read a lot of pages here. The dev gets busy with school and probably took the summer off. There are more than a few mentions of it. It's also been barely 2 months since the last build. So I'm not sure where you see 'they packed it in.' Try to be a little optimistic. Seems that's lacking around xda a lot lately.
[Galaxy S 4 i9505 Original Android Development] gaww:
The OP has been gone for some time (he finished school a few years back), so most development went with him.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes, that's in my case if I patch the kernel ie. update the ramdisk leading to bootloop and oreo currently only works as primary for me.
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Yes correct, because of Oreo's early mount feature(google it). There is a workaround, but it's a hack and quite a hassle
[Galaxy S 4 i9505 Original Android Development] marcdw:
That early mount thing is putting a kink in my ROM flashing. On my Moto G5S+ I use MultiROM but most ROMs released since July have early mount and don't work (crashes MultiROM when they boot).

Total bummer for multi booters.

ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] juppi:
I can not install lineage os 15.1 and 16.0 on herolte.

I always get the following error message:

E3004: This package is for device: heroltebmc,herolteskt,heroltektt,heroltelgt,heroltexx,herolte; this device is .script aborted:

How can i set the correct device name?

I'm using lineage os 14.1 as my primary rom.

---------- Post added at 12:29 PM ---------- Previous post was at 12:29 PM ----------

I can not install lineage os 15.1 and 16.0 on herolte.

I always get the following error message:

E3004: This package is for device: heroltebmc,herolteskt,heroltektt,heroltelgt,heroltexx,herolte; this device is .script aborted:

How can i set the correct device name?

I'm using lineage os 14.1 as my primary rom.
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I get a similar error "this package is for jfltexx. This device is ""."
[Galaxy S 4 i9505 Original Android Development] jer194:
If you are experienced, and know what you are doing, try this (at your own risk):

Make sure the ROM is really built for your device. If so,

unzip the ROM, remove the assert lines from the updater script, zip again, flash that new zip.

You can read more here, under 'DBP', or google the error message.
[Galaxy S 4 i9505 Original Android Development] drakonknayt:
if I turned the wrong way , then please tell me where to write.

This is code from sony.yml

---

- name: Sony C6603

id: yuga

codenames:

- C6603

- yuga

architecture: armeabi-v7a

block_devs:

base_dirs:

- /dev/block/platform/msm_sdcc.1/by-name

- /dev/block/bootdevice/by-name

system:

- /dev/block/bootdevice/by-name/system

- /dev/block/mmcblk0p24

- /dev/block/platform/msm_sdcc.1/by-name/system

cache:

- /dev/block/bootdevice/by-name/cache

- /dev/block/mmcblk0p25

- /dev/block/platform/msm_sdcc.1/by-name/cache

data:

- /dev/block/bootdevice/by-name/userdata

- /dev/block/mmcblk0p26

- /dev/block/platform/msm_sdcc.1/by-name/userdata

boot:

- /dev/block/bootdevice/by-name/boot

- /dev/block/mmcblk0p17

- /dev/block/platform/msm_sdcc.1/by-name/boot

recovery:

- /dev/block/bootdevice/by-name/recovery

- /dev/block/mmcblk0p23

- /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

extra:

- /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

- /dev/block/platform/msm_sdcc.1/by-name/LTALabel

- /dev/block/platform/msm_sdcc.1/by-name/TA

- /dev/block/platform/msm_sdcc.1/by-name/aboot

- /dev/block/platform/msm_sdcc.1/by-name/alt_aboot

- /dev/block/platform/msm_sdcc.1/by-name/alt_rpm

- /dev/block/platform/msm_sdcc.1/by-name/alt_s1sbl2

- /dev/block/platform/msm_sdcc.1/by-name/alt_sbl1

- /dev/block/platform/msm_sdcc.1/by-name/alt_sbl2

- /dev/block/platform/msm_sdcc.1/by-name/alt_sbl3

- /dev/block/platform/msm_sdcc.1/by-name/alt_tz

- /dev/block/platform/msm_sdcc.1/by-name/apps_log

- /dev/block/platform/msm_sdcc.1/by-name/m9kefs1

- /dev/block/platform/msm_sdcc.1/by-name/m9kefs2

- /dev/block/platform/msm_sdcc.1/by-name/m9kefs3

- /dev/block/platform/msm_sdcc.1/by-name/ramdump

- /dev/block/platform/msm_sdcc.1/by-name/rpm

- /dev/block/platform/msm_sdcc.1/by-name/s1sbl2

- /dev/block/platform/msm_sdcc.1/by-name/sbl1

- /dev/block/platform/msm_sdcc.1/by-name/sbl2

- /dev/block/platform/msm_sdcc.1/by-name/sbl3

- /dev/block/platform/msm_sdcc.1/by-name/tz

- /dev/block/sda1

- /dev/block/mmcblk1

- /dev/block/mmcblk1p1

boot_ui:

supported: true

flags:

- TW_GRAPHICS_FORCE_USE_LINELENGTH

brightness_path: /sys/class/leds/lcd-backlight/brightness

max_brightness: 255

default_brightness: 168

cpu_temp_path: /sys/devices/virtual/thermal/thermal_zone0/temp

battery_path: /sys/class/power_supply/battery/capacity

graphics_backends:
[Galaxy S 4 i9505 Original Android Development] klorinczi:
There was a bug in Dual Boot Patcher, which resulted this error.

I think it was fixed in latest DBP version.

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I used the latest apk.
[Galaxy S 4 i9505 Original Android Development] klorinczi:
I remembered incorrectly, the change was not merged into DBP. See this:

https://github.com/chenxiaolong/DualBootPatcher/commits/oreo-properties

As you can see last activity of [MENTION=4277844]chenxiaolong[/MENTION] was at Aug 12, 2018.

The issue was mentioned here:

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

https://github.com/chenxiaolong/DualBootPatcher/pull/1247

https://github.com/chenxiaolong/DualBootPatcher/commit/77367aededc4b36618de645cc2123d0c31d89a6d

I did not see any activity from him since that patch, which he did under his vacation... :(

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] uninstalll:
Hi

İ m using Vibe p1 with primary rom aex 5.8 (8.1.0)and secondary (data slot) original rom (6.0.1).my problem is in original rom dbp cant get root rights.

How can i resolve this problem.
[Galaxy S 4 i9505 Original Android Development] gaww:
Surprising - he got an S9 that cannot be used with duelboot. Would be great to see him back in a big way.
[Galaxy S 4 i9505 Original Android Development] pedram.iz:
you have to edit "updater-script" and remove assert lines like:

Code:

assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););

ifelse(is_mounted("/system"), unmount("/system"));

2- To Flash AROMA ROMs flash patched zip from TWRP
[Galaxy S 4 i9505 Original Android Development] Rauf787:
Can anybody fix unbale to set the kerna

[IMG="error img"]https://drive.google.com/file/d/1SfKjW4P4TdQ-_u0962HjzLisvTAAi-TF/view?usp=drivesdk[/IMG]

[IMG="img 2"]https://drive.google.com/file/d/1IfLLmpTSmxX9zsdgH0ezoSBKez7vzhw2/view?usp=drivesdk[/IMG]

---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------

Can anybody fix unbale to set the kerna on xiaomi Mi A1 devices
[Galaxy S 4 i9505 Original Android Development] Zombillano:
Hi there! I'm trying to dual boot my nexus 6p. As primary ROM I'm using Lineage OS 15.1 (Oreo). I tried to flash Pure Nexus (equivalent to 7.1.2) and Lineage OS 14 (equivalent to 7.1.1) as both data and secondary ROM. When I tried to flash them as secondary ROM I got an error when TRWP was flashing boot.img.

When I tried to flash them to data, both of them installs just fine, but when I reboot I get bootlogo and nothing else. I also tried to wipe cache/dalvik cache after installing but I'm still getting stuck at bootlogo.

I am unencrypted. I'm using Magisk 17 and the last release of Dual Boot Patcher.

I've ran out of ideas of how to solve this, so I hope someone can help me. I'm aware that the main developer of the project is inactive, but Im pretty sure someone else will be able to help me
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I actually had removed those lines and still nothing. As far as I'm aware the roms aren't aroma.
[Galaxy S 4 i9505 Original Android Development] Zombillano:
So here is what I found so far: I'm not able to boot nougat roms using oreo's vendor-radio-bootloader. I though it was possible to have dual boot Oreo-Nougat as well as some other people here, but it looks like the nexus 6p works in a different way.

Does anybody know if there is a way to make a nougat rom boot using oreo's vendor? I'm almost sure that there isn't a way.

Also, does anybody know if there's a way to flash vendor-radio-bootloader when launching a secondary/data rom?
[Galaxy S 4 i9505 Original Android Development] Eazart:
Hello please i download this app to my Tecno K7 android 7.0 kernel 3.18.35

Am getting this error when I click Rom
[Galaxy S 4 i9505 Original Android Development] Eazart:
I installed the app on my Tecno K7 android 7.0 kernel 3.18.35 and I have busybox installed and magisk as root but when I click "Rom" the app closes.
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
You will first need to go to this link and add support for your device. Then you have to wait for the next build, if there is one. https://github.com/chenxiaolong/DualBootPatcher/wiki/[Devices]-How-to-support-a-new-device. I currently have the same problem with a device of mine. Unfortunately there's nothing we can do unless you build the app from source.
[Galaxy S 4 i9505 Original Android Development] China2058:
Unable to load, already root, my device is Micromax a311, please solve this problem.:crying:
[Galaxy S 4 i9505 Original Android Development] marcdw:
Reminder, here is a list of supported devices. Make sure it is consulted before trying to use Dual Boot Patcher.

https://dbp.noobdev.io/supported_devices.html

If your device is not there then do as [MENTION=8165603]DragonFire1024[/MENTION] suggests and hope.

ZTE Axon 7 A2017U, Project New World, Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] edyny1:
Which latest version will have "dream2lte" option instead of dreamlte when patching? On my s8+ i cannot flash some patched files due to that.
[Galaxy S 4 i9505 Original Android Development] jerryspring:
Don't in-app flash..flash patched zip in recovery
[Galaxy S 4 i9505 Original Android Development] edyny1:
Yeah i know but i don't mean that. If you look at my screenshot when patching a zip and choosing the device. Latest's versions have dreamlte for both s8 and s8+ in dualboot patcher apk and s8+ supposed to be dream2lte. So when i go to flash the file for example "csc selection with is for dream2lte i get device not recognized.
[Galaxy S 4 i9505 Original Android Development] edyny1:
Look at this screenshot from from v9.3.0 r499
[Galaxy S 4 i9505 Original Android Development] jerryspring:
Then your device isn't supported
[Galaxy S 4 i9505 Original Android Development] gaww:
There is/was a separate duelboot thread for S8's, so would have thought it was supported .
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
Any porting for Xiaomi Mi Mix 2s????? :(
[Galaxy S 4 i9505 Original Android Development] marcdw:
Say, I just noticed something recently. On my other device with DBP I needed to flash the SubstratumRescue.zip. Patched and flashed. All seemed good. Back in the ROM, however, nothing changed so I did a quick comparison.

The rescue zip has an update-binary that is actually a script. Updater-script is just a place holder. When the zip is Patched DBP replaces the update-binary with its own. That's a bummer as the rescue zip does nothing because of that.

Makes me wonder if that has something to do with some past flash-successfully-but-nothing-happens issues I've had. Mostly after moving up to 806 (previously had 765 I think).

So, is replacing update-binary always been there?

Moto G5S Plus XT1806, LiquidRemix 9.1.4 ROM, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] aaron74:
[MENTION=4277844]chenxiaolong[/MENTION]

Any way to get this to work with Huawei/Honor devices? Specifically Honor7x (Mate SE)
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
Just awesome!!! Using on a TW as primary and RR as secondary...congratz on this... Both ROMs working perfectly
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Yup! It has always replaced update-binary for a while(that's how it 'sets up Multiboot environment' whenever you flash a patched zip file), but it's supposed to automatically run the original update-binary after the environment is set up(you see it's the update-binary that calls updater-script) tho I'm not sure if anything broke in the latest updates. I don't have any solutions either, that's all I know :( Hope this helps!
[Galaxy S 4 i9505 Original Android Development] marcdw:
Thanks for the clarification. I guess for those few instances where the original zip has an update-binary that's actually a script (and updater-script is just a placeholder) I can easily do a copy-n-paste between them. Hopefully the patched zip will work fine then.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
Hi all, can somebody take a look at my log and tell me what's going on and how to fix it? TIA
[Galaxy S 4 i9505 Original Android Development] haoyangw:
You're basically facing the same issue as the people below, and here's the solution:

In fact you're using a jflte as well. Perhaps you should search through this thread before asking for help lol, I found the above similar issues and the solution within a minute after searching the error
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
Edit:delete
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
Sometimes I don't have time to search through 1350 pages. next time a link reference wouldn't kill you
[Galaxy S 4 i9505 Original Android Development] haoyangw:
? I'm literally in the middle of an exam period right now, but I only spent 1 min to find those posts and the solution lol. I just searched this: 'this device is' in this thread and it's like the first 3 results. And fyi I didn't see those posts and the solution before, neither have I read through most pages here, I just found the exact error keywords and searched. And I'm not a dev either, I just got really good at finding error keywords in logfiles after a few years of tinkering. But personally I don't mind answering repeated questions or searching through threads either so it's not my problem, just that others may be bothered by repeated questions. So it's not compulsory to do this, but would be really nice. And I apologise if I was a bit harsh, I'm not trying to be, just giving a suggestion