Database Info

[Q] Samsung galaxy S5 is not booting with custom zImage

Hi Friends,
I flashed my samsung galaxy S5 with custom boot.img updated custom zImage, But after flash its not able to boot. Its always going in download mode. Friends on download mode screen i am seeing that "QUALCOM SECUREBOOT: ENABLE". Is it mean that bootloader is locked and for flashing i have to unlock it first but same time i have doubt if bootloader is locked then how i am able to flash.
Kernel i am downloading from samsung website for my specific phone model number. So i have less doubt on that. Atleast it should have to boot with that kernel.

arvind3023 said:
Hi Friends,
I flashed my samsung galaxy S5 with custom boot.img updated custom zImage, But after flash its not able to boot. Its always going in download mode. Friends on download mode screen i am seeing that "QUALCOM SECUREBOOT: ENABLE". Is it mean that bootloader is locked and for flashing i have to unlock it first but same time i have doubt if bootloader is locked then how i am able to flash.
Kernel i am downloading from samsung website for my specific phone model number. So i have less doubt on that. Atleast it should have to boot with that kernel.
Click to expand...
Click to collapse
Did you also put the correct rom?

[B]How to disable QUALCOM SECUREBOOT[/B]
blentavi said:
Did you also put the correct rom?
Click to expand...
Click to collapse
I extracted default boot.img from phone, Checked this boot.img by flashing in phone, its working fine. I updated this boot.img with custom zImage and then i flashed phone with this boot.img using ODIN tool.
I have more doubt on "QUALCOM SECUREBOOT: ENABLE", feels like its not allowing to boot with custom boot.img. My doubt is beacuse Original boot.img and custom boot.img hash values are different, might be this "QUALCOM SECUREBOOT:ENABLE" feature is stoping custom boot.img with different hash value to flash. Please help me if you know how to disable it.

arvind3023 said:
I extracted default boot.img from phone, Checked this boot.img by flashing in phone, its working fine. I updated this boot.img with custom zImage and then i flashed phone with this boot.img using ODIN tool.
I have more doubt on "QUALCOM SECUREBOOT: ENABLE", feels like its not allowing to boot with custom boot.img. My doubt is beacuse Original boot.img and custom boot.img hash values are different, might be this "QUALCOM SECUREBOOT:ENABLE" feature is stoping custom boot.img with different hash value to flash. Please help me if you know how to disable it.
Click to expand...
Click to collapse
live.samsung-updates.com/index.php?device=none
look there !! there are the latest FW for Samsung mobile.
Download it (maybe unzip?)
Which version of Odin are you using?
Put your phone into download mode. Pull the battery. Reinsert it. Press and hold Volume Up+Volume Down(press in the middle)+Power Button until it reboots.
Launch Odin by right clicking it and selecting Run as Administrator. Ensure that nothing Samsung related is running in the background of your PC. Check the Task Manager.
Select the PDA slot in Odin and target the firmware you unzipped earlier.
Plug your phone in to the PC using the factory supplied USB cable. Do not use hub. Odin should detect your phone. Your PC may install some drivers.
Press start in Odin.
Let the phone fully reboot. Perform a factory wipe.

blentavi said:
live.samsung-updates.com/index.php?device=none
look there !! there are the latest FW for Samsung mobile.
Download it (maybe unzip?)
Which version of Odin are you using?
Put your phone into download mode. Pull the battery. Reinsert it. Press and hold Volume Up+Volume Down(press in the middle)+Power Button until it reboots.
Launch Odin by right clicking it and selecting Run as Administrator. Ensure that nothing Samsung related is running in the background of your PC. Check the Task Manager.
Select the PDA slot in Odin and target the firmware you unzipped earlier.
Plug your phone in to the PC using the factory supplied USB cable. Do not use hub. Odin should detect your phone. Your PC may install some drivers.
Press start in Odin.
Let the phone fully reboot. Perform a factory wipe.
Click to expand...
Click to collapse
Thanks for your reply,
I searched firmware for my phone model number which is SM-G900R7, But its not there. But i think your post bring closer to my soltution. Thanks again

maybe this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
or maybe
http://alchemistar.blogspot.de/2014/06/sm-g900.html

blentavi said:
maybe this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
or maybe
http://alchemistar.blogspot.de/2014/06/sm-g900.html
Click to expand...
Click to collapse
Thanks for your replies,
Upper link i tried already, from there u can get source code for kernel and source code for file system for S5.After compilation u will get zImage and system.img. system.img i dont want to flash for now but zImage compiled from here i updated in defualt boot.img but its not booting because of KNOX feature SECUREBOOT ENABLE. So i feel i should have to flash with some unlocked firmware or KNOX disabled firmware image first.
Lower Link what you mentioned is not having binaries related to my model number, my model number is SM-G900R7. I have to get a KNOX disabled firmware for my model number SM-G900R7.
live.samsung-updates.com/index.php?device=none
I feel above link you posted earlier i can something from there. I have to try it tommorow. Here its 1 o'clock night. Going to sleep.
Thanks for your replies.

SM-G930A in infinite loop

Hello! I installed an AP to be a superuser, but after I've done so (using a tutorial I can't link since I have less than 10 posts) the phone bricked. It was supposed to do that and then be able to root it, but it didn't work. Now I'm stuck. I downloaded the stock AP from this forum but when I try to install it says "model mismatch fail"
Can someone help me please?

Entering Download mode, this is the info I get.
ODIN MODE (HIGH SPEED)
PRODUCT NAE: SM-G930A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
WARRATY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE
AP SWREV: B4 (2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: ENABLE

I noticed I shouldn't have posted a question in this subforum. I apologize but I can't delete it.

Zyurat said:
I noticed I shouldn't have posted a question in this subforum. I apologize but I can't delete it.
Click to expand...
Click to collapse
Havr you trued downloading and flashin with ODIN the rom for your phone. Flash all the files, not only the AP. What does ODIN say appart from the "mismatch message"
Sent from my SM-G930F using Tapatalk

FRP unlock SM-G930F Oreo 8.0.0 (binary 3?)

Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2

contact me via whtasapp +2347069605746

i am stuck with the same problem...
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
i need help to ...i guess

same problem here pretty much, any solutions?

please disregard. accidently posted
disregard. mistake

I'm stuck in same issue
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
BINARY: Samsung official
System status: official
FRP LOCK: ON
Secure Download: Enable
Warranty: 0x030c
RP SWREV: B:3 K:1 S:2
KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0
I tried Smart Switch recovery feature but it's now showing there. When I try to go to recovery mode. It said. "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software". Backstory. I install TWRP in the device from download mode without rooting it. And jump to TWRP on the first restart. And install SuperUser, Xpose etc then restart and enable Super User on boot. The phone is locked after installing new updates. I try to flash BL, AP using Odin 3.12 and 3.13.1. It's failing
Can't turn on the phone. What to do? Please help. Thanks

Step one: Download some marshmallow rom or some nougat rom which has some frp bypass exploit, download an oreo rom and download patched odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Step two: flash the oreo rom and boot your device, so you know that your device does actually boot and is not totally broken.
Step three: you need to mix up the two roms, its been a while since i've done this, so i don't remember how i mixed the roms up, i think i installed AP, CP and CSC of the marshmallow/nougat rom and BL of the Oreo rom. Just try this out, if it won't work, you need to try to mix them up differently, maybe install BL and CP of the Oreo rom and AP + CSC of the marshmallow/nougat rom. Just try out until odin says it passed and the phone boots into marshmallow/nougat
Step four: use an frp bypass exploit that works on the marshallow/nougat rom you installed
please don't be angry because of my bad english and bad formatting, hope it works for you. I did this on the second bootloader version, so maybe samsung fixed this on your bootloader version.

qamar.cyb said:
BINARY: Samsung official
System status: official
FRP LOCK: ON
Secure Download: Enable
Warranty: 0x030c
RP SWREV: B:3 K:1 S:2
KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0
I tried Smart Switch recovery feature but it's now showing there. When I try to go to recovery mode. It said. "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software". Backstory. I install TWRP in the device from download mode without rooting it. And jump to TWRP on the first restart. And install SuperUser, Xpose etc then restart and enable Super User on boot. The phone is locked after installing new updates. I try to flash BL, AP using Odin 3.12 and 3.13.1. It's failing
Can't turn on the phone. What to do? Please help. Thanks
Click to expand...
Click to collapse
Sorry for late answer, I think I can help. I can upload files later for you to download.

I followed this video and it works. (Verified on SM-G930F)
edit:
Cannot post outside links, but search on youtube for "BOOM!!!Without PC! Samsung S7 Edge SM-G935F Binary 3 Remove Google Account.Bypass FRP." on youtube.
Hope it helps

frp off binary3
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!

BOGDANCOSARCA said:
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!
Click to expand...
Click to collapse
Thank you, but it is already fixed.

monsterkaka said:
Thank you, but it is already fixed.
Click to expand...
Click to collapse
Hi Someone please help me, im on binary 3 oreao firmware, ive tried various things but im learning also but would like a fix.
please help?

monsterkaka said:
Thank you, but it is already fixed.
Click to expand...
Click to collapse
Hi Mate how did you fix this?? is your last problem was something like this? if its YES help me. check atteachments.

pedropenduko said:
Hi Mate how did you fix this?? is your last problem was something like this? if its YES help me. check atteachments.
Click to expand...
Click to collapse
Yes something like that. PM me if you still have the problem. I might be able to help.

BOGDANCOSARCA said:
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!
Click to expand...
Click to collapse
can you make it more clear plz from "we will go into recovery...." i cant understand what you typing here...

i have thesame problem
monsterkaka said:
Yes something like that. PM me if you still have the problem. I might be able to help.
Click to expand...
Click to collapse
mate... can u tell us the solution? thanks

Is possible to root Xcover Pro?

Hello,
I have unlocked the bootloader. I tried to do the steps with Magisk, this is it:
-Install Magisk.
-Patch AP.
-Copy it to PC.
-ReFlash with ODIN.
But when I do that, I got errors during installation on Download mode and the phone bricks. So I don't know if I am doing something wrong or happens that this device can't be rooted.
I have been searching but can't find any reliable information about, could you please give me some information or help?
Thank you!

Bump!

Got this error following installation instructions:
ODIN MODE (AVB Fail)
vbm*** Error verifying vbmeta image: HASH_MISMATCH (3)
vbmeta: VERIFICATION_DISABLED bit is set
CUSTOM VBMETA
VBMETA G715FNXXU8CUE1, 4000301 4R

Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
tys0n said:
It's pretty simple and straight forward. I won't go in on details about odin, drivers etc as there's many guides about that already.
Or join the A40 tg group for any assistance with firmware, odin etc.
You'll need to unlock bootloader first, and it will TRIP KNOX.
Please read up on what it means before you proceed if you're not sure about it. It can't be reversed.
Download and install latest Magisk manager to your phone. https://github.com/topjohnwu/Magisk/releases
Download and install 7zip ZS to your pc. https://github.com/mcmilk/7-Zip-zstd/releases
Get the firmware for your phone and extract the AP file from the firmware zip. (Use samfirm or frija for fast download)
Open the AP*.tar.md5 with 7zip ZS and click on the boot.img.lz4, then drag the boot.img out of there.
Copy the boot.img to your phone, open Magisk Manager and click install, and again install, then "select and patch a file".
Browse to the boot.img you just copied to your phone and let Magisk do it's magic.
You'll find a magisk_patched.img in your download folder when it's done.
Copy it over to your pc, rename it to boot.img and make a .tar archive with boot.img in it.
Open Odin, put the tar in AP slot, connect your phone in download mode and hit start in Odin.
Open Magisk Manager again once the phone is booted to finish the setup.
Done.
Click to expand...
Click to collapse
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.

Awesome! The bad thing is that I already sold Xcover Pro because I need root yes or yes but well, I hope it will be useful for people in the future! Maybe even somebody try to port LineageOS.

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later

-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?

-SpaceCowboy- said:
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
Click to expand...
Click to collapse
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far

On my rooted SM-G715FN, I have:
CURRENT BINARY: Custom (0x3)
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF(U)
Secure Download: Enabled
Click to expand...
Click to collapse
In Developer Options, I have `OEM Unlocking` enabled.
iBowToAndroid said:
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
Click to expand...
Click to collapse
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.

d5sword said:
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
Click to expand...
Click to collapse
Because his phone is not SM-G715FN

The ADB removal method worked for me. There's a "Debloat" text file up on GitHub that makes this a breeze.
Link: https://github.com/khlam/debloat-samsung-android tellthebell
Once in debug mode, USB connected, and drivers installed:
ADB shell < commands.txt
Obviously, the text file must reside in the same folder as ADB.

travis659 said:
El método de eliminación de ADB funcionó para mí. Hay un archivo de texto "Debloat" en GitHub que hace que esto sea muy sencillo.
Enlace: https://github.com/khlam/debloat-samsung-android tellthebell
Una vez en modo de depuración, USB conectado y controladores instalados:
Shell ADB <comandos.txt
Obviamente, el archivo de texto debe residir en la misma carpeta que ADB.
Click to expand...
Click to collapse
i think only working in snapdragon devices, no? the Xcover use Exynos

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
Just wanted to say a huge thank you to yourself and tys0n.
I purchased an Xcover Pro brand new from Microless global for an absolute steal...as in a price that was simply too good to be true. It was only upon setting up the device that I realised why they were offering such a low price.
The device was encumbered by an unavoidable corporate knox enrollment service. Sadly I suspect most people who purchase from them won't realise just how much control of their device they are handing to some random company if they just press OK during setup, but I wasn't having it. Ignoring the enrolment promp was not possible; you couldn't even access the home button or recent button until you'd authorised under knox and handed control of the device over to some faceless entity.
Thanks to the efforts of those in this thread I have been able to unlock BL, root the SM-G715FN/DS and freeze all of the knox bull****. The device now belongs to me.
The only thing I'd like to ad for those that come here looking for answers is that the process above is spot on, but I had to use this tool to create my .tar file. Simply creating a .tar archive with the .img file in it wasn't good enough for my device; it rejected that as an unauthorised file.
Use this tool once you've patched the boot.img with magisk and renamed it.
[Script][Tool] how to create a tar.md5 file from img For Odin
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file. unzip the file tool, and put your img files into the same directory of the batch file...
forum.xda-developers.com
Props to mkh.mourad and testament to the usefulness of XDA that a file from 2013 got me over the line.
I'm certainly no developer, but given the relative ease with which we got this far, I hope it's not too far down the road until we get TWRP and can start mucking around with some roms. Please post here if you have any ideas. This device has real potential as a very long term solution.

Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.

TomasNM said:
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
Click to expand...
Click to collapse
The "KG" status must be in "checking" so that you can flash a custom binary, you must leave the phone on 168 hours in a row with an internet connection otherwise it will not disappear

SpaceCowboy,
thank you for the advice, I waited a bit and today I managed to root the phone successfully.
However, I tried to install some Magisk modules and the phone stuck on initial screen (Samsung Galaxy Xcover Pro), even not get to the "SAMSUNG" screen.
Only solution was to wipe all data in recovery.
Any ideas how to install Magisk modules without risk?

Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.

Psyckosama said:
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Click to expand...
Click to collapse
What's your Baseband Version?

iBowToAndroid said:
What's your Baseband Version?
Click to expand...
Click to collapse
g715u1uescbuj1

Psyckosama said:
g715u1uescbuj1
Click to expand...
Click to collapse
OEM unlock doesn't exist on US models. This model is bootloader unlockable via paid 3rd party services, but only up until bootloader revision 7. Since you're fully updated, you have revision 12

[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.)