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
Related
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"
Today I tried to install lineageOS on my Oneplus nord, without succeeding. In addition to failing, I caused some problems.
What I did
1: fastboot flashing unlock
2 twrp: https://forum.xda-developers.com/t/...ficial-twrp-for-oneplus-nord-testing.4142149/
3: i tried to install the official lineage os without succeeding. to try to succeed i reset the phone from twrp, but nothing. it gives errors
4: rebooting, the phone no longer has a room and starts twrp. doing several tests I lock and unlock the device.
5: then i tried to reinstall oxugenOS with twrp, but nothing it gives the same errors as when i tried with lineage os
6: i tried and install oxugenOS like this (with ubuntu) https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/ but it gives the following errors:
Spoiler
Sending 'boot_b' (98304 KB) OKAY [ 2.920s]
Writing 'boot_b' OKAY [ 0.473s]
Finished. Total time: 3.466s
Sending 'dtbo' (8192 KB) OKAY [ 0.233s]
Writing 'dtbo' OKAY [ 0.025s]
Finished. Total time: 0.276s
Sending 'modem_b' (153804 KB) OKAY [ 4.486s]
Writing 'modem_b' OKAY [ 0.724s]
Finished. Total time: 5.263s
Sending 'recovery' (102400 KB) OKAY [ 2.977s]
Writing 'recovery' OKAY [ 0.540s]
Finished. Total time: 3.588s
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.012s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 7.838s
< waiting for any device >
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.016s]
Finished. Total time: 0.079s
Sending 'aop_b' (192 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.006s]
Finished. Total time: 0.016s
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.004s]
Finished. Total time: 0.009s
Sending 'dsp_b' (65536 KB) OKAY [ 1.914s]
Writing 'dsp_b' OKAY [ 0.399s]
Finished. Total time: 2.355s
Sending 'featenabler_b' (88 KB) OKAY [ 0.004s]
Writing 'featenabler_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
Sending 'hyp_b' (404 KB) OKAY [ 0.012s]
Writing 'hyp_b' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'imagefv_b' (524 KB) OKAY [ 0.018s]
Writing 'imagefv_b' OKAY [ 0.007s]
Finished. Total time: 0.028s
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending 'logo_b' (6532 KB) OKAY [ 0.188s]
Writing 'logo_b' OKAY [ 0.060s]
Finished. Total time: 0.258s
Sending 'oem_stanvbk' (2108 KB) OKAY [ 0.060s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.083s
Sending 'odm' (916 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.011s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz_b' (3104 KB) OKAY [ 0.096s]
Writing 'tz_b' OKAY [ 0.024s]
Finished. Total time: 0.126s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
Sending 'xbl_b' (3256 KB) OKAY [ 0.098s]
Writing 'xbl_b' OKAY [ 0.067s]
Finished. Total time: 0.171s
Sending 'xbl_config_b' (80 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.008s]
Finished. Total time: 0.014s
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (523157 KB) OKAY [ 16.625s]
Writing 'system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (519986 KB) OKAY [ 16.454s]
Writing 'vendor' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/3 (523058 KB) OKAY [ 16.814s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.051s
in a nutshell it can't read the partition: odm, system, vendor, product
Someone help me i dont know what to do.
It seems you fixed it yourself trying using the unbrick tool, congratulations
solved: https://forum.xda-developers.com/t/...vice-to-oxygenos.4148415/page-4#post-85282065
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
Hello, Im relatively new to this kinda things, but i wanted to flash my Moto g8 plus to run LineageOS. saddly I have not gotten it to work, and now I want to reflash it with the original rom. I got the needed files, but now It won't flash anything.
My device is shown by fastboot.
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot devices
ZY227BZ9Q8 fastboot
here for example Im trying to flash the bootloader, I get the same error for anything that I try to flash
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
Does Anybody has a good Idea what I can do next?
Its the next day and for no reason flashing works again, but I think it doesnt work completly because I dont have the Right image
[email protected]:~/Android/Sdk/platform-tools$ ./flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.005s]
Finished. Total time: 0.005s
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.343s]
Finished. Total time: 0.345s
Sending 'bootloader' (14204 KB) OKAY [ 0.362s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 1 vs 15
OKAY [ 0.009s]
Finished. Total time: 0.010s
Sending 'modem_a' (81040 KB) OKAY [ 1.955s]
Writing 'modem_a' OKAY [ 0.349s]
Finished. Total time: 2.305s
Sending 'fsg_a' (10936 KB) OKAY [ 0.264s]
Writing 'fsg_a' OKAY [ 0.105s]
Finished. Total time: 0.370s
Sending 'bluetooth_a' (744 KB) OKAY [ 0.019s]
Writing 'bluetooth_a' OKAY [ 0.056s]
Finished. Total time: 0.075s
Sending 'dsp_a' (32768 KB) OKAY [ 0.792s]
Writing 'dsp_a' OKAY [ 0.174s]
Finished. Total time: 0.967s
Sending 'logo_a' (2864 KB) OKAY [ 0.070s]
Writing 'logo_a' OKAY [ 0.052s]
Finished. Total time: 0.122s
Sending 'boot_a' (65536 KB) OKAY [ 1.585s]
Writing 'boot_a' OKAY [ 0.769s]
Finished. Total time: 2.387s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.197s]
Writing 'dtbo_a' OKAY [ 0.097s]
Finished. Total time: 0.295s
Sending 'system_a' (524284 KB) OKAY [ 12.641s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 12.642s
Sending 'system_a' (524284 KB) OKAY [ 12.689s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 15.106s
Sending 'system_a' (524284 KB) OKAY [ 12.664s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 14.815s
Sending 'system_a' (489100 KB) OKAY [ 11.837s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 13.967s
Sending 'system_a' (522304 KB) OKAY [ 12.571s]
Writing 'system_a' OKAY [ 0.002s]
Finished. Total time: 14.566s
Sending 'system_b' (524284 KB) OKAY [ 12.636s]
Writing 'system_b' OKAY [ 0.001s]
Finished. Total time: 14.795s
Sending 'system_b' (95452 KB) OKAY [ 2.302s]
Writing 'system_b' OKAY [ 0.002s]
Finished. Total time: 4.617s
Sending 'oem_a' (11940 KB) OKAY [ 0.291s]
Writing 'oem_a' (bootloader) WARNING: oem_a anti rollback downgrade, 1 vs 15
(bootloader) WARNING: oem_a anti rollback downgrade, 1 vs 15
OKAY [ 0.099s]
Finished. Total time: 0.802s
Sending 'oem_b' (7504 KB) OKAY [ 0.181s]
Writing 'oem_b' (bootloader) WARNING: oem_b anti rollback downgrade, 1 vs 15
(bootloader) WARNING: oem_b anti rollback downgrade, 1 vs 15
OKAY [ 0.112s]
Finished. Total time: 0.294s
Sending 'vendor_a' (461332 KB) OKAY [ 12.436s]
Writing 'vendor_a' OKAY [ 2.036s]
Finished. Total time: 14.479s
Erasing 'modemst1' OKAY [ 0.040s]
Finished. Total time: 0.040s
Erasing 'modemst2' OKAY [ 0.040s]
Finished. Total time: 0.040s
Erasing 'carrier' OKAY [ 0.041s]
Finished. Total time: 0.041s
Erasing 'userdata' OKAY [ 0.084s]
Finished. Total time: 0.085s
Erasing 'ddr' OKAY [ 0.044s]
Finished. Total time: 0.044s
Sending 'fsg_a' (10936 KB) OKAY [ 0.267s]
Writing 'fsg_a' OKAY [ 0.099s]
Finished. Total time: 0.367s
Sending 'bluetooth_a' (744 KB) OKAY [ 0.019s]
Writing 'bluetooth_a' OKAY [ 0.072s]
Finished. Total time: 0.091s
OKAY [ 0.002s]
Finished. Total time: 0.002s
Ok flashed another image, and got nor errors this time, but sadly it will only show the battery loading screen
My Phone was just lying around and randomly is Trying to boot
it works!-
It's almost done...
D!OS is rolling out the next Days. It's pretty basic for now. Based on latest Android 12.1/12L with Google Apps.
If You want to be one of the first who uses this new Xperia exclusive OS, leave a Comment and become a Tester!
Need Testers for J9110 Xperia 1 Dual Sim
J8110 Xperia 1 Single Sim Builds will come later. But feel free to try out the Xperia 1 Dual Sim Variant...
I'm in!
mikaelgr717 said:
I'm in!
Click to expand...
Click to collapse
Great. You can grab the Zip from here once it's uploaded:
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
Just extract the Zip to Your Fastboot Folder and double click the AOSXP Flash .bat File
Download and extract the Xperia Software Binaries from Sony to the same folder
Rename the Image to oem.img and run the OEM Flash .bat File to flash the Binaries
Done. You can access the Recovery by holding Volume down while turning on the Device. In case You want to wipe or so...
Please leave Feedback here once You tried it
I give it a try.
(J9110)
It's up. Camera may not work and same for Mobile Data but thats due to the SODP and should be fixed soon...
And thanks for Your Interest Folks! Really looking forward to let AOSXP grow as owner of Dev Ice Technologies (The Company behind it). Be prepared for awesome Things!
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
xpt1 said:
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
Click to expand...
Click to collapse
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Miustone said:
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Click to expand...
Click to collapse
yes it stop at the sony logo.
xpt1 said:
yes it stop at the sony logo.
Click to expand...
Click to collapse
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Miustone said:
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Click to expand...
Click to collapse
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
xpt1 said:
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
Click to expand...
Click to collapse
{
"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"
}
No, but work is going on. 10 Hours+ each day
Any news about AOSXP for now?
Miustone said:
伟大的。上传后，您可以从此处获取 Zip：
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
只需将 Zip 解压缩到您的 Fastboot 文件夹，然后双击 AOSXP Flash .bat 文件
从 Sony 下载 Xperia 软件二进制文件并将其解压缩到同一文件夹
将映像重命名为 oem.img 并运行 OEM Flash .bat 文件以刷新二进制文件
完毕。您可以通过在打开设备时按住音量来访问恢复。万一你想擦什么……
尝试后请在此处留下反馈
Click to expand...
Click to collapse
惯于
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Miustone said:
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Click to expand...
Click to collapse
Can you also insert the sony camera apk, I need the dedicated button, the button unfortunately does not work with gcam
D!OS_J9110.zip tested right now, still stuck on sony logo.
xpt1 said:
D!OS_J9110.zip tested right now, still stuck on sony logo.
Click to expand...
Click to collapse
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
my latest android stock: J9110_Customized EU_55.2.A.4.332-R10C
oem: SW_binaries_for_Xperia_Android_12_4.19_v1c_kumano.img ( renamed to oem.img )
i will flash one more time an copy the script.
D!OS installation started...
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.188s]
Writing 'dtbo_a' OKAY [ 0.031s]
Finished. Total time: 0.266s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.203s]
Writing 'dtbo_b' OKAY [ 0.047s]
Finished. Total time: 0.297s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta_a' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta_b' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'boot_a' (65536 KB) OKAY [ 1.515s]
Writing 'boot_a' OKAY [ 0.266s]
Finished. Total time: 2.203s
Sending 'boot_b' (65536 KB) OKAY [ 1.531s]
Writing 'boot_b' OKAY [ 0.251s]
Finished. Total time: 2.235s
Sending 'vendor_a' (117496 KB) OKAY [ 2.745s]
Writing 'vendor_a' OKAY [ 0.000s]
Finished. Total time: 2.776s
Sending 'vendor_b' (117496 KB) OKAY [ 2.777s]
Writing 'vendor_b' OKAY [ 0.000s]
Finished. Total time: 4.104s
Sending sparse 'system_a' 1/5 (775200 KB) OKAY [ 18.492s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (774120 KB) OKAY [ 18.532s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (774120 KB) OKAY [ 18.708s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (774120 KB) OKAY [ 18.525s]
Writing 'system_a' OKAY [ 0.016s]
Sending sparse 'system_a' 5/5 (566052 KB) OKAY [ 13.684s]
Writing 'system_a' OKAY [ 0.000s]
Finished. Total time: 89.373s
Sending sparse 'system_b' 1/5 (775200 KB) OKAY [ 18.204s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/5 (774120 KB) OKAY [ 18.467s]
Writing 'system_b' OKAY [ 0.016s]
Sending sparse 'system_b' 3/5 (774120 KB) OKAY [ 18.560s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 4/5 (774120 KB) OKAY [ 18.448s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 5/5 (566052 KB) OKAY [ 13.607s]
Writing 'system_b' OKAY [ 0.000s]
Finished. Total time: 94.854s
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Finished. Total time: 7.708s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D!OS installed. Press any Key to exit...
XPERIA OEM installation started...
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.005s
Sending 'oem_a' (279196 KB) OKAY [ 7.131s]
Writing 'oem_a' OKAY [ 13.073s]
Finished. Total time: 20.283s
Sending 'oem_b' (279196 KB) OKAY [ 6.522s]
Writing 'oem_b' OKAY [ 13.005s]
Finished. Total time: 19.558s
Erasing 'userdata' OKAY [ 76.212s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 28074734 4k blocks and 7020544 inodes
Filesystem UUID: b91d1bf4-c4b1-11ec-a85f-5f6820032de7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition
')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
XPERIA OEM installed. Press any Key to exit...