Dead Oneplus 7pro data recovery - OnePlus 7 Pro Questions & Answers

Hii My oneplus 7 pro get dead… blackout while using and battery life is very good never faced problem, it is on 65% while dead. Now nothing is working it is not powering ON, no volume up + power, volume down + power, all three together. But nothing is working. I also tried keep my phone charging full night. My charger is OK. But it also not worked.
i visited oneplus store, they told me first they update software then they will check if there is any internal hardware malfunction. So i took my mobile back. Because I don’t want to loose my important data of last two years, it have my experiments, my future projects, my btc mobile wallets, and photos and videos.
is there anyway to recover my data?
after software update can i recover my data?
I tried everything, dogphone toolkit, drfone. But they don’t have option for oneplus 7 pro?
so please help and suggest what to do to recover my data. Or is there chances to recover my data after flashing ROM?

First to plug it to PC and see how PC recognize it. Android device or qualcomm device or oneplus 7pro... I have heard these variations.

hkdoublecat said:
First to plug it to PC and see how PC recognize it. Android device or qualcomm device or oneplus 7pro... I have heard these variations.
Click to expand...
Click to collapse
It recognize by USD, tried flashing ROM also not worked, so now it’s submitted to service center, they are also not able to flash ROM, so have some hardware issues. Now they will charge me 25000rs for motherboard after 2-3 days they will call and inform that motherboard need to be replaced.

Akky272727 said:
It recognize by USD, tried flashing ROM also not worked, so now it’s submitted to service center, they are also not able to flash ROM, so have some hardware issues. Now they will charge me 25000rs for motherboard after 2-3 days they will call and inform that motherboard need to be replaced.
Click to expand...
Click to collapse
I searched all over with the forensic data expert, but there is no chances of data recovery.. if oneplus 7 pro is totally dead, even taking out EMMC will also not help to recover data. So finally i lost my data, without any damages this phone dead totally. Now i am thinking how oneplus phones are said best in market.

Akky272727 said:
It recognize by USD, tried flashing ROM also not worked, so now it’s submitted to service center, they are also not able to flash ROM, so have some hardware issues. Now they will charge me 25000rs for motherboard after 2-3 days they will call and inform that motherboard need to be replaced.
Click to expand...
Click to collapse
I faced same problem. Phone just died and nothing I could do to recover anything. At least I was under warranty. But I really hope it wont happen again.

Related

OnePlus One super hard bricked?

Hello, I was flashing cm-11.0-XNF9XBS28K-bacon-signed on my opo and something went wrong on recovery, it was like rom flashing went wrong and it didn't happen, so I went to wipe and I'm pretty sure that I selected everything in wipe section, literally everything and hit the reboot button, and my phone won't wake up, no response, tried to press buttons in every combinations for maybe 1 min? My computer won't recognize my phone, nothing happens, no vibration, no sound ;x I think I erased everything, but is it possible to delete bootloader that way? Btw my battery was charged to about 90%.
I tried charging in for about 14hs and nothing happened, phone and charger during this time were cold. I tried to recognize it by Windows 10/XP and Ubuntu but no reponse from phone, so I coulnd't use this magical method with qualcomm port and drivers, and then this Color. Is it really bad hardware brick?
Have you tried this thread by any chance? Hopefully it works. Worked for me when I bricked mine by flashing hydrogen
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
I tried, but my PC can't detect my phone in any state.
latuch91 said:
I tried, but my PC can't detect my phone in any state.
Click to expand...
Click to collapse
Can you try long pressing the power button for 10 seconds or more to turn it off. Then long press the power button and connect to a PC and see if it responds
Sent from my A0001 using Tapatalk
Ok I will try, but I tried before some combinations with buttons and connecting to PC, now I'm testing "dead battery" so 12hrs without touching and 6 hrs charging and then unplug and plug again. But I'm almost convinced that it's something with mainboard I talked to OP and they said that they will exchange my phone If it happened during flashing Cyanogen ROM.
//Still no respond from the PC and phone. Completely dead.
Dont worry, they wont know u had twrp if the phone is hard bricked. Just carry on your RMA process. Good luck...
Today's remote session went as I thought will be, did almost everything as this technician. Now awaiting RMA ticket.
latuch91 said:
Today's remote session went as I thought will be, did almost everything as this technician. Now awaiting RMA ticket.
Click to expand...
Click to collapse
hello i hard bricked my opo two days ago but its ok now plz follow this
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
malikzafar said:
hello i hard bricked my opo two days ago but its ok now plz follow this
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
:good: Used this thread twice now and it saved my phone. Give it a shot.

Huawei Mate 8 supposedly hard bricked (SOLVED)

Okay, I leave here my story in case some other unlucky owner pass the same problem.
I have the NXT-DL00 model, one day, I finished recharging the device, made a cache and garbage cleaning, I selected reset the machine and....nothing, I pressed the power to turn it on again, nothing. No combination of buttons worked, no sign to put it back on the charger, no sign on the PC only as unrecognized USB or a device called "SER COM HSILICON". That is, my phone was dead, but also have a Xiaomi redmi Note 3 Pro, did not care much and would send him back to China by the warranty. But ... the luck was not good girl and my Xiaomi had the SAME problem, the solution I found involved to force a reset on the device connecting two points on the motherboard, but make sure that it was not a hardware problem, I preferred to just disconnect the battery cables and the USB, voila, the device simply returned to life as before and had no longer such a problem, then by removing assumptions and a little brain, it was not hard to imagine that Huawei was the SAME problem. I bought the key proper Torx for him, open the machine and did the same thing, disconnected all the cables and waited about 5 minutes. Well, just as the Xiaomi, Huawei rise from the dead.
Your Huawei got shocked
bluheart said:
Your Huawei got shocked
Click to expand...
Click to collapse
Hahaha, indeed, but it was resurrected. :laugh:
Cool had tried those hardware things years back
It's a good share

Zenfone 6 stays black after EDL Mode

Hi!
TL,DR:
Phone froze while using, and it kept freezing. Now phone wont boot at all, only EDL Mode works. However, after EDL phone wont still boot.
Longer story:
I've got quite a problem here. I was playing Pokemon GO with my friend yesterday. Suddenly my phone went quiet. I saw PoGo froze for 5 seconds and then phone rebooted itself. It went back to LineageOS (17.1) which I've installed successfully via TWRP. Then the phone rebooted itself again many times again and again, and each time it crashed earlier than before. When LineageOS did fail for booting for several times, the phone went straight to bootloader. I tried to open recovery but it crashed too. Then It came back to bootloader and I said Power Off.
I waited for half an hour but the phone was failing boot. It wen't even worse: the phone wont go to bootloader any longer, it just stays black.
I've done an EDL Mode recovery couple of times before when I was messing around my first custom ROM installation with Lineage. Now when I set the phone to EDL Mode via cable I made (it was an easy task) I can hear Windows detecting my phone (which it didn't detect before) and uses the QDLoader 9008 EDL Driver.
Then I use the "update_image_EDL.bat" to regenerate the partitions.
Now here's the tricky part: After the .bat file the phone should reboot to bootloader, however this doesn't happen, and the phone just exits ELD mode (I can hear it from Windows it doesn't detect the phone anymore) and then just stays black. It doesn't react to any buttons or cables, and Im also sure it has battery. I even opened the case and removed the battery from its port and putting it back to see if the phone reacts then my actions, but no.
It feels like the only thing I can do here is the ELD mode. I tried it several times later, and that's all.
Also trying to continue with the instructions with QDLoader 9008 fix (the flashall_AFT.cmd) won't lead anywhere, because Windows doesn't detect the phone after that.
Thank you in advance for any tips and tricks.
Edit: Just to add; I've tried removing SDcard and SIM cards also. No effect.
Edit2: Here's the copy of the 'update_install_EDL.bat' results: https: //paste.ofcode.org/bPLQA6T484rKEEb2URa8yv
After more failed tries and thinking, my friend was looking at my log from update_install_EDL.bat he was thinking about the warning it gave. Well, I went looking for the sector limit which was put by rawprogram4.xml and I added the missing sector to the count. Now the error is missing from log but it went nowhere in the progress however. I've done the .bat now many times, but nothing seems to be working. I've removed the battery and put it back before edl and after edl and tried booting with just the powerbutton and with the Vol+ and power btn, but nothing comes up.
If you got a log from the update_install_EDL.bat, I'd appreciate if you could post it somewhere for me to see did you get the same warning as I did.
I also want to point out that ANY comment is welcome... I keep you posted whenever theres some progress.
Okay. I decided to take my Zenfone 6 to Asus authorized repair shop. They said I've got short circuit in the motherboard. God knows how that happened. However I can't get it under the warranty because earlier I repaired my broken screen glass in a unauthorized repair shop. which has voided the warranty. Asus told me that the repair would cost me 527,2 EUR (624,30 USD). I'll not be paying that much for a repair, so it looks like Im out of the business..
I also want to note that I purchased the phone 4.6.2020 and it was in the screen repair for 30 days. So with my quick calculations I paid totally 12 eur for each day I had a chance to use it.
Edit: I want to say here that the repair shop takes 60€ (71 USD) for their excellent service. Okay, I admit that they we're quick on the result, for about 30 hours they responded, but ofc I'd like to have more info but they told the phone must be taken to the ASUS factory then.
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
abx12 said:
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Click to expand...
Click to collapse
Yeah Im sorry for the log. The warning on there was basicly telling that the bios.img is larger by one sector than the sector size given to the update_install_edl.bat. It was fixed by adding the one sector to the rawprogram4.xml file.
I was aware of the sahara fail, it was fixed by unplugging the cable and back in (restarting the edl mode ofc). And I also tried another cable.
What comes to the directory (folder) names I was aware of that too, the script don't do a very good job with folders having spaces or special letters.
homerlovesbeer said:
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
Click to expand...
Click to collapse
My working theory is that this high failure rate is affecting all of series so they have no way to determine which units should be fixed/replaced. It's very sketchy but they've put themselves into this situation with poor QC in the first place.

OnePlus 6 crash dump - multiple users facing crashdump mode issue in past two months

So I've been using my OnePlus for about 2 years. The phone was kept in a rugged armor case, never dropped nor was it ever exposed to any sort of moisture. The device was never rooted nor was the bootloader ever unlocked.
At the end of August 2020 last month I was using maps when it suddenly crashed and went into Qualcomm Crashdump mode. I thought not a big deal, xda would have a fix to this.
I came home and for two weeks I tried different builds of the msmdownload tool with different methods to revive the phone. None of them worked. The 9.0 build did end up booting the phone but only for a short while before it got stuck, shut off and went into crash dump mode again. I can only boot into fastboot mode and that only sometimes (ofc EDL mode as well).
Fed up, I contacted OnePlus and scheduled a remote session with them. As was no surprise they used the msmdownload tool as well (build 10.3.0). And it obviously did not work and adviced me to visit the nearest support center. Unfortunately there is no service center nearby in my country so I dug deeper trying to find people with similar issue. Now this is the funny part.
On the brands own community app I found 5-6 other people who faced the exact same issue. They tried everything and when nothing worked they eventually went to the service center and were told that apparently the motherboard needs to be changed and it will cost as much as the phones value in today's date. Here's the interesting fact. All these 6 users were on the latest OOS 10.3.5 and faced this issue in the span of those 4 weeks. August to September of 2020.
The purpose of this thread:
1) To diagnose the issue with the help of the xda community as I believe that there is no way that the mobo could get fried this way.
2) To possibly find a solution as the phone is in absolute scratch less condition.
3) and most important, to find other people than those 6 who have faced this exact issue in the past couple of months so that it could be raised with OnePlus. Im hoping that OnePlus could at least diagnose it and release a tool for the fix if there are enough of us. Wishful thinking maybe but worth a shot.
Hoping for your support. Peace.
Guess what might be 7th person. My oneplus 6 keeps shutting down all of a sudden and some times even wont start or something might start but again goes off while booting. So, then i have to start it after 10 mins and so and start it again and that too wait for 5 to 10 mins after starting before start using it or else it goes off again. Cant use it for heavy usage any more like before. Sometimes even turns off all of sudden. i have used all msm tools to reinstall but no use. Funny thing is while evening setting up the phone after flashing it goes off. Dont no if its hardware problem or not. I also have not dropped my phone.. Can any one find whats the problem?
@ms2020 has the same exact problem as you describe here but on 6t. We did all we could. I even tagged osmosis and he said if msm tool won't work then unfortunately it's a no go...
Same problem here. I have two OnePlus 6. One has OOS 10.3.5 with a locked bootloader, the other one has a custom rom.
6 weeks ago I was using google chrome on the one with OOS and suddenly the phone froze for few seconds and went to crash dump mode. I tried every msm tools version and every suggestions I found, but none of them worked.
The one with custom rom hasn't had any problem so far.
flash713 said:
@ms2020 has the same exact problem as you describe here but on 6t. We did all we could. I even tagged osmosis and he said if msm tool won't work then unfortunately it's a no go...
Click to expand...
Click to collapse
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
yawarkhalid said:
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
Click to expand...
Click to collapse
I think it was around August 19th or 20th.
yawarkhalid said:
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
Click to expand...
Click to collapse
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me. ?
Are you thinking it was something in an OOS update? Possibly?
flash713 said:
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me.
Are you thinking it was something in an OOS update? Possibly?
Click to expand...
Click to collapse
Whaaat, my OP 6 also went to crashdump mode like 2 or 3 times but got rebooted automatically soon after, never happened since.This was also around the time of August. man the part where you told abt your nexus 6p, it hit me. I also had the 6p and it suffered the same fate, sadly there was no support for the phone where i live and it's just lying dead in my drawer ever since. Just hope this doesn't happen again...
flash713 said:
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me.
Are you thinking it was something in an OOS update? Possibly?
Click to expand...
Click to collapse
It's obviously a software issue after the latest update. My phone was never once dropped or exposed to moisture or charged with anything except the in box charger in the one year. There is no possiblity that mine was a hardware issue as OP suggests.
Sidenote: was any of your phones at less than 10% of storage remaining? My phone was below 10% odlf storage.
Also confirm your storage? 6/64 or 6/128? Mine was 6/64.
I have a similar problem, my OnePlus 6 is sometimes just freezing in the system, then shuts down and goes to CrashDump mode. I have this problem since half a year. Sometimes it just reboots normally.
What I also notices: When my phone shuts down because of low battery and I plug it in, it should enter the charging mode, where it shows the battery percentage and some animation, but mine goes into CrashDump Mode.
flo071 said:
I have a similar problem, my OnePlus 6 is sometimes just freezing in the system, then shuts down and goes to CrashDump mode. I have this problem since half a year. Sometimes it just reboots normally.
What I also notices: When my phone shuts down because of low battery and I plug it in, it should enter the charging mode, where it shows the battery percentage and some animation, but mine goes into CrashDump Mode.
Click to expand...
Click to collapse
I had my 6t do same thing! Low battery, plugged it in and went to crash dump. When I get low battery again I'm going to see if I can make it do it again. I hope OnePlus can hook us up with a fix before more of our devices end up needing work done on them and are not able to be used because of it. So far I've been lucky enough to always get out of crash dump my holding volume +&- button and power down until I see fastboot screen and releasing then at bootloader screen just hit power and I reboot back in to system.
Op has gotta be right about this being software issue. I'm going to roll back on msm tool to a previous OOS. When I update from 9xx I'll stop a few OOS's before 10.3.5 and see if any of this occurs while on an earlier version of OOS. Worth a shot. I'll report back in this same post in a few days as to what OOS I'm on and if I have this low battery plug in crash dump or crash dump any other way.
flash713 said:
I had my 6t do same thing! Low battery, plugged it in and went to crash dump. When I get low battery again I'm going to see if I can make it do it again. I hope OnePlus can hook us up with a fix before more of our devices end up needing work done on them and are not able to be used because of it. So far I've been lucky enough to always get out of crash dump my holding volume +&- button and power down until I see fastboot screen and releasing then at bootloader screen just hit power and I reboot back in to system.
Op has gotta be right about this being software issue. I'm going to roll back on msm tool to a previous OOS. When I update from 9xx I'll stop a few OOS's before 10.3.5 and see if any of this occurs while on an earlier version of OOS. Worth a shot. I'll report back in this same post in a few days as to what OOS I'm on and if I have this low battery plug in crash dump or crash dump any other way.
Click to expand...
Click to collapse
Any update??
yawarkhalid said:
Any update??
Click to expand...
Click to collapse
Just had another crash dump and "Attecomp" below where it said crash dump. My device is a T-Mobile model that's been converted to Global. Since I started flashing roms back in the Nexus S days I've always kept dev options on and usb debugging checked... Currently flashing OOS in twrp. Will report back if I boot up to system or whatever happens. I do know I had 65-70% battery when this happened. I was on Pixen Android 11 with no extra mods or anything installed at the time.
Six or seven times previous I've always been able to manually do the button press , enter fastboot mode, hit power and I would boot system. This time when I did that and it looped around back to crash dump mode again. So I manually booted twrp and waiting for it to finish flashing now... Fingers crossed. ?
I'm good. I did a clean twrp install of latest OOS 10.3.6, Corvus and finalize, formatted data and im back booted up now and setting up phone.
flash713 said:
Just had another crash dump and "Attecomp" below where it said crash dump. My device is a T-Mobile model that's been converted to Global. Since I started flashing roms back in the Nexus S days I've always kept dev options on and usb debugging checked... Currently flashing OOS in twrp. Will report back if I boot up to system or whatever happens. I do know I had 65-70% battery when this happened. I was on Pixen Android 11 with no extra mods or anything installed at the time.
Six or seven times previous I've always been able to manually do the button press , enter fastboot mode, hit power and I would boot system. This time when I did that and it looped around back to crash dump mode again. So I manually booted twrp and waiting for it to finish flashing now... Fingers crossed.
I'm good. I did a clean twrp install of latest OOS 10.3.6, Corvus and finalize, formatted data and im back booted up now and setting up phone.
Click to expand...
Click to collapse
So this is the update. A person in my town had the same issue. Went to a local repair shop. They informed that its an issue of the IC. I think its jargon for the mobo in the local market. So they repaired his "IC" and apparently his phone is running fine now. Costed about 40USD. Will take it to them in a few days and report back. Still cant understand how its a hardware issue though.
yawarkhalid said:
Any update??
Click to expand...
Click to collapse
Just read that crash dump happens due to a kernel issue on OnePlus 6/6t. Read that on a telegram group.
Also see this for details: https://github.com/Ashutosh-s-Test-...mmit/a7611e75d6b4262b22475e0e12a9ecf84cf5e443
This must mean that this is one way that crash dump occurs. Because not all crash dumps are the same. If so then how come I've been there 7-8 times and always gotten back to a working device by going to fastboot mode manually and rebooting system.
And some people are stuck in crash dump and cannot do anything about it.
Every time I've been to crash dump mode I could always do the manual button press to enter fastboot mode and then hot exit that and reboot system by selecting "start " using power button when it's at the bootloader mode. Except yesterday...
Yesterday I had just installed OOS and Pixen 11 and booted system and setup my phone. All was good and my battery was at 55%. Then I booted twrp to flash magisk debug for root and instead of rebooting system like I selected from twrp it went to crash dump and when I tried the usual solution instead of rebooting to system it looped around right back to crash dump again. I booted twrp and installed OOS + Corvus and formatted data and booted fine. ?
yawarkhalid said:
So I've been using my OnePlus for about 2 years. The phone was kept in a rugged armor case, never dropped nor was it ever exposed to any sort of moisture. The device was never rooted nor was the bootloader ever unlocked.
At the end of August 2020 last month I was using maps when it suddenly crashed and went into Qualcomm Crashdump mode. I thought not a big deal, xda would have a fix to this.
I came home and for two weeks I tried different builds of the msmdownload tool with different methods to revive the phone. None of them worked. The 9.0 build did end up booting the phone but only for a short while before it got stuck, shut off and went into crash dump mode again. I can only boot into fastboot mode and that only sometimes (ofc EDL mode as well).
Fed up, I contacted OnePlus and scheduled a remote session with them. As was no surprise they used the msmdownload tool as well (build 10.3.0). And it obviously did not work and adviced me to visit the nearest support center. Unfortunately there is no service center nearby in my country so I dug deeper trying to find people with similar issue. Now this is the funny part.
On the brands own community app I found 5-6 other people who faced the exact same issue. They tried everything and when nothing worked they eventually went to the service center and were told that apparently the motherboard needs to be changed and it will cost as much as the phones value in today's date. Here's the interesting fact. All these 6 users were on the latest OOS 10.3.5 and faced this issue in the span of those 4 weeks. August to September of 2020.
The purpose of this thread:
1) To diagnose the issue with the help of the xda community as I believe that there is no way that the mobo could get fried this way.
2) To possibly find a solution as the phone is in absolute scratch less condition.
3) and most important, to find other people than those 6 who have faced this exact issue in the past couple of months so that it could be raised with OnePlus. Im hoping that OnePlus could at least diagnose it and release a tool for the fix if there are enough of us. Wishful thinking maybe but worth a shot.
Hoping for your support. Peace. ✌
Click to expand...
Click to collapse
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Deeksha Naurange said:
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Click to expand...
Click to collapse
Try msmdownload tool. Look for the link on xda. Thats your only option. If that works, it works. Else you cant do anything. My scrathless OP6 is as good as a brick right now.
Deeksha Naurange said:
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Click to expand...
Click to collapse
Have you tried holding down power+ volume +&- until you see fastboot mode?? Then select power while you are in "start" screen? Does it reboot back to crash dump when you do this or does your phone boot back up? I have seen crash dump 15 times on my 6t and only one time this didnt work. One time i wqs sent back to crash dump and because i always enable dev options and usb debugging immediately after i boot anything i flashed a rom and was able to boot up and had my phone back.
If you dont have an unlocked bootloader and enable dev options and usb debugging immediately then you should because this has been an issue for many months now w/the 6 and 6t.
If you have a lock screen enabled see funk wizards how to root thread and using twrp file mananger delete lockscreen.db and if other directories are present that he talks about on his thread delete them too then flash a rom.
Search high and low and read up. If for oneplus 6 and or 6t search both sections as theyre so much alike... Everything you need to know is already here. See my signiture for link to "how to navigate xda 2021."
If this does not work use msm tool. If msm tool doesnt work thats the end of the road.
(Edited 9:38pm central time)
I faced this same issue after 2 years of usage of the Oneplus6, QUALCOM CRASH DUMP and the device status locked,,device bricked and helpless after trying all possibilities,
Flaw seems to be at Oneplus factory hardware IC
My camera is practically unusable, it locks very much on the front. I only get it sometimes when I restart my phone, but imagine you in a situation of taking a quick photo having to ask people to wait for your phone to restart before you can take a photo. Besides it shut down when I'm using it, and I can only call after a few minutes.

Oneplus 6 no longer connects to WiFi and cellular and randomly restarts

Hi,
I was using a few months ago my Oneplus 6 and decided to install the android 11 beta on it.
After few weeks it randomly restarted and now it can't connect to WiFi and cellular and after a while of it being powered up it restarts after a while.
I tried factory resetting and MSM Download Tool (downgrading to android 8.1) but to no avail.
Then I tried to see the IMEIs of the phone and they were blank same thing with the WiFi MAC.
I don't know what to do, but if somebody can help me recover this phone i'll appreciate it.
Kirito821 said:
Hi,
I was using a few months ago my Oneplus 6 and decided to install the android 11 beta on it.
After few weeks it randomly restarted and now it can't connect to WiFi and cellular and after a while of it being powered up it restarts after a while.
I tried factory resetting and MSM Download Tool (downgrading to android 8.1) but to no avail.
Then I tried to see the IMEIs of the phone and they were blank same thing with the WiFi MAC.
I don't know what to do, but if somebody can help me recover this phone i'll appreciate it.
Click to expand...
Click to collapse
This is mostly likely a HW problem, based on what you described i would say it's the RF IC chip which is "SDR845".
Either get that replaced by a shop or replace the whole motherboard which costs more but requires less skills.
All parts can be purchased online but require some skill to pull off so a pro is recommended.
Dear Team,
I am also facing exactly the same problem.
And Thank you for pointing - IMEI n MAC address are not showing when problem is there.
Is there any solution
Works fine randomly in between & then goes bad in few hours....
Kindly help
I first got network IC replaced
Then after few days
I got motherboard replaced
And now after few days
Again the same problem scenario occurring
My repair shop person says now it can be battery fault...
Or may be something related to temperature
I still believe it is something solve able for sure...

Categories

Resources