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 ?
Related
I have a Moto Z (XT1650-03) which I OEM Unlocked using the process to obtain a code from the Motorola site. I've reflashed the stock firmware XT1650-03_GRIFFIN_RETCA_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC. However, whenever I try to use the fastboot oem lock function, I get the message "(bootloader) still require signed boot.img".
In another thread, Entrec mentioned something about flashing a custom logo to at least get rid of the unlocked bootloader message but I'd still like to re-lock the phone period. Any suggestions?
Cheers!
UPDATE: finally got the Nougat update to install, so I guess my updated question is this: is there any way to relock my Moto Z on the Nougat update?
May I ask the reason?
enetec said:
May I ask the reason?
Click to expand...
Click to collapse
One reason for some is being able to use Android Pay
lollyjay said:
One reason for some is being able to use Android Pay
Click to expand...
Click to collapse
Are you sure locked bootloader is needed for it? I've only heard about root issues...
enetec said:
Are you sure locked bootloader is needed for it? I've only heard about root issues...
Click to expand...
Click to collapse
The SafetyNet API used by Android Pay now detects and flags unlocked bootloader :crying:
lollyjay said:
The SafetyNet API used by Android Pay now detects and flags unlocked bootloader :crying:
Click to expand...
Click to collapse
enetec said:
May I ask the reason?
Click to expand...
Click to collapse
At the moment, no real reason but yes, I've heard that some apps (like Android Pay which is supposedly coming here soon) don't work on devices with an unlocked bootloader.
I also cannot relock the bootloader. I downloaded a stock rom and flashed everything one at a time but at the end when I type fastboot oem lock it still says I need to flash a motorola signed boot.
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
and the rom I used was XT1650-03_GRIFFIN_RETUS_MPL24.246-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
thefatalepic said:
I also cannot relock the bootloader. I downloaded a stock rom and flashed everything one at a time but at the end when I type fastboot oem lock it still says I need to flash a motorola signed boot.
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
and the rom I used was XT1650-03_GRIFFIN_RETUS_MPL24.246-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Yup, I used the RETCA version and got the same issue. Was doing a bit more reading and sounds like it's a pretty moot point anyways. If you can manage to relock it, the unlocked bootloader message still remains.
pixelens said:
Yup, I used the RETCA version and got the same issue. Was doing a bit more reading and sounds like it's a pretty moot point anyways. If you can manage to relock it, the unlocked bootloader message still remains.
Click to expand...
Click to collapse
I'm only trying to lock it because I wasn't able to fully root it. I can't get root to stick and I'd rather relock it so I can still use Android Pay. I'm stuck in between, I can't root it and I can't unroot it. -__-
Unlocking the boot loader has been a "one way" process for Motorola phones for a long time. I am not sure if it's a fuse that gets blown or what but I have never heard of some one re-locking anything but Nexus devices.
thefatalepic said:
I'm only trying to lock it because I wasn't able to fully root it. I can't get root to stick and I'd rather relock it so I can still use Android Pay. I'm stuck in between, I can't root it and I can't unroot it. -__-
Click to expand...
Click to collapse
Thanks for comfirming, wasn't sure if Android Pay worked with an unlocked phone or not... oh well. Still haven't been able to ftr.
Locking the unlocked bootloader
I have spent days on the forums here on xda. I did come across a post from someone who seemed to have expertise (the development forum). It seems the Moto Z has a Qfuse. I you trip it then there is no going back. So Nougat is a one way path.
The good news that if you are patient then there is a path forward towards unlocking and rooting. Motorola voids you warranty but on the other hand they very much promote development and experimentation.
OrBy said:
Unlocking the boot loader has been a "one way" process for Motorola phones for a long time. I am not sure if it's a fuse that gets blown or what but I have never heard of some one re-locking anything but Nexus devices.
Click to expand...
Click to collapse
Since I've been researching on XDA today about relocking on another platform I can say confidently that many devices can have their bootloaders relocked. (Sometimes requiring 'tricky techniques') However there are generally a bunch of restrictions.
Specifically what I hoped to achieve was being able to customize a device with a 3rd-party rom and recovery, and then re-lock the bootloader for security reasons. (Making it harder for someone else to break into it if it gets stolen etc) But unfortunately most of them require all the partitions to be stock builds before they will re-lock.
Not sure, as I'm new to Moto Z, but my old Moto X could be rekocked. But it wouldn't return to a "locked" state. It world show as "relocked".
Could be the same result with the Z, and not sure how that would affect any software that is looking for a "locked" bootloader.
Darth said:
Not sure, as I'm new to Moto Z, but my old Moto X could be rekocked. But it wouldn't return to a "locked" state. It world show as "relocked".
Click to expand...
Click to collapse
Very interesting.
I know the OnePlus devices are very blase about such things, whereas Samsung's have some sort of "tamper" flag whenever you unlock the bootloader.
I'm slowly but surely starting to get up to speed on which vendor does what.. lots to learn..
help
pixelens said:
I have a Moto Z (XT1650-03) which I OEM Unlocked using the process to obtain a code from the Motorola site. I've reflashed the stock firmware XT1650-03_GRIFFIN_RETCA_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC. However, whenever I try to use the fastboot oem lock function, I get the message "(bootloader) still require signed boot.img".
In another thread, Entrec mentioned something about flashing a custom logo to at least get rid of the unlocked bootloader message but I'd still like to re-lock the phone period. Any suggestions?
Cheers!
UPDATE: finally got the Nougat update to install, so I guess my updated question is this: is there any way to relock my Moto Z on the Nougat update?
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
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
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
Click to expand...
Click to collapse
Would I need to flash everything, if only the recovery partition was flashed with TWRP?
apocalypse_bg said:
Would I need to flash everything, if only the recovery partition was flashed with TWRP?
Click to expand...
Click to collapse
Thank You Your post Was very helpful to me. My bootloader is now locked.
When you relock the bootloader, can anyone confirm for me if the message about the bootloader being unlocked is still there? I plan to sell this in the future and that could determine potential buyers
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:
Hello all!
So I got tired of waiting for the latest update to hit my phone so I figured I would do it manually. After plenty of experience with Moto phones I gathered that the official RETAIL files should work with all of the GSM versions of the Moto Z2 Play. This is confirmed to work with both XT1710-01 and XT1710-07, but is likely to work with others (but not the US Verizon Model). For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
As usual, you take full responsibility for anything you do to your phone, but since your bootloader is locked, this should be fairly low risk, barring some sort of power loss mid-flash.
How to:
1. Download & Install Motorola Drivers from XDA.
2. Download & extract stock rom from here.
3. Use mfastboot/fastboot to run the following commands/run the attached .bat file. (Hint: make sure fastboot files are in the same directory as the the ROM files and .bat file).
3a. If you need more help on mfastboot or fastboot, look here.
Code:
echo off
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash Start
echo -------------------------------------------------------------------------
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 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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash End
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
4. Enjoy!
Hope this helps!
but how is obtained stock rom?
For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
Click to expand...
Click to collapse
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
timster01 said:
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
Click to expand...
Click to collapse
I had no problem flashing with a locked bootloader. Didn't even have to wipe. What error did you get when you tried to flash?
I am wondering if it works on an XT1710-08 model...
Hi guys,
Did not see anyone here on XDA who uploaded recently leaked OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
06.03.2019, THE NEWEST PPW29.116-20 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1Axk870qsui9w3TnnRQM9pt618CQ0CnHz
MIRROR: https://mega.nz/#!0ZUyTAqI!XXPwj0mcsGs0wLFwxwX8V0OeFXgCe-NXf-2VbDvr5Nc
OLDER BUILD: PPW29.116-16 FIRMWARE DOWNLOAD (RETAIL) - BE CAREFUL, IT BREAKS SAFETYNET ON EUROPEAN G6+ VARIANTS!
DOWNLOAD: https://drive.google.com/open?id=1F0SFwVyXgy3ZixL36W6xwxjqPJAwiDus
MIRROR: https://mega.nz/#!VJ8xEYRT!rb476WxlV099PVJrLwbFIr1Z3XNjo89sO5MU-HfPzMQ
OLDER BUILD: PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
--- If you don't want to erase all your phone data, use script from G6PlusFlashPieOfficial_NoErase.zip. This will upgrade your G6+ to Android Pie without erasing data. ---
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 bluetooth BTFM.bin
fastboot flash dsp dspso.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).
Screenshots.
PS. Digital Wellbeing installed via Magisk.
My brother has a Moto G6 Plus (bought in Europe) without root, will he be able to update it without loosing his data?
Thanks in advance guys.
Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot 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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot reboot
This is normaly how i update my G6 Plus and never expierence problems......
cdfreak said:
Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot 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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot reboot
This is normaly how i update my G6 Plus and never expierence problems......
Click to expand...
Click to collapse
Exactly like this.
@cyberon these commands are for your brother.
rafikowy said:
Screenshots.
PS. Digital Wellbeing installed via Magisk.
Click to expand...
Click to collapse
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?
thump said:
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?
Click to expand...
Click to collapse
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.
smitharro said:
It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).
Click to expand...
Click to collapse
which file i need to do the 2nd method and where can i download it?
rafikowy said:
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.
Click to expand...
Click to collapse
Just rechecked and found my System Updates page no longer gives the "system integrity" error either. Still do get the "verity" error, but seems of no concern. Cool.
giorgis91 said:
which file i need to do the 2nd method and where can i download it?
Click to expand...
Click to collapse
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU
smitharro said:
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU
Click to expand...
Click to collapse
Will it wipe the phone ?
giorgis91 said:
Will it wipe the phone ?
Click to expand...
Click to collapse
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Suggestions
rafikowy said:
Hi guys,
Did not see anyone here on XDA who uploaded recently released OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
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 bluetooth BTFM.bin[PHP][/PHP]
fastboot flash dsp dspso.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
I place an "m" in front of fastboot to use mfastboot.
Get the mfastbootv2 it's best for flashing this way imo
Good work buddy.
What's the command erase carrier for?
smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
giorgis91 said:
Is that multilang or only in english?
Click to expand...
Click to collapse
smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english
giorgis91 said:
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english
Click to expand...
Click to collapse
All stock ROMs are multilingual. So Italian shouldn't be a problem.
what dos this mane: Verity mode is set to disabled when you boot the phone up?
cdfreak said:
what dos this mane: Verity mode is set to disabled when you boot the phone up?
Click to expand...
Click to collapse
A short explanation:
dm-verity
transparent integrity checking for block devices
read error if block integrity check fails
try to recover damaged blocks (from Android 7.0)
useful for read-only partitions like*system
fundamental part of*verified boot*on Android
Verified boot
device software integrity based on hardware root of trust
Boot chain (simplified)
verify*bootloader*using a hardware root of trust
bootloader*verifies*boot*and*recoverypartition
kernel*verifies*system*partition
uses dm-verity for the integrity checks once execution has moved to the boot partition
Hmmm. For some reason I get "Server error" in play store. And autobrightness jumps up and down every few seconds. Have tried returning to oreo and reflashing/factory resetting to no avail On reteu.
EDIT: Hmm also get the error in oreo now Anyone know whats up? Came from Lineage 16.
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
I think you have to do a twrp backup and then restore it.it's strange but works
Inviato dal mio GT-N5120 utilizzando Tapatalk
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
JulioCeesarC said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
Click to expand...
Click to collapse
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
junejo46726 said:
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
try to install 8.0 again and after that unlock bootloader and try to install 9.0 again with bootloader unlocked
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
I recomend bootloader unlocked for this process
junejo46726 said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
kain83 said:
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
Click to expand...
Click to collapse
did you try cleaning your cache? I used 19.3.
kewlzter said:
did you try cleaning your cache? I used 19.3.
Click to expand...
Click to collapse
I didn't indeed. I'm gonna give it a try, thanks
EDIT: it works!! So installed 19.3 version and wiped cache/dalvik, then reboot. So far so good, many thanks!!
keeps saying waiting for device
hindraftv said:
keeps saying waiting for device
Click to expand...
Click to collapse
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
reallydan said:
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
Click to expand...
Click to collapse
Clean flash or dirty flash?
rayudu123 said:
Clean flash or dirty flash?
Click to expand...
Click to collapse
Clean flash
reallydan said:
Clean flash
Click to expand...
Click to collapse
Is it possible to flash indian pie version after release of pie in india??? Or do we face any problem in flashing??
Everything works except dark theme. Any fix?
kewlzter said:
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
Click to expand...
Click to collapse
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
hindraftv said:
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
Click to expand...
Click to collapse
Why sure...
Step 1: you get yourself a usb cable.
Step 2: you plug one end into your computer.
Step 3: plug the other end into your phone..
glad to help
kewlzter said:
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
Click to expand...
Click to collapse
I also tried but fastboot saying can not load twrp @JulioCeesarC