Database Users

[Q] After unrevoked3 charginf while off locks phone

Hi all,
I have a Wildfire and proceeded to root it by using unrevoked. Followed the instructions and it all went well. To confirm, I also successfully used a root requiring app without problems.
The only thing is I'm unable to charge the phone while its turned off. If I do so, the red light comes up (normal) but never turns green to signal a full charge. It was hooked up all night. And, when I pull the plug, it stays red. The phone doesn't even turn on. I have to remove the battery for a second and the phone works again. As far as I can see, no problems while the phone is powered on.
First of all I wanted to hear if anyone else is having the same problem.
Then, if there's a method to unroot this cell. It's not american and not branded, so I would need a RUU file matching it. How do I search for such a rom?
Thanks!
Fabio

It's a known problem with the unrevoked procedure on Wildfire (as a forum search would have revealed).
I'm afraid I have no idea if an rru will fix it. Easy solution: leave the device on when charging.
Sent from my HTC Wildfire using XDA App

Sorry for the noise, then. But beileve it or not, I did in fact search before posting. What search did you do to obtain results?
Fabio
Edit: sorry, I'm really feeling dumb now. First search, got the result. Again, sorry for the noise!

Just found about that recently and it was the first time I've charged the phone while it's switched off. And yes it is far better off charging it with the phone switched on.

After perma root phone won't shut down completely.

After getting perma root and installing Bacon bits 0.3, when I want to turn my phone off completely it instead just boots back up into the recovery. Does anyone else have this problem or have any ideas how to resolve it?
Sent from my T-Mobile G2 using XDA App

I have no idea, but noticed it too...
Sent from my T-Mobile G2 using XDA App

I am apparently having this problem as well now. I never noticed it before and even after a battery pull my phone seems to boot back into recovery. Any help with this problem would be greatly appreciated. Thanks in advance!

One thing to note is that you need to make sure that you don't have it plugged in and charging. It's known to boot on its own when you do that. I'm not sure if that is a bugged feature or not, but I also have Bacon Bits installed and can shut down fine.
Although, my phone stays on all the time.
Sent from my T-Mobile G2 using XDA App

Ok just tried to turn off my phone with it unplugged and it did not turn on to recovery. So kind of a boo bug for now but I am sure that it will get worked out.

Heh... I'm guessing you all have Clockwork Recovery installed? That's the problem. At least, when I switched to the test keys recovery, it wouldn't constantly start back up with any power regardless of how I shut down.

hmm..i have baconbits installed and dont have this problem. ill look into it

(URGENT) Nexus 4 not turning on. Please help me.

Ok, so here's the problem:
I plugged my limited edition white Nexus 4 into the wall charger, and it locked normally, even the lock animation came. (Didn't power off, just locked.).
I just pressed the power button as I normally would, but it did not ask me for the unlock pattern. In fact, all I could see was a dim LED backlight.
So I searched on Google and then on xda, and found a thread which instructed me to hold down the volume up and power buttons for 20-30 seconds, and then to hold down the power button. I did this, and it made my phone boot up normally. But when I unlocked my phone, I noticed that the screen was flickering. Not black and white or whatever, but between the different brightnesses. I then locked the phone (Not power off).
After turning it back on, there were no problems, in fact, I just rebooted the phone, and it seems to be working fine.
I want to know how I can prevent this problem from happening again, and what to do if this happens again.
I haven't rooted, custom ROMmed or unlocked bootloader, and do not plan to do so. All I have done yet is update my phone to Android 4.3, using an official Google .zip file I found on DroidLife. It is an official file, not a leaked build. I do not think that is relevant, but I thought I should tell you anyway. Also, this may have something to do with the charger, because the phone turned off as soon as I plugged it in, or the timing was just ridiculously good.
Please read this carefully, every line is important. Nexus 4 specs have been given in signature.

poop happens. you cant provide any logs at the moment, so we cant see what happened. just a fyi, stock, official roms, also are buggy occasionally. my guess is that it had a derp somewhere to begin with, it happens. a reboot, or a forced reboot usually resolves the situation. with root, theres a bit more troubleshooting/action that can be taken in a situation like this, maybe even some preventative action like a dalvik wipe.

simms22 said:
poop happens. you cant provide any logs at the moment, so we cant see what happened. just a fyi, stock, official roms, also are buggy occasionally. my guess is that it had a derp somewhere to begin with, it happens. a reboot, or a forced reboot usually resolves the situation. with root, theres a bit more troubleshooting/action that can be taken in a situation like this, maybe even some preventative action like a dalvik wipe.
Click to expand...
Click to collapse
Thanks for the reply
If I root the Nexus 4, will i be able to install OTA?? Even installing through adb sideload is fine with me. Basically, is it possible to root and still get updates? If it is possible, what is the method to install updates? What is the most reliable method to root for Nexus 4? Can I root without installing a custom recovery? I'm not gonna install custom ROMs on the Nexus until it is outdated. Sorry about all the questions, as I am very curious.

[Q] Blinking Red LED Notification

Hi,
I tried to change my file system from Dalvik to ART and when my phone was optimizing apps after reboot, my phone suddenly shut off and it wouldn't turn on. If I try to turn it on, it will show a solid red LED for 3 seconds or so and then start showing a blinking red LED.
I did manage to get into the bootloader and I flashed the whole factory image for Kitkat and erased my data through fastboot, but it didn't fix anything. Anyone know if there's anything else I can do? My phone is outside warranty because I bought it on release date last year :/

Look what this guy had: http://forum.xda-developers.com/showthread.php?p=47968382
Spoiler: it's the exact same issue, and he resolved it. Wouldn't it have been great if you just searched the forums for a similar thread before posting this? I can answer that. Yes, yes it would have been great. It would have saved you time waiting for an answer here. And it would have saved me time writing this rant. So next time, use search.
Sent from my Nexus 4 using Tapatalk

Oh thank you. What great luck that he had the same problem. Does anyone actually know why disconnecting the battery cable would solve the problem? It seems odd that this is caused by a software problem, but a physical fix returned it back to normal.

Problem solved, so i suppose we can close this thread now

Phone keeps turning off! Never while using it & sometimes when phone is not moving.

Phone keeps turning off! Never while using it & sometimes when phone is not moving.
I have an LG-D801 running 4.4.2 kernal 3.4.0 and software D80120a. I also have and use TWRP for recovery. Ever since I rooted my phone and installed this rom, everything has been perfect! That was about 4 months ago. I have and use lots of apps, most of which I have been using for years without any issues. Lately I have been finding my phone off in my pocket for some reason. It now is happening maybe 6-10 times a day which is really getting annoying.
The LG G2 battery doesn't come out so not like it got loose. I have tested it by sitting on the desk lightly and checking it later to STILL find it turned off. So I know I'm not bumping it. I have tried an app killer to kill apps before turning off the screen but it still seems to happen. The phone is still relatively new so I doubt it's hardware, I baby my phones.
Any ideas for ways to make it STAY on without flashing a new rom? Or maybe ideas for how to diagnose what is shutting it down?
(I am looking for ideas and useable feedback, please don't respond that my phone has hardware issues and needs to be replaced!)

UnknownCloakedMan said:
I have an LG-D801 running 4.4.2 kernal 3.4.0 and software D80120a. I also have and use TWRP for recovery. Ever since I rooted my phone and installed this rom, everything has been perfect! That was about 4 months ago. I have and use lots of apps, most of which I have been using for years without any issues. Lately I have been finding my phone off in my pocket for some reason. It now is happening maybe 6-10 times a day which is really getting annoying.
The LG G2 battery doesn't come out so not like it got loose. I have tested it by sitting on the desk lightly and checking it later to STILL find it turned off. So I know I'm not bumping it. I have tried an app killer to kill apps before turning off the screen but it still seems to happen. The phone is still relatively new so I doubt it's hardware, I baby my phones.
Any ideas for ways to make it STAY on without flashing a new rom? Or maybe ideas for how to diagnose what is shutting it down?
(I am looking for ideas and useable feedback, please don't respond that my phone has hardware issues and needs to be replaced!)
Click to expand...
Click to collapse
Are you sure it's actually off and not just asleep and not waking up. I've never seen a generally working phone turn itself off. On another device we called it the SOD (Sleep of Death) and required a long press on the power to reboot. It's most likely a rooted app like something Xposed related perhaps.

wolfclan68 said:
Are you sure it's actually off and not just asleep and not waking up. I've never seen a generally working phone turn itself off. On another device we called it the SOD (Sleep of Death) and required a long press on the power to reboot. It's most likely a rooted app like something Xposed related perhaps.
Click to expand...
Click to collapse
How can I tell the difference? Basically I press the power button once quickly to turn the screen on and it doesn't come on. I hold it for maybe 3 seconds and get the booting up stuff. I am guessing if it was sleeping I'd have to hold it much longer?

UnknownCloakedMan said:
How can I tell the difference? Basically I press the power button once quickly to turn the screen on and it doesn't come on. I hold it for maybe 3 seconds and get the booting up stuff. I am guessing if it was sleeping I'd have to hold it much longer?
Click to expand...
Click to collapse
Yeah bud, that's a new one on me. Do you have any root apps that could be the cause? Like Xposed.

wolfclan68 said:
Yeah bud, that's a new one on me. Do you have any root apps that could be the cause? Like Xposed.
Click to expand...
Click to collapse
Thanks for the help. After reading your previous post, I decided to remove GravityBox KK and Xposed. I was using it because I find it annoying that when I plug in my phone at night, it turns on my screen. Not a big deal...
I also use SuperSU and LuckyPatcher which both use root. The only other thing I can think of is that I semi-recently upgraded my Play Store (v4.8.19 using Lucky Patcher) which I had some troubles with. It kept saying my /system was out of space and for some reason, even with root, it tells me acces denied when changing stuff inside the /system such as boot animation.

so... just an update. It's still doing it even after I uninstalled all the apps that need root. I really wish there was a log or something (like Windows) to tell me why it keeps turning off!
I have noticed it seems to happen much more often if I am texting somebody even though I'm using the default app for messages. It literally was turning off after every message I sent early before the other person was able to reply for about 5 messages in a row.