Develop Bugs

[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)

How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me

reserved.

Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?

dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.

for step 6, can we transfer the file via SD card?

afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck

s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.

I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse

s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.

Guide updated with more details

Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse

s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.

I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!

s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.

Guide updated and added flash TWRP instructions

afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.

ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.

afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc

Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.

s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.

[Guide] Root Galaxy A10 Magisk prenormal rmm/kg state (October Patch- later)

Hi All this is just a quick tutorial to help you all root your devices, on later firmwares
This 100% works ive done it over and over without any problems. I am currently on october patch latest firmware for my A105FN. As you may know Samsung have now added extra security meaning even if you have already unlocked your bootloader after you patch the firmware with magisk, flash patched firmware and reboot you will be greeted with that dreadfull message, Only official binaries allowed and your device will be locked and wont boot untill you reflash stock firmware again. The below will help get you out of the prenormal kg state, and save's you a 7 days waiting period as we dont have any TWRP available for our device at this time. Also note due to the extra security magisk cant be flashed with the whole firmware no more, as each time you flash the firmware your back at square 1.
Note: You will need 7-zip - google is your freind
1. Download odin: https://odindownloader.com/download/odin3-v3-13-3.
2. download the latest stock firmware for your device via SamMobile
3. Download latest Magisk Manager - https://www.google.co.uk/amp/s/forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
4. Flash latest firmware via odin and let device boot up and finish setting up.
5. Grab Your Firmware AP_A105FXXXX.tar.md5 remove the md5 so its a tar file makes it easier to work with. Copy it to your device storage.
6. Install latest magisk manager, and open check advanced settings to make sure recovery is checked, select install image / patch image and select the AP file you put on your device, magisk will patch and save as magisk_patched on your internal storage. Copy this back to your pc and extract it.
7. Download this https://forum.xda-developers.com/attachment.php?attachmentid=4818715&d=1568308074 thanks to @droidzer1 and extract the vbmeta.img.
8. Make a new folder on you pc it's temporary so you know where your files are. From the Ap magisk_patch.tar you extracted, copy the boot.img, recovery.img, and the downloaded vbmeta.img from step 7. And place them in the new folder you created, using your mouse select all 3 and right click select 7-zip add to archive, select tar format and name it magisk.tar.
9. Now we have all the files ready back to your device, if your bootloader is already unlocked skip this step and move to the next. For those that havent unlocked there bootloader go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it, if the OEM switch is not there proceed to step 10. If it is and you enabled it it might ask you to factory reset if not it will be this way to complete the unlock bootloader.......
switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
10. Remove any account you have on your device go to settings, look for time and date automatic time zones, turn it off and set date back 8 days from now (example 30th today change date to 22nd) restart device. Now go straight back into automatic time zones settings and turn it back on. Again reboot device, when device reboots turn it off. You can now enter download mode and it should say checking instead of prenormal that means you good to go. Those of you that had no OEM switch in developer mode please now check.... if it's there enable it and go back to step 10 unlocking bootloader then proceed to step 11.
11. Open odin and select in the ap tab the magisk.tar you created earlier. Plug in your usb whilst holding vol-up and vol-down together to boot into download, press vol-up to proceed. Press start on odin and soon as it finishes and device reboots and you see the bootloader message hold power and vol-up until into stock recovery, select wipe factory reset then select reboot device, this the same as soon as you see bootloader unlocked message hold power and the vol-up together this time count to 7.... and release. Phone wont boot it will go blackscreen and reboot, dont worry this is normal, again do the exact same at bootloader unlocked msg screen hold power and vol-up count to 7... release, now phone will boot and you can set it up.
Note: you will need to reinstall magisk manager and on 1st open it will ask do to additional setup, let it do its thing, then device will reboot,
Remeber every time your device reboots you will have to do the power and vol-up to boot system with root.
I hope this guide help you and a big thank you to @afaneh92 for his original guide

thnaks man
how do i install twrp?
if it is possible, can i flash GSI?

tttt7hhhhjjjk said:
thnaks man
how do i install twrp?
if it is possible, can i flash GSI?
Click to expand...
Click to collapse
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.

mikeyb123 said:
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.
Click to expand...
Click to collapse
thanks for the fast reply man :good:

I gave up rooting this phone, ended up bootloop 3 times and always has to flash it to get the phone working again

timba123 said:
Any chimeratool tricks for no oem unlocking in developer options? On a102u1
Click to expand...
Click to collapse
no.. chimera tool cant unlock the bl on usa variants

hello Thanks for this method but not working after install again magisk manager , say app magisk is not installed and not root
When I was creating the magisk_patch file with magisk manager go to advanced settings and check recovery mode
is it correct?

S20 SM-G980F Exynos bootloop after restarting, (Even after flashing !)

I have rooted s20 Exynos with Magisk ,every thing was working fine and for a moment my device stuck into Bootloop after I have done a restart for no reason !
First I tried factory reset from recovery mode and nothing happen then I tried flashing the latest official firmware but nothing happened too still stuck on animation screen and restarting loop
( Attached link for the video of bootloop )

ahmedamr002 said:
I have rooted s20 Exynos with Magisk ,every thing was working fine and for a moment my device stuck into Bootloop after I have done a restart for no reason !
First I tried factory reset from recovery mode and nothing happen then I tried flashing the latest official firmware but nothing happened too still stuck on animation screen and restarting loop
( Attached link for the video of bootloop )
Click to expand...
Click to collapse
Any help??

Did you flash dm-verity zip?

Kenora_I said:
Did you flash dm-verity zip?
Click to expand...
Click to collapse
No i didn't , what is dm- verity zip ?
excuse me i'm still newbie

jesec said:
Applicable Models:
All Exynos models including but not limited to:
SM-G980F or SM-G980F/DS (S20)
SM-G981B or SM-G981B/DS (S20)
SM-G985F or SM-G985F/DS (S20+)
SM-G986B or SM-G986B/DS (S20+)
SM-G988B or SM-G988B/DS (S20 Ultra)
All BL-unlockable Snapdragon models including but not limited to:
SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
SM-G981N (S20, Korea)
SM-G986N (S20+, Korea)
SM-G988N (S20 Ultra, Korea)
Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .
Frequently used key combinations of S20 series:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S20 series uses A-only partition which means there is only one set of system partition.
3. S20 series uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
6. Remember your model and CSC.
View attachment 4990047
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
View attachment 4990049
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
View attachment 4990051
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
View attachment 4990053
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.
You can also download a KERNEL TAR archive of your version here:
Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
and then skip to Step 6.
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
View attachment 4990061
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
View attachment 4990063
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
View attachment 4999117View attachment 4990073View attachment 4990075View attachment 4990079View attachment 4999119
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
XDA:DevDB Information
Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20
Contributors
jesec
Version Information
Status: Stable
Created 2020-04-08
Last Updated 2020-04-08
Click to expand...
Click to collapse
You disabled secure boot with a patched vbmeta.img?
Follow this guide for root.

ahmedamr002 said:
No i didn't , what is dm- verity zip ?
excuse me i'm still newbie
Click to expand...
Click to collapse
Disables the /system editing protection, sorry that dosent matter with magisk.

Kenora_I said:
Disables the /system editing protection, sorry that dosent matter with magisk.
Click to expand...
Click to collapse
can you tell me how to flash dm verity file ?

Update : i have flashed official firmware, still the same problem, please anyone help

Ha
ahmedamr002 said:
Update : i have flashed official firmware, still the same problem, please anyone help
Click to expand...
Click to collapse
I have the same problem, did u fix it?

[GUIDE][ROOT][UNROOT] Rooting/UnRooting A505FN

In this post I'll describe my experience with Root and Unroot of Samsung Galaxy A505FN/DS (DualSim)
I wrote threads on XDA and called for help but I didn't always get it, so I had to look for solutions myself, which I'll share now.
[Root]​
[READ BEFORE START]​Bricking Samsung devices is reallyyyy hard - but If you mess something up - I'm not responsible for it.
Root, although it gives you new features, also takes away old ones
- Your Knox will be broken - there is no option to skip it, apps like Samsung Pass will never work again (even after unroot).
- Some applications will not be available in Google Play (e.g. Netflix), you can use another store such as Aurora Store, but it does not give a 100% guarantee that you will install the application you need.
- You won't pass SafetyNet attestation - you can use Magisk (Zygisk to be exact) + denylist modules for this, but it also doesn't always work (in my example it didn't work on Stock ROM).
- Unstable system... Almost, because as long as you root your phone, nothing should happen - however, I've already more than once downloaded a module for Magisk and after installing it the phone wouldn't reboot or the phone reset itself at least once in a few days, then you have to disable the module or do a Factory Reset, and doing a backup every time you install a module is not convenient.
- Banking apps - in my case, I wasn't able to add my card to Google Pay or use autocomplete in Google Chrome when I wanted to enter my credit card information. I was also unable to pay via NFC.
[START]​1. Make a backup - Rooting will earse all data that you have collected on your phone! You can make backup in your phone settings.
[Samsung Cloud] Settings -> Accounts & Backup -> Data with backup (Under Samsung Cloud Tab) -> Select Apps to backup | Then backup files & photos on Dropbox, Onedrive, Google Drive
[Google] Settings -> Accounts & Backup -> Data with backup (Under Google Drive Tab) -> Click "Make Backup now"
2. Enable Developer Options - Settings -> Phone - Information -> Software information -> Click about 10 times on "Version number" until you see the text "Developer mode has been activated" or until you have to enter the lock code
3. Unlock OEM in Developer Options - Settings -> Developer Options (on far bottom) -> Check "Unlock OEM"
4. Turn on USB Debugging - Developer Options -> Check "USB Debugging"
5. Download & install Samsung Drivers
6. Download ODIN
7. Download Platform Tools
8. Download OrangeFox (only for full root) (Credits to @Enzoaquino)
9. Download MultiDisabler
10. Turn off the phone, when it is turned off press Volume UP and Volume DOWN simultaneously and connect the phone to the computer using the USB cable and wait to screen turn on
11. You can see instructions on screen -> Long Press Volume UP, on next screen confirm unlocking bootloader by clicking Volume UP (All Your data will be earsed now!).
12. Your phone will be restarted two times, wait, after that, disconnect your phone from PC and configure your phone (you need connect to the internet) and do one more time step 2., 3. and 4., but after doing step 4. connect your phone to PC and wait to dialog box pop in -> hit "Always Allow from this PC", and then hit "Allow"
13. Open folder with platform tools (you need to see adb.exe file) and type "CMD" into directory path box and hit enter
{
"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"
}
13. You should see a command line window now - type "adb devices" and hit enter, this should print your android device connected to Your PC
14. If You see Your device, type "adb reboot download" and wait for Your phone to restart
15. When Your phone showing a "blue" screen with text "Downloading...", open ODIN on Your PC
Similar to this
16. In ODIN, Click AP button and pick OrangeFox file that you downloaded earlier
17. Go into "Options" tab and uncheck "Auto Reboot"
18. Click "Start"
19. After ODIN finish flashing, let a phone be still connected to Your PC, press Volume DOWN + Power button for 7 seconds and after Your screen goes black, fast press Volume UP + Power until You see OrangeFox Logo (on Orange Background)
20. Format Data by clicking Bin icon o bottom of Your screen, then click "Format Data" tab and type "yes" to confirm.
21. After that, copy MultiDisabler (multidisabler-samsung-3.1.zip) from Your PC to Your Phone and click this file on your phone in OrangeFox
22. Swipe to install this file
23. Do not click on "Reboot System"! You need to click "Back" then click last icon on bottom of your screen (3 - dash), then click "Reboot" and then select "Recovery". Your phone will reset and You can see that its stuck on Samsung logo -> wait a while and press Volume DOWN + Power for 7 seconds, Your phone will reset and turn on properly.
24. Configure, Connect to internet and open Magisk App (with default icon), It will say that "Magisk needs to download additional files and complete the installation" -> allow
25. After that, turn on Magisk App one more time, it will say the same message that on step previous -> allow
26. Open Magisk App, click "Update" button under "Magisk" panel (not on Magisk App panel) and under "Options" tab check "Recovery Mode" and click "Next" - wait until You will see "Reboot Device" button on bottom right of Your screen- click this button and after reset open Magisk App and check if Magisk App is updated too - if not, click update. (Thanks to @gosc747 for reminding me about this)
27. Your Phone should restart and... You have root on Your Phone, congrats!
[UnRoot]​
[READ BEFORE START]​- This will do Factory Reset
- You need to find a ROM that fits Your phone -> Here is the site that I recommend to download ROM for Samsung A505FN (A lot of ROMs, Full speed download and.. FREE).
What If I pick wrong ROM?
- It will not install but Your phone will still work,
- Some functions can stop working (example: Your screen will not autorotate)
[START]​So, after You pick a Samsung A505FN on that site, You need to know CSC Code for Your phone... But where You can find it?
If You still have original ROM:
1. (On Your phone) Go into settings -> Phone - Informations (on far bottom) -> software information -> Provider software version
2. here you will have your code
3. Type first part of that into Search Box on site that i provided
4. Download Selected ROM, repack this in folder of Your choose
5. Connect Your phone to Your PC
6. open Command Line (like in step 13. in rooting) and type "adb reboot download"
7. After reset, open ODIN, and place all files from Your ROM here
8. Click Start
9. Your Phone will reset automatically, after it's boots up, disconnect phone from pc and turn Your phone off
10. Press Volume UP + Volume DOWN and plug-in Your usb cable connected to Your PC
11. You will see "blue" screen, long press Volume UP and confirm Locking Bootloader by clicking Volume UP (this will earse all Your data).
12. And.. done!
Ask Something If You Want​I try to help​

Hmmmm why not use a modified kernel instead of patch recovery? When using patched recovery, you need to figure out the right button combinations to boot to system or recovery,whereas when you use patched kernel you can just simpky boot without button combinations.

JuanTamqd21 said:
Hmmmm why not use a modified kernel instead of patch recovery? When using patched recovery, you need to figure out the right button combinations to boot to system or recovery,whereas when you use patched kernel you can just simpky boot without button combinations.
Click to expand...
Click to collapse
I mean yee, if u wanna stay with original ROM but just have Magisk installed, then patching custom kernel is good idea - but if u want install custom ROM or something, its good to have custom recovery (besides the fact that you can patch custom kernel via custom recovery)

@TheWolf_Prod
I tried your guide on my Samsung Galaxy A50 (SM-A50FN / DS), I confirm it works
After entering Magisk, I choose to run in Recovery, it starts, but it does not go into Recovery, but normally on the phone
Tell me, do you know how to do this, how do I update to Magisk v24.3 via "Select and patch file"?
Because I downloaded from another TWRP and ROOT guide and I also have a problem with it
And I do on your tutorial as I did on my previous TWRP tutorial:
I choose the method "Select and patch a file" creates the AP magisk _patched for me, I transfer it to my laptop, turn off the phone and enter Download mode, run Odin (I deselect auto start), add files BL, AP (magisk_patched), CS, CSC, gives me start, loaded, exiting, from Download mode, starting Recovery mode, giving, restarting and bootloop is on

~ "I choose to run in Recovery, it starts, but it does not go into Recovery, but normally on the phone"
I guess this is Samsung's "unique feature" - the only option to enter OrangeFox/TWRP is turn phone off -> press Volume UP + Power and when phone vibrates, plug USB cable connected under PC to phone.
~ "After entering Magisk, I choose to run in Recovery, it starts, but it does not go into Recovery, but normally on the phone"
So - on my phone I noticed this problem:
Sometimes when I reset my phone (Either manually or through a dead battery) then after restarting - I lost ROOT privileges. Therefore, if for some reason you need to reset your phone - do it preferably through Magisk (main page -> click the "refresh" icon -> Reboot Recovery) then you can be sure that your phone will boot with ROOT privileges
If your phone has reset itself or you forgot to do it via Magisk - turn phone off -> press Volume UP + Power and when phone vibrates, plug USB cable connected under PC (or any device where you can copy files from it) to phone - then in OrangeFox/TWRP menu You need to click "Reset Recovery" and unplug USB Cable.
~ "Tell me, do you know how to do this, how do I update to Magisk v24.3 via "Select and patch file"?"
So, I don't use TWRP - if You have OrangeFox all You need to update Magisk is just click "Update" in Magisk App.
I read this on this website:
Choose “Select and Patch a File” in method, and select the AP tar file (from Your ROM)
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
If it still doesn't work then try to install Ypur ROM without the Magisk patch - maybe you downloaded the wrong ROM?

TheWolf_Prod said:
So - on my phone I noticed this problem:
Sometimes when I reset my phone (Either manually or through a dead battery) then after restarting - I lost ROOT privileges. Therefore, if for some reason you need to reset your phone - do it preferably through Magisk (main page -> click the "refresh" icon -> Reboot Recovery) then you can be sure that your phone will boot with ROOT privileges
If your phone has reset itself or you forgot to do it via Magisk - turn phone off -> press Volume UP + Power and when phone vibrates, plug USB cable connected under PC (or any device where you can copy files from it) to phone - then in OrangeFox/TWRP menu You need to click "Reset Recovery" and unplug USB Cable.
Click to expand...
Click to collapse
I wonder where the problem
TheWolf_Prod said:
So, I don't use TWRP - if You have OrangeFox all You need to update Magisk is just click "Update" in Magisk App.
I read this on this website:
Choose “Select and Patch a File” in method, and select the AP tar file (from Your ROM)
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
If it still doesn't work then try to install Ypur ROM without the Magisk patch - maybe you downloaded the wrong ROM?
Click to expand...
Click to collapse
I have OrangeFox at the moment, I've seen this link before and read it, unfortunately, it doesn't work, bootloop pops up and OrangeFox recovery is missing.
I have an official ROM:
Version Android: 11
Changelist: 22264509
Build Date Mon, 14 Mar 2022 03:20:54 +0000
Security Patch Level: 2022-03-01
Product code: XEO
PDA: A505FNXXS9CVC2
CSC: A505FNOXM9CVB1

When my phone has reset itself or I do it via Magisk, my device is stuck on the lock screen. Whenever I unlock my device, the screen turns black, not responding, or auto restart.
I tried to solve the issue by booting into Fox recovery, then turning on/off Magisk core, or using the Fox Reboot function to reboot into System or Recovery but it is impossible to solve the problem.

bellial7 said:
When my phone has reset itself or I do it via Magisk, my device is stuck on the lock screen. Whenever I unlock my device, the screen turns black, not responding, or auto restart.
I tried to solve the issue by booting into Fox recovery, then turning on/off Magisk core, or using the Fox Reboot function to reboot into System or Recovery but it is impossible to solve the problem.
Click to expand...
Click to collapse
flash pass reset zip

Hey would unrooting the device enable banking apps again?

How To Guide Samsung Galaxy A54 5G [Root Stock ROM with Magisk]

WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel

Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app​

V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171​"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.​"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.​"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)​"App > Installed" shows the currently installed version of the Magisk app​
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations

Hello,
What about Knox with this method ??
Thanks

leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.

Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.

terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.

Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!

draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.

So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?

Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.

sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?

Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself

LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.

knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..

bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.

bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.

Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..