[GUIDE]Flashing Custom ROMs the easy way [A/B Devices only]

[GUIDE]Flashing Custom ROMs the easy way [A/B Devices only] - Android General

I created a script that'll ease Custom ROM installation on A/B devices. The script is generic and will work w/ any rom, device.
General flash instructions:
-Flash your devices' Stock ROM (for firmware)
-Flash your Custom ROM of choice
-Flash Finalize.zip
-Boot to System
Download finalize script from here
#######################################
For the intellectuals: This script clears the dalvik-cache and copies the firmware to both slots.
Hope this saved you guys some headache while flashing ROMs.

THREAD CLOSED
As per the request of the OP, this thread has been closed.
Please refer to this thread for continuous support in regards to this project.
Thx,
mrjuniork (Forum Moderator)

Related

Cyanogenmod ROM

Hello,
I am wanting to flash the following stable Cyanogenmod ROM to my HTC Desire S, but I am unsure whether or not I follow the same procedure as you would normally do. How would I flash the following ROM to my phone?
http://get.cm/get/2KF
Thanks in advance

The cm installer is not compatible with the saga, the cm roms in the development forum are all "unofficial" ports. If you check the compatability chart for the app you will see that the saga is not listed. Saga does not have official cm support as the kernel is considered unstable.
"Don't be so humble - you are not that great."
- Golda Meir (1898-1978)

deadphone99 said:
Hello,
I am wanting to flash the following stable Cyanogenmod ROM to my HTC Desire S, but I am unsure whether or not I follow the same procedure as you would normally do. How would I flash the following ROM to my phone?
http://get.cm/get/2KF
Thanks in advance
Click to expand...
Click to collapse
If you are 'unlock s-on'
-Full wipe(except sd)
-Flash rom
-Flash gapps(if needed)
-Reboot into fasboot
-Flash boot.img
-Reboot device
if s-off
-Full wipe(except sd)
-Flash rom
-Flash gapps(if needed)
-Reboot
*make a nandroid backup before proceeding
**backup your contacts, sms, account, data before flashing new rom
Check out the Help Thread if you want any further info. Post #1 to #3 contains most of the frequently ask questions and links.
Edit : i stand corrected, but i dont think you require gapps as it is already included.

[MI 4i/ferrari][OFFICIAL] DualbootPatcher - a much simpler dual boot solution

{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support Xiaomi Mi 4i.
I am not the creator, just the supporter
Disclaimer
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.
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
NOTE: If you want to dualboot a Miui ROM, I highly recommend installing Miui as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
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.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App 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.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
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.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
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:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Special Thanks
@chenxiaolong for the awesome DualBootPatcher. @onano for intial works on Xiaomi devices, helping me with builds and also his thread template for Redmi 1S
@thewisenerd for initial bringing up Dual Boot Patcher to Xiaomi Mi 4i
XDA:DevDB Information
[MI 4i/ferrari][OFFICIAL] DualbootPatcher - a much simpler dual boot solution, ROM for the Xiaomi Mi 4i
Contributors
faizauthar12, thewisenerd, chenxiaolong, onano
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-12-05
Last Updated 2016-12-07

Reserved
/* FAQ */
Q: is that possible to dual booting Miui with cm/AOSP rom?
A: yes it's possible, the primary rom must be Miui
Q: can i dual boot Miui and Miui?
A: you can't , while installing the secondary rom, you will got an error or something like that
Q: can we dual boot Miui 6 with anything or vice versa?
A: no you can't it will flash / patch the current primary Miui rom with the rom flashable zip
Q: is there is anyone do Miui and cm?
A: yes is it, go here (give him a thanks tho)
a video tutorial by @sharan.nyn
is here

- Will try this later. But anyways, thanks in advance!

Did anyone try this....?? I tried and getting an error(Unfortunately Dual Boot patcher(Debug) has stopped) while patching the ROM zip file. I am using the unofficial patcher app as advised in the instructions. Official app doesn't have the Mi4i in the device list hence not able to patch the zip. Can anyone please through some light to go forward.

apna.suresh0305 said:
Did anyone try this....?? I tried and getting an error(Unfortunately Dual Boot patcher(Debug) has stopped) while patching the ROM zip file. I am using the unofficial patcher app as advised in the instructions. Official app doesn't have the Mi4i in the device list hence not able to patch the zip. Can anyone please through some light to go forward.
Click to expand...
Click to collapse
Which ROM zip did you try to patch?
I was able to patch cm-12.1 zips correctly. Haven't tried with Marshmallow yet.

Appreciate if we could get the support for Elephone M2 as well....??? Below is the url for device thread.
http://forum.xda-developers.com/elephone-m2
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
thewisenerd said:
Which ROM zip did you try to patch?
I was able to patch cm-12.1 zips correctly. Haven't tried with Marshmallow yet.
Click to expand...
Click to collapse
I tried below mokee official builds...
http://download.mokeedev.com/?device=ferrari&type=release
I did a trick that the patcher is installed in my other mobile "Elephone M2" and patched zip files successfully, then moved those files again to Mi4i and installed. It worked.
Surprisingly i could able to patch from my secondary ROM (Mokee) but not from the primary rom(MIUI). I believe that MIUI rom is not supporting for patching it seems.

apna.suresh0305 said:
Appreciate if we could get the support for Elephone M2 as well....??? Below is the url for device thread.
http://forum.xda-developers.com/elephone-m2
don't spam orig dev section, use private messaging system
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
I tried below mokee official builds...
http://download.mokeedev.com/?device=ferrari&type=release
I did a trick that the patcher is installed in my other mobile "Elephone M2" and patched zip files successfully, then moved those files again to Mi4i and installed. It worked.
Surprisingly i could able to patch from my secondary ROM (Mokee) but not from the primary rom(MIUI). I believe that MIUI rom is not supporting for patching it seems.
Click to expand...
Click to collapse
provide logcat if possible

Thanks a lot for this, after years of runing multi boot on laptop, now I can runing multi boot on phone also. I have succses with triple boot install, everything is working well except one little thing: can in-app switch to another rom only if I on primary (RR 5.1.1), but, if on secondary (slim bit 6.0.1) or on data-slot rom (RR 6.0.1), I can switch to another rom only from twrp via flashing boot.img, even DualBootUtility.zip not working.
I have a one question: What is a Leaks app, who cames with DualBoot patcher app?? What means all that notifications/messages MainActivity leaks, leaks this, leaks that, etc... and what mean that message about memory dumping?? Thanks for answer.

cannot flash cm13 as secondary using miui as primary. Please if any body has tried elaborate steps to dualboot.

If you want to install cm13 as a secondary, that mean cm13 will be installed in chroot environment inside your MIUI ROM, exact path is /system/multiboot/dual. MIUI is "little big" rom, did you check how much free space you have in your MIUI /system partition? And what kind of error you got in recovery when you try to flas secondary.
In any case, steps for flashing are:
1. Boot into MIUI
2. Open Dual Boot Patcher app
3. Go to "Patch Zip File" option
4. Add your cm13.zip (and gapps optional), choose "secondary" on popup, if you want to install as a secondary on /system partition of existing rom
5. Press check mark in top right corner to patch zips you added
6. Boot into TWRP and flash cm13-blah-blah-dual.zip (and gapps-blah-blah-dual.zip optional) just normal, as a usually roms.
That's it.

Do i need to patch primary rom also before installing secondary?
I tried to upgrade primary stock rom with primary patched rom, got error cannot flash over rom through Dual Boot Patcher App.
I tried to clean install primary via TWRP, got error Failed to compute sha1sum of boot. Failed to flash zip file.
How do i make it work? Do I keep primary stock ROM as it is (MIUI) or patch primary ROM and flash secondary CM13.

stiw47 said:
Thanks a lot for this, after years of runing multi boot on laptop, now I can runing multi boot on phone also. I have succses with triple boot install, everything is working well except one little thing: can in-app switch to another rom only if I on primary (RR 5.1.1), but, if on secondary (slim bit 6.0.1) or on data-slot rom (RR 6.0.1), I can switch to another rom only from twrp via flashing boot.img, even DualBootUtility.zip not working.
I have a one question: What is a Leaks app, who cames with DualBoot patcher app?? What means all that notifications/messages MainActivity leaks, leaks this, leaks that, etc... and what mean that message about memory dumping?? Thanks for answer.
Click to expand...
Click to collapse
Can you explain the procedure step by step how did you manage to get triple boot ? Thanks

Account removal
Deleted

Is the project still going?
The status is testing from the first time I saw this thread

Hello. Somewhen at begining of this year, I was use some unofficial version of this app on MI 4i, founded here, in this thread, and mentioned version was working properly. Now, I want to fire up multiboot again, but as I see, things was changed here. Actualy, there is not MI 4i as supported device in latest snapshot provided in first post. Can someone give me a link for previous unofficial Dual Boot Patcher app?
Thanks in advance.
EDIT: Sorry, guys, such a stupid from my side. I found an app, in first post ofcourse.

It's possible
Sorry cause double post, but just for info, I successful running a MIUI V8.0.2.0.LXIMIDG Global Stable in dual boot with ResurrectionRemix-M-v5.7.4-20161005-ferrari from @Rohan purohit
Yes, yes, MIUI 8 in combination with M custom ROM on same phone. We already know, if we want to install L or M custom ROM on our phone, we must have 6.x.x firmware as a base. Procedure for making dual boot MIUI 8 + L/M custom ROM is same as usually. Main trick is how to switch ROM. Again, same as usually, but before every switching, you have to flash firmware files from recovery - 6.x.x if you switching to custom ROM and 8.x.x if you switching to MIUI.
Conclusion: I realy don't like MIUI, I am a person who like AOSP way, but MIUI camera is really really great, and some other features are pretty cool, now I have best from both world.
Unfortunately, this thread is little dead , but if you want to setup something like this or similarly, and stuck somewhere, be free to ask here or PM me, and I can write some mini tut with steps.

stiw47 said:
Sorry cause double post, but just for info, I successful running a MIUI V8.0.2.0.LXIMIDG Global Stable in dual boot with ResurrectionRemix-M-v5.7.4-20161005-ferrari from @Rohan purohit
Yes, yes, MIUI 8 in combination with M custom ROM on same phone. We already know, if we want to install L or M custom ROM on our phone, we must have 6.x.x firmware as a base. Procedure for making dual boot MIUI 8 + L/M custom ROM is same as usually. Main trick is how to switch ROM. Again, same as usually, but before every switching, you have to flash firmware files from recovery - 6.x.x if you switching to custom ROM and 8.x.x if you switching to MIUI.
Click to expand...
Click to collapse
Hey I'm trying to do exactly that! But I'm a little confused about what you mentioned - I am currently running MIUI 8 and wanted to flash a custom M ROM with the DualBoot Patcher, do I need to flash MIUI 6 before doing this? Or can I proceed to setting up the dualboot alongside MIUI 8? I also didn't understand what you meant about switching between the ROMs, do I need to flash a different version of MIUI to the MIUI partition every time I want to switch?
Sorry for so many questions, I was just confused about that and really wanted to do this, to get the best both MIUI and clean Android!

fonefan88 said:
Hey I'm trying to do exactly that! But I'm a little confused about what you mentioned - I am currently running MIUI 8 and wanted to flash a custom M ROM with the DualBoot Patcher, do I need to flash MIUI 6 before doing this? Or can I proceed to setting up the dualboot alongside MIUI 8? I also didn't understand what you meant about switching between the ROMs, do I need to flash a different version of MIUI to the MIUI partition every time I want to switch?
Sorry for so many questions, I was just confused about that and really wanted to do this, to get the best both MIUI and clean Android!
Click to expand...
Click to collapse
You should download or transfer a custom rom .zip file (and gapps optional) on your phone
Open Dual Boot Patcher app and patch all .zip files you want to install as a 'Data slot' (be creative and give some name to your data slot, it is mandatory).
After this you will get new .zip files (e.g. Rom-Name-data-slot-name.zip and Gapps-data-slot-name.zip) and this is a whole magic. Those new .zip files have instructions to be installed inside /data/multiboot/data-slot-name folder inside your primary ROM, not inside /system as ussual.
You will get a modded boot.img inside /sdcard/MultiBoot/data-slot-name also, and this boot.img have instructions to boot OS from /data/multiboot/data-slot-name , not from /system as ussual
Before installation of secondary ROM, start DualBoot Patcher app, and set a kernel of MIUI as a primary:
This is not nothing specialy, after this you will get a stock boot.img of MIUI8 inside a /sdcard/MultiBoot/primary, but you'll need it for further booting back to MIUI
Boot into TWRP and install a secondary ROM and gapps, usually as a normal rom and thats it.
***Switching between ROMs***
From MIUI to Custom:
Boot into TWRP
Install V6.6.10.0.firmware.zip (this is not whole ROM, this is already known firmaware files, here from xda)
Install /sdcard/MultiBoot/data-slot-name/boot.img as => Image => Boot
Reboot System and whoala, you are in custom ROM.
From Custom ROM to MIUI:
Boot into TWRP
Install V8.0.2.0.firmware.zip (this is not whole ROM, this is same as V6.6.10.0.firmware.zip mentioned above, but with firmware files for MIUI 8, packed by me )
Install /sdcard/MultiBoot/primary/boot.img as => Image => Boot
Reboot System and whoala, you are in MIUI.
I hope, I was helpful

YES that really helped clarify the process, thank you SO MUCH!! I really appreciate it!!

@stiw47
seems you're happy with dual boot patcher
check this out
https://dbp.noobdev.io/
have a nice day

[MOD] MultiROM v33 for Xperia L [Updated 02-10-2017]

Downloads
1. Main downloads
MultiROM: multirom-2017MMDD-v33x-taoshan.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-taoshan.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8930 Marshmallow based):
multirom_kernel-2016MMDD-taoshan.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
* No longer required thanks to the no-kexec workaround.
2. Third-party kernels with kexec-hardboot patch
* None, No longer needed due to no-kexec implementation.
3. MultiROM Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
* Flash uninstaller zip from recovery to remove MultiROM completely. This will also remove all your secondary ROMs.How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
OPTIONAL: Read about the no-kexec workaround by nkk71
Reboot the phone and Enjoy MultiROM!
Changelogs
Code:
=========================================
MultiROM v33x - TWRP 3.1.1 - 02/10/2017
=========================================
* Fixed incorrect mounting of partitions in TWRP
* Removed unused and deprecated flags in TWRP
* Fixed MultiROM TWRP versioning
=========================================
MultiROM v33x - TWRP 3.1.1 - 24/09/2017
=========================================
* [B]Fixed touchscreen issue in MultiROM UI[/B]
* cyttsp3: Update multi-touch protocol for display driver
* defconfig: Compress kernel with XZ (Smaller TWRP Size)
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
* Include all recent improvements from TWRP 3.1.1
* Updated to no-kexec workaround v4.1 by nkk71
* Autoboot accessible for external / MicroSD
* Improved versioning with header showing build date
* Built in a clean new tree of Android 7.1.2 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
=========================================
MultiROM v33x - TWRP 3.1.0 - 15/06/2016
=========================================
* Fixed MultiROM logo in UI
* Some Minor changes in the UI
=========================================
MultiROM v33x - TWRP 3.0.2 - 13/06/2016
=========================================
* Initial public release

FAQ and other notes
FAQ and other notesAbout security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods. Best solution is to remove the root zip from the ROM and flash it separately later.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.Current local manifest of the MultiROM build
Code:

Awesome work bro,thanks!!!

You are the best
Honestly, I never imagined that I'll be able to see multiRom on Xperia L
Thanks Dev. :laugh:

Awesome dev!
Will test it as soon as possible!
Thanks!

Awesome! Will test it for sure

WTF (What The Fantastic)
You're the best I'll try it ASAP

Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?

So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work

Mouaz Kaadan said:
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
Click to expand...
Click to collapse
1. Yes
2. Yes. You can keep your data along with ROM installation on ext sd.
n78 shadow said:
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Click to expand...
Click to collapse
No chances of bricking at all if you follow instruction and flash it correctly.

Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs

Aenadon said:
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Click to expand...
Click to collapse
1. Yep.
2. There is no Ubuntu OS ported for Xperia L.

Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?

kumardeepu said:
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
Click to expand...
Click to collapse
Please go through entire thread. Everything is written there.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
Click to expand...
Click to collapse

STRYDER~007 said:
Please go through entire thread. Everything is written there.
Click to expand...
Click to collapse
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?

kumardeepu said:
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
Click to expand...
Click to collapse
Yes.
Well actually in detail, First stock rom via flashtool->Root->Install SuperSU->Install Recovery via Recovery Installer app->Flash MultiROM Recovery zip->Reboot to MultiROM recovery->Flash MultiROM zip->Add Custom ROM!

MultiROM Updated
MultiROM updated with minor UI changes. Check OP.
Changelogs-
Code:
** 15-06-2016
- Fixed MultiROM logo in UI
- Some Minor changes in the UI

It fails when i try to flash the multirom zip
Why??
Sorry for my bad English

ShadowA9 said:
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
Click to expand...
Click to collapse
Flash MultiROM recovery zip first then boot into new recovery and flash multirom zip.

Development [CLOSED][GAPPS] Google Essential Pack [x64][R][11]

Hi there,
This is my custom google package for android 11-[R] based on my universal script for dynamic partitions.
What advantages ???
. Fast flashing (less than 3 seconds !!!) : to flash right away after flashing your custom vanilla ROM.
. Clear package : all contents are visible to the user who can manipulate/update on its own !
. Compatible with all [x64] devices ...
DOWNLOAD
Here

Whats about android auto. Does it work with your package - with a degoogled rom?

Thanks

Update 2021-10-07
addon.d remover (.zip) added :
. to flash before you install/update a new build of your custom rom ... so you have a clean build install without persistent open gapps
. No need to flash the whole original software to cleanup open gapps !

THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator

Development [21.06.23] Full ROM System-RW for S908E/B I Magisk ROM Module for all S22 I Dr.Ketan ROM

S908B & S908E system-rw Dr.Ketan ROM
Supported device : S918B & S908E/N for Full ROM, All rootable variants for Magisk Module
We do support usually 2-3 years since device launched, but yet no guarantee, We may drop support for any device / any variant/s anytime without any prior notice.
ROM Features
ROM Features varies with version of ROM. For more details, read changelog post. Link available in post #3 for changelog of all versions.
Must read changelog for a version you are going to install, it will have latest information about features, changes, known bug list/fix and Installation guide of respective version.
There are two types of ROM available since OneUI 5.0
1.Full system-rw ROM : Full ROM includes super.img with system-rw capabilities + stock enforcing kernel + ROM Control & Modification
Supported device : S908B & S908E
2.Magisk ROM Module and here explained in details how it is different from full ROM
Supported device : All S22 variants
Credit and Thanks :
@Chainfire - Respected elite developer for supersu and his unbelievable contribution to XDA/Android community. @wanam - Respected elite developer for his awesome contribution and references to his works.
@topjohnwu for Magisk
@xperiacle the amazing developer for reference to his work and tools. @amarullz for aroma installer. @gharrington for 3minit battery and QuickLaunch.
ROM Control source and all credit and thanks goes to @daxgirl and @Wuby986 for their open source project for RomControl.
@AbrahamGC for some ideas samsungvn htcmania & 4PDA for tips and some stock apks.
AbrahamGC and Anan1211 for Secure folder and s-health A12 ianmacd for TWRP @afaneh92 for TWRP, system/vendor rw scripts and modules. @Arteush for bluetooth fix (losing BT pair on reboot) on Android Q, aka_vkl for Dolby digital, kdrag0n for SafetyNet fix @Winb33 for custom font pack. HuskyDG for Bootloop Protector magisk module. MrWeahere for CRB Kitchen

XDA devDB InformationS908 I Dr.Ketan ROM , ROM for the Samsung Galaxy S22 Ultra
Contributors
Dr.Ketan
ROM OS Version: Android 12
ROM Kernel: Stock (pre-rooted). Source code (samsung) here
ROM Firmware Required: Stock Samsung specified version
Version Information
Status: Stable
Created 2022-03-12

Installation, Important Infos & Download
Installation : State of the art Installation procedure.
Detailed installation guide separately available in download area along with ROM files for Full ROM and for magisk module read changelog post.
WARNING
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but ROM is patched for all these mentioned features. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
ROM Tool permission : Files & media - To save and read files, Calendar - Tool needs some time monitoring to avoid using RT immediately after reboot. Special access for accessibility service - Since Android 12 it requires for QS panel custom Toggl e.g. Reboot to recovery
Download : https://drketanrom.com/

ChangeLog for Magisk Module ROM
OneUI 4.0
Spoiler: ChangeLog OneUI 4.1
ChangeLog OneUI 4.1
- S01 - 12.03.2022
- S02 - 14.03.2022
- S03 - 19.03.2022 & S03.1 - 30.03.2022
- S04 - 06.04.2022
- S05 - 27.04.2022
- S06 - 27.05.2022
- S07 - 05.06.2022
- S08 - 18.06.2022
- S09 - 08.07.2022
- S10 - 05.08.2022
- S11 - 15.10.2022
OneUI 5.0
- T01 - 26.10.2022
- T02 - 19.11.2022
- T03 - 14.12.2022
- T04 - 15.01.2023
OneUI 5.1
- T05 - 17.02.2023
- T06 - 11.03.2023
- T07 - 14.04.2023
- T08 - 15.05.2023
- T09 - 20.06.2023
ChangeLog for Full System-RW ROM
OneUI 5.0
- T01 - 07.11.2022
- T02 - 20.11.2022
- T03 - 14.12.2022
- T04 - 17.01.2023
OneUI 5.1
- T05 - 17.02.2023
- T06 - 11.03.2023
- T07 - 11.04.2023
- T08 - 12.05.2023
- T09 - 21.06.2023

How to Root (currently non rooted device) with or without TWRP
Spoiler: Root existing non rooted device
Root with or Without TWRP
1.Root without TWRP :
Unlock Bootloader
You needs to download stock firmware (You can get stock firmware with Frija) and extract AP*.tar.md5 file and patch with magisk. Flash patched file with AP tab of Odin PS : In case root files without TWRP available in download area for your variant, you can use that for AP slot instead of Patching AP
put device in download mode and connect to PC and flash above files
Reboot to recovery and select to format data
Reboot to system → You will see Magisk stub in drawer → Update it. (In case stub not there, Donload magisk app from Download area and intall manually) → Open Magisk - It will ask to complete additionl setup, Let it do. → Reboot device. You are now ready to Intall Dr.Ketan ROM module. Move to next step.
2.Root with TWRP
Unlock Bootloader
Download TWRP, Patched vbmeta and Kernel and system-rw script zip from TWRP thread (Link below)
Select TWRP tar file with AP slot and Patched vbmeta for USERDATA slot of Odin PS : In case root files with TWRP available in download area for your variant, you can use that for AP slot. It contains both TWRP+patched vbmeta
Put device in download mode and connect to PC and flash above files
When Flashing completes, disconnect device and starightway reboot to TWRP
Run multidisabler from TWRP → Advanced → Terminal → and type : multidisabler (it may take few minutes, keep patience)
Wipe Data (Full wipe, that you needs to type YES to continue)
Reboot TWRP and now connect to PC and copy Custom kernel and flash from TWRP as zip
get Latest magisk apk and flash from TWRP
If you want to make system-rw, Get afaneh92_lp_rw_tool_v*.zip from TWRP thread and flash
Reboot device to system Update Magisk from stub if availble OR Install Magisk apk
Now ready to install Dr.Ketan Module, Follow XDA ROM Changelog post to install ROM Module
Thanks & Credit to Afaneh92 for TWRP & Kernel, below are link for OP Exynos and SnapDragon
PS : For detailed instructions about Magisk installation (root) read here. In case still you have question, move to Question forum of S22 section and ask for help. This thread is development thread and any questions related to how to root will be ignored.
How to Update Firmware and Keep root/twrp intact without losing data
PS : We highly recommend to make data backup before trying this as something went wrong and you may lose data.
Spoiler: Update Firmwre with Keeping Root/TWRP/data intact
Read below methods depending on you have root with or without TWRP
1.Rooted S908B/E/N/0 without TWRP
Unlock bootloader
You needs to download stock firmware you want to update (You can get stock firmware with Frija) and extract AP*.tar.md5 file and patch with magisk. Select Patched AP file for AP slot and BL*.tar.md5,CP_tar.md5,Home_CSC*tar.md5 for BL,CP and CSC slot accordingly. (PS : In case root files without TWRP available in download area for your variant, you can use that for AP slot instead of Patching AP, Importnt : Use Home_CSC*tar.md5 if you want to keep data. Selecting CSC*.tar.md5 will Wipe data autometiclly.)
Reboot device → You are now ready to Intall Dr.Ketan ROM module. Move to next step.
2.Rooted S908B/E/N/0 with TWRP
Download latest firmware as per pre-requisite
Disable Auto Reboot option in Odin
Select appropriate slot in Odin for BL,AP,CP and CSC (Using HOME_CSC will keep data, while using CSC* will format data) from stock firmware
Select TWRP file for USEDATA slot . File must include patched vbmeta file. If TWRP doesn't have patched vbmeta included, you have to make one yourself. To make TWRP+Patched vbmeta : Download both the files from TWRP thread and extract it to get recovery.img and vbmet.img. On your PC, select these two .img files and Rt click → select 7zip → Add to archieve → select archieve format "tar" → Select OK and this will create a tar file that have TWRP+Patched vbmeta. Use newly created tar file for Userdat slot of Odin. PS : Incase download area have Rootfiles with TWRP for your device then it contains everything TWRP+patched vbmeta + Kernel, extract zip to get all required files
When Flashing completes, disconnect device and starightway reboot to TWRP. Importnt : At this stage you should be quick to reboot to TWRP, If you flais and device tries to boot to system, you may have to wipe data.
Run multidisabler from TWRP → Advanced → Terminal → and type : multidisabler (it may take few minutes, keep patience)
Wipe Data (If you are already using Afaneh92's TWRP and used multidisabler + Format data, you can select to Factory Reset too (This will preserve media file) OR you can skip wipe option at all in case you want dirty Install.)
Reboot to TWRP In case you have wiped data.
Copy Kernel & Magisk apk/zip to device (Alternatively use USB storage)
Install kernel (Flash Kernel zip from TWRP)
Flash Magisk
If you want to make system-rw, Get afaneh92_lp_rw_tool_v*.zip from TWRP thread and flash
If you don't have magisk app in drawer (in case of clean install), Install manually.
Open Magisk app and complete setup if it asked for
PS : If you are on any other TWRP or Stock recovery, you must FORMAT DATA (That requires to type 'Yes' to confrm wipe)
Now ready to install Dr.Ketan Module, Follow XDA ROM Changelog post to install ROM Module
Thanks & Credit to Afaneh92 for TWRP & Kernel, below are link for OP Exynos and SnapDragon
PS : For detailed instructions about Magisk installation (root) read here. In case still you have question, move to Question forum of S22 section and ask for help. This thread is development thread and any questions related to how to root will be ignored.

Help & Support
We do support only ROM related queries here over XDA thread only, we do not have/encourage any private support over telegram or other media to support ROM related queries.
We do not answer any ROM related question over private chat.
If your queries doesn't have enough information, it will be ignored.
We recommend everyone to read OP,Changelog and Installation guide before you install ROM. If answer to your queries already there in OP, Changelog post or in Installation guide, it will be ignored
Any queries not reated to XDA ROM (e.g. TweaksPro) then you must seek help from developer over mail/privately. Here we discuss only XDA ROM related issue.
For reporting issue/bugs you must provide enough info as said below under "How to report bug/issue"
How to report bugs/Issue?
To report issue, you needs to provide following informations, else it will be ignored. Also if your query is already mentioned on OP/ChangeLogg post, it will be ignored.
1.ROM build number.
2.Dirty/Clean Install. - If you have dirty installed, Then first clean install and report if issue persists.
3.Bug/Issue appears right after installing or later?
4.How to reproduce error.
5.Is there any same reports there on thread on your searching?
6.Is there any mention about same bug on OP or changeLog post?
7.Logs - Attach logs here/Upload to other places where it can be downloaded without registration and doesn't have ad (we recommend dropbox/Gdrive) and post link.
Click to expand...
Click to collapse

Finally! After all the teasers and trailers ... We are getting into serious business !
THANK YOU
All the best and cheers Dr. !

ChangeLog S01
Based on S908EXXU1AVBF Android12 March 2022 security patch OneUI 4.1
ROM Tool on essential fix auto setup zygisk including SafetyNet fix (no needs to change any option manually)
Important Instructions for setting up ROM (NEW)
Prerequisite :
Must have installed firmware S908EXXU1AVBF S22 Ultra
Rooted device with Magisk (Zygisk) Intallled (Follow steps belo in case you have non rooted device)
How to Root device
Unlock bootloader
Download Root_files*.zip (available in download area) - Extract and Flash Root_Files_*.tar.md5 with Odin for AP tab
Reboot to recovery and select to format data (Factory reset option on stock recovery)
Reboot device → You will see Magisk stub in drawer → Update it. (In case stuf not there, Donload magisk app from Donload area and intall manually) → Open Magisk - It will ask to complete additionl setup, Let it do. → Reboot device. You are now ready to Intall Dr.Ketan ROM module. Move to next step.
How to Install Dr.Ketn ROM Module
Download DrKetan_ROM_S*_module.zip and copy to device, We recommend to check MD5 to rule out faulty download
Uninstall any other magisk module you have installed
Open Magisk app → Click on Module → Select Install from storage → Select Module file you have copied to device → Complete Intallation and reboot device
Setting up device first time after Module installation
Open ROM Tool, Apply essential fix and Reboot,
After reboot you can check SafetyNet and should be passed. You can use this app from playstore or This from Github to check SafetyNet
Now you can further setup ROM a per your liking. Also MagikHide is Configure Denylist now and available under Magisk Settings.
Since A12 Stable Magisk not working and new Magisk doesn't have buil-in Module repo, You can get standalone module manager from here For more details and queries about new magisk ref this
PS : Plz don't install any other mods for SafetyNet, All queries related to Magisk/SafetyNet will be ignored if already explained above
TweaksPro version requires 4.1.0 or up
ROM Features (XDA Version)
- Ad Free QS Panel Toggle
- Reboot to recovery QS Panel Toggle
- Native call recorder (Manual) While you are on call - click 3 dot - Record (Should work without CSC restriction)
- Auto Call recorder without CSC restriction (ROM Tool - Mods & Fix)
- High Volume warning disabled
- Pre fixed Titanium freezing while restoring apps
- Probable fix for Titanium Backup schedule
- Internet browser Secret mode
- S Health patch for using with rooted device.
- ROM Tool with following Options
AdFree mode Enable/Disable
Single click install/uninstall custom fonts (on the fly)
YouTube Vanced Installer (No xposed requires)
NonRoot - Requires MicroG to login
Root - Truely alternate to Youtube, Can login to youtube without MicroG (disable Play store update)
You have to click on NonRoot/Root depending on your choice, then you needs to click "Install" tab and latest version of Youtube vanced will get installed.
StatusBar Icons
Show/Hide stock battery
Show/Hide 3minit battery
show/hide stock clock
show/hide 3minit clock
ROM Control - See below
Mods & Fix
Auto Call Record
Titanium backup FC fix
Google Pay Fix
Added camera fix (Certain users reported camera failed issue. This is reported on stock too, here is someworkaroung meanwhile samsung fix it)
SafetyNet Fix
Samsung Health & Private share fix
Update & Fix
- ROM Control (systemUI preferences)
Battery Bar with thickness and color option
Virtual key on statusbar (Lt/Cinter/Rt)
Network meter with Toggle (Lt/Rt/Quick Panel/None) with color option
PS : There may be few more options in ROM control but won't work if those are not mentioned here.
Known Bug/Tips/Fix
3 minit users can use 3minit battery paid version for free. Check this (Thanks to gharrington )
Tips on TWRP and App Backup/Restore Read Here
Download : DrKetanROM.com
PS : This is a fully customized ROM and for end users only, ROM or any part of ROM not allowed to redistribute,modify or to use as base to prepare new ROM.
STATUS : Online

Haleluja, its here!! Great amazing work! OMG I'm so excited! Let's go!!
Thanks alot !!! Finally I can unpack my S22 Ultra ^^ and use it as real Phone
Proud to be the first worldwide to have a Custom ROM, FULL ROOT, Adblock etc on a S22 Ultra Exynos
Community LOVE for you!! ♥♥♥♥♥
EDIT: HERE IS THE GUIDE TO USE FOR EXYNOS (still testing)
Ok, so basically find and download the firmware (S908BXXU1AVC6 for EU - or ask me for the File..) to the phone eather with the Phone itself or trought USB-Cable, install magisk.apk from here, unpack the zip file from Firmware and patch the ap file via magisk, get the files to the pc and use odin to flash the patched Firmware.
of course unlock bootloader before and go to download mode.
Here is how to do that:
Guide to root Galaxy S22 Ultra (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. Sorry for USA models, you can't root unless you can unlock your bootloader You...
forum.xda-developers.com
or
https://www.droidwin.com/how-to-unlock-bootloader-on-samsung-galaxy-s22-s22-plus-s22-ultra/
Then follow the other steps from Dr. Ketan

S01 Dr.Ketan Magisk ROM is Online now
Must read changelog above for Installation guide and other Info
Thank you for Support & Trust on this ROM.

no rom, only module

Yaiks. Hopefully it will be available for B variant

iampatricktan said:
Yaiks. Hopefully it will be available for B variant
Click to expand...
Click to collapse
You can try on exynos (only module, no root files). If it doesn't work then maximum you needs is to factory reset.
In that case I may consider to make separate rom

dr.ketan said:
You can try on exynos (only module, no root files). If it doesn't work then maximum you needs is to factory reset.
In that case I may consider to make separate rom
Click to expand...
Click to collapse
I think its much better to make separate only for Exnos variant? So that files for SD will not be included, correct me if I'm wrong about that. Also been using your ROM since my Note 9.

dr.ketan said:
S01 Dr.Ketan Magisk ROM is Online now
Must read changelog above for Installation guide and other Info
Thank you for Support & Trust on this ROM.
.
Click to expand...
Click to collapse
Huge thx my bro

ok, so great news, it works at least for exynos as well!
Safetynet also works!
Problems so far:
Can't change my keyboard - UI restarts
com.android.phone closes down
and it says system is unstable - please do a factory restore - on boot up.
But all in all it seems to work, with root etc.

Thx Dr My bro. Hopefully we can have the Exynos version seperatly if possible and not too much of your time consuming.

beautyangel said:
Thx Dr My bro. Hopefully we can have the Exynos version seperatly if possible and not too much of your time consuming.
Click to expand...
Click to collapse
||||| said:
ok, so great news, it works at least for exynos as well!
Safetynet also works!
Problems so far:
Can't change my keyboard - UI restarts
com.android.phone closes down
and it says system is unstable - please do a factory restore - on boot up.
But all in all it seems to work, with root etc.
Click to expand...
Click to collapse
Will do it later today
Any of you free just inbox me

For S908B EXYNOS Users
I have added Bootlogo error text removal file in Download area. Instructions packed inside.
PS : DON'T USE ON SNAPDRAGON device
.

A thousand thank yous @dr.ketan and to @||||| for your Exynos work
Just need delivery of my S22 from Sammy now

dr.ketan said:
For S908B EXYNOS Users
I have added Bootlogo error text removal file in Download area. Instructions packed inside.
PS : DON'T USE ON SNAPDRAGON device
Huge Huge thx Dr my Bro and @||||| for all Awesome job.
Click to expand...
Click to collapse

Database Info

welcome