Develop Bugs

"the system has been destroyed" HELP!

so today i decided to root my Redmi note 8T. and now i deeply regret it. I had no idea what i was doing and now im ended up with "The system has been destroyed". what can i do now? ive tried flashing a new rom on to it with mi flash tool, but it gave me a "can not find flash_all_lock.bin" so now i cant do anything. the only thing i can get into is fastboot mode. what can i do to fix this?
help is much appreciated.

hecc_itsme said:
so today i decided to root my Redmi note 8T. and now i deeply regret it. I had no idea what i was doing and now im ended up with "The system has been destroyed". what can i do now? ive tried flashing a new rom on to it with mi flash tool, but it gave me a "can not find flash_all_lock.bin" so now i cant do anything. the only thing i can get into is fastboot mode. what can i do to fix this?
help is much appreciated.
Click to expand...
Click to collapse
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6

got it fixed.
mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
Click to expand...
Click to collapse
well. i got the system is destroyed thing fixed by unlocking again with the unlock tool , i guess i didnt give enough context. i was trying to re-lock it after regretting ever touching that "Unlock Now" button and i tried the command line method that every video i found used. and thats what threw me in that hell. i still havnt figured out how to re-lock the bootloader though. any chance you know how? thanks.

hecc_itsme said:
well. i got the system is destroyed thing fixed by unlocking again with the unlock tool , i guess i didnt give enough context. i was trying to re-lock it after regretting ever touching that "Unlock Now" button and i tried the command line method that every video i found used. and thats what threw me in that hell. i still havnt figured out how to re-lock the bootloader though. any chance you know how? thanks.
Click to expand...
Click to collapse
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869

mrmazak said:
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869
Click to expand...
Click to collapse
Does that actually work? Kinda scared to do things now. If it works, why isn't it the first result that comes up when someone Googles it? It would be so much easier

any idea what this means in mi flash... error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done

bluefender said:
any idea what this means in mi flash... error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
Click to expand...
Click to collapse
Not sure. I did see other person post that they had that message, and can't remember what they did to get around. But this should show up if you search the note 8 forums

mrmazak said:
yes.
you seemed to have been on the correct path before. but maybe you didn't have the fastboot rom downloaded.
The message you had as an error was "flash-all-lock file not found" this file (just a windows batch file by the way).
if you made ANY changes with unlocked bootloader, then locking it most dangerous.
Its recommended to use the flash-all-lock method.
maybe, if you are having trouble with the manual flashing, you can use a "tool" to do all the work. Like this one
https://forum.xda-developers.com/redmi-note-8/how-to/tool-tool-one-driverstwrpfactory-t4009869
Click to expand...
Click to collapse
so, it would be dangerous if i already flashed twrp on it?

mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6
Click to expand...
Click to collapse
well since i now want to re-lock it i tried doing that but the same problem still occurs.

hecc_itsme said:
so, it would be dangerous if i already flashed twrp on it?
Click to expand...
Click to collapse
Yes it will.

mrmazak said:
Yes it will.
Click to expand...
Click to collapse
so should i just give up on trying to re-lock it?

hecc_itsme said:
so should i just give up on trying to re-lock it?
Click to expand...
Click to collapse
Make sure your system is untouched before relocking. Flash a full fastboot ROM and select clean all and lock. Then your phone can lock and boot up with no problem. Note: Don't flash global version system on a Chinese hardware or vice versa or you will brick.

mrmazak said:
well this is easy to do. I mean both easy to fix and as you now know easy get into this situation.
Little background info here will help you understand what has happened.
Android systems have gone to what is know as avb type system (A.ndroid V.erified B.oot), which means the system knows when the factory supplied software has been changed. The message you received basicly is just telling you , "hey this software is not the same as when it left the factory"
The system know this has been changed by checking files signature information. This signature is stored in a separate partition. The "vbmeta" partition.
When you use any modified system, you are supposed to tell the vbmeta partition to ignore the changes.
You do this by flashing the vbmeta.img to it's partition with a command to disable verification.
***Update will come here when I cut and paste the command and file from the many other threads here with the Info****. Or maybe you do a search and find it before I get to it.
here is a link to the answer
https://forum.xda-developers.com/showpost.php?p=82470133&postcount=6
Click to expand...
Click to collapse
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????

vinay069 said:
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????
Click to expand...
Click to collapse
Yes, if you do not, then the stock recovery gets restored.

mrmazak said:
Yes, if you do not, then the stock recovery gets restored.
Click to expand...
Click to collapse
Ok it so it means vbmeta doesn't destroy system in stock miui rom.... Thanks .... I was very curious about this

hecc_itsme said:
so should i just give up on trying to re-lock it?
Click to expand...
Click to collapse
Just flash fastboot rom via miflash and select "clean_all_and_lock" before flashing. Works perfectly.

vinay069 said:
Do i need to flash vbmeta if i don't flash any custom rom ??? I mean just flash twrp and reboot to stock miui????
Click to expand...
Click to collapse
i think just flashing twrp is enough to make it dangerous, since thats the only thing i did, and the only thing i get is the system has been destroyed. so yeah, i just gave up. i mean it doesnt effect me much anyways

Question I'm very overwhelmed please help

The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.

First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).

samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/boot​This is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recovery​This is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!

samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.

Question Help me understand GIS for Xperia 10 III

I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.

wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.

General Would be nice if....

Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.

bobfrantic said:
Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.
Click to expand...
Click to collapse
I've heard rumors it's located in the actual bootloader, so messing something up there could result in a dead device

ShaDisNX255 said:
I've heard rumors it's located in the actual bootloader, so messing something up there could result in a dead device
Click to expand...
Click to collapse
I decompiled boot.img and found no images

bobfrantic said:
I decompiled boot.img and found no images
Click to expand...
Click to collapse
boot.img is not bootloader. I don't really know which "image" it is exactly but it's definitely not boot.img
Try searching in the BL_ file and decompiling everything there idk

Used to be located it up_param.bin or param.bin (idk anymore if it was in AP or CP) but those files don't exist anymore for some reason. Also wanted to remove it like i used to do on my A50

JanBoyGamer23 said:
Used to be located it up_param.bin or param.bin (idk anymore if it was in AP or CP) but those files don't exist anymore for some reason. Also wanted to remove it like i used to do on my A50
Click to expand...
Click to collapse
up_param.bin don't exsist in snapdragon chipsets. That's what makes finding the warning images so difficult...

I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.

1812CE said:
I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.
Click to expand...
Click to collapse
I can install apps that let me modify things on my phone. Give easy access to root partion to be able to push files to. Also getting ad blocking with AdAway with root instead of vpn which is slow.

1812CE said:
I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.
Click to expand...
Click to collapse
There's some features that Samsung disables on A-series phones. You can activate most with a rooted phone.

bobfrantic said:
Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.
Click to expand...
Click to collapse
By the way, the image is located in abl.elf

ShaDisNX255 said:
By the way, the image is located in abl.elf
Click to expand...
Click to collapse
great and how to access it?? LOL

bobfrantic said:
great and how to access it?? LOL
Click to expand...
Click to collapse
That's the mistery

ShaDisNX255 said:
That's the mistery
Click to expand...
Click to collapse
how do you know then that is where the image(s) are. curious. any kitchen to decompile the file?

bobfrantic said:
how do you know then that is where the image(s) are. curious. any kitchen to decompile the file?
Click to expand...
Click to collapse
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.

ShaDisNX255 said:
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.
Click to expand...
Click to collapse
I took a "brief" look at those threads, didn't read about just deleting the abl.elf file from the bl_xxxx.tar

would be nice if this phone have a AKG speakers ^^

bobfrantic said:
I took a "brief" look at those threads, didn't read about just deleting the abl.elf file from the bl_xxxx.tar
Click to expand...
Click to collapse
I already gave you a tldr, it's simply not possible

ShaDisNX255 said:
I already gave you a tldr, it's simply not possible
Click to expand...
Click to collapse
Tis indeed a dead end at this time. But maybe someone can figure it out...

ShaDisNX255 said:
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.
Click to expand...
Click to collapse
There was some release post on XDA thought of a "modded/patched Odin" which apparently "bypasses all signature checks" or something like that. I wonder if it applies to the bootloader.

SevastianXDA said:
There was some release post on XDA thought of a "modded/patched Odin" which apparently "bypasses all signature checks" or something like that. I wonder if it applies to the bootloader.
Click to expand...
Click to collapse
The phone also checks for stuff, so even if you can bypass Odin's checks, you can't bypass the phone's checks

How To Guide A23 Unlock Bootloader and Root guides with Video

This is not my work, this simply was found and done by others, so all credit to them
Warning Unlocking and rooting your device is not for everyone, and you risk damaging your device so do it at your own risk.
saw several people asking about, so he is the methods.
to unlock boot loader
to root
video
text Guide by Juhn Wu (Magisk creator)
https://topjohnwu.github.io/Magisk/install.html

Still no any other alternative OS?
Any idea what to install instead of samsung OS?

Rupdabe-GalaxyS6EdgePlus said:
Still no any other alternative OS?
Any idea what to install instead of samsung OS?
Click to expand...
Click to collapse
nothing A23 specific that i know of, but you can try GSI roms

theduke7 said:
nothing A23 specific that i know of, but you can try GSI roms
Click to expand...
Click to collapse
Tnx

will this root method work on the boost variant?

this.guy.lol said:
will this root method work on the boost variant?
Click to expand...
Click to collapse
Nope, any Samsung phone that's sold in the US aka having the letter U or DL "not too sure about ones with U1" cannot be rooted due to having a locked down bootloader and no OEM unlock option, it's been like this ever since the S6 back in 2015. an exploit for the SM-A236U and the SM-S236DL would need to be found to even get close to rooting.

this method works. BUT......
i can root my phone. magisk works fine, but apparently I don't have write permissions on /system
it is unusable because android is annoying me with "service provider update.... the phone needs to be restarted." you can't click away either. over and over again.
SM-A236B

So i unlocked the bootloader and flashed with odin magisk patched boot.img and everything is working fine. Except SELinux, which is in permissive mode now. Jeez.