• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

OEM unlocking doesn't show up

Search This thread

matteo0026

Senior Member
Jul 1, 2015
1,405
808
21
Treviso
Lenovo P2
BQ Aquaris X Pro
Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
Any solutions?
There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).
 
  • Like
Reactions: AussieNordo

matteo0026

Senior Member
Jul 1, 2015
1,405
808
21
Treviso
Lenovo P2
BQ Aquaris X Pro
There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.
I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.
 
  • Like
Reactions: AussieNordo

jirido

Member
Dec 3, 2021
8
0
Suomi
Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.

I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2

"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.

lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)

ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031

Still no device shows up with fastboot.

When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.

Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...

----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.

Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.

With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.

Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.
 
Last edited:

matteo0026

Senior Member
Jul 1, 2015
1,405
808
21
Treviso
Lenovo P2
BQ Aquaris X Pro
Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.

I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2

"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.

lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)

ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031

Still no device shows up with fastboot.

When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.

Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...

----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.

Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.

With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.

Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.
 

jirido

Member
Dec 3, 2021
8
0
Suomi
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.


And no windows in sight here... First time ever said.. SADLY !!????
 

matteo0026

Senior Member
Jul 1, 2015
1,405
808
21
Treviso
Lenovo P2
BQ Aquaris X Pro
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.


And no windows in sight here... First time ever said.. SADLY !!????
Then, if you don't have Windows, it's ok to use Heimdall, but you have to use it correctly. Use .img file, and if it doesn't work, rename the file to recovery.img
 

jirido

Member
Dec 3, 2021
8
0
Suomi
Yes. Just as you said. I did reinstall stock to all partitions and then flashed an older twrk to recovery after having rebooted. Then I updated it to latest. And now it works. I am a bit on the fence if I should root or not.. But Yeah.
Thanks guys.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
    Any solutions?
    There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).
    1
    There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.
    I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.