I rooted my phone near the launch of the Pixel 2 so I could get wifi tether to work with my gUDP Verizon plan (device is from Google). I am still on 8.0 and having issues updating to 8.1. I'm having a lot of issues with crashing apps etc so I'm hoping updating will help.
I've tried a few methods unsuccessfully. I tried to do the uninstall with Magisk but it stated that the boot files weren't there. I deleted Magisk per another set of instructions and attempted to sideload and failing there as well.
I can get the phone connected with ADB. The bootloader is unlocked still. After that, I'm at a loss at what to do next. Any assistance would be appreciated its been a few years since I've messed around this stuff and obviously, things have changed and/or I've gotten dumber.
Download the full factory image, the latest.
Unzip it into your platform tools folder.
Find the flash-all.bat file and open it with notepad and edit out the -w and save it. Removing that saves your data apps and settings.
Open a command prompt in your platform tools folder
Connect the phone to the PC
Adb reboot bootloader
flash-all.bat
Reboot, redo your root and wifi tether haxk
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 6.458s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 6.461s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 4.517s]
writing 'radio_b'...
OKAY [ 0.572s]
finished. total time: 5.091s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.228s
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.029s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 21.596s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 6.476s
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 (349 MB) to disk... took 3.851s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ10n
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 711KPED0781084
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ10n'.
Update requires 'TMZ12b'.
finished. total time: 0.016s
Press any key to exit...
jdougal11 said:
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Click to expand...
Click to collapse
Did you first unlock your bootloader critical partition?
fastboot flashing unlock_critical
Same here, my apps crash like crazy and i factory reset like 3 times but still same problem except that now is only social apps and a couple games that keeps crashing and not even reinstalling and fixes the problem
Related
I've ran this multiple times on multiple stock images (8.0, 8.1, 9.0), (Bootloader is unlocked on fastboot mode but in developer area it shows greyd out )
But after flashing, I reboot and see my old rom booting up. Can anyone tell me why is it not flashing?
My output
sudo ./flash-all.sh
Sending 'bootloader_a' (32248 KB) OKAY [ 1.111s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.041s]
Finished. Total time: 3.274s
rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.058s
< waiting for any device >
Sending 'radio_a' (57272 KB) OKAY [ 2.063s]
Writing 'radio_a' OKAY [ 0.489s]
Finished. Total time: 2.683s
rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.058s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1709121620
Baseband Version.....: 8996-013053-1706271859
Serial Number........: HT6A10203511
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.156s
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 (1808 MB) to disk... took 37.338s
archive does not contain 'system.sig'
extracting system_other.img (780 MB) to disk... took 16.314s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (251 MB) to disk... took 1.702s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
/home/danish/Downloads/marlin-opr3.170623.013/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
~/Downloads/marlin-opr3.170623.013 took 1m 20s
➜ sudo ./fastboot --set-active=other
Setting current slot to 'b' OKAY [ 0.101s]
Finished. Total time: 0.184s
~/Downloads/marlin-opr3.170623.013
➜ sudo ./flash-all.sh
Sending 'bootloader_b' (32248 KB) OKAY [ 1.352s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 1.760s]
Finished. Total time: 3.221s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.086s
Sending 'radio_b' (57272 KB) OKAY [ 2.303s]
Writing 'radio_b' OKAY [ 0.499s]
Finished. Total time: 2.940s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.060s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1709121620
Baseband Version.....: 8996-013053-1706271859
Serial Number........: HT6A10203511
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.215s
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 (1808 MB) to disk... took 29.163s
archive does not contain 'system.sig'
extracting system_other.img (780 MB) to disk... took 23.849s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (251 MB) to disk... took 2.097s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
/home/danish/Downloads/marlin-opr3.170623.013/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
Manually use terminal to enter the commands. From the looks of it, everything but the system img updated. Open the bat file to use as a reference for the commands. It should be 'fastboot flash -w update (system zip)'. Easiest way would be to drag and drop the system zip into terminal after the 'update' part of the command. If you wish to not have the update erase your sd memory, leave out the '-w'. Have fun.
Opps! Deleted.
Hi, I recently changed to a Custom ROM (Resurrection Remix) and stupid me forgot to backup before unlocking the bootloader, meaning I don't have a stock image. Here's the whole thing:
Resurrection Remix is based on LOS, so I have Lineage recovery atm.
I don't have TWRP flashed, but even when I used fastboot boot twrp.img it booted into TWRP and kept flashing the TWRP logo you see when you boot into it. If you have a TWRP backup I can try and use, that would be great. When I try flashing the official factory image, it just flashes a few things, says it can't find the file 'userdata' and says it failed, here's what happens:
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 2.031s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.949s]
finished. total time: 3.985s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.054s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 3.132s]
writing 'radio_a'...
OKAY [ 0.461s]
finished. total time: 3.601s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.998s
target reported max download size of 536870912 bytes
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 'recovery.img'
extracting system.img (1938 MB) to disk... took 127.844s
archive does not contain 'system.sig'
extracting system_other.img (311 MB) to disk... took 104.834s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (260 MB) to disk... took 13.234s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...
My Pixel XL is in bootloader mode and I do have an OS installed, so I still can access the phone.
Please help, thanks!
Lol. Why do you try to flash stock image using minimal ADB/Fastboot? Did you try following the Google way?
Basically: unzip the factory image and double click flash-all.bat script ?
Here is a proper how-to:
https://developers.google.com/android/images
Good luck...
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
target reported max download size of 536870912 bytes
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 'recovery.img'
extracting system.img (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: 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 had the same issue yesterday. Fixed it by downloading the latest SDK platform tools here https://developer.android.com/studio/releases/platform-tools and extracting all the files into the same folder as the factory image with the flash-all script.
christanya99 said:
Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
target reported max download size of 536870912 bytes
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 'recovery.img'
extracting system.img (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: 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
Click to expand...
Click to collapse
The problem is "/usr/lib/android-sdk/platform-tools/mke2fs"
* Check that you have a mke2fs in that directory. If yes, install the latest platform-tools
* If you don't, install the full platform-tools (not the small pack containing only fastboot, adb, and a few other stuff...)
The fix from the other answer will work, but you shouldn't have the install platform-tools in every stock image you want to install...
I was having similar errors with my google Pixel C. Its stock .zip file has again another .zip file.I also extracted that .zip file and manually flashed each .img one by one and it did worked for me.
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
(I used sudo to be extra safe.)
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
target reported max download size of 536870912 bytes
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 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
samsam2020 said:
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
target reported max download size of 536870912 bytes
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 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
Click to expand...
Click to collapse
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Homeboy76 said:
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
:good::good::good:
Very GOOD man!
Just tried and i was able to restore the factory image
also rooted my phone again!!
Million thanks for your help.
Hello, I am trying to unroot my phone and relock the bootloader, but I am having some troubles.
After some trial and error with various forums guides here on XDA, I have been trying to use the Tool All in One, the MSM, but nothing is working. Furthermore, I am worried that I have bricked my phone.
The things I have done so far are:
Initially, I rooted the phone with Magisk. During this, I made a file that told my GPS to be where an application wanted it to be, and saved is a system file.
I have since decided to resell the phone and the buyer wants it to be stock. So, I tried the above mentioned tools of Tool All In one, and tried to flash a stock rom but it gave me an error.
I tried MSM but the device comes back as an error to do with serial number or something.
Whilst playing around with these tools, I have some how sent the phone into a permanent fastboot state and I am unable to reboot into any other state, and so I tried to use the guide found here, https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
This just lead to another failure, where it said I don't have the partitian.
If anyone can help me just get the phone to being a stock phone with no bootloader unlock, that would be great. Happy to chat over Discord if that helps!
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9c9ee59
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (96 MB) to disk... took 0.262s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.328s]
Writing 'boot_a' OKAY [ 0.422s]
extracting dtbo.img (16 MB) to disk... took 0.038s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.399s]
Writing 'dtbo' OKAY [ 0.059s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.012s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.227s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.426s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Press any key to exit...
This is what I get when I try to use https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
"fastboot reboot fastboot" to get into fastbootD and then reflash all partitions
In case anyone stumbles across this one day looking for a fix, I found one. My issue was that msm would not connect to sahara and tool all in one wouldn't lock the boot loader without the phone becoming corrupt. To make matters worse, through out all this I lost the ability to use adb and had to use fastboot, and even worse, I some how lost the os entirely and was only able to get into the boot loader.
So the fix for all of this, aka, how to get back to entirely stock software with no root or Bootloader unlocked is this:
1. Install lineageos recover and then os using fast boot so there is at least an operating system and ability to use adb again.
2. Start the phone entirely so you know it works
3. Go back to the bootloader and Install twrp recover
4. Format phone and then adb sideload oxygen os
5. boatload lock with Tool all in one
And wallah it was fixed. If someone needs to know the exact step by step I'm sure I might reply again one day but for now, I'm going to bed!