yashsingh1/xdaforums huggingface dataset:
[General Topics] Minuz:
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
[General Topics] hkjo:
Only $120 ?!
[General Topics] Minuz:
128$ to be exact.

Samsung - Køb nyeste Galaxy telefoner her - CBB Mobil

Samsung har nogle af de mest populære mobiler. Find bl.a. Samsung Galaxy i stort udvalg, og få en ny mobil til Små Priser her.

www.cbb.dk

Don't think you can order from out side of Denmark. you can always move :)
[General Topics] hkjo:
@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?
[General Topics] Minuz:
@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!

Spoiler content hidden.
[General Topics] hkjo:
@atriom

If it's working now, why waste time on trying to update?
[General Topics] hkjo:
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.
[General Topics] abcuky:
I installed ACR and it works fine. It requires to enable a dedicated Service in accessibility options of phone settings.
[General Topics] abcuky:
Is there any developer working on Galaxy A41 TWRP? Now it seems that rooting is achieved, however no TWRP (or modified CWM) available at all...
[General Topics] hkjo:
Unrooted, with "ACR Unchained"?

Does it work for VoLTE?

Does it record in "microphone mode", rather than directly from the "phone line"?

Android 9/10 call recording issues | ACR - Another Call Recorder by NLL APPS

Official information from NLL Apps about call recording issues on Android 9 and Android 10.

nllapps.com
[General Topics] F308:
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.
[General Topics] F308:
Yes. Strange with this phone that it is not exploited while it is really nice.

Rooting gives options and I could live only one month without it, I ignored warranty loss.

Backup having root is completely different thing in comparison to normal.

Not talking about access to invisible for average user partitions.

An idea came to me.

What if I would install TWO Magisks?

One in ramdisk, the second in recovery?

If sh*t casually would hit the fan we could use another to repair the other.

Second thought:

Both probably would mount the same real partitions then question is what options would be available.
[General Topics] hkjo:
Doesn't work here, even with the accessibility service. Only local side is recorded, not the remote side.

Tried with both ACR Unchained 33.3 from ApkMirror, and the one on the Samsung store (ACR 33.3-samsung-unChained). Also tried the basic non-unchained version on the Google Store.

Phone firmware is March 2021, A415F XXU 1BUC3 / A415F OXM 1BUC3.

The CSC is CAC.
[General Topics] hkjo:
Well, the native call recording works when setting

<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>

None of the 85 CSCs in this multi-CSC firmware have it set, so initially I wasn't sure if the feature was included at all. But so far so good.
[General Topics] F308:
Would you kindly tell where it is?

In build.props?
[General Topics] F308:
I just figured out that Samsung Galaxy A41 is not on XDA inventory list.

I wanted add it to my profile for people to know as it is in habit but cannot.
[General Topics] Bagoreng:
Yeah. One of my relatives has this model and I hoped I could set it up right because they're complaining it's nagging them with a lot of popups ... looks like TWRP and LOS aren't supported yet, but I guess if rooting works at least that could help out slowing down the horses a little bit.

Perhaps if I could borrow their phone briefly to assist with anything here ... but that's quite a bit risky if I break it.

EDIT: Recently Magisk uses one app now, so the procedure is most likely different now right, at least for the new versions?

Could anyone else also confirm the rooting procedure, I'm hesitant to do this on a relative's phone, if it was my own I had no problem.
[General Topics] F308:
Well. It always is risky.

At start learn how to get out of bootloop to be able to access phone.

I mean - learn to boot into recovery, download and safe mode.

This in general is enough.

The second - have backups.

Many of them, made in different way.

Original Samsung's backup, third party app backup, ADB backup, 3C All-In-One backup.

At this point you are about safe concerning your data.

Titanium Backup disappointed me a bit, it happened that it froze in the middle of restoration.

Not all apps permit to be restored, some have to be installed again.

Next step - disable bloatware using ADB.

This way you get rid of about 130 crap apk's without root and eventually it may be sufficient for your cousins.

In general rooting in situation when there is no TWRP serves not much for average user.

Rooting was pretty easy, much more than years ago with Sony, but later I went into bootloops 3-4 times playing with root things.

One of Magisk modules caused it, too.

Be aware:

Don't touch financial applications, even if you don't use them.

I disabled Samsung Pay and had to restore fresh ROM.

With TWRP it was possible to fix it, but this is not the option for A41.

I am lucky, my banking app works even if I don't have Safety Net fix green, then this area is black for me.

Ask if you want to know more particular details, this post is long enough.
[General Topics] Bagoreng:
Well the major thing I'd do with root, among some extra settings, is to also use a custom hosts file to block various malicious things the relatives could click when browsing as they're very naive and curious, as well as to block some potentially shocking or inappropriate things that may turn stomach of relatives upside down or inadvertently show up while browsing things with family.

I'm not sure if DNS66 is able to apply it self to work with Mobile Data, the last time I set it up on another tablet it required I think an URL location (so I had to host the file somewhere) and was kinda buggy and wouldn't want to update the latest version of the file from the URL. That tablet did not have network/calling capability so I didn't had an opportunity to test actually.
[General Topics] F308:
Yes. I did that ASAP.

It was one of purposes which for me were worth losing warranty.

Having Magisk I installed module Systemless Hosts.

I loaded my own hosts file compiled from data taken from some servers (below in italic fonts you have URLs).

# Please do not modify it directly, it will be overwritten when AdAway is applied again.

# This file is generated from the following sources:

# This hosts file is generated by AdAway.

# http://adaway.org/hosts.txt

# http://hosts-file.net/ad_servers.asp

# http://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext

# http://winhelp2002.mvps.org/hosts.txt

# http://adblock.mahakala.is/

My hosts contains more than 1.9 million lines (!) directing dns names to 127.0.0.1 and has weight 60 Mb.

All commercials and trackers hit their heads into the wall once and forever.

Of course my hosts will not be overwritten as I don't have AdAway. No need.

BTW:

What extra settings would you do having root if I may ask?
[General Topics] Bagoreng:
Slowly debloating it I have unfortunately started testing a bit later than I wanted, now I noticed the original camera app has a disappearing options screen, anything on the HUD/overlay can be modified and adjusted, but clicking the setting gear icon displays the options for only a second and preventing any modifications.

The FW is A415FXXU1ATH2 and region is SIO and there were only 3 bixby things on:

com.samsung.android.app.settings.bixby
com.samsung.android.bixby.service
com.samsung.android.bixbyvision.framework

One of the debloater guides said that bixby affects camera functionality so I reinstalled these 3 (rebooted and cleared cache) but it didn't solve the issue so it's something else in this case.

Perhaps some features of the original camera might be needed down the line but I don't know, so that's my goal to keep this functional but I guess for the time being perhaps not the most important thing. I remember from other phones were the ability to do high-refresh rate recording was locked to some private API that only the official camera app had access too and not possible with OpenCamera. Either way I'll install OpenCamera as well and it may just work out fine for what the user needs.

EDIT: Currently uninstalled apps:

com.google.android.onetimeinitializer
com.google.android.ext.shared
com.google.android.ext.services
com.google.android.configupdater
com.google.android.gm
com.google.android.apps.tachyon
com.google.android.setupwizard
com.google.android.apps.docs
com.google.android.apps.maps
com.google.android.syncadapters.contacts
com.google.android.tts
com.google.android.partnersetup
com.google.android.googlequicksearchbox
com.google.android.videos
com.google.android.feedback
com.google.android.printservice.recommendation
com.google.android.apps.photos
com.google.android.syncadapters.calendar
com.google.android.projection.gearhead
com.google.android.apps.turbo
com.google.android.apps.setupwizard.searchselector
com.google.android.gms.location.history
com.google.android.apps.youtube.music
com.google.android.youtube
com.google.android.apps.restore

com.netflix.partner.activation
com.netflix.mediaclient
com.microsoft.appmanager
com.microsoft.skydrive
com.microsoft.office.outlook
com.microsoft.office.officehubrow

com.samsung.android.mdx.quickboard
com.samsung.android.app.galaxyfinder
com.samsung.android.game.gamehome
com.samsung.android.app.social
com.samsung.android.aware.service
com.samsung.android.rubin.app
com.samsung.android.app.sharelive
com.samsung.android.knox.analytics.uploader
com.samsung.android.smartswitchassistant

com.facebook.katana
com.facebook.services
com.facebook.system
com.facebook.appmanager

EDIT - UPDATE

I have done a factory reset as part of the configuration, to start fresh, and to try to fix this issue, but it did not work, this has to be a manufacturer bug.

Looks like Camera Settings does not work on A415FXXU1ATH2 stock firmware, as soon as it displays it disappears.

I'm attempting to do an update of the FW.

EDIT: UPDATE 2

The issue has been fixed in the subsequent OS FW updates.
[General Topics] claudito77:
hi to all, I'm new in this thread. I have to buy a new phone but It should be as small as possible. I'm considering to buy an older model or this a41. I've always had rooted phones and this one seems to be a little trouble. So I would like to ask you, how many bloatware apps (like FB, GMAIL, LINKEDIN ETC) are preinstalled on this device? I mean, just to know how many of them can not be uninstalled without root

thanks
[General Topics] F308:
This is pretty nice phone and was really easy to root.

Eventually Magisk is brillant software, my respect.

Pity that it is not much cared on XDA.

I uninstalled about 130 apps.

I think you can uninstall all applications without root using ADB, but it is rather not recommended.
[General Topics] claudito77:
This is pretty nice phone and was really easy to root.

Eventually Magisk is brillant software, my respect.

thanks so much for the feedback, but can you explain? In the thread I've read there's no twrp for a41, so how did you install magisk without it?
[General Topics] F308:
Directly.

Installation

The Magic Mask for Android

topjohnwu.github.io
[General Topics] Bagoreng:
I did go through your post when you attempted to root, but the tone of your text sounded worrying. You are also going back and forth with question and answers. Your english isn't the best in that post as well. No offense but just pointing that out because with these sensetive things we need to be ofcourse very careful and also communicate very clearly and technically. Perhaps if you could summarize the procedure out again and then it may give others some reassurance so they could give it a try. If they succeed then I might also attempt it.

Just to confirm my phone is SM-A415F/DSN was /PLS, so it's a bit difference there.

You should confirm your model so that we have a clear picture, if you attempt, and please report back the results and your process, much appreciated. To get this started we need more examples on record, otherwise most people will remain reluctant.
[General Topics] Bagoreng:
Omg ... 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", I guess that may be needed for TWRP and LOS, I hope they didn't do anything else that prevents at least rooting.
[General Topics] F308:
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.
[General Topics] Bagoreng:
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.
[General Topics] F308:
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:

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?
[General Topics] Bagoreng:
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.