Related
@mouse723 signaled that first Lineage OS rom for X2 has been released:
ROM Name:
Huawei X2 GEM-703L LineageOS 13
ROM Size:
873 MB (916,101,856 bytes)
Adapted version:
Android6.x
Author brief introduction:
Piaooop
Release Date:
2017.09.12
Download Links:
ROM : pan.baidu.com/s/1qXY5GfE
Gapps: http://opengapps.org/ (choose ARMVA &Android 6.0, prefer pico apps)
Installation requirements:
1 your device must have any android 6 rom installed already
2 twrp recovery must be installed
Installation:
1 restart device into twrp recovery mode
2 make a backup of your firmware
3 wipe data/factory reset
4 Install Piaooop X2 lineageOS 13.zip
5 if you need google apps and google services install the desired gapps pack .zip file
6 if you want root access, install SuperSU.zip from here
Not Working: (thanks to @ajsmsg78 for first test)
- Data does not work (No SIM and no sim settings at all)
- Camera's zoom
- Double tap
- no smart-cover detection
Other possible issues:
- if you face too much battery comsuption, try greenify
- colors mismatch in camera
I flashed that ROM already don't even waste your time nothing works
I tested that rom. Don't waste your time, sim cards don't work and the camera bugs are still there.
The rom zip is also password protected so I can't take it apart and fix it. I don't know why these Chinese devs insist on password protecting an Android rom and never providing a file_contexts file to make it possible to extract and rebuild. They port roms and then make it impossible for anyone else to try and fix them. They can fix this one themselves, I want no part of it.
Thread closed - the ROM is effectively closed source, so no place for it on XDA.
[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "CORAL" Magisk/Stock Boot Images
**Huge thanks to @murphyjasonc for sharing the pre-patched boot image, and @sidhaarthm for testing this method and his detailed notes!**
PLEASE READ ALL ADDITIONAL NOTES IN THE FIRST 3 POSTS. THIS IS A MAJOR UPDATE TO A NEW VERSION OF ANDROID AND CONSEQUENTLY COMES WITH A MUCH HIGHER RISK OF BOOTLOOPING IF YOU'RE NOT CAREFUL. I PERSONALLY AM WAITING TO UPDATE TO ANDROID R (WAITING ON GRAVITYBOX GOODNESS) SO I WON'T BE ABLE TO HELP AS MUCH - PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! =)
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.200720.009, Sep 2020, All carriers except IN"!
Magisk Canary v20424 (11f254e5) Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933259
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933258
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682933260
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
READ THIS ENTIRE POST BEFORE PROCEEDING!
ADDITIONAL PRELIMINARY STEPS COMPARED TO PREVIOUS MONTHS - DO NOT SKIP!!!!:
A. Make sure all of your Magisk / EdXposed modules are updated for compatibility with R. For example:
* Magisk Module: Riru (Riru - Core) v21.3
* Magisk Module / EdXposed version: EdXposed v.0.5.0.6-android_r (4561) [this is a Canary build]
B. Recommend disabling any Magisk and/or Xposed modules that have not been tested with Android R.
C. Install latest Magisk Manager Canary build: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
D. Regular reboot the phone to make sure updates are applied before proceeding with the rest of the update process.
---------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200805.001, Aug 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq3a.200805.001-factory-dtbo.img: https://androidfilehost.com/?fid=8889791610682906527
coral-qq3a.200805.001-factory-boot.img: https://androidfilehost.com/?fid=8889791610682906525
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.200720.009-b447daff.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq3a.200805.001-factory-boot.img
3. fastboot flash dtbo coral-qq3a.200805.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.200720.009-b447daff.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.200720.009-magisk_patched-c20424.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
---------------------------
ADDITIONAL NOTES FROM @sidhaarthm, WHO TESTED FOR ME - THERE'S SOME GOOD INFO HERE TO HELP PREP YOU BEFORE UPDATING YOUR PHONE:
Okay, so I just successfully completed the steps and I'm booted into Android 11 without issues.
Here are my observations, notes and findings:
Pre-requisites:
- I installed the Canary Build of Magisk apk - it basically overwrote the existing installation of Magisk and worked straight away. I remained on the 'stable' update channel.
- I uninstalled all the Accent and Colour Mods from Tulsadiver as he is yet to update the mods for R11 (although he's confirmed its' possible and will publish it soon).
- I also deleted the AK3 Helper module from Magisk that gets flashed with Kirisakura Kernel since I was about to to flash the stock kernel anyway.
- I left the GPay SQlite Fix, Systemless Hosts, Busybox, V4A and AML Modules in Magisk enabled and as is.
Upgrade Notes:
- Followed your instructions to the T and the upgrade process was a breeze.
- I did extract the boot file from the factory ROM and patched it in Canary Magisk myself on my P4XL, but I chickened out at the last minute and flashed the boot file you had provided anyway. Reason being the flashed boot IMG I generated was 33,292 KB vs the one you had provided (and the ones I saw posted in other threads) were all 33,332 KB. So there was definitely some differences there and I just didn't want to risk it at that point.
- The phone got a bit hot during the upgrade process - around 40C+ but I suppose that's alright. Its' cooled down now and running okay.
- I did not flash any Kernel yet since I am waiting for the next official Kirisakura Kernel release for R11.
Findings:
- My P4XL booted first time, no bootloops etc - finalised the upgrade in a couple of minutes and everything thereafter seems smooth as butter.
- GPay works perfect without any tinkering (that's a big plus!)
- Device is rooted and all Root apps (AdAway, TiB etc), all work as normal. Camera, WiFi, Bluetooth, everything works, no issues whatsoever.
- Face Unlock works as normal and so do all the apps that use the biometric API to unlock (banking apps etc).
- SafetyNet fails on ctsProfile (evalType Hardware) but it was the same before upgrading to R11, so not surprised.
- Viper FX doesn't work post upgrading to R11 - that's expected and people have already reported the same 'failed at patching system' error on the main thread. Hopefully we get an upgrade at some point. Really gutted about this one as I love V4A!
Click to expand...
Click to collapse
Big thanks to @sidhaarthm for being an awesome and detailed tester!
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
* Looks like Tulsadiver uploaded a boot image for A11, although it hasn't been tested yet: https://forum.xda-developers.com/showpost.php?p=83462451&postcount=150
Coming from an earlier build than August 2020?
Download the September 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
Since this is a major jump to a new version of Android, I don't want to recommend this yet until someone tests it. If anybody tries this way successfully, please let me know so we can update this part. Thanks!
I just updated from Android 10 August (I use your method since, what, April now?) and everything worked without a problem. For security purposes I deactivated Edxposed beforehand, though. The first booting takes a while after the updating, maybe 3-4 minutes, don't be afraid to wait. I was. Lol.
Edit: Jea, Android4Viper is broken. Needs fix asap
Also a big thanks from me, all went well! A little reminder for people running lawnchair & quickswitch: disable both and set stock recent provider to pixel launcher! Both are not compatible yet... Almost had to factory reset because of this ?
An other big thanks from me, I used your guide again and everything is working.
I used Magisk from the Canary channel and installed MagiskHide Props Config.
Safetynet : Basicintegrity V, ctsProfile V and evalType BASIC., this is good.
When the Kirisakura Kernel is available I will install this kernel for Android 11.
when you install latest Magisk Manager Canary build, is this supposed to overwrite the current stable build or ad an additional separate magisk app?
has anyone installed riru and edxposed (if so what version you using) after root from a fresh update (Full wipe update, root, then install modules) any issues?
***EDIT (for dummies like me)*** can confirm works via fresh install too
-Just download / install riru core 21.3 via magisk.
-Download latest edXposed manager v4.5.7.
-Download v0.5.0.6 4561 from canary tab in edXposed manager.
-Flash that zip in magisk.
-Just make sure you don't flash and exposed directly from the download module list in magisk those are not the canary builds. You have to flash the zip from internal storage you just downloaded.
So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?
bigmatt503 said:
So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img --slot all
Homeboy76 said:
fastboot flash boot magisk_patched.img --slot all
Click to expand...
Click to collapse
Thanks for the help. I got working by flashing "_a" after img
bigmatt503 said:
Thanks for the help. I got working by flashing "_a" after img
Click to expand...
Click to collapse
No problem, glad you found a solution to the problem. :good:
Ok, the first time I did this, it didn't change anything(after I finished I was still on Android 10, with the August update), so I may have did something wrong, I'm not sure. Anyway, I did it a second time, and voila, it works. Your guides are always the best bro!
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Not able to boot after flashing the patched img says no valid slot to boot
bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
Google Pay works - I utilised the GPay SQlite fix method (look it up, plenty of threads on it) but I actually had that before I upgraded to R11. Once I successfully upgraded using the steps provided in this thread, I didn't have to do a thing and GPay still works
As for banking apps, depends where you are. I'm in the UK and with Magisk Hide and some trickery, I've manged to get Monzo, Starling, Amex, HSBC and Tesco Banking apps to work on my Pixel 4 XL. The only ones I seem to struggle with (that have strong root detection) are Barclaycard and Lloyds Banking Group apps such as Halifax, MBNA etc.
Hope that helps :good:
bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
I'm in the USA and G-pay works without doing anything. All of my banking /credit card apps work too
Has anyone had SafetyNet randomly stop passing for both basicIntegrity and ctsProfile together? When I first upgraded to 11 and set everything up, I was able to pass even with EdXposed installed, then it stopped passing with EdXposed a few days later, but would pass both with it disabled. Now it won't pass at all even with EdXposed disabled.
Anyone have any ideas before I resort to wiping and starting over?
has anybody with android 11 and magisk able to use smali patcher or app systemizer? i cannot get either to work yet
This guide worked perfectly for me, cheers.
Just need to wait for YouTube vanced
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
Important information:
This thread is for LineageOS 19.1 opensource builds for Mi 4C/4S. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Permissive
Data Usage
Encryption
VoLTE (may fix)
Installation:
If you are on the stock OS, you will first need to unlock, then you need a custom recovery. You can get the recommended TWRP here.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on libra
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
AndroidFileHost
Changelog:
Changes for libra
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to Tipz Team
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@WJXXBSH, @TipzRickyCheung, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required:
Based On: LineageOS
Reserved
Nice... Longlast libra....
New Update!
20220518
Changelog:
Fixed DT2W
Added support for Dirac audio enhancement
Added support for Ambient Display
Added support for Edge Tap
Improved power consumption estimation
Download
If I only write to the system and gapps, then I can boot normally.
If magisk are written, the system cannot be boot on and restarts in a loop.
Correctly installed Rom Lineage 19 and MindTheGapps in xiaWRomi MI4C with 2Gb of storage. I have the TWRP Orange-Fox and the F2FS partition, I formatted the data and did a zip installation lineage-19.1-20220518-UNOFFICIAL-libra, deleted in system/system/fonts Notosans CJK in case there was not enough space to install MindTheGapps-12.1 .0-arm64-20220416_174313.zip.
Everything worked fine, after setting up the Google account.
Don't install Magics, because someone said it was incompatible.
If I find any error, I'll tell you about it. Thank you very much
Edit:I just installed Magisk v25.0 working perfectly.
Edit: After using it for two days with internet, Sygic, Google Maps, iGo and it works fine. The problems that I detect are: some unexpected restart, some delay on the unlock screen. The GPS connection is not precise, but it was already with the previous ROMs and the battery is fine.
Thank you very much for keeping MI 4c alive
thanks a lot
Hi @tipzrickycheung,
Thank you for the ROM.
I use Mi4c, 3GB RAM. I flashed recommended Firmware before I clean flash your ROM. What I've noticed is that the phone is getting quite hot when not much loaded. Also there are issues with Bluthooth. It happens each time I connect to Hi-Fi system and then I can't do much on the phone, it freezes. I have to restart it.
lousido said:
Correctly installed Rom Lineage 19 and MindTheGapps in xiaWRomi MI4C with 2Gb of storage. I have the TWRP Orange-Fox and the F2FS partition, I formatted the data and did a zip installation lineage-19.1-20220518-UNOFFICIAL-libra, deleted in system/system/fonts Notosans CJK in case there was not enough space to install MindTheGapps-12.1 .0-arm64-20220416_174313.zip.
Everything worked fine, after setting up the Google account.
Don't install Magics, because someone said it was incompatible.
If I find any error, I'll tell you about it. Thank you very much
Edit:I just installed Magisk v25.0 working perfectly.
Edit: After using it for two days with internet, Sygic, Google Maps, iGo and it works fine. The problems that I detect are: some unexpected restart, some delay on the unlock screen. The GPS connection is not precise, but it was already with the previous ROMs and the battery is fine.
Thank you very much for keeping MI 4c alive
Click to expand...
Click to collapse
Hi,
can you please help me with some installation instructions step by step?
I have downloaded everything and i prepared but i don't want to miss any essential step.
Thank you for your help.
AngelTudorache said:
Hi,
can you please help me with some installation instructions step by step?
I have downloaded everything and i prepared but i don't want to miss any essential step.
Thank you for your help.
Click to expand...
Click to collapse
I am not an expert to make a tutorial, my way of proceeding is: trial and error.
The process is the same that we use to install other previous ROMs.
My experiments are always with a device that I don't need, so if it doesn't work the first time, I try again ?????
If you have any specific problem, you can comment on it and we will try to find a solution.
Cheer up and good luck
Now i have TWRP installed and MIUI 9.5.2.0 (NXKCNFA) running on my device.
What should be the next step? To boot into TWRP and wipe the phone? Than i should copy the LineageOS 19.1 on the phone?
In this link you have instructions on how to do it.
Luck
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com
In this link you have instructions on how to do it.
Luck
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com
Do anybody know where to post kernel related questions? I've just got to the point of building the nethunter kernel tree for libra, but I can not boot the anykernel it generates. I know I'm missing parameters, but nethunter documentation is not helping, at all...
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock bootloader
Boot into download mode
Flash recovery using heimdall or odin
Boot into recovery right as it finishes flashing
Flash ROM using adb sideload path_to_ROM.zip command
Optionally flash GAPPS the same way you flashed ROM
Format data in recovery
Reboot to system.
Downloads:
RECOVERY
ROM
GAPPS
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Credits
Doomer231
A2L5E0X1
DeHuMaNiZeD
Linux4
Device tree and kernel source code:
R8S-OSS
Issues:
voLTE[wont fix, unless any samsung gets voLTE fixed]
fingerprint scanner might not work
overlays might need some tweaking
no encryption
permissive SELinux
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
BraskOviedo said:
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
Click to expand...
Click to collapse
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Thank you for the ROM and the quick answer, if I can help out with something please let me know, thank you.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Forgot to ask, is there an ETA? Is it LineageOS 20? Thank you
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
It´s the October 2022 patch
Doomvrr said:
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Click to expand...
Click to collapse
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Agreed.
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
All-In-One said:
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
Click to expand...
Click to collapse
Imho and experience this nearly always down to the Xposed modules not xposed itself. I have been using xposed since my Galaxy S and its been reliable and solid enough that after 10 Samsung devices later (S, S2, S4, S5, Note5, S6, S7, S7edge, Note9, S20FE) I will always install it. And the Xposed modules I run ar XpirvacyLua, Firefds kit [Q], GravityBox [Q] which are then Managed by EdXposed. I tend not to update the modules unless there is a specific issue that an update will fix.
Nope, check the twrp thread i the section we are upto 3.7.x which supports Android 12 (and should support 13 due to it being an incrmental update on 12).
Thats a fair comment.
Hello, is there a possibility to release this also for snapdragon?