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
Hello,
i tried to update my OP6 to a custom Rom. In TWRP i unfortunately wipe everything and reboot to recovery without install a Rom.
Not the Phone starts only in Fastboot Mode. If i try to start TWRP from Fastboot, i get this Error Message:
C:\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.926s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.977s
I tried to flash different Kernels with flashing:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
The Kernel will bi flashed without Error, but TWRP do not start.
I also tried the Fastboot Rom, but also with no Luck. If i try the flash-all.bat i get the following Messages:
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.506s
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.078s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2860 MB) to disk... took 41.306s
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.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 12.753s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: %1 ist keine zulässige Win32-Anwendung. (193)
error: Cannot generate image for userdata
Press any key to exit...
Can anyone Help me?
Msm download tool and ur done
Thats it! Thanks.
Hello,
I am trying to play around with a Wiko U Feel (posting in general Q&A since this device doesn't have its thread), and wanted to play around with the /system ROM, but am stuck unable to rebuild a modified ROM.
Here is the story :
So I got the ROM, used the simg2img from Ubuntu 18.04 's packages, mounted it, made a minor change, unmounted, repacked with the img2simg, but wasn't able to reflash, with the output :
Code:
[email protected]:~/Documents/Android/wiko-u-feel/custom_rom$ fastboot flash system system.new.img
target reported max download size of 134217728 bytes
erasing 'system'...
OKAY [ 0.023s]
sending sparse 'system' 1/19 (129568 KB)...
OKAY [ 12.538s]
writing 'system' 1/19...
FAILED (remote: Unknown chunk type)
finished. total time: 12.604s
As it turns out, modifying the file isn't even necessary :
Code:
[email protected]:~/Documents/Android/wiko-u-feel/custom_rom$ simg2img system.img system.raw.img
[email protected]:~/Documents/Android/wiko-u-feel/custom_rom$ img2simg system.raw.img system.new.img
[email protected]:~/Documents/Android/wiko-u-feel/custom_rom$ file system.img system.new.img
system.img: Android sparse image, version: 1.0, Total of 786384 4096-byte output blocks in 3158 input chunks.
system.new.img: Android sparse image, version: 1.0, Total of 786384 4096-byte output blocks in 2262 input chunks.
I have tried a few other simg2img/img2simg binaries, but same results so far, and I am running out of ideas. If anyone has any idea he/she may want to share, that would be very welcome
I followed the instructions on Google's site, but when I ran the script, it failed.
Output:
Code:
[email protected]:~/hammerhead-m4b30z$ ./flash-all.sh
< waiting for any device >
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.524s]
finished. total time: 0.834s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.740s]
writing 'radio'...
OKAY [ 3.131s]
finished. total time: 4.871s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (9 MB)...
archive does not contain 'recovery.sig'
extracting system.img (996 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-FXsDZt: 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
Hey there everyone!
I have a Problem, i had my Oneplus 7 PRO bricked while i was doing wipes...
I tried doing fastboot install but no sucess
(I was originally in Android 11)
Spoiler: Fastboot Log
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.467s
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.058s
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 17.116s
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.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 4.923s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 475706264 (232278 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 968 (GC reserved = 484)
Info: format successful
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: d3275955
--------------------------------------------
sending 'boot_a' (98304 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 5.088s
Press any key to exit...
Here is the log for my fastboot, i tried this method and the msm tool...
The MSM Tool get stuck when it try to download the system...
Please help me recover <3
Januh said:
Hey there everyone!
I have a Problem, i had my Oneplus 7 PRO bricked while i was doing wipes...
I tried doing fastboot install but no sucess
(I was originally in Android 11)
Spoiler: Fastboot Log
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.467s
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.058s
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 17.116s
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.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 4.923s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 475706264 (232278 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 968 (GC reserved = 484)
Info: format successful
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: d3275955
--------------------------------------------
sending 'boot_a' (98304 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 5.088s
Press any key to exit...
Here is the log for my fastboot, i tried this method and the msm tool...
The MSM Tool get stuck when it try to download the system...
Please help me recover <3
Click to expand...
Click to collapse
Any luck? Seems the box for Sha256 Check needs to be unselected -- haven't dealt with this scenario, but seems like it could occur as a result of skipping that step possibly.
Good luck fixing what is still an awesome device!
Januh said:
Hey there everyone!
I have a Problem, i had my Oneplus 7 PRO bricked while i was doing wipes...
I tried doing fastboot install but no sucess
(I was originally in Android 11)
Spoiler: Fastboot Log
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.467s
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.058s
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 17.116s
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.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 4.923s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 475706264 (232278 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 968 (GC reserved = 484)
Info: format successful
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: d3275955
--------------------------------------------
sending 'boot_a' (98304 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 5.088s
Press any key to exit...
Here is the log for my fastboot, i tried this method and the msm tool...
The MSM Tool get stuck when it try to download the system...
Please help me recover <3
Click to expand...
Click to collapse
Hey did you manage to recover your phone?