Related
Agnostic-kernel - filesystem independent kernel flasher
WARNING!
Please, make a backup or be prepared to roll back to a working state somehow. You are using this tool on your own responsibility. You have been warned!
If anything goes wrong, flashing another kernel that was working for you before should return your device to a working state.
Repository on GitHub
This is a recovery tool primarily made for kernel/ROM developers, but anyone is welcome to use it, provided he knows what to do. It was made to enable kernel developers to have a single .zip with the kernel which will work on all partition layouts like All-F2FS, Data-F2FS and All-EXT4 (the standard layout).
It takes a boot.img, unpacks it during the installation, finds out what partition layout is used on the device, changes the fstab in the ramdisk accordingly, repacks the boot.img and flashes it.
Instructions for kernel/ROM developers/flashaholics who wish to incorporate this tool:
Make sure your kernel is compiled with F2FS drivers.
Download agnostic-kernel-template.zip
Replace the boot.img-placeholder in the .zip with your boot.img.
OPTIONAL: change the fstab in fstab/ folder to specify any mount options you wish to use. Make sure you include a line for each partition and filesystem combination you want to use.
OPTIONAL: change the updater-script to print any additional messages or make modifications to the kernel after flashing.
Instructions for users who wish to try this tool:
Choose one of the prepacked kernels you wish to install and download it.
Install it via recovery.
Instructions for people who wish to port it to other devices:
Change the asserts in updater-script to check for your device name.
Change the fstab in the fstab/ folder. Make sure you include a line for each partition and filesystem combination you want to use.
Change the FSTAB variable in tools/repack-and-flash.sh to contain the name of your fstab file.
Change the BOOT_PARTITION variable to contain the path to your /boot partition device.
Currently supported partition layouts:
/system on EXT4 or F2FS
/cache on EXT4 or F2FS
/data on EXT4 or F2FS
Filesystem changes are supported only on these partitions because the Nexus 7 doesn't have any other EXT4 partitions by default.
If you want to add support for some other device specific layout (F2FS formatted SD card comes to mind, for example), feel free to do so or contact me, but it may require some changes to your recovery too.
Tested on:
Kernels
3.2.5-XPerience by @TeamMex
LegoKernel / SlimKernel by @legolas93
franco.Kernel by @franciscofranco and modified by @HTCDreamOn
linux-tegra-nv-3.1-grouper by @HTCDreamOn
M-Kernel by @Metallice
Recoveries
CWM Recovery 6.0.4.3 by ClockworkMod
TWRP by @legolas93[/MENTION]
MultiROM recovery by @@Tasssadar
ROMs
ROM shouldn't matter, I tested on various 4.4 / 5.0 ROMs and even without a ROM and it always worked.
Downloads
Pre-packed kernels:
Kernel from SlimROM by @legolas93
3.2.5-XPerience-19 by @TeamMex
Empty template for devs:
agnostic-kernel-template.zipYou can download other kernels using agnostic-kernel in their respective threads.
Credits:
Android Image Kitchen - @osm0sis - this wouldn't be possible without him
F2FS Recovery - @legolas93
Kernels on which I tested - @TeamMex & @legolas93 & @franciscofranco & @HTCDreamOn & @Metallice
Recovery magic - @Chainfire & @_that
Answers to a lot of my problems - forum.xda-developers.com community
Some nice ideas - @Metallice
Partition layout checking, scripting - @frantisek.nesveda
If you wish to incorporate or modify this tool, please, mention me somewhere, thanks
Changelog:
13th November 2014
This is a highly recommended update for all developers using agnostic-kernel.
Now completely ROM independent
Updated Android Kitchen to version 1.6 - thanks, @osm0sis!
Fixed an issue with Android Kitchen binaries using /system/bin/linker which was not always available.
First I did an ugly hack to solve the issue...
and then I found out that the updated Android Kitchen binaries are statically linked now and the ugly hack was not needed anymore.
Changes to the way fstab is generated - now it uses only one file and deletes unneeded lines from it - inspired by @Metallice
Added more error-checking
Some other small fixes and improvements
Tested on a lot of recoveries and partition layouts.
13th May 2014
Fixed an issue with the zip which could arise when /system was not mounted before the install.
Tested on a lot of recoveries and partition layouts.
12th May 2014
Initial release.
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
aosp said:
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
Click to expand...
Click to collapse
If I'm not mistaken, this is a code in a custom recovery that enables the user to select if he wants to format his partitions as F2FS or EXT4, similar to what the MultiROM recovery does after yesterday's update?
If so, I don't see the connection that your code has with my tool... My tool is a template for a recovery zip, in which kernel devs can place their boot.img, and when the user installs that zip with the boot.img, the script in that zip will check for which partitions does the user have formatted as F2FS and modify the fstab in the boot.img accordingly.
Updated all the zips with a bugfix. The Android Image Kitchen would not start on CWM when /system was not mounted, because it tried to use sh in /system/bin instead of /sbin.
Also, I tested the zips on more partition layouts and recoveries, and verified that it works right both on CWM and TWRP and on ALL-F2FS, Data-F2FS and ALL-EXT4.
awesome work
How do we convert if we only have a zimage and no boot.img
Sent from my Nexus 7 using Tapatalk
chaostrodamis said:
How do we convert if we only have a zimage and no boot.img
Click to expand...
Click to collapse
The changes are all done to the ramdisk, so you can't do them without one, at least not with this method.
But, if you look how @sgt. meow does it in his Oxydo kernel, perhaps that is the way you could use. He unpacks the ramdisk from the currently installed kernel and then packs it with his zImage to a boot.img which he then flashes. This requires that the user first flashes another kernel with f2fs working, and then flashes your kernel.
Perhaps it would be easier if you packed your kernel with some ramdisk and then used it.
An updated version of agnostic-kernel is available in the OP. See post #2 for changelog.
Both the template zip and the two prepacked kernels are updated.
This is a highly reccomended update for all kernel developers, as it fixes compatibility issues with some ROMs (AOSP Lollipop, for example).
I've also published sources to my working folder on GitHub, if anyone is interested. There's nothing really important there, though.
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
RoryB said:
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
Click to expand...
Click to collapse
You're welcome. And you could perhaps try pulling the boot.img with dd, something like this:
Code:
dd if=$BOOT_PARTITION of=/tmp/agnostic-kernel/boot.img
I don't take responsibility for any damage may happen to your device because of using this tool, USE AT YOUR OWN RISKA new generation of Android ROMs development...The ClassyKitchen
{
"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"
}
About:
A new C++ Windows application that based on ASSAYYED KITCHEN to deal with the most of android ROMs (stock images, stock updates, running device ..... etc)
In addition to built-in apktool to easily decompile & recompile apk in the PROJECT
And with a friendly user interface with full mouse control just one click.
With static build feature and a new built-in windows tools feature (hex dump) that makes the whole working environment into one exe file only.
ROM editor features:
1 - Supported ROMs type for extract:
Any stock system[lz4] & boot[lz4] [cache | odm] images
All Samsung stock firmwares (TAR[.MD5]) with support for LZ4 compress
All Google stock firmwares (ZIP)
All Lineage stock ROMs (system.new.dat[br] & vendor - payload.bin)
Any other images dumped from other stock ROMs (Huawei - HTC.....etc)
Rooted device OR custom recovery (*With technology to dump boot & system & vendor images without need a space on device*)
2 - Supported ROM edits:
Pre-remove for Samsung RMM security
DeOdex for android [4.x.x] till [9.x.x]
ZipAlign for all APKs & JARs
Heavy DeBloat ROM with Re-Bloat
Full DeKnox ROM
Clean ROM from all CSC apks (in Samsung ROMs)
Support safe and powerful Build.prop tweaks
Support change Build Number text
Support add busybox into the ROM itself with all available symlinks in image
3 - Supported ROM build:
ZIP ROM contains sparse system [vendor & odm] dat
ZIP ROM for custom recovery flashing
ZIP images ROM for fastboot flashing
TAR images ROM for Samsung devices
Support compress Samsung images with original LZ4 format
4 - Supported boot image edits:
Support all boot images partitions names other than boot.img
Remove dm-verity with AVB & ForceEncryption
Enable ADB
Patch sepolicy (supports CIL) to supported deodexed Oreo
Add / Remove Magisk Root to boot image directly in windows
Support patch boot image to run scripts during boot that placed in /system/smart_scripts
5 - Supported Apktool:
Decompile single apk
Recompile single apk
Sign single apk
Support option to specify [New | Original] apk signature
Support use custom apktool.jar selected by user
Support Decompile - Recompile multi APKs in the same time
Support Decompile - Recompile JAR files (Support multi classes files)
6 - Supported On Device Features:
Support dump full device memory using (adb root) - supported (EMMC & UFS) Without need any space on device
Support dump specified partitions from device using (adb root) - (List to user and pick needed partitions)
General Features:
Quite simple user interface
Very safe when working with images ROM for files [modes, gid, uid, contexts, capabilities]
Read the exact EXT4 [symbolic links, full permissions] and re-apply them when building
Write full permissions for [fs_config, contexts, capabilities] when building an EXT4 image or in [updater-script]
Support fix the case sensitive problems with ROMs like (Samsung S8 / S8+)
Support save project and restore it when needing
Support [Added edits log] to allow the user to see all edits he made
Support add custom text during flash in recovery
Support save the system image and [odm] image sizes to rebuild them using the exact original size
Support allow user to change the build configs (size, sparse header, images ext)
Support custom debloat list
Support more that one connected ADB device and list them to user to pick one to pull ROM from
Pro Version:
The kitchen has two versions Free & Pro
And the Pro version requiring a small donation (20$) and it needs an authenticating code to run it on a specified PC,
If anyone need to use it just download and run then send to me the output code with a transaction ID to send the activation code that match the given code.
NOTE: The Pro version is to supporting my work only, and the Free version is enough to create a full modded flashable ROM
- The following features are only available in Pro version:
All On Device Features
Pull ROM from Rooted device or custom recovery
Change Build Number text
Build TAR images ROM for Samsung devices
Build ZIP images ROM for fastboot flashing
Add Magisk Root to boot image directly in Windows
Patch boot image to run script during boot
Decompile - Recompile multi APKs in the same time
Manual DeBloat as user wants
Download link:
- Latest Free Version: http://www.mediafire.com/file/7uch95enkpc7q2p/ClassyKitchen_Free_Beta_1.0.4.7z/file
- Latest Pro Version: http://www.mediafire.com/file/l62q85rj8d8lqu0/ClassyKitchen_Pro_Beta_1.0.4.7z/file
Changelog:
- Version: 1.0.4 - BETA:
Added support to build sparse dat images
Improved some props read in OnePlus devices
Added new tab On Device Features: Support dump Full device memory without need space on device & dump selected partitions without need space too (Pro Version)
Updated flash_kernel.sh script
Updated Magisk to version 18.0
- Version: 1.0.3 - BETA: Free Version - Pro Version
Added support to Decompile - Recompile multi apks in the same time (Pro Version)
Added support to manual DeBloat (list all ROM apks to user to pick one and remove) (Pro Version)
Updated DeKnox list
Improved dump ROM from device (skip search for ODM - VENDOR partitions if the device doesn't have them)
Added support to decompile & recompile JAR files
Added support to deal with boot images that have names other than boot.img
Added support to build ODM image in fastboot build option
ReCoded all Deodex codes to support ROMs that have symlinked 64 oat files like Huawei devices
Updated Magisk Root files and Magisk sources to v18
- Version: 1.0.2 - BETA: Free Version - Pro Version
Added support to ReCompress Samsung images to LZ4 during TAR building
Updated packing original APK signature during APK compiling
Updated Magisk to 17.3 (2018-11-22)
Added SmartScripts feature to easy run scripts as Root during system boot (Pro Version)
- Version: 1.0.1 - BETA: Free Version - Pro Version
Fixed bug happened when switch from system_root to system type ROM
Added support to vendor (build zip - build images - extract)
Updated building images codes (better size printing)
Added support to (vendor.new.dat[br])
Added support to pull vendor image from Rooted devices
- Version: 1.0.0 - BETA: Free Version - Pro Version
Initial release
Reports & Request features:
To report any issue Please provide a pic for the Error happened in the Kitchen and A link for the ROM used (Without them I can not provide any help) (Posting here not via PM please).
To request any features to add or any notes about exists features just post about them on this thread (Or via PM).
Credits:
- Cygwin Project: For base tools to deal with Linux symbolic links in Windows
- 7zip: For 7z binary to deal with EXT4 filesystem
- AOPS Platform Tools: For ADB tools
- And_pda: For ImgExtractor tool
- LZ4 Project: For sources to deal with lz4 compressed images
- AOSP Sources: For all android sources (sparse converting, simg2img, aapt, zipalign, brotli, cdex_convert_sources, readelf......etc)
- Cubinator: For his EXT4 images analyzing python sources
- testwhat: For oat2dex tool
- anestisb: For vdexExtractor tool
- Linus Yang: For compact_dex_converter tool
@topjohnwu: For Magiskboot tool sources
@JesusFreke: For his Smali & Baksmali
@xpirt: For sdat2img python tool
@iuss: For payload_dumper python tool
@iBotPeaches: For apktool tool
WoW , that was mind blowing . I Just got my Pro version, and i build my first tar rom and it was flashed successfully . Thank you sir.
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
arvs47 said:
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
Click to expand...
Click to collapse
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
AndroDef said:
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
Click to expand...
Click to collapse
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
arvs47 said:
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
Click to expand...
Click to collapse
No, Porting feature is not supported now
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
dr460nf1r3 said:
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
Click to expand...
Click to collapse
Create a (txt) file and write in it all items you want to remove (Names with extensions only without paths)
Then press on Debloat and select custom debloat list and select your txt file (File browser)
At samsung ruins, it would not be possible to include vendor.img.lz4 among the unpacked and repackaged
You also have to change things to get the better rom done
Thanks in advance
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
dr460nf1r3 said:
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
Click to expand...
Click to collapse
Thanks for the prompt answer. I didnt have a clue about that. Good to know.
Any idea why my SIM and radios got screwed up. No cellphone signal, didnt even ask for the SIM pin as if it didnt see it. The wifi didnt connect the usual network. Bluetooth kept asking me many times to confirm the connection code of my WearOs watch.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
AndroDef said:
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
Click to expand...
Click to collapse
Do you mean flashing the full stock on Odin? That would make me lose TWRP. And the idea for me of using your very nice ROM creating tool was to remain official, rooted, without having to install custom recovery again.
It worked perfectly on my tablet.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Sapiens said:
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
I finished add support for vendor partition and will release the update soon.
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
vendor.new.dat missed
Sapiens said:
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
After debloat process you can navigate to (PROJECT_FILES/DEBLOAT) and delete what you want then restore the needed items by the kitchen, However I will add manual debloat feature and currently I attached the debloat list of the kitchen.
daxiaamu said:
vendor.new.dat missed
Click to expand...
Click to collapse
Send to me a link for a firmware contents that file.
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Link for this this "Tech Karan (for his similar guide)"?
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
nsfnd said:
Link for this this "Tech Karan (for his similar guide)"?
Click to expand...
Click to collapse
You are right, sorry for forgetting this link. I have just edited the first post
nsfnd said:
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
Click to expand...
Click to collapse
Yes, I have found this bug, too. This happens because there is the same one on Poco F1 (base rom).
Also, there are some missing applications, which can be installed as normal .apk files from APKMirror:
-> Mi Browser
-> Mi Cleaner
-> Mi Scanner
They made an Android 12, MIUI 13 version for Poco F1.
I tried to do the same technic explained above for that.
But Jancox Tools failed to extract with errors.
(imgextractor.py and ext4.py, NameError: name 'xattr' is not defined)
Link for the rom.
PocoOs Stable Channel (Official)
╭━┳━┳━┳━╮╭━┳━━╮ ┃╋┃┃┃╭┫┃┃┃┃┃━━┫ ┃╭┫┃┃╰┫┃┃┃┃┣━━┃ ╰╯╰━┻━┻━╯╰━┻━━╯ MIUI 13.0.4 EU rom Based on Android 12, Code name:Ignition🔥 ======================= Maintained by @facerracer4u ======================= About PocoOs: PocoOs comes with all poco standards We do not include harmful mods, and we...
t.me
Maybe you want to check it out.
Unfortunately, we have to make a compatible vendor.img for Mi 8. Otherwise, every MIUI 13 (Android 12) ROM cannot be booted (the existing vendor files are compatible with Android 11 MIUI ROM's). I will try to port /vendor, but I am not promising anything
At least, there is a compatible kernel (No Gravity v3.x.x)
Edit: NoGravityKernel does not support /system_ext (so for most MIUI S ROM's it is not compatible)
OK, ιt's been a long time since my last post, but I have found a bootable Android 12 version of MIUI 13, but I have not managed to fix the common bugs from Pocophone F1:
<!> audio
<!> camera
<!> slow motion while watching videos (due to the audio bug)
Also, this ROM does not have NFC support (Poco F1 does not come with)
In order to install it, I have flashed:
-> the ROM (by deleting the first line in /META-INF/com/google/android/updater-script
-> permissiver v5
-> dfe (disable forced encryption)
-> XDKernel-2.6
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Advanced Gears said:
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Click to expand...
Click to collapse
Well done, That's great!!!
Hoping to see a fully working android 12 and MIUI 13 soon on our MI8
So, after replacing some audio policy files from /vendor/etc, the sound comes out normally. However, I still have bugs such as slow videos and silent sounds coming as media when earphones are not connected. Are there some files at /vendor/etc to be replaced? I haven't found anything else, yet
(Also, I haven't looked for the required files for NFC support)
OK, now it's ported with no bugs.
Missing features: NFC support (Due to my inexperience, I cannot make bootable system and vendor .img files by using image kitchens and it's more difficult to set the correct permissions to files in the /bin folders from recovery)
The files to be changed are mentioned in this uploaded .txt file
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Thanks for sharing your progress, its exciting indeed.
Is it possible for you in the future to share a simpler way for us non advanced users to easily upgrade to MIUI 13, e.g through recovery zip from TWRP.
Because I don't own these ROM's, please check some Telegram channels. The file name of this one (with the mentioned changes) may remind you something
Advanced Gears said:
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Click to expand...
Click to collapse
Hello, is this manual suitable for mi mix 3?
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Hello I am new to this, but I already have an unlocked bootloader.
Can you please confirm :-
1. Which tool I need to use to flash the ROM .img files, Xiaomi Flash Tool?
2. Which latest MIUI 13 ROM is most suitable, POCO OS •13.0.12.0 EU [ IGNITION 4.0 ].zip?
3. Which beryllium2dipper-patch.zip patch I need to use for the Mi 8?
4. Only bug is NFC right? Will audio, camera, safetynet, banking apps, xiaomi account and cloud work?
Edit:
I am not sure if the steps are correct and which beryllium2dipper-patch.zip patch file I should use
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Advanced Gears said:
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Click to expand...
Click to collapse
Thanks for the explanation, I have flashed successfully with minor tweaks.
To resume:-
Prerequisites:
1. MIUI13 Android 12 firmware (POCO OS IGNITION 2.0) feels more responsive
2. Phone ROM with unlocked bootloader and OrangeFox recovery.
3. Phone ROM must be on latest Official ROM (Global/China)
4. Phone ROM must not encypted or /data formatted
Boot to OrangeFox recovery:
1. Flash .img files; system.img, cust.img (system_ext), vendor.img, boot.img (POCO OS IGNITION 2.0)
2. Flash .zip files; DFE (disable forced encryption), latest stable beryllium2dipper-patch, permissive and XD kernel
3. Reboot phone to system and enjoy
Edit:
I have reverted back to my old ROM (xiaomi.eu MIUI12.5} as I feel its more polished and optimised but its nice to see Android 12 with MIUI13 fully working ported to the Mi 8.
tbalden's
CleanSlate kernel
for Asus ZenFone 9
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"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"
}
As always tbalden is here to bring you authentic new features first in line, this year Asus ZF9.
No root elevation (magisk) needed for all functions and preference switches through CS Config App
Release Calendar
Version 2.4.0 - 13 of Dec 2022
Version 1.4.2 - 28 of Oct 2022
Version 1.0.0 - 29 of Aug 2022
Should work on official ROM bases 32.2050.2050.x+.
Features:
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Haptic Type Tweak change haptic feedback waveform types
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass passes if using without Magisk/Rooting, flashing the boot img only, Google Pay should work
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Face down screen off - put phone face down to turn screen off
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by ASUS, 5.10.x
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Requirements
- Unlocked ZF 9, stock or with magisk root
- BACKUP: make sure you have a stock image (boot img) from asus before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion apps on your phone (both found down below in Download section). (On play store version: with Android 12 you need to join the Beta program for the correct app versions.) Set them up initially.
- Non-rooted method: 0. download the non-rooted boot img.zip, UNZIP it first!
Reboot to bootloader, and flash the images with these commands:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
.. reboot, enjoy
- Rooted method: 0. download the rooted installer zip
1. install magisk
2. use a Kernel Flasher to flash the installer zip
- For SafetyNet, Adblocking, after flashing you might need to restart the phone after the first boot, otherwise it might not work.
- For adblocking KAdaway switching on and off, you will need to Force Close browser app like Chrome to let it work in the given browser.
- For Play Integrity (with SafetyNet passing) you might need to Clean App Data in Google Play Store app to make it reevaluate Integrity
--- If you have magisk installed Play Integrity might be tripped. I only tested without Magisk, flashing CleanSlate 1.0.0 bootimage.
- If using Companion App for notification / gesture etc features, there's a setting in the app to Switch off Proximity sensor while Screen is on. This will prevent the flickering, but Face down screen off feature won't work
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
Download
Android 13
Non rooted, Android 13 images
ZF9 non rooted installer images zipped - 33.2060.2060.65 WW - CS 1.4.2: https://forum.xda-developers.com/attachments/fastboot_cleanslate_s_zf9_240_imgs-zip.5784177/
Rooted installer zip, Android 13 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 2.4.0: https://forum.xda-developers.com/attachments/cleanslate_s_zf9_240-zip.5784179/
Android 12
Non rooted, Android 12 images
ZF9 non rooted installer images zipped - 32.2050.2050.29 WW - CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Rooted installer zip, Android 12 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android 12 image
ZF9 boot image zipped - 32.2030.2030.26 WW - CS 1.0.0: https://www.androidfilehost.com/?fid=14871746926876840958
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore:
You need to join the BETA program to get the working version for the kernel!
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.2.x -- Donation premium on playstore:
You need to join the Beta program to get the working version for the kernel!
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
How to join beta program: https://forum.xda-developers.com/t/...ashlight-s2s-vib-dec-22.4281807/post-86171493
Android 12:
Companion App 3.3.9 -- Normal free download:
https://www.androidfilehost.com/?fid=15664248565197208875
Configuration App 3.2.11 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876820727
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Special thanks to AnyKernel installer developer: osm0sis
To @Freak07 for all his work on XDA and help
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
Source Code: https://github.com/tbalden/android_kernel_asus_zf9_common-kernel
Readme's and howtos
Changelogs come here later
Be aware that in Battery Saver feature, there's CURRENTLY NO CAMERA APP FOREGROUND DETECTION! Please disable this feature when you use Camera apps (otherwise slow camera, video recording)!
Hopefully camera detection can come later, as still working on more features.
nice work!
great to see you here
Great develop
Thanks for sharing! If I have the patience to get the C version when it eventually releases, I'll give this kernel a try!
- Update Android 12 Stable - 1.4.0 -
Major CleanSlate feature update
- Build and repack to QGKI2 kernel format (boot, vendor_boot, vendor_dlkm, dtbo images) with new scripts
--- Thanks go to @Freak07 for the teamwork of many hours in getting to the bottom of this crooked path to build Qualcomm's new modular kernel format and make it work on the ZenFone 9
--- Thanks go to ASUS for providing the most complete sources zip for Qualcomm based QGKI kernels up to date by ANY vendor/OEM.
--- Thanks go to @osm0sis for his AK3 installer and @capntrips for his excellent tooling in AK3 and the tips help he lended in the process of getting things rolling
- Now all features possible to implement added to drivers
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
-- Updates
-- Hosts file for KAdaway
-- Safetynet + Play integrity still passes without Magisk
-- All features work with or without Magisk (tho flashing magisk will break safetynet until you use SafetyNet fix magisk modules)
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.0 Downloads:
Rooted installer zip:
CleanSlate S 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820728
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2030.2030.26)
fastboot image zip CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820729
Cleanslate config app version 3.2.11 needed for new features:
Free version download: https://www.androidfilehost.com/?fid=14871746926876820727
Premium version: https://play.google.com/store/apps/details?id=org.cleanslate.csconfig&hl=hu&gl=US
- rolled out to playstore Beta program
Read first post in thread for installation details.
Will it run with the latest fw update?
NisseGurra said:
Will it run with the latest fw update?
Click to expand...
Click to collapse
It actually runs, but new sources are up, and I'm updating the installers soon.
- Update Android 12 Stable - 1.4.1 -
CleanSlate asus sources update
-- sources updated to 2040.23
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.1 Downloads:
Rooted installer zip:
CleanSlate S 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834460
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2040.2040.23)
fastboot image zip CS 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834462
Read first post in thread for installation details.
Installed, seems flawless
2040.28 update is up, with sources. The new sources has no changes, tested, I'm using the .23 based cs kernel without issues.
- Update Android 12 Stable - 1.4.2 -
CleanSlate asus sources update
-- sources updated to 2050.29
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.2 Downloads:
Rooted installer zip:
CleanSlate S 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2050.2050.29)
fastboot image zip CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Read first post in thread for installation details.
Is there any way to add vowifi or volte without rooting with a kernel like this?
Hello,
I recently buy this phone and wanted to increase the battery life of this phone.
This seem to be an good option, but have you information about battery life with this kernel ?
Thanks you.
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
dragonii said:
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
Click to expand...
Click to collapse
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
tbalden said:
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
Click to expand...
Click to collapse
So, according to you, I should just take the latest zip file and run the commands in fastboot mode even if I flashed already the cleanstate img file in the first post?
EDIT: did it already and no more error messages with version 1.4.2. Thanks !
Hi again,
How can I access these features? There are not showing up in the CleanSlate Configuration tool.
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
Thanks in advance,
Dr.Ketan ROM for S23 (All variants)
This is Magisk Module ROM : Here explained in details how it is different from full ROM
Full ROM for S23U (S918B) Here
Supported device : All rootable S23 variants.
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.
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 InformationS918 I Dr.Ketan ROM , ROM for the Samsung Galaxy S23 Ultra
Contributors
Dr.Ketan
ROM OS Version: Android 13
ROM Kernel: Stock (pre-rooted). Source code (samsung) here
ROM Firmware Required: Stock Samsung specified version
Version Information
Status: Stable
Created 2023-02-14
Installation and Download & Notes
Important :
- For this you needed rooted device. With rooting device
You will lose warranty
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
OTA won't work once you root device.
You can unroot device & relock bootloader by flashing stock firmware, but you can never restore tripped knox status back to 0x0. Certain knox features will not work once you have tripped knox even after re-locking BL
- 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
Installation :
Read ChangeLog post for Installation instructions (link on post #3)
Download : https://drketanrom.com/
Changelog
- T02 - 14.02.2023
- T03 - 22.02.2023
- T04 - 09.03.2023
- T06 - 05.04.2023
- T07 - 07.05.2023
- T08 - 17.06.2023
How to root & Update : Here is guide to root S23 & update rooted device
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
Here some common Q/A regarding Magisk ROM which new users want to have.
What is Magisk ROM?
Magisk ROM is small modified part of ROM which applies systemlessly. Though modification remains same as full ROM. Most of OneUI based full ROM have hardly 2-5% of modification systemwide but it integrates to system to make a full ROM. Magisk ROM also have same modification but it is systemless and use magisk overlay function. So, modification part remain same whether it is Magisk or Full ROM
Why Magisk ROM choosen over Full ROM?
Actually when S22 released, For long time there was no option to modify system because of new f2fs system ro partition type. So during this time I have choosen to make Magisk ROM so user at least have an option for all the modification which I commonly have in my all previous full ROMs. After so many users liked it so thought this to continue where there is no full ROM support I can provide due to time.
Magisk ROM doesn't have system-rw?
System-rw is complete different thing. As of now Full ROm also don't have system-rw support, in future if there is system-rw script available, Magisk ROM will work on both conditions.
Magisk ROM is made with different base from my variant
Samsung stock ROM almost have 90-98% files same in system with different variant. My Magisk ROM hardly uses any file that is different variant wise. So if you are using different base in theoretically only almost files you are using are same in all variant.
What is Debloting option?
As said earlier system-rw capabilities have nothing to do with Magisk ROM, If you wish you can make system-rw and debloat what you want. Indeed making full ROM with system-rw developer needs to struggle to remove bloatware. As system-rw needs more space compared to compressed system-ro. So making full ROM with all partition rw, you must have to remove good amount of bloatware while with Magisk ROM have complete user choice what to remove or keep.
It is difficult to update new firware compare to full ROM?
No, most of OneUI based full ROM still ask you to update to latest stock firmwre before using full ROM. Updating stock firmware also possible without even wiping data (Though must make backup for safety), Read post #4 for more details. Sort procedure is - Update firmware + keep root all in one go → Update ROM module - That's it.
Changelog have ROM installation guide. Also Magisk ROM module may work if your base is not matching. You can find more info in changelog post.
Apart from ll these queries, as a devloper Here some reasons why I prefer magisk ROM
Very easy to updte ROM. I have updated ROM as ealy as just few hrs only.
Easier Installation.
Easier Uninstallation : Didn't like ROM? simply disable modules and you are back to stock.
Support most of variant in One ROM. Also since A13, I am planning to add support for S22 (non ultra) devices too.
No feature wise limitation with magisk ROM.
What is Best way to Install magisk ROM?
Nothing special. Simply Root your device. It doesn't matter If you are using root with stock recovery or TWRP, You are using encrypted or decrypted data, using system-ro or rw. You are free to choose one suites you best. As far as you have rooted device, you can use Magisk ROM.
I prefer full ROM : Currently we are supporting full ROM with System-RW only for S908B, S908E and S908N. For other variant only option available is Magisk Module ROM
I hope these will make clear many points new users may have with Magisk ROM Module.
Regards.
ChangeLog T02 Magisk Module ROM for All s23 variant
Based on S918BXXU1AWA6 Android13 Jan 2023 security patch OneUI 5.1
It will remove some of common bloatware now. Though it won't break any major functions. Some of bloatware may be useful like gmail, maps but those you can easily install from the Playstore
ROM Tool on essential fix auto setup zygisk including SafetyNet fix & GPay Fix (no needs to change any option manually)
System Recover utility : This new feature can detect SystemUI mods malfunction (Yet no one reported though), and fix it on it's own. You just needs to wait 30-40 seconds after booting device. It will notify when fix applied and device needs reboot.
For details ROM features read below
Important Instructions for setting up ROM
Prerequisite :
Must have installed firmware S91*XXU1AWA6 S23
Rooted device with Magisk (Zygisk) Intallled
We recommend to make EFS (IMEI) backup as soon you root device and keep copy to safer place (outside device)
Warning!
We strongly recommend to make backup data before installing ROM Module, non matching verion or other factors may cause bootloop and you may needed to Factory Reset in certain circumstances. Also ROM Installer may prevent it by installing bootloop protector module but no guarantee!
ROOT & TWRP
You must have rooted S23 Ultra to use this ROM
For Root with TWRP/Without TWRP and for How to update base firmware (Dirty/Clean) read post #4
Once you have rooted device, below is guide about how to install ROM
How to Install Dr.Ketan ROM Module (New!)
Download app ROM Installar XDA S23 T*.apk and and Install as regular apk (* = ROM verion)
Uninstall any other magisk module you have installed
Open ROM Installaer app → Grant SU permission → Just seat and relax. It will auto download ROM and Install automatically. You can see process on screen. → Reboot device when asked.
Benefits of ROM Instller : This method have some extra benefits over regular installation like
It won't process if no root access found
It will block installation on wrong devices
It will abort Installation process if MD5 doesn't match (Corrupt download) to prevent bootloop.
Also it will show current firmware version and available firmware version (You should not install if there is much difference in firmware base) Read prerequisite above for recommended firware)
How to Update Dr.Ketan ROM Module (For those who are already on Dr.Ketan ROM Module older version)
Remove all magisk Module
Update new base firmware according prerequisite & Root device (read post #4 for more details)
Install Module as per said above "How to Install Dr.Ketan ROM Module"
Setting up device first time after Module installation
Open ROM Tool from app drawer and 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 (ROM Tool will offer to install this during Essential fix too)
Now you can further setup ROM a per your liking. Also MagikHide is Configure Denylist now and available under Magisk Settings.
Since A12 new Magisk (Zygisk) doesn't have buil-in Module repo, You can get standalone module manager from here (ROM Tool will offer to install this during Essential fix too) For more details and queries about new magisk ref this
Important Note for Dual active SIM users :
After Module ROM Installation, Internet/Network may not be available, Once you apply esssential Fix from ROM Tool- it will detect it and fix on it's own. Netork/Internet will be available after reboot.
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 5.1.0 or up
ROM Features (XDA Version)
- Ad Free QS Panel Toggle
- Secure Folder
- Reboot to recovery QS Panel Toggle
- Native call recorder (Manual) (call record option during in-call)
- 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.
- Option to remove carrier bloatwares
- ROM Tool with following Options
AdFree mode Enable/Disable
Long Press Home button customization
System UI Mods (custom) : Needs to Install custom SystemUI
Show/Hide stock battery
Show/Hide 3minit battery
show/hide stock clock
show/hide 3minit clock
Statusbr mods & color : see ROM Control below
SystemUI Mods (Stock Mods - QuickStar Module functions) : Works without installing custom SystemUI
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.
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 + GPay Fix New (Use only if Fix with Applying Essential fix doesn't work)
Samsung Health & Private share fix
NetFlix / Amazon Prime Fix : Needs If TWRP + Decrypted data
Access denied PopUp fix
Wavelet sound mode dump permission
Remove Customization : This will remove system customization of ROM and retain stock experience, also before using this option still you can Apply Essentail fix for sopme critical fix like SafetyNet, GPay etc. All systemless fix still remain after removing customization.
Update & Fix
Bootloader / Busybox checker
ROM Info
- ROM Control (systemUI preferences)
Battery Bar with thickness and color option + Charging Animations
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
Tips on TWRP and App Backup/Restore Read Here
Download : DrKetanROM.com
STATUS : Online
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.
Hi all, T01 Dr Ketan rom , Root explorer R/W is working for me. All good for deletion and rebooted inside data/app and user folder.
{
"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"
}
Johnny Eng said:
Hi all, T01 Dr Ketan rom , Root explorer R/W is working for me. All good for deletion and rebooted inside data/app and user folder.
Click to expand...
Click to collapse
Issue is system not data. You can edit in data partition not system
Great Idea with Magisk Modul für S23.
I use long time this one for 1+ 8 Pro
dr.ketan said:
Issue is system not data. You can edit in data partition not system
Click to expand...
Click to collapse
Noted thanks
How do you root the device beforehand?
deleted
ChangeLog T03 Magisk Module ROM for All S23 variant
Based on S918BXXU1AWBD Android13 Feb 2023 security patch OneUI 5.1
It will remove some of common bloatware now. Though it won't break any major functions. Some of bloatware may be useful like gmail, maps but those you can easily install from the Playstore
ROM Tool on essential fix auto setup zygisk including SafetyNet fix & GPay Fix (no needs to change any option manually)
PreFixed Bluetooth lost pairing after reboot.
System Recover utility : This new feature can detect SystemUI mods malfunction (Yet no one reported though), and fix it on it's own. You just needs to wait 30-40 seconds after booting device. It will notify when fix applied and device needs reboot.
For details ROM features read below
Important Instructions for setting up ROM
Prerequisite :
Must have installed firmware S91*XXU1AWBD on Samsung Galaxy S23 variant
Rooted device with Magisk (Zygisk) Intallled
We recommend to make EFS (IMEI) backup as soon you root device and keep copy to safer place (outside device)
Remove all installed Magisk Module
Warning!
We strongly recommend to make backup data before installing ROM Module, non matching verion or other factors may cause bootloop and you may needed to Factory Reset in certain circumstances. Also ROM Installer may prevent it by installing bootloop protector module but no guarantee!
ROOT & TWRP
You must have rooted S23 Ultra to use this ROM
For Root with TWRP/Without TWRP and for How to update base firmware (Dirty/Clean) read post #4
Once you have rooted device, below is guide about how to install ROM
How to Install Dr.Ketan ROM Module (New!)
Download app ROM Installar XDA S23 T*.apk and and Install as regular apk (* = ROM verion)
Uninstall all the magisk modules you have installed
Open ROM Installaer app → Grant SU permission → Just seat and relax. It will auto download ROM and Install automatically. You can see process on screen. → Reboot device when asked.
Benefits of ROM Instller : This method have some extra benefits over regular installation like
It won't process if no root access found
It will block installation on wrong devices
It will abort Installation process if MD5 doesn't match (Corrupt download) to prevent bootloop.
Also it will show current firmware version and available firmware version (You should not install if there is much difference in firmware base) Read prerequisite above for recommended firware)
How to Update Dr.Ketan ROM Module (For those who are already on Dr.Ketan ROM Module older version)
Remove all magisk Module
Update new base firmware according prerequisite & Root device (read post #4 for more details)
Install Module as per said above "How to Install Dr.Ketan ROM Module"
Setting up device first time after Module installation
Open ROM Tool from app drawer and 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 (ROM Tool will offer to install this during Essential fix too)
Now you can further setup ROM a per your liking. Also MagikHide is Configure Denylist now and available under Magisk Settings.
Since A12 new Magisk (Zygisk) doesn't have buil-in Module repo, You can get standalone module manager from here (ROM Tool will offer to install this during Essential fix too) 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 5.1.0 or up
ROM Features (XDA Version)
- Ad Free QS Panel Toggle
- Secure Folder
- Reboot to recovery QS Panel Toggle
- Native call recorder (Manual) (call record option during in-call)
- 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.
- Option to remove carrier bloatwares
- ROM Tool with following Options
AdFree mode Enable/Disable
Long Press Home button customization
System UI Mods (custom) : Needs to Install custom SystemUI
Show/Hide stock battery
Show/Hide 3minit battery
show/hide stock clock
show/hide 3minit clock
Statusbr mods & color : see ROM Control below
SystemUI Mods (Stock Mods - QuickStar Module functions) : Works without installing custom SystemUI
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.
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 + GPay Fix New (Use only if Fix with Applying Essential fix doesn't work)
Samsung Health & Private share fix
NetFlix / Amazon Prime Fix : Needs If TWRP + Decrypted data
Access denied PopUp fix
Wavelet sound mode dump permission
Remove Customization : This will remove system customization of ROM and retain stock experience, also before using this option still you can Apply Essentail fix for sopme critical fix like SafetyNet, GPay etc. All systemless fix still remain after removing customization.
Update & Fix
Bootloader / Busybox checker
ROM Info
- ROM Control (systemUI preferences)
Battery Bar with thickness and color option + Charging Animations
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
Tips on TWRP and App Backup/Restore Read Here
Download : DrKetanROM.com
STATUS : Online
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.
T03 Magisk Module ROM is now online for S918* XXU1AWBD firmware
.
dr.ketan said:
T03 Magisk Module ROM is now online for S918* XXU1AWBD firmware
.
Click to expand...
Click to collapse
Is thie T03 a full ROM or just a module to be installed with Magisk?
Do you know when "TweaksPro" will be available?
Many Thanks in advance
Famcon said:
Is thie T03 a full ROM or just a module to be installed with Magisk?
Do you know when "TweaksPro" will be available?
Many Thanks in advance
Click to expand...
Click to collapse
This thread is for magisk module only
There is separate thread available for full rom. Full rom support available only for S23 ultra
TweaksPro available available already
dr.ketan said:
This thread is for magisk module only
There is separate thread available for full rom. Full rom support available only for S23 ultra
TweaksPro available available already
Click to expand...
Click to collapse
Thanks for the prompt reply Dr.Ketan.
on the site there is no mencion that is working with S23 Ultra, see below
Famcon said:
Thanks for the prompt reply Dr.Ketan.
on the site there is no mencion that is working with S23 Ultra, see below
Click to expand...
Click to collapse
Forget to update. Check ROMs - S23 page
dr.ketan said:
Forget to update. Check ROMs - S23 page
Click to expand...
Click to collapse
TOP! My Ultra will be arriving any time now, then I'll try Root and module T03. I'm still not sure if Tweaks is a Magisks Module of fill ROM. If kust a Module then I would buy it instead of T03. In that casa, is there a uncomplicated way via paypal to send the money to get tweaks?
Sorry for such basic question, but its all a bit new. KR, fc