Database Info

[Q] corrupt cache, can't format ext4

Last Friday I tried to flash android 5 lolipop to my Nexus 5. It froze in the erasing part.
Eventualy switched the phone off and on. There was a loop where you could only see the droid, even in recovery mode.
I got around that loop by flashing TWRP to the recovery partition.
Al recovery ROM's however all state that they can't mount /cache.
I formatted the hell out of it but sadly it didn't solve the problem.
So using adb shell I removed the cache partition, recreated it and formatted it.
So here is my partition table:
Code:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 15.8GB 13.7GB ext4 userdata
29 15.8GB 15.8GB 5632B grow
Notice the missing ext4 for partition 27. After deleting and recreating the partition I formatted it with the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
this resulted in:
Code:
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
44832 inodes, 179200 blocks
8960 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
So at this point I wanted to check the my partition table again, but this time i got an error message:
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
Mounting results in:
Code:
mount /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: Invalid argument
Did I make any mistakes here? I did not rooted the phone (yet). Is this necessary?
The re partitioning part comes from a guide here originally for the kindle.
Current status is that I re flashed stock droid 4.4.4. It starts, but all Google applications crash and I have no cellular network .
Guess they all depend on the cache directory.
Any help on making the cache partition work again would be much appreciated!

Oh jeez. I guess by now you know what you've done wrong. In case you don't, you should have just flashed the stock cache.img via fastboot as the very first step.
When you say you flashed stock, how?
What is the output of fastboot flash cache cache.img?
Sent from my Nexus 5 using Tapatalk

My bad! I should have mentioned that I had tried all the basic steps.
So I flashed the original cache.img many times. Because some say it takes more then 1 try to fix a corrupt cache.
Also tried a manual erase and a format of the cache partition.
Flashing the cache is somewhat strange, I have 2 variants. One is done in a heartbeat saying everything went well:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.511s]
sending 'cache' (13348 KB)...
OKAY [ 0.627s]
writing 'cache'...
OKAY [ 1.026s]
finished. total time: 2.169s
And then if I run it again it gets stuck at erasing:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
I once left it overnight but the following morning it was still erasing...
All the time the result is the same. A phone with crashing apps and no cellular network.
To answer your other question. I used fastboot to do a flash-all from the stock image from Google (image-hammerhead-ktu84p (4.4.4)).
Also did the manual version where I manual erase the partitions and flash them.
After this I get a working 4.4.4 with the exception that all Google apps crash (including Play etc, so the basic needs) and I have no cellular network.
Resulting in a useless phone.

The first output looks normal. Try and get it to that stage again so there is a successful flash, then try And fix persist partition as that has similar symptoms. Guide linked in my signature
Sent from my Nexus 5 using Tapatalk

Thank you so much for your reply.
I followed this guide.
The repair did nothing so I entered:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Since my dev/block/platform/msm_sdcc.1/by-name directory was empty is also did that same command for the cache:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
initially that looked like a good thing. The mounting error's where gone after i rebooted the phone.
But things took a turn for the worst. Where before i had a 50% chance on failing to erase the cache. I now have gained a 50% chance to fail at the writing stage.
Resulting in the device not being flash-able because there is more than one part that needs to be flashed.
Also, Philz is not usable. Although flashing states successful, It just won't boot into it. TWRP is the only thing that still works.
Did I do this myself by creating that cache bit? Or is corruption more likely?

Its hard to say. But I think it needs a professional repair now.
Sent from my Nexus 5 using Tapatalk

I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.

Dujinga said:
I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.
Click to expand...
Click to collapse
It cannot break things further. Have you tried dd zero out cache? If there is an I/O problem then that most certainly will break the dd command. You can also try to read back the cache partition with dd command to /data or to / if have enough space on / to confirm there are no I/O errors. If you havent find any I/O errors then I can imagine two things. Something got messed up in the gpt partition or the mmc is fauilty.

I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Sent from my Nexus 5 using Tapatalk

Thank you for your reply. But running this command wil be a problem as it requiers Philz and ADB.
I can still flash Philz in the recovery, but it won't boot into the recovey afterwards
Guys, I want to thank you for all the help, but I'm giving up.
Gonna contact the supplier with the question how to resolve this issue.

Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
rootSU said:
Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Pretty sure "FAILED (remote: flash write failure)" error means that the emmc is hosed.
It's best you claim warranty/insurance.
-Sent from a Lollipop'd Hammerhead!

Ok, so I flashed Philz again (btw TWRP always kept working but that one has a strange shell (limited)).
This time instead of booting straight into recovery after I flashed it, I turned it off and on again.
Now I could get into Philz.
So I ran:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Expecting it to fail, but this was the result:
Code:
dd: writing '/dev/block/mmcblk0p27': No space left on device
1433601+0 records in
1433600+0 records out
734003200 bytes (700.0MB) copied, 41.996465 seconds, 16.7MB/s
That seems OK to me
So I'm going to try a bit more. I already openend a case with the reseller though.
One way or another this will get resolved

I didn't see that error. Yes, hosed.
Sent from my Nexus 5 using Tapatalk

The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh

Dujinga said:
The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh
Click to expand...
Click to collapse
It's a wild goose chase mate. Do you even know what the error stands for? "Flash write failure" means the emmc is toast and hence nothing can be written on it. It's kinda become read only now. Even if the flash is successful, a quick reboot will roll everything back.
It's best you take it up with your seller and claim warranty. There;s nothing you can do.
Good luck!

I got the return instructions. Gonna mail it tommorow.
Once again a huge thanks to all of you guys. :good:

Strangely soft-bricked stock Moto G

Hi there, i have spent hours trying to recover my Moto G XT1032 using this forum and I have mad progress but my phone is still dead.
Phone:
Motorola XT1032 - it was the latest stock ROM, always updated to the newest version. (Very probably a non-branded EU retail, 5.1 ROM)
Problem:
Battery got drained. When put on charger, it was 'optimising cache app x of y' for a long time, sometimes it does this anyway.
Then it went into bootloop, stuck at the Motorola logo. It doesn't restart and the logo doesn't starts animating like it normally does.
Fastboot (Power + vol down) worked, but going into recovery failed, leaving me stuck with the same M logo.
Solutions tried:
1. Connection to computer: didn't work. Seen as 'fastboot device' when in fastboot but that's it.
2. Using Android recovery software. Useless because of the above and useless pieces of software anyway.
3. Re-flashing stock ROM. After installing Motorola drivers and mfastboot, I tried to flash FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC, and according to the phone it was successful, but it still left me stuck at the bootloop. Even after manually flashing everything from partition tables to system images.
4. I unlocked the phone to install a custom TWRP recovery. The unlock was successful.
5. Tried to install TWRP recovery - to recover my files at least -, the command line says success, the phone says
Code:
Mismatched partition size (recovery)
Many have said in this forum to ignore this message - well, I can't since it can't write the recovery partition.
6. At this point the factory recovery started working ('no command' screen, then pressing 'vol up + power')
7. I have been able to boot into TWRP with
Code:
mfastboot boot twrp-3.0.0.0_2-falcon.img
What a workaround! Well, I have at least been able to access my files over MTP. Yay! :fingers-crossed:
8. Here comes the problem: I can't wipe the device. I can't copy anything over MTP. I can't delete files over mtp: it looks like the files are deleted but they reappear after restarting the device.
Note: I can access a simple
Code:
adb shell
in recovery.
So once again, I'm unable to install a custom recovery via mfastboot, and it looks like the whole device was write-protected for whatever reason. At least I've been able to save my data thanks to the useful resources here! Any ideas about what else I could possibly try?
Any help is much appreciated!

Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy

Paradox♀ said:
Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy
Click to expand...
Click to collapse
Thanks!
It erased everything OK, at least no error messages.
Fun fact: it still boots into factory recovery after erasing the recovery partition!
Fun fact 2: I still can't flash custom recoveries like TWRP. ('Partition mismatch' error and then boots into factory recovery as if nothing changed. If I manually 'mfastboot boot twrp....img' into the image, then the internal storage shows up intact as before the phone was broken!
Then I flashed new stock ROMs, all returned OK, but still bootloop:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Here's the complete output:
Code:
D:\tmp>mfastboot erase system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.023s]
finished. total time: 0.025s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.018s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.026s]
finished. total time: 0.028s
D:\tmp>mfastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.037s]
finished. total time: 0.037s
D:\tmp>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.303s]
finished. total time: 0.330s
D:\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.930s]
finished. total time: 1.018s
D:\tmp>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.036s]
finished. total time: 0.095s
D:\tmp>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.585s]
finished. total time: 0.948s
D:\tmp>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.363s]
writing 'recovery'...
OKAY [ 0.591s]
finished. total time: 0.958s
D:\tmp>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.153s]
writing 'system'...
OKAY [ 7.753s]
finished. total time: 15.907s
D:\tmp>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256953 KB)...
OKAY [ 8.132s]
writing 'system'...
OKAY [ 7.910s]
finished. total time: 16.044s
D:\tmp>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260396 KB)...
OKAY [ 8.234s]
writing 'system'...
OKAY [ 7.899s]
finished. total time: 16.137s
D:\tmp>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166176 KB)...
OKAY [ 5.274s]
writing 'system'...
OKAY [ 6.251s]
finished. total time: 11.528s
D:\tmp>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.599s]
writing 'modem'...
OKAY [ 0.763s]
finished. total time: 2.365s
D:\tmp>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.088s]
writing 'fsg'...
OKAY [ 3.177s]
finished. total time: 3.268s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.017s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.024s
D:\tmp>mfastboot reboot
rebooting...
finished. total time: 0.002s
D:\tmp>
I think I have the same symptoms as this user.
Maybe the file system is corrupted? Or the bootloader?
Or just the flash memory in the phone stopped working properly.
Let's recap:
Erasing partitions doesn't actually erase them but it returns OK
Can't erase userdata
Can't install custom recoveries
Flashing stock ROM returns OK but still can't boot.

I'm pretty sure the eMMC (internal memory chip) has been damaged. Goodbye, phone...
Fortunately I still had my good ol' ZTE Blade sitting in the drawer.

Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.

Paradox♀ said:
Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.
Click to expand...
Click to collapse
tl;dr: can't fsck, can't format, can't mfastboot erase, can't twrp erase.
Thanks! I've tried it, it doesn't work. Looks like it's wiped, then after restart it doesn't.
But doesn't the command you have suggested before
Code:
mfastboot erase userdata
erase the data partition?
I'm concerned that the eMMC is damaged and my phone can't be put to life again - if a complete erase & flash (including partition table, see my previous post) doesn't work then what does?
Here's a df output from TWRP:
Code:
/data # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 435.3M 20.0K 435.3M 0% /dev
tmpfs 435.3M 20.0K 435.3M 0% /tmp
/dev/block/mmcblk0p33
651.7M 11.6M 640.0M 2% /cache
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /data
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /sdcard
/dev/block/mmcblk0p1 62.4M 46.5M 15.9M 75% /firmware
/dev/block/mmcblk0p34
960.6M 938.1M 22.6M 98% /system
Here's a worrisome FSCK output on the data partition:
Code:
/sbin # fsck.f2fs /dev/block/mmcblk0p36
fsck.f2fs /dev/block/mmcblk0p36
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: MKFS version
""
Info: FSCK version
from "Linux version 3.4.42-g89906d6 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Feb 26 06:48:18 CST 2016"
to "Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x31040]
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x315d9]
NID[0x31040] is unreachable
NID[0x315d9] is unreachable
NID[0x315da] is unreachable
NID[0x315e2] is unreachable
NID[0x315e6] is unreachable
NID[0x315ec] is unreachable
NID[0x315ef] is unreachable
NID[0x315f1] is unreachable
NID[0x315f4] is unreachable
NID[0x315f9] is unreachable
NID[0x31600] is unreachable
[FSCK] Unreachable nat entries [Fail] [0xb]
[FSCK] SIT valid block bitmap checking [Fail]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Fail] [0xfd3d3]
[FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x78ea]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x78f5]
[FSCK] valid_inode_count matched with CP [Fail] [0x75ed]
[FSCK] free segment_count matched with CP [Ok..] [0x15a]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Fail]
Error: Could not conduct fsync!!!
Done.
And what happens when I try to format the data partition? This:
Code:
/sbin # mkfs.f2fs /dev/block/mmcblk0p36
mkfs.f2fs /dev/block/mmcblk0p36
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
Error: Could not conduct fsync!!!
Info: format successful
Exact same error as for example here.

Hey is there any chance that you have a backup image that could be used to restore the partitions?

Paradox♀ said:
Hey is there any chance that you have a backup image that could be used to restore the partitions?
Click to expand...
Click to collapse
Well, I don't, but I used stock ROM images from this forum. It's the same stuff that was installed before failure.
If I can't run a simple fsck, then I'm 90% sure it's some hardware issue. Based on how many people are having the same problem, maybe the eMMC chips are reaching the end of their (short) lifetime.

Yeah it seems so.

Huawei mate 9 dump needed

Hello all
Since nobody helped me with my mate 9, which did no sign of life, i started searching...on the mainboard.
I found the tespoint that gave me access to board, loaded fastboot in the ram, and now my MATE 9 shows in the fastboot devices.
This, i think ,is a big step for MATE 9 phones, which we might brick.
OK, so here is what i need. If it work, i promise that in maximum 1 day after testing this, i will post a guide for unbrick.
Code:
C:\Users\MONSTER>fastboot flash boot F:\dload\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16208 KB)...
OKAY [ 0.549s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.680s
This is the error style i got,when flashing boot,recovery,fastboot,and others.
Flashing system,product,vendor,vector, works.
As @Tkkg1994 posted here, https://forum.xda-developers.com/showpost.php?p=70410219&postcount=454
vrl.img really exists (i never heard of,and firstly,i thought that is URL.img ) )and may have something to do with partition table or smth like that.
I would need as many as partitions possible, since i have only those extracted from update.app.
So,please,anyone, if have time,try to help.
PS: @duraaraa - sir, i'm disturbing you again. but again,i think you can help.

What do you need, and how to help you?
Gesendet von meinem MHA-L29 mit Tapatalk

i need those img's
verlist.img
vrl.img
vrl_backup.img
dts.img
dtx.img
version.img
isp_boot.img
patch.img
persist.img
secure_storage.img
splash2.img
But i admit,that i have no idea how to get them from a working phone.Maybe others can help here.
I also have no idea how @Tkkg1994 obtained this partition list.

Hmm, the some are included in update.app , which can be extracted. But this is a basic thing you already know.
Indeed the most are not in updated.app like vrl.img dtx, version, isp, pathch persist etc. Maybe they are temporary build during update process.

well...with those in update.app already tried,they solve nothing,even if flashing is ok.
something is missing...
and btw....who seen before this error?
flash write prim vrl failure

Monster.Kali said:
I would need as many as partitions possible, since i have only those extracted from update.app.
Click to expand...
Click to collapse
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.

user4774 said:
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.
Click to expand...
Click to collapse
well, i don't have that clear understanding. i'm a noob.
imagine that at work, (gsm repair shop)i'm helped by software and hardware tools.
i never did that before,to load something into ram for x reason.
so right now, i try to learn things, and to bring my phone back to life.
what i tried to do,was like that. if i broke internal partitions,that after restart killed my phone, now i'm trying to get them back,maybe they solve something.
in ram, i loaded fastboot image and xloader.
that gave me access to fastboot.
until some clear instructions, i keep trying.

Monster.Kali said:
now i'm trying to get them back,maybe they solve something.
Click to expand...
Click to collapse
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
fastboot (aka bootloader) is the partition /dev/sdd24
Code:
24 151552 154623 12.0M fastboot_a
and the xloader is on a different 4MB "disk" /dev/sda
Code:
# fdisk -l /dev/block/sda
Note: sector size is 4096 (not 512)
Disk /dev/block/sda: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 1 heads, 8 sectors/track
Units: cylinders of 8 * 4096 = 32768 bytes
Disk /dev/block/sda doesn't contain a valid partition table

user4774 said:
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/NEW/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/NEW/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
Click to expand...
Click to collapse
that's good.
it would be easier to do what i want, with cat, as you said.
i would follow partitions profile by tkkg1994, and write them to emmc.
but since i have only fastboot.....

Monster.Kali said:
but since i have only fastboot.....
Click to expand...
Click to collapse
Check which partitions you can extract from the full ROM/UPDATE.APP.
For your reference, my MHAL29C432 has 4 "scsi" disks /dev/sda (4MB xloader), /dev/sdb (4MB unused), /dev/sdc (frp stuff)
Code:
# fdisk -l /dev/block/sdc
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdc: 16384 sectors, 64.0M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2047
Number Start (sector) End (sector) Size Name
1 128 255 512K frp
2 256 767 2048K persist
3 768 2047 5120K reserved1
and /dev/sdd
Code:
# fdisk -l /dev/block/sdd
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdd: 124928000 sectors, 576M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15615999
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
3 384 2559 8704K modem_secure
4 2560 4095 6144K nvme
5 4096 20479 64.0M oeminfo
6 20480 28671 32.0M secure_storage
7 28672 36863 32.0M modem_om
8 36864 37887 4096K modemnvm_factory
9 37888 38911 4096K modemnvm_backup
10 38912 41983 12.0M modemnvm_img
11 41984 43007 4096K modemnvm_system
12 43008 63487 80.0M splash2
13 63488 129023 256M cache
14 129024 129535 2048K bootfail_info
15 129536 130047 2048K misc
16 130048 138239 32.0M reserved2
17 138240 139263 4096K reserved10
18 139264 141311 8192K hisee_fs
19 141312 145407 16.0M dfx
20 145408 149503 16.0M rrecord
21 149504 149567 256K fw_lpm3_a
22 149568 150527 3840K reserved3_a
23 150528 151551 4096K hisee_img_a
24 151552 154623 12.0M fastboot_a
25 154624 155647 4096K vector_a
26 155648 156159 2048K isp_boot_a
27 156160 159743 14.0M isp_firmware_a
28 159744 162815 12.0M fw_hifi_a
29 162816 164863 8192K teeos_a
30 164864 181247 64.0M recovery2_a
31 181248 185343 16.0M sensorhub_a
32 185344 193535 32.0M boot_a
33 193536 209919 64.0M recovery_a
34 209920 214015 16.0M dts_a
35 214016 214527 2048K trustfirmware_a
36 214528 228863 56.0M modem_fw_a
37 228864 241663 50.0M reserved4_a
38 241664 262143 80.0M modemnvm_update_a
39 262144 270335 32.0M patch_a
40 270336 278527 32.0M version_a
41 278528 479231 784M vendor_a
42 479232 528383 192M product_a
43 528384 577535 192M cust_a
44 577536 1777663 4688M system_a
45 1777664 1810431 128M reserved5
46 1810432 15615999 52.6G userdata

ok
got all missing img files from update.app with 7zip, not with update extractor.
on some of them, i have different sizes
here is the log of fastboot.
many of them flashed ok.
some not.
Code:
C:\Users\MONSTER>fastboot flash hisee_fs F:\dload\UPDATE\hisee_fs.img
target reported max download size of 471859200 bytes
sending 'hisee_fs' (8192 KB)...
OKAY [ 0.288s]
writing 'hisee_fs'...
OKAY [ 0.092s]
finished. total time: 0.386s
C:\Users\MONSTER>fastboot flash dfx F:\dload\UPDATE\dfx.img
target reported max download size of 471859200 bytes
sending 'dfx' (16384 KB)...
OKAY [ 0.561s]
writing 'dfx'...
OKAY [ 0.161s]
finished. total time: 0.728s
C:\Users\MONSTER>fastboot flash rrecord F:\dload\UPDATE\rrecord.img
target reported max download size of 471859200 bytes
sending 'rrecord' (16384 KB)...
OKAY [ 0.562s]
writing 'rrecord'...
OKAY [ 0.157s]
finished. total time: 0.725s
C:\Users\MONSTER>fastboot flash fw_lpm3_a F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3_a' (256 KB)...
OKAY [ 0.017s]
writing 'fw_lpm3_a'...
FAILED (remote: image verification error)
finished. total time: 0.061s
C:\Users\MONSTER>fastboot flash fw_lpm3 F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3' (256 KB)...
OKAY [ 0.015s]
writing 'fw_lpm3'...
FAILED (remote: image verification error)
finished. total time: 0.059s
C:\Users\MONSTER>fastboot flash reserved3_a F:\dload\UPDATE\reserved3_a.img
target reported max download size of 471859200 bytes
sending 'reserved3_a' (3840 KB)...
OKAY [ 0.136s]
writing 'reserved3_a'...
OKAY [ 0.056s]
finished. total time: 0.198s
C:\Users\MONSTER>fastboot flash hisee_img_a F:\dload\UPDATE\hisee_img_a.img
target reported max download size of 471859200 bytes
sending 'hisee_img_a' (4096 KB)...
OKAY [ 0.141s]
writing 'hisee_img_a'...
OKAY [ 0.058s]
finished. total time: 0.205s
C:\Users\MONSTER>fastboot flash fastboot_a F:\dload\UPDATE\fastboot_a.img
target reported max download size of 471859200 bytes
sending 'fastboot_a' (12288 KB)...
OKAY [ 0.423s]
writing 'fastboot_a'...
FAILED (remote: image verification error)
finished. total time: 0.466s
C:\Users\MONSTER>fastboot flash vector_a F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector_a' (4096 KB)...
OKAY [ 0.145s]
writing 'vector_a'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash vector F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector' (4096 KB)...
OKAY [ 0.145s]
writing 'vector'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash isp_boot_a F:\dload\UPDATE\isp_boot_a.img
target reported max download size of 471859200 bytes
sending 'isp_boot_a' (2048 KB)...
OKAY [ 0.074s]
writing 'isp_boot_a'...
OKAY [ 0.055s]
finished. total time: 0.135s
C:\Users\MONSTER>fastboot flash isp_firmware_a F:\dload\UPDATE\isp_firmware_a.im
g
target reported max download size of 471859200 bytes
sending 'isp_firmware_a' (14336 KB)...
OKAY [ 0.494s]
writing 'isp_firmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.539s
C:\Users\MONSTER>fastboot flash fw_hifi_a F:\dload\UPDATE\fw_hifi_a.img
target reported max download size of 471859200 bytes
sending 'fw_hifi_a' (12288 KB)...
OKAY [ 0.424s]
writing 'fw_hifi_a'...
FAILED (remote: image verification error)
finished. total time: 0.467s
C:\Users\MONSTER>fastboot flash teeos_a F:\dload\UPDATE\teeos_a.img
target reported max download size of 471859200 bytes
sending 'teeos_a' (8192 KB)...
OKAY [ 0.286s]
writing 'teeos_a'...
FAILED (remote: image verification error)
finished. total time: 0.329s
C:\Users\MONSTER>fastboot flash recovery2_a F:\dload\UPDATE\recovery2_a.img
target reported max download size of 471859200 bytes
sending 'recovery2_a' (65536 KB)...
OKAY [ 2.230s]
writing 'recovery2_a'...
FAILED (remote: image verification error)
finished. total time: 2.273s
C:\Users\MONSTER>fastboot flash dts_a F:\dload\UPDATE\dts_a.img
target reported max download size of 471859200 bytes
sending 'dts_a' (16384 KB)...
OKAY [ 0.562s]
writing 'dts_a'...
FAILED (remote: image verification error)
finished. total time: 0.603s
C:\Users\MONSTER>fastboot flash trustfirmware_a F:\dload\UPDATE\trustfirmware_a.
img
target reported max download size of 471859200 bytes
sending 'trustfirmware_a' (2048 KB)...
OKAY [ 0.077s]
writing 'trustfirmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.123s
C:\Users\MONSTER>fastboot flash modem_fw_a F:\dload\UPDATE\modem_fw_a.img
target reported max download size of 471859200 bytes
sending 'modem_fw_a' (57344 KB)...
OKAY [ 1.943s]
writing 'modem_fw_a'...
FAILED (remote: image verification error)
finished. total time: 1.988s
C:\Users\MONSTER>fastboot flash reserved4_a F:\dload\UPDATE\reserved4_a.img
target reported max download size of 471859200 bytes
sending 'reserved4_a' (51200 KB)...
OKAY [ 1.743s]
writing 'reserved4_a'...
OKAY [ 0.413s]
finished. total time: 2.162s
C:\Users\MONSTER>fastboot flash modemnvm_update_a F:\dload\UPDATE\modemnvm_updat
e_a.img
target reported max download size of 471859200 bytes
sending 'modemnvm_update_a' (81920 KB)...
OKAY [ 2.762s]
writing 'modemnvm_update_a'...
OKAY [ 0.648s]
finished. total time: 3.416s
C:\Users\MONSTER>fastboot flash patch_a F:\dload\UPDATE\patch_a.img
target reported max download size of 471859200 bytes
sending 'patch_a' (32768 KB)...
OKAY [ 1.117s]
writing 'patch_a'...
OKAY [ 0.275s]
finished. total time: 1.398s
C:\Users\MONSTER>fastboot flash version_a F:\dload\UPDATE\version_a.img F:\dload
\UPDATE\version_a.img
target reported max download size of 471859200 bytes
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\MONSTER>fastboot flash vendor_a F:\dload\UPDATE\vendor_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (460726 KB)...
OKAY [ 16.785s]
writing 'vendor_a'...
OKAY [ 4.661s]
sending sparse 'vendor_a' (340470 KB)...
OKAY [ 12.505s]
writing 'vendor_a'...
OKAY [ 3.312s]
finished. total time: 37.272s
C:\Users\MONSTER>fastboot flash product_a F:\dload\UPDATE\product_a.img
target reported max download size of 471859200 bytes
sending 'product_a' (196608 KB)...
OKAY [ 6.675s]
writing 'product_a'...
OKAY [ 1.536s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash cust_a F:\dload\UPDATE\cust_a.img
target reported max download size of 471859200 bytes
sending 'cust_a' (196608 KB)...
OKAY [ 6.705s]
writing 'cust_a'...
OKAY [ 1.507s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash system_a F:\dload\UPDATE\system_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 593316360 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 112839176 is not a multiple of t
he block size 4096
sending sparse 'system_a' (457291 KB)...
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
OKAY [ 16.816s]
writing 'system_a'...
FAILED (remote: sparse flash write failure)
finished. total time: 22.552s
C:\Users\MONSTER>fastboot flash frp F:\dload\UPDATE\frp.img
target reported max download size of 471859200 bytes
sending 'frp' (512 KB)...
OKAY [ 0.025s]
writing 'frp'...
OKAY [ 0.022s]
finished. total time: 0.052s
C:\Users\MONSTER>fastboot flash persist F:\dload\UPDATE\persist.img
target reported max download size of 471859200 bytes
sending 'persist' (2048 KB)...
OKAY [ 0.075s]
writing 'persist'...
FAILED (remote: partition length get error)
finished. total time: 0.093s
C:\Users\MONSTER>fastboot flash reserved1 F:\dload\UPDATE\reserved1.img
target reported max download size of 471859200 bytes
sending 'reserved1' (5120 KB)...
OKAY [ 0.182s]
writing 'reserved1'...
FAILED (remote: partition length get error)
finished. total time: 0.204s
C:\Users\MONSTER>fastboot reboot
any idea of some img to load into ram?
or is there a method, that, allows me to flash files on emmc, over serial port?
i mean, serial port allows me to load them into ram.
but i wonder if it's capable to see the emmc.
@user4774 - i noticed that, flashing img's in the order that you gave me, beginning with vrl and vrl_backup, the write prim vrl failed error is gone.
so all of them,in that log,are flashed in order.

@ajsmsg78 - sir, i saw your no force encription boot image, and wanted to ask if you could help me with some file to load into ram, but which is capable to accept some others commands, excluding fastboot

Pixel 2 command flash error

I am attempting to "unroot" my phone and when i try to flash the factory image there is an error "FAILED (remote: Command Flash Error)"
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38652 KB)...
OKAY [ 0.869s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.881s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.349s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.896s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.168s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 10.391s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.813s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (345 MB) to disk... took 2.220s
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 13933563 4k blocks and 3489792 inodes
Filesystem UUID: caba058e-0ebc-11e8-a919-19e9115ff992
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
finished. total time: 0.020s
I tried a tutorial i found online where i sideloaded a OTA with adb but that spikes an incompatibility error
"failed to verify package compatibility runtime info and framework compatibility matrix are incompatible"
I just want to factory reset it and lock the device.

IAmRoot_Console said:
I am attempting to "unroot" my phone and when i try to flash the factory image there is an error "FAILED (remote: Command Flash Error)"
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38652 KB)...
OKAY [ 0.869s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.881s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.349s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.896s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.168s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 10.391s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.813s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (345 MB) to disk... took 2.220s
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 13933563 4k blocks and 3489792 inodes
Filesystem UUID: caba058e-0ebc-11e8-a919-19e9115ff992
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
finished. total time: 0.020s
I tried a tutorial i found online where i sideloaded a OTA with adb but that spikes an incompatibility error
"failed to verify package compatibility runtime info and framework compatibility matrix are incompatible"
I just want to factory reset it and lock the device.
Click to expand...
Click to collapse
I would first try a different USB cable then if that doesn't work try another PC. It also appears that your trying to flash the B partition and not the A partition of your device

What next
@enzyne Ok just tried a new cable and a new pc and niether did work. Also how do i flash to Partition a of the device and would the be the source of my problems? because right now i can go into recoverymode and the bootloader screen and that is it.

Not partition found?
Now when i try to flash Slot a it says "FAILED (remote: No such partition.)"
target reported max download size of 536870912 bytes
sending 'slot_a' (32768 KB)...
OKAY [ 0.735s]
writing 'slot_a'...
FAILED (remote: No such partition.)
finished. total time: 0.738s
Same on slot b could be because the same img is on there

To be clear you still have an unlocked bootloader correct? What platform tools are you using? The latest ones from google?

enzyne said:
To be clear you still have an unlocked bootloader correct? What platform tools are you using? The latest ones from google?
Click to expand...
Click to collapse
I am using the latest Platform-tools (ADB/Fastboot) tools from google and the bootloader is unlocked. My problem is that when i try to flash the factory image all it does is spit out the Command Flash Error. I got it into recovery mode by flashing boot.img to the two slots (a and b) and i tried to sideload the OTA but i got a compatibility error so now im stuck on what to do

IAmRoot_Console said:
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
------------------------
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
Click to expand...
Click to collapse
Are you flashing an older version than what's installed on your phone?
Sent from my Pixel 2 using Tapatalk

ajrty33 said:
Are you flashing an older version than what's installed on your phone?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Now i feel like an idiot i just had to flash 8.0 and now it is working and is stock

There is another way. You can edit the checkpoint to override and flash any version of bootloader.
---------- Post added at 06:52 PM ---------- Previous post was at 06:34 PM ----------
SOLVED BY TRIAL. IN CASE ANYONE ELSE IS GETTING THE SAME ERRORS, DO THIS -->
OPEN THE image-walleye-opm1.1****.zip in winzip, winrar, 7z - and open the android-info.txt by notepad++ or noptepad and edit the "require version-bootloader=mw.8898-002.00***.*** to the one that is asked for in the cmd error log and rerun the flash-all.bat

OnePlus 6 stuck in bootloader

At this point, I just need to get my phone working again. I don't care if it is stock, but right now, I cannot get out of bootloader. Most everything I try to do with fastboot fails....
Code:
$ fastboot devices
b6f10fbb fastboot
$ fastboot boot OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
downloading 'boot.img'...
OKAY [ 1.998s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.012s
$ fastboot flash boot OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.051s]
writing 'boot_a'...
OKAY [ 0.307s]
finished. total time: 2.358s
$ fastboot -w
wiping userdata...
mke2fs 1.45.5 (07-Jan-2020)
Warning: RAID stripe-width 1 not an even multiple of stride 2.
/tmp/TemporaryFile-a9OdTu: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
pwd: /library/phone tools/10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-fastboot
$ fastboot -w update images.zip
< waiting for any device >
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2860 MB)...
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)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB)...
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.45.5 (07-Jan-2020)
Warning: RAID stripe-width 1 not an even multiple of stride 2.
/tmp/TemporaryFile-7kXuEc: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I have a bunch of tools downloaded.
OS is Ubuntu 20.04. I do not have ready access to Windows.

u need msmflashtool on windown to fix it easy, if it not worked for you just send me msg on telegram
@NotReal0
( i dont need your money )