Database Info

[Q] Universal Linux Toolkit v2.1.0 error

hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia

Can not flash anythink

Hi. I have a OPO that i cant flash or erase anything.
It`s encrypted and what i boot OS it`s asks for a code and it doesn`t meter which one i will write. The phone says:
View attachment 3283408
When i press on Reset Phone - nothing hepends.
Rebooting to recovery (The ColorOS recovery V1.2) and Wipe data and cache does nothing.
Flashing custom recovery or erasing user-data whiting fast-boot falls (with locked and unlocked boot-loader) s:
target reported max download size of 1073741824 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.844s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.893s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.066s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.000s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.037s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.016s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.057s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'tz' (283 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.366s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.019s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 8feeb7e6
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5606 KB)...
OKAY [ 0.188s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.257s
Press any key to exit...
Even flashing with MSM8974DownloadTool falls - only 8974_msimage.mbn flashes and phone power offs by it self.
Tried to temporary boot custom recovery and wipe anything - no lack.
Please help

Partition error, Help me please (OnePlus North)

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

stucked while flashing Pixel 5 - SPB3 - Android 12 Beta 3 for OnePlus 8 Series using video of TechiBee

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

Tryed Flashing, no Nothing works. nee Help

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!-