yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=4277844]chenxiaolong[/MENTION],

For future releases..it seems Hellybean will be named Hellykat now:

http://xdaforums.com/showpost.php?p=47956424&postcount=67

And Broodplank's aosp rom is "aosp44" now.

For now I renamed in both cases and patched using 3.1.0.apk,no issue but for "Hellybean" the "support for removing those pesky device check asserts" (always smiling when I see that changelog part thinking that at first i did not dare ask you to support this lol) didn't work.

Asserts were still there.

Was then renamed to Hellybean Hellykat zip on 3.1.0.apk patcher.
[Galaxy S 4 i9505 Original Android Development] wingg:
Yes it's a matter of naming.

I'd patched leatest GoogleEdition 4.4 very simply: ->> just renamed it as CM11 leatest nightly but without "nboodev" ...

Regards

//->>
[Galaxy S 4 i9505 Original Android Development] `SBR`:
is it booting up??.. as the Ram disk will be different btw CM11 and GE..
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Renaming works. Just remember KK4.4 -> JB4.3 (KK - kit kat, JB - jelly bean) :D

Anyway, this will be fixed in the next release: https://github.com/chenxiaolong/DualBootPatcher/commit/2dc26e9af1db73879a3539996781a41e180d13bd
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll fix both of them now. I'm not sure if it's supposed to be "Hellykat" or just "Hellkat" so I'll make it accept both.

As for the assert issue, I really need to work on that. Right now, the code for that is pretty crappy :D

EDIT: Are you sure the device check thingy didn't work? The code doesn't actually remove the assert, but instead adds a "true == true" check to the beginning. I do it this was because the assert might be spread over multiple lines and deleting one would result in a syntax error.

EDIT2: Just for the heck of it, I flashed a jfltexx recovery on my S4 and I was able to install Hellkat just fine :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=4277844]chenxiaolong[/MENTION],

wow wow wow..(hellkat,JBvsKK,asserts?...makes 3 wow yep) really not fair of me to make you lose time like this lol,sorry ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem, I'm bored right now anyway ;)

EDIT: Version 3.1.1 released
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
[MENTION=4277844]chenxiaolong[/MENTION]

Dear Chen, would it be possible to list which TW Roms will work with our patcher? At the moment it is so unclear which ROM to choose as a secondary "System".
[Galaxy S 4 i9505 Original Android Development] Shanks:
Negalite and triforce worked for me
[Galaxy S 4 i9505 Original Android Development] rlorange:
Anyone else having trouble getting ge 4.4 to work? The rom zip installs fine but first boot won't get past splash screen for me
[Galaxy S 4 i9505 Original Android Development] `SBR`:
patch the latest KT kernel and try.. the latest patch is working with KT GE version
[Galaxy S 4 i9505 Original Android Development] farovitus:
Bro you need to focus a lil bit to make this work.:angel:

Flash any kernel from twrp (step 1)

Using your pc and 7zip program, open that kernel.zip you flashed in twrp, and extract a file with ".img" extension then rename that file to boot and copy it to your internal storage in Multiboot/primary/.... (Step 2)

Problem solved.:good:
[Galaxy S 4 i9505 Original Android Development] RaghuStar:
Ok thanks I will try with this and reply ...:D
[Galaxy S 4 i9505 Original Android Development] RaghuStar:
Cpn3+

Ok here what I get when I try installing rom In other slots say second slot... I get the report like this...

And for kernel ...till now no one prepared custom kernel for my device...well that exist for Coolpad note 3 but not for plus device...so once again hopeless...
[Galaxy S 4 i9505 Original Android Development] Eleo:
Please check your storage on /cache. Multislot is for /cache.

Better install it to dataslot. It is safest of all.

Reading multiboot.log now.

Yeap, it says /cache filesystem cannot ve mount. Try on dataslot
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Ok, I think this patcher isnt working for me.

I can patch my ROM, but I cant set the Kernel for my primary ROM.

It says, my device isnt recognized.

Hope it will work in a newer version...
[Galaxy S 4 i9505 Original Android Development] alassshka:
Hi! Im a user Xiaomi Redmi Note 4 (MTK), and i really want to install this app on my phone) Dear, developer(-s) could you enable Note4 in your app)
[Galaxy S 4 i9505 Original Android Development] sronweb:
Maybe I have moved forward, because the primary Rom is Dr.Ketan M12 based on Note 7 I have edited build.prop ro.product.device and to.build.product to trltexx but I still get error as attached screenshot. But I don't see a setting where my device should be detected as "trltecan"
[Galaxy S 4 i9505 Original Android Development] Eleo:
From the logs you shared 22 hours ago

P.S. Forgot ro.build.product and ro.omni.device. They are also trltecan
[Galaxy S 4 i9505 Original Android Development] sronweb:
thank you. Investigating.....
[Galaxy S 4 i9505 Original Android Development] Eleo:
Open your logs zip, go to recovery/default.prop file. That is in your recovery default.prop.

Since you had too many logs files I just combined them in one file to search easily. Then found in which file I found those lines.

That should be your issue. IDK what is your device and what should be written there instead

:confused:
[Galaxy S 4 i9505 Original Android Development] gaww:
I also have a nougat in data slot working ok.
[Galaxy S 4 i9505 Original Android Development] A_Random_Guy:
Anyone able to run DualBootPatcher on Windows? Mine errors at can't find find or load plugin 'windows'
[Galaxy S 4 i9505 Original Android Development] Eleo:
See this
[Galaxy S 4 i9505 Original Android Development] `SBR`:
[MENTION=4277844]chenxiaolong[/MENTION], after a long time (S4) back to Dual patcher app for Axon 7.. .

it's good to see you're still updating the app. good work.

i have a request, might be already answered here, if possible please fix this for Axon 7.

the when i try convert the zip and flashing it's failing in Trustzone verfication. manully removing the trustzone lines it's working perfectly.. can you add a way to skip the trustzone.

below is theh code.

assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
[Galaxy S 4 i9505 Original Android Development] AceLine:
Hi Chenxiaolong,

with this post I add the GetLogs-File for the Samsung Galaxy Note 10.1, WIFI-Only (GT-N8010)

Thank you for your great help!

Best regards, Ingmar
[Galaxy S 4 i9505 Original Android Development] turikos:
DualBootPatch Error

Hi everyone!

I have an SM-G900F with Official Lineage 14.1 as primary ROM.

I tried to install XXX No Limits 6.1 ROM to my extSDcard, but i get this error.

Is somebody may help me please
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Try to flash in recovery
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
Here is the log from my attempt on my Verizon lg v20. Vs995. Would love to see dual boot on this device! Thank you for your time and consideration.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Your log is only about patching the zip.

Can you patch a zip?
[Galaxy S 4 i9505 Original Android Development] turikos:
I tried it, but the same error occured
[Galaxy S 4 i9505 Original Android Development] VampireHeart:
I hope next release have full support for Oneplus3t, I tried to make working actual version on my device but it don't recognise correctly his partitions so can't set primary ROM and kernel.

I used this fantastic app on my 6P time ago and with 7 ROMs tougher. :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] cc6691:
Please can anyone make support for asus zenfone 2 laser Z00L

Or make a guide on how to add support for non supported devices please
[Galaxy S 4 i9505 Original Android Development] Eleo:
Share logs via getlogs and wait patiently
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
No, the zips don't patch.
[Galaxy S 4 i9505 Original Android Development] Islam Looca:
Got an issue with nougat for nexus 4, current primary is chroma 6.0.1.

I did the following :

1- installed DBP, set the kernel, patch the rom zip and installed it successfully in a data slot.

2- rom boots fine then installed DBP to switch between roms.

3- switched to primary and it boots, then switched back to secondary then it stucks at boot animation, wiping cache and dalvik for secondary doesn't help.

This problem is with any nougat rom, aosp or lineage os, i don't know what's the problem ?
[Galaxy S 4 i9505 Original Android Development] skivnit:
Hey guys last time i used this was on my s4 now id want to give it another shot with aosp roms popping on the s7 forums. I have everything running. Only problem is app data and app sharing.

Question 1. Do i need to download the app on my secondary rom?

Question 2. I have shared spotify data however i dont find my downloaded tracks on my primary rom
[Galaxy S 4 i9505 Original Android Development] Eleo:
1. Yes

2. Firstly you share data of an app in one slot, reboot, then restore app data since its data folder has now been changed. Then install app on other slot, dont restore app data, reboot (you may have data restoted on new slot too, nevermind, since it will change the folder for app data after app sharing+reboot, the restored data before app sharing will not be useful unless you stop data sharing on that slot). After boot data on your previous ROM is now usable on new slot too and changes you make on app data (add smth or remove smth) are directly translated to every slot that has shared that app's data.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Edit
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Solved
[Galaxy S 4 i9505 Original Android Development] Eleo:
Logs? Can you please share logs after unsuccessful flash?

I already showed that you can flash ROM into extsd as shown in my post#1, post#2 and post#3.

It is possibly a device-specific issue. But without logs we cant say anything
[Galaxy S 4 i9505 Original Android Development] Siema89:
Is it possible to convert my current OS without losing data and add another?

I'm using Samsung Galaxy S7, Exynos variant, with stock nougat ROM and SuperStock 2.3.0 custom kernel. I'd like to "append" LineageOS to my current installation. Is it possible without losing any data in my stock ROM?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Convert? You mean like from primary to dataslot? Move to other slot (lets say dataslot 1) backup primary ROM, wipe present primary (the one you backed up) then restore into dataslot (lets say dataslot 2). Do it all from dual boot patcher app from different slot (other than primary, or any other one you want to "convert")
[Galaxy S 4 i9505 Original Android Development] Siema89:
No, I mean from a "clean" state (never installed dual boot patcher before) to a working dual boot installation with my current state as primary. And preserving current data (i.e. without wiping the device clean).
[Galaxy S 4 i9505 Original Android Development] Eleo:
Just install DBP and select set kernel. That will trigger dual boot from your present ROM. Your current ROM from that moment is coded as "primary" on dual boot patcher and boot.img of your kernel from present ROM is copied to multiboot folder. It is faster first time since it doesnt require moving/copying any system files/folders to internal or external, since your /system folder is kept untouched. Only boot.img is copied.
[Galaxy S 4 i9505 Original Android Development] Siema89:
That's what I wanted to know, thanks!
[Galaxy S 4 i9505 Original Android Development] gaww:
What do you mean by ExtSD 1,2, and 3?
[Galaxy S 4 i9505 Original Android Development] Eleo:
:eek:

They are links to my forum posts, not extsd slots. I never used the word "slot" there. Just shortened the links to not occupy too much space. Will change them to post#1, post#2 and post#3 then
[Galaxy S 4 i9505 Original Android Development] Eleo:
Did you flash a patched kernel to your patched OS (or did it have a kernel preinstalled?) before trying to boot to it? All I see are some kernel errors and the resulting vibration as you said. If not, I may read it in more details later, since it is getting late at night here
[Galaxy S 4 i9505 Original Android Development] gaww:
Is there on my one 4.1 gb folder set up for ExtSD and not one set up for each ExtSD Rom flashed?

I have gave a tw Rom in ExtSD already and if the us only one it is too full.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I think I couldnt understand the question directly...

System.img size for each slot of ROM depends on the capacity of your /system folder. For me, it is 2.3GB for note3. Each of my ext.sd slots have 2.3GB space taken as system.img for each. If there is an issue for system.img file bigger than 4GB, you may try changing your extsd FS to exfat
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
This had a kernel pre-installed, and when I try boot it's kernel manually, using TWRP,I still get the same error

_New World Order (NWO)_
[Galaxy S 4 i9505 Original Android Development] gaww:
I still think there may be only 4.1 for all ExtSD flashed. I have a tw in one, and as I have two other tw based Tom's, I was going to delete the one on the ExtSD anyway. Going to wipe it and try again.

The failure to boot looks alot like it did years ago when I ran out of room in the system partition.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Just to be sure can you try it as dataslot instead of extsd so that we know what is causing it?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
This device is my 2nd device that I added support to, my first port was total success, but this device(p9 lite,id=vns,codename=hwvns-h) is being troublesome, if I install on data-slot* all install well w/o problems, but it can't boot, it vibrates then reverts to recovery TWRP, maybe I've missed something during porting OR adding support for this device...anyway,mbtool fails to connect, and thus in app functions non work except patching, but device model is correctly recognized.

_New World Order (NWO)_
[Galaxy S 4 i9505 Original Android Development] rick09:
Is it in the works to have the LG V20 Unlocked model US996 officially supported? I can't imagine it's much different than the H918 T-Mobile model which is supported. So far I've successfully patched, flashed, and booted a stock based ROM (primary) and Resurrection Remix (secondary).

Problem is it seems I'm very limited in what I can patch/flash. So far it only successfully patched and flashed to secondary. I haven't tried multi or Ext-sd, but I was not able to get the data slot working.

Also when trying to flash patched ROMS etc in recovery (TWRP) they always fail. I believe the error says something along the lines of the patched file being for H918 and not US996. I looked into removing the get-prop lines in the updater script per the advice of another poster, but there's way too many get-prop lines! I wouldn't begin to know what to remove.

Any advice or insight is greatly appreciated!
[Galaxy S 4 i9505 Original Android Development] A1EXXX:
Any support to Xiaomi Mi 4c? Add it, please!
[Galaxy S 4 i9505 Original Android Development] Eleo:
If you have already shared logs, please patiently wait!

You can flash to secondary (into /system) but not to dataslot? Can you share logs for unsuccessful flash to dataslot? Are you sure it is not related to free space?
[Galaxy S 4 i9505 Original Android Development] A1EXXX:
What logs? How to make it? :D
[Galaxy S 4 i9505 Original Android Development] Eleo:
Download and flash getlogs zip from https://dbp.noobdev.io/downloads/ and share the tarball it creates in /sdcard/logs/ (file extension is tar.gz) here in attachment of a post with your phone model.

This will aid developer to support your phone for dualboot if it is not supported yet

Wait patiently and read changelogs and updates on same link that you downloaded getlogs to see when your phone is supported.

Cheers
[Galaxy S 4 i9505 Original Android Development] A1EXXX:
Add Xiaomi Mi 4c support, please.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Deleted

---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------

I also had booting problems with extsd flashed roms. Formatting the extsd card instead of exFAT to FAT32 solved the problem.

It seems there is a problem with the exFAT driver.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Very interesting. As I showed I have no such issue with exFAT. It should be smth in app that is causing specific issues on phones other than s4 and note 3. I cant explain it by any other way
[Galaxy S 4 i9505 Original Android Development] gaww:
Gave up on ExtSD for resurrection - getting rid on 3rd tw (system on ExtSD but all data on internal) freed up a lot of room on internal, so have resurrection on a data slot.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I noticed extsd boot problem only on my Samsung Galaxy S4 i9505 since about October 2016 with 64GB sdcard. Before I had no boot problem, and as I remember, I used 32GB sdcard.

On my S3 i9305, I don't use DBP.
[Galaxy S 4 i9505 Original Android Development] Eleo:
One possible explanation stays that your sd is not as fast... I think that is the only difference left. What else can you find different in configuration so that it wont work on s4 but work on note3
[Galaxy S 4 i9505 Original Android Development] vxkillswitchxv37:
Is there any way of getting this to work on the LG V20 H910 AT&T Varient?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Shate logs (explained millions of times here) and wait patiently if it isnt already compatible

Just look here. It was posted on same page as your post. Please try to be more attentive next time
[Galaxy S 4 i9505 Original Android Development] vxkillswitchxv37:
Could you please add support for the AT&T LG V20 H910 varient. Thanks.
[Galaxy S 4 i9505 Original Android Development] SimmoF:
Is it possible to add support for the Docomo Japan variant of Galaxy Note 3. I've peeked at your sources and it seems you just need to add it to the 01_galaxy_note.yml file.

From what I can tell the userdata partition is different and brightness path is different.

here is what I've put together.

- name: Samsung Galaxy Note 3 (Docomo)
id: hltedcm
codenames:
- hltedcm
architecture: armeabi-v7a

block_devs:
base_dirs:
- /dev/block/platform/msm_sdcc.1/by-name
system:
- /dev/block/platform/msm_sdcc.1/by-name/system
- /dev/block/mmcblk0p23
cache:
- /dev/block/platform/msm_sdcc.1/by-name/cache
- /dev/block/mmcblk0p24
data:
- /dev/block/platform/msm_sdcc.1/by-name/userdata
- /dev/block/mmcblk0p25
boot:
- /dev/block/platform/msm_sdcc.1/by-name/boot
- /dev/block/mmcblk0p14
recovery:
- /dev/block/platform/msm_sdcc.1/by-name/recovery
- /dev/block/mmcblk0p15

boot_ui:
supported: true
flags:
- TW_QCOM_RTC_FIX
- TW_HAS_DOWNLOAD_MODE
graphics_backends:
- fbdev
pixel_format: RGBX_8888
brightness_path: /sys/devices/mdp.0/qcom,mdss_fb_primary.190/leds/lcd-backlight/brightness
max_brightness: 255
default_brightness: 162
theme: portrait_hdpi
[Galaxy S 4 i9505 Original Android Development] :
[MENTION=4598795]Eleo[/MENTION] Help Needed

Our device dual boots but Everytime when we need to boot a Patched ROM we have to manually put boot.img from patched ROM.zip to Internal storage/multiboot/data-slot...(ext-sd) folder & Then Flash Supersu zip Flashing Patched Supersu is fine but putting boot.img in Multiboot folder Everytime stucks I think other devices Are able to put boot.img directly in Multiboot folder then why can't our device is able to do the same ???

Flashing nested Zips & ROM.zip with system.new.dat compression are not getting flashed successfuly

For our device

Also app sharing not working even after updating ramdisk

I am Uploading logs Plz someone read the whole logs & detect the problem to rectify it also if any kind person present here plz read logs detect the problem & rectify the sources for our device too:):):)

Note : "Everytime i use to update ramdisk in my primary Rom but this time i have don't updated the ramdisk as it is breaking our device fingerprint module but even on updating ramdisk the same problem persists"

Device = Lenovo k4 note (3gb)

Codename = A7010a48

Thank you:good::good::good:

Cheers..........✌️✌️✌️

Logs???
[Galaxy S 4 i9505 Original Android Development] Eleo:
I remember yoir device was not supported then you tried to support it by yourself, is it true? Or your device was supported by dev himself?
[Galaxy S 4 i9505 Original Android Development] :
Yes sir i tried it before to support myself but now it's officially​ supported by the dev the latest snapshots have my device listed [MENTION=4598795]Eleo[/MENTION] ???
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
I guess the logs didn't get you the information you needed? Should I maybe try from a different rom/ kernel? When I tried to patch the zip, it treated it as a directory, not an archive file (as in I was being asked to select a file inside of the zip. )
[Galaxy S 4 i9505 Original Android Development] welder73:
If the zip opens,just long press on it and tap "Open",it will patch then...
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I made backup of my primary stock rom, and now I tried to restore to extsd slot, but it failed with error.

Any idea, what might be the problem?
[Galaxy S 4 i9505 Original Android Development] Team DevDigitel:
*****Looking for the location of this file / comment to make changes to skip this check.*****

Check device

This stage will perform several actions related to the target device:

Verify that mbtool.installer.device in info.prop matches one of the following properties (unless mbtool.installer.ignore-codename is set to true, in which case the check will be skipped)

ro.product.device

ro.build.product

ro.patcher.device
[Galaxy S 4 i9505 Original Android Development] webmaster33:
If I try to restore to primary, from another rom, then I also get error:
[Galaxy S 4 i9505 Original Android Development] Team DevDigitel:
can anyone help me with making this edit to avoid my roms from being skipped for flashing? im having device mis-match issues.

Check device

This stage will perform several actions related to the target device:

Verify that mbtool.installer.device in info.prop matches one of the following properties (unless mbtool.installer.ignore-codename is set to true, in which case the check will be skipped)

ro.product.device

ro.build.product

ro.patcher.device

This is the devs remarks for the edit that needs completed to fix my issue
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Why do you post twice?
[Galaxy S 4 i9505 Original Android Development] Team DevDigitel:
because you attatched 4 XXXXXXL photos overtop of my post making the entire page unbearable.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Having other message posted after your one, is not a reason to post your problem multiple times.

Be patient...
[Galaxy S 4 i9505 Original Android Development] BJumperBR:
I know this may sound stupid but how do I restore a backup made using Dual Boot Patcher app? I can't find it anywhere...

EDIT: Nevermind... Just found the option to restore. (Flash "backup")
[Galaxy S 4 i9505 Original Android Development] hero355:
I can't patch any zip file, getting below error.

Current rom : CRdroid v2.4 Android 7.1.1

http://imgur.com/otcqIzd
[Galaxy S 4 i9505 Original Android Development] gaww:
I have not been able to get backups to work. Is there a guide to using the patcher to make and move slot backups?