Database Users

[GUIDE] Unlock the bootloader of Zuk Z1 without using fastboot & wiping userdata

Introduction
As we know, the official way to unlock the bootloader of Zuk Z1 is through fastboot.
For a untouched device, the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]false[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first, then via bootloader/fastboot interface:
Code:
fastboot -i 0x2b4c oem unlock-go
It'll eventually erase the userdata.
Then the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]true[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
Inspired by the findings on similar devices, we can actually unlock the bootloader of Zuk Z1 without using fastboot, while keeping the userdata intact.
How-to
Warning!
It is dangerous! This whole thing is basically one giant hack - which is not intended to be done by normal users. It is messing with the bootloader partition, so it is possible that something goes wrong and you will have a nice & costly brick in your pocket. Be prepared to revive the device from a hard-brick.
1.
Enable 'OEM unlocking' under Developer options. You may need to tap the Build number 7 times under About phone to get the Developer options under Settings.
2.
We need root access (kinda expected!). To root the device without unlocking bootloader, use KingRoot. Use the Android version.
Now there is a catch! KingRoot can root the device, cause the latest build of Cyanogen OS (cm-12.1-YOG4PAS3OH-ham ATM) contains such vulnerabilities which can be exploited by the root exploits used by KingRoot. But we can't ensure about future.
3.
After being rooted, use adb shell or any terminal emulator to dump the 'aboot' i.e bootloader partition in internal sdcard:
Code:
su
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
4.
Now we need to modify the dumped image using hex-editor. For Zuk Z1:
Code:
Unlock Bit Position - 0x001FFE10 Hex
Tamper Bit Position - 0x001FFE14 Hex
'00' means false, '01' means true. So to set the bootloader as unlocked, we just need to change the following:
{
"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"
}
Save the modified image as 'abootmod.img' inside your sdcard.
5.
Now its time to flash back the modded bootloader. Execute the following from adb shell or any terminal emulator:
Code:
su
dd if=/sdcard/abootmod.img of=/dev/block/bootdevice/by-name/aboot
Do a reboot & voila! You have unlocked the bootloader! Don't just believe me - check the status of the bootloader to ensure.
Note
1. We can also reset the tamper bit using this procedure.
2. If you prefer GUI, then you can use this fantastic app by @wanam.
3. This is tested on an international Zuk Z1 running cm-12.1-YOG4PAS3OH-ham. Please test & post feedback to ensure compatibility.
4. I'm not providing pre-modified images as it increases the risk of bricking the devices having older/newer bootloaders - please do it yourself. The offsets should be unchanged in future, though.
Credits
1. @osm0sis
2. @segv11
3. @Mnt-XDA
4. @Tengo10 - for risking his device for this experiment.
5. Users of XDA.
Happy tinkering! :highfive: :good:

Reserved for future.

I tested now and working okay. Thaaaaaaaaaaaaaaaaanks

after using dd for writing the modified image it worked. seems to be a problem using the app Partitions Backup & Restore
old post
Doesn't worked for me.
fastboot -i 0x2b4c oem device-info still shows
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.009s]
finished. total time: 0.010s
when I read the aboot-partition after writing the modified image my modification is gone, i used Partitions Backup & Restore App for reading and writing
Click to expand...
Click to collapse

Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you

Lems84 said:
Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you
Click to expand...
Click to collapse
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first

yes I did it, USB debogging and OEM unlocking on the ZUI interface.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse

Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
I also have the same problem.I enabled OEM.solutions please?kindly?

Thanks!

Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx

carstenheuer said:
Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx
Click to expand...
Click to collapse
The Problem is that he don't own that phone.

Tengo10 said:
The Problem is that he don't own that phone.
Click to expand...
Click to collapse
what happen when i flash TWRP with flashify app when the bootloader is still locked?

carstenheuer said:
what happen when i flash TWRP with flashify app when the bootloader is still locked?
Click to expand...
Click to collapse
Nothing special, you only can't flash unsignt zips and IMG.

Hello, I'm having this problem. I do not see the "OEM Unlocking". I have enabled USB Debugging already. Please help.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse

Problems with fastboot
I was going to follow this guide but fastboot doesn't recognize my zuk. I tried to install all the drivers from sdk, and then i tried also to manually select them in the devices settings of windows but my pc says that there aren't any drivers in the folders. Ho can I solve it? I looked over and over the internet but this phone is apparently really rare so there are no working solutions for this. Can someone help me? :crying:

It works!
Zuk Z1 international, it worked perfectly! Just, I had to change the name of abootmod in about to substitute the original file, so " dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot "

You should have written a bigger warning that it ERASES USERDATA!

Tuberomix said:
You should have written a bigger warning that it ERASES USERDATA!
Click to expand...
Click to collapse
Well, this method doesn't touch the userdata partition.

Titokhan said:
Well, this method doesn't touch the userdata partition.
Click to expand...
Click to collapse
Whatever it wipes, I do ask that you put a warning in big, bold, red letters!

@Tuberomix
Looks like there is some misunderstanding; this method doesn't wipe anything. Can you please elaborate about your experience?

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.

[guide] root le x626

First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk

Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.

How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse

onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset

okay, thanks for your response and clarification...cheers to that.

Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>

tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?

Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

Please see screenshot...
{
"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"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power

Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??

tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip

Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.

tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it

Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'

tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power

Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !

tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome

Don't suppose kingroot or similar works? I'm very lazy lol

I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help

How to unlock a Moto G7 xt1962-6

I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?

rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/

Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"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"
}

rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?

Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .

rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!

Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan

WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.

rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all