Trashed my Bootloader, GPT tables corrupt - Moto G5 Plus Questions & Answers

So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
Code:
$ fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.059s
$ fastboot flash bootloader bootloader.img
Sending 'bootloader' (5115 KB) OKAY [ 0.114s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
Finished. Total time: 0.309s
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Code:
<waiting for device>
Flashing recovery results in
Code:
$ fastboot flash recovery twrp-3.2.3-1-potter.img
Sending 'recovery' (16316 KB) OKAY [ 0.351s]
Writing 'recovery' (bootloader) Image not signed or corrupt
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Finished. Total time: 0.355s
Any help is appreciated!

Drkmatr1984 said:
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Flashing recovery results in
Any help is appreciated!
Click to expand...
Click to collapse
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.

Also, make sure to flash the latest stock firmware, being sure not to try and revert to an earlier version. Don't flash blankflash unless you are totally bricked, with just flashing light. Your device will never be the same if you do.

riyan65 said:
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Click to expand...
Click to collapse
How do I use ADB if I can't get beyond fastboot? I can't load TWRP or flash TWRP to get into it to access ADB. And ADB commands don't work from the fastboot bootloader screen.
Doing "fastboot erase <partition name>" or "fastboot format:ext4 <partition name>" also fails same as the other fastboot flash commands so I can't erase my partitions from fastboot before re-flashing.

If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.

[email protected] said:
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
Click to expand...
Click to collapse
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
Code:
C:\ProgramData\LMSA\Download\RomFiles>fastboot devices
ZY224262W9 fastboot
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.008s
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224262W9 fastboot
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>OREO.BAT
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
FAILED (remote failure)
Finished. Total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.146s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 6.967s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (20580 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
Sending 'oem' (104608 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.012s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.0
Sending 'system' (256553 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.1
Sending 'system' (256617 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.2
Sending 'system' (254213 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.3
Sending 'system' (256710 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.4
Sending 'system' (256912 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.5
Sending 'system' (257861 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.6
Sending 'system' (260027 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.7
Sending 'system' (257601 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.8
Sending 'system' (257805 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
Sending 'modem' (71921 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
Sending 'fsg' (3012 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' FAILED (command write failed
(Unknown error))
Finished. Total time: 34.761s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase customize
Erasing 'customize' FAILED (command write failed
(Unknown error))
Finished. Total time: 14.723s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase clogo
Erasing 'clogo' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
FAILED (command write failed (Unknown error))
Finished. Total time: 5.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
Occasionally I can get a different message
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) OKAY [ 0.325s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
FAILED (status read failed (Too many links))
Finished. Total time: 0.533s
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.005s]
Writing 'partition' (bootloader) Validating 'gpt.
default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.085s
But it always fails.

Drkmatr1984 said:
If all fastboot commands fail, including ,
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
and
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Occasionally I can get a different message
and
But it always fails.
Click to expand...
Click to collapse
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I am using the latest from lolinet, they do not have the latest (OPSS28.85-13-5) uploaded there yet. I did manage to find a copy here But I am at work on slow internet so it may take me all night to finish downloading it

At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.

[email protected] said:
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
Click to expand...
Click to collapse
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!

Drkmatr1984 said:
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Click to expand...
Click to collapse
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6C657D3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 23:25:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-ElementalX-G5-3.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Mon Oct 1 22:31:26 EDT 2018
(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: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-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
Finished. Total time: 0.010s
Is it because the secure boot is on?

You should edit your imei in your getvar output.
When you recovered from hard brick before, did you use Vache's for this device, or the albus blankflash for Addison?
I assume you are trying to get into recovery by using the volume button, but have you tried fastboot commands.
Code:
fastboot reboot recovery
sometimes works.
With a copy of TWRP in your adb/fastboot folder, try
Code:
fastboot boot image twrp.img
or
Code:
fastboot boot recovery twrp.img
where you have renamed your TWRP image to the twrp.img. This boots into twrp without installing, and has been reported to work with fubarred partition tables. If it boots, you then can access tools to repair gpt partition tables via adb.

Drkmatr1984 said:
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Is it because the secure boot is on?
Click to expand...
Click to collapse
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!

nicolap8 said:
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
Click to expand...
Click to collapse
Ok, thanks! and done!
I will give these new suggestions a try later tonight. I did hear about booting into TWRP before, but have had little luck with that. However, I think I have only tried fastboot boot twrp.img and not with recovery or image as keywords in there...

OK, so the two fastboot commands are not the correct syntax.
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot image twrp.img
fastboot: error: cannot load 'image': No such file or directory
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory
Doing this:
Code:
$ fastboot boot boot.img recovery.img
fastboot: error: cannot boot a boot.img *and* ramdisk
Almost works lol
"fastboot reboot recovery" just gives this:
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Doing "fastboot boot twrp.img" works but it hangs at the "your device is not safe" screen and never actually loads. "fastboot getvar all" returns interesting things in the slot section. Those slots don't seem normal to me. Also, my ro.fingerprint looks like it's for nougat, but my bootloader is Oreo. I'm willing to break this phone to fix it if possible, so if anyone has any riskier suggestions for me to try I'm down as I've already gone 4 days without a phone and am about to buy a new one either way.

Drkmatr1984 said:
OK, so the two fastboot commands are not the correct syntax.
Click to expand...
Click to collapse
If you are not able to get the fastboot help you have not to try to flash anything!

nicolap8 said:
If you are not able to get the fastboot help you have not to try to flash anything!
Click to expand...
Click to collapse
What? I don't understand you.
I am reading this
And am trying to understand the fastboot boot command better. It requires a kernel image and a ramdisk image. So far I have tried by using zImage from ElementalX kernel as kernel and twrp.img as Ramdisk but the boot just hangs for a long time. Does anyone know the Correct command to boot into TWRP(and kernel) from USB on this device? (Confirmed working and tested, please!)
Here are all of my attempts so far:
Code:
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26769408 bytes
Downloading 'boot.img' OKAY [ 0.563s]
booting OKAY [ 0.080s]
Finished. Total time: 0.860s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26611712 bytes
Downloading 'boot.img' OKAY [ 0.554s]
booting OKAY [ 0.073s]
Finished. Total time: 0.667s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot linux-2.6/arch/arm/boot/zImage twrp.img
fastboot: error: cannot load 'linux-2.6/arch/arm/boot/zImage': No such file or directory
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot Ele
ElementalX-G5-3.00.zip elex.zImage
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot ElementalX-G5-3.00.zip twrp.img
creating boot image...
creating boot image - 29065216 bytes
Downloading 'boot.img' OKAY [ 0.606s]
booting OKAY [ 0.081s]
Finished. Total time: 0.764s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage twrp.img
creating boot image...
creating boot image - 23590912 bytes
Downloading 'boot.img' OKAY [ 0.496s]
booting OKAY [ 0.109s]
Finished. Total time: 0.642s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage
creating boot image...
creating boot image - 6883328 bytes
Downloading 'boot.img' OKAY [ 0.154s]
booting OKAY [ 0.079s]
Finished. Total time: 0.245s

Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?

Drkmatr1984 said:
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Click to expand...
Click to collapse
fastboot boot twrp.img

craigl14 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
That only works when you have a boot partition that is intact.
Since my partition tables are ****ed it just hangs at boot when I run that command. I need the full command with kernel option to make it boot so that I can edit the partitions from TWRP. However, I don't know enough about the kernel of this phone, or where to obtain its sources, or how to compile them, or any of that to make it work. I'm hoping one of the ROM devs will clue me in as I can't be the only person with this phone to ever Fubar their partition tables.
I found this :
Code:
To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Which seems to suggest it's possible but I just need the correct kernel and rootfs image to boot TWRP.

Related

need the stock fastboot rom for the build npjs 25.93-14.4, (March security patch)

In need of the full stock firmware for the latest build NPJS 25.93-14.4(march security patch) with the bootloader relocking ability, just like the link below for the build NPJ25-93-14 as it won't allow me downgrade and relock the bootloader anymore:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
In need for relocking the bootloader as I need to try my luck with the service center for the screen burn issue.
Any help would be really appreciated.
Much thanks in advance.
You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Note that the first two lines HAVE to be repeated like that.
C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>fastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.017s
C:\mfastboot>fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.006s]
finished. total time: 0.007s
it says still still require signed boot.img
I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?
SoNic67 said:
I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?
Click to expand...
Click to collapse
I'm on NPJS 25.93.14.4, i'll just downgrade to 25-93-14 and check with the commands provided.
Btw, thank you and sorry as I'm a noob and bothering you again and again.
just one thing, I'll be using the following commnads:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
for downgrading to 93-14.
That would be fine right?
Yeah, fastboot or mfastboot are equal. It's a batch file in that zip file that does the locking automatically:
Code:
mfastboot oem lock begin
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot
C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>mfastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.011s]
finished. total time: 0.012s
C:\mfastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.043s
C:\mfastboot>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (3651 KB)...
OKAY [ 0.153s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.433s]
finished. total time: 0.589s
C:\mfastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2105 KB)...
OKAY [ 0.084s]
writing 'logo'...
OKAY [ 0.055s]
finished. total time: 0.142s
C:\mfastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.653s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.821s
C:\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.649s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.819s
C:\mfastboot>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.648s]
writing 'dsp'...
OKAY [ 0.242s]
finished. total time: 0.894s
C:\mfastboot>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (96490 KB)...
OKAY [ 3.744s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.804s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261001 KB)...
OKAY [ 10.083s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.149s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250858 KB)...
OKAY [ 9.720s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.749s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (254625 KB)...
OKAY [ 9.288s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.317s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (261577 KB)...
OKAY [ 9.615s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.636s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (260443 KB)...
OKAY [ 9.842s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.880s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (248842 KB)...
OKAY [ 9.306s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.332s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (259549 KB)...
OKAY [ 9.799s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.843s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (82497 KB)...
OKAY [ 3.210s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.229s
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (76954 KB)...
OKAY [ 3.005s]
writing 'modem'...
OKAY [ 1.133s]
finished. total time: 4.142s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.031s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (2040 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 0.064s]
finished. total time: 0.151s
C:\mfastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.322s]
finished. total time: 1.352s
C:\mfastboot>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\mfastboot>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.017s]
finished. total time: 0.019s
C:\mfastboot>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.004s]
finished. total time: 0.006s
C:\mfastboot>mfastboot reboot
SoNic67 said:
You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
Note that the first two lines HAVE to be repeated like that.
Click to expand...
Click to collapse
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.
MK+2017 said:
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.
Click to expand...
Click to collapse
yupp, i too think that the bootloader can only be relocked if the latest official firmware with the latest security patch is flashed via fastboot.
If possible can anyone please provide the latest firmware for xt1643 with the march sec. patch?
I have assumed that he has just installed the update and didn't change anything in the system.
i am on stock 93-14 build, dec sec. patch. Now should i have to wait for the march firmware to be posted or is there anything else that i can still do to lock the bootloader?
Once you flash an official OTA, you cannot downgrade the bootloader and partition table to a previous version. And locking the bootloader will need the latest fastboot firmware. Also, please consider using something like pastebin or hastebin for such long logs/outputs.
that is what i need, is it possible to create the new firmware using the latest ota file?
That's I haven't updated to 93-14-4 build cause you never know what goes wrong with your phone BTW way you can temporarily fix the screen burn issue by changing the RGB values using kernel auditor or ex kernel manager
Sent from my Moto G4 Plus using Tapatalk
yupp, i am using the bluelight filter for the time being
Same thing here, guess we have to wait for official and complete firmware... -_-
yupp, waiting for the same
Good Ness e
https://forum.xda-developers.com/mo...rom-npjs25-93-14-4-march-1-t3608138?nocache=1

bootloader is bricked

Hello,
I have bricked my bootloader in the past to refresh my bootloader. I have unbricked my phone to bootloader 1.03 with blank flash. Now when i try to flash, erase do ANYTHING it won't allow me because my OEM_LOCKED state. If i try to unlock my bootloader it says:
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.032s]
finished. total time: 0.036s
but there is no android installed.
When i try to flash a stock rom it says:
Code:
C:\Users\nick\Desktop\total firmware>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.068s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.088s
C:\Users\nick\Desktop\total firmware>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.540s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.576s
C:\Users\nick\Desktop\total firmware>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.548s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.568s
C:\Users\nick\Desktop\total firmware>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.532s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.560s
C:\Users\nick\Desktop\total firmware>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [ 3.993s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 4.017s
C:\Users\nick\Desktop\total firmware>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...
Everything is 'invalid partition name'.
when i try to brick my bootloader again to install try again it says
Code:
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
(bootloader) Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.036s
rebooting...
And when i try to flash another bootloader it says:
Code:
PS C:\Users\nick\Desktop\total firmware> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.250s
PS C:\Users\nick\Desktop\total firmware>
please help
I guess there is a partion problem
Look into this thread
https://forum.xda-developers.com/showthread.php?t=3496912
Sent from my Moto G4 Plus using Tapatalk
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
codGmer said:
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
Click to expand...
Click to collapse
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
givitago said:
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
Click to expand...
Click to collapse
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
codGmer said:
Did you run all stock steps in order? In particular this one first:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
I too have this question bro .... Plus help me if you find a solution ... I m a newbie... Nd face the same problem as yours
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
givitago said:
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
Click to expand...
Click to collapse
Im affraid i already tried booting twrp but without success.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(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: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(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) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s
hey bro , did you get any solution of this problem?
i am getting
fastboot reason : failed to initialize partition table
any solution?
king_priithvi said:
hey bro , did you get any solution of this problem?
Click to expand...
Click to collapse
Provide more information of your problem/situation,
what happened ?
Have you flashed any firmware ?
Took any OTA ?
What was firmware version you were using ?
Tried latest December's firmware ? This> https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I think you're flashing older bootloader & GPT then it is already installed on your device;
take a look here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
from that thread download the latest ROM and firstly flash GPT and boot-loader by following command:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
but however after flashing the latest firmware the current blankflash that we have won't work, because GPT and boot-loader version is higher.
now after you flashed the GPT and bootloader then flash the whole firmware by following commands:
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
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
Now once you flashed it then you're good to go:good:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
king_prithvi said:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
Click to expand...
Click to collapse
Are you able to flash the latest stock ROM via fastboot? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
kiyip said:
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
Click to expand...
Click to collapse
What device do you have? I'm guessing it's a Moto X4 from the TWRP name?
Are you on Nougat or Oreo? From looking at this thread, you've got 2 different build: https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432
If you are running a X4, you may have better luck over there rather than here on the Moto G4 forums, as there's more users familiar with the A/B partitioning on the Moto X4.
Ohh my bad, I had like 6 xda tabs open, I actually meant to post it there. My bad man, thank you!
got the same problem any luck yet?
Any luck yet? I got a suggestion that the problem could only get fixed flashing the memory of the phone directly with this kind of device... (search for the octopus box, I cant post links yet im new here) but im lost and they say that thing is expensive... I really want my phone to be saved on my computer. My case is exactly the same as you.... oem locked and failed partition everything and remote failure.
SOLVED!! Failed to initialize partition table
..
First of all convert phone to hard brick to Softbrick...
After that if you want to bootup phone than..IT shows bootloader log::
Failed to initialize partition Table
SOLUTION:-
1) Download Minimal ADB Drivers , gpt.bin, Motorola Device driver
For link mail me on [email protected]
2.) Now Install adb and motorola drivers .
3.) Copy gpt.bin file in ADB folder in installed drive.
4.) Open Minimal ADB and Fastboot.exe
Now Run the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot
The cell phone should restart after this if you do not type the last code and enter if still yes it is not just hang up and call to enter the fastboot.
Now YOUR PROBLEM SOLVED
codGmer said:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
Copy the gpt.biin file in that folder and try again, that should work.

[Start Up Failed] [Error: Failed to pass validation ] I cant flash stock.

First: Sorry for my horrible english.
Second: I have a G5+ with a wrong SKU model (See screenshots) XT1601 (Is from G4 play, and yes, the phone is original)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, the other day i want to flash via terminal stock 8. ( I cant unlock bootloader, so i cant have twrp or similar)
And... My phone got bricked. And now, i cant unlock OEM, and cant flash any rom via all the known methods (Lenovo assistant etc) because the assistant dont recognize my phone (Bc the model in the phone is wrong XT1601) and i dont know what rom i need to flash because i dont find the exact rom i have working before.
And when i try to flash any rom i got this kind of messages in my device:
[Start Up Failed] [Error: Failed to pass validation ] [Fastboot reason: UTAG "bootmode" configured on fastboot]
And the Stock Recovery is gone.
I try to unlock OEM via all the known methos with no luck.
And i try THIS without any luck too.
Any method to revive the phone?
Thanks!
Did you try fastboot oem fb_mode_clear ?
May be try to flash a newer firmware. The latest one.
Oreo has 9 system files. systemsparsechunk(0-8). Did you flash all the files? Bc some guides have only 5 files(0-4).
debdeep98 said:
Did you try fastboot oem fb_mode_clear ?
May be try to flash a newer firmware. The latest one.
Oreo has 9 system files. systemsparsechunk(0-8). Did you flash all the files? Bc some guides have only 5 files(0-4).
Click to expand...
Click to collapse
My device dont have recovery Stock anymore, is this a problem?
And, what rom i need to flash?
Gothorian said:
My device dont have recovery Stock anymore, is this a problem?
And, what rom i need to flash?
Click to expand...
Click to collapse
No need to use recovery. You need to boot into bootloader (also no need to be unlocked) and enter the command debdeep98 suggests.
lpulido said:
No need to use recovery. You need to boot into bootloader (also no need to be unlocked) and enter the command debdeep98 suggests.
Click to expand...
Click to collapse
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.
Gothorian said:
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.
Click to expand...
Click to collapse
Can you post the picture of bootloader, so we could confirm which firmware your device needs.but still you You could flash your country firmware from here.
Link:-https://mirrors.lolinet.com/firmware/moto/potter/official/
And here is the procedure thread :-https://forum.xda-developers.com/g5...stboot-flash-stock-oreo-t3848433/post77752702
Gothorian said:
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.
Click to expand...
Click to collapse
So I'm guessing your model is xt1680. So just flash the latest retail firmware 85-17-6 from link riyan mentioned. Update channels won't matter anymore since update cycle is over.
debdeep98 said:
So I'm guessing your model is xt1680. So just flash the latest retail firmware 85-17-6 from link riyan mentioned. Update channels won't matter anymore since update cycle is over.
Click to expand...
Click to collapse
Ok, let me try, but u need to know i downloaded the correct rom i have before and try to flash it without luck. And the terminal give me this kind of results (And with other roms i try too):
And then, i reboot my phone and got Start Up Failed. Error: Failed to pass validation etc etc etc.
Edit: Yes, i have drivers installed.
Gothorian said:
Ok, let me try, but u need to know i downloaded the correct rom i have before and try to flash it without luck. And the terminal give me this kind of results (And with other roms i try too):
And then, i reboot my phone and got Start Up Failed. Error: Failed to pass validation etc etc etc.
Click to expand...
Click to collapse
Yeah.. no.. It says security version downgrade.. Means you are on a newer firmware and you are trying to flash an older firmware.. Try the latest firmware..
Try
Code:
fastboot getvar all
. This should show the last build id.. it should be (bootloader) ro.build.fingerprint. something like this.. you either get the lastest firmware or the one you are already on..
I don't remember correctly but flashing older firmware bricks the device. I think. There are guides to restore.
Edit. Okay just saw that you are on 92-4. Just try an OPS build.
debdeep98 said:
Yeah.. no.. It says security version downgrade.. Means you are on a newer firmware and you are trying to flash an older firmware.. Try the latest firmware..
Try
Code:
fastboot getvar all
. This should show the last build id.. it should be (bootloader) ro.build.fingerprint. something like this.. you either get the lastest firmware or the one you are already on..
I don't remember correctly but flashing older firmware bricks the device. I think. There are guides to restore.
Edit. Okay just saw that you are on 92-4. Just try an OPS build.
Click to expand...
Click to collapse
Sorry im new with Moto Devices, (All my life i have Samsungs) what are OPS build? And where i find it?
Thanks for u help.
Gothorian said:
Sorry im new with Moto Devices, (All my life i have Samsungs) what are OPS build? And where i find it?
Thanks for u help.
Click to expand...
Click to collapse
Your build no (compilacion) starts with NPS. That is a nougat(7) build. OPS are the Oreo(8) builds.
What is the version of the firmware you are trying to flash? And which guide are you using?
debdeep98 said:
Your build no (compilacion) starts with NPS. That is a nougat(7) build. OPS are the Oreo(8) builds.
What is the version of the firmware you are trying to flash? And which guide are you using?
Click to expand...
Click to collapse
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.
Gothorian said:
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.
Click to expand...
Click to collapse
Why don't you use Lenovo Moto smart assistant app in your pc as it will flash the device with the latest firmware and you don't need to do anything.
riyan65 said:
Why don't you use Lenovo Moto smart assistant app in your pc as it will flash the device with the latest firmware and you don't need to do anything.
Click to expand...
Click to collapse
Because Lenovo Moto smart assistant dont recognize mi phone.
Gothorian said:
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.
Click to expand...
Click to collapse
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.
debdeep98 said:
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.
Click to expand...
Click to collapse
Let me try flashing the rom u post. And no. I cant unlock bootloader sadly.
debdeep98 said:
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.
Click to expand...
Click to collapse
Still nothing. I adjunt the code in ADB/Fastboot:
Code:
Microsoft Windows [Versión 10.0.17763.503]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot devices
ZY2245XNKB fastboot
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.203s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.156s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.781s]
finished. total time: 0.922s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.141s]
finished. total time: 0.234s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>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.407s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.516s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.812s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.391s]
writing 'dsp'...
OKAY [ 0.297s]
finished. total time: 0.719s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.516s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.687s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256557 KB)...
OKAY [ 6.141s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.312s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256617 KB)...
OKAY [ 6.098s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.176s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (253985 KB)...
OKAY [ 6.092s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.186s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256710 KB)...
OKAY [ 6.178s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.240s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256912 KB)...
OKAY [ 6.093s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.125s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (257861 KB)...
OKAY [ 6.069s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.147s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260027 KB)...
OKAY [ 6.191s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.269s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (257785 KB)...
OKAY [ 6.129s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.223s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (257830 KB)...
OKAY [ 6.194s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.272s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.735s]
writing 'modem'...
OKAY [ 1.141s]
finished. total time: 2.891s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.062s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.235s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.187s]
finished. total time: 0.203s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.266s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.172s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.578s]
finished. total time: 0.766s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.234s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.703s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.532s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.828s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.391s]
writing 'dsp'...
OKAY [ 0.301s]
finished. total time: 0.722s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.506s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.646s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256557 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.274s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256617 KB)...
OKAY [ 6.109s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.140s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (253985 KB)...
OKAY [ 6.156s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.218s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (256710 KB)...
OKAY [ 6.172s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.234s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (256912 KB)...
OKAY [ 6.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.048s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (257861 KB)...
OKAY [ 6.265s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.312s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (260027 KB)...
OKAY [ 6.356s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.396s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (257785 KB)...
OKAY [ 6.057s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.182s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (257830 KB)...
OKAY [ 6.156s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.203s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 1.109s]
finished. total time: 2.875s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.062s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.219s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.187s]
finished. total time: 0.187s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
And in Fastboot i got this:Invalid PIV system image. Why the phone cant flash any rom? it worries me.
In Bootloader Logs i got this:
Set Up Failed. Your device didn't start up successfully try to conect...
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-Through from normal boot mode
And yes, im trying flash the rom u gaveme.
Gothorian said:
Still nothing. I adjunt the code in ADB/Fastboot:
And in Fastboot i got this:Invalid PIV system image. Why the phone cant flash any rom? it worries me.
In Bootloader Logs i got this:
Set Up Failed. Your device didn't start up successfully try to conect...
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-Through from normal boot mode
And yes, im trying flash the rom u gaveme.
Click to expand...
Click to collapse
Can you post the procedure how you are flashing the ROM in device.
riyan65 said:
Can you post the procedure how you are flashing the ROM in device.
Click to expand...
Click to collapse
Im use this procedure, basically y extract the xml.zip into fastboot lite folder, run the CMD first i do "fastboot device" if the pc recognize my phone and copy/paste all the commands and wait.
Did you buy the device brand new or was it second hand?
It looks like the device was already bricked once and someone blank flashed it.
Flashing isn't working because the model no is different probably.
Someone managed to flash oreo with the Z Play bootloader the phone boots up but there is no connectivity.

Can't flash rom, stuck in TWRP recovery

I've had my G4+ rooted for quite a while and i need to format it so my mom can have it since I recently changed to a OnePlus 6T.
I tried to use the factory reset from the settings (seems like it was a big mistake on my part) and it didn't work, so I'm now trying to flash a stock rom through adb (I'd done this before), but I don't know what I need to do at this point, I'm at a loss, I even tried the commands to flash the rom and it seems to copy the system files but some stuff fails in the process.. I don't know what to do, did I just brick my device? please help
In case that helps, I have TWRP installed
And I think this might help, I personally don't know what to do with this info but this is what the command prompt throws back at me when trying to flash the custom rom while in bootloader mode:
D:\Downloads\Moto G4\platform-tools>adb devices List of devices attached
D:\Downloads\Moto G4\platform-tools>fastboot oem fb_mode_set OKAY [ 0.003s] Finished. Total time: 0.007s
D:\Downloads\Moto G4\platform-tools>fastboot flash partition gpt.bin (bootloader) has-slotartition: not found (bootloader) is-logicalartition: not found Sending 'partition' (32 KB) OKAY [ 0.170s] Writing 'partition' (bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash bootloader bootloader.img (bootloader) has-slot:bootloader: not found (bootloader) is-logical:bootloader: not found Sending 'bootloader' (2546 KB) OKAY [ 0.250s] Writing 'bootloader' (bootloader) Invalid partition name bootloader FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash logo logo.bin (bootloader) has-slot:logo: not found (bootloader) is-logical:logo: not found Sending 'logo' (2833 KB) OKAY [ 0.259s] Writing 'logo' OKAY [ 0.064s] Finished. Total time: 0.669s
D:\Downloads\Moto G4\platform-tools>fastboot flash boot boot.img (bootloader) has-slot:boot: not found (bootloader) is-logical:boot: not found Sending 'boot' (32768 KB) OKAY [ 1.203s] Writing 'boot' (bootloader) Image size exeeded partition limits (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash recovery recovery.img (bootloader) has-slot:recovery: not found (bootloader) is-logical:recovery: not found Sending 'recovery' (32752 KB) OKAY [ 1.202s] Writing 'recovery' (bootloader) Image size exeeded partition limits (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.0 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (262143 KB) OKAY [ 8.414s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.1 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (262142 KB) OKAY [ 8.415s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.2 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (239188 KB) OKAY [ 7.693s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.3 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (258879 KB) OKAY [ 8.313s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.4 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (260734 KB) OKAY [ 8.370s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.5 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (239870 KB) OKAY [ 7.714s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.6 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (232504 KB) OKAY [ 7.482s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.7 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (257945 KB) OKAY [ 8.283s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.8 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (257992 KB) OKAY [ 8.286s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.9 (bootloader) has-slot:system: not found (bootloader) is-logical:system: not found Sending 'system' (168148 KB) OKAY [ 5.483s] Writing 'system' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash modem NON-HLOS.bin (bootloader) has-slot:modem: not found (bootloader) is-logical:modem: not found Sending 'modem' (37144 KB) OKAY [ 1.341s] Writing 'modem' OKAY [ 0.569s] Finished. Total time: 2.398s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst1 (bootloader) has-slot:modemst1: not found Erasing 'modemst1' OKAY [ 0.022s] Finished. Total time: 0.222s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst2 (bootloader) has-slot:modemst2: not found Erasing 'modemst2' OKAY [ 0.023s] Finished. Total time: 0.241s
D:\Downloads\Moto G4\platform-tools>fastboot flash fsg fsg.mbn (bootloader) has-slot:fsg: not found (bootloader) is-logical:fsg: not found Sending 'fsg' (1260 KB) OKAY [ 0.210s] Writing 'fsg' OKAY [ 0.051s] Finished. Total time: 0.469s
D:\Downloads\Moto G4\platform-tools>fastboot erase cache (bootloader) has-slot:cache: not found Erasing 'cache' OKAY [ 0.015s] Finished. Total time: 0.214s
D:\Downloads\Moto G4\platform-tools>fastboot erase userdata (bootloader) has-slot:userdata: not found Erasing 'userdata' OKAY [ 0.127s] Finished. Total time: 0.327s
D:\Downloads\Moto G4\platform-tools>fastboot erase customize (bootloader) has-slot:customize: not found Erasing 'customize' OKAY [ 0.013s] Finished. Total time: 0.214s
D:\Downloads\Moto G4\platform-tools>fastboot erase clogo (bootloader) has-slot:clogo: not found Erasing 'clogo' OKAY [ 0.015s] Finished. Total time: 0.217s
D:\Downloads\Moto G4\platform-tools>fastboot oem fb_mode_clear OKAY [ 0.004s] Finished. Total time: 0.008s
D:\Downloads\Moto G4\platform-tools>
Click to expand...
Click to collapse
Also, I tried wiping system, data, cache and dalvik-cache and here's what TWRP says: TWRP Errors
I get similar errors when trying to install my stock zip (from the external sd, I don't have an OTG cable right now so I copied to the sd card)
Is it possible the bootloader was re-locked with fastboot?
What's the ROM version you're trying to flash? Assuming TWRP hasn't been replaced by stock recovery and you can still load it, it would be interesting to know what kind of errors happen if you tried a TWRP flashable ROM instead of a fastboot ROM. Use the phone's internal storage (/sdcard directory) and avoid using an external SD card. But first see if you can both format and wipe in TWRP without errors.
You don't need an OTG cable for any of this. To simplify trouble shooting, eliminate the external SD card even if temporarily.
manjaroid said:
Is it possible the bootloader was re-locked with fastboot?
What's the ROM version you're trying to flash? Assuming TWRP hasn't been replaced by stock recovery and you can still load it, it would be interesting to know what kind of errors happen if you tried a TWRP flashable ROM instead of a fastboot ROM. Use the phone's internal storage (/sdcard directory) and avoid using an external SD card. But first see if you can both format and wipe in TWRP without errors.
You don't need an OTG cable for any of this. To simplify trouble shooting, eliminate the external SD card even if temporarily.
Click to expand...
Click to collapse
I'm trying to flash a stock ROM from this thread: http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364.
I'm still using TWRP, it wasn't replaced by stock fortunately. I'll download one or two flashable roms and see if that works.
Also, just tried to go through the process of unlocking the bootloader (in case it was re-locked as you say), and when putting the unique key and all, it says:
Code:
(bootloader) invalid boot state
And something I missed to mention now that I think about it, upon booting the phone it doesn't show the usual unlocked bootloader warning, instead its all black and it just says: "N/A" literally.
Now, upon trying to flash a TWRP flashable ROM, specifically "AFH" from the Nougat 7.0 section of this thread, I got the following:
Image 1
Image 2
Zedlav said:
I'm trying to flash a stock ROM from this thread: http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364.
Click to expand...
Click to collapse
I'm curious why you installed Moto X Play firmware to a G4 Plus. Or was the URL above a mistake and you meant this one?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
---------- Post added at 10:33 PM ---------- Previous post was at 10:02 PM ----------
Zedlav said:
Also, just tried to go through the process of unlocking the bootloader (in case it was re-locked as you say), and when putting the unique key and all, it says:
Code:
(bootloader) invalid boot state
Click to expand...
Click to collapse
That error indicates your bootloader is already unlocked. Flashing errors probably mean you're attempting to flash outdated firmware which sometimes causes problems with Motorola phones, so best to use the same or newer firmware than what was previously installed. See what happens with Oreo.
I suggest starting from scratch as cleanly as possible. I would even re-flash TWRP (official for G4 athene) for extra measure. And note the TWRP instructions about rebooting back into TWRP before flashing your Android ROM to avoid having to repeat installing TWRP. Also, the /system partition needs to be read-only if and when TWRP prompts you about it.
Format and wipe as described here: https://andi34.github.io/faq/faq_twrp.html
Then with the phone in fastboot mode and connected to your PC, flash the latest fastboot 8.1.0 ROM which will replace TWRP with stock recovery. If Android starts and runs normally after that, you should be able to re-lock the bootloader and hand it off to your mom.
And something I missed to mention now that I think about it, upon booting the phone it doesn't show the usual unlocked bootloader warning, instead its all black and it just says: "N/A" literally.
Click to expand...
Click to collapse
You'll see the N/A notice on the boot screen when booting into recovery or a custom ROM is booting. Once stock is running N/A should go away.
I'm curious why you installed Moto X Play firmware to a G4 Plus. Or was the URL above a mistake and you meant this one?
https://forum.xda-developers.com/mot...rch-1-t3608138
Click to expand...
Click to collapse
Oh god, I had been using the wrong rom all this time LOL, but it was working, I mean, before all of this I had flashed that x play stock rom on the g4 plus and it was working without a problem for some reason..
I suggest starting from scratch as cleanly as possible. I would even re-flash TWRP (official for G4 athene) for extra measure. And note the TWRP instructions about rebooting back into TWRP before flashing your Android ROM to avoid having to repeat installing TWRP. Also, the /system partition needs to be read-only if and when TWRP prompts you about it.
Format and wipe as described here: https://andi34.github.io/faq/faq_twrp.html
Then with the phone in fastboot mode and connected to your PC, flash the latest fastboot 8.1.0 ROM which will replace TWRP with stock recovery. If Android starts and runs normally after that, you should be able to re-lock the bootloader and hand it off to your mom.
Click to expand...
Click to collapse
Alright, so I reflashed TWRP, did the whole format and wipe thing: Format results Wipe results
I'm downloading the 8.0 image from the stock thread you linked me but its going to take a while, the servers seem to be very slow. In the meantime i tried flashing the twrp-flashable one I downloaded earlier: Image 1 Image 2 Image 3
It would seem it went okay, but I rebooted and nothing changed, so I tried flashing the X Play image i had as I had done before, but I still got errors in the process and it didn't work:
D:\Downloads\Moto G4\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.004s]
Finished. Total time: 0.016s
D:\Downloads\Moto G4\platform-tools>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (32 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (2546 KB) OKAY [ 0.251s]
Writing 'bootloader' (bootloader) Invalid partition name bootloader
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (2833 KB) OKAY [ 0.260s]
Writing 'logo' OKAY [ 0.065s]
Finished. Total time: 0.670s
D:\Downloads\Moto G4\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (32768 KB) OKAY [ 1.203s]
Writing 'boot' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (32752 KB) OKAY [ 1.203s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262143 KB) OKAY [ 8.415s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262142 KB) OKAY [ 8.415s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (239188 KB) OKAY [ 7.693s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (258879 KB) OKAY [ 8.312s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (260734 KB) OKAY [ 8.370s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (239870 KB) OKAY [ 7.714s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (232504 KB) OKAY [ 7.482s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257945 KB) OKAY [ 8.283s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257992 KB) OKAY [ 8.286s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.9
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (168148 KB) OKAY [ 5.458s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
D:\Downloads\Moto G4\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (37144 KB) OKAY [ 1.337s]
Writing 'modem' OKAY [ 0.570s]
Finished. Total time: 2.365s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.026s]
Finished. Total time: 0.242s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.024s]
Finished. Total time: 0.222s
D:\Downloads\Moto G4\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (1260 KB) OKAY [ 0.210s]
Writing 'fsg' OKAY [ 0.050s]
Finished. Total time: 0.468s
D:\Downloads\Moto G4\platform-tools>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.214s
D:\Downloads\Moto G4\platform-tools>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.475s]
Finished. Total time: 0.673s
D:\Downloads\Moto G4\platform-tools>fastboot erase customize
(bootloader) has-slot:customize: not found
Erasing 'customize' OKAY [ 0.013s]
Finished. Total time: 0.211s
D:\Downloads\Moto G4\platform-tools>fastboot erase clogo
(bootloader) has-slot:clogo: not found
Erasing 'clogo' OKAY [ 0.015s]
Finished. Total time: 0.211s
D:\Downloads\Moto G4\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.004s]
Finished. Total time: 0.007s
D:\Downloads\Moto G4\platform-tools>fastboot reboot
Rebooting OKAY [ 0.004s]
Finished. Total time: 0.009s
Click to expand...
Click to collapse
When I'm able to download the stock g4 plus image from the thread i'll try with that one and post my results, but I still don't understand what's going on
First off, whether you're flashing stock or custom, you need to stick to firmware specifically for Moto G4/G4 Plus athene. Just because firmware from a different Moto booted your phone doesn't mean it's working. Ditto for TWRP so make sure you're using the official release for G4 athene. An unofficial fork of TWRP probably won't do any harm, but for trouble shooting a stock Android install, there's no reason to stray from official TWRP.
Zedlav said:
....I'm downloading the 8.0 image...
Click to expand...
Click to collapse
Verify that this ROM is version 8.1.0 build OPJ28.111-22 or the more recent build OPJ28.111-22-1. If the ROM is literally version 8.0 that's not right.
Based on your fastboot errors, I'm wondering at this point if partitions have been mangled and even the correct firmware isn't going to flash successfully. Even if the phone boots and everything appears well at first glance, you could find out something is terribly wrong. Like the radio not working because EFS partitions (IMEI) are messed up.
Right now I'm not sure how to advise. I'm tempted to say "blankflash" but I don't think you're there yet because the phone is starting and you can load recovery. Let's hope somebody with more experience chimes in.
For now I suggest disregarding TWRP flashable ROMs and plan on getting through this with adb and fastboot.
I decided to give it another try, from the start:
Formatted data, then dalvik + system + cache, no problems, no red messages or anything lol
Then, reflashing TWRP:
D:\Downloads\Moto G4\platform-tools>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.569s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.189s]
Finished. Total time: 0.967s
Click to expand...
Click to collapse
I guess that's.. not 100% okay but.. alright.
Now, as usual, bunch of errors while flashing:
D:\Downloads\Moto G4\platform-tools>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (32 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.088s]
Finished. Total time: 0.469s
D:\Downloads\Moto G4\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (3651 KB) OKAY [ 0.285s]
Writing 'bootloader' (bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.426s]
Finished. Total time: 0.922s
D:\Downloads\Moto G4\platform-tools>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (2186 KB) OKAY [ 0.239s]
Writing 'logo' OKAY [ 0.056s]
Finished. Total time: 0.502s
D:\Downloads\Moto G4\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.686s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.381s]
Finished. Total time: 1.320s
D:\Downloads\Moto G4\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.689s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.414s]
Finished. Total time: 1.321s
D:\Downloads\Moto G4\platform-tools>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.685s]
Writing 'dsp' OKAY [ 0.244s]
Finished. Total time: 1.457s
D:\Downloads\Moto G4\platform-tools>fastboot flash oem oem.img
(bootloader) has-slotem: not found
(bootloader) is-logicalem: not found
Sending 'oem' (69480 KB) OKAY [ 2.356s]
Writing 'oem' OKAY [ 0.988s]
Finished. Total time: 4.045s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (256517 KB) OKAY [ 8.240s]
Writing 'system' OKAY [ 3.703s]
Finished. Total time: 14.796s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (258339 KB) OKAY [ 8.297s]
Writing 'system' OKAY [ 3.449s]
Finished. Total time: 13.631s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (260247 KB) OKAY [ 8.356s]
Writing 'system' OKAY [ 3.572s]
Finished. Total time: 14.133s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261038 KB) OKAY [ 8.381s]
Writing 'system' OKAY [ 3.399s]
Finished. Total time: 15.160s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (258070 KB) OKAY [ 8.286s]
Writing 'system' OKAY [ 3.368s]
Finished. Total time: 15.010s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262061 KB) OKAY [ 8.413s]
Writing 'system' OKAY [ 3.328s]
Finished. Total time: 13.900s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (244352 KB) OKAY [ 7.856s]
Writing 'system' OKAY [ 3.871s]
Finished. Total time: 14.325s
D:\Downloads\Moto G4\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (88696 KB) OKAY [ 2.959s]
Writing 'system' OKAY [ 1.172s]
Finished. Total time: 4.785s
D:\Downloads\Moto G4\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (69401 KB) OKAY [ 2.353s]
Writing 'modem' OKAY [ 1.004s]
Finished. Total time: 4.087s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.027s]
Finished. Total time: 0.225s
D:\Downloads\Moto G4\platform-tools>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.023s]
Finished. Total time: 0.222s
D:\Downloads\Moto G4\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2104 KB) OKAY [ 0.235s]
Writing 'fsg' OKAY [ 0.063s]
Finished. Total time: 0.506s
D:\Downloads\Moto G4\platform-tools>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.018s]
Finished. Total time: 0.215s
D:\Downloads\Moto G4\platform-tools>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.447s]
Finished. Total time: 0.646s
D:\Downloads\Moto G4\platform-tools>fastboot reboot
Rebooting OKAY [ 0.005s]
Finished. Total time: 0.009s
Click to expand...
Click to collapse
Now, it says ID: bad key instead of ID: N/A, and there's the android mascot with its belly open saying: No command.
So yeah, didn't work.. I guess I'll look into the blankflash process but I have never done that before
EDIT: weird af thing just happened, I started the blankflash.bat from the guide while I was in fastboot but it was kinda stuck in "waiting for device" so i decided to close and reboot, and now it seems to be loading with the moto and lenovo logos... Now it seems to be working properly lol, this feels weird
Zedlav said:
Now, it says ID: bad key instead of ID: N/A, and there's the android mascot with its belly open saying: No command.
So yeah, didn't work.. I guess I'll look into the blankflash process but I have never done that before
EDIT: weird af thing just happened, I started the blankflash.bat from the guide while I was in fastboot but it was kinda stuck in "waiting for device" so i decided to close and reboot, and now it seems to be loading with the moto and lenovo logos... Now it seems to be working properly lol, this feels weird
Click to expand...
Click to collapse
After a clean install like this the first boot-up can take abnormally long. You probably just needed to wait it out. So is the phone starting and running now?
TWRP's output appears scary at first but looks like it flashed normally. All those "not found" messages during the ROM flash were followed by a bunch of "OKAY" messages. And I see that you flashed recovery.img which overwrote TWRP, so you must have seen the Android mascot in bootloader mode at some point during a reboot. All good!
If the phone is booting normally with stock recovery installed, you're ready to re-lock the bootloader if that's what you want. When the bootloader is locked the N/A and/or bad key notice will disappear along with Moto's unlocked bootloader screen. (I had it wrong in my other post; "bad key" is displayed when booting custom ROMs and custom recovery, where "N/A" is a normal part of the unlocked bootloader screen.)
Btw, blankflash is for devices that are hard bricked but you weren't even soft bricked (except for the brief time immediately after format). It's a last resort when phones play dead or partitions are scrambled. I'm glad to hear you stopped it before it did anything.
It seems to be working fine now, but there's an issue right now that I don't understand.
It only boots into the system if I go into the bootloader and restart from there. I had powered it off to save battery and powered it on right now, it goes straight to the android mascot thing with the belly open along with "No command" text. At that point I go to bootloader, click on "Start", then it boots up with the moto and lenovo logos and sounds.
From what I gather i'd say it isn't getting the command to boot up android when powering on, but no idea how to change that. I need to fix this because I know my mom will not be able to reproduce these steps in the case the phone powers off for whatever reason... Any ideas?
And also, thanks a lot for all of your help!!
Zedlav said:
It seems to be working fine now, but there's an issue right now that I don't understand.
It only boots into the system if I go into the bootloader and restart from there. I had powered it off to save battery and powered it on right now, it goes straight to the android mascot thing with the belly open along with "No command" text. At that point I go to bootloader, click on "Start", then it boots up with the moto and lenovo logos and sounds.
From what I gather i'd say it isn't getting the command to boot up android when powering on, but no idea how to change that. I need to fix this because I know my mom will not be able to reproduce these steps in the case the phone powers off for whatever reason... Any ideas?
And also, thanks a lot for all of your help!!
Click to expand...
Click to collapse
Here in the forums there should be a lot of discussion about all kinds of devices with this same problem. Solutions vary depending on what caused it.
First try a couple of cold restarts. Power off and let the phone sit a few minutes before each start up. If the system still isn't booting try clearing Dalvik cache, power off and start back up. If you're still booting straight into the bootloader try flashing the ROM all over again. You don't need TWRP recovery for this, just flash while the phone is in bootloader mode.
By chance did you flash the 7.0 Nougat ROM? If so try 8.1.0 Oreo. There are bootloop issues with Moto phones that have been downgraded.
I've been using the 8.1.0 Oreo rom. Before all of this happened it used to have a 7.0.1 rom (which I noticed it was the X Play's rom after all this time lol) and never got updated.
I flashed TWRP to wipe Dalvik, did that and rebooted, it didn't help, and after that I couldn't reach TWRP recovery through bootloader. So then I re-flashed the rom (this time changing the recovery line to flash twrp instead of stock), but nothing changed, I still can't boot the phone without going through the bootloader, not even through TWRP's Reboot > system.
Sorry I took a while to answer back, its been a busy couple of days
Zedlav said:
I've been using the 8.1.0 Oreo rom. Before all of this happened it used to have a 7.0.1 rom (which I noticed it was the X Play's rom after all this time lol) and never got updated.
Click to expand...
Click to collapse
Sorry, but right now I'm stumped on what to try next. You don't want to duplicate this post but you might consider starting a new post on the topic of flashing the wrong firmware. I still wonder how that may have affected your partitions.
If the fight is still on, maybe this post is pertinent to your problem installing stock Android to your G4 Plus.
https://forum.xda-developers.com/showpost.php?p=80118362&postcount=1442
Fingers crossed.

Moto g6 plus does not allow to install any rom

Hi, my problem is the following, and it is that my moto g6 plus does not allow me to install any rom, I tried from fastboot and I always get this:
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot flash partition gpt.bin
(bootloader) slot-countad-size: not found
(bootloader) slot-su: not found
(bootloader) slot-suffixessize: not found
(bootloader) partition-: not found
(bootloader) max-download-sizertition: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot flash bootloader bootloader.img
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot flash modem NON-HLOS.bin
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffi: not found
(bootloader) max-download-sizede: not found
target didn't report max-download-size
sending 'modem' (77976 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot flash fsg fsg.mbn
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'fsg' (7424 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot erase modemst1
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffi: not found
(bootloader) partition-ty: not found
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1on-ty
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot erase modemst2
(bootloader) slot-countty: not found
(bootloader) slot-suffi: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2on-typ
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Fran\Downloads\XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml>fastboot flash bluetooth BTFM.bin
(bootloader) slot-counttyp: not found
(bootloader) slot-su: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
target reported max download size of 536870912 bytes
sending 'bluetooth' (400 KB)...
FAILED (status read failed (Too many links))
finished. total time: 293.466s
I have twrp and I also tried installing the rom from there, I have the rom in the sd memory but I get a corrupt file, I don't know what to do anymore, I await your answers, thank you very much!
Are you running from a 3.0 usb port? try another usb port, or even another computer. Mine has issues on one pc but no issue in another. Also change cables if you have cause it could be bad cable connection.
Did you use command "fastboot getvar max-sparse-size" before flashing?
Also, wipe with TWRP all the partitions like system vendor oem data dalvik cache internal storage. Don't forget a backup.

Categories

Resources