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
Related
First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
rubiix said:
First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
Click to expand...
Click to collapse
Let me clear few of your terms
Bootloop : Your device spins on CyanogenMod logo
Hard brick : Your device won't even boot into recovery and when you press power button(10-15sec), it'll vibrate just once
Softbrick : Same as bootloop, but you can boot into your custom recovery like TWRP
The solution to all your problems is to flash fastboot/factory images of Cyanogen OS 12.1 (Tutorial link in general section). Make sure that you backup your internal storage.
Flash them and use it for 2 days, if you continue to face issues, quote me here or somebody else will help you on this board
Might be a hardware issue
rubiix said:
First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
Click to expand...
Click to collapse
I've had a similar issue arise in my OPO around a month back. The phone used to randomly switch off. In most cases it didn't switch on for around 10-15 minutes. I installed different roms, cleared data/dalvik .... you name it, I did everything, but the issue still persisted. I came to the realisation that it had to be a hardware issue. Took it to a service centre, where they confirmed it was an issue with the motherboard ( although initially they just flashed cm11 and handed it to me). So basically, my phone is with the service centre for the past 5 days and is awaiting the new part.
What I'm saying is, get it to the service centre as quickly as possible, if you're nearing the end of your warranty and get it analysed and fixed. Wish your OPO a speedy recovery
Mr hOaX said:
Let me clear few of your terms
Bootloop : Your device spins on CyanogenMod logo
Hard brick : Your device won't even boot into recovery and when you press power button(10-15sec), it'll vibrate just once
Softbrick : Same as bootloop, but you can boot into your custom recovery like TWRP
The solution to all your problems is to flash fastboot/factory images of Cyanogen OS 12.1 (Tutorial link in general section). Make sure that you backup your internal storage.
Flash them and use it for 2 days, if you continue to face issues, quote me here or somebody else will help you on this board
Click to expand...
Click to collapse
Thanks for the Information,
I really appreciate your Help. Just one question, is the backup that I can create via TWRP enough or should i backup everything seperatly?
And @p403nix, Thanks for your tip !!! That's a nice information, the only Problem about that is, that in my Homecountry the Oneplus Support is very terrible. I am in contact with the customer support tho, but I don't expect too much
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/
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys
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.
Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])
Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.
Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway
Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...
Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.
CaptainFedora, did you solve the problem? I have the same issue...
Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.
Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.