Database Develop

[SOLVED] Samsung A5 2017 (A520F) Dual Sim - How to Root Nougat?

I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?

Keith0222 said:
I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?
Click to expand...
Click to collapse
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk

say55 said:
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk
Click to expand...
Click to collapse
Hey! Thanks for the reply. So, I just Flash this in TWRP like all Zip's and then Flash Magisk?
EDIT: It seems the boot image is something I have already tried, except I flashed SuperSU after, instead of Magisk. If you don't mind, could you go through this post, as this is the only problem remaining.

Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!

Keith0222 said:
Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!
Click to expand...
Click to collapse
Hi, will smart switch still work after rooting?

Magisk + root + TWRP

Hi fellas,
I am about to flash magisk+twrp+root on my exynos device but I am worried about the following:
- Is it be possible after twrp flash to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access my data?
- I read that when knox is tripped samsung pay and google pay do not work but there is a workaround (hide root) to fix that. What functionality does not work at all after tripping knox?
- How do OTA updates work? Do I need to flash the OTA update everytime an update is rolled out? Will I every time lose my data?
Thanks!

dklearhos said:
Hi fellas,
I am about to flash magisk+twrp+root on my exynos device but I am worried about the following:
- Is it be possible after twrp flash to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access my data?
- I read that when knox is tripped samsung pay and google pay do not work but there is a workaround (hide root) to fix that. What functionality does not work at all after tripping knox?
- How do OTA updates work? Do I need to flash the OTA update everytime an update is rolled out? Will I every time lose my data?
Thanks!
Click to expand...
Click to collapse
No,you cant encrypt data or lock bootloader after rooting/ installing twrp.
Yes samsung and google pay works after a tweak. Same as netflix.Secure folder,Samsung pass and S health.And if you are a gamer Fortnite too.But Fortnite and S health can be fixed.
To install ota you download the latest stock firmware with SamFirm/Frija and patch the AP file in Magisk Manager.Download the latest TWRP and patch it too.In Odin on your pc,put BL file ,patched AP file,CP file and Home_CSC/CSC file.Put phone in download mode and connect it to pc.Click start.After that let it boot.You will see phone will not be rooted,just use combibation keys for booting with root.Install flashify and install the TWRP as recovery file.Boot into TWRP and flash multidisabler from TWRP thread.Go to rebootand select Recovery.Let it boot and you are done!
Yes you need to manually install the update every month( everytime an update is rolled out).
If in odin you use CSC file your data will be deleted.If you use HOME_CSC your data will be intact.

ExtremeGrief said:
No,you cant encrypt data or lock bootloader after rooting/ installing twrp.
Yes samsung and google pay works after a tweak. Same as netflix.Secure folder,Samsung pass and S health.And if you are a gamer Fortnite too.But Fortnite and S health can be fixed.
To install ota you download the latest stock firmware with SamFirm/Frija and patch the AP file in Magisk Manager.Download the latest TWRP and patch it too.In Odin on your pc,put BL file ,patched AP file,CP file and Home_CSC/CSC file.Put phone in download mode and connect it to pc.Click start.After that let it boot.You will see phone will not be rooted,just use combibation keys for booting with root.Install flashify and install the TWRP as recovery file.Boot into TWRP and flash multidisabler from TWRP thread.Go to rebootand select Recovery.Let it boot and you are done!
Yes you need to manually install the update every month( everytime an update is rolled out).
If in odin you use CSC file your data will be deleted.If you use HOME_CSC your data will be intact.
Click to expand...
Click to collapse
Sorry to revive such an old thread but you mentioned we can flash multidisabler and reboot. But multidisabler official thread OP says we need to wipe data every time multidisabler is flashed? Can you confirm this please?

ykumar00 said:
Sorry to revive such an old thread but you mentioned we can flash multidisabler and reboot. But multidisabler official thread OP says we need to wipe data every time multidisabler is flashed? Can you confirm this please?
Click to expand...
Click to collapse
No. Untick the reboot option in Odin when flashing the patched files. Then, when flash is complete, boot to TWRP recovery (hold vol up + Bixby when booting) and flash multidisabler in TWRP before booting the phone normally.
Note - on first boot, TWRP will reboot again. Make sure you're ready to hold vol up + Bixby again as it reboots.
As long as you install multidisabler before phone boots normally you shouldn't lose any data.

Magisk patch on SM-A520F (Galaxy A5 2017) FAILED

Hello,
I've been using magisk for some time now and no problem until now. I recently updated my firmware to the last version and intended to update it and keeping magisk, but it didn't worked.
Every time I would flash magisk to the boot image by any mean, the system would boot and tell me "system was modified : press the nuke button to restore it (you will lose all your data lol)" or womething like that.
I was able to flash the stock update and get my phone working with the last firmware but magisk is not installed. I also installed TWRP without problems (helped me a lot to flash the stock boot.img and restore the phone).
I tried to install magisk using :
- Odin : Modified boot.img using magisk app and repacked as boot.img.lz4 in the AP file (with correct lz4 parameters)
- TWRP : Flashed modified boot.img from earlier
- TWRP : Flashed magisk ZIP directly
- Odin : Flash full AP modified by Magisk app
Every time, I have that black screen that tells me my system will be wiped if I continue. Magisk, Odin or TWRP do not return any error
Feel free to ask for any file or further info and thank you for your help !
Firwmare version is A520FXXUGCTKA_CL19831441_QB36271825_REV00
Magisk app returns :
- Ramdisk YES
- A/B NO
- SAR NO

Did you try after you install the new rom through Odin, then instal Twrp and then in Twrp you Format data(not wipe) then immediately install magisk. If dosen't work try with another firmware.
I never update firmwares if there isn any visible difference. Mostly is always some security fixes which i dont care about.

hey, Im having a different issue where after installing lineage 18.1 on my a5 i flashed the latest magisk but once i got in the phone it cycled into a bootloop and now it's eternally turned off cant even turn it into twrp. any suggestion?

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!

issues flashing combination rom

hello fellas , i have s10 ,problem : always booting up to recovery mode ( couldn`t find solution for it )
,,,, oem is locked and there is no way i can flash twrp or custom rom off course ( btw i am noob)
i tried flashing combination rom using odin ( just to enable usb debugging ) but many msesages of (please get the approval ) for pit ,bootloader, system ...etc
googled the issue , found someone saying it is sort of protection that requires unique key should be requested from samsung
So , how can in bypass it to make successful combination rom flashing ?
any extra files needed plus to the combination rom and pit file ?
please help me out
note : repeat: my phone is oem locked , at flashing stock rom is success but reboots directly to recovery mode ...this is my major problem ,
if anyone can post me sm-g973f (bit15) adb enabler file ?????
it might help
if you guys can hand me in either of those it will be deeply appreciated
thank you all

giants....does combination flashing successful with test points ? and where can i find them inside s10 ?

Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html

meric57 said:
Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
thanks for reply , sadly the device can take only the stock rom , any custom will be rejected due to oem lock , and if i flashed stock one it will boot up to recovery not the system ,

So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.

meric57 said:
So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.
Click to expand...
Click to collapse
already said when i flash stock rom device turns up to recovery mode not to the system . the only thing i see is flashing combinations which is now impossible without token , is there a trick or workaround to bypass getting in the recovery mode after flashing stock ?

put device in download mode start from scratch with odin official firmware

meric57 said:
put device in download mode start from scratch with odin official firmware
Click to expand...
Click to collapse
like i said before , successful flashing stock rom , after that the mobile goes to recovery mode not to the system

Hello Rose, I had the concern like you these for its that it is necessary to start from zero. I also did like you too when I start with power back TRWP direct, I had to reinstall official rom Android 12, use which TRWP for your S10 exynos the one the twrp-3.6.2_9-2-beyond1lte.img yes or no you know that you have to patch its image with magisk 25.2 then rename it in recovery and replace the one in AP with the recovery modify then flash with odin.
In your quote start with TRWP then you take the boot.img of the AP flashed it then try to restart in recovery.
watch this video

i dont have active android in my device and it can NOT boot up to system if i flashed stock
before stupidly activate oem lock i had zero problems , locked oem and flashed stock and then i got recovery interface , can not log in system

i have LG 4k tv which i messed its software , but managed to reset it all by shorting pins >>> can it be done the same way with my s10 ? if yes , anyone can show me where circuit shorting pins are ?

not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home

meric57 said:
not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home
Click to expand...
Click to collapse
not working ,,,, any instructions or updates to flash factory binary without fail via odin ?

googled to download sboot to fix the whole thing , no luck , can anyone attach it here please ? bit15 (uf protection)

Hello Roseen, so how does your S10 react starting on TRWP or getting stuck on the Samsung logo. I don't see that you tried to do things without having looked at the tutorials on XDA. well a 4G exynos G973F you have the Android 12 UI 4.1 rom.
Does your pc recognize the S10 when it starts up, did you get the message in red safety e and the yellow triangle plus the message, at worst try with another smartphone to film the start-up.
What does your last post mean with bit15.
I put you the link for the tutorial s 10 of the forum
Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) (Without combination keys for active Magisk after normal restart –...
forum.xda-developers.com