I got the unlock code and everything. Installed drivers, got everything in place but when I use the command " fastboot oem unlock "key"
It fails and shows me a remote error along with this
Enable OEM unlock in dev option .
But I can't see that option in dev options and iam fed up with this. I tried searching Google but no luck. I checked the cid to see if it is unlockable and the string was endling with " 007 " means unlockable.
Iam running marshmello ota. All factory. No root nothing..
Any help would be really appreciated. I just want to install cyanogen
Bigbraveballs said:
I got the unlock code and everything. Installed drivers, got everything in place but when I use the command " fastboot oem unlock "key"
It fails and shows me a remote error along with this
Enable OEM unlock in dev option .
But I can't see that option in dev options and iam fed up with this. I tried searching Google but no luck. I checked the cid to see if it is unlockable and the string was endling with " 007 " means unlockable.
Iam running marshmello ota. All factory. No root nothing..
Any help would be really appreciated. I just want to install cyanogen
Click to expand...
Click to collapse
Take a look at this thread in Lenovo/Motorola forums (currently 74 pages long), it seems you're not the only one that has this issue (e.g. post #10 [last post in page 1], post #14 [4th post in page 2] and post #15).
Go to settings/apps/all/settings and clear data only , then go back to about phone/ build number 7 times ,enable developer options oem unlock may be present. Try this.
had the same issue
SOLVED
I was fiddeling with my moto X 2nd and stuck on the same issue.
Running a OTA 6.0 stock unbranded FW Moto X 2nd
Same problem, no OEM UNLOCK under Dev options.
then gave up on the phone and started playing around with fastboot mode and went into recovery to have a peek, and solved the issue.
detailed info for other googelers:
(VOL DOWN while pressing POWER, release POWER after a few seconds still holding VOL DOWN for a few more extra seconds takes you to FASTBOOT, from there select RECOVERY, and when the broken android appears, press POWER to get into RECOVERY)
Cleared my CACHE partition and after that made a FACTORY RESET under RECOVERY and then REBOOT
Restarted phone and did the initial setup, selected not to enable REMOTE PROTECTION (this might also be the reason the allow oem unlock button was enabled, as said, have no clue what made it work)
And Voila! the "allow oem unlock" button was there after enabeling DEVELOPER OPTIONS and I could enable it and unlock the bootloader.
maybe the formatting of cache partition did the trick since it was OTA updated, i have no clue, but it is now there.
this helped me clean kingroot
drmuruga said:
Go to settings/apps/all/settings and clear data only , then go back to about phone/ build number 7 times ,enable developer options oem unlock may be present. Try this.
Click to expand...
Click to collapse
I was messing with my pos alcatel pixi phone trying to root and unlock and installed kingroot, big mistake it was very hard to get rid of. I finally got it to uninstall but it left behind a com.kingroot. Doing this procedure enabled me to uninstall it when previously I was unable. THANKS
Hello, may I ask about the A20e (SM-A202F) here in this A20 forum?
My A20e does not show an option for unlocking the bootloader (well, I thought the "OEM unlocking" would be the term to search for as I know it from my S7).
I started the A20e the first time after unboxing, with no SIM card and no WiFi connected. The date (never updated) was a day in March 2019.
I then even set the date back by 4 weeks and rebooted the phone (as was suggested for the A20, if I remember correctly, if problems with a non-existing or greyed-out OEM unlocking option appear).
Still, no OEM unlocking option is available in the developer options (not even greyed out).
Can other A20e (SM-A202F) users please confirm this? Or do you have that option?
Maybe it's not needed on the A20e, but who knows?
Phone info:
One UI 1.1
Android 9
Baseband ...ASF3
Kernel 4.4.111-16308935
Buildnumber ...ASG1
SE enforcing ..._0004
Knox version 3.3 API level 28 TIMA 4.1.0
Provider ...XKN DBT (unbranded)
Security patch Jul-2019 Release 1
7wells said:
Hello, may I ask about the A20e (SM-A202F) here in this A20 forum?
My A20e does not show an option for unlocking the bootloader (well, I thought the "OEM unlocking" would be the term to search for as I know it from my S7).
I started the A20e the first time after unboxing, with no SIM card and no WiFi connected. The date (never updated) was a day in March 2019.
I then even set the date back by 4 weeks and rebooted the phone (as was suggested for the A20, if I remember correctly, if problems with a non-existing or greyed-out OEM unlocking option appear).
Still, no OEM unlocking option is available in the developer options (not even greyed out).
Can other A20e (SM-A202F) users please confirm this? Or do you have that option?
Maybe it's not needed on the A20e, but who knows?
Phone info:
One UI 1.1
Android 9
Baseband ...ASF3
Kernel 4.4.111-16308935
Buildnumber ...ASG1
SE enforcing ..._0004
Knox version 3.3 API level 28 TIMA 4.1.0
Provider ...XKN DBT (unbranded)
Security patch Jul-2019 Release 1
Click to expand...
Click to collapse
Someone who's already rooted.
https://forum.xda-developers.com/showpost.php?p=80113161&postcount=77
Or
https://forum.xda-developers.com/showpost.php?p=81125253&postcount=180
It also happened with me. I will try to explain what I did to bypass this waiting. First, you got to format everything, cache and data, then reboot your phone and do all of that configuration, but don't turn your wi-fi ON or connect to the internet, go to the date & time settings, set the date to 7 (or more) days back from today and then go to the system updates and try to update your phone (now connected to the internet). Whatever happens now doesn't matter, the important thing is to make sure that your phone got a registry that you tried to update the system 7 days ago. You may now reboot your phone, after rebooting set the date for the current day and turn on developer options, you will see the bootloader option.
Thank you!
Coming back to this (moved) thread after a while, I wonder if unlocking the bootloader will trip Knox. So, will it?
Are there any ways to root the Samsung A20e without tripping Knox?
7wells said:
Thank you!
Coming back to this (moved) thread after a while, I wonder if unlocking the bootloader will trip Knox. So, will it?
Are there any ways to root the Samsung A20e without tripping Knox?
Click to expand...
Click to collapse
I'm sorry but Samsung Knox was made to be tripped. If you touch your recovery partition the Knox will be broken.
Do only changes of the recovery trip Knox?
Is rooting the A20e possible without tripping Knox? (I guess, no)
re-unlock A20e (europa)
Hi, I have problem with re-unlocking bootloader on Galaxy A20e (SM-A202F) after accidental locking in download mode.
- the OEM unlocking option is not displayed in the developer options (it is not possible even after moving the date back 7+ days and clicking on updates and restart mobile)
- After turn on, hold vol- and vol+ and plug in USB cable attached to pc I don't have the option to choose the unlock bootloader by long pressing vol +, only Volume up: Continue and Volume down: Cancel (restart phone)
How to re-unlock bootloader on this mobile? Now I can flashing only original Samsung firmware via Odin, but I need root...
Thanks for tips
.
TWRP now available
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
re-unlock locked bootloader A20e (europa)
lebigmac said:
I had the same problem. Here is my solution. I hope it helps. Click my thanks button if it worked for you. Good luck!
https://forum.xda-developers.com/showthread.php?p=83209365#post83209365
Click to expand...
Click to collapse
The procedure does not work. I also performed a wipe cache and a wipe data / factory reset. Then I connected wifi and waited 10 days. Nevertheless, the OEM unlock option is not available in the debug options, and the "Volume long press Device unlock mode" option is not available after entering the download mode. Can anyone advise?
.
lebigmac said:
Hi. Does it say 'KG state: prenormal' on the top left corner when you go into Download mode?
What firmware did you try it with?
Also you shouldn't have to wait 10 days after connecting to a wifi hotspot for it to validate. On my device the validation process is done within a minute.
Click to expand...
Click to collapse
Hi, KG state: prenormal, FRP lock: OFF, OEM Lock: ON(U1), firmware is original XEZ-A202FXXU3ASL4-20200120200351 (Android 9). The last procedure, waiting 10 days, was the last of many I tried.
johnny_nb said:
The procedure does not work. I also performed a wipe cache and a wipe data / factory reset. Then I connected wifi and waited 10 days. Nevertheless, the OEM unlock option is not available in the debug options, and the "Volume long press Device unlock mode" option is not available after entering the download mode. Can anyone advise?
Click to expand...
Click to collapse
set date back 2 weeks
physwizz said:
set date back 2 weeks
Click to expand...
Click to collapse
Hi, I tried to return the date in 7, 14, 30 days and a few months, but without success. I have Samsun Galaxy A20e SM-A202F
Tried to clicking through threads and used search... but seems I am blind.
I have SM-A202F CSC ROM and dreaming to have CSC DBT.
How to change active CSC?
Tried with Odin:
Code:
A202FXXU3BTI7_A202FOXM3BTI7_DBT
Then realized seems Multi CSC because ROM have also OXM ""Region""...
Second attempt with Combination Firmware...
Code:
COMBINATION_FAC_FA90_A202FXXU3ATD1_FAC3ATD1_CL15768665_QB30267852_REV00_user_mid_noship.tar.md5
Here Odin failed... and I saw funny warning text on screen...
Thought this will be easy 5 minute flash and voila ready DBT...
Thanx in advance.
Best Regards
Seems I managed my problem.
First mistake was to flash 5 files... with Home...
Now I have DBT, after using SIM Card from Germany and flashed 4 files and pressed Button during Settup and... magic...
Tried before without SIM card...
Only as info.
Best Regards
adfree said:
Seems I managed my problem.
First mistake was to flash 5 files... with Home...
Now I have DBT, after using SIM Card from Germany and flashed 4 files and pressed Button during Settup and... magic...
Tried before without SIM card...
Only as info.
Best Regards
Click to expand...
Click to collapse
Good news
Try this
https://forum.xda-developers.com/galaxy-a20/development/a20e-testers-t4183683
cizordj said:
I'm sorry but Samsung Knox was made to be tripped. If you touch your recovery partition the Knox will be broken.
Click to expand...
Click to collapse
I managed to do the "bootloader", to log in in "download" mode and to have the "root of my A20e.. without major problems.... but the whole thing is almost useless because anyway you can not change (for what I need) the information of the phone (imei, SN... etc etc etc),, and I believe that it depends precisely on the new security it is equipped with, in accordance withGoogle.......I won't hide from you that I would gladly install the good old Android 4.4......
johnny_nb said:
re-unlock A20e (europa)
Hi, I have problem with re-unlocking bootloader on Galaxy A20e (SM-A202F) after accidental locking in download mode.
- the OEM unlocking option is not displayed in the developer options (it is not possible even after moving the date back 7+ days and clicking on updates and restart mobile)
- After turn on, hold vol- and vol+ and plug in USB cable attached to pc I don't have the option to choose the unlock bootloader by long pressing vol +, only Volume up: Continue and Volume down: Cancel (restart phone)
How to re-unlock bootloader on this mobile? Now I can flashing only original Samsung firmware via Odin, but I need root...
Thanks for tips
Click to expand...
Click to collapse
--------
" - the OEM unlocking option is not displayed in the developer options "....: METTI UN ACCOUNT GOOGLE NEGLI ACCOUNT DEL TELEFONO
Sandro111 said:
--------
" - the OEM unlocking option is not displayed in the developer options "....: METTI UN ACCOUNT GOOGLE NEGLI ACCOUNT DEL TELEFONO
Click to expand...
Click to collapse
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
-Go to software update then check for update and wait till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
Have just bought a Galaxy Tab S5e SM-T725 and my intention was to flash TWRP and Lineage 18.1 for microG. Actually the device runs Android 11 stock. Think maybe the problem starts that in Developer Options I cannot even find "OEM unlocking" option, so cannot switch the option and allow the unlocking. When I go in Download mode there's no way to start unlocking the bootlader. Any thoughts? Thanks to anyone in advance.
Found the sol, I post it for helping who get stucked like me. The problem is that lately in many Samsung deviced The "OEM unlocking" appears in Developer Options menu only at least 7 days after you activated or reset the device, but HERE there's a guide on how to force that time so to solve instantanealy.
Hello everyone, I have a Nokia 6 TA-1021 that I think is soft bricked as it does not get past the Nokia logo on boot, but it can go in recovery and download modes. My PC correctly recognizes the phone when using fastboot.
I did not unlock the bootloader previously (only used it as a plain user, no custom roms, no root, only OTA updates...). Also, I never turned on the "Allow OEM unlock" flag when the phone was working. I think it was running Android 9 Pie, but I'm not 100% sure, could also be Android 8 Oreo.
I don't know exactly how and when it did get into this situation, because when I changed my phone two years ago it was still working (I even booted it up a couple times last year). Then I wanted to boot it up last week and found this situation.
I've been looking inside the entire Nokia 6 section here to find a possible solution to no luck.
I managed to get a stock firmware to be flashed with OST LA, but as I said, the bootloader is not unlocked and the "Allow OEM unlock" switch is off, so I'm pretty much stuck.
I don't know if this helps, but in recovery mode it displays an error message that reads "E:[libfs_mgr]dt_fstab: Failed to find device for partition system". Also, I tried to do a factory reset a couple times, also to no luck.
Can this phone be unbricked? ANY help will be much appreciated!