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.
Related
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
bpodnar said:
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
Click to expand...
Click to collapse
No i don't have this problem format your phone or reinstall your os.
nope, thank god i dont have this on my oneplus but i had it on my galaxy s7 so i understand its a pain
bpodnar said:
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
Click to expand...
Click to collapse
What are you doing when it shuts down?
First time when I noticed that phone is off I press power button few times and hold it and desktop showed up. Today I was holding power button and the phone booted from the begining.
bpodnar said:
First time when I noticed that phone is off I press power button few times and hold it and desktop showed up. Today I was holding power button and the phone booted from the begining.
Click to expand...
Click to collapse
Well if your looking for help you need to give more details than "it just turns off". What's the battery level? Where you using it? Was it in your pocket? Are you running the latest version of Oxygen OS? Does it happen when it's plugged in? Have you tried to factory reset it?
battery was 80%, phone was on the table, running Oxygen 5.1.9, not happening when plugged in, didnt try factory reset, bootloader is locked, no root.
So... there are some plausible reasons, because your phone doesn't shut off when plugged in:
The battery simply is faulty and you have to send your phone back.
Something runs in the background, and makes you just believe, the phone shut off. Would explain the long holding power button procedure (simply shuts off the phone the hard way and reboots it).
An app is really draining your battery that fast. Bitcoin mining perhaps. Not that good explanation, because you were at 80% you said.
I'd go for #2. Check your apps - maybe there's one, causing this.
I go with uninstalling few apps I suspect causing this behaviour so we'll see what happens next.
Your not alone and this is definitely not so simple as a "faulty battery" .its something in the kernel causing panic and its happening only to certain chipset revisions .we need to open a ticket on oneplus
Got something similar today. 5.1. 9 unlocked and rooted, battery around 70%, same place, time, location etc like almost everyday). During conversations in Messenger and WhatsApp screen went black. I pressed power and I've seen keyboard to input pin with comment that pin have to be inserted after restart (normal behavior after reboot anyway), this reboot took maybe 2 seconds. But screen hasn't responsed for my attempt to input pin. I couldn't do anything). Hard reset (with holding power) solved problem.
OnePlus 6 @ Tapatalk
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
bpodnar said:
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
Click to expand...
Click to collapse
If you haven't modified your device (root, twrp, etc) in any way then it's absolutely a reason for a warranty claim.
Device isnt rooted or BL unlocked, all is stock. I will contact Oneplus support service if device goes off by itself again. I've installed latest software update 5.1.11 and all fine for last 2 days, lets hope it will stay like that.
bpodnar said:
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
Click to expand...
Click to collapse
No idea, rooted stock here, but happen only once on previous version on OOS. I will contact OP when it happen again.
OnePlus 6 @ Tapatalk
I sent my device back for replacement .definitely a device side issue for me .5.1.11 no good on my end
varund7726 said:
I sent my device back for replacement .definitely a device side issue for me .5.1.11 no good on my end
Click to expand...
Click to collapse
you were on 5.1.11 when it happened?
virtyx said:
you were on 5.1.11 when it happened?
Click to expand...
Click to collapse
Both 5.1.9 & 5.1.11
Yes, I've had this too. Screen goes black and phone dies.
Hmm somethimes fingerprint or face unlock dosent work, and i have to enter password. I think mine reboot somethimes, but haven't caut it in action yet.
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.
Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution
Dear all,
On my redmi 6, I was on android 8.1 (10.3.6.0 cereus precisely) and I prepared myself to try android 9
I had exactly this recovery recovery-TWRP-3.3.0-0423-REDMI6-CN-wzsx150.img and I did the necessary (backup everything) to be ready for the worse
Don't ask me why but I +/- remembered that recovery was tricky with android pie and I stupdly decided to flash the latest recovery I found on TWRP: twrp-3.5.1_9-0-cereus.img
Just after the flash I said reboot to recovery but: I'm in a "bootloop" not the one people have when booting in android, it's before!
Whatever the power or vol+ / vol- combination, long press power etc. , the screen is black it vibrates every 5 sec and I cannot enter neither recovery (i can understand...) NOR fastboot!
First time it happened to me to be stuck at this level. I do not know what to do, I tried desperate physical manipulations and crawl the internet meanwhile, but I do not see any trick, only solution is for an android bootloop, but not "early phone boot" (the 1 second before recovery or fastboot)
Can someone save me?
Hi, you've got your phone hard bricked, which means, that it coould be fixed, but it takes a lot of time to find a solution or you'll spend days trying to fix it, but its just gonna be a waste of time.
You can try methods that other people did, and maybe you'll get lucky, and unbrick your phone.
Other fix, is that you're gonna take your phone to an authoried Xiaomi store and hope for the best.
There are 10s of threads on hard bricks on Redmi 6 (for example: removing your battery for a couple of minues and putting it back, using SP flash (but you must have an authorized Xiaomi account, ...)).
If none of my solutions worked, I suggest buying a new phone. Redmi 6 is old and unstable after all (it didnt get MIUI 12 because of "performace issues"), so I guess thats the best you can do.
Im not really an expert for this kinda stuff.
I hope this will help you, but Im not saying that I could solve the brick.
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
edwin_r said:
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
Click to expand...
Click to collapse
Hi Edwin, Im glad to hear that your phone is back and running
For any of you other people that have this problem, I would recommend removing and replugging the battery, but remmember, there are more solutions you can find on XDA, that could fix the hard brick.
Also, for those of you that are willing to wait days, weeks, or even months and dont have the tools to open your phone and removing and replugging the battery, I would recommend checking out other solutions or just buying a new phone. Like I said before, Redmi 6 is old and unstable and theres a high change that you might get a hard brick, so if you want to install a custom ROM or a custom recovery, think twice before you do it and always have a backup phone.
I wish you all the best in solving your hard brick