Notice: you may download ROM version according to your build number. Do it only when you receive a notice to update after your phone is rooted.
Root will be removed during the process but you can regain it.
https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/
You can use your fastboot commands below to flash ROM
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 boot boot.img
fastboot flash dtbo dtbo.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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
(optional) fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
(optional) fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
You don't have to use "fastboot erase userdata" if you don't want to wipe. It's OK as it's minor update
Use "fastboot flash boot patched_boot.img" if you want to regain root. You can do it later. Grab original boot.img from ROM and patch it with Magisk. "patched_boot.img" is default name of output file and you can name it to whatever you like.
You can read full flashing commands opening "flashfile.xml" with Notepad++
Soft brick with AMZ_9.0_PPO29.114-16-5
I'm in a soft brick position where my Moto G7 (XT1962-1) is stuck in a boot loop. I'm interested in running these commands, but I'm concerned that I won't be able to get to true stock because there's no stock image for the AMZ variant of the phone @ mirrors.lolinet / firmware / moto / river / official. I've tried flashing the retail variant, which has the same build version as my phone via
Code:
fastboot flash boot boot.img
, but no luck. Do you know if running this list of commands would be safe to run on my AMZ phone against the files for the retail version?
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 boot boot.img
fastboot flash dtbo dtbo.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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
(optional) fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
(optional) fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
panmaj said:
I'm in a soft brick position where my Moto G7 (XT1962-1) is stuck in a boot loop. I'm interested in running these commands, but I'm concerned that I won't be able to get to true stock because there's no stock image for the AMZ variant of the phone @ mirrors.lolinet / firmware / moto / river / official. I've tried flashing the retail variant, which has the same build version as my phone via
Code:
fastboot flash boot boot.img
, but no luck. Do you know if running this list of commands would be safe to run on my AMZ phone against the files for the retail version?
Click to expand...
Click to collapse
this is the lastest for the amazon edition
XT1962-1_RIVER_AMZ_9.0_PPO29.114-16-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
do not flash retail
ptn107 said:
this is the lastest for the amazon edition...
do not flash retail
Click to expand...
Click to collapse
Thanks! I actually have tried this image already after flashing the retail version , but that didn't break it out of the boot loop either. A concern I had in running the longer comand was that the version listed here was at version PPO29.114-16-7, but my phone was @ PPO29.114-16-5.
I'm at a point where I don't have much (more) to lose, so I'll try running these commands tomorrow otherwise.
Success!
This worked for me! Thanks so much for the encouragement!
ptn107 said:
this is the lastest for the amazon edition
do not flash retail
Click to expand...
Click to collapse
Any considerations having TWRP installed?
Thanks for these instructions! I was wondering--if I've already flashed TWRP on the device, are the any additional steps required prior to or after the fastboot commands that you posted? I presume I'll need to re-flash TWRP afterwards, but I wanted to make sure that all goes smoothly getting back to stock. Thanks in advance.
Is it safe to take these updates? Does it change the bootloader version?
I'm trying to keep my phone on a bootloader that will be safe for any custom roms that might come out in the future.. (false hope?)
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
I'm still back on RETUS PP029.114-16 and the BL version (from fastboot) shows MBM-2.1-river_retail-b89272e-190116
Is this different for you guys that have moved up to PP029.114-16-5 or PP029.114-16-7 ?
skuppej said:
Is it safe to take these updates? Does it change the bootloader version?
I'm trying to keep my phone on a bootloader that will be safe for any custom roms that might come out in the future.. (false hope?)
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
I'm still back on RETUS PP029.114-16 and the BL version (from fastboot) shows MBM-2.1-river_retail-b89272e-190116
Is this different for you guys that have moved up to PP029.114-16-5 or PP029.114-16-7 ?
Click to expand...
Click to collapse
xt1962-1
PPO29.114-16-7
MBM-2.1-river_retail-b89272e-190228
PPOS29.80-61-2 river-retail build
ptn107 said:
xt1962-1
PPO29.114-16-7
MBM-2.1-river_retail-b89272e-190228
Click to expand...
Click to collapse
I see a newer zip file on the lolinet repository in the RETAIL directory. I downloaded the file. Here is the text from the txt file.
BUILD REQUEST INFO:
SW Version: river-user 9 PPOS29.80-61-2 b7f44 release-keysM632_11.47.01.85R
MBM Version: MBM-2.1-river_retail-535b1da-190401
Modem Version: M632_11.47.01.85R
FSG Version: FSG-8953-21.64
Build Fingerprint: motorola/river/river:9/PPOS29.80-61-2/b7f44:user/release-keys
CQATest App Version: 6.0.4
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.201.2.river.retail.en.US
Model Number: moto g(7)
Android Version: 9
Baseband Version: M632_11.47.01.85R
Build Id: PPOS29.80-61-2
SW Display Build ID: PPOS29.80-61-2
Build Date: Mon Apr 1 21:05:17 CDT 2019
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.29.201.2.river.retail.en.US
Version when read from CPV: river-user 9 PPOS29.80-61-2 b7f44 release-keys
AB Update Enabled: True
Full Treble Enabled: True
cou94114 said:
I see a newer zip file on the lolinet repository in the RETAIL directory. I downloaded the file. Here is the text from the txt file.
BUILD REQUEST INFO:
SW Version: river-user 9 PPOS29.80-61-2 b7f44 release-keysM632_11.47.01.85R
MBM Version: MBM-2.1-river_retail-535b1da-190401
Modem Version: M632_11.47.01.85R
FSG Version: FSG-8953-21.64
Build Fingerprint: motorola/river/river:9/PPOS29.80-61-2/b7f44:user/release-keys
CQATest App Version: 6.0.4
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.201.2.river.retail.en.US
Model Number: moto g(7)
Android Version: 9
Baseband Version: M632_11.47.01.85R
Build Id: PPOS29.80-61-2
SW Display Build ID: PPOS29.80-61-2
Build Date: Mon Apr 1 21:05:17 CDT 2019
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.29.201.2.river.retail.en.US
Version when read from CPV: river-user 9 PPOS29.80-61-2 b7f44 release-keys
AB Update Enabled: True
Full Treble Enabled: True
Click to expand...
Click to collapse
I won't be flashing that. Seems like a brick situation to me.
ptn107 said:
I won't be flashing that. Seems like a brick situation to me.
Click to expand...
Click to collapse
Agreed. I posted about the 80-61-2 version because I hadn't seen any other posts about it.
Given the build date (Apr 1 2019), it could be an April Fool's joke build.
cou94114 said:
Agreed. I posted about the 80-61-2 version because I hadn't seen any other posts about it.
Given the build date (Apr 1 2019), it could be an April Fool's joke build.
Click to expand...
Click to collapse
Some joke!
Just FYI.... I've been checking this repository for a while, and that build wasn't always there. On top of that, a quick check indicates it is the latest RET version. It's legit.
The modem is older than 29.114-16-7. If someone else wants to flash it and post a pic of 'system -> about phone -> android' that's cool.
Just flashed this... No problem. As I said.
I'm the RET version. Build date on -5 is Feb 1
Build date on -7 one is Feb 28
Here you go, just evidence that is safe guys lol
warBeard_actual said:
Just flashed this... No problem. As I said.
I'm the RET version. Build date on -5 is Feb 1
Build date on -7 one is Feb 28
Click to expand...
Click to collapse
I flashed the 29.114-16-7 files and the Security Patch level shows January 1, 2019. What is the security patch level for the 29.80-61-2 image?
ptn107 said:
xt1962-1
PPO29.114-16-7
MBM-2.1-river_retail-b89272e-190228
Click to expand...
Click to collapse
Thanks. So it does look like BL version changed from MBM-2.1-river_retail-b89272e-190116 to MBM-2.1-river_retail-b89272e-190228
Guess ya'll aren't too concerned about updating your BL version, eh?
I just know on my Moto X Pure you were hosed if you upgraded from MM (6.0) to N (7.0) and you couldn't revert your bootloader, and there were issues with the roms on 7.0 BL
I just got an update notification for 114-6-7-2 (security updates for April 1, 2019). The LMSA application is still pulling the 114-6-7 update zip.
Latest build is available with the LMSA application (RIVER_PPOS29.114_16_7_2_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip).
Related
Hi guys!
I have got the XT1621 and i have a lot of lag when i flash a nougat firmware through fastboot
But when i install marshmallow (23.4) and i update by ota to nougat (-14) it is very smooth!!
The problem is that i updated by induced ota from -14 to -14-4 nougat
The real problem is that the bootloader updated to .05 version and i cant flash marshmallow and update by ota to -14 because it would end in hardbrick!!
What can i do to downgrade??
If i hardbricked my moto g4 with intention, could i flash the -14 bootloader blankflash file? It could be a way to downgrade the bootloader
Any other idea of what can i do?
I recall you can downgrade to MM if you wish, just do not flash the GPT and bootloader partitions. Leave them as they are. That way, you'll avoid a hard brick (but you'll need to flash the latest firmware to re-lock your device).
Of course, you'll need an unlocked bootloader for this to work, and the appropriate stock ROM (a copy is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETAIL/) - I see XT1622 MPJ24.139-23.4 which matches what you had before (though I strongly recommend double checking it's the right firmware).
Then follow this guide to downgrade: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
If you're unable to download the script that's mentioned in the guide, you may try the following fastboot commands (note the absence of the locking, GPT and bootloader commands).
Code:
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 erase customize
fastboot erase clogo
fastboot reboot
This procedure will wipe your device and should revert your device to an MM baseband and system. As always, back up your data, move it off your device until you're done flashing.
File Name: XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-13_cid7_subsidy-DEFAULT_CFC.xml.zip
MD5: E5256ED0E689F6760E61F4DD534BA3C5
MBM Version: A0.4D
GPT: 05
Modem Version: M8992_1255331.29.01.88.02R
FSG Version: FSG-8994-01.94.03
System Version: 24.231.13.clark_retasia_ds.retasia.en.03
Blur Version: Blur_Version.24.231.13.clark_retasia_ds.retasia.en.03
Baseband Version: M8992_1255331.29.01.88.02R
Build Number: MPHS24.107-58-13
Build Date: Thu Dec 8 06:07:12 CST 2016
Build Fingerprint: motorola/clark_retasia_ds/clark_ds:6.0.1/MPHS24.107-58-13/8:user/release-keys
https://mega.nz/#!ZPAU2AoZ!JaC6v6Q4GFgfyJVtCccswO4LULe94qPwds5td715qU4
do you have any link to download just modem files of version 6?
i'm gonna flash xt1572_RETASIA_DS_7.0 on XT1570 chinese version which currently runs this retasia_ds_6.0.1
hagi_mostafa said:
do you have any link to download just modem files of version 6?
i'm gonna flash xt1572_RETASIA_DS_7.0 on XT1570 chinese version which currently runs this retasia_ds_6.0.1
Click to expand...
Click to collapse
i have no link just for modem.
just do flash boot and system files of 7.0's stockrom on xt1570,keep itself modem and fsg unchanged,it will work perfectly.
i have flashed 7.0_LA and 7.0_US_pure on my xt1570,all work perfectly.and now stay on 7.0_US_pure with dual sim.
hagi_mostafa said:
do you have any link to download just modem files of version 6?
i'm gonna flash xt1572_RETASIA_DS_7.0 on XT1570 chinese version which currently runs this retasia_ds_6.0.1
Click to expand...
Click to collapse
you can download the stockrom from the link(https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1572/ASIA) and extract it
zi_mo said:
i have no link just for modem.
just do flash boot and system files of 7.0's stockrom on xt1570,keep itself modem and fsg unchanged,it will work perfectly.
i have flashed 7.0_LA and 7.0_US_pure on my xt1570,all work perfectly.and now stay on 7.0_US_pure with dual sim.
Click to expand...
Click to collapse
so are the commands gonna be as following?:
fastboot erase system
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.XX
fastboot erase cache
fastboot erase userdata
fastboot reboot
hagi_mostafa said:
so are the commands gonna be as following?:
fastboot erase system
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.XX
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
not necessary to flash logo/recovery
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
.1
***
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
zi_mo said:
not necessary to flash logo/recovery
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
.1
***
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
very thanks to you, i successfully managed to upgrade my moto x style xt1570 chinese version dual sim to android 7 nougat with following code and rom:
XT1572_CLARK_RETASIA_DS_7.0_NPHS25.200-15-3_cid7_subsidy-DEFAULT_CFC.xml
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system 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 erase cache
fastboot erase userdata
fastboot reboot
Latest full firmware have posted from the Motorola Firmware Team. For fi at least it is inclusive of the Sept 2018 security patch.
Google FI
Amazon Prime Edition
Updated 10/9
Hi. Could someone tell me please is the opws28.46-21-9 on oreo 8.0 or 8.1? What's the difference between opw and opws software?
It's 8.1.
ptn107 said:
Latest full firmwares have posted from the Motorola Firmware Team.
https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC
Click to expand...
Click to collapse
Please, anyone can explain the name files?
brunopio said:
Please, anyone can explain the name files?
Click to expand...
Click to collapse
payton is moto retail
payton_amz is the amazon prime edition
payton_fi is the Android One version
ptn107 said:
payton is moto retail
payton_amz is the amazon prime edition
payton_fi is the Android One version
Click to expand...
Click to collapse
from your experience do you think the android one version is better than retail?
From the info file inside the Android One archive. This is the August 1 security update.
BUILD REQUEST INFO:
SW Version: payton_fi-user 8.1.0 OPWS28.46-21-8 7116 release-keysM660_7042.27.01.74R
MBM Version: MBM-3.0-uefi-455afa3-180726
Modem Version: M660_7042.27.01.74R
FSG Version: FSG-660-01.87
Build Fingerprint: motorola/payton_fi/payton_sprout:8.1.0/OPWS28.46-21-8/7116:user/release-keys
CQATest App Version: 6.0.3
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.241.11.payton_fi.google_fi.en.US
Model Number: moto x4
Android Version: 8.1.0
Baseband Version: M660_7042.27.01.74R
Build Id: OPWS28.46-21-8
SW Display Build ID: OPWS28.3.2
Build Date: Thu Jul 26 14:26:54 CDT 2018
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.28.241.11.payton_fi.google_fi.en.US
Version when read from CPV: payton_fi-user 8.1.0 OPWS28.46-21-8 7116 release-keys
AB Update Enabled: True
Full Treble Enabled: False
bluedragon12 said:
from your experience do you think the android one version is better than retail?
Click to expand...
Click to collapse
The AndroidOne version lacks the gesture navigation using the fingerprint reader and one or two features in the Moto app. Other than that they are basically the same close to stock android. I only used the A1 version never saw the need to switch. A1 has a better update cycle though and it's on 8.1.
I got the xt1900-4 openCL channel with OPWS27.2.3 (android 8.0)... ¿Can i install the PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zi version?
i didn't unlock my bootloader... i wanna flash the rom but i don't wanna unlock my bootloader...
RodBonzai said:
I got the xt1900-4 openCL channel with OPWS27.2.3 (android 8.0)... ¿Can i install the PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zi version?
i didn't unlock my bootloader... i wanna flash the rom but i don't wanna unlock my bootloader...
Click to expand...
Click to collapse
You can, but you'll lose OTA because of the different software channel.
abrfilho said:
You can, but you'll lose OTA because of the different software channel.
Click to expand...
Click to collapse
How do you flash without unlocking the bootloader?
TeamRainless said:
How do you flash without unlocking the bootloader?
Click to expand...
Click to collapse
Using fastboot commands, but not every rom will flash, I succeed flashing Android One over my X4 without unlocking, you just need the same security patch, if it's older will soft brick with locked bootloader.
You can follow the tutorial here for returning to stock rom, the latest available ROMs for Retail and Android One have August security patch.
abrfilho said:
Using fastboot commands, but not every rom will flash, I succeed flashing Android One over my X4 without unlocking, you just need the same security patch, if it's older will soft brick with locked bootloader.
You can follow the tutorial here for returning to stock rom, the latest available ROMs for Retail and Android One have August security patch.
Click to expand...
Click to collapse
Actually i flash the firmware via fastboot (the file flashfile.xml have the linecodes) ... i got Oreo 8.1 without issues (for the moment :angel
I'll let you know if I notice something strange in the next days
these are the lines of code that I use:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
abrfilho said:
Using fastboot commands, but not every rom will flash, I succeed flashing Android One over my X4 without unlocking, you just need the same security patch, if it's older will soft brick with locked bootloader.
You can follow the tutorial here for returning to stock rom, the latest available ROMs for Retail and Android One have August security patch.
Click to expand...
Click to collapse
What software channel are you on now? Are people getting OTA updates on the new channel? (Can't quite understand why they wouldn't...)
RodBonzai said:
Actually i flash the firmware via fastboot (the file flashfile.xml have the linecodes) ... i got Oreo 8.1 without issues (for the moment :angel
I'll let you know if I notice something strange in the next days
these are the lines of code that I use:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Click to expand...
Click to collapse
Where did you get the download? And were you already on the August update on 8.0?
RodBonzai said:
Actually i flash the firmware via fastboot (the file flashfile.xml have the linecodes) ... i got Oreo 8.1 without issues (for the moment :angel
I'll let you know if I notice something strange in the next days
these are the lines of code that I use:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Click to expand...
Click to collapse
Yes, the tutorial to return to stock have a script with the necessary commands, it's all through fastboot.
TeamRainless said:
What software channel are you on now? Are people getting OTA updates on the new channel? (Can't quite understand why they wouldn't...)
Where did you get the download? And were you already on the August update on 8.0?
Click to expand...
Click to collapse
Now I'm using LineageOS 16, but the software channel is hardware dependent, I'll try to explain to you why people with different software channels don't receive OTA, each software channel is like a server, they provide the software to the clients, the phones, each server act independent, retbr have one software, retus have other, reteu other and so on... If you put a ROM on your phone that your software channel don't have, like flashing Android One, a ROM that only retus have, on a retbr phone, the phone will lose OTA, because the software channel don't support Android One, even if you flash Android One, the software channel will remain the same and you can't change it.
You can find the Android One 8.1 and Retail 8.1 with August at AndroidFileHost, I have Android 8 with only June patch, retbr support this ROM and I think the others software channels, except retus and amz, support it too, and because of that.
You can find the file here, it's my folder: https://drive.google.com/open?id=1TLzouN4KKdxysxkMaBKEzlfg9-ptEiO_
If anyone was wondering, Xposed continues to cause bootloop on latest firmware
(deleted)
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
September 2018 OTA for Retail (retus sw channel) (Oreo 8.1):
Blur_Version.28.251.20.payton.retail.en.US
Click to "Download" and save as ZIP file.
Edit:
edited links
Comby_sk said:
Both files save as ZIP file.
Click to expand...
Click to collapse
Tried both and get "Access to dlmgr.gtm.svcmot.com was denied - You don't have authorization to view this page. - HTTP ERROR 403" (with Chrome)
Can you provide an alternative link?
Nevermind - Worked from a different PC.
Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
September 2018 OTA for Retail (retus sw channel) (Oreo 8.1):
Blur_Version.28.251.20.payton.retail.en.US
Click to "Download" and save as ZIP file.
Edit:
edited links
Click to expand...
Click to collapse
How can I apply this update with unlocked bootloader and magisk rooted X4?
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Change log?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Thanks a lot, my friend... Now I can root my Moto G7 River again! ?
How do I flash this .zip?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Tried to install on a xt1962-4 and it goes bootloop :c
MatheusDeFino said:
Tried to install on a xt1962-4 and it goes bootloop :c
Click to expand...
Click to collapse
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
ptn107 said:
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
Click to expand...
Click to collapse
How install?
Mathiusb said:
How install?
Click to expand...
Click to collapse
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 dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system 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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Unroot first?
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
eztechio said:
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
Click to expand...
Click to collapse
You can manually download and flash the new firmware and then patch boot with magisk again. You do not need to go back to stock first.
adb sideload
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Filename differences PPO vs PPOS
Does PPO vs PPOS in the filename mean that PPOS can be sideloaded and the other only via OTA or from internal?
ptn107 said:
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 dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system 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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Is this method to install for RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip or it is for Mathiusb's xt1962-4 version?
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Actually ignore my posts. I just read the flashfile.xml in the zip and it has the same steps. duh!
Fastboot 'waiting for any device'
A new Moto G7 XT-1962 US-Retail running the original ROM, unlocked, rooted, and with TWRP installed. It seems to be working okay but somehow during unlocking and setup, it no longer detects the SIM.
So I thought that flashing the most-recent update might also resolve the SIM problem at the same time. Steps from this forum were followed with a difference that I was using a Mac. The contents of the platform-tools (adb-fastboot) directory were combined with the extracted ROM zip files and the terminal launched from there. Like the Windows technique.
ADB works now and Fastboot had worked before using this same approach for the oem unlocking routine:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZY226JMG38 device
Now Fastboot (from platform-tools_r29.0.4-darwin.zip) returns "waiting…" and hangs:
Code:
$ fastboot device
< waiting for any device >
$ fastboot getvar max-sparse-size
< waiting for any device >
$ fastboot oem fb_mode_set
< waiting for any device >
$ sudo fastboot device
Password:
< waiting for any device >
Any suggestions about Fastboot and comments about fixing my undetected SIM appreciated. This flashing routine is a scary undertaking for this dummie.
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
eztechio said:
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
Click to expand...
Click to collapse
Thanks @eztechio, but the problem turns out to be the fastboot command itself. Only <waiting for device> in the code sample of my post.
---------- Post added at 11:32 AM ---------- Previous post was at 11:25 AM ----------
I stumbled across the answer to my main question elsewhere and hope this might be helpful to other Mac users.
In MacOS adb and fastboot commands must be preceded with "./" most of the time. Why the exception where some adb commands work without it I don't know.
Code:
$ adb devices
List of devices attached
ZY226JMG38 device
$ ./adb devices
List of devices attached
ZY226JMG38 device
$ ./adb reboot bootloader
$ ./fastboot devices
ZY226JMG38 fastboot
$ ./fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
With fastboot working now, it's on to this dummie adventuring into the ROM update…
Thanks @ptn107. Your fastboot steps worked like a charm. I'm now up to date on ROM Build PPOS29.114-134-2
A fresh, clean slate. Just had to install TWRP and Magisk again. My problem before of not detecting the SIM now resolved.
Just wish I could have retained my user apps and data through the upgrade process. Not executing fastboot erase userdata might have been the approach, but I didn't want to chance it.
eztechio said:
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Click to expand...
Click to collapse
I think u have to unzip and flash files through fastboot commands
@HueyT - Yes I had to extract the files and perform each fastboot command in my command prompt terminal. All is good now. I'm actually now on the latest released firmware by doing the same update steps.
Will it bootloop if I install RETUS on AMZ XT1962-1 phones?
I have flashed several times to this phone and never have I had issues. Yet, after trying out Lineage OS 17.1 I can no longer get broadband connection. I have flashed back to the stock ROM and I still have the same issue that was happening with Lineage OS 17.1 . Basically, it seems as if my IMEI info isn't getting pulled to the system. I noticed that when at the bootloader screen it says ""Baseband: (Not Found). I'm thinking this might have something to do with my issue. (I don't really know.)
EDIT: I will add that I do have wireless functionality and can get internet perfectly fine. Why I think it's IMEI related is because it isn't filled in the OS About phone section. I've even done *#06# and that just shows the serial number of my phone.
[ I do see the following ]
Running: fastboot getvar all
...
(bootloader) version-baseband: <not found>
...
(bootloader) imei: 3595250... // I omitted part of this for privacy reasons.
(bootloader) meid:
...
I have done the following as well to no effect:
fastboot oem config carrier virgin, vzw
fastboot oem config fsg-id virgin, vzw
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
ITDominator said:
I have flashed several times to this phone and never have I had issues. Yet, after trying out Lineage OS 17.1 I can no longer get broadband connection. I have flashed back to the stock ROM and I still have the same issue that was happening with Lineage OS 17.1 . Basically, it seems as if my IMEI info isn't getting pulled to the system. I noticed that when at the bootloader screen it says ""Baseband: (Not Found). I'm thinking this might have something to do with my issue. (I don't really know.)
EDIT: I will add that I do have wireless functionality and can get internet perfectly fine. Why I think it's IMEI related is because it isn't filled in the OS About phone section. I've even done *#06# and that just shows the serial number of my phone.
[ I do see the following ]
Running: fastboot getvar all
...
(bootloader) version-baseband: <not found>
...
(bootloader) imei: 3595250... // I omitted part of this for privacy reasons.
(bootloader) meid:
...
I have done the following as well to no effect:
fastboot oem config carrier virgin, vzw
fastboot oem config fsg-id virgin, vzw
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Click to expand...
Click to collapse
I would try flashing just the modems not sure if u in us if u are u can try the retus modems do it several times just lost base band some times have to try different modems from different carriers https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw. Go here if u need more help
</sigh> I kid ya'll not, I resolved my issue.... I know the stock firmware I had worked for me plenty of times but it looks like trying a different and newer version worked in its stead.
I got the new firmware from here: <Add https back to the link>
//mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
I used the following version:
XT1955-5_OCEAN_RETUS_10_QPO30.85-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I used all the same commands I've ran before.
fastboot oem fb_mode_set oem
fastboot erase all
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 dtbo dtbo.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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
#fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
roadkill42 said:
I would try flashing just the modems not sure if u in us if u are u can try the retus modems do it several times just lost base band some times have to try different modems from different carriers...
Click to expand...
Click to collapse
I would have sworn the former stock ROM I had was RETUS but looking at it's info, I'm no longer sure. Even then, it was at one point working fine when flashing it. I tried a new stock ROM and later newer build version and that seems to have worked. I'm happy yet frustrated with how much time I've sunk into this issue. </sigh>
(AVOID AT ALL COSTS)
Here is the old stock ROM build info:
BUILD REQUEST INFO:
SW Version: ocean-user 9 PPO29.114-134 fee207 release-keysM632_26.100.01.120.01R
MBM Version: MBM-2.1-ocean_retail-b508f3a-190702
Modem Version: M632_26.100.01.120.01R
FSG Version: FSG-8953-22.112
Build Fingerprint: motorola/ocean/ocean:9/PPO29.114-134/fee207:user/release-keys
CQATest App Version: 6.0.4
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.271.151.ocean.retail.en.US
Model Number: moto g(7) power
Android Version: 9
Baseband Version: M632_26.100.01.120.01R
Build Id: PPO29.114-134
SW Display Build ID: PPO29.114-134
Build Date: Tue Jul 2 04:40:26 CDT 2019
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.29.271.151.ocean.retail.en.US
Version when read from CPV: ocean-user 9 PPO29.114-134 fee207 release-keys
AB Update Enabled: True
Full Treble Enabled: True
ITDominator said:
</sigh> I kid ya'll not, I resolved my issue.... I know the stock firmware I had worked for me plenty of times but it looks like trying a different and newer version worked in its stead.
I got the new firmware from here: <Add https back to the link>
//mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
I used the following version:
XT1955-5_OCEAN_RETUS_10_QPO30.85-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I used all the same commands I've ran before.
fastboot oem fb_mode_set oem
fastboot erase all
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 dtbo dtbo.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_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 vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
#fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
There is one more command for q this is all the commands for 10 aka q
You are missing one command line.
roadkill42 said:
There is one more command for q this is all the commands for 10 aka q
Click to expand...
Click to collapse
Please note that version Q or 10 has one more sparsechunk file, so you must add a line fastboot flash system system.img_sparsechunk.10 If you don't you will not have a full load.
tamwood53 said:
Please note that version Q or 10 has one more sparsechunk file, so you must add a line fastboot flash system system.img_sparsechunk.10 If you don't you will not have a full load.
Click to expand...
Click to collapse
Well...it seems to run fine without the chunk? I ran flashing without that last img_sparsechunk and I don't have issues currently. (Didn't see it existed when I flashed...) Will it affect updating by any chance?