Good morning, after searching and reading endless post of solutions I did not find any. To if I prepared to post the problem here and see if any solution arises, since we are several affected by this.
I pass the following: When I try to flash firmware stock con ABDtool . First flicks (Prevalidation Failed) Bootloader when flashing:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
It could be caused by not unlocking the boot loader, but My bootloader it unlocked
The bootloader data:
AP Fastoboot Flash Mode (Secure)
BL:80.CB (sha-cfa8344, 2015-11-20 18:51.42)
Baseband: Not found
Product Variant: osprey XT1542 8 GB P2B
Serial Nmber zY2232NR5Q
CPU: MSM8916
eMMC: (GB Micron RV= 06 PV= 12 TY= 17
DRAM: 1024MB Elpida S8 SDRAM DIE= 4GB
Console (NULL): null
Battery Ok
Device is UNLOCKED. Status code 3
Software Status: Modified
Connect USB Data Cable.
You can flash the stock in the same way without flashing those 2 lines, but the terminal lights up and goes straight to Fastboot. Any way to fix it ??
For example I reboot from the Android menu and start in fastboot and I have to press Star to start android.
The ADB commands
fastboot devices
**************
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
*****************
fastboot flash logo logo.bin
If you searched, you would know preflash validation errors mean your device has newer firmware then you are trying to flash. locked devices do no support​ downgrading, if you can't skip gpt.bin and bootloader.bin and get it booting, you're probably out of luck.
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
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).
August 1 security update is out
RIVER_RETAIL_9.0_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
== Installation ==
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash partition 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 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
If you don't want to clear your existing data, you can skip fastboot erase userdata
I used this method to update a couple days ago as i got sick of the update telling me it failed. No issues so far. Had to re-root with magisk after but... such is life.
I can also confirm this works
Stock boot img
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
fwr6236437 said:
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
Click to expand...
Click to collapse
from PPOS29.114-134-4
boot.img
Thank you so much! Works great!
Thanks for this write up and break down. It saved my sanity. I havent been with Android since the Nexus 5 and picked up the G7 on a BF sale and decided to try and root it and use custom ROMs. Quick story I jacked it up bad so just wanted to get it back to stock and even then was having issues. This worked. Much appreciated.
Clutch
This saved my life because this was my first time rooting and i got stuck in a bootloop trying to root my moto g7 with magisk. Im so glad i found this.
hello guys I'm new to this community !! I needed your help to restore my phone's baseband !! in fastboot mode baseband shows how not found !!! I already have the bootloader unlocked .. I would like using TWRP to flash baseband again ???
MY phone specs
BL:MBM3.0-becham_retail-8ca64c4-190220
Baseband: <not found>
Product/Variant: beckham XT1929-5 64GB PVT
if someone can help me with some method to solve with linux or zip flash i am very grateful thanks to all
I finally figured out how to recover a base band from motorola Z3 play !!!
NOTE: <<<< NEED BOOTLOADER UNLOCKED >>>>
After unlocking the bootloader I used this rom
<<<< XT1929-5_BECKHAM_RETBR_9.0_PPWS29.131-27-1-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC >>>
!!! To install the system on the smartphone
correcting the connection problem and corrupted IMEI
Comand line to INSTALL ROM IN ADB TOOLS:
----------------------------------------------------------------------------------------------------------
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
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 carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
----------------------------------------------------------------------------
After installation the problem will be fixed I hope I helped it took me 3 days to solve this problem even having intermediate knowledge of android system !!!
for people who have no knowledge !! a wrong root can cause a briking baseband easily
my email for some help if you want !!
[email protected]