Database Info

Root, ext4

I'm trying to root a Samsung Galaxy A30s with Android 10.
Till now I deactivated FRP and unlocked the bootloader.
I successfully extracted (with lz4_win64_v1_9_2) from boot.img.lz4 to boot.img.ext4, but now I need to extract boot.img.ext4 to boot.img as I saw it is written here. I tried with ext4_unpacker; Ext2explore-2.2.71. No luck.
Tried forward to extract with lz4_win64_v1_9_2, but it says "header unrecognized". I'll upload a screenshot to see the steps I've been through.
If somebody have a full method to root this type of phone will be great. Or just how to bring ext4 file to boot.img.
Also I'm interested if xposed framework it's working on.
L.E: Ok. I managed to extract boot.img, intall magisk to my phone, patch the boot.img. Then recompile the new file magisk_patched.img in magisk_patched.img.l4z and then again to magisk_patched.tar for ODIN. But when I try to flash it with ODIN it fails. FRP off, OEM LOCK OFF, Secure download: enabled.
Thank you!

[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi 10X 4G / Xiaomi Redmi Note 9)

PATCHED VBMETA.IMG for MERLIN by VD171
For what do I need it ?
If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once only. Once flashed, you don't need to flash vbmeta again.
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM
- V12.0.1.0.RJOMIXM
- V12.0.8.0.QJOMIXM
- V12.0.7.0.QJOMIXM
- V12.0.6.0.QJOMIXM
- V12.0.5.0.QJOMIXM
- V12.0.4.0.QJOMIXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
How to flash it?
Code:
fastboot flash vbmeta vbmeta_vd171.img
MD5 hashes:
AL2522-Merlin-V039-Q-0513: ca9ccb577b5a1efd348949f9ed99409f
AL2522-Merlin-V044-Q-0920: dccbc87dbedc7f758120feac72e6c6cf
V12.5.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.8.0.QJOMIXM: 4a59b0481aa2a3bd5381fd51d2da3184
V12.0.7.0.QJOMIXM: 64fa528e39ebcd4838b92d5b120b0035
V12.0.6.0.QJOMIXM: 974e9c3462b4346a70ff370f6c28527b
V12.0.5.0.QJOMIXM: 7c68fe2373188e20abd4f1c68cb949b1
V12.0.4.0.QJOMIXM: 39ef5250fd562e20b6530cf8a0a96943
V12.0.3.0.QJOMIXM: 13c896c8dc4924bed5b63673a0a38a1a
V11.0.5.0.QJOMIXM: 2323b64102370a98f1641bc4d8227c52
V11.0.4.0.QJOMIXM: 666c0fbbd4d329001290277fcfd052d8
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171

empty.cad said:
Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171
Click to expand...
Click to collapse
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz. You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you got patched boot.img and patched vbmeta.img files.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it

empty.cad said:
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it
Click to expand...
Click to collapse
Did you unlock the bootloader?
The patched boot and patched vbmeta are enough to root it, but it requires unlocked bootloader.

Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.

bismeet said:
Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.
Click to expand...
Click to collapse
Try to flash the whole MIUI again and try to root again following properly the steps.

VD171 said:
Try to flash the whole MIUI again and try to root again following properly the steps.
Click to expand...
Click to collapse
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.

bismeet said:
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.
Click to expand...
Click to collapse
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?

VD171 said:
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?
Click to expand...
Click to collapse
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.

bismeet said:
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.
Click to expand...
Click to collapse
I know. You need keep trying other usb ports and usb cables.

VD171 said:
I know. You need keep trying other usb ports and usb cables.
Click to expand...
Click to collapse
Tried all. Guess I need to add new ports to my phones and laptops.

bismeet said:
Tried all. Guess I need to add new ports to my phones and laptops.
Click to expand...
Click to collapse
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.

VD171 said:
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.
Click to expand...
Click to collapse
Okay.
I guess this phone is not rootable.
Never buying mtk device again.

bismeet said:
Okay.
I guess this phone is not rootable.
Never buying mtk device again.
Click to expand...
Click to collapse
What is your device?

VD171 said:
What is your device?
Click to expand...
Click to collapse
Redmi note 9 mtk version from India/

bismeet said:
Redmi note 9 mtk version from India/
Click to expand...
Click to collapse
Everyone has already rooted it.

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)

llxxVENOMxxll said:
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)
Click to expand...
Click to collapse
Yes, you can't flash patched vbmeta while bootloader is locked.
You need to unlock bootloader first if you want to apply any change to any partition.

How To Guide [Pixel 7 Pro] [TD1A.220804.031] Root guide + Extracted Images + How to

How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila

A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot

Reserved

Thanks!

Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk

I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).

Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).

so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img

I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro

mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image

Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking

I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?

whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.

Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.

zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.

mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?

Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459

whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.

Magisk zip install on TWRP, now Lineage OS wont boot

When booting now just stuck on "Boot loader is unlocked" warning screen. When booting into TWRP using volume and power buttons, all my restore options are random alphanumeric characters (I think this means encryption...).
I checked both slots, one is for the bootwarning screen, other is for TWRP... What do....

restore the backup of vendor or use from download. reason: magisk from recovery requires parameter to preserve encryption, otherwise the fstab is modified in a way encryption is no longer functional.

alecxs said:
restore the backup of vendor or use from download. reason: magisk from recovery requires parameter to preserve encryption, otherwise the fstab is modified in a way encryption is no longer functional.
Click to expand...
Click to collapse
How can I restore anything in TWRP if everything is alphanumeric babel (encrypted)?
What are my options realistically in this situation?

download vendor and flash from fastboot or adb

alecxs said:
download vendor and flash from fastboot or adb
Click to expand...
Click to collapse
As in a vendor blob? Where do I download it?

I don't know what ROM, just examples
[ROM][OFFICIAL][enchilada][13] LineageOS 20
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As OnePlus doesn't always provide download links for all of for their Oxygen OS ROMs & OTA update zips, we mirrored them on AndroidFileHost and put the links in one post so that they're easy to find. This is not a support thread for issues you...
forum.xda-developers.com
you need to extract with payload dumper
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com

Odin have somes problems when i flash patched Samsung Galaxy A03 image

Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up

Feox said:
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Click to expand...
Click to collapse
Feox said:
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
Click to expand...
Click to collapse
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.

ethical_haquer said:
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
Click to expand...
Click to collapse
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...

Feox said:
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Click to expand...
Click to collapse
So you are following the official installation instructions? I'm pretty sure you don't have to:
Feox said:
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
Click to expand...
Click to collapse
as the official installation instructions for a Samsung device running A9 or higher say:
"
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
"
It doesn't sound like you have to isolate the boot.img.

Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?

Feox said:
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Click to expand...
Click to collapse
Just read the official installation instructions I linked to. I only copied part of it and pasted it here so you could see it.