Database Develop

[Q] Help: Unable to flash TWRP on unlocked bootloader after 4.4 update

I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?

danherbert said:
I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
Click to expand...
Click to collapse
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Sent on my Moto X

flashallthetime said:
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Click to expand...
Click to collapse
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.

danherbert said:
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
Click to expand...
Click to collapse
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Sent on my Moto X

flashallthetime said:
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Click to expand...
Click to collapse
Your suggestion worked. I didn't have easy access to a Windows machine so I couldn't use rsdlite. I had to manually reset to stock. For anyone who stumbles upon this thread, these are the steps I used which worked for me:
Make sure adb and fastboot from the Android SDK are already part of your PATH.
Download moto-fastboot for Mac OS X
Download the Kitkat 4.4 update for Sprint (Make sure to download the version that matches the build number from "Settings -> About Phone" in your device)
Download the Kitkat 4.4 version of TWRP
Extract the factory image .zip to a folder
Copy the moto-fastboot binary to the folder you extracted the factory image to and rename it to "mfastboot"
Copy the TWRP .img file to the folder with the factory image files
Create a file named "factoryreset.sh" and paste the following as its contents
Code:
#!/bin/sh
FASTBOOT=./mfastboot
$FASTBOOT getvar max-download-size
$FASTBOOT oem fb_mode_set
$FASTBOOT flash partition gpt.bin
$FASTBOOT flash motoboot motoboot.img
$FASTBOOT flash logo logo.bin
$FASTBOOT flash boot boot.img
$FASTBOOT flash recovery recovery.img
$FASTBOOT flash system system.img
$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 config carrier sprint
$FASTBOOT oem fb_mode_clear
Open a terminal and navigate to the directory you created
On your device, navigate to "Settings -> About Phone" and tap on the build number 7 times to enable developer mode
Go back to the main "Settings" screen, open "Developer Options", and enable USB Debugging
Connect your device to your computer. Go back to your device, make sure you choose to trust your computer to use ADB in the dialog that pops up, then run the following command from your terminal
Code:
adb reboot-bootloader
Once your device is in fastboot mode, run the command
Code:
sh factoryreset.sh
From the device choose to boot normally and wait for it to finish booting completely.
Run the command
Code:
adb reboot-bootloader
Once the device is in fastboot mode again, run the command
Code:
fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
From your device, power up normally then reboot into the recovery. If everything went smoothly you'll boot into TWRP recovery.
Code:
adb reboot recovery

[Untested][Linux/ Mac] Fastboot package for Oreo January update

Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.

downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?

i dont have a Mac, windows 10. how do i flash it ?

soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.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 lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot

majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once

@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker

soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.

Can you explain me how you extracted payload.bin to .img files

ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.

I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.

I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?

Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html

Hard brick xt1775 unbricked.

Hello everyone.
My phone was hard bricked 3 monhts ago.
And today I unbrick it.
I use different model(E4 sprint) unbrick file but it work.

.........

......

cAN YOU SHARE THE METHOD?

help
ismail0100 said:
Hello everyone.
My phone was hard bricked 3 monhts ago.
And today I unbrick it.
I use different model(E4 sprint) unbrick file but it work.
Click to expand...
Click to collapse
please share the metod. I have a xt1775 model phone from lenovo, international version, and I cant unbricked

johita2006 said:
please share the metod. I have a xt1775 model phone from lenovo, international version, and I cant unbricked
Click to expand...
Click to collapse
I use this topic. (https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408)
Fisrt Message have a unbrick.img file link on mega. I download this unbrick.img file. I know different phone model but it work.
After use this topic(https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012)
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) (dont do it this part)Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) (For us unbrick.img not mmcblk0.img)Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=unbrick.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
after write file on sdcard use this command and use last firmware.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

ismail0100 said:
I use this topic. (https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408)
Fisrt Message have a unbrick.img file link on mega. I download this unbrick.img file. I know different phone model but it work.
After use this topic(https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012)
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) (dont do it this part)Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) (For us unbrick.img not mmcblk0.img)Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=unbrick.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
after write file on sdcard use this command and use last firmware.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
What did you name the sd card?

paigao said:
What did you name the sd card?
Click to expand...
Click to collapse
I did not remember sorry. Probably not change

Could someone tell me a blankflash file compatible with the Moto g5s plus?

My Moto g5s plus bricked out of nowhere, only the led keeps blinking, how can I fix this? I know there is no blankflash for this template, but is there a way to solve it?

Felipe9229 said:
My Moto g5s plus bricked out of nowhere, only the led keeps blinking, how can I fix this? I know there is no blankflash for this template, but is there a way to solve it?
Click to expand...
Click to collapse
To unbrick your device you need to have mmcblk0 file.
Here is the procedure for extracting mmcblk0.
https://forum.xda-developers.com/mo...eate-mmcblk0-img-device-t3803176/post76795590
Here is the procedure for unbrick the hard bricked device.
Requirements
Freshly formatted microSD card of at least 32gb (It needs to have at least 31.3gb free after formatting - if it displays as less you will need to buy a 64gb microSD card)
7zip
Linux mint live usb/dvd
USB card reader
Method
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stick that is at least 8gb or a dvd
Do not run Linux as a virtual machine on Windows! Use the live USB/DVD
0) Put the Moto g5s plus on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Things to note
Linux Live dvd doesn't have open as root so just open in terminal and add sudo to the start of the commands
I've included this in the commands below
If you get a status error just remove status=progress from the terminal command below
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and the flashing process should start
When it finishes, test the sdcard in the phone and it should boot!
If you get a size error of the sdcard in terminal you have to change the sdcard and try again!
Thanks to @vaserbanix for the original version of this guide
Re-flash Stock Firmware
Once the phone is in bootloader mode you can flash stock firmware via fastboot
Note that in order to flash gpt the firmware MUST be the same or newer than the version currently on your phone
Once you have firmware that is the same or newer than your current version you can remove the sd card and run these commands (assuming you have fastboot all setup on your pc)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5 (only oreo firmware)
fastboot flash system system.img_sparsechunk.6 (only oreo firmware)
fastboot flash system system.img_sparsechunk.7 (only oreo firmware)
fastboot flash system system.img_sparsechunk.8 (only oreo firmware)
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 (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot

riyan65 said:
To unbrick your device you need to have mmcblk0 file.
Here is the procedure for extracting mmcblk0.
https://forum.xda-developers.com/mo...eate-mmcblk0-img-device-t3803176/post76795590
Here is the procedure for unbrick the hard bricked device.
Requirements
Freshly formatted microSD card of at least 32gb (It needs to have at least 31.3gb free after formatting - if it displays as less you will need to buy a 64gb microSD card)
7zip
Linux mint live usb/dvd
USB card reader
Method
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stick that is at least 8gb or a dvd
Do not run Linux as a virtual machine on Windows! Use the live USB/DVD
0) Put the Moto g5s plus on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Things to note
Linux Live dvd doesn't have open as root so just open in terminal and add sudo to the start of the commands
I've included this in the commands below
If you get a status error just remove status=progress from the terminal command below
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and the flashing process should start
When it finishes, test the sdcard in the phone and it should boot!
If you get a size error of the sdcard in terminal you have to change the sdcard and try again!
Thanks to @vaserbanix for the original version of this guide
Re-flash Stock Firmware
Once the phone is in bootloader mode you can flash stock firmware via fastboot
Note that in order to flash gpt the firmware MUST be the same or newer than the version currently on your phone
Once you have firmware that is the same or newer than your current version you can remove the sd card and run these commands (assuming you have fastboot all setup on your pc)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5 (only oreo firmware)
fastboot flash system system.img_sparsechunk.6 (only oreo firmware)
fastboot flash system system.img_sparsechunk.7 (only oreo firmware)
fastboot flash system system.img_sparsechunk.8 (only oreo firmware)
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 (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Hey Friend, I don't Have other moto G5S plus for extracting mmcblk0 file.

Felipe9229 said:
To unbrick your device you need to have mmcblk0 file.
Here is the procedure for extracting mmcblk0.
https://forum.xda-developers.com/mo...eate-mmcblk0-img-device-t3803176/post76795590
Here is the procedure for unbrick the hard bricked device.
Requirements
Freshly formatted microSD card of at least 32gb (It needs to have at least 31.3gb free after formatting - if it displays as less you will need to buy a 64gb microSD card)
7zip
Linux mint live usb/dvd
USB card reader
Method
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stick that is at least 8gb or a dvd
Do not run Linux as a virtual machine on Windows! Use the live USB/DVD
0) Put the Moto g5s plus on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Things to note
Linux Live dvd doesn't have open as root so just open in terminal and add sudo to the start of the commands
I've included this in the commands below
If you get a status error just remove status=progress from the terminal command below
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
and the flashing process should start
When it finishes, test the sdcard in the phone and it should boot!
If you get a size error of the sdcard in terminal you have to change the sdcard and try again!
Thanks to @vaserbanix for the original version of this guide
Re-flash Stock Firmware
Once the phone is in bootloader mode you can flash stock firmware via fastboot
Note that in order to flash gpt the firmware MUST be the same or newer than the version currently on your phone
Once you have firmware that is the same or newer than your current version you can remove the sd card and run these commands (assuming you have fastboot all setup on your pc)
Hey Friend, I don't Have other moto G5S plus for extracting mmcblk0 file.
Click to expand...
Click to collapse
You can try asking your xda friends, to extract the mmcblk0 file. Or someone with this device you know who can help.

Felipe9229 said:
My Moto g5s plus bricked out of nowhere, only the led keeps blinking, how can I fix this? I know there is no blankflash for this template, but is there a way to solve it?
Click to expand...
Click to collapse
i am succesfully extracted mmcblk0.img from my working moto g5s plus today. But the size is about 62.5 GB (without zipping), Unable to upload - my daily data limit is only 2gb, Were is your location?

pradeeppk said:
i am succesfully extracted mmcblk0.img from my working moto g5s plus today. But the size is about 62.5 GB (without zipping), Unable to upload - my daily data limit is only 2gb, Were is your location?
Click to expand...
Click to collapse
:crying::crying::crying:

Guide: howto update stock rom with unlocked bootloader, root, TWRP and keep user data

With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot​
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img​

wedgehog said:
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot​
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img​
Click to expand...
Click to collapse
with XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml at least for me dirty flash failed, rom didn't boot
did a backup of /data/ to external storage from TWRP with internal storage decrypted (had to boot TWRP from fastboot a couple of times before the decrypt password prompt were shown on boot of TWRP)
did also a backup of internal storage over MTP with TWRP to computer.
then flashed again with below commands, WHICH WILL ERASE INTERNAL STORAGE
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot​
Thereafter successfull boot, reboot to flash mode, boot TWRP again, restore internal storage over MTP from TWRP, restore of data from backup to external storage which were made above
all apps and settings back, and on latest moto firmware.

any chance of capturing the delta OTA's to make them twrp-flashable?

Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
Would probably be doable as in almost all other devices in general and older motorola devices in particular have had that. I for one do not have the knowledge of how to do that (and not the time available even if I had that knowledge =) )

I can confirm that at least for me, a dirty flash like the one described in post 1 in this thread worked again with the latest OTA/firmware for RETEU - XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC, when written over the second latest (XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
I did however have trouble booting the latest twrp twrp-3.3.1-0-v5.1-lake-jlb from fastboot, phone rebooted after it was sent over adb boot instead of booting twrp it went straight back to fastboot. Tried many times with rebooting to phone home screen in between. But adb fastbooting the older twrp-3.3.0-lake worked straight away, and thereafter installing twrp-3.3.1-0-v5.1-lake-jlb with it's zip worked straight away.

I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.

SvenHee said:
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
Click to expand...
Click to collapse
Doesn't seem likely, date is 2009

For reference, here is the line where I found this url:
Code:
12-06 14:19:06.869 5831 14719 D OtaApp : UpdaterEngineHelper:applyPayload, applying payload with downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/*lots-of-stuff*%3D offsetvalue = 9258 fileSize = 107713236

Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
It would be no problem to catch them and make them TWRP flashable. But it's strongly not recommended to do that!! Do an OTA-update only if your device is fully on stock! Otherwise the OTA-update will override incorrect blocks of your partitions and this could crash your entire system irreversible.