yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ROMFACTORY:
RR update coming today
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Urmelausmall:
Hi. Very happy that you are back! Do you plan to update the AIM Rom too? I like the Rom very much but it has very old security patches.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ROMFACTORY:
yes tomorrow
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] HannibalLecter:
you mean Oreo?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ZainBilq:
Nope...he clarified it is nougat...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Urmelausmall:
Looking forward to the AIM Update ? wich Kernel do you use at your builds? Is it again your accent Kernel or do you use nijel8 ones?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Darkstone27:
will this ROM be updated?for nougat based i mean
[Huawei P10 Plus Questions & Answers] JF-GINO:
Hey everyone,

Ive recently had a problem trying to use a few root apps with my phone that require USB debugging and to my surprise found out it turns itself off after I leave the options screen.

Is this a normal security feature? Is there a way to keep it on?

Obviously it stays on when activated and connected to USB on a PC, but that does not help me when an app needs it. I have never seen this behavior before yet everything in USB debugging sticks (except some options after re-boot like DPI)

And thats another question,

How do we keep DPI changes in developer mode to stick after reboot.

Maybe there is a config XML somewhere in the system as normal DPI changes to the sparse Build.prop do not work since dpi is controlled via rom level.

Any help or input would be appreciated if this usb debugging thing is not normal for everyone.

If anyone knows about the DPI thing that would ne also helpful
[Windows 10 Mobile] Fa310tx:
Hello...

Is there a hack or app to have the phone remind after some pre-determined amount of time for missed calls and/or texts?

Android can activate such features with apps, but I've never seen a way to do it with Windows Phone (at least, through official means).

JJ
[LG V20 Questions & Answers] maxi65:
Assalam o alaikum

Hi

I've unlocked my v20's bootloader and tried to install twrp by using a command in command prompt " fastboot flash recovery twrp.img" cmd says flashing okay but after flashing twrp the device shows up a screen saying " Device cannot be checked for corruption lock it again"

And it doesn't boot into recovery.

When i boot it into recovery using adb command phone says "no command"

I want to know how can i fix it.

Thanks in advance
[Miscellaneous Android Development] Uday Hegde:
DualBoot Patcher - Add Support

(Unofficial & Official)​

Dualboot patcher is an open source project that makes an android phone compatible with multiple roms by patching them.That is we can install more than one rom on an android device at a time. But we cant use both at the same time,a restart is required to switch between roms. This awsome app is contributed to the android world by [MENTION=4277844]chenxiaolong[/MENTION].

Pre Requirements :

Device must be rooted.

Custom recovery (twrp/cwm) should be installed.

Basic knowledge about rom flashing.

Patience

Active brain.

Can I use it on my x device right now ?

Check here the list of supported devices -Supported Devices

If your device is listed, its well and good download only the app from below links.

Downloads :

Download the app from

Mediafire

Or official server -

https://dbp.noobdev.io/downloads/

These are releases automatically built from the source by the continuous integration server.
Due to the constantly changing nature of the ROM development community, DualBootPatcher has many incremental releases as opposed to large, infrequent releases.
These releases contain the latest and greatest features, but may also have unforeseen bugs.
Be sure to make backup before installing and using these builds!

Terminal Emulator

Other Patches :

GET_PROP ; Mirror

PATCH_DATA ; Mirror

Your device is not in the list..?? Then you are at right place

NOTE: If you are new to dual boot patcher, and don't know to unbrick in case of soft/hard bricks, first take a full backup before doing anything.

Im not responsible for anything that happens to your device

Common Steps :

First download and install the app from any of the above links, open roms section.

Grant all the permissions including root permissions.

you need bellow properties (info) of your device

Code names of your device.

Archetecture.

All mount point and block device path details.

Mandatory (for boot ui) :-

Cpu temp path, brightness control path.

Flags for bootui

Grafics backends

For more info

To get these info,

Flash this from twrp and you will get most of the required details - GET_PROP

This works on all mtk 64bit devices,( should work on others also).

But details for boot ui may not be proper for all devices, you have to check it yourself.

After flashing this,

two files - info.txt and <brand_name>.yml are created in internal storage. You can edit them with any text editors if you find some details are Wrong or Missing !

Method 1: Patching data of DBP to work with your device

In this method, we required info.txt that is created on internal, make changes in it if required.

Make sure you have already downloaded, installed the app and opened roms section.

And also flashed GET_PROP.zip from link given above.

Then go to twrp and flash this script - PATCH_DATA

It will patch data of dbp app and makes it work with your device(it will takes the info from info.txt)

Now boot to system and open Terminal Emulator,

type :-

su
dbp.sh

Your device should support now.

For confirmation ->

it should ask to set kernel when you open roms section.
[Miscellaneous Android Development] Uday Hegde:
Method 2 : Add Official Support

In this method, you have to add the device definition to the SOURCE of DualBoot Patcher.

<brand_name>.yml created in internal can help us in doing this.

Do the required changes in it using any text editor.

(like adding some codenames used in custom roms, remove bootui part if it is not supported).

First LogIn to your github account or SignUp for free.

If ur using in mobile,Select desktop version at right bottom.

Fork DualBoot Patcher from SOURCE to your git account.

(fork option is at right top.)

Now head on to your git account, open DualBoot Patcher repo.

Check whether there is your <brand_name>.yml at /data/devices/<here>

If it is already there :- just copy all the contents of your yml file to that in git.

If the file does not exist, you have to do two things

Upload yml file to /data/devices/<here>

Edit /data/devices/CMakeLists.txt - add your <brand_name>.yml in the list

Now the source of Dual Boot Patcher that supports your device is ready in your git account.

Either you can compile the app by yourself :- Procedure ( need a lnux pc or linux server )

Or :-

Select New pull request(in your git account).

Select the same in next page also to confirm pull request.

You will have to wait for some time, and the admins will verfy your pull request,

If it is all proper, they will merge it to source.

The next release of the app will have official support to your device.
[Miscellaneous Android Development] Uday Hegde:
Original thread by Chenxiaolong

https://xdaforums.com/android/development/tutorial-dual-boot-roms-patcher-t3559254

Common Q &A :

This is too lengthy, it totally went over my head. Won't it be much simpler..??

Something went wrong.I need help...

Stuck at Roms section, what can be done.??

Not showning any device in patch roms section..!!
[Miscellaneous Android Development] K001droid:
Good [MENTION=7469287]Uday Hegde[/MENTION].

It will help a lot of people.
[Miscellaneous Android Development] Uday Hegde:
Thanks
[Miscellaneous Android Development] kutlay1653:
flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip
[Miscellaneous Android Development] Uday Hegde:
Your device..??

Can u provide /etc/recovery.fstab from your recovery..??

Get_prop.zip have some limitations, ill try to fix them..
[Miscellaneous Android Development] kutlay1653:
Mt6592 General Mobile etab5 fstab in zip file
[Miscellaneous Android Development] Uday Hegde:
Check with this...

Ill add it to the main thread if its working...
[Miscellaneous Android Development] kutlay1653:
it worked but when i try to patch a rom on dualbootpatcher it gives fc any idea?

Edit i forget update ramdisk but when i try update ramdisk app says cant update ?
[Miscellaneous Android Development] Uday Hegde:
Sorry, i hav no idea about that issue

You may try with older vesions...

Wait [MENTION=6726295]kutlay1653[/MENTION] check this :-
[Miscellaneous Android Development] androiabledroid:
I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'G42' is not recognized
[Miscellaneous Android Development] Uday Hegde:
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
[Miscellaneous Android Development] androiabledroid:
Tried and now same error and one more thing I think this is responsible for this. Please see attachment
[Miscellaneous Android Development] sagargjasani264:
Can't download patch_data.zip....

It says authorised download...
[Miscellaneous Android Development] Uday Hegde:
Mirror added in download section..;)

Its an issue that dualboot patcher app can't read device.json file after modification, though i fixed correct uid,gid and permissions.

So i placed the file in internal and created a symlink to its data directory.this actually worked for me

Let me try some other workarounds and i will try to fix it..:good:
[Miscellaneous Android Development] sagargjasani264:
After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..
[Miscellaneous Android Development] Uday Hegde:
This is the issue with latest app, that issue is even exist on supported device(coolpad note 3 lite)

Use older app, (u can use the one given in download section, mediafire link)
[Miscellaneous Android Development] kutlay1653:
Stuck at this section
[Miscellaneous Android Development] Uday Hegde:
Ohh

Thats new issue that i saw..?:confused:
[Miscellaneous Android Development] kutlay1653:
i found my issue . my issue is when i try the open roms section the dualboot app try to create boot.img in data/data/com.github..../cache/boot.img but the cant create bootimg i tried manually put bootimg but didnt work

The app creates 10 GB bootimg but my boot img is just 10 mb :silly:
[Miscellaneous Android Development] Uday Hegde:
Oww,..

Then its error in partition detection:eek:

Ill check what need to be modified in getprop.zip

Can you share the two file created in internal,

info.txt and *.yml..??
[Miscellaneous Android Development] kutlay1653:
Here sir
[Miscellaneous Android Development] Uday Hegde:
Found the issue,

Probably can't be solved...

App uses DD backup method to backup boot.img (its the main reason)

But in your device, partition size need to be applied as argument for dd which must be included in the source ( otherwise infinitely loops ).

Im not sure But you can still try..

Use very old version of the app,

Patch your rom and other zips.

First backup your current boot.img

Flash the patched rom && backup its boot.img also and then reboot

Whenever you want to change the rom, just restore its boot.img
[Miscellaneous Android Development] androiabledroid:
Tell me solution
[Miscellaneous Android Development] Uday Hegde:
Links updated in the thread, try patch_data.zip

And run

su
dbp.sh

In terminal emulator.
[Miscellaneous Android Development] androiabledroid:
Still same

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

When I try to patch zip app stopped unfortunately
[Miscellaneous Android Development] Uday Hegde:
Better check in other rom or older app versions..
[Miscellaneous Android Development] androiabledroid:
Now I am getting failed to boot room which I have flashed the secondary room on my device I used older version
[Miscellaneous Android Development] Uday Hegde:
Use data slot
[Miscellaneous Android Development] androiabledroid:
Already in day

---------- Post added at 02:09 AM ---------- Previous post was at 01:41 AM ----------

Using data slot already

---------- Post added at 02:13 AM ---------- Previous post was at 02:09 AM ----------

Whenever I tried to flash patched rom using twrp and I restart so I got three vibrations at a time then goes to recovery mode what is this

---------- Post added at 02:25 AM ---------- Previous post was at 02:13 AM ----------

Fixed that issue
[Miscellaneous Android Development] androiabledroid:
Now i am getting decrypted password error i tried to use my decryption password but it says wrong but it's work fine in TWRP
[Miscellaneous Android Development] viper**7:
Kernel and multiboot errors

Hi,

Glad to see that u have come up with a patch for all unsupported devices.

I tried installing DualBoot-Patcher-9.0.0-R60-ms013g-2016.10.25 and then applied the patches as described (since newer versions develop more storage space issues after installation). Though I'm able to s3elect my device name and patch zip file, I'm experiencing following errors:

1. While trying to set kernel on the primary; it returns an error: " Could not determine the boot partition because this device's codename 'vegetahd' is not recognized.

2. While trying to update ramdisk ; it returns an error : " The ramdisk failed to update. The log was saved to Multiboot/ramdisk-update.log in the internal storage "

3. While flashing ; it returns error : " [Multiboot] Failed to extract multiboot files from zip, [Multiboot] Failed to flash zip file.

Thank you, and I appreciate your help.
[Miscellaneous Android Development] Uday Hegde:
Better dont use encrypted data..!!
[Miscellaneous Android Development] Uday Hegde:
Thanks for your support And sorry for late reply...

Check /sdcard/info.txt, 'vegetahd' is included in CODENAMES,

If not incuded, add it yourself and flash patc_data.zip again

And i recomend the version which i included in the thread(mediafire link)
[Miscellaneous Android Development] defy_owner:
Update ramdisk failed. I have lenovo a6000 with custom rom zenui marshmallow. [MENTION=7469287]Uday Hegde[/MENTION]
[Miscellaneous Android Development] Uday Hegde:
looks like log is partially missing..

try with latest app, it may work.
[Miscellaneous Android Development] defy_owner:
Thank u sir for ur reply. Here is the new log with the latest app version. I think this line is culprit. Failed to load /storage/emulated/0/MultiBoot/primary/config.json
[Miscellaneous Android Development] adamharris7890:
unofficial not working

I flashed get-prop .zip and patch_data.zip and it went fine.But when i open dualbootpatcher and the ROM section IG says "could not determine the device's boot partition because this device's codename gtexlte is not recognized".Pls help.I'm using a Samsung Galaxy Tab A 2016 7.0 SM-T285
[Miscellaneous Android Development] defy_owner:
I think u skipped the terminal emulator part. After flashing the both zips i think u should use terminal emulator to open the dual boot patcher. Kindly read the op post for details.
[Miscellaneous Android Development] adamharris7890:
I did use terminal emu. Not working

Here

is a copy from the info. text file[I don't know how to attach files;)]pls see anything wrong

Device=samsung SM-T285

CodeNames=sm-t285 gtexslte

Architecture=armeabi-v7a

id=gtexslte

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

battery_path=/sys/class/power_supply/battery/capacity

brightness_path=

Base_dirs= /dev/block/platform/sdio_emmc/by-num /dev/block/bootdevice/by-num

System_block= /dev/block/bootdevice/by-num/system

Data_block= /dev/block/bootdevice/by-num/userdata

Cache_block= /dev/block/bootdevice/by-num/cache

Boot_block= /dev/block/bootdevice/by-num/boot

Recovery_block= /dev/block/bootdevice/by-num/recovery

Extra_block=/dev/block/mmcblk0p17 /dev/block/mmcblk1p1 /dev/block/platform/sdio_emmc/by-name/HIDDEN /dev/block/platform/sdio_emmc/by-num/p1 /dev/block/platform/sdio_emmc/by-num/p10 /dev/block/platform/sdio_emmc/by-num/p11 /dev/block/platform/sdio_emmc/by-num/p12 /dev/block/platform/sdio_emmc/by-num/p13 /dev/block/platform/sdio_emmc/by-num/p14 /dev/block/platform/sdio_emmc/by-num/p15 /dev/block/platform/sdio_emmc/by-num/p16 /dev/block/platform/sdio_emmc/by-num/p17 /dev/block/platform/sdio_emmc/by-num/p18 /dev/block/platform/sdio_emmc/by-num/p19 /dev/block/platform/sdio_emmc/by-num/p2 /dev/block/platform/sdio_emmc/by-num/p20 /dev/block/platform/sdio_emmc/by-num/p21 /dev/block/platform/sdio_emmc/by-num/p22 /dev/block/platform/sdio_emmc/by-num/p23 /dev/block/platform/sdio_emmc/by-num/p24 /dev/block/platform/sdio_emmc/by-num/p25 /dev/block/platform/sdio_emmc/by-num/p26 /dev/block/platform/sdio_emmc/by-num/p27 /dev/block/platform/sdio_emmc/by-num/p3 /dev/block/platform/sdio_emmc/by-num/p4 /dev/block/platform/sdio_emmc/by-num/p5 /dev/block/platform/sdio_emmc/by-num/p6 /dev/block/platform/sdio_emmc/by-num/p7 /dev/block/platform/sdio_emmc/by-num/p8 /dev/block/platform/sdio_emmc/by-num/p9

bootui=true

Flags=TW_GRAPHICS_FORCE_USE_LINELENGTH

Graphics_backends=fbdev
[Miscellaneous Android Development] Uday Hegde:
Probably many blockdev-details detected by the patch are wrong ( differs from device to device ).

Please check yourself.

(You can check /etc/recovery.fstab from twrp to get those info)
[Miscellaneous Android Development] Razz...:
Dual Rom Boots to Recovery After 5 vibrations

First of all thanks a lot for this useful thread...I followed every steps...my device gets detected...But when I Update Ram disk of primary Rom and install bootui and reboots my primary Rom After 5 vibrations Boots into Recovery.

Added secondary Rom on data slot flashed and booted again 5 vibrations and Boots into Recovery...Tried Adding secondary Rom to system slot as i had free space again 5 vibrations and Boots into Recovery....plzzz help

Also Not getting DBP bootui in Recovery.

Graphics backends showing

Graphics_backends=fbdev
[Miscellaneous Android Development] king4ng:
Not Recognized!

I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'TECNO-C8' is not recognized.

I see other users here having same problems as mine. Please help us bro.
[Miscellaneous Android Development] paeffiong:
This is working flawlessly in my phone the ulefone tiger.
[Miscellaneous Android Development] Madd_Maxx:
When it becomes possible to install Android 8.1 OREO as the second ROM?

Oreo ROM installation is correct, but does not start.

How long to wait? Already appeared beta Android P.
[Miscellaneous Android Development] blacklisted.rock:
Any of you found solution of device codename not recognized problem?

I don't think it's json file.

Because when we try to create patched zip or img, the device is listed and recognized.

I pulled the request to add my device.

It should solve the problem (if it was json file) in next built.

But anyways tell me about your solution !
[Miscellaneous Android Development] blacklisted.rock:
Solution?

Any luck with solution?

I'm having same problem and log is almost same too

I think it's because of wrong partition details
[Miscellaneous Android Development] aureliomilitao:
no possible install DualBoot with Miui multipro in primary and Rom Oreo aosp in data slot?

i try and no Works ... help please
[Miscellaneous Android Development] Reza740:
Hi,first time before I say thanks for this guide,but every step I following my device stuck in twrp mode(everything looks successufully even I reboot manual after update boot ui),this is my device are RN5A ugg,any solution for this suck and I forget my rom is MIUI Pro,thank agains for any suggest solutions.
[Miscellaneous Android Development] joesnose:
Hello and thankyou.

Trying to get this working fails to update ramdisk.

Any suggestions?
[Miscellaneous Android Development] joesnose:
And multirom log.
[Miscellaneous Android Development] joesnose:
Deleted
[Miscellaneous Android Development] joesnose:
Solved the ramdisk issue, was a broblem with my mount points in info.txt.

Now I have a new problem, 5 vibrations upon reboot and then boots to recovery.
[Miscellaneous Android Development] Reza740:
Please for OP,I found this treble check apk from another forum to my device not support partition only A-device,and maybe you can edit for another users,thanks for your guide
[Miscellaneous Android Development] iamaboothahiru:
it's not working for me ,

Some lines missing in info.txt how can I correct the info.txt ,Give me working dbp info.txt *.yml file
[Miscellaneous Android Development] Uday Hegde:
here is an example of info.txt. seperate each value by a space.

sorry, I didn't get you...

that won't be a problem, you can still use app.

but boot UI doesn't works on primary rom.

you can fix it by some modifications in boot.IMG

this patch only tries to add your device name and properties in dualboot patcher's data.

further issues are related to app's source , rom and partition you selected. try changing them all one by one...
[Miscellaneous Android Development] joesnose:
Thanks for response.

i have an x86 device so cant use dualboot utilities . What is the pro ess of manually swithing roms?
[Miscellaneous Android Development] Uday Hegde:
you can just switch within the app and reboot.

or flash boot.img of respective rom from twrp
[Miscellaneous Android Development] joesnose:
Thanks
[Miscellaneous Android Development] yebo1:
Hi, will the dualbooting work for kitkat 4.4 2 phone, and which twrp recovery version should be used? Cus i'm having some error in my info.txt file.
[Miscellaneous Android Development] xd4d3v:
Nevermind :)
[Miscellaneous Android Development] hari_patel:
Its working on coolpad note 5

Thanks for sharing
[Miscellaneous Android Development] drakonknayt:
Please help me

Please help me with adding for officcial devices a Sony xperia Z (c6603)
[Miscellaneous Android Development] Codita123:
I need help

It says could not determine the boot block device, failed to flash ZIP file.

I can't get my boot block. My phone is A5 2016 or a510f. Help me.

:good:
[Miscellaneous Android Development] Bronnel:
I followed the steps its not working on LG V30+, I added pull request and I'm waiting for official support.
[Miscellaneous Android Development] mateHD:
Hi,

I tried to do with Xiaomi MI 8 pro, but after I execute the .sh, the mbtool wont start.

"Faild to update mbtool. Many operations, such as switching ROMs will not work"

Do you have any idea?

Thanks guys

The files:

info.txt

xiaomi.yml
[Miscellaneous Android Development] HemanthJabalpuri:
[MENTION=4277844]chenxiaolong[/MENTION] today announced that dual boot patcher is no longer developed.

https://github.com/chenxiaolong/DualBootPatcher
[Miscellaneous Android Development] king4ng:
I have edited the tecno.yml file in github but cannot commit changes because it is not highlighted to click, please help.
[Miscellaneous Android Development] LgPWN'd:
That's Sad

But it's ok he gave us his blessings to continue the project without him...

So here's to hope that It'll continue on
[Miscellaneous Android Development] :
I hope somebody can get some proper treble support going with this. I was able to get the app and utilities working for treble, switches roms, patches ramdisk, everything appears to work. Primary rom boots fine, secondary rom just sits at the bootanimation. I worked on it for a week and gave up.