[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Nokia X/XL - Nokia X

{
"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?

Related

[GUIDE] How to Have 750 MB Internal Menory in SGY (dualboot mod)

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.

[ROM][STOCK][Lolipop][deodexed,resigned,zipaligned] D5503 14.5.A.0.270 Enhanced LP

Hi, just to share with you!
Whats this? In short, it is deodexed -> resigned -> zipaligned, installed busybox, supersu, dual recovery (vol up for twrp, vol down for cwm), 5way reboot menu ...and some other changes which you can read about it here -> https://github.com/munjeni/D5503_14.5.A.0.242/commits/master .
How to download rom:
- go to here -> https://github.com/munjeni/D5503_14.5.A.0.242/tree/ae7b18de7faa97eaf01eff1c2b6abeb540feaf6f and on the right side you have "Download zip"
- after downloading rom is not ready, do not flash!!!
How to install:
- after you download rom you must repack zip since git always add things into new folder inside zip so you will need repack it first before installing!
- simple open main zip and go to folder "14.5.A.0.242.master", select all files from these folder, drag and drop it to a new empty zip, you are done. Before you flash rom please read "iportant" section! Flash these new zip with any recovery. Done.
Mirrored download link (using this you no need to repack anything, just download and install!):
- https://mega.co.nz/#!Co1yERia!eJVCBjTZrjXok3KXZxM9xp_28I9Pos-LPYKjigJ6Bok
Important:
- you must fully wipe /data partition (mean delete everything from /data folder)! Or another solution, flash only userdata from any LolyPop ftf! Why? Because all old files from internal storage is not relabeled and you will encounter a lot of problems and all these files can not be accessed from android, pictures, private files... etc is not accessible than! Don't think it will work without wipe, it will not! Wioe data factory reset have no sense, I recomend installing userdata from ftf since its more a safe way!
Changelog:
- https://github.com/munjeni/D5503_14.5.A.0.242/commits/master
Enjoy!
munjeni said:
Hi, just to share with you!
Whats this? In short, it is deodexed -> resigned -> zipaligned, installed busybox, supersu, dual recovery (vol up for twrp, vol down for cwm), ...and some other changes which you can read about it here -> https://github.com/munjeni/D5503_14.5.A.0.242/commits/master . Curently I am stoped development on this rom since I am unable to solve thing like this -> lolipop have two classpaths (BOOTCKLASSPATH and SYSTEMSERVERCLASSPATH) and I not understand how to access classes from one classpath to another classpath, if you have idea how I can get this than I will probably continue development. My plan was implementing privacy guard rom cm12 but since I have problem accessing classes I am temporary stoped
How to download rom:
- go to here -> https://github.com/munjeni/D5503_14.5.A.0.242 and on the right side you have "Download zip"
- after downloading rom is not ready, do not flash!!!
How to install:
- after you download rom you must repack zip since git always add things into new folder inside zip so you will need repack it first before installing!
- simple open main zip and go to folder "14.5.A.0.242.master", select all files from these folder, drag and drop it to a new empty zip, you are done. Flash these new zip with any recovery. I have made some automated scripts so you no need to wipe anything since everything needed will be done auto so just click "install" and wait until rom get installed.
Enjoy!
Click to expand...
Click to collapse
Flashed this ROM and it is amazing.
Debloated it, installed some mods like xposed, xposed fix, modded services.jar for superuser mode, modified mixer_paths.xml for more loudness and some apps like MyAndroidTools, TitaniumBackup, Greenify.
Works like a charm and good battery life.
Only thing is the aweful toogle change by Google (no silent, vibrate toggle on quick settings) - but this depends NOT on your ROM.
Thx munjeni (one more time) for your time, work and effort.
m.
Investigated and got solution for 5 way reboot menu
Where you got moded services with superuser mod? I wanted to start porting it from cm12 but if it is allready exist I will be glad to look into it
munjeni said:
Investigated and got solution for 5 way reboot menu, you can download from here (just download android.policy.jar and replace) -> https://github.com/munjeni/D5503_14.../system/framework/android.policy.jar?raw=true enjoy
Where you got moded services with superuser mod? I wanted to start porting it from cm12 but if it is allready exist I will be glad to look into it
Click to expand...
Click to collapse
http://forum.xda-developers.com/sony-xperia-z1-compact/themes-apps/mod-accent-systemui-t3088719
moonryder said:
http://forum.xda-developers.com/sony-xperia-z1-compact/themes-apps/mod-accent-systemui-t3088719
Click to expand...
Click to collapse
I have no idea why it is caled SuperUser Mod since it have nothing related to SuperUser. It is just SignatureDisable mod, author stupidly gave these name to these mod which apsolutly have nothing related to superuser If you look into commits on my git you will notice that you no need his services.jar since my rom allready have disabled signature verification, I not guarant you how his services is patched, but I can sugest you to replace services.jar whith one from my rom since compatibility is guaranted
This http://www.androidauthority.com/cyanogenmod-12-superuser-577985/ is what I call superuser mod (I have plan to port it here), and diferencie between "wrongly named" superusermod and real superusermod like one from cm12 is like this and this
munjeni said:
...and diferencie between "wrongly named" superusermod and real superusermod like one from cm12 is like this and this
Click to expand...
Click to collapse
LOL
Ok bro will wait for a "real" PrivacyGuard for LP 5.0.2, modded by the master munjeni itself
When trying to install an app from sd card, I am getting out of space message, can't install apps from sd card
btw.. already wiped everything, and system storage shows correct info
nemphis said:
When trying to install an app from sd card, I am getting out of space message, can't install apps from sd card
btw.. already wiped everything, and system storage shows correct info
Click to expand...
Click to collapse
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
I can install apps from sdcard [emoji18]
But I am unable to download some apps from playstore
munjeni said:
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
Click to expand...
Click to collapse
NO problems here, i can install apps from sd card am on stock rooted lollipop with unlocked boot-loader.
I'll wait for another simplified flashable version of your rom.
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Freshly installed and everything is perfect ! Thank you very much brah !!
D5503 UB Dstriker ROM KK.157
Winb33 said:
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Click to expand...
Click to collapse
i tried that and / or replaced some things like bootanimation, fonts etc.
Flashing failed, so flash it untouched and remove / add things then.
pathaniya said:
NO problems here, i can install apps from sd card am on stock rooted lollipop with unlocked boot-loader.
I'll wait for another simplified flashable version of your rom.
Click to expand...
Click to collapse
I'm trying to solve this but have no idea how to do it, it is selinux restriction (if somebody have idea how it can be solved let me know please), but temporary solution is: via terminal emulator disable selinux, than install app, than enable selinux. To disable selinux write "setenforce 0", than install app, than enable selinux "setenforce 1"
Winb33 said:
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Click to expand...
Click to collapse
You can but only if you propertly remove lines from updater-script since it is hardcoded with our rom, instead recovery will abort installation if you missed something in updater-script ! My sugestion is, remove things manualy using an root file explorer, or at least add some lines in updater script which will remove things that you want
munjeni said:
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
Click to expand...
Click to collapse
First when installed FR version same problems with SD card. Also ESexplorer had problems accessing SD card
Now on stock rooted works everything fine related to SD card.
Run also SDfix app becouse Titanium problem
Sent from my D5503 using XDA Free mobile app
EasySR said:
First when installed FR version same problems with SD card. Also ESexplorer had problems accessing SD card
Now on stock rooted works everything fine related to SD card.
Run also SDfix app becouse Titanium problem
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
No man, you no need sdcard fix. I allready included sdcard fix https://github.com/munjeni/D5503_14.5.A.0.242/commit/21b396daf721791c3675de417c543ba6184e21d1 and you can read / write any storage without problems, but we speak about problem related to the "installing apps from sdcard"! For example, if you try to install blablabla.apk which is on any storage you will get "no free space" error since selinux DENIED installing it, I don't have idea why it happen since I am not familiar with selinux, only very basic things by now. I will try to solve this problem!
munjeni said:
No man, you no need sdcard fix. I allready included sdcard fix https://github.com/munjeni/D5503_14.5.A.0.242/commit/21b396daf721791c3675de417c543ba6184e21d1 and you can read / write any storage without problems, but we speak about problem related to the "installing apps from sdcard"! For example, if you try to install blablabla.apk which is on any storage you will get "no free space" error since selinux DENIED installing it, I don't have idea why it happen since I am not familiar with selinux, only very basic things by now. I will try to solve this problem!
Click to expand...
Click to collapse
Just installed app on stock rooted lolipop (3G Watchdog) from SD card
Sent from my GT-P5110 using XDA Free mobile app
Hey guys, I'm having a hard time installing xposed installer, I get "not enough space" error. Could any of you help out a fellow user..?
D5503 UB Dstriker ROM KK.157
EasySR said:
Just installed app on stock rooted lolipop (3G Watchdog) from SD card
Sent from my GT-P5110 using XDA Free mobile app
Click to expand...
Click to collapse
Ok thanks for info. On my rom selinux must be disabled temporary before installing any app from sdcard, than enabled. I will try to understand why it happening. For sure it is related to selinux. I replaced platform key in selinux_policy.xml since all apks on our rom is resigned and zipaligned but it was not solved problem related to the installing apks from sdcard.

CM 13 on Note 2 (N7100) The beauty of Marshmallow - My Review so far!

This is my personal experience with CM13 by Ivan meler
It may vary from your own experience but this can
Be very useful for everyone interested in using
Marshmallow on note 2. Am not responsible for any
Outcome whatsoever that may come by applying
Anything stated here on your phone, do it at your own
Risk
Click to expand...
Click to collapse
THE MYTH
YOU HAVE TO WIPE EVERYTHING Including your internal sdcard.
You don't have to wipe your internal sdcard to install Marshmallow CM13
For me, Marshmallow is everything that lollipop should be!
Great credits to XDA, CM and all the developers here who tirelessly
Worked to make lollipop better, in my opinion, I think that
Google gathered most of these fixes and implemented it into
the Marshmallow.
FLASHING MARSHMALLOW CM13
There's a lot of things that could look confusing about
Flashing CM13 but it's not as complicated as many had
Made it look.
THE DO'S AND DON'T
Don't leave your external in the the phone while running CM13 you
Won't like the outcome
Don't attempt dirty flash of CM13 On CM12.1
Don't format only system partition before flashing CM13
HOW TO FLASH CM13
I used Philz touch but TWRP recovery can Still do it. put the CM13 zip in the internal memory
If you're using philz recovery use clean to install new Rom. if you're using TWRP format /system, /data, /cache, /preload
Flash CM13 Zip
Here comes the gapps issues time: make sure that you have any other keyboard apk in your internal phone memory
If you reboot the system now everything will work well without gapps.
there are two different outcomes: if you flash CM13, (don't wipe cache or dalvik) flash gapps (i used open gapps full and slim zero mini) and reboot system
this means you won't be stuck setup wizard but In some cases you may still have AOSP keyboard unfortunately has stopped, disable it and install the keyboard apk you have in your phone memory
If you flash CM13 reboot the system before flashing gapps, you will face setup wizard issue and possibly Aosp keyboard issue whenever you flash gapps.
NEW DEVELOPMENT
Credits to @psndna88 the latest Angi kernel pureCM 4.4.9 (with SELinux permissive)
Makes it possible to use external sdcard and otg in CM13 but don't get so excited!
With Angi kernel 4.4.9 pureCM your external sdcard can be in your phone with
CM13 running perfectly but you can't use your sdcard files as normally as you do before. No app can see the sdcard (gallery and music player inclusive) the only way
You can access sdcard and OTG is via system settings - storage & USB. You can copy
Anything back to the internal memory - that's all you can do!
THE NEW FEATURES
There's no difference in the UI but many interesting changes and modifications in the system
#The multi window cut my attention although we had it in TW but its every welcomed
#Google now on tap is Nice
#Dose mode works but with full (stock) gapps I lost 6% of battery over night
Dose with slim gapps is way better with 2% battery loss over night
#Improvement on WiFi - unlike CM12.1 my WiFi can connect to a new network
While the phone is sleeping
#Dailer improvements - you can copy numbers that you just typed inside dailer
#Audio Fx improvement - combination of Angi kernel and Audio Fx was something Else in Marshmallow, so so sweet,dynamic and powerful.
#System animation, transition and scrolling lot better.
#Google settings now inside system settings
#default root works just fine but if you can't live with the # sign on status bar flash superSU
#App permission is way better - no matter the amount of permission an app requires you can choose to deny all or unnecessary permissions all by yourself.
#Even the android default Easter egg game has improved. I scored 14 on second attempt, never got 3 in lollipop
And many more options.
#I couldn't find System UI tuner in Ivan meler CM13
My Verdict
If you can't live without sdcard, wait for next updates
This is what lollipop should have been
It's a good improvement on lollipop.
The charging slowly that shows on the lock screen is a bug (it shows on both stock CM and Angi kernel) but the charging current is OK and the battery charges rapidly.
Bolumstar said:
THE MYTH
YOU HAVE TO WIPE EVERYTHING Including your internal sdcard.
You don't have to wipe your internal sdcard to install Marshmallow CM13
For me, Marshmallow is everything that lollipop should be!
Great credits to XDA, CM and all the developers here who tirelessly
Worked to make lollipop better, in my opinion, I think that
Google gathered most of these fixes and implemented it into
the Marshmallow.
FLASHING MARSHMALLOW CM13
There's a lot of things that could look confusing about
Flashing CM13 but it's not as complicated as many had
Made it look.
THE DO'S AND DON'T
Don't leave your external in the the phone while running CM13 you
Won't like the outcome
Don't attempt dirty flash of CM13 On CM12.1
Don't format only system partition before flashing CM13
HOW TO FLASH CM13
I used Philz touch but TWRP recovery can Still do it. put the CM13 zip in the internal memory
If you're using philz recovery use clean to install new Rom. if you're using TWRP format /system, /data, /cache, /preload
Flash CM13 Zip
Here comes the gapps issues time: make sure that you have any other keyboard apk in your internal phone memory
If you reboot the system now everything will work well without gapps.
there are two different outcomes: if you flash CM13, (don't wipe cache or dalvik) flash gapps (i used open gapps full and slim zero mini) and reboot system
this means you won't be stuck setup wizard but In some cases you may still have AOSP keyboard unfortunately has stopped, disable it and install the keyboard apk you have in your phone memory
If you flash CM13 reboot the system before flashing gapps, you will face setup wizard issue and possibly Aosp keyboard issue whenever you flash gapps.
NEW DEVELOPMENT
Credits to @psndna88 the latest Angi kernel pureCM 4.4.9 (with SELinux permissive)
Makes it possible to use external sdcard and otg in CM13 but don't get so excited!
With Angi kernel 4.4.9 pureCM your external sdcard can be in your phone with
CM13 running perfectly but you can't use your sdcard files as normally as you do before. No app can see the sdcard (gallery and music player inclusive) the only way
You can access sdcard and OTG is via system settings - storage & USB. You can copy
Anything back to the internal memory - that's all you can do!
THE NEW FEATURES
There's no difference in the UI but many interesting changes and modifications in the system
#The multi window cut my attention although we had it in TW but its every welcomed
#Google now on tap is Nice
#Dose mode works but with full (stock) gapps I lost 6% of battery over night
Dose with slim gapps is way better with 2% battery loss over night
#Improvement on WiFi - unlike CM12.1 my WiFi can connect to a new network
While the phone is sleeping
#Dailer improvements - you can copy numbers that you just typed inside dailer
#Audio Fx improvement - combination of Angi kernel and Audio Fx was something Else in Marshmallow, so so sweet,dynamic and powerful.
#System animation, transition and scrolling lot better.
#Google settings now inside system settings
#default root works just fine but if you can't live with the # sign on status bar flash superSU
#App permission is way better - no matter the amount of permission an app requires you can choose to deny all or unnecessary permissions all by yourself.
#Even the android default Easter egg game has improved. I scored 14 on second attempt, never got 3 in lollipop
And many more options.
#I couldn't find System UI tuner in Ivan meler CM13
My Verdict
If you can't live without sdcard, wait for next updates
This is what lollipop should have been
It's a good improvement on lollipop.
Click to expand...
Click to collapse
spen included or not?
muzliamir92 said:
spen included or not?
Click to expand...
Click to collapse
Not Included
Okey..thanks
Thanks
Thanks
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
Installed Ivan_meler cm13 with stock gapps...everything works except camera app bundle with the ROM..its gives me reboot...callsound quality is very poor..not upto mark.....
---------- Post added at 10:08 AM ---------- Previous post was at 09:59 AM ----------
U r unable to edit contacts like addition of pics.
Playback of videos is some what tricky.
Overall, ROM is smooth & fast, way better from stock ROM.
I wonder that if cm 13 is working so great on note 2 then why Samsung is denied latest update toall note 2 users android 6 ???
@saggi2015 Samsung and most OEM are interested in
Making profit. They want to force you to use not 4 or 5
Even when your note 2 can still serve your well. It was the
Disappointment of note 2 not getting lollipop from
Samsung that moved me to xda. Today am using
Android 6.0.1 but Samsung said we should get stocked in
4.4.2
Am currently using Resurrection Remix marshmallow and it already Rock stable and daily driver on its 1st release. Everything works fine.
Very true... I highly agree with u
How to uninstall stock gapps
---------- Post added at 03:19 PM ---------- Previous post was at 03:00 PM ----------
I wanted to uninstall stock gapps to install Nano or any lighter version of gapps
saggi2015 said:
How to uninstall stock gapps
---------- Post added at 03:19 PM ---------- Previous post was at 03:00 PM ----------
I wanted to uninstall stock gapps to install Nano or any lighter version of gapps
Click to expand...
Click to collapse
Most time you don't uninstall gapps. The bug free
Way is to wipe cache, wipe dalvik cache, format
/system partition flash the ROM again and flash the
New gapps you want to use.
Full gapps consumes more battery
I'll recommend slim mini gapps. Abt 172mb and it
Has Google now on tap
Thanks
have you tried DMD Panorama app with this rom? it`s not working...and not only this one app, but most of pano apps are not working, on any custom rom...only on stock 4.4.2 is working ok....it`s a very anoying bug
lulzcart said:
have you tried DMD Panorama app with this rom? it`s not working...and not only this one app, but most of pano apps are not working, on any custom rom...only on stock 4.4.2 is working ok....it`s a very anoying bug
Click to expand...
Click to collapse
There are many apps that are not Marshmallow ready.
The new permission system in Marshmallow requires
Devs to update their apps to work better.
Alternatively, you can clear app cache and/or data
And give it permissions manually. If it doesn't work,
Take a logcat and the rom Dev or any other member
Can help you out....
Bolumstar said:
There are many apps that are not Marshmallow ready.
The new permission system in Marshmallow requires
Devs to update their apps to work better.
Alternatively, you can clear app cache and/or data
And give it permissions manually. If it doesn't work,
Take a logcat and the rom Dev or any other member
Can help you out....
Click to expand...
Click to collapse
nothing will work to make this app and most panorama app to work...not even on CM 12.1, or any other custom rom....on the stock rom it works perfectly
I flashed Marshmallow on N7105 yesterday (the unofficial version) and I can't recognize any problems with leaving external in while flashing or any problems afterwards.
I did the cm 13
but when i came to flash gapps i stuck here,i am using twrp and the message appear was mds not match,aborting zip install, the gapps file which i download was ARM 6.0 SUPER
alkwaga said:
I did the cm 13
but when i came to flash gapps i stuck here,i am using twrp and the message appear was mds not match,aborting zip install, the gapps file which i download was ARM 6.0 SUPER
Click to expand...
Click to collapse
First, md5 is used to check if the file is correctly copied
Or downloaded. In very rare cases it might be wrong while
The file is ok.
Try flashing the gapps zip again but this time uncheck the
md5 checksum in TWRP recovery. If it fails then the zip
Files is corrupt.
Try re-downloading the the gapps zip file. I will
Recommend slim mini gapps or open gapps mini
Bolumstar said:
THE MYTH
YOU HAVE TO WIPE EVERYTHING Including your internal sdcard.
You don't have to wipe your internal sdcard to install Marshmallow CM13
For me, Marshmallow is everything that lollipop should be!
Great credits to XDA, CM and all the developers here who tirelessly
Worked to make lollipop better, in my opinion, I think that
Google gathered most of these fixes and implemented it into
the Marshmallow.
FLASHING MARSHMALLOW CM13
There's a lot of things that could look confusing about
Flashing CM13 but it's not as complicated as many had
Made it look.
THE DO'S AND DON'T
Don't leave your external in the the phone while running CM13 you
Won't like the outcome
Don't attempt dirty flash of CM13 On CM12.1
Don't format only system partition before flashing CM13
HOW TO FLASH CM13
I used Philz touch but TWRP recovery can Still do it. put the CM13 zip in the internal memory
If you're using philz recovery use clean to install new Rom. if you're using TWRP format /system, /data, /cache, /preload
Flash CM13 Zip
Here comes the gapps issues time: make sure that you have any other keyboard apk in your internal phone memory
If you reboot the system now everything will work well without gapps.
there are two different outcomes: if you flash CM13, (don't wipe cache or dalvik) flash gapps (i used open gapps full and slim zero mini) and reboot system
this means you won't be stuck setup wizard but In some cases you may still have AOSP keyboard unfortunately has stopped, disable it and install the keyboard apk you have in your phone memory
If you flash CM13 reboot the system before flashing gapps, you will face setup wizard issue and possibly Aosp keyboard issue whenever you flash gapps.
NEW DEVELOPMENT
Credits to @psndna88 the latest Angi kernel pureCM 4.4.9 (with SELinux permissive)
Makes it possible to use external sdcard and otg in CM13 but don't get so excited!
With Angi kernel 4.4.9 pureCM your external sdcard can be in your phone with
CM13 running perfectly but you can't use your sdcard files as normally as you do before. No app can see the sdcard (gallery and music player inclusive) the only way
You can access sdcard and OTG is via system settings - storage & USB. You can copy
Anything back to the internal memory - that's all you can do!
THE NEW FEATURES
There's no difference in the UI but many interesting changes and modifications in the system
#The multi window cut my attention although we had it in TW but its every welcomed
#Google now on tap is Nice
#Dose mode works but with full (stock) gapps I lost 6% of battery over night
Dose with slim gapps is way better with 2% battery loss over night
#Improvement on WiFi - unlike CM12.1 my WiFi can connect to a new network
While the phone is sleeping
#Dailer improvements - you can copy numbers that you just typed inside dailer
#Audio Fx improvement - combination of Angi kernel and Audio Fx was something Else in Marshmallow, so so sweet,dynamic and powerful.
#System animation, transition and scrolling lot better.
#Google settings now inside system settings
#default root works just fine but if you can't live with the # sign on status bar flash superSU
#App permission is way better - no matter the amount of permission an app requires you can choose to deny all or unnecessary permissions all by yourself.
#Even the android default Easter egg game has improved. I scored 14 on second attempt, never got 3 in lollipop
And many more options.
#I couldn't find System UI tuner in Ivan meler CM13
My Verdict
If you can't live without sdcard, wait for next updates
This is what lollipop should have been
It's a good improvement on lollipop.
Click to expand...
Click to collapse
I can't install custom recovery in my note 2 n7100. Returned with nand write start error with odin always in many versions and error 12 with heimdall.
Please help me with this issue. Thanks.
How can I download cm13 for note 2?
Please give me a download link...
Sent from my SM-N9005 using Tapatalk

[ROM-DISCONTINUED][SGH-T989][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Hercules

{
"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!

[APP][Unofficial]Dual Boot Patcher for 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

Categories

Resources