How To Guide How to root Samsung A52s (SM-A528B/DS) with working Camera

[testestestest]

Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).

Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).

I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.

I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader

1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay

UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).

 

[testestestest]

reserved

 

[testestestest]

Ok, I feel happy for you you succeeded to root your phone with your camera working and you pass the SafetyNet test by activating Zygist with safetynet-fix v2.2.1, but what have you done differently from my guide as you as you just got updated information from my thread ?

You passed SafetyNet test and so what next ???

Have you got Samsung Secure Folder, Samsung Health or Samsung Pay working or such other protected Samsung apps ???

Are you getting Xprivacylua or AfWall+ (may be this one but not sure) working ???
Firefds kit [R] is not yet update to be compatible with Android 12, so it only partially works...

On my Galaxy Note 9, I didn't pass SafetyNet test, but Samsung Secure Folder, Google pay, Samsung Health are fully working... ^^
Samsung Pay is working but only with a Samsung Watch...
With another configuration I passed SafetyNet test but all above apps aren't working at all !!! ^^

I don't mind you created another thread and another guide on how to root the A528B but what is the interest if you don't explain how you improved mine and what new features you got ???

A. I didn't read your guide since your guide openly says it doesn't work with camera
B. I needed camera so I created my own guide where the camera works and it is here for everyone to read

 

[bobfrantic]

Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).

Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).

I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.

I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader

1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay

UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).

Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHoo

 

[bobfrantic]

Ok but does it changes anything since my post #218 of my own guide ?

not that i can tell

UPDATED : How to root Galaxy A52S 5G (SM-A528B)

This is a highly updated tutorial on how to root the Galaxy A52S 5G (SM-A528B) phone based on new version of Magisk and from feedbacks I received from users after the release of the first guide version ! ;) This guide should work with other...

forum.xda-developers.com

As I was myself trying to use Zygist with SafetyNet 2.2.1 version even though I didn't mention it explicitely as Safetynet 2.2.1 is only working with Zygist ?

"Ok, nice try mate but Zygisk-LSPosed is even worse !!!

It broke FoxMagiskModuleManager when Zygisk-LSPosed has very poor modules list. It broke AfWall+ and it partially broke Firefds kit and no progress at all with Samsung apps !!!"

Does this still apply ?

yes as far as lsposed goes, never used the fox app or afwall so can't say. no gravity box for android 12 yet

 

[bobfrantic]

So that means that since my post #218 no one with failed camera has installed SafetyNet Fix 2.2.1 with Zygist and no one has checked if that has an impact on the camera, and thus no report to me ??? lol

I just remind you that my camera has always been working so I couldn't expected any changes on this aspect... ^^

Finally, if my guide offered "limited root", this one offers even more limited one as with the exception of AdAway what this root stands for if you can't at least protect your privacy ???

you are lucky enough to be in a region that allows the camera to function while boot loader is unlocked

 

[bobfrantic]

One thing I've noticed, after a restart the camera fails until closing it and killing the app in recent apps, then it works.

 

[Pinokaille]

Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).

Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).

I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.

I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader

1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay

UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).

thank you very much )))) I will try this weekend!

 

[WaveAbuser]

Guys, can anybody explain to me , why Samsung is apparently making it so hard for the customers to root their devices? Is it a problem with Samsung or with Magisk, or both?

Not being able to root via Magisk is a real dealbreaker to this otherwise well-specced phone (at least it is to me!).

 

[bobfrantic]

Going to try this method with Android 11 using Magisk 24.3 and safety net 2.2.1 which I hope will allow the camera to work also.

Edit: It works with android 11.

 

[bobfrantic]

Why wouldn't it work with Android 11 as it is not related ???

You mean you downgraded to Android 11 and got stuck with a very old security patch just to get GravityBox and probably with Firefds Kit [R] working ??? lol

Yes, yes and yes. LOL and better battery life too

 

[bobfrantic]

I've had no bootloops when changing things FireFDS and I'm glad to have a working gravity box... I'll report battery after a few days.

 

[Kyodaigumo]

Guys, I DID IT !!!!

Hi, I'm new here and I bought the A528B, I don't speak English and I use google translate... maybe this is asking too much but a step by step video would be too much to ask? having to translate it costs me a lot trying to follow the guide...
I don't understand how I have to do to be able to root it and have the camera working

 

[Yader latino]

Ok, confirmo que esto funciona!! Bien hecho señor. Muchas gracias y animo a todos a hacer Desbloquee el gestor de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)

Chicos, LO HICE!!!!
Samsung A52s (SM-A528B/DS) en funcionamiento con cargador de arranque desbloqueado, rooteado (Magisk), pasando SafetyNet y CÁMARA DE TRABAJO (yaaay).

El problema es que no tengo idea de cómo lo hice, porque fueron 3 días de flashear, parchear, reinstalar y bloquear el teléfono también (desafortunadamente).

Adjunto una captura de pantalla que hice con el teléfono mientras escribía esta publicación en Word. Alguien quería capturas de pantalla en pantalla dividida como prueba, así que... boom, aquí tienes.

Tengo muchas fotos que hice en los últimos 3 días, así que intentaré escribir algunas instrucciones más detalladas pronto. Pero ahora al menos prueba esto:
Esto debería funcionar para cualquier persona, incluso para las personas que no tendrán una cámara en funcionamiento después de desbloquear el gestor de arranque.

1. Descargue el último firmware y Odin de samfw.com (no sé por qué, pero estos fueron solo uno que se cubrieron para mí, bloquearon mi teléfono antes con un firmware diferente)
2. Descomprima el firmware descargado y copie AP a un teléfono con Magisk 24.1
3. Use la aplicación Magisk para parchear el archivo AP y descárguelo nuevamente a la PC
4. Desbloquee el cargador de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
5. Reiniciar
6. Vaya al modo de descarga (debería ver OEM: APAGADO (U))
7. Flashee con Odin todos los archivos de Firmware que descargó, pero a AP puso el archivo parcheado
8. Reiniciar
9. Vaya a magisk, haga lo que quiera, reinicie, en la configuración active el host integrado, active Zygisk, reinicie, descargue e instale el módulo kdrag0n's safetynet-fix v2.2.1 ( https://github.com/kdrag0n/safetynet -fix/ lanzamientos )
10. reiniciar
11. siiii

ACTUALIZACIÓN: Ok, parece que el software de la cámara fallará después de reiniciar una vez. Cuando lo cierras y lo abres de nuevo, funciona.
CONFIRMADO: Tuve que volver a flashear después de probar TWRP y ahora puedo confirmar que parchear "safetynet-fix v2.2.1" te permitirá usar la cámara después de una ejecución. La aplicación Samsung Cam fallará en la primera ejecución, por lo que cuando la elimine en el conmutador de aplicaciones y vuelva a ejecutarla, funcionará de manera normal (cambiando de cámara, frontal/trasera y todo).

EL DESBLOQUEO DE ARRANQUE ES ANTES O DESPUES DE PARCHEAR EL AP

 

[ch3mn3y]

Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.

 

[ShaDisNX255]

Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.

Well then, there you go. You got bootloop for not following the instructions

 

[luffy786]

Did i understand right?

2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC

These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?

 

[ShaDisNX255]

Did i understand right?


These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?

You can install the Magisk app without being rooted. It's an app like any other app, you simply won't have root access. So install it on your A52s 5G and patch your files with it.

 

[BlueChris]

Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?

 

[ShaDisNX255]

Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?

Well, I added these 2 lines:
wlan.wfd.hdcp=disable wifi.interface=wlan0

On the following files:

product/etc/build.prop
system/build.prop
system/system_ext/etc/build.prop
vendor/build.prop
vendor/default.prop

I'm pretty sure not all of them are needed but I'm too lazy to figure out which prop file really needs it lmao if I had to take a guess I'd say either vendor build.prop or default.prop, who knows.