yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A54 5G] V0latyle:
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​
[Samsung Galaxy A54 5G] knighToFdemonS:
thank you, ive adjusted the how-to to your recommendations
[Samsung Galaxy A54 5G] leosoftstudios:
Hello,

What about Knox with this method ??

Thanks
[Samsung Galaxy A54 5G] knighToFdemonS:
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.
[Samsung Galaxy A54 5G] terry_mccann:
Why would someone root it? One UI is the most perfect Android imaginable....

Opinion,of course.
[Samsung Galaxy A54 5G] knighToFdemonS:
Funny how this pops up in every thread here :D 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? :D

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.
[Samsung Galaxy A54 5G] draykhar:
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!
[Samsung Galaxy A54 5G] knighToFdemonS:
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.
[Samsung Galaxy A54 5G] urbanman2004:
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?
[Samsung Galaxy A54 5G] sameog:
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.
[Samsung Galaxy A54 5G] urbanman2004:
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?
[Samsung Galaxy A54 5G] LidelnFR:
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
[Samsung Galaxy A54 5G] knighToFdemonS:
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.
[Samsung Galaxy A54 5G] bizkit_120:
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
[Samsung Galaxy A54 5G] bizkit_120:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
[Samsung Galaxy A54 5G] urbanman2004:
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.
[Samsung Galaxy A54 5G] urbanman2004:
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.
[Samsung Galaxy A54 5G] bizkit_120:
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..
[Samsung Galaxy A54 5G] fredapied:
Same issue for a French A54

Don't know how to fix that annoying nag screen....

i haven't this with the stock rom...
[Samsung Galaxy A54 5G] LidelnFR:
Yes same here Fred (FR + Bouygues), and no issue with stock

I tried a few queries like "force reset network capabilities" things like that, to no avail

It's still manageable (switch app twice after clicking "redémarrer", because after clicking this button the screen is like frozen), but painful yet

I know very well OP is not responsible for the firmwares we can download from samfrew or sammobile, so I'm not throwing any stones here :)

However, would loooove to get rid of that glitch! ^^

Maybe it's specific to French firmwares that are broken somehow, and we must wait for an update from Samsung.

Or maybe we should have downloaded an older firmware, and proceeded afterwards with an update directly on the phone... 🤔 too lazy to try, I must confess
[Samsung Galaxy A54 5G] fredapied:
I tried many things like you with no luck ( SFR too) install/unistall Carrier from google, remove APN parameters.

i will run under stock rom until someone find the trick.

hope he/she will read this thread
[Samsung Galaxy A54 5G] Nitorac:
Hey, I had the same issue, you can disable the system packages responsible for that nasty popup. Via adb shell or any terminal emulator :

su
pm disable com.samsung.android.sdm.config
pm disable com.samsung.android.cidmanager

You can also use any debloater to blacklist packages named (in French): "Mise à jour configuration"

The only weird thing I see is sometimes a random reboots that happens after a manual reboot, but it's okay.

EDIT: I know it's not the root of the issue but only a small patch on it, but it makes magisk usable until a definitive patch will be out
[Samsung Galaxy A54 5G] fredapied:
@Nitorac

thanks for your answer and guide.

i spent all my day trying to make it work...

i'm now using the stock rom but i will try your trick asap.

perhaps should we report this bug on Magisk dev github ?
[Samsung Galaxy A54 5G] urbanman2004:
Are you talking a/b downgrading from the current firmware on my A54 device by using Odin to flash it? That's the only logical method that I could think of w/o unlocking the bootloader...
[Samsung Galaxy A54 5G] Nitorac:
It's maybe not Magisk's fault, it could be a knox related issue for example, one should investigate that and if it's really coming from Magisk, then I think we could report the bug.
[Samsung Galaxy A54 5G] fredapied:
@Nitorac :

could it be only a french issue ?

this rom is not a XEF only like before but an EUX so, a lot of foreign users should report this bug...

a noticed that the root procedure is a bit different than other android versions :

before this A54 i was owning an A40

with this phone i just a had to patch the boot.img located in Ap file with magisk and then flash this boot.img zipped in a tar file with odin and the root was done.

with this A54 and android 13, i had to flash all this big AP file.

i tried the old good procedure with this new A54 with no luck (just flashing the boot.img)

and i neved had an issue like this about carrier update before.

like you said, perhaps it's not a magisk issue, knox, or just the carrier that detects root ?

Could we backup the carrier settings from a stock Rom and then over write it to the rooted rom ?
[Samsung Galaxy A54 5G] googlephoneFKLenAsh:
All US version samsung phones, be it unlocked version or carrier versions, are not eligible for bootloader unlock. There are some paid 3rd party service to unlock bootloader like the A53.
[Samsung Galaxy A54 5G] urbanman2004:
Are you sure regarding your assertion?
[Samsung Galaxy A54 5G] googlephoneFKLenAsh:
100% sure unless you are talking about old samsung phones before 2017. I am talking about a fact, not assertion.

No us version samsung phones after galaxy S7 are eligible for official bootloader unlock.
[Samsung Galaxy A54 5G] Nitorac:
I agree !

I also have observed this and I was wondering if it's related. I googled some forums to create a single-CSC rom with XEF instead of EUX but for now I have no clues.

I think it worked that way on A40 because you had already applied a custom vbmeta and samsung multidisabler.

On this rom, when giving to Magisk the full rom, it patches the boot.img and vbmeta.img

> like you said, perhaps it's not a magisk issue, knox, or just the carrier that detects root ?

I don't know, maybe when I'll have time I could investigate that.

> Could we backup the carrier settings from a stock Rom and then over write it to the rooted rom ?

It could work yes !
[Samsung Galaxy A54 5G] Nitorac:
I'm new to Android firmware patching, ecosystem, compilechain and stuff.

I achieve to port TWRP for the A54 5G by learning from afaneh92 TWRP ports for other devices : https://github.com/Nitorac/android_device_samsung_a54x

The recovery boots but there is many errors probably due to lack of multidisabler and I think I did something wrong with the partition mounts (/etc/fstab) but I don't know why (maybe I have to convert vendor's EROFS to F2FS RW but I have no clues).

If you have no data to loose and you want to test it : https://github.com/Nitorac/android_device_samsung_a54x/tree/main/manual_builds/b1f7b7b

I will try to fix the errors but since my A54 5G is my main phone, I have to make backups everytime I dev on it x')
[Samsung Galaxy A54 5G] knighToFdemonS:
What do you guys (with no OEM unlock option) get, when you enable USB debugging and try to unlock it via fastboot?

Seems like the command for that has changed over time, try "fastboot flashing unlock", "fastboot oem unlock" ... there seems to be a few iterations. does that work or what error do you get?
[Samsung Galaxy A54 5G] kimoVoid:
What about system updates? Does the phone still receive OneUI updates after all this, and will I have to re-download the firmware every time the OS updates and do everything again?
[Samsung Galaxy A54 5G] mrbonine:
Right tf on! Or why would you not want to?
[Samsung Galaxy A54 5G] mrbonine:
If you don't know the benefits and risks and effort/time/patience to root, go up several levels to a different thread or board. Wondering with open mouth and neutral brain in a model specific board with rooting issues doesn't add anything of value here. You will hopefully get a polite response but don't expect one.

Maybe I missed it earlier in the thread, but it's always good to mention bootloader locking initially to be sure you know the Samsung Corporate policy, which seems to be US + Broadcom specific. The second important thing for everyone to know is whether you're working to root stock firmware or not.

The answers to that used to be that non-stock required root but there are claims that non-stock firmware can be implemented without root: I haven't attempted that on a Samsung device. Anyone that suggests it's better or even possible should have done it themselves and be ready to answer specific questions.

Anyone new here should note that a number of people will claim to have done something a very seasoned developer has found from experience will not work. As with DNA mutations rarely are these repeatable or beneficial without serious introduced device problems. My advice on this, consult with a senior technical person here before making claims and never offer, 'yes that worked' unless you did exactly what was specified and you can prove it.

I'm still in the doubt phase of A54, my first non-S flexibility. Not only for root, but now also removable storage, an insidious inflation to retail pricing with no benefit, like other iPhone innovations like the audio jack. Note that both were sold as space saving and water resistance required and were both were manufacturer cost plus revenue upside building changes, for the manufacturer for memory and more broadly through Bluetooth headphones/sets that always have vendor specific settings.
[Samsung Galaxy A54 5G] mrbonine:
I'm not sure how you're defining official, but several phones including US versions have bootloader unlockable by paid service. That's certainly not official Samsung and "official rooting" may be done by other manufacturers but I've never seen that claim on a Samsung mobile or tablet.
[Samsung Galaxy A54 5G] googlephoneFKLenAsh:
Official means manufacturer (samsung) allows bootloader unlock and samsung will provide the OEM unlock toggle in the settings and the bootloader unlock procedure in the firmware.

Samsung phones/tablets in non-us markets allow for official bootloader unlock. Samsung non-cellular tablets in the US are also eligible for official bootloader unlock.
[Samsung Galaxy A54 5G] Nonny_SA:
Hello friends !

I think i need some help here again :-) like with all my phones, i like the a54 but i get wile fashing allways very , well nervious , i had allways luck so fare but reading a moment longer dosent hurt , i dont flash every day so i am not the most praticed one here ;-) .... is there maybe also a video on this ?

i do have here :

SM-A546E

sovtware version : SM-A546E_OWB_PEO_13_0009 - PEO/PEO/PEO/PEO

so from the firware link i downloaded this firmware:

PEO-A546EXXS4AWF7-20230715072151

because its says the :

A546EXXS4AWF7

and also the PEO i belive its the csc , i am in peru :)

i would be very thankfull if someone with experience take a look i do the correct thing here :)

ok i unzipped the firmwareand copied the complete folder , but i am not sure its needed just the AP_ file rigth ?

Magisk i dont see in the playstore, i had to donwload for the developer page , the 26.1 APK file, i hope this is the correct one ...

here a point what i am also not sure about , what means point 15 , put in a TAR ? i have winrar but i belive there is no TAR option ... or means this just delete the .md5 ending ? and the place the file in odin AP_ ?

so fare i didnt start the process , i aam collection informations here first :)

i what to keep stock rom but i what AdAway as root version for exaple ...

and DriodWall (firewal) ...

but normally i had also to do a TWRP recovery installed before, here is not the risk of losinf this EFS partition , i liked in the TWRP the full backup option !

Do we dont need something like this here ?

ok thats it from me for now 🙃

Thanks for reading this all and have a nice day

Greetings !
[Samsung Galaxy A54 5G] habibi2004:
hallo

wipe data/casha (factory rest) after flash bevor first boot
[Samsung Galaxy A54 5G] andreidi:
I am also awaiting for a TWRP solution to this phone only so I can backup/restore. Is there any other way to backup the rom with all existing settings and restore it when needed, it doesn't matter if ODIN is needed, as long as you can simply restore everything with cache and settings.
[Samsung Galaxy A54 5G] andreidi:
I cannot modify anything is system folder after rooting. Root Explorer doesn't mount it as R/W. Is this normal? Does it have to do with dm-verity encryption? I want to fully remove bloatware from system to also free up space, not only RAM, with ADB AppControl you only remove them from user data.

I guess there is no way to install custom recovery even if TWRP for Android 13 would exist, because there is not dm-verity patch yet for this device. Am I right?

I can confirm the issue with carrier configuration also on my EUX version, but solved disabling sdconfig as posted before.
[Samsung Galaxy A54 5G] Nacalto:
Hey there !

Does someone get something to fix the "Service Provider Update" ?

Thanks y'all !
[Samsung Galaxy A54 5G] andreidi:
Disable com.samsung.android.sdm.config using ADB AppControl and reboot.
[Samsung Galaxy A54 5G] Nacalto:
It worked ! Thanks mate !
[Samsung Galaxy A54 5G] BlackMesa123:
Devices shipping with Android 13 use EROFS for OS partitions which are read-only, your best bet is to use systemless modules such as magic_overlayfs to apply modifications in your OS partition.

TWRP based on Android 13 is required for this device to work properly, unfortunately the developers haven’t released any updates on it since March.
[Samsung Galaxy A54 5G] andreidi:
Thanks for you reply. I wanted to permanently delete bloatware apps from system/app system/priv-app so I can have more free space, instead of ADB AppControl which only removes them from user data. But this won't work with the magisk overlay, because all the modifications would be virtually made, so the data from the original system won't be deleted.
[Samsung Galaxy A54 5G] BlackMesa123:
This doesn’t matters as with the module I’ve sent you it will act like you did remove the files in the original partition, with the bonus of reverting your changes by simply disabling the module in Magisk/KernelSU
[Samsung Galaxy A54 5G] andreidi:
But if I can revert the changes, then this means that the files are not physically removed, so there is no extra free space obtained. So basically there isn't anything removed from the internal memory.

About the TWRP, I guess a dm-verity patch would be needed to succesfully have this working (my previous M30s needed this after flashing en before rebooting to system).

One more question, since there is no TWRP for Android 13 yet: is there a way to fully backup everything (a sort of NANDROID backup) and then by system failure to restore this (using ADB from PC for example?) and have everything set up as before? I assume that if the system partitions are read-only, then it can't happen anything bad in there, so it would only be the data and cache partitions. I used TWRP all the time to make a backup of everything and if I by accident messed up with the system, I would restore that and avoid a new installation from the beginning.
[Samsung Galaxy A54 5G] shiboby:
So my SM-A546B/DS

I don't see any blue screen. I have a black screen when I adb reboot to recovery. I also dont see any option to long press to unlock bootloader. What do I do from here? On an SM-A546B/DS (EUX)

SOLVED: While the phone is completely off, hold both volume keys and then attach a USB cable that is attached to your computer. This will bring up the blue screen.
[Samsung Galaxy A54 5G] shiboby:
So I have the phone rooted and set up, but I have a recurring issue. I keep getting a pop-up titled "Service Provider Update" with the text "You phone needs to restart to set up features and services from your service provider. Apps and layouts may change after your phone is updated.: It then gives me a button that says "Restart." However, when I tap it nothing happens. As long as it is on the screen, I can't do anything. However, if I tap the back button, it disappears and I can use my phone again. That is, until the pop-up comes back, which it does about every 20-30 minutes. Anyone know how I can fix this? Is there an update service I can turn off?v
[Samsung Galaxy A54 5G] BlackMesa123:
I had the same error and I fixed it by flashing the stock vbmeta image (https://github.com/BlackMesa123/proprietary_vendor_samsung_a54x/releases)
[Samsung Galaxy A54 5G] shiboby:
How do I extract that from the stock firmware I downloaded? I wanna make sure the versions match
[Samsung Galaxy A54 5G] BlackMesa123:
No need to extract it manually, download the kernel tar in the GitHub repo I sent you that matches your firmware.
[Samsung Galaxy A54 5G] andreidi:
Or disable com.samsung.android.sdm.config using ADB AppControl and reboot.
[Samsung Galaxy A54 5G] shiboby:
couldn't find it. could you tell me how to manually extract it?
[Samsung Galaxy A54 5G] fredapied:
Hello,

1/Could you explain how it works ?

why this vbmeta.img is making this nag screen 'provider services update" ?

2/To do ourserves, vbmeta.img could be found in AP stock rom:

So we just have to extract vbmeta.img then .tar it and flash it using odin ?

3/And you explain to patch with your kernel.tar but in your archive there is also boot.img

and to root the phone, Magisk patches this boot.img

so, if flashing with the stock boot.img from your archive and vbmeta.Img we lost the root, or am i wrong ?

Thanks for your answers.

Fred.
[Samsung Galaxy A54 5G] KAW0:
I tried to flash my a54 but my device is not listed by fastboot devices in both regular mode and blue screen mode. ADB works fine. I thought it was a driver problem in windows but i tried it in archlinux with the same result.
[Samsung Galaxy A54 5G] BlackMesa123:
- That error happens when the TEE service cannot load the VaultKeeper TA correctly, in my case reflashing the stock vbmeta image solved the issue.

- No, that’s the stock image. A patched image is handcrafted to make sure the AVB checks pass regardless of the image status. You can find a patched vbmeta image in my repository.

- Yes, the main purpose of my repository is to automatically fetch and download the latest firmware binaries to avoid me downloading the whole firmware just to extract those specific files, saves me time and also keeps me updated when a new update is released.
[Samsung Galaxy A54 5G] BlackMesa123:
Fastboot is not available on Samsung devices unless you flash a custom recovery with fastboot support (there are none for this device) or patch yourself the stock recovery to enable fastboot. To flash in Download mode you must use Samsung’s Odin.
[Samsung Galaxy A54 5G] fredapied:
Thank you answering, but i'm a bit confused :

can i use my own vbmeta.img like i said , with 7zip :

unzip the AP, then unzip the vbmeta.img.lz4 to get the vbmeta.img

And then tar this vbmeta.img and just flash it with odin ?

It's not necessary to use a patched vbmeta (like to said, it's to make sure).

It's a strange behaviour, because with others phones, i never had this issue when rooting, and i was just patching stock boot.img with magisk and the phone was rooted, no need to play with this vbmeta.img