Database Develop

Removing warning bootloader unlocked

hi
i unlocked my bootloader and then i reflash thr original firmware and lock the bootloader succesfully
but the red warning of bootloader unlocked still is present every time i power on my moto x
some help?
thank u
( i tried with a original logo from Moto g but got a weird image with all blured lines)

There's a thread for this. It's not difficult to find.

nhizzat said:
There's a thread for this. It's not difficult to find.
Click to expand...
Click to collapse
/// solved
thank u

danger2u said:
/// solved
thank u
Click to expand...
Click to collapse
How did you solve it because no matter what I do the warning still there .... Thanks

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
danger2u said:
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy
Click to expand...
Click to collapse
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.

KidJoe said:
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
Click to expand...
Click to collapse
this was tested and working great on Moto x xt1053
is the same logo as before the unlocked bootloader
i just want to help
if my thread is not helping u can close it

[Q] (Bootloader) Failed to Erase partition Moto X 2014

I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.

vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
Click to expand...
Click to collapse
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked.
Click to expand...
Click to collapse
Just remember - you cannot downgrade the bootloader or the partition table!!

JulesJam said:
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Just remember - you cannot downgrade the bootloader or the partition table!!
Click to expand...
Click to collapse
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
What should I do now!! to get my phone back working!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
vignesh245 said:
What should I do now!! to get my phone back working!
Click to expand...
Click to collapse
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error.
Click to expand...
Click to collapse
gpt.bin is the partition table. If you were trying to flash a lower version partition table than your bootloader version, you cannot do that!!!
What is your bootloader version?

JulesJam said:
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
Is Motorola Device Manager installed on your computer? If not, install it:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then connect your phone in fastboot mode to your computer and run MDM and see if MDM can repair your phone.
Also - are you using version 2 of mfastboot to flash?

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
its 60.11

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
vignesh245 said:
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
Click to expand...
Click to collapse
OK let me know how it goes.

JulesJam said:
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
OK let me know how it goes.
Click to expand...
Click to collapse
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!

vignesh245 said:
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
Click to expand...
Click to collapse
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.

JulesJam said:
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
Click to expand...
Click to collapse
MDM did not fix my phone yes I am on Xt1095.
Thanks will try it and let you know

vignesh245 said:
MDM did not fix my phone yes I am on Xt1095.
Click to expand...
Click to collapse
OK, it is probably the custom recovery.

JulesJam said:
OK, it is probably the custom recovery.
Click to expand...
Click to collapse
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??

vignesh245 said:
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
Click to expand...
Click to collapse
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.

JulesJam said:
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
Click to expand...
Click to collapse
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||

vignesh245 said:
Can Motorola help my situation Mine is a pure edition?|
Click to expand...
Click to collapse
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.

JulesJam said:
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
Click to expand...
Click to collapse
Thanks a lot will contact motorola get my device replaced !.

vignesh245 said:
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
Click to expand...
Click to collapse
try using the "erase" command instead of format, I've found on my PC format works, but on Mac I need to use erase.

How to update Moto x (2nd Gen) To marshmallow

Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.

abdullah.ahsan11 said:
Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.
Click to expand...
Click to collapse
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..

Salik Iqbal said:
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..
Click to expand...
Click to collapse
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?

abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg

abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk

AGISCI said:
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am a noob . Can You please refer me a link/tutorial. I know about king root but sunshine is new to me
UPDATE:
I tried to root with kingroot and it failed

For links to relevant guides and tutorials see Tony Stark's sticky at the top of the general forum.

Hi Sir, Gus Ghanem, pleased take two minutes to help me
Gus Ghanem said:
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
Dear sir,
I have Verizon xt 1096 and want to install Android 6.0 from other variants like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMA, it should work on GSM networks 2G and UMTS 3G and LTE because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if it not necessary for upgrade process.
I will be very thankful to you.
Sorry I forgotten to mention, now I am on stock 5.1
Please also post some commands for fastboot. Thanks

abrarakram19 said:
Dear sir,
I have Version xt 1096 and want to install Android 6.0 from other Version like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMD, it should work on GSM networks 2G and 3G because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if is it not necessary for upgrade process.
I will be very thankful to you.
Click to expand...
Click to collapse
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much sir. I will try and I hope it will be done with your cooperation. If I felt any trouble I will beg some help from you. Thanks again.

Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
Or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any future updated firmware in same location MEGA from where I downloaded earlier.
And will I get any future OTA from Motorola i.e. 6.0.1 or higher and should I install that OTA if arrives, or not?
I will wait for your reply. Thank again

abrarakram19 said:
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any futur updated firmware in same location MEGA from where I downloaded earlier.
I will wait for your reply. Thank again
Click to expand...
Click to collapse
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.

Gus Ghanem said:
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.
Click to expand...
Click to collapse
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.

abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk

abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:10 PM ---------- Previous post was at 04:10 PM ----------
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
AGISCI said:
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow*
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.*
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please. Actually I hate this warnings screen and cautions every time when I power on my device and moto boot animation is terrible since I unlocked the bootloader.

verizon unlocked device.
sir i have an unlocked verizon moto x 2nd generation. can i get official motorola 6.0 update? is there any way?
thanks

Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks

abrarakram19 said:
Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks
Click to expand...
Click to collapse
For those who use verizon service there is this rom:
http://forum.xda-developers.com/showthread.php?t=3327345
Verizon cdma works in this custom stock rom.
Sent from my XT1095 using Tapatalk

Hi,
i just got brand new unused Moto X 2nd gen (2014), It has 4.4 Android on it, but OTA update does not want to work anymore, as of 15.1.2020.
It is unlocked XT1095.
I am looking for somebody to help me over Skype to update it to 5.1 and then to 6.0 - the way usual update would go, and would donate to you via PayPal.

bootloader relocked - stuck in fastboot mode

Hello everybody.
My brother bricked his xt1097 recently and, unable to fix it or find someone that could do it, he brought a new phone for him and gave me his old one.
The phone goes directly to fastboot mode, it says "Device is LOCKED" and "Software Status: Modified". I failed in finding an stock rom that I could successfully flash. Current flashed image fails to boot with "failed to validate system image". I cannot flash zip roms as the current recovery doesn't boot.
Bootloader reports version 61.00 (sha-130760b, 2016-08-24).
Cannot unlock also:
Code:
> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
I am with a very cheap phone right now (Nokia Lumia 525) I would get a really nicer phone if I resurect this Moto X.
Thanks :good:

Have you read this:
https://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------
HTML:
https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147

MAAZAHMEDSIDDIQEE said:
Have you read this:
https://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------
HTML:
https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
Yes, I did read. I still could not flash anything. Always fails with "hab check failed" when flashing boot, system or recovery.
I am not trying to flash anything other than boot, system or recovery to avoid further bricking.
Tried all three firmwares starting with VICTARA_RETBR_XT1097 that are in firmware.center
Now I am downloading RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC to try again
Thanks for your help

mrachid said:
Yes, I did read. I still could not flash anything. Always fails with "hab check failed" when flashing boot, system or recovery.
I am not trying to flash anything other than boot, system or recovery to avoid further bricking.
Tried all three firmwares starting with VICTARA_RETBR_XT1097 that are in firmware.center
Now I am downloading RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC to try again
Thanks for your help
Click to expand...
Click to collapse
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788

MAAZAHMEDSIDDIQEE said:
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788
Click to expand...
Click to collapse
Did not get what to do, exactly. The solution doesn't apply for this phone, I think.
---
I tried one more RETBR firmware without success. I am afraid that the bootloader currently installed is expecting a ROM other than the original one for this phone, checking for a ROM of another region or a ROM that I would not find.
Also status code of lock is 0. The phone bricked overnight, which makes me think an OTA did it.

MAAZAHMEDSIDDIQEE said:
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788
Click to expand...
Click to collapse
https://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081

[X527] No wifi, no sim detection / Can't complete setup assistant [SOLVED]

Hello friends!
After i tried to find a way to bypass LeEco login on the install of stock based ROM , i have bricked my phone (not really bricked, but i will tell you). On the first boot i cant complete the setup, because X527 dont detect my sim cards and shows no wifi networks (So i cant go to developer options and can not use a dial code).
After i have read a lot, im sure it was a problem with the efs or nvram (The last working boot shows no serial and no bootloader). But now im on Stock ROM and Stock Recovery and need an option to repair efs/nvram over fastboot or stock recovery, without changing anything in the phone itself.
Hope you guys can help me...

i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.

anjel05 said:
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
Click to expand...
Click to collapse
I can't install TWRP because i have to go to the developer options, but my phone can not start....

quasimodo88 said:
I can't install TWRP because i have to go to the developer options, but my phone can not start....
Click to expand...
Click to collapse
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default

anjel05 said:
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
Click to expand...
Click to collapse
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s

quasimodo88 said:
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
Click to expand...
Click to collapse
You have to do
U need to unlock first dude

DarknessKiller said:
You have to do
U need to unlock first dude
Click to expand...
Click to collapse
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s

quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you install the drivers you need?

anjel05 said:
Did you install the drivers you need?
Click to expand...
Click to collapse
Yes i did. My phone is shown under fastboot devices.

quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.

Dudeonyx said:
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Click to expand...
Click to collapse
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?

quasimodo88 said:
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
Click to expand...
Click to collapse
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.

Dudeonyx said:
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Click to expand...
Click to collapse
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.

quasimodo88 said:
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
Click to expand...
Click to collapse
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp

Dudeonyx said:
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Click to expand...
Click to collapse
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html

quasimodo88 said:
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
Click to expand...
Click to collapse
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now

Dudeonyx said:
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Click to expand...
Click to collapse
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?

quasimodo88 said:
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
Click to expand...
Click to collapse
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that

Dudeonyx said:
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Click to expand...
Click to collapse
Ok, i will try it now. Don't run away :fingers-crossed:

quasimodo88 said:
Ok, i will try it now. Don't run away :fingers-crossed:
Click to expand...
Click to collapse
Good luck, also I noticed that your issue isn't leeco account login but rather Google's factory reset protection. So if this fails you can search for ways to bypass google factory reset protection.