I have the rom downloaded and I just want to know how to flash the stock rom since the files are a little different in the Moto G7 Play. I was in the process of trying to gain root access and one of the events caused me to lose sim card detection, so I want to flash it back to the original state to see if that fixes it. I attached a screenshot of my rom.
Thanks
use the flashfile.xlm to tell you which order to flash the files in. just make sure youve downloaded the correct rom version to the one you have/had before the problem...that is this one is 105-57... otherwise if your trying to flash a older version rom you might run into problems flashing it.
jwreidmoto said:
I have the rom downloaded and I just want to know how to flash the stock rom since the files are a little different in the Moto G7 Play. I was in the process of trying to gain root access and one of the events caused me to lose sim card detection, so I want to flash it back to the original state to see if that fixes it. I attached a screenshot of my rom.
Thanks
Click to expand...
Click to collapse
The easiest and most foolproof way is to read the flashfile.xml inside your firmware zip. This is taken from the most recent Pie update from Sprint for the Moto G7 Play.
<phone_model model="channel_sprint"/>
<software_version version="channel_sprint-user 9 PCY29.105-134 3d133 release-keysM632_26.100.01.120.01R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="7f966547ae0da254b599f22380b4e426" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="d7a82bbcd5d236e4472b75da4840178c" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="5589ffd28dd3f04a7d5a12bf91a4b5dc" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="4051200188fb631ad351632a7e8e4661" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="330051cf4bad4a337b30cbbf90439f90" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="86b16aaf451af6fbfd03a5aee8d17486" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="b175571ccc933681ced5ebdca4472c39" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="0c80316dcd235b0f518e46807ebd9e02" filename="dtbo.img" operation="flash" partition="dtbo"/>
<step MD5="27533ed08e8bd1f002882eac880d2ec8" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="07bf4514b20965a39e55b023715f37b2" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="e856fc09cd4dac7ead54ec97ebc0e143" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="217857df38225f0ca4cf5f834bd5e3cb" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="c356bd9845845a05b6032af8a27e491e" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="a168b1389a044e5ed56d2a4a6dcfa96f" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="fbc6669a31cc8f8b098f5d260915fae9" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="2c757650843740dd6ad4ae333a2ee0f7" filename="system.img_sparsechunk.7" operation="flash" partition="system"/>
<step MD5="db47ec98a25ae42c3e8d167f24d20490" filename="system_b.img_sparsechunk.0" operation="flash" partition="system_b"/>
<step MD5="5e3b9b937b421f3ae42124b62b5bf9e9" filename="system_b.img_sparsechunk.1" operation="flash" partition="system_b"/>
<step MD5="b9d404c81209e6ac87ec01ae0496ea57" filename="system_b.img_sparsechunk.2" operation="flash" partition="system_b"/>
<step MD5="927da415259568d9f55e0e2dc1513c81" filename="vendor.img" operation="flash" partition="vendor"/>
<step MD5="24e36787f2fabbf9750af4a4d19d9d89" filename="oem.img" operation="flash" partition="oem"/>
<step MD5="c900cf1eb5d3a51a8cdc98f18bd64430" filename="oem_other.img" operation="flash" partition="oem_b"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
How do you make sense of it? The first thing is to understand the order fastboot accepts commands. Fastboot likes to do things in this order.
(Operation) (Partition) (File)
or in other words...
(Flash or erase?) (Where am I going?) (Who am I sending?)
fastboot can also run variables. There's no need to go in depth here, but it needs to be touched on. The first 2 commands in the list are oddballs because of it.
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
All you need to know for this, is that you should do it, and it translates to this in fastboot...
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
Now for the rest. The next one looks like an oddball, but it actually isn't. It means what it says.
<step MD5="7f966547ae0da254b599f22380b4e426" filename="gpt.bin" operation="flash" partition="partition"/>
partition="partition"- That's right, it really says that. It follows same the order I laid out earlier though. This translates to,
fastboot flash partition gpt.bin
(flash or erase? flash.) (Where am I going? partition.) (Who am I sending? gpt.bin)
Let's look at couple more just for the sake of clarity.
<step MD5="d7a82bbcd5d236e4472b75da4840178c" filename="bootloader.img" operation="flash" partition="bootloader"/>
Becomes...
fastboot flash bootloader bootloader.img
<step MD5="5589ffd28dd3f04a7d5a12bf91a4b5dc" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1 etc...
Some rules & notes:
1. Always follow all the commands in the flashfile.xml, and follow them in order!
2. Sometimes the bootloader or gpt.bin won't flash. This just means they're older than your current one. If this happens, just skip it.
3. I thought this list would be longer, but apparently it isn't. If anyone has questions just ask.
or to put it simply...it would turn out something like this
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
last two commands erase the phone to stock etc.
Thanks so much!
One more question
I will be flashing ppy29.105.57 and then letting the phone update to ppy29.105.134 by itself. Before I tried rooting I flashed the updated ROM ppy29.105.134 to slot b because I was running the update at the time. How can I start fresh and erase the update in slot b? I may plan to use the phone unrooted afterwards as rooting has been unlucky with my phone variant.
Thanks
redavenger said:
or to put it simply...it would turn out something like this
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
last two commands erase the phone to stock etc.
Click to expand...
Click to collapse
I successfully put it back to stock. I booted it and updated it to the latest version and I got sim card access back. WoooHooooo!!! Now I know I can fix whatever happens now. I will continue trying to root with twrp4.img
Thanks again!
Hi, i want to flash retapac channel rom to g7play in which there is ppys29.105-134-2 version.. can i flash retapac ppy29.55-6
Related
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Anutter226 said:
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Click to expand...
Click to collapse
What happens with the flash-all.bat file?
delete
airmaxx23 said:
What happens with the flash-all.bat file?
Click to expand...
Click to collapse
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Your fastboot is likely too old and can't read the pixel partitions. Make sure your Google drivers and fastboot files are up to date and try again.
Sent from my Pixel XL using Tapatalk
Anutter226 said:
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Click to expand...
Click to collapse
I have used the flash all script several times and it works flawlessly.
Nevermind..
kiddiosky said:
Nevermind..
Click to expand...
Click to collapse
Mate somehow i too need the manuall commands Did you solved the problem/?
Hi, i flashed a bad boot file and my phone is stuck on bootloader, i tried to get into edl but it's still stuck.
my bootloader is unlocked and i have access to download mode and i can run commands via fastboot. the problem is i can't remember what whas my android version (just got the phone yesterday, i think it's 8.1)
any idea how to get the phone working (any solution is good: back to stock or whatever)
oh, and i don't have root access if it's relevant.
thanks!
If you can access fastboot you can try
Code:
fastboot oem edl
And connect your phone to a PC and use MiFlash to flash the stock clean rom that you can download here
If it doesn't work, since you have access to fastboot you can extract images from here and flash them via fastboot by running the following commands from the same location of the images :
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
first of all - thank you!
i tried with miflash and it didn't work. when i flash an img file it's flashing it too fast, almost like it didn't do anything, and then it is stuck again.
about the second solution - how can i exctract img files from the file you gave me? there is a bin file in there and no img...
[edit]: it didn't flash because the folder name has spaces, now it's working. thanks!
b.t.w: do you know if there is another twrp for a2 lite then the one here ? because this is what started the problems..
I used to be like that when I was trying root by magisk
your device has update security september or aug ?! to see in setting - about
you can find original boot.img of update secrutiy your device (in topic:magisk update ota) to re-flash and reboot ... everything will be fine
Sent from my Mi A2 Lite using XDA Labs
I flashed stock rom and it's all good now. thanks!
if anyone has working twrp for a2 lite (not the one that published here unoffical)- it would help me.
As far as I know, the one you posted is the only version of TWRP for now. But the official TWRP for the Redmi 6 Pro (that is exactly the same device as ours but with dufferent partitions and MIUI ROM) has been released so fortunately the official build will be availbable for the A2 Lite soon
(btw, if ever needed again, the payload.bin file also needs to bé unpacked with a tool named "payload dumper" for example)
wrong. delete
Note:
The guide is written by Liangchen Chen who is the man behind F(x)tec. I am just sharing the guide. You can find the original post from here:
https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Downloads:
The Fastboot restoration file can be downloaded in here:
https://drive.google.com/open?id=1uFp7Eoyb_BrvL9oIzpAa_nD3QaJSqyUY
You can use ADB drivers from Google:
https://developer.android.com/studio/run/win-usb
Preparation:
You need to have a PC and installed universal ADB driver
Completely turn off the phone.
Download the firmware and copy all the files into the adb folder which installed with the driver.
Procedures:
Hold Volume down + Power key together, when the logo shows up, release both fingers. The phone should boot into bootloader.
Connect the phone to the PC, and because the driver is installed, system should have identified the connection.
Right click Windows Logo --- Run --- Type
Code:
cmd
In command line, move to the adb folder using cd. For example, if the adb folder is in C:\adb, type
Code:
cd C:\adb
Then we need to see if the device successfully connects, type
Code:
fastboot devices
The outcome should have a device list there.
If the device is successfully connected, run the following commands:
Code:
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
After it’s all finished, run
Code:
fastboot reboot
And the phone should now restored to factory state.
The firmware is the restoration file got it. Big Thank you.
please help me i am having this kind of problem it is saying fastboot: error: cannot load 'devcfg.mbn': no such file or directory
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZF522784QB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 32AA9F6547C0BDE1000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-13-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 3:10:57 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
(bootloader) ro.build.fingerprint[1]: 70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C70602
all: listed above
finished. total time: 0.007s
Click to expand...
Click to collapse
adrianosk8 said:
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
Click to expand...
Click to collapse
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Sent from my ali using XDA Labs
sd_shadow said:
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Click to expand...
Click to collapse
I already installed all these RETBR roms. None started. when the Motorola logo appears, the device restarts.
I was searching the net and I found some articles saying that it could be because the processor is MIDIATEK (MT6771V / WL). AND THAT WOULD HAVE TO DOWNLOAD MTK / Sp flashing tools:
https://flashtool.org/5/download-sp-flash-tool.html
to install the rom on devices with this processor.
then I installed this program, but it needs the rom to have a file called "mt6771-scatter- android-file.txt "- what my device's roms don't have.
So I found a program that would generate this file (mt6xxx -scatter-android-file.txt):
https://mega.nz/file/YAogUAAL#cAbYxrWcUODmyVLD6p2Oz-YTsxm9Fb61A0RUq6OmkYI
but as nothing is so easy in this life, the program does not identify my device. not even after I installed the MidiaTek drivers (MTK drivers):
I don't know what to do.
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash -u system_a system.img_sparsechunk.1 fastboot flash -u system_a system.img_sparsechunk.2 fastboot flash -u system_a system.img_sparsechunk.3 fastboot flash -u system_a system.img_sparsechunk.4 fastboot flash -u system_a system.img_sparsechunk.5 fastboot flash -u system_a system.img_sparsechunk.6 fastboot flash -u system_a system.img_sparsechunk.7 fastboot flash -u system_a system.img_sparsechunk.8 fastboot flash system_b system_other.img_sparsechunk.0 fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
did it work? and could you install magisk after that?
Matiasfh01 said:
did it work? and could you install magisk after that?
Click to expand...
Click to collapse
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.
adrianosk8 said:
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.
Click to expand...
Click to collapse
can u poste the final flashfile here pls
Matiasfh01 said:
can u poste the final flashfile here pls
Click to expand...
Click to collapse
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Watter flash het u gebruik?
adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i need the firmware i use to fix the xt2015-2 please brother I could not solve
I could not solve
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
you have saved my phone Bro!
this works..
Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?
BrenoSilva1997 said:
Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?
Click to expand...
Click to collapse
You can use LMSA to flash g8 stock rom
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
hello, I know this is more than I year old but still I wanted to thank you for posting this solution, I was having a really hard time trying to fix my mom's phone and just with this all got solved, thank you
adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i love u
My little sister gave me his phone because it was looping at bootlogo
I've flashed some firmwares before so i tried to fix it. I downloaded this firmware: https://mirrors.lolinet.com/firmware/moto/ocean/official/AMXMX/
and tried to flash it but i didn't work. Still bootlooping, tried with blankflash but none of this versions did anything, just <waiting for device> Blankflash i used: https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
i realized that the battery level screen don't displays anymore. when i connect it it's looping at electricity logo
Variables i think might know
version: 0.5
version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-210201
product: ocean
secure: yes
securestate: oem_locked
factory-modes: disabled
iswarrantyvoid: no
max-download-size: 536870912
imei: [I hide it for security but i got one]
carrier_sku: XT1955-2
ro.carrier: amxmx
running-boot-lun: 0
slot-successful:_a: No
slot-successful:_b: No
slot-bootable:_a: No
What could i do?
Lol, i just solved it
Tried with Lenovo/Moto smart assistant : https://support.lenovo.com/us/en/downloads/ds101291
Flashed but not worked at all (but It's an important step), then i downloaded https://drive.google.com/file/d/1LzWEzxSbg56GqIZaVHj8WxbuTMNWfzKb/view
and ran this commands on cmd
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
Not all commands worked but cmd skip those, then the phone worked again
I got a problem with the IMEI (I'ts 'unknow') but i can't flash another NON-HLOS.bin file (The correct for my firmware version)
At least it works for wifi usage