Database Develop

Unable to Relock Bootloader and SIM card NOT READING error on MOTO X 2014 AT&T XT1097

Unable to Relock Bootloader and SIM card NOT READING error on MOTO X 2014 AT&T XT1097
i have unlocked bootloader on my moto X 2014 (canada variant) XT1097 and status code : 3
after flashing stock roms & many attempts to relock the bootloader but no luck to lock my phone bootloader
with this cmd in the fastboot mode.
{
fastboot oem lock
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
} (this statment also shows to flash any signed img (i dont know what it means))
as well as while i am flashing rom i got this errors
{
hab check failed for recovery
hab check failed for boot
} in pink colour
my phone is unable to read sim card (NO Network)
can anyone suggest any solution.

maninder.email said:
i have unlocked bootloader on my moto X 2014 (canada variant) XT1097 and status code : 3
after flashing stock roms & many attempts to relock the bootloader but no luck to lock my phone bootloader
with this cmd in the fastboot mode.
{
fastboot oem lock
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
} (this statment also shows to flash any signed img (i dont know what it means))
as well as while i am flashing rom i got this errors
{
hab check failed for recovery
hab check failed for boot
} in pink colour
my phone is unable to read sim card (NO Network)
can anyone suggest any solution.
Click to expand...
Click to collapse
If you're using your ATT XT1097 with a Canadian carrier, then you need to flash the VICTARA_RETCA_XT1097_6.0 firmware:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
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
Every single line, so that ALL files are stock. There's no advantage to relocking the bootloader, you won't get warranty back. But try relocking it after flashing the full factory firmware.

Gus Ghanem said:
If you're using your ATT XT1097 with a Canadian carrier, then you need to flash the VICTARA_RETCA_XT1097_6.0 firmware:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
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
Every single line, so that ALL files are stock. There's no advantage to relocking the bootloader, you won't get warranty back. But try relocking it after flashing the full factory firmware.
Click to expand...
Click to collapse
yahoo! Phone is able to read my Wind sim card and i am able to make phone calls.
Thanks Gus Ghanem
I really appreciate your help
i followed your instructions.

maninder.email said:
yahoo! Phone is able to read my Wind sim card and i am able to make phone calls.
Thanks Gus Ghanem
I really appreciate your help
i followed your instructions.
Click to expand...
Click to collapse
You're welcome! I'm glad it's working

System status back to Official

I have tried to flash Stock rom and relock bootloader already but System Status still : Modified
Anyone can help me?

When I had a Moto G4 Plus, when I upgraded via OTA (from 6.0 to 7.0) the status changes, I do not know if the Moto X4 will do the same
How do you block the bootloader? can you teach me? I already want to block it and I can not without mentioning that at the beginning I get the message of this one and I have to press the power button to advance :/

You need official signed stock images to flash which have not been released by Lenovo. There's no return from unlocking the bootloader currently.

Neffy27 said:
You need official signed stock images to flash which have not been released by Lenovo. There's no return from unlocking the bootloader currently.
Click to expand...
Click to collapse
That means i need to blink it to Lenovo shop to flash back to original signed rom right?

lol right

Signed ROMs: https://androidfilehost.com/?w=files&flid=229118
Payton_ = Retail
Payton_Fi = Android ONE
Payton_AMZ = AMAZON
THIS WILL WIPE ALL YOUR DATA AND THE SECURITY PATCH MUST TO BE THE SAME AS YOU HAVE NOW OR ABOVE for example Retail 8.1 - 1 April Security Patch.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
If your bootloader is already block you can skip this commands:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
instand of they you can use:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fasboot reboot

lucasbitencourt said:
Signed ROMs:
Payton_ = Retail
Payton_Fi = Android ONE
Payton_AMZ = AMAZON
THIS WILL WIPE ALL YOUR DATA AND THE SECURITY PATCH MUST TO BE THE SAME AS YOU HAVE NOW OR ABOVE for example Retail 8.1 - 1 April Security Patch.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
If your bootloader is already block you can skip this commands:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
instand of they you can use:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fasboot reboot
Click to expand...
Click to collapse
Hi! I have Moto X4 XT1900-7 4/64 (Europe)
I have downloaded Retail ROM version, and did everything like you describe for devices with unlocked bootloader. And I have a problem. During the start i see "Your device has loaded a different operating system. Visit this link on another device: motorola [dot] com [slash] unlockbootloader…". Then device starts, but I can't connect it to my laptop via USB (I have also tried with another PC). It's charging, but there is no notification to choose connection mode. In settings the option "USB Not connected" is grey. Do you have any ideas?

MNelaer said:
Hi! I have Moto X4 XT1900-7 4/64 (Europe)
I have downloaded Retail ROM version, and did everything like you describe for devices with unlocked bootloader. And I have a problem. During the start i see "Your device has loaded a different operating system. Visit this link on another device: motorola [dot] com [slash] unlockbootloader…". Then device starts, but I can't connect it to my laptop via USB (I have also tried with another PC). It's charging, but there is no notification to choose connection mode. In settings the option "USB Not connected" is grey. Do you have any ideas?
Click to expand...
Click to collapse
On 8.1 there's a bug in April Security Patch the USB only works with de lockscreen security disabled. See if the June update is available for you, then update, if not, go to developer's options and check the option OEM Unlocker then flash this:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
if oem lock doesn't works change to: fastboot flashing lock or oem relock
Some phones only clears the massage after a update.

It works properly only via mfastboot for me, don't really know why. Before you answered I have boot-looped my device (with no possibility to run adb/fastboot commands, ya). But mfastboot helped me to boot 8.0 Retail ROM from the link you mentioned before and then to lock Moto X OEM.

lucasbitencourt said:
Signed ROMs: https://androidfilehost.com/?w=files&flid=229118
Click to expand...
Click to collapse
Those are not signed or he wouldn't get that message. You can flash all the available copied payton ROMs all day manually to get the phone working.
@MNelaer - Go here to get your phone working again.

Neffy27 said:
Those are not signed or he wouldn't get that message. You can flash all the available copied payton ROMs all day manually to get the phone working.
@MNelaer - Go here to get your phone working again.
Click to expand...
Click to collapse
This ROMs are signed, and we can flash without unlock de bootloader.

Downgrade Pie To Oreo ?

I regret my English but I need your help update my X4 Oreo 8.1 Patch November to Pie 9.0, I have a da Fiio Q1 mark II which worked perfectly in Oreo 8.1 through OTG, after updating this stopped working normally , it connects and disconnects only until the smartphone restarts, is there a way to go back to oreo? It is not Fi project

Yes, the way is:
1. unlock bootloader (this erase all user data / internal storage)
2. flash Oreo full fastboot package

Comby_sk said:
2. flash Oreo full fastboot package
Click to expand...
Click to collapse
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.

jbaumert said:
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.
Click to expand...
Click to collapse
Flashing full fastboot package with correct script and unlocked bootloader doing this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
I downgraded many times my X4 from Pie to Nougat or from Pie to Oreo.

Comby_sk can I do it with this scribt?!
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot flash modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot
RAW Paste Data

@tomtom_38 yes, you do.

many thanks

Can I Upgrade my XT1805 to Oreo ?

My XT1805 is rooted and bootloader unlocked and stuck on NPSS26.116-61-5.
Is there any way to upgrade this to stock Oreo ?

BUMP
I don't need Root so just want to do anything to get Oreo installed

championc said:
My XT1805 is rooted and bootloader unlocked and stuck on NPSS26.116-61-5.
Is there any way to upgrade this to stock Oreo ?
Click to expand...
Click to collapse
You can update via fasboot

diegomartinezlovey said:
You can update via fasboot
Click to expand...
Click to collapse
Where can I find the relevant firmware and full procedure to use please ?

championc said:
Where can I find the relevant firmware and full procedure to use please ?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.10
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 reboot

Can you relock the bootloader?

Title. Alternatively, can you still receive OTAs with an unlocked bootloader if the firmware is stock?
Currently the issue is that the firmware files you can find online throw a bad key error on the boot and recovery images, so it's not possible to lock the bootloader that way. Motorola also doesn't provide proper OTA packages to download (I asked the support) and an emergency recovery tool like Samsung Kies doesn't seem to exist for Moto.
What are my options here? I want to give the device to a relative and need everything to work.

I did it with this code on fastboot folder (Minimal ADB & Fastboot Portable 1.4.3) with the last firmware RETAIL PPSS29.55-37-4 and then use RSD Lite to re-flash the firmware, it worked for me. Do it under your own risk.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot oem lock
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin

Thank you, that worked perfectly!

HeavyHDx said:
Thank you, that worked perfectly!
Click to expand...
Click to collapse
@HeavyHDx I highly recommend to re-flash the firmware on RSD Lite (if you haven't did it) because it could be some errors with the NON-HLOS.bin, like no sound when calling, at least that happened with me.

How could it worked perfectly since some commands are non-sense??
The Moto g6 is a A-only device... So all commands for XXX_other.img or "_b.img" won't be executed.
The second thing is that this device has a "adspso.bin" file for partition "dsp". But the command here will flash a "dspso.bin" file.
What about /recovery???