Database Info

Noverca HTC Rom - Vodafone Magic - TESTING

hi. it's just a port of daldroid's rom
daldroid said:
OK, I tried to prepare a working rom for you. No patches respect to my original mod for the "other Magics" except for APN list.
changed the kernel and wifi driver for your device, but I'm not able to test it.
So, please, flash this only if you are used to flash firmware and prepared to have a non working system.
I REPEAT. I made this ROM without testing if bootable or working on vodafone and likes Magics. Be prepared to reflash a previous working rom you already flashed and tested.
WARNING !!! WARNING !!!! Please read all the post before trying to flash
FLASH THIS ROM AT YOUR OWN RISK. IT'S UNTESTED
1) Download the file daldroid-untested-vodamagic-signed.zip
2) rename it to update.zip
3) copy to the sdcard
4) start in recovery mode, WIPE and try to update.
Let me know if it works for you.
SUGGESTION: If you can resist to the temptation, allow for somebody else to post if it works or not! ;-)
------ EDIT ----
WARNING THIS ROM IS ONLY FOR VODAFONE AND COMPATIBLE MAGICs. DO NOT EVEN TRY TO FLASH IT ON TIM, ORIGINAL HTC AND MORE IN GENERAL EVERY DEVICE YOU TESTED WITH MY DALDROID ROM RELEASED IN THE OTHER THREAD
WAIT for the download link. Uploading right now
--------------
only english: http://www.megaupload.com/?d=61EQ1YCS
es_pirulo multilanguage http://www.megaupload.com/?d=2OJDFD31
nk02 multilanguage beta2 http://www.megaupload.com/?d=NFHDQFL5 <- with market fix
nk02 multilanguage beta3 http://www.megaupload.com/?d=7OM7CE9R <- market fix + superuser + busybox
--------------
Click to expand...
Click to collapse

Thx - we will test it out.....

Any one try ir yet?

Tested and big bugs for me:
1.- cannot create or sync contacts (manually, google contacts or exchange contacts)
2.- cannot finish google account wizard. It says something about "open your keyboard" and cannot continue.
Anyone have the same problems??

es_pirulo said:
Tested and big bugs for me:
1.- cannot create or sync contacts (manually, google contacts or exchange contacts)
2.- cannot finish google account wizard. It says something about "open your keyboard" and cannot continue.
Anyone have the same problems??
Click to expand...
Click to collapse
Sorry, I'm not able to test this version of the rom because it doesn't run on my TIM magic. Maybe something related to boot.img working for vodafone, maybe something related to fixups.
The original was only an almost vanilla mod of the original rom kindly dumped by joost39. (added adb shell root and disabled rom secure)
Sorry for asking, but did you wipe your existing data and cache partitions when switching from your former rom?
If bugs are confirmed I could try to generate an image as similar to the original as I can (I'll have to change the kernel and wifi, however, but the problems you are reporting don't appear related to HW support in the kernel).
If you didn't wipe, try a wipe of the data and let us know.
Bye
daldroid

daldroid said:
Sorry, I'm not able to test this version of the rom because it doesn't run on my TIM magic. Maybe something related to boot.img working for vodafone, maybe something related to fixups.
The original was only an almost vanilla mod of the original rom kindly dumped by joost39. (added adb shell root and disabled rom secure)
Sorry for asking, but did you wipe your existing data and cache partitions when switching from your former rom?
If bugs are confirmed I could try to generate an image as similar to the original as I can (I'll have to change the kernel and wifi, however, but the problems you are reporting don't appear related to HW support in the kernel).
If you didn't wipe, try a wipe of the data and let us know.
Bye
daldroid
Click to expand...
Click to collapse
I've made the process of "apply updates" two times (both of them wiping first).
I'll try to format the sd card and start the process again.
I think it's something related with the HTC Dialer.

es_pirulo said:
Tested and big bugs for me:
1.- cannot create or sync contacts (manually, google contacts or exchange contacts)
2.- cannot finish google account wizard. It says something about "open your keyboard" and cannot continue.
Anyone have the same problems??
Click to expand...
Click to collapse
I have the same proplems, I hope that nk02 will fix this

No its not working.... Yet

OK, I tried to prepare a working rom for you. No patches respect to my original mod for the "other Magics" except for APN list.
changed the kernel and wifi driver for your device, but I'm not able to test it.
So, please, flash this only if you are used to flash firmware and prepared to have a non working system.
I REPEAT. I made this ROM without testing if bootable or working on vodafone and likes Magics. Be prepared to reflash a previous working rom you already flashed and tested.
WARNING !!! WARNING !!!! Please read all the post before trying to flash
FLASH THIS ROM AT YOUR OWN RISK. IT'S UNTESTED
1) Download the file daldroid-untested-vodamagic-signed.zip
2) rename it to update.zip
3) copy to the sdcard
4) start in recovery mode, WIPE and try to update.
Let me know if it works for you.
SUGGESTION: If you can resist to the temptation, allow for somebody else to post if it works or not! ;-)
------ EDIT ----
WARNING THIS ROM IS ONLY FOR VODAFONE AND COMPATIBLE MAGICs. DO NOT EVEN TRY TO FLASH IT ON TIM, ORIGINAL HTC AND MORE IN GENERAL EVERY DEVICE YOU TESTED WITH MY DALDROID ROM RELEASED IN THE OTHER THREAD
WAIT for the download link. Uploading right now
--------------
http://www.megaupload.com/?d=61EQ1YCS
--------------

I´ll test it out when my new Vodafoneunit arrives! Thx Daldroid

daldroid said:
OK, I tried to prepare a working rom for you. No patches respect to my original mod for the "other Magics" except for APN list.
changed the kernel and wifi driver for your device, but I'm not able to test it.
So, please, flash this only if you are used to flash firmware and prepared to have a non working system.
I REPEAT. I made this ROM without testing if bootable or working on vodafone and likes Magics. Be prepared to reflash a previous working rom you already flashed and tested.
WARNING !!! WARNING !!!! Please read all the post before trying to flash
FLASH THIS ROM AT YOUR OWN RISK. IT'S UNTESTED
1) Download the file daldroid-untested-vodamagic-signed.zip
2) rename it to update.zip
3) copy to the sdcard
4) start in recovery mode, WIPE and try to update.
Let me know if it works for you.
SUGGESTION: If you can resist to the temptation, allow for somebody else to post if it works or not! ;-)
------ EDIT ----
WARNING THIS ROM IS ONLY FOR VODAFONE AND COMPATIBLE MAGICs. DO NOT EVEN TRY TO FLASH IT ON TIM, ORIGINAL HTC AND MORE IN GENERAL EVERY DEVICE YOU TESTED WITH MY DALDROID ROM RELEASED IN THE OTHER THREAD
WAIT for the download link. Uploading right now
--------------
http://www.megaupload.com/?d=61EQ1YCS
--------------
Click to expand...
Click to collapse
I'm going to work now. I'll try it this afternoon.

Any one tried this rom ? please keep update others. I am waiting for my magic.

I have installed it.
All seems to work ok!!!
But it's only in english.

oscar.palomar said:
I have installed it.
All seems to work ok!!!
But it's only in english.
Click to expand...
Click to collapse
In order to debug the problem with contacts ppl reported, I made the image as much like to the original as possible.
I suppose you can clear conf settings in menu->settings->applications
or just copy system/customize/CID/default.xml from the update.zip
adb remount
adb push ....
reboot and verify if all the languages are unlocked.
Or wait for the next rom image ;-)

daldroid said:
In order to debug the problem with contacts ppl reported, I made the image as much like to the original as possible.
I suppose you can clear conf settings in menu->settings->applications
or just copy system/customize/CID/default.xml from the update.zip
adb remount
adb push ....
reboot and verify if all the languages are unlocked.
Or wait for the next rom image ;-)
Click to expand...
Click to collapse
i'm uploading a multilanguage version for you

sounds good thanks a lot. waiting for multilanguage version fix.

WARNING: As TIM htc rom, the market of this rom doesn't have all apps!

Thank you for your work again.
Downloading and will post results in a while...

thank you for all. I have to follow these steps to flash with this rom right?
1. Copy to sd card as "update.zip"
2. Reboot into recovery mode (HOME+POWER)
3. Wipe (option that has [ALT+W] beside it)
4. Apply update (option with [ALT+S] beside it)
5. Reboot (HOME+BACK)
enjoy.

janjan said:
thank you for all. I have to follow these steps to flash with this rom right?
1. Copy to sd card as "update.zip"
2. Reboot into recovery mode (HOME+POWER)
3. Wipe (option that has [ALT+W] beside it)
4. Apply update (option with [ALT+S] beside it)
5. Reboot (HOME+BACK)
enjoy.
Click to expand...
Click to collapse
right! (with the testkey recovery )

Screen does not respond while using Android

I have tried both Incubus26jc's Super Froyo (RLS8) and VaniljEclair RLS7c . I manage to install them in sd card (I want to use them via haret.exe) but when I reach the welcome screen where I have to touch the android to continue, the screen does not respond ( D-pad and center button work). Could someone help me? I decided to open a new thread because of what I have searched, I found only one member with a similar (but not the same) problem
The installation method I follow is this (mostly copied from a SuperJMN's post):
1º Run HaRET
2º From the installer, select Install System
3º Choose install update (if any)
4º Choose to fix permissions (if there had been an update)
5º Reset (don't select "Quit", just reset, this is to avoid problems)
6º Wait for Windows Mobile to start and run HaRET again.

Although I am flashing to nand and you are using haret/zimage, we may have the same problem with the unified touch screen driver that DZO implemented around 16 June. Is there is a way to use the kernel .nbh and system .tar with haret, rather than zimage? If so, you might try using an older kernel from before 16 June ... or perhaps an older zimage.

I have similar problem, if not the exactly the same. Using an older kernel seems to be a workaround of this problem. hxxp://forum.xda-developers.com/showpost.php?p=7041656&postcount=21 (You need to fix the hxxp as appropriate as I am not allowed to link URL yet)

i have the similar problem too, havent fixed it :/

I tried zImage-12-06-10 (the last one before the 16th of June) and installation procedure did not even start. But zImage-29-04-10 worked for me. However, Froyo is not that fast. If I change any files (zImage or something else) is it possible to have a speed improvement?

Same problems.
All Android realeases work on my pola100 only with zImage 29.04.10.
No work with other kernel.
I suggest to developers to analyse 29.04.10 and try to understand WHY this works and others no.
Regards.

regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
also check this for solution from k_k
HTH

mensa07 said:
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
Click to expand...
Click to collapse
Those are the changes after which my touchscreen stopped working.
mensa07 said:
also check this for solution from k_k
Click to expand...
Click to collapse
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!

tmcfarland said:
Those are the changes after which my touchscreen stopped working.
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
Click to expand...
Click to collapse
you can use terminal or adb to change the value

files for a fast android version
Could someone with a fast and stable version of eclair or froyo please tell us what files did he/she used to make that happen because I installed incubus froyo build and it is a bit slow? I am talking about installing it in my sd card and run it using haret.exe

[GPL][updated 03.02.2011] Kernel with minimized touchscreen bug

I did dirty hack: insert msleep(1) after each input thread synchonization in mcs6000 driver.
Now hack is not dirty, just found that driver has native implementation of "sleep".
Result: 15-30% cpu use with tap down.
Included all tweaks from GNM OC Kernel.
Packaged in koush's anykernel for compatibility with any rom.
Do not forget to make nandroid backup first.
Probably fixed "scroll bug".
v1.1: added pressure sensitivity (works correctly only for single touch because of our touchscreen).
Link: http://www.mediafire.com/?li7aviy6awdebs5
Sources: https://github.com/mik9/ThunderG-Kernel

I triwd to flash it,but when i flash i have error,one file isn't in the zip

Redownload. I updated zip few minutes ago.

Do i need to clean all my data, or i only need to flash the Kernel?

Got errors while flashing the zip.
Code:
E:Wrong digest: META-INF/com/google/android/updater-script
E:Verification failed
Installation aborted.

RevengeFNF said:
Do i need to clean all my data, or i only need to flash the Kernel?
Click to expand...
Click to collapse
No. Only apply kernel.zip via recovery (that flash new kernel).
domenic_s said:
Got errors while flashing the zip.
Code:
E:Wrong digest: META-INF/com/google/android/updater-script
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
Ok, so i need to sign it. Will fix this in a few minutes.

it does not work, just tried to flash in custom recovery, it says missing something. turned off verification and again the same problem.

mik_os said:
No. Only apply kernel.zip via recovery (that flash new kernel).
Ok, so i need to sign it. Will fix this in a few minutes.
Click to expand...
Click to collapse
i have this problem please fix it thank

ok did post it too late haha hope that u have done a great step mike thx for everything

Updated link in first post.

About unsigned zip files
You can flash unsigned zips. In the recovery menu just select Other -> Toggle Signature Verify. It will disable this verify.
About this hack. It's working. BUT the scroll works buggy now. For example, you cannot make the contacts menu scroll from the beginning to the end fast now

I flashed it...and hey: IT WORKS. Well done mik_os.
//edit: just recocknized the bugs on scrolling...that sucks.

kashtancheg said:
You can flash unsigned zips. In the recovery menu just select Other -> Toggle Signature Verify. It will disable this verify.
About this hack. It's working. BUT the scroll works buggy now. For example, you cannot make the contacts menu scroll from the beginning to the end fast now
Click to expand...
Click to collapse
I would not say that it became too buggy, only a little bit (very little). And maybe you have too much contacts in youe contact list

nope it works really nice here mik thx alot for fixing this

unbelievable, it works!

miki, is it possible insert some double or something with float value? I mean if it is possible do less that 1 millisecond? For example msleep(0.5)? It will be faster for scrolling, but will not do loop on touch.
//Edit:
It should be possible... http://www.handyboard.com/oldhb/software/icmanual/node86.html
//Edit2:
or maybe use usleep(microsecond)

We can't use usleep in kernel level code because it is libc function. And msleep accept only integer (int/long).

Genius things are always simple! The bug wich couldn't be solved for 3 years!
Mik, I think you should work in google
NFS Shift runs perfectly now when applying the brake!

kashtancheg said:
Genius things are always simple! The bug wich couldn't be solved for 3 years!
Mic, I think you should work in google
NFS Shift runs perfectly now when applying the brake!
Click to expand...
Click to collapse
The bug in our phone is not related to famous bug in android issue tracker. And my hack is little bit crappy

Mik os you are a god XD thank you for this kernel work very very good

Multi Boot Menu for Xperia Z1 Compact

Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse

No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:

munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app

Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it

Sounds definitely awesome!

Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.

Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!

munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?

XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!

munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL

XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!

munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.

New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!

I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?

munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback

Solved! Will give you soon cm11 in multiboot!

munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:

Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!

Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47

Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?

[GUIDE][APP][ANDROID]DualBoot Patcher on Unsupported Devices, Add Official Support

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 @chenxiaolong.
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/
Code:
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 :-
Code:
su
dbp.sh
Your device should support now.
For confirmation ->
it should ask to set kernel when you open roms section.
Set kernel, update-ramdisk in primary-rom's options, do not reboot.
Install boot ui in settings.
Now reboot to check whether boot ui is working or not.
A twrp like screen will appear during boot if its working.
If boot ui is not working, try to change graphics backends value in info.txt and reflash PATCH_DATA
No worries if boot ui is not working, you can still use the app to dual boot roms on your device
Click to expand...
Click to collapse

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.

After getting support for your device, if you are strugling to use it,
Just google or youtube for dual boot patcher.
Its way of use are same on almost all devices.
Click to expand...
Click to collapse
Original thread by Chenxiaolong
https://forum.xda-developers.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..??
1. Just download apps and patches from download section.
2. Install app, open roms section there.
3. Now reboot to twrp,
flash GET_PROP.zip and then flash PATCH_DATA.zip(should be in this order)
4. Reboot to system, open terminal emulator app and type :-
Code:
su
dbp.sh
5. Now DualBoot Patcher should work on your device
Click to expand...
Click to collapse
Something went wrong.I need help...
You are most welcome...
But please come up with info.txt, <brand>.yml and MultiBoot/devices.json
that are created in the storage(internal or external, & mention it)
Dont forget to have look into comment section befor reporting, it may solve your probleams sometimes.
Click to expand...
Click to collapse
Stuck at Roms section, what can be done.??
Probably it is not possible to make a full support for your device,
But still its possible to dual boot using this app,
But you need to try lot of workarounds by your own.
Click to expand...
Click to collapse
Not showning any device in patch roms section..!!
1. Find patched devices.json yourself,
2. Place it in internal storage.
3. Create it's symlink to /data/data/com.github.*/files/*/here.
(You can use Root Browser or romtoolbox)
Click to expand...
Click to collapse

Good @Uday Hegde.
It will help a lot of people.

kuberrocks96 said:
Good @Uday Hegde.
It will help a lot of people.
Click to expand...
Click to collapse
Thanks

flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip

kutlay1653 said:
flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip
Click to expand...
Click to collapse
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..

Uday Hegde said:
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..
Click to expand...
Click to collapse
Mt6592 General Mobile etab5 fstab in zip file

kutlay1653 said:
Mt6592 General Mobile etab5 fstab in zip file
Click to expand...
Click to collapse
Check with this...
Ill add it to the main thread if its working...

Uday Hegde said:
Check with this...
Ill add it to the main thread if its working...
Click to expand...
Click to collapse
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 ?

kutlay1653 said:
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 ?
Click to expand...
Click to collapse
Sorry, i hav no idea about that issue
You may try with older vesions...
Wait @kutlay1653 check this :-
Uday Hegde said:
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
Click to expand...
Click to collapse

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

Mohd.faraz.abc said:
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
Click to expand...
Click to collapse
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

Uday Hegde said:
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
Click to expand...
Click to collapse
Tried and now same error and one more thing I think this is responsible for this. Please see attachment

Can't download patch_data.zip....
It says authorised download...

sagargjasani264 said:
Can't download patch_data.zip....
It says authorised download...
Click to expand...
Click to collapse
Mirror added in download section..
Mohd.faraz.abc said:
Tried and now same error and one more thing I think this is responsible for this. Please see attachment
Click to expand...
Click to collapse
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:

After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..

sagargjasani264 said:
After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..
Click to expand...
Click to collapse
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)

Stuck at this section

kutlay1653 said:
Stuck at this section
Click to expand...
Click to collapse
Ohh
Thats new issue that i saw..?