Bricked my phone... Can only boot into fastboot, and cannot connect to msm tool. Please help. This is the first time in 12 years of tinkering I have ever turned a phone into a paperweight
kinkoff85 said:
Bricked my phone... Can only boot into fastboot, and cannot connect to msm tool. Please help. This is the first time in 12 years of tinkering I have ever turned a phone into a paperweight
Click to expand...
Click to collapse
The MSM tool thread has everything you need and the instructions in the OP are very good.
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
PS: if you can get into bootloader, then your phone is obviously not bricked.
It won't go
BillGoss said:
The MSM tool thread has everything you need and the instructions in the OP are very good.
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
PS: if you can get into bootloader, then your phone is obviously not bricked.
Click to expand...
Click to collapse
It won't load anything but fastboot
If phone won't connect in EDL try using different usb port on your pc. Works a lot of the time.
Have you disabled the driver signature, are you have the latest Qualcomm drivers and the latest OnePlus drivers ?
kinkoff85 said:
It won't go
It won't load anything but fastboot
Click to expand...
Click to collapse
We can't see your phone or what you've done unless you tell us. Why don't you describe in detail what you did and what happened.
BillGoss said:
We can't see your phone or what you've done unless you tell us. Why don't you describe in detail what you did and what happened.
Click to expand...
Click to collapse
I tried flashing a custom ROM based off Pixel and android 12... It rebooted and went straight to fastboot and that's the only place it will go is fastboot. I later read that rom was not compatible with the 8t only the 8 and 8pro. Whenever I try to connect it with MSM TOOL it simply reboots right back into fastboot. I do have TWRP recovery installed but cannot figure how to flash or side load from there either. I've tried over and over.
When you're in fastboot, flash TWRP and then boot into recovery.
BillGoss said:
When you're in fastboot, flash TWRP and then boot into recovery.
Click to expand...
Click to collapse
There is nothing to flash once in recovery.
You'll have to format data (wipe>format data: type 'yes') and then sideloaded what you want to flash.
Try these fixes mentioned in these videos
and
especially the tips from the second video, helped me once I couldn't get into edl mode.
Related
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.
I'm really new to all of this so sorry for the ignorance. I'm trying to revert my OP8T KB2003 back to OxygenOS and get rid of Lineage and TWRP. Can't seem to find a proper tutorial on how to do that. Any help would be greatly appreciated.
You can revert via MSM tool.
Rootk1t said:
You can revert via MSM
Click to expand...
Click to collapse
Thanks for the reply. So I tried the different firmware and followed the instructions, but it doesn't seem to be able to pick up the phone. I'm holding down both volume buttons for a few seconds before plugging it in. Does the bootloader being unlocked have something to do with it? If so i'm unsure how to lock it again.
rando_lando said:
Thanks for the reply. So I tried the different firmware and followed the instructions, but it doesn't seem to be able to pick up the phone. I'm holding down both volume buttons for a few seconds before plugging it in. Does the bootloader being unlocked have something to do with it? If so i'm unsure how to lock it again.
Click to expand...
Click to collapse
Does the phone show in device manager as Qualcomm HS-USB QDLoader 9008?
If yes, try entering edl mode again.
If no, you need to install the Qualcomm drivers.
Rootk1t said:
Does the phone show in device manager as Qualcomm HS-USB QDLoader 9008?
If yes, try entering edl mode again.
If no, you need to install the Qualcomm drivers.
Click to expand...
Click to collapse
It shows up as QUSB_BULK How would I go about installing the drivers?
I also wasnt able to start the MSM Tool with pushing Buttons. If drivers are correct you should Google Boot edl Mode via ADB command. This worked for me.
There is a good thread in the "guide" section that could make it alot easier for you.
[ROM][STOCK][FASTBOOT] Stock OxygenOS Fastboot ROMs For OnePlus 8T
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you 😉. I have extracted all images from the stock zip...
forum.xda-developers.com
I'm also trying to get back to oos from derp. Can't I just use the flashable beta zips using twrp and then format data?
I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
aIecxs said:
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Click to expand...
Click to collapse
Does the fact that I can communicate and flash via Download Mode (SP Flash Tool) mean that I didn't lose my preloader? I'm kinda stuck trying to flash the Stock ROM (demanding verified image files, even though I'm using the original firmware for flashing... probably)
Lada333 said:
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
Click to expand...
Click to collapse
I'll check the guides online, hopefully I'll find one that'll help.
mouradsme said:
demanding verified image files, even though I'm using the original firmware for flashing
Click to expand...
Click to collapse
I've also had issues previously with trying to flash stock images on Samsung phones. Not sure if you have country-specific images, if you do, try giving all of them a shot. I'm from Hungary, and a locally bought Samsung phone only came to life after flashing a Spanish factory image.
you need to (by)pass SLA/DAA authentication
Now I managed to bypass protection, and got the successful flash message from SP Flash Tool.
But I still can't solve the issue (Phone still only responsive from BROM)
For reference I'm using the global version of RMX3171 (Realme Narzo 30A) based on MT6768, and the Stock ROM is available online.
I flashed every partition (Provided in the Stock ROM), and Now it is booting, showing the logo + a message "Download not completed Error Code 0x992566 " and then it reboots after a minute or so -_-
I think that means you did not flash all partitions (some not included in Download)
In the other thread someone mentioned "Format All + Download" very bad idea never do this.
did you try unlocking bootloader from mtkclient like suggested in that thread?
mouradsme said:
Hello,
Can someone share their nvdata & nvram + oppo_custom?
I seem to have formatted mine, and need them to recover my Narzo 30A.
Click to expand...
Click to collapse
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
aIecxs said:
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
Click to expand...
Click to collapse
I came across the tool, but I failed to enter into Meta Mode.
I'm trying to make my phone boot to the system, then I'll try restoring my IMEI's using MTK Engineering app.
Thanks for links though
mouradsme said:
I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
Click to expand...
Click to collapse
There is no such thing as a "hard bricked" device that can still boot into TWRP. A hard bricked device is completely dead and shows no kind of activity or function. It won't charge, it won't boot into any kind of mode and can't make a connection to PC, makes no sound when connecting to PC and it won't appear in device manager when connected to PC.
A device that can boot into download mode but not its other modes is just a softbricked device.
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
Using my old OnePlus 8T I was able to unlock, root and install a custom kernel.
Any ideas?
shadowofdeth said:
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
the good news is your phone can very likely be fixed. however in my experience you will need a computer. Folks here would love to help but knowing what device you are having an issue with would probably help with response to your situation. from fastboot you can boot a recovery image for your device and go from there. from fastboot you can also likely flash stock firmware to your device and start over fresh. It's also common to have to perform a factory reset after flashing the device to get it to properly boot.
Click to expand...
Click to collapse
OnePlus 9.
I tried searching but there are so many dead ends for finding the stock recovery. Even with that I'd still be bricked.
Where would one find the stock recovery, kernel and fastboot ready update.zip?
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
MrSteelX said:
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
Click to expand...
Click to collapse
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
shadowofdeth said:
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
Click to expand...
Click to collapse
borrow a laptop from someone , use the msm tool
taintsx said:
borrow a laptop from someone , use the msm tool
Click to expand...
Click to collapse
Im so close I can smell it now. Managed to get Python installed (had to deep dive into the comments on articles and tutorials) and have everything extracted in the last hour.
Now, for flashing these images I have to use Termux and it's working for the most part. My issue is now that I can flash one batch of images but not the other as per the xda guide linked now:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
I keep getting errors about the partition being locked or something.
So close man. So close.
Locked partitions can only be flashed in fastbootd (fastboot reboot fastboot to get there).
First of all... Hold the both volume and power button for around 2 minutes. It'll take you to the bootloader mode. Then from the bootloader mode turn off your device then boot into edl then flash with msm.
Lesson learned
Hi,
After updating my OnePlus Nord (EU) to OxygenOS 12 and noticing how full of bugs it is, I've decided to flash PixelExperience on it.
I followed the official PixelExperience install guide: I successfully unlocked my bootloader, and then went ahead to flash the recovery.
Exactly as written in the guide, I performed a fastboot flash recovery recovery.img.
The command finished as expected without any errors, so I rebooted into the recovery with fastboot reboot recovery, only to get an error screen, with a title in Chinese and an error message: "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.", so my device got soft-bricked.
I tried flashing it again - didn't work.
So I tried flashing TWRP - also didn't work.
I tried to flash a stock recovery from this thread - also didn't work.
I at least tried to recover it back to stock, so I downloaded the MSM tool and Qualcomm drivers and tried to get my device into Qualcomm EDL mode.
I tried many combinations of button pressings, I tried fastboot oem edl, but I just couldn't get it into EDL mode, it just booted into fastboot every time.
How could I fix this - flashing a recovery or at least revert it back to stock?
Bro, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works
krish-ag said:
Oo, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works
Click to expand...
Click to collapse
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?
AmitGold said:
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?
Click to expand...
Click to collapse
In edl mode, u will not see anything on the phone screen.
To use edl mode, press vol up and down simultaneously (without power botton) for 10 secs and then connect it to pc via usb cable
Then u will hv to use the MSM tool according to ur nation (like India, EU etc) for a specific OOS version
Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times
AmitGold said:
Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times
Click to expand...
Click to collapse
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..
krish-ag said:
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..
Click to expand...
Click to collapse
Tried that also... Didn't work
AmitGold said:
Tried that also... Didn't work
Click to expand...
Click to collapse
did it just reboot or boot into bootloader again?
Also can u share a recorded video of the process i hv told u?
It booted into the bootloader.
Attaching a video of this process
Bro first thing, it should be of 10 secs not 30. I m pretty sure that's what preventing to to boot to edl
Second, i want a video of those adb method steps that i told u but now first try ur method only but for 10 secs
AmitGold said:
It booted into the bootloader.
Attaching a video of this process
Click to expand...
Click to collapse
I have the same issue, did you fix that?
Use a USB2 port if not already obvious. (I fought getting into EDL mode for hours the first time - maybe you already know this, sorry if redundant. 10 seconds, 40 seconds, doesn't matter, adl, fastboot, key presses - everyone focuses on the that. Finally with red cable and USB-2 port, it works easily.)