Database Info

Stuck at fastboot (rooted) - Need help please

Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA

nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!

Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.

maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png

Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.

zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure

szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.

zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked

szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.

zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!

szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....

Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???

[UnBrick] Flashing Latest Stable ROM using Fastboot Mode

Bricked Device but has unlocked bootloader and having access to Fastboot Mode​
Before doing the process, make sure you have to remove your SdCard and having sufficient battery power to ensure that the process won't be interrupted and to prevent higher chances to hard bricked your device (Dead)
Requirements:
Accessible Fastboot
Unlocked Pocophone F1 Device
Laptop/PC
Type-C Data Cable (Not Charging Cable because it has no data output and input)
Microsoft Visual C++ Redist 2015, 2017 and 2019 (Please report what kind of error you get when flashing and provide a screenshot)
Fastboot ROM updated to 11.0.6.0 (get it here: https://bigota.d.miui.com/V11.0.6.0...M_20200227.0000.00_10.0_global_983cdd2f82.tgz)
Qualcomm Drivers (Search in Google)
Latest Mi Flasher (https://www.xiaomiflash.com/)
7-Zip to extract .tgz file type (This is more efficient and has fewer errors) https://www.7-zip.org/
Patience and Hope
NOTE: FASTBOOT MUST BE ACCESSIBLE, IF NOT, THIS TUTORIAL IS NOT FOR YOU​
{
"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"
}
Code:
While Turned off, Hold POWER + VOL DOWN for a few seconds
1. Install the drivers needed (Qualcomm, Microsoft Redist 2015, 2017 & 2019)
2. Reboot your Laptop/PC to make sure all drivers are working
3. Using 7-Zip, extract the Fastboot ROM (beryllium_global_images...da212305c9.tgz) to any designated directory/folder
4. Open Mi Flasher
5. Click "Browse" and navigate to your extracted folder of Fastboot ROM
6. Select the folder that contains the extracted Fastboot ROM
7. On the bottom right, select "Clean All"
8. Now, reboot your phone to Fastboot Mode
Vol Down + Power Button
Click to expand...
Click to collapse
9. Connect your phone to your Laptop/PC
Mi Flasher should recognize your phone. If not, check your Laptop's/PC's USB Port, it might be broken. Try another port, from USB 3.0 to USB 2.0 If the problem still exists, try reinstalling your drivers. Some users faced problems on AMD system, try it on INTEL based system for more stability.
Click to expand...
Click to collapse
10. After all that, click Flash
The process should take about 5-10 minutes depends on what kind of Laptop/PC you have
Click to expand...
Click to collapse
11. If you see on the results tab "Success", then the flashing is completed
12. Now, try rebooting your device
The booting might take about 5-15 minutes, just be patient
Click to expand...
Click to collapse
Bricked Device but has locked bootloader, you applied for unlocking, and have access to Fastboot Mode
There might be a chance. If you applied for unlocking the bootloader, you can still unlock the bootloader by downloading the Mi Unlock Tool on their website https://en.miui.com/unlock/ and boot to fastboot mode and follow the steps provided on their website.
Bricked Device but has locked bootloader, you didn't apply for unlocking, and having access to Fastboot Mode
Your Device is HARD BRICKED. You cannot Flash your phone with a locked bootloader, if you cannot reboot or your device has bootloop after an OTA update, sideload, etc. you should bring your device via the nearest Xiaomi Service Center for further analysis.
You could do the flashing by using EDL Cable (Deep Flash Cable). Or by Testpoints to access EDL with locked bootloader. Find a guide anywhere in XDA or in YouTube.

Is the EDL mode is the same as fastboot mode? Afaik they're different

DAusRon said:
Is the EDL mode is the same as fastboot mode? Afaik they're different
Click to expand...
Click to collapse
EDL or download mode term is used for samsung devices (uses ODIN). They are alike as fastboot mode (uses flasher e.g MI Flash tool, MTK flasher, qualcomm flasher, etc.)

Edl flashing means using a edl flash cable or hardware test points. It allows to unbrick a corrupted bootloader .

anvesh583 said:
Edl flashing via this method doesn't require permissions or what since I heard edl flashing is locked and requires authentication .
Click to expand...
Click to collapse
Going to edit my post since that someone confuses about EDL and Fastboot.
And yes, only Xiaomi has access to EDL Mode (Emergency Download Mode) to force flash system images or firmware because they are the OEM of the device. Only Fastboot that can user be accessed but it requires an unlocked bootloader.
Theoretically as an user, you can access EDL Mode but it requires such tools and knowledge.

Why when I plugin my phone to miflash it only shows the option to unlock and erase data, rather than the flash function?

pipyakas said:
Why when I plugin my phone to miflash it only shows the option to unlock and erase data, rather than the flash function?
Click to expand...
Click to collapse
Please provide a screenshot so that I can know if what update of Mi Flasher you have

anvesh583 said:
Edl flashing means using a edl flash cable or hardware test points. It allows to unbrick a corrupted bootloader .
Click to expand...
Click to collapse
Darklouis said:
Please provide a screenshot so that I can know if what update of Mi Flasher you have
Click to expand...
Click to collapse
Oh no.. You downloaded Mi Unlocker, not Mi Flasher.
Please search in a MIUI Forum or Google "Mi Flash Tool"

Darklouis said:
Oh no.. You downloaded Mi Unlocker, not Mi Flasher.
Please search in a MIUI Forum or Google "Mi Flash Tool"
Click to expand...
Click to collapse
Ya I figured. The problem though, is that your post is linking to miflash unlock tool while you say you need to download the Flasher
I ended up just googled it and got my flash back to miui successful

pipyakas said:
Ya I figured. The problem though, is that your post is linking to miflash unlock tool while you say you need to download the Flasher
I ended up just googled it and got my flash back to miui successful
Click to expand...
Click to collapse
Sorry, will fix it though.

Wanna thank you for this post first. However I was unable to run the latest MiFlash due the error as seen on screenshot. (Windows 10)
No matter what I was trying to do, MiFlash was still asking to install drivers (including Nvidia drivers, wtf?)
USB drivers were installed correctly as I could see connected device with installed drivers and fastboot devices have also worked fine. I have done several reboots, windows test mode, but without success...
If anybody else is having same issue, I was able to use probably very old version of MiFlash to successfully flash fastboot MIUI image.
Poco F1 again operational

Nexus5-32GB said:
Wanna thank you for this post first. However I was unable to run the latest MiFlash due the error as seen on screenshot. (Windows 10)
No matter what I was trying to do, MiFlash was still asking to install drivers (including Nvidia drivers, wtf?)
USB drivers were installed correctly as I could see connected device with installed drivers and fastboot devices have also worked fine. I have done several reboots, windows test mode, but without success...
If anybody else is having same issue, I was able to use probably very old version of MiFlash to successfully flash fastboot MIUI image.
Poco F1 again operational
Click to expand...
Click to collapse
New and updated Mi Flash Tools needs new drivers (including Visual C++ 2015 or the 2017/2018 one, Microsoft Framework, etc. e.g. just like installing a game, it needs drivers to work)

edl required dfc cable/testpoint and auth mi account, no need ubl,,
and fastboot only need ubl..

Darklouis said:
New and updated Mi Flash Tools needs new drivers (including Visual C++ 2015 or the 2017/2018 one, Microsoft Framework, etc. e.g. just like installing a game, it needs drivers to work)
Click to expand...
Click to collapse
That is correct and I have all of them installed, but still unable to run latest MiFlash properly.

Nexus5-32GB said:
That is correct and I have all of them installed, but still unable to run latest MiFlash properly.
Click to expand...
Click to collapse
Please send me a screencap on the details panel

Darklouis said:
Please send me a screencap on the details panel
Click to expand...
Click to collapse
here you are

Nexus5-32GB said:
here you are
Click to expand...
Click to collapse
Got the exact same problem with new Miflash. Tried the old version but it gives me an error. See screencap. The file it says missing is actually there.

The attachment went wrong. Maybe now
Edit:
Maybe you can see my attachment, ican't i dont get why.
Anyways Miflash sends an error message saying ' can not found file flash_all.bat '
When i open the tar file the flash_all.bat file is there.

pederzen said:
The attachment went wrong. Maybe now
Edit:
Maybe you can see my attachment, ican't i dont get why.
Anyways Miflash sends an error message saying ' can not found file flash_all.bat '
When i open the tar file the flash_all.bat file is there.
Click to expand...
Click to collapse
Bootloader is open but USB debugging was off when the bootloop accured. ADB does not recognise device, older MiFlash does but gives error written above. Any idea how to proceed? Your help is much appreciated

pederzen said:
Bootloader is open but USB debugging was off when the bootloop accured. ADB does not recognise device, older MiFlash does but gives error written above. Any idea how to proceed? Your help is much appreciated
Click to expand...
Click to collapse
Make sure you have the drivers installed.
Check it on "Device Manager" while the device is connected with fastboot mode on.

How To Guide Global/US unbricking guide.

Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"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"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.

Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp

akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!

I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?

panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way

@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks

winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!

I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??

from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!

panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp

winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me

the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.

i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons

papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!

allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx

iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?

OnePlus 8t KB2001 stuck in a loop

I shifted from apple to android recently and I decided to root my device OnePlus 8t KB2001 (I believe I have Android 12) as I wanted to install kali on it. Therefore I decided to follow instructions on this website. I did not type the steps because I did not want to lose out on any key details.
I performed all the steps till here:
I did not perform step 6, instead, I performed step 7 as I wanted to install TWRP Recovery on my phone permanently.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to the instructions I was supposed to boot my device to TWRP. Since I am currently booted to Fastboot, I used the Volume Keys to bring up the Recovery option and hit the Power key to confirm the decision.
As per the instruction as soon as my OnePlus boots to TWRP, it will ask to decrypt data. I was supposed to simply enter my phone’s password/PIN to proceed ahead but this never happened. Instead, I am stuck in a situation where I am seeing the following screen:
I searched every single option and there's no Online Update (keep data) option. I am stuck in this loop for hours. Even the option of formatting data doesn't remove this RECOVERY.
I don't know if this information would help but I can enter the Fastboot Mode by tapping on "Advanced" and selecting "Reboot to fastboot mode".
It would be really helpful if someone can tell me a fix to this problem as I really don't want to throw this phone away as I just got it today.

You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.

I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.

TheNewHEROBRINE said:
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
Click to expand...
Click to collapse
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?

FakeGemstone said:
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
Click to expand...
Click to collapse
Thank you, this really gives me hope that my money will not go to waste. Now I am just in the process of trying to find a solution where I can my make phone the way it was which is without having any TWRP

kooluser said:
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
Click to expand...
Click to collapse
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanism too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.

TheNewHEROBRINE said:
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanisms too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device

kooluser said:
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
Click to expand...
Click to collapse
I'm happy for you too

TheNewHEROBRINE said:
I'm happy for you too
Click to expand...
Click to collapse
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it

Did you flash TWRP after switching slot? If so you should be able to boot into it by holding power and volume down while turning the phone on.

Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?

kooluser said:
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
Click to expand...
Click to collapse
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.

TheNewHEROBRINE said:
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
Click to expand...
Click to collapse
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone

kooluser said:
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
Click to expand...
Click to collapse
It's not a problem to have TWRP installed.

TheNewHEROBRINE said:
It's not a problem to have TWRP installed.
Click to expand...
Click to collapse
Thank you so much for helping me and solving all my queries

kooluser said:
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Click to expand...
Click to collapse
You can install magisk from TWRP recovery.
Changing slots is also possible there.

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.