Database Info

ROOT [n910C] Samsung Galaxy Note 4 Andoid 5.1.1 with Same Bootloader (5.1.1)

Hi Everyone, This is my first post. I am not a developer. Hope this will help you to Root your Note 4 N910C on 5.1.1, if you have any suggestions for me, you're most welcome
Note: I am not responsible for any damage of your phone, kindly read the steps carefully and follow one by one. I have done this with my Galaxy Note 4 N910C on Andoid 5.1.1. Its 100% working.​I have read many thread and websites, I only find Root Note 4 N910C with 5.0.1 bootloader, there was no any option without 5.0.1 bootloader one.
So, with this method you can stay with 5.1.1 Bootloader and can Root your phone. So, here is method I am going to explain you.
First Make sure that your phone's battery is charged above 60%
STEP-1
You need these Files to Root Your Note 4 N910C with Bootloader 5.1.1
Odin3_v3.10.7
SpaceX Kernel
TWRP Recovery
SuperSU
STEP-2
Connect your phone with your computer, You must have installed Samsung USB Drivers in your computer (if you don't have drivers, you can download Samsung USB Drivers Click here)
STEP-3
Copy SpaceX Kernel and SuperSU files in SD Card - Note: I have done this with SpaceX Kernel, if you want to use GoogyMax Kernel or any other Cutom Kernel you can try it. However, I highly recommend SpaceX Kernel.
STEP-4
Disconnect your phone and Switch off then put it into Download Mode (Press HOME+POWER+VOLUME DOWN) Buttons at same time until logo (GALAXY NOTE 4 Powered by Android LOGO) appears.
STEP-5
Open Odin3_v3.10.7 file in your computer (I will recommend open the file as an Administrator - right click on the file.)
STEP-6
Connect your phone with Computer - After Connecting, you will see in the first box [Blue Color] COM:6 or 8 or any other number.
---> if you will not see this please reinstall the Samsung USB Drivers and restart your computer and reconnect your phone.
STEP-6
Click on AP and select TWRP Recovery File from your computer, you have downloaded
Before Click on the Start, please make sure that your phone should not restart. Because it may orverwrite the stock recovery
You Can Do this:
When you see PASS on the window REMOVE The Battery or Press VOLUME UP+POWER+HOME buttons, it will show you the TWRP Recovery page
STEP-7
If you want your can Backup your Stock Kernel, if you want to update your Stock RoM, or install updates in future.
here are the steps:
1. select backup in TWRP Recovery
2. check Boot and uncheck all other options
3. swipe the backup option - and it will save in your internal storage - or you can also choose external storage option, its there
STEP-8
1. Now Install SpaceX Kernel - Click on the install and find SpaceX Kernel and install
2. Go Back and again Install SuperSU
STEP-9
Restart your phone
Your are Done Now!
If you want to check if you phone has been rooted or not,
1. Open SuperSU app in your phone go to setting -> Access (default) -> make it Grant.
2. Download Root Checker from Play Store and check if your ROM is Rooted.
Thank you!
I am new, please let me know if you have any suggests/advise for me.

Thanks, followed instructions to the letter and it's working for me

kazim said:
Thanks, followed instructions to the letter and it's working for me
Click to expand...
Click to collapse
You are welcome!

Titanium backup failed to find root access

Works!
Thanks man! followed the instructions to the letter, works great![

whats the difference between this version or flashing 5.0.1, rooting and flashing 5.1.1 bootloader afterwards?
like this
You can download the bootloader ► here or ► here and flash it via Odin adding the file in the "BL" box.
from here?
http://electron-team.com/dn5_note4_n910c.html

Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.

niceashwin79 said:
Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.
Click to expand...
Click to collapse
you can rebirth it also by flashing 5.1.1 fro scratch from sammobile...

annus9214 said:
Titanium backup failed to find root access
Click to expand...
Click to collapse
you may need busybox, install it from playstore

SUPERSU link for OPO COS 13 ( 6.0.1) ? help

Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:

I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.

srink.007 said:
Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
Click to expand...
Click to collapse
squigley said:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
Click to expand...
Click to collapse
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Ok, so I found a Beta version of SuperSU 2.7.1, and it seems to have worked. It was a different install process, saying it detected a "systemless root" or something, and it needed to patch the boot image. After that I appear to have root access again..
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Edit: Whoops, guess I should have refreshed the page before posting.. What you said is correct Ken.

Thank you
kenboyles72 said:
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
thanks a lot

DONE
http://imgur.com/hh3qkdxGuys Finally I have done it. Yes the phone is rooted now
1. Flash Stock COS 12
2.Update Stock COS 13 using stock recovery
3. Installed SUPERSU (chainfire) from Play Store
3. Install TWRP
4. Create NANDROID BACKUP (optional , I have created since I doubted the rooting process on cos 13)
5. Installed Latest STABLE SUPERSU ( V 2.65 as of now) {my last attempt with beta 2.71 failed }
6. Done
http://imgur.com/hh3qkdx

[GUIDE] Root, Bootloader Unlocks, and More!

Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!​
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.

i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.

The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021​
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com

I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...

its uploading sorry it failed at 99 percent

jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated

jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded

jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!

tested on one of the spares I had kicking around
does what it says on the tin
!kickass

The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps

The OP has been updated to reflect @jrkruse 's new instructions

AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.

jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.

I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe

guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.

AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.

guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.

AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks

guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help

["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]

Root Samaung Galaxy s7 (SM-G930F)

Hi i want to root my samaung galaxy s7 (SM-G930F) but when I flash everything/install everything it wont boot correctly it stays on the Samsung logo. My android version is 7.0,
Baseband-version G930FXXU1DQD7,
Buildnumber NRD90M.G930FXXU1DQFL.
I tried using this guide (galaxys7root.co m/galaxy-s7-s7-edge-root/how-to-root-galaxy-s7-or-s7-edge-on-android-7-0-nougat-w-magisk/)
I can't use links so there is a space by .co m can someone please help me

issi.ma said:
Hi i want to root my samaung galaxy s7 but when I flash everything/install everything it wont boot correctly it stays on the Samsung logo can someone please help me
Click to expand...
Click to collapse
Hi mate
In order to help we need more detail like , phone model , what stock firmware you have , what guide did you followed .......the more detail the better...

MAX 404 said:
Hi mate
In order to help we need more detail like , phone model , what stock firmware you have , what guide did you followed .......the more detail the better...
Click to expand...
Click to collapse
i've edit my text can you work with that or do you need more info?

issi.ma said:
i've edit my text can you work with that or do you need more info?
Click to expand...
Click to collapse
On the thread you posted , it talks about a Samsung AntiRoot Removal Kit no idea what is that .......
Was the rom rooted before trying Magisk?
Can you get into TWRP?
Did you flashed Magisk successfully?
From Magisk support thread
Bootloop
If you end up in a bootloop when installing Magisk, run the uninstaller script in recovery, flash a clean boot image (the uninstaller restores a copy of the untouched boot image, so this step is “just in case”) and start over. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data, but these can be removed manually.
First make sure your system can boot up without Magisk.
Boot to recovery and install Magisk. Boot up your system without installing any modules. Also see "Module causing issues" below.
If your system bootloops again and you're using a custom kernel, try starting over without installing that kernel. If there's still a bootloop your system might just not be compatible. One possibility is to try finding another custom kernel that is compatible. Also see "Nothing works!" below.
Try to flash Magisk again , if everything fail as we really do not know what the Samsung antiroot removal file did , you may have to start fresh all over . I mean flash stock rom again and do it all over . If you decide to do so . Check this thread use it as a guide , in order to avoid losing your data ( factory reset) use home_csc instead of CSC file but it must be same as the one you have now, you know it?
After your pone boots normally , use this guide to install TWRP
Follow steps 1 -9 exactly at 10 use Magisk instead of SuperSu , with Magisk Dm verity file is not necessary

How To Guide [Root] Samsung Galaxy A52 SM-A525F Magisk Root

Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial

Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.

Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?

<deleted>

VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..

hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far

Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?

Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com

hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?

Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video

My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?

Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked

hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?

Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also

hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?

I think I found one :

Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings

I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?

I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?

Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again