Develop Bugs

[APP][Unofficial]Dual Boot Patcher for Xperia M - Sony Xperia M

Hello all, I added support for Xperia M single and dual sims in Dual Boot patcher, but since my phone is bricked, I couldn't test before I make this release, however I am sure it should work as expected. Test and give your feedback ​
{
"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"
}
I am proud to present first Dualboot project For Xperia M. This 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 (like /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Xperia M to the DualBootPatcher App, I am not the developer, I am just the maintainer.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM 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. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app from the download section below.
4. Root
What does the app do ?:
It 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 App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set correctly and under Partition configuration select secondary (will install 2nd ROM in /system) or data or external SDCard slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like LOS13-20170807-nicki-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
Other How to ?
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".
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
Source:
Source
All Releases:
Releases
Downloads:
In attachments
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@RendyAK for inspiration, help and tips
@yshalsager For help and tips
Enjoy ​

Reversed

Thanks man for your work. I installed second rom in external sd card but I forgot to flash magisk zip file. Now my device boots into second rom but I don't have root access and if I install anything through twrp, it will get installed in system partition which is not the partition for second rom. What should I do now?

hhjadeja007 said:
Thanks man for your work. I installed second rom in external sd card but I forgot to flash magisk zip file. Now my device boots into second rom but I don't have root access and if I install anything through twrp, it will get installed in system partition which is not the partition for second rom. What should I do now?
Click to expand...
Click to collapse
You should read the thread​
Anyway, install DBP apk on the secondary rom too, from there you can switch roms
For your root problem, anything that you want to flash into the secondary rom should be patched too; for example you patched LOS13 with the id "secondary" to be installed in external SD card and you want to have root and gapps too, so you have to patch supersu.zip and gapps.zip with the id "secondary" to be installed into external SD card too.
it is simple, and please read the thread next time :good:

Mysteryagr said:
You should read the thread
Anyway, install DBP apk on the secondary rom too, from there you can switch roms
Click to expand...
Click to collapse
Thanks man for help. I thought I would be needing root access for switching the roms. But it turns out that I don't require root for that. Thanks again
And one another important thing, magisk v13 is not supported in dual app patcher. So ig you want root then flash v12

any plan make this app to official, , ,

hhjadeja007 said:
Thanks man for help. I thought I would be needing root access for switching the roms. But it turns out that I don't require root for that. Thanks again
And one another important thing, magisk v13 is not supported in dual app patcher. So ig you want root then flash v12
Click to expand...
Click to collapse
- Use superSU.zip on the secondary rom
- One important note: If you are stuck, or having a bootloop and can't boot into primary rom, reboot into recovery and flash boot.img you backed up when you first used the app, its location is on internal memory, and you can use the same steps to switch to the secondary rom without using the app.

mika21 said:
any plan make this app to official, , ,
Click to expand...
Click to collapse
Already done a pull request to support this app officially, the original developer should accept it, if he done so, you can enjoy official releases and automated builds

Great thread sir !!! , sorry too late reading. Will try this soon

Nicklas Van Dam said:
Great thread sir !!! , sorry too late reading. Will try this soon
Click to expand...
Click to collapse
waiting for feedback

Official support has been added
https://dbp.noobdev.io/supported_devices.html

i will download second rom and try it out

trexv2 said:
i will download second rom and try it out
Click to expand...
Click to collapse
Don't forget to give a feedback

can i use it for sony m2 dual sim D2302?

hooooossamq said:
can i use it for sony m2 dual sim D2302?
Click to expand...
Click to collapse
No

Update Ramdisk Problem
Hello,
I sucessfully installed the app on my xperia m ss. The first step to set the kernel worked, but when i want to update the ramdisk, I'll get the error: "Failed to update ramdisk".
I tried 3 different kernel (alexa, nova and stock one), but I get the same error. --> Log is attached
Can you please tell, wich kernel works for the xperia m SS 15.4.A.1.9 Firmware
Thanks,
Peter

Related

Hi all,
This is not squashed ROM for EU HD2 which contains all files from the stock RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed. Yes of course some executables(akmd, reboot, vold), some libraries, some config files and kernel were replaced for Leo. The reason of why I do this is my wish to have Desire HD ROM on my EU HD2 which is closest to stock.
The ROM size is about 407M. I do not like squashed ROMs. We all have sdcards and I do not see any sense to make squashed ROM. Therefore this build uses the second partition of sdcard to store dalvik cache, data, system apps, framework. So size of this rom in NAND is 391Mb, and in sdcard is 16Mb. I recommend you to use 1024MB second partition, but not less.
My CWM installation script mounts the second partition of sdcard to /data, creates sysfiles directory and copies /system/etc/clockwidget, and /system/etc/slideshow and /system/etc/soundimage to this second partition into /data/sysfiles directory. After that the script creates symbolic links to these three directories in /system/etc direcory, and copies all other files of ROM to system partition in NAND. So we have 391Mb of files in NAND, and 16Mb of files in the second partition of sdcard.
The kernel mounts the second partition of sdcard to /data before the init.rc script will be run. Therefore android use this partition as internal storage, and we see free space of this partition as free phone storage in info.
The content:
- Full stock Desire HD RUU 1.72.405.3
- Last Gauner's kernel.
- Fixed mms.
- Fixed WiFi MAC.
- Fixed su.
- Fixed sql lib.
- Fixed first and external partition mounting.
- Percent battery.
- Rmnet is ON by default, if you would like to enable ppp you should create ppp file in /system directory and reboot your phone. To create the ppp file you should connect your phone to PC and run this command in a terminal:
adb shell touch /system/ppp
You should delete this file and reboot your phone if you would like to enable rmnet again:
adb shell rm -f /system/ppp
Not worked:
- 720p recording
- bluetooth MAC
Removed apps:
- Ereader. Use the attached archive if you would like to use ereader. Install it by CWM.
Link to ereader
"How to install" is in the readme file of the build. Please, read it! This ROM is only flashable using ClockworkMod. CWM v 1.2 is included into archive of this build. Note, system partition in NAND should be 399Mb.
CWM v 1.2 fix:
If you would like to use CWM backup and restore you should replace CWM initrd.gz file on this file. I fixed CWM to soppurting partition layout without userdata partition..
Update the previous version ROM:
If you would like to update the previous version you should not touch your sdcard. You should do this only: format NAND by task29, install magldr, flash new CWM partition layout, install new ROM.
Recommendations:
- I recommend to format NAND by task29 before install this ROM. After formatting will be done you should install magldr again. All tools are included into the archive.
- I recommend to calibrate G-Sensor. To do it go to Seetings->Display->G_Sensor calibration->, place your phone FACE-DOWN on level surface, press Calibrate button. After calibration will be finished press Ok button.
- If you would like to use the "backup second partition" feature in CWM, the second partition should be labeled as sd-ext.
- Sometimes magldr does copying of data with errors(lost data) in the "USB MassStg" mode, but you do not see these errors. Next you can see that the ROM installation was finished shortly. If it happens you should look into CWM log and you will see some errors of files extraction from archive. If you will copy this archive to sdcard again, but only by CWM or by other cardreader, you will not see these errors in CWM log. Therefore I recommend you to copy ROM zip to sdcard by CWM or by other cardreader.
- To get a CWM log you should do this:
a) Install the ROM
b) After the installation will be completed you should not reboot your phone! Go to "advanced" item of CWM menu.
c) Next select "Report Error" item. CWM will create the clockworkmod directory in root of sdcard.
d) Next copy the recovery.log file from the clockworkmod directory and attach this file to the thread. I will check it.
- The first loading(from the phone rebooting moment to appearance of the language choice screen) is long. Be patient, please.
- Please, setup only that you really need during the first boot. Desire ROM is syncing and configuring a lot of stuff during first boot if you have entered your google account. I recommend to setup all needed accounts after initial setup. And, please, let system sync and configure all stuff, next reboot your phone. After this work will be completed the ROM will be fast. I recommend:
a) disable the sync of accounts which are no needed for you, or change "Update schedule" of these accounts.
b) disable the "Back up my setting" for google account if it is no needed for you.
c) disable Automatic brightness and set Brightness to min value.
- Note, please, you can use CifsManager to mount cifs(samba(ms windows))/nfs network resources to your phone. This tool is available in the Market. It allows you to play music or watch movies from any shared resources which are available in your local network without copying this content to your phone. To use it your phone should be connected to local network by WiFi.
Currently I have 2Gb ext4 second partition on my Transcend 6-class sdcard. I can tell the system works properly and fast:
{
"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"
}
Performance:
Please, look at my video if you would like to see the performance of this ROM.
Download:
EFP v.2 HD2 Desire HD stock (last Gauner's kernel)
Kernels: (only if you would like to replace a kernel of your already installed ROM to other kernel)
Gauner's kernel with ext4
MDJ's 10.3 kernel
MDJ's 10.4OC kernel
Updates:
Desire HD stock toolbar
Desire HD custom toolbar with percent battery
How to install kernels, updates or fixs:
1. You should have already ClockworkMod(zImage and initrd.gz) on sdcard. If you use ROM-ZIP builds I think you have it already.
2. Copy the update.zip file from an update or a fixs archive to sdcard root.
3. Reboot your phone, hold Power button to access the magldr menu.
4. Next select the "Boot AD SD" item. ClockworkMod will be loaded and you will see ClockworkMod Recovery menu.
5. Select the "apply update from sdcard" item.
6. Select "Yes".
7. After flashing will be done select the "reboot system now" item.

what working and not working ???

It would be nice to have the readme of each build at least posted in the first post, so we don't have to download everything to see if we need it
I am always looking for a PURE/Stock Desire HD build, with no frils and no EXTRA apps, for a TMOUS HD2. But with no readme , i'll wait for someone first.
Greetings Santroph

Did it Include CM Mod setting?

Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.

is this ext 2 ,ext 3 ,ext 4 same?

santroph said:
Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.
Click to expand...
Click to collapse
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.

sathara said:
is this ext 2 ,ext 3 ,ext 4 same?
Click to expand...
Click to collapse
check www.google.com

AngelDeath said:
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.
Click to expand...
Click to collapse
same here.. I also find CWM yest..

does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone

wtf? i can`t choose CWMREC directory...

i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm

hamdir said:
i dont get it its based on andrews work, so is it a2sd+ or data2sd?
Click to expand...
Click to collapse
a2sd+ as per the title

swordfish2009 said:
a2sd+ as per the title
Click to expand...
Click to collapse
the title says its based on andrews rom and the screen shots shows data2sd (768MB free)
so yea although i know the title says a2sd+ i need confirmation

What working?
What working and what not?
mms, volume, hd video???????

after i unlock phone its stuck at the htc logo
i have ext2 partition already
and i flashed the required partition size!

zheliapov said:
wtf? i can`t choose CWMREC directory...
Click to expand...
Click to collapse
From the "How to instal" in readme file:
...Copy the CwMRec directory from the 2_step directory to root of sdcard.
After copying will be finished disconnect USB cable.
Go to "Services->BootSettings->AD SD Dir" in the magldr menu and select the CWMREC directory....
1. Perhaps you forgot to disconnect a USB cable safely.
2. You copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory. In this case the CwMRec directory not exists on sdcard, the zImage and initrd.gz files are placed in root of sdcard. You should skip the step of selecting directory for boot from SD or select the <.> .
hamdir said:
i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm
Click to expand...
Click to collapse
This is a2sd+.
In case of A2SD the internal storage does not include external partition, you will see only size of free space in NAND. But in case A2SD+ you will see free space of the external partition as size of intrenal storage.

rejdzu said:
does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone
Click to expand...
Click to collapse
I am using Gauner's kernel build currently and I do not have any issues with root.

something is awfully wrong
the gauner version keeps giving me a bootloop

I think you forgot to disconnect a USB cable safely. Or you copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory.
Click to expand...
Click to collapse
Not working... Any ideas?

{
"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"
}
3.2.1
This build is the exact copy of my RAFDROID HD EXT
the difference is that some parts of the system are "squashed" to give you the possibility to NOT USE any Ext partition for data.
I dont like squashedfs, but someone requested an hd build with some free space on nand (about 50mb) because some one not install a lot of apps and prefer to not use sd ext partition.
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
FEATURES
All the main features of RAFDROID HD EXT plus:
- odexed back to save dalvik cache space
- free user space after first boot: 101mb
- App2SD enabled if you use and SD with an EXT partition
CHANGELOG
Code:
3.2.1 - 3 MAR 11
Fixed Market FC
3.2- 3 MAR11
Some improvements and fixes to radio/audio driver,
this "should" fix phone freeze in some setups, also if I was not able to replicate the issues
Tweaked for more battery life on some sd cards usage
Updated hosts file with last one
3.1 - Initial release
=== INSTALL INSTRUCTIONS (CWR) - NEW USERS WITHOUT CWR INSTALLED OR WITH CWR BUT USING ANOTHER ROM ===
This process will erase everything on your nand. So, if you are already using a previous rom, backup everything!
Download PANASONIC SD FORMATTER and use it to format your card with FULL ERASE
You need to flash MAGDLR 1.13
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Download the FULL RAFDROID PACKAGE and copy the entire zip (not extracted!) on the SD CARD root.
Put the SD CARD in your phone and power it on and go in the MAGDLR menu (hold the power key while powering up)
Select BOOT AD RECOVERY
Click on INSTALL ZIP FROM SD CARD and then CHOOSE ZIP FROM SD CARD
Select the FULL_RAFDROID_HD*******.zip that you downloaded before.
Select "Yes - Install........" and wait for installation then Go back with power button and select REBOOT SYSTEM NOW
First boot can take up to 20 minutes. If you are stuck on white screen with HTC logo just wait. If you hear boot sound more than one time, you had a bootlop and something has gone wrong. Delete everything, reformat your SD card, read again the instructions and try again.
When you see the lockscreen, give at least 5 minutes to settle. Then do all your settings and then reboot again
Enjoy.
Remember: if you want to avoid Data Corruption always choose SHUT OFF and not reboot!
=== INSTALL INSTRUCTIONS (CWR) - UPGRADING FROM A PREVIOUS RAFDROID VERSION (2.2 or greater) WITH ALREADY CWR INSTALLED===
Since the data storage method is different, you cannot upgrade from a different RAFDROID HD version. You have to install fresh. Anyway you will keep your data and apps installed.
============ CONFIG.TXT ============Used some ideas and code bits from Dandiest's init script.
You can create a config.txt file on the root of your sdcard to configure some things at boot.
Actually you can configure the following options
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
old_light_driver=0
auto_btn_backlight=1
The init script will also create an init.log file on your sd card at every boot. This will help you and me with debugging if something not works fine. If you have issues please always post your init.log file when reporting your problem.​
============ KERNEL ============
You can refer to my kernel thread for updates, changelog, and comments
http://forum.xda-developers.com/showthread.php?t=940823
​============ SQUASHED FILE SYSTEM ============
App, Framework and most of Lib folders, are squashed.
Anyway you can push or delete any file from those folder because any file is simlinked.
Example: if you want to use a different framework-res.apk, you can copy it in the /system/framework folder. At this point the simlink will be removed and your new file will be stored on nand, not in the squashed filesystem. This means that more "new files" you push in the squashed folders, less nand space you will have.
Anyway please note that I left only about 13mb free on "system". This means you will not able to push more then 13mb files. If you like to change a lot of things.. this build and squashfs is not for you.
============ DOWNLOADS ============
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Full Rafdroid HD 3.2 LIGHT SQ
http://hotfile.com/dl/108421743/5bfea5b/full_rafdroid_hd_3r2f1_light_sq.zip.html
MD5: 97018DD4D05FAAFBCC5F9329AEB03F28
SHA1: F6B6D67B90B96E02FCDA70D98836450B6FAE9917
CRC32: 150CCA2B
OLDER VERSIONS:
3.1 : http://www.multiupload.com/X8VBC6WKYV
============ DONATE ============
I made this version just for people that were asking, so if you think this helps you, a small donation for a coffe or a beer, is appreciated. Otherwise a click on the "thanks" button is appreciated too
============ CREDITS AND THANKS ============
Credit to all the people that made all this possible: Cotulla, DFT, darkstone, markinus, danijel, rajko and some one other I'm missing...
Big Thanks to Cass, ocm, darkstone, rajko, crawlingcity, atoore for their help in the last months and to be always available to help
Thanks to all the users who donated and helped me to keep going
Thanks to all the testers and users of my builds that with their reports helped me to solve bugs and issues.
Thanks also to Sergio76, imilka, cmylxgo for the nice talks and knowledge sharing​

FAQ
Q: I have low quadrant score
A: This is normal. Nand is slower. Anyway during day usage you shold not notice big difference
Q: I have small freeze when installing apps
A: This happens with all Desire HD builds. I can't do nothing to avoid this
Q: I'm using App2SD but my internal memory keep decreasing at any app installed
A: Go in the application management and move the installed abb back in the phone. Some apps anyway keep some datas in internal mem.
Q: My phone sometimes freeze and I have to reboot.
A: Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
Q: Can you provide a different link or a mirror different from hotfile?
A: I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
Q: During/after boot a window appears with "System process not respoding". What I have to do?
A: This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
Q: I have robo voice when I make a call
A: To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
Q: I have very low audio during calls
A: During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
Q: after boot I see only a white screen with a green htc logo
A: just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
Q: I'm having high battery drain
A: Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
Q: It's really laggy!!!!
A: as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
Q: I have no GPS or the fix is really slow
A: Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
Q: It not boots
A: partition again and format again your sd card. follow the guide linked in the first post. post your init.log. check that you flashed the custom recovery linked in the instructions.
Q: I have no data/3G/HSDPA
A: probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
Q: How do I remove BOOTSOUND / How do I change bootanim
A: bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
Q: I have wake up lag
A: It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem.
Q: My screen stays off after call
a) Maybe this can help: http://forum.xda-developers.com/showthread.php?t=946012 ATM very few people have this issue, so I wonder is related to sd card.
Q: My contacts pictures are low res after sync!
A: this is a google problem, read here http://code.google.com/p/android/issues/detail?id=4147
Q: I have random reboots
A: Seems to be related to your phone, read here http://forum.xda-developers.com/showthread.php?t=941845 and here http://forum.xda-developers.com/showthread.php?t=898804
​

UPDATES:
​
Instructions:
1. Download your update and copy it to your sd card folder. Dont use MAGDLR mass storage mode because will corrupt your files. Use an sd card reader on your pc or usb mass storage mode in recovery menu
2. Boot into MAGDLR and choose BOOT AD RECOVERY
3. Make a backup! It will save your life if something goes wrong and you want to roll back! You are aware now!
4. Click on INSTALL ZIP FROM SD CARD
5. Click on CHOOSE ZIP FROM SD CARD
6. Select the update zip that you downloaded before
7. Select "Yes - Install........" and wait for installation
8. Go back with power button and select REBOOT SYSTEM NOW
Removed Apps for version 3.X -> http://www.multiupload.com/H5IPNFYBG4
old acdb file (read the faq if you dont know what this is) -> http://www.multiupload.com/AHV0UIKHZF
Stock Framework, only for version 3.X -> http://www.multiupload.com/TVDWWVDNL1
RAFDROID Framework, only for version 3.X -> http://www.multiupload.com/ZC4P6KSKWL
Replacing fonts with standard Desire HD one http://www.multiupload.com/N4VR74W8PK
Replacing fonts with Rafdroid one http://www.multiupload.com/E9UKQBEE4P
If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/showpost.php?p=10584806&postcount=280

- maybe I need also this -

First! Nice!

waiting...

are there any advantages on HD2 TMOUS?

rafpigna said:
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
Click to expand...
Click to collapse
I gues not rizky_p
rizky_p said:
are there any advantages on HD2 TMOUS?
Click to expand...
Click to collapse

link is on-line

Thanks, will try

Going to try this tonight, looks good. Any one tried it yet?

Ston said:
Going to try this tonight, looks good. Any one tried it yet?
Click to expand...
Click to collapse
Yep, works a treat

Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts

I always had problem with data on ext partition due to easy file corruption, so I'm trying this...thanks!

thesniffer said:
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
Click to expand...
Click to collapse
You can use the update zips from my EXT build.

Very nice and smooth build
But one question: Has anyone tried to change the kernel to Rfp 1.6 or 1.5? I just tried and now the phone is stuck at "gogogo" ...

Intersting

rafpigna said:
You can use the update zips from my EXT build.
Click to expand...
Click to collapse
So via CWM Recovery as i supposed.
Thanks again for your kindness and keep up your valuable work

hi raf
i installed this one(only for proof of concept),works great and i think it is a little faster than the "normal" rafroid,i dont have any lag!!! but 101mb.....very poor...
back to rafroid HD "normal" with d2sd..... i love more space!!!

nice & good release
keep up the good work
cheers!

WARNING: THIS MOD IS INTENDED FOR ADVANCED USER
this mod is difficult to applied. for an easier method, you can use my guide here about increasing internal memory without dualboot kernel. if you want a NEW-BETTER-FASTER-BUGLESS method to save your internal memory, you can use my akuro mod in this thread
anyway, this is only one of dualboot implementation based on irfanbagus's work. I actually doing this for fun. this mod is actually intended for rom development for any rom dev who want to develop a custom rom without a risk got a bootloop in his device. please feel free to discuss all stuff about dualboot mod or how to enhance it but don't ask about how to install it on your device. if you don't know how to install it, it means this mod doesn't suitable for you. don't worry. there's a lot of alternative method to save your internal memory space as I've stated above.
let's get straight on how we do this. first of all, in this mod the second ROM will installed on sdcard with modified partition size. we'll make bigger partition on data and system partition. please look into the picture below.
{
"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"
}
requirement:
1. know how to customize a rom.
2. know how to install a custom kernel
3. know how to partition sdcard, and of course
3. a sdcard minimal 8gb class 6.
what you'll nedd:
1. a custom rom to be modified.
2. a dualboot custom kernel. you can get it here. http://www.mediafire.com/?6zrkh6a872036x7
3. a modified rom installer script. http://www.mediafire.com/download.php?nxgiz0993brp9re
4. a partition tools.
5. all things needed to modify a rom.
the steps:
1. >>>SDCARD PARTITION<<<
make 4 partition on your sdcard. all partition is primary. my recommended setting for all partition is. 6gb fat32 on first partition, 300mb ext3 on 2nd partition, 300mb ext3 for 3rd partition, and the rest ext3 for 4th partition. you can modify the the 1st and 4th size but don't change the 2nd and 3rd partition size.
2. >>>install irfan's dualboot kernel<<<
feel free to use any method to install the kernel. you can use mai77's, faqbly's method or odin to install the kernel.
3. >>>ROM preparation<<<
extract your custom rom. replace meta-inf folder with the one I've give to you. this script will install your rom to your sdcard partition. re-zip the rom, then copy it to your formatted sdcard (in the 1st partition of course). if these script didn't work check irfan's original post for detailed guide on modifying installer script here http://forum.xda-developers.com/showthread.php?t=1598803
4. >>>dual boot setting and ROM installation<<<
create a blank file in sdcard named 'bootsdcard' then go to recovery mode. install your custom rom. wait till it finished then reboot. the first installation will take a longer than the usual. be patient.
finish. enjoy your 2nd rom with larger /data and /system partition
========
there are several possibilities on installing the new rom. in most cases, it have succesfully installed the rom (I've got no report on installation failure till this moment). but if the rom doesn't work, you'll need to modify the rom and the installer script.
DISCLAIMER:
1. DO IT WITH YOUR OWN RISK.
2. the succession rate is depend on your custom rom and your sdcard quality. do your best to modify it.
3. don't use a2sd or link2sd
4. don't install the app on sdcard when you use the 2nd rom.
5. it will get laggy if your sdcard is not fast enough. you'll need a faster one.
6. this mood will make your battery drains faster. please be cautious.
credits:
1. myss ROM developer. my installation script is based on it.
2. irfanbagus, for the dualboot kernel and his helpfull guide.
3. all XDA member who have share their knowledge for us.
I'm a chemist student. another mid-user here. no need to give thanks. give them to the dev instead.
UPDATE:
http://www.mediafire.com/download.php?hw9jgrui1ga4akg
this is another updater script which automatically delete your sdcard's /data partition.
savie have made another kernel with dualboot support. if you feel this kernel doesn't fit with your necessity, you can use savie's one you can get his kernel in dev section [url="http://forum.xda-developers.com/showthread.php?t=1761166]here[/url]

reserved for modification

wow 750 internal mem?!!!!

seems like i need to buy a new sd card

what will happen
if my android in dualboot rom and active usb storage mode?

you can use usb storage mode just like as you use your first rom.

It is true. How make more free space?
Sent from my GT-S5360 using Tapatalk

1st partition, fat32, is used for regular use (store photos, music, etc)
2nd partition is system partition
3rd partition is cache partition
4th partition is data partition
you can increase the size of 4th partition to have larger size of data partition.

Plz give me repencics 3 modded meta-inf.zip file.
Sent from my GT-S5360 using Tapatalk

ive seen this same thing on the galaxy mini,,,but no need for a lot opf thing ,just flash a custom kernel i think,,
can you guys take a look at this
here is the source
http://androidadvices.com/increase-internal-memory-samsung-galaxy-mini-s5570-1gb/2/

tandob said:
Plz give me repencics 3 modded meta-inf.zip file.
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
is my script didn't work?
zeusseuz said:
ive seen this same thing on the galaxy mini,,,but no need for a lot opf thing ,just flash a custom kernel i think,,
Click to expand...
Click to collapse
I though that its totally different. this mod is based on dualboot implementation.

zeusseuz said:
ive seen this same thing on the galaxy mini,,,but no need for a lot opf thing ,just flash a custom kernel i think,,
Click to expand...
Click to collapse
this mod need more complex step because of dual boot. you not only get bigger (or smaller, it is resizeable) internal storage, but you also got 2 different rom in one phone that you can select which one is active with easy way (no need re-flashing) and both working independent (no share data, apps, account). it's mix of data2sd, system2sd, and cache2sd.
in this case, kurotsugi want to make use data2sd capabilities.

kurotsugi said:
is my script didn't work?
No no it is working. But plz give me a solution, when i want to flash another rom by your process then what to do? Before flashing i have to do again flash the kernel and then format ext partition? I am using ddla1 firmware. When i install the dual boot kernel by odin or cwm method it getting boot loops.
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse

I'm not sure, but I think the method which mentioned zeusseuz is called 'ungaze'.

tandob said:
No no it is working. But plz give me a solution, when i want to flash another rom by your process then what to do? Before flashing i have to do again flash the kernel and then format ext partition? I am using ddla1 firmware. When i install the dual boot kernel by odin or cwm method it getting boot loops.
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
before you install another 2nd rom you should reformat (or simply delete all files) in sdcard's data partition (the 4th partition). you don't need to install the kernel again.

kurotsugi said:
before you install another 2nd rom you should reformat (or simply delete all files) in sdcard's data partition (the 4th partition). you don't need to install the kernel again.
Click to expand...
Click to collapse
Where i FOUND the files? I have MODIFIED REPENCIS ROM AND FLASHED. IT DOES NOT BOOTED. ONLY THE SCREEN STAY "GALAXY Y YOUNG GT-S5360" PLZ GIVE ME THE META-INF. ZIP FOR REPENCICS
In this pic there have in meta-INF folder of REPENCICS have some files. Which files in have to replace?
Sent from my GT-S5360 using Tapatalk

You said that my script is working, so I assume that you have already installed a 2nd rom (I think its repencis v3) and its working. now, you want to install another 2nd rom (a modified repencis v3) in your sdcard. am I right?
if you want to install another 2nd rom, please follow this guide:
1. reformat your 4th partition.
2. extract your rom.
3. replace folder meta-inf with the one from me.
4. rezip your file, put in your sdcard.
5. make bootsdcard file in your sdcard's root.
6. enter recovery mode.
7. install your rom, reboot
in any case if this guide didn't work, the probem may comes from your modification. I don't know what you've done to modify it but I think your modification makes the rom didn't work.

kurotsugi said:
You said that my script is working, so I assume that you have already installed a 2nd rom (I think its repencis v3) and its working. now, you want to install another 2nd rom (a modified repencis v3) in your sdcard. am I right?
if you want to install another 2nd rom, please follow this guide:
1. reformat your 4th partition.
2. extract your rom.
3. replace folder meta-inf with the one from me.
4. rezip your file, put in your sdcard.
5. make bootsdcard file in your sdcard's root.
6. enter recovery mode.
7. install your rom, reboot
in any case if this guide didn't work, the probem may comes from your modification. I don't know what you've done to modify it but I think your modification makes the rom didn't work.
Click to expand...
Click to collapse
I have done with hybrid v2.1 it is not working with REPENCICS, cognitive digital rom etc.
Sent from my GT-S5360 using Tapatalk

this is the original meta-inf of repencics
http://db.tt/gxt31q56
Sent from my GT-S5360 using Tapatalk

i'm so sorry, i can't acces my computer at this moment till friday. you may ask irfanbagus if you can't wait.

{
"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 CandySiX. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @Cuzz1369 @rc420head @Flashalot @Venomtester @Darknites @javelinanddart @calebcabob @NoSpamDan
ROM
DEVICES/KERNELS
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
FEATURES
Choose from CMTE or OMS (RRO Layers is DEPRECATED)
Battery bar
LCD density options
Multi-window
Status bar customization
Quick setting customization
Quick setting pull down options
Force expand notifications
Time contextual headers in panel
Dark UI switch
Advanced power menu
Extra IME options
In-Call vibration options
Lockscreen customizations:
-Shortcuts
-Music visualizer
-Weather​Animations:
-Power menu
-List view
-System
-Toast​Navbar customization (CMTE only):
-SmartBar
-Fling
-Pulse​ Hardware Buttons settings:
-Slim Hardware key rebinding
-Long-press/double-tap actions
-Volume rocker​On the Go mode
Screenshot Crop & Share
Fully charged notification and toggle
CPU info overlay (Developer options)
Snap camera (Sultan's)
More to come, we are never done...
CHANGELOG
WARNING!
This is a Virtually Repartitioned ROM!
What this means is that you will need to take some special steps to flash this ROM. Don't worry, it's not that hard, and you will be able to return to stock with Odin at any time. The cool thing is that it will support a ton of app and app data storage and will behave like a more modern device.
The basic idea with virtual repartitioning is that the partitions are renumbered from the stock numbering, but not resized. So the most important parts of this are (as an FYI, you don't need to know this ):
-The 2GB /data partition becomes a most adequate 2GB /system partition for the ROM and GApps.
-The 12GB Internal SD partition becomes /data, so you have that space to install apps.
It is strongly recommended to use an External SD card to store the ROM/flashing files and for backups, etc., however it is not mandatory. If you do not have an External SD and you need to format the /data and /Internal storage partitions, you will have to copy the files you need from your PC again. Easy peasy, right?
FAQ/NOTES:
When formatting the device, first go to the Mount menu and make sure none of the partitions you want to format are mounted. If they are, formatting will fail.
Make sure you have NOT selected Mount USB Storage, and that the MTP button says "Enable MTP", which means it is DISABLED. If either of these are enabled, then formatting may fail.
The /system partition is formatted as EXT4.
The /data and /cache partitions can be formatted as either EXT4 or F2FS.
The Internal Storage should be formatted as EXT4 or F2FS.
The External SD card (if you have one) would be best formatted as FAT, which you can do in your computer. When the ROM boots, it will detect the card and offer you one of two different ways to use it, as "Internal storage" that will only work with your device for security (requires formatting and encryption by Android), or as "Portable storage" that will work in other devices.
CAUTION: With Internal, you will have to entirely format your card if you have issues and it can not be used in ANY other device. In fact, it will become invisible in file managers because it becomes an extension to the Internal SD card storage. Format the ExternalSD card to Internal Format at your own risk.
When formatting /data, the default behavior is that /data/media is not deleted. In order to wipe /data/media, you need to either go to TWRP > Wipe > Advanced wipe > Format data, or delete the folder manually through the file manager in TWRP.
TWRP > Wipe > Advanced wipe > Format data is also needed if you plan to use device encryption, because this step allows for a space at the end of /data to contain the encryption information. Without this, encryption will fail!
IMPORTANT: If you have flashed a modified PIT file, flash back the STOCK PIT. You can also return to stock by using Odin and a Factory Image.
If you are trying to get back to the stock partitioning:
Flash a stock TWRP recovery ZIP or IMG file, or use Odin to push a TAR recovery over. After doing this you need to reboot your device into Recovery to load up the newly flashed version, and format each of the partitions to their defaults (ext4, for the most part). If you encounter errors formatting, reboot back into Recovery and try again.
Check SamMobile.com for stock ROM packages. (There is a Stock ROM version in my AFH account which should be used for recovery purposes only.) Odin should also find the device if it's in download mode and you can flash a stock ROM back on it if you want.
If you are not sure you used the correct recovery or you just want to check the partition structure (I may ask for this), you can run each of these commands from an adb prompt, and save the output to a file for linking in the thread for help/analysis:
blkid
cat /proc/mounts
df
INSTALLATION STEPS:
Here is what you need to do; please follow the below steps carefully!
Connect your device to your computer and FULLY BACK UP YOUR FILES from both your Internal and External Storage!
While you are backing up your files, download the following files to your computer:
A custom TWRP recovery for virtually partitioned ROMs (see Post 2).
The ROM zip file (see Post 2).
A 6.0 Gapps package, pico recommended for now. (optional - see Post 2).
Copy all of these files to your device's External SD card. If you don't have an External SD card, then you will need to copy them over from your computer after formatting your internal storage.
MAKE A NANDROID BACKUP!
Using your EXISTING RECOVERY, format /system, /data, /cache and /Internal Storage.
Flash a VIRTUAL REPARTITIONED RECOVERY.
REBOOT to Recovery to use the new one.
Select Wipe > Advanced Wipe > System, then press the "Repair or change file system" button. Choose "Change File System" and select EXT4. Swipe to apply.
Press the back button and verify the Size: and Free: values at the top. The System partition should be 2GB. Press the Repair button and swipe to apply.
For good measure, now press the Resize button and swipe to apply.
Repeat steps 1-3 for the Data partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Repeat steps 1-3 for the Cache partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Reboot to Recovery and wipe /system again.
Flash the CandySiX zip
Flash Gapps (nano or pico Open GApps or BaNks ones, etc.). You may have to experiment a little.
Reboot and Enjoy
Please give first boot a good several minutes. If you get stuck at the boot animation for a long time, try removing your ExternalSD card and reboot without it.
IMPORTANT - PROBLEMS/ISSUES:
If you have issues, I need the following:
Logs from you (logcat, last_kmsg, dmesg) linked to on pastebin.com or hasteb.in, showing the failure.
A clear description of the steps that I need to take to exactly reproduce the problem.
State what flavor build you are on: CMTE, Layers, OMS, etc...
Please DO NOT complain about problems and offer nothing to help fix it. I reserve the right to ignore you for not following insructions...
NO ETA REQUESTS!
Special thanks to @gimmeitorilltell, @bryan2894, CyanogenMod, SlimRoms, Omni and all the rest who make their source open, we can't do this on our own.
XDA:DevDB Information
[ROM-DISCONTINUED][SGH-T989][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Hercules, ROM for the T-Mobile Samsung Galaxy S II
Contributors
NoSpamDan, gimmeitorilltell
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.2
Stable Release Date: 2016-02-11
Created 2016-01-01
Last Updated 2017-01-05

Downloads
Make sure you have FULLY READ and FULLY UNDERSTAND the OP (Post 1) above before following any steps!
RECOVERY
BaNks just announced they aren't supporting TWRP versions below 3.0.
@bryan2894 has a Flashable 3.X version you can flash here:
https://androidfilehost.com/?fid=24545065934258236
(My previous TWRP 2.8.7.0 for Virtual Partitioned ROMs: TWRP_2.8.7.0.VP_hercules_NSD.zip)
TWO ROM VERSIONS: Effective 26July2016, choose from CMTE or OMS/Substratum!
(You can NOT flash one on top of the other... If you decide to switch and try the other one, you MUST Clean Flash!)
DOWNLOAD CMTE (CM Theme Engine based) ROM:
CandySiX-celox-3.2-OFFICIAL-0903.zip
DOWNLOAD OMS/Substratum themed ROM (Substratum app required - Guide to using Substratum):
CandySiX-celox-3.2.S-OFFICIAL-0910.zip
GAPPS
"Normal" BaNks Dynamic GApps
Open GApps
Your best bet is to flash a Pico GApps package made for Android Marshmallow which doesn't have an included keyboard or any keyboard modifications. Watch out for GApps that replace Gallery too!
EXTRAS
- If you want to remove the built-in SuperSU, flash this in recovery after the ROM: SuperSU_Root_Remover.zip
Previous ROM versions for convenience (can be found on my AFH account unless they are OTAs).
DO NOT FLASH a CMTE ROM on top of an OMS or LAYERS version. You must CLEAN FLASH if switching theme engines!
OMS/Substratum-based:
CandySiX-celox-3.2.S-OFFICIAL-0902.zip
CandySiX-celox-3.2.S-OFFICIAL-0817.zip
CandySiX-celox-3.2.S-OFFICIAL-0808.zip
CandySiX-celox-3.2.S-OFFICIAL-0807.zip
CMTE-based:
CandySiX-celox-3.2-OFFICIAL-0817.zip
CandySiX-celox-3.2-OFFICIAL-0809.zip
CandySiX-celox-3.2-OFFICIAL-0807.zip
CandySiX-celox-3.1-OFFICIAL-0728.zip
Layers-based (deprecated):
CandySiX-celox-2.3-OFFICIAL-0514.zip
Previous GApps versions can be found on my AFH account here.

FAQ/Info
Due to several requests, here is some further information...
DISABLE HARDWARE CAPACITIVE KEYS AND LIGHTS
NOTE: This information is now outdated, as I've added ROM features for it. I'll leave it here, but hidden for now...
Several have asked about this. I am working on an in-ROM setting for each, but I simply haven't had the time. For now you can do it manually if you like.
If you decide to try/use the following instructions, please understand that you do this entirely at your own risk
Some people like to use the NavBar soft keys (on-screen). If this is you, below you will find some commands you can use to disable the built-in Hardware Keys and Hardware Key Lights.
***NOTE: Both the HW Keys switch and the HW Key Lights switch are a WIP and do not currently work properly!
Using adb or a terminal emulator app (or the built-in one that you can install in your app drawer by enabling Settings > Developer Options > Local terminal), issue the commands under the HW Keys option you want to apply.
For each item listed, copy/paste or type the commands, one line at a time, and EXACTLY as they are shown. Press ENTER after each command.
Open adb or the terminal emulator app and issue the following commands to start a shell with root access. Press ENTER after each command.
(Be sure to accept any Superuser root access propmpts you receive while doing this.)
Code:
adb shell
su root
Now issue one or a combination of the following:
To DISABLE Hardware Touch KEYS:
Code:
echo 0 > /sys/class/sec/sec_touchkey/keypad_enable
To ENABLE Hardware Touch KEYS:
Code:
echo 1 > /sys/class/sec/sec_touchkey/keypad_enable
You should be able to use the ScreenFilter app from the Play Store to disable the HW Key lights. You can even disable the Screen Filter notifications if you like (long-press on the notification, then select the "i" button), but beware this could trick you later.
Enjoy!

Let me know how this works out for you folks. I still need Mobile Data tested and please remember it's Alpha right now, so I need logs when things aren't working.

Thanks for your work. I'm excited for testing this rom.

juni12 said:
Thanks for your work. I'm excited for testing this rom.
Click to expand...
Click to collapse
It is a WIP right now, and there will be more Candy goodness added soon... Hopefully everything works for the Herc since I don't own one (but I have a Skyrocket and have actually flashed Herc ROMs on it )

Stand by... new build compiling now... seems something was missing for Mobile Data to work. I'll update the d/l link when ready.
EDIT: New build is up, and Mobile Data works. Happy New Year!

@NoSpamDan
candy6, thanks for the great work , u really rock man

Just a heads-up, make sure you grab this build or newer for now: CandySiX-alpha-hercules-OFFICIAL-0101-06.zip
(The previous "UNOFFICIAL" builds had broken vendor blobs and no mobile data.)
EDIT: I have updated Post 2 with a modified BanKs Dynamic GApps version that has the keyboard libraries removed. Temporarily fixes the AOSP keyboard FC. You can get Google Keyboard after setting up your account on the Play Store...

Gonna try this soon.

My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.

edwin270 said:
My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.
Click to expand...
Click to collapse
I would call those preferences, not issues...
1. Swipe away the notification unless you have not initially set up the card (you didn't quote the notification message you are getting).
2. Nav bar is in the next build... are your touch light buttons broken?
3. DPI may be forthcoming, not sure.
EDIT: Navbar does not appear to be present in the new build. Looking into it.

New build is up in Post 2: CandySiX-alpha-hercules-OFFICIAL-0102-16.zip
This one has Quick Settings Tile Customization, Status Bar mods, Battery mods... more features to come in the near future!

...

juni12 said:
About the first build if we talk about performance, you can put beta because the rom works super fast. For a fledgling rom it is excellent. It would alfa because it lacks certain configurations and features (such as screen capture, buttons Turn off lights ...) but it is significant that installs Facebook, which in other roms including lollipop did not occur. Thanks!
Click to expand...
Click to collapse
Depends what version you are runnig because Vol Dn. + Power has always been for screenshot, plus in my last build, there were Power menu customizations like Screen Shot for those who prefer that method. Look in Settings > Candy Interface.
CandySiX was maturing on the previous CyanogenMod base but the decision was made to switch to an AOSP base. Come CAF repos are needed and still some CM too, but things are speeding back into shape! Next build should have NavBar (I hope). Will be testing soon.

New build up in Post 2 with working Navigation Bar and some other things - CandySiX-alpha-hercules-OFFICIAL-0103-04.zip. Things will be slowing down here shortly once I return to work...

New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
Sorry, no time to outline the changes but should have Quick Unlock, new boot animation and several other updates...
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024

Bootloop
NoSpamDan said:
New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024
Click to expand...
Click to collapse
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.

Lucky2say said:
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.
Click to expand...
Click to collapse
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
If you get in bootloop or have a camera flash issue (if it wasn't because of low battery), plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Cheers!

Cheers![/QUOTE]
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
Click to expand...
Click to collapse
My bad.. I may have done something wrong tweaking settings and stuff. I changed DPI, it got bootloop, I formatted external card using TWRP VP, it got bootloop, etc. I reflashed ROM, Gapps and bootanimation. Now it's working fine.
have a camera flash issue (if it wasn't because of low battery)
Click to expand...
Click to collapse
I've switched to google camera app and the problem is gone. (Even with low battery)
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Click to expand...
Click to collapse
Honestly, I didn't know that marshmallow has introduced the new portable function for External SD. I was looking for the old way of External SD mount (I don't know what to call it.) again it was my fault.
plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
Click to expand...
Click to collapse
I didn't post the logs because the problems were caused by my side. I shouldn't have disabled some apps and flashed boot animation after using the rom.
As you might have figured out i'm a noob (guilty! I know I deserve to die! =P ), one more thing, there's no youtube, calender, calculator and browser apps included in the package/rom. Or is it just me?
This is a perfect rom.
Many Thanks!

{
"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"
}
I am proud to present the first dual boot project for the Nokia X/XL/X+ (normandy) .This 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
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 198 supported devices and their variations.
Information:
I have managed to support for Nokia X/XL/X+ to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM 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. Hard. A lot.
Requirements:
1. A Custom Recovery (Tested using TWRP 3.1)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
It 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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
Before you start using the app, take note of these:
1- You must have re-partitioned storage (1gb system + 2gb data), we are taking about Dualboot on 4gb emmc
2- Before you start, it's important to change ro.product.device value to "normandy" without quotes in your build.prop, if you don't do this, you can't use the app.
3- You must be on KK ROM or higher to use this app (primary ROM), but you can use any ROM (JB/KK/LP/MM) as secondary ROM.
Now, you can use the app:
1- Download, install and open the app.
2- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
3- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now.
4- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to "normandy" and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- I did't test booting from ext-sd card, so if you will do it I'M NOT RESPONSIBLE of any possible BRICKS!
5- Click continue and select where to save the patched file.
6- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
7- The app will patch the zip. When done, go back to "ROMs".
8- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
9- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like AOSPA_4.4.4_NOKIA_XL_UNOFFICIAL_BY_YSH_dual).
10-Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
11- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
11- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
12- Now reboot and wait till finishing 2nd ROM first boot. if ROM was 4.4+ install DualBootPatcher apk so you can easily switch ROMs, if not there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
13- return back to your primary ROM, open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk.
14- Now you can change ROMs simply using boot ui (some thing like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs -but i recommend only /system and /data-:
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. (The best choice for normandy)
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. Our normandy's cache partition is about 100MB which is not enough to install a ROM on.
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r86.gfc253e2"
Screenshots:
In screenshots tab
Click to expand...
Click to collapse
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Known issues:
- Can't use any LP ROM as primary on XL.
- Data sharing won't work if you are using JB ROM.
Credits:
 @chenxiaolong for the awesome DualBootPatcher.
 @androidlover5842 for helping me always
 @veez21 for testing on Nokia X and Bootui screens
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Nokia X/XL, Tool/Utility for the Nokia X
Contributors
yshalsager, androidlover5842, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Current Beta Version: 9.2.0.r86.gfc253e2
Beta Release Date: 2017-04-30
Created 2017-05-02
Last Updated 2017-05-02

Reserved

Created 2017-05-02
Last Updated 2017-05-02[/QUOTE]
hello dualboot?
hey, i literally have no space in data and system partitions...so if i install rom on ext sd and do app sharing on data
does that mean i will have a secondary rom with the same data?

If i want to use JB ROM as secondery rom, I needed a zip file. Right?
---------- Post added at 04:23 AM ---------- Previous post was at 04:21 AM ----------
ani00 said:
Created 2017-05-02
Last Updated 2017-05-02
hello dualboot?
hey, i literally have no space in data and system partitions...so if i install rom on ext sd and do app sharing on data
does that mean i will have a secondary rom with the same data?
Click to expand...
Click to collapse
I have nearly same question. I want to know if I install a app in primery one and data sharing on and does the app will show on secondery one or just data of it will be share between roms? If we have to install same app in both of roms then we will have very limited space for installing.

ani00 said:
hello dualboot
hey, i literally have no space in data and system partitions...so if i install rom on ext sd and do app sharing on data
does that mean i will have a secondary rom with the same data?
Click to expand...
Click to collapse
I think you didn't read this :
The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location
Click to expand...
Click to collapse
abhijit1998 said:
If i want to use JB ROM as secondery rom, I needed a zip file. Right?
Yes, or you can simply switch using boot ui like screenshots
---------- Post added at 04:23 AM ---------- Previous post was at 04:21 AM ----------
I have nearly same question. I want to know if I install a app in primery one and data sharing on and does the app will show on secondery one or just data of it will be share between roms? If we have to install same app in both of roms then we will have very limited space for installing.
Click to expand...
Click to collapse
Just data sharing - storing in same location -

how can i flash rom patch zip in secondary or primary rom?

ani00 said:
how can i flash rom patch zip in secondary or primary rom?
Click to expand...
Click to collapse
Please read the guide carefully. I've answered all possible questions
To install zip to primary
Patch zip file to primary. Flash it using recovery or inapp flasher through second rom.
To install zip to secondary
Patch zip file and flash using app

Awesome!!

We are on XDA news!
I was checking xda as I always do and I surprised for seeing our project on homepage. Thanks XDA ?

Awesome. Just awesome. I dont own this device now. But i remember. I flashed this device twice. CM and stock Nokia OS. Nice phone but lack of ram.

I tried to use as you told in description. First I was using Nexus X ROM as primary. When I update ram disk and pressed reboot. But while starting phone vibrates five time in a raw. Then stuck at Nokia logo. Did not started. Later I tried one more without updating ram disk and installed stock Nokia ROM. I booted to stock ROM. Later I tried to go back to primary one by the zip file. but when trying it shows some error like. But I rebooted and it booted to stock JB ROM. Don't know why this happened.
Secondly I installed nameless ROM. I tried all procedure and updated ram disk too. For this ROM my phone booted. But I saw some thing which I did not expected. The ROM is not showing SD card. No storage details in settings menu. I rebooted and saw same thing. Tried to unmount but nothing happens. But SD card is working fine.
I go back to Nexus X ROM by flashing it by TWRP recovery. I used TWRP 3.0.0-0.
I tried all Installation of ROM by the app in build flasher.
Anyway, Good thing that it is not hard. I will try another ROM for my device. Don't know what ROM veez21 used. But thanks. Tell me if you fount anything about this.

abhijit1998 said:
I tried to use as you told in description. First I was using Nexus X ROM as primary. When I update ram disk and pressed reboot. But while starting phone vibrates five time in a raw. Then stuck at Nokia logo. Did not started. Later I tried one more without updating ram disk and installed stock Nokia ROM. I booted to stock ROM. Later I tried to go back to primary one by the zip file. but when trying it shows some error like. But I rebooted and it booted to stock JB ROM. Don't know why this happened.
Secondly I installed nameless ROM. I tried all procedure and updated ram disk too. For this ROM my phone booted. But I saw some thing which I did not expected. The ROM is not showing SD card. No storage details in settings menu. I rebooted and saw same thing. Tried to unmount but nothing happens. But SD card is working fine.
I go back to Nexus X ROM by flashing it by TWRP recovery. I used TWRP 3.0.0-0.
I tried all Installation of ROM by the app in build flasher.
Anyway, Good thing that it is not hard. I will try another ROM for my device. Don't know what ROM veez21 used. But thanks. Tell me if you fount anything about this.
Click to expand...
Click to collapse
I don't know what kernel Nexus ROM is using. Try changing it.
Without updating ramdisk you won't be able to change roms.
In KK ROMS after updating ramdisk internal storage is disabled not sdcard.
Veez21 tested it using Cm13

yshalsager said:
I don't know what kernel Nexus ROM is using. Try changing it.
Without updating ramdisk you won't be able to change roms.
In KK ROMS after updating ramdisk internal storage is disabled not sdcard.
Veez21 tested it using Cm13
Click to expand...
Click to collapse
Null kernel is used in Nexus X rom.
Do you know how to make a flashable rom which is installed in our device? I want to make stock rom zip file which is latest. Then I will use duallboot. I wanna keep stock rom as secondery as I play some games. Stock rom's flashable zip file is availabe but they are older versions.
---------- Post added at 03:54 AM ---------- Previous post was at 03:51 AM ----------
yshalsager said:
I don't know what kernel Nexus ROM is using. Try changing it.
Without updating ramdisk you won't be able to change roms.
In KK ROMS after updating ramdisk internal storage is disabled not sdcard.
Veez21 tested it using Cm13
Click to expand...
Click to collapse
you told internal storage is disabled after ram disk update.?? Before starting any dualboot thing I used the swap sd card option in setting which made ext sd card as internal. So that why I was not able to see sd card in my device.??

abhijit1998 said:
Null kernel is used in Nexus X rom.
Do you know how to make a flashable rom which is installed in our device? I want to make stock rom zip file which is latest. Then I will use duallboot. I wanna keep stock rom as secondery as I play some games. Stock rom's flashable zip file is availabe but they are older versions.
---------- Post added at 03:54 AM ---------- Previous post was at 03:51 AM ----------
you told internal storage is disabled after ram disk update. Before starting any dualboot thing I used the swap sd card option in setting which made ext sd card as internal. So that why I was not able to see sd card in my device.
Click to expand...
Click to collapse
Latest stock rom 1.2.4.2 flashable zip https://forum.xda-developers.com/showthread.php?t=2745614

yshalsager said:
Latest stock rom 1.2.4.2 flashable zip https://forum.xda-developers.com/showthread.php?t=2745614
Click to expand...
Click to collapse
I think 1.2.4.2 is not latest. Latest is 1.2.4.3.... and mine is 1.2.4.3.... I can not remember is there a way to flash img file with pached? I have stock image file...

Found
well found a new trick to make zip file of the stock ROM which is installed into our device.
link- https://forum.xda-developers.com/showthread.php?t=2746044
Now have to make zip file with the ROM. It will be not that hard for me.

abhijit1998 said:
well found a new trick to make zip file of the stock ROM which is installed into our device.
link- https://forum.xda-developers.com/showthread.php?t=2746044
Now have to make zip file with the ROM. It will be not that hard for me.
Click to expand...
Click to collapse
Well, you can also use the META-INF from stock deodexed rom to avoid errors with symlinking

yshalsager said:
Well, you can also use the META-INF from stock deodexed rom to avoid errors with symlinking
Click to expand...
Click to collapse
Well I already thought that. I already made one with the help of a old stock ROM and replaced stock kernel with null kernel. Just have to transfer the rom into my phone from pc.

Successfully done. AOSPA ROM as primary and B-ROM as secondary. Both installed in system partition. One problem found. WiFi hotspot is not working in secondary ROM. When no dual boot used, everything works perfectly. But after dual boot, WiFi hotspot is not working in B-ROM. Tried to restore partitions, but no success. WiFi hotspot is Woking perfectly in AOSPA ROM, not in B-ROM.
One more thing. Some time after using boot ui no boot animation of ROMs came up, but ROM still starting. Don't know why.

abhijit1998 said:
Successfully done. AOSPA ROM as primary and B-ROM as secondary. Both installed in system partition. One problem found. WiFi hotspot is not working in secondary ROM. When no dual boot used, everything works perfectly. But after dual boot, WiFi hotspot is not working in B-ROM. Tried to restore partitions, but no success. WiFi hotspot is Woking perfectly in AOSPA ROM, not in B-ROM.
One more thing. Some time after using boot ui no boot animation of ROMs came up, but ROM still starting. Don't know why.
Click to expand...
Click to collapse
Any fix?