No OEM/bootloader unlocking option on the A20e (SM-A202F)? - Samsung Galaxy A20 Questions & Answers

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

Related

Can't find enable OEM unlock option in dev option. Can't unlock bootloader

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

Solution to the problem of the non-existent OEM unlock option after update to 8.1

With this tutorial you can reactivate de OEM unlock option to install twrp or Downgrade to 7.0 nougat
Files you need:
#Samsung drivers
#Latest stock firmware
#Odin downloader
#Miracle box
NOTE:
Be sure back up your important matters in your phone.
Steps on REMOVING RMM
Be sure your phone is on and its normal(in a sleep state or in home screen) do not turn off.
1. install samsung drivers
2. Disable antivirus
3.extract miracle all zip files
4. Run miracle box loader(run as admin)
5.then set your time to 2 years past.. Ex. Date today, just change the year.
6.then close miracle box.
7.open miracle box loader again(you will see miracle box is working now)
8. Connect the phone.
(Always check the phone. if there something pops up, tick "always allow" then "allow")
9.click "Connect" button on the top left side on miracle box
10. Click "Samsung tab" on the miracle box
11.Click scan on the top right corner
12. Set the mode selection into : Download then hit "Go" button you will notice that your phone is on download mode and its blank. Just let it be on that state its on the process right now.
13. Click on "Reset Reactivation/EE Locks
14. Hit " Start button" and now its on the process.
You will see error on the miracle. That's okay you're almost there to get rid of it.
15.reboot the phone in download just hold synchronously press vol - , home button , and power then wait until you get again in the selection and then select "Continue". As you can see there's no more RMM State: prenormal in info. It means you're almost there..
16. Flash stock via Odin.
Setup your phone
You're done.. Check Dev Options and you see "OEM Toggle".
LINKS:
Miracle Box: https://drive.google.com/file/d/1n_UGxEEmvJFGym0li05GH5tw087_7GjW/view
Download your preference rom here : https://updato.com/firmware-archive-select-model?q=SM-j730&exact=1&r=&v=&rpp=15
Credits: Shivam
Flash stock by Odin with the four files
bl . ap .csc .pda from the nogut firmware?
martinexa said:
With this tutorial you can reactivate de OEM unlock option to install twrp or Downgrade to 7.0 nougat
Files you need:
#Samsung drivers
#Latest stock firmware
#Odin downloader
#Miracle box
NOTE:
Be sure back up your important matters in your phone.
Steps on REMOVING RMM
Be sure your phone is on and its normal(in a sleep state or in home screen) do not turn off.
1. install samsung drivers
2. Disable antivirus
3.extract miracle all zip files
4. Run miracle box loader(run as admin)
5.then set your time to 2 years past.. Ex. Date today, just change the year.
6.then close miracle box.
7.open miracle box loader again(you will see miracle box is working now)
8. Connect the phone.
(Always check the phone. if there something pops up, tick "always allow" then "allow")
9.click "Connect" button on the top left side on miracle box
10. Click "Samsung tab" on the miracle box
11.Click scan on the top right corner
12. Set the mode selection into : Download then hit "Go" button you will notice that your phone is on download mode and its blank. Just let it be on that state its on the process right now.
13. Click on "Reset Reactivation/EE Locks
14. Hit " Start button" and now its on the process.
You will see error on the miracle. That's okay you're almost there to get rid of it.
15.reboot the phone in download just hold synchronously press vol - , home button , and power then wait until you get again in the selection and then select "Continue". As you can see there's no more RMM State: prenormal in info. It means you're almost there..
16. Flash stock via Odin.
Setup your phone
You're done.. Check Dev Options and you see "OEM Toggle".
LINKS:
Miracle Box: https://drive.google.com/file/d/1n_UGxEEmvJFGym0li05GH5tw087_7GjW/view
Download your preference rom here : https://updato.com/firmware-archive-select-model?q=SM-j730&exact=1&r=&v=&rpp=15
Credits: Shivam
Click to expand...
Click to collapse
Plz sir Find out any other solution that can work without using of miraclebox
FRP block is like so simple to bypass the Samsung security in nougat rom . plz find a solution like that to bypass the RMM state prenormal so that Oem unlock is enable .
Well i just try a trick myself , i mean in Rmm state prenormal we can't flash TWRP or we cant root our phone with magisk
But when i was flash a combination frameware on my j730Gm after it there is no pop up msg in download mode Rmm state prenormal than i was quite happy but after it when i was trying to flash TWRP in my phone after it , my phone doesn't boot it start nd then restart so its not work but flashing combination frameware we can bypass rmm state prenormal but we can't switch on our phone its like a bull **** and we can't go in TWRP mode plz help me im in bad situation now i hate Samsung new oreo update battery drain problem and somewhere lags in it ui. it is a worst situation for me now iam no longer to root my phone, no custom rom :crying::crying::crying: :crying:
ahmed10g said:
Flash stock by Odin with the four files
bl . ap .csc .pda from the nogut firmware?
Click to expand...
Click to collapse
Oreo first.
worked great thanks man
Miracle box shows 'can not connected phone' help pls
skayii said:
Miracle box shows 'can not connected phone' help pls
Click to expand...
Click to collapse
install drivers and run as admin
martinexa said:
install drivers and run as admin
Click to expand...
Click to collapse
other version of miracle box fixed problem
skayii said:
other version of miracle box fixed problem
Click to expand...
Click to collapse
I have some random reboots after downgrade. I install twrp and then y flash superstock. I flashed it two times and have reboots. Twice a day
martinexa said:
I have some random reboots after downgrade. I install twrp and then y flash superstock. I flashed it two times and have reboots. Twice a day
Click to expand...
Click to collapse
Why are you telling me this
skayii said:
Why are you telling me this
Click to expand...
Click to collapse
Solo te cuento. Nada más. Yo tuve este problema
Anyone tried this with j730GM, because i follow all steps but oem don't appears
sergioland said:
Anyone tried this with j730GM, because i follow all steps but oem don't appears
Click to expand...
Click to collapse
You must flash oreo stock again
OMG! It works!! Tested on J701F
I had to OEM unlocked because the touch screen stopped working after the phone automatically updated to OREO 8.1 (because the touch screen was replaced and obviously Samsung dropped support for non-oem touch panels in this update) so I have looked everywhere for solution until I found it here http://www.technocaretricks.com/samsung-j701f-touch-not-working-after-update-to-8-1-oreo/
But flashing that TAR file wasn't possible without changing the RMM state.
Thanks a lot, you are a lifesaver
martinexa said:
5.then set your time to 2 years past.. Ex. Date today, just change the year.
Click to expand...
Click to collapse
The PC time, or the phone time?
martinexa said:
16. Flash stock via Odin.
Click to expand...
Click to collapse
Could I flash a rooted rom?
thx.
InvertedMonkey said:
The PC time, or the phone time?
Could I flash a rooted rom?
thx.
Click to expand...
Click to collapse
PC time bro
First. Do the process and flash oreo stock again and then you can see the oem unlock option.. After that you can flash twrp and the rom that you want
deleted.
Thanks. I follow instructions and I can manage to flash twrp
And helios kernel.the only thing I notice after all those flashing is when I check dev option is OEM unlock is gone again. But don't care this moment because I manage to root my phone and that is ok. thanks again
Work on S9 to or only J7?
crizalid8 said:
Work on S9 to or only J7?
Click to expand...
Click to collapse
I dont know, but you can try

Recovering data from SM-J510FN with forgotten lockscreen PIN

Greetings everyone!
I've stumbled upon a bit of a interesting problem today. I came to visit my cousin living abroad and was asked if I could somehow recover her data from SM-J510FN which she forgot a password for (she wasn't using it after she got a new phone, hence the reason she forgot the PIN ...). Phone is fully stock, (she is not tech savvy) so I believe she didn't even touch developers options (I don't know if USB debugging is on by default) and device has a FAP lock when I booted into download mode *It really does say it in the upper left corner of the screen when booted in DL mode*. So I tried the following:
Tried deleting *.key with ADB (didn't show the device with "adb devices" command)
Flashing TWRP with Odin (failed because of the FAP lock)
I could enter bootloader and update device via ADB sideload/SD card (vol up + home key combo when booting)
Phone is fully stock, I know I could just wipe/factory reset and call it a day, but there must be a way to recover it
Thanks in advance!
Vuxa said:
Greetings everyone!
I've stumbled upon a bit of a interesting problem today. I came to visit my cousin living abroad and was asked if I could somehow recover her data from SM-J510FN which she forgot a password for (she wasn't using it after she got a new phone, hence the reason she forgot the PIN ...). Phone is fully stock, (she is not tech savvy) so I believe she didn't even touch developers options (I don't know if USB debugging is on by default) and device has a FAP lock when I booted into download mode *It really does say it in the upper left corner of the screen when booted in DL mode*. So I tried the following:
Tried deleting *.key with ADB (didn't show the device with "adb devices" command)
Flashing TWRP with Odin (failed because of the FAP lock)
I could enter bootloader and update device via ADB sideload/SD card (vol up + home key combo when booting)
Phone is fully stock, I know I could just wipe/factory reset and call it a day, but there must be a way to recover it
Thanks in advance!
Click to expand...
Click to collapse
Was it pin or other type of lock?
Yes, it's a PIN type lock, also I forgot to mention that it's running 7.1.1 firmware
Vuxa said:
Yes, it's a PIN type lock, also I forgot to mention that it's running 7.1.1 firmware
Click to expand...
Click to collapse
Then...you can't.

MDM Locked Galaxy Tab A

I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!
I can fix it remotely the last hope
Same Issue here,
Any one had any luck with MDM T307U. Please assist.
rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.
How to Remove MDM Control from Android?​For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.
Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3

ROOT SM-T555 Nougat (Android 7.1.1)

Hello...
I am looking for a working way to root my SM-T555
The device is running android 7.1.1;
base ver. "T555XXU1CQHA";
build ver. "NMF26X.T555XXU1CRG1";
Samsung experience 8.5;
Android security patch August 2017.
So far, the several attempts I made using every T55X related software I found in this website have been unsuccessful.
It would seem that the rooting software available is for "Marshmallow only", thus not Nougat specific,
though I read some comments stating that the TWRP made for MM worked on Nougat too and, after that, Magisk would/could do the job...
So I gave it a try but, after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again.
On top of that, the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device though, supposedly, the patches were not for Nougat, anyway...
The developer options page, once activated, can only be "turned off" ("greyed out") but cannot be deactivated;
while, on other devices, if you turn it off the page usually disappears after rebooting then you have to tap 7 times the build version, again, in order to make it appear.
I never had problems in rooting any of the phones and tablets I have /had, including an SM-T819 running Nougat 7.1.1,
thanks to the great job done by the coders in this community to whom I would like to express my appreciation for what they do for the benefit of us all.
But this thing seems to reject everything I throw at it and it's been the most stubborn "phone like object" I ever fought with.
So far I am the one loosing the fight... I wish some of you guys could give me the means to defeat it.
Thanks in advance to whoever may be available to help me out.
Flash TWRP, then install Magisk in TWRP.
V0latyle said:
Flash TWRP, then install Magisk in TWRP.
Click to expand...
Click to collapse
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
endlessquest said:
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
Click to expand...
Click to collapse
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
V0latyle said:
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
Click to expand...
Click to collapse
of course I did follow the guide by the book. also, the recovery appears to be installed properly, Odin showing a nice green PASS sign, but it doesn't work anyway
now about unlocking the bootloader, as I mentioned in my first post:
"the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device"
every time I had to re install the system, so there clock want back to zero. Maybe I should be waiting for the allotted number of days to pass on order for the OEM unlock key to appear...
but before my first attempt to root the device, almost one month was past and the OEM unlock key wasn't there, notwithstanding...
I hope there was a chance that the bootloader was already unlocked...
to be concise (schematic):
tablet in download mode
untick auto reboot in Odin
AP loaded with "smt550_cf-autoroot.tar"
flash with Odin, OK, green sign PASS
reboot manually home+volume down+power,
then switch to volume up when screen becomes black
the Samsung logo appears and stays there indefinitely
So I turn the device off, long pressing the power key
then I try and turn on the tablet but does not turn on anymore,
not even pressing the power button for 30 second
then I press home+volume down+power again
to enter download mode and reinstall stock rom
(the same happens with
sm-t550_p550_p555_cf-autoroot.tar
or twrp_3.0.2-1_sm-t550_mm_7816.tar,
I also tried
twrp_3.1.1-1_sm-t355_251117
remark: none of them mentions T555 nougat)
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
V0latyle said:
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
Click to expand...
Click to collapse
What process did you follow to unlock your bootloader?
Stop trying to use Autoroot. Let's figure out what we need to do to get TWRP on your device. Once we do that, you can flash Magisk in TWRP for root.
Please read this guide, sections 1 through 4 (don't worry about the GSI stuff) and tell me what you have or have not done.
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
endlessquest said:
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
Click to expand...
Click to collapse
This is the first step. You cannot flash custom or modified images if the bootloader is locked.
Connect to the Internet and check for updates in system options, then check Developer Options again.
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
endlessquest said:
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
Click to expand...
Click to collapse
Has it ever appeared before?
V0latyle said:
Has it ever appeared before?
Click to expand...
Click to collapse
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
endlessquest said:
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
Click to expand...
Click to collapse
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
V0latyle said:
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
Click to expand...
Click to collapse
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
the Samsung SM-T819 I am writing from has a snapdragon chip
but I had no problem unlocking/rooting it,
I bought both the devices here in Rome
now that's a mystery...
endlessquest said:
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
Click to expand...
Click to collapse
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
V0latyle said:
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
Click to expand...
Click to collapse
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
endlessquest said:
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
Click to expand...
Click to collapse
You manually checked for an update too?
Did you try disconnecting from the Internet, disabling network time, and manually setting the time ahead 1 week?

Categories

Resources