[CLOSED] Enable Native Call Recording [OOS] [ROOT/NON-ROOT] [APP/MAGISK MODULE/ADB/TASKER] - OnePlus 5 Themes, Apps, and Mods

Introduction
Hello everyone! You might/might not know that OxygenOS (and ROMs based on it) have an in-built/native call recording feature. However, it is not enabled for everyone as it is region-locked and it might/might not be illegal to record calls where you are, with/without notifying the other party that the call is being recorded.
This thread has been created with the intent of enabling this call recording feature on OxygenOS (and ROMs based on it). There are several ways to achieve this, which have been listed below. You can use any method, as per your preference, and it should work. Let's get straight to it then!
Ways to Enable
Non-Root Method(s)
ADB command via a computer
Root Method(s) (in order of recommendation)
Magisk module
Flashable zip
Tasker profile
App which runs on boot
Detailed Information and Usage
Non-Root Method(s)
Spoiler: ADB command via a computer
Requirements: A working ADB interface on a computer, USB debugging enabled on the device
Usage: Run the following command to enable native call recording:
Code:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Reboot Survival: No
Root Method(s) (in order of recommendation)
Spoiler: Magisk module
Requirements: Magisk
Usage: Download and copy the EnableOOSNativeCallRecording-Magisk v9.1.zip to your device. Once done, install it in Magisk Manager as a module.
Reboot Survival: Yes
Spoiler: Flashable zip
Requirements: TWRP
Usage: Download and copy the EnableOOSNativeCallRecording-Flashable v8.0.zip to your device. Once done, reboot to recovery (TWRP) and just flash the zip.
Reboot Survival: Yes
Note: This method should work for rootless users too, but it needs TWRP and hence an unlocked bootloader.
Spoiler: Tasker profile
Requirements: A rooted device, Tasker
Usage: Download and copy the EnableOOSNativeCallRecordingv2.prf.xml to your device. Once done, import it in Tasker as a profile.
Reboot Survival: Yes
Spoiler: App which runs on boot
Requirements: A rooted device
Usage: Download and install the EnableOOSNativeCallRecording v2.0.apk and run it. At the first launch, grant root access to the app.
Reboot Survival: Yes
Downloads
Google Drive Folder (Primary)
AndroidFileHost Folder (Mirror)
Compatibility
Device(s)
All OnePlus Devices
ROM(s)
OxygenOS
Important Read-Me Points
[Magisk module only] The module installation has been designed to use the existing TeleService.apk from your device and modify it. Hence, if you update your ROM, there is a chance that the original apk that was modified is updated with the ROM update, which might lead to bootloops/other issues after installing the update, with this module installed. To avoid this from happening, always update your ROM by following these steps: Uninstall the existing module -> Reboot -> Download and apply the system update -> Reboot -> Download and install the latest module -> Reboot your phone again once the installation is complete.
[App method only] After your device fully boots up, a notification message will appear in the status bar/pull down notification panel to let you know that call recording has been enabled (which will go after 10 seconds if you don't swipe it away).
[App method only] There is also a "Read Me" link in the notification message if you want to read a short information regarding the app.
[All methods] Please make sure that you wait for at least 30 seconds after boot before checking if the call recording menu option is visible for you under the stock dialer's settings.
[All methods] All your recordings will be stored either at /storage/emulated/0/Record/PhoneRecord OR /storage/emulated/0/Android/data/com.oneplus.communication.data/files/Record in the aac format.
[All methods] The mod works only works when using the stock OxygenOS dialer, and it will not enable call recording in any other app, like Google Dialer, etc.
[All methods] If something that is supposed to run on boot is not executing on boot, you need to turn off advanced optimisation: Settings -> Battery -> Battery optimisation -> Three dot menu (⋮) -> Advanced optimisation -> Turn off.
[All methods] The mod enables native call recording option, but may not turn on auto-recording of the calls. If you wish to do that, after using one of the methods listed above, open the Stock Dialer App -> Three dot menu (⋮) -> Settings -> Auto-record calls -> Turn on.
[All methods] If you have hidden root from the stock dialer app via Magisk Hide, the call recording option might disappear after sometime. Make sure that the stock dialer is not checked in the Magisk Hide selection list.
Disclaimers
I am not the developer of the Enable OOS Native Call Recording app. I merely stumbled upon it in OnePlus 3T's Themes, Apps and Mods forum and I take no credit for it. Please direct all your thanks and/or donations towards @padlad, the original developer of the app. Link to the original thread is here.
I am not the developer of the flashable zip. The zip was posted later in this thread and I take no credit for it. Please direct all your thanks and/or donations towards @Zackptg5, the original developer of the flashable zip.
I am not the developer of the Tasker profile. The profile was posted later in this thread and I take no credit for it. Please direct all your thanks and/or donations towards @strongst, the original creator of the Tasker profile (original idea by @Fif_).
You are doing this at your own risk. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you are unsure of how to go about something.
It might be illegal in your country to record calls with/without notifying the other party that the call is being recorded. Either ways, you are responsible for using this mod.
Thanks To
@padlad, for creating the Enable Call Recording app and the Tasker profile
@Zackptg5, for creating the flashable zip
@strongst, for creating the Tasker profile and for being super helpful to everyone
@My Name is ShaoXIa, for doing excellent research work and making great recommendations for improving the stability and effectiveness of the Magisk module
@Taknok, for improving race condition handling at boot
@topjohnwu, for Magisk and all the work he's ever done for the community
@osm0sis, for the AnyKernel3 template and all the work he's ever done for the community
@joaomgcd, for Tasker
@Tomek Kondrat, for the mention in this XDA article
All of you guys for viewing this thread
Changelog
Spoiler: Enable OOS Native Call Recording Apk
v1.0 - Initial release
v2.0 - Enable run-on-boot
Spoiler: EnableOOSNativeCallRecording-Magisk Zip
v1.0 - Initial release for Magisk v13.1, v13.2, v13.3
v2.0 - Update for Magisk v14.0
v3.0 - Update for Magisk v15.0
v3.1 - Reduced the script execution delay from 2 minutes post boot to 10 seconds post boot
v3.2 - Slightly increased the script execution delay from 10 seconds post boot to 30 seconds post boot
v4.0 - Update for Magisk v16.0
v5.0 - Update for Magisk v17.0
v5.1 - Made the script execute the command 5 times at an interval of 30 seconds after boot
v5.2 - Made the script execute the command every minute infinitely post the initial run
v5.3 - Adjusted the script to make the infinite loop run asynchronously
v5.4 - Reverted changes made in v5.2 and v5.3 as most of the users preferred and had no issues with v5.1
v6.0 - Fixed call recording automatically getting disabled after a while
v6.1 - Reverted the last change which caused SIM settings force closes
v7.0 - Permanently fixed call recording automatically getting disabled after a while and fixed the SIM settings force close issue that was caused by the release of v6.0
v8.0 - Update for Magisk v19.0
v9.0 - Updated template and added manufacturer check
v9.1 - Base template update and manufacturer check bug fix
v9.2 - Improve race condition handling at boot and fixed installation failures with Magisk Canary
Spoiler: EnableOOSNativeCallRecording-Flashable Zip
v1.0 - Initial release
v2.0 - Updated to remove the separate init file and run the command from existing the init.rc file
v3.0 - Updated to include device codenames in addition to the official device names
v4.0 - Synced with the latest AnyKernel template and new BusyBox
v5.0 - Synced with the latest AnyKernel template and changed backup/restore method
v6.0 - Completely re-wrote flashable zip; now works for rootless users too who have an unlocked bootloader and TWRP installed
v7.0 - Added a slight delay in command execution to support Treble OOS; shifted the script to /system/etc/init
v8.0 - Permanently fixed call recording automatically getting disabled after a while
Spoiler: EnableOOSNativeCallRecording Prf Xml
v1.0 - Initial release
v2.0 - Updated parameters for stability and effectiveness
OP Update Information
Created: July 10, 2017
Last Updated: January 17, 2021

Tried it on my OOS 4.5.5 stock. Works flawlessly!

Simple word: COOL!
Sent from my OnePlus5 using XDA Labs

Works great for me. I've been played by these customer service representativeslately. No more. I'm recording all their bs so I can play it right back to them when they try to act like "Who said that?". Thank you! ?
Sent from my OnePlus 5 using XDA Labs

Thanks

You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.

djsubterrain said:
You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.
Click to expand...
Click to collapse
It's probably true in UK that you need to warn if the phone call is recorded. In some other countries it might be completely illegal to record phone calls. But at least in Finland you may record every phone call if you are a participant in that conversation without warnings or notifications.

Working on FreedomOS - thanks!

Awesome! Can we perhaps enable this using adb shell commands when not rooted somehow?

Thanks, I had to disable battery optimization for the app option 1 in order to be runned at boot.
Sent from my OnePlus 5 using XDA Labs

Flint2 said:
Thanks, I had to disable battery optimization for the app option 1 in order to be runned at boot.
Click to expand...
Click to collapse
Instead of doing that, go to Settings -> Battery -> Battery optimisation -> Three dot menu (⋮) -> Advanced optimisation -> Turn off. That should help. Try it after adding the app back to the battery optimized list.

djsubterrain said:
You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.
Click to expand...
Click to collapse
In New York only one party had to be aware.

What is the battery consumption like?
Increases or not?

Marucins said:
What is the battery consumption like?
Increases or not?
Click to expand...
Click to collapse
I don't think it should impact the battery consumption at all. The app doesn't run in the background, and the only thing it does (on boot/when run manually) is change a toggle in secure settings. Everything else is baked into OOS. Also, I personally haven't observed any increase in battery consumption at all after using the app than the standard consumption.

Why did the command disappear after restart?
"settings put global op_voice_recording_supported_by_mcc 1"
Where to add it to be permanent? -> build.prop ??
//edit
I created a script that runs 3C Toolbox on system startup.

not working on my oos 4.5.5
Tried installing the app. It didnt ask for any root approval or didnt boot up. It didnt wok for me at all. Any suggestions ??
rgds
Lal
shadowstep said:
Disclaimer: I am not the developer of this app. I merely stumbled upon it in OnePlus 3T's Themes, Apps and Mods forum, and decided to give it a shot on my OnePlus 5. It worked like a charm, so I decided to post here for everyone's benefit. I take no credit for this work. Please direct all your thanks and/or donations towards @padlad, the original developer of this app. Link to the original thread is here.
Hi all!
Want to utilize OOS's native call recording feature without any hassles? Look no further! The app works with OOS 4.5.x flawlessly, with the OnePlus 5. There are two variants of the app, one that runs on boot (which will automatically enable the native call recording feature at every boot) and the second one that doesn't run on boot, and hence the feature will be disabled after every reboot and you will have to manually enable it (by clicking on the app icon) after the reboot.
For those curious, all that this app does is execute a root command line which enables the native call recording feature present in OOS's stock dialer. The command line is -
Code:
su
settings put global op_voice_recording_supported_by_mcc 1
Please note that this app requires root, so it will request for the root permission at it's first run. After your device fully boots up, a notification message will appear in the status bar/pull down notification panel to let you know that call recording has been enabled (which will go after 10 seconds if you don't swipe it away). There is also a "Read Me" link in the notification message if you want to read a short information regarding the app.
All your recordings will be stored at /storage/emulated/0/Record/PhoneRecord in the aac format.
Download Links:
Click here to download variant 1 (Auto-enabled at boot, call recording will be turned on automatically at every boot)
Click here to download variant 2 (Not enabled at boot, call recording will not be turned on automatically at every boot)
Have fun!
Click to expand...
Click to collapse

"adb shell settings put global op_voice_recording_supported_by_mcc 1" seems to work for non-root too, however, might not survive restart. Lets see if I can fix that.

Marucins said:
Why did the command disappear after restart?
"settings put global op_voice_recording_supported_by_mcc 1"
Where to add it to be permanent? -> build.prop ??
//edit
I created a script that runs 3C Toolbox on system startup.
Click to expand...
Click to collapse
If you run the command manually via a terminal, it would work for the current session but as soon as you restart the phone, it would get reset to it's default value for OOS, i.e. 0. It's a hidden, secure setting and different from the stuff build.prop contains. If you want to use build.prop to enable call recording on boot, find the value below in build.prop & change it:
Code:
persist.sys.oem.region=OverSeas
[I]TO[/I]
persist.sys.oem.region=CN
This will change your phone's OEM region to China, where call recording is enabled by default by OnePlus and therefore call recording will be enabled for you too. Also, it will survive a reboot, since it's a build.prop change.
maneklal said:
Tried installing the app. It didnt ask for any root approval or didnt boot up. It didnt wok for me at all. Any suggestions ??
rgds
Lal
Click to expand...
Click to collapse
Which variant did you try? The one that auto-starts at every boot or the normal one? Also, what root system are you using - Magisk or SuperSU? All the people I know who've tried this have reported success, so I'm sure something is up at your end only.
asc366 said:
"adb shell settings put global op_voice_recording_supported_by_mcc 1" seems to work for non-root too, however, might not survive restart. Lets see if I can fix that.
Click to expand...
Click to collapse
Yeah? Interesting. My guess is that if you run the command via ADB, it doesn't need root and will work on unrooted OOS, but won't survive a reboot. However, if you run the command via a terminal emulator on the phone itself (the commands that I've mentioned in the first post), then you will need root or else the setting won't be changed. I hope this answers your question!

shadowstep said:
Yep, read my first response above. You don't need root to enable call recording, it can be done via the adb command, but it won't survive a reboot. This is where the app helps!
Click to expand...
Click to collapse
So let me get this straight; I can do the adb shell command while unrooted and running this with a terminal emulator, I need "su" (thus, root) ?

asc366 said:
So let me get this straight; I can do the adb shell command while unrooted and running this with a terminal emulator, I need "su" (thus, root) ?
Click to expand...
Click to collapse
Yes, I edited my reply in my last post for clarity. Apologies for the confusion. Don't have root? Run the command via an adb shell from a computer/laptop. Have root? Run the command via a terminal emulator on the phone itself.

Related

[ROM] [LP 5.1.1] Validus Unofficial Hardened Updated June 17

Rom updated to LP 5.1.1 on June 17. All latest features included:
My Changes:
1. Thermanager values fixed to prevent flickering and low charging. There is ZERO flickering.
2. Camcoder mike low recording sound fixed
3. VOLTE enabled (if and when your carrier implements it). If you go to Network, you'll see Volte enabled; also in phone test menu, you will see VOLTE flag enabled
4. WIFI background scanning disabled - better battery life
5. GSM Network is handled by System, as opposed to Modem
6. Shady IPs cleaned thought the rom
7. Kernel with Overclock, Voltage, Screen Color and TWRP integrated.
9. All usual hardened features in kernel (see original description below)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13068
Do a clean flash, since this is LP 5.1.1
_______________________________________________________________________________________________________
Rom updated March 20. Over 800 downloads in 8 days and 6 "thanks you". Thanks...
Some changes: sound control in kernel which allows to compensate for low camera mike recording (use Trickster mode or similar app); wifi background scanning is disabled - better battery life; latest validus and cm changes
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/dl/?id=11628
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is the latest Validus LP compiled from sources on March 11. Latest CM changes including FM Radio
Changes:
1. Kernel with all ciphers, hashes, random number generation enabled
2. SeLinux disabled, Tomoyo security enabled
3. 256 bit encryption with increased key length and 5000 iteration, as opposed to weak 2000
4. Latest CM and Validus changes including black interface and changing keyboard theme based on app color
5. Black Contacts fixed (now white text on black background)
6. Led lights normal brightness fixed
7. TWRP 2.8.X integrated into kernel
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/?id=8646#downloads
Install:
1. Be on Kitkat at least, rooted and with recovery
2. Enter recovery, wipe System/Cache/Data
3. Flash the rom
4. Flash data from your previously saved Lollipop rom (optional, but works on my device)
5. Reboot and enjoy
Credit: Validus Team, Slimroms, AOSP, Cyanogenmod, Omniroms
Warning: I am not responsible for death and destruction resulting from flashing this rom. You are on your own.
Kernel Source: https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Validus Lollipop Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/Team-Validus/android
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP Cyanogenmod
Version Information
Status: Testing
Created 2015-03-12
Last Updated 2015-06-17
Screen Shots
Screen shots added.
For those who are interested in encrypting the data partition. Remember, there is no longer any visible slowdown. What you need to do before or after encryption is to enable "Disable HW overlay" in Developer Options. There is a catch, though: this won't stick after reboot unless you implement an init.d script that will take care of this.
Here is the script : http://d-h.st/QIiE
Download the script by using the blue button (unless you want their ridiculous exe. download manager)
Put the script into /system/etc/init.d with at least 750 permission and reboot. You will see that Disable HW overlay option is ticked by default.
Also, I recommend ADB shell encrypting, as opposed to doing it from Security menu for several reasons: first with ADB you are not limited by 16 characters, you can use a passphrase that you can remember and no one can break; second, in Security menu, encryption will use your pin password (which is short) to encrypt. Remember, you only need a long passphrase to boot, and if your rom has "soft reboot", you don't need to enter password at all. Here is how to do it:
1. Go to Security menu and enable Pin/Password/Pattern or None. Your screen password could be short, as it is independent from boot password.
2. Next, pick a long boot password. You need to convert it into hex: just use this site https://www.online-toolz.com/tools/text-hex-convertor.php for conversion. Now, copy your hexed password (for future pasting).
3. Next, go to Developer Options and enable ADB; Root for ADB + APPS
4. Connect your phone to your computer
5. Open Terminal and type "adb shell" without quotes and press enter
6 Then type "su" also no quotes and press enter
7. Now type the following without quotes: vdc cryptfs enablecrypto inplace password HERE PASTE YOUR ACTUAL HEXED PASSWORD and press enter. Remember, don't type HERE PASTE YOUR PASSWORD, instead paste your hexed password there.
8. After you press enter, your phone will reboot and start encrypting. In a few minutes, you will get another reboot and a prompt for boot password. Here, enter your actual password (not the hexed one). Your phone will boot and you can check in the Security options that your phone is encrypted.
Enjoy.
Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app
meliacentrum said:
Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM bugs....
Do Google Services work on this build?
Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug
shingers5 said:
Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug
Click to expand...
Click to collapse
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.
Good compilation
My previos ROM was RR. Trying this. Data was restored from RR is normal.
I like this Validus ROM
All what I want is included + Black Theme (Default)
Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640
Instruction for Encrypting Data Partition
See post #3 on how to encrypt your data partition without any visible slowdown.
http://forum.xda-developers.com/showpost.php?p=59392722&postcount=3
ggs2 said:
Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640
Click to expand...
Click to collapse
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.
I actually like thia ROm and the default theme too. Been using since flashing and gapps work. Had a few issues but flashed banks gapps and they worked fine
Does this have low LED bug? Can't see LED... tried xposed that works though:
optimumpro said:
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.
Click to expand...
Click to collapse
ggs2 said:
Does this have low LED bug? Can't see LED... tried xposed that works though:
Click to expand...
Click to collapse
Led is fixed, unless you use a different kernel.
optimumpro said:
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.
Click to expand...
Click to collapse
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?
steveeJ said:
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?
Click to expand...
Click to collapse
I don't use Gapps, but another user a few posts above said they worked...
optimumpro said:
Led is fixed, unless you use a different kernel.
Click to expand...
Click to collapse
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...
ggs2 said:
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...
Click to expand...
Click to collapse
Did you follow directions in my other post? Did you install xposed and xprivacy in Resurection? I have validus with data restored from Resurection and xposed and xprivacy work fine.
optimumpro said:
I don't use Gapps, but another user a few posts above said they worked...
Click to expand...
Click to collapse
gapps seem to work so far!
I'm currently trying to mount the sdcard which is ext4 formatted. I can mount it manually via the shell, but vold won't notice any of that. I guess I need to figure out how to persistently change /fstab.qcom file.

[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]

AOSP for OnePlus 5
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
This ROM boots also with a locked bootloader.
See second post to get more information.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
Known issues
See Third post.
Changelog
See third post.
Download
Releases can be found on AndroidFileHost: here
Old releases on SourceForge: here
Installation
Backup everything and remove PIN protection before installing this ROM.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
GApps can be found here:
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/30-Jan-2021/
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
If you want to keep the TWRP flashed, flash the persist_twrp.zip provided here:
https://sourceforge.net/projects/aosponeplus/files/Misc/
And flash the TWRP image you prefer (if you have a locked bootloader, follow the steps in the second post).
Sources
Manifest on github: https://github.com/robertoglandroid/local_manifests
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5, ROM for the OnePlus 5
Contributors
robertogl
Source Code: https://github.com/robertoglandroid/local_manifests
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-10-29
Last Updated 2021-10-06
Boot with locked bootloader
Following the next points, you will be able to boot this ROM with the locked bootloader on OnePlus 5. This will grant the security of your own data, as no one will be able to flash any new image without first deleting everything from the data partition: this is because unlocking the bootloader again requires to format the data partition.
If the data are encrypted (if you are using a PIN or the fingerprint to unlock your device), your data are safe.
Also, no more wait time or 'you have unlocked the bootloader' screen at boot
Be aware that in this 'beta' version, I'm still using AOSP keys, that are actually publicly available.
ATTENTION: ALL THE DATA ON THE DEVICE WILL BE LOST FOLLOWING THIS PROCEDURE
The following link contains different useful files:
https://androidfilehost.com/?w=files&flid=320711
a signed twrp image: signed_twrp.zip Thanks @codeworkx for the actual TWRP recovery!
a signed boot image with Magisk preinstalled: signed_magisk_boot_[date].img
a 'persist twrp' recovery zip: persist_twrp.zip
Download the signed TWRP image signed_twrp.zip
Enter in fastboot mode. There are two ways, select the one you prefer:
from adb, run the command 'adb reboot bootloader'
or power on the device pressing the power up button and the power button at the same time
Run the following command to flash the signed recovery:
fastboot flash recovery signed_twrp.img
Using the volume buttons, select 'RECOVERY' and using the power button boot into recovery.
This TWRP version does not support decrypting data if a numeric PIN is used, but this is not an issue. If asked for a PIN, just 'cancel' the dialog to get into the TWRP main screen.
From adb, push the OTA file and the GAPPS file:
adb push aosp_cheeseburger-ota-user-20201121.zip /data/update.zip
adb push FlameGApps-11.0-basic-arm64-20201024-ALPHA-10.zip /data/gapps.zip
(any gapps package should work, but I've only tested this)
adb push signed_magisk_boot_[date].img /data/magisk.img (only if you need Magisk)
adb push persist_twrp.zip /data/persist_twrp.zip (only if you want to persist the TWRP recovery after boot)
From the TWRP interface, select 'Install' and flash first the 'update.zip' file and secondly the 'gapps.zip' file.
If you want to persist the TWRP recovery, flash also the 'persist_twrp.zip' file.
If you need magisk, from the TWRP interface select 'Install Image' and install also the magisk.img file in the boot partition.
From the TWRP interface, reboot into fastboot (bootloader) mode again.
Run the command (ATTENTION: ALL THE DATA ON THE DEVICE WILL BE DELETED):
fastboot oem lock
Confirm the lock operation on the device's screen.
After the reboot, the device will probably boot again into the TWRP recovery: in this case, clear all the data from /data and restart the device (Wipe -> Format Data). Android will boot with the locked bootloader.
Important note: the device will now boot only signed image. DO NOT change boot.img without first check if it is signed. The images provided in this thread all are signed using AOSP keys.
If you are using Magisk, DO NOT UPDATE MAGISK after this installation. You can only update the Magisk Manager. At first boot, open the Magisk Manager and follow the instructions on screen.
If you don't flash the persist_twrp.zip archive, Android will replace the recovery at every boot with the stock signed recovery*. This stock recovery only flashes signed images (the OTAs from this thread are all signed), so if you need the TWRP, you have to use ADB sideload to flash the signed TWRP.
I've uploaded here a signed zip that can flash the signed TWRP while using the locked bootloader:
https://androidfilehost.com/?w=files&flid=320711
(signed_twrp.zip)
enter into recovery (with the physical buttons or with 'adb reboot recovery')
Press and hold the Power button. While holding the Power button press the Volume Up button then release the Volume Up button then the Power button to get into the Recovery UI
select 'apply update from ADB'
connect the phone and the pc, and from the pc run:
adb sideload twrp_signed.zip
reboot the phone selecting the 'reboot system now' from the recovery. Immediately after confirming the reboot, press the volume up button and keep it pressed until the boot mode is requested: select 'Recovery mode' and the phone will boot into the signed TWRP recovery. If the phone does not reboot, press the power button and after one second press the volume button keeping both buttons pressed until the device boots again.
Remember that, if you boot Android, you will lose the TWRP again.
How to update via TWRP
TWRP cannot decrypt the data partition using this ROM if you are using a PIN (it works fine using a pattern, for example).
To update the ROM:
- enter into TWRP recovery
- push the .zip update via adb:
$ adb push update.zip /data/
- from the TWRP recovery, select 'Install' e select the zip as /data/update.zip
If you need the TWRP recovery to be persisted, flash also the persis_twrp.zip archive again.
If you have a locked bootloader and you are using Magisk, flash the boot image with Magisk preinstalled again.
Notification LED control (BETA)
The ROM has an integrated Led Manager. It can be enabled from the SettingsExtra preinstalled app.
When enabled, the Android LED API will not work anymore: the colors
indicated in any application will not work: the only way to turn on the
LED is to use SettingsExtra.
Note that no error will be generated when a third party will try to turn
on the LED: the LED will simply not work.
The Led colors, blinking effect and filters are configurable, but there is no UI available.
The configuration can be injected using a text file, for example:
Code:
com.example.myapplication,,00FFFF,
com.example.myapplication,display,FFFF00,blink,500,5000
com.example.myapplication,test,0000FF,blink,500,500
android,debugging,FF00FF,blink,500,5000
The file should contains only lines with that structure, it should be named SettingsExtraLedConfiguration.conf, and it should be push as:
adb push SettingsExtraLedConfiguration.conf /sdcard/
You can also generate the file directly on the phone, but it could be a bit difficult as the file needs to be formatted correctly.
The rules are:
- colors are in hexadecimal, and they can be generated here (any website will work fine): https://htmlcolorcodes.com/
- the structure of every line is:
application package name, string, color, blink?, milliseconds ON, milliseconds OFF
where:
- application package name: the application package name, for example com.whatsapp for Whatsapp or com.android.settings for the Android Settings. You can use simple 'android' for the SystemUI notification (for example for the USB debugging notification)
- string: a word or a phrase to match the title of the notification. For example, setting as application package name 'com.whatsapp' and as string 'Name Surnane', this rules will only apply to notifications including the text 'Name Surname' in the notification title. Useful to filter for particular contact, for example. It is case insensitive. Leave this field empty to assign the same color to all the notifications from the indicated application.
- color: the hexadecimal color of the led
- bling: use the work 'blink' if you want the led to blink. Leave this empty, and not include the milliseconds parameters if you want the led to be always on
- milliseconds ON: integer value to indicate how much the led should stay on
- milliseconds OFF: integer value to indicate how much the led should stay off
The led is hardcoded to be yellow while the phone is charging and green when the phone is charging but with 100% battery.
The priorities are:
- the charging led colors have the lowest priority -> if a notification with a color is present, the charging status will not be shown
- if multiple notifications are present, the latest notification color is shown
- when one notification goes away, the color of the latest notification appeared will be shown
- the rule with a string indicated has priority over a rule for the same app but without matching string.
When the Led Manager is enabled from SettingsExtra, it is already working but I suggest a reboot so that the application can get all the notifications from the boot.
When the configuration file is updated, restart the manager from SettingsExtra (turn the LED manager option off and on again) or reboot the phone to load the new rules.
*as clarification, with 'stock recovery' the stock recovery from this ROM is intendend (not the Oxygen OS recovery).
Future plans
- Bug fixing. Known problems reported by users:
unable to go to setting from notification panel when lockscreen is disabled
unable to make/receive video call from dailer (call get disconnet) - voip calls (whatsapp, telegram, zoom) work fine
- New features to add:
face unlock
Different ringtones for the two sims
hide battery icon on status bar
Already fixed issues/added features
'find out what music is playing near you' Pixel feature is not working OnePlus 5 is not supported (OnePlus' blobs)
Gestures does not work correctly They are not supported by AOSP
wifi bridge Validated with OS release 20210225
gaming mode Added in SettingsExtra with OS release 20210210
vowifi is not working Fixed with OS release 20210123
advanced power menu Added in SettingsExtra with OS release 20210110
couldn't restore data from cloud (tried with alpha and beta flameGApps) Gapps issues (solved with NikGapps from december 31, 2020)
Auto brightness tile Added with OS release 20201227
volte/vowifi icon missing in status bar Fixed with OS release 20201225
No bluetooth battery level icon on status bar Fixed with OS release 20201205
I could not set up my work profile for my office application (Intune Company Portal Microsoft) - Should be fixed with OS release 20201205, waiting feedback
Call recording Done with OS release 20201205
Double tap to wake is not working with Always On Display mode enabled Fixed with OS release 20201128
USB Preferences are greyed out when launched from notification bar, but works for developer options Fixed with OS release 20201125
The menu on the display color gamut selection in the Settings Extra app overlaps with the menu title Fixed with OS release 20201125
This must be a Gapps issue, but could not restore my old backup from cloud Fixed with OS release 20201125
nfc tile is greyed out Fixed with OS release 20201125
Android auto is not working Fixed with gapps 'NikGapps-basic-arm64-11-20201122-signed.zip'
Cannot sign in chrome by default. First you need to go to settings and give it all the permissions it needs. Same for few other apps. Solved using different Gapps, for example the Nick Gapps (Thanks @SunitTalwar)
system navigation option in both accessibility and system/gestures Google decided this way
Update blobs from OOS 10.0.1 Done with OS release 20201121
no option to swap recents and back buttons Added with OS release 20201121
I couldn't find a way to hide that horrible google search bar Not possible without changing the Launcher code. Third party launchers (like Nova Launcher) do not have this issue.
backlight on hardware buttons not working Fixed with OS release 20201106
play store not certified Fixed with OS release 20201108
google pay not working Fixed with OS release 20201108
Dash charge is not tested Confirmed working with OS release 20201108
backlight on hardware buttons not consistent in case of quick multiple touches Fixed with OS release 20201109
Missing Android 10 theme customization on developer options Fixed with OS release 20201114
Always On Display Added with OS release 20201109
Changelog
[06/10/2021] aosp_cheeseburger-ota-user-20211006.zip
October 2021 Security Patch (synced with AOSP android-11.0.0_46)
Changelog of previous releases
[19/09/2021] aosp_cheeseburger-ota-user-20210919.zip
September 2021 Security Patch (synced with AOSP android-11.0.0_43)
A lot of code change to prepare support for Android 12
[08/08/2021] aosp_cheeseburger-ota-user-20210808.zip
August 2021 Security Patch (synced with AOSP android-11.0.0_40)
SettingsExtra: fix an issue causing call recording to not detect call ending
SettingsExtra: fix issue causing buttons backlight to stay with screen off
[08/07/2021] aosp_cheeseburger-ota-user-20210708.zip
July 2021 Security Patch (synced with AOSP android-11.0.0_r39)
Enable 'Cards and passes' (Settings -> System -> Gestires -> Power menu)
Requires Google Pay installed
Gestures are now working properly
SettingsExtra: add option to enable on-screen navigation bar
SettingsExtra: add option to turn off capacitive buttons backlight
Update Call Recording/Vibration: both call recording and vibration now actually starts when other side picks up (and not when you dial the number!)
SettingsExtra: add option to select Call Recordings directory
[15/06/2021] aosp_cheeseburger-ota-user-20210615.zip
Fix stock recovery not working
[13/06/2021] aosp_cheeseburger-ota-user-20210613.zip
June 2021 Security Patch (synced with AOSP android-11.0.0_r38)
Synced with LineageOS sources
Switch to AMR files for call recording (for better quality and compatibility)
SettingsExtra: add option to enable vibration at call connect/disconnect
[04/05/2021] aosp_cheeseburger-ota-user-20210504.zip
May 2021 Security Patch (synced with AOSP android-11.0.0_r37)
Phone now turns on automatically if an alarm is set
Fix device rebooting into recovery while listening to Whatsapp audio messages with LED manager enabled
[19/04/2021] aosp_cheeseburger-ota-user-20210419.zip
Changelog:
SettingsExtra: enable call recording on volte/vowifi calls
[18/04/2021] aosp_cheeseburger-ota-user-20210418.zip
Changelog:
Sync kernel sources with LineageOS
Should fix charging issues
Various fixes to SettingsExtra
Fix some issues with Dynamic Modem
Fix an issue causing the VoLTE icon to not be present in some situations
Disable call recording in case of VoLTE/VoWifi calls (Android does not support recording those calls)
[05/04/2021] aosp_cheeseburger-ota-user-20210405b.zip
Changelog:
April 2021 Security Patch (synced with AOSP android-11.0.0_r34)
[05/04/2021] aosp_cheeseburger-ota-user-20210405.zip
Changelog:
Switch back to the Lineage-based kernel
Synced with LineageOS sources
SettingsExtra: fix 'set vibration intensity' on Lazy kernel
Fix search not working on Settings app
Fix wrong strings on 'System' page in the Settings app
Fix audio not working during some calls
Fix wrong NFC icon tile
Improve fingerprint responsiveness with screen off
[20/03/2021] aosp_cheeseburger-ota-user-20210320.zip
Changelog:
Synced with LineageOS sources
Enabled EAS - Energy-aware scheduling
Switch to Lazy Kernel - https://forum.xda-developers.com/t/lazy-kernel-for-op5-t-02-28-2021.4077467/
[07/03/2021] aosp_cheeseburger-ota-user-20210307.zip
Changelog:
March 2021 Security Patch (synced with AOSP android-11.0.0_r32)
[25/02/2021] aosp_cheeseburger-ota-user-20210225.zip
Changelog:
Improvements to LED Manager
Validate wifi bridge - when wifi is connected and hotspot is enabled, the phone will work as wifi extender
[10/02/2021] aosp_cheeseburger-ota-user-20210210.zip
Changelog:
Add gaming mode tile - when enabled, capacitive buttons/auto brightness/heads up notifications are disable
Fix an issue causing audio to be disabled during voice calls
Improvements to LED Manager
[07/02/2021] aosp_cheeseburger-ota-user-20210207.zip
Changelog:
(BETA) Add notification LED control options
[04/02/2021] aosp_cheeseburger-ota-user-20210204.zip
Changelog:
Sync with LineageOS 18.1 product definition sources
Fix low audio level on recorded video
Add option to select vibration intensity (SettingsExtra)
[02/02/2021] aosp_cheeseburger-ota-user-20210202.zip
Changelog:
February 2021 Security Patch (synced with AOSP android-11.0.0_r31)
[23/01/2021] aosp_cheeseburger-ota-user-20210123.zip
Changelog:
Sync LineageOS 18.1 product definition sources
Fix VoWifi not working
Add option to show the VoWifi icon on status bar (SettingsExtra)
[10/01/2021] aosp_cheeseburger-ota-user-20210110.zip
Changelog:
Fixed race condition causing the bluetooth icon on status bar to be present without devices connected
Rewrite the mechanism to manage slider events - should be a lot more stable now!
Disabled audio safe volume level warning
Added advanced reboot options to SettingsExtra (only reboot in recovery or fastboot mode at the moment)
[04/01/2021] aosp_cheeseburger-ota-user-20210104.zip
Changelog:
January 2021 Security Patch (synced with AOSP android-11.0.0_r27)
[03/01/2021] aosp_cheeseburger-ota-user-20210103.zip
Changelog:
Fix front camera not working with some applications using Camera API1
[02/01/2021] aosp_cheeseburger-ota-user-20210102.zip
Changelog:
Allow disabling heads up notifications from SettingsExtra
Fix SettingsExtra disabling all Accessibility Services except SettingsExtra at boot
Improve mechanism to manage screen off slider events (this should prevent the screen from turning on sometimes when the volume slider is used)
[27/12/2020] aosp_cheeseburger-ota-user-20201227.zip
Changelog:
Add Adaptive Brightness tile (automatic brightness)
Add support for Pocket Mode (SettingsExtra) - disable fingerprint reader and double tap to wake when proximity sensor is covered and screen is off
Some code refactoring
[25/12/2020] aosp_cheeseburger-ota-user-20201225.zip
Changelog:
Fix Wellbeing not working
Add option to show the VoLTE icon on status bar (SettingsExtra)
Add support for multiple users (Settings -> System -> Multiple user)
Add blur to the background when notification bar is pulled down (it is possible to disable this from developer options -> Enable blurs)
Sync LineageOS 18.1 product definition
Sync with Google release android-11.0.0_r24
[08/12/2020] aosp_cheeseburger-ota-user-20201208.zip
December 2020 Security Patch (synced with AOSP android-11.0.0_r21)
Add Dynamic Modem feature to SettingsExtra: allow to automatically change network mode (GSM, LTE, 3G, etc...) when wifi connects or disconnects
Internal code refactoring of SettingsExtra
[06/12/2020] aosp_cheeseburger-ota-user-20201206.zip
Fix Bluetooth status bar icon not showing the battery level
[05/12/2020] aosp_cheeseburger-ota-user-20201205.zip
Add option to enable Call Recording - available in the Settings Extra app
Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a battery level)
Update Qualcomm HALs to the latest sources from Lineage
[28/11/2020] aosp_cheeseburger-ota-user-20201128.zip
Double tap to wake now works with Always On Display mode enabled
Fix NFC tile crash at boot
[25/11/2020] aosp_cheeseburger-ota-user-20201125.zip
USB preferences now works when launched from notification panel
Add working NFC tile
Fix overlapping of display color gamut menu on Settings Extra app
Add AOSP messaging app - Fix first boot backup restoring
[21/11/2020] aosp_cheeseburger-ota-user-20201121.zip
Update OnePlus blobs from OOS 10.0.1 (Added Camera EIS): you have to flash the correct firmware or the latest official OOS release before flashing this ROM! Firmwares can be found in the LineageOS 18 thread (first post)
Double tap to wake is now working (not in Always On Display mode)
Double tap to wake is disabled by default - enable it from Settings -> Display -> Tap to wake
Added Settings Extra app:
Allow to swap back and recent capacitive buttons
Allow to enable display DC dimming
Allow to change display color gamut (DCI-P3 or sRGB)
Following the steps in the second post, it is now possible to boot this ROM with a locked bootloader
[14/11/2020] aosp_cheeseburger-ota-user-20201114.zip
Dark mode is now really dark on the Android Settings (and not grey)
Enable AOSP theming options on Settings -> display -> Styles & wallpapers
Enable AOSP Night Light filter options (low blue light) on Settings -> display -> Night Light
[09/11/2020] aosp_cheeseburger-ota-user-20201109.zip
Show the correct Android Security Patch version on the Android Settings UI
Improve reliability of the capacitive buttons backlight
Add Always On Display - Enable from Settings -> Display -> Lock Screen -> 'Always show time and info'
[08/11/2020] aosp_cheeseburger-ota-user-20201108.zip
SafetyNull fully passes*
Google Play Store is now certified
* This is tested with this ROM and GApps installed - no Magisk Works also with Magisk installed
* To pass SafetyNet, the 'Android Security Update' on the Android Settings is reporting 'April 5, 2020': this is only reported as old Security Patches, the ROM has actually the latest secutiry patches available from Google. Fixed with OS release 20201109
[07/11/2020] aosp_cheeseburger-ota-user-20201107.zip
Allow thirdy party apps to access the fingerprint sensor
Fix an issue causing a 'Device lock by admin' warning when unlocking the device
[06/11/2020] aosp_cheeseburger-ota-user-20201106.zip
Enable backlight for capacitive hardware buttons
[04/11/2020] aosp_cheeseburger-ota-user-20201104.zip
November 2020 Security Patch
Sync with AOSP android-11.0.0_r17 tag
[29/10/2020] aosp_cheeseburger-ota-user-20201029.zip
First release
Added to the OnePlus 5 Index Thread here.
shadowstep said:
Added to the OnePlus 5 Index Thread here.
Click to expand...
Click to collapse
Thank you
I've tested phone calls and 3g/4g connectivity on both sim slots and they are working correctly
What's the correct way to downgrade to stable 10 in case something goes wrong?
petrea_86 said:
What's the correct way to downgrade to stable 10 in case something goes wrong?
Click to expand...
Click to collapse
It works as other ROMs: go into TWRP recovery, clear data/cache, install stable OOS from zip, reboot
robertogl said:
It works as other ROMs: go into TWRP recovery, clear data/cache, install stable OOS from zip, reboot
Click to expand...
Click to collapse
Figured out myself , plus I had to lock the bootloader back but thanks a lot anyway. Cheers.
petrea_86 said:
Figured out myself , plus I had to lock the bootloader back but thanks a lot anyway. Cheers.
Click to expand...
Click to collapse
Did you try the rom? Do you have any feedback?
robertogl said:
Did you try the rom? Do you have any feedback?
Click to expand...
Click to collapse
No, I haven't yet. I tried yaap 11.0 before I found this thread. I'd like to try it but I think I will encouter the same issues. Will google pay work on it? If not, is there any way to make it work?
petrea_86 said:
No, I haven't yet. I tried yaap 11.0 before I found this thread. I'd like to try it but I think I will encouter the same issues. Will google pay work on it? If not, is there any way to make it work?
Click to expand...
Click to collapse
At the moment, Google Pay won't work as in most custom rom.
I think that signing the images and locking the bootloader will help, but as explained in the second post this is still a work in progress on my side.
robertogl said:
At the moment, Google Pay won't work as in most custom rom.
I think that signing the images and locking the bootloader will help, but as explained in the second post this is still a work in progress on my side.
Click to expand...
Click to collapse
I definitely can help you with testing but you can help me with other stuff It's been 10 years now since I haven't played around with all this but it's comming back little by little. Although a lot of things have changed. Now magisk is the king I see.
robertogl said:
Did you try the rom? Do you have any feedback?
Click to expand...
Click to collapse
I did try this ROM, initial impressions pretty Fast (boot and general operations) , Tried this with NIK Stock GAPPS . Camera was working and so was alert slider . Calls, sound and other basic stuff.
Only thing missing was backlight for hardware buttons. Can you please add that as well .
Also Google playstore showed device as not certified . Assuming it is due to device signatures in build prop as other custom roms are able to bypass this by spoofing phone as a Pixel device. Not sure if this could be used in a pure AOSP ROM .
Apart from that pretty stable , was just missing hardware key light and uncertified play store .
I'm currently on stock OOS 10 with locked bootloader after checking yaasp today. Can anyone tell me how to get a full nandroid backup? I would like to test this rom as well and help you out as much as possible, but don't wanna go through clean install process each time I do it. I'd use it as my daily driver even with some bugs unsorted, but can't do that without google pay.
petrea_86 said:
I definitely can help you with testing but you can help me with other stuff It's been 10 years now since I haven't played around with all this but it's comming back little by little. Although a lot of things have changed. Now magisk is the king I see.
Click to expand...
Click to collapse
I'll work on the new signed images in the following couple of weeks. Hopefully, we'll get google pay working
SunitTalwar said:
I did try this ROM, initial impressions pretty Fast (boot and general operations) , Tried this with NIK Stock GAPPS . Camera was working and so was alert slider . Calls, sound and other basic stuff.
Click to expand...
Click to collapse
Thank you, every feedback is important at this stage.
SunitTalwar said:
Only thing missing was backlight for hardware buttons. Can you please add that as well .
Click to expand...
Click to collapse
I saw how other roms do this, and it was not compatible to a pure AOSP rom. I did not give it much importance at first, but I'd look into this for the next release.
SunitTalwar said:
Also Google playstore showed device as not certified . Assuming it is due to device signatures in build prop as other custom roms are able to bypass this by spoofing phone as a Pixel device. Not sure if this could be used in a pure AOSP ROM .
Apart from that pretty stable , was just missing hardware key light and uncertified play store .
Click to expand...
Click to collapse
You are probably correct about the play store certification. And yes, we can do the spoofing stuff also on this ROM, as far as I'm aware of the tricks other ROMs are doing. I'll look into this.
Second post updated with:
- backlight on hardware buttons not working
- play store not certified
- google pay not working.
petrea_86 said:
I'm currently on stock OOS 10 with locked bootloader after checking yaasp today. Can anyone tell me how to get a full nandroid backup? I would like to test this rom as well and help you out as much as possible, but don't wanna go through clean install process each time I do it. I'd use it as my daily driver even with some bugs unsorted, but can't do that without google pay.
Click to expand...
Click to collapse
You should be able to do a full nandroid using a TWRP recovery (look at the thread from codeworkx here on xda). Note that TWRP does not support parallel app at the moment, so if you'are using those you cannot do the nandroid.
Also, you cannot do this process with an unlocked bootloader.
T̶h̶e̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶i̶s̶ ̶t̶h̶a̶t̶ ̶t̶w̶r̶p̶ ̶d̶i̶s̶a̶p̶p̶e̶a̶r̶s̶ ̶o̶n̶c̶e̶ ̶I̶ ̶l̶o̶c̶k̶ ̶t̶h̶e̶ ̶b̶o̶o̶t̶l̶o̶a̶d̶e̶r̶.̶ ̶H̶o̶w̶ ̶t̶o̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶t̶w̶r̶p̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶b̶o̶o̶t̶l̶o̶a̶d̶e̶r̶ ̶b̶e̶i̶n̶g̶ ̶l̶o̶c̶k̶e̶d̶?̶ Done using adb full backup. Now back to testing.
Any screenshots? Features?
New build in the first post: aosp_cheeseburger-ota-user-20201104.zip
Changelog:
November 2020 Security Patch
Sync with AOSP android-11.0.0_r17 tag
Also added instructions to the third post on how to update the rom using the TWRP recovery (in case of encrypted data).
morfances said:
Any screenshots? Features?
Click to expand...
Click to collapse
There is nothing particular. There are no features over the AOSP operating system. I like this way

[ROM][A515F/DS][OneUI 3.1 - S20 Port] Just4Fun v1

HELLo everyone...
After several weeks, months and before Android 12 released, i decided to share this ROM to this A51 community. Hopefully you guys enjoy it and don't offend me if the ROM is bad, so....let's get it ON.
Things to do before flashing:
1. Make sure you're on binary 5 (this ROM tested and using binary 5 vendor, so to avoid any broken or whatever error flash your device with latest firmware).
2. Backup your IMEI (highly recommended).
Flashing:
1. Clean flash is recommended. Flash kernel, flash J4F vendor and system.img, flash multy disabler (if necessary) then full wipe and also you can perform "typing YES" format. Reboot to recovery again, then flash as usual you guys always do (Magisk etc.).
ROM Features from S20 and Note 20 line up:
1. Samsung Dex (not full features coz need fix at kernel level).
2. Flagship live blur
3. Flagship edge lighting style
4. AirCommand (S pen)
5. LiveDrawing
6. Multy screen resolutions (HD+ - FHD+ - WQHD+)
7. 1000++ system fonts
8. Flagship sound quality and effects
9. Camera features unlocked (pro video etc.)
10. All original A51 features
11. Common tweaks here and there and so many possibility to unlock another S20 features
Bugs:
Minor glitch in pro mode video, and not really remember and deep testing everything, but hopefully still acceptable (hopefully ) but yeah..nothing's perfect, if you found one let's discuss together in A51 telegram group: https://t.me/samsunga51
Hall of Fame:
@MrWaehere for his awesome CRB kitchen
@VDavid003 and his rom TreeUI for my inspiration and countless help
@Yillié and his OFox recovery and also countless help and advise and ideas
@BlassGO and his Dynamic Installer, patches, advise and countless contributions (thanks for making AirCommand even greater lol)
@manudinath and his projects.
@Winb33 for fonts mod
@topjohnwu for Magisk
@ianmacd for multy disabler and TWRP
Stock Kernel Source
PM me if i forgot to mention someone.
Advise and Tips:
- It's normal during first boot if lags occurs, give the ROM some times to settle, finish your setup, update your apps and you good to go..
- It's better to avoid update in Galaxy store related to system app, such as MDE Service Framework, Samsung Core Services etc. It might causing conflict due to mixed up firmware. But anyway it's up to you.
- Please do not complain regarding app missing (getting debloated) and related to debloat. Because it's very hard to acomodate every person's taste. Bloatware is very Objective and absurd for each person and I know it's supposed to be using Aroma installer or any script but i don't have time that much to do that.
Download link:
**when you click this link and downloading, that's mean you're agree to all the consequences and i'm not responsible to anything - do with your own risk**
LINK
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Yillié said:
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Click to expand...
Click to collapse
nah, you have doing so great/ thank you s much for everything.
Testing .

			
				
perro
Ole its already, nice
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
Ia possible wirh This vendor run fingerprint perfectly in havoc
Badger50 said:
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
Click to expand...
Click to collapse
If run for You send details my friend
Someone knows how to pass CTSprofile in magisk with this rom?
gobblefunk said:
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
Click to expand...
Click to collapse
system and vendor.
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
mhm...thanks for everything
jagpanzer said:
system and vendor.
Click to expand...
Click to collapse
Kernel 11 support this ROM?
Magisk 23.1
Download Magisk 706a4922 alpha apk
Download File Magisk 706a4922 alpha apk
apkadmin.com
Changelog magisk 23.1
DOWNLOAD VERSion ALPHA:
Magisk v23.1 (706a4922-alpha)
Changelog:
• Switch to zygisk to execute the deny list,
• Magiskhide has been completely removed
• Denylist Added
• Restart to take effect after changing the switch state of zygisk
• Major changes, some problems may occur, temporarily not pushed to the update channel
Others changes in APK:
[General] supports pure 64-bit devices
-[General] Support Android 12 emulator
-[Zygisk] code injection framework
-[General] Remove MagiskHide
-[General] Support simulator loading module
-[MagiskBoot] supports zImage format
-[MagiskBoot] Add zopfli encoder
-[MagiskInit] supports boot configuration
-[App] Repair installation function will now check whether the script under /data/adb/magisk/ is not updated
-[MagiskInit] supports some Meizu devices
-[MagiskSU] If supported by the kernel, use isolated devpts
-[MagiskSU] Fix pts configuration code, no additional sepolicy rules are now required
-[MagiskBoot] supports v4 boot image header format
-[MagiskInit] Support some OnePlus and Opal devices Oplus.fstab
-[App] The update module needs to be restarted, mark deletion is not allowed
-[App] Delete online warehouse
-[App] Add mount information to the saved log file
-[App] Adapt to Android 12 API level
-[App] Display running waiting pop-up window when hiding/resuming the application
-[Stub] Open source obfuscation function
-[Script] View and display the sepolicy rule folder of the module
-【App】Hide the screen overlay when you need to pop up the window. Android 12+
-[App] Delete the floating bottom bar and change it to a general bottom operation bar
-[General] Support compilation cache
-[General] Added rejection list function
-[App] Delete DoH
-[App] Delete SafetyNet
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Bluetooth connect error
hacker812c said:
Kernel 11 support this ROM?
Click to expand...
Click to collapse
during testing i only test with BF2. you can try
Arya1999 said:
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Click to expand...
Click to collapse
sorry, no time.
Inomjon6940🇺🇿 said:
Bluetooth connect error
Click to expand...
Click to collapse
last time i try with old BT 4.0 earphone was fine and also BT call. will test again, on last build i've made changes and could be broke something

Development [10.04.22] F926B I Dr.Ketan Magisk ROM I OneUI 4.1

F926B I Dr.Ketan ROM
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 @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.
​​​
​​XDA devDB Information​S908 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-04-10
Installation and Download & Notes
Important :
- 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. (hope in future we can get it working on tripped knox device)
- OTA won't work once you root device.
- 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
OneUI 4.1
- S01 - 10.04.2022
Rsrvd 4
ChangeLog S01
Based on F926BXXU1CVC5 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
Prerequisite :
Must have installed firmware F926BXXU1CVC5 (Reported working on F926BXXS1CVCA April scurity patch too)
Rooted device with Magisk (Zygisk) Intallled (Follow steps below in case you have non rooted device)
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!
Spoiler: Brief instructions about how to root
[*](Root F926B)
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
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 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.
[*]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 Install Dr.Ketn ROM Module (New!)
Download app ROM Installar XDA F3 S*.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).
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)
Single click installation
It prevents bootloop with magisk module installation on incompatible formware version by injection bootloop protection 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
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
Boot splash warning removal. At presently available for Exynos (S908B) only, get it from ROM download area. Instructios packed inside.
[*]
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
First !!!
Totally recommended with lots of features !
Dear friends
I have consider to make this ROM as there is no active development on Fold3 and everyone should thank to @pvillasuso for pushing me lol! ROM made within couple of hrs and that without having device so may some bugs expcted, but according testers, stable enough for release.
Also thanks to all testers who have tested and reported. I may not be able to release ROM with every new firmware but will try my best when time permits.
Again thank you all for showing love & trust for Dr.Ketan ROM
Hi,
Perfect Rom!!! thank you Dr.Ketan to provide us with this rom
works like a charm! great work doc!
Installed your ROM, and finally my Fold3 is happy Thank you Dr.Ketan for your excellent work!
Sinus1 said:
Installed your ROM, and finally my Fold3 is happy Thank you Dr.Ketan for your excellent work!
Click to expand...
Click to collapse
will we ever see this rom for the usa version ther sm-f926u??
Important :
ROM S01 reported working on base F926BXXS1CVCA April scurity patch too, so you can first update to new base - Root - Install ROM (follow installation guid above)
.
junevtec said:
will we ever see this rom for the usa version ther sm-f926u??
Click to expand...
Click to collapse
Not possible , this is just for the F926B variant only .
AFAIK for several reasons, such as rooting and unlocking bootloader not available for for sm-f926u
It says installed, but there is no ROM Tool app
klemen241 said:
It says installed, but there is no ROM Tool app
Click to expand...
Click to collapse
Show me magisk module page screenshot
dr.ketan said:
Show me magisk module page screenshot
Click to expand...
Click to collapse
can be a problem that i am on march security update?
klemen241 said:
can be a problem that i am on march security update?
Click to expand...
Click to collapse
If you are on non supported firmware then module itself have turnd off (Check module page) to prevent bootloop. Read installation guide and changelog post and follow it to the letter.
dr.ketan said:
If you are on non supported firmware then module itself have turnd off (Check module page) to prevent bootloop. Read installation guide and changelog post and follow it to the letter.
Click to expand...
Click to collapse
That must be it. I will update official firmware and try again. thanks
ps: rom works great. For now no problems. Only in the battery bar addon, has ON and OFF switched haha.
Thanks for the ROM.
Is Samsung Health and Galaxy Watch pairing working properly?
mcn1970 said:
Thanks for the ROM.
Is Samsung Health and Galaxy Watch pairing working properly?
Click to expand...
Click to collapse
Yes , both working properly

***CLOSED*** [ROM] Project Unbound V2.1 [G98X]-[DVL3]-[OneUI5.0]

PROJECT UNBOUND
Hello XDA Community, I present the newest Project for the Galaxy S20 series...Project Unbound. This Project is a full port of the Galaxy S21 firmware, currently G998BXXS5DVL3.
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE; IT IS YOUR CHOICE AND RESPONSIBILITY FOR WHAT YOU DO WITH IT. IF YOU COME TO ME AND COMPLAIN, I WILL LAUGH AT YOU.​
Spoiler: View Unbound Information
Spoiler: Supported Devices
SM-G980F
SM-G981B
SM-G985F
SM-G986B
SM-G988B
Spoiler: Base
G998BXXS5DVL3
Spoiler: View Unbound Features
Spoiler: View Kernel Information
This ROM currently uses the Stock Samsung Kernel.
The clean source code of the Kernel used in this Project can be found here.
Spoiler: View CSC Information
Spoiler: View selectable CSC Features
Call Recording
Shutter Sound Menu
Real-time Network speed
App Lock support
Anti-Phishing support in Samsung Messages
Anti Malware feature disabled in Device Care
Colour of Days in the Calendar app.
Camera enabled during calls.
Recent App protection
The default homepage in Samsung Internet is set to this
Knox Guard support is disabled.
Enhanced Image Quality.
eSIM support.
Spoiler: View CSC Base
G998BXXSDVL3
Spoiler: View ROM Features
Spoiler: Settings/Services & other Features
Knox disabled
Disabled file encryption
Disabled process authentication
Disabled VaultKeeper
Disabled SCS
Disabled esecos daemon
Disabled AVB
Loads of additional camera features
Loads of additional Single Take features
Full OneUI 4.1 experience
Fully enabled screenshots in secure apps (Including DRM-protected apps). Thanks @edzamber
Disabled Watchdog, thanks @ananjaser1211
Official Status in Settings
Unbound Information & Banner in Software information
Spoiler: Aroma Features
A new menu containing many additional selectable features exclusive to UnboundROM.
Integrated ROM control into the installation.
Wipe Options (Dirty Flash or Clean Flash)
CSC Features (Add a range of CSC features during the installation)
Boot Animation options (Choose to either stay stock or apply our V2 animation)
Embedded Magisk Installation (Optional to choose Magisk Canary, Magisk Alpha, or stay Unrooted)
Hosts options (AdAway installation, with the ability to backup & restore your previous hosts file)
Spoiler: Generic fixes
Galaxy Watch Pairing
Bluetooth pairings
Single Take
Portrait Mode
64MP Super Resolution
SafetyNet (must use kdrag0n's module)
Private Share
Secure WiFi
Spoiler: Misc Tweaks & Mods
Custom Boot logos for each device, thanks @dutchman89
Unbound boot animation by @dutchman89
A large number of prop tweaks for battery, data, performance, and Dalvik
Netflix fix (HD is now fixed)
Frame buffer increased to help with gaming
Spoiler: The Bug list
RED = The Bug needs logs.
ORANGE = The Bug has been reported, and the error has been found; a fix is expected in a future release.
GREEN = A fix file has been provided for this bug and will be implemented in the next available rom release.
Facial Recognition (The error has been found, and a fix is being internally tested. Facial recognition works on G988B.)
Spoiler: View Installation Information
Spoiler: Stock ROM to UnboundROM
NOTICE: The steps below will trip Knox & possibly void your Warranty; following these steps will perform a mandatory data wipe due to Bootloader status changes, so please make sure you back up any/all of your important files somewhere else other than your phone's storage.
STEP 1: UNLOCKING THE BOOTLOADER:
1. Enable Developer Options; you can do this by going to Settings -> About Phone -> Software Information -> Tap "Build Number" 7 times and enter your phone's pin if prompted.
2. Open Developer Options and enable the "Allow OEM Unlocking" option.
3. Shut down your phone.
4. Connect your phone to your PC or connect your headphones to boot into Download Mode with the combination (HOLD VOLUME UP + VOLUME DOWN)
5. Press and hold the Volume up button (Bootloader unlock screen)
6. Once on the Bootloader unlock screen, press the Volume up button to confirm the unlock (WARNING: This action will perform a factory reset, and the phone may restart once or twice (this is normal), you will soon boot back into the Setup wizard, skip this initial setup there is no need to login to anything.)
7. Enable Developer options again (Follow Step 1) and check that the OEM toggle is enabled & greyed out.
8. Congratulations, you have unlocked the Bootloader and are ready to continue to the next step.
STEP 2: FLASHING TWRP + PATCHED VBMETA:
1. Download this TWRP+VBMETA file to your PC.
2. Boot your phone into Download Mode.
3. Single press Volume Up to start ODIN Mode
4. Load ODIN on your PC.
5. Go to options and untick "Auto Reboot..."
6. Select the (USERDATA) slot and select the downloaded file from Step 1.
7. Click start on ODIN and wait for it to finish.
8. Upon a pass, keep the phone connected to your PC or headphones, then hold the Power button + Volume down button; as soon as the screen goes black, hold the Power button and Volume UP button.
9. You should now be in TWRP.
STEP 3: INITIAL TWRP STEPS:
1. Do a complete data wipe (Wipe -> Format Data -> Type "yes")
2. Reboot back into RECOVERY (Reboot -> Recovery)
3. Download the latest Unbound release and copy it to your phone (PC to Phone) or a USB OTG device, or if you have SD Card, you could store it on that.
STEP 4: INSTALLING UNBOUNDROM:
1. In TWRP, click "Install" if using a USB OTG device, press "Select storage", and press "USB OTG" or "SD Card" if using an SD Card.
2. Browse to the location you stored the ROM zip.
3. Swipe to confirm the flash.
4. Follow the on-screen instructions, select your desired features, and wait for the ROM to install.
5. When the ROM has finished installing, press "Save Logs" to send to the Developer if you bump into any issues.
6. Reboot into the System.
7. Do the setup wizard as usual.
8. Congratulations, you have successfully installed UnboundROM and are good to go! Enjoy!​
Spoiler: Other ROM to UnboundROM
CLEAN FLASH (RECOMMENDED)
1. Boot into TWRP
2. Load UnboundROM zip
3. In Wipe Options, select "Clean Install"
4. Follow the on-screen instructions, and wait for UnboundROM to be installed.
5. Boot into the System.
DIRTY FLASH (NOT RECOMMENDED)
A dirty flash may or may not work, as we cannot guarantee that flashing UnboundROM over the top of another ROM will cause any issues; so, therefore, we do not recommend it, but of course, it is your device and your responsibility so please feel free to make your own choice here but please do not come to our chats and complain about issues caused from a dirty flash over another custom ROM.​
Spoiler: Unbound version update (V1.1 to V1.2 etc)
When updating versions of Unbound, it is very dependent on what version you are currently running and the version you want to update to, an example being if you are on V1.0 and want to update to V1.1, a dirty flash would be fine unless stated in the OP otherwise.
However, if you say you are upgrading the OS version, i.e. OneUI 4 to OneUI 5, you would need to update your device to the latest firmware first via SamFirm/Frija/hadesFirm etc.
Please take note of the changelogs of each version as they will state the requirements to update and if a clean flash will be required or not.
When a dirty flash is impossible, and you need to update your device to the latest/specified firmware, please follow the recommended steps below. These steps will assume you are already running UnboundROM:
1. Download the latest/required firmware using either samFirm, Frija or hadesFirm
2. Unzip the firmware zip and remove the .md5 from the end of each file name.
3. Boot your phone into download mode, load Odin, turn off Auto reboot options, and load the files into the relevant slots. ( BL = BL, AP = AP, CP = CP, CSC = HOME_CSC) (IT IS IMPORTANT TO USE "HOME_CSC" TO KEEP YOUR DATA INTACT)
4. Press start, and wait for it to complete.
5. When complete, keeping the phone connected to the PC, boot your phone into TWRP, and load the latest/downloaded rom.zip
6. Follow the on-screen instructions and wait for the ROM to be installed.
7. When the installation is complete, press the "Save Log" button in case of any issues.
8. Congratulations, you have successfully updated your version of UnboundROM. Boot to the System and enjoy!​
Spoiler: View Changelog
Spoiler: V2.1
Updated to G998BXXS5DVL3
Added the Unbound Kernel
Removed all Christmas theming.
Removed embedded Canary (Alpha works better with Banking Apps)
Spoiler: V2.0 - Christmas Edition
The Unbound Christmas Theme has been applied.
Christmas theme includes a new boot animation, new logos and new boot logos.
Spoiler: V2.0.2
The device-specific files have been revised and updated.
Support for G985F has been fixed.
Spoiler: V2.0.1
The issue causing a green screen after using 10x zoom has been fixed.
The issue causing a forced crash after taking a Night Mode photo has been addressed.
An issue causing a crash during the post-processing of a photo has been fixed.
Spoiler: V2.0
Updated base to G998BXXSDVK1
I have fixed some errors where 120Hz would not be applied.
Applied CloudflareDNS settings globally.
I separated the Modes & Routines app into another option in the Debloat section instead of being removed when selecting to remove Bixby.
Spoiler: V1.5.0
Updated base to G988BXXUFFVI7
Fixed Netflix HD/HDR
Add some new Network tweaks
Add Burn In Protection
Spoiler: V1.4.0
Updated base to G998BXXU5CVGB
Fixed camera issue
Spoiler: V1.3.0
Updated base to G998BXXU5CVF2
Integrated ROM control into the main installation
Applied low brightness fix.
Spoiler: V1.2
Updated base to G998BXXU5CVDD
Implemented Portrait Mode Fix
Implemented Single Take Fix
Added a bunch of Single Take & Camera mods by default.
Misc fixes.
Spoiler: V1.1
Updated base to G998BXXU4CVD2
Implemented Night Mode fix
Fixed missing Secure Folder
Fixed missing USSD code dependencies
Updated embedded Magisk versions to the latest
Spoiler: V1.0
Initial Release
"Useful Links" removed by moderator
Download links removed by moderator
Spoiler: Unbound Credits
Dutchman89 - Boot Animation, custom boot logos, and other branding logos. Thanks a ton.
Anan1211 - Endless help throughout the years
corsicanu - Endless service throughout the years & official TWRP
Topjohnwu - Magisk Developer
Nathan - Aroma colouring
Samsung - Base Firmware
Andrei - Help & Support
All of the Unbound testers team
If I missed your name and you feel you should be credited, please DM me on Telegram with why you should be credited.
Reserved
Reserved
thanks
Bundle of Thanks
So with this we can have Google Discovery in Homescreen?
Yes.
Hello, how is this comparing with beyond rom; is the SoT better, performance wise, customisation, etc...? thank you
john S7 said:
Hello, how is this comparing with beyond rom; is the SoT better, performance wise, customisation, etc...? thank you
Click to expand...
Click to collapse
Give SoT some time, only released yesterday.
Unbound is full S21 Firmware, Beyond is stock rom with root.
I could not get secure folder to work. Is there a patch?
Will romcontrol be in the plans?
For people who are not familiar with intricacies of Galaxy line firmwares - what are differences between S20 and S21 firmware? What is the benefit of switching it?
So, everything works? All cameras, 120Hz, Google Pay?
I'm inclined to try it, but my phone is well configured now, so i'm a bit sceptical.
myaslioglu said:
I could not get secure folder to work. Is there a patch?
Click to expand...
Click to collapse
Fixed in V1.1 in testing
ZaraZwracam said:
For people who are not familiar with intricacies of Galaxy line firmwares - what are differences between S20 and S21 firmware? What is the benefit of switching it?
Click to expand...
Click to collapse
More features
pintasmapila said:
So, everything works? All cameras, 120Hz, Google Pay?
I'm inclined to try it, but my phone is well configured now, so i'm a bit sceptical.
Click to expand...
Click to collapse
Read the bugs list
The code *#1234# does not work.
S20 Ultra
Thank you for this! I'll try flashing it later
Is a degoogled flavour planned? Thats one thing I'm really missing at the moment
endim8 said:
Thank you for this! I'll try flashing it later
Is a degoogled flavour planned? Thats one thing I'm really missing at the moment
Click to expand...
Click to collapse
I hate google too
Shame Samsung firmware heavily relies on Google.
I dont get how some people think theyre somehow "winning" by getting rid of google...i have never understood it...all youre literally doing is making your device, and therefore life, less functional
Reminds me of that ROM some dev cooked up for my old Pixel 2XL and other devices that was so paranoid focussed that on their FAQ it actually said to wear baseball caps to avoid detection in real life and keep your phone in a farady bag when not using it...im not even joking here
Personally all the same level of bonkers thought processes to me, seems like everyone who feels this way should go and join a militia in Michigan and bang on about the "new world order"
If you dont like google apps, then go and buy an iphone and see how much you like that.....ill keep your seat warm here for when you get back
Google isnt the problem, its what people cough up on social media and communications thats the problem....and i cant believe people havent figured this out by now...stop blaming google, they only use what you voluntarily give them...so please stop blaming Google, its your fault, stop sharing so much... some people cant help themselves, oversharing has become a cancer...
Me, ive been interconnected since BBS days, and to date theres not even one picture of me out there, or any of my personal info, probably because i dont think im important enough to bother people with my inane life...sadly this restraint is not shared by most of society...people like to vomit everything they do in life onto the web, with pictures
And then they want to bang on about privacy and the erosion of such
I weep for humanity, youre the problem...
Can guys that installed this rom write their opinion about it instead of writing "philosophy" about things that have nothing to do with the rom?

Categories

Resources