hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia
Hav the same trouble with fastboot. I can't flash any rom, any changes to recovery.
AP Fastboot 10.9B(*) (sha-9d3ad55, 2012-09-15 04:39:04) / AP Fastboot 10.9B(*) (sha-1e9f557, 2012-11-03 09:05:20) - tried on both
Device is LOCKED, Status Code: 0
XT926 NON developer edition
Always get a problem with GPT / boot / system. With any flashing method (RSD Lite + VZW_XT926_4.0.4-7.7.1Q-144_VQW_S3-34-25_CFC.xml or RSD Lite + VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml or DROID_RAZR_HD_Utility1.10).
cw-recovery-vanquish.img get Preflash validation failed
When i tried to flash VZW_XT926_4.0.4-7.7.1Q-144_VQW_S3-34-25_CFC.xml.zip with RSD Lite (6.1.4) i get also
Code:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
When i tried to flash VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip with RSD Lite (6.1.4) i get also
Code:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
DROID_RAZR_HD_Utility 1.10 of course take me the same answer (The phone says Partition (boot) Security Version Downgraded) :
Code:
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.957s
sending 'system' (30720 KB)...
OKAY [ 2.325s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.531s
sending 'recovery' (10240 KB)...
OKAY [ 0.780s]
writing 'recovery'...
OKAY [ 2.923s]
finished. total time: 3.705s
Recovery mode also give me some errors, but i can flash any file from sd or wipe data/cache:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/caller
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Official Motorola update program on desktop also have problem with gpt_main - Preflash validation failed for GPT
You can't flash anything but stock since you have a locked bootloader and xt926. please re-download the fastboot package for jelly bean, don't modify anything (you can't add any custom recovery) and post screenshots of any failures in rsdlite.
For flashing roms, you will have to use safestrap instead.
Sent from my XT925 using Tapatalk 2
danifunker said:
You can't flash anything but stock since you have a locked bootloader and xt926. please re-download the fastboot package for jelly bean, don't modify anything (you can't add any custom recovery) and post screenshots of any failures in rsdlite.
For flashing roms, you will have to use safestrap instead.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Thanx, man! I'll try it today.
I can't flash stock too.
I already said, that
Official Motorola update program on desktop also have problem with gpt_main - Preflash validation failed for GPT
Click to expand...
Click to collapse
When i tried to flash VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip with RSD Lite (6.1.4) i get also
Code:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip is a original firmware from http://forum.xda-developers.com/showthread.php?t=2035131
Or maybe do you mean
fastboot package for jelly bean
Click to expand...
Click to collapse
something other than "Firmware DROID RAZR HD Verizon Jelly Bean 4.1.1 by "Firmware Team" from http://forum.xda-developers.com/showthread.php?t=2035131 ?
Which version of rsdlite are you using?
Sent from my XT925 using Tapatalk 2
danifunker said:
Which version of rsdlite are you using?
Click to expand...
Click to collapse
6.1.4. The last one.
When i tried to flash VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip with RSD Lite (6.1.4)
Click to expand...
Click to collapse
jedi220987 said:
6.1.4. The last one.
Click to expand...
Click to collapse
Are you sure this is XT926, not XT925? Please take a new screenshot of RSD Lite (before you flash) with the model information fully visible, as in this screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danifunker said:
Are you sure this is XT926, not XT925?
Click to expand...
Click to collapse
Yeah, of course i have XT926. On the phone's back side is XT926. And i flashed already safestrap for XT926 when the phone worked, and use Droid Utility for XT926.
But i has some trouble with battery and want to flash once again. Last time before stuck in fastboot mode i tried to flash LTE modem for my local frequency from XT925(Telcel). Maybe this can explain why i can't flash files for XT926. Maybe i flash fastboot for XT925 and phone think now that i have XT925, but it's wrong. But as i see - i have correctly XT926 fastboot and can change two fastboot version with RSD Lite or Droid Utility:
- AP Fastboot 10.9B(*) (sha-9d3ad55, 2012-09-15 04:39:04)
- AP Fastboot 10.9B(*) (sha-1e9f557, 2012-11-03 09:05:20)
Maybe i need a newer fastboot for JB (maybe 4.2?)? Anyone have it? I can't flash latest stock rom from Motorola over official Motorola utility too. Has the same error with gpt_main.
Can you please unzip your Rom file. Inside that file will be a /bat file called "flash_fastboot.bat"
Run that with your phone in fastboot mode.
If that doesn't work download this fastboot.
http://forum.xda-developers.com/showthread.php?t=1953948
And put "mfastboot.exe" in your unzipped Rom directory, rename it to "fastboot.exe" (to replace the old version that's in there)
and try again.
Let me know how it goes.
Brad
Darbness said:
Can you please unzip your Rom file. Inside that file will be a /bat file called "flash_fastboot.bat"
Run that with your phone in fastboot mode.
If that doesn't work download this fastboot.
http://forum.xda-developers.com/showthread.php?t=1953948
And put "mfastboot.exe" in your unzipped Rom directory, rename it to "fastboot.exe" (to replace the old version that's in there)
and try again.
Brad
Click to expand...
Click to collapse
Thanx, Brad!
In original firmware like VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip isn't file flash_fastboot.bat
Only flashboot.exe in Windows directory
So i replace Windows/fastboot.exe with mfastboot.exe from the link. And then flash once again with RSDLite.
Have the same result with gpt_main and downgraded security version.
And i can change two fastboot version, but can't flash anyway something with the both version.
But as i see - i have correctly XT926 fastboot and can change two fastboot version with RSD Lite or Droid Utility:
- AP Fastboot 10.9B(*) (sha-9d3ad55, 2012-09-15 04:39:04)
- AP Fastboot 10.9B(*) (sha-1e9f557, 2012-11-03 09:05:20)
Click to expand...
Click to collapse
jedi220987 said:
Thanx, Brad!
In original firmware like VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip isn't file flash_fastboot.bat
Only flashboot.exe in Windows directory
So i replace Windows/fastboot.exe with mfastboot.exe from the link. And then flash once again with RSDLite.
Have the same result with gpt_main and downgraded security version.
And i can change two fastboot version, but can't flash anyway something with the both version.
Click to expand...
Click to collapse
I'm at work atm when I get home I'll post the script.
Are you using Windows?
If you are you need to move the fastboot.exe into the main directory and run this file from the same directory.
Brad
Darbness said:
Are you using Windows?
If you are you need to move the fastboot.exe into the main directory and run this file from the same directory.
Brad
Click to expand...
Click to collapse
So. I run this script and get the same on the phone screen:
Code:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Partition (boot) Security Version Downgraded
preflash validation failed for boot
Partition (system) Security Version Downgraded
PIV block validation for system failed
Invalid PIV image: system
And here is console from desktop with the same errors:
Code:
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.422s]
finished. total time: 0.437s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.016s]
writing 'sbl2'...
OKAY [ 0.734s]
finished. total time: 0.750s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
OKAY [ 0.906s]
finished. total time: 0.969s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
OKAY [ 0.422s]
finished. total time: 0.453s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.453s]
finished. total time: 0.469s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.672s]
finished. total time: 0.687s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
pause
Press any key to continue . . .
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash partition gpt_main0.bin
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.172s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.422s]
finished. total time: 0.437s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.016s]
writing 'sbl2'...
OKAY [ 0.719s]
finished. total time: 0.734s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
OKAY [ 0.906s]
finished. total time: 0.953s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.437s]
finished. total time: 0.453s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.031s]
writing 'tz'...
OKAY [ 0.437s]
finished. total time: 0.469s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.672s]
finished. total time: 0.703s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.953s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.312s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.516s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.766s]
writing 'recovery'...
OKAY [ 2.516s]
finished. total time: 3.281s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash modem NON-HLOS.bin
sending 'modem' (30720 KB)...
OKAY [ 2.297s]
writing 'modem'...
OKAY [ 0.875s]
sending 'modem' (17496 KB)...
OKAY [ 3.781s]
writing 'modem'...
OKAY [ 1.047s]
finished. total time: 8.000s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.469s]
finished. total time: 0.516s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash logo logo.bin
sending 'logo' (1709 KB)...
OKAY [ 0.141s]
writing 'logo'...
OKAY [ 1.109s]
finished. total time: 1.250s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash cdrom cdrom
sending 'cdrom' (30720 KB)...
OKAY [ 2.312s]
writing 'cdrom'...
OKAY [ 2.906s]
sending 'cdrom' (22538 KB)...
OKAY [ 4.141s]
writing 'cdrom'...
OKAY [ 2.391s]
finished. total time: 11.750s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.594s]
finished. total time: 0.594s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.594s]
finished. total time: 0.594s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash fsg fsg.mbn
sending 'fsg' (2704 KB)...
OKAY [ 0.203s]
writing 'fsg'...
OKAY [ 1.062s]
finished. total time: 1.266s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase cache
erasing 'cache'...
OKAY [ 0.969s]
finished. total time: 0.969s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase userdata
erasing 'userdata'...
OKAY [ 7.016s]
finished. total time: 7.016s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase tombstones
erasing 'tombstones'...
OKAY [ 0.719s]
finished. total time: 0.719s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
pause
Press any key to continue . . .
Can you try and get into recovery? press vol + and power on then select recovery.
Brad
Darbness said:
Can you try and get into recovery? press vol + and power on then select recovery.
Brad
Click to expand...
Click to collapse
Yeah, i can enter into recovery mode without any problems.
And already press + and - to get a recovery menu.
Flash once again from desktop in recovery mode? Or place image files into sd-card? Or place an archive with ROM into sd-card? =)
Interesting, Can you please delete the line
"fastboot flash partition gpt_main0.bin"
from the fastboot.bat and try again.
Brad
Darbness said:
Interesting, Can you please delete the line
"fastboot flash partition gpt_main0.bin"
from the fastboot.bat and try again.
Brad
Click to expand...
Click to collapse
The same trouble, but without GPT failed. =)
Phone:
Code:
Partition (boot) Security Version Downgraded
preflash validation failed for boot
Partition (system) Security Version Downgraded
PIV block validation for system failed
Invalid PIV image: system
Console from desktop:
Code:
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.422s]
finished. total time: 0.437s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.016s]
writing 'sbl2'...
OKAY [ 0.734s]
finished. total time: 0.750s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
OKAY [ 0.906s]
finished. total time: 0.969s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
OKAY [ 0.422s]
finished. total time: 0.453s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.453s]
finished. total time: 0.469s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.672s]
finished. total time: 0.687s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
pause
Press any key to continue . . .
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (100 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.422s]
finished. total time: 0.437s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl2 sbl2.mbn
sending 'sbl2' (126 KB)...
OKAY [ 0.016s]
writing 'sbl2'...
OKAY [ 0.719s]
finished. total time: 0.734s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash sbl3 sbl3.mbn
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
OKAY [ 0.906s]
finished. total time: 0.953s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash rpm rpm.mbn
sending 'rpm' (140 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.437s]
finished. total time: 0.453s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash tz tz.mbn
sending 'tz' (192 KB)...
OKAY [ 0.031s]
writing 'tz'...
OKAY [ 0.437s]
finished. total time: 0.469s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.672s]
finished. total time: 0.703s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.953s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.312s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.516s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.766s]
writing 'recovery'...
OKAY [ 2.516s]
finished. total time: 3.281s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash modem NON-HLOS.bin
sending 'modem' (30720 KB)...
OKAY [ 2.297s]
writing 'modem'...
OKAY [ 0.875s]
sending 'modem' (17496 KB)...
OKAY [ 3.781s]
writing 'modem'...
OKAY [ 1.047s]
finished. total time: 8.000s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.469s]
finished. total time: 0.516s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash logo logo.bin
sending 'logo' (1709 KB)...
OKAY [ 0.141s]
writing 'logo'...
OKAY [ 1.109s]
finished. total time: 1.250s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash cdrom cdrom
sending 'cdrom' (30720 KB)...
OKAY [ 2.312s]
writing 'cdrom'...
OKAY [ 2.906s]
sending 'cdrom' (22538 KB)...
OKAY [ 4.141s]
writing 'cdrom'...
OKAY [ 2.391s]
finished. total time: 11.750s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.594s]
finished. total time: 0.594s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.594s]
finished. total time: 0.594s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot flash fsg fsg.mbn
sending 'fsg' (2704 KB)...
OKAY [ 0.203s]
writing 'fsg'...
OKAY [ 1.062s]
finished. total time: 1.266s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase cache
erasing 'cache'...
OKAY [ 0.969s]
finished. total time: 0.969s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase userdata
erasing 'userdata'...
OKAY [ 7.016s]
finished. total time: 7.016s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
fastboot erase tombstones
erasing 'tombstones'...
OKAY [ 0.719s]
finished. total time: 0.719s
c:\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml\VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml>
pause
Press any key to continue . . .
The error "Security Version Downgraded" should only happen if you are going to an older version, did you download the leaked version?
Darbness said:
The error "Security Version Downgraded" should only happen if you are going to an older version, did you download the leaked version?
Click to expand...
Click to collapse
Yeah, i understand what means this error. =)
I've downloaded the latest original version that can find - http://forum.xda-developers.com/showthread.php?t=2035131
As i know, this is not leaked version. Just original ROM-image from Mototola. Or?
And the original firmware from Motorola utility also have the same errors, but i don't know why....
[/COLOR]Wait, dont. but we need to find the update.zip for the xt926 razr hd.
---------- Post added at 07:36 PM ---------- Previous post was at 07:30 PM ----------
Sorry I have hit a wall and dont know how else I can help you.
I have an XT925 so I cant even try to emulate your problem on my phone.
All i can say is to try a different version of the firmware?
Brad
One last attemp, download this file
"http://www.mydroidfiles.com/downloads/Satman80/delta-ota-Blur_Version.0.7.2-9.1.41.XT926.Verizon.en.US/delta-ota-Blur_Version.0.7.2-9.1.41.XT926.Verizon.en.US.zip"
then follow these steps,
"http://www.droidforums.net/forum/droid-razr/213197-offical-ota-zip-installation-guide-droid-razr-razr-maxx.html"
Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.
What recovery you using?
Sent from my Nexus S using xda app-developers app
Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.
It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app
Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.
system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app
Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?
I was given a xt1080 for repair
24.13.2.obake-maxx
SU6-7.2
Locked bootloader. No root. No adb access.
System boots but there is constants force close of background processes like gapps and acore.
I wanted to factory reset and I did but on reboot it had all the same apps and user data intact, no factory state.
Changing any config or uninstalling any app result in it being back after reboot.
What I've tried so far:
-Factory option in AP Fastboot menu. Reboots to system with all the data intact.
-Recovery option in AP Fastboot menu. Reboots to bootloader and states "Boot up failed".
-fastboot erase userdata
-fastboot -w
both with the resulting output:
erasing 'userdata'...
OKAY [ 0.500s]
erasing 'cache'...
OKAY [ 0.620s]
finished. total time: 1.120s
but sadly all userdata is sitting there intact after reboot.
I downloaded VZW-4.4.4-SU6-7.2-release-keys.xml.zip. Tried with RSDLite but it didn't detect the device.
I have installed the drivers and MotorolaDeviceManager. So I decompressed the firmware and flashed the partitions
using fastboot in a script. Resulting in all partitions being flashed OK but after reboot the device
was the same as before with all the apps and user data present. Spooky isn't it?
Can some one offer me any advice? Is it a hardware faliure?
Output of the script follows:
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_set
< waiting for device >
...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.220s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.444s]
finished. total time: 0.665s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.360s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 4.540s]
finished. total time: 4.900s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash logo logo.bin
sending 'logo' (215 KB)...
OKAY [ 0.290s]
writing 'logo'...
OKAY [ 0.811s]
finished. total time: 1.102s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.900s]
writing 'boot'...
OKAY [ 1.872s]
finished. total time: 2.772s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.900s]
writing 'recovery'...
OKAY [ 1.512s]
finished. total time: 2.412s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.426s]
writing 'system'...
OKAY [ 54.106s]
sending 'system' (531955 KB)...
OKAY [ 33.515s]
writing 'system'...
OKAY [ 36.056s]
finished. total time: 173.103s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash modem NON-HLOS.bin
sending 'modem' (54252 KB)...
OKAY [ 3.671s]
writing 'modem'...
OKAY [ 2.330s]
finished. total time: 6.002s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.419s]
finished. total time: 0.419s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.419s]
finished. total time: 0.419s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash fsg fsg.mbn
sending 'fsg' (538 KB)...
OKAY [ 0.330s]
writing 'fsg'...
OKAY [ 0.761s]
finished. total time: 1.092s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.649s]
finished. total time: 0.649s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.540s]
finished. total time: 0.540s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase customize
erasing 'customize'...
OKAY [ 0.150s]
finished. total time: 0.150s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase clogo
erasing 'clogo'...
OKAY [ 0.518s]
finished. total time: 0.518s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem config carrier gsm
...
Failed to flash config value
OKAY [ 0.149s]
finished. total time: 0.150s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_clear
...
OKAY [ 0.148s]
finished. total time: 0.148s
C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
I selected BP Tools in bootloader menu. Now I have adb access. Tried to delete some files, this is what I get:
[email protected]:/sdcard/dcim/Camera $ rm *
rm *
rm failed for IMG_20160222_223144143.jpg, Read-only file system
255|[email protected]:/sdcard/dcim/Camera $
In BP Tools mode various devices get detected. One of them is Motorola QC Diag Port, I installed the drivers.
Now it shows in QPST software. QPST has a Software Download utility that is suposed to flash bootloaders,
partitions images and whole firmware images. Does any one has any experience flashing with QPST?
Do you already resolve this issue? I got the same problem.
Please help me out my phone goes to crash dump mode while installing Pixel 5 - SPB3 - Android 12 Beta 3 for OnePlus 8 Series using video of #TechiBee
Following were the commands and errors ======
Pixel S for OnePlus8 Series
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.006s]
Finished. Total time: 0.124s
Sending 'recovery' (102400 KB) OKAY [ 5.226s]
Writing 'recovery' OKAY [ 0.350s]
Finished. Total time: 5.679s
Sending 'dtbo_a' (24576 KB) OKAY [ 1.247s]
Writing 'dtbo_a' OKAY [ 0.078s]
Finished. Total time: 1.383s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.115s]
Finished. Total time: 0.667s
rebooting into fastboot OKAY [ 0.007s]
Finished. Total time: 0.042s
< waiting for any device >
Deleting 'system_b' OKAY [ 0.007s]
Finished. Total time: 0.008s
Deleting 'product_b' OKAY [ 0.006s]
Finished. Total time: 0.006s
Deleting 'system_ext_b' OKAY [ 0.006s]
Finished. Total time: 0.007s
Deleting 'system_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Deleting 'vendor_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Erasing 'system_ext_a' OKAY [ 0.036s]
Finished. Total time: 0.041s
Erasing 'product_a' OKAY [ 0.036s]
Finished. Total time: 0.043s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/14 (262140 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 377.221s
finally my devies goes to crash dump mode and now only opens fastboot mode.
do msm
wawanRedblack said:
do msm
Click to expand...
Click to collapse
Besides EDL, he can also use fastboot mode
Update firmware,
if still stuck, try this in fastboot mode:
fastboot delete-logical-partition product_a
fastboot create-logical-partition product_a 100000
wawanRedblack said:
do msm
Click to expand...
Click to collapse
no response while trying msm please help me out
CDI-78 said:
Update firmware,
if still stuck, try this in fastboot mode:
fastboot delete-logical-partition product_a
fastboot create-logical-partition product_a 100000
Click to expand...
Click to collapse
how to update firmware in crash dump mode please help me
LR7875 said:
Besides EDL, he can also use fastboot mode
Click to expand...
Click to collapse
how to use fastboot mode to solve this problem please help
wawanRedblack said:
do msm
Click to expand...
Click to collapse
hello sir i tried to do msm but not dedected any devices while doing msm please help me
Crash Dump (9008/900E) mode need Qualcomm HS-USB driver:
Microsoft Update Catalog
www.catalog.update.microsoft.com
Kundan Shrestha said:
now only opens fastboot mode.
Click to expand...
Click to collapse
'Only opens fastboot mode'
should be
'cannot open fastboot mode'
from my understanding. But everyone has typos, sorry for the misunderstanding caused.
Did u try to format a d reinstall android 11??
Kundan Shrestha said:
Please help me out my phone goes to crash dump mode while installing Pixel 5 - SPB3 - Android 12 Beta 3 for OnePlus 8 Series using video of #TechiBee
Following were the commands and errors ======
Pixel S for OnePlus8 Series
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.006s]
Finished. Total time: 0.124s
Sending 'recovery' (102400 KB) OKAY [ 5.226s]
Writing 'recovery' OKAY [ 0.350s]
Finished. Total time: 5.679s
Sending 'dtbo_a' (24576 KB) OKAY [ 1.247s]
Writing 'dtbo_a' OKAY [ 0.078s]
Finished. Total time: 1.383s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.540s]
Writing 'dtbo_b' OKAY [ 0.115s]
Finished. Total time: 0.667s
rebooting into fastboot OKAY [ 0.007s]
Finished. Total time: 0.042s
< waiting for any device >
Deleting 'system_b' OKAY [ 0.007s]
Finished. Total time: 0.008s
Deleting 'product_b' OKAY [ 0.006s]
Finished. Total time: 0.006s
Deleting 'system_ext_b' OKAY [ 0.006s]
Finished. Total time: 0.007s
Deleting 'system_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Deleting 'vendor_a' OKAY [ 0.005s]
Finished. Total time: 0.006s
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
Finished. Total time: 0.006s
Erasing 'system_ext_a' OKAY [ 0.036s]
Finished. Total time: 0.041s
Erasing 'product_a' OKAY [ 0.036s]
Finished. Total time: 0.043s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/14 (262140 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 377.221s
finally my devies goes to crash dump mode and now only opens fastboot mode.
Click to expand...
Click to collapse
Looks like you may. Need to resize your system partion