After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!
Related
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
The idea is to boot it in download mode. You'll need the Qualcomm drivers, msm download tool, and oos full rom. Run the tool as administrator.
Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Fastboot require Android SDK(Software Development Kit) and different USB drivers for windows computer may be that's the reason why your Fastboot is not working.
To Root your oneplus 6 :
https://www.theandroidsoul.com/oneplus-6-root/
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Pipp8888 said:
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Click to expand...
Click to collapse
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
thejase said:
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
Click to expand...
Click to collapse
How can I uninstall the old drivers? Thanks
Pipp8888 said:
How can I uninstall the old drivers? Thanks
Click to expand...
Click to collapse
https://www.drivethelife.com/window...remove-driver-on-windows-10-8-7-xp-vista.html
i unistalled all drivers with Driver Takent. The only driver detected is ADB whem i connect the phone. The Device Manager still recognise my phone in the Usb Devices section as "OnePlus" and still doesn't let me upgrade to the qualcomm drivers.
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Pipp8888 said:
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Click to expand...
Click to collapse
If it works, yes ofc.
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you
marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?
These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view
not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.
I have made huge mistake and i dont know what to do and would really appreciate some help. I was on Open Beta 17 with magisk and twrp and i decided i wanted to revert the stock using msmtool. I have used it before so i know about all the drivers to install and how to get to edl and so on. So i started the msm software and hit start, but a few seconds into the flash i got the an error "firehosewritedata failed" and since then my device cant be recognised by my computer and its not booting up or even showing that its charging. I tried reinstalling the drivers and trying msmtool but the device isnt recognised at all.
Booting into fastboot only says Update download failed please check your download flow is right
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Use a USB 2.0 port.
amirage said:
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Click to expand...
Click to collapse
MrSteelX said:
Use a USB 2.0 port.
Click to expand...
Click to collapse
Thank you for the feedback, and the late reply. I eventually reinstalled all oneplus drivers again and put windows to debugging mode and tried one more msmtool flash, and after a lot of praying and swearing it finally flashed successfully. For future reference, windows debugging mode is a good place to be in for doing these flashes or to ensure no fails.
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com