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
Disclaimer :
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
and[COLOR="Red"] I am also not responsible for anything happens as a result of flashing these files[/COLOR]
Hey Guys,
Here are the Stock Firmwares for potter
Lets Proceed :
1) Install Minimal ADB and Fastboot
https://www.androidfilehost.com/?fid=745425885120698566
2) Extract stock firmware zip
3) Now copy all the stuff that is in this zip into the folder where you extract the firmware.
4) Turn on ADB debugging from dev options menu and use 'adb reboot-bootloader' (Without quotes) in cmd to reboot your phone into boot-loader mode
5) Open the extracted firmware folder then press SHIFT+right click in the folder where you extract the firmware and select 'open command window here' option
6) and then Paste the following commands and hit Enter :
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
↑
This Script will not Re-Lock Your Boot-loader
But if you want to Re-lock your bootloader, then use the following commands: (Thanks to @Nirbhay2 and @aSaro12)
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
And After Flashing it Please Re-flash the whole firmware again :
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
But if you Don't want to do it manually, Here's the automated BAT script for you;
Just copy and paste it to the extracted folder (Thanks to @Tech_Savvy) : Download Here
This Script will not Re-lock the Boot-loader
----
You can Skip GPT and Boot-loader Partitions if you want
But Keep in mind that You Cannot DOWNGRADE These 2 Partitions
And if you try to do so, then you'll Possibly end up with HardBrick
You will need the appropriate version of the firmware according to your device version
SO PROCEED WITH CAUTION
Firmware Download Links :
1) NPN25.137-67-5 for XT1686 (Indian Varient)
Download Directly from Motorola Servers
Mirror 1 -pCloud
Mirror 2 -Google Drive
Mirror 3 -Dropbox
---
2) NPN25.137-35-5 for all Amazon (US) variants : Link N/A
and NPNS25.137-83 for Non-US Amazon Variant : Link N/A
and for the Non-Amazon Variants NPN25.137-83 : Link N/A
---
3) NPNS25.137-35-5 for Retail GB varient (Thanks to skooter32 for info) Link N/A
And NPN25.137-83 : Link N/A
---
4) NPN25.137-15 for Brazil-Mexico varient (XT1681 - XT1683) Link N/A
-----
Choose Carefully which one to flash
Special Thanks to rikk and @anuraag.neo For Capturing Indian varient zip! if you like my work then please hit that THANKS ? Button!
Troubleshooting :
Stuck on ' Waiting for devices' :
1) Make Sure your device is detected in Bootloader interface aka Fastboot mode, you can simple see your device listed in device manager.
2) Install Motorola Driver IF you haven't Installed it yet. Because it can be the main reason for this error. Download it HERE : http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
access denied
bornlivedie said:
access denied
Click to expand...
Click to collapse
mirror is uploading, just be patient
bornlivedie said:
access denied
Click to expand...
Click to collapse
alright, mirror is up
https://goo.gl/oRp7ou
Thank you. I am already on this firmware. But will use this in future if I dare to root my mobile in future
Sent from my Moto G (5) Plus using Tapatalk
This work on xt1687?
JassyelZ said:
This work on xt1687?
Click to expand...
Click to collapse
Don't think so, the XT1687 should be the US variant of the G5 Plus, and the NPN25.137-67-5 is the Indian ROM.
You probably want to look for the NPN25.137-83 stock ROM.
JassyelZ said:
This work on xt1687?
Click to expand...
Click to collapse
This is the firmware I flash on my XT1687
https://drive.google.com/file/d/0BwXyT5PTGsEHWmVhZFBsV0szS1k/view?usp=drivesdk
mikeyinid said:
This is the firmware I flash on my XT1687
https://drive.google.com/file/d/0BwXyT5PTGsEHWmVhZFBsV0szS1k/view?usp=drivesdk
Click to expand...
Click to collapse
With this its possible relock the bootloader? I have agoust patch
JassyelZ said:
With this its possible relock the bootloader? I have agoust patch
Click to expand...
Click to collapse
I have Verizon so I haven't got that update. I can't say for sure.
Hey, I'd hard bricked my xt1686 and have revived it using Albus blankflash and am running the stock deodexed and debloated ROM provided here on the forum. Can I use your method to go back to stock?
roydhritiman said:
Hey, I'd hard bricked my xt1686 and have revived it using Albus blankflash and am running the stock deodexed and debloated ROM provided here on the forum. Can I use your method to go back to stock?
Click to expand...
Click to collapse
i also the same problem, i tried but failed . can you confirm that is working or not
Chandru1166 said:
i also the same problem, i tried but failed . can you confirm that is working or not
Click to expand...
Click to collapse
failed in reviving your phone using albus blankflash?
or using this method to go back to stock?
The commands
fastboot erase customize
fastboot erase clogo
return error messages and are not relevant. Check the flashfile.xml in the ROM.
Will i still be able to unlock again and flash twrp for customs roms and stuff.
I any complications please tell me the steps. BTW this is highly appreciated.
ksvirdi105 said:
Will i still be able to unlock again and flash twrp for customs roms and stuff.
I any complications please tell me the steps. BTW this is highly appreciated.
Click to expand...
Click to collapse
can you tell me the build no and the model no. of your device?
roydhritiman said:
Hey, I'd hard bricked my xt1686 and have revived it using Albus blankflash and am running the stock deodexed and debloated ROM provided here on the forum. Can I use your method to go back to stock?
Click to expand...
Click to collapse
if you have xt1686 and if you got the update before hardbricking then you can use it
siddhesh9146 said:
if you have xt1686 and if you got the update before hardbricking then you can use it
Click to expand...
Click to collapse
yup i got the xt1686 and yes i had the 67-5 update before hard bricking, so i can use it right!?
Should be work on xt1680?
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
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash Bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Android 11 to Android 10 downgrade
It seems Motorola has disabled bootloader downgrade through Anti-Rollback in Android 11. The latest version of Android 11 (Q1-19-58-30-2) doesn't allow vbmeta to be flashed. Fastboot would return following error:
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 16
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
skritch said:
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
Click to expand...
Click to collapse
Also wanna know this
Disillusionedsal said:
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs12
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 super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Click to expand...
Click to collapse
How long is the "fastboot oem fb_mode_clear" command supposed to last? Left it for a lot of time and nothing happens, I check the bootloader logs and last log is erase:ddr. If I select Start from the menu using the up/down keys and the start button, it takes me to a screen where it says no valid firmware detected contact motorola support. Please help
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
snowman2765 said:
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
Click to expand...
Click to collapse
anybody?
if i want to downgrade to low version from high version, need to unlock bootloader??
snowman2765 said:
anybody?
Click to expand...
Click to collapse
Try use lowercase bluetooth
tha_mechanic said:
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
Click to expand...
Click to collapse
if the bootloader is unlocked does that mean it can be used with any carrier? what exactly would an unlocked bootloader enable?
Unlocked bootloader just allows you to flash custom .img on the device
This however wont fix the fingerprint scanner, that even if you did the workaround after unlocking ( https://forum.xda-developers.com/t/fix-fingerprint-not-working-after-bootloader-unlock.4214041/ ) , because you lost root after flashing stock and no way to edit the goodix files.
Anyway to properly return to stock and get fingerprint scanner back ?
EDIT: Nvm, the fix works properly with just skipping all the goodix part and doing all the CQA Menu Mode operations per the instructions.
Hello - it's been about 10 years since I played with any XDA stuff or custom roms. I have a stock Motorola G Power that bricked itself. It will not boot and recovery mode just gives me "No Command". Only option seems to be factory data reset.
Can anyone suggest a procedure to allow me to either re-install the stock software to get into the phone or recover my data? Sadly I had not backed anything up since last summer.
Should I just try to reflash a stock rom to see if i can get in? Will flashing the rom kill the onboard storage?
Cant find the exact same version either:
SOFIA10/QPMS30.80-63-6-8-5
I found 63-6-8-10 and 63-6-8-3 but not the exact same. Phone is Retail US.
Any help would be appreciated.
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Uberhare said:
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Click to expand...
Click to collapse
You can try flashing the stock from and just skip the erase userdata step.
The firmware contains a file named flash_file.xml contains the flash commands
You can use Online FlashFile Converter to convert the .XML to simple fastboot commands.
You also should check if getvar is-userspace
Code:
fastboot getvar is-userspace
if yes you need to switch between fastboot and fastbootd
If it's no you don't need to worry about fastbootd
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You can try flashing the stock from and just skip the erase userdata step.
Click to expand...
Click to collapse
Do I need to unlock the bootloader for flashing an original file?
Uberhare said:
Do I need to unlock the bootloader for flashing an original file?
Click to expand...
Click to collapse
No, you shouldn't need to but it's easier if the bootloader is unlocked.
Unlikely, you can unlock the bootloader now anyways.
Unless you enabled OEM Unlocking in Dev Options already.
If you did enable OEM Unlocking, I would Unlock the bootloader.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Uberhare said:
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Click to expand...
Click to collapse
Easier may not be the right word.
If the bootloader is unlocked, you are less likely to have issues flashing.
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
fastboot getvar is-userspace returns:
is-userspace: no
Finished. Total time: 0.002s
I found where fastbootd is.
C:\Android>fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.002s
Uberhare said:
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
Click to expand...
Click to collapse
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
sd_shadow said:
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
Click to expand...
Click to collapse
adb devices does not show anything in either mode. That is why I looked for fastboot mode. Should I trouble shoot that first?
This is what I want with the erase commands deleted at the end? The erase commands are what will kill my data or is there something else I need to remove?
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
echo Press any key to restart the phone!
pause
fastboot reboot
exit
Looks like phone doesn't respond to commands in fastbootd only normal.
I successfully ran the batch file, but the phone still doesn't boot. What is my next step? (besides throwing it against the wall!)
Phone accepts all the files for the current version of software, as well as commands to clear some of the labels. So the userdata is still there, I just can't get to it. Can you read these with a jtag like the older phones?
What if I try to roll it forward to Android 11 through the stock roms?