Database Info

Locked bootloader / but fastboot is working?? Not flashing recovery though

OTA softbricked? the device of my friend
Although the bootloader is unlocked, I was able to flash new firmware with fastboot with succes!! The device is now booting 4.1.1 (10.4.2.20)again
So, I tried to flash TWRP through fastboot (it's still responding to fastboot), but that fails:
Code:
FAILED <remote: <InvalidState>>
Thinking it is because the bootloader is locked, installed unlocking tool. Run it, at the last step, where you have to click the -normally- bar with image of locked lock to unlock, I get the dreaded network error, more importantly: the lock image is UNlocked
What could be the case now?

n/m http://forum.xda-developers.com/showthread.php?t=2037266
fastboot is available, flashing is not

How to restore the encrypted bootloader?

hi guys, i've unlocked the bootloader with the dc-unlocker2client , And i want to go back to the original boot loader, i've tried to re flash the 137 and eve the 129 chinese rom but the annoying message on boot startup still exist..
so how to go back?

youre mixing up two things: the bootloader and the boot image
the former (bootloader) you unlock via fastboot and the unlock code that you read out via dc-unlocker. this is the reason why u receive the message at bootup and u can relock the bootloader via fastboot as well (fastboot oem relock XXXXXXXXX)
the latter is the boot image that u have to decrypt in order to be able to root properly and not be stuck in a boot loop. the boot.img is reflashed once u install a new stock firmware. but the bootloader lock state is untouched by this, thats why u manually have to relock it using fastboot!
cheers

thats weird.. i entered the fastboot mode
and opened the minimal adb - and wrote the command : fastboot oem relock XXXXXXXXX
the XXXX is my unlock code from the dc software i guess..
and its says : failed : stat not match
so.. how can i lock it again?

http://postimg.org/image/50dz3y0vf/

U should flash stock recovery first...then relock your bootloader

Help with logo.bin

Hello. So I've restored my old XT1032 to 5.1 stock and locked the bootloader again but I'm still getting the unlocked bootloader warning message when booting. I've tried to reflash the logo.bin but that didn't work.
Any ideas?
Thanks

flash the logo.bin from here:
http://forum.xda-developers.com/showthread.php?t=2548530
and then it will go away. Motorola did this beacuse the bootloader was unlocked before and relock it doesn't bring back the original boot logo. In bootloader mode you can see that you have now STATUS CODE: 2 instead of 0 when never was unlocked.

Flashing firmwire

Hi, I'm trying to flash firmware on moto g3 but when I write command "fastboot flash partition gpt.bin" it tells me "error: cannot found 'gpt.bin' ". I have got all files thats are necessary. What is wrong with my phone? Some one had this problem? Someone can help me?

I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?

Theheero said:
I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?
Click to expand...
Click to collapse
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.

acejavelin said:
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.
Click to expand...
Click to collapse
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?

Theheero said:
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?
Click to expand...
Click to collapse
Don't do it. Download the factory images for your specific device here https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639, and flash them.

Has logo.bin changed structure? Still get an unlocked warning

I just flashed a custom logo.bin to my Moto G9+ (using "fastboot flash logo logo.bin" and logo_a & logo_b). My custom image replaced logo_boot, logo_unlocked, yellow, red & orange.
When I boot the phone I see my image for a second, then the unlocked warning for ~10 seconds, then my image again for a further few seconds. I've checked that the logo.bin entries I've mentioned were all changed to my image.
Why does the unlocked warning still show up and what can I do about it?
Thanks.