This is made for the XT1900-02 which is the 64gb/4gb dual sim variant sold internationally
Please do not flash this on any other variant you risk bricking your device
Install instructions:
Download Moto X4 Stock Firmware from below.
Make sure you have adb/fastboot drivers on your pc
Now extract stock firmware into a folder
Now, turn off your device and boot into bootloader by pressing volume down button and power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Downloads:
PAYTON_PPWS29.69-26-4_9_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
https://www.androidfilehost.com/?fid=11410963190603915881
PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
https://www.androidfilehost.com/?fid=1322778262903985819
Credits to @lohanbarth for the install instructions
Thanks, i was waiting for this.
Is this is signed Motorola official firmware or custom firmware??
No, it is not.
viswaA5 said:
Is this is signed Motorola official firmware or custom firmware??
Click to expand...
Click to collapse
This is not an official Motorola Recovery Image, you will have a warning that this is a wrong software when you boot up with your re-lock bootloader. And also no future OTA update.
khanhlinh said:
This is not an official Motorola Recovery Image, you will have a warning that this is a wrong software when you boot up with your re-lock bootloader. And also no future OTA update.
Click to expand...
Click to collapse
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
ding17 said:
Is there any way around this?
Click to expand...
Click to collapse
No unless Motorola releases their signed images which will most likely never happen. This has been said many times throughout these forums and it's in the FAQs thread.
ding17 said:
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
Click to expand...
Click to collapse
Hello give your Moto Rom link pls
Battery faulty
ding17 said:
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
Click to expand...
Click to collapse
I am sure Moto behind this, my phone stuck at 50%, but it's show 100%, that's why it drain super fast.
Anyone know how to changes fonts on stock firmware pls help or guide me how to do that
mujju85 said:
Anyone know how to changes fonts on stock firmware pls help or guide me how to do that
Click to expand...
Click to collapse
Not without rooting your phone. If you do not plan on rooting your stock install, the only thing you really can do is change the font display size.
Magisk has several modules that will allow you to change your system default font. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
**EDIT**
Found my issue. Been a while since I've been in the rooting game... mfastboot is the actual command. Once I got mfastboot everything worked perfectly
**EDIT**
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
fastboot flash fsg fsg.mbn
Sending 'fsg__a' (5508 KB) OKAY [ 0.154s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
Finished. Total time: 0.161s
pantoner said:
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
Click to expand...
Click to collapse
I had this problem when I used the latest android SDK tools. If you use the linux-fastboot or mfastboot (Windows) Motorola utility it will just work. Alternatively, try and find an older version of the ADB/Fastboot tools.
There is nothing wrong with the downloaded ROM.
Update :
It is compatible as per the posts in other threads
.....................................
My device is XT1900-2 6GB Ram variant. Is this firmware compatible with my device?
Software channel is Retin and below are current firmware software parameters.
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-3-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.306.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M660_7036.16.01.69.02R PAYTON_APACDSDS
(bootloader) version-baseband[1]: _CUST
Any Solution for such kind of issue?
Facing the same issue with my mobile any solution for this?
pantoner said:
**EDIT**
Found my issue. Been a while since I've been in the rooting game... mfastboot is the actual command. Once I got mfastboot everything worked perfectly
**EDIT**
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
fastboot flash fsg fsg.mbn
Sending 'fsg__a' (5508 KB) OKAY [ 0.154s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
Finished. Total time: 0.161s
Click to expand...
Click to collapse
Sir i locked the oem after all commands and now i am in a boot loop....moto logo....what to do
Can you provide Android Pie Firmware for XT1900-02? I have unlocked bootloader so there is no other way to update!
I have added the Pie firmware to the OP
PAYTON_PPWS29.69-26-4_9_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
Thanks for this. This might be a noob question, but how can i check if i have pie firmware on mine? I flashed a pie ROM the first day i got the phone but i didn't flash any firmware on it.. Everything works fine as far as i can say.... (Battery drains super fast tho)
Hello,
I have XT1900-02 (stock rom unrooted and bootloader locked) I only want to flash the modem or baseband file instead of the entire rom as i am having issues with Volte(No incoming calls) service center flashed my device but it didn't help.
Please help me with the steps or commands that i need to use to do
Unlocking Bootloader, Rooting, Etc
Hi, I have recently purchased the XT1900-2, 6GB, 64 GB model and have updated to 9.0 using the procedure in this thread. I would like to know what are the possibilities of rooting, unlocking bootloader without losing warranty?
Related
hello I try everything and cant make my phone to work, I'm asking to somebody if can help me to upload a moto e 2nd gen. XT1526 SPRINT Backup, I made my backup and save it in a different sd card but for some reason, it wipe it and delete everything on the memory
Are you asking for someone to link you to the ROM you need? I'm not following you.
Mdkcheatz said:
Are you asking for someone to link you to the ROM you need? I'm not following you.
Click to expand...
Click to collapse
sorry, I didn't be to explicit, yea Im asking to somebody to link me a rom or a nandroid backup or a twrp backup of the moto e tx1526 cdma sprint, because I already try almost all of the roms and non of them still working for me, and I delete accidently my own backup.
or probably still not release some sprint rom's?
I didn't find your specific ROM yet but there were XT1526 ROMs which may help from this note I made for myself back when I needed mine... Its possible that a similar ROM may work for you. Just make sure you are using GSM version if you are GSM and vice versa: Installing incompatible firmware can lead to hard bricking.
Do not rely on these links to last. Some are already down.
RETUS = Retail US
TMO = T-Mobile
This is the only source of leaked Moto E Firmware. Some Links are down. The XT1527 TMO (T-Mobile subsidy) version works but it may lock only to Tmobile. I assume you can flash to any of those carriers to inherit their subsidy.
FileFactory
Flashing a compatible ROM will not:
Mess up Fastboot
Lock bootloader (it is possible to lock it, however, locking* the bootloader could screw up your last chance of restore.
Flash a compatible ROM will:
Overwrite Recovery (easily reflashed)
Remove Root (easily reflash)
Reset everything to near factory settings.
Fix Baseband
To reflash ROM:
I've put together some commands that are needed to flash the rom files. Copy and save as [any_file_name].bat
fastboot oem fb_mode_set
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
Save .bat file to the same directory as the rom files.
Have Fastboot installed.
Have Moto Drivers installed.
Boot Moto into Fastboot mode
Load terminal and confirm connection to device. (Type "fastboot devices")
$cd into a folder with extracted .xml files.
In terminal, type [name_you_gave_file].bat and it should automatically start flashing the rom files.
Reboot phone and it should be* restored.
---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
Sorry the link didn't parse:
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Try one of these three XT1526 ROMS (actually 2: the boost subsidy version won't help you obviously)
Good luck!
luzbel3821 said:
sorry, I didn't be to explicit, yea Im asking to somebody to link me a rom or a nandroid backup or a twrp backup of the moto e tx1526 cdma sprint, because I already try almost all of the roms and non of them still working for me, and I delete accidently my own backup.
or probably still not release some sprint rom's?
Click to expand...
Click to collapse
Hi, did you manage to solve your issue? I am also in the same boat, looking forsprint moto e stock 5.1 firmware or comatible. Didyou have any success?
dreckgos said:
Hi, did you manage to solve your issue? I am also in the same boat, looking forsprint moto e stock 5.1 firmware or comatible. Didyou have any success?
Click to expand...
Click to collapse
rom for sprint didn't come out yet, but this rom work perfect on sprint network http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
its on the last post by Mdkcheatz, just follow the instruccions
luzbel3821 said:
rom for sprint didn't come out yet, but this rom work perfect on sprint network http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
its on the last post by Mdkcheatz, just follow the instruccions
Click to expand...
Click to collapse
Hm, I tried the 5.1 boost ROM from the same site, but I got a bootloop if only flashing system and hang on boot if following the full process....
dreckgos said:
Hm, I tried the 5.1 boost ROM from the same site, but I got a bootloop if only flashing system and hang on boot if following the full process....
Click to expand...
Click to collapse
Huh, I tried again and this time it worked. The problem was that previously I used a script to flash and it did not include a fastboot invocation for the last piece of the system image.
Yea that does to me too, but don't use BOOST 5.1 instead use Boost 5.0.2 and once you started it will ask you on your phone to OTA upgrade
dreckgos said:
Huh, I tried again and this time it worked. The problem was that previously I used a script to flash and it did not include a fastboot invocation for the last piece of the system image.
Click to expand...
Click to collapse
but no luck for me getting this message, any solution?
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
alshanu said:
but no luck for me getting this message, any solution?
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
Click to expand...
Click to collapse
Did you make sure to unlock your bootloader?
Also, you shouldn't bump a year-old topic.
xtermmin said:
Did you make sure to unlock your bootloader?
Also, you shouldn't bump a year-old topic.
Click to expand...
Click to collapse
Ya I gave up. Thank you
Hi,
I was trying to flash stock rom to my Moto E Indian version. It was running Cm 12 but suddenly it stopped detecting sim card. so I used this script to flash the stock firmware
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
pause
mfastboot.exe reboot
but flash wasnt successful and its now stuck at recovery loop. If I try to flash any custom rom from recovery it says unable to mound data and system. Tried everything I know but doesnt help.
when I flash the above script it shows CM boot logo and gets stuck there
Using this stock firmware RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC
C:\MotoTool\ADB>"Retail+lock.bat"
C:\MotoTool\ADB>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.089s]
finished. total time: 0.092s
C:\MotoTool\ADB>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.577s
C:\MotoTool\ADB>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.099s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.574s
C:\MotoTool\ADB>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.233s
C:\MotoTool\ADB>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.101s
C:\MotoTool\ADB>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 1.757s]
finished. total time: 2.161s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (243072 KB)...
OKAY [ 7.676s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.348s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257254 KB)...
OKAY [ 8.128s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.197s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (201709 KB)...
OKAY [ 6.381s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.447s
C:\MotoTool\ADB>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.507s]
writing 'modem'...
OKAY [ 4.589s]
finished. total time: 6.101s
C:\MotoTool\ADB>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\MotoTool\ADB>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.025s
C:\MotoTool\ADB>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.106s]
writing 'fsg'...
OKAY [ 0.127s]
finished. total time: 0.237s
C:\MotoTool\ADB>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.369s
C:\MotoTool\ADB>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.415s]
finished. total time: 1.419s
C:\MotoTool\ADB>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.043s]
finished. total time: 0.046s
C:\MotoTool\ADB>pause
Press any key to continue . . .
C:\MotoTool\ADB>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
C:\MotoTool\ADB>
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
rizzee said:
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
Click to expand...
Click to collapse
Try the 5.1 factory images
please provide me the link of 5.1 if you have.
Here you go : Link
rizzee said:
please provide me the link of 5.1 if you have.
Click to expand...
Click to collapse
Why u all gave lock command at first?
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
rizzee said:
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
Click to expand...
Click to collapse
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
nilanko said:
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
Click to expand...
Click to collapse
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
rizzee said:
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
Click to expand...
Click to collapse
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
nilanko said:
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
Click to expand...
Click to collapse
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Click to expand...
Click to collapse
I'm confused which one to download and install, there are many different versions available.
rizzee said:
I'm confused which one to download and install, there are many different versions available.
Click to expand...
Click to collapse
I made a correctin to the previous post
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
nilanko said:
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
Click to expand...
Click to collapse
Maybe you're right... He does have the 5.0.2 bootloader... So, flashing the 5.1 gpt.bin won't do any harm.
At least that is what I think
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Click to expand...
Click to collapse
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
rizzee said:
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
Click to expand...
Click to collapse
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Rohitagni said:
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Click to expand...
Click to collapse
failed bootloader preflash validation failed
rizzee said:
failed bootloader preflash validation failed
Click to expand...
Click to collapse
It won't work unless you unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2753110
Hi guys, a friend of mine had a problem with his Moto E XT1021 and I'm trying to help him. I'm stuck on this screen and i don't know what to do:
AP Fastboot Flash Mode (S)
...
Battery OK
Devis is LOCKED. Status Code: 0
Connect USB Data Cable
...
failet to validate system image
Fastboot Reason: Fall-through from not charger-boot mode
He told me that he started to have problems after updating his phone. Whatever I do, I get:
failed to validate system image
Boot up failed
I tried to unlock the bootloader, but when I type fastboot oem get_unlock_data I get this error:
(bootloader) Could not get unlock data! OKAY [ 0.166s] finished. total time: 0.173s
...any suggestions? Thanks.
Anyone who can help me?
Here's the link of stock firmware, flash it (guide included) :
http://forum.xda-developers.com/showthread.php?t=2755857
It doesn't require unlocked bootloader.
I tried but I get this error when i type the flash boot command:
C:\...\XT1021_CONDOR_RETEU_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.398s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.463s
The smartphone shows: "hab check failed for boot"
...it is possible that I downloaded the wrong version ?
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Yes, they returned okay. When I type mfastboot flash boot boot.img, I get "failed".
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Why are you assuming that I'm using the Indian version ? The phone was purchased from Amazon in Italy and I was trying to flash the stock retail EU 5.1
I tried the 4. KitKat but i got some error about downgrading.
What you actually did, before this problem was caused?
Were you using the same rom(that you're trying flash) ??
It's not my phone, but he said that after an updating (was a normal update. I suppose it was the 5.1 update) he started receiving this problem.
Can you help me?
Okay skip the boot.img step and execute the rest of the commands.
Okay I will try
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
rafapp said:
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
Click to expand...
Click to collapse
That's not done dude.
It shouldn't have fixed your device the main part was this
mfastboot.exe flash system system.img_sparsechunk*
and that returned Failed too. Since the bootloader isn't unlocked so flashing custom recovery isn't possible too.
There's no other way I can see but device is bricked.
So is it impossibile to unbrick it?
rafapp said:
So is it impossibile to unbrick it?
Click to expand...
Click to collapse
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
-z3r0- said:
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
Click to expand...
Click to collapse
I tried and it didn't work. All the commands failed.
hello,
i follwd the procedure u said but all are unsuccssfull and even i tried by skipping the boot.img step and executed the rest of the commands.
but i found
prevalidtion failed for
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
-z3r0- said:
Okay skip the boot.img step and execute the rest of the commands.
Click to expand...
Click to collapse
Hi, did this get resolved? I have the same problem. My XT1021 (UK Tesco variant) had been switched off for some time. When I turned back on it was looping in fastboot. Could not even turn it off. I tried flashing with a number of stock ROMs using usb to PC and mfastboot commands. Many stock ROMS caused errors on various commands, the 5.1 UK Tesco variant seemed to work perfectly - no errors displayed on phone or PC. But hone now boots too fastboot and shows the failed to validate system image error. Battery is apparently OK .. is something else likely to be toasted?
Its an old phone but would be good for my son as he starts senior school until he has proved he won't lose it
Similar Problem with Moto XT1225
Hi there, I've similar problem with XT1225.
I tried to lock the oem and it is locked with status code 2. I forgot to enable OEM unlocking from the Developer options and now I have no way to boot my device it always end up loading into fastboot mode.
Any help would be appreciated.
As the topic
Wysłane z mojego XT1650 przy użyciu Tapatalka
[email protected] said:
As the topic
Wysłane z mojego XT1650 przy użyciu Tapatalka
Click to expand...
Click to collapse
There's probably guides on it around here, maybe in the general section.
Curious why though? And if the Z is like the X, it won't return to "locked" state, it will go to "relocked." I don't know that for a fact, but that's how the X is. So it won't help for warranty, plus they already know you unlocked if you used their site. And not sure apps looking for a locked bootloader will accept "relocked." But that's purely a guess.
BTW, of its like other devices, you lock it using fastboot.
With command "fastboot oem lock"
the instruction for lock the boot of moto z
Darth said:
There's probably guides on it around here, maybe in the general section.
Curious why though? And if the Z is like the X, it won't return to "locked" state, it will go to "relocked." I don't know that for a fact, but that's how the X is. So it won't help for warranty, plus they already know you unlocked if you used their site. And not sure apps looking for a locked bootloader will accept "relocked." But that's purely a guess.
BTW, of its like other devices, you lock it using fastboot.
With command "fastboot oem lock"
Click to expand...
Click to collapse
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
next you have to rund the next comand
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot oem lock
wait and thats all your phone restart with your boot locked
Made a batch file (edited from evogp autoscript file for moto z play) for relocking. worked with my flashing 25.86--17-3-4 on my retus. Make sure you update it with the amount of sparsechunks you have
phone shows as oem_locked but with modified software (probably wrong firmware or something on mine since i manually flash nougat on it from other software channels)
https://drive.google.com/open?id=0By5BhZqSOZAESk1PYXZ3dnZFYXM
taphius said:
Made a batch file (edited from evogp autoscript file for moto z play) for relocking. worked with my flashing 25.86--17-3-4 on my retus. Make sure you update it with the amount of sparsechunks you have
phone shows as oem_locked but with modified software (probably wrong firmware or something on mine since i manually flash nougat on it from other software channels)
https://drive.google.com/open?id=0By5BhZqSOZAESk1PYXZ3dnZFYXM
Click to expand...
Click to collapse
If I understand you correctly, this flashes the original firmware. How did you get your modified ROM on the phone then?
7bob said:
If I understand you correctly, this flashes the original firmware. How did you get your modified ROM on the phone then?
Click to expand...
Click to collapse
It flashes whatever firmware is in the folder with it. I'm on a stock room but bootloader shows as custom software. Probably due to flashing retmx or retbr before
That doesn't seem to work, I can't even flash the original boot.img:
Code:
~ $ fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.110s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.598s
boot.img and recovery.img are not signed by Motorola. So there is atm no way to (re)lock the Bootloader
kaliberx said:
boot.img and recovery.img are not signed by Motorola. So there is atm no way to (re)lock the Bootloader
Click to expand...
Click to collapse
I used the script to relock my own bootloader.
He looks like he is trying to flash an older boot image. Try a newer one.
I'll throw what exactly I did in a few once I get time, I updated to 25.86-17-3-4 flashing everything from evogps script first, then ran my relock
used this to flash everything per evogps script
@Echo off
ECHO.
ECHO. Script by @evogp ...
ECHO.
ECHO.
ECHO. Flashing Bootloader and more...
ECHO.
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
ECHO.
ECHO. Flashing System ...
ECHO.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system system.img_sparsechunk.13
mfastboot flash system system.img_sparsechunk.14
mfastboot flash system system.img_sparsechunk.15
mfastboot flash system system.img_sparsechunk.16
mfastboot flash oem oem.img
ECHO.
ECHO. Wipe Cache and Data ...
ECHO.
mfastboot erase carrier
mfastboot erase cache
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
ECHO.
ECHO. Installation Complete!
ECHO.
PAUSE
mfastboot reboot
EXIT /b 0
then used my relock script after to lock bootloader.
Again, and it is said many Times here in the Moto Z Forums :
impossible to lock, because firmware-images are all NOT singed by Motorola, to be exact : boot.img and recovery.img.
https://mobilesupport.lenovo.com/us/en/solution/MS91987
Well and these signed Images, arent in the Wild. Only Lenovo/Motorola has them, here :
https://motorola-global-portal.cust...edirect/standalone/bootloader/recovery-images
but only for some Devices, and there is no Moto Z yet in the List. So the only Way is to send it in to get it relocked correctly, and they maybe will charge you for the Process/Service.
kaliberx said:
Again, and it is said many Times here in the Moto Z Forums :
impossible to lock, because firmware-images are all NOT singed by Motorola, to be exact : boot.img and recovery.img.
https://mobilesupport.lenovo.com/us/en/solution/MS91987
Well and these signed Images, arent in the Wild. Only Lenovo/Motorola has them, here :
https://motorola-global-portal.cust...edirect/standalone/bootloader/recovery-images
but only for some Devices, and there is no Moto Z yet in the List. So the only Way is to send it in to get it relocked correctly, and they maybe will charge you for the Process/Service.
Click to expand...
Click to collapse
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
taphius said:
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
Click to expand...
Click to collapse
And the current status of phone
taphius said:
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
Click to expand...
Click to collapse
Well I'll be damned... Cool
OK Taphus then do go a bit deeper into your Specs :
What was the Devices Retxx before you unlocked, and which firmware RetXX used you to relock the bootloader ?
I was RETEU (Germany) before, but because there is only a 6.01 Image, it isnt possible to flash with Nougat Bootloader.
SO i used and tried RETBR, RETMX and RETLA, got all onto the latest Security Patchlevel, but i didnt got the Bootloader locked at all.
And here Moto says that only they can do it.
kaliberx said:
OK Taphus then do go a bit deeper into your Specs :
What was the Devices Retxx before you unlocked, and which firmware RetXX used you to relock the bootloader ?
I was RETEU (Germany) before, but because there is only a 6.01 Image, it isnt possible to flash with Nougat Bootloader.
SO i used and tried RETBR, RETMX and RETLA, got all onto the latest Security Patchlevel, but i didnt got the Bootloader locked at all.
And here Moto says that only they can do it.
Click to expand...
Click to collapse
retus, flashed XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in the video.
I flashed retmx/retca or whatever was the way to get nougat on the US model before it released for us as well.
taphius said:
retus, flashed XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in the video.
I flashed retmx/retca or whatever was the way to get nougat on the US model before it released for us as well.
Click to expand...
Click to collapse
Yes and thats it : The Image checks the Device, if it's on the same Retail-Channel (Thats why you're on the RetEU-Software-Channel, even if you flash a RetMX Image).
So if the Retail-Channel of the Image differs from the Channel on the Device : Bad Key, GPT wont flash and Bootloader Lock not possible, until you send it in to Motorola or Motorola releases a Image for your Channel.
So i have to correct myself : Images are signed, but only for the RET-Channel of your Device.
Could you please extract and post your bootloader.img? I am in version 91.05 and it does not allow boot.img to flash as the boot.img has bad key or no key. I am able to flash outside fastboot oem lock command, but if I issue a oem lock command, my version of bootloader is not allowing me to flash boot image.
edit: I got the bootloader but everything else flashes but the gpt bin, and hence I am unable to flash boot.img..
anilisanil said:
Could you please extract and post your bootloader.img? I am in version 91.05 and it does not allow boot.img to flash as the boot.img has bad key or no key. I am able to flash outside fastboot oem lock command, but if I issue a oem lock command, my version of bootloader is not allowing me to flash boot image.
edit: I got the bootloader but everything else flashes but the gpt bin, and hence I am unable to flash boot.img..
Click to expand...
Click to collapse
my boot img was from the firmware file i used.
I re-locked it using this method , it worked but after getting it up and running I did an OTA update and bricked my device. Once I get it back on , can I still use fastboot to load the ROM?
guys, help please, where do I get signed boot image ?
Hi,
I unlocked my bootloader and installed LineageOS on my Moto Z.
For security reasons, I wanted to re-lock my bootloader using
Code:
fastboot oem lock
. When doing so, I got this warning:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
I was wondering if locking the bootloader would really wipe all user data. Has anyone tried and can confirm that?
Thanks,
Bob
Yes it will wipe all of your data.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
Yes it will wipe all of your data.
Click to expand...
Click to collapse
Thank you for your quick reply. Did you try it?
And is there some other way to lock the bootloader, without wiping data?
7bob said:
Thank you for your quick reply. Did you try it?
And is there some other way to lock the bootloader, without wiping data?
Click to expand...
Click to collapse
Yes, I have unlocked multiple bootloaders [emoji6]
No, there is no other way as of now.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
Yes, I have unlocked multiple bootloaders [emoji6]
Click to expand...
Click to collapse
Just to make sure, I'm talking about LOCKING the bootloader, not unlocking!
7bob said:
Just to make sure, I'm talking about LOCKING the bootloader, not unlocking!
Click to expand...
Click to collapse
When you lock your bootloader, it should not effect your data at all. Whenever you unlock it, it will wipe your data.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
When you lock your bootloader, it should not effect your data at all. Whenever you unlock it, it will wipe your data.
Click to expand...
Click to collapse
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
7bob said:
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
Click to expand...
Click to collapse
Well... It looks like they changed it. It appears I misread your first post. As the warning states, it will likely wipe your data. Sorry about that.
Sent from my XT1650-03 using Tapatalk
7bob said:
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
Click to expand...
Click to collapse
Did you lock your bootloader yet?
Sent from my XT1650 using Tapatalk
how to lock of the bootloader
7bob said:
Hi,
I unlocked my bootloader and installed LineageOS on my Moto Z.
For security reasons, I wanted to re-lock my bootloader using
Code:
fastboot oem lock
. When doing so, I got this warning:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
I was wondering if locking the bootloader would really wipe all user data. Has anyone tried and can confirm that?
Thanks,
Bob
Click to expand...
Click to collapse
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
next you have to rund the next comand
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot oem lock
wait and thats all your phone restart with your boot locked
PiousInquisitor said:
Did you lock your bootloader yet?
Click to expand...
Click to collapse
No.
oxido_pank said:
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
Click to expand...
Click to collapse
Thanks for the hints, but will that process wipe user data?
7bob said:
No.
Thanks for the hints, but will that process wipe user data?
Click to expand...
Click to collapse
Yeah because you make a flash of system
I Ever Say make a backup of the files that you need first
Next of flash restore all files and this all, but before make a hard reset of your phone
Nice day
I tried today, but I didn't succeed:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.001s]
finished. total time: 0.001s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
finished. total time: 0.001s
So it seems that I cannot lock the bootloader by just executing fastboot oem lock two or three times. At least nothing was wiped after executing the commands.
7bob said:
I tried today, but I didn't succeed:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.001s]
finished. total time: 0.001s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
finished. total time: 0.001s
So it seems that I cannot lock the bootloader by just executing fastboot oem lock two or three times. At least nothing was wiped after executing the commands.
Click to expand...
Click to collapse
It doesn't let you lock the bootloader with a "bad" (i.e. non-stock) kernel or special partitions (e.g. oem) etc. But you're lucky: if it had relocked the bootloader in the current setup you could have easily 'bricked' your phone. Instead, it checks the signatures of various components first and only if it finds valid (stock-rom)-signatures, the lock comes back on.
If you still want to put the lock on, flash a valid stock-rom (version: like the most recent stock rom version your phone has ever seen, or newer. The bootloader doesn't allow downgrading).
You can do it all at once or step by step: gpt.bin first, then boot.img, recovery.img .... check puttin on the lock... Then it'll complain what else it wants you to flash next.. and so on. In the end, the bootloader will be locked and there is no immediate sign that it was ever unlocked.
benzinerwin said:
[...]
If you still want to put the lock on, flash a valid stock-rom (version: like the most recent stock rom version your phone has ever seen, or newer. The bootloader doesn't allow downgrading).
[...]
Click to expand...
Click to collapse
This would be the exact problem of most of the people here including myself, when trying to relock the bootloader.
I'm using the reteu variant of 1650-03 and am unable to get a stock ROM which is working with "fasboot oem lock begin".
Tried the "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT" as this seems to be te latest available. Unfortunately, this ROM seems to be too old, cause before unlocking/rooting etc I updated to latest april OTA...
Getting this:
Code:
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
sp4rt4n-i17 said:
This would be the exact problem of most of the people here including myself, when trying to relock the bootloader.
I'm using the reteu variant of 1650-03 and am unable to get a stock ROM which is working with "fasboot oem lock begin".
Tried the "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT" as this seems to be te latest available. Unfortunately, this ROM seems to be too old, cause before unlocking/rooting etc I updated to latest april OTA...
Getting this:
Code:
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, you're right, the error message clearly states that the NPL25.86-30 package is "too old"...
Which was the most recent version of Nougat you had on your phone?
What ist the current bootloader version (e.g. BL 91.05)?
benzinerwin said:
Ok, you're right, the error message clearly states that the NPL25.86-30 package is "too old"...
Which was the most recent version of Nougat you had on your phone?
What ist the current bootloader version (e.g. BL 91.05)?
Click to expand...
Click to collapse
Version was NPLS25.86-30-12 and BL is 91.05
sp4rt4n-i17 said:
Version was NPLS25.86-30-12 and BL is 91.05
Click to expand...
Click to collapse
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
benzinerwin said:
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
Click to expand...
Click to collapse
Flashing (via fastboot) the NPL25.86-30 without trying to relock the BL is no problem, did this several times (on other devices too )
You're right -like I wrote before - I've updated the device via OTA to latest april patch and I think that could cause the problem with relocking.
Other problem could be that one really need to use a (latest/Nougat) RETEU stock ROM for relocking RETEU device. I do not really know IF there is a diference between RETBR/RETMX and RETEU stock ROMs, as obviosly RETBR is working with my RETEU device and softwarechannel in "About device" is showing "reteu", but for relocking it could be necessary to use a stock RETEU ROM.
As I'm having TWRP installed, the loss of all data is no problem, and I will try what you suggested.
Final thought on this:
Solution could be just waiting for an up-to-date RETEU stock ROM with latest patchlevel or at least one which is above april (for now) and then try to relock BL with flashing this one.
I'm not in the situation that I really need a locked BL, but for research and in case of reselling the device, a solution for this problem would be great to know.
benzinerwin said:
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
Click to expand...
Click to collapse
It says ''still required signed boot.img''
Guess we don't have that yet :crying: