Database Info

Install custom recovery and root on Cubot J5?

I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:

jimboo80 said:
I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:
Click to expand...
Click to collapse
My dear friend did you try:
https://www.cyanogenmods.org/how-to-root-cubot-j5-and-install-twrp-recovery/
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?

I have the same problem the thread starter indicates in the title: I can install the TWRP recovery image that gopikrishnanrmg linked, but the installation of Magisk doesn't work. It says it installs successfully, but I can't get root rights and if I install the Magisk app, it says that Magisk is not installed. Magisk canary doesn't work either. Does someone have an idea what I might have done wrong? Or does that mean that the device is not supported by Magisk?

gopikrishnanrmg said:
My dear friend did you try:
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?
Click to expand...
Click to collapse
Sorry for the late answer, life happens
I get it installed with that guide after unlocking flash state, but when it reboots it give me a message "orange state" and the phone resets.
and the recovery porter did not work for me, maybe i´m to old for this hehe was a while since i rooted a device, and i´m defenitly no hacker
btw if you need to look on the firmware cubot(dot)net has a downloadable link for the j5.

I have the same problem and I can't do anything about it, maybe some specific source or a hint in the form of YT

Has anyone figured out how to upload Twrp recovery to Cubot J5 ????

I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.

たろう said:
I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash recovery magisk_patched-23000_recovery.im
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.
Click to expand...
Click to collapse
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.

weeman45 said:
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.
Click to expand...
Click to collapse
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
{
"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"
}

たろう said:
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
Click to expand...
Click to collapse
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!

weeman45 said:
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!
Click to expand...
Click to collapse
I'm so glad to hear that.
I have no plans to install GSI images.

たろう said:
I'm so glad to hear that.
I have no plans to install GSI images.
Click to expand...
Click to collapse
You really helped a lot. I'm always glad to tinker with spare phones.
For anyone else stumbling upon this thread trying to install a GSI image: Here is how i succeeded.
1. Enable unlocking in your developer settings
2. Use "fastboot flashing unlock" to enable flashing (this performs a factory reset)
3. wipe your system partition with "fastboot erase system"
4. Flash your GSI image wizh "fastboot flash system 'path-to-your-GSI' "
5. flash the provided vbmeta with "fastboot --disable-verity --disable-verification flash vbmeta 'path-to-vbmeta.img' "
I had success with lineageos 18 A/B with gapps. Make sure that it's not too big in size or else you will get an error message stating it is too big.
If you have troubles getting into recovery/fastboot, use the SPflashtool to revover your stock firmware (be sure to NOT format all because you will lose your IMEI information in that process!) and try again

Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?

pat2858 said:
Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?
Click to expand...
Click to collapse
I have no idea.
if possible to initialize with flash tool and then try again.

Tried it, but no luck.
Don't know why magisk is crashing all the time.

pat2858 said:
Tried it, but no luck.
Don't know why magisk is crashing all the time.
Click to expand...
Click to collapse
Is the Magisk version 23?
I have not confirmed the latest version(24~)

[RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 3

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse

Frequently Asked Questions (FAQ)
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP zip from twrp.me
Magisk app
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install TWRP zip in Magisk app
Install Magisk "to Inactive Slot (After OTA)" in Magisk app
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites (for stock images, see attachments to post #3):
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip. Make a note of the slot to which the zip is installing (you will need this after the next step).
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
Open the Reboot menu in TWRP and switch to the slot to which the zip installed from step 4. Reboot to system now, or go to the next step.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse

Stock Boot/DTBO/Recovery Images

Keep up the good work m8 @Captain_Throwback :highfive:

Great job!

Reserved

sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?

Woohoo! Excellent!
Sent from my ASUS_I003D using Tapatalk

about twrp
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.

chacho_2me said:
sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?
Click to expand...
Click to collapse
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.

Captain_Throwback said:
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
Click to expand...
Click to collapse
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now

Monsibd said:
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Click to expand...
Click to collapse
Where is the recovery log from the TWRP boot where it was prompting for password? The OP clearly states that a log should be included with any issues. Do me a favor and try flashing the TWRP attached and let me know if it boots.
https://drive.google.com/file/d/1-2qBUqYv0AWnvqDmxIY2DqRqwG5dSwHg/view?usp=drivesdk
If it does, I can adjust the TWRP image linked in the OP. If it doesn't, I'll definitely need a log to understand the issue, and your device details.

So I did some testing, and it appears that if you're not on the latest .58 firmware, then TWRP may not boot successfully. Can anyone that has had an issue with booting TWRP please report their device variant and firmware version? If you're not on the latest, please update and then try TWRP.
WW 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/...US_I003_1-ASUS-17.0823.2007.58-1.1.9-user.zip
CN 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS661KS/UL-ASUS_I003_1-CN-17.0823.2007.58-1.1.45-user.zip
If that doesn't work, let me know.
EDIT: Actually I need to check again. I think I broke my TWRP tree so it may not be the kernel at all :/

Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?

Captain_Throwback said:
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
Click to expand...
Click to collapse
so basically installing twrp can still be overwritten when flashing original firmware from asus
.thanx sir

Monsibd said:
Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
Click to expand...
Click to collapse
So maybe there is some difference with the CN device that's causing this issue. Everyone it's working for is running WW firmware. Not sure what's different with the CN firmware, but that's unsettling.
Since the full firmware file is available, you can just use payload dumper to get the stock recovery image.
And yes, a clean flash with logs would be great, thanks!

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
same as you im on the latest ww firmware tencent games variant and rooted

bouyhy01 said:
same as you im on the latest ww firmware tencent games variant and rooted
Click to expand...
Click to collapse
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.

Captain_Throwback said:
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.
Click to expand...
Click to collapse
thank you very much captain i'll be waiting for it to test

Stock rom of Doogee S96 pro

Dear community,
I have a doogee S96 pro, I'm from Italy, and I installed TWRP from the unofficaltwrp guide.
Now I'm no more able to boot, the phones goes directly to the recovery.
Probably magisk was no able to patch the system and to disable the tm verity (avb). I have a super partition, and from what I saw the fstab is inside the vendor partition inside super.
Doogee does not provide stock roms, so I cannot restore the phone as factory settings, that's why I open this thread.
Is someone available to help me booting into Android or available to give me the stock boot/recovery img? It's a fast and safe procedure, I can give more details on how to do.
Thank you!

Dear @giubenez I had a similar problem. But after I got in touch with doogee support they sent me the firmware. I want to share it with you and with any other person that wants to ROOT THE DOOGEE S96 PRO
The following link is the firmware and upgrade tool. Please open and download.
Please note that if your computer system is French you need to change the name of the downloaded file.
Spoiler: Link
ZN129（S96）
Folder
1drv.ms
When upgrading the firmware, please do not select the 'Format All+Download' option
When flashing the phone, please set up the software first, turn off the phone, and then connect the phone to the computer.
Best wishes

Wow! thank you!!!
You saved... us!
Why doogee does not respond to me? why they not post the firmware on the forum? WTF

@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
Google introduced vbmeta which is also a verity check. An option to bypass this check is to flash an empty vbmeta.img before attempting to flash TWRP recovery.
Click to expand...
Click to collapse
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"

Ankiseth said:
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Click to expand...
Click to collapse
GOD BLESS YOU, Ankiseth!
YOU SAVE MY PHONE! SPFLASH AND EVERYTHING WORKS!

Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
Good day, I would like to ask you to help us. Please use the following link: https://1drv.ms/u/s!AvX9KABcpSV1kTOgCMsUkLyXY-we?e=nMchxl Download the previous version of the S96pro firmware and follow the tutorial to return the phone to OTA The previous version (ver3.02) was upgraded. The tutorial has been included in the firmware compression package. Please test the night vision camera after flashing the camera and let me know if it can be used normally. Thank you very much.
Click to expand...
Click to collapse
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth :
Please note that if your computer system is French you need to change the name of the downloaded file.
Click to expand...
Click to collapse
which file ?

berzerking said:
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
There Is Hope Brother... I Just Downloaded The Files And Used The SCATTER-LOADING FILE From 3.02 on SP-FlashTools 5.2 Switched It To Download Only And Hit Download .. Plugged In My Phone To USB While OFF And aftyer the loading was complete .. Phone Reboot As If NEW. ( HARD RESET) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!! Now i Just Have To ReLoad All Apps And Accounts .. And Wait For The oukitel WP7 i ordered out of frustration. Will Be Doing A Review Comparison On Both Cameras !!!!! You Can Follow Me Here If Interested https://www.youtube.com/channel/UCYOpd4yooYgKS-0xe63jnCw

Hi all. Thanks for the information. I was in touch with doogee and they say to me that there is an update during this WE (S9S88A7.DGE.DOOGEE.EEA.HB.HJAYYDVFAZ.0128.V3.03820210313-2312.
Nothing change IR camera don't work
I will flash my S96pro during the week with S9S88A7.DGE.DOOGEE.EEA.HB.HJ.AYYDVFAZ.1130.V3.02.zip and I'll post here what happened

HouseOwl said:
) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!!
Click to expand...
Click to collapse
Yes !!!!! it s alive !!!!
Thank you dude ! my ir works again !!!!!

btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you

berzerking said:
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
Can you write a tutorial? Have you used SP flash tool?
Thank you!

giubenez said:
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
Click to expand...
Click to collapse
I solved in this way:
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(with the empty vbmeta
>fastboot.exe flash recovery recovery.img
(with the stock recovery)
>fastboot reboot
after that the update attempted to start and failed, the phone then boot to android.
The updates always failes after that, so I disabled them.

this is why the update fails..is it because I used the the Russian super img?
{
"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"
}
#edit: it was because I flashed the wrong recovery. With the correct one, i still have issues with the update: md5 chechsum controll is not passed and the update aborts.
I don't care, I prefer a rooted phone without the updates.

your device has not passed the test and may not work properly - Here is a message on the screen . Constantly overloaded is not included in the recovery. The firmware doesn't help.

Could someone repost the S96Pro stock firmware... I can't find it anywhere online, thanks in advance

I'm uploading them.
https://bit.ly/3en9EZY

Thanks giubenez ,u saved me but now I have the watermark from formatting Google Key State : Fail, I don't see a factory mode file to freeze, tried ADB and couldn't find the build prop values, has anyone else ran into this with a fix?

I can't get what problem are you facing. I unlocked and rooted my s96 pro.
If you describe your issue i can help you solving it.
However, i found very risky to root the phone, if you plan to do the ota updates avoid TWRP since it'll make you bootloop at the moment you try to install the update.
The only way to solve it is to flash the stock recovery through adb.

So.. yeah.
I have recently procured this device and want to install twrp, and stock and/or test a gsi and in what capacity the phone works with one of those.
Enabled both developer mode & the usb debug mode and adb devices lists the device.
N.B; the supplied s96pro cable does not seem to carry data, "presumably" because doogee is cheapskates on cables, as well in the support department. I had to use my sony headphone cable. Go figure, its consequential at least, so there's that.
In any case, read this thread and have downloaded all files, including the apparently new stock rom that is listed since yesterday in the evidently wholesome user Ankiseth's link above.
Questions:
In the 4pda link there are some instructions, specifically the adb command with the boot.img, however.. the links seems to be dead. What to do?
A) Can I first do the vbmeta command and then use our lord and savior Ankiseth's twrp recovery file and follow a generic "Case II: Devices with A/B partition scheme" mentioned in this xda twrp guide?
B) Hope that some other wholesome user share the boot.img file?
(Or, can I use the one in the zip file 'S9S88A7.DGE.DOOGEE.HB.HJ.AYYDVFAZ.1203.V3.04' ?)
-
After twrp is accessible can I use twrp/adb and install either the mentioned shared rom and any gsi for that matter?
I use linux and sure there is spflash, but the adb & twrp combo "subjectively feels" as a more stable way of doing things.

Update 2. Got both twrp and magisk going. Now to figure out if I can install a gsi.
Update, got spflashtool working and used the latest stock rom mentioned in my previous post.
However.
I patched the boot.img from said stock rom in magisk and also flashed twrp-recovery with fastboot.
No luck. Magisk seems not to be installed and the usual twrp gui does not show, seems to be the stock recovery. Got a orange state though.

How To Guide Gaining root access on New Oxygen OS A12 for the op9.

Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
Just sharing what I've learned. Have to patch boot.img and vendor boot.img and flash out of folder in sdk on desktop.Then use vb_meta.img to disable verity flash. Guide above has to be followed to a T. Even though it's for the Chinese version Color os works fine on Oos... Patch boot.img /vendor_boot with magisk 23.0. This way magisk hide and modules work. If you patch with canary version of magisk you loose both. I'm attaching stock boot, vb_meta vendor_boot.img files for the Global unlocked op9. Files are from new A12 os. Btw 23.0 works perfectly on A12. If this helps hit the like button; it's free.
0p9 partitions..A 12 - Google Drive
drive.google.com

This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.

allenjthomsen said:
This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.
Click to expand...
Click to collapse
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
I can verify that my method works 100% on build C.36 of A12, because i am currently running it and have redone the steps multiple times to make sure nothing happens that could be bad ,the steps i have listed above in the previous post work perfectly and still let me have root currently, and i have only patched the stock boot.img.
{
"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"
}

If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.

allenjthomsen said:
If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.
Click to expand...
Click to collapse
How does one undo the disable verity with stock vb_meta after flashing back stock boot.img and vendor boot.img ,I still couldn't take internal Google ota today. Failed after I tried restoring both of those.

Anyone knows if the new oos12 is actually "stable"? Haha

infamousvincci said:
Anyone knows if the new oos12 is actually "stable"? Haha
Click to expand...
Click to collapse
Yes all the small issues I had are corrected in today's am build.

mattie_49 said:
Yes all the small issues I had are corrected in today's am build.
Click to expand...
Click to collapse
I talk to you in TG bro. Its me, the one that has a op9 that doesnt read sim on oos12. Hahaha

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.

mizarddo said:
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.
Click to expand...
Click to collapse
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked

mooadeer said:
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked
Click to expand...
Click to collapse
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
It helps a lot thank you I just got my oneplus 9 and it's on the latest update C.47 and I don't have too much experience with onePlus or even the new android devices I'm a little bit outdated didn't use root and stuff sins the android 5 that's why I'm a little bit confused I don't want to break it

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
Update following your instructions everything is Ok done with rooting thank you
LE2113 on C.47

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
from where can I download boot.img for version:
LE2113_11.C.47: LE2113_11.C.47_1470_202203102118
Thanks and best regards

Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
you mean boot image from OP? My question is how I get that file

aldoc01 said:
you mean boot image from OP? My question is how I get that file
Click to expand...
Click to collapse
Yep, stock boot images can be extracted from full zips with tools (payload extractor).
Also, i have a collection, check it out.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...

EtherealRemnant said:
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...
Click to expand...
Click to collapse
If you don't jump magisk across from A11 you have to disable verity with vb_meta partition as well to gain permanent root on A12. This I know it's my post.

Trying to fix corrupted boot file on oneplus 8 5g in2017 tmobile model (FIXED)

sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply

Provenscroll said:
sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply
Click to expand...
Click to collapse
Hi, try to download the firmware for your device and flash it to your phone.

Jan Skokan said:
Hi, try to download the firmware for your device and flash it to your phone.
Click to expand...
Click to collapse
Do you know where I could find the stock firmware?

Provenscroll said:
Do you know where I could find the stock firmware?
Click to expand...
Click to collapse
Try this

Jan Skokan said:
Try this
Click to expand...
Click to collapse
It's telling me to get a "download package". Do I have to pay for this?

First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!

immortalwon said:
First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!
Click to expand...
Click to collapse
I'm talking about the website with the package thing, when i tried to boot into twrp i got this error
./fastboot boot twrp-3.7.0_11-0-instantnoodle.img
Sending 'boot.img' (67276 KB) OKAY [ 1.949s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

[OnePlus 8][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Has old firmware you can download / flash. You can use a tool called Payload dumper on the firmware to extract all the sections and re-flash the sections you messed up. Can you get into the bootloader / fastboot screen and show me what it shows?
Re-download the twrp file for your device, rename it to twrp.img and try to do this command
Make sure you also have the correct drivers installed on your pc and disable driver signature enforcement:
fastboot boot twrp.img

{
"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"
}
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked

Provenscroll said:
View attachment 5863469
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked
Click to expand...
Click to collapse
Ok the fact you can enter into this mode and it says device unlocked is good. I am not sure why it doesn't allow you to boot with the above mentioned command into recovery.
Please make sure like I previously mentioned you have latest platform tools, latest oneplus usb drivers and try to switch to a usb 2.0 port on your pc or laptop. Disable driver signature enforcement in windows before you try to install oneplus drivers.

I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post

Provenscroll said:
I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post
Click to expand...
Click to collapse
I think you corrupted a bunch of stuff when you used a linux machine to flash a recovery. The drivers are vastly different on a linux machine. You might have to use a MSM tool at this point, but I am not sure if the T-mobile version has one. Keep us updated on the new cable. Also try different usb ports as well.
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
@Provenscroll EDIT: I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.

immortalwon said:
I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.
Click to expand...
Click to collapse
So i tried this and it successfully flashed:
.\fastboot flash recovery_b twrp.img
Sending 'recovery_b' (67276 KB) OKAY [ 1.638s]
Writing 'recovery_b' OKAY [ 0.212s]
Finished. Total time: 2.093s
When I reboot into recovery though it just ends up at the boot/recovery error
immortalwon said:
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
My android was at 12 so that might explain why flashing twrp isn't working

immortalwon said:
I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
Does the firmware i flash onto the phone also have to match the original android version?

Provenscroll said:
Does the firmware i flash onto the phone also have to match the original android version?
Click to expand...
Click to collapse
Yes I would try it on A11 first. But don't quote me on that because there is a reason I don't like using carrier based phones instead of fully unlocked phones. They come with unpredictable problems. Try at own risk. I would first try to boot into TWRP first on a11 firmware and then flash TWRP recovery with the option: "Install Recovery ramdisk" then select the .img file you downloaded from website. You can also use: Go to Advanced > Flash Current TWRP.
But the problem is: you need to be able to BOOT first into the recovery.
Heck I would try to boot with the a11 twrp right now just to see if it loads instead of using the flash command, if it boots up its a good sign but it probably won't have decryption support, all your files will look like random numbers. Your bootloader is unlocked so common sense dictates it should be able to boot the twrp.
Fastboot boot twrp.img
EDIT: Well I tried to boot unofficial a12 twrp onto my device and it didn't boot into it. So it might not work for you either. I am on stock oos 11 and the a11 version is the only one that boots.
This link might be able to help:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8pro-official-beta-3.4341707/
I noticed at this link, they have different .img files then the official website. Give it a try. They mentioned flashing instead of booting, so it's slightly confusing.

Ok so I tried flashing a boot.img file I extracted from a payload I got from here
OnePlus Android 12 Tracker: Here are all the official OxygenOS 12 builds to download and install
OxygenOS 12 Open Beta builds based on Android 12 have begun rolling out to multiple OnePlus smartphones. Head on over for the download links!
www.xda-developers.com
and now theres a recovery screen:
I tried using format data to see what happens since my important data is already backed up, when i did this my phone rebooted into a setup screen but when i get to the point where i have to setup my network the screen hangs and the phone restarts. Maybe this is because the roms model number doesn't exactly align with my phone?

I got it in twrp!!

Provenscroll said:
I got it in twrp!!
View attachment 5866011
Click to expand...
Click to collapse
Nice work man, what did you do exactly?

immortalwon said:
Nice work man, what did you do exactly?
Click to expand...
Click to collapse
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp

Provenscroll said:
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp
Click to expand...
Click to collapse
Ok I am not sure what you should do at this point: flashing the recovery while in TWRP or simply booting into it future wise. I read on t-mobile devices, if you try to flash it might brick it but I am not sure.