Database Users

[Q] [Fastboot] Can't flash Stock ROM

Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!

I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!

Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers

bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!

I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?

bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.

SOLVED: ZenFone 3 Laser (ZC551KL) dm-verity no boot

I set my phone down last night and came back to it with this screen and it will not boot into Android. It's not rooted or unlocked, the only thing I can think of is that an OTA killed it somehow, although I wasn't alerted to one or initiate anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I touch any of the buttons this screen comes up. Rebooting just starts the process over again.
I can see the phone with fastboot, and I tried flashing the factory boot.img again with no luck. I'm unable to find the factory recovery.img or system.img anywhere to give that a shot.

that was happened to my zenfone 3 5.5 too,
solution just flash firmware from asus with stock recovery

I can't get into the recovery to flash, unless I'm doing something wrong, I can only get to the bootloader and I cant find the proper .img files to flash with fastboot.

when I select reboot to recovery in fastboot it just reboots to the dm-verity screen again. It's like the recovery is just gone.

Just got off the phone with Asus, they were no help at all. I asked for the recovery image and they don't have one, what?
Does anyone know of a way to extract data from the internal storage in fastboot? I'd like to get a copy of that before I send it in...

SOLVED!
I created a modified UPDATE.ZIP using this method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data

So I did this with the newest firmware.
I can boot to recovery now (couldn't before just like yourself) but on the flash from fastboot I got
>target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
erasing 'system'...
OKAY [ 0.010s]
sending sparse 'system' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
OKAY [ 0.030s]
writing 'system'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.060s
Meaning something failed.
I'm stuck on the ASUS boot screen
Tried a Factory Reset from recovery, still nothing.
I tried fastboot erase system -w
then reflashing the newest firmware, and still nothing
Since I can get to the recovery now, does anyone have a stock .img i can flash? or any other ideas?

Try flashing the firmware .zip from either the SD card or sideload in recovery.

Niemer said:
Try flashing the firmware .zip from either the SD card or sideload in recovery.
Click to expand...
Click to collapse
I will try that tonight. Thanks!

unknown partition 'wallox.zip
SOLVED
Hi, Your response has been very useful, but I still Have a Problem With regard. The Times tells me That does not FIND the zip file needed, other times: Unknown Partition 'wallox.zip
What's the Problem?
ps. Excuse my language

Niemer said:
SOLVED!
I created a modified UPDATE.ZIP using http://forum.xda-developers.com/showpost.php?p=69380242&postcount=3 method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data
Click to expand...
Click to collapse
the link is broken... can you please give the update.zip file. Thanks
[EDIT: update.zip found ! phone recovered... all ok, thanks ]

Niemer said:
SOLVED!
I created a modified UPDATE.ZIP using http://forum.xda-developers.com/showpost.php?p=69380242&postcount=3 method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data
Click to expand...
Click to collapse
link not works

help
hello to all guys, can someone give me the modified file fastboot flash system update.zip .. I'd be very grateful ..
Hello

edowar said:
that was happened to my zenfone 3 5.5 too,
solution just flash firmware from asus with stock recovery
Click to expand...
Click to collapse
how did you able to flash sir? Mine is coming on same dm-verity screen again and again.

akashnigam said:
how did you able to flash sir? Mine is coming on same dm-verity screen again and again.
Click to expand...
Click to collapse
Create the modified update as instructed here https://forum.xda-developers.com/showpost.php?p=69380242&postcount=3
I can boot into the setup dialogue now but the phone keeps shutting down on its own after a few seconds. Anyone experiencing the same thing?

Hi. I just made a post with a fairly comprehensive solution to the brick-problem that I had. If your problem is anything like mine was, then it should be useful.
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
Much thanks to Niemer for being the inspiration for the solution. And thanks to everyone in the forum for asking good questions and posting good responses.

Niemer can you be so kind and upload your update.zip anywhere?

Lets open this tiny beast up!!!!

One click solution to unbrick and fix "no recovery mode" on zenfone 3 laser (zc551kl)
Just accidentally i found a "one click" solution to unbrick / fix loop boot / fix no recovery mode... My story started after i unlocked my Zenfone 3 Laser ZC551KL (Z01BDC) bootloader with the official tool from Asus. After i couldn't find any custom rom for this phone, i wanted to re-lock my bootloader to receive FOTA updates, so, i flashed boot.img and recovery.img from a Zenfone 2 Laser as i couldn't find files for mine, and i soft bricked it... boot loop, would only boot in bootloader, can't even access the "recovery" to apply the firmware update from sd card. After couple days of searching EVERY SINGLE WEB SITE for a viable, easy solution to fix my phone, and hundreds of files, firmwares, tools downloaded, i found it, right under my nose... Earlier in the process of looking for a solution, i downloaded a stock firmware zip (Asus_ZenFone_3_Laser_ZC551KL_WW-ZC551KL_13.40.104.1_20161014, who also included SP_Flash_Tool_v5.1720_Win. It's roughly 1.84 Gb, and 4.07 Gb after unzipping. So just download the zip, unzipp it and go into the folder and look for subfolder "Firmware+ Tool", where you'll find lots of files... look for "flashall_AFT", it's a "Windows Command script" file... double click it with your phone connected in fastboot mode, and wait. Will take 5-10 minutes, just be patient. I lost all my hopes while i was trying this just for sick of it, i left it "work" and went for a smoke... When i came back, my phone was on, with the Android Welcome setting screen.... I think i cried of happiness in my brain. Hope will help others fix the issue. Just to note, this method did not relocked my bootloader, is still unlocked, but what the hell, my phone is alive again. Aaaa, and even if i had Android 7.1.1 before, after this fix, i have Android 6.1 which i will keep till August 2018 when we'll get the Oreo for Zenfone 3 Laser. If you want to, after this fix, you can go to Asus page and download the latest version you'll like and install it manually. Here is the only link where you need to go and download the zip file to fix (it will redirect you to Mediafire for download): http://stockandroidrom.com/asus-zenfone-3-laser-zc551kl-usb-driver/
Wish you all the best.

Need Latest Firmware+Tool for my Asus zc551kl please. Update.zip and Rother method not working. Progress bar on bootscreen 2 sec delay and power off. I'm no update later 6.0.1 with unlocking bootlooader. Please,help me

moto g4 stuck in fastboot mode (Hard brick)

hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful

have you found the solution

adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet

System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem

Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?

null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again

Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that

Rom flashing failed . What should I do?

adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?

This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Installing lineage OS - stuck on start screen, would very much appreciate assistance

I've been following this guide with the aim of installing lineageos on a 6T I just bought: https://lineageosroms.com/fajita/#installation.
I downloaded the following files in advance:
copy-partitions-20200903_1329.zip
lineage-18.1-20211230-nightly-fajita-signed.zip
lineage-18.1-20211230-recovery-fajita.img
I have followed all the steps up to and including steps 6 of part 'Temporarily booting a custom recovery using fastboot'. The last part that appeared to run successfully was step 5 e.g.: fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Here is the output of the commands run on the host (serial number redacted):
adb reboot bootloader
➜ fastboot devices
******* fastboot
➜ fastboot oem unlock
OKAY [ 0.036s]
Finished. Total time: 0.036s
➜ adb reboot bootloader
➜ fastboot devices
******** fastboot
➜ fastboot flash lineage-18.1-20211230-recovery-fajita.img
unknown partition 'lineage-18.1-20211230-recovery-fajita.img'
fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'
➜ fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Sending 'boot_a' (65536 KB) OKAY [ 1.543s]
Writing 'boot_a' OKAY [ 0.332s]
Finished. Total time: 1.973s
➜ fastboot devices
******** fastboot. ### This is where I just see the message about the OEM being unlocked and integrity.
➜ adb sideload copy-partitions-20200903_1329.zip ## I ran this even though I just saw the integrity message in the hope it would then enable me to select 'Apply Update'.
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
➜ fastboot devices
******** fastboot
NB I once accidentally wrote fastboot flash lineage-18.1-20211230-recovery-fajita.img instead of fastboot flash boot lineage-18.1-20211230-recovery-fajita.img (i.e. I missed off the 'boot'). However, as I got the immediate error "fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'" I suppose it was a no-op and hopefully didn't do any harm.
The problem is that when I then booted into the phone with volume down and power (step 6) I just got a screen with a message about the OEM being unlocked and phone integrity.
I powered the phone off after waiting a while with volume up and power. Then powered on. Same message. Since then I've tried powering off and on with both volume up and volume down and power. I get into a mode where I can select start, restart boot loader, recovery mode and power off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As I understood I'm trying to get into 'recovery mode' I selected that, but that just restarts the phone. I think that just took me back to the integrity message and at that point I ran the command adb sideload copy-partitions-20200903_1329.zip in the hope it would bring up the option to apply the update. However, now whenever I restart the phone I don't see the integrity message, just the 'options' menu (please see 'start' option above). I don't see the OEM unlocked/integrity message any more regardless of how I start the phone.
I have now tried basically all the options including restart the bootloader. All lead back to the same screen. When I have the phone connected to my mac via usb, I can still at least see it with fastboot devices:
fastboot devices
******** fastboot
As the guide I'm following doesn't show what you ought to see at each step I'm not sure what should have happened on step 6 when booting into recovery mode (this is my first flash) but as the guide says
'On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.' I'm guessing it should at least have booted into a UI different to the one I'm seeing.
Is there anything I can do now? Should I try flashing another recovery image? Re running anything? Is it 'bricked'?
Really appreciate any guidance.

PS one thing I've noticed is that the instructions of 6T (https://lineageosroms.com/fajita/#installation) say we should run
fastboot flash boot <recovery_filename>.img
whereas the instructions for earlier and later models of the one plus (and other brands) say to run
fastboot flash recovery <recovery_filename>.img
Of course this might be correct, but does anyone know if this is a mistake in the instructions - i.e. should it have been 'recovery' not 'boot' for the 6/6T?
---- EDIT -----
Having looked up some documentation on fastboot (which say the structure of the command is basically fastboot flash <partition> <filename>) and then read around a bit on partitions on Android phones, I'm getting the impression android phones pretty much always have a recovery partition, which would make me think that the 'boot' command is indeed wrong. That said, I've got next to no experience with this so it's hard to be sure that the command isn't correct for some reason I'm not aware of, that only pertains to a few generations of phones.
Anyone?
--- EDIT 2 ----
The maintainers of the wiki.lineageos.org have confirmed to me that the line fastboot flash boot <recovery_filename>.img is written as intended. So still at square one.
Any ideas, anyone?

FWIW I got there. In case it helps anyone to know any of the sordid details, first I flashed back the stock ROM using this thread. Worked pretty much as described albeit I had to unzip the images folder and move the bat file into it so it found the images (first had to get hold of a windows machine).
Once I had it installed again I took an android update on the device. I think it highly likely that this was the cause of the original issue reported above - following the lineageOS wiki would probably have worked from that point, but I never found out as I decided I wanted TWRP anyway and used that as my custom recovery instead. That said, I now realise I could just as well have only installed TWRP after flashing lineage, as flashing LineageOS wiped TWRP.
BTW, I really can't fathom why I either didn't clock or ignored the message about making sure you're on the latest 11 firmware (in a red box!) at the top of the lineageOS install wiki. I don't remember seeing it but perhaps I just thought it would be fine as it was a 'fresh' phone (that had probably lying in a box for a year or so). Anyway, lesson learned.
Had to scramble over some other issues, involving booting a temp 'test' TWRP from crdroid first before flashing the official one, described around this page. I also had an odd 'no system' message in TWRP after wiping the existing system (following these instructions to check which bits to wipe when using TWRP before flashing a custom ROM). Anyone reading might want to check those instructions by asking on a lineageos forum if it makes sense to wipe 'system' on TWRP before flashing the lineage ROM - as I got a message after flashing lineage (in TWRP, before rebooting) that there was no 'system'. However it rebooted (with an error re corrupt user data that I was able to fix just by allowing lineage to wipe the user data again), so it's hard to see how that report of there being no system can have been strictly accurate.
But. I. got. there.

PS now I remember why I didn't see the warning to update the firmware. I was (unknowingly) viewing a repost (on lineageosroms) rather than the original wiki (on wiki.lineageos.org). Beware

i have the same thing but on a newer phone, my pc cant see it so im stuck here for now