Database Users

Help, a/b parition screwing up my OS

Hey so I was previously on the oreo beta and reverted back to stock. I reflashed stock using a few tutorials around and it worked for a bit but magisk was screwing it up and the log file kept filling up all the storage (a known bug) and every time it rebooted it would factory reset the phone. For some reason I changed the active partition to b instead of a and magisk isnt installed but apps like snapchat don't work.
What's the best course of action to fix this? Twrp doesnt show up in recovery, its only the stock recovery. Do I need to reflash twrp on partition b and swap back to a?

Flash back to stock
Then do not lock bootloaders
Sent from my PH-1 using XDA Labs

I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?

zNiiC said:
I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?
Click to expand...
Click to collapse
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.

tech_head said:
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.
Click to expand...
Click to collapse
Hmm thats the guide I used. I'll try it again.

zNiiC said:
Hmm thats the guide I used. I'll try it again.
Click to expand...
Click to collapse
He's what I see for a "flash_all.bat/sh" for Oreo Beta2:
fastboot flash abl_a abl
fastboot flash abl_b abl
fastboot flash bluetooth_a bluetooth
fastboot flash bluetooth_b bluetooth
fastboot flash boot_a boot
fastboot flash boot_b boot
fastboot flash cmnlib_a cmnlib
fastboot flash cmnlib_b cmnlib
fastboot flash cmnlib64_a cmnlib64
fastboot flash cmnlib64_b cmnlib64
fastboot flash devcfg_a devcfg
fastboot flash devcfg_b devcfg
fastboot flash dsp_a dsp
fastboot flash dsp_b dsp
fastboot flash hyp_a hyp
fastboot flash hyp_b hyp
fastboot flash keymaster_a keymaster
fastboot flash keymaster_b keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash modem_a modem
fastboot flash modem_b modem
fastboot flash nvdef_a nvdef
fastboot flash nvdef_b nvdef
fastboot flash pmic_a pmic
fastboot flash pmic_b pmic
fastboot flash rpm_a rpm
fastboot flash rpm_b rpm
fastboot flash system_a system
fastboot flash system_b system
fastboot flash tz_a tz
fastboot flash tz_b tz
fastboot flash vendor_a vendor
fastboot flash vendor_b vendor
fastboot flash xbl_a xbl
fastboot flash xbl_b xbl
Note that both partitions are flashed.
Look at the flash commands in the version you want to go to and make sure BOTH slots are being flashed.

I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.

zNiiC said:
I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.
Click to expand...
Click to collapse
I'm sure you have solved this, but for the record, it's either. .bat or .sh depending on whether you are using windows or Linux.

[guide][Payload.bin] Install OTA zip without Twrp

Payload.bin is a file which contains many imgs(system.img,boot.img...).
you can find some extracted files in: https://github.com/TadiT7/xiaomi_jasmine_dump
Requests:
Windows
Payload Drumper Download Here
Python Download Here
Fastboot Download Here
Bootloader unlocked
Step:
Extract rom zip and get payload.bin
Extract payload_drumper-win64 from zip
Put payload.bin in playload_input folder
Run payload_dumper.exe
Flash imgs using fastboot
For Mi A2:
Code:
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
if you see "invalid sparse file format at header magi" when flashing system and vendor, ignore it and wait.
if you needed root you can flash patched_boot.img
Code:
fastboot boot patch_boot.img
then Download Magisk installer and flash direct again Magisk.
or
Code:
fastboot flash boot_a patch_boot.img
This process take some time.
if you update O to P, frist boot will take long long time, you can force reboot(press 10s power button) to resolve it.
It may take a little time in frist screen.

so i need to copy all the img in to the adb folder for fastboot?

Rohit.ghosh said:
so i need to copy all the img in to the adb folder for fastboot?
Click to expand...
Click to collapse
Yup

I've just uploaded the images.
Here is the link: https://drive.google.com/open?id=1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4
Didn't test myself yet. If someone try it leave some feedback.

What is payload.bin and what will it do ?

How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.

Windows detected virus on payload dumper?

Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
Restart the phone, I have this problem when I install the ROM using MiFlash, the phone only starts after I restart the smartphone. Try it there.

Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
Mine took more than normal, but under 5 minutes I'd say. Maybe it depends on how many things you've installed, idk.
Switch apps lags as hell by the way. Anyone with this problem? It's bothering me a lot.

Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
force reboot can resolve

help!!
I got a message "invalid sparse file format at header magi" in system and vendor images
I download again, use payload and use uploaded images, same error :crying:
in sideload using ota file I got "error in /sideload/packege.zip (status 1)
bootloader is unlocked

sinantuysuz said:
Windows detected virus on payload dumper?
Click to expand...
Click to collapse
yes

Olivatti said:
I got a message "invalid sparse file format at header magi" in system and vendor images
I download again, use payload and use uploaded images, same error :crying:
in sideload using ota file I got "error in /sideload/packege.zip (status 1)
bootloader is unlocked
Click to expand...
Click to collapse
invalid sparse file format at header mag" it is normal, can be continue

No it is normal. Wait for few minutes it will proceed.

is it mandatory to flash both slot?
---------- Post added at 04:51 PM ---------- Previous post was at 04:20 PM ----------
i am getting boot loop

I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.

Hey, where's the link for patched_boot.img?
thanks

Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
Same, I just get bootloops every time.

Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
Same

rasputine said:
Hey, where's the link for patched_boot.img?
thanks
Click to expand...
Click to collapse
I have one here - https://sourceforge.net/projects/xioami/files/Mi A2/
---------- Post added at 01:54 AM ---------- Previous post was at 01:50 AM ----------
Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
It will take some time (around 5-7 mins) to complete when flashing system & vendor to both a/b .. after it is done, fastboot will be active again then can proceed to next image flashing.
To make it easier ... make those commands in a single batch file. So after you connect your device to PC in fastboot mode, just run the batch file .. let it do its thing until it finish .. this will take around 30 mins to complete.
EDIT : Sharing my own batch file here if anyone want to try, so you don't need to write each line of fastboot flash *** one after another images.
https://forum.xda-developers.com/showpost.php?p=78123332&postcount=457

[easy guide] [android pie mia2] [cam2api+root]

Hello Guys
So I decided to make a more easy guide to install Android 9
Using a Fastboot Flash
-REQUIRES-
CMD (DONT WORK ON POWERSHELL)
FASTBOOT FLASH UNLOCKED
FASTBOOT FLASH_CRITICAL UNLOCKED
Download this File
https://drive.google.com/file/d/1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4/view
(This is all img of BUILD)
Download this file
https://drive.google.com/file/d/1gwmmcQ1YAqiHVqBWtgouJPOwSHpJTdOO/view?usp=drivesdk
(fastboot necessary files)
1 Extract zip of Build
2 Extract zip of fastboot files on Build folder
3 Connect MIA2 in fastboot mode
4 Start flash using the commands :
IMPORTANT NOTE
IN SYSTEM FLASH MAY YOU GIVE ERROR ON MAGIC SPARSE.
IGNORE IT AND LET FLASH FINISH
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
Your apps don't be wipped!
*If you got a Bootloop*
fastboot erase system_a
fastboot erase system_b
fastboot erase vendor_a
fastboot erase vendor_b
And flash all again
Enabled CAM2API + ROOT
Fist of all Install Magisk Manager
FIRST BOOT IN SYSTEM
Download this
https://drive.google.com/file/d/11bUI_vz4hYvxEgu5dNEkpHuNBatbAtEz/view?usp=drivesdk
Put into Build folder than
Connect in fastboot mode
And use followed command
fastboot boot patched_boot.img
Open Magisk and Directly install Magisk zip
Now go to Root Explorer
System/build.prop look for
persist.camera.hal3.enabled=0
Change to =1
Have to lines on build.prop change all.
Don't forget to hit Thanks.

riirezende said:
Hello Guys
So I decided to make a more easy guide to install Android 9
Using a Fastboot Flash
-REQUIRES-
FASTBOOT FLASH UNLOCKED
FASTBOOT FLASH_CRITICAL UNLOCKED
Download this File
https://drive.google.com/file/d/1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4/view
(This is all img of BUILD)
Download this file
https://drive.google.com/file/d/1gwmmcQ1YAqiHVqBWtgouJPOwSHpJTdOO/view?usp=drivesdk
(fastboot necessary files)
1 Extract zip of Build
2 Extract zip of fastboot files on Build folder
3 Connect MIA2 in fastboot mode
4 Start flash using the commands :
IMPORTANT NOTE
IN SYSTEM FLASH MAY YOU GIVE ERROR ON MAGIC SPARSE.
IGNORE IT AND LET FLASH FINISH
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
Your apps don't be wipped!
Enabled CAM2API + ROOT
Fist of all Install Magisk Manager
Download this
https://drive.google.com/file/d/11bUI_vz4hYvxEgu5dNEkpHuNBatbAtEz/view?usp=drivesdk
Put into Build folder than
Connect in fastboot mode
And use followed command
fastboot boot patched_boot.img
Open Magisk and Directly install Magisk zip
Now go to Root Explorer
System/build.prop look for
persist.camera.hal3.enabled=0
Change to =1
Have to lines on build.prop change all.
Don't forget to hit Thanks.
Click to expand...
Click to collapse
If u already have magisk why u editing build.prop?
just flash camera2api enabler

Adinid said:
If u already have magisk why u editing build.prop?
just flash camera2api enabler
Click to expand...
Click to collapse
Because don't work ???
Need change stock values

riirezende said:
Because don't work ???
Need change stock values
Click to expand...
Click to collapse
u tried to install this in magisk manager?

Adinid said:
u tried to install this in magisk manager?
Click to expand...
Click to collapse
Yes Dude as I say need change values existing on build.prop

Hey.....camera2api enabler screwed my root with magisk...!!!

Can you share some AnTuTu Benchmarks scores please?

Im getting stuck on the Android One screen.

harrypakhale said:
Im getting stuck on the Android One screen.
Click to expand...
Click to collapse
same cases

Do you solve it?

harrypakhale said:
Im getting stuck on the Android One screen.
Click to expand...
Click to collapse
Same here, bootloop after flashing.

+1

EricTrasancos said:
Do you solve it?
Click to expand...
Click to collapse
No problem at the files. Must be followed correct.

JimYoung said:
Same here, bootloop after flashing.
Click to expand...
Click to collapse
hellonasty said:
+1
Click to expand...
Click to collapse
Followed correctly?
Some guys are related boot loop in all methods.
I suggest you try again slowly

I also ended up on bootloop first time. It seems that the problem was that I was using fastboot with powershell.

So if I get the error in system I should NOT try flashing system again, but just ignore it and continue with vendor?

Get bootloop. I flashed this twice and failed to boot

Worked perfectly. For those who have trouble: Make sure to wait (EVEN 10MIN IF IT'S NECESSARY) after flashing both system_a and system_b as vendor_a and vendor_b. DO NOT CLOSE CMD. Make sure to use CMD and not PowerShell. If after fastboot reboot the phone shows a flashing black screen after the Android One logo DO NOT PANIC! AFTER A WHILE IT BOOTS UP NORMALLY.

soygogeta4 said:
Worked perfectly. For those who have trouble: Make sure to wait (EVEN 10MIN IF IT'S NECESSARY) after flashing both system_a and system_b as vendor_a and vendor_b. DO NOT CLOSE CMD. Make sure to use CMD and not PowerShell. If after fastboot reboot the phone shows a flashing black screen after the Android One logo DO NOT PANIC! AFTER A WHILE IT BOOTS UP NORMALLY.
Click to expand...
Click to collapse
Mine just stuck at black screen and when I press the power button it vibrates

Worked but when i edited build.prop it messed up my root with magisk
---------- Post added at 10:39 AM ---------- Previous post was at 10:03 AM ----------
djavo22 said:
Hey.....camera2api enabler screwed my root with magisk...!!!
Click to expand...
Click to collapse
Me too, found a solution?

Can't get hard bricked OP8P to EDL mode

Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated

I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.

Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something

I've tried everything...

I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.

Reserved.

try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )

Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.

If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.

BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp

Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?

BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.

You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.

I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)

Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse

MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.