Hardware issue?? Screen Sleep and unable to turn on - ONE Q&A, Help & Troubleshooting

Hi,
I bought OPO before 1 week. Still as it condition means not rooted yet. From last 3 days having issue with screen sleep. I've set 30 sec to turn off display. When I try to double tap or power button to unlock my screen isn't turning on. I need to press power button for sometime for reboot.
Please help me to solve this issue.

HemZone said:
Hi,
I bought OPO before 1 week. Still as it condition means not rooted yet. From last 3 days having issue with screen sleep. I've set 30 sec to turn off display. When I try to double tap or power button to unlock my screen isn't turning on. I need to press power button for sometime for reboot.
Please help me to solve this issue.
Click to expand...
Click to collapse
Hey man, what rom are you running? If you running CM12, flash the last modem.
And turn of Ambitien Screen (dont know exactly how its spelled)

elinho said:
Hey man, what rom are you running? If you running CM12, flash the last modem.
And turn of Ambitien Screen (dont know exactly how its spelled)
Click to expand...
Click to collapse
His post states that he's not rooted, stock.
Transmitted via Bacon

While I didn't ever have this problem on CM11S, try going to Settings -> Display -> Turn off Prevent accidental wake up.
That solved it for me, I feel like the proximity sensor on the OPO is a bit odd at times.
Other wise a factory reset could help you.

@all, Thanks for quickly reply
@elinho I've not rooted my device so using stock rom.. CM 11 with Kitkat 4.4.4
@timmaaa You are right dude..
@Cheesus182 I tried that but still same issue..
I'm thinking to root my device, Which ROM you guys recommend.. BugLess
Thanks..
Cheesus182 said:
While I didn't ever have this problem on CM11S, try going to Settings -> Display -> Turn off Prevent accidental wake up.
That solved it for me, I feel like the proximity sensor on the OPO is a bit odd at times.
Other wise a factory reset could help you.
Click to expand...
Click to collapse
elinho said:
Hey man, what rom are you running? If you running CM12, flash the last modem.
And turn of Ambitien Screen (dont know exactly how its spelled)
Click to expand...
Click to collapse
timmaaa said:
His post states that he's not rooted, stock.
Transmitted via Bacon
Click to expand...
Click to collapse

HemZone said:
@all, Thanks for quickly reply
@elinho I've not rooted my device so using stock rom.. CM 11 with Kitkat 4.4.4
@timmaaa You are right dude..
@Cheesus182 I tried that but still same issue..
I'm thinking to root my device, Which ROM you guys recommend.. BugLess
Thanks..
Click to expand...
Click to collapse
Honestly, asking for a ROM recommendation will get you nowhere because you'll get ten dudes with ten different opinions on which to use. Read a few of ROM threads to see which have the features you like, and read the last few pages of each thread to see if people are reporting bugs or not.
Transmitted via Bacon

As mentioned above, too many ROMs and everyone prefers their one.
Only thing I really advise you on, don't flash a CM12 ROM. In my opinion its very buggy and has more issues than its worth.
Go with a CM11 ROM for now but if your going to flash anyway give a factory reset a try first.

Thank you very much! I will try with factory backup. Any alternative solution to resolve this screen sleep issue?
timmaaa said:
Honestly, asking for a ROM recommendation will get you nowhere because you'll get ten dudes with ten different opinions on which to use. Read a few of ROM threads to see which have the features you like, and read the last few pages of each thread to see if people are reporting bugs or not.
Transmitted via Bacon
Click to expand...
Click to collapse
Cheesus182 said:
As mentioned above, too many ROMs and everyone prefers their one.
Only thing I really advise you on, don't flash a CM12 ROM. In my opinion its very buggy and has more issues than its worth.
Go with a CM11 ROM for now but if your going to flash anyway give a factory reset a try first.
Click to expand...
Click to collapse

Related

[Q] Flashed 4.4.4 deoxdexed stock rom, Calls dont work HELP

so i was on cataclysm from the beginning and everything worked great. I flashed stock 4.4.4 cause i want to use just xposed with a nice vanilla rom. everything works great except i cant get or place calls. i have sprint lte full bars, can get data and everything send texts/mms, go on facebook, dl stuff, just no calls. wifi or not doesnt matter either. everytime i try to place one it just sits on dialing and i lose all bars and then says can t make call, no connection. once i hang up the bars and lte come back.
I have noticed my network ends up on global sometimes instead of LTE but even when i switch it to LTE it still doesnt work. i have updated prl and profile too. Any ideas? thanks
EDIT: yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/forum/#!topic/nexus/Or6_6zCtBwc
seems like it might be sprints fault
Did you wipe?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Did you wipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
fergdizzle9090 said:
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
Click to expand...
Click to collapse
did you update the bootloader and radio?
Zepius said:
did you update the bootloader and radio?
Click to expand...
Click to collapse
no i did not, just twrp. would that be the problem?
possibly. you should do it to be safe.
Zepius said:
possibly. you should do it to be safe.
Click to expand...
Click to collapse
do you have to do it when you upgrade android versions? is there any quick link you can post to help me out with it? im not all that familiar with updating those. Ill search around and see what I can find. thanks for the suggestion though
Im thinking about RMAing my nexus 5 though because the power button is very loose and rattles loudly when i tap the screen, dont want a crappy refurb in place of my mint pristine nexus though :/ lol
Rma is always new
Sent from my Nexus 5 using Tapatalk
rootSU said:
Rma is always new
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
oh i didnt know that. well great thanks. Ill give the updates a shot and consider the rma more now i know ill be getting a new phone. just dont want to be without it for a while lol
yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/fo...ce=footer#!msg/nexus/Or6_6zCtBwc/j5CP8vy4jGAJ
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Lokke9191 said:
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
fergdizzle9090 said:
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
Click to expand...
Click to collapse
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Lethargy said:
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Click to expand...
Click to collapse
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
fergdizzle9090 said:
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
Click to expand...
Click to collapse
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Lethargy said:
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Click to expand...
Click to collapse
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
fergdizzle9090 said:
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
Click to expand...
Click to collapse
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
thanks ill try it out when i got a spare moment. now that im thinking of it this all happened after i updated twrp, so could that be the root of all this you think? because i used the twrp app to update it instead of flashing, and i noticed it has been acting extremely weird lately.
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
hsas.69 said:
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
Click to expand...
Click to collapse
ill look into it. people who have this problem said its not the apn though because i get data just fine and i can recieve calls. its only when i am placing a call it goes crazy and disconnects me
EDIT: so anyone know how to get to apn for sprint? its not under mobile networks. is it buried in a dialer menu or something?...
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
well full reflash of 4.4.4 stock from google through fastboot didnt work :/ i noticed also that it hasnt been connecting during initial setup, i have to connect to wifi. think my phone might be borked :crying:

[Q] Scrolling sensitivity & ghosting

Hi All,
I've installed TugaPower V35 and currently upgrading to 36. I have an issue with the scrolling sensitivity.
When scrolling a list, like contacts, I require to use a long and really fast flick on the screen in order to get just this very small push in the scrolling speed.
In some cases I experience ghosting or weird touch issues that disabling me from typing a message.
can someone please guide me for a fix?
Thanks!
please, anyone?
Why not actually ask in the Tuga thread?
Transmitted via Bacon
because it's not rom related.
I stated what I'm running currently in order to provide somewhat useful info. but its not rom related.
Have you tried a wipe and fresh install of CM11S?
Transmitted via Bacon
I didn't. Is this really going to solve this?
If I'm on 5.0.2, then how an older version will amend this issue?
gil80 said:
I didn't. Is this really going to solve this?
If I'm on 5.0.2, then how an older version will amend this issue?
Click to expand...
Click to collapse
It isn't about going forwards or backwards, it's about undoing any modifications/bugs/firmware mismatches by returning the device to a stock configuration (flashing the fastboot stock images). If anything is going to fix your problem, this is your best bet.
Transmitted via Bacon
Ok. So from my current version, can you please direct me to the best guide on how to go back to latest stock and then at least unlock and root?
thanks!
You'll find full instructions in section 8 of my guide thread. You don't need to relock your bootloader, and just root again as you normally would.
Transmitted via Bacon
Thank you, sir!
What do you think about: http://forum.xda-developers.com/one...conv6cm11s-t2861173/post55109051#post55109051
Should I try this ROM as this is tweaked but still CM11
gil80 said:
Thank you, sir!
What do you think about: http://forum.xda-developers.com/one...conv6cm11s-t2861173/post55109051#post55109051
Should I try this ROM as this is tweaked but still CM11
Click to expand...
Click to collapse
You can try the ROM, but you still need to wipe and flash the stock images first.
Transmitted via Bacon
Yep, I thought so. Ok, I'll try that, though experience tells me that I won't get it resolved.
My wife has the OPO and I installed latest cm12 nightly and her phone doesn't have these issues... I bought mine 2nd hand and that is my punishment.
gil80 said:
Yep, I thought so. Ok, I'll try that, though experience tells me that I won't get it resolved.
My wife has the OPO and I installed latest cm12 nightly and her phone doesn't have these issues... I bought mine 2nd hand and that is my punishment.
Click to expand...
Click to collapse
It may not get it resolved, but it's still worth a try, and it's your best hope.
Transmitted via Bacon
I'm not sure if this is related, but try with boeffla kernel ( http://forum.xda-developers.com/one...ernel-boeffla-kernel-1-0-2-0-beta-09-t2899974 )
and with this firmware: https://www.androidfilehost.com/?fid=95916177934519251 (credits to katinatez, pulled from this thread: http://forum.xda-developers.com/oneplus-one/development/rom-cm11-temasek-build-t2870743 )
I'm having a similar problem and it seems to be better now. Let me know
Fede

[Q] Capacitive Keys Problem

Hey guys,
So I flashed this rom two weeks back http://forum.xda-developers.com/oneplus-one/development/rom-paranoidandroid-5-0-alpha1-t2956478
after running cm12s nightlies for a while. The capacitive keys stopped working after I flashed this rom with the PA gapps and they still don't work after trying multiple roms + relocking unlocking bootloader and flashing 44s. Kinda frustrated cause I don't know what I can do. Any ideas?
Thanks
How did you flash 44S?
Transmitted via Bacon
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Sanjitha.d said:
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Click to expand...
Click to collapse
By recovery tool you mean flashing with fastboot, right?
Transmitted via Bacon
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Sanjitha.d said:
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Click to expand...
Click to collapse
That's what I meant, that's flashing with fastboot. The only thing I can think of doing is completely wiping your phone including user data (back up important files first) and flashing the stock images again, but manually this time. You can find a download and instructions in section 8 of my guide thread.
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Alright, I've also tried manually flashing the stuff myself but I'll do it according to your guide to see if it works. You don't think it could be anything software/firmware related after that yeah? I remember there was a guy who said that he had to do a full wipe to make the cap keys to work on the initial pa thread but actually no idea on how this screwed up lel
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Sanjitha.d said:
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Click to expand...
Click to collapse
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
timmaaa said:
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Sanjitha.d said:
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Click to expand...
Click to collapse
Can't really suggest one because I don't use them, but you'll find them all listed in my index thread here:
http://forum.xda-developers.com/showthread.php?t=2843675
I can't think of anything else on the software/firmware side of things, everything has been wiped and reflashed.
Transmitted via Bacon
I have a similar issue. The softkeys stopped working right after i unlocked the bootloader. They light up but do not respond. can anything be done? I unlocked the bootloader via adb.

[Q] Lockscreen issue!

Hi, so I was using my opo with stock CM11S without a hitch and when I took the phone out and hit the power button to show the lock screen it didn't respond. I had to switch the phone off and on by long pressing power button and every time the phone goes to sleep I have to do this all over. How do I stop this?
lockscreen
Bridge Ric said:
Hi, so I was using my opo with stock CM11S without a hitch and when I took the phone out and hit the power button to show the lock screen it didn't respond. I had to switch the phone off and on by long pressing power button and every time the phone goes to sleep I have to do this all over. How do I stop this?
Click to expand...
Click to collapse
Go into Settings->Security->Screen lock and try a different screen lock setting. Reboot the phone. Set it back to original. Reboot. Cross your fingers.
You can try toggling the double-tap to wake gesture, too.
Didnt work mate
proximity sensor?
Bridge Ric said:
Didnt work mate
Click to expand...
Click to collapse
Google "power button doesn't unlock oneplus":
https://forums.oneplus.net/threads/power-button-doesnt-unlock-neither-double-tap.292269/
Among other google-y things.
P.S.--glad you tried.
pbergonzi said:
Google "power button doesn't unlock oneplus":
https://forums.oneplus.net/threads/power-button-doesnt-unlock-neither-double-tap.292269/
Among other google-y things.
P.S.--glad you tried.
Click to expand...
Click to collapse
I disabled Prevent Accidental WAkeup blah and it worked!
great
Bridge Ric said:
I disabled Prevent Accidental WAkeup blah and it worked!
Click to expand...
Click to collapse
Nice move--glad you fixed it, and thanks for reporting back--that'll be the first thing I say next time someone asks.
Well you know..., either that or "use google."
Bridge Ric said:
I disabled Prevent Accidental WAkeup blah and it worked!
Click to expand...
Click to collapse
This hasn't actually fixed the problem. I'm guessing you recently went from a Lollipop ROM back to KitKat on CM11S, right? Did you flash the KitKat modem first?
Transmitted via Bacon
timmaaa said:
This hasn't actually fixed the problem. I'm guessing you recently went from a Lollipop ROM back to KitKat on CM11S, right? Did you flash the KitKat modem first?
Transmitted via Bacon
Click to expand...
Click to collapse
I did. I read about how not flashing the modems can do stuff like screen going dead on calls and stuff but I can't be bothered to flash it as we're so close to CM12S anyway so when I update to that the issues will go away anyway
Bridge Ric said:
I did. I read about how not flashing the modems can do stuff like screen going dead on calls and stuff but I can't be bothered to flash it as we're so close to CM12S anyway so when I update to that the issues will go away anyway
Click to expand...
Click to collapse
You can't be bothered? It's a simple zip flash in TWRP, takes 15 seconds.
Transmitted via Bacon

oneplus one stuck at bootloop when not charging

HI I have 1+1 and its 2 years 3 month old. Presently its on CM13 MM(oxygen OS I guess) and rooted and have a recovery also. I did root and recovery around 8 months back.
2 days back when mobile was in pocket and 35% battery it went in to bootloop. after lot of stuffs like clearing cache and dalvik cache nothing worked.
Later at night i found out that mobile is working fine when its connected to charging (either by lapi or Mob charger). Hence I didn't go back to old recovery.
yesterday fully drained my battery and later charged to full and found same issue.
I am not able to make out whats the issue and how to move forward if I don't want to loose my resent data state. PLs guys help me to solve this issue.
will do whatever needed to restore my mobile. TIA
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Hunting_Party10 said:
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Click to expand...
Click to collapse
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
praveen4u13 said:
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
Click to expand...
Click to collapse
Try a factory reset?
Mr.Ak said:
Try a factory reset?
Click to expand...
Click to collapse
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
praveen4u13 said:
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
Click to expand...
Click to collapse
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Mr.Ak said:
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Click to expand...
Click to collapse
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
praveen4u13 said:
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
Click to expand...
Click to collapse
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Mr.Ak said:
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Click to expand...
Click to collapse
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Mr.Ak said:
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Click to expand...
Click to collapse
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
is it not strange that so many people (including) have started facing this issue suddenly in the past two months?
I too am facing this issue. Has anyone managed to find a fix for the issue?
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Did flashing cos13 fixed the issue? I'm also facing the same issue
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
praveen4u13 said:
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
Click to expand...
Click to collapse
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
piez97 said:
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
Click to expand...
Click to collapse
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
praveen4u13 said:
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
Click to expand...
Click to collapse
I contacted my nearest customer care. They said that they have to analyze the phone and it would take almost 15 days. Did you get a new battery?
praveen4u13 said:
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
Click to expand...
Click to collapse
Same issue, start from 3 days ago...
Without charger or power bank i can't use phone [emoji19]
My phone is old around 2.5+ year
Sent from my A0001 using Tapatalk
Me too having the same issue. Seems like OnePlus one devices have some kind of kill switch to ruin it after 2.5 years. Quite a few number of people seems to have this issue all of a sudden.

Categories

Resources