com.android.phone has stopped - Nexus 6 Q&A, Help & Troubleshooting

After installing the latest security update for my Nexus 6, v7.1.1 I keep getting com.android.phone has stopped and android.process.acore has stopped. I'm not unfamiliar on how to reinstall factory image so I tried and I keep getting this
M:\Chrome Downloads\shamu-n6f27m-factory-bf5cce08 (2)\shamu-n6f27m>flash-all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
(bootloader) flashing 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...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.774s]
finished. total time: 0.909s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.082s
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.618s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.937s]
finished. total time: 5.558s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.081s
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
W/ziparchive(10484): Zip: unable to truncate file to 1619795140: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
Now I have installed SDK and Platform tools. I copy and pasted all the files form the platform tools into the Shamu folder. But no dice. Does anyone have a fix for the processes that keep stopping or know what Im doing wrong when I try to flash?

I have the same issue. I even went back to the previous patch and the phone was still not working properly. Home key didn't work and neither did the notification bar. I factory defaulted on the previous security patch and the phone was back in working order. From a fresh default I upgraded again to the latest patch and services started failing.

I see
davidmoore said:
I have the same issue. I even went back to the previous patch and the phone was still not working properly. Home key didn't work and neither did the notification bar. I factory defaulted on the previous security patch and the phone was back in working order. From a fresh default I upgraded again to the latest patch and services started failing.
Click to expand...
Click to collapse
Not good! I was finally able to factory reset the phone. I guess I will hold off on new updates.

Exact same problem. Haven't been able to get the phone do to anything so far. Battery is draining from 100 to 20 in about 2 hours despite the screen being dark.

use google dialer...

I finally factory reset from 7.1.1 to 7.0. Phone works now. I'm not going back to 7.1.1 unless I can figure out what's going on. The new update to 7.1.1 didn't agree with some app. My suspicion is that it might be "Should I answer." It all worked fine until the security update installed however.

Okay so I have the same issue. But I can't even boot into my custom recovery because it seems like the security patch wiped it? Can anyone help?

Connect to fastboot and reinstall TWRP? If you want recovery, it is what you must do.
You could also use ADB to sideload back to a working factory release.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Related

am i bricked?

was running stock android with unlocked bootloader. wanted to install cm. used wugfresh nrt and rooted and installed twrp. then used twrp to flash cm and open gapps. everything did just fine. was running cm.
then found out i was not rooted?. then followed this video https://www.youtube.com/watch?v=84D2-UnUIA4&t=38s to root.
ended up bricking? i can get to the start screen by entering bootloader mode but whenever i choose any option ....
start, restart bootloader, recovery mode, factory, etc.. nothing happens
i am able to use platform tools and run the command fastboot devices and it is listed.
i am getting failures when trying to run flash-all.bat and flash recovery
This is what i get when i try the flash-all.bat
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
(bootloader) flashing 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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.456s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.733s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.788s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.009s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-72.00
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: REDACTED
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-72.00'.
Update requires 'moto-apq8084-72.01'.
finished. total time: 0.020s
Press any key to exit...
This is what i get when i try to run fastboot flash recovery twrp.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>
it says on the bottom of the screen..........
AP Fastboot flash mode secure
BI info
Baseband info
Product/Variant info
Serial Number info
CPU info
eMMC info
DRAM info
Console [Null]
Battery OK charging
Device is UNLOCKED Status Code 3
Transfer Mode: USB Connected
Am i screwed? Seems like i should be able to flash twrp to have a recovery and then flash another rom.
TIA,
johnboyinfl
If you're unlocked you can't be bricked.... Just flash the latest factory image and start all over..
I never use the flash all script, i flash all files individually. You can also use Nexus Root Toolkit to flash the image.
[email protected] said:
was running stock android with unlocked bootloader. wanted to install cm. used wugfresh nrt and rooted and installed twrp. then used twrp to flash cm and open gapps. everything did just fine. was running cm.
then found out i was not rooted?. then followed this video https://www.youtube.com/watch?v=84D2-UnUIA4&t=38s to root.
ended up bricking? i can get to the start screen by entering bootloader mode but whenever i choose any option ....
start, restart bootloader, recovery mode, factory, etc.. nothing happens
i am able to use platform tools and run the command fastboot devices and it is listed.
i am getting failures when trying to run flash-all.bat and flash recovery
This is what i get when i try the flash-all.bat
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
(bootloader) flashing 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) Failed to write primary GPT.
... TRUNCATED.
Click to expand...
Click to collapse
This is the point where it went south.
Am i screwed? Seems like i should be able to flash twrp to have a recovery and then flash another rom.
Click to expand...
Click to collapse
I think you're screwed. It messed up your partition table (that's what GPT is), AND in doing so probably destroyed the data that it had to "backup and restore".
There is a possibility that if you try a few more times to flash the bootloader (just the bootloader, DO NOT use flash-all.bat), and are able to get it successfully written, then you may be able to follow that with the rest of the partitions, but I wouldn't count on it.
Also, try this from a LINUX box. Windows is a bloated mess and introduces a lot of unknown variables. More bloat and more variables = less certainty of a successful outcome. In fact, I would NEVER suggest trying fastboot from windows, since you stand a much higher chance of sending corrupt data across the line. Unlike update.zip's, fastboot does NOT validate the data integrity.
---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------
blanco2701 said:
If you're unlocked you can't be bricked.... Just flash the latest factory image and start all over..
Click to expand...
Click to collapse
OF COURSE you can brick an unlocked device!
All you have to do is delete part of the bootloader, and then you can no longer boot to fastboot.
I never use the flash all script, i flash all files individually. You can also use Nexus Root Toolkit to flash the image.
Click to expand...
Click to collapse
NEVER use anything that is called a "root toolkit".
There is nothing special about root, it is as easy to add root as running "fastboot flash boot boot.img"
i have tried multiple times to just flash the bootloader and still no luck. i would say i am screwed. just went out and bought something cheap because i am getting ready to head away for the holidays. not sure what i might get myself after the holiday.
thanks for the help.
johnboyinfl
might have made some progress.... not sure... this is where i am at after multiple attempts flashing just the bootloader...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) flashing 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...
(bootloader) Failed to write EFI backup GPT entries.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.462s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
----------------------------------------------------------
TIA
johnboyinfl
[email protected] said:
might have made some progress.... not sure... this is where i am at after multiple attempts flashing just the bootloader...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) flashing 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...
(bootloader) Failed to write EFI backup GPT entries.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.462s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
----------------------------------------------------------
TIA
johnboyinfl
Click to expand...
Click to collapse
If you are flashing all of the factory images (.img) files manually, what happens if you try the following commands? This will wipe your device completely. NOTE: Each line below is just one command.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
update...
i think i am still out of luck.... failed to write primary GPT....
Doesn't look good.
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) flashing 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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.451s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.634s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 14.629s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Creating filesystem with parameters:
Size: 59777200128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14594043
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14594043 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
TIA
johnboyinfl
RMarkwald said:
If you are flashing all of the factory images (.img) files manually, what happens if you try the following commands? This will wipe your device completely. NOTE: Each line below is just one command.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Program Files (x86)\Android\android-sdk\platform-tools\
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
ZX1G325LRV fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase boot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.006s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.006s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.004s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
error: cannot load 'bootloader-shamu-moto-apq8084-72.01'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.42+fsg-9625-02.113
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
error: cannot load 'radio-shamu-d4.01-9625-05.42+fsg-9625-02.113'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
error: cannot load 'boot.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
error: cannot load 'cache.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I've not done this with Windows and use linux but I've run into issues with fastboot if I don't run it as root. Try it again running fastboot as an administrator in Windows in case there are permission problems.
Also, show the output of fastboot getvar all.
Did you unlock the bootloader? fastboot oem unlock
How about booting directly into twrp?
fastboot boot recovery twrp-3.0.3-0-shamu.img
If you can do this you might be able to use a flashable image or perhaps for erase some partitions.
You in trouble son...
There is a restore brick thread... Where it talks about blankflashing...
Start there...
May the force be with you...
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop
Shogunes said:
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop
Click to expand...
Click to collapse
Wrong Forum check here.

Attempted Root, No Longer Can Boot :(

Hello,
I was following the instructions here ( https://forum.xda-developers.com/dr...t-unlock-droid-turbo-6-0-1-mcg24-251-t3639618 )
When I then went to install "MagiskManager" , upon rebooting, I found a "No Command" screen.
When I attempt to reboot it just sends me to the recovery screen. Anything I do there yields the same result of either "No Command" or recovery.
When I connect to my computer via USB it still recognizes as being connected , so I am sure I can bring my Turbo back to life.
Could someone point me in the direction of what I could do in this circumstance?
Thank you!
-Reiz
Update ( Not Good )
Reizvoller said:
Hello,
I was following the instructions here ( https://forum.xda-developers.com/dr...t-unlock-droid-turbo-6-0-1-mcg24-251-t3639618 )
When I then went to install "MagiskManager" , upon rebooting, I found a "No Command" screen.
When I attempt to reboot it just sends me to the recovery screen. Anything I do there yields the same result of either "No Command" or recovery.
When I connect to my computer via USB it still recognizes as being connected , so I am sure I can bring my Turbo back to life.
Could someone point me in the direction of what I could do in this circumstance?
Thank you!
-Reiz
Click to expand...
Click to collapse
Hello,
After some fiddling and attempting to figure out how to push a recovery to my phone I reinstalled ADB/Fastboot and now my phone no longer sees that it is connected to a computer.
It just says "Connect USB Data Cable" at the bottom even though it says the battery is charging (( still only getting to the recovery screen ))
I have firmware from ( http://rootjunkysdl.com/files/?dir=Droid Turbo/Firmware )
and I have the needed drivers installed.
How do I get the firmware onto the phone?
Thanks!
Did you try to root via. A custom recovery? If so what version of SuperSU, or magisk
Sent from my DROID Turbo using Tapatalk
Rshelver said:
Did you try to root via. A custom recovery? If so what version of SuperSU, or magisk
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
To be clear I followed the steps found here ( https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/ ) specifically the "Install Step By Step" section.
This includes the link to the Magisk version I was using and all the commands I used with the phone.
It was after I completed the "Step by Step" instructions that I then opened the Magisk app, then allowed it to install it's tools. From there it asked for a reboot, I obliged, and now I am faced with the scenario I am in.
If there is anywhere else I can be more clear or provide more information please let me know.
At this point I'd just like to boot to stock if that's what needs to happen
Okay, did you unlock the bootloader using sunshine?
And can you clarify the model number of your device.
Sent from my DROID Turbo using Tapatalk
Rshelver said:
Okay, did you unlock the bootloader using sunshine?
And can you clarify the model number of your device.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Howdy,
No, I did not use Sunshine as that was not described in the instructions
My exact device is "Droid Turbo XT1254" , it /was/ fully stock with latest OTA from ISP
I just ran through the Bootloader Logs again ( unsure if they are of any use ) but they say...
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
fastboot reason : fall-through from charger boot mode
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
boot up failed
I then scrolled to "Restart Bootloader" which brings me right back to the bootloader, but now the logs says:
Fastboot Reason : Reboot mode set to fastboot
Then when I use "Start"
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
boot up failed
If there is any other info I can give I'd be happy to. Thank you very much for your time!
Oka, that's the problem, I noticed that the forum you posted was about a different but very similar phone, when my phone was stuck I used this video https://youtu.be/6avEPGWB8E0
Disclaimer: it will completely wipe your system of everything and install android 5.1, even though it tells you to edit the files DO NOT, I edited then and it made it much worse.
Sent from my DROID Turbo using Tapatalk
Good morning
Howdy,
I am trying to method you have provided and I am running into errors because my bootloader is locked I believe.
When I run the RootJunky bat script I get error messages like these for each of the images it wants to push :
Code:
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>VRZ_XT1254_SU2-12_12_CFC.bat
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>SET fastboot=fastboot.exe
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.053s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash motoboot bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:motoboot: not found
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.073s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.122s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (85771 KB)...
OKAY [ 2.738s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 4.510s]
finished. total time: 7.249s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2631 KB)...
OKAY [ 0.086s]
writing 'logo'...
OKAY [ 0.199s]
finished. total time: 0.287s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.553s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 0.541s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.785s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 8.388s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.443s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254164 KB)...
OKAY [ 8.126s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.133s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 8.341s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.346s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 8.347s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.356s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262143 KB)...
OKAY [ 8.358s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.365s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 8.344s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.350s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (9924 KB)...
OKAY [ 0.317s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.324s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase ddr
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:ddr: not found
erasing 'ddr'...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.171s]
finished. total time: 0.172s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 17.493s]
finished. total time: 17.494s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>pause
Press any key to continue . . .
I then went to this forum link ( https://forum.xda-developers.com/dr...-bootloader-os-failed-to-flash-t3032775/page3 ) and am trying to unlock my bootloader via the Motorola instructions ( https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b )
and I am getting this error :
Code:
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.047s
My phone knows it's connected via USB ( rebooting made the drivers work ) but when I do "adb devices" , no device is listed even though I am at the recovery screen.
Any further advice would be appreciated!
Update ( Still no good )
Howdy,
When I try
"fastboot devices" it returns
???????????? fastboot
:\ did I really kill kill kill my phone?
Reizvoller said:
Howdy,
When I try
"fastboot devices" it returns
???????????? fastboot
:\ did I really kill kill kill my phone?
Click to expand...
Click to collapse
Hmmmm, that's strange. I don't think you killed it, try using a different micrusb, that fixed the problem for me when I was using adb
Sent from my DROID Turbo using Tapatalk
Rshelver said:
Hmmmm, that's strange. I don't think you killed it, try using a different micrusb, that fixed the problem for me when I was using adb
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
I'm going to go back to a dumb-phone if it's the USB cable that's messing me up... lol
I will give that a shot once I find a different one around here. In the mean time I did get "fastboot devices" to give me an ID string for the phone.
So, that's something
Reizvoller said:
I'm going to go back to a dumb-phone if it's the USB cable that's messing me up... lol
I will give that a shot once I find a different one around here. In the mean time I did get "fastboot devices" to give me an ID string for the phone.
So, that's something
Click to expand...
Click to collapse
Since, you got fastboot devices to work try all of the next steps, it should work
Sent from my DROID Turbo using Tapatalk
When I do "RootJunky"s thing I still have the same end result.
Code:
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>VRZ_XT1254_SU2-12_12_CFC.bat
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>SET fastboot=fastboot.exe
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.054s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash motoboot bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:motoboot: not found
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.085s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.131s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (85771 KB)...
OKAY [ 2.786s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.436s]
finished. total time: 4.240s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2631 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.073s]
finished. total time: 0.169s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.569s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.815s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.800s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 8.537s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.600s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254164 KB)...
OKAY [ 8.318s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.329s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3.903s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk4
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262141 KB)...
OKAY [ 8.589s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.589s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262143 KB)...
OKAY [ 8.624s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.624s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 8.586s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.586s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe flash system system.img_sparsechunk7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (9924 KB)...
OKAY [ 0.331s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.349s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase ddr
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:ddr: not found
erasing 'ddr'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.072s]
finished. total time: 0.072s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.730s]
finished. total time: 0.730s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>fastboot.exe oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\reizv\Downloads\VRZ_XT1254_SU2-12_12_CFC.xml>pause
Press any key to continue . . .
Okay, I remember I had to change the file a tiny bit, but not how rootjunky did, when I get home later I could email you the files if you wished
Sent from my DROID Turbo using Tapatalk
If that wouldn't be too much trouble to ask, I would really appreciate it
So if other people run into this issue, how about post it here so they can get the fix too?
And you will be glorified as the savior of the Turbos!
Will do
Sent from my DROID Turbo using Tapatalk
Rshelver said:
Okay, did you unlock the bootloader using sunshine?
And can you clarify the model number of your device.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Reizvoller said:
Howdy,
No, I did not use Sunshine as that was not described in the instructions
Click to expand...
Click to collapse
They are described in the instructions. You were just reading the wrong instructions. In that thread you are pointing to (in this Droid Turbo forum):
[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5
This is in the first post:
jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
The temp root is meant to be used as a tool to then unlock the bootloader using Sunshine. You shouldn't even be messing with Magisk and stuff until after unlocking the bootloader with Sunshine.
In comments throughout that thread (in this forum), we make it clear the temp root is only to be used temporarily. On the very last page of that thread, I just recently told someone if they didn't unlock their bootloader and kept trying to use just the temp root, they did so at their own risk.
Maybe that wasn't your intent, to use the "temp root" permanently, but still you then went over to the temp root thread (in another device forum) and followed all those instructions.
The problem is the temp root dev, whom I respect, didn't really make that temp root thread for the Droid Turbo. He started it as a simple tool, but then later developed it into a very extensive system for perpetual root. He doesn't even mention Sunshine in those instructions, right? Whereas @jcase's post (in this forum) clearly mentions you need to use Sunshine to unlock your bootloader... So, you can see those weren't quite the right instructions...
Whereas this thread below (in this forum) is what you should have been using for root and unlock instructions. It mentions the same temp root as a tool to use to get Sunshine to work -- but WARNS to NOT follow all the temp root instruction thread.
[GUIDE] How to unlock your Droid Turbo bootloader, install TWRP and gain root access
6. !!!DO THIS STEP ONLY IF YOU'RE ON MCG24.251-5-5!!! Follow the instructions here to obtain temporary root:
https://forum.xda-developers.com/g4-...ader-t3639316/.
DO NOT perform the uninstall step, and ignore all steps that mention Magisk or Magisk Manager.
Click to expand...
Click to collapse
Instead just simply use the temp root to then use Sunshine to unlock the bootloader, and you never have to worry about temp root shenanigans again. After THAT, then it even goes on to Magisk, TWRP and all other things.
Over HERE, in the Droid Turbo forum, the powerful temp root is only used as simple tool to get bootloader unlock and then permanent root and custom recovery.
I'm very sorry for your problems, but I hope this warning helps other people.
That all makes far more sense now, thank you very much for setting me straight with this information.
Reizvoller said:
Howdy,
No, I did not use Sunshine as that was not described in the instructions
My exact device is "Droid Turbo XT1254" , it /was/ fully stock with latest OTA from ISP
I just ran through the Bootloader Logs again ( unsure if they are of any use ) but they say...
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
fastboot reason : fall-through from charger boot mode
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
boot up failed
I then scrolled to "Restart Bootloader" which brings me right back to the bootloader, but now the logs says:
Fastboot Reason : Reboot mode set to fastboot
Then when I use "Start"
bab checked failed for boot
failed to verify bab image boot
failed to validate boot image: ret=-1
boot up failed
If there is any other info I can give I'd be happy to. Thank you very much for your time!
Click to expand...
Click to collapse
Looks like you are flashing an old firmware, you must flash most recent version of XT1254 MCG24.251-5-5 if your device is Verizon carrier or just copy/paste all log from "fastboot getvar all".

Moto G5s Plus hard brick - help needed

Hi all,
So I have well and truly hardbricked my XT1803. Most probably arose as I foolishly flashed a Potter firmware to my Sanders phone. Teaches me for not reading everything carefully before going ahead to flash firmware.
Anyway, I'm now in the situation where I have hard bricked my device completely. No OS, no recovery, no bootloader. Strangely the device can be found if install the device on my PC as "Android ADB interface" and I can run fastboot commands in cmd (however nothing appears on the phones screen). I've detailed my getvar all details below if that helps!
I've tried re-flashing NPS26.116-61 on the device and this gives me an error at the first hurdle as per the below.
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.096s
I've tried blank flash based on the G5 forums to see if this can boot some life into it, however the phone is not recognising as QUALCOMM HS-USB QDLoader 9008
If I force install of the QUALCOMM HS-USB QDLoader 9008 drivers, this just gives me the < waiting for device > if I run blank flash.
Fastboot getvar all as per the below - I've added some in bold as these have been purposely hidden.
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: XXXXXXXXX
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3xxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 01-08-2018
(bootloader) sku: XT1803
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 2:46 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPS26.116-61/74:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.231.74.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-Resurrected-Kernel
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x 2
(bootloader) kernel.version[2]: 0150123 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: MPT Thu Jan 11 23:42:06 EST 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.07-0-g3b15bb0
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=283f623
(bootloader) devcfg.git: git=283f623
(bootloader) keymaster.git: git=283f623
(bootloader) cmnlib.git: git=283f623
(bootloader) cmnlib64.git: git=283f623
(bootloader) prov.git: git=283f623
(bootloader) aboot.git: git=MBM-NG-VC1.07-0-g9d7f987
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.211s
If anyone has any thoughts on bringing this back to life I'd great appreciate it!
Bro try flashing this firmware
https://androidfilehost.com/?fid=673956719939831738
Ur using old version
Hi there,
Thanks for your advice. I tried this and got the following errors on flashing the firmware. All steps were successful other than the below.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
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.101s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.143s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.445s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.457s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.428s]
finished. total time: 0.888s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.609s
i have same problem please give me the solution please
kooljim45 said:
Hi there,
Thanks for your advice. I tried this and got the following errors on flashing the firmware. All steps were successful other than the below.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
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.101s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.143s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.445s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.457s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.428s]
finished. total time: 0.888s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.609s
Click to expand...
Click to collapse
u need to download new firmware or try skipping gpt if ur bootloader is unlocked
Try flash twrp and flashable stock
When 61-5 no work
Sent from my Moto G5S Plus using XDA Labs
Adi5 said:
Try flash twrp and flashable stock
When 61-5 no work
Sent from my Moto G5S Plus using XDA Labs
Click to expand...
Click to collapse
Seriously? How can he flash twrp flashable zip without accessing twrp
Sri Datta said:
Seriously? How can he flash twrp flashable zip without accessing twrp
Click to expand...
Click to collapse
My bad
I didn't say error while flashing recovery
Fastboot boot twrp.img maybe will work but it won't help
Sent from my Moto G5S Plus using XDA Labs
I have tried the latest firmware. The biggest issue is that my PC can see the device through fastboot, however nothing appears on the phone screen.
Do ...U have twrp . Working???..try a custom ROM bro ....
TWRP is not working. The bootloader doesn't start. There is no recovery mode.
Fast boot mode??
Bro try unlocking bootloader then flash bootloader
Image primary_gpt failed validation
Hi! Sorry about my language, im from Argentina. I'm trying to flash a rom on Moto G5S Plus, and i catch this error:
Image primary_gpt failed validation.
Log is here:
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.154s
I'm Flashing: SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Anybody can help me please? I cant install Magisk anyway!
XT1800. Nougat 7.1.1
Thks
damansilla said:
Hi! Sorry about my language, im from Argentina. I'm trying to flash a rom on Moto G5S Plus, and i catch this error:
Image primary_gpt failed validation.
Log is here:
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.154s
I'm Flashing: SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Anybody can help me please? I cant install Magisk anyway!
XT1800. Nougat 7.1.1
Thks
Click to expand...
Click to collapse
U need flash newest software..... Which software channel u have?
Adi5 said:
U need flash newest software..... Which software channel u have?
Click to expand...
Click to collapse
Hi! What do you refer with software channel? Sorry i dont understand.
I did some research on this.. Your out of luck. Best is to sell it for parts not working. Or take it to a shop that specialize in phone repair.. Might cost you a $100, but it is better than buying a new one, which is costly.
damansilla said:
Hi! What do you refer with software channel? Sorry i dont understand.
Click to expand...
Click to collapse
Every region has a Software channel, you can check the name of your region's channel in the About Phone section
thippu46 said:
Every region has a Software channel, you can check the name of your region's channel in the About Phone section
Click to expand...
Click to collapse
Hi! My channel Is retar.
Thanks!
damansilla said:
Hi! My channel Is retar.
Thanks!
Click to expand...
Click to collapse
Which version u have now?

{help needed} Phone Unable to Boot: Falls back to Fastboot,

This Happened all of a sudden. Phone was running stock only , nothing ever altered. Seems like phone was trying to update itself and something wrong happened.
Oem is locked.
Software status says Modified
oem_get_unlock_data fails to retrieve device ID, says "unable to read datablock"
rest all say the screen shots.
Service Center denies availing warranty or software fix as software status says "Modified". Rather provided quote of INR 18k
this happened to me too once, and scared me as ***k
you got to delete the orphaned ota via fastboot
i am not 100% sure this is the exact command i used to fix my issue, but pretty much confident
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/fota
you can enter this either via fastboot or via recovery terminal
ElKorki said:
this happened to me too once, and scared me as ***k
you got to delete the orphaned ota via fastboot
i am not 100% sure this is the exact command i used to fix my issue, but pretty much confident
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/fota
you can enter this either via fastboot or via recovery terminal
Click to expand...
Click to collapse
I am afraid if this can be done, as I tried to perform wipe using fastboot but all in vein. It throws error. Though Will give it a try.
shwetanklal said:
I am afraid if this can be done, as I tried to perform wipe using fastboot but all in vein. It throws error. Though Will give it a try.
Click to expand...
Click to collapse
I'm following this thread. I think the same thing happened to my GF phone a few days ago. It has never been boot loader unlocked . I'm out of town and need to fix it when I return .
I think when sanders 000000 phone is ****ed.... Should be xt1804,xt1805,xt1800....
Adi5 said:
I think when sanders 000000 phone is ****ed.... Should be xt1804,xt1805,xt1800....
Click to expand...
Click to collapse
A lot more info is garbage when fetched from fastboot .IMEI is null. Cif is 0xDEAD. Many other variable returns null or 000000000. I have given up on this phone as of now . Kinda busy these days.
I wish if there was a tool to force flash ROM .
But still, since memory seems inaccessible ,even that wouldn't have helped.
I just discovered that stock rom may be flashed even when the bootloader is locked.
But am getting error of pre-flash validation . I was wondering if someone could help me to choose right stock rom from here .
Fastboot gatvar all result as follows:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 5e88a864
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0275010D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.579s
Trying to flash Stock Return this:
Code:
...
FAILED (remote failure)
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.029s]
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.149s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootlo
ader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.203s]
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.541s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.088s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.161s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.697s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.916s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.675s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.942s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.565s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.638s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 19.780s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 30.193s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 30.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 21.350s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 21.401s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 28.165s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.224s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 23.995s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.045s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 25.289s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 25.357s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 15.092s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 15.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 2.591s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 2.661s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.076s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.107s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.183s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.082s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.073s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase logo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
erasing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
FAILED (remote failure)
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Firm ware i tried flashing was SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.
Someone please help me to skip pre-validation flash by suggesting someway to flash unconditionally or help me select right stock rom that passes validation.
Suggest using the most current firmware SANDERS_NPSS26.116-26-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, it can be found on xda for downloading.
As far as i remember I had the same issue when having already been on a higher firmware version than the one I'm trying to flash.
good luck !
mmephisto said:
Suggest using the most current firmware SANDERS_NPSS26.116-26-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, it can be found on xda for downloading.
As far as i remember I had the same issue when having already been on a higher firmware version than the one I'm trying to flash.
good luck !
Click to expand...
Click to collapse
Its only for eu varient
Adi5 said:
Its only for eu varient
Click to expand...
Click to collapse
Yes, true. Afaik the firmware he tries to flash is EU as well ?! (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
So the SANDERS_NPS26.116-26-14... is the newer version of SANDERS_NPS26.116-26, and therefore it should be the correct one? Or am I wrong ?
mmephisto said:
Yes, true. Afaik the firmware he tries to flash is EU as well ?! (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
So the SANDERS_NPS26.116-26-14... is the newer version of SANDERS_NPS26.116-26, and therefore it should be the correct one? Or am I wrong ?
Click to expand...
Click to collapse
From reading the initial post, the opening poster appears to have an Indian device (quoting INR - Indian Rupees). Thus, flashing a firmware meant for EU devices and not for Indian devices isn't a good idea, especially for a device in this state. I think the correct Indian firmware would be NPSS26.116-61-8.
Unfortunately, those errors looks like the motherboard flash memory may be failing. You could try to flash this NPSS26.116-61-8 firmware https://androidfilehost.com/?fid=746163614322262641 and see how you get on. If your device is still dead after flashing, unfortunately you may have to either pay to get the device fixed or purchase a new device.
echo92 said:
From reading the initial post, the opening poster appears to have an Indian device (quoting INR - Indian Rupees). Thus, flashing a firmware meant for EU devices and not for Indian devices isn't a good idea, especially for a device in this state. I think the correct Indian firmware would be NPSS26.116-61-8.
Unfortunately, those errors looks like the motherboard flash memory may be failing. You could try to flash this NPSS26.116-61-8 firmware https://androidfilehost.com/?fid=746163614322262641 and see how you get on. If your device is still dead after flashing, unfortunately you may have to either pay to get the device fixed or purchase a new device.
Click to expand...
Click to collapse
This is so cool, I was in the exact fix and after flashing the EU firmware I had my radio off! I am gonna try this today evening once I am home.
echo92 said:
From reading the initial post, the opening poster appears to have an Indian device (quoting INR - Indian Rupees). Thus, flashing a firmware meant for EU devices and not for Indian devices isn't a good idea, especially for a device in this state. I think the correct Indian firmware would be NPSS26.116-61-8.
Unfortunately, those errors looks like the motherboard flash memory may be failing. You could try to flash this NPSS26.116-61-8 firmware https://androidfilehost.com/?fid=746163614322262641 and see how you get on. If your device is still dead after flashing, unfortunately you may have to either pay to get the device fixed or purchase a new device.
Click to expand...
Click to collapse
Thanks a lot . Am gonna try it.:good:
echo92 said:
From reading the initial post, the opening poster appears to have an Indian device (quoting INR - Indian Rupees). Thus, flashing a firmware meant for EU devices and not for Indian devices isn't a good idea, especially for a device in this state. I think the correct Indian firmware would be NPSS26.116-61-8.
Unfortunately, those errors looks like the motherboard flash memory may be failing. You could try to flash this NPSS26.116-61-8 firmware https://androidfilehost.com/?fid=746163614322262641 and see how you get on. If your device is still dead after flashing, unfortunately you may have to either pay to get the device fixed or purchase a new device.
Click to expand...
Click to collapse
Error remains the same. Unable to flash/prevlidate/writing failed /Remote error. All of it. I guess the phone is dead.
shwetanklal said:
Error remains the same. Unable to flash/prevlidate/writing failed /Remote error. All of it. I guess the phone is dead.
Click to expand...
Click to collapse
Any update? Even im facing the same problem
Holding volume down button first and then simultaneously holding power button all these for two minutes while connected to original charger did the trick for me yesterday
But the issue repeated again today and the fix doesn't seem to work
!!!!!!!
Got it serviced,they fixed it under 3 hours!
Maxz21 said:
Any update? Even im facing the same problem
Holding volume down button first and then simultaneously holding power button all these for two minutes while connected to original charger did the trick for me yesterday
But the issue repeated again today and the fix doesn't seem to work
!!!!!!!
Got it serviced,they fixed it under 3 hours!
Click to expand...
Click to collapse
Great!
unluckily service center guys in my place know nothing except changing the board for something they don't want to understand.
shwetanklal said:
Great!
unluckily service center guys in my place know nothing except changing the board for something they don't want to understand.
Click to expand...
Click to collapse
Its fyn as long as they don't charge you for it.
I got it done for free!
G5S Plus - Startup Failed
Hello
I have a problem. My cell phone turned off after charging, then it got slow, I restarted it and it got slower and then when it starts up it looks, show this:
Booloader logs
start up failed:
your device didnt start up successfully. use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
ap fastboot flash mode (secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Pressing volume down and power button does not work. It only works to keep the power button and it shows the previous message.
Digit adb devices and shows:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
digit mfastboot devices and shows:
e237d3d5 fastboot
digit mfastboot oem fb_mode_set and shows:
...
FAILED (remote failure)
finished. total time: -0.000s
digit fastboot oem get_unlock_data and shows:
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.018s
this show when run mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: e237d3--
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: B14FE28700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Can you help me ...
the motorola support says that the phone need a software recharge at a service center, but the pandemian this are closed
I install:
MotorolaDeviceManager_2.5.4
rescue_and_smart_v5.0.0.25_setup
adb and mfastboot
The usb interface show by the phone pc conection "Motorola ADB interface"
I try recover with Rescue and smart assistant: rescue option select Moto G Plus (5th Gen S) model: XT1801 and show this:
Failed to natch the connected device. Reconect device, then try again.
I run the software and sho the phone model but dont reconize this when i select
I connect the celular phone by usb and conect

i softbricked moto g6 :(

so here i am, after 2 days of scrutinizing every corner of the internet, looking for solution. i had my moto g6 on pie but out of curiosity i wanted try out different roms and here is what happened:
- after ive successfully unlocked the oem lock, installed twrp and tried to install different roms just to run into error 255 and such i gave up and thought **** it lets go back to original rom, so i fired up fastboot and put back oreo that i downloaded from here, the splashscreen however was still bearing the 'device has been unlocked and cant be trusted' message, so i thought i would put back the oem lock and then formatted the device... ooops and thats when i started having these problems.
- since then i cant install any rom - stock or mod (i was however successful in flashing twrp back on the phone)
- fastboot says FLASHING_LOCKED and having tried maybe 6 different stock roms i noticed that i can flash these two lines without problems:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
but anything after that is giving me (bootloader) flash permission denied FAILED (remote failure) in powershell
so to sum it up: i can boot into fastboot or twrp but i cant do much anything else
ive seemed to exhaust every remote advice out there and really dont know what to do anymore
any of you guys could point me in the right direction? or is the phone done and done?
here is the fastboot var list
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 14: 4:32 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
thx
Peter
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
najjannajS650 said:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
Click to expand...
Click to collapse
thanks, i think ive already tried that already before,
here is a recap of what happens when i type in fastboot flashing unlock
- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.
- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.
i dont have any rom installed so i cant get into developers options and allow OEM unlock
edited: and if i try ./fastboot oem unlock
i get
... (bootloader) invalid boot state
:crying:
nobody has solution to this? really????
delosanto said:
nobody has solution to this? really????
Click to expand...
Click to collapse
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Spaceminer said:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Click to expand...
Click to collapse
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
delosanto said:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
Click to expand...
Click to collapse
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Spaceminer said:
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Click to expand...
Click to collapse
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
delosanto said:
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: son[email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Click to expand...
Click to collapse
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Spaceminer said:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Click to expand...
Click to collapse
im in the uk, please dont say there is still hope
delosanto said:
im in the uk, please dont say there is still hope
Click to expand...
Click to collapse
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
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.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
i tried to flashed the files exactly in the order they appear in .info file
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem NON-HLOS.bin
./fastboot flash fsg fsg.mbn
./fastboot flash dsp adspso.bin
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash system system.img_sparsechunk.8
./fastboot flash system system.img_sparsechunk.9
./fastboot flash vendor vendor.img_sparsechunk.0
./fastboot flash vendor vendor.img_sparsechunk.1
./fastboot flash oem oem.img
./fastboot erase cache
./fastboot erase userdata
./fastboot erase ddr
./fastboot oem fb_mode_clear
./fastboot reboot
delosanto said:
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
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.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
Click to expand...
Click to collapse
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------
@delosanto
Are you able to boot or flash twrp?
Spaceminer said:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
Click to expand...
Click to collapse
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.
yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode
Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Ragarianok said:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Click to expand...
Click to collapse
the last OS that was successfully flashed was Oreo
delosanto said:
the last OS that was successfully flashed was Oreo
Click to expand...
Click to collapse
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Spaceminer said:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Click to expand...
Click to collapse
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
delosanto said:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
Click to expand...
Click to collapse
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Spaceminer said:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Click to expand...
Click to collapse
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error
(bootloader) flash permission denied
FAILED (remote failure)
but then it crashes back to fastboot
and i even did a clean windows installation today

Categories

Resources