Database Info

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik

Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out

I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..

YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks

Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.

zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.

Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s

That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon

Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo

Im have the same issue but I have no recovery installed..Anyway to do this

i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

[q] cant enable usb debugging

My Nexus 5 will not boot it gets stuck on the 4 circles spinning loading screen, when i go into recovery mode it says E: failed to mount /cache (Invalid Argument), i have tried wipe data/factory reset but it still does the same thing, now i want to flash it to a factory image but USB debugging isn't enabled and i cant turn on the phone to enable it, is there any other way to enable it? I'm new to this so i don't know much about it, any help would be great, thanks.

First try to wipe cache. This may take up to 15 minutes.
If it doesn't work: You don't need USB debugging enabled to flash a factory image.

experience7 said:
First try to wipe cache. This may take up to 15 minutes.
If it doesn't work: You don't need USB debugging enabled to flash a factory image.
Click to expand...
Click to collapse
I have tried wiping cache, still does the same thing, and the tutorial i was on to unlock the boot loader said i needed USB debugging enabled.

You don't need USB debugging on to flash factory image .
Sent from my Nexus 5 using Tapatalk

You are getting mixed up. Adb is for when android is up and running. If it's crashed you boot to the bootloader and use fastboot
fastboot flash boot boot.img
fastboot flash system system.img

Ben36 said:
You are getting mixed up. Adb is for when android is up and running. If it's crashed you boot to the bootloader and use fastboot
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
when i try to fastboot flash boot boot.img it says
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.153s]
writing 'boot'...
FAILED < remote: not supported in locked device>
finished. total time: 0.619s
and nothing happens on the phone, am i doing something wrong ? i am new to doing this so any help would be appreciated, thanks.

Chris2073 said:
when i try to fastboot flash boot boot.img it says
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.153s]
writing 'boot'...
FAILED < remote: not supported in locked device>
finished. total time: 0.619s
and nothing happens on the phone, am i doing something wrong ? i am new to doing this so any help would be appreciated, thanks.
Click to expand...
Click to collapse
First, unlock your bootloader.
fastboot oem unlock
Then you use the fastboot flash commands.
By the way where is this guide which tells you need usb debuging enabled to unlock bootloader? I see this nonsense everytime.
Sent from my Nexus 5 using XDA Free mobile app

bitdomo said:
First, unlock your bootloader.
fastboot oem unlock
Then you use the fastboot flash commands.
By the way where is this guide which tells you need usb debuging enabled to unlock bootloader? I see this nonsense everytime.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that, now when i try to flash system i get
FAILED (remote: flash write failure)is there anything i can do about this? or is it the end of my Nexus 5? Thanks for all your help.

Chris2073 said:
I tried that, now when i try to flash system i get
FAILED (remote: flash write failure)is there anything i can do about this? or is it the end of my Nexus 5? Thanks for all your help.
Click to expand...
Click to collapse
I am sorry to tell you but flash chip of the device is gone bad. You have to buy a new motherboard

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.

e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps

smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C

GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?

smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt

Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i

GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.

I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!

GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.

ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.

meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.

I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.

GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?

I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/

Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )

Go to an independent repair shop. They have the equipment to flash on the motherboard.

Moto G3 (XT1543, osprey) stuck at fastboot screen

Dear people,
First of all, although dilligent and trying to do my homework, I am a total newbie regarding anything Android. Therefore, if I am posting on the wrong section of the site, please let me know and I will try my best to fix it.
That being said, I have a Moto G3 (Moto G 2015), model XT1543 (osprey), that is stuck in the fastboot boot. I have searched a lot of the web trying to find solutions and, after having failed all of them, decided to come here for assistance.
My device only boots and displays:
AP Fastboot Flash Mode (Secure)
version downgrade for recovery
failed to validate recovery image
ERROR: Failed to pass verification, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode​
I already downloaded the appropriate TWRP recovery image for the device (osprey), but the bootloader is locked and, since I can't get into the system properly, I can't switch the "Unlock OEM boot" flag when the full system is running.
In particular, when I try to flash TWRP, this is what I get:
# fastboot flash recovery twrp-3.1.0-1-osprey.img
target reported max download size of 268435456 bytes
sending 'recovery' (7546 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.454s​
Indeed, since I am only in fastboot mode, I went away and requested a boot unlock code from Motorola and trying to unlock the bootloader and this is what I get:
# fastboot oem unlock <my-code-here>
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.034s​
I already tried looking at similar questions in many, many forums and no answer actually applied to my device (including, for example, https://forum.xda-developers.com/2015-moto-g/help/moto-g3-struck-fastboot-screen-t3542147 and even others for other models and vendors).
Thanks in advance for any help.

At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Sent from my MotoG3 using Tapatalk

riggerman0421 said:
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Click to expand...
Click to collapse
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).

rtbrito said:
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
Click to expand...
Click to collapse
You can follow the guide here. Try it with the latest firmware available here.
Broadcasted from Zeta Reticuli

P8 Lite:Fastboot command (Failed: Command not allowed)

So i am having a problem while trying to install TWRP via ADB. When i am typing command "fastboot flash recovery recovery.img" i get this "Failed:<remote> Command not allowed" code.
I tried using cmd and Powershell with Administrator's right but the same thing happening again and again. I even tried to root the phone using in-phone programmes (Kingroot, Kingoroot, iRoot)in order to use Flashify and flash recovery through there and still nothing. OEM is unlocked and i can't really relock the phone since i dont have the unlock code anymore and Huawei doesn't support Unlocking devices anymore from her website to get a new one.
Things i did up to this point:
Enabled USB Debugging
Installed Huawei USB Drivers
Opened Powershell/Minimal ADB and Fastboot with Administrator
Typed command "fastboot flash recovery recovery.img"
Got this :
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.584s
Is there any way of installing TWRP on this phone ?
Is there any method i can root this phone in order to flash TWRP from Flashify?

xWonderizZ said:
So i am having a problem while trying to install TWRP via ADB. When i am typing command "fastboot flash recovery recovery.img" i get this "Failed:<remote> Command not allowed" code.
I tried using cmd and Powershell with Administrator's right but the same thing happening again and again. I even tried to root the phone using in-phone programmes (Kingroot, Kingoroot, iRoot)in order to use Flashify and flash recovery through there and still nothing. OEM is unlocked and i can't really relock the phone since i dont have the unlock code anymore and Huawei doesn't support Unlocking devices anymore from her website to get a new one.
Things i did up to this point:
Enabled USB Debugging
Installed Huawei USB Drivers
Opened Powershell/Minimal ADB and Fastboot with Administrator
Typed command "fastboot flash recovery recovery.img"
Got this :
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.584s
Is there any way of installing TWRP on this phone ?
Is there any method i can root this phone in order to flash TWRP from Flashify?
Click to expand...
Click to collapse
In huawei devices recovery named recovery_ramdisk, so fastboot command is different.
I suggest use huawei multi tool for flashing recovery or system gsi .

hamedsolo said:
In huawei devices recovery named recovery_ramdisk, so fastboot command is different.
I suggest use huawei multi tool for flashing recovery or system gsi .
Click to expand...
Click to collapse
Do you know the fastboot command ? Also do i have to name my recovery as recovery_ramdisk?

xWonderizZ said:
Do you know the fastboot command ? Also do i have to name my recovery as recovery_ramdisk?
Click to expand...
Click to collapse
look at this
tobyffm said:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
Mod can close this thread.
Click to expand...
Click to collapse
as I said before, use this tool and don't bother yourself with typing commands
https://forum.xda-developers.com/t/tool-huawei-multi-tool-v8-by-team-mt.3523923/
do more search my friend

hamedsolo said:
look at this
as I said before, use this tool and don't bother yourself with typing commands
https://forum.xda-developers.com/t/tool-huawei-multi-tool-v8-by-team-mt.3523923/
do more search my friend
Click to expand...
Click to collapse
I will give it a try. Thanks a lot

hamedsolo said:
look at this
as I said before, use this tool and don't bother yourself with typing commands
https://forum.xda-developers.com/t/tool-huawei-multi-tool-v8-by-team-mt.3523923/
do more search my friend
Click to expand...
Click to collapse
404 Not Found​Also the site https://pro-teammt.ru/huawei-multi-tool is not working.

alex27riva said:
404 Not Found​Also the site https://pro-teammt.ru/huawei-multi-tool is not working.
Click to expand...
Click to collapse
I uploaded my files to this link. Rar pass is [email protected] . I hope you find it useful.
4.49 MB file on MEGA
mega.nz