So I have a galaxy s4 active and I rooted a while back with kingroot I know it isn't good but I did it anyway... and unistalled king root completely and supposedly should have removed my root. So I was trying to play Pokemon Go after recently purchasing a pokemon go plus and I can't play and it is because of safetynet even though I have no root. I realized that when I boot up my s4 a screen with a padlock icon and text that says custom appears. I thought this may mean my bootloader is unlocked and that this could trigger me failing safety net. I have been looking every where on how to relock my bootloader. I just want to pass that safety net baloney.
MillaShows said:
So I have a galaxy s4 active and I rooted a while back with kingroot I know it isn't good but I did it anyway... and unistalled king root completely and supposedly should have removed my root. So I was trying to play Pokemon Go after recently purchasing a pokemon go plus and I can't play and it is because of safetynet even though I have no root. I realized that when I boot up my s4 a screen with a padlock icon and text that says custom appears. I thought this may mean my bootloader is unlocked and that this could trigger me failing safety net. I have been looking every where on how to relock my bootloader. I just want to pass that safety net baloney.
Click to expand...
Click to collapse
Greetings and welcome to assist. Try installing latest stock firmware for your device with odin or kies/smartswitch
Regards
Sawdoctor
I used smartswitch and I have the latest firmware
So I used smartswitch and it said I had the latest firmware what now?
I tried everything
So smartswitch said my device isn't compatible to initialize (sgh-i537) so I tried using Odin to return to stock but the only firmware avaliable for my device is kitkat and I have lollipop so I cant downgrade can I? Even then I get and error in download mode saying fail secure download: boot or something like that. If I hard reset through the stock recovery will I be able to pass safetynet I even tried triangle away because I thought maybe it had something to do with my system being custom and it needed to be official and triangle away didn't even work I tried rooting again just so I could rename the su files to su1 which people said would let you play that didn't work either I looking how get magisk I couldn't do it. Is there anyway I can fully go back to stock that will work and will allow me to pass safetynet I am not concerned about root currently I don't need it.
It may be not easy for some users. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Flashing Instructions
Make sure the bootloader unlocked
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing twrp-3.5.2_10-0-a52q.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key until red warning "This phone is not running Samsung's official software..." disappears. Then release all keys. It will take more time than usual until TWRP recovery appears.
Install Kakarot-UNI-1-A52-2021-05-13-23-11.zip
Install Disable_Dm-Verity_ForceEncrypt_20210320.zip
Install Magisk-v23.0.zip, Swipe to confirm Flash ( Ignore this if you don't want to root it )
Format data
Select Reboot to System
Setup the phone
Done!
Rooting
Connect Phone to Internet
Install Magisk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done
Recommended to Watch This Video!
Download and Terms
The phone bootloader must be unlocked, if not read How to unlock bootloader Galaxy A52
Download TWRP twrp-3.5.2_10-0-a52q.tar
Download Disable_Dm-Verity_ForceEncrypt_20210320.zip
Download Kakarot-UNI-1-A52-2021-05-13-23-11.zipsafetynet-fix-v1.1.1.zip
Download Magisk-v23.0.apk stable Rename to Magisk-v23.0.zip
Credits to:@RealVelosh for TWRP 3.5.2
@neel0210 for Kakarot Kernel
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
kidkree1 said:
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
Click to expand...
Click to collapse
Yes, it works
So I have been looking into rooting as well. And dozens of threads are mistakenly assuming OEM unlock is an available option under Developer Options on this phone. It's not there. So anything after that is not going to happen. I am referring to the A52 5G US version with the 750c Snapdragon chipset.
The only supported option is paying ransom for a 3rd party unlock as far as I can tell.
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Faakarna said:
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Click to expand...
Click to collapse
This method should work, unless you have the U.S. variant in which case you won't be able to use any method until you unlock the bootloader (paid services afaik)
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Simon1511 said:
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Click to expand...
Click to collapse
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
ShaDisNX255 said:
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
Click to expand...
Click to collapse
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Simon1511 said:
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Click to expand...
Click to collapse
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
ShaDisNX255 said:
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
Click to expand...
Click to collapse
Ok, thanks. Was just curious if relocking BL could fix it
Magisk Hide has been removed from the main server, so it won't pass CTS now. There is a fix, please search!
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
FlugHund said:
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
Click to expand...
Click to collapse
Did you figure out how to fix this?? I have the same issue!
Hello guys, so I was rooting my phone and I had just ended loading the "A52_MagiskPatched_AndroidHowTo.tar" AP thing via Odin. Instead of taking me to the recovery and is stuck at this screen.View attachment 5474237
I can still load into the download screen, but that's all.
If any one has any solutions please reply, I am sure I did all the steps, but now I'm doubting myself is there a way to revert it or something?
If someone can help me I promise to give a small compensation!
Discord: Non Sense Speaks#4580
DID YOU FIND SOLUTION TO THIS? I HAVE SAME LOGO ISSUE AND WANT TO REMOVE BOOTLADER UNLOCKED RED ALERT
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
frenxl said:
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
Click to expand...
Click to collapse
Because you can't flash root files using stock recovery, they're unofficial files.
Hi! I have a new Samsung Galaxy A52 (SM-A525M variant, Latin America). Anyone tried this method on the "M" variant yet? I've already unlocked the bootloader successfully.
More data:
A525MUBU4AUJ3
nov. 2021 security update
I can debloat it with ADB, but I love root.
Thanks in advance to this great community!
EDIT: I want to thank explicitly ShaDisNX255 for the guide and help in succesfully rooting my phone!
I have the Edge S version. I have tried both EU and China ROMs (via TinyScript) but no matter which ones I use Google pay gives an error message. See pic. Bootloader is unlocked, and for what it's worth When I've tried to sideload ROMs via ADB I get an "unrecognized error messages.
That message constantly returns regards if I delete the file within the .android folder, revoke access in developer settings.....Lastly, it was rooted previously, and currently shows as unrooted.
Any thoughts? If it's just an unlocked bootloader, how do I relock it? How to I revert to comes ROM as if it's 100% BNIB?
You need install magisk to root
set zygisk hide root
install safetynet module to pass safetynet to use google pay
kenwu said:
You need install magisk to root
set zygisk hide root
install safetynet module to pass safetynet to use google pay
Click to expand...
Click to collapse
But it says I'm NOT rooted, that's the thing
hawki said:
But it says I'm NOT rooted, that's the thing
Click to expand...
Click to collapse
Google pay must check if the bootloader is unlocked i guess, as well as checking for root
I managed to get google pay to work by using the magisk build.prop module and just made it spoof that it is another motorola phone, then just make all google play and pay apps hide magisk and wipe all their data
Beetle84 said:
Google pay must check if the bootloader is unlocked i guess, as well as checking for root
Click to expand...
Click to collapse
I have the Moto g100 with the North American firmware. I oem unlock mine both Google pay and PayPal apps work fine. The only thing I did notice. Was in the Google Play store under settings and then all the way to the bottom where it says about. It said device not certified
I enabled It with sucess. You need to install TWRP + MAGISK ... Use magisk to hide root from any app. You should install safatynet.fix module inside magisk and Reboot ... After that try to check If safetynet is certified using safetynet test apps from play store. You will be happy like me ... It's working NFC well!!
Hi,
Ive a rooted 8t with the c.15 version.
I just saw that there is an incremental update to c.16.
How can I update to it with magisk without losing root.
Also I cant use my google pay, most likely because the root , im trying to find it in the hide section in magisk but cant find it, is there another way how to hide it?
Thanks
saar17 said:
Hi,
Ive a rooted 8t with the c.15 version.
I just saw that there is an incremental update to c.16.
How can I update to it with magisk without losing root.
Also I cant use my google pay, most likely because the root , im trying to find it in the hide section in magisk but cant find it, is there another way how to hide it?
Thanks
Click to expand...
Click to collapse
You could try the OOS 12 process I've suggested in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
If you use it, let me know how it worked.
Have you got the modified USNF Magisk module installed?
Did you enable Zygisk, DenyList, and add Google Pay to Configure DenyList?
Also, regarding Google Pay see https://forums.oneplus.com/threads/oxygenos-12-c-16-update-for-oneplus-8t.1574300/ where it says "There is a known issue that Google Pay might fail to work after installing this build." That post also has some suggestions.
Is anybody else facing the problem the universal safetynet fix not working all of a sudden?
I didn't modify anything but since today I get a massage telling me my device doesn't match software requirements.
Because of that I did a manual update inlcuding patching but same problem.
Did google push some update?
hi mate i am not getting a answer anywhere else how did u root your z flip 3 as i've got sm-f711b and i cannot unlock my bootloader
follow the steps in this guide:
Guide to root Galaxy Z Flip 3 (B/N/0), unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. I am not responsible for bricked devices, dead SD cards although it is not...
forum.xda-developers.com
If your're from the US there maybe restrictions not allowing you to unlock your phone. Maybe a Non-Snapdragon version instead Samsung proprietary SOC- But I'm not sure.
all z flip 3 are snapdragon im from the uk
maroc84 said:
Is anybody else facing the problem the universal safetynet fix not working all of a sudden?
I didn't modify anything but since today I get a massage telling me my device doesn't match software requirements.
Because of that I did a manual update inlcuding patching but same problem.
Did google push some update?
Click to expand...
Click to collapse
There is a magisk module you can flash to make gpay work
I used to use it on my rooted phones before I got my z flip3(us version can't root it)
luigi90210 said:
There is a magisk module you can flash to make gpay work
I used to use it on my rooted phones before I got my z flip3(us version can't root it)
Click to expand...
Click to collapse
Did you read the text/title?
Anyway. I unrooted my device.
maroc84 said:
Did you read the text/title?
Anyway. I unrooted my device.
Click to expand...
Click to collapse
Did you not read what I wrote, I didn't say it was your module or safety net fix, there is literally a module you have to search on GitHub or XDA that allows gpay to work when rooted, had you looked it up you might have found it
Anyways enjoy your Knox tripped samsung
luigi90210 said:
Did you not read what I wrote, I didn't say it was your module or safety net fix, there is literally a module you have to search on GitHub or XDA that allows gpay to work when rooted, had you looked it up you might have found it
Anyways enjoy your Knox tripped samsung
Click to expand...
Click to collapse
My device was rooted (so Knox was tripped anyway) way before I was asking here.
You wrote about a module to flash - so if you meant something else as a magisk module you should write more details.
I don't know what you mean with Knox, seems very salty. My device is working fine and I don't care if Knox is tripped or not. I have a solution for everything I was rooting the device in the first place. So no need for an rooted phone anymore.