Database Users

how lock bootloader mate 8

hi i am new user to mate 8 and i want ask how relock the bootloader because i received unlock i try with fastboot cammand but he write me that
FAILED (remote: Command not allowed)
finished. total time: 0.015s
that i write in cmd to lock is fastboot oem lock and my bootloader code
please help me thanks

winnie19810 said:
hi i am new user to mate 8 and i want ask how relock the bootloader because i received unlock i try with fastboot cammand but he write me that
FAILED (remote: Command not allowed)
finished. total time: 0.015s
that i write in cmd to lock is fastboot oem lock and my bootloader code
please help me thanks
Click to expand...
Click to collapse
fastboot oem relock (+your code )
I think that's the syntax

try my tool [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility

Does relocking get rid of the message saying your device has been tampered with?

somboons said:
try my tool [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility
Click to expand...
Click to collapse
Dont detect my phone.
On command line detect, but in your too,l don't detect on fastboot mode.

ovitaIRC said:
Dont detect my phone.
On command line detect, but in your too,l don't detect on fastboot mode.
Click to expand...
Click to collapse
Type fastboot oem lock

fastboot oem lock does not working, fastboot oem relock does, but after that you will only see relocked in fastboot mode. If you want to send back your phone to the Service in guarantee, you need to have the Locked status (if not, relocked is fine).
To do that, follow this guide:
http://forum.xda-developers.com/mate-8/general/whats-happened-message-boot-screen-t3321943

When I updated the phone software (UPDATE.APP dload method) my phone got relocked

I go from B193 to B320 and go back to B180/193,the Bootloader is “Locked“ after this Procedur.

HTC Desire 310 brick, bootloop, SPFlashTool failure - disconnect after few second

I have a big problem with my old phone. Well, I have a HTC Desire 310 which was not used for a long time, after launch stopped on the logo. Then I decided to install stock rom. I downloaded a rom from a Russian site, then installed the MediaTek USB VCOM drivers and the FlashTool SP program.
The problem is that I broke something that the phone has bootloop and at the bottom of the message "TOOL DL Image Fail!". When I try to flash the rom with the battery after 9 seconds to restart and without battery after 2 seconds and disappears from the device manager.
I do not remember if this phone had administrator privileges
I downloaded various versions of FlashTool and drivers from different sources and nothing
Does anyone have any ideas what else can be done?
I used these guides:
https://forum.xda-developers.com/android/help/tuto-how-to-unbrick-htc-desire-310-dual-t3057203
https://forum.xda-developers.com/general/rooting-roms/guide-mediatek-spflashtool-failure-t2936933
https://forum.xda-developers.com/showthread.php?t=1982587
PS. Please excuse my English, if someone does not understand something I will try to explain more clearly.

I solved part of the problem. After many attempts to install rom. The next problem is unlocking the bootloader.
There are further problems. To enter fastboot I was write adb reboot-bootloader into the console (volume - and power not working).
Then a black screen appears and a small inscription FASTBOOT mode... .
When I enter the command fastboot device my device is visible but after entering command fastboot oem get_identifier_tokenit three dots appear and nothing happens
Another problem is the incorrect CID. I do not know if you have to download the bootloader first or change the CID

Currently, in fastboot mode, no commands work except fastboot devices.
I get errors when I type fastboot getvar:
Code:
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.003s
help

Exacty same problem. Someone please help what can i do?
Thank you very much

Need HELP about unbricking U Ultra :(

Need some help if someone can do that
- I have oem unlocked my b/l with unlock code, install twrp, try some polished rom but i don't like it and try to go back to oem locked state to flash an RUU file through ADB...
When i go to download/fastboot mode and type a "fastboot oem lock" command i have a message
"C:\adb>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.028s]
finished. total time: 0.029s"
to my PC and on my phone i have a question "Yes to OEM lock and hard reset or No to live..."
I point to Yes and when confirm that my phone rebooted to a loop rebooting and blinking display with HTC logo and red words text...
Whatever i try to do it's always blinking/rebooting
Is there any way to normallise my phone and turn to any normal state?!
TNX

I moved out from previous state!!!
What a luck!
Dont know how but pressed VolUp+VolDown+Power and gone to bootloader state. After that have to unlock b/l again and after that when gone to Recovery, my TWRP is still there what a sweetness....
When enter to TWRP just some quick tex "Decrypting phone" and immediately rebooting to a normal state with all working phone states!
Is there any way to lock b/l again, turn to OEM state and to do a normal/regular HTC updating???
My last HTC update was 1.64.401.10 and European version...
Any advice?
TNX

Flash stock recovery: https://forum.xda-developers.com/u-ultra/development/unlocked-model-stock-recovery-t3585622 and you should be able to lock your bootloader successfully.
Never update with a third-party recovery. After you are done updating, install custom recovery again.

Ok.
I didn't know that
Tnx

PRA-LX1 stuck in bootloop, can't be turned off - locked, access to fastboot only!

Hello xda,
my cousin owns the P8Lite (PRA-LX1) and gave it to me to attempt unbricking it.
The device is stuck in a permanent bootloop, showing the Huawei logo. When pressing the power button for ~10s, it simply turns itself on again (even when not connected to a PC or the wall socket), which to me is very strange behaviour but I do not own a Huawei device.
I can get to fastboot (https://ibb.co/ixPtAn).
ADB does not recognize the device.
Fastboot does not let me boot a temporary recovery (be it the stock one or twrp), neither does it allow me to flash any file.
I have tried downloading the update.app file onto the root directory of the sd card and force the phone into the update mode (power, vol+, vol- at the same time) but to no avail.
Since it is not my own device and I cannot boot into Android at all, I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Is this device permanently bricked and a lost cause or is there still hope?

dejavecue said:
I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Click to expand...
Click to collapse
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH

badhabitsdiehard said:
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH
Click to expand...
Click to collapse
Oh yes I got the original one. But since I cannot boot, I cannot get the S/N that is apparently required as well.
Edit: Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website. It still says
PS C:\Users\*\Downloads\unlock bootloader> fastboot oem unlock ************
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\Users\*\Downloads\unlock bootloader>
Click to expand...
Click to collapse

dejavecue said:
Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website.
Click to expand...
Click to collapse
Hi, sorry for the delay.
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?

Thank you for your comment:
badhabitsdiehard said:
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Click to expand...
Click to collapse
Code:
$ fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.012s]
finished. total time: 0.014s
badhabitsdiehard said:
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?
Click to expand...
Click to collapse
Code:
$ fastboot oem frp-unlock {password censored}
...
FAILED (remote: password matching failed!!)
finished. total time: 0.211s
It is definitely the code I got from the Huawei Website.

x727 Failed (remote: oem unlock is not allowed)

I have a problem with unlock bootloader, it says "FAILED (remote: OEM unlock is not allowed) finished. Total time: 0.031s, I use LEX727 with eui version 5.8.021s. Please help me to unlock the bootloader.

Kavolux said:
I have a problem with unlock bootloader, it says "FAILED (remote: OEM unlock is not allowed) finished. Total time: 0.031s, I use LEX727 with eui version 5.8.021s. Please help me to unlock the bootloader.
Click to expand...
Click to collapse
Start here >> https://r.tapatalk.com/shareLink?ur...share_tid=3500388&share_fid=3793&share_type=t
Sent from my PH-1 using Tapatalk

Fixed it with qfl
I downloaded a stock from from
download.lenovo.com/lsa/Rescue/Tablet/TB-X104/TB-X104F_S100031_190224_ROW_DCC.zip
And used
https://www.96boards.org/documentation/consumer/guides/qdl.md.html
To install qdl
Then I found the programmer inside the first download and including the unsparse upgrade.xml and the patch0.xml
Reboot to fastboot to turn it off and unplug do the hold down vol down while plugging it in to get into the qdl edl mode
Took a few tries and I may have cycled through the ffbm mode with the qdl running but I don't think thas