Database Info

[GUIDE] Upgrade/Downgrade between Nougat and Oreo

WARNING: This guide is tested on Nokia 6 TA-1000 only!
ALWAYS DO BACKUP BEFORE PERFORM ANYTHING!
Use Titanium Backup, Internal Backup Tool or...whatever.
中文版教程：http://bbs.dospy.com/viewthread.php?tid=17830185&bbsid=1021&page=1
Click to expand...
Click to collapse
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
If you're running Android O that comes from OTA Update, that means the bootloader must be downgraded before downgrade your phone to Nougat.
If you've already have old bootloader, skip this part.
Click to expand...
Click to collapse
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
Power off your phone, then connect your phone to a charger.
When you see the charging logo, press and hold Volume Up and Power key.
If you see "No command" displayed, release both keys, then press Volume Up while holding Power key. This will pop up a menu.
Click to expand...
Click to collapse
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
If your phone can boot into OS normally, skip this part.
Click to expand...
Click to collapse
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
NOTE: Root package included in recovery isn't compatible with Android Oreo.
Click to expand...
Click to collapse
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.

I successfully sucessfully fw (Oreo) through OST 6.0.4 and have installed TWRP on Oreo.
But the Root package does not work.
I'm testing with the zip install package via TWRP as the MODs for example (Emoji package, Font, ...) Hope it works.

I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?

hawwin88 said:
I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?
Click to expand...
Click to collapse
You can use a text editor (do not use notepad) to edit the md5.dat, and modify the checksum to expected checksum displayed on the phone, then flash again.
I'll reupload the correct package soon.

anyone tested on t 1021

Can we get root access and xposed on oreo or is it still unavailable?.

Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks

TA-1021 Downgrade help
is this method useful for nokia 6 TA-1021??????

hikari_calyx said:
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.
Click to expand...
Click to collapse
Hi, i have Oreo 8.1 install in my ta 1003, initially it was a ta 1000 but i did flash the ta 1003 rom after down grading the bootloader with help of another thread. I want try out this Home brew rom and am not sure how to go about. The ta 1003 has issues with the network, like the VoLTE option is not working.

I cant get to stock recovery manually, I tried holding power and up volume but still not working. I'm using TA 1039 with Android 8.1.
What should i do?
hikari_calyx said:
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
Click to expand...
Click to collapse

Sorry, just one question.
If the TWRP already has those partitions decrypted, can the userdata partition be safely restored after updating from Nougat to Oreo?

does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore

Dantheman221 said:
does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore
Click to expand...
Click to collapse
Change c2dms into oss-cn-hangzhou.aliyuncs :
https://ota-filesite.oss-cn-hangzhou.aliyuncs.com/SWUpdate/500000748

Hello
After updating to Android 9, I lost dm-verity command and TWRP. Fastboot says it's an invalid command now. Help?
Edit: Okay, flashed old bootloader and got dm-verity back. Unlocked bootloader, now am stuck on recovery, won't boot to 7.1.1 OS. Help?

[GUIDE][ROOT]Galaxy M30S Bootloader Unlocking and Rooting Guide

Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.​
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
Method 1
1. Download the latest firmware for your device.
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
3. Install the latest Magisk Manager
4. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
5. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar, Copy the patched file to your PC.
6. Download and extract odin(link given below).
7. Install Samsung USB drivers if not installed automatically.
8. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
9. Flash magisk_patched.tar as AP in Odin, together with the BL, CP and CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
10. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
11. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
12. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
13. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
14. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
15. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
16. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
17. Enjoy Magisk
Method 2
INS Only
*To Make Things Easier*
1. Download the firmware(already patched) from the link given below
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Flash AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Continue steps from 10 to 17 from method 1
Method 3: Rooting with TWRP[Thread]
1. Download Twrp based on ASL2 firmware only which already have magisk patched.
2. Go to download mode
3. Using odin flash TWRP in AP slot.
4. Reboot to twrp and format data.
4. Now you have Magisk + Twrp
Note: Magisk will be disabled when you reboot the device normally. To get into Magisk enabled system, Turn off your phone and use Volume up + power buttons to turn on and release it as soon as you see Samsung Galaxy M30S logo. This will boot into magisk system, I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC used instead of CSC)
Downloads
Patched Firmware INS only
Odin
Samsung USB Drivers
NOTICE: Flash TWRP To Fix Reboot Issues After Patching ROM

????
Thankyou bro
But I think u should also post the process to patch the firmware.

Is this verified did u tried it physically? If yes then also make a video thanks

Gurjotjatt said:
Is this verified did u tried it physically? If yes then also make a video thanks
Click to expand...
Click to collapse
Yes Verified root, will try to post video soon

santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?

santhoosh said:
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.​
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Either use adb reboot download, or Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
1. Download the firmware from the link given below.
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Load AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Now Start Flashing!
8. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
9. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
10. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
11. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
12. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
13. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
14. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
15. Enjoy Magisk
Click to expand...
Click to collapse
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.

redymedan said:
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
://www.youtube.com/watch?v=ILvgki0pFHE
Click to expand...
Click to collapse
To make things easier I have already patched the firmware that I have attached, And it is patched with magisk latest v20.1 which is working fine.

Gurjotjatt said:
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
Click to expand...
Click to collapse
For every update either it may be magisk or firmware update, you need to patch firmware and flash it manually

shamsud said:
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Click to expand...
Click to collapse
Post Updated with patch method

Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...

_hunter said:
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
Click to expand...
Click to collapse
Yes there is OEM unlocking in developers mode it's like 6the option

Gurjotjatt said:
Yes there is OEM unlocking in developers mode it's like 6the option
Click to expand...
Click to collapse
OK... funny thing: it is there now. The only thing is changed: I "gave up" on rooting -- and started setting up phone -- inserted SIM-card and attached my Google account. -- might be worth adding this to the first post.

Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
And error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
Click to expand...
Click to collapse
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...

_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?

its not workimg for my m30s i have followed every step
but its still showing cts profile:false

santhoosh said:
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
Click to expand...
Click to collapse
Resolved that issue flashing original (without Magisk patching) firmware.
Confirmed afterwards that you only can see "OEM unlocking" when your Google account attached.
But yes: it's appears that bootloader still was locked -- that "OEM unlocking" -- it's not grayed-out.
So, the question is: how you're supposed to unlock it?
-- "reboot download" and long pressing Volume Up there -- from the first post -- does nothing
-- "reboot recovery" + wipe data + reboot to bootloader -- from the "movie" -- does nothing

Comment if someone got success in Rooting m30s..!!

_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
I have the same problem.

Gurjotjatt said:
Comment if someone got success in Rooting m30s..!!
Click to expand...
Click to collapse
Considering we have Magisk available -- rooting is rather trivial. Setback is with unlocking bootloader

Finally Rooted
After couple of tries and disappearing OEM Unlocking button, finally I was successful in rooting using the method from this post. It took me some time to master booting directly into recovery after flashing patched images using Odin!
Also, did not realized that you need to connect USB cable to PC and press volume up and down at same time to get the bootloader unlock option.
Thank You OP.

Development [AOSP-11] [UNOFFICIAL] [SW REV 1] Samsung SM-A125F TWRP

Mod edit : link removed and thread locked while waiting for twrp kernel source link.
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​Install instructions:
1. Download an arbitrary SM-A125F firmware zip package newer than 7 May 2021 on SamMobile.com, whose Android version is 11 (Android 10 based firmware no longer work at all)
2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages
3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)
4. If OEM unlocking is unseen to you, take software updates first
5. Also inside Developments settings, enable USB debugging
6a. Run an ADB command to disable dm-verity thru your PC (Or TWRP fails to boot, this isn’t done for my part, so my device is being boot looped)
6b. Sign your own vbmeta.img instead of the stock one, but of course you could still choose as fewer items to be verified as possible; but my own custom vbmeta.img will still be released for you, if you’re relatively new to TWRP
7. Download the TWRP image from my SourceForge project
8. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC
9. Hold <VolUp> to unlock OEM
10. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C
11. Press <VolUp> without holding to enter Download mode
12. Open Heimdall to flash the downloaded TWRP on the partition ‘‘recovery’’ with my TWRP image renamed to ‘‘recovery.img’’
13. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
14. Enjoy!

The Android 11 update is not yet available for my country, maybe soon it'll be available. Anyways can i ask whats working and whats not?

You should have posted the thread as development though, yet you posted it as a question Also thank you for your hard work in making this recovery!

Helix-one said:
The Android 11 update is not yet available for my country, maybe soon it'll be available. Anyways can i ask whats working and whats not?
Click to expand...
Click to collapse
Neither for my country, but you don’t need to pay attention to your regions, yes my TWRP build no longer works on Android 10 based firmware (told at my first step thanks?)

Do you have any screenshots of TWRP?

Helix-one said:
Do you have any screenshots of TWRP?
Click to expand...
Click to collapse
No, i’m still getting my vbmeta.img signed for my TWRP, when done, there will be snaps.

Can we get the vbmeta?

Sokue said:
Can we get the vbmeta?
Click to expand...
Click to collapse
Yes https://sf.net/p/twrp-samsung-a12, and flashed also with TWRP itself, but the device is still being boot looped

How did you disable dm-verity?

Mod edit : link removed and thread locked while waiting for twrp kernel source link.

How To Guide Unlocking the bootloader and rooting

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
UNLOCKING BOOTLOADER​1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. After holding VOL UP for 10 seconeds you should get in to the screen that will let you unlock the OEM so now just press VOL UP.
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
12. Check in developer options if oem unlocking is grayed out, if it isn't factory reset data and wipe chace partiton will have to be done.
ROOTING​1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds).
After the phone turns off, amedietly boot in to recovery (Vol + and POWER at the same time)
12. Make a factory data reset and whipe cache partition
13. Reboot in to system
14. Conect to interent during setup
15. Enable dev options by taping on build number 7 time. OEM UNLOCKING must be grayed out.
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing, go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
20. After flash reboot
21. Check in developer options if oem unlocking is grayed out, if it isn't the instalation process will have to be followed again
THIS IS A OLD METHOD OF INSTALLING TWRP
INSTALLING TWRP, I RECOMEND FOLOWING MY LATEST GUIDE
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
​INSTALLING TWRP OLD METHOD​# If you are not on the A125F or A127F you might have to do a crossflashing fimware operation
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp

LAST_krypton said:
Code:
Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
Click to expand...
Click to collapse

LAST_krypton said:
Code:
# Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
UNLOCKING BOOTLOADER
Code:
1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. VOL UP for bootloader unlock
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
ROOTING
Code:
1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds)
12. After the phone turns of, amedietly boot in to recovery (Vol + and POWER at the same time)
13. Make a factory data reset and whipe cache partition
14. Reboot in to system
15. Conect to interent during setup
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
19. After setup reboot
INSTALLING TWRP
Code:
If you are not on the A125F model you will have to disable MTK Secure Boot and Secure Download and might also downgrade SW REV and then install A125F fimware
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
Click to expand...
Click to collapse
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers

edward0181 said:
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
Click to expand...
Click to collapse
Ok sure, I will do it when I get time.
Cheers

Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.

Rularick5 said:
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Click to expand...
Click to collapse
It is possible, and it is the only way for you to do what?. To flash A125F fimware on A125U you have to go through a really complicated method to succeeded, you would have to dismantle the phone and force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware. And forgot to mention, you have to go trought some litle pain with SBL aswel.

Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.

Rularick5 said:
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Click to expand...
Click to collapse
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.

LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the i gues
Click to expand...
Click to collapse
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.

Rularick5 said:
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Click to expand...
Click to collapse
See here, https://forum.xda-developers.com/t/...ing-theories-and-issues-with-our-a12.4336999/

LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
Click to expand...
Click to collapse
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1

Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start

wiiddakidd said:
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
Click to expand...
Click to collapse
You donwload the same fimware your phone is running and copy the AP.tar.md5 fimware file to your phone. Install cannary version of magisk and patch the AP.tar.md5. Transfer magisk_patched-xxxxxxx.tar back to your pc and in odin flash it in AP slot.

wiiddakidd said:
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Click to expand...
Click to collapse
A guide for that, maybe some other day. It would require phone disasembely to force PRELOADER. And what error do you when flashing AP file?

Hello, long time forum lurker here but never posted anything before. I recently have been having a headache from several different AT&T phones all being restricted to the point where I can't do anything with them. I have an SM-A125U from att that doesn't have an OEM unlock option.
Through my Ubuntu computer I can run some basic adb and fastboot commands but nothing that actually helps me. Still though the fact that I can make the phone go to recovery and fastboot make me wonder if there is really nothing I can do about this. Frija also won't let me get a firmware file for my device.
Not totally sure how it works but somebody said AT&T encrypts the software so you can't access specific functions. I am just wondering is there anything I can do through adb or fastboot to fix this issue in any way, or if my only real option is to just buy a new unlocked phone or something?

I explained it here, if it still doesn't work then comment again here.
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com

Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT

drcroc said:
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
Click to expand...
Click to collapse
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.

LAST_krypton said:
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
Click to expand...
Click to collapse
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?

drcroc said:
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
Click to expand...
Click to collapse
Make sure OEM unlocking and usb debuging have applayed. Boot in to system, reset developer options and then enable them back. After that enable OEM unlocking and usb debuging and restart. After reseting and booting back in to SYSTEM power off the phone and hold VOL + and VOL - at the same time. UNLOCKING MENUE should now be shown and you will be able to get in to it by VOL + longpress.

[Guide] TWRP and ROOT for A20e (A202f) [Updated]

My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!

[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek

does encryp work on this ? dont need to backup just hide data part if fone is stole

This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.

SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp

Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before

OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!

Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?

I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.

fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?

fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.

I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?

lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.

Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?

lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....

Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)

lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.

Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)