Database Info

Soft Brick with Locked Booloader in Moto g3 XT1550 (Dual-SIM)

Deal all Great and Senior Devs specially @lost101 need yours extrem help
i was on rr rom 5.1 and later after that i have flash Stock Factory Firmware Image of same model via Fastboot
i was successfully booted and also received the MM update so i had downloaded it and install it after final step to reboot i was stuck on unlock boot loader warring image so after seeing many threads i have flashed Stock MM Factory Firmware Image of same model via Fastboot as i wanted to sell this phone so i have tried to relock the boot loader so i have tried
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
all the commands was showing okay while flashing
also boot loader got locked on final fastboot reboot i stuck on boot loop :crying:
and now I can only get into Fastboot mode .but I can't flash anything because the bootloader is locked. and I can't unlock the bootloader because I can't toggle the stupid "Allow OEM Unlock" setting.
please don't tell to visit service center its boot loop image showing unlock boot loader warning
pls help all great devs if their is any solution
thanks in advace

Stop with all locking. You cannot undo Bootloader unlock, period. Do not use any lock commands. Begin again, this time with: fastboot oem unlock
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.

thanks @lost101 for the reply sir
but as in locked boot loader status code 2
all comments were flashing successfully but in the end on final reboot its stuck on boot loader warning logo again screen goes off again boot loader warning logo comes this process repeats
also i am not able to boot into stock recovery which agains open boot loader
following are the commands
C:\Users\Bhupesh\Desktop\Moto>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.733s]
finished. total time: 0.749s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.624s]
finished. total time: 1.718s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.562s]
writing 'boot'...
OKAY [ 0.938s]
finished. total time: 1.500s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.515s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.713s]
writing 'system'...
OKAY [ 11.861s]
finished. total time: 20.574s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (245933 KB)...
OKAY [ 8.190s]
writing 'system'...
OKAY [ 7.958s]
finished. total time: 16.164s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (249279 KB)...
OKAY [ 8.300s]
writing 'system'...
OKAY [ 7.769s]
finished. total time: 16.069s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.726s]
writing 'system'...
OKAY [ 9.734s]
finished. total time: 18.461s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (63875 KB)...
OKAY [ 2.150s]
writing 'system'...
OKAY [ 11.283s]
finished. total time: 13.436s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.237s]
writing 'modem'...
OKAY [ 1.056s]
finished. total time: 2.298s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.973s]
finished. total time: 3.976s
C:\Users\Bhupesh\Desktop\Moto>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\Users\Bhupesh\Desktop\Moto>
also while
C:\Users\Bhupesh\Desktop\Moto>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.017s
thanks in advance

This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.

lost101 said:
This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.
Click to expand...
Click to collapse
thanks @lost101 for the reply again
its seems I am getting the failure message
"version downgrade for system"
"Invalid PIV signed system image "
C:\Users\Bhupesh\Desktop\Moto>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.156s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.281s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.702s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.357s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.718s]
writing 'recovery'...
OKAY [ 1.030s]
finished. total time: 1.763s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (232264 KB)...
OKAY [ 7.769s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.424s
C:\Users\Bhupesh\Desktop\Moto>
also while using MM Factory Firmware Images before which was getting successfully flashed i was still not able to boot on stcok recovery with boot loop
i have done almost googleing abt this issue
and i bet u are the only who can make my device normal
thanks in advance

Try using RSD lite as described here by @thinkfreedom:
http://forum.xda-developers.com/showpost.php?p=64844324&postcount=275​

Not i my case waited for 20-30 minute
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101

I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?

tmmcbots said:
I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?
Click to expand...
Click to collapse
yes i can via RSD Lite 6.2.4 try https://getmovil.com/motorola/moto-g-2015-android-5-1-1-lollipop/
hope u get booted

bhu999 said:
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101
Click to expand...
Click to collapse
Try flashing TWRP and than any custom rom i think CM13 will be better....U have tried so much so at least u can have shoot on this step...
Sent from my Toilet using Moto G3....

cant flash twrp with locked boot loader
its says Invalid partion size

bhu999 said:
cant flash twrp with locked boot loader
its says Invalid partion size
Click to expand...
Click to collapse
If you are in warranty just go to service center.. They will flash firmware.. Don't tell them you have previously unlocked boatloader.. They are just mad.. They even won't ask for money if you are in warranty period.. These guys are not aware of bootloader is previously unlocked or not.. That's the last option..
Sent from my Moto G(Osprey)

[CLOSED] Can't flash TWRP after RUU

Hello,
I have installed latest RUU. I want to flash TWRP, but it doesn't work because i have S-ON.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (44328 KB)...
OKAY [ 7.337s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 7.346s
It is unlocked. I also tried to unlock it again, but s-on stand still their.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.003s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) Device is unlocked
OKAY [ 0.012s]
finished. total time: 1.016s
S-Off for custom recovery, but i can't gain root access to use sunshine.
Furthermore i don't know how. Some advise or useful links would be nice thanks.
EDIT: Was problem myself, had to go to download mode, not bootloader, worked fine

XT1033 "Soft" Brick - Stuck on "unlocked bootloader"

A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:

Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps

matmutant said:
Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps
Click to expand...
Click to collapse
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.

lhtrevisan said:
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.
Click to expand...
Click to collapse
This make me think you would need to flash a 5.1 gpt.bin (that you can find in an official zip for your XT1033 device), and then retry to update the bootloader
Though I should work, "sh*t happens" sometime (I am currently failing to update a Peregrine from JB to CM13 xD

Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.

lhtrevisan said:
Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.
Click to expand...
Click to collapse
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"

matmutant said:
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"
Click to expand...
Click to collapse
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar version-bootloader"
version-bootloader: 411A
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T099706POH
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: 50AA5E040F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 9 4: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:5.1/LPBS23.13-56-2/2:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.201.2.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Feb 26 07:13:58 CST 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.060s

When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173

matmutant said:
When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173
Click to expand...
Click to collapse
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.

lhtrevisan said:
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.
Click to expand...
Click to collapse
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there

matmutant said:
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there
Click to expand...
Click to collapse
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/

lhtrevisan said:
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/
Click to expand...
Click to collapse
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash

matmutant said:
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash
Click to expand...
Click to collapse
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?

[Failed]
lhtrevisan said:
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?
Click to expand...
Click to collapse
You're welcome!
I am really sorry I couldn't help you more,
Maybe your friend can try the last option him/herself ?
I don't think you can close the thread yourself, but let's keep it open if someone ever wants to add something one day

How to revert back to normal from gpe
Sent from my Redmi 3S using XDA-Developers mobile app

lhtrevisan said:
A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:
Click to expand...
Click to collapse
May be, check your android version matches TWRP recovery version

[GUIDE][ROM][STOCK] XT1766 Stock Firmware & Restoration Guide

Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749

this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.

iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:

MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411

iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.

Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.

iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.

Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.

MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.

Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help

Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?

error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.

UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.

[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone

MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).

MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike

resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.

madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968

resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.

madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>

Stuck in fastboot

Hi all,
I need help with my phone being stuck in fastboot...
Today i tried to flash Lineage OS using this guide. I did this from scratch with a stock phone, not rooted or unlocked or anything.
Everything went fine until Step 4 under ROM Installation. My phone refused to start into TWRP. It didn't even start the lineage rom, it always just warned me about my phone being a risk because it is unlocked and then proceeded to start the stock Rom. So i tried the whole thing over and over again a couple of times, always with the same result. Then i read someone writing about how he first had to use wipe > format data before flashing the Rom in TWRP in the Guide Thread (Page 3). So i tried that too. But i must have done something wrong because it now led to my phone restarting into a fastboot mode, which didn't look like the fastboot screen it booted into before e.g. different font style, black background without the little android thingy on the top, and it now says "oem_locked" again.
When i try to boot the system it says:
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
I tried to unlock the phone again using "fastboot oem unlock MYKEY" on my computer it says:
(bootloader) feature disabled
OKAY [ 0.003s]
finished. total time: 0.004s
So i tried to flash back to the stock image as described here.
But i get a "remote failure" error after every command.
Here is the output from Powershell:
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
PS D:\Minimal ADB and Fastboot> ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.055s
PS D:\Minimal ADB and Fastboot> ./fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.249s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.437s
PS D:\Minimal ADB and Fastboot> ./fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (65396 KB)...
OKAY [ 2.147s]
writing 'modem_a'...
(bootloader) Invalid partition name modem_a
FAILED (remote failure)
finished. total time: 2.158s
PS D:\Minimal ADB and Fastboot> ./fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (11684 KB)...
OKAY [ 0.379s]
writing 'fsg_a'...
(bootloader) Invalid partition name fsg_a
FAILED (remote failure)
finished. total time: 0.392s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.027s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp_a'...
(bootloader) Invalid partition name dsp_a
FAILED (remote failure)
finished. total time: 0.538s
PS D:\Minimal ADB and Fastboot> ./fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (1285 KB)...
OKAY [ 0.046s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.057s
PS D:\Minimal ADB and Fastboot> ./fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (32768 KB)...
OKAY [ 1.085s]
writing 'boot_a'...
(bootloader) Invalid partition name boot_a
FAILED (remote failure)
finished. total time: 1.093s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dtbo_a dtbo.img
target reported max download size of 536870912 bytes
sending 'dtbo_a' (1760 KB)...
OKAY [ 0.058s]
writing 'dtbo_a'...
(bootloader) Invalid partition name dtbo_a
FAILED (remote failure)
finished. total time: 0.066s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (258873 KB)...
OKAY [ 8.397s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.409s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (249260 KB)...
OKAY [ 8.139s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.153s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (262081 KB)...
OKAY [ 8.677s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.693s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (262141 KB)...
OKAY [ 8.533s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.540s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (257008 KB)...
OKAY [ 8.366s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.374s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (242308 KB)...
OKAY [ 7.906s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 7.912s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (262060 KB)...
OKAY [ 8.585s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.596s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (255940 KB)...
OKAY [ 8.420s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.436s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.8
target reported max download size of 536870912 bytes
sending 'system_a' (261918 KB)...
OKAY [ 8.584s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.594s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.9
target reported max download size of 536870912 bytes
sending 'system_a' (83808 KB)...
OKAY [ 2.728s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 2.738s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (262140 KB)...
OKAY [ 8.349s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.357s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (262024 KB)...
OKAY [ 8.368s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.376s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (43968 KB)...
OKAY [ 1.414s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 1.423s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'vendor_a' (259120 KB)...
OKAY [ 8.524s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 8.531s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'vendor_a' (147628 KB)...
OKAY [ 4.843s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 4.850s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (103040 KB)...
OKAY [ 3.370s]
writing 'oem_a'...
(bootloader) Invalid partition name oem_a
FAILED (remote failure)
finished. total time: 3.377s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_b oem_other.img
target reported max download size of 536870912 bytes
sending 'oem_b' (185456 KB)...
OKAY [ 6.032s]
writing 'oem_b'...
(bootloader) Invalid partition name oem_b
FAILED (remote failure)
finished. total time: 6.044s
PS D:\Minimal ADB and Fastboot> ./fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
PS D:\Minimal ADB and Fastboot> ./fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_clear
...
OKAY [ 0.001s]
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot reboot
rebooting...
finished. total time: 0.001s
And now i'm pretty lost and don't really know how to proceed. It would be great if somebody hat some advice

This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.

kry52 said:
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Thats unfortunat
I tried the blankflash too, with the same outcome. Then i guess i'll do the same.... put in the box and wait for a solution, if there will ever be any :fingers-crossed:
Anyway... thank you for the reply

Tried switching slots?
To check active slot
Code:
fastboot getvar current-slot
To change to slot a
Code:
fastboot --set-active=a
To change to slot b
Code:
fastboot --set-active=b
To toggle from active to inactive Slot
Code:
fastboot set_active other
Sent from my mata using XDA Labs
---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------
kry52 said:
... I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Was phone in emergency download mode?
Sent from my mata using XDA Labs

In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE

@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?

bondu546 said:
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
Click to expand...
Click to collapse
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...

jodytejada said:
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
Click to expand...
Click to collapse
My PC shows "Android ADB Interface" when the phone is loaded in this emergency fastboot mode, but anyway - ADB commands don't work, fastboot commands bring failures because of the partitions issue and more than that - this emergency fastboot loader is oem_locked and can't be unlocked in a standard way

Will this 134-2 file work on a phone updated to 134-4 ??
Geofferey said:
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
Click to expand...
Click to collapse
This is a 134-2 blankflash file - will it work on 134-4 ??
Despite everyone else being able to flash to a different variant of the XT1955 firmware - apparently the Verizon XT1955-6 is OEM locked at the boot.img stage.
Currently there is no PDOS29.114-134-4 firmware to download at https://mirrors.lolinet.com/firmware.../official/VZW/ to repair it by a re-install of the firmware with - and one cannot install an earlier version . . . unless you know of a way . . .
Everything will re-flash but boot.img and dtbo.img
The Lenovo MOTO Smart Assistant comes back and says it is not supported . . . after recognizing it
Is there a way to re-set the OEM issues of the phone to take earlier versions of the OS - or other variants that you know of ??
Even factory reset is not available - I will look for a fastboot command that can do it - because that is all I can do - it boots right to fastboot now only

estofjlw said:
This is a 134-2 blankflash file - will it work on 134-4 ??
...
Click to expand...
Click to collapse
It should work for any XT1955-5
Sent from my ocean using XDA Labs

sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse

estofjlw said:
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
I believe the boot.img in the blank flash can be updated too.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse

What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???

jodytejada said:
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
Click to expand...
Click to collapse
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs

VZW update locks out any other firmware
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too. /QUOTE]
That would be great except if it updates to newer than the RETUS firmware boot.img - which will cause a pre-flash error instead of an oem boot.img error
I have not tried yet . . . but the RETUS 134-4 firmware is older than the VZW 134-4 firmware which has not been posted on the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ website.
No other ocean variant I looked at is newer either - some have the 11/04 modify date - but inside the folder it is not the 134-4 firmware that is for that date.
Verizon's 134-4 update came down between November 2 and 4 in three updates as 1, 2 and then straight to 4 - behind my back on wifi and since the bootloader is still oem locked - and because it is Verizon - not eligible for an unlock code from Motorola due the Verizon ordering it as an oem branded phone, unless I can make it look like a RETUS bootloader to Motorola in the middle of the flash while the bootloader can be unlocked so they provide an unlock code for it _ I am betting I am screwed until the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ site has a post for the 134-4 VZW firmware
Right now it boots to fastboot mode immediately - so I do not want to make it worse and actually brick it
I looked inside the blank flash zip and there is no boot.img - but from my understanding the blank flash contacts the boot img and updates it - to what and how I do not know - in my case it needs to "downgrade" it an earlier date - I sure I had Magisk so it could patch the boot.img and fix this. See https://www.reddit.com/r/MotoG/comments/cdsbw6/quick_reference_moto_g7_power_manually_flashing/
The trouble is of course there is no access to ADB copy, push and pull commands in fastboot
I have a XT1955-5 True Factory unlocked Retail US Phone on the way - and this one will have to be shelved
Click to expand...
Click to collapse
Click to expand...
Click to collapse

sd_shadow said:
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Any solution at this point? or onlly a brick to my collection?

sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too.
Click to expand...
Click to collapse
Well I have my answer . . . the Verizon XT1955-6 version restricts using blankflash and it will not go in EDL at all
C:\>fastboot oem blankflash
...
(bootloader) command restricted
FAILED (remote failure)
Since I can flash the RETUS bootloader can anyone suggest another work around to get past boot.img and DTBO.img
Click to expand...
Click to collapse

I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5

KeRbYRoK said:
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
Click to expand...
Click to collapse
Look for retus blank flash

Thanks man.
Ok what I did was hit it with blankflash. That still wouldn't clear out the faulty bootloader that was from the wrong firmware. But I found a new Android 10 firmware flashed it all checks were good and I'm sending this message from it right now.