Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
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 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
Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
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 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
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.
I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.
Related
Here's The Video Tutorial on Downgrading Your Moto E from Android 5.0.2 to STOCK KitKat 4.4.4. Yes ! 4.4.4.
http://youtu.be/w7S5WmlPgrI
1. Download Stock 4.4.4
2. Download mfastboot.
3. Download ADB. ( Download Links are in video description)
Now flash Stock 4.4.4 using adb.
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot 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 flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware ! And I bet it would not brick your phone...
THANK.
Get Me On ; [email protected]
Like Us On Facebook www.facebook.com/axayleo
Will it work on locked bootloader..
Yes
mukulgupta690 said:
Will it work on locked bootloader..
Click to expand...
Click to collapse
Yes It will because the Stock firmwares are officially signed by Motorola.
I have installed soak test version of android 5.0.2...will i get the official update in future...motorola guys says that if you installed softer manually you will not get that please help..
You will get update if you have not rooted and installed custom recovery.
mukulgupta690 said:
I have installed soak test version of android 5.0.2...will i get the official update in future...motorola guys says that if you installed softer manually you will not get that please help..
Click to expand...
Click to collapse
It depends on if you have rooted and installed custom recovery or not. But if you are not on root you will get update for sure...
Will unlocking and locking the bootloader show the status code 2 in reocvery menu???
KaziRahman said:
Will unlocking and locking the bootloader show the status code 2 in reocvery menu???
Click to expand...
Click to collapse
locked bootloader is not required to get OTA update, the only require is stock recovery and stock rom.
Thanks , it worked after unlocking Bootloader
please read the sticky warning thread for this issue.
[WARNING] IMPORTANT DOWNGRADING / HARD BRICKING INFORMATION
USE THIS AT YOUR OWN RISK!!!!!!
Unable to Downgrade from Lollipop
Hi , i tried downgrading from soak test lollipop to 4.4.4 and i get the following error . Help me if possible . I have locked bootloader.
C:\Users\ \Desktop\ \ \Stock 4.4.4> fastboot flash boot boo
t.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.353s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.033s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot flash recovery
recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.318s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot.exe flash syst
em system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (243072 KB)...
OKAY [ 8.025s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.701s
sham4u2sam said:
Hi , i tried downgrading from soak test lollipop to 4.4.4 and i get the following error . Help me if possible . I have locked bootloader.
C:\Users\ \Desktop\ \ \Stock 4.4.4> fastboot flash boot boo
t.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.353s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.033s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot flash recovery
recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.318s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot.exe flash syst
em system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (243072 KB)...
OKAY [ 8.025s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.701s
Click to expand...
Click to collapse
Download the signed stock rom by motorola, the problem will be solved. This rom is not official/signed. OP just updated a faulty link.
bhumik147 said:
Download the signed stock rom by motorola, the problem will be solved. This rom is not official/signed. OP just updated a faulty link.
Click to expand...
Click to collapse
can u provide link for that , searched in XDA coudnt find it .
My mistake, There is no Stock Image by motorola yet for 4.4.4
A Complete solution for your Comment.
bhumik147 said:
Beware of this post , it will lead you to hard brick your device permanently.
Click to expand...
Click to collapse
Oh then why didn't the same procedure bricked sorry hard bricked my device A-Hole. Don't Spam Shaking your Moto G. This is for Moto E.
1. The commands include flashing gpt.bin partition and motoboot which will lead to hardbrick on downgrade from 5.0.2.
I am also Moto G user, from experience in that phone i know how downgrading destroys your device.
Click to expand...
Click to collapse
Isn't it funny. You at least had read the sticky that what makes your device get in Hard brick.
That's by downgrading to 4.4.2 and then upgrading via OTA to 4.4.4. A-Hole so, STFU.
Read This S**thead
http://forum.xda-developers.com/moto-e/general/warning-downgrading-information-moto-e-t3062859
2. Also, the images are not officially signed by motorola. i.e 4.4.4 ROM. Proof is in the image.
I Thank god , my bootloader was locked and i failed to flash the ROM properly.
Click to expand...
Click to collapse
So, search for Official KitKat 4.4.4 Stock Rom for Moto E on XDA itself. You'll find the same ROM. And Keep Sharing Screenshot Thats good for you jerk.
And talking about what happened in your screenshot go head on to Motorola's official website and Download official 4.4.2 KitKat Stock Rom and flash it. I bet you'll see the same. That's an not yet fixed problem with moto E.
Research before you say A-Hole.
The commands of downgrade should be :
mfastboot flash boot boot.img
mfastboot 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 flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
"with for a SIGNED ROM"
Click to expand...
Click to collapse
Now this last answer to whole of your post.
This is if you are downgrading from 4.4.4 to 4.4.2...
Not if you're getting off with lollipop. Okay Read Heading Carefully it downgrading from lollipop to KitKat 4.4.4
A MeanHead Watch my Video Carefully It worked and I successfully downgraded to KitKat. And Everyone even a noon knows that to install Lollipop soak test one must be on Stock android 4.4.4. And After flashing this I successfully Upgraded to Lollipop. So get Life and don't spam. Like you're jealous or something.
If it was supposed to brick my device would have bricked first I do this almost every 2 Week. And never ever encountered a soft brick you talking about hardbrick...
Toledo_JAB said:
please read the sticky warning thread for this issue.
[WARNING] IMPORTANT DOWNGRADING / HARD BRICKING INFORMATION
USE THIS AT YOUR OWN RISK!!!!!!
Click to expand...
Click to collapse
Yeah You are Right. It will HARDBRICK if someone downgrades to 4.4.2 and then upgrades via OTA to 4.4.4.
But Mine is Downgrading directly to 4.4.4 from 5.0.2 so no issues like Hard brick isn't.
Meanwhile i never encountered it.
btw thanks a lots for a useful link...
meakshay_mishra said:
Yeah You are Right. It will HARDBRICK ..
Click to expand...
Click to collapse
oh , sorry bro. I had a great misunderstanding. Sorry for the trouble, you are right about it. The only solution is we have to wait for stock 5.0.2 Image by motorola to lock the bootloader.
bhumik147 said:
oh , sorry bro. I had a great misunderstanding. Sorry for the trouble, you are right about it. The only solution is we have to wait for stock 5.0.2 Image by motorola to lock the bootloader.
Click to expand...
Click to collapse
But I think Motorola is thinking to upgrade Moto E directly to 5.1
meakshay_mishra said:
But I think Motorola is thinking to upgrade Moto E directly to 5.1
Click to expand...
Click to collapse
More later we will get the official taste. Anyways, 5.0.1 is not smooth like in other devices , which is saok's issue and aosp issue too.
meakshay_mishra said:
Here's The Video Tutorial on Downgrading Your Moto E from Android 5.0.2 to STOCK KitKat 4.4.4. Yes ! 4.4.4.
http://youtu.be/w7S5WmlPgrI
1. Download Stock 4.4.4
2. Download mfastboot.
3. Download ADB. ( Download Links are in video description)
Now flash Stock 4.4.4 using adb.
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot 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 flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware ! And I bet it would not brick your phone...
THANK.
Get Me On ; [email protected]
Like Us On Facebook www.facebook.com/axayleo
Click to expand...
Click to collapse
Does it work on rooted MotoE ? I read somewhere that its works only none rooted and stock recovery installed phone
Anyone tried this method?
it worked for me
Hello guys,
I'm trying to downgrade my Moto X Play XT1563, I found a tutorial on the Internet using the fastboot for such a feat. From what I saw, many people use this tutorial to upgrade or simply go back to what it was before "flash".
But in the first command line, when I type in CMD, an error appears:
> fastboot flash partition gpt.bin
target reported max download size of 268435456 byte
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
The tutorial is for this purpose doubt
1) Extract the Fastboot / ADB and images (zip ROM), extract the two zip's to a folder of your choice
2) Restart your phone mode 'Bootloader' (Turn off the cell and then press the volume button (minus) and (power for 2 seconds) and then release the power.)
It would be interesting to have activated in the "Developer options" the option "Allow OEM Unlock"
3) Now the CMD, enter the commands:
NOTE: system.img_sparsechunk may contain name or number, so check if you have only modify the hour.
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fastboot erase userdata
fastboot reboot
I wonder if someone could help me solve this case, please.
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
THANKS!
Wardenn said:
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
Click to expand...
Click to collapse
Man you are the ****ing best! You save my phone. Thank you very much! I was so stressed! THANKSSSS!
So I tried CM13 and wanted to go back to everything official. So I restored the ROM from this place: https://github.com/motoxplay/stock
...using this guide: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Then I tried read the official Motorola guide to re-locking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately it doesn't work. Using the guide, at the first step, I get this message:
Code:
fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.141s
So I searched more on the web and ended up trying this:
Code:
fastboot oem lock
or
Code:
fastboot oem lock begin
and get this:
Code:
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.023s]
finished. total time: 0.023s
I also found someone around here who said that by flashing the ROM his bootloader was locked again. That didn't work for me. I'm still getting this
Code:
"Device is UNLOCKED. Status Code: 3"
on the bootloader.
What can I do?
My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.
minimale_ldz said:
My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.
Click to expand...
Click to collapse
Well for the bootloader they only give us 5.1 and my ROM is 6.1. But when I tried to flash the 5.1 ROM from the same page I got the same message. I'm a bit stuck.
Then I tried to reinstall TWRP and again same message.
I'm stuck...
OK so I was able to install TWRP and then try to go back to 5.1 but that didn't work. It's a shame I thought I could trust that Motorola would give good information.
Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.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.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!
Prosis said:
Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.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.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!
Click to expand...
Click to collapse
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?
xboysz said:
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?
Click to expand...
Click to collapse
That was in my OP : https://github.com/motoxplay/stock
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.
Prosis said:
That was in my OP :
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.
Click to expand...
Click to collapse
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?
xboysz said:
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?
Click to expand...
Click to collapse
You're welcome! I understand the frustration!
My status is 2. You can't get it back to what it was. 2 is an indicator that it was unlocked but that it's now locked.
Hi guys,
How can i relock the bootloader?
There is some guide,please?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
I haven't been able to relock it yet.
I unlocked, flashed a custom ROM and then restored everything to stock but after that it was giving me some strange error about system/boot partition "altered" (if I remember correctly).
I said strange because there was no root neither twrp installed, I'm still confused.
So if I flash the stock rom and launch fastboot OEM Lock, it doesn't work?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
Firstly you have to flash all the images except boot.img,oem.img and system.img Then run fastboot oem lock.Then it ask for the confirmation Run the same command again.Then flash oem.img,boot.img and system.img.Then run fatboot oem lock again.This locks the bootloader
Use this command
fastboot oem lock begin
Then followed by the commands used to flash stock rom.
Then lastly use
fastboot oem lock.
You need signed boot or oem image
coloxim said:
Hi guys,
How can i relock the bootloader?
There is some guide,please?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
Click to expand...
Click to collapse
i have tried almost all ways to lock moto g5 plus bootloader but it requires signed boot or oem image to lock the bootloader and without them you can't lock the bootloader.
i searched a lot but was not able to find signed images, as the stock roms available for moto g5 plus are also not signed.
g_chahar said:
as the stock roms available for moto g5 plus are also not signed.
Click to expand...
Click to collapse
Really?
Yes,
manos78 said:
Really?
Click to expand...
Click to collapse
yes as i checked motorola website and for Moto G family there are only available signed roms are for XT1541, XT1543, XT1548, XT1625.. as i tested NPN25.137-33,NPN25.137-35 both but they didn't work. We have to wait for motorola to make the official rom available for moto G5 plus.
g_chahar said:
We have to wait for motorola to make the official rom available for moto G5 plus.
Click to expand...
Click to collapse
OK. Thank you for comment this!
Peharps you can ask in the official Motorola's forum for the signed ROM.
manos78 said:
OK. Thank you for comment this!
Peharps you can ask in the official Motorola's forum for the signed ROM.
Click to expand...
Click to collapse
i will make it available on XDA within a weak as i contacted someone, he will arrange the rom from Motorola Service Centre in 2-3 days.. and after testing it i will upload the same.
I'm thinking on unlocking the bootloader and installing TWRP in my G5 Plus but now I'm curious, why are you after locking it back again?
Lock Bootloader
Any update on this, I also need to lock my G5 plus bootloader.
Thanks
bootimage
is there a signed boot image out there im back to stock adb says i need a signed boot image
g_chahar said:
i will make it available on XDA within a weak as i contacted someone, he will arrange the rom from Motorola Service Centre in 2-3 days.. and after testing it i will upload the same.
Click to expand...
Click to collapse
Perfect
i talked with cutomer service on motorola site an they say to run the g4 software
but i dont know if there an idiot or not
I managed to lock the bootloader, it's fairly simple.
Download the full stock OTA from here: https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
Unzip it and go into fastboot mode.
Code:
fastboot oem lock begin
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot oem lock
Sources: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ and https://forum.xda-developers.com/showpost.php?p=72494649&postcount=23
mikkoc said:
I managed to lock the bootloader, it's fairly simple.
Download the full stock OTA from here: https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
Unzip it and go into fastboot mode.
Code:
fastboot oem lock begin
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot oem lock
Sources: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ and https://forum.xda-developers.com/showpost.php?p=72494649&postcount=23
Click to expand...
Click to collapse
Hello can you tell me which firmware u flashed and how you did in detail please
piyushahir said:
Hello can you tell me which firmware u flashed and how you did in detail please
Click to expand...
Click to collapse
I flashed NPN25.137-35
I get a error whene flashing files:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.078s
ADB and Fastboot find my Phone normal.
Schrotty35 said:
I get a error whene flashing files:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
I didn't flash this file at all, only the ones in my previous post.
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
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 erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.
Thanks
Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.
This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>
Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.