yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] redymedan:
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
[Samsung Galaxy A52 4G] kidkree1:
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?
[Samsung Galaxy A52 4G] redymedan:
Yes, it works
[Samsung Galaxy A52 4G] hammeru:
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.
[Samsung Galaxy A52 4G] Faakarna:
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
[Samsung Galaxy A52 4G] ShaDisNX255:
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)
[Samsung Galaxy A52 4G] Simon1511:
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?
[Samsung Galaxy A52 4G] ShaDisNX255:
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
[Samsung Galaxy A52 4G] Simon1511:
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
[Samsung Galaxy A52 4G] ShaDisNX255:
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.
[Samsung Galaxy A52 4G] Simon1511:
Ok, thanks. Was just curious if relocking BL could fix it
[Samsung Galaxy A52 4G] Ali Shabbir:
Magisk Hide has been removed from the main server, so it won't pass CTS now. There is a fix, please search!
[Samsung Galaxy A52 4G] FlugHund:
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.
[Samsung Galaxy A52 4G] ARCHANGELGABRIEL:
Did you figure out how to fix this?? I have the same issue!
[Samsung Galaxy A52 4G] ARCHANGELGABRIEL:
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
[Samsung Galaxy A52 4G] Cyberbloc:
DID YOU FIND SOLUTION TO THIS? I HAVE SAME LOGO ISSUE AND WANT TO REMOVE BOOTLADER UNLOCKED RED ALERT
[Samsung Galaxy A52 4G] frenxl:
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.
[Samsung Galaxy A52 4G] ShaDisNX255:
Because you can't flash root files using stock recovery, they're unofficial files.
[Samsung Galaxy A52 4G] gebxda:
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!
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] uotlaf:
Download

View attachment 5350209View attachment 5350211View attachment 5350215

Known issues:

You can tell me

What works:

Flashing

Touch screen (It works without waiting the 10 seconds!)

Encryption(up to android 11)

Backup and Restore(up to android 11)

Sensors(battery, temp, etc)

Fastbootd

WARNING

This device uses Dynamic Partitions

This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.

In order to flash the individual partitions, you will have to boot into fastbootd.
​

TWRP for Motorola One Fusion (Astro)

Contribuitors

Uotlaf, Pedro Henrique Lima Abreu, Martin

Source code: https://github.com/TeamWin

Source Code:

TWRP: https://github.com/omnirom/android_bootable_recovery

Device Tree: https://github.com/sdm710-motorola/android_device_motorola_astro_twrp

Version Information

Status: Stable

Current Stable Version: 3.6.1-_11-0_v1

Stable Release Date: 2022-03-03

Current Beta Version: -

Beta Release Date: -

Created 2021-06-28

Last Updated 2022-03-03
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] uotlaf:
Reserved
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] uotlaf:
3.6.1-11-0_v1:
Update to RPLS(Android 11)
Fix ~10sec to init touchscreen
Fix vibracall stopping out of nowhere
3.5.2-10-0_v2:
Fixed mount sdcard
Fastbootd working
3.5.2-10-0_v1:
Initial Release
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] dpkg-i-foo-deb:
You should try using fastboot to flash them as that is the way you're supposed to do it :D
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] uotlaf:
yep. It works
[Motorola One Fusion ROMs, Kernels, Recoveries, & O] reddermanu:
@uotlaf please update to Android 12 encryption for use with android 12 gsi custom roms 🤩🤩
[Google Camera Mods] gkornaks:
Thanks for the app! Filters are not working on Asus Zenfone 8.
[Google Camera Mods] mjun1:
When you say "not working", you mean:

- app crashes OR

- functionality itself doesn't provide expected result

?

Can you provide some stack trace / log of what happens when you try to open filters? Unfortunately I don't have this device so can't test it myself.
[Google Camera Mods] gkornaks:
The functionality is not working. Not applying filters. How can I provide a trace/log?
[Google Camera Mods] tortino:
On Samsung A50 the filters work, I just tried with seppia and it was applied correctly.
[Google Camera Mods] mjun1:
Usually by connecting your device to your computer and running adb logcat and looking for lines that contain the word cameralite. But there are also logcat (and general logging) applications available for running directly on phone.

But if I'm not mistaken Asus Zenfone 8 is running on Android 11 - I think this will not work correctly as Google Camera Go is supporting Android versions from 8.0 to 10.0. I think that next round of budget phones will use Android Go 11 platform which will in turn also provide newer Go flavored apks which might be better supported.
[Google Camera Mods] tortino:
my a50 is running android 11 and the filters seems to work correctly.

I didn't tested other functionality apart taking some photos and the seppia filter.
[Google Camera Mods] gkornaks:
Thanks! Yes, I'm on A11. Also noticed that photos not stamped with location.
[Google Camera Mods] G.C.Mukonde:
Filters and location not working on Android 10
[Google Camera Mods] G.C.Mukonde:
Filters and location not working but the rest is ok thanks
[Google Camera Mods] nereis:
Works fine on Android 11 with Pixel 3 so not a version issue.
[Google Camera Mods] philipped346:
big thank for this work !

work fine on my nexus 5 , only location don't work .
[Google Camera Mods] ajaysinghmaan:
If you could increase the resolution of night mode to at least 8mp and make hdr image a little sharper with lesser exposure, it would be perfect for many many devices without gcam , would really appreciate if you can ( if possible).
[Google Camera Mods] mik101:
Working great here on a Redmi Note Pro 5 running LoS 18.1. Thank you for your efforts.

Edit: location tagging isn't working on my device, night mode looks a little worse than Greatness' GCamGo, and a few other little issues on my particular device. It's still a viable option for many users wanting a version of GCamGo for their devices.
[Google Camera Mods] Medicineguy:
I wish the option to mute camera sounds was there.

Other than that, very good and thank you.
[Google Camera Mods] Migush:
Camera GO <v2.8 has an issue with my phone were pressing the capture button does nothing. Camera GO 2.8 works fine, however, I'd love to have this modded version working! Any chances of porting this to 2.8?
[Google Camera Mods] GroovyG:
Awesome! Just what I needed running a AOSP ROM.

Looking forward to future releases :)
[Google Camera Mods] Hausemaster:
This is the best version of modded gcam go so far, thank you, sir!

Eidt, eventually more features will be available, so I hope something in the community will keep the gcam go modding scene alive, reason being that this app can run on Exynos devices, and that's a big win!
[Google Camera Mods] nvidamd:
It's good to see new Gcam go mod. I'll have check this.

Anw, do you have find a way to use regular Gcam in XA2 without UB?
[Google Camera Mods] Tizu69:
Doesn't seem to work on my phone (Xiaomi Mi 10T Lite using Pixel Experience, Android 12), it's just showing this error message which I've never seen before.
[Google Camera Mods] Fr0styyyy:
Filters aren't working on infinix note 10 pro.
[Google Camera Mods] Hausemaster:
This app probably doesn't support Android 12...
[Google Camera Mods] Tizu69:
No, it does. I just had an old version of gcam that was preinstalled with my rom installed, but hidden
[Google Camera Mods] Argonon:
Just about everything but filters work and I haven't tried translate yet. It's much better than the stock mtk camera. My device has crap specs lol it's Android Go Phone. 32bit binder64. At least it's on Android 13. I pulled stock boot and magisk patched it. Thanks so much. I'll use as daily driver cam for this device! Vortex ZG55 Android Go Tirisamu
[Fire TV Android Development] 9lalex9:
Is eFuse removed in the firmware?
[Fire TV Android Development] Sus_i:
Afaik the efuse doesn't burn during ROM flashing (i.e. you can't find the efuse burning in the updater scripts).

Afaik it can only burn, if TZ gets an update during ROM flashing, then the efuse gets burned at the next reboot (only possible in case of a locked Stick = stock recovery).

But as you know, for an unlocked stick, TWRP recovery will block updating/flashing TZ to tee1 and 2, same for LK and PL images. No LK/TZ updates = no fuse burning ;)

I think @9lalex9 asked about what rbox did with his last prerooted, cuz rbox removed the kernel script that burns the efuse in the boot.img of his prerooted Rom. This is not needed as long as TWRP is always there, but it if you like you can do it too. Maybe ask @Pretoriano80 I guess he can tell you some detailed things about the kernel :) Another way may be to grab the prerooted rom as source for your modded rom...

Yes. You're right, it's awful, the most terrible thing they did in the last years^^

So keep going on with this, please :)
[Fire TV Android Development] SweenWolf:
Can you also fix Accessibility? Only thing which is keeping me from upgrading

@

Sus_i​

[EDIT]

So I was thinking of patching to fix Accessibility,

I have deodexed the ROMs and I was thinking of following few approaches.

1. Replace logan

2. Replace Services with older version

3. Try to patch the jar of Services.

Even though i have some experience with smali jar and basic stuff but i have no experience with binary files.

Now i have some questions relating some problems.

Changing stuff in TWRP does not affect the System

So i have to find a way to flash without taking to much time.

And what's the matter with efuse??

On which version does it blow up and what are the caveats?
[Fire TV Android Development] SweenWolf:
Hi again,

I have patched this file (fosservices.jar) its from 6.2.7.3, can anyone check if it fixes accessibility.
[Fire TV Android Development] Skel40:
Where can I overwrite this file? 6.2.7.3 patches accessibility. Get the file from 6.2.7.1. I'm glad to test it out rn
[Fire TV Android Development] SweenWolf:
replace this with /system/framework/fosservices.jar , there should also be an odex file in /system/framework/oat/arm/fosservices.odex (delete this file).

this file is from 6.2.7.3 where accessibility services are restricted to system apps only.

on 6.2.7.1 there is no such restriction.

if you are on 6.2.7.1 then theres no need to test because accessibility works just fine. i need to test this on newer version, and i am also unable to download your zip file for whatever reason. if i had then i could have gave you patched version from 6.2.8.0

The reason why I am not doing is because i have removed root and TWRP.

if this worked on 6.2.8.0 then i will update to that using TWRP, remove OTA apps, and patch this file and lock the bootloader again.

[Question] If i relock the bootloader and it replaces the boot image with stock one. will it blow the efuse?
[Fire TV Android Development] Skel40:
Thanks for getting back to me. That's strange. It's downloading fine on my end. I'll try to upload it on mega or something like that. That's not recommended. Any OS after 6.2.7.7 will blow the efuse on a locked bootloader so the exploit is no longer working unless you kept your device in an unlocked state like mine. I own 3 4K's fully unlocked with 6.2.7.7 because of older easy to navigate ui and the efuse being disabled as well thanks to TWRP. Once you're unlocked you're safe. What I should recommend instead is getting one of the latest pre-rooted roms available due to the efuse check being removed then replace the boot.img. Don't update with the official stock version as that will keep your device locked for good. No bootrom to access anymore. It's impossible so if you want to take the risk go ahead but I don't advise doing so.
[Fire TV Android Development] SweenWolf:
Thanks, I was reading other post on XDA where people are stuck with locked bootloader on 6.2.8.0, I do not do OTA updates, and I certainly don't update without assurance that my apps work fine on it. i was thinking of getting an image and make some changes by removing the efuse binaries from bin and also was thinking of unlocking ADB on Boot.img and if found removing efuse from there, the thing is i have to patch boot.img as my stick becomes unstable with TWRP. but for now I just wanted to go 6.2.7.3 and check if everything goes right i will stay on it else jump back to 6.2.7.1

Sorry for bothering you, what version introduced profile in FireTV?
[Fire TV Android Development] Skel40:
That makes sense! I don't update thru ota either. This is off topic but do you know why updating the settings V2 app on 6.2.7.1 won't do anything to add av sync tuning and wifi icons by any chance? It acts like an update but doesn't add those features in. Maybe it's the .jar files? I also have a slight issue with my old UI rom too. Its laggy as if something heavy is running in the background. Do you think I should run a logcat? I'll need to upload the rom to mega for you to see and possibly fix. The version that introduced profiles was 6.2.8.0_3233
[Fire TV Android Development] Skel40:
@SweenWolf I tried the .jar file. It bootloops on version 6.2.8.0_3236
[Fire TV Android Development] SweenWolf:
Thanks for trying but this is to be installed on 6.2.7.3 not 6.2.8.0, I thought you had that, let me download the app from mega and then patch the file of 6.2.8.0
[Fire TV Android Development] Skel40:
My fault. I should've paid attention..
[Fire TV Android Development] SweenWolf:
i haven't checked but as far as i know, the actual code is in the settings V2, but the shortcuts are embedded in the amazon launcher, so there will be two icons in two different places one in the network activity of the Settings apk where as the other is on Amazon Launcher itself.
[Fire TV Android Development] SweenWolf:
here is the patched version from the rom you provided.

try this one and make sure you have given correct permissions i.e. 644
[Fire TV Android Development] Pretoriano80:
People stuck with locked bootloader on 6.2.8.0 most likely never unlocked it before updating to 6.2.8.0.

Devices unlocked previously, before 6.2.8.0 are fine, unless you restore everything to stock, including boot, recovery, bootloader, and tz.

Also, as long as you keep TWRP (i don't know why you removed yours) then you are pretty safe, even if you install a full stock rom (TWRP has a failsafe mechanism which prevents flashing the critical images (recovery, tz, and bootloader).

As for modifying the boot image, there's not much to do, just disabling the efuse_check or anything efuse related from the ramdisk.
[Fire TV Android Development] SweenWolf:
Thanks for the info, my stick randomly reboots itself if i have TWRP installed.

And File Manager of TWRP had no affect on the System partition (for me atleast)

And I also always has a pendrive attached with the stick with some movies and videos on it.

Which cause boot delay also because it waits for TWRP.

I upgraded to 6273 and there was no Accessibility, so i had to unlock the bootloader once again to go back to 6271.

I use many apps which requires Accessibility like and two main ones are for Launcher and for Mouse Services.

As i don't use google play services or make any changes to the system and with 6271 being last version to support Accessibility i decided to stick with it and just disable updates. And relocked the bootloader, because i had no use of TWRP anymore. Until now, if Accessibility is fixed i might upgrade.

But like you said, it burns the fuse when we update the TZ and that can only be updated by the recovery, TWRP will never update the TZ so we are safe, but even the stock recovery needs an update package to flash the TZ right?

Because of the script it will delete the efuse check and ewriter then it will not blow the fuse, Just like in OP.

Even if i then relock the bootloader, and the updates will be blocked to the system, because there are some update apps which sideloads the OTA package (i read their codes) then if their are no offline update file present in the system how will the stock recovery flash the TZ.

I'm just asking, i know amazon also has some tricks under their sleeves and they can do something notorious.
[Fire TV Android Development] Skel40:
I confirm Accessibility works on 6.2.8.0 3236. Thanks @SweenWolf

I used Total Commander for chmod without commands too
[Fire TV Android Development] SweenWolf:
Good to hear, one more question. How have you disabled the OTA check, i was thinking of patching OTA files also
[Fire TV Android Development] hasobist:
Hello!

Wonder the apps never get auto updated by the Appstore.

Set to auto is good.

Hope your network issue gets resolved.

Cheers!
[Fire TV Android Development] Skel40:
Anytime! Try these two and let me know if it fixes the issue? One of them is responsible for the monitor screen to show up with your resolution, network, etc with its developer options and adding proxies. The other one allows the Wi-Fi connection test in settings to work and is seperate from the monitor screen. If it still doesn't work, I'll update you with the provisioner and recess apps
[Fire TV Android Development] Videophile:
Thanks again :),

I got the base installed ok but the:

System_Status_Monitor_SystemStatusMonitor.apk

Seems to be corrupt.

Do I need to install this in an alternate way?

So far, since updating what I have been able to; I haven't had any drop outs... Fingers crossed it's fixed.
[Fire TV Android Development] Skel40:
You're welcome. If the other one is corrupted don't worry about that. It's already installed in the system by default and isn't meant for apk install. Awesome that the base installed correctly. This should now fix the speed test without the "system update" prompt and your Wi-Fi. Do a reboot and let me know again if it's working 😇
[Fire TV Android Development] Videophile:
Unfortunately I'm still getting the WiFi drop and can't access settings when it does. :(

Didn't drop at all weekend but has just happened again this evening.

*Edit*

However, this time, when restarting it does fix itself and the WiFi connects and holds.

So it's definitely been improved.
[Fire TV Android Development] ROM_gamer987:
Magisk says it's not installed for me, also did anyone test gapps yet?
[Fire TV Android Development] Videophile:
Can you think of any thing else to try? Perhaps some other apps that might benefit from updating? Starting to think this is definitely a hardware issue.

Thanks for all your help.
[Fire TV Android Development] Videophile:
Install Magisk 25.1 FTV from tsyniks post here:

His Google drive link has all you need.

Google Drive

His post for gapps is here too: with other apps included if you want to try.

https://xdaforums.com/t/magisk-module-firetv-4k-stick-add-ons.3979117/
[Fire TV Android Development] ROM_gamer987:
Do I use AFTV-MM or AFTV-GAPPS?
[Fire TV Android Development] Videophile:
It's either AFTV-MM or AFTV-MM-GAPPS

So one with one without Google apps

For Magisk you'll want to go in the Magisk folder.
[Fire TV Android Development] Skel40:
I haven't tested gapps yet. I released a new 6.7.0.0 version on my OP
[Fire TV Android Development] Videophile:
@Skel40 do you have any other ideas to try and fix my WiFi drops? Still having the issue with it dropping on only this Firestick. Thanks :)
[Fire TV Android Development] Skel40:
Have you updated to the 6.7.0.0 rom on my OP? If that still doesn't work, try clearing the dalvik and cache in TWRP
[Fire TV Android Development] Videophile:
All updated. No issue for a week or so, but now issue has returned. WiFi completely drops. Can't get into network settings either. Won't open when clicking "network" in Firestick about menu. Any last ditch attempts I can try before giving up and throwing this stick out.

The fact I can't get into the network settings menu when this happens still makes me think it's something to do with the Firestick itself.

As always, your help is thoroughly appreciated.