I tried to change the boot image on my OnePlus One and accidentally flashed a file called logo.img (I don't know where it came from) instead of the logo.bin using Fastboot ("fastboot flash LOGO logo.img" where it should have been "fastboot flash LOGO logo.bin"). As a result, I can't boot into CyanogenMod, TWRP, or Fastboot.
How might I flash the correct logo.bin file over the corrupted partition if I can't access either of the two methods for flashing?
So the phone won't power on at all? And how do you not know where it came from? How could you possibly flash something to your device without knowing what it is or where it came from?
Transmitted via Bacon
timmaaa said:
So the phone won't power on at all? And how do you not know where it came from? How could you possibly flash something to your device without knowing what it is or where it came from?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, it was hard bricked. I attempted to make my own boot logo.bin file a few months ago and forgot to delete it from my SDK folder when I realized it was screwed up. I had forgotten that that was still there so I accidentally flashed that instead of the correct .bin.
I fixed the hard brick using this: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
asmth00 said:
Yeah, it was hard bricked. I attempted to make my own boot logo.bin file a few months ago and forgot to delete it from my SDK folder when I realized it was screwed up. I had forgotten that that was still there so I accidentally flashed that instead of the correct .bin.
I fixed the hard brick using this: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
It wasn't hard-bricked, it was soft-bricked.
Transmitted via Bacon
timmaaa said:
It wasn't hard-bricked, it was soft-bricked.
Transmitted via Bacon
Click to expand...
Click to collapse
No, it was hard bricked. I've soft bricked my device several times and have easily been able to pull it out. The boot partition was messed up as a result of my trying to fix it. Nothing was working - recovery, fastboot, Cyan, and I was getting QSUSB_BULK in device manager.
asmth00 said:
No, it was hard bricked. I've soft bricked my device several times and have easily been able to pull it out. The boot partition was messed up as a result of my trying to fix it. Nothing was working - recovery, fastboot, Cyan, and I was getting QSUSB_BULK in device manager.
Click to expand...
Click to collapse
That's still a soft-brick, it's just more severe. A hard brick will not power on or respond to any stimulus at all, the only way to fix a hard brick is by soldering onto the main board itself and using jtag to repair it.
Transmitted via Bacon
Related
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Again it's probably dead eMMC lol
Giolte_ said:
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Click to expand...
Click to collapse
Emmc is corrupt you have to send it again. Juat coincedence that it happened again
So I have to send again to LG?
Giolte_ said:
So I have to send again to LG?
Click to expand...
Click to collapse
I just said that -.-
Sorry, I have reloaded the page when only Lethargy had posted
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Giolte_ said:
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Click to expand...
Click to collapse
Sure looks like you have to rma the device again
Sent from my Nexus 5 using XDA Free mobile app
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Giolte_ said:
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Click to expand...
Click to collapse
Have you tried LG Flashtool?
No, I have not understood how to use it..
I have not understood things like the factory version change, and I don't want to brick the phone... there is anything else that I can do?
The phone is already pretty much bricked imo.. Flash write failure means write access to the eMMC has gone kaappuuuttt!
You need to send the device back to LG as already stated by others. It's very unfortunate that this happened to you twice in such a short period.
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Giolte_ said:
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Click to expand...
Click to collapse
Locking the bootloading doesn't wipe your recovery. You will need to flash the stock recovery via fastboot to replace twrp. However, I doubt whether you will be able to replace it since the eMMC has gone bad. Anyways, there;'s nothing to loose.. Give it a shot.
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Giolte_ said:
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Click to expand...
Click to collapse
1. Unlock the bootloader (if it's locked).
2. Flash stock recovery.img via fastboot.
3. Reboot and use command "fastboot boot twrp.img" //This will boot your device into twrp.
4. Sideload this file in twrp: http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907
The above file will reset the tamper flag and lock the bootloader!
When I extract the files from the zip, the boot, system and recovery are dated 12/12/2008... is this normal?
Yes..
Ok, last questions... if I'll flash the zip, I have to use in sideload this: "adb sideload cwm-Nexus.BootUnlocker.zip"?
And why, there is "cwm" in the name? Sorry for all these questions, but I don't want to burn my last hope...
Hello all
I have a baaaaad situation going on!
I have been trying to delete me superuser in twrp, but something terrible happened....
1) When i boot my 1+ it just stays black.
2) When i boot into fastboot it just shows a linux penguin logo and noting else.
3) When i go to twrp i can do multiple things like adb sideload, and i can push a rom to my phone.
-> but everytime i do this and try to install it, it just fails and says i have no OS installed when i want to reboot.
I've contacted support from 1+ but nothing yet so far...
Anyone here who can help me? (i'm open for teamviewer and even want to pay the person who can fix my Oneplus)
Hoping one of you can help me!
Greetz
Michel
(I have a picture of the logo but i can't post i due to beiing a new member here )
You can't communicate with your phone through fastboot and ADB? Oh ****...
How did you manage to replace the bootloader with a Linux penguin? When you go into fast boot and type does fast boot devices does the pc recognize the phone?
Sent from my One A0001 using Tapatalk
The thing is, i was rooting my device and after i've done that my rootchecker told me the root was incomplete...
So smart as i was i started a complete unroot, to do it all over again...
In this process my device got stuck... so i booted in TWRP recovery to uninstall everything from the root over there..
Here i managed to delete my complete OS.... 8-|
After reading every tutorial and guide i figured out that on my phone my developper otions were NOT enabled...
So i contacted the oneplus support, who even remotely connected to my computer from Beijing to Belgium.. but never the less my problem was not solved and i was still stuck on the f*cking Linux logo...
So i started searching for a flashable ROM (in this case i found Pacman Nightly Signed) to flash on my phone through command on Windows.
After many hours and even more attempts i managed to go in adb en flash it by the sideload way.
So not through "adb push romname.zip /sdcard...." but by "adb sideload romname.zip /sdcard...."
And the pacman rom started to install and booted my phone to language selection...
PS: i cried :cyclops:
Glad to hear that you fixed your phone. I wouldn't contact oneplus support for things like this, chances are you'll get a reply back from xda faster as well as searching on your own to resolve the issue.
Sent from my One A0001 using Tapatalk
OnePlus One no OS, no Charge and that stupid lunix penguin
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
timmaaa said:
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
---------- Post added at 10:09 AM ---------- Previous post was at 09:58 AM ----------
Coug76 said:
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I'm having an issue gettjngit into fastboot its died and all I'm getting is a black flashing screen!
Any tips on how to get it to charge?
Ashleigh.17 said:
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
Click to expand...
Click to collapse
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
timmaaa said:
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Ashleigh.17 said:
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Click to expand...
Click to collapse
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
timmaaa said:
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
Click to expand...
Click to collapse
okay
thank you for all your help hopefully I'll be posting later with some good news
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Ashleigh.17 said:
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Click to expand...
Click to collapse
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Ashleigh.17 said:
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Click to expand...
Click to collapse
Lol, no worries, glad to help.
timmaaa said:
Lol, no worries, glad to help.
Click to expand...
Click to collapse
This is better than the best soapserie
....
Is he going to make it?
Yes
Great! :good:
Oooooh nooooo!!!
He's got a locked bootloader
Damn F*ING
This will never turn out right
OH, look here comes @timmaaa again
He says what? :silly:Really is it possible
Yes YES YYEEEEESSS
I did it, it's working again
I loooove you
:highfive::highfive::highfive:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
ElmoRapz said:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
Click to expand...
Click to collapse
It looks like you did the same thing that I did.
Its a pretty easy fix your going to be able to avoid all of the unlocking boot loader issues I had.
To begin with when your try an turn the device on is the screen flashing black?
I believe I've bricked my OPO. I was trying to flash OxygenOS today and it wasn't flashing completely right. I decided to not try anymore and flash back to 05Q. However, in doing that I bricked my phone. Volume- and power doesn't bring me to recovery, I can't access bootloader. However when I press volume- and power it still sounds the connection and I can see it in my device managers, I just can't do anything. When I try to do anything through ADB it says no fastboot devices found. CUrrently, my phone doesn't have boot.img, recovery.img, and system.img. I do have a latest backup of my 05Q from this morning before I did all of this.
Any help would be great. Thanks!
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Try one plus one recovery toolkit 1.0 it will slove ur problem same think happens to me it will help me
timmaaa said:
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Definitely works. Just did the same after I tried to downgrade from OxygenOS and bricked my device.
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
Using my old OnePlus 8T I was able to unlock, root and install a custom kernel.
Any ideas?
shadowofdeth said:
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
the good news is your phone can very likely be fixed. however in my experience you will need a computer. Folks here would love to help but knowing what device you are having an issue with would probably help with response to your situation. from fastboot you can boot a recovery image for your device and go from there. from fastboot you can also likely flash stock firmware to your device and start over fresh. It's also common to have to perform a factory reset after flashing the device to get it to properly boot.
Click to expand...
Click to collapse
OnePlus 9.
I tried searching but there are so many dead ends for finding the stock recovery. Even with that I'd still be bricked.
Where would one find the stock recovery, kernel and fastboot ready update.zip?
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
MrSteelX said:
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
Click to expand...
Click to collapse
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
shadowofdeth said:
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
Click to expand...
Click to collapse
borrow a laptop from someone , use the msm tool
taintsx said:
borrow a laptop from someone , use the msm tool
Click to expand...
Click to collapse
Im so close I can smell it now. Managed to get Python installed (had to deep dive into the comments on articles and tutorials) and have everything extracted in the last hour.
Now, for flashing these images I have to use Termux and it's working for the most part. My issue is now that I can flash one batch of images but not the other as per the xda guide linked now:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
I keep getting errors about the partition being locked or something.
So close man. So close.
Locked partitions can only be flashed in fastbootd (fastboot reboot fastboot to get there).
First of all... Hold the both volume and power button for around 2 minutes. It'll take you to the bootloader mode. Then from the bootloader mode turn off your device then boot into edl then flash with msm.
Lesson learned