Okay so I've tested around with some apps and somehow WhatsApp and Snapchat were able to access the camera though I have no idea why and why the main camera app can't.
Okay so I've tested around with some apps and somehow WhatsApp and Snapchat were able to access the camera though I have no idea why and why the main camera app can't.
Okay so I've tested around with some apps and somehow WhatsApp and Snapchat were able to access the camera though I have no idea why and why the main camera app can't.
Perfect. Works.Install the MagiskHide Props Config with magisk, use a terminal emulater and type SU then enter then type props and enter, wait for a list of options. take #2 then select "c" (without the quotes) to set a custom value and enter and then type SM-A526B and enter, say Y to the next two options, then Y to reboot. That will get camera working by spoofing a phone other than the A52S.
What terminal emulator are you using? Termux doesn't seem to have the SU commandInstall the MagiskHide Props Config with magisk, use a terminal emulater and type SU then enter then type props and enter, wait for a list of options. take #2 then select "c" (without the quotes) to set a custom value and enter and then type SM-A526B and enter, say Y to the next two options, then Y to reboot. That will get camera working by spoofing a phone other than the A52S.
i used termux actually, see the screen shot. at the $ type su and enter.What terminal emulator are you using? Termux doesn't seem to have the SU command
Nope everything working fine here in all banking apps, google wallet, paying with nfc etc.Hi guys.
I also bought an A52s 5G. I am very satisfied, perhaps the best current mid-range smartphone. I want to root but I read somewhere that Magisk Hide doesn't work. So neither banking apps nor Google Pay and others work. I'm right?
Thanks, greetings.
Have a look at this link. This may help youGuys, 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. Acacia wood
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).
Hello.Install the MagiskHide Props Config with magisk, use a terminal emulater and type SU then enter then type props and enter, wait for a list of options. take #2 then select "c" (without the quotes) to set a custom value and enter and then type SM-A526B and enter, say Y to the next two options, then Y to reboot. That will get camera working by spoofing a phone other than the A52S.
did you install the MagiskHide Props Config via magisk modules?Hello.
I already have the phone rooted and everything is perfect but the camera does not work.
I am doing this tutorial but when I type "props" I get the message: inaccessible or not found
What should I do?
Thanks
Now perfect, thanks mate.did you install the MagiskHide Props Config via magisk modules?
Glad to read that.
english only on xda, use translator pleaseHi , Hallo ich habe immer noch ein Kamera Proplem Nach Root und TWRP installation habe alles aus euren Beiträgen auspropiert ohne erfolg hat jemand vieleicht noch eine idee?
Hi! Will this method work in Android 13?
there is a better method now that we have twrp. install twrp with the vbmeta file at the post for it and follow all instructions completely. have magisk apk on your phone, and also rename a copy of it to magisk.zip on your phone in the external card. reboot to the twrp and install the magisk.zip. then when back into your phone, install the magisk.apk and open it. it will say it has to reboot so do so. when it has rebooted, you are done
Even in Android 13? No more camera issue?there is a better method now that we have twrp. install twrp with the vbmeta file at the post for it and follow all instructions completely. have magisk apk on your phone, and also rename a copy of it to magisk.zip on your phone in the external card. reboot to the twrp and install the magisk.zip. then when back into your phone, install the magisk.apk and open it. it will say it has to reboot so do so. when it has rebooted, you are done
![]()
[RECOVERY][OFFICIAL] TWRP 3.7.0-2 for Galaxy A52s 5G
Team Win Recovery Project #include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research...forum.xda-developers.com
Even no camera issue on Android 13!
Okay so I've tested around with some apps and somehow WhatsApp and Snapchat were able to access the camera though I have no idea why and why the main camera app can't.
Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHooGuys, 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).