Fastboot Drivers - X Style (Pure) Q&A, Help & Troubleshooting

Fastboot Drivers - X Style (Pure) Q&A, Help & Troubleshooting

Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.

A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/

jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk

Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.

https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.

Related

Motorol Moto G 2nd edition XT1608 UK - STUCK ON BLACK BACKLIT SCREEN

Hi all.
Had a moto g for a while and had no problems at all, until yesterday: WhatsApp crashed and said do I want to restore the history - I chose yes, and then it looked as if the app crashed, a black screen appeared
Turn the phone on/off and after the boot process has finished (android/motorola logo) the phone is once again stuck on the black screen -
Tried clearing the cache from the recovery mode , I've tried using fastboot and flashing the ROM back to 4.4.4 - but had absolutely no success
It was suggested to install ClockWordMod recovery or TWM, and I did this using fastboot, fastboot says it's complete and ok, but then everytime I go to recovery mode I have the lying down android saying no command, and the only place I can get too from there is the normal android recovery screen , I've tried reseting the factory defaults, clearing cache , but I can'#t get anything to work
Any help/advice is really appreciated - does anyone know why I cant boot into clockwork recovery after having flashed it successfully according to fastboot?
Thanks
Mark

You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.

ArtRahul said:
You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.
Click to expand...
Click to collapse
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!

You don't need the files for UK. Files for any other country will also work. Here's a tool how to restore to 4.4.4, and there are the images for UK too, I just checked, the link is working. http://forum.xda-developers.com/showthread.php?t=2983295

mapito said:
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!
Click to expand...
Click to collapse
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.

ArtRahul said:
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.
Click to expand...
Click to collapse
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader

mapito said:
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader
Click to expand...
Click to collapse
any chance you could put that stock firmware somewhere else? EVERY time i try and dl off google drive it NEVER ever finishes gets near and then says download interrupted
I did try 4.4.4.
and i got the following;
MOTO G 2nd GEN Kitkat 4.4.4 FIRMWARE Flasher
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.360s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.045s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.130s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.370s]
writing 'boot'...
OKAY [ 0.235s]
finished. total time: 0.610s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.380s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 0.585s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257527 KB)...
OKAY [ 8.376s]
writing 'system'...
OKAY [ 4.691s]
finished. total time: 13.072s
target max-sparse-size: 256MB
sending 'system' (260629 KB)...
OKAY [ 8.502s]
writing 'system'...
OKAY [ 4.423s]
finished. total time: 12.931s
target max-sparse-size: 256MB
sending 'system' (255304 KB)...
OKAY [ 8.312s]
writing 'system'...
OKAY [ 4.786s]
finished. total time: 13.109s
target max-sparse-size: 256MB
sending 'system' (76792 KB)...
OKAY [ 2.531s]
writing 'system'...
OKAY [ 1.273s]
finished. total time: 3.804s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49252 KB)...
OKAY [ 1.641s]
writing 'modem'...
OKAY [ 0.827s]
finished. total time: 2.478s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.015s
target max-sparse-size: 256MB
sending 'fsg' (650 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.075s]
finished. total time: 0.170s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
DONE!.........PRESS ANY KEY TO REBOOT
which is because the firmware isnt suitable for the device?
also bootloader is 48.82 - thats ok? dont need to update it , right?

I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit

mapito said:
I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit
Click to expand...
Click to collapse
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.

ArtRahul said:
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.
Click to expand...
Click to collapse
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2

mapito said:
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2
Click to expand...
Click to collapse
If last time, on your phone, you used Lollipop, then it's 5.0.2 and if KitKat then it's 4.4.4, simple.
And you'll need mfastboot2

turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement

http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587/page4

mapito said:
turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement
Click to expand...
Click to collapse
what errors are you getting now...
are these (failed to validate system image/ fall-through from normal boot)??
If these are the errors you will have to re-flash the commands given above(as I told you in previous post).
I had same problem twice yet, and fixed by this process, so I can make you sure that you too should try again, and report the news here. I am here to help you.

Try using fastboot to boot philz cwm temporarily.
Fastboot boot Phil'srecovery.IMG
(or whatever its named)
Then use philz to format your partitions. Assuming twrp is installed already, Reboot to enter twrp. then use twrp to format partitions. Install ROM.
Sent from my Moto G 2014 using XDA Free mobile app

no TWR installed can i still use this recovery img or wont it work?

mapito said:
no TWR installed can i still use this recovery img or wont it work?
Click to expand...
Click to collapse
Install twrp recovery.
Sent from my Moto G 2014 using XDA Free mobile app

I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only

mapito said:
I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only
Click to expand...
Click to collapse
Did you try booting into philz with the command I gave you yet? Doesn't install, just boots the recovery image.
Sent from my Moto G 2014 using XDA Free mobile app

hey thanks for replyingI hadn't yet
I'll try that in a minute just grabbing the Philz recovery image
hope this works
thanks!

Stuck at FASTBOOT Zenfone Selfie/Zenfone Laser (Z00U/Z00T)

Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s

https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom

Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed:

Moto G4 XT1622 Bricked......

Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
C:\adb>fastboot oem fb_mode_set
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.172s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.319s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.172s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.687s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.891s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.664s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.883s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257278 KB)...
OKAY [ 9.982s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.097s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 10.125s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.157s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (258384 KB)...
OKAY [ 10.076s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.107s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (252313 KB)...
OKAY [ 9.973s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.004s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (254404 KB)...
OKAY [ 10.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.064s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (258060 KB)...
OKAY [ 10.114s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.161s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76857 KB)...
OKAY [ 3.038s]
writing 'modem'...
OKAY [ 2.036s]
finished. total time: 5.075s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1864 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.210s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse

what have you done to your phone at the first place when it was working? did you unlock bootloader? were you flashing some customised roms? have your try to root? ... or something else?

Hi,
Nothing like rooting flashing roms etc. I think an update installed and booted to the Start Up Failed error.
Thanks,
Phatzy

Device didn't start successfully. Bootloader issue?

So my moto G5 plus has had a problem. I was on stock oreo and it just crashed one day prompting "Your device didn't start up successfully". So I repaired it using the Lenovo software repair assistant and it worked quite perfectly. Now that I had a reset I thought of trying Pixel Experience [AOSP & CAF] ROM and flashed it.
It crashed again and now Lenovo software repair assistant is not able to repair it. Any particular reason? I had USB debugging on and OEM set to unlock when this ROM was working fine. I downloaded the stock ROM repair assistant suggested and tried fastboot way but it also didn't work. There was always remote failure.
Also, adb isn't detecting my device. fastboot is detecting though. here are some details:
Code:
C:\adb>adb devices
List of devices attached
*blank*
C:\adb>fastboot devices
ZY223XXJ9S fastboot
Code:
C:\adb\ROM>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
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.077s
C:\adb\ROM>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.117s]
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.326s
C:\adb\ROM>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.051s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.064s
C:\adb\ROM>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.380s]
writing 'boot'...
(bootloader) Image signed with key bad key
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.486s
C:\adb\ROM>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.462s]
writing 'recovery'...
(bootloader) Image signed with key bad key
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.615s
C:\adb\ROM>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.356s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.369s
C:\adb\ROM>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.268s]
writing 'oem'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 2.279s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256557 KB)...
OKAY [ 5.592s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.621s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256617 KB)...
OKAY [ 5.602s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.726s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (254213 KB)...
OKAY [ 5.576s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.636s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (256710 KB)...
OKAY [ 5.672s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.735s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (256912 KB)...
OKAY [ 5.649s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.811s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (257861 KB)...
OKAY [ 5.629s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.764s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (260027 KB)...
OKAY [ 5.705s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.869s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (257557 KB)...
OKAY [ 5.623s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.793s
C:\adb\ROM>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (257826 KB)...
OKAY [ 5.628s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 5.680s
C:\adb\ROM>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.580s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.592s
C:\adb\ROM>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.009s
C:\adb\ROM>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.008s
C:\adb\ROM>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.070s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.083s
C:\adb\ROM>fastboot erase cache
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.068s
C:\adb\ROM>fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.009s
C:\adb\ROM>fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.007s
C:\adb\ROM>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\adb\ROM>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.116s
C:\adb\ROM>fastboot reboot
rebooting...
finished. total time: 0.003s
My device is connected to pc as "fastboot potter S"
I also trying getting the unlock key through fastboot. While I got the key, I was not able to unlock it (remote failure). Is there a solution? Any other details required from my side?
Fair warning: I'm so not a pro at this (clearly). I already ordered a new phone but the feel that I'm not able to get a solution from hours and hours of browsing xda is just disheartening. I refuse to give up on this one. Too many good memories associated with it

Well if you were on pixel experience then your bootloader is already unlocked so no need to do that. The fb log shows security version downgrade which happens when you try to flash an older firmware. Try the getvar command and it should show some more details and then just download the correct firmware. Does your twrp work?

Exactly. Grab the latest firmware 8.1.0_OPS28.85-17-6-2 (February security patch) and flash it. There's no newer stock firmware so a downgrade isn't possible
Sent from my Moto G5 Plus using XDA Labs

debdeep98 said:
Well if you were on pixel experience then your bootloader is already unlocked so no need to do that. The fb log shows security version downgrade which happens when you try to flash an older firmware. Try the getvar command and it should show some more details and then just download the correct firmware. Does your twrp work?
Click to expand...
Click to collapse
I can't get pass the boot screen. It just says device didn't start successfully. I'll try the getvar and will post again. I can't even reboot the phone or the bootlocker using fastboot.

Unlocked bootloader Phone stuck in bootloop

I successfully unlocked my bootloader last night. I went through the process of patching the img file through magisk to root and flashed it via fastbooot. I have been stuck in a loop since. I can still get into fastboot. I have tried Smart Assistant and RSD but they wont detect my phone.
I tried a using different firmware as others have posted and i'm still stuck.
here is my process on powershell:
PS C:\Android> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
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...
OKAY [ 0.092s]
finished. total time: 0.095s
PS C:\Android> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.179s]
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_30.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64_30.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster64.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.317s]
finished. total time: 0.497s
PS C:\Android> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Android> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (65900 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 0.512s]
finished. total time: 2.040s
PS C:\Android> fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (11612 KB)...
OKAY [ 0.270s]
writing 'fsg'...
OKAY [ 0.089s]
finished. total time: 0.361s
PS C:\Android> fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android> fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.016s
PS C:\Android> fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin'
PS C:\Android> fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
PS C:\Android> fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
PS C:\Android> fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.380s]
writing 'dsp'...
OKAY [ 0.104s]
finished. total time: 0.486s
PS C:\Android> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2633 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.107s
PS C:\Android> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.789s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.641s]
finished. total time: 1.431s
PS C:\Android> fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (256852 KB)...
OKAY [ 5.933s]
writing 'system'...
OKAY [ 1.093s]
finished. total time: 7.028s
PS C:\Android> fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 6.062s]
writing 'system'...
OKAY [ 1.102s]
finished. total time: 7.166s
PS C:\Android> fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (234600 KB)...
OKAY [ 5.424s]
writing 'system'...
OKAY [ 0.955s]
finished. total time: 6.379s
PS C:\Android> fastboot flash system system.img_sparsechunk.3 target reported max download size of 536870912 bytes
sending 'system' (259529 KB)...
OKAY [ 5.998s]
writing 'system'...
OKAY [ 1.075s]
finished. total time: 7.075s
PS C:\Android> fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 6.061s]
writing 'system'...
OKAY [ 1.114s]
finished. total time: 7.177s
PS C:\Android> fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (252895 KB)...
OKAY [ 5.852s]
writing 'system'...
OKAY [ 1.144s]
finished. total time: 6.997s
PS C:\Android> fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 6.070s]
writing 'system'...
OKAY [ 1.092s]
finished. total time: 7.163s
PS C:\Android> fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system' (260863 KB)...
OKAY [ 6.071s]
writing 'system'...
OKAY [ 1.883s]
finished. total time: 7.955s
PS C:\Android> fastboot flash system_b system_other.img
error: cannot load 'system_other.img'
PS C:\Android> fastboot flash oem oem_other.img
target reported max download size of 536870912 bytes
sending 'oem' (43696 KB)...
OKAY [ 1.012s]
writing 'oem'...
OKAY [ 0.219s]
finished. total time: 1.233s
PS C:\Android> fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (68308 KB)...
OKAY [ 1.584s]
writing 'oem'...
OKAY [ 0.300s]
finished. total time: 1.887s
PS C:\Android> fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.032s]
finished. total time: 0.033s
PS C:\Android> fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.082s]
finished. total time: 0.083s
PS C:\Android> fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
PS C:\Android> fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
PS C:\Android> fastboot reboot
rebooting...
finished. total time: 0.001s

You need to wipe everything with fastboot commands. Then flash stock again. Also there's no need to do any of that anymore to get root. Just flash the latest magisk in TWRP next time.

Phalanx7621 said:
You need to wipe everything with fastboot commands. Then flash stock again. Also there's no need to do any of that anymore to get root. Just flash the latest magisk in TWRP next time.
Click to expand...
Click to collapse
Thank you for the reply
Should "Fastboot erase" wipe it all out?
do you know where I can the correct stock room for XT1962-1?
Sent from my SM-N975U using Tapatalk

Extract all files from stock zip and run flashall.bat file at command prompt with phone connected in bootloader mode. This will flash and erase all to correct retail stock at Lolinet mirror
https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/

Flashall.bat file
Extract into adb folder (same as all files in stock zip file)

HueyT said:
Extract into adb folder (same as all files in stock zip file)
Click to expand...
Click to collapse
Thank you for your help!! I'll let you know how it goes
Sent from my SM-N975U using Tapatalk

HueyT said:
Extract into adb folder (same as all files in stock zip file)
Click to expand...
Click to collapse
Update: I'm back up and running! I really appreciate the help! my bootloader is still unlocked, what is the best way to root this device?

dnsource said:
Update: I'm back up and running! I really appreciate the help! my bootloader is still unlocked, what is the best way to root this device?
Click to expand...
Click to collapse
Install TWRP and then flash Magisk 20.2 and Magisk Manager APK

While patching the boot.img for your first installation, did you choose "Preserve force encryption" in "Advanced Settings"?

Database Users

welcome