Database Info

F*&# FRP!!!

So, my Note 5 somehow got reset with OEM unlock OFF. Also, I was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from ADB is disabled
2. Update from External Storage is disabled
3. Apply_Cache is depricated
If I reboot to bootloader i get the charging symbol with:
Kernal ins not seandroid
Custom Binary blocked by frp lock
can someone throw some ideas out there about what I should do?:angel:

kennybrooks said:
so, my note 5 somehow got reset with oem unlock off. Also, i was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from adb is disabled
2. Update from external storage is disabled
3. Apply_cache is depricated
if i reboot to bootloader i get the charging symbol with:
kernal ins not seandroid
custom binary blocked by frp lock
can someone throw some ideas out there about what i should do?:angel:
Click to expand...
Click to collapse
reflash the stock rom only with odin! No recovery, no root! Then reflash the rest! Do not try to flash with recovery! Search threads for your note 5 version of firmware. And from now on make sure you keep oem on!

sir0knightfall said:
reflash the stock rom only with odin! No recovery, no root! Then reflash the rest! Do not try to flash with recovery! Search threads for your note 5 version of firmware. And from now on make sure you keep oem on!
Click to expand...
Click to collapse
odin won't recognize my phone! what could that be?

KennyBrooks said:
So, my Note 5 somehow got reset with OEM unlock OFF. Also, I was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from ADB is disabled
2. Update from External Storage is disabled
3. Apply_Cache is depricated
If I reboot to bootloader i get the charging symbol with:
Kernal ins not seandroid
Custom Binary blocked by frp lock
can someone throw some ideas out there about what I should do?:angel:
Click to expand...
Click to collapse
This guy can help you out or even me http://forum.xda-developers.com/tmobile-galaxy-note5/general/free-sim-frp-unlock-t3376396

KennyBrooks said:
odin won't recognize my phone! what could that be?
Click to expand...
Click to collapse
Kenny,
The new stock firmware is available here: https://www.androidfilehost.com/?fid=24588232905721433
Unzip it, ODIN flash it.
FRP is automatically activated when you add a Google Account now. Remove the Google account before factory reset, rooting and installing a custom ROM.
PS: I learned the hard way too.

rmarinella said:
Kenny,
The new stock firmware is available here: https://www.androidfilehost.com/?fid=24588232905721433
Unzip it, ODIN flash it.
FRP is automatically activated when you add a Google Account now. Remove the Google account before factory reset, rooting and installing a custom ROM.
PS: I learned the hard way too.
Click to expand...
Click to collapse
Odin won't recognize my phone at all. My computer sees it as "Unknown USB Device (Device Descriptor Request Failed)." how do I fix this?

KennyBrooks said:
Odin won't recognize my phone at all. My computer sees it as "Unknown USB Device (Device Descriptor Request Failed)." how do I fix this?
Click to expand...
Click to collapse
Try going this route and doing an emergency recovery.
http://www.samsung.com/us/sidesync/

rmarinella said:
Try going this route and doing an emergency recovery.
http://www.samsung.com/us/sidesync/
Click to expand...
Click to collapse
should i use download mode or recovery?

I don't recall. Biggest reason I pointed you here is that a proper driver is also included. I think recovery mode though.

ulefone Power 2 Development and Support

Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.

I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools

No flash No verity encrypt to Disable boot verification

XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?

So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help

where is the scatter file?

gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.

Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file

it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.

i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.

any custom ROM

non yet

hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S

Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?

kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.

ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!

pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.

ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"

Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.

ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!

Galaxy s7 FRP lock, dm verity error, need help

Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?

mrkole said:
Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
s/n: r58jc1a22hr
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?
Click to expand...
Click to collapse
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)

Craz Basics said:
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)
Click to expand...
Click to collapse
i only used AP. I was following a youtube video where he only selected AP

mrkole said:
i only used AP. I was following a youtube video where he only selected AP
Click to expand...
Click to collapse
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.

Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.

audit13 said:
Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?

Craz Basics said:
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?

mrkole said:
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
Click to expand...
Click to collapse
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.

Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.

Craz Basics said:
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!

audit13 said:
Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!

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

Note 20 Ultra 5G (Exynos) Rooting Problem

Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.

codenamefred said:
Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.
Click to expand...
Click to collapse
EXACTLY AFTER 7 DAYS I WAS ABLE TO ROOT MY DEVICE FOLLOWING THE FIRST METHOD, AND THERE WAS NO ERROR THIS TIME. THANKS XDA.
DEAR MODERATORS CAN DELETE THIS POST.