Problems relocking bootloader - Honor 7 General

Hi, I'm having update problems after unlock bootloader, and when I try to relock, I get this error:
fastboot oem relock XXXXXXXXXXXXXXXXX (my code)
...
FAILED (remote: root type is risk)
finished. total time: 0.788s
I have tryed with b100, with b121... in all cases, same error... Any ideas?
Thanks in advanced.

same goes to me

lomunet said:
Hi, I'm having update problems after unlock bootloader, and when I try to relock, I get this error:
fastboot oem relock XXXXXXXXXXXXXXXXX (my code)
...
FAILED (remote: root type is risk)
finished. total time: 0.788s
I have tryed with b100, with b121... in all cases, same error... Any ideas?
Thanks in advanced.
Click to expand...
Click to collapse
You should check other threads for your problems same as yours first, then and only then you should create a new one to avoid same question asked many times. You can find your solution posted HERE.

Related

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.

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

Mist built and now problems with bootloader FAILED (remote: Command not allowed)

Hello, and I have mist built yesterday with my Huawei P8 Lite ALE-21 dual Sim.
I wanted to play this Rome yesterday
https://forum.xda-developers.com/showpost.php?p=73230358&postcount=2 b895_update.zip
This did not work and made a mistake.
After that, I re-imported the original ROM without any problems.
After all it was again, I booted into the bootloader / fastboot synonymous but works
as soon as I now the recovery (fastboot flash recovery recovery.img)
I always get the following message.
target reported max download size of 471859200 bytes
sending ´recovery´ (25152kb)...
OKAY [ 0,797s]
writing ´recovery´...
FAILED (remote: Command not allowed)
finished. total time: 0.797s
The bootloader / fastboot is unlocked.
Did I shoot this now?
What could I do about it because the Huawei site where you get
the bootloader unlock code did not work anymore in Germany!!
Would appreciate a response or help very much.
Sorry for the bad english, i have translated with google
EDIT: it work again!
same issue
Hi I have the exact same issue with my Huawei p8 lite I can only go into fast boot mode but it says Phone locked and all my commands give me the exact same error Failed (remote:command not allowed ) and advice for me ? Thank you
Unlock the bootloader again (fastboot oem unlock <code>) and try again

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

Categories

Resources