After fulfilling the Software Checklist with the One UI Pie 9.0 firmware, you can tell Samsung devices are better. Some users love the Samsung Hardware, But not Software. Why I am telling you this now because of your Samsung Galaxy A40 comes with the Powerful 4 GB RAM and Mid-Range Exynos processor with One UI OS. It comes with the Pie 9.0 One UI as a default OS. So, your device will receive Two Major upgrades and regular security patch updates. If you are a regular user, you don’t need to root your mobile. Trust me, 4 GB RAM can handle a lot of background apps. You don’t have to remove or stop the background apps manually. Because, after rooting your device will not receive official updates from Samsung, due to some security trigger. If you are regular root apps user, you can follow the below steps to achieve root on your mobile. This method is based on Patched firmware.
Why should you Root Samsung Galaxy A40?
You should have a strong reason for rooting. Samsung Already released One UI 9.0 Pie and is already optimized. You have More than Enough 4 GB RAM to use daily apps without Lag for years. You can use this device without lag for years until Samsung mess with some Bloatware. But beyond, this not go reasons, you are addicted to some root apps, or you are a frequent user of some Custom OS, you can proceed further. But if you want to root because everybody is doing, I advise you, don’t root If you didn’t have any experience. For regular users, It can become a Nightmare.
How to Root Samsung Galaxy A40 Pie 9.0 ( SM-A405FN, SM-A405FM, SM-A405S )
First of all, thanks to topjohnwu – XDA developer for finding this way and this genius is a one who discovered and maintaining Magisk. We Also thank another XDA Developer- zavajon, Who tried in the mobile and Successfully tested this method. Samsung Galaxy A40 International variants come with a flexible bootloader. This means that the smartphone can be easily rooted. Also, the device can accept to install TWRP recovery or any other custom recovery file/app alike. Don’t try with Snapdragon US Variants like Verizon devices. They come with locked Bootloader.
But In the below method, we are going to Root this device by using Magisk, not TWRP. You can install TWRP using the official App when it is released. TWRP recovery is a custom recovery file which must be installed on Samsung Galaxy devices because you can root them successfully. In this article, we explained the easiest method to follow and install TWRP recovery on Samsung Galaxy A40. However, the tool required for rooting this device is the Magisk App.
With the help of TWRP Recovery, you can quickly flash the latest version of Magisk into your A40 to gain root access. Before sharing the tutorial, you may want to know that, with the TWRP recovery present on your device, you can easily install any custom ROM or firmware. Does it seem complicated? Relax, everything will be explained succinctly in bullets.
Things to check out for;
Check your device model number.
- Install Latest Magisk Manager.
Make sure your device battery is charged above 50%
Backup your current files and data- Full Data Loss Process (save them on external storage).
- You cannot use Samsung Pay, Secured folder, and some official apps from Samsung.
- You can’t update your firmware, to get new firmware you have to follow the below steps with the latest firmware.
- Read full tutorial before the process.
Pre-Requirement Steps
Unlock Bootloader
Enable USB Debugging Mode and OEM Unlock on your mobile. To do this; go to settings >>> about >>> Tap on the “Build Number” 7-10 times consistently to enable “Developer Options,” then go to the “Developer Options” and enable USB Debugging Mode and OEM Unlock. There is no complicated process in the Samsung Galaxy A40.
- Switch off your device. Enter into Download Mode-> Volume Up+Volume Down and Connect your mobile with PC using USB Cable. When Download mode warning screen Appears, Press Volume Up button to unlock Bootloader.
- The above process will wipe your User Data. After Setup your device, Please recheck the OEM Unlock in the settings. Sometimes It Will Lock Again.
Preparing Magisk Patched Firmware
Download and install the Samsung USB driver to your computer system.
Also, download the ODIN software. Select above Oreo version in the ODIN list. Install ODIN on your PC.
- Download Samsung Galaxy A40 Firmware and save it on your Device’s Internal Storage. Your Current OS version and Downloaded Version AP and CSC should be Same.
- You can use Phone Info to know your firmware version.
- Download 7Zip-ZS Install on your PC. Extract the files in downloaded firmware using 7Zip-ZS. You will get four data. Copy “AP.tar.md5” file to your mobile.
- Download Magisk Manager (Download Latest version) or Magisk canary and Install it on your mobile. Open Installed Magisk and Select Install in Magisk, It will ask For zip file and Patch Boot Image File. Select the Boot Image file.
Navigate to your copied AP File and patch the file.
- Wait for the process to complete, In the end, you will get magisk patched .tar file. The .tar file will be in the same folder where you have the Stock firmware file.
- Copy magisk_patched.tar file to your PC.
Flash Patched Boot Image using ODIN
- Switch off your Mobile. Enter into Download mode->Volume Down+ Volume Up Buttons and Connect Your Mobile To PC via USB Cable, After Samsung Logo Appear, Release all keys.
- After entering into Download Mode, it will say Warning, Press Volume Up button to continue.
- Launch Odin Application.
- It Will Show the message added.
- If you did not get this message Repeat the above steps.
- After Getting Added Message Select, AP/PDA Button then Browse for the magisk patched file selects it. All other three files should be Unpatched and Extracted from the firmware. So, Now you got four files in the ODIN. Un-Tick the Auto-Reboot.
- Press Start wait for the tasks to complete. After the process complete, Press Volume Down+ Power button to exit Download mode. When the screen goes off, Immediately Press Volume Up + Power buttons to boot into Recovery mode.
- After entering into Stock recovery mode, Go to Wipe Data/Factory Reset and Select Yes to wipe data. It will erase your saved data in your device. Don’t Boot into OS, Read below Boot stages before booting.
Boot into Rooted OS
- Press and Hold Volume Up + Power buttons, release all the keys once the Bootloader warning appears. You have to set up your device like a new device. You can select the root status using Root Checker.
- Stock Recovery Boot – Press and Hold Volume Up + Power buttons, release keys while you hold the Volume Up key.
- You will see Magisk Manager in your App drawer. If you can’t find the app, you can install Magisk Manager in your mobile.
What More?
In my opinion, Samsung Galaxy A40 doesn’t need rooting. With the Exynos 7904 and 4 GB RAM, your device can perform well. If you don’t know how much RAM you need, You will never use this much RAM. You should not Boot into Normal OS Booting, by pressing the power button, after firmware flash. It will boot you to Non-Rooted environment. If you accidentally urged and boot frequently, Don’t panic, after setup everything, switch off your device and boot into Rooted OS using above mentioned keys. If you root your device, because of the battery drain issues, you can optimize your battery without root.
Selva Kumar is an Android Devices Enthusiast, Who Can Talk and Write About Anything If You Give a Hint About the respective devices. He is a Computer Science Graduate, Making His Career towards this Technology. He is always eager to try new Android devices — not only Software level but Hardware-level Also. Beyond this, He is a Good Swimmer, Guitarist.
3rd try – no success: flashing process “recovery.img” fails every time, and it ends up in an inappropriate status as the phone doesn’t reboot anymore!
Using Smart-Switch doesn’t work too, but reflashing with Odin with the stock-room files – not the magisk_patched.tar – recovers the machine…
No matter, what went wrong, I did it correctly explained in this tutorial.
In use:
* Win10
* Odin 3.13
* Samsung Galaxy A405FN
The stock-rom compares precisely to the one primarily installed on the phone A405FNXXU2ASG1
you should flash the flashed file in AP. Other files should be Same CSC Firmware files.
Well, I flashed magisk_patched.tar in AP/PDA, but also the other 3 files from the original firmware file in one turn…
Do you mean only to flash the magisk-patched.tar, and not the others too?
Ahh I fixed it, you can’t just enter via the bootloader you have to hold volup+down for a few seconds then plug in the USB and keep pressing to begin the download mode that allows custom ROMs.
I keep getting this error too.
SM-A405FN
A405FNXXU3ATA4
Will this method also work for the SM-A405FZ variant?
This method is based on magisk patched firmware. Follow the same steps on the SM-A405FZ firmware.
Hello,
My first try was OK with Odin: PASSED. But after the Wipe in recovery mode, I don’t understand clearly the next step and what to do. So I have booted in “system now.” The restart was OK, but the telephone wasn’t rooted.
So, second try and then the same trouble as Joe :
hangs in Odin in “Recovery” and on-screen telephone the following message “only officially released binary is allowed to be flashed (VBMETA)
also: reflashing with Odin with the stock-rom files – not the magisk_patched.tar – recovers the machine, but the OEM features have disappeared …?
Any idea?
Your Current firmware and patched firmware should be same. Means, the build number should be the same. You should not update the firmware, after the update. Selecting the firmware, means, not only the build number, the region should be the same. Or Else you will lose some features depend on the region.
Hi,
solved for me following thread on XDA, by modifying boot.img with Magisk last release (not canary version)
Hi Vning, thanks for your feedback. The same issue for me :-/ stuck on recovery.img in Odin…
Do you have the link on Xda?
Thanks in advance
To avoid this error, I Advise this tep when flashing the AP file in ODIN. With the AP File Flash the Three UnPatched Files also. We Updated the article
Thanks for your answer 🙂 but I followed exactly the tutorial. I put the patched file in ap and the three original files in the others boxes… unfortunately It doesn’t work.
Your current firmware in your mobile should match with the patched firmware. Means Build number, Region, and Security Patch update date should be Same. Can you tell your Build number of your phone?
I had to reflash with new firmware because, after the upload, it crashed; so I installed magisk and flash the file based on the original firmware A405FNXXU2ASG1_LUX.
So it’s precisely the same
Your current firmware and Patched firmware should be the same, including build number and region.
Good news, i succed to pass the recovery bug…. but now I can’t reached the recovery mode, it’s going in download mode directly :-/
hi you have a solution?
i’m blocked in idem step
The basis of using Magisk to root the SM-a405fn is loading TWRP recovery, according to this article. There is NO TWRP recovery for this phone currently. If there was, I would not have a look for alternative solutions such as Magisk.
Not everyone Root their device because of Custom ROMs. Most of us Root our mobile because we are regular root apps user. When We buy new mobiles, We can’t wait for the Official TWRP. It can take some time. In Those Situations, this magisk patched method will help us. So, If you consider Custom ROM, Yes you have to wait. But, you can’t root Samsung Pie versions like Old method. You have to modify the Boot files using Magisk, Before TWRP Installation.
Hi
I’m not at all keen on rooting my new A40 but have been told by people at Boldbeast that the ONLY way to get their or any phone recording software to work as it should, is to root the phone.
Again, I don’t want to do that, lose warranty and other functions, etc… so, the question is, does anyone know of a good phone recorder prog that will work on my a40??
Thank you.
After the Pie update, most of the Android mobiles can’t get recorded audio in two ways. We can achieve this only with the help of Root. Other apps don’t work efficiently. They only recorded in one direction.
Hi. That’s what’s happening with mine ( Boldbeast )..just the one side.
It’s very annoying as BB talks to be the ‘best’ and you pay for it ..and it doesn’t work… no signs of them trying to fix it neither.. they say, you’ve got no choice but to root the phone.
As that will invalidate the warranty..and the phone is only a month old, I’m not keen on that option… only option or not.
Yes. It can happen with all other Call recorders. Due to some security measures, you can’t record the audio without rooting.
Thanks again for your reply.
Can I ask you? Should I choose to do the root then, because call recording is essential to me? Will I lose any other functions of the phone? Anything detrimental about the process ??
Thank you.
Mike.
After rooting, you will not get the official updates from Samsung. If you do not bother about the updates, you can root your mobile.
Thank you very much for your help.
Mike.
Hi, everyone works well, until I want to flash the custom AP done by Magisk with Odin. The screen on my phone starts to write something like, “Only official released binaries are allowed to be flashed(VBMETA).”
I re-checked, afterward, and on the boot loader screen, it was written OEM LOCK: OFF(U). So it doesn’t come from this. Moreover, I use the ROM I downloaded (and then customed with magisk), and the phone works well. Pls, help me!
SM-405FN/DS
Thanks in advance!
Your current firmware build number should match with the patched firmware. Flash the patched file along with three non-patched firmware files.
Thanks for your reply,
I’ve always patched the custom ap file with the other three non-patched data, but it refuses me because of the error I wrote on my first comment.
And the current build number matches the custom firmware because the actual firmware I use is the one downloaded on the website.
Your Knox is tripped. Take a complete backup. Wipe user data before flashing the firmware files using ODIN.
Still not working with the same error message…
Try this- Flash the new version of the firmware using ODIN and then Patch the same firmware and flash again with ODIN.
Nevermind, it now works.
Thank you a lot for your help!
Great…:)
What did you do? I can’t seem to get past this either
Recovery image file…… stays there for hours.
This method doesn’t involve any recovery. What recovery did you flash?