Related
What is this?
This mod removes the persistent "Device is HD capable" Notification that appears on many custom roms
Applicability?
This mod is meant for Yu Yureka Plus running Resurrection Remix Rom 5.8.0 Official Build. For other devices, keep reading...
How does it do it?
The culprit package that causes this notification to appear in the status bar is ims.apk - located at /system/vendor/app/ims
This mod replaces that file with a modded one. More on that below...
Instruction of use
1) Download file - NR_yurekaRR580o.zip
2) Reboot phone into TRWP recovery
3) Mount > System partition
4) Install > NR_yurekaRR580o.zip file
5) Reboot
Downloads
1) Notification remover - NR_yurekaRR580o.zip
2) To re-enable this notification again, flash this file - NEN_yurekaRR580o.zip
-------------------
FOR OTHER DEVICES
This mod was made using the ims.apk file extracted out of Resurrection remix rom 5.8.0 official build meant for the yureka plus phone. So whether this mod will work on other phones cannot be answered. But if you want to create this mod for your phone, here are some quick lessons:
1) Find ims.apk file in your phone and extract it to PC
Try looking for it in /system/vendor/app/ims
2) Use apktool and do these edits in ims.apk
Decompile ims.apk
In ims.apk>res>values>bools.xml
Change value of config_update_service_status to True
In ims.apk>res>values>strings.xml
Delete value of device_is_hd_capable
In ims.apk>res>values-mcc** (inside dozen or so folders) > bools.xml
Change all values of config_update_service_status to False
Re-compile ims.apk and give necessary signs. And use it any flashable zip
Credits:
This mod is based on KabirKalsi's similar mod found here that he made for the redmi 3. All credits to him.
Will this works in RR Official March build??
Sent from my YU5510 using Tapatalk
Thanks for help. That notification was irritating me since I flashed voLTE firmware. Followed modification steps mentioned above.
PFA, apk file which worked for me on Yu Yureka RR v5.8.2.
Device Model: Yu Yureka AO5510
OS: RR-N-v5.8.2-20170307-tomato-unofficial
Flashed: voLTE firmware.
Android 7.1.1 (Resurrection Remix Nougat 7.1.1_r25 - NOF27B)
Steps to install:
make an adb connection to pc.
1. adb reboot recovery
2. adb push ims.apk /system/vendor/app/ims/
-- expected output -> [100%] /system/vendor/app/ims/ims.apk
3. adb reboot.
Done.
Download link. (remove the spaces)
http :// s000.tinyupload.com /index.php ? file_id = 37766304712524729237
Credits
@broadways
Worked perfectly fine on Moto G4 plus running Ressurection Remix.
If it remove hd sign...then is it add the volte icon??
Sent from my YU5510 using Tapatalk
Worked like a charm
Thanks man! It was really helpful and I used APK Editor to edit the values. Thanks a lot again. Cheers!
thanks for your help,I moved HD capable by this artcle.
Dolby atom for android
Download "Dolby atom.zip" flash via recovery
Link Is Bellow
https://drive.google.com/file/d/0BxyNK0IHexvkLVRkRUQ4UWFsdk0/view?usp=docslist_api
Mirror linkhttps://drive.google.com/file/d/0BxyNK0IHexvkLVRkRUQ4UWFsdk0/view?usp=docslist_api
1) Reboot into recovery
2) install this zip file wherever save in your directory and flash
3) Wipe dalvik and cache
Now reboot your device.
.....And enjoy it music
Viper4androidfinally work for sm j710 for better music experiance.
Downlod link bellow.
https://drive.google.com/file/d/0BxyNK0IHexvkR3E2UkVnR055UHM/view?usp=docslist_api
And
Mirror link VIPER4ANDROID
Download and install.
This steps for samsung variant devices all other chinies just install and open.. may be work fine
1) Download selinux mode changer APK from Google and install. Grant super user access and change the Linux mode imforcing to permissive.
2) open root explorer open system/build.prop file and put there bellow line in the end of the page for work v4a properly.
3) download universal unit d suport.apk then tap on button.
Copy this and paste in build prop fIle
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
And save it.
4) Install v4a 2.5.0.5 this app r u downloaded and open.
install driver and reboot device.. ..
Working in the j700M??
Enviado de meu SM-J700M usando Tapatalk
I think so work on all model but plz make a backup of all rom via recovery
Hi, this is a simple fix to make the camera working in gsi like Resurrection Remix. I have this problem only with this gsi.
In phone with a root explorer go to:
- /system
-open build prop, scroll down and mod this line like this:
-if you don't have add: persist.camera.HAL3.enabled=1
Boot to twrp, and flash this:
-Permissiver v2
If using Gcam, don't use Hdr+ Advanced
Profit. :good:
Carrier phones are odd-ball siblings of their global counterparts. As such, they do not enjoy nor receive the same level of support as that of the latter in the modding scene (custom ROMs, recoveries, etc.), even though both carry the same brand model name, e.g. Xperia XZ1 G8341 "Global" vs. Xperia XZ1 SO-01K "NTT DoCoMo". This is because of the subtle underlying hardware differences between the global and carrier variants, even if they have the same specsheet.
One can try flashing ROMs for a global variant onto one of these phones, but it can be a hit or miss, with some hardware components not working like NFC and even losing other functions like the fullseg receiver. And even if it seems to run fine, there may be other issues like poor battery performance because of a non-functioning hardware preventing deep sleep.
Given the above, if you're like me who has one of these carrier phones and doesn't mind running stock where everything works, then this guide is for you. This will allow you to customize several aspects of the system as indicated per section.
This guide has been made possible with the great work of @j4nn on his temproot exploit via CVE-2019-2215 here, extended to support carrier phones from NTT DoCoMo, au KDDI, and Softbank. Once you achieve temporary privilege escalation by running bindershell, you can execute the following commands from inside a terminal emulator (if you followed the howto from the link) or the adb shell. There is no need to setup Magisk. All changes are permanent, except for those in /data that will be erased upon factory reset.
Keep in mind the following:
1. Customizations in this guide were done on an Xperia XZ1 SO-01K from NTT DoCoMo. I think that the file system from the other carriers shouldn't differ that much, but let me know if there are any discrepancies and I'll see if I can help.
2. Make backup of the files if you wish to revert them later on.
3. Avoid making changes in files and/or directories other than those as detailed in this guide, specifically in /oem and /data.
4. The starting directory for files to be copied is assumed to be at /sdcard, i.e. the root directory of the internal storage.
5. Always remount as read-write before committing the changes in /oem:
Code:
# mount -o rw,remount /oem
6. Restart the phone for changes to take effect.
{
"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"
}
Let's get started.
• Boot animation
Shave off a few seconds of boot-up time by removing the boot animation, or you can replace this to whatever you want (you'll have to make sure that the boot animation is in compatible format with the phone). To remove:
Code:
# cd /oem/media
# rm bootanimation.zip
# touch bootanimation.zip
# chmod 644 bootanimation.zip
It is not enough that you delete the file, because then the system will load /system/media/bootanimation.zip. You need to create a zero-byte file with the proper permissions.
• Boot logo
I found an empty splash partition that is 32.64 MiB in size. I'm still trying to figure out if flashing a compatible boot splash image to this partition will make the bootloader load this image instead of the one built into it, just like in the case of the boot animation above. I still have to determine the compatible format for this splash image.
If you have further information regarding the format please share it here. I'm also trying to change the blinding light of that boot logo to something more tolerable.
• Emoji font
Fast fact: Did you know that emoji comes from the Japanese words 'e' meaning picture and 'moji' meaning character?
To replace (assuming you have a font file named MyFont.ttf):
Code:
# cd /oem/fonts
# rm ColorUniEmoji.ttf DcmColorIEmoji.ttf
# cp /sdcard/MyFont.ttf ColorUniEmoji.ttf
# chmod 644 ColorUniEmoji.ttf
The two ttf files are referenced in /system/etc/fonts.xml, but it is the ColorUniEmoji.ttf file that needs to be replaced to make changes to the system emoji. Removing this file will only defer the system to load all glyphs from /system/fonts/NotoColorEmoji.ttf, so rename your font file accordingly.
• Display font
To have your own font apart from the choices in Settings > Display > Change font for display (assuming you have a font file named MyFont.ttf):
Code:
# cp /sdcard/MyFont.ttf /data/system/fonts/UserFont.ttf
• Installing apps into /system
You can achieve the same effect of installing apps into /system (without triggering the 'Your device is corrupt' boot message) as follows (assuming you have an app named MyApp.apk):
Code:
# cd /oem/app
# mkdir MyApp
# chmod 755 MyApp
# cp /sdcard/MyApp.apk MyApp/
# chmod 644 MyApp/MyApp.apk
Replace /oem/app with /oem/priv-app as needed.
• Debloat
Effortlessly debloat your phone from carrier-specific apps and services by making modifications in /oem/android-config/early_config.xml. The package names contained in the xml file will disappear from the system upon restart. A factory reset will not even bring those packages back. You can remove the package names should you decide to have the need for them. Restart the phone and they will appear again.
Here's mine configured with the bare-minimum packages to avoid bootloops and other issues. You can change it to suit your needs, just follow the file structure. I purposefully didn't indent the lines I added to easily see them.
You can also rename or delete the folder /oem/deletable-app if you don't want to have those apps contained therein to be installed by the system upon a factory reset.
Note for SO-01K:
Do not include the com.nttdocomo.android.phonemotion package if you use the stock phone dialer com.sonymobile.android.dialer. The dialer will crash whenever you receive an incoming call, preventing you from answering it.
• GPS
UPDATE: The GPS doesn't work no matter what parameters are changed in the gps.conf file. It doesn't detect any satellites, so it doesn't lock-in on your coordinates, at least this is the case with mine. This may be another limitation of using a carrier-locked phone outside of it's country of origin. I'm afraid that the only remedy for this would be to flash a global ROM variant, especially if binaries are involved. I know this to be the case because I have an SOV37 on Japan ROM and no GPS work there also, but after flashing it to a Global ROM then I got GPS to work properly.
I'm still trying to find out how to fix this without unlocking the bootloader, but I'm not holding my breath.
Tweak the GPS parameters of the phone in /oem/android-config/gps.conf.
• Preset networks
Remove /oem/android-config/preset_networks.conf if you don't want to have carrier saved networks present whenever you reset your network settings or factory reset.
• APNs
I have always wondered why carrier phones don't automatically populate the APN for any SIM other than a Japanese SIM, even after having the phone SIM unlocked. As it turns out, the system of these phones doesn't really include the APN parameters of other networks outside Japan.
/system/etc/apns-conf.xml, which is where all APN parameters for all networks of the World can be found, is a symlink to /data/customization/apns-conf.xml, which itself is another symlink to /system/etc/customization/settings/defaults/apns-conf.xml, which is an xml file containing zero APN parameters.
As you can see, we can change this by replacing the symlink in /data/customization/apns-conf.xml with the full xml file from Google's source repository found here. This will download a file named apns-conf-full.txt. This is base64 encoded. To decode:
Code:
$ base64 -d /sdcard/Download/apns-conf-full.txt > /sdcard/apns-conf.xml
Unfortunately, upon every restart the system reverts /data/customization/apns-conf.xml to the original symlink. To prevent this, we need to make the file immutable with chattr, but this command is not available in the system.
If you followed the howto from the temproot link, and ran bindershell from a terminal emulator, you will come across the post of @Tifs detailing on how to successfully start Magisk from the same. You just need to download the arm64/busybox binary from one of the posted links.
When you have this and the xml files ready, then:
Code:
# cd /data/local/tmp
# cp /sdcard/Download/busybox .
# chmod +x busybox
# cd /data/customization
# rm apns-conf.xml
# cp /sdcard/apns-conf.xml .
# chmod 644 apns-conf.xml
# /data/local/tmp/busybox chattr +i apns-conf.xml
After restarting the phone, try Settings > Network & Internet > Mobile network > Access point names > Reset to default and see the available APNs for your SIM.
• VoWiFi / Wi-Fi calling
These carrier phones came provisioned with VoLTE and Video Calling but not Wi-Fi calling, at least in the case of mine. I'm not sure how useful Video Calling would be outside Japan, and it seems that Wi-Fi Calling is not used there. @pbarrette provided a great overview of the configs that enable VoLTE and Wi-Fi Calling here. But we are interested in enabling Wi-Fi Calling so here are the relevant changes to make:
1. Decompile /oem/overlay/com.android.carrierconfig-res-305.apk on your phone or PC.
2. Once decompiled, modify res/xml/vendor.xml with the following values as follows:
Code:
<boolean name="carrier_wfc_ims_available_bool" value="true" />
<boolean name="carrier_default_wfc_ims_enabled_bool" value="true" />
3. Rebuild the decompiled apk and overwrite the original file with the modified one.
4. Append the following line to /oem/system-properties/config.prop:
Code:
persist.data.iwlan.enable=true
5. It may be necessary to change/reinsert SIM after phone restart for the changes to take place.
• Build.prop
It is not possible to add or modify values in /system/build.prop without triggering the 'Your device is corrupt' boot message. However, you can add or modify certain values in /oem/system-properties/config.prop, which gets read into the system property database.
If you are using Gboard and you want custom themes for it, then you can append these lines for example:
Code:
ro.com.google.ime.themes_dir=/oem/etc/gboard_theme
ro.com.google.ime.theme_file=swiftinstaller.zip
Edit the values as needed.
Here are the other interesting values to modify:
Code:
# show the NFC icon
ro.nfc.icon.enable=true
# disable the forced camera shutter sound
ro.camera.sound.forced=0
It may also be necessary to decompile /oem/overlay/android-res-305.apk, then modify res/values/bools.xml as follows:
Code:
<bool name="config_camera_sound_forced">false</bool>
to turn off the forced camera shutter sound. I did both modifications, but try the config.prop value first. It may be enough.
* VoLTE / 4G calling
There should be a matching APN entry to use VoLTE with your network operator. Unfortunately, this is missing as well, and if you try to add it manually in Settings > Network & Internet > Mobile network > Access point names, it doesn't get saved. This is the case with mine.
UPDATE: I just acquired an Xperia XZ2 SOV37 "au KDDI" running Android 10. When I tried adding an APN of type 'ims' there, I got an 'Operator does not allow adding APNs of type dun, ims.' So it is a carrier-imposed restriction on the phone, only that in my XZ1 it fails silently.
You can add the APN entry in two locations:
1. /data/customization/apns-conf.xml, but you can only do this before making the file immutable; or
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
In both cases, this is the APN entry you need to add:
Code:
<apn carrier="IMS" apn="ims" mcc="{mcc}" mnc="{mnc}" type="ims" protocol="IPV4V6" roaming_protocol="IP" />
Replace the values in curly braces with the MCC and MNC of your network operator.
* CellBroadcastReceiver
Each carrier phone comes with their own way of receiving emergency alerts depending on the network operator. All of them however don't include the CellBroadcastReceiver app like the other models do.
If you want to receive such alerts, then download this apk here. Rename it as CellBroadcastReceiver.apk then do the following:
Code:
# cd /oem/priv-app
# mkdir CellBroadcastReceiver
# chmod 755 CellBroadcastReceiver
# cd CellBroadcastReceiver
# cp /sdcard/CellBroadcastReceiver.apk .
# chmod 644 CellBroadcastReceiver.apk
* Sound enhancement
Sound enhancements like the DSEE HX, ClearAudio+, etc. apply only on stock media players like the Music and Video player (but not on any other else it seems) in the case of Android 8.0 Oreo. On Android 9.0 Pie, these enhancements apply system-wide for all media playing apps. An upgrade is recommended if this customization is needed.
While customizations such as these may not come close to the level you get with custom ROMs (and the updated software and security that come with it), these will at least give you something to control and tweak AND STILL get a device with a locked bootloader (and all the goodies that come with it like passing SafetyNet and Key Attestations, Widevine L1, intact DRM keys, etc.). You get the best of both worlds, at the cost of running a not-so-updated system.
I will add more sections to this as soon as I made some more modifications. I hope you find this guide useful as much as I enjoyed creating it. If you do, please hit the LIKE button. It will be very much appreciated.
Changelog
* 2021-08-02: initial posting, revised with images
* 2021-08-03: added section on VoLTE
* 2021-08-04: updated VoLTE, added section on CellBroadcastReceiver
* 2021-08-11: updated GPS
* 2021-08-14: added section on Sound enhancement
braveheartleo said:
* VoLTE / 4G calling
There should be a matching APN entry to use VoLTE with your network operator. Unfortunately, this is missing as well, and if you try to add it manually in Settings > Network & Internet > Mobile network > Access point names, it doesn't get saved. This is the case with mine.
UPDATE: I just acquired an Xperia XZ2 SOV37 "au KDDI" running Android 10. When I tried adding an APN of type 'ims' there, I got an 'Operator does not allow adding APNs of type dun, ims.' So it is a carrier-imposed restriction on the phone, only that in my XZ1 it fails silently.
You can add the APN entry in two locations:
1. /data/customization/apns-conf.xml, but you can only do this before making the file immutable; or
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
In both cases, this is the APN entry you need to add:
Code:
<apn carrier="IMS" apn="ims" mcc="{mcc}" mnc="{mnc}" type="ims" protocol="IPV4V6" roaming_protocol="IP" />
Replace the values in curly braces with the MCC and MNC of your network operator.
Click to expand...
Click to collapse
braveheartleo
Thanks a lot for such a helpful post.
I have a SO-02K XZ2 Compact docomo, running android 9.0, unlocked bootloader, rooted.
I could not find file "apns-conf.xml" on "/system/etc/".
After rebuilding "android-res-305.apk" ... each time i tried to manually add APN (through Newtrok & internet > Mobile network > Advanced > Access Point Names) i end up with no APNs.
what could be wrong?
shamllakh said:
After rebuilding "android-res-305.apk" ... each time i tried to manually add APN (through Newtrok & internet > Mobile network > Advanced > Access Point Names) i end up with no APNs.
Click to expand...
Click to collapse
Hi, sorry for the very late reply, I must have missed the notification for this one.
If you read my post carefully, then you would have already gotten the answer to your question.
I'm not sure what you did after rebuilding the file, but if you followed my post correctly then you wouldn't have the need to manually add an APN entry for VoLTE, which doesn't get saved.
@braveheartleo regarding 4g/volte I tried to modify the apns-conf.xml. I managed to have ims registered but for some reason, after a while it reverts back to not registered even though i made it immutable. I would like to try the other way by decompiling android resapk but I don't know how to. Do you mind sharing a basic guide and the pre requisites. I tried recompiling in windows using apktool and I don't know if I'm doing it right, I didn't see any res folder after inside. I tried the apk tool on the go but I'm not lucky to have it installed, I think the development of the app has stopped years ago. I have sov36 so I am also thinking maybe it's deferent on how you do it compare to softbank?
braveheartleo said:
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
Click to expand...
Click to collapse
@braveheartleo I managed to decompile android-res-305.apk but there is no res folder or apns.xml on it for sov36 au. I tried to look onto the same apk for s0-01k and it is present. I guess docomo build their firmware a bit different than kddi au. I tried modifying apns-conf.xml and i get ims registered but i still can't make calls. And after a while it reverts back to not registered even after making it immutable.
braveheartleo said:
• Debloat
Click to expand...
Click to collapse
I also want to add that they can easily debloat by flashing global rom and still have temp root. It worked on my xz1 au/sov36.
nitrams said:
I also want to add that they can easily debloat by flashing global rom and still have temp root. It worked on my xz1 au/sov36.
Click to expand...
Click to collapse
I just want to point that flashing global rom will loose the volte. But I have found a solution for that or maybe others already knew about it. By modifying oem/system-properties/config.prop and adding these lines and not justnthe volte but it will also activate wifi calling and video calling.
persist.data.iwlan.enable=true
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.data.iwlan=1
persist.data.iwlan.ipsec.ap=1
persist.radio.volte.dan_support=true
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.radio.VT_ENABLE=1
persist.sys.cust.lte_config=true
persist.rcs.supported=1
But still, im unlucky to have my carrier's volte work for me.
GitHub - edgd1er/voenabler: voenabler
voenabler. Contribute to edgd1er/voenabler development by creating an account on GitHub.
github.com
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