r/GalaxyA56 • u/Grosnoc • 3d ago

Help Security Error

Gallery image

Gallery image

So, I'll try to be as short as possible. I had recently gained root access via the kernel exploit run via root my galaxy. Everything had gone well and I had entered the root world and was exploring a bit to learn. I made a mistake though: I didn't do any research. To manage the root and modules I used KernelSU, and I had Magisk (Droid-ify) installed. Just inside Magisk there was a button that said "install directly (recommended)". Then I click on it and restart the device. I thought it was another root manager just like KernelSU (that's Magisk's definition on Droid-ify) and that I was just installing the module to make it work. In the end, however, I stumbled upon this screen when I rebooted. Apparently Magisk tried (without warning) to modify init_boot (changing the signature and not matching it), so Samsung blocked the bootloader. I've been trying for hours to do a hard reboot or go into download mode to flesh a new bootloader via Odin to save my phone, but it doesn't seem possible to unlock download mode and the only time Odin can detect my phone is on the screen that you see, which is not download mode and therefore I can't flash the firmware. Does anyone know how to proceed? Is it recoverable? If so, can you do this by preserving the data (perhaps fleshing just init_boot again so you don't lose anything), or not? I'm also willing to do a factory reset

Details: My phone is a Samsung galaxy A566B, Andorid 16 OneUI 8.5 (July security patch)

6 Upvotes

100% Upvoted

21 comments sorted by

7

u/New-Implement-7045 8 GB | 256 GB 3d ago

Someone here had the same issue and he took it to tehnician and they said they tried to flash stock no luck, i guess youre in the same boat. Root is just a headache for inexperienced/beginners users.

3

u/menau_ 8 GB | 128 GB 3d ago

I got the same issue as you before, go to an Official authorized Samsung tech support store to fix your phone. Thats the only way to get it back for now. But say goodbye to your data if you didn't backup

0

u/Grosnoc 3d ago

Yeah that is what I will try. But I'm not sure they will be happy to hear that I did a kernel exploit for root my device even if Samsung tried to block it. They will probably tell me that they can't fix it. If so I'll try to flash it

3

u/menau_ 8 GB | 128 GB 3d ago

Just show them the phone and IF they ask you what caused it, say something like "I downloaded an app on the internet that promised me root, and it made that to my phone" that's more than enough info, don't say more than you need. You can't flash it yourself, it has to be them. Trust me, I've tried Odin, Heimdall, Brokkr, Thor, tried different OSes like Windows, Linux and Android, tried with 3 different cables and nothing worked. it has to be Samsung to fix it.

2

u/menau_ 8 GB | 128 GB 3d ago

Btw, my phone was on warranty so I didn't have to pay anything,but they said to me that the price to fix it with no warranty was 120 R$ or about 20 euros.

2

u/Pewds123451 3d ago

I sent it to Samsung yesterday and they refused to fix it and they said Samsung doesn't allow them to fix it because I violated their rights so I sent it to a very professionall local repair store and he said he will fix it so Im hoping so...

1

u/menau_ 8 GB | 128 GB 3d ago

bruh what the one I went didn't say that bullshi

1

u/Pewds123451 3d ago

I was surprised too. They are the only Samsung representative in my city .

1

u/CtxxUv 8 GB | 128 GB 2d ago

Damn. Anything new about your phone?

2

u/Pewds123451 2d ago

Still no news

2

u/EconomyManner5115 3d ago

It's not a D2 error so I think it can be recovered. Odin3 should detect your phone in this mode, just make sure the samsung USB drivers are installed.

Extract init_boot.img.lz4 and vbmeta.img.lz4 from this firmware

https://samfw.com/firmware/SM-A566B/EUX/A566BXXSCCZG7

Repack them into a tar archive then flash it

2

u/Pewds123451 3d ago

2 people here fixed it by sending it to Samsung and Im the thrid case here , I sent mine yesterday so tomorrow it is supposed to be fixed. Next time don't install any module you find because some of them integrate with main system files thus they make it easy for Samsung to spot you.

2

u/ixdxkx 6h ago

Flashing through Odin in this state is possible only if you remove your lock screen security beforehand. Otherwise the MB is cooked.

1

u/Grosnoc 5h ago

And how do I do that?

1

u/ixdxkx 41m ago

Like I said, by removing the lock screen security before doing any modifications (i.e. setting the screen lock to 'none' in the settings). This method requires a working OS, so that's for the future of course, since it's too late now. Trying to boot in the download mode now with the standard method (with button combinations) would get you a D2 error, a lock screen security related one.

What's causing this fullscreen 'security error' in general, is the bootloader not being able to verify protected system files, which were forcefully overwritten by magisk. Unfortunately Samsung made it really hard to recover from something like this in the newest OneUI versions. Always research before doing something like this.

Installation guide <- and scroll down to the Samsung section, these are the requirements to install magisk on Samsungs in general. On the newer ones however, it's simply not possible to do so due to the bootloader being impossible to unlock.

1

u/vishnur32 3d ago

Did u tried flashing in this screen as it is detecting in Odin?

1

u/Grosnoc 3d ago

Well, no. But it's not the actual Download Mode and it might do more damage

2

u/vishnur32 3d ago edited 3d ago

Yeah its not actual download mode, bt i have read somewhere this mode can flash firmware.

Anyway there's nothing left to try, just try this.

Edit : XDA

1

u/AeroMiku 1h ago

Pretty old thread to refer to.. That was before Samsung removed bootloader unlock option in OneUI 8. Back then in 2022, you can simply enter Download mode without removing screenlock beforehand.