HI Everybody Who Got The RETUS Variant Of The Moto G7 Power.
And Want's To Get Last Android 10 Q August Security Patch.
I Know We Still Are Running PIE For Some Weird Reason So This IS A Safe Way To Get In Sync.
And Get Last Android Q Stock ""Official"" Motorola Firmware OCEAN_QPOS30.52-29-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml-SOAP
Yes I Call It SOAP , Well Im Using The Method That People Who Took The Test SOAK. Of Android Q In Brazil. So What They Do Was Just Flash 4 *.img files via fastboot having android 9 pie installed on their devices this was really safe back then and now because we are not touching the bootloader so there is no way to brick your moto G7 Power RETUS Variant.
So Here Down Is The FILE Which Contains the images that you need to flash after clean flash stock pie and boot twrp.img and flash copyparts-AB.zip if you have this device for long time you already know the drill so get those files first .
so last pie stock is for "RETUS" =
OCEAN_PPOS29.114-134-7-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
you can get it on Rescue and Smart Assistant (LMSA) , just put your motorola g7 power -5 variant on fastboot mode and connect it to the pc in windows and click on Rescue then it will Detect your Device REAL Firmware then start the flash but just let it Download The Big 1.8 G file then look in the Download Dir Folder And Move The Firmware From There To Other Place and then Drop On That Folder fastboot-adb-tools-minimal
and start flashing with this commands =
#!/bin/bash
time clear
time fastboot flash partition gpt.bin
time fastboot flash bootloader bootloader.img
time fastboot flash modem_a NON-HLOS.bin
time fastboot flash fsg_a fsg.mbn
time fastboot erase modemst1
time fastboot erase modemst2
time fastboot flash dsp_a adspso.bin
time fastboot flash logo_a logo.bin
time fastboot flash boot_a boot.img
time fastboot flash dtbo_a dtbo.img
time fastboot flash system_a system.img_sparsechunk.0
time fastboot flash system_a system.img_sparsechunk.1
time fastboot flash system_a system.img_sparsechunk.2
time fastboot flash system_a system.img_sparsechunk.3
time fastboot flash system_a system.img_sparsechunk.4
time fastboot flash system_a system.img_sparsechunk.5
time fastboot flash system_a system.img_sparsechunk.6
time fastboot flash system_a system.img_sparsechunk.7
time fastboot flash system_a system.img_sparsechunk.8
time fastboot flash system_a system.img_sparsechunk.9
time fastboot flash system_b system_b.img_sparsechunk.0
time fastboot flash system_b system_b.img_sparsechunk.1
time fastboot flash system_b system_b.img_sparsechunk.2
time fastboot flash vendor_a vendor.img_sparsechunk.0
time fastboot flash vendor_a vendor.img_sparsechunk.1
time fastboot flash oem_a oem.img
time fastboot flash oem_b oem_other.img
time fastboot erase userdata
time fastboot erase DDR
time fastboot oem fb_mode_clear
time fastboot set_active a
time fastboot reboot-bootloader
sleep 5
time fastboot getvar max-sparse-size
time fastboot oem fb_mode_set
time fastboot flash partition gpt.bin
time fastboot flash bootloader bootloader.img
time fastboot reboot-bootloader
sleep 5
time fastboot flash modem_a NON-HLOS.bin
time fastboot flash fsg_a fsg.mbn
time fastboot flash dsp_a adspso.bin
time fastboot flash logo_a logo.bin
time fastboot flash boot_a boot.img
time fastboot flash dtbo_a dtbo.img
time fastboot flash vendor_a vendor.img_sparsechunk.0
time fastboot flash vendor_a vendor.img_sparsechunk.1
time fastboot flash vendor_b vendor.img_sparsechunk.0
time fastboot flash vendor_b vendor.img_sparsechunk.1
time fastboot flash oem_a oem.img
time fastboot flash oem_b oem.img
time fastboot oem fb_mode_clear
time fastboot reboot-bootloader
sleep 3
time fastboot getvar all
time fastboot reboot
after the system reboot don't connect to internet or set password pins or fingerprints or account just finnish the setup soon as possible enter in Developers Options And Activate USB Debugging > conect to the pc and run adb reboot bootloader
Then Now ********
fastboot boot twrp.img
boot the twrp recovery img and flash copyparts-AB.zip And Avoid Bricking.
Continue The Next STEP > Download This File . =
https://mega.nz/file/J5cxFYzD#TwI9_JFeiDXTGZzRY01IWJFmydayu9o10rzhsVjLwjg
to extract on linux =
tar xJpf OCEAN_QPOS30.52-29-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.tar.xz --xattrs-include='*.*' --numeric-owner
For Windows You Can Use 7-zip or Winrar.
then flash with this commands >
#!/bin/bash
time fastboot set_active a
time fastboot getvar max-sparse-size
time fastboot oem fb_mode_set
time fastboot flash boot_a boot.img
time fastboot flash boot_b boot.img
time fastboot flash dtbo_a dtbo.img
time fastboot flash dtbo_b dtbo.img
time fastboot flash logo_a logo.bin
time fastboot flash logo_b logo.bin
time fastboot flash system_a system_a.img
time fastboot flash system_b system_b.img
time fastboot flash vendor_a vendor.img
time fastboot flash vendor_b vendor.img
time fastboot erase DDR
time fastboot erase userdata
time fastboot oem fb_mode_clear
time fastboot reboot bootloader
sleep 5
time fastboot getvar all
time fastboot -w
time fastboot reboot
That ^ Can Be Used As bash shell script or just Copy&Paste On The Terminal In The Same Dir Where The Files Are , if is in windows remove "time" and add to fastboot at the end the extension .exe
DONE Then Now You Can Enjoy STOCK Q.
Thank's For Reading And Good Luck Who Try's This IS REALLy SAFE JUST DONT FORGET TO FLASH COPYPARTS-AB.zip.
IF Bricks "Bricked In The Name OF Science ." Don't Blame "ME" Blame Science.
UPDATE August Security Patch Moto G7 Power Stock Q For Retus Safe Upgrade.
Friday, August 28 2020
OCEAN_QPOS30.52-29-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt
BUILD REQUEST INFO:
Build Fingerprint: motorola/ocean/ocean:10/QPOS30.52-29-5/0fb90:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.201.4.ocean.retail.en.US
Model Number: moto g(7) power
Android Version: 10
Build Id: QPOS30.52-29-5
SW Display Build ID: QPOS30.52-29-5
Build Date: Tue Jul 28 13:01:40 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.30.201.4.ocean.retail.en.US
Version when read from CPV: ocean-user 10 QPOS30.52-29-5 0fb90 release-keys
AB Update Enabled: True
Full Treble Enabled: True
This is my first a/b device, and without this guide, i would have flashed as if this was an a-only device and probably would have messed something up. Thanks for this, it worked perfectly. Enjoying 10 now
One note that should be added, in order to get cts to pass, you need to use the magiskhide prop config module and set it to our android 9 fp. RETUS using q will not pass cts without that change.
palmbeach05 said:
One note that should be added, in order to get cts to pass, you need to use the magiskhide prop config module and set it to our android 9 fp. RETUS using q will not pass cts without that change.
Click to expand...
Click to collapse
If u flash new 9 retus I didn't need to run the props but did any ways
Good Lord! That's a lot of work to flash over to Q! There has to be an easier method. Can you describe more on how to do the 4 *.img file flash method? Also do you have to erase userdata? I just unlocked & flashed my Metro G7 power to retus to allow Verizon sim to read. Will have to wait for an update method as I'm not ready to erase everything again. Good work though!
roadkill42 said:
If u flash new 9 retus I didn't need to run the props but did any ways
Click to expand...
Click to collapse
That might be the difference then. I went from June Android 9 OTA without reflashing the fw, to a/b copy zip, then to flashing the q fw from above.
I just Uploaded The Blankflash for Pie 9 and for 10 Q .
I hope no one bricks but follow what i wrote and no one will have any problems , There is The CopyPartitions-AB.zip never forget to flash it after flash stock pie. And "NO" to Clarify No There IS no Need To Flash Any Custom Kernel On This Firmware.
Hey what about for the regular Moto g6? Can you please make a separate post on it telling me how to flash the latest stock firmware for the us retail because i cannot hear audio when calling with the defualt dialer and instead i have to use a different app and that is very inconvenient. Please, someone make a thread on RETUS channel for moto g6 stock firmware flash with all steps as well as the files and code for executing the code. Or DM/PM me. PS: i am only 15 and i shouldnt have tampered around with my device but i badly wanted more customization so i decided to do so without my dads persmission and now i am stuck here with call audio not working. any help is greatly appreciated.
smartasiankid said:
Hey what about for the regular Moto g6? Can you please make a separate post on it telling me how to flash the latest stock firmware for the us retail because i cannot hear audio when calling with the defualt dialer and instead i have to use a different app and that is very inconvenient. Please, someone make a thread on RETUS channel for moto g6 stock firmware flash with all steps as well as the files and code for executing the code. Or DM/PM me. PS: i am only 15 and i shouldnt have tampered around with my device but i badly wanted more customization so i decided to do so without my dads persmission and now i am stuck here with call audio not working. any help is greatly appreciated.
Click to expand...
Click to collapse
BTW my discord is badassrajesh508#1529
do agree all these guides help on XDA .that's what i do read an research before attempting anything new.these newer a/bdevices require more care and work to flash custom roms and stuf like that.
will this work for international version like 1955-2.
mrk2815 said:
do agree all these guides help on XDA .that's what i do read an research before attempting anything new.these newer a/bdevices require more care and work to flash custom roms and stuf like that.
Click to expand...
Click to collapse
NVM I figured that most of them have wrong modem versions.
Related
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!
Hello all!
So I got tired of waiting for the latest update to hit my phone so I figured I would do it manually. After plenty of experience with Moto phones I gathered that the official RETAIL files should work with all of the GSM versions of the Moto Z2 Play. This is confirmed to work with both XT1710-01 and XT1710-07, but is likely to work with others (but not the US Verizon Model). For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
As usual, you take full responsibility for anything you do to your phone, but since your bootloader is locked, this should be fairly low risk, barring some sort of power loss mid-flash.
How to:
1. Download & Install Motorola Drivers from XDA.
2. Download & extract stock rom from here.
3. Use mfastboot/fastboot to run the following commands/run the attached .bat file. (Hint: make sure fastboot files are in the same directory as the the ROM files and .bat file).
3a. If you need more help on mfastboot or fastboot, look here.
Code:
echo off
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash Start
echo -------------------------------------------------------------------------
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash End
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
4. Enjoy!
Hope this helps!
but how is obtained stock rom?
For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
Click to expand...
Click to collapse
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
timster01 said:
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
Click to expand...
Click to collapse
I had no problem flashing with a locked bootloader. Didn't even have to wipe. What error did you get when you tried to flash?
I am wondering if it works on an XT1710-08 model...
hello friends ??
I am from Peru looking for yesterday from several corners of the web I found the stock ROM of the #MotoXplay ..well I now use a #MotoZplay but I also have a #MotoXplay very well preserved ..
watching on your Sim tray I noticed that there was the sim2 slot obviously blocked by my telephone operator.
the ROM I found is dual SIM and is for the region latam
I download and install it .. so far goes very well with its short 2gb ram I leave the steps and the link + the commands and some screenshots..
And yes, now I have 2 IMEI..
although it does not read the sim2 there will be some solution later.
Sorry for my bad English..
This my first post..
:V
The process is with ADb_Fastboot
ROM stock 7.1.1.
https://androidfilehost.com/?fid=889964283620759436
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 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 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
Screenshots
https://pin.it/VMEIdiO
https://pin.it/1VEnQkP
https://pin.it/UiIcyiO
https://pin.it/8ea8tfO
sorry but still not loading images xda
https://forum.xda-developers.com/chef-central/android/install-android-nougat-7-1-1-official-t3691943
Perfect & Thanks!
You are awesome, no problems on an xt1563, only the commands:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
they give error, but they are not problem to install the update. :good::good::good::good:
elvizpdx said:
looking for yesterday from several corners of the web I found the stock ROM
Click to expand...
Click to collapse
It was published already, a day before your post.
[Evert] [Stock] Firmware - Return to Stock.Disclaimer
I can not be held responsible for any type of problem with your device. This information is for the sole purpose of reporting and is delivered "as is". Only the tests will confirm if everything works well or does not work at all, proceed with caution.
Recommendations.
Make sure to back up all information, device data, and (optional) persistence partitions of the device.
Always use common sense, and confirm that you do not have an error message in the console. Verify that things are done correctly.
Requirements
Make sure that the drivers and everything related to connectivity is working properly. The official Motorola drivers work fine, and the google fastboot drivers too. Look for tutorials on installing the fastboot driver if your computer is not detecting it properly, the tutorials of other moto models (eg moto g5 plus) on the drivers and others work just as well.
All this process spends time and of course the battery of your device, make sure you have a good battery (50+) and stay connected as much as possible.
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware, but it depends on each one...
All the commands and others are done from the fastboot utility, you can find it in https://developer.android.com/studio/releases/platform-tools.
Process
Download the correct firmware for your device.
Right now there are not many firmware available, as time passes the list will grow.
One of several sites is LOLINET.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAIL/
(If not already installed, make sure of ..) Install the drivers and download the fastboot utility. And of course, verify that the driver works properly. It will be done later.
Extract the fastboot utility, and the firmware within the same directory.
To verify the connection, enter the bootloader of your device, connect it with the PC. On the PC; run the console, go to the folder where you extracted the fastboot utility, and type fastboot.exe devices, you should see the listed device in the console.
If the connection works correctly and you notice nothing strange, you can start the process.
Open the console in the directory where the fastboot utility is on the firmware files, there should be no more folders inside. (In this case you should adjust the path of the files in the commands). And write the following commands, verify that you do not have errors.:
Warning,
The commands listed below as "optional" do not necessarily have to be executed, but to be completely safe, execute them all, as long as you have the right firmware.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (optional)
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1 (Optional)
fastboot erase modemst2 (Optional)
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase carrier (Optional)
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
[I][/I]
Press the Power button, and wait a bit.. It will take a few minutes to start.
If you hear "Hello moto", congratulations you are in Stock (and everything "should work fine").
Notes
If your firmware has more or less sparsechunk files (eg, sparsechunk.3 or img_sparsechunk.7), run them all.
The bootloader will remain unlocked.
If all this was helpful, I hope your thanks.
With love by iGor.
And how remove verity Mode enabled?..and a black screen saying phone flashed with different software
IGorMcLven said:
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware
Click to expand...
Click to collapse
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
rybshik said:
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
Click to expand...
Click to collapse
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Dual SIM XT1926-7: firmware and TWRP issue
lcmp said:
I have the same phone.
Before you flash your phone make sure that you have a backup of :
EFS and Persist partitions
Click to expand...
Click to collapse
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
rybshik said:
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
Click to expand...
Click to collapse
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
TWRP decryption issue
lcmp said:
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
Click to expand...
Click to collapse
for which firmware build? Pie or Oreo?
In my case, I was able to back up with twrp-3.3.1-0-evert.img before flashing Magisk. And I was able to Magisk-root with twrp-3.3.1-0-evert.img successfully as well.
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
So I tried twrp-3.2.3-42-evert.img and it worked.
Is it possible to permanently remove encryption?
rybshik said:
for which firmware build? Pie or Oreo?
Click to expand...
Click to collapse
PIE
rybshik said:
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
Click to expand...
Click to collapse
I´m not an expert, but from what i know, You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition. Then your backups will succeed.
rybshik said:
Is it possible to permanently remove encryption?
Click to expand...
Click to collapse
I read it´s possible but i´m no expert on the subject. Why would you want to remove encryption? I think its a good feature
lcmp said:
You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition.
Click to expand...
Click to collapse
Does TWRP ask for a PIN during back up?
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
rybshik said:
Does TWRP ask for a PIN during back up?
Click to expand...
Click to collapse
What I noticed is that when TWRP 3.3 boots, it asks for your pin or unlock pattern in order to use that as the credential to get the decryption key and decrypt the data partition. TWRP 3.2 won't do this ( again, in my experience ) hence the back up fails because everything is encrypted.
This is how I noticed that force installing TWRP 3.2 was useless. it doesn´t ask for your pin or your unlock pattern so it doesn´t have a way of decrypting the data partition. Again this was my experience. A more advanced android / twrp user could give a definite answer.
rybshik said:
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
Click to expand...
Click to collapse
I think so, yes. If you don´t have a pin or unlock pattern in your phone, TWRP doesn´t have a way to "authenticate" and get the decryption key and decrypt the data partition. Again, I´m assuming this out of my own experience.
Hello, can anyone share me the persist file from a xt1926-6 please?
I am having an issue with this file and I don't know what to do now
Thank you
lcmp said:
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
Hello, how did you solve the persist issue? I have it corrupt and I don't know what to do
Thanks
lcmp said:
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Toonka95 said:
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Click to expand...
Click to collapse
You can, recently I posted a solution for this issue (i believe it's the same as yours)
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
The following are the official firmware commands
Code:
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
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
sd_shadow said:
The following are the official firmware commands
Code:
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
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
WoKoschekk said:
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
Click to expand...
Click to collapse
Yeah man it took me all day to try to get it all working again, the fix was i downloaded an older stock rom and it restored my IMEI, it had to be the older version though because the newer one would recover it. Anyways now i'm never erasing that carrier or modem if it's not really necessary.
revert xt1926-3 to factory (2020)
IGorMcLven said:
[Evert] [Stock] Firmware - Return to Stock.
Code:
...
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
...
Click to expand...
Click to collapse
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
tseeling said:
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
Click to expand...
Click to collapse
Needs Termux and python.
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.