Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Try fastboot getvar all then do fastboot set_active to either a or b depending on which partion you are on you want to change it also pretty sure USB debugging doesn't matter in bootloader you can also try fastboot oem unlock to unlock bootloader to boot twrp unless you updated to oos twrp doesn't work yet
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
JonasHS said:
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
Click to expand...
Click to collapse
With MSM he will get everything wiped on his device. This is not he is intending to do.
AK138 said:
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Click to expand...
Click to collapse
Run fastboot flash recovery twrp.img ... And then fastboot reboot recovery or choose recovery on your phone.
Sometimes holding volume up and power to do a soft reset boots back into system worth a try.
Related
Hello Guys,
I was trying to flash magisk using twrp since i was getting magisk not installed error.
i used this guide https://www.youtube.com/watch?v=NmEzjTG0cTI
As soon as i flashed patched image and tried to boot the phone rebooted and stuck in oem is unlocked.
Now i am unable to boot it in fastboot mode or recovery mode.
I tried all key combos.
even my pc is unable to detect and says the device connected is malfunctioned.
Please help!
Try the msm tool
hiteshredekar said:
unable to boot it in fastboot mode or recovery mode.
Click to expand...
Click to collapse
TWRP: Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead
Unplug Your phone then
turn it off
Manually boot it into recovery by keeping Power + Volume Down button pressed.
manasgirdhar said:
Try the msm tool
Click to expand...
Click to collapse
Does this MSM Tool also work for OnePlus?
To search just with your favorite Search-Engine for this tool is one thing, do you know the link to a trustworthy source?
By the way, I cannot lock my bootloader (just like the OP) and I would like to go back to stock. I found a Video, but it says I need Oxygen OS 4.0.2, if anybody knows where I can get that ?
Zürcher said:
TWRP: Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead
Unplug Your phone then
turn it off
Manually boot it into recovery by keeping Power + Volume Down button pressed.
Does this MSM Tool also work for OnePlus?
To search just with your favorite Search-Engine for this tool is one thing, do you know the link to a trustworthy source?
By the way, I cannot lock my bootloader (just like the OP) and I would like to go back to stock. I found a Video, but it says I need Oxygen OS 4.0.2, if anybody knows where I can get that ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Literally a few threads below this one
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.
ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.
ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.
Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.
So I tried today to install evolution x on my brand new OnePlus 8T and when the installation was over I noticed that my phone would not reboot. When I tried to reboot it myself then it went back to FastBoot.
I tried the "Start" and the "Restart bootloader" options but it didn't work.
I tried the "Power off" option and then restarted it but it went back to FastBoot
I even tried the "Recovery mode" but with every option in it nothing changed. I was either going back to Recovery Mode or to FastBoot
I would really appreciate any help. Please let me know if I can do anything.
You can follow this guide:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Use button combination boot up EDL mode is little tricky. If you can access fastboot, use command "fastboot oem edl" boot EDL.
You may need to install the EDL driver manually, This is very important:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
sfoklus said:
So I tried today to install evolution x on my brand new OnePlus 8T and when the installation was over I noticed that my phone would not reboot. When I tried to reboot it myself then it went back to FastBoot.
I tried the "Start" and the "Restart bootloader" options but it didn't work.
I tried the "Power off" option and then restarted it but it went back to FastBoot
I even tried the "Recovery mode" but with every option in it nothing changed. I was either going back to Recovery Mode or to FastBoot
I would really appreciate any help. Please let me know if I can do anything.
Click to expand...
Click to collapse
I'm assuming you used TWRP from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/ to flash the rom. I'm guessing you forgot to flash the TWRP installer after flashing the rom otherwise you'd be able to get back to TWRP.
Flash the TWRP img file to recovery again while you're in fastboot. That should let you boot into recovery.
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.
and that is the guide ive been following. however i keep getting partition issues.
lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".
okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.
Hi guys,
I think I've tried it all at this point so I'm in need of some help.
I've got the T-Mobile IN2017 version of the OP8. I wanted to get rid of the T-Mobile junk and get access to the "regular" updates.
I started with this guide: [Guide] Convert to Global [WIP]
I got my unlock token today and gave 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT a shot. When it booted into Rescue Mode I assumed something had gone wrong so I told it to wipe everything and I figured I'd start over. I realized this was probably a good thing because I had neglected to backup anything.
I used instantnoodlet_15_O.16_201001 to reset. I couldn't get the volume up + volume down combination to work at all so used adb to reboot in edl. All went well.
I then re-unlocked the bootloader, flash booted into twrp-3.3.1-test10-instantnoodle-unified-mauronofrio.img and made some backups.
I installed the latest Magisk (changing .apk to .zip) within TWRP, and used adb shell to make a backup of my persist.img
I went back to 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT and ran the flash-all.bat but this time it failed and I've found myself bricked: CrashDump Mode.
I've only been able to switch betwen CrashDump Mode, off, and Fastboot. When I'm in Fastboot if I try to start or boot in recovery it just ends up back at CrashDump. If I do a hard power off and try holding volume up + down to get into edl I end up at Fastboot again as soon as I plug the usb in. The commands fastboot reboot edl, fastboot oem edl, and fastboot reboot-edl all give me errors. I can no longer flash boot into TWRP. I've tried flashing the 11.0.0 Global again but I get "Flashing is not allowed for critical partitions" and "partition not found" errors before I end up back at the CrashDump screen.
When in CrashDump it shows up in my device manager as Qualcomm HS-USB Diagnostics 900E (COM13). When I'm in fastboot it appears as OnePlus Android Bootloader Interace. I have uninstalled the drivers and reinstalled the drivers (OnePlus_USB_Drivers_Setup, QDLoader HS-USB Driver_64Bit, androidwinusb). I'm using the latest Platform Tools. I am in test mode and I have turned off driver signature.
I only have two USB 3.0 ports and I don't have access to another Windows PC. I have used three different USB cables, including the OnePlus original, in both ports. I have taken off my phone case to make sure nothing is interfering with me pushing volume up + down. My thumb hurts from pressing it so much. I've done this dozens of times now. No EDL.
I'm at a loss. Someone please help me!
Edit: I've tried using the All-In-One-Tool but it says reboot to EDL doesn't work because I'm in fastboot and trying to boot into the latest twrp still just sends me back to CrashDump.
Solved!
I came across this twrp guide: [TWRP][3.6.0-11-b7][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA] and unlike the other I had used, this one didn't warn against flashing and only booting. I flashed the img for twrp-op8-3.6.0_11-infected-b4 to recovery_a and recovery_b and booted into recovery. At first it just said I was in fastboot, it didn't give me all the usual twrp options, and the only buttons were to reboot and to switch between fastboot and adb (which did nothing, it stayed in fastboot). I tried to reboot to edl and ended up back at the fastboot screen. From here I tried again to boot into recovery and this time I got all the usual twrp options. I rebooted into edl and was able to successfully unbrick with the 10.5.7 MSM. Flashed the global 10.5.7 MSM and I'm set. Updated to A11 and everything is groovy!