Database Info

[ROM] Marina Rom Lite for ALCTAEL OT 990

Marina ROM lite [Eng] based of stock firmware 2.3.4 for Alcatel OT 990​
The fast,lightweight,modified with many tweaks and new capabilities firmware based of stock!
Installed:
CWM Recovery
Rooted,SuperSu and Busybox
Scripts of init.d (ZipAlign, defrag db, scheduler for block and increased caches,fast speed net and more...)
ZArchiver - applications work with archives
Zeam launcher - lightweight launcher
Swype keyboard (only Ru,Eng language pack added)
QuickPic - alternate fast gallery
ClockSync - sync time app
exDialer - dialer from MIUI
Root Explorer - file manager
DSP Manager - EQ from cyanogen
Removed:
many third-party applications of google and alcatel
Modified:
Status bar with widgets "quick settings" and control brightest by slide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(widgets support long tap and slide on line of this right/left)
Power menu with "reboot and recovery"
Changed the graphics system and animation
Reconstructed Phone.apk with Contacts.apk (support large avatars)
CRT effect for lock keyboard (must active animation)
Hosts "no ads"
and other...
Warning:
All data will be erased
Only for pre-installed firmware 2.3.4 Gingerbread
Install this ROM via CWM Recovery as install zip from sdcard
marina rom lite
Read this post .::Upgrade backup & restore zip, odexed deodex rom for Alcatel OT 990 to learn more new possibilities::.
ICS Style for Marina Rom (screenshots)

Thanks Gulyuk, great job!!!

if you want,I can add patch for CRT effect on unlock keyboard,later
for all errors, bugs and suggestions please contact us here
Gulyuk.s

ext partition
this rom can handle the extended partition ?
the original 2.3 cannot

kergekecske said:
this rom can handle the extended partition ?
the original 2.3 cannot
Click to expand...
Click to collapse
No, without sources of kernel can not,but can move the dalvik-cache from / data to /cache or / custpack and free up space under apps
for this I'm used the script
Gulyuk.s

flashed through cwm : endless boot loop

kergekecske said:
flashed through cwm : endless boot loop
Click to expand...
Click to collapse
if you have firmware 2.2.2 that's impossible for you
Yes or No?

from 222 to marina - bootloop , alcatel logo back to android and again
i reflashed an frg83g.v53-b (uk) version thru cwm - it works
i try to flash marina again ...
---------- Post added at 01:01 PM ---------- Previous post was at 12:49 PM ----------
situation is the same like in post 6
froyo back

kergekecske said:
from 222 to marina - bootloop , alcatel logo back to android and again
i reflashed an frg83g.v53-b (uk) version thru cwm - it works
i try to flash marina again ...
Click to expand...
Click to collapse
frg83g.v53-b this assembly-based on firmware 2.2.2 and you must stop process,when you once upgraded to 2.3.4 then try again flashed marina

It works perfectly,thank you gulyuk.s

So,if you not uses the CWM recovery,I can create this ROM as fastboot flashable
needed it ?
also I upgraded my "backup and restore scripts for recovery" (added backup userdata and recovery) and after my work time upload it
Gulyuk.s

no luck
No luck for me. I contacted you via twitter.
Anyway - I tried wiping the partition/data, and still nothing.
I even created img files for the fastboot, and now I'm not in a boot loop, but I'm stuck in bootsplash logo (ALCATELonetouch) with black background.
Previous ROM was Froyo 2.2.2 (debranded).

Никола said:
No luck for me. I contacted you via twitter.
Anyway - I tried wiping the partition/data, and still nothing.
I even created img files for the fastboot, and now I'm not in a boot loop, but I'm stuck in bootsplash logo (ALCATELonetouch) with black background.
Previous ROM was Froyo 2.2.2 (debranded).
Click to expand...
Click to collapse
you must pre install official firmware 2.3.4 via one touch upgrade then try again flash this update.zip
flashed custom rom of 2.3.4 on rom of 2.2.2 - not compatible
Gulyuk.s

Help!
Hello Gulyuk.s!
I think you're the right guy to ask bout this,
I have this device OT 990 i was successfully rooted this device using Super oneclick when it was in the lower version Froyo. But then I used to update my device using OTU and give me a Gingerbread version which In this version I cannot root my phone even to down grade the version or to rollback the previous version in short i hate it! Is there any way to solve my problem? I've backup my previous version using Clockworkmod (CWM) is there a chance to put back my backups to my device? I can't even run properly my CWM because I don't have permission to my device .
I have this files in my backup folder of CWM ( .android_secure, boot, cache, data, nandroid.md5, recovery, system, and update.zip)
Hope I can get some feedback from you..... Thank you...
dude,

First,there's no working solution to downgrade from 2.3 to 2.2.Second,I think your backup is useless,because i don't see the custpack partition of the phone in your list(that part. holds half of system apps and related files).Your only option now is using a custom,pre-rooted ROM.(e.g. this ROM).

great..
and will be waiting for more languages update..
arabic letters reversed like in 2.2.2 and 2.3.4
but there was windows application to convert framework.jar, libwebcore.so and some other lib files.. to a files support arabic . not the menus just reading and writing.. "
its arabic_script_0.906_windows i guess

2.2.2 -> 2.3.4 not possible
gulyuk.s said:
you must pre install official firmware 2.3.4 via one touch upgrade then try again flash this update.zip
flashed custom rom of 2.3.4 on rom of 2.2.2 - not compatible
Gulyuk.s
Click to expand...
Click to collapse
Oh, didn't know that!
Спасибо, друг

Никола said:
Oh, didn't know that!
Спасибо, друг
Click to expand...
Click to collapse
sorry ^^ но почему ты в личку не написал сразу по русски?
вам не дали обновления до 2.3 что ли?
hi dude000143
If you want to downgrade to 2.2.2 - grieve you, it is not possible
but you can get root permission, flash this recovery via fastboot
View attachment recovery.img
use this command when your device connected with pc in mode fastboot:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
and via recovery you must flash supersu.zip
View attachment su.zip as install zip from sdcard
good luck ^^
Mr-m07
give your backup files of boot.img,system.img and custpack.img
I need to install and disassemble your firmware

gulyuk.s
the same img files in your rom

Mr-m07 said:
gulyuk.s
the same img files in your rom
Click to expand...
Click to collapse
I did not understand you
Is your firmware available without Arabic?
Gulyuk.s

[RECOVERY] ClockworkMod Recovery 5.0.2.8 for vc088x tablets |v1.1b| 30-4-2012

ClockworkMod Recovery 5.0.2.8 unofficial port for Vimicro vc088x based tablets v1.1 beta by mikeNG a.k.a mikeioannina
Info:
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain 3e recovery and uses Edify scripting exclusively.
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
More info about creating your own update-scripts is here.
Disclaimer:
This is still experimental.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR TABLET!
Some options might not work correctly and you might brick your tablet and/or lose your personal data!​
Features:
ADB root shell in recovery
Options:
Reboot system now
Apply update from sdcard
Wipe data / factory reset
Wipe cache partition
Install zip from sdcard
----Choose zip from sdcard
----Apply /sdcard/update.zip
----Toggle signature verification
----Toggle script asserts
----Choose zip from internal sdcard
Backup and restore
----Backup
----Restore
----Advanced restore
Mounts and storage
----Mount / unmount /sdcard
----Mount / unmount /emmc
----Mount / unmount /system
----Mount / unmount /data
----Mount / unmount /cache
----Format /sdcard
----Format /emmc
----Format /system
----Format /data
----Format /cache
----Mount USB storage
Advanced
----Reboot recovery
----Wipe Dalvik Cache
----Wipe Battery Stats
----Report Error
----Key Test
----Partition SD Card
--------Ext Size
--------Swap Size (Set this to 0)
--------Rest Size (vfat)
----Fix permissions
Power off
Requirements:
Basic skills in using adb or terminal emulator.
Installation:
It is recommended to do a clean install with this FlashTool first, then install the recovery image, so there is no problem with the sizes of the partitions of the internal sd.
1. Unzip the file you downloaded, you will get recovery.img
2. Copy recovery.img in your sdcard
3. Now type the following command in adb shell or in Terminal emulator:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p3
4. It will show a message after a while, it means it's completed
Usage:
1. Turn off the device
2. Turn on the device
3. When the boot logo appears, press immediately the menu button and hold it down for 3sec approximately.
Working:
Not everything is tested yet. You are the testers for the most of the things. I've tried a backup & restore, it worked. Also tried installing a modified kernel image, it worked too.
Known bugs:
Some errors about /cache are displayed when you boot, factory reset or wipe cache. They stop if you go every time under "mounts and storage" and you mount the cache partition.
Download links:
v1.1 beta for Haipad M8 1GB version
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
koush: for making this wonderful recovery
Cyanogen: for all the support for android
ilarrain & teamhacksung: the fixes for the 32bit framebuffer problems​

Changelog:
24-11-2011 / ClockworkMod Recovery 5.0.2.6 v1.0a
- Initial port for the M8
- Removed multiple "No" prompts in confirm dialogs
- Fixed screen update bug
25-4-2012 / ClockworkMod Recovery 5.0.2.8 v1.1b
- Ported latest CM7 Recovery
- Fixed 32bit framebuffer (multiple screens) problem. Now the image is perfect
- Capitalized first letter of all menus in the recovery
- Changed the color from default orange to default ICS blue on the menus
To Do:
- Add support for more vc088x based tablets

is this still working?

Terramoto said:
is this still working?
Click to expand...
Click to collapse
Yes but I lost the sources so I can't build anything new

how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........

ss429842 said:
how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........
Click to expand...
Click to collapse
I didn't unpack the image, I compiled from source. Unfortunately I lost the modified sources so I can't help you :/

[ROOT][ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM

SliPer ModRecovery and G1317D RootROM. What are they?
SliPer ModRecovery is a custom Andriod system recovery. G1317D RootROM is a custom ROM for Gigabyte GSmart G1317D smartphone with Dual-SIM support. Several versions of G1317D RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1317D RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1317D RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1317D RootROM preserves SliPer ModRecovery on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1317D RootROM by using SliPer ModRecovery?
Before calling for service install G1317D RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1317D RootROM?
NO userdata will be erased during G1317D RootROM installation process, but it would be better to backup your valuable data anyway!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1317D RootROM by using SliPer ModRecovery.
Download one of G1317D RootROMs:
G1317D-0.50.4_pl_cz.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1317D-0.50.4_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
Then copy update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable for your G1317D from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder.
Then turn off your device, insert SDCard (with update1.zip/update.zip located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. Confirm the update. Smartphone will reboot once during the installation process and boot up in normal mode with SU and BusyBox installed after everything will be completed. Enjoy!
In order to check whether you've got SliPer ModRecovery properly installed, delete/move update1.zip/update.zip from the root of SDCard, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then SliPer ModRecovery has been installed properly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM

Installed and it works.
Can I use an A2SD script with it?

If you're talking about partitioning SDCard in ext3/ext4 and moving apps to SDCard ext partition then I think it won't work because kernel hasn't been changed. If I'm not wrong this function should be supported by kernel to work properly and the stock kernel isn't able to handle ext partitions.

Hi! May be I dont understand but for why it needed?
Root & busybox everyone can do by yourself…
What more?
Better will be if <entuziasts> doing for supporting by device of swap file, because it device is lowprice cause it RAM mem very small…
А теперь на родном ;-)
Почему бы не сделать возможность устройством поддержки свап?
Это было бы куда востребованее…
На смарте катастрофически не хватает оперативки для 2 приложений.
Очень прошу прислушаться к моему сообщению.
Спасибо!

Thanks for sharing.

I prepared a custom ROM for this model but I got flashing GSmart logo and an exclamation mark time after time. Android Kitchen hasn't found any errors in ROM. What causes that error?

hi sliper123 bro...
where do I could find fastboot mode driver for gsmart G1315??? thank you before...
Sent from my Nexian-A895 using Tapatalk 2

[UPDATE-v3.3][PORT][RECOVERY] Carliv Touch Recovery For Iris458Q/XOLO-Q600/CROSS A88

This is the port of Carliv Touch Recovery v3.3 based on latest ClockWorkMod 6.0.5.1 for LAVA Iris458Q
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is kitkat based recovery and has full SELinux support .Since LAVA iris458Q , XOLO Q600 and CROSS A88 are similar (clone) devices . This recovery should work on these devices . Test at your own risk . And always have a backup before flashing anything .
NOTE: Don't use this recovery on any other device except above specified devices !!!
Changelog by Master Carliv
Version 2.7 update (11-dec-2014):
- rebuilt from base (cwm 6.0.3.7) and add improvements on top.
- reintegrated bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- better compressed backups integration - pigz support from cm-11
- new "nvram backup/restore" menu functionality: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- the recovery has now an increased stability, many issues are solved
- the content of the backup folder will contain only what an usual clockworkmod backup contain, and that will make it easy to restore backups made with older versions.
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- some other changes.
Click to expand...
Click to collapse
Version 2.5 update (29.06.2014):
- cleaned up the source code
- removed "wipe all" option from wipe menu (too many users wiped their system and blamed me); if you need to wipe system, use "format system" from "mounts/storage"
- rearanged menu order in root menu to restore CWM order
- added a "nvram backup/restore" menu in "carliv" section: the nvram partition will be backed up in clockworkmod/backup folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- some other small changes.
Click to expand...
Click to collapse
Version 3.3 last release (21-apr-2015):
- based on cwm (cwm 6.0.5.1) and added improvements on top.
- bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- many fixes in code;
- cleaned up the source code;
- reset battery stats option;
- wipe all - preflash option;
- removed nvram backup/restore because it can corrupt the bootloader;
- a new advanced backup/restore menu
- separate power and wipe menu
- aroma file manager integration (you can flash the attached AromaFM_installer.zip in recovery, and that will place the aromafm.zip at its place).
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
Click to expand...
Click to collapse
Some screenshots of Recovery
​
DOWNLOAD:Check the attachments-for older JB stock kernel based and for new-Drive​
Installation:
First rename the file to recovery.img then for
Mobile -> copy to sd card and flash using Mobile Uncle Tools.
or
PC -> Use SP Flash to flash it to phone.
or
For latest version directly flash the recovery zip in custom recovery or extract recovery.img and follow above methods.​
Kernel Source:GitHub​
Credits:
@Doha for his KK kernel
@carliv for his awesome recovery
@carliv for his user friendly guide
@Koush for his amazing CWM recovery
@Napstar for his full touch modules
@bgcngm for his unpack/repack utils
@sk8erwitskil for aromafm menu​If anybody missed PM me​
If you have Mediatek MTK android and your model is not listed anywhere in xda and if you want a custom recovery use MTK droid tools for windows or click on below links to port a custom recovery for your device.
http://forum.xda-developers.com/showthread.php?t=2648309
http://forum.xda-developers.com/showthread.php?p=46206519
http://forum.xda-developers.com/showthread.php?p=52851128
http://forum.xda-developers.com/showthread.php?t=2759981
http://forum.xda-developers.com/showthread.php?t=2201860

[APP][Official]Dual Boot Patcher for Samsung Galaxy J2 (J23G-SPRD)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About Dual Boot Patcher
Dual Boot Patcher will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary. Huge thanks to @chenxiaolong for his wonderful app.
This app patches
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
How to use the patcher
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Instructions for dual booting
The patcher offers several locations for installing ROMs
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
NOTE:
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
If you want to dualboot a TouchWiz ROM, I highly recommend installing TouchWiz as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How do I.. blah blah..?
Switch the ROM from custom recovery if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Unofficial App/Apk : https://drive.google.com/open?id=0B7BTXFMgzL4rRXNBZUhaWl9PdWs
Unofficial DualBootUtilities : https://drive.google.com/open?id=0B7BTXFMgzL4rckFVZllCUV9DZ2s
Official Downloads : https://dbp.noobdev.io/downloads/
XDA:DevDB Information
Official Dual Boot Patcher for SM-J200H/DD
Contributors
Parthib, Lzzy12, samankh
Source Code: https://github.com/Parthib24/DualBootPatcher_downgrade
Version Information
Status: Testing
Main/Official Source code
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Created 2017-08-21
Last Updated 2017-08-21

Reserved
Now Its Official.!