Related
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037
Switched phone on after work, phone powers up, boots up and then freezes after around 20 secs then switches off and re-boots, the process then starts again over and over again.
I've tried deleting cache, master reset, safe mode, simulated battery reset which does not work. I let the battery run flat by putting the phone into download mode and then recharged the battery but still nothing. The phone seems stable only in download mode.
I managed to re-install stock 7.0 firmware via Odin. Firmware installs fine, phone boots up and then freezes on welcome screen and then boots up again. I then tried 6.0.1, again installs fine, I get the welcome set up screen but after a 20 odd secs freezes up again.
The phone is less than two years old. Samsung service centre warranty job? Thanks.
Yes. Mine had also freezing and reboot issues, Sammy changed the Mainboard
The phone is less than two years old. Samsung service centre warranty job?
Click to expand...
Click to collapse
Same problem after 5 months.
Yes get it back to service centre
guys this sounds like the same issues the lgg4 was having with the ilapo bootloop also a snapdragon
had bad solder points on the big cores and they would come loose over time and basicly the phone was stuck in a infinite loop
Hi there, my google nexus 5 has completely dead. Yesterday i was using my phone and it shutdown itself. Now i'm not able to charge or turn on the phone. No bootloop, no logo, no sound, nothing... If i connect the phone to pc windows is not able to recognize the hardware, no windows sound, no bootloop on the phone, no life signal. There is any way to fix the problem? Thanks
Try opening the phone, disconnect the battery for a few minutes, reconnect battery, connect to a charger and look for a flashing red led. Don't try to turn on the phone during this process.
I opened the phone, when i connect a charger i can hear something like an imperceptible click noise... and the logic board become hot:crying:
I had this issue recently. The phone was not turning on like you mentioned.
I was able to enter recovery mode (hold power + volume down for few seconds)
Once in recovery I wiped cache. Now the phone turns on.
I still get sudden restarts with heavy use. But at least the phone turns on now.
I took the phone to a phone repair kiosk. He told me he had 3 customers complaining of similar issues with their Nexus 5 and that he was unable to fix it.
I'm with Rogers, latest firmware, stock, locked bootloader.
erryday said:
I had this issue recently. The phone was not turning on like you mentioned.
I was able to enter recovery mode (hold power + volume down for few seconds)
Once in recovery I wiped cache. Now the phone turns on.
I still get sudden restarts with heavy use. But at least the phone turns on now.
I took the phone to a phone repair kiosk. He told me he had 3 customers complaining of similar issues with their Nexus 5 and that he was unable to fix it.
I'm with Rogers, latest firmware, stock, locked bootloader.
Click to expand...
Click to collapse
one day we will discover google has been killing older phones with updates once pixel was released, lel. jkjk
I just talked to LG Customer service. He told me the whole logic board needs to be replaced. Which would set me back $150+tax and downgrade my storage to 16Gb. No thanks.
I was hoping for a workaround, like installing a custom kernel with specific settings.
I have already tried factory reset, switching to LineageOS, removing sim card. Nothing helped.
Underclocking with Elemental X Kernel seems to be the best workaround so far.
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?
So,, first of all, hello everyone! I'm new, I'm not a device-proficient, and I'm in a problem with my phone.
This might get complicated.
So my problem starts just some days ago. When I am charging my phone with a tablet charger, it now stuck on the COOLPAD screen when plugged in. It bricked itself, but if I restart boot the phone it will turn on and goes normal, so I turn it off again then charge it with an appropriate charger. And it works and charges. Although that usually the tab charger didn't do this to my phone before.
But then.... That's just the start.
When I booted it on after charge fully and then turned off for some hours, it will boot, but no sound coming when booting on COOLPAD screen, which indicates a problem. The booting on the screen of that takes long, very long then when it's On, surprise surprise the wifi can't connect to any nets suddenly, Sim card cant be read (indicated as No Service) , SD card not detected as well(also indicated as No SD card) . Seems like a malfunction. I had experience the same before 5 months ago (and it goes semi-perma so I asked Coolpad center for software reinstall).
So what did I do? I restarted the phone through the Chinese recovery mode. Booted up right, and back to normal. But this happens just when I boot it on morning now. I am scared this might get worse and will completely bootloop or brick my phone in the future (just like the same problem I face some month ago).
So should I never turn my phone off again or is there a fix for this? Tried factory resetting it in the past, the problem just got even worse so I won't do it again the third time my phone is broken again after software reinstall again. Please help, can't really switch phone until able to find a very reasonable priced ones.:crying:
NOTE: Some day before, my Coolshow app got disabled by Play Store because of "danger" reasons. It is a system app that comes with Coolpad. I can't enable it again because the enable app isn't there, just a greyed out Disable button. I don't like to reset the preferences of apps because it'll make me need to set everything up again. Problem already occurring 3 days ago, till now.