Samsung Galaxy A41 - no XDA-Forum, no Community, no Custom ROMs

Search This thread

F308

Senior Member
Feb 25, 2013
326
46
EU
Of course working with new things causes that questions come then I ask if forum members met such situations earlier.

To confirm:
Phone is SM-A415F, in English - Samsung Galaxy A41.

At start I installed A415FXXU1BUA1/PRT, recently I flushed security patch and it was 415FXXU1BUC3/OPV.
Looks like first time I did mistake taking ROM designed for other operator but it didn't do any damage, still it was ROM for the same country.

Installation is described really well in given link.
Unpack ROM, patch AP_*.tar file using Magisk apk, flush ROM using patched AP*, not original.
That's all.

When I have root I try everything possible, want to know limits how far may I go and how deeply I can mess.
No wonder, that sooner or later bootloop had to happen, but flushing working ROM again was enough to fix problem and I have learnt alot along the way.

That doesn't mean I guarantee that you will have everything painless. Everyone risks his own wallet, this is the base rule here.
 

Bagoreng

Member
Apr 16, 2021
13
1
... flushed ... flushed ...
You mean flashed right ...? Flushing actually has the opposite meaning, big difference. This term is never used in this context. If anyone would use this term here, practically the older firmware does get flushed out of the way, but this process really has no relation to the older data already on the phone, it's an overwrite of whatever is there. We are flashing (writing to the flash memory chip) the new ROM.

I'm sorry but it appears you are using a translator and the english it throws back is not that good. I was able to reconstruct some of it. I think half of the context has been lost and I can't be sure about some things. It is really not conclusive whether you meant things literally or not, you're saying things like "I have to do everything possible; a boot loop must happen but it can be easily fixed .." is something I've never heard anyone around this community say when I was looking for help with other phones. There's no way I'm going to attempt this expecting a sure boot loop to happen in the middle of the process. This is not how you would share instructions with the community at large, if you meant that literally. Your experimentation has to be separate from the good and sure process you would share with others. Otherwise it's only useful for those who can experiment and have the resources at spare. You should note in this situation it may be risky, instead of "it's easy", because yes it may be easy but it may not be a wise thing to attempt for others. Bricking can be easy too. Difficulty of the procedure in terms of complexity and time doesn't really matter that much, the assurance and the end results matter more. People who don't have the opportunity to experiment cannot make use of such risky procedures.

For translator. It is helpful if you type short sentences and don't use commas. It tends to translate better like this.

Still, thanks for your reply. For now I'll remain in standby until we get more latest information and examples. You may be correct but I can't make a decision based on too few examples. The older root instructions in this thread may not be applicable to the latest ROM/Magisk procedure anymore because Magisk App is one thing now, no more Magisk Manager, so the whole process may be different.

Also, Samsung EU sites show 3 sub?-models of the supposably /DSN model

Galaxy A41 - SM-A41FZBDEUG
Galaxy A41 - SM-A41FZKDEUG
Galaxy A41 - SM-A41FZWDEUG
And apparently on a different samsung page (product vs support) all these 3 are actually the A415F/DSN model, but I can't find the Z?DEUG ending anywhere on my phone physically or in the software, not sure where this is labeled, so I don't know which one I have in terms of Z?DEUG.
 
Last edited:

F308

Senior Member
Feb 25, 2013
326
46
EU
Thanx for correction.
Sometimes a typo or error happens.
About the rest.
Let me choose how I share my experiences with others.
The World is big and for sure there are other people thinking like I do.
Nobody is forced to follow my path, though.
Every forum has "ignore" option as well.

Concerning this:
"I have to do everything possible; a boot loop must happen but it can be easily fixed .." is something I've never heard anyone around this community say.
Well.
You've just heard it first time.

As I said I do with phone everything I can imagine to push it to it's limits and sometimes beyond because I want know where limits are and how good I am in fixing problems.
May I?
 
Last edited:

Bagoreng

Member
Apr 16, 2021
13
1
That's all good. I'm glad someone is able to do this, all your attempts need is a disclaimer that you're doing wild experimentation, which is kind of a requirement early in the device's customization lifecycle. So yeah we appreciate your attempts very much, just need more people like you to confirm and reconfirm the procedures as sure and safe.

Though you haven't explained when and how the bootloop does happen.
 

hkjo

Senior Member
Mar 24, 2013
84
13
Would you kindly tell where it is?
In build.props?
/optics/configs/carriers/<3-letter-csc>/conf/cscfeature.xml

Decode the XML with OmcTextDecoder. No need to reencode before using it back on the phone.

I copied all the files from that directory, modified the XML, and overridden the original directory with a basic Magisk module.

I think they removed OEM Unlock in developer options somewhere between summer 2020 and March 2021, I just updated to ...BUC3 from March and there's no "OEM Unlock".
It's there on my XXU 1BUC3 (CAC), inside Developer Options.

The older root instructions in this thread may not be applicable to the latest ROM/Magisk
1BUC3 and Magisk 22.1 here.

Also, Samsung EU sites show 3 sub?-models of the supposably /DSN model

Galaxy A41 - SM-A41FZBDEUG
Galaxy A41 - SM-A41FZKDEUG
Galaxy A41 - SM-A41FZWDEUG

Not sure how the retail models correlate with firmware versions, but you already have the phone so probably just mind the firmware version.

I think the 2nd letter after the base model is color (B/K/W = black/red/ white?).
 
  • Like
Reactions: F308

F308

Senior Member
Feb 25, 2013
326
46
EU
/optics/configs/carriers/<3-letter-csc>/conf/cscfeature.xml

Decode the XML with OmcTextDecoder. No need to reencode before using it back on the phone.

I copied all the files from that directory, modified the XML, and overridden the original directory with a basic Magisk module.
Easy said.
This action I would do first time then questions come in bunches.
Search results are not clear enough for me.
There's no such thing like "Basic" Magisk module then I understand it was just term you used telling that you used Magisk itself to do it.
How exactly?
Did you create zip containing this directory and installed it with help of Magisk?
Did you modify boot.img?
Did you use REPLACE= feature somewehere?
If yes - where? Where you located modified directory?

I see Magisk tree like:
/sbin/.magisk/
|---block
|---busybox
|---mirror - (many dirs here)
|---modules
|---3c
|---hosts
|---MagiskHidePropsConf
|--- rootdir - (many dirs here)

Hints would be very appreciated.
For now, before you answer, I probably replace file directly but the knowledge would be very useful in future.
I would revert direct modification.
 

hkjo

Senior Member
Mar 24, 2013
84
13
There's no such thing like "Basic" Magisk module then I understand it was just term you used telling that you used Magisk itself to do it.
Yeah, I meant the word literally. See attached for what I'm using on a "CAC" CSC. I've replaced the "conf" directory on Magisk's post-fs-data.sh stage. Not sure if that's the ideal but it works.

Install from the Magisk app like any module.

CSC settings changed:

Camera_ShutterSoundMenu = true

Common_DisablePhoneNumberFormatting = false (show phone numbers with dashes; too bad it still ignores dashes you write manually in contact numbers)

Contact_SupportDuoVideoCall = false (don't integrate Duo into the normal dialer)

Setting_SupportRealTimeNetworkSpeed = true (shows transfer speed in status bar; stupidly, the toggle is available in the settings only when connected)

VoiceCall_ConfigRecording = RecordingAllowed

---

By the way, there's Android 11 with OneUI 3 rolling out now.

Not sure how it affects the CSC features enabled above.

Besides that, as usual, Samsung take a step forward and at the same time a step back. OneUI 3 degrades some GUI and features, just like OneUI 2.x ruined other things (like the battery graph). I'm thinking, best hold off for now, or even avoid it entirely.
 

Attachments

  • SamA41CscModCac.zip
    9.3 KB · Views: 7
Last edited:
  • Like
Reactions: F308

F308

Senior Member
Feb 25, 2013
326
46
EU
Thank you.
Will try bit later.
In the meantime I loaded modified cscfeature.xml directly to it's place, added only one line which was mentioned in thread.
Tried Magisk Skvaler recording module but it is paid and I won't buy it at this moment.
Bad luck. It expired for me today as I tried it once in the past.
External recorder, Cube ACR, recorded only my voice.

AFAIK Android 11 won't have recording limitation, then maybe efforts will not be necessary but HowTo knowledge is always worth it's value.
For my country it is not published yet.
Hope TopJohnWu will adopt Magisk quickly to use it if such necessity occurrs.
Maybe not.

All the best for you.
 

Bagoreng

Member
Apr 16, 2021
13
1
I would like to report that for some reason OEM Unlock option has reappeared in Developer Options, it happened after I first connected to the internet and installed some other apps such as DNS66, Firefox, OpenCamera etc. I don't remember doing anything special through adb or flipping any settings in the last minutes of the initial configuration process. So it's kinda weird.

With the basic setup done I have now returned the phone to the relative and hopefully they don't mess anything up, but if I need to see/configure anything more I can ask them at will, I might continue fidding with it through the months perhaps bringing some feedback to the community where I can. DNS66 is quite a bit crashy here and I'm not sure what could it be, if it's something I removed too much, but I managed to make it work by editing the default hosts file that's cached locally and blocking the update URL so it'll stay how I'd like it, because the thing crashes when I try to add new filter or edit the default one, pretty much stuck and unusable otherwise.


1BUC3 and Magisk 22.1 here.

Thanks for your report, tho you did upgrade from an already installed Magisk previously right? (or does it need reinstall after upgrade?)


Not sure how the retail models correlate with firmware versions, but you already have the phone so probably just mind the firmware version.

I think the 2nd letter after the base model is color (B/K/W = black/red/ white?).

Yeah it's black, but no idea, haven't found anything more on this.
 

hkjo

Senior Member
Mar 24, 2013
84
13
1BUC3 and Magisk 22.1 here.

you did upgrade from an already installed Magisk previously right? (or does it need reinstall after upgrade?)

No, I didn't have Magisk on the older firmware.

I OTA-upgraded to 1BUC3, Magisk-patched the same firmware, flashed with Odin. Needed to install the Magisk APK afterwards, since I flashed CSC_*.tar.md5 rather than HOME_CSC (which presumably leaves the user data intact). Not sure if that's required, but that's what I did.
 

F308

Senior Member
Feb 25, 2013
326
46
EU
I would like to report that for some reason OEM Unlock option has reappeared in Developer Options, it happened after I first connected to the internet and installed some other apps such as DNS66, Firefox, OpenCamera etc.
Did you have root access and Magisk at this moment?
If so - OEM Unlock is visible this way, but it is not certain what it means.
Important is that you have root.
Later Magisk modules may behave in weird way sometimes, that we have to be aware of.
Once you have root you are at home.
Even flashing modified ROM second time or doing factory reset doesn't remove it.
If app complains hide magisk for it.

Added later:
I installed ACR phone, agreed for everything it required, still recorded only myself.
Maybe really it depends of country?
In mine recording is allowed if remote person know that he is being recorded.



hkjo:​

1. I created my zip following your example.
2. What do you use to record calls?
3. Weird thing:
While my ROM is OPV - in Settings->About phone-> Software info > I see Service Provider SW ver. like XEO/XEO,XEO/EUX/XEO.
What the hell that supposes to mean?
Maybe I should load modified cscfeature.xml to those directories instead of POV?

Added later:
Sorry, you wrote already:
I installed ACR and it works fine. It requires to enable a dedicated Service in accessibility options of phone settings.
I enabled something but recorded only myself.
Need make second try.
 

Attachments

  • Screenshot_20210501-192258_Settings.jpg
    Screenshot_20210501-192258_Settings.jpg
    279.5 KB · Views: 14
Last edited:

hkjo

Senior Member
Mar 24, 2013
84
13
2. What do you use to record calls?
The native call recorder, which is a button in the stock dialer:

https://preview.redd.it/k1qsxx3pd83...bp&s=978e2657fa54a2e568adebc9939724a805f78ba0

Sorry, you wrote already:
That wasn't me. ACR didn't work correctly here.

While my ROM is OPV - in Settings->About phone-> Software info > I see Service Provider SW ver. like XEO/XEO,XEO/EUX/XEO.
4 slash codes? Only 3 here (one is the comma separated dual-SIM item), and that's also what I recall seeing on the web.

Try changing inside XEO.

EUX seems to be Germany. Most codes are under /configs/carriers/, but EUX is of the few that are under /configs/carriers/single/. Maybe something special about it.
 
Last edited:
  • Like
Reactions: F308

Bagoreng

Member
Apr 16, 2021
13
1
Did you have root access and Magisk at this moment?

No, I was not attempting anything custom at all. I was still proceeding with plan to configure the phone without root or anything custom, just ADB debugging. And didn't bother unlocking the bootlader. I wasn't trying to root from the beginning, when I saw lack of Lineage OS and TWRP, too risky in this case. I might attempt it somewhere in the future tho. Relatives got really stubborn about "so many days" without the phone.

I tried to configure the phone with ATH2 build. It ended up being mostly learning experience. Throughout I found some side effects and bugs and other inconveniences lefover by the months of phone usage since it's purchase. I ended up doing a factory reset. Then I updated the FW using the phone it self, over Wi-Fi, the official way. And another factory reset. After that OEM Unlock was nowhere, I even searched the whole settings for it and nothing. I proceeded with the ADB only plan to debloat the phone. I was regularly in Dev Options setting other things and did infact periodically check for the OEM Unlock option and I never saw it. And then when I was almost finished, literally, then I see it, and I can't remember what exactly could have caused it because about 1-2 hours of connecting to the internet with WiFi, installing 3rd-party-apps, inserting SIM card and connecting with Cellular was all there. One of those actions may have triggered something else to trip and so on. Who knows. This may be a bug or it may be intentional.
 

F308

Senior Member
Feb 25, 2013
326
46
EU
Try changing inside XEO.
Banzaiii!!!
That I tried and it works.
Solution so far may be in one of two points.
Either it was XEO where change was necessary or it was matter of button which initially was not visible.
I had "add other caller" instead of "record call".
I made changes in both, XEO and POV, added as well your line related to CscFeature_Camera thinking that you added it for a reason:

<!-- === Mod1 === --> <CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<!-- === Mod2 === -->

(Only those two lines were added).
Voila!!!
Bow of respect and thanks for help.

BTW:
Right now in place of "+" button I have recorder button.
Do you eventually have an idea how to add "+" to screen again?
It adds another person to call, now it is not possible while sometimes useful.
 

Attachments

  • Call_Screen.png
    Call_Screen.png
    114.2 KB · Views: 9
Last edited:
  • Like
Reactions: hkjo

hkjo

Senior Member
Mar 24, 2013
84
13
Do you eventually have an idea how to add "+" to screen again?
It adds another person to call, now it is not possible while sometimes useful.

You can use instead the menu's "Add Call".
I don't know if it's possible to configure which buttons appear in the dialer's main screen.

added as well your line related to CscFeature_Camera thinking that you added it for a reason
Well, yeah. To be able to have the camera silent without muting globally. :)
 

F308

Senior Member
Feb 25, 2013
326
46
EU
You can use instead the menu's "Add Call".
I don't know if it's possible to configure which buttons appear in the dialer's main screen.


Well, yeah. To be able to have the camera silent without muting globally. :)
1. Somehow recording button replaced "+", but it is not that important now.
Maybe it is embedded in dialing application?

2. Well. Then this had nothing to do with recording.
I wondered if eventually camera had shared function which might be used in recording as it records sound.

Nevermind.
Feels good to win the battle, allies like you should be appreciated, too.
You are part of the success.
 

hkjo

Senior Member
Mar 24, 2013
84
13
1. Somehow recording button replaced "+", but it is not that important now.
Yes, but the Add Call function is still available in the menu. Maybe Add Call would be more useful as a button than Bluetooth, but it's not a big deal.

part of the success.
Next things to fix (not me :)): get 60fps video recording to work somehow, get some GCam to work, have the Bluetooth icon show in the status bar, better battery graph (like in older OneUI)...
 

F308

Senior Member
Feb 25, 2013
326
46
EU
I remember that with video there were problems in the past.
HQ video didn't work well with stabilization, sometimes phone simply didn't connect to camera and reboot was the only solution.
I didn't fight with it too much.
4K video simply consumed megabytes of space in nulltime.

For myself I met in the past graph which displayed realtime network traffic on status bar.
Digits are displayed by many apk's but they are not readable without magnifying glass, graph was marvellous.

BTW:
Did you use BetterBatteryStats?
It was giving much information.
Following conclusions from those data I had nightly battery usage in range 0.1-0.3%/hour, sometimes 0.5-0.8.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi there!
    I could help in bringing up TWRP and start some ROM development.

    DM/Message me :)
    1
    @F308

    I think I read Android 11 breaks video recording with screen off?
    (Like with this app.)

    And while Samsung's OneUI 3 may have some improvements, it seems there are also downgrades. Has the full QuickSettings screen become 3 lines instead of 4, or app drawer folders 3 icons in a line instead of 4?
    I confirm quicksettings screen is now on 3 lines
  • 6
    What's the deal with the Samsung Galaxy A41?

    For reference:
    https://en.wikipedia.org/wiki/Samsung_Galaxy_A41
    https://www.samsung.com/A41

    👉 There is no XDA-Forum for this smartphone
    👉 There also seems to be no community for this phone.
    👉 Searching the internet for A41 compatible Custom ROMs ends in less than nothingness even in the darkest corners.

    What's going on? The phone is on the market since March 2020. The phone is pretty good in specs (middle-class).
    AND it is the ONLY phone under 200 bucks today that is NOT larger than 150mm in length and therefor usable in pockets.

    I don't get it why it doesn't get the same attention as the other competitors in the same price class.

    Can anybody enlighten me what's happening?
    Please XDA mods and admins, if this is just a mistake, please open a samsung forum for the A41!
    2
    I bought a new Galaxy A41 for 180€ and I'm just setting it up.
    I want to share my thoughts so far about:
    the hardware, the software, things like rooting.

    The Installation and Software:
    The phone starts and already wants to trick you into signing data collection agreements (Terms of Service (not optional), marketing, analytics, 3rd party shares (3 optional)).
    If you select by common sense and only check ToS you'll get fooled when you check the last radio button which says "I've read all of the above and agree (..)" which enabled all optional radio buttons again right before you click next. What a dirty play.
    Also it is not possible to skip the WiFi selection screen ("skip" is greyed out) making it impossible to setup the phone without internet access. This has nothing to do with FRP, this is before anything google related is setup. Samsung clearly states it requires internet to setup the phone and install necessary provider software. Once it gets internet it gets activated and the "skip" option becomes clickable after the next factory reset. This practice makes me really angry. It's obviously the price you pay when you buy a low- to mid-range class phone - you'll pay the rest with your personal data.
    I setup the phone without creating google and samsung accounts (I never got one of these anyways) and got to the home screen. If you havent enabled WiFi yet, there aren't many apps at all pre-installed, just a few useful and a few bloatware apps (like Facebook, MS Office, etc).
    If you give it WiFi however, it kinda explodes with leeching, loading and updating Apps you never asked for. Only some of these can be "disabled" and only some of them can be "uninstalled" the normal way. Some of the unwanted you can't uninstall nor disable. (This is where you wish you had root access)
    The phone had Security Patch Level installed from August 2020. Making OTA firmware updates 3x (about 1-3gb) will get you to Sec.Patch Level November 2020 which is the latest available OTA (we have February 2021 now). That's not a good sign IMO.. so it's already a few month behind the patch cycle..
    So, software wise there aren't many useful apps for me installed, really just the utter basics and much more 3rd party bloatware and Samsung nonsense apps. It's not as much as with the Poco X3, but still much...

    The Hardware:
    The super amoled display is the biggest feature of the phone. and it's really great, the colors, the viewing angle, the brightness.. all top notch.
    Battery is with only 3500mA/h not that big, but it's astonishing strong and it holds up the uptime it promises so far. I can only hope it stays like that even after a few years.
    The size of the phone is what actually made me buy this phone. its the only phone under 6.5" under 200€ and not older than a year. all newer phones are bigger. The size is great, it's slim, but long. (6,1" ~15cm long)
    I didn't expect it to be that heavy, though. well, the weight is not really heavy, but compared to older phones it is a good bit heavier.
    The Camera is just Mediocre, I already knew this from reviews before but playing around with it and seeing the results underscores it. The final pics alltogether look always a bit washen out if you zoom in. There aren't enough professional advanced settings in the camera settings compared to open camera or mx camera. you have to stick with what you get. The Sensor of the camera is despite 48mpixels only mediocre. the widescreen lens is a nice feature but quality wise not that good either. Selfie cam is subjectively good enough though.
    HDR setting and results are a joke compared to mx camera.

    Rooting:
    I actually planned to root the phone with magisk and installing TWRP. However, I ended up not rooting or installing TWRP at all. The reasons are various.
    First, It's possible to unlock the bootloader in developer settings (after the phone called home..). You'll get a nagscreen every time you boot the phone up after it's unlocked. From this point on you might be able to root the phone with Magisk (following the advices a few posts above), but it'll probably trigger and brick KNOX status.
    I decided to NOT do that and relocked the bootloader, because there seems to be no lively community for this phone, there are no Custom ROMs available nor any custom bootloaders. And I might want to sell the phone again if it doesn't fit my likings and that'll be more difficult with broken KNOX status. Also that way I can get OTA stock updates as long as the phone is supported.
    There is also no supported version of TWRP for the A41. And TWRP on phones like this is tricky as you can read at the A40 TWRP page: TWRP A40 read chapter "This device uses system-as-root in an A-only partition configuration." Also the device is using File Based Encryption and not Full Disc Encryption. I don't know if TWRP works with that environment at all yet.
    So currently the only benefits of getting root would be to be able to completely uninstall some bloatware. The rest (firewall, adblocker, backups, etc) is pretty much possible without root access.
    I really hope this phone is able to get custom ROMs and community in the future, though.


    Hi all!

    I have one of these since a couple of days and I have to say it is a really nice phone with a really bad issue: the jpg compression is super aggressive
    and photos that should look great given the lens and sensor look bland and smudgy. As far as I understand, there is no camera api2 exposed at all by default. All camera apps that I have tried produce worse images and gcam does not work (I have tried about 20 different ones, for Mediatek and otherwise). If Samsung could just let me bump up JPEG quality to 95% I would be completely satisfied with this phone, but I guess that would never happen.

    I therefore wonder, is there any chance that your success rooting the phone could lead to bumping up the JPEG quality of the stock camera app, eventually expose camera api2 or somehow allow us to install a version of gcam down the line?

    Cheers!

    I exactly know what you mean as I watch the pics I just made with the same phone. I don't know if you could change anything in this regard after rooting but it actually looks to me like it's rather the built in camera sensor that makes the quality not that good and not so much the jpeg compression. It doesn't really look like jpeg artifacts, it's more like a washen out painting. I doubt you'll get anything better by rooting the phone, but thats just guessing. Also: did you check out the Image format options? "4:3" vs "4:3 48mpixels"?
    2
    Got the phone yesterday (about 120$) and got it rooted with Odin and Magisk took a little back and forward.. been a while sines I have been on Samsung phone.

    I like this small cheap compact phone, tired of the big bricks.
    Was installing from a new phone with latest update from Samsung.

    So wrote a small guide to help out..

    Everything on phone will get wiped/factory reset , so take backup , you have been warned.
    Take no responsibility of brick etc. (or typos!)
    !PLEASE CHECK WHAT VERSION PHONE YOU HAVE MINE IS SM-A415F AND THE GUIDE WAS WRITTEN FOR THAT PHONE!


    Quick guide:
    1* On PC or phone download you stock firmware for you region: https://samfw.com/firmware/SM-A415F
    My was NEE witch is Nordic Europe.
    Unpack or Transfer the AP_* file to you phone, i used microsd so didn't unpack on phone.
    (sd card need to be exFAT , you can format to that in Windows, so it cant handle big files over ~4GB)

    2* Install lates Magisk manager from https://github.com/topjohnwu/Magisk/releases/latest (Used v22.0) on phone.
    Install Magisk patch the AP_* file from before
    Transfer it back to PC, we will use this later!

    3* Start phone, (if new phone don't bother sign in google/samsung etc.. it will all be wiped/factory reset!)
    Enable Developer mode:
    Setting, about device tag 7 times on Build..
    (If its not shown connect to the internet and wait ~5min..)
    Check "OEM unlocking" , "USB debugging".

    4* Turn off the phone, press volume +/- while you connect PC to Phone with USB-C.
    When screen "WARNING...Custom OS can cause problems.." press and hold Volume +, and press Volume + to confirm what you are doing!
    Let it reboot.

    5* Enable Developer mode:
    Setting, about device tag 7 times on Build..
    (If its not shown connect to the internet and wait ~5min..)
    Check to see if "OEM unlocking" is greyed out enabled , check enable"USB debugging".

    6* Turn off the phone, press volume +/- while you connect PC to Phone with USB-C.
    Press Volume +(don't hold like last time.)

    7* On PC open latest Odin (used v3.14.4) from https://odindownloader.com/ (no sure it that the official site but what i used, please let me know if there is a better one.)
    Unpack the folder to your PC hard drive and start Odin3*.exe, uncheck "Auto reboot" make sure "F.Reset Time" is checked.
    Use the original firmware files from (1*) "BL, CP, CSC" BUT the AP_* that you transferred from Phone.

    Press start and hopefully you will get a "<OSM> All threads completed. (succeed 1 / failed 0)" when it's done!
    Restart phone.

    I had to download magisk and install it again but everything seems to be working..

    Cheers
    1
    2* Install lates Magisk manager from https://github.com/topjohnwu/Magisk/releases/latest (Used v22.0) on phone.
    Concerning the above.
    Would you kindly tell what stub-release.apk visible there is for?
    Is it needed?

    I've recently bought A41 and root access is what I miss a lot in it.
    I rooted phones in the past then I have some experience which caused that related questions came to my mind.
    If anyone can answer them it would be for use for me and others.
    Those are, maybe obsolete but better to be on the safe side.

    Question Zero:
    Is the rooting possible to revert?
    This probably affects warranty AFAIK then it would be good to have way back to original state.

    1. What about certificates?
    Past in time there was TA partition which had to be preserved before unlocking bootloader.

    2. How it is with updates after rooting, eventually how to stay safe when Android 11 comes what is expected in the middle of the year?

    Thank you in advance.

    #----------------------
    Added 2 days later.

    With a bit of fear I succeeded to root my phone.
    Software version was A415FXXU1BUA1.
    (https://samfw.com/firmware/SM-A415F/PLS)
    I
    have problem with SafetyNet status, though, see picture.
    Should I worry?

    Concerning point 2 I found sort of answer.
    AP_* should be patched again before flashing.

    #------------------
    As long as it will be possible to edit this post I will inform you about my adventure with rooting by using Magisk.

    Today I installed Xposed and NFC active over locked screen modules for Magisk and went into bootloop. Not sure which of them was guilty.
    I flashed patched software once more and observed that I am short of space, system screams.
    Unfortunately I don't know how it was first time, because bootloop came all of the sudden.
    What is funny is fact that one of file manages show 4Gb of internal memory while other 8Gb but both full to 95%.
    Where is rest of space?
    It should be mounted or mentioned anywhere.

    There's no TWRP recovery for Galaxy A41. Bad luck, too.
    SafetyNet fix is not available for Samsung at this moment, either.

    I've read that Magisk manages many things then it should be possible to manage space, but how?
    I didn't find anything related.

    Any observations and comments will be appreciated.

    #------ Final action -------------------
    Factory reset fixed problem.
    Good thing that root access still remained.
    I have enough for now.

    BTW:
    Looks like bootloader returned to locked state, see picture.
    SafetyNet is still red, though.

    Worth to know:
    Factory reset didn't revoke my changes made under /system, probably because programmers didn't consider that anyone will be messing there.

    Could someone make me a favor and provide fingerprints from original A415FXXU1BUA1 ROM?
    I am trying to get build props from it but due to lack of experience it takes time to unpack and seek through whole this stuff.
    1
    Would you kindly tell where it is?
    In build.props?
    /optics/configs/carriers/<3-letter-csc>/conf/cscfeature.xml

    Decode the XML with OmcTextDecoder. No need to reencode before using it back on the phone.

    I copied all the files from that directory, modified the XML, and overridden the original directory with a basic Magisk module.

    I think they removed OEM Unlock in developer options somewhere between summer 2020 and March 2021, I just updated to ...BUC3 from March and there's no "OEM Unlock".
    It's there on my XXU 1BUC3 (CAC), inside Developer Options.

    The older root instructions in this thread may not be applicable to the latest ROM/Magisk
    1BUC3 and Magisk 22.1 here.

    Also, Samsung EU sites show 3 sub?-models of the supposably /DSN model

    Galaxy A41 - SM-A41FZBDEUG
    Galaxy A41 - SM-A41FZKDEUG
    Galaxy A41 - SM-A41FZWDEUG

    Not sure how the retail models correlate with firmware versions, but you already have the phone so probably just mind the firmware version.

    I think the 2nd letter after the base model is color (B/K/W = black/red/ white?).