Develop Bugs

How to re-lock Bootloader of all Potter version

Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader.
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 I am also not responsible for anything happens as a result of flashing these files
What you need :
1- Motorola drivers :
64-bit
32-bit
2- Minimal ADB and Fastboot:
Minimal ADB and Fastboot
3- Stock Fastboot flashable official firmware.
Here is the donwload of NPNS25.133-37-11 it should be perfect for lock BL for all RETEU users:
Mirror 1 (MEGA)
Mirror 2 (GoogleDrive)
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
Now let's start with the guide.
1- Install Minimal ADB and Fastboot.
2- Extract stock firmware to any folder.
3- Now copy all the stuff that is in Minimal ADB and Fastboot folder in the folder where you extract the firmware.
4- Connect your device in fastboot mode (power off the device and while you press VOL down button insert the USB cable).
5- Open ADB and Fastboot terminal (press SHIFT+right click on the folder where you extract the firmware and select "open command window here").
6- Now type in Fastboot terminal "fastboot devices" (without commas) to be sure that your device is recognized.
7- Type these command one by one on terminal
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
Now your device will restart and your BL will be locked.
Now for be sure reflash all the complete firmware repeat the point from 5 to 7 but insert this code now
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
Now you will be able to receive the OTA update with your locked BL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @Nirbhay2

aSaro12 said:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Click to expand...
Click to collapse
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:

manos78 said:
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
Click to expand...
Click to collapse
Yes, this is a little but important thing. :good::good:

Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

siddhesh9146 said:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
That thread is specific for Indian Variant.
And if you read carrefully I've mentioned the writer of the thread that you've posted.

Thank you!!
That worked perfectly on XT1685. Much appreciated.

Thanks
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?

SeRi0uS007 said:
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
Click to expand...
Click to collapse
My Software status is also Modified and I never got ota's I always had to manually clean flash stock images. If someone found a way I would love to know how to get ota's on stock rom.

Thank you. my phone can get OTG now.

I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !

pfufux said:
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
Click to expand...
Click to collapse
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?

tufoz said:
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
Click to expand...
Click to collapse
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.

pfufux said:
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
Click to expand...
Click to collapse
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93

pfufux said:
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
Click to expand...
Click to collapse
Everyone else is getting the 137-92 update, why does yours say 137-93?

I don't know but the update came from OTA.

pfufux said:
I don't know but the update came from OTA.
Click to expand...
Click to collapse
you confirm me that amazon replaced your phone? i think i will do the same thing

Ok .. i tried the procedure again.. I used 137.33.11 cid 50 NPNS but i got this error messages..
when flashing system: invalid signed image
when flashing bootloader "security downgrade version"...
any hint?

tufoz said:
you confirm me that amazon replaced your phone? i think i will do the same thing
Click to expand...
Click to collapse
I confirm Amazon changed the motherboard of my phone. I have a new IMEI number.

I can't re lock bootloader
Hi, i am trying to install stock rom and relock bootloader because after installing custom rom, i am not getting network in my device. but now after installing stock rom(see below image for version), i cant relock my bootloader. it gives me error like security downgrade issue.

Thanks a lot
:good::good::good::good:
the indian variant relock is not correctly explained
You Have Explained It
Listen all
You will need the firmware which you were using before unlocking your bootloader then only you can relock it again
Now i can give it for warranty Thanks a Lot

Found a way to recover hard brick bootloader

Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

magix01 said:
Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
Click to expand...
Click to collapse
How have you managed to enter the "bootloader" mode?

You don't need an unlocked bootloader to flash stock firmware via fastboot
Just download the firmware and use fastboot to flash it (all parts)
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Plus what did you use to re-image the bootloader?

I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
try rewrite bootloader, I don't know if it will work, but try.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.

if you share the method
ASHDCBZ said:
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.
Click to expand...
Click to collapse
if you share the method, so faster we can find a way to revive the g5 and you would help us all
si comparte el metodo, asi mas rapido podremos buscar la forma de revivir el moto g5 y nos ayudarias a todos

This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.

magix01 said:
This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.
Click to expand...
Click to collapse
You have to flash the entire firmware in order - not just boot.img (which is the kernel)
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

I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
I think that should work because he is having the bootloader version B8.24 and the rom posted on XDA having B8.23

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
Still cant flash it, however i tried your firmware, flashed bootloader, now version changed from B8.23 to B8.25, but when i get to fastboot flash boot boot.img i still get:
sending 'boot' (16384 KB)...
OKAY [ 20.642s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 20.830s
This happens on B8.25 new version, got anything else to try?
Edit: I flashed B8.23 bootloader and it bricked the phone again to Qcom loader... this time it wont flash bootloader with exploit again so its dead 100% i think.

Obviously don't try and downgrade the bootloader
Can you just flash twrp recovery & access recovery mode to flash a custom rom?

Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.

magix01 said:
Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.
Click to expand...
Click to collapse
You would have to say how you rreimaged the bootloader so those with unlocked bootloaders can try
I take it you used something like z3x or similar software

I used JTAG flasher from GSM forum, but the thing is my bootloader used to be unlocked then after flash it went to locked status and CID was 0xDEAD, basically now i cant every fix it with jtag so its dead totally.

try with RSD Lite, is automated

Tried still same problem just this time it fails with gpt.bin, also the phone is totally bricked again so ...

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Yeah, that's pretty ****ed up

Help Z2 PLAY XT1710-11 + Testing

Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
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 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends

I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .

(Bootloader) Permission denied [SOLVED]

Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:
Code:
fastboot -w
And i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried to remove them:
In TWRP I tried to do something but all I get is something similar to this:
Am I missing something? Thanks for your help.

I've been reading the question and answer forum, apparently it's a problem with the encryption.
I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?

In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata

TheFixItMan said:
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
Click to expand...
Click to collapse
Hello, good (and bad) news
I did and now I have MTP for TWRP.
But still CMD says "Bootloader is logical @@@ not found"
"@@@" is depending on what you are trying to flash, be it system or recovery.
I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.
Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.
I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.
It makes me believe that something is still encrypted.
I mean this.

I also tried
Code:
fastboot format:ext4 userdata
But I have this:

Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!

TheFixItMan said:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
Click to expand...
Click to collapse
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.

Hello again, I saw you in another post that apparently has the same problem as me, it is this:
Decryption unsuccessfull
Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia...
forum.xda-developers.com

I have the same bugs, do you think I should run the command to decrypt?

Dislekzi4 said:
Ok, I'll get to the point.
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Click to expand...
Click to collapse
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)

Hi, it work!
Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.

I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything

Rod_Ems said:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Click to expand...
Click to collapse
Enable adb debugging on your device in dev options
Make sure you are using the latest platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip
Navigate your cmd window to to the platform tools directory
In cmd type
adb devices
Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to
Then type
adb devices
And your device is authorised

TheFixItMan said:
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Click to expand...
Click to collapse
mine show the following error message: device '(null)' not found

danniel_sx said:
mine show the following error message: device '(null)' not found
Click to expand...
Click to collapse
Either
Your phone is not connected to pc
Faulty cable
You haven't installed Motorola USB drivers
You are using the wrong commands
If in fastboot mode type
fastboot devices
If in recovery mode type
adb devices
Your device should be listed if correctly connected

I found a solution, i'm argentinian so sorry if my english is bad
the fastboot menu of the combination power + volume down have no permissions to all modifications
You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power
Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons
Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions

Android 11 update.

Receiving Android 11 in Argentina. RETAR
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow , finally .....

Hey, vos sabes que actualice y me brickeo el telefono....
te salio bien?

I had problems after the update. The phone was always with Stock rom and it was never touched for anything root. It was updated by OTA and it became a brick after the reboot. I tried to recover by fastboot with the rom on android 9, 10 and 11 (11 rom downloaded from the lenovo app for pc) without any success.

hey, please someone dump stock firmware from that update, thanks in advance

stockrom.net_KANE_RSA31.Q1-48-36-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
drive.google.com

cdanieltoralesp said:
stockrom.net_KANE_RSA31.Q1-48-36-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
this rom works for AT&T Mexico ??? or for which country is it functional? how is it installed? What are the adb commands?

Poland•
Motoflash Pro

Does anyone flashed this particular Android 11 firmware ? How it works ? I'm a little bit confused because I didn't find anywhere on trustworthy sites , official firmware for Moto XT1970-3 . So , what's up guys ?

to update to android 11 ... why does the bootloader have to be locked again? You will not be able to create a .bat file like the one in this post = MOTO-VISION_ACTION_FASTBOOT-TOOL_9-10.zip - https://forum.xda-developers.com/t/...hare-thread-tool-fastboot-flash-info.3943516/ maybe you need different adb commands ???? Does anyone have knowledge and help us create a way to flash android 11 from adb? Thanks in advance.

I used this commands and extracted firmware files to folder with adb and fastboot tools and it booted but only with unlocked bootloader. I have tried flashing same region as mine with locked bootloader from A10 to A11 (reteu) and cannot boot. Security error.
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.11
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash system_b system_other.img_sparsechunk.3
fastboot flash vendor_a vendor.img
fastboot erase userdata
fastboot reboot bootloader
EDIT:
I added edited bat file but i dont know its works.
I copied lines and edited to comands i have write.
Please tell me if it works

Finally received Android 11 by OTA . Phone locked , unroot , in original state .
XT1970-3 , RETEU channel .
RSA31.Q1-48-36-11
Didn't observed major improvements , on the contrary old unoptimized apks are not fluent . Boot sequence is faster , face recognition is slower also fingerprint unlock . WiFi is better , Mobile Data apparently the same . Camera apk seems to be a little bit better . Internet browser seems a little bit faster . Banks apks , are working . Touch sensitivity the same .
Overall maybe is just an impression but I feel the phone kind of laggy .

MyBike4Life said:
I used this commands and extracted firmware files to folder with adb and fastboot tools and it booted but only with unlocked bootloader. I have tried flashing same region as mine with locked bootloader from A10 to A11 (reteu) and cannot boot. Security error.
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.11
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash system_b system_other.img_sparsechunk.3
fastboot flash vendor_a vendor.img
fastboot erase userdata
fastboot reboot bootloader
EDIT:
I added edited bat file but i dont know its works.
I copied lines and edited to comands i have write.
Please tell me if it works
Click to expand...
Click to collapse
I'm going to try, after a while I'll be back and I'll tell you how it went.

The .bat file worked very well, now I have Android 11, my channel is ATTXT, but I made flash of a ROM from another channel different from mine (TEFMX), now I have a question, you can have Root with magisk in Android 11???

Not received Android 11 on XT1970-1 Retla Brazil Costa rica version

Just received Android 11 , about 1 week ago , last few days I just got second Android 11 update with security patch till 01 August all these for XT1970-3 . It seems it has a better battery saver

Is there a way I can root Motorola One Vision Android 11 ?
Because I have tried a lot of times, but it all leads to infinite rebooting (I think it's called soft brick or something)
Maybe there is a way to root it correctly, but I think I have been doing it wrong
I would appreciate your help <3

DI_G7 said:
Is there a way I can root Motorola One Vision Android 11 ?
Because I have tried a lot of times, but it all leads to infinite rebooting (I think it's called soft brick or something)
Maybe there is a way to root it correctly, but I think I have been doing it wrong
I would appreciate your help <3
Click to expand...
Click to collapse
I managed to get root in android 11, I just followed the guide in the post where twrp-3.3.1-test4 comes out, and I also managed to install edExposed with the Gravitybox Module.

tin0o said:
I managed to get root in android 11, I just followed the guide in the post where twrp-3.3.1-test4 comes out, and I also managed to install edExposed with the Gravitybox Module.
Click to expand...
Click to collapse
I have tried to install TWRP too but it leads to an error after the command
Fastboot flash TWRP.img
Can you tell me how did you installed TWRP?
.
It would help me a lot <3

Finally Android 11 came into Retla Region XT1970-1 (Brasil or Spanish)