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.
Related
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
First off, this is my first time posting so not sure if I am posting in the right thread. Now for my question, I was reverting back to Android O from the developer preview of Android P as I wanted to root and use a custom rom. When doing so I kept getting an error, I then tried flashing individual files which seemed to work however it ended up being a broken version, I fixed this by factory resetting. Thinking all was well I tried flashing TWRP and it would not let me flash saying that there is not recovery, something along those lines. I can use the phone in android 8 with all the apps I need, so my phone is not a brick. I would appreciate any help that can help me properly flash android so that I can root my phone and get a custom rom.
CMD of when I try to use the flash all file.
Sending 'bootloader_a' (32248 KB) OKAY [ 0.792s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.100s]
Finished. Total time: 3.002s
rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.038s
Sending 'radio_a' (57320 KB) OKAY [ 1.342s]
Writing 'radio_a' OKAY [ 0.498s]
Finished. Total time: 1.952s
rebooting into bootloader OKAY [ 0.035s]
Finished. Total time: 0.036s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT76C0200295
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.049s]
extracting boot.img (29 MB) to disk... took 0.148s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1762 MB) to disk... took 8.817s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 3.350s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (251 MB) to disk... took 1.467s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata
Press any key to exit...
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.
Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.
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 )
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?