So after 8 hours my battery still said 100% and even shut off due to dead battery and it still said 100% full. In TWRP it also shows 100% full. Any ideas? I have it on the turbo charger now, since it died, and will wait about 2 hours then try to reset battery stats. Not sure what else to try. Nothing new installed, phone is stock other than rooted and TRWP.
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
huh?
The phone was rooted the day I got it, Nov 9th, and it just started doing it today. So how does root automatically cause the issue?
Anyway, any ideas would be great I think resetting the batterystats has worked just curious what may have started it.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
I've never had issues from just rooting. Rooting a phone doesn't cause issues but rather installing root apps and changing things causes issues. I would try to flash back to stock (backup data first) and then root it again to see of that fixes it.
Also did you use CF-Autoroot or one of the tool kits?
I fixed the issue, after that battery died I let it charge for about 4 hours with the quick charger and then reset the battery stats by using an app that deletes the batterystats.bin file. Then did a reboot and now the battery level is no longer stuck on 100%.
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
lifeisfun said:
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
Click to expand...
Click to collapse
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
root has nothing to do with breaking your phone. all root does is give you superuser permission. what breaks phones are dirty hacks that you yourself chose to use.
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
lifeisfun said:
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
Click to expand...
Click to collapse
I would just put it down to "OS Confusion "
danarama said:
I would just put it down to "OS Confusion "
Click to expand...
Click to collapse
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
lifeisfun said:
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
Click to expand...
Click to collapse
Yeah maybe battery firmware confusion. I don't know where TWRP gets its reading from.
Still Works!
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
Thanks.
Related
Well, I was browsing around the market and my n5 just abruptly shut itself off. It hasn't been able to turn back on since. I've tried every key/charge/magic trick in the book so its DEAD!
Happy to jump in the RMA line at this point but was wondering if any others can confirm DEAD devices. The RMA thread is kinda full of nitpick issues but a dead device is a dead device.
This was the only discussion chain I could find on the issue but maybe someone from google will comment on dead devices. lol
https://productforums.google.com/forum/#!msg/nexus/lI6A3fA8bvw/d3eQlqEqabEJ
EDIT:
so it appears holding down both volume buttons + power while it's plugged in to the charger (not USB to PC) will temporarily boot the phone. You can then do a restore to stock and issue gets fixed. :good:
Damn. That blows.
Sent from the jaws of my Hammerhead!
mrro82 said:
Damn. That blows.
Click to expand...
Click to collapse
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Since I was able to get it booted tethered to the power I'm going to have it drain the battery to dead and see if it resets itself or something. Maybe a bad idea but I guess I don't care at this point it's already RMAd and I don't know what else to try. lol
Zenoran said:
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Click to expand...
Click to collapse
Do you have a backup you can attempt to restore?
Have you tried to adb into it?
Delete damn it
I would never install twrp.
There is a stock rom in here somewhere. Flash it boot loader and see what happens.
Synyster06Gates said:
Do you have a backup you can attempt to restore?
Click to expand...
Click to collapse
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Zenoran said:
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Click to expand...
Click to collapse
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
caribouxda said:
I would never install twrp.
Click to expand...
Click to collapse
Why wouldn't you? In situations like this, it is extremely helpful. Do you expect him to install CWM or something? From my understanding, at least when I first got my phone and flash a custom recovery, CWM wasn't booting. If you are here to try and press your opinion on which custom recovery you prefer, go to their official thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app
floxrin said:
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Zenoran said:
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Click to expand...
Click to collapse
That's good to hear man. I couldn't imagine how I'd feel if that happened to me. Thankfully XDA us the place that it is and the members, for the most part, have the ability to help us troubleshoot most of our issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ok so I've installed 10.4.B.0.569 rooted and everything.
After a while my phone becomes sluggish and barely anything works anymore.
At some point it becomes so sluggish that even my clock slows down...
I did a fresh installed wiped EVERYTHING! Tried other kernels, but the same thing always happens...
One time when it became really bad I did a factory reset but even the first time after the reset it became sluggish again...
I freshly installed the new FW on the 14th and nothing bad happened till today. (Before the 14th I also had trouble with this fw, but they came like after a day max) On 4.2 I've never had these issues before.
The only solution I can think of is removing my 64gb card and see if that has any effect.
Hopefully anyone else has some suggestions that I can try.
Here are some screenshots.
P.S. When the phone becomes really sluggish the battery drains really fast.... like 30% per hour while the screen is off.....
And the phone randomly buzzes at times. Sometimes 1 buzz, sometimes 3 buzzes.
http://imgur.com/Ij4nbWU
Edit:
I planned to post more screenshots, but saving a screenshot takes like 1 minute and I can't even connect the phone to my PC because the drivers fail to be installed. Even though it worked just fine before...
Can you post a logcat and kmsg?
Sent from my C6603
alnikki25k said:
Can you post a logcat and kmsg?
Sent from my C6603
Click to expand...
Click to collapse
I've got no clue how to get the logs. It's been ages since I've done these kind of things.
I just did a factory reset and removed my sdcard just to see if that caused the problem.
Could you please tell me how to get the logs? So that I can post them next time it happens again. (Which it probably will...)
Dsteppa said:
I've got no clue how to get the logs. It's been ages since I've done these kind of things.
I just did a factory reset and removed my sdcard just to see if that caused the problem.
Could you please tell me how to get the logs? So that I can post them next time it happens again. (Which it probably will...)
Click to expand...
Click to collapse
Follow this thread
http://forum.xda-developers.com/showthread.php?t=2185929
Click to expand...
Click to collapse
alnikki25k said:
Follow this thread
Click to expand...
Click to collapse
Ok I'll keep it in mind when it happens again.
alnikki25k said:
Can you post a logcat and kmsg?
Sent from my C6603
Click to expand...
Click to collapse
Ok here are the logs:
Hope that they are helpful
which rom u put on ?
maybe bad/corrupted download
check wake locks
Dsteppa said:
Ok here are the logs:
Hope that they are helpful
Click to expand...
Click to collapse
Are you using DooMKernel?
alnikki25k said:
Are you using DooMKernel?
Click to expand...
Click to collapse
Yes I am, but I have the same issue with stock kernel
My friend recently gave me her old HTC One, and I've been trying to fix it, but I can't quite figure it out.
She said it started bootlooping randomly after she plugged it in to charge. When I first received it I plugged it in and mashed the power button until it turned on. Booted up just fine. But now it's in a stupid bootloop that takes me to a blank desktop with no dock or wallpaper,and then reboots after a few minutes.
Can a battery issue cause this? A complete factory reset from recovery is not an option because I'm trying to save her photos. I don't know how I can get 11gb worth of them off when it's not booting properly.. Any ideas for fixing this or getting the photos off?
Have you tried to wipe data factory reset from recovery ?
That doesn't erase photos
Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.
rha_december said:
Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.
Click to expand...
Click to collapse
in stock recovery try and erase cache .. Don't factory reset ... everything would be gone
Ughh,... A bit too late. Lost everything and it didn't even fix my problem. Ah well. I think I need to replace the battery anyway. That, and my computer doesn't even detect the phone when I plug it in.
rha_december said:
Oh really? I thought it did. This is a stock recovery btw. No root or anything. And it's on 4.1.
Click to expand...
Click to collapse
Oh I'm sorry , i didn't know it was stock recovery.
I assumed custom recovery.
rahulsethi said:
Oh I'm sorry , i didn't know it was stock recovery.
I assumed custom recovery.
Click to expand...
Click to collapse
It's fine. I jumped the gun. Losing some photos had never killed anybody haha..
I should have remembered.. But I haven't done anything with Android for so long because I had been stuck with a locked S4 for a while..
Anyway, I'll replace the battery and see if that helps.
rha_december said:
It's fine. I jumped the gun. Losing some photos had never killed anybody haha..
I should have remembered.. But I haven't done anything with Android for so long because I had been stuck with a locked S4 for a while..
Anyway, I'll replace the battery and see if that helps.
Click to expand...
Click to collapse
you realize the One is a 9 out of 10 on difficulty to disassemble
clsA said:
you realize the One is a 9 out of 10 on difficulty to disassemble
Click to expand...
Click to collapse
Yeah, but I've disassembled phones before and I have faith in my hands haha.
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
EDIT:
Not sure what the exact issue was, but I downloaded the Droid Turbo OEM from HERE. Waited 8 hours to download (original links don't work anymore and the mirror is stupid and charges for a fast download), unzipped the file, then ran the VRZ_XT1254_SU4TL-44_44_CFC.bat and it booted right up and has been working fine. I then simply installed TWRP, flashed SuperSU, then edited the build.prop to get hotspot working.
flametail2518 said:
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
Click to expand...
Click to collapse
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
GreaterLesser said:
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
Click to expand...
Click to collapse
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
TheSt33v said:
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
Click to expand...
Click to collapse
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
GreaterLesser said:
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
Click to expand...
Click to collapse
Honestly, I have no idea.
I agree yes try recalibrating the battery. Or do a clean flash. It should recalibrate the battery when you do this.
The calibration is simply a file based on battery reads.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
flametail2518 said:
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
Click to expand...
Click to collapse
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
My phone likes to shut down around 1-8% without warning, but it does say Powering down as it does it. It's kind of annoying, but I'm sure that's not similar to what you're experiencing.
TheSt33v said:
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
Click to expand...
Click to collapse
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
flametail2518 said:
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
Click to expand...
Click to collapse
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
See previous post. I got it fixed today.
Sent from my SHIELD Tablet using Tapatalk
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
flametail2518 said:
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
Click to expand...
Click to collapse
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
TheSt33v said:
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
Click to expand...
Click to collapse
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
flametail2518 said:
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
TheSt33v said:
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
Click to expand...
Click to collapse
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
flametail2518 said:
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
Click to expand...
Click to collapse
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
TheSt33v said:
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
Click to expand...
Click to collapse
The free option said they look for physical damage first then go on to the repair.
Manually extracted stock ROM after all updates for now, include boot.img, recovery.img and system.img for LG Warch Urbane 1st gen.
GOOGLE Drive
The link is broken, my friend
Link is working here. Hopefully the author of the 998 mhz 4 core mod can get this boot image and get that going. I miss having that little boost in speed.
DrRyder said:
Link is working here. Hopefully the author of the 998 mhz 4 core mod can get this boot image and get that going. I miss having that little boost in speed.
Click to expand...
Click to collapse
how can i downgrade to 5.1 from 2.0 on my lg urbane?
kaosar said:
how can i downgrade to 5.1 from 2.0 on my lg urbane?
Click to expand...
Click to collapse
There are a lot of threads out there on how to downgrade from 2.0 to 1.5. Do a little searching and you can find them. I havent needed to downgrade.
DrRyder said:
There are a lot of threads out there on how to downgrade from 2.0 to 1.5. Do a little searching and you can find them. I havent needed to downgrade.
Click to expand...
Click to collapse
How to install? There is no specific way install. Can u provide me link how to downgrade 1.5 without any problem?
kaosar said:
How to install? There is no specific way install. Can u provide me link how to downgrade 1.5 without any problem?
Click to expand...
Click to collapse
This maybe? https://www.reddit.com/r/AndroidWear/comments/651ijs/how_to_downgrade_the_urbane_from_20_to_15/
I take no responsibility lol. I had no need to downgrade back to 1.5 so I really couldn't help you further. You'll have to do some digging on your own, bud. 2.0 with the unlocked 4 core 998 mhz boot image has made my watch enjoyable again. I also disabled a bunch of apps that I didnt need running like other watch faces, etc to help conserve battery.
When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.
i have same issue. some times it stays longer out of charger but goes off once i do a
i have same issue. some times it stays longer out of charger but goes off once i do a
kaosar said:
When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.
Click to expand...
Click to collapse
kaosar said:
When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.
Click to expand...
Click to collapse
your issue same with me
inuer said:
your issue same with me
Click to expand...
Click to collapse
same here. Happened a week ago
zul8er said:
same here. Happened a week ago
Click to expand...
Click to collapse
Just got this issue on mine too right after flashing this kernel
liam_davenport said:
Just got this issue on mine too right after flashing this kernel
Click to expand...
Click to collapse
Reflashing stock img fixed it for me
liam_davenport said:
Reflashing stock img fixed it for me
Click to expand...
Click to collapse
Sadly it didn't work for me.
I have tried flash stock boot, rec, sys, and wipe everything, but no luck.
At least you fixed yours, so worth a try for others
liweichen6 said:
Sadly it didn't work for me.
I have tried flash stock boot, rec, sys, and wipe everything, but no luck.
At least you fixed yours, so worth a try for others
Click to expand...
Click to collapse
Damn not sure then I was thinking maybe a partition is f**ked you could format partitions and retry the img that might work
liam_davenport said:
Damn not sure then I was thinking maybe a partition is f**ked you could format partitions and retry the img that might work
Click to expand...
Click to collapse
Later I found this guide in Watch R forum, which might be related.
Since it requires mod on battery I'm not so sure if I should proceed (or I can try to replace a battery).
Or I could switch something new. It has been years and I always want to try something new lol.
Anyway thanks for effort
liweichen6 said:
Later I found this guide in Watch R forum, which might be related.
Since it requires mod on battery I'm not so sure if I should proceed (or I can try to replace a battery).
Or I could switch something new. It has been years and I always want to try something new lol.
Anyway thanks for effort
Click to expand...
Click to collapse
thanks for the link , i did this on my urbane and it fixed the problem
I like this post...
Link down... Has anybody got a link for latest stock recovery.img (after 2017 version NXGC47?)