Database Users

unable to relock bootloader on op5?

I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?

You don't need to relock it, OnePlus warranty still covers unlocked bootloaders so it won't make a difference.

Thanks - would be useful to know how/why it isn't lockable though!

I just relocked bootloader on my Oneplus 5..
The normal way, fastboot oem lock.

gneville said:
I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?
Click to expand...
Click to collapse
Same here, I'm also sending back my OP5.
I have flashed the full zip stock from OnePlus.net, factory reset, reflash the rom... and still get the "not allowed" issue

Wahoux said:
Same here, I'm also sending back my OP5.
I have flashed the full zip stock from OnePlus.net, factory reset, reflash the rom... and still get the "not allowed" issue
Click to expand...
Click to collapse
Do you have wiped the dalvik cache, cache and data partition ? maybe then retry lock the bootloader en see of that works ?

Pieter20 said:
Do you have wiped the dalvik cache, cache and data partition ? maybe then retry lock the bootloader en see of that works ?
Click to expand...
Click to collapse
I have the same problem as OP. I wiped everything several times and is flashed a stock rom via adb sideload/ via twrp/ via stock recovery and is imposible to lock the bootloader. i tried W10, W7 and Ubuntu, no dice.
If i go to developer options the unlocking bootloader option is greyed out with this text:
The bootloader is already unlocked
I also tried with Hydrogen, the problem stays.
Can someone boot to fastboot and tell me what text appears to you in this colum?
PRODUCT_NAME -
After that mine says QC_Reference_Phone
I also interested in this fastboot command:
fastboot oem device-info
after that i get this
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.008s]
finished. total time: 0.008s
is the selinux_type the same as mine????

hardspartan360 said:
I have the same problem as OP. I wiped everything several times and is flashed a stock rom via adb sideload/ via twrp/ via stock recovery and is imposible to lock the bootloader. i tried W10, W7 and Ubuntu, no dice.
If i go to developer options the unlocking bootloader option is greyed out with this text:
The bootloader is already unlocked
I also tried with Hydrogen, the problem stays.
Can someone boot to fastboot and tell me what text appears to you in this colum?
PRODUCT_NAME -
After that mine says QC_Reference_Phone
I also interested in this fastboot command:
fastboot oem device-info
after that i get this
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.008s]
finished. total time: 0.008s
is the selinux_type the same as mine????
Click to expand...
Click to collapse
Reads the same for me, however I haven't tried relocking the bootloader.
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0

HueleSnaiL said:
Reads the same for me, however I haven't tried relocking the bootloader.
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
Click to expand...
Click to collapse
mmm... interesting.
Now we need someone that has relocked to compare. Your device product_name on fastboot is also the same?
i'm suspecting some people have a different bootloader than others and that's why some people can relock and others don't.
i erased almost everything (boot, system, recovery, data, cache) and the bootloader thing stays the same.
The other possibility is some file stored in "/" that prevents the relock but i'm afraid to brick, this files are accesible via twrp recovery file manager.

hardspartan360 said:
mmm... interesting.
Now we need someone that has relocked to compare. Your device product_name on fastboot is also the same?
i'm suspecting some people have a different bootloader than others and that's why some people can relock and others don't.
i erased almost everything (boot, system, recovery, data, cache) and the bootloader thing stays the same.
The other possibility is some file stored in "/" that prevents the relock but i'm afraid to brick, this files are accesible via twrp recovery file manager.
Click to expand...
Click to collapse
Mine says PRODUCT_NAME - QC_Reference_Phone. I think that's the same as everyone else.
I don't have any idea of what could be wrong, are you using the latest adb/fastboot version?

HueleSnaiL said:
Mine says PRODUCT_NAME - QC_Reference_Phone. I think that's the same as everyone else.
I don't have any idea of what could be wrong, are you using the latest adb/fastboot version?
Click to expand...
Click to collapse
Yeah, i'm using latest minimal adb fastboot.
I relocked a lot of phones in the past, including Op3 and Op3T but this one is a pain.
Enviado desde mi Nexus 5 mediante Tapatalk

gneville said:
I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?
Click to expand...
Click to collapse
Why do you want to do that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Verzonden vanaf mijn iPad met Tapatalk

How I relocked my One Plus 5
TL;DR to lock the phone:
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery (Maybe keeping TWRP works too, if you want to have the phone locked but keep TWRP?)
Run this command on your PC and select "Yes" on the phone. The phone will be wiped.
Code:
fastboot flashing lock
If you get "Your device is corrupt.", boot to recovery, find "Install from adb" and install full ZIP from your PC:
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
More detailed story
I wanted to get rid of the scary boot warnings on my phone because I'm selling it. I flashed the stock recovery, wiped everything, booted to fastboot but the lock commands didn't work.
Code:
fastboot flashing lock &:: this didn't work
fastboot oem lock &:: also didn't work
I booted the phone and looked at the "OEM unlocking" slider, but this is greyed out.
After being annoyed at things not working, I reinstalled TWRP, booted into recovery, and I flashed the Magisk zip file to install Magisk. Booted the phone normally, now "OEM unlocking" can be enabled (I think Magisk tricks the system so this can be re-enabled).
I rebooted to fastboot mode, typed "fastboot flashing lock", and the phone prompted me if I wanted to lock it. Success! But before this, I realized I have to first flash the stock recovery. So I did that, booted to fastboot, and repeated "fastboot flashing lock" to lock the phone.
Rebooting the phone I get the warning that the phone is corrupt:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Click to expand...
Click to collapse
They probably see that the system's been modified. Maybe I should've uninstalled Magisk. I rebooted to recovery, selected "Install from adb" and on my PC
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
After this, I rebooted the phone, and no more warnings! Yay!

you also need to flash stock recovery.

The way I did it:
- flash stock OOS with TWRP
- Fastboot flash stock recovery
- locked bootloader successfully

netsharc said:
[*] Install TWRP and Magisk if you don't have them yet.
[*] Magisk should allow you to slide "OEM unlocking" to "enabled"
[*] Reboot to fastboot
[*] Flash stock recovery (Maybe keeping TWRP works too, if you want to have the phone locked but keep TWRP?)
[*] Run this command on your PC and select "Yes" on the phone. The phone will be wiped.
Code:
fastboot flashing lock
[*] If you get "Your device is corrupt.", boot to recovery, find "Install from adb" and install full ZIP from your PC:
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
Click to expand...
Click to collapse
Thanks for sharing mate.
I`ve alredy rooted with SuperSu and TWRP installed. How do I flash Magisk over SuperSu ?
And I`ve tried to flash latest FW (OOS 4.5.10 Full Zip) with TWRP, but whenever I try to reboot it always says " No OS Installed .......".
I`ve tried several times, but every time it remains the same.
I totally new to OP devices. It would be very helpful, if you share how to revert back to stock OOS and lock the bootloader.

here in this video u can see in detail how to lock bootloader. hope this help
https://www.youtube.com/watch?v=CQYCSdDUdAU

Noob can't unlock bootloader

Hi folks,
I just received my Essential Phone, purchased through amazon. As you recall, the Essential Phone was rumored to have an unlocked bootloader. This was confirmed by @essential confirming that it will, in a tweet.
However, this is not what I'm experiencing with the phone.
After powering it up and playing around a bit, I enabled USB debugging and linked it to my computer, where I have the latest (as of today) android platform tools installed. I rebooted to fastboot and tried to issue "fastboot oem unlock", as I did with my previous phone, a nexus 6p. However, it seems "oem" is no longer a valid subcommand of fastboot; it has been renamed to "flashing unlock", along with some other new-to-me commands:
Code:
$ fastboot --help
usage: fastboot [ <option> ] <command>
commands:
.....
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
The "flashing unlock" command looks interesting. Let's try that:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
Hmmm... I don't like the look of that. Well, let's see what "get_unlock_ability" says:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Ok, that looks bad too. Let's try those other new commands and see if we can get anywhere...
Code:
$ fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s
Nope.
Code:
$ fastboot flashing get_unlock_bootloader_nonce
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Double nope.
Well that's not encouraging. I don't claim to be any sort of expert in regards to unlocking phones, but I can't find any other methods using these tools, and Essential's docs aren't any help. I've contact their phone support but haven't heard back after about an hour. (They use some ridiculous system where you schedule a callback... Not happy.)
So, I'm feeling pretty upset. Let's be clear here:
Essential said this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But shipped a product with this:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s

Did you turn on the allow unlocking toggle in developer options?

tw1tch175 said:
Did you turn on the allow unlocking toggle in developer options?
Click to expand...
Click to collapse
Thanks, that did the trick

xMopx said:
Thanks, that did the trick
Click to expand...
Click to collapse
So ...wich are the right steps and command d to unlock the bootloader?
thx

mastercut said:
So ...wich are the right steps and command d to unlock the bootloader?
thx
Click to expand...
Click to collapse
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers

frhoward said:
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
Click to expand...
Click to collapse
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?

DenverDroid said:
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
Click to expand...
Click to collapse
First in fastboot type "fastboot devices" if a string of numbers answers it is ok otherwise you need fastboot driver ....have you cheked?

Hi guys, I have an issue with unlocking the bootloader. fastboot devices returns the device ID, but flashing unlock gives me failed, unknown command error. I cannot get it working. Any ideas?
/edit: changing PC's helped

Essential Phone stuck in Start up screen with Locked Bootloader
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!

[email protected] said:
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
Click to expand...
Click to collapse
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.

wrecklesswun said:
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
Click to expand...
Click to collapse
Yeah, I had such instances too in the past. But no luck this time...
My OEM locking is not switched on and I'm unable to sideload the OTA or Rest the phone to factory.

Can't Re-Unlock bootloader?

Hi i've done something stupid, i've blocked bootloader idk why, anyway im in LineageOs 16, but now i can't back to stock or flash something else ¿i cant re-unlock bootloader?

What is the error that you're getting?

Fastboot flash bootloader permission denied

elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.

weazie said:
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
Click to expand...
Click to collapse
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P

elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
Did you find any solution?
Same problem!

Works for me!
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
First, install gnirehtet for reverse tethering internet with usb and pc
https://github.com/Genymobile/gnirehtet
Then you will see that you can enable OEM

I'm still not able to unlock oem in settings. I have WIFI on and did all the updates to the latest

elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Same error here. Did anyone find a solution?

Constantinologia said:
Same error here. Did anyone find a solution?
Click to expand...
Click to collapse
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.

mrsiri said:
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
Click to expand...
Click to collapse
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Constantinologia said:
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
View attachment 5251849 View attachment 5251851
Click to expand...
Click to collapse
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings

mrsiri said:
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
Click to expand...
Click to collapse
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s

Constantinologia said:
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Click to expand...
Click to collapse
I don't remember the steps to reproduce, but I remember being possible to take the very own boot.img currently flash on your phone. I think it was through adb commands, what if you try booting that one instead? That's what I did on mine, but it didn't help with toggling oem unlock, only entering the system

I accidentally locked mine and im in the same situation as everyone here, but i think the only solution is BlankFlashing or sideloading a signed OTA on it... Im trying everyday new possible methods of fixing it and if i get into some ill share here

hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good Luck

thehulk1969 said:
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good LuckView attachment 5274327
Click to expand...
Click to collapse
It would be the solution if the stock was corrupted, but i have locked mine on StyxOS, and there isn't any boot.img for it so stock boot.img gives a system corrupted error. But nice idea.
Edit: Does it need to match the ro.fingerprint on getvar all? only tested with latest pie, so

Amazon Fire TV (1st Generation) unlock

Please help me to unlock the bootloader, access the network. I use USB a - USB A. after the update, only the logo is loaded. Enable debugging via usb is not possible
PS D:\Amazon\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot oem device-info
(bootloader) Device tampered: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools> fastboot -w
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools> fastboot getvar all
all:
Finished. Total time: 0.000s
PS D:\Amazon\platform-tools>

If your FTV is on FireOS 5 (505 and up), then forget about this sh*t. No unlock possible^^

Sus_i said:
If your FTV is on FireOS 5 (505 and up), then forget about this sh*t. No unlock possible^^
Click to expand...
Click to collapse
I don't even know what version is out there. Given.
Wanted to add that fastboot works!!!
Maybe have the option of using test points to unlock?

Boot the FTV1 up (with disabled updates) and look in the settings for your fireOS version. Afaik the devices with 51.xxx (5 digits) can unlocked/rooted with software/adb.
FireOS 5 can´t bootloader unlocked, because bootloader checks fuses (5.0.5 and up). Last software rootable version is 5.0.5.
Aside from fireOS, if you build a low voltage emmc reader and solder wires to a few pins onto the board of the FTV, you can flash the emmc with twrp (for locked bootloader) and a prerooted rom from rbox.
https://www.exploitee.rs/index.php/Exploitee.rs_Low_Voltage_e-MMC_Adapter

Sus_i said:
Boot the FTV1 up (with disabled updates) and look in the settings for your fireOS version. Afaik the devices with 51.xxx (5 digits) can unlocked/rooted with software/adb.
FireOS 5 can´t bootloader unlocked, because bootloader checks fuses (5.0.5 and up). Last software rootable version is 5.0.5.
Aside from fireOS, if you build a low voltage emmc reader and solder wires to a few pins onto the board of the FTV, you can flash the emmc with twrp (for locked bootloader) and a prerooted rom from rbox.
https://www.exploitee.rs/index.php/Exploitee.rs_Low_Voltage_e-MMC_Adapter
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have it only boots to the logo and all to go to settings is not possible. I used a usb a-usb a cable to connect. So I have a prefix is defined in the device Manager as a fastboot device, and as adb is not. Will you be able to specify on the scheme to specify the contacts to which you want to connect and more detailed instructions for recovery?

Take a look at the gtv hackers, you can see the pin out of the adapter and the pins on the board. There is also a video.
https://www.exploitee.rs/index.php/Amazon_FireTV
If you get this adapter (seems sold out/ you need to build it on your own) you can read/write to all partitions on the emmc (with a pc running linux), flash a new recovery and so on.
But maybe you find a way to reset the FTV on this site?
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/

Sus_i said:
Take a look at the gtv hackers, you can see the pin out of the adapter and the pins on the board. There is also a video.
https://www.exploitee.rs/index.php/Amazon_FireTV
If you get this adapter (seems sold out/ you need to build it on your own) you can read/write to all partitions on the emmc (with a pc running linux), flash a new recovery and so on.
But maybe you find a way to reset the FTV on this site?
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Unfortunately, I don't have a low voltage eMMC adapter and don't know if I can find one. With UART you can unlock something? Uart is more available to me.

Don´t know, but don´t think so.

Sus_i said:
Don´t know, but don´t think so.
Click to expand...
Click to collapse
And how do you know why it doesn't switch to adb mode? Only fastboot works for me.

smurat_82 said:
And how do you know why it doesn't switch to adb mode? Only fastboot works for me.
Click to expand...
Click to collapse
I would try a usb hub with a usb keyboard for reset if the reset via remote doesn´t work.
You can look in the bueller bootloader unlock threads here on xda (fire tv android development section), maybe the fastboot commands work for you.

Sus_i said:
I would try a usb hub with a usb keyboard for reset if the reset via remote doesn´t work.
You can look in the bueller bootloader unlock threads here on xda (fire tv android development section), maybe the fastboot commands work for you.
Click to expand...
Click to collapse
Unfortunately, did not help a full reset Alt+i+Print screen, and adb is not available, only fastboot mode

Maybe try this:
fastboot erase data
fastboot erase cache

Sus_i said:
Maybe try this:
fastboot erase data
fastboot erase cache
Click to expand...
Click to collapse
I tried, didn't help
PS D:\Amazon\platform-tools> fastboot devices
7090020141650DN4 fastboot
PS D:\Amazon\platform-tools> fastboot erase data
Erasing 'data' FAILED (remote: 'erasing not allowed for locked hw')
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools> fastboot erase cache
Erasing 'cache' FAILED (remote: 'erasing not allowed for locked hw')
Finished. Total time: 0.016s
PS D:\Amazon\platform-tools>
Probably only this method will help, thank you very much for your help
https://www.youtube.com/watch?v=IgC4iDzQ8gw&feature=youtu.be

You can try this.
https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337/post56987752#post56987752

Struggling to flash the x720 , Help !

Hi
Long story short
i got my leeco le pro 3 x720
i got it from aliexpress and this is how it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So When i received the phone i went and installed the usb drivers and the adb tool ofc after i did my research
so in the adb and after checking for the devices there , i reboot into fastboot mode and checked for the device and it was recognized , i sent "fastboot oem unlock-go" to unlock the boot loader , i received this :
...
OKAY [ 0.008s]
finished. total time: 0.009s
then i checked with "fastboot oem device-info"
and i got :
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
now into the problem
when i reboot and check again with "fastboot oem device-info" :
i receive :
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
So i went and did everything again but instead of reboot i flashed the latest twrp from the official stie
then i did "fastboot boot [recoveryname]" to boot to the recovery , that did work and i got into the twrp
but when i shut my device and enter to the recovery via "power button and volume up"
i get the leeco logo + recovery underneath it , then everything turns black
when i connect to the adb and check for adb devices it says recovery
but the screen stays black until I reboot to to the system again
so heres what i tried ( another twrp version "old ones" and didnt work i tried the stock recovery again and it did not work)
i get the same black screen when I get to the recovey i can access the recovery only via "fastboot boot recovery.img"
even if i did "adb reboot recovery" i get black screen
i tried All in one tool to check with the bootloader again when i check the statue of the boot loader nothing happens
when i try to unlock it it says failed , i didnt wont to press lock bootloader cause i dont know how to use the tool yet.
and one more thing : when i got to twrp on the first time via "fastboot boot...." when i try to flash i get vendor errors and stuff.
so please help me , i spent two days or more searching for any clue :'(
its my first time into custom roms and i really want to flash the leeco le pro 3 into a better rom
i even tried to flash my Lg stylo 2 plus to 8.1 oreo and that was a piece of cake i got it running in less than an hour
as a test subject.
HELP ! ​

Yep, EUI will restore the stock recovery. You have to do the TWRP installation this way, especially step 5:
Installation:
1. Make sure your bootloader is unlocked
2. Download the recovery image from above
3. Reboot into fastboot
4. Run this command (Change the .img to whatever the name of file is you downloaded): fastboot flash recovery twrp-3.5.0_9-1-zl1.img
5. Once it is flashed, please force a reboot to recovery by holding down the Power and Volume Up buttons at the same time until the phone reboots and you see the LeEco logo and the word "recovery" underneath it. (This is because if you allow normal boot after flashing TWRP while you are using EUI and your phone reboots to EUI it will overwrite the recovery with the stock EUI recovery. Forcing a reboot from the bootloader to recovery prevents this issue)

is it okay if the bootloader unlock temporarily ? i did try unlocking the bootloader then flashing the twrp then rebooting to recovery with the power key and volume but same issue the screen turns black after the leeco logo with the recovery word , the only way i can access twrp by fastboot boot "name".img , but i dont know if its the correct way

Ehm, sorry, right now I see that you didi not flash the bootloader. You have to do this with:
fastboot flash recovery.img

did everything you suggested , still when i go to recovery i get a black screen cant install my roms like this , im sad now

No, I think we missed something. Check this step by step guide completly:
https://www.getdroidtips.com/unlock-bootloader-leeco-le-pro-3/
Did you OEM unlock before you unlock the boitloader?

i did every single thing oem unlock usb debugin my pc is recognizing the phone in adb and fastboot
i unlocked the bootloader with the command fastboot oem unlock-go
then checked with fastboot oem device-info
then i flashed latest twrp recovery with "fastboot boot recovery [name].img
then i pressed and hold power and volume up untill i got leeco logo + recovery word then the screen goes black thats it

So first part should be OK. But you did not flash the recovery. fastboot boot recovery.img is just to started the recovery from memory and not to install it. The correct command to flash is: fastboot flash recovery.img
After this you have to do the force reboot.

i typed the wrong command xD i really flash it with fastboot flash you can check the whole steps i did in the main thread above , anyways i found the problem and got everything working all i need to do was to flash a new firmware to unlock the bootloader and thats it , thank you for helping :3

Well done. Wih the the new firmware you removed EUI. So the bootloader isn't reset anymore. Have fun with the device.

THANK YOU SO MUCH !!