Moto Z boots only in Recovery / TWRP only - Moto Z Questions & Answers

Moto Z boots only in Recovery / TWRP only - Moto Z Questions & Answers

I made a not-so-smart-decision and tried to update the most recent OTA via Flashfire.
Probably I took a wrong path in Flashfire or missed an important option. However, this happened:
Code:
…
FileNotFoundException: /dev/block/platform/624000.ufshc/by-name/… (Read-only file system)
…
Rebooting...
Error have been detected. Delaying reboot for three minutes in the hope you'll notice. You could reboot manually, of course
And since then the mobile just reboots into Recovery / TWRP.
I tried to reset it completely now via
sudo fastboot flash boot boot.img
sudo fastboot flash oem oem.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash system system.img_sparsechunk.6
sudo fastboot flash system system.img_sparsechunk.7
sudo fastboot flash system system.img_sparsechunk.8
sudo fastboot flash system system.img_sparsechunk.9
sudo fastboot flash system system.img_sparsechunk.10
sudo fastboot flash system system.img_sparsechunk.11
sudo fastboot flash system system.img_sparsechunk.12
Click to expand...
Click to collapse
and the image RETBR/XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (I have the GER/EU model but the last time I had a problem with the device people recommended the BR image).
This doesn't help so far. And I don't know why. I also resetted cache, userdata etc.
I didn't flash recovery so far because I fear to brick the Moto Z totally.
Nothing helps so far. It still boots into TWRP.
Does anyone have any idea what I could to to rescue the mobile?
Thank you in advance and have a nice day
EDIT: Okay, flashing the stock recovery helped.
How can I mark this thread as solved?
EDIT 2: As I flashed the (old) stock ROM now, I thought OTAs should be possible but they result in an error. But I don't have TWRP or root installed yet. Do you have any idea why that could be?

Related

[help]phone is bricked!!!

hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it

macszxc said:
hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it
Click to expand...
Click to collapse
Use a SD card to flash the ROM using TWRP. Also check on TWRP that the internal and external memory are mounted.
Sent from my XT1650 using XDA-Developers mobile app

Or ADB Sideload. Simple stuff

macszxc said:
hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it
Click to expand...
Click to collapse
Don't panic! As long as you can get to recovery or bootloader you aren't bricked
I would restore to stock and try everything again.
Here's the stock US ROM https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
There's a link around here for stock EU ROM if you need that instead.
Use these commands from an ADB prompt:
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

thx guys it worked with flashing stock rom

macszxc said:
thx guys it worked with flashing stock rom
Click to expand...
Click to collapse
I went through the exact same thing, wipe the whole system out, couldn't reboot even after flashing another ROM, then I figured, the boot.img must have gone missing, so I just fastboot flash boot boot.img (the one from within the stock ROM), then the phone booted

beaubin said:
I went through the exact same thing, wipe the whole system out, couldn't reboot even after flashing another ROM, then I figured, the boot.img must have gone missing, so I just fastboot flash boot boot.img (the one from within the stock ROM), then the phone booted
Click to expand...
Click to collapse
I'm ever more of the opinion that our Z is a device very hard to seriously brick...

Prfndhatrdofman said:
Don't panic! As long as you can get to recovery or bootloader you aren't bricked
I would restore to stock and try everything again.
Here's the stock US ROM https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
There's a link around here for stock EU ROM if you need that instead.
Use these commands from an ADB prompt:
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
Click to expand...
Click to collapse
Hello, can you give me the EU stock rom, and please for god's sake don't give me this file factory link because this website is downloading slower to force me to buy their premium ****, thanks.

Phone messed up.

Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..

You need to flash back full stock ROM for your device. Had same issue. But that's if you are downgradable to MM roms

tafarelli said:
Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..
Click to expand...
Click to collapse
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?

Ok I have tried.
I flashed http://www.filefactory.com/file/6ht...ubsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip using following commands:
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 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 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 oem config carrier T-2
fastboot oem fb_mode_clear
Phone booted to mm stock (build number MPL 24.246-17) but I already had one reboot few minutes after.
Any suggestions?

kaxuna1 said:
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?
Click to expand...
Click to collapse
I tried with cm but it's not helping.

Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..

tafarelli said:
Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..
Click to expand...
Click to collapse
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?

kaxuna1 said:
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?
Click to expand...
Click to collapse
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..

Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
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 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 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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.

Hello @tafarelli what versión bootloader have your ?? Very thanks
Downgrade the Nougat at Mm ?
Regards

I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..

tafarelli said:
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..
Click to expand...
Click to collapse
Yes I tried and it's been a 12 hours without reboot so thanks friend you saved me... I will try that nougat method you posted bello ???
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
tafarelli said:
Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
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 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 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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.
Click to expand...
Click to collapse
??????

tafarelli said:
I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..
Click to expand...
Click to collapse
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards

iron maiden said:
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards
Click to expand...
Click to collapse
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.

tafarelli said:
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.
Click to expand...
Click to collapse
Hello my Moto z is in nougat but I was wondering if you had bootloader Nougat and could return to forgive MM if I made you believe that it was in brick my phone sorry for my English there is no image factory of the last version? NPL25.86-17-3 " I installed this by adb sideload but I like to install the whole image thanks
regards

Boot Loop

Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
I've tried flashing stock firmware from 6.0.1 then flashing ota through side load
Flashing other countries firmware (which always ends in fail messages)
I've tried multiple rom from the forum which just loop.
I've spent about 6 hours trying different combinations of recovery, boot and other images with no luck.
Any help is appreciated.
Sent from my iPhone using Tapatalk

criptix said:
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!

HippieFlasher said:
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
Click to expand...
Click to collapse
Dude, you are awesome. Worked like a charm. Was missing fastboot getvar max-sparse-size andbfastboot oem fb_mode_set plus I was flashing the modem after the chunks. Thanks again!
Sent from my iPhone using Tapatalk

Anytime! Glad I could help!

[FASTBOOT ROM] OREO Retail OPS27.76-12-25 (April) using Fastboot

Hi all, i have found this on Motozbrasil Blogspot.
It reported XT1710-01, XT1710-02, XT1710-06, XT1710-07, XT1710-09 e XT1710-10 models as working, but my XT1710-08 works too (see details in this post).
>>>> All credits and thanks go to motozbrasil and its staff. It is not my creation, i have just shared and reported my personal experience with my XT1710-08, not listened on that site.
A special, big, superb thanks to Junior Passos @Junior Passos the op of the motozbrasil thread. <<<
Basical steps:
1) Install drivers (Win) and reboot pc;
2) Unzip firmware and ADB + FASTBOOT - MZ2PLAY in the same folder (thanks to htcmania for package);
3) Put your phone in fastboot mode (Vol down + Power) then Connect to pc, waiting for drivers if needed;
4) Double click on z.bat (edit it with your own commands or use my zips attached changing "mfastboot" voices with "fastboot", so delete "m" from every single command), press a button.
Profit.
We needed a retail fastboot Oreo rom, so here we are.
All at your own risk.
Good luck.
Due to motozbrasil site down on link posted, i linked new adb fastboot and Installer. As soon as possibile i will change and upload installers attached.
Other links for rom only, here (thanks @thedoginthewok):
MEGA:
https://mega.nz/#!Y51hDRRQ!fxS5qoi2rklgtyQP5ydpcd7nM7qIl-wbsd9zJIF6doQ
Google Drive:
https://drive.google.com/file/d/1kyr8AHFZKv5-ASmCEpGHc8CqGgJFc6YO/view
I advice you to proceed over Windows, but in case...
> On Linux
Linux doesn't need drivers.
How to install adb/fastboot on linux, macos, win (depends on your distro): https://www.xda-developers.com/install-adb-windows-macos-linux/
If you are under Ubuntu the easiest way for installing adb-tools is (from terminal):
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Command under Terminal (Win/Linux) are:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash 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
In some cases (for example XT1710-08) is useful to skip (if you come from NPSS26.118-19-1-6):
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
If you pass directly from ZUI skip also:
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Those for preserving signal and data connection.
---
If you have a corrupted boot.img and you are not able to flash (like bangood or other shops do with chinese model), you first have to give that:
fastboot flashing unlock
Click to expand...
Click to collapse
Hope is useful.
Link above are for Win (1st) and Linux (2nd)**.
** if you use attached .sh remember you have to connect you phone in fastboot mode to pc and then double click on it in the same folder you have unzipped firmware. Attached .bat and .sh files evading erase modemst1 and st2, so it is good for some brand device, not for other.
Remember, all at your own risk.
Thanks @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
About Magisk, you could give a thanks to Fabio Feher:
Fabio Feher said:
It work for me:
1: Reboot into Bootloader
2: ADB Flash TWRP
3: Start Recovery (TWRP)
4: Enter in ADVANCED > TERMINAL
5: Run commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6: Flash Magisk
7: Reboot.
Click to expand...
Click to collapse

It should work. Unfortunately,I'm already using Oreo. Otherwise,I will try this fastboot ROM.

HTCDevil said:
Hi all, i have found this:
http://motozbrasil.blogspot.it/2018/05/firmware-moto-z-play-xt1710-firmware.html?m=1
All credit and thanks to motozbrasil and its staff.
I will try it on my XT1710-08, although not in the list on the site.
We need a retail fastboot Oreo rom, so here we are.
All at your own risk.
Good luck.
Click to expand...
Click to collapse
If possible , could you please upload the firmware on google Drive , because i am not able to download oreo firmware from Your given link, it downloads for about 100MB and then the download process fails.

flashnub said:
If possible , could you please upload the firmware on google Drive , because i am not able to download oreo firmware from Your given link, it downloads for about 100MB and then the download process fails.
Click to expand...
Click to collapse
I could try

I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.

Thank you
thedoginthewok said:
I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.
Click to expand...
Click to collapse
Hey thanks for Uploading it to Google Drive .
I have successfully loaded the Oreo Firmware, no hicc-ups at all, procedure went smooth.
Now my Moto Z2 Play XT1710-10 is running Oreo

thedoginthewok said:
I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.
Click to expand...
Click to collapse
Thanks, i edit first post.
Good flash guys

flashnub said:
Hey thanks for Uploading it to Google Drive .
I have successfully loaded the Oreo Firmware, no hicc-ups at all, procedure went smooth.
Now my Moto Z2 Play XT1710-10 is running Oreo
Click to expand...
Click to collapse
Nice to see, no thanks for me

Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?

Face1ess said:
Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?
Click to expand...
Click to collapse
Data is not wiped.

For those who were looking for fastboot commands here they are:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash 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

HTCDevil said:
Nice to see, no thanks for me
Click to expand...
Click to collapse
hey thanks mate, you were the reason i even thought of trying to Flash the Firmware first.

Face1ess said:
Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?
Click to expand...
Click to collapse
Users have tested it and said you don't lose your /data

I've updated my 09 successfully without loosing data.

Works for my 09 without loosing anythings. Tkx .

Vavooon said:
I've updated my 09 successfully without loosing data.
Click to expand...
Click to collapse
Great, thanks for info

Niiiicee, updated using your method and everything works nice and smooth. Haven't lost anything either! I hope it doesn't break the OTA

I can also confirm - the data and settings after the update are not touched
09 model, reteu

I have a moto z2 play 7.1.1. NPSS26. 118-22 and the XT1710-09 model. This guide work on my smartphone?

oliondo said:
I have a moto z2 play 7.1.1. NPSS26. 118-22 and the XT1710-09 model. This guide work on my smartphone?
Click to expand...
Click to collapse
It should work without any problem.
Works on my xt1710-08, i evade fastboot erase modemst1 and modemst2.

[ROM][STOCK][RETAIL] Official Stock Pie 9 [updated March 6th]

Hi guys,
Did not see anyone here on XDA who uploaded recently leaked OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
06.03.2019, THE NEWEST PPW29.116-20 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1Axk870qsui9w3TnnRQM9pt618CQ0CnHz
MIRROR: https://mega.nz/#!0ZUyTAqI!XXPwj0mcsGs0wLFwxwX8V0OeFXgCe-NXf-2VbDvr5Nc
OLDER BUILD: PPW29.116-16 FIRMWARE DOWNLOAD (RETAIL) - BE CAREFUL, IT BREAKS SAFETYNET ON EUROPEAN G6+ VARIANTS!
DOWNLOAD: https://drive.google.com/open?id=1F0SFwVyXgy3ZixL36W6xwxjqPJAwiDus
MIRROR: https://mega.nz/#!VJ8xEYRT!rb476WxlV099PVJrLwbFIr1Z3XNjo89sO5MU-HfPzMQ
OLDER BUILD: PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
--- If you don't want to erase all your phone data, use script from G6PlusFlashPieOfficial_NoErase.zip. This will upgrade your G6+ to Android Pie without erasing data. ---
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).

Screenshots.
PS. Digital Wellbeing installed via Magisk.

My brother has a Moto G6 Plus (bought in Europe) without root, will he be able to update it without loosing his data?
Thanks in advance guys.

Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot reboot
This is normaly how i update my G6 Plus and never expierence problems......

cdfreak said:
Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot reboot
This is normaly how i update my G6 Plus and never expierence problems......
Click to expand...
Click to collapse
Exactly like this. 
 @cyberon these commands are for your brother.

rafikowy said:
Screenshots.
PS. Digital Wellbeing installed via Magisk.
Click to expand...
Click to collapse
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?

thump said:
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?
Click to expand...
Click to collapse
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.

smitharro said:
It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).
Click to expand...
Click to collapse
which file i need to do the 2nd method and where can i download it?

rafikowy said:
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.
Click to expand...
Click to collapse
Just rechecked and found my System Updates page no longer gives the "system integrity" error either. Still do get the "verity" error, but seems of no concern. Cool.

giorgis91 said:
which file i need to do the 2nd method and where can i download it?
Click to expand...
Click to collapse
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU

smitharro said:
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU
Click to expand...
Click to collapse
Will it wipe the phone ?

giorgis91 said:
Will it wipe the phone ?
Click to expand...
Click to collapse
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'

Suggestions
rafikowy said:
Hi guys,
Did not see anyone here on XDA who uploaded recently released OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin[PHP][/PHP]
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
I place an "m" in front of fastboot to use mfastboot.
Get the mfastbootv2 it's best for flashing this way imo
Good work buddy.

What's the command erase carrier for?

smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
giorgis91 said:
Is that multilang or only in english?
Click to expand...
Click to collapse
smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english

giorgis91 said:
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english
Click to expand...
Click to collapse
All stock ROMs are multilingual. So Italian shouldn't be a problem.

what dos this mane: Verity mode is set to disabled when you boot the phone up?

cdfreak said:
what dos this mane: Verity mode is set to disabled when you boot the phone up?
Click to expand...
Click to collapse
A short explanation:
dm-verity
transparent integrity checking for block devices
read error if block integrity check fails
try to recover damaged blocks (from Android 7.0)
useful for read-only partitions like*system
fundamental part of*verified boot*on Android
Verified boot
device software integrity based on hardware root of trust
Boot chain (simplified)
verify*bootloader*using a hardware root of trust
bootloader*verifies*boot*and*recoverypartition
kernel*verifies*system*partition
uses dm-verity for the integrity checks once execution has moved to the boot partition

Hmmm. For some reason I get "Server error" in play store. And autobrightness jumps up and down every few seconds. Have tried returning to oreo and reflashing/factory resetting to no avail On reteu.
EDIT: Hmm also get the error in oreo now Anyone know whats up? Came from Lineage 16.

Better Mobile App

welcome