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
Related
So I was playing with my nexus s and the screen shut off with out the old TV animation and woke it back up and I see SAFE MODE in the bottom left.
I rebooted and was back to normal..... has anybody else had this problem and how did it happen? What caused it?
Sent from my Nexus S using XDA App
I had the same thing happen to me last night as well. I'm not sure what caused it? Like you I rebooted my phone, and I was all good again.
Happened to me yesterday when booting the phone. Rebooted and everything went back to normal.
that happened to me when i had my HTC Hero CDMA
i never figured out what it was.
I had this same thing on my myTouch 3G. If you held down a button while starting up it put the
Phone in Safe Mode. It basically made all non-default applications not work. Did you guys try starting it up while holding a button?
Sent from my T-Mobile myTouch 3G Slide using XDA App
I had the same thing. I remember I was trying to boot into bootloader with the down volume key. That didn't work but I think that may have been the cause. Of course I now know it's the up button that does it all.
Sent from my Nexus S using XDA App
Hi guys from what i have read the safe mode is in case you get app. that starts to act up my making your phone go nuts you can go in to safe mode by turn off your phone and while turning it on hold the menu button you go in to safe mode that way no third party app. are loaded so you can delete the app. that gave you the trouble that's what i have seen on the nexus s!!!!!!
good deal. I remember that I was wiping the screen off on my shirt while booting. Must have been what caused it. Useful info for the future for sure.
It happens when you turn on teh phone and half way through the boot process you hold the volume buttons
I just finished uninstalling everything on this phone thinking it was an app doing this. Tonight is the first I've noticed this.
Here's the scenario. Phone is on and plugged into charger in car. I have root and recovery. No problems with those installs. I try to shut off the phone and it goes like it did, then a few seconds after the charge light comes on when the phone is off, it boots into recovery by itself. I pulled the battery and no change. I turn the phone off while unplugged and it stays off. Keeping the phone off, I plug it into the charger and recovery boots up. This is the strangest friggin thing I've ever seen!
I'm going to ruu it when I get home shortly. I will see if it does it then. If okay then I will root it and see if it does it. If not then I will install recovery and see if it does it. I don't think it was doing this with root only but I will see when I get home.
If it turns out to be recovery, I can live without it for a while until a newer version comes out. I prefer rooted stock anyways. Anyone seen this? I doubt it.
Sent from my PG06100 using XDA App
Others were talking about having this issue, so it could very well be a preliminary issue with root on the shift
Sent from a truly Epic phone and a transparent XDA app
This is a known issue with CW recovery. I am thinking about learning how to make a recovery for us, as this really bothers me.
cloverdale said:
This is a known issue with CW recovery. I am thinking about learning how to make a recovery for us, as this really bothers me.
Click to expand...
Click to collapse
Please do! Mine boots into recovery anytime I plug the charger in while the phone's off.
^ Shift Faced
I ruu'd and rooted and will stay this way until things get ironed out.
jesusice said:
Please do! Mine boots into recovery anytime I plug the charger in while the phone's off.
^ Shift Faced
Click to expand...
Click to collapse
I am working on it, but since I know no java, it will take some time.
Finally got mine rooted today, ran into some weird issues, but haven't experienced this issue. I did run into some issues with it plugged in an booting the phone. It wouldn't boot when power was pressed. Charge light would also stay on after it was unplugged. Battery pull resolved my issue. Not the same I know but kinda quirky
Hello all,
Received my a7 a few days ago and was noticing sometimes it wouldn't wake up when it went to standby. The green indicator on the top of the device became solid instead of blinking which I assume means its not in standby anymore, but the screen remains blank. I thought a factory reset would fix the problem, but it didnt. I installed dexters mod last night and it did nothing to fix the problem. Any suggestions? Should I send it back or is there a fix for this?
Adam
You can't send back while you have custom ROM. Revert to stock ROM and try to reproduce the problem. Install 2-3 applications and check. Then install a few apps again.
I think it's app fault.
Sent from my HTC Glacier using XDA App
I just installed the new firmware and its doing the same thing, even before installing any apps. Gonna send it back.
Sent from my SAMSUNG-SGH-I897 using XDA App
Mine did this briefly, I removed power cord, pressed reboot button with paperclip, then went to recovery mode and did factory wipe. I've been good ever since. This did not help until I tried with cord out for entire process.
Hi
I have a rooted stock ROM/Theme MT4G which I noticed last week that it stopped going to sleep. If I set the timeout to 15 seconds (or anything) then right after the timeout is reached the screen sleeps and then within a second immediately comes back on (to the lock screen). It keeps doing that no matter what settings I try. This of course kills the battery life with my screen being nearly 100% of use.
I thought it was related to an app update so I removed nearly everything I could to no avail. Thinking that it was something related to the ROM I decided to try a different ROM. I installed CM7RC2 and low and behold the same problem persisted. I had to disable trackball wake for this problem to go away. I then tried several other ROMs and the problem still remained. I've attempted the various Royal* ROMs and the same problem persisted. Any Sense based ROM was problematic since I had no way of disabling Trackball Wake so I'm now running CM7 (nighties).
The other snag I'm having is that I too have the problematic power button but in my case I have to REALLY press hard to operate the power button which of course is annoying.
Anyone have any suggestions or experience with this sort of problem?
Thanks.
Did you check out the Cyanogen mod 7 in settings ?
I did. That's what I'm running now.what exactly are you suggesting? Thanks.
Sent from my HTC Glacier using XDA App
I have the same exact issue, ive been trying to get some devs to add the disable trackpad wake option in sense roms but so far nothing so right now i use either royalginger or royalmiui im on miui but i really miss sense :/
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah ive tried that be4 with no luck
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
I must have done that a bunch of times already but nothing worked except CM7 because I can disable the trackpad wake function. I wish Sense based ROMs allows for disabling the trackpad...that would be greatly appreciated. An even more helpful feature is the ability to remap the buttons.
Is it possible your trackpad is defective? DO you notice other odd behavior that could be related to it?
If your using google voice its the application doing that you can fix this on cm 7 by moving the application to the Sd card.
Sent from my HTC Glacier using XDA Premium App
I believe this is a real hardware issue... It seemed that the optical sensor in the trackpad is broken and it's always sending signal to the kernel telling that it detected activity but in reality nothing was going on, so the kernel can never go into power saving mode.
Sense UI is a CLOSED SOURCE software, there's nothing you can do to patch it.
Since ALL MT4G are still under the 1 year Manufacturer's warranty, you should call T-Mobile/HTC to get it fixed or just get a replacement....
Ok I found a solution for us mt4g owners with the messed up trackpads, you are gonna have to flash virtuous unity rom v. 2.39 and then apply this patch:
http://dl.dropbox.com/u/28766802/Virtuous/trackpad_disabled.zip
This patch was made by one of the developers of the rom chrisch1974 specially for this issue, so good luck =D
Same problem, but found work-around
My phone (MT4G) has the same issue but I know why it happened. I got caught in the rain and although I had the phone in my pocket, it got wet. Everything works except that. I left in a bag of rice overnight to no avail.
Anyway, when I press the power button to send it to sleep mode, it just comes back to the lock screen. If I let it time out, it goes out but comes right back to the lock screen. Sounds familiar?
What works for me is holding the home button (the one with the sensor) and, while still holding the home button, pressing the power button once. It is then that I let go of the home button.
Works, but sometimes I have to repeat this charade a couple of times before it sticks. Usually have to repeat it when I don't fully press the home button.
Anyway, hopefully this will help someone that is stuck with this phone and is unable to get a replacement.
Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert
Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app
I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app
The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.
It's 4 days old. Send it back as defective.
turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.
I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium
Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.
did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.
I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.
I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok
Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...
djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.