Agassi2-W09B - three buttons update - 5% and failed. - Huawei MediaPad T5 Questions & Answers

Agassi2-W09B - three buttons update - 5% and failed. - Huawei MediaPad T5 Questions & Answers

Hi. As the topic. I tried to upload lineage but something went wrong so I did a fastboot cleanup. I made the instructions:
fastboot erase preinstall
fastboot erase webtop
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase userdata
fastboot –w
After that I download firmware "Huawei MediaPad T5 AGS2-W09 hw demo Agassi2-W09B 8.0.0.181D(EEAC652) Firmware 8.0.0 r1 EMUI8.0 05015UUP [androidhost.ru]" which i copied in 8gb sd dload/update.app.
the operation lasts until 5% and system returned software install failed. Now I don't know what should I do.
{
"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"
}

after installation image in fastboot with codes i have another error. During installation i had problem with vbmeta. system returned information "'image verification error'"
C:\adb>fastboot erase system
Erasing 'system' OKAY [ 29.238s]
Finished. Total time: 29.250s
C:\adb>fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.085s]
Finished. Total time: 0.096s
C:\adb>fastboot erase cache
Erasing 'cache' OKAY [ 1.123s]
Finished. Total time: 1.134s
C:\adb>fastboot erase kernel
Erasing 'kernel' OKAY [ 0.219s]
Finished. Total time: 0.230s
C:\adb>fastboot flash kernel kernel.img
Sending 'kernel' (24576 KB) OKAY [ 0.631s]
Writing 'kernel' OKAY [ 0.477s]
Finished. Total time: 1.129s
C:\adb>fastboot erase ramdisk
Erasing 'ramdisk' OKAY [ 0.152s]
Finished. Total time: 0.163s
C:\adb>fastboot flash recovery_ramdisk ramdisk.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.847s]
Writing 'recovery_ramdisk' OKAY [ 0.269s]
Finished. Total time: 1.141s
C:\adb>fastboot erase vendor
Erasing 'vendor' OKAY [ 6.678s]
Finished. Total time: 6.689s
C:\adb>fastboot flash vendor vendor.img
Sending 'vendor' (16384 KB) OKAY [ 0.423s]
Writing 'vendor' OKAY [ 0.134s]
Finished. Total time: 0.578s
C:\adb>fastboot erase vbmeta
Erasing 'vbmeta' OKAY [ 0.055s]
Finished. Total time: 0.066s
C:\adb>fastboot flash vbmeta vbmeta.img
fastboot: error: cannot load 'vbmeta.img': No such file or directory
C:\adb>fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (6 KB) OKAY [ 0.005s]
Writing 'vbmeta' FAILED (remote: 'image verification error')
fastboot: error: Command failed
C:\adb>fastboot flash system system.img
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 12.891s]
Writing 'system' OKAY [ 5.768s]
Sending sparse 'system' 2/7 (459709 KB) OKAY [ 11.909s]
Writing 'system' OKAY [ 3.959s]
Sending sparse 'system' 3/7 (448134 KB) OKAY [ 11.817s]
Writing 'system' OKAY [ 4.148s]
Sending sparse 'system' 4/7 (456673 KB) OKAY [ 12.007s]
Writing 'system' OKAY [ 4.172s]
Sending sparse 'system' 5/7 (442991 KB) OKAY [ 11.536s]
Writing 'system' OKAY [ 3.716s]
Sending sparse 'system' 6/7 (415739 KB) OKAY [ 10.795s]
Writing 'system' OKAY [ 3.489s]
Sending sparse 'system' 7/7 (183048 KB) OKAY [ 4.772s]
Writing 'system' OKAY [ 1.642s]
Finished. Total time: 103.228s
C:\adb>fastboot flash cache cache.img
Sending 'cache' (6200 KB) OKAY [ 0.162s]
Writing 'cache' OKAY [ 0.098s]
Finished. Total time: 0.282s
C:\adb>fastboot flash userdata userdata.img
Sending 'userdata' (24576 KB) OKAY [ 0.632s]
Writing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.275s]
Finished. Total time: 0.930s
C:\adb>FASTBOOT REBOOT
fastboot: usage: unknown command REBOOT
C:\adb>fastboot reboot
Rebooting OKAY [ 0.020s]
Finished. Total time: 0.022s
C:\adb>
Click to expand...
Click to collapse
I added the recovery_ramdisk.img and ramdisk.img files. All the same. continuous bootloop. After all, I also uploaded the os lineage. And then the same.

Go to eRecovery and recover system (you deleted boot partition. that includes part of the bootloader, wich causes corrupt bootloader (or fastboot). vol+ and pwr button. If bootloader unlocked, wait for "your device has been unlocked" screen and then press vol+ for 5-6 sec. If bootloader is not unlocked, follow first part of my LOS18.1 installation guide. That will show you bootloader screen.
I recommend you to use LOS18.1 too. Performance is better than stock emui

Related

XT926 stuck in fastboot / recovery mode.

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"

Error 70 when trying to install GAPPS

Hi people
Yesterday I updated my phone to CyanogenMod(CM)13.0 which went fine. However when I rebooted the phone a popup came up the entire time telling me that google play services stopped working. In an attempt to fix it, I accidently removed google play services, causing a bunch of trouble at the moment.
I went to the CM Wiki and first I downloaded the "nano" variant of the GAPPS, trying to fix everything in the end. I put the file on my phone and tried to install it via recovery. This message came up however:
Insufficiënt storage space available in system partition. You may want to use a smaller GAPPS package or consider removing some apps using GAPPS-config ( bla bla) Error code 70.
As far as I can see, it is able to mount /system and /data, but the partition does not seem to have enough space left, at least so it says.
After that I tried the same with the "pico" variant, which also gave the same result. Pretty strange for a package that small.
So after taking a backup of important files I tried to wipe data/factory reset (was going to reinstall everything), to which I got an error "data wipe failed", which is correct since I can still boot in CM13 after that.
So I'm a bit in trouble here. I cannot seem to wipe my phone entirely, nor am I able to reinstall GAPPS due to this error 70.
Could this be a permissions problem somehow?
Things I have done so far to check what the problem could be:
- I've checked the space left on the /system partition which is 501 MB. Should be enough I guess?
- I've checked the /system partition for errors via adb shell while the phone was in recovery mode, which came out clean.
Below a picture of output of "mount", "df -h" and "uname -a" for extra information.
{
"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"
}
Thanks

Was the phone dirty flashed from an older cm13 rom or was it dirty flashed over a non-cm13 rom?

What do you mean with dirty flashed?
i got this Phone from a friend and the Original stock rom was installed. I installed Cyanogenmod together with gapps and everything went fine back then.

Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.

audit13 said:
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
Click to expand...
Click to collapse
The Phone is working perfectly on its own, except for the google-applications.
That is the reason I only need GApps, to repair the initial problem.
Would it be a solution to format /data and /system and start all over? Although i'm worried that I will still not be able to install GApps due to error 70...

I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.

Which recovery do you use? TWRP or CWM?
Which build date of open gapps have you tried? The latest one?

audit13 said:
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Click to expand...
Click to collapse
It started installing after I initiated the flash-all command. This is the output. i downloaded the correct image and searched the net to know how I had to work with fastboot and such.
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
The full log:
D:\temp\Hammerhead>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
OKAY [ 0.536s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.107s]
finished. total time: 0.110s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.733s]
writing 'radio'...
OKAY [ 3.121s]
finished. total time: 4.858s
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
So, again something about the file being to large. I locked and unlocked the lock state of my phone to make sure it would remove data, to get more space. I guess it did not really work.
Anything else I can do?

Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?

audit13 said:
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
Click to expand...
Click to collapse
Non, they were not edited out. They just did not show up.
Ok, I got the Android stock rom installed on the phone, but now something else is wrong. here is what i did:
Code:
D:\temp\Hammerhead>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.632s]
sending 'system' (1020413 KB)...
OKAY [ 33.134s]
writing 'system'...
OKAY [ 68.970s]
finished. total time: 102.738s
D:\temp\Hammerhead>fastboot flash data data.img
error: cannot load 'data.img'
D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s
D:\temp\Hammerhead>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.489s]
sending 'cache' (13348 KB)...
OKAY [ 0.647s]
writing 'cache'...
OKAY [ 1.074s]
finished. total time: 2.215s
D:\temp\Hammerhead>fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.481s]
writing 'boot'...
OKAY [ 0.774s]
finished. total time: 1.260s
I first erased the partitions "system", "data" and "cache". After that I flashed "system", "userdata", "cache", and lastly "boot"
The phone booted into the rom, I entered my PIN, after which it complained my data was corrupt. It makes sense because of this:
"D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s"
It prolly needs the data partition to write stuff to.
Somehow the partition table of data seems to be gone.
So, the plot thickens! Is there a way I can recreate this partition table, or am I supposed to do something else?

fastboot flash userdata userdata.img
btw, nothing is wrong with your partition table, there is simply no partition on the phone called data. Data is part of userdata partition.

The commands are:
fastboot erase userdata
fastboot flash userdata userdata.img
The img file has to be extracted from the mmb29s zip file.

Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.

GTCG said:
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
Click to expand...
Click to collapse
Ok, I got it working again. Back on stock rom atm. Thanks for help everyone!

xt1080 write protected?

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.

How to fix "Critical partition flashing is not allowed" In Fastboot

Hello Friends! I'm Getting This Error While I'm Trying To Flash Stock Rom In Lenovo TB-8704X.
{
"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"
}
<!-----The Error Msg Start-----!>
Sending 'tz' (1519 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'sbl1' (378 KB) OKAY [ 0.039s]
Writing 'sbl1' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'rpm' (170 KB) OKAY [ 0.037s]
Writing 'rpm' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'aboot' (605 KB) OKAY [ 0.047s]
Writing 'aboot' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'devcfg' (38 KB) OKAY [ 0.037s]
Writing 'devcfg' OKAY [ 0.020s]
Finished. Total time: 0.111s
Sending 'keymaster' (220 KB) OKAY [ 0.026s]
Writing 'keymaster' OKAY [ 0.005s]
Finished. Total time: 0.160s
Sending 'cmnlib' (200 KB) OKAY [ 0.037s]
Writing 'cmnlib' OKAY [ 0.012s]
Finished. Total time: 0.122s
Sending 'cmnlib64' (254 KB) OKAY [ 0.036s]
Writing 'cmnlib64' OKAY [ 0.017s]
Finished. Total time: 0.110s
Sending 'tzbak' (1519 KB) OKAY [ 0.077s]
Writing 'tzbak' OKAY [ 0.013s]
Finished. Total time: 0.159s
Sending 'sbl1bak' (378 KB) OKAY [ 0.047s]
Writing 'sbl1bak' OKAY [ 0.016s]
Finished. Total time: 0.123s
Sending 'rpmbak' (170 KB) OKAY [ 0.036s]
Writing 'rpmbak' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'abootbak' (605 KB) OKAY [ 0.047s]
Writing 'abootbak' OKAY [ 0.018s]
Finished. Total time: 0.126s
Sending 'devcfgbak' (38 KB) OKAY [ 0.037s]
Writing 'devcfgbak' OKAY [ 0.010s]
Finished. Total time: 0.123s
Sending 'keymasterbak' (220 KB) OKAY [ 0.031s]
Writing 'keymasterbak' OKAY [ 0.009s]
Finished. Total time: 0.112s
Sending 'cmnlibbak' (200 KB) OKAY [ 0.036s]
Writing 'cmnlibbak' OKAY [ 0.005s]
Finished. Total time: 0.117s
Sending 'cmnlib64bak' (254 KB) OKAY [ 0.027s]
Writing 'cmnlib64bak' OKAY [ 0.011s]
Finished. Total time: 0.122s
Erasing 'boot' OKAY [ 0.027s]
Finished. Total time: 0.055s
Sending 'modem' (86016 KB) OKAY [ 3.267s]
Writing 'modem' OKAY [ 0.399s]
Finished. Total time: 3.836s
fastboot: error: cannot load 'system.img': No such file or directory
Sending 'cache' (6248 KB) OKAY [ 0.249s]
Writing 'cache' OKAY [ 0.040s]
Finished. Total time: 0.479s
fastboot: error: cannot load 'userdata.img': No such file or directory
Sending 'recovery' (16587 KB) OKAY [ 0.699s]
Writing 'recovery' OKAY [ 0.079s]
Finished. Total time: 0.896s
Sending 'dsp' (16384 KB) OKAY [ 0.641s]
Writing 'dsp' OKAY [ 0.085s]
Finished. Total time: 0.816s
Sending 'mdtp' (17390 KB) OKAY [ 0.724s]
Writing 'mdtp' OKAY [ 0.093s]
Finished. Total time: 0.919s
Erasing 'splash' OKAY [ 0.025s]
Finished. Total time: 0.057s
Sending 'splash' (313 KB) OKAY [ 0.047s]
Writing 'splash' OKAY [ 0.009s]
Finished. Total time: 0.182s
Erasing 'DDR' OKAY [ 0.018s]
Finished. Total time: 0.045s
Sending 'boot' (11741 KB) OKAY [ 0.366s]
Writing 'boot' OKAY [ 0.053s]
Finished. Total time: 0.723s
Rebooting OKAY [ 0.008s]
Finished. Total time: 0.023s
Press any key to continue . . .
<!-----Error Msg End-----!>
And One MOre Thing! In The Stock Rom, There Is system.img and userdata.img Files Are Missing.
I Have Downloaded Stock Rom From Many Popular Sites, But Those Files Are Missing Also There.
...
Then I Have Tryed To Flash With QFIL
But I Got These Error Here:
Can Any One Please Help Me About This? I Don't Have Any Recovery In This Devices. So I Have To Do This With PC.
Pls If U or Your Any Friend Know a Solution About This Then Tell ME PLS
<!-----More Attachment-----!>

Unlock Critical partitions by means of Fastboot then retry.

jwoegerbauer said:
Unlock Critical partitions by means of Fastboot then retry.
Click to expand...
Click to collapse
So How Can I Unlock It?

Code:
fastboot flashing unlock_critical

jwoegerbauer said:
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks A Lot. But There Is system.img and userdata.img File are Missing. Can U Please Help Me?

Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.

jwoegerbauer said:
Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.
Click to expand...
Click to collapse
No, I Don't think soo. I Have Downloaded Rom From Many Popular Site. But There's Also these files are missing. And In the QcomDloader Tool, When I Try to flash. It Says, "Cannot Read Rawprogram.xml" file

Well, you have a contrary opinion ...

If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.

tek3195 said:
If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.
Click to expand...
Click to collapse
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.

[email protected] said:
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.
Click to expand...
Click to collapse
ok, you are looking at the diff between using raw and sparse images. When you ask how to with QFIL/QcomDloader/Fastboot Mode you can't use them the same way. QFIL and the double handful of Qualcomm flashing utilities like it don't use fastboot, they use sahara. They are different protocols dealing with different formats. I linked a short tutorial to point you in the right direction, maybe, or I hope so anyway. tutorial

fastboot error no such file

im getting this error when im flashing an image
{
"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"
}

MehmetCanWT said:
im getting this error when im flashing an image
View attachment 5694307
Click to expand...
Click to collapse
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.

ipdev said:
Newer devices have two modes for fastboot commands.
bootloader (fastboot).fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
Click to expand...
Click to collapse
i have fastbootd and bootloader
my phone is trident a24

im flashing image on fastbootd

If you still get the error in fastbootd, then..
- Try a different usb cable or port.
- Make sure to use a USB-2 port on the computer.
Known issues using a USB-3 or USB-C port for flashing devices.
- Incompatible version of fastboot.
- Incompatible image file format or corrupted image file.
Newer versions of fastboot should detect the active slot.
Some older devices (and older fastboot), you have to call the slot you want to flash.
fastboot flash flash system_a legion.img
fastboot system_b legion.img
--
I looked up the trident a24, nice looking phone.
Released with Android 10 (?), it should be a slot device.
I could not find out if it was a normal A/B device or one of the odd few A-Olny slot devices.
You can find the current (active) slot.
fastboot getvar current-slot
You can set the active slot.
fastboot set_active a
fastboot set_active b
Cheers.
PS.
When I updated my main computer, I only have USB-C ports on new computer.
I use a cheap USB-C hub that includes a USB-2 port and do all my flashing using it.

i just waited a night and problem solved thanks to all

Database Info

welcome