Database Users

Help, my Moto X Style XT1752 Brick :(

Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
https://www.youtube.com/watch?v=njXQYn53SPc
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.

AlexAndroid said:
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
Click to expand...
Click to collapse
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.

acejavelin said:
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
Click to expand...
Click to collapse
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.

AlexAndroid said:
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
Click to expand...
Click to collapse
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?

acejavelin said:
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
Click to expand...
Click to collapse
You mean this? (attached image)

Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you

AlexAndroid said:
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
Click to expand...
Click to collapse
Do you know how to use fastboot and adb? This is from a computer...

acejavelin said:
Do you know how to use fastboot and adb? This is from a computer...
Click to expand...
Click to collapse
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ---
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: 368A71011E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: -----
(bootloader) meid:
(bootloader) date: 12-13-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Feb 5 7:26: 3 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_APAC_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga389d53 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:27:17 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retapac

AlexAndroid said:
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) date: 12-13-2016
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
Click to expand...
Click to collapse
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot

acejavelin said:
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?

AlexAndroid said:
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
Click to expand...
Click to collapse
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.

acejavelin said:
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
Click to expand...
Click to collapse
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s

AlexAndroid said:
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
Click to expand...
Click to collapse
Then your choices are Moto repair or wait for the 20-16 firmware to be released.

acejavelin said:
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
Click to expand...
Click to collapse
Do Motorola's official technical services have the necessary firmware?

AlexAndroid said:
Do Motorola's official technical services have the necessary firmware?
Click to expand...
Click to collapse
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/

If you are in warranty and u haven't unlocked your boot loader yet you can give silly reason's like i revived updates last night but battery was low and while updating it turned off and now my phone isn't booting up

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Hello, finally I take the equipment to an official technical service of Motorola, where they told me that they could not repair it since the cell phone did not take Software. Is this possible or would it be that the technical service did not have the necessary software version?

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Good afternoon, I return the subject after a long time since yesterday I thought to try again, and I found that the cell now turns on, but when trying to complete the initial configuration, after choosing the language gives me to select the wifi networks, where it does not detect any, and I do not enable the jump or forward button, and I'm stuck there again, it's very strange, as soon as I enter that screen, it gives me the option to add a new network, and I can see that says Mac Address with pure zeros, as if it did not have MAC.
If I try to enter the recovery, now I see "No Command" (previously not directly entered), and there is no way to skip this "No Command", I have tried all the methods that appear online.
EDIT: I was able to get into recovery, but I do not know if it can help me now.
Any ideas? he seems to be brigado, but not as much as before

Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.

Edvin73 said:
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Click to expand...
Click to collapse
I still have a problem, when the device is turned on, it always turns on Bootloader mode, and I have to select "Start" to turn it on. This is why when you want to upgrade to Android 7 via OTA, when the device is restarted during installation, it enters Bootloader mode, select "Start", restarts the update, restarts in Bootloader, and remains in an infinite cycle.
Is there a solution to this? I have already activated USB debugging in order to unlock the Bootloader.
Thank you!!

XT1580 bootloader stuck/brick

Hello, i have a huge problem with my moto x force kinzie XT1580 P301 (Says on the bootloader screen)
i was updating to nougat then i have a crash and my phone cant boot, it just goes to the bootloader screen with a legend that says "start up failed" this are the things i tried
As far i know with bootloader locked i have to flash on fastboot or RDSlite the original carrier firmware wich i dont know wich one is, i tried different official firmwares and some files get an error while trying to flash them on fastboot or maybe i'm missing one.
So, i tried to get my bootloader unlocked, wverything goes fine until i have to put the code with commandoem unlock and get this
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
i can't even boot to check that option
Please, help me guys.
Edit: Thanks if someone was figuring a solution, i find one, with my bootloader unlocked i just flashed this firmware XT1580_KINZIE_RETLA_DS_6.0_MPKS24.78-8-12_cid12_subsidy-DEFAULT_CFC.xml using mfastboot because normal fastboot get errors and using this commands that provided the user roweboat56 in this
mfastboot oem fb_mode_set
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
the phone boot fine, and then i unlocked the bootloader sucefully.

Simple Moto G4 Question

Motorola G4 XT1625
Minor Problem: Phone will not start normally, only boots into Fastboot mode.
Minor Problem: Phone is oem Locked
Major Problem: I never went into "settings" on the phone and ENABLED OEM UNLOCKING.
Question: Is it possible to recover this phone or am I spinning my wheels here?
A little background. Not a developer, just trying to get my phone running again. I have installed Moto tools on my PC, requested and received an unlock code, connected to the phone and can send commands via command line. I understand what the issue is, and hindsight says I should have enabled the phone for development on day 1 based on the risk of an OTA update failure. I've read nearly every forum post regarding this topic, just haven't got clear answer as to if this phone is recoverable.
Oh, and if this looks slightly familiar, its a repost of a thread I started in the general Android help and Q&A forum. I received an email from Brandon, chief admin, letting me know I may receive more info from the MOTO G4 forum.
Thanks in advance.....

Hello there, if the phone boots only into fastboot mode it may be that Stock OS has been wiped, therefore having no OS would reboot the phone every time. When you unlock the bootloader the user data gets erased and the phone goes into factory reset, however, you didn't have OEM unlocked. I don't see if it should be an issue right now.
What I would do is trying to find the stock ROM of your G4, and re flashing it. What I also would do is just try to flash recovery thru fastboot and see if it works.
Quick question, do you see the unlocked boot loader message when you boot your phone ? (this phone cannot be trusted blah blah)
Let me know if it works either way. I don't think OEM lock should be an issue if the system partition has been erased. You got an unlock code and used it.
Good luck!

If you can remember what firmware you had before attempting to unlock your bootloader, you can find a lot of the athene firmwares here: https://androidfilehost.com/?a=show&w=files&flid=72578
For US Nougat devices, I recall the latest build is NPJ25.93-14.7 (though there are reports that there is a newer build being deployed).
That's an odd issue to experience though - can you remember what happened to your device? Was there a factory reset or an erase command issued? A locked bootloader normally should not permit you to erase the system.
With OEM unlocking disabled, you likely would have been blocked from being able to unlock your bootloader. However, by requesting the unlock key, Motorola has a record of the request against your IMEI, so may refuse to service your device under the now voided warranty. Perhaps the best bet at this moment in time is to try a stock ROM reflash.
If you can't remember what stock firmware you had, or want a confirmation, then I'd like to see your getvar info please:
1)Boot to bootloader, connect your device to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes, press Enter on your keyboard.
3)Paste the output into a post here, you may wish to remove your IMEI. This output should be a list of your device variables and give us an idea of the state of your device.

Thank you both for help here.
Quick question, do you see the unlocked boot loader message when you boot your phone ? (this phone cannot be trusted blah blah)
No, the phone will not boot in any mode, factory,recovery,etc, and comes back with
Start Up Failed:
AP Fastboot Flash Mode (secure)
Fastboot reason : UTAG "bootmode" configured as fastboot
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
As to the pre-failure status, the phone was fine after the last upgrade, I believe in late December or early January. I also noticed that the internal storage was running thin so I uninstalled some unused apps as well as using the storage/apps/ clear cache method to get the unused space back to about 3GB unused. No problems after that either. The problem started with the phone doing one of two things, it either shut down such that I had to hold the power button down for 30 sec to start/reboot the phone, or would it simply do a full reboot on its own. The period between these events varied, sometimes a matter of minutes, other times a day or two. It did this for about a week until it booted into the mode I described earlier.
The following is the requested data from the phone,
Thanks again for your help
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: ***********
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: ***********
(bootloader) meid:
(bootloader) date: 01-11-2017
(bootloader) sku: XT1625
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 24 17:32:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14.7-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.246.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.64R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcb2b19d (hudsoncm
(bootloader) kernel.version[1]: @ilclbld30) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Nov 23 16:36:43 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.280s

Thank you for your patience, I'm starting to come up the learning curve a little bit.
I did go to the AndroidFileHost site and downloaded what looked like the most recent Athene set of files, based on its upload date and version number.
My limited knowledge tells me that this is older than the firmware loaded on the phone and will not load (see errors below)(security version downgrade)
I've only included 2 of the failures, I assume that is enough info....
****************************
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.051s
fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.554s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.727s
*******************************************
I was following these instructions, adapting to fit the files that came in the down load
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Makettle said:
Thank you for your patience, I'm starting to come up the learning curve a little bit.
I did go to the AndroidFileHost site and downloaded what looked like the most recent Athene set of files, based on its upload date and version number.
My limited knowledge tells me that this is older than the firmware loaded on the phone and will not load (see errors below)(security version downgrade)
I've only included 2 of the failures, I assume that is enough info....
****************************
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.051s
fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.554s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.727s
*******************************************
I was following these instructions, adapting to fit the files that came in the down load
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks for the getvar info. That suggests you have the NPJ25.93-14.7-3 US retail firmware (December 2017 security patch). Unfortunately, we don't have that firmware leaked to us yet - hopefully someone can capture the correct firmware from Motorola.
As you've correctly surmised, the firmwares we've got are too old for your device, and particularly as your bootloader is locked, the locked bootloader is rejecting any firmware that is older than the current version (as locked bootloaders do not permit firmware downgrades).
You could refer your device to a service centre and see if they can flash the latest firmware onto your device (and hopefully not charge you), or wait for a retail NPJ25.93-14.7-3 stock firmware to 'unofficially' appear.

Thanks Echo92, the help has been greatly appreciated.
It was an Ah Ha moment with your last message when I realized I could see the version of firmware from the getvar info, like I said I'm coming up the learning curve, just been a slow climb.......
I have contacted Motorola service about the phone, the response I received was that the G4 is not repairable, I could purchase a replacement for $90, which when you think about it is not a bad deal, but they only offered it with a 90 day warranty. I did not specifically ask about them simply re-flashing it, so I'm not sure if that was an option or not.
In case your curious, I've since replaced the phone, different brand, but will keep this one as a backup if I can eventually get the firmware re-loaded (hoping that it is not hardware related problem)
Thanks again

Flashed Stock ROM, but Bootloader NOT Re-Locking

*** [LATEST UPDATE, Unresolved] *** Issue Persists after reverting to original ROM and back to latest firmware (all signed, official copies)
I'm [STILL] stuck!
I was part of MFN beta test of android 10, but it would no longer allow me to install OTA updates of latest security patches, so i decided to try re-locking the bootloader, reverting back to stock 9 pie, and going back to OTA updates to get latest 10 Q official stock version...
Now I can't get valid boot image to re-lock bootloader with adb/fastboot!
(bootloader) Image signed with key bad key
(bootloader) Still require signed boot.img
I already tried LMSA rescue/software assistant. It reads device but when trying to rescue, doesn't like to play nice with my modified phone!
* [UPDATE 1]:
* flashed another firmware, now baseband doesn't work, no data/LTE signal good, not reading sim card at all?!
** [UPDATE 2]:
** After reverting back to PPOS29.114-134-14 (9 Pie) >>> now baseband works, LTE signal good, sim card reading again
** BUT STILL unsigned boot image (still void warranty, still can't lock bootloader to use Google Pay)
** Thanks, Huey for link to 10Q version, I'll try it out and post update...
*** [UPDATE 3]:
*** I flashed HueyT's 10 Q Rom (RIVER_QPU30.52-16-2)
*** Phone functioning again with 10 Q (network, baseband,etc all good)
*** BUT STILL unsigned boot image (STILL void warranty, STILL can't lock bootloader to use Google Pay)
*** "(bootloader) Image signed with key bad key"
*** "(bootloader) Still require signed boot.img"
:crying:

natesc0tt said:
I'm stuck!
I was part of MFN beta test of android 10, but it would no longer allow me to install OTA updates of latest security patches, so i decided to try re-locking the bootloader, reverting back to stock 9 pie, and going back to OTA updates to get latest 10 Q official stock version...
Now I can't get valid boot image to work with adb/fastboot!
(bootloader) Image signed with key bad key
(bootloader) Still require signed boot.img
I already tried LMSA rescue/software assistant. It reads device but when trying to rescue, doesn't like to talk to my modified phone!
now baseband not working, no signal, can't read sim card !?!?
Anyone have stock firmware xt1962-1 RETUS 10 Q, RIVER_QPU30.52 ????:crying:
Click to expand...
Click to collapse
Did you use a stock boot.img?
After the message "Still require signed boot.img" flash your boot.img again and run "fastboot oem lock". Then another message should appear like "Still require signed system.img".
---------- Post added at 07:55 PM ---------- Previous post was at 07:40 PM ----------
BTW: You must try to relock the bootloader while having Pie version installed and not beta version.

WoKoschekk said:
Did you use a stock boot.img?
After the message "Still require signed boot.img" flash your boot.img again and run "fastboot oem lock". Then another message should appear like "Still require signed system.img".
---------- Post added at 07:55 PM ---------- Previous post was at 07:40 PM ----------
BTW: You must try to relock the bootloader while having Pie version installed and not beta version.
Click to expand...
Click to collapse
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"

natesc0tt said:
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"
Click to expand...
Click to collapse
Pie version flashed completely?
Output fastboot getvar ro.build.fingerprint?
I guess relocking fails because it's like a downgrade for the bootloader while having stock Pie installed.

yes, that is why i am asking for a 10/Q stock firmware so it doesn't have to try reverting backwards to 9/pie
fastboot getvar all...
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 24E8811B00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355************
(bootloader) meid:
(bootloader) date: 12-06-2019
(bootloader) sku: XT1962-1
(bootloader) carrier_sku: XT1962-1
(bootloader) battid: SB18C34004
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 20:48:22 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-14/0cccf:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.20.river.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R RIVER_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld168) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Sat Ap
(bootloader) kernel.version[3]: r 4 06:27:07 CDT 2020
(bootloader) sbl1.git: MBM-2.1-river_retail-516ad1ccba-200404
(bootloader) rpm.git: MBM-2.1-river_retail-22daab39-200404
(bootloader) tz.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) devcfg.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) keymaster.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) cmnlib.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) cmnlib64.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) prov.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) aboot.git: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.012s

natesc0tt said:
yes, that is why i am asking for a 10/Q stock firmware so it doesn't have to try reverting backwards to 9/pie
Click to expand...
Click to collapse
I understand your problem. But there must be any solutions from Motorola for this issue. Otherwise you will have to wait for the Android 10 update.

https://drive.google.com/file/d/1ijf31WzBRAmlwBTtdLcTRPyTDtMjGn0a/view?usp=sharing
---------- Post added at 08:46 PM ---------- Previous post was at 08:46 PM ----------
natesc0tt said:
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"
Click to expand...
Click to collapse
See above

thanks HueyT! Do u know if this is for XT1692-1 variant? What's your venmo? If this works, I'm buying u a beer!

From what I understand, the stock fw for US,IN,EU ect. should be available before too much longer. Tired of waiting too but I'm not ready to risk using anything short of a perfect (signed) match to root with. I miss all my fav. root appz!

FYI, This was my Flashing procedure:
(every step passed besides "flash boot boot.img" <<< failed!)
fastboot oem lock begin
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 system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
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
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock

FYI, This was my Flashing procedure:
(every step passed besides "flash boot boot.img" <<< failed!)
fastboot oem lock begin
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 system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
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
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock

HardBricked Moto G7

Hey guys,
I was trying to install HavocOS on my moto g7(River) and while wiping cache and internal storage through TWRP I accidentally also wiped the System as well, now the phone boots up into fastboot mode with the oem status shows up as Locked. I tried flashing stock Rom using fastboot ( as the phone still enters fastboot mode) it returns a error saying
FAILED (remote: '')
fastboot: error: Command failed
Trying to enter recovers give the following error
Startup failed:
No bootable A/B slot
failed to boot Linux, falling back to fastboot
Boot up failed
And trying to flash TWRP gives the same error
C:\platform-tools>fastboot boot twrp-3.5.2_10-0-river.img
Sending 'boot.img' (32754 KB) OKAY [ 0.710s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
any help would be appreciated.

Ayush758 said:
Hey guys,
I was trying to install HavocOS on my moto g7(River) and while wiping cache and internal storage through TWRP I accidentally also wiped the System as well, now the phone boots up into fastboot mode with the oem status shows up as Locked. I tried flashing stock Rom using fastboot ( as the phone still enters fastboot mode) it returns a error saying
FAILED (remote: '')
fastboot: error: Command failed
any help would be appreciated.
Click to expand...
Click to collapse
Try the following...
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
If it fails to erase userdata, then use fastboot -w. Erase what you can regardless, and reboot directly to the bootloader. Then try flashing vbmeta first. If that doesn't work. Make sure you have the correct firmware and make sure it's the same or a newer version than what you were on. If all else fails, you need to trigger EDL somehow and blank flash.

Spaceminer said:
Try the following...
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
If it fails to erase userdata, then use fastboot -w. Erase what you can regardless, and reboot directly to the bootloader. Then try flashing vbmeta first. If that doesn't work. Make sure you have the correct firmware and make sure it's the same or a newer version than what you were on. If all else fails, you need to trigger EDL somehow and blank flash.
Click to expand...
Click to collapse
Where do I find vbmeta ? The stock firmware image I have does not have vbmeta
this is where I am downloading the stock firmware from https://mirrors.lolinet.com/firmware/moto/river/official/

Ayush758 said:
Where do I find vbmeta ? The stock firmware image I have does not have vbmeta
this is where I am downloading the stock firmware from https://mirrors.lolinet.com/firmware/moto/river/official/
Click to expand...
Click to collapse
I didn't expect that. Start with gpt and the bootloader. See if it works.

Spaceminer said:
I didn't expect that. Start with gpt and the bootloader. See if it works.
Click to expand...
Click to collapse
When I try to flash boot loader I get the following error
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7419 KB) OKAY [ 0.355s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
And when I flash GPT this is the error
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.167s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed

Ayush758 said:
When I try to flash boot loader I get the following error
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7419 KB) OKAY [ 0.355s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
And when I flash GPT this is the error
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.167s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
When in bootloader/fastboot, check what the output of "fastboot getvar all" and it should show build fingerprint in some of the output. Are you flashing same firmware as shown in the output? I'd assume same or newer should work . But otherwise may need to trigger EDL to blank flash as already mentioned

Jleeblanch said:
When in bootloader/fastboot, check what the output of "fastboot getvar all" and it should show build fingerprint in some of the output. Are you flashing same firmware as shown in the output? I'd assume same or newer should work . But otherwise may need to trigger EDL to blank flash as already mentioned
Click to expand...
Click to collapse
This is the output of fastboot getvar all
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-191127
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: b92aa885
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-191127
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
The build fingerprint seems to be blank.

Ayush758 said:
This is the output of fastboot getvar all
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-191127
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: b92aa885
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-191127
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
The build fingerprint seems to be blank.
Click to expand...
Click to collapse
Try running "fastboot oem blankflash" and see if it reboots into EDL mode. If so you'll just need a blank flash file and that should fix you up.

Spaceminer said:
Try running "fastboot oem blankflash" and see if it reboots into EDL mode. If so you'll just need a blank flash file and that should fix you up.
Click to expand...
Click to collapse
Yes it enters blankflash mode , do we have a link to the blank flash file?

Ayush758 said:
Yes it enters blankflash mode , do we have a link to the blank flash file?
Click to expand...
Click to collapse
Oh yeah! There's a bunch of them. What's your model number and device code name? I'll help you find it, and I know where the tools are to run it.
Edit: I found it! River - there are 3 here. https://mirrors.lolinet.com/firmware/moto/river/blankflash/
If those don't work, I know there's more in the threads here. We just gotta find the right one. And here's the tools you'll need. Runs on windows 7/8/10. If you use Linux then I think we'll need to find RSD lite.
QPST utilities

Here's an easy step by step I put together a long time ago. It'll work on the G7 too. Just make sure to use your blank flash files.
successful blankflash on xt1952-4
so after many, many, many hours of tinkering with the blankflash from various devices. i finally got the right combination of files for the singleimage.bin using the blankflash for river. i couldnt say exactly how i ended up getting the device to...
forum.xda-developers.com

Spaceminer said:
Here's an easy step by step I put together a long time ago. It'll work on the G7 too. Just make sure to use your blank flash files.
successful blankflash on xt1952-4
so after many, many, many hours of tinkering with the blankflash from various devices. i finally got the right combination of files for the singleimage.bin using the blankflash for river. i couldnt say exactly how i ended up getting the device to...
forum.xda-developers.com
Click to expand...
Click to collapse
Hey i tried all the steps and thanks to you I can boot back to fast boot menu, but I have having other problems now. I am trying to flash the default firmware here's the list of commands
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
This is the error it returns
flash modem NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65884 KB) OKAY [ 1.945s]
Writing 'modem_a' OKAY [ 0.346s]
Finished. Total time: 2.386s
and also recovery only works if I do fastboot boot recovery.img
once I have access to recovery and i flash the recovery.zip the new installed recovery does not respond to touch screen( I did try older versions of TWRP all have the same issues) .
and it's also not able to mount /data so I have to wipe-> Format data for it to work.

Ayush758 said:
Hey i tried all the steps and thanks to you I can boot back to fast boot menu, but I have having other problems now. I am trying to flash the default firmware here's the list of commands
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
This is the error it returns
flash modem NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65884 KB) OKAY [ 1.945s]
Writing 'modem_a' OKAY [ 0.346s]
Finished. Total time: 2.386s
and also recovery only works if I do fastboot boot recovery.img
once I have access to recovery and i flash the recovery.zip the new installed recovery does not respond to touch screen( I did try older version TWRP all are having the same issues) .
and it's also not able to mount /data so I have to wipe-> Format data for it to work.
Click to expand...
Click to collapse

Ayush758 said:
Hey i tried all the steps and thanks to you I can boot back to fast boot menu, but I have having other problems now. I am trying to flash the default firmware here's the list of commands
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
This is the error it returns
flash modem NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65884 KB) OKAY [ 1.945s]
Writing 'modem_a' OKAY [ 0.346s]
Finished. Total time: 2.386s
and also recovery only works if I do fastboot boot recovery.img
once I have access to recovery and i flash the recovery.zip the new installed recovery does not respond to touch screen( I did try older versions of TWRP all have the same issues) .
and it's also not able to mount /data so I have to wipe-> Format data for it to work.
Click to expand...
Click to collapse
"flash modem NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65884 KB) OKAY [ 1.945s]
Writing 'modem_a' OKAY [ 0.346s]"
This isn't an error. It flashed correctly. Just flash everything in there and in order. The OS should boot up after that.

Spaceminer said:
"flash modem NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65884 KB) OKAY [ 1.945s]
Writing 'modem_a' OKAY [ 0.346s]"
This isn't an error. It flashed correctly. Just flash everything in there and in order. The OS should boot up after that.
Click to expand...
Click to collapse
Okay so I flashed everything but it just boots up and goes to fastboot mode, does not boot up to the OS

Ayush758 said:
Okay so I flashed everything but it just boots up and goes to fastboot mode.
Click to expand...
Click to collapse
Boot stock recovery and factory reset.

Spaceminer said:
Boot stock recovery and factory reset.
Click to expand...
Click to collapse
Recovery mode says No command with a exclamation mark on the android logo.

Ayush758 said:
Recovery mode says No command with a exclamation mark on the android logo.
Click to expand...
Click to collapse
That's good. Hold the power button and tap vol down 2x then release. If that doesn't work try power+Vol up 2x and release.

Spaceminer said:
That's good. Hold the power button and tap vol down 2x then release. If that doesn't work try power+Vol up 2x and release.
Click to expand...
Click to collapse
Thank you for all the help, It was not the recovery but a error I made . The flash commands were wrong I forgot to add some files in the commands list here is the full command list if someone wants to use it.
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 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.1
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
Thank you for you help again man I am able to boot into my phone now . Will make a guide on all this so if someone has the same issue they can fix it.

I have a similar problem with a hard bricked Moto G7. I successfully installed Lineage 18, but was getting error / nag messages at startup. A Motorola pop-up saying the device was unsafe. After about 10 seconds it would then boot into Lineage successfully.
I then rooted the device in an attempt to stop the nag messages, and now it won’t boot up into the OS. It will boot into fastboot / boot loader. But if you try to boot the OS it just goes to a black screen and the OS never starts.
I can’t get it to flash for TWRP. If I type “fastboot devices” the phone will show up in the list. But if I try to flash TWRP.img it says that no devices are present.
I would appreciate any suggestions you might have. Thank you!