Related
Hello,
I am an owner of HTC Sensation, rooted with Android Revolution 7.3.
My phone has ~1,5 years, since its first days i was using Android Revolution ROM, never had any problem.
Today, my phone first lost signal. Itcould not connect to any mobile network so I tried to restart it, when i got back to it after 5 minutes, the phone was stuck on beats audio logo and when i touched it, it felt very hot, it was never that hot even I used it for hours playing some games or browsing internet. (I think it was processor, down side of the phone, below battery, but because of that battery got a bit hotter too) I had to pull off the battery, I've waited till it got cold and tried to run again but rom was not working so i reflashed it from my sd card, after the next restart (phone did not get hot) when phone was checking installed apps, it simply turned itself off. Before battery showed around 80% charged, after reinstall 30% and it happened in max 10 minutes ,but after that shut down I could not turn it on. LED was not working, I tried pulling off battery, charging it, charging without abttery then connecting it, trying to reboot with abs but PC could not see the device.
The only thing I noticed, when i was trying tocharge it for the first time, processor was getting hotter but LED was not working, but then, it simply went cold.
I have no idea what I could do more here, it looks like hardware problem but te only thing i could not check was putting a new battery and try it then. Is there anything I can do more about it?
For any help, thank you.
PS: When the phone 'died' it was using faux123's 1,5 GHz kernel which came with the ROM. AsI said, before this event, everything was working perfectly, no sign of this incoming event. No restarts, freezes or crashes.
*If it matters, i was charging phone every 4-5 days, never let it go below 10%, bettery is from HTC EVO 1730mAh (original).
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
rzr86 said:
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
Click to expand...
Click to collapse
I can do nothing. No reaction.
MarcBliz said:
I can do nothing. No reaction.
Click to expand...
Click to collapse
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
rzr86 said:
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
Click to expand...
Click to collapse
Re-tried these methods, hoped I had done soemthing wrong before. I saw the artice before, was hoping there are different ways to revive the phone. Tried this, says device not found. Looks like the only method would be this JTAG box but it's a bit expensive or try to send it to repair.
Anyway thank you for your time, I appreciate it.
-And if I might ask, any idea why the phone heated up itself on nearly last startup as I mentioned in my thread? It would be allright if the phone just died before this event, now it just makes me think there might be bigger hardware problem which just caused the death and it's not worth repair.
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/
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
My OPO is having a reboot issue, was on cos13, cm14.1 and ubuntu with mutirom,
Symptoms
1. the phone stays on if connected to a charger or powerbank.
and without charger it bootloops at the 1+ logo
2. in switched off state, when charger is connected the battery sometimes shows 0% and increases to 100%
3. with charger i entered cm recovery, removed the charger, the phone stayed all night long with cm recovery menu display on.
after draining the battery, i plugged back charger and the phone in switched off state did show the regular charging animation and took the usual time to full charge.
after full charge I removed the charger, tried to power on the phone boot loops at 1+ logo.
4. without charger it can enter fastboot mode.
5. with charger it can boot into os, shows charging, led lit up, but after removing charger it won't stay long, also if opening camera it turns off.
6. even on powerbank it can boot up and stay switched on. and work normally (camera etc anything)
(7. while turned off and on charger the animation shows charging but the top led isn't on.) - I don't remember it lighting up on charging while switched off
8. the night before this issue occured, my phone rebooted twice while watching youtube. and in the previous nights also I noticed battery dropping overnight.
what all I tried,
1. fastboot flashed cos, - not solved
2. flashed using Qualcomm USB port tool - not solved.
3. ran the make_ext4fs /dev/block/mmcblk0p15 command in twrp. - not solved.
4. erased and flashed persist.img - not solved.
so what could be the problem, opo is now my secondary phone, now using op3 as primary.
The battery is at its end of its life....replace the battery and all your problem will be gone...
you're not the only one that have experiences this problem (i have seen more then 10 people having the same problem)...last year and this year there a lot of people having bootloop problem due to dying battery...factory reset, flash stock rom and etc won't help you solved this problem...
i personally have this problem last year and after i replace the battery all my problem gone...i think Oneplus made OPO batteries only lasted for 2 and a half year....
iPusak Gaoq™ said:
The battery is at its end of its life....replace the battery and all your problem will be gone...
you're not the only one that have experiences this problem (i have seen more then 10 people having the same problem)...last year and this year there a lot of people having bootloop problem due to dying battery...factory reset, flash stock rom and etc won't help you solved this problem...
i personally have this problem last year and after i replace the battery all my problem gone...i think Oneplus made OPO batteries only lasted for 2 and a half year....
Click to expand...
Click to collapse
thanks for the reply i guessed that, but still wasn't sure, can it be also due to any issues to board, anyway since i've done with flashing and all i'll try an OP service center, and hope it won't costs me big.
jnraj said:
thanks for the reply i guessed that, but still wasn't sure, can it be also due to any issues to board, anyway since i've done with flashing and all i'll try an OP service center, and hope it won't costs me big.
Click to expand...
Click to collapse
Nope it is not issues with the motherboard but batteries...the phone can be turn on like normal when charger is connected and goes into bootloop once the charger is disconnected....its a clear sign that the battery is dying...when it connected to the charger, it may look like the battery is full but it is not...just buy a new battery and all your problem will be gone...you can try flashing lot of rom, revert to stock or whatever you do in fastboot but it ain't gonna help you...it might boot normally but within an hour it will goes back to bootloop....
like i said before i was on the same pages as you last year...all the flashing stuff didn't work until i replace the battery....there no issues with the motherboard whatsoever....my phone still work atm without any bootloop problem...
feel free to go to OP services center if you want, if they tell you it was a motherboard issues then you have been screwed by the services center by repairing something that is still in good condition and you gonna pay more then just a batteries afterwards...
iPusak Gaoq™ said:
Nope it is not issues with the motherboard but batteries...the phone can be turn on like normal when charger is connected and goes into bootloop once the charger is disconnected....its a clear sign that the battery is dying...when it connected to the charger, it may look like the battery is full but it is not...just buy a new battery and all your problem will be gone...you can try flashing lot of rom, revert to stock or whatever you do in fastboot but it ain't gonna help you...it might boot normally but within an hour it will goes back to bootloop....
like i said before i was on the same pages as you last year...all the flashing stuff didn't work until i replace the battery....there no issues with the motherboard whatsoever....my phone still work atm without any bootloop problem...
feel free to go to OP services center if you want, if they tell you it was a motherboard issues then you have been screwed by the services center by repairing something that is still in good condition and you gonna pay more then just a batteries afterwards...
Click to expand...
Click to collapse
I have almost exactly the same problem. The thing is I cannot find a way to enter multirom recovery even on a charger. When on a charger it tries to boot into my primary rom but gets stuck on it endlessly.
Are you sure its the battery? I mean, mine charges to 100% when plugged in and doesnt seem to have any problem with charging. Mine did it a few days ago, it went into a bootloop for no reason. I havent touched anything for a year and it happened so randomly and lost everything I had on it...
MetalmanIX said:
I have almost exactly the same problem. The thing is I cannot find a way to enter multirom recovery even on a charger. When on a charger it tries to boot into my primary rom but gets stuck on it endlessly.
Are you sure its the battery? I mean, mine charges to 100% when plugged in and doesnt seem to have any problem with charging. Mine did it a few days ago, it went into a bootloop for no reason. I havent touched anything for a year and it happened so randomly and lost everything I had on it...
Click to expand...
Click to collapse
Yes i'm sure of it...i have seen more then 10 opo user in my country that have the same problem as me and when they all replace the battery after my suggestion...all their problem go away without having reflash anything...
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
Yes i'm sure of it...i have seen more then 10 opo user in my country that have the same problem as me and when they all replace the battery after my suggestion...all their problem go away without having reflash anything...
Click to expand...
Click to collapse
Hey dude Thanks a lot... I was facing exactly same issue for last 2 days... I bought OPO on Dec 5 th 2014... I think its battery only works 2 years...
@iPusak Gaoq™, tried to get a suitable battery online but the shipping charge killed most deals, some were even counterfeits, so finally I decided to visit an op service centre, they replaced the battery with a new one, now my OPO is good as new. thanks again.
I was just going to post, about my issue, but the forum suggested your post. I read the first post, and yes, I am facing the exact same problem. Taking a picture and the phone shuts off. Vibrating from getting a notification and restart.
And the saddest part, the phone won't boot into OS if is it not plugged to PC or AC power.
My Opo is almost two years old. Can you suggest a good battery replacement for me?
leokook said:
I was just going to post, about my issue, but the forum suggested your post. I read the first post, and yes, I am facing the exact same problem. Taking a picture and the phone shuts off. Vibrating from getting a notification and restart.
And the saddest part, the phone won't boot into OS if is it not plugged to PC or AC power.
My Opo is almost two years old. Can you suggest a good battery replacement for me?
Click to expand...
Click to collapse
Hard to suggest which batteries is good if you planning to bought it online cause there no way you can know whether the batteries you gonna buy is original or OEM...only when you bought the batteries in a retail store then you can see whether its original or OEM and yes the differences between both batteries is noticeable...
Sent from my A0001 using Tapatalk
Hello All, Don't know whether posting in right thread or wrong!....
My OPO is almost 3 years old, it is rebooting automatically i.e Powered by Android screen showing & then again it will restart with the same. Continuously rebooting the same until long press the power button for force shutdown. I need a solution , kindly help me out.
Am not an software engineer to understand the programming terms, hence if you share line to line steps, i can try..
Harishxda said:
Hello All, Don't know whether posting in right thread or wrong!....
My OPO is almost 3 years old, it is rebooting automatically i.e Powered by Android screen showing & then again it will restart with the same. Continuously rebooting the same until long press the power button for force shutdown. I need a solution , kindly help me out.
Am not an software engineer to understand the programming terms, hence if you share line to line steps, i can try..
Click to expand...
Click to collapse
Replace the battery of your Phone, it will be back to normal.
Changed battery but issue is sill there..
Will i found original battery at Ahmedabad Service Center
jnraj said:
@iPusak Gaoq™, tried to get a suitable battery online but the shipping charge killed most deals, some were even counterfeits, so finally I decided to visit an op service centre, they replaced the battery with a new one, now my OPO is good as new. thanks again.
Click to expand...
Click to collapse
as i m facing same issue since last sunday, i think i shall go to Oneplus Service center here in ahmedabad for replacement of battery, how much they charged for battery replacement.??
thanks..
samiran das 03 said:
Changed battery but issue is sill there..
Click to expand...
Click to collapse
you still having OPO? Did issue resolve?
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?