Database Info

Is my stock phone bricked?

It's a stock phone, unrooted bootloader locked. The phone was updated to the latest firmware a few days ago and was working well since.
Today I left the phone on the desk for a while. When I came back, the phone had rebooted and was in the fastboot mode screen.
I tried to restart but it just loops back to same screen. Does not even go into recovery!!
What snapped it, cant understand!
Is it bricked? How do I revive the phone now?
Please help!
Thanks

Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/

sms2000 said:
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
Click to expand...
Click to collapse
Do I also need to flash stock recovery from fastboot?
Thanks again.

observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
No, recovery is part of the ROM, so not needed.

If it's a completely stock device, why not contact OnePlus and get a replacement?

Are you guys suggesting ADB sideload command? My USB debugging seems to be off, returns empty on "adb devices"
I am unaware of fastboot command to flash the stock rom, googled it but could not figure out the right command.
Thanks

maigre said:
If it's a completely stock device, why not contact OnePlus and get a replacement?
Click to expand...
Click to collapse
That's right.
If am not able to fix it myself with members help, I'll have to go through customer support drill.

observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

jerrywmilton said:
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now

observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
Fingers crossed mate! Hope you get it right!

observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
yeah, I was gonna say....just follow directions carefully....it works....same set up has been working for years for each different model.

Thanks to each one of you.
The issue is resolved
I used the unbrick tool i.e. MSMDownloadTool to fix the problem. Hope it does hot happen again!
Thanks

[HELP] Bricked Oneplus 6 - Qualcomm CrashDump - already tried everything

Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.

Did you try msm download tool? If not, nead that thread and good luck

whizeguy said:
Did you try msm download tool? If not, nead that thread and good luck
Click to expand...
Click to collapse
Hi!
Thanks for your reply, but I think you do not read my entire post
As I said, i've already tried at least 8 different versions of msmDownloadTool.
If you have any other suggestion, I'll appreciate.

so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot

EarthquakeXS said:
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
Click to expand...
Click to collapse
Yes, I am unable to enter into Fastboot Mode.
When I try, the logo saying "fastboot" appears, but after 4 seconds, the systems stucks on CrashDump error screen again.
That way my PC cannot find my phone with ADB or FASTBOOT commands.
The only tool that works is msmDownloadTool, but even with a success run with that tool, my system does not start and stills under CrashDump error.
I was thinking if exists some version of msmDownloadTool that justs restore the fastboot and unlock bootloader with brute force.
Thats my last hope

hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!

sanaulla jauhar said:
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
Click to expand...
Click to collapse
Hi!
Can you please provide some link to this tool?
Thanks for your help!

mikesmarcos said:
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Click to expand...
Click to collapse
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?

Hi dude are u here ? i will help u

Try this
Rhach1d237 said:
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Click to expand...
Click to collapse
Source is a videotutorial. google oneplus 6 hardbrick and click the video of Max Lee
(it worked for me)
the download takes an awful lot of time
first get your phone into qualcomm download mode by holding down volume up + power button and plug your device in your PC.
(first unzip the hardbrick zip folder) then the oneplus 6 folder and than the .exe file and click 'start' if it detects your phone.
That is flashing every chip and Hydrogen OS 5.whatever.3 but that is not important. Your phone should boot and than you can install Oxygen OS with android 10(thats the other zip folder) using the local upgrade feature.
(make sure to enable google play services after upgrade from hydrogen OS)
Hope it will work for you too if you haven't tried it already.

failed root fastboot only help please

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.

Fastboot waiting for any device

Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.

A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!

Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!

Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com

This is installed and works with me

ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.

Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror

Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?

ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.

This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.

fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.

Oneplus 8T stuck in Qualcomm CrashDump mode

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!