Develop Bugs

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 .

cant start my moto z2 force (brick?)

Hello everyone i tryed to root my moto z2 force using xda tutorials but it didnt work, i unlocked bootloader, so when i installed magisk and recovery twrp didnt start my device, i decided to reinstall stock rom because i read that to recover my device i can do it, i downloaded a telcel firmware for Mexico for moto z2 force but i cant install bootloader with the command: fastboot flash bootloader bootloader.img
and now when i turn on my device it says that i have a diferent operating system and reboot and same message all time, help please

Can you get into fastboot mode if so use uzephi's
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 return to stock image but use the firmware for your device from here https://mirrors.lolinet.com/firmware/moto/nash/official/

riskyfuture said:
Can you get into fastboot mode if so use uzephi's
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 return to stock image but use the firmware for your device from here https://mirrors.lolinet.com/firmware/moto/nash/official/
Click to expand...
Click to collapse
i really apreciate your help really i was desperate hahaha, before do this you replyed i was reading a lot abot the problem but not really for moto z2 force and they said that have to install the last firmware with last bootloader to recover, then i did it i downloaded the last https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
then i tryed to flash bootloader and really flashed!!, so i turned on my phone and now works normal i used this commands:
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 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
apreciate your help a lot really thx
UPDATE: i have a question. found in your software link the Telcel MX firmware of my moto Z2 force, but if i update from OTA on my actual firmware is the posibility to get brick??, i dont know if install the Telcel firmware because it has Telcel aplications i hate of carrier

Z2 with no OS. Need help to get it back

Hello everbody,
Here is my story of how I managed it to have to OS on my Z2 Force (XT1789-6 with 6gb). I wanted to have lineagos on my smartphone and installed it before on my smartphone therefore I thought it would be easy.
1. I visited the official page and followed there instruction until the twrp instruction
HTML:
https://wiki.lineageos.org/devices/nash/install
. I did an oem unlock and installed twrp temporally (fastboot boot twrp-3.2.3-1-nash.img) and did a full backup.
2. I was reading on this forum that I need Oreo on my phone to install lineage, therefore I tried to update it. All attempts to update it failed. I was able to download updates to my phone and it started to install but it always failed.
3. I tried to flash the fitting Oreo Version on my phone (XT1789—06) OPXS27.109-49-5 from
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
with the sequence in #5 but it would only flash the bootloader and fails for the rest (erase works).
I flashed no gpt.bin!
*(fastboot flash bootloader bootloader.img) -> only when needed!
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 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
Click to expand...
Click to collapse
Fastboot menu now showed a modified Version
4. Since the official website does not tell about having Oreo on you smartphone I wanted to give it a try and proceeded with their instruction. I wiped the system and tried to install lineage with help of TWRP with resulted in Error 255.
5. I tried to Recover with TWRP but it told me that no partition is selected. Fastboot menu shows that there is no partition a/b.
I tried to flash Nougat from the same source like Oreo which works for bootloader (and gpt.bin) and fails for the rest
xxx>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (97411 KB) OKAY [ 2.684s]
Writing 'modem__a' (bootloader) Invalid partitio
n name modem__a
FAILED (remote failure)
Finished. Total time: 2.700s
6. No it shows me in fastboot that I have an unmodified oem locked phone. On start up it tells me that I have a corrupted phone and instead of the yellow unlocked bootloader warning its red. Its starts over and over again until I start fastboot.
Can you suggest me how I can get back to stock or to lineage?

b.bew said:
Hello everbody,
Here is my story of how I managed it to have to OS on my Z2 Force (XT1789-6 with 6gb). I wanted to have lineagos on my smartphone and installed it before on my smartphone therefore I thought it would be easy.
1. I visited the official page and followed there instruction until the twrp instruction
HTML:
https://wiki.lineageos.org/devices/nash/install
. I did an oem unlock and installed twrp temporally (fastboot boot twrp-3.2.3-1-nash.img) and did a full backup.
2. I was reading on this forum that I need Oreo on my phone to install lineage, therefore I tried to update it. All attempts to update it failed. I was able to download updates to my phone and it started to install but it always failed.
3. I tried to flash the fitting Oreo Version on my phone (XT1789—06) OPXS27.109-49-5 from
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
with the sequence in #5 but it would only flash the bootloader and fails for the rest (erase works).
Fastboot menu now showed a modified Version
4. Since the official website does not tell about having Oreo on you smartphone I wanted to give it a try and proceeded with their instruction. I wiped the system and tried to install lineage with help of TWRP with resulted in Error 255.
5. I tried to Recover with TWRP but it told me that no partition is selected. Fastboot menu shows that there is no partition a/b.
I tried to flash Nougat from the same source like Oreo which works for bootloader (and gpt.bin) and fails for the rest
xxx>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (97411 KB) OKAY [ 2.684s]
Writing 'modem__a' (bootloader) Invalid partitio
n name modem__a
FAILED (remote failure)
Finished. Total time: 2.700s
6. No it shows me in fastboot that I have an unmodified oem locked phone. On start up it tells me that I have a corrupted phone and instead of the yellow unlocked bootloader warning its red. Its starts over and over again until I start fastboot.
Can you suggest me how I can get back to stock or to lineage?
Click to expand...
Click to collapse
Try this commands:
fastboot --set-active=_a
pause
fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
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 oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=_b
fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_b bootloader.img
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_b oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=_a
fastboot reboot bootloader

Wow thanks. Worked out perfectly.

So many thanks, this helped me from a hard brick

Android 10 Stock Fastboot

Fastboot:
V11.0.15.0.QFQMIXM
TGZ
laurel_sprout_global_images_V11.0.15.0.QFQMIXM_10.0.tgz
https://www.androidfilehost.com/?fid=4349826312261807505
RAR
laurel_sprout_global_images_V11.0.15.0.QFQMIXM_10.0.rar
https://www.androidfilehost.com/?fid=4349826312261807506
V11.0.15.0.QFQMIXM
TGZ
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10. 0.tgz
https://androidfilehost.com/?fid=4349826312261783904
MD5: d6dc459e6cdb5f2b39c06be17090a455
RAR
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10.0.rar
https://www.androidfilehost.com/?fid=4349826312261785200
MD5: 5e7a3635661663db4c8953fca27f3be3
Note: Extracted from OTA zip & compiled back using maximum compression

edwaine said:
Fastboot:
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10. 0.tgz
https://www.androidfilehost.com/?fid...26312261783904
MD5: d6dc459e6cdb5f2b39c06be17090a455
Note: Extracted from OTA zip & compiled back using maximum compression
Click to expand...
Click to collapse
I extracted it but I didn't find the flash_all except data/bat script. Should not be?

papafan said:
I extracted it but I didn't find the flash_all except data/bat script. Should not be?
Click to expand...
Click to collapse
What program did you use to open the file? All the needed files are there.
{
"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"
}
Make sure you wait for the load to complete as this is a highly compressed zip file.

edwaine said:
What program did you use to open the file? All the needed files are there.
Make sure you wait for the load to complete as this is a highly compressed zip file.
Click to expand...
Click to collapse
Here in the first photo I don't see the " flash_all _except storage / bat " script. In a similar case when I flashed the stock A9 .tgz file, I also had this ability, to flash rom without lose data.

link not working :crying:

sunny3503 said:
link not working :crying:
Click to expand...
Click to collapse
Works fine for me.
Anyways, will post another link under RAR file.
Update: File uploaded, OP updated. Please check.

What about EU version PFQEUXM. Is it also available?
and another question... Will High Brightness Mode be available in android 10 for Mi A3?

tomiasx22 said:
What about EU version PFQEUXM. Is it also available?
and another question... Will High Brightness Mode be available in android 10 for Mi A3?
Click to expand...
Click to collapse
Eu version wasn't released by xiaomi yet so you will have to wait for it to be released.
And as for high brightness that's an issue with the Android one program. Being apart of the Android one program limits max brightness to 350 nits (actually just slightly less than 350 nits)
Xiaomi cc9e is basically the same device with miui and has max manual brightness of 530 nits.
It's a result of being part of Android one. Just Google it

tgz link not work

garylawwd said:
Eu version wasn't released by xiaomi yet so you will have to wait for it to be released.
And as for high brightness that's an issue with the Android one program. Being apart of the Android one program limits max brightness to 350 nits (actually just slightly less than 350 nits)
Xiaomi cc9e is basically the same device with miui and has max manual brightness of 530 nits.
It's a result of being part of Android one. Just Google it
Click to expand...
Click to collapse
Thanks for this answer. Of course I checked it before writing this post, sorry that I didn't mention that.
There are some rankinkgs on the web, where much older devices have brighter display, which put Mi A3 in the end of theese rankings...
Maybe stupid question, but do you think this may change in new Android One based on android 10?
Or is any other solution to improve brightness?
Applications to improve brightness on Google Play doesn't work with this phone (of course rooted).
but maybe Magisk module etc. ?
e.g. in Google Pixel 4 they explain how to enable this mode...
https://hothardware.com/news/google-pixel-4-high-brightness-mode

alcopsy said:
tgz link not work
Click to expand...
Click to collapse
The correct link:
https://androidfilehost.com/?fid=4349826312261783904
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
sunny3503 said:
link not working :crying:
Click to expand...
Click to collapse
I found the correct link:
https://androidfilehost.com/?fid=4349826312261783904

thx!

I had no recovery and used flash_all.bat expecting to factory reset (including data), but it just updated my room and all my data (files, accounts, lockscreen, fingers, logins etc) was keeped.. Device is "ok" is this normal?

when I run the script flash.all.bat nothing happens how it does
Envoyé de mon Mi A3 en utilisant Tapatalk

Did you put your files in adb folder?

I unzipped the folder and I put it on my desktop in the same folder or I have minimal adb and fastboot
Envoyé de mon Mi A3 en utilisant Tapatalk
View attachment 5010703
I succeeded by installing Platforms tools on my pc and putting everything in the corresponding folder

Hello, can I install the .tgz version with MiFlash Tool?
Edit: I tried to flash the .tgz firmware with MiFlashTool but apparently it can't be installed this way. I'm going to try fastboot now. Let's see how it goes.
Edit 2: I ended up flashing the .tgz official April update of EU ROM. Switched from global to EU using miflash tool.

all instruction to run in cmd
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase vendor_a
fastboot erase vendor_b
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash product_a product.img
fastboot flash product_b product.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

Post updated to include Fastboot V11.0.15.0.QFQMIXM

edwaine said:
Post updated to include Fastboot V11.0.15.0.QFQMIXM
Click to expand...
Click to collapse
I am in stock A10 11.0.1.0 euro version. Can I install the global stock fastboot 11.0.15.0 without lose data?

Firmmware Flash Bash Script

Hello, all. For those of you running Linux, I made a bash script to consolidate all the fastboot commands required to flash the stock firmware into one command. The command to run the script. After downloading, you may have to run
chmod +x flashscript.sh
to make it executable. Just place it in the directory of all the firmware files, make it executable and run it with
./flashstock.sh
Watch it in action here. https://youtu.be/g-ss1qKO7Vg
Well XDA says invalid file when I try to upload it, so here's the file in text form.
Enjoy.
Starts on the next line with #! and runs to the end. Make into .txt file, make executable, place in stock firmware directory and run with ./flashstock.sh
#!/bin/bash
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot bootloader

Try this change the zip to bat

roadkill42 said:
Try this change the zip to bat
Click to expand...
Click to collapse
https://mega.nz/file/uFpmBCpI#Ntr8gegku2TxsZiebK-C6sfQxWG7Fl9_J0fCqHLMFmw or this

I have the Verizon model , will this script work with my phone ?

cortez52 said:
I have the Verizon model , will this script work with my phone ?
Click to expand...
Click to collapse
That I don't know good question though have u checked on tellagram group some one in there might know

Just so u guys know , I've seen the Verizon model on eBay romed an rooted so the bootloader can be unlocked !
Sent from my moto g(7) power using Tapatalk

cortez52 said:
Just so u guys know , I've seen the Verizon model on eBay romed an rooted so the bootloader can be unlocked !
Click to expand...
Click to collapse
Somebody apparently some one hasn't released on how might be that they used a program to refashe hole thing with different factory imge to gei it done

cortez52 said:
I have the Verizon model , will this script work with my phone ?
Click to expand...
Click to collapse
Have a look inside your firmware.zip, there is a flashfile.xml which contains all commands you must use with your phone.