I tried rooting my phone now it will not get pass the loading screen. I tried to flash the stock ruu but I get errors
I have pictures but not aloud to post yet. But on my phone it says
Software status modified
Unlocked
S-on
.
When I try to flash the ruu zip I get
C:\Users\KJ\Desktop\platform-tools>fastboot flash zip rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
OKAY [ 1.065s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_q
(bootloader) LrXHZ
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.142s
Bump
Hi,
I am trying to revive my Asus and running into following problem. I read multiple threads and forums and have executed multiple commands in cmd fastboot. Getting following errors:
First I was running into error that "vrl needs to be flashed" which I found a correct (I hope) file and flashed the vrl, and then flashed CM13 or stock ROM from Asus website. Which fastboot returns with "OKAY flashed partition system. Time 28 seconds" Still wont boot and stuck on boot logo.
C:\adb>fastboot devices
G5NPFP026657RFA fastboot
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.031s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.448s]
writing 'system'...
(bootloader) Flashing partition: system
FAILED (remote: VRL need to be flashed!)
finished. total time: 28.511s
C:\adb>fastboot flash vrl vrl2.bin
(bootloader) vrl partition type: raw
target reported max download size of 1019215872 bytes
sending 'vrl' (128 KB)...
(bootloader) Ready to receive: 0x00020000 size of data
OKAY [ 0.016s]
writing 'vrl'...
(bootloader) Flashing partition: vrl
OKAY [ 0.078s]
finished. total time: 0.094s
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.047s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.424s]
writing 'system'...
(bootloader) Flashing partition: system
OKAY [ 0.031s]
finished. total time: 28.518s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Any of the senior members or other who have more knowledge, please shade some light here and tell me what am I doing wrong??
I also get below error at times, and my computer gets stuck every time I execute below command and it takes forever for it to get back to working by itself unless I try to close the application.
C:\adb>fastboot update system "C:\adb\UL-P023-WW-4.7.3.0-user.zip"
W/ ( 448): Unable to open 'system': No such file or directory
error: failed to open zip file 'system': I/O Error
C:\adb>fastboot flash system UL-P023-WW-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 175719111 is not a multiple of t
he block size 4096
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 1.102s
Very much keen to read some good replies. Thanks in advance guys.
Hey Guys,
i'm having a big Problem. I hard bricked a OP x.
I think there is a problem with the partitions.
I can flash recoverys. I can't flash or wipe anything in TWRP because "Failed to mount '/system' (invalid argument)".
And flashing stock OOS via fastboot is not working too.
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' 1/2 (524284 KB)...
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
OKAY [ 16.890s]
writing 'system' 1/2...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 23.014s
Any way to get it working again?
cat /proc/partitions
echoes an empty list :/
=> Mega Unbrick Guide
So, I tried to flash a GSI on my Treble Compatible Wiko Lenny 5, I checked with the app and I have A only.
So I downloaded the A Only ARM 64 IMG and I can't flash it.
It says:
$ fastboot flash system PixelExperienceP-a64-aonly.img
target reported max download size of 134217728 bytes
erasing 'system'...
OKAY [ 0.017s]
sending sparse 'system' 1/13 (131068 KB)...
OKAY [ 4.908s]
writing 'system' 1/13...
FAILED (remote: sparse image size span overflow.)
finished. total time: 4.929s
What can I do? I even tried -S (AMOUNT OF KB/MB) but nothing! :crying:
Hope someone can help.
Hi. I had the same issue about 3 days ago. I have not yet figured a way to flash the GSI rom yet. But I was able to get my phone working again.
What I did was to
1. Download my phone's stock rom
2. Extract the system.img
3. Flash it using adb.
As for your personal files, unless you've already backed them up, I don think there is a way to get them back.
Hope I was of enough help
Hi all, i wanted to remove my RR Rom, which was draining a lot battery.
But when i downloaded a new rom (Paranoid Android) and followed the fastboot commands i encounted an error.
7T PRO\payload_dumper-win64\payload_output> fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
So i tried to revert back to stock with this tutorial ( https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 )
But now i am getting these errors:
error: failed to load 'images.zip': No such file or directory
Press any key to exit...
But the images.zip is there , i can see it.
Also when i try other flash ables .bat files:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.224s]
writing 'userdata'...
OKAY [ 0.003s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 7.236s
error: cannot load 'aop.img'
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'dsp.img'
error: cannot load 'dtbo.img'
error: cannot load 'dtbo.img'
error: cannot load 'modem.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'storsec.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'system.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'system.img'
error: cannot load 'vbmeta.img'
error: cannot load 'vbmeta.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'vendor.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'vendor.img'
error: cannot load 'LOGO.img'
error: cannot load 'LOGO.img'
Press any key to continue . . .
I also tried to install TRWP and go from there, but then i get this error:
PS C:\Users\Raseven\Desktop\7T PRO> fastboot flash recovery_a twrp.img
target reported max download size of 805306368 bytes
sending 'recovery_a' (41796 KB)...
OKAY [ 0.899s]
writing 'recovery_a'...
OKAY [ 0.169s]
finished. total time: 1.073s
PS C:\Users\Raseven\Desktop\7T PRO> fastboot flash recovery_b twrp.img
target reported max download size of 805306368 bytes
sending 'recovery_b' (41796 KB)...
OKAY [ 0.900s]
writing 'recovery_b'...
OKAY [ 0.135s]
finished. total time: 1.039s
PS C:\Users\Raseven\Desktop\7T PRO> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.900s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.928s
PS C:\Users\Raseven\Desktop\7T PRO>
Is my phone bricked or ??
From OB8-OnePlus7ProOxygen_13.W.21_OTA_021_all_1912261255_76782007d7dbec-FASTBOOT i tried flash-all bat file :
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: bf29c267
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'b' OKAY [ 0.003s]
extracting boot.img (96 MB) to disk... took 0.273s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.154s]
Writing 'boot_b' OKAY [ 0.372s]
extracting dtbo.img (16 MB) to disk... took 0.042s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.366s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.197s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.203s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
And another:
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.292s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.043s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk... took 13.269s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 3.842s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 7645ccf6-e8b0-11ea-a92e-2fe9f70f7b34
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 (262144 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: bf29c267
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 2.129s]
writing 'boot_b'...
OKAY [ 0.317s]
sending 'dtbo' (16384 KB)...
OKAY [ 0.361s]
writing 'dtbo'...
OKAY [ 0.069s]
sending sparse 'system' 1/5 (779514 KB)...
Ok i seemed to have fixed it, using the MSM Tool So admin u can lock this.