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

Search This thread

Zirila

Senior Member
Jul 31, 2015
226
95
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!
 
Last edited:

avalanche1609

Member
Sep 20, 2016
6
2
yepp - I have such an 'outbreak of hell' product - still struggling to root this beast. 90% of the references in the i-net are fake/copied from other Axx or just bla-bla.
Up to now odin (different versions) seems only to be able to flash Samsung CRAPROM (needed it several times after ended bricked)
- magisk patched boot img not working/ending up in boot-loop,
- magisk patching AP dies before finishing (img is 3.5GB instead 4GB)

Samsung - not a success story
 
  • Like
Reactions: Akhil99

Zirila

Senior Member
Jul 31, 2015
226
95
Up to now odin (different versions) seems only to be able to flash Samsung CRAPROM (needed it several times after ended bricked)
- magisk patched boot img not working/ending up in boot-loop,
- magisk patching AP dies before finishing (img is 3.5GB instead 4GB)

Samsung - not a success story

omg.. I was hoping to be able to root the phone at least with magisk.. but what you say doesn't sound well. I saw all those copy-paste tutorials for A41 on the internet too.. thought at least something gotta work.
I still don't get it. this should be a popular phone by its smaller size, low price and good super amoled display.
unbelievable there is no community, roots, custom roms, or at least discussion threads.

friends are getting a few A41 phones.. now that'll be a funny mess to root and handle. :/

@avalanche1609 just curious, you said you let magisk patch AP and it dies before finishing (3.5gb/4gb).. why did you let it patch the 4gb AP file? isn't the way to root the phone with magisk like:
-> get the same original firmware that is currently installed on the phone and extract the boot.img.tar from it.
-> copy that to you phone, let magisk patch the boot.img.tar (about 20mb in size)
-> copy patched_boot.img.tar to you pc
-> flash patched_boot.img.tar from pc with odin back to your phone in download mode (using AP(!) not BL in odin) and that file is about 20mb, not more!
shouldn't that be it?
why did you let magisk patch a 4GB AP?
also: which odin3 version did you use? 99% floating around are fake and malicious, all these 3.14.4 verisons are fake.
 
Last edited:

lebigmac

Account currently disabled
Jan 31, 2017
1,206
813
If you can unlock the bootloader you're already half way there. Then boot into a TWRP using fastboot boot recovery.img and flash Magisk from there. You might also have to disable DM verity somehow.
Good luck
 

Zirila

Senior Member
Jul 31, 2015
226
95
If you can unlock the bootloader you're already half way there. Then boot into a TWRP using fastboot boot recovery.img and flash Magisk from there. You might also have to disable DM verity somehow.
Good luck
unlocking the bootloader should be no problem as far as I heard. but I also heard there is no TWRP version that actually really supports the device (and encryption afterwards). installing twrp with fastboot could be possible, also booting TWRP with fastboot could be possible, but for what? just for installing magisk that way? Isn't the other way easier? -> installing magisk manager, patch the boot image, and flash it back? especially when there is no fitting TWRP version anyway?
 

avalanche1609

Member
Sep 20, 2016
6
2
unlocking the bootloader should be no problem as far as I heard. but I also heard there is no TWRP version that actually really supports the device (and encryption afterwards). installing twrp with fastboot could be possible, also booting TWRP with fastboot could be possible, but for what? just for installing magisk that way? Isn't the other way easier? -> installing magisk manager, patch the boot image, and flash it back? especially when there is no fitting TWRP version anyway?


The samsung brick is rooted now - one successful act of self defense !

- the newest magisk from github (21410) is able to do the job of patching.
(feeding magisk only with an extracted boot.img doesn't work! six different odin versions (<3.14.4) are not able to flash the created boot-image tar file)
- Magisk definitely needs the complete extracted 4GB AP file from the stock firmware - and the canary/github version of magisk is able to patch it (without crashing) and created 4GB patch.tar-file which odin accepts.


fastboot isn't an option - the device is detected but nothing else works/is implemented by samsung

If there is a suitable TWRP around - let me know.
 

Zirila

Senior Member
Jul 31, 2015
226
95
The samsung brick is rooted now - one successful act of self defense !
- the newest magisk from github (21410) is able to do the job of patching.
(feeding magisk only with an extracted boot.img doesn't work! six different odin versions (<3.14.4) are not able to flash the created boot-image tar file)
- Magisk definitely needs the complete extracted 4GB AP file from the stock firmware - and the canary/github version of magisk is able to patch it (without crashing) and created 4GB patch.tar-file which odin accepts.


fastboot isn't an option - the device is detected but nothing else works/is implemented by samsung

If there is a suitable TWRP around - let me know.

That's great news! So there actually is a way to get root on A41 and I'm glad it worked out fine for you so far.
I'm eager looking forward to root one of them for myself, I guess in a few days I'll have the chance to do so (I'll report then).
I'll take your advice and look for the latest magisk build from github.
It still looks very strange to me that magisk requires more than the boot image to patch. maybe it has something to do with dynamic partitions/ram disk the phone might use or the like. idk. maybe it then needs these files also. or probably the firmware is a little bit different from the one installed on the phone. I'm just guessing, not knowing. At least it works and when it takes to patch a 4gb file, well, then let it take that much.

That's the point where it'd be fine to have a XDA A41 forum with community and already people with experience, since it's a phone almost 1 year old now..

regarding the suppported TWRP version.. idk.. I would just trial and error things out. maybe it works with the latest version already. But better check it out before you plan to use the phone regularly..

I also don't know much about the fastboot options, I thought it works like usual as long as the bootloader is unlocked.. but flashing TWRP with odin or the twrp app itself could work too.

oh and the original question from the opening thread still remains open:
where is the community? where are the custom roms? :)
 
Last edited:

korpenkraxar

Senior Member
Jun 25, 2009
84
9
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!
 
Last edited:

Zirila

Senior Member
Jul 31, 2015
226
95
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"?
 
Last edited:

korpenkraxar

Senior Member
Jun 25, 2009
84
9
Hi!

I checked out all the various formats and played around with the ISO settings grabbing some indoor pics in a relatively poorly lit environment.

First, it is a shame that the HDR is inactivated when using the "4:3 48mpixels" mode or PRO mode because I kind of like that HDR effect otherwise. It seems to me like the aggressive compression automatically kicks in on ISO levels 400 and above, while levels 100 and 200 look alright to me: edges with high contrast look more natural and I find the "natural" pixel noise more tolerable than the washed out smudge effect from the compression.

A "4:3 48mpixels" photo with ISO 200 looks acceptable IMHO and with a little bit of tweaking in Snapseed, I was quite pleased with the result. More grain and a bit darker than what I get from a Zenfone 5 with GCam, but tolerable for a modern phone.

With "4:3 48mpixels" ISO 200 we get quite large file sizes and there is no pixel binning or HDR, but for those random pics that I would like to share with friends in social media, this mode is ok.

Overall, the screen and form factor of the phone is great and it is a fun and comfortable one to use, aside from the camera snafu. I suspect there are some artificial configuration restraints here put in by Samsung. I stand by my original remark that a higher JPEG compression ratio would be great. No idea if it can be configured via root.

As a side note, coming from a Pixel 1 and then a Zenfone 5, it is amazing how well GCam captures photos...
 

hkjo

Senior Member
Mar 24, 2013
89
15

Minuz

Member
Sep 16, 2010
6
5
www.freakyclips.org
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
 

Attachments

  • Screenshot_20210317-125736_Root Checker Basic.jpg
    Screenshot_20210317-125736_Root Checker Basic.jpg
    77.1 KB · Views: 152
Last edited:

hkjo

Senior Member
Mar 24, 2013
89
15
@Minuz

Half the price? The ad there might actually be truthful: 800 DKK instead of the normal 1800. Not bad, unless you have to commit to the operator. Are they clearing the stock to make room for the disappointing A42?

Is Samsung's call recording enabled on the NEE firmware? Any idea if one can flash stock firmware from other regions?
 
Last edited:

Minuz

Member
Sep 16, 2010
6
5
www.freakyclips.org

@hkjo

They have similar deals every month, getting customers, cleaning storage for "older/cheap" phones witch are flooding the market atm.
No binding of to the cellphone company, but i'm pretty sure you have to be a danish citizen.

Can see any record options in call settings or phone options, but with root it should be possible to find a app.

-

Regarding of the experience so fare on the phone is great.. coming from a Xiaomi Note 9 Pro , Samsung S10+.
I really like this compact phone, it does everything i need.
The sound is not the best and the plastic back tend to vibrate with the sound from the speaker, but a case will help that.

Update : Had some problems with a danish authentication app Nemid but got it working!
Having some ustabile crashes witch is all on me trying to get a authentication app to work on root phone.. doing some less stable solution.
Got the authentication app working on previous rooted phones, but something is triggered on this phone/software.. With may be the reason for me not using this phone in the future.
(App Nemid)

Hopefully there will come some custom roms or workaround.
 
Last edited:

atriom

New member
Mar 21, 2021
1
0
Well hello you all!


Actually I'm lucky to now finally find some other people with the same phone...

So about my little story in the Android universe:

--- Skip if not interested ---

Coming from a Samsung S3 to an OnePlus 3T. I rooted the OP3T and installed Lineage OS some years ago.. I traded it in for an iPhone 6S from my mom and giving the OP3T to my sister.. I just had enough of this Android because you often get stuck with something, the apps are less mature and it just all feals like you always need to be enthusiastic about the phone.. So I had a lucky year with the iPhone but somewhat I wanted to get an Android device again. Then I found a refurbished Google Pixel - 1st Gen, 2 years ago and bought it for 200€. The battery seemed to be pretty ripped since the phone had to be in the package for months or even years.. Since I didn't want to have the reseller sent me a new phone with maybe similar problems I decided to repair it on my own..
I then damaged the display in the process, needed to replace it as well with the battery and in the end spent about 350€ for the Pixel... I was kind of pissed but it was a nice phone.. Until I dropped it and the display was completly dead but wasn't shattered last year.. So then I just thought I had enough of smartphones and went with a rework of the Nokia 8810 (the 4G edition) and my iPad until I then decided in September 2020 that I needed a new phone. I somehow could still get the Pixel to work but didn't want to spend 150€ again for replacement parts. For the same phone which wasn't better since then.. But the chip the Snapdragon 820 is pretty neat, 4GB RAM enough and the camera great. Just the Display isn't that nice and modern looking... Maybe I should have gone that way..

--- End of my story what was before my A41 ---

So then I did some research - which phone looks nice for less than 300€, isn't big - since big screen phones are just bulky and you need two hands and I don't like that..

I found the A41 and thought since I don't do gaming and stuff on the phone, just a bit Twitter and messaging, it should be fast enough. Turns out after now several months of use since September 2020 it feels often slow.. I as well didn't like many Samsung Bloatware stuff but somehow got it configured that I don't bother that much now.. But I always wanted to have a custom ROM and it's just frustrating to do research on the device and just finding crappy articles as someone before mentioned.. You just get redirected etc... or find websites with auto generated content.

So to my experience so far:

Coming from the Pixel (and the iPhone 6S) I just have to say the camera is crap. I just don't like it and I think they shouldn't have gone with the trend and go for dual or even triple cameras. But with one lens and doing that one great. I share the criticism that the 48MP mode is somehow the one you want since the images look blurry when not using this mode. But then you don't have HDR as said, cant zoom in (software design isn't great here - you could switch to not 48MP here but now...) and images need to be taken with a calm hand because they often are blurred otherwise. And even then: The images are just in every point then those from the 12MP pixel. (In general this is easy to be explained bc each pixel has less light and is smaller resulting in less quality of the information per pixel. And if this is just really bad you need great software and often bigger sensors to don't just shrink the pixel size on the sensor..)

The chipset as mentioned: Ok, but somewhat sluggish... It feels pretty slow and everything in the UI seems to be a bit delayed on the screen.. But you just get used to this.. (Which still doesn't make this a good point)

I then had issues for months with my GPS module which often seemed to not work but then suddendly worked and I don't know why... Since then everything seems to be working fine regarding to locations.. It did work sometimes before and was pretty accurate but it just didn't work in 90% of the situations I tried it..

I actually like the display and battery. Both are great, I get maybe 60-70% usage per day and this is great. The display is also pleasing and I like the size although it could be a bit smaller..

The reason why I found this thread now is my latest problem though..
Since 2 months or so I tried to install an update but it just doesn't work. I somewhere found a OTA file (I think sammobile and I hate it that I needed to register there and Samsung isn't providing the files on their own).. And after booting into recovery and starting to sideload it... It just keeps stuck there as well with just 0%... I just hate this phone now and don't want to use it anymore since it just has no community, it feels sluggish sometimes, the camera isn't great and it's a Samsung phone with no possibility for a custom ROM...

What are your thoughts? Where do you agree - should I maybe try to just wipe it, sell it for 100€ on ebay and repair my old pixel? I just thought I might be luckier with that one ... Or maybe get an iPhone again but then.. those are even used that expensive, but just are so good usable in everyday use.. I am a pretty technical competent person, used Linux for like 3 years on the Desktop with no windows on dual boot don't have any problems solving most problems with software what so ever.. But I just don't want to run into problems with the devices I use daily and need to be reliable. If I want projects to waste my time I find them. I install software on servers and configure them.. But this phone and android in general... I sometimes like it, but then I feel like I need a brake and use something that has less bugs.. (up to the point that I like it again.. I'm pretty ambivalent on that topic)
 

hkjo

Senior Member
Mar 24, 2013
89
15
Can see any record options in call settings or phone options, but with root it should be possible to find a app.
I thought it'd be easier to use semi-official means to enable recording, rather than root.

Found a thread listing Samsung country codes where recording is enabled, but the list is pretty slim. Intersecting it with the list of countries in which this phone is available (based on one of the firmware sites), I think there's actually no official version with recording enabled.

I'm not sure if that rules out official recording. Maybe CSC selection is generic and not per phone, so all countries would be available.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    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!
    3
    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
    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"?
    1
    yepp - I have such an 'outbreak of hell' product - still struggling to root this beast. 90% of the references in the i-net are fake/copied from other Axx or just bla-bla.
    Up to now odin (different versions) seems only to be able to flash Samsung CRAPROM (needed it several times after ended bricked)
    - magisk patched boot img not working/ending up in boot-loop,
    - magisk patching AP dies before finishing (img is 3.5GB instead 4GB)

    Samsung - not a success story
    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.