It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
lc3necro said:
It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
Click to expand...
Click to collapse
Themes not updated for Android O, will crash the phone. Happened to me and a few others yesterday.
There's only like 1 or 2 themes out there that are Android O ready, so read the theme's description before installing it.
lc3necro said:
It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
Click to expand...
Click to collapse
This happened to me as well with DNA Project:
https://play.google.com/store/apps/details?id=com.xdnax.apps.dnadarkproject&hl=en
They have since updated the play store details to include "Does not support Android Oreo"
Go ahead and check out this thread for "safe" options
I actually had this happen the other day while using Onyx, which says it supports Oreo.
Not sure what caused it, but it was while applying system.ui overlays.
I caused this to happen to me by flashing the legacy removal ZIP in TWRP, because I wanted to make sure I removed all remnants. Omfg I'm so pissed right now. I was using Substratum on Oreo (Pixel XL) with Swift Dark Substratum Theme +Oreo & Samsung theme.
I shouldn't have done that...besides one crash in Facebook, everything was fine after disabling the theme. My Pixel 2 XL will be here in 12 days...I don't want to go through setting up this phone all over again :''(
happened to me last night. Lost a lot of priceless photos. Substratum should not install overlays which are not supported on the device.
---------- Post added at 03:12 AM ---------- Previous post was at 03:09 AM ----------
also there must be something to disable the overlays while in recovery. the rescue zip should be made on sd card + it must be flashable through stock recovery for people without root /andromeda users. We pay money for the app and if this is what it does then theaming will not be a really a thing lot of people would like to do.
Related
I got carried away there, so I'll summarize:
Yesterday most of the apps on my phone started crashing. I tried clearing from recovery mode, but nothing went away. Today, I've tried to reflash to stock to get the phone completely clean, but also no good. Even using master clear and reflashing the rom doesn't clear the phone out. Everyone says it works, but the applications are all still there after the reboot, except now they all crash, including launcherpro, leaving me no way to do anything at all on the phone
I'm desperate because my phone is currently unusable. Please help!
Update: I found another method for doing it, listed below, which worked. Still no data though
Anyone have any ideas what might have happened/how I can fix?
2.- :::: CAPTIVATE HARD RESET :::
captivate must be powered OFF to perform this reset, If the device is on, turn it off
- Press and hold both volume buttons + -
- While holding down volume buttons + -, press the power button while maintaining the volume buttons pressed in for around 5 seconds
- Release volume buttons but, keep the power button pressed
- you'll see at&t start up animation release power button
- menu appears
- follow instructions using volume buttons
delete cache data, press power
delete all user data, press power
reboot system, press power
*** (optional) turn off the phone, put my sim card back, turn the phone on
Holy crap... I don't know what's wrong now... I did "Delete user data" and "delete cache" from the boot menu, and STILL everything is there!
What is wrong with my phone?
reflashing to stock... hopefully this does the trick...
ok I went through the process of flashing to stock, and it said it worked, but the old applications are still there!
Now, when I reboot, I get a ton of force close messages; presumably everything that normally would be launching on startup.
how do I actually clear this device and get it back to stock?!
for reference, here's the page I used:
http://forum.xda-developers.com/showthread.php?t=731989
I having the same exact problem where I tried to flash back and I have all these process error message thats dont let me do anything really need some help on this one been at it for hours
seps1816 said:
I having the same exact problem where I tried to flash back and I have all these process error message thats dont let me do anything really need some help on this one been at it for hours
Click to expand...
Click to collapse
Hey there,
I'm afraid this won't help much, but in the end I had to call the AT&T warranty department and get a replacement phone. There's a 1 year on the phone, and while I had to jump through some hoops, they did replace it. If you're within 30 days then you're definitely in luck, as you can take it back to the store you bought it at
Good luck!
Today I accidently entered Safe Mode on my ICS 4.04 Haipai i9200 phone and a user in our thread knew that most Android phones have this feature. Here is what I wrote and it applies to most Android phone systems. If you see the words, "Safe mode" in the lower left corner of their phone and or experiencing boot loop due to force closure. Here is what I wrote:
robarnold is right about Safe Mode and the article he posted (which is now linked in my quoted reply) provides more information about Safe Mode. Please see the attached picture to see what Safe Mode looks like on our phones. If your phone were to enter Safe Mode, those words would appear on all your screens. As per the article, most if not all your apps will be suspended or not work.
Basically there are two known ways to enter Safe Mode:
1. Android detects a problem with a newly installed app and force-closes it while entering into Safe Mode.
2. A combination of key presses at power application;
Newly installed app force-closes the system
The gist of the article provided by Rob says that if a newly installed app causes system conflicts, Android will force close that app to prevent it from possibly doing malicious harm. At the same time, Android will suspend the majority of all other apps and display "Safe mode" in the lower left corner of your phone as per the picture.
The reason for this is to provide the user an opportunity to clean the system of the app which is causing the force closure. Chances are it the most recent app installed but it could be a combination of apps that are coming into conflict with one another.
If you suspect a newly installed app of causing this problem and you see Safe Mode on screen, STOP, COLLECT YOUR WITS and BREATHE NORMALLY. You have several options.
SAFE MODE OPTIONS
1. Press the System or Menu Button in the lower left corner and navigate to Manage apps.
2. Find the most recent app you installed.
3. Force close it.
4. Disable it if possible.
5. Remove this app.
6. Reboot the boot to see if the Safe mode is gone.
If the Safe mode label is still present, the article suggests that it may be necessary to press several keys to achieve the removal of the Safe mode label and its effect of suspending the other apps. In essence, we now move to the second discussion of entry into Safe mode:
1. Safe mode can be entered by pressing buttons at start-up. Most likely, this is what I did today as I was getting ready to leave for an appointment. The Safe Mode label freaked me out and when I could use the Rebooter app or any other app, I became scared.
2. I don't know exactly which buttons I pressed but it mostly likely was the System and Home (center big button) and maybe even the Escape/Back button on the right. My phone slipped slightly as I turned it on and my left thumb was flying as I manuevered my left hand to balance the phone.
3. The right combination of buttons, which supposedly are the same to enter Safe Mode, are the same to exit Safe Mode.
4. If you are certain you entered Safe Mode by accident - meaning you know you did not recently or just now installed an app that force closed Android, then you just have to find the combo to exit it.
5. The article suggests that pressing the volume buttons might clear the Safe Mode on the first reboot after initial entry into Safe Mode.
6. If the Safe Mode label disappears after pressing the volume buttons, your phone is okay.
7. If the label is still present, try rebooting the phone again.
The article suggests as per my experience that if you cannot clear the Safe Mode, your last resort is to do a factory reset of the phone. Fortunately in my case, I had ClockworkMod Recovery available and restored my system via a backup recovery.
ronbo's Final Thoughts
Hope I never see Safe Mode again (and, I won't go looking for it) but I recommend you learn how to do a Factory Reset by pressing and holding the Volume Down Button with a simultaneous press of the Power Button. You want to see the Factory Test and Reset Menu when you are calm. TRUST ME ON THAT!
robarnold said:
Hi,
Yes safe mode exists and is a useful if not essential tool for those of who like to experiment with their Android devices.
I'd suggest that it will always be worthwhile to know how to access Safe Mode and recover from it if you are going to install unsigned apps.
The following link may more useful to those who would like to know more:
http://www.tested.com/news/feature/3071-how-to-use-androids-safe-mode-to-save-a-phone-from-boot-loops/.
Cheers
Rob
Click to expand...
Click to collapse
help me with sony arc s cant get it off
Safe Mode = Wet Phone
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
whoa !!! I just did boot up my xolo a500 in sage mode . I was shocked . so I just pulled my battery and re insterted it . now its normal
Appalbarry said:
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
Click to expand...
Click to collapse
I have this same issue except my phone doesn't have a removable battery (evo 4g lte). My down volume button doesn't work and I can't seem to escape safe mode no matter what I do help?
Sent from my Nexus 7 using Tapatalk 2
guih said:
I have this same issue except my phone doesn't have a removable battery (evo 4g lte). My down volume button doesn't work and I can't seem to escape safe mode no matter what I do help?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Same issue..
skywayskase said:
Same issue..
Click to expand...
Click to collapse
Try the adb command
Adb reboot
sent from my super advanced mini fridge
A work-around for phones stuck in safe mode due to water damage etc but that seem to work fine otherwise is to convert the (trusted) apps you need from data apps to system apps (move the .apk from /data/app to /system/app after installing via the Play Store). You may need to use Mounts2Sd or something similar with an sd-ext partition if you don't have enough space in your internal /system partition for all the apps you need. (With Mounts2Sd, placing the apps in /data/app-system on the sd-ext partition will fool the phone into thinking the apps are in /system/app and you can then use them in safe mode). If anybody is aware of a simpler script that does the same thing, please lmk.
If this helps you, please hit the Thanks button.
i have this on my tab 3 i can't exit from it tried reboot and factory restart and shut down
what is the solution ?
Same issue here...
Appalbarry said:
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
Click to expand...
Click to collapse
I am facing the same problem. I had used my phone in rain. Now the volume down and power button are not working. And the most irritating part is that it rebooted into Safe mode which I dont like. Done factory resetting which took me from safe mode but the volume down and power buttons are still not working.
Anyone knowing how to get rid of these, please share it... Thanks in advance !!!
Lawrence kunhi said:
I am facing the same problem. I had used my phone in rain. Now the volume down and power button are not working. And the most irritating part is that it rebooted into Safe mode which I dont like. Done factory resetting which took me from safe mode but the volume down and power buttons are still not working.
Anyone knowing how to get rid of these, please share it... Thanks in advance !!!
Click to expand...
Click to collapse
How did u get rid of "safe mode"? I have vol down stuck and phone always goes into safe mode
I tried a factory reset from setting>backup and reset>factory data reset and phone shuts down...the i have to press power button and phone gets into safe mode again.
got the same problem with my lenovo a859. it got wet and now just boots into recovery where i can not choose any other options besides the first (reboot system now). Is there any way to start the phone/ do a factory reset?
I have a parental control program on my kids phone.
Safe mode of course enables to erase it.
Is it a way on a rooted android to disable it?
Turn off safe mode
Yes, safe mode does exist. It is the default mode in your android phone without extra apps installed. When in safe mode you cannot use your favourite apps. I understand it can get irritating some times.
You can try rebooting your phone. It worked for me.
---------- Post added at 04:40 PM ---------- Previous post was at 03:51 PM ----------
If that does not work, here's a guide that helped me exit safe mode
Eagleman71 said:
I have a parental control program on my kids phone.
Safe mode of course enables to erase it.
Is it a way on a rooted android to disable it?
Click to expand...
Click to collapse
Did you find a solution to your problem?
Is there anyway to completely disable safe mode, e.g. by adb?
Good day to all. I'm here resorted to ask about my problem here because I really can't handle it. I been googling for days. I'm ran out of resources from both google and tablet. So, I hope you can help me here. Note I'm going to write this in FULL detail here, so expect this to be a extremely long post. (I been warning you) So here goes....
Anyone uses the brand Ramos?(kind of unpopular brand) I use Ramos W21, it's been using it around 1 year and a half, and it endured a lot of problems, but fixed by researching on online forums and apply various methods there. Now, I think it's finally gave up...
One time, when I opened it and play my usual apps and browsing, it caused the errors " unfortunately
google.process.gapps has stopped", unfortunately browser has stoped",and "unforturnately google play has stopped". Then, I tried to clear data the similar apps in settings as usual, and even disabling them. Then more errors exploded, and "unfortunately launcher has stopped" appears. The menu screen(where the usual wallpaper and shortcut apps are located) turns black, while my running apps are still there running. When I pressed the back key to exit the app, now only tons of errors from the launcher appears endlessly(while the screen is black.
The time I finally turned it off by hard reset it made its way to the main problem: the bootloop.
Okay, here's where the thing gets real. It opens with the usual ramos logo, but the next one is a silver flashing android logo instead of enlarged ramos logo with spinning fire from the letter o(which is NOT my usual boot up screen) When I turned it off, it reopens again up to flashing silver android logo and the cycle repeats, even with pin reset until battery dies out. No recovery mode, so I can't use it to fix this. USB connections can't be recognized when inserted to PC. And no, the tablet is not rooted, and I don't customized anything, no mods, and no fancy roms. Just using a stock rom.
So now what? All I have here is just a sd card slot, which I think there's hope in there. Right now it has two options, deal with it and fix with all of might, or repair it in the nearest repair shop(something that is pretty risky, a lot of fakes and robbers here)
Well, this is the first time I post here, so sorry for anything that goes wrong. Thanks in advance.
Hi, thank you for using XDA Assist. It sounds like a rouge app has replaced your boot animation. Rather than try to chase that down and try to fix it I'd flash the stock firmware and start all over. Unfortunately there is very little about your device on XDA. So you'll probably have to google that.
Solved!!!
Update: I FINALLY FIXED IT!!! IT WAS A MIRACLE!!! O.O
After I keep on wrecking it's power buttons and volume buttons, I discovered something decisive!
This tablet actually HAS RECOVERY MODE! Again, it has a recovery mode! However, the way how to input it is very unique compared to most devices, including other devices from the same brand!
Now having the power of recovery state, I first selected "wipe data cache". The old large Ramos logo with spinning fire appeared again! But it's still bootlooping. So I went back on recovery state, selected "factory reset" and boom, IT BOOTS LIKE BRAND NEW!!! (sacrificing my old data though)
Okay, I don't want this recovery mode powers to be kept only by me. So I'm going to share it to all Ramos users,especially the model W21, like right now!
1. To do this, you need power button and volume up button.
2. While bootlooping, hold the power button and volume button at the same time and it will turn it off(Then expect it to turn on back up again automatically)
3. When it opens up again to the small Ramos logo(no fire animation), now RELEASE the POWER BUTTON ONLY, and keep holding the volume up button. Note, this is important! If you do anymore than this, it will either black out, go bootlooping once again, or ultimately, nothing.
4. Keep holding the volume up button, then the ramos logo will disappear, and now it will enter to our holy grail, RECOVERY MODE! Congratz!
Now when you finally have a normal working Ramos tablet again, you may go there again by turning it off by "Power Off" (assuming that your tablet is open) then holding the power and volume up(then follow above!)
I hope this will help a ton for Ramos users! :laugh:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
jd1639 said:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
Click to expand...
Click to collapse
Well thank you then for the link. Gotta go there!
Thread closed.
I followed the guide on here to root my LG stylo but now it is stuck on the TWRP screen and I can't 'swipe to unlock' it nor can I even power off the phone. The status led is red and the phone is completely unresponsive. I just got this phone today to replace my old phone which bit the dust and now am freaking out a bit. I am not new to flashing and checked my software version before doing so and followed the guide carefully and everything went just as described before rebooting twrp. I have never had a phone with non removable battery but holding any combination of hardware buttons for 15 seconds doesn't do anything either.
Your help is very much appreciated.
this phone have removable battery and frist what version you have t mobile boos vm sprint
Thanks I feel so stupid I thought it didn't but I realized it did. So I erased the .twrps file (which I read somewhere while looking for a fix) and removed the battery and it rebooted fine. How can I go back to test twrp or what should my next steps be? This is metropcs btw if that matters.
Btw thanks so kindly for reply quickly.
This and Xposed G4 TweaksBox advanced power menu are my fave ways...
https://play.google.com/store/apps/details?id=gt.reboot.utility This one looks good too, cause ya can enable and disable which reboot options you want to show up in the menu https://play.google.com/store/apps/details?id=com.jc.rebootmanager
Otherwise power + vol up then release power and press it again I believe, or release vol up while holding in power and pressing it again, damn dyslexia I forget and never used the key combination once yet to get into twrp. haha
Read this.
http://androidforums.com/threads/h631-ms631-twrp-2-8-7-0-touch-recovery-lg-g-stylo.926967/page-3
Same happened to me. I have metro.
Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers
kibalcic said:
Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers
Click to expand...
Click to collapse
Try holding volume up + power button for 10-15 seconds phone should power down , when it does hold voume down plus power button should take you to recovery mode.
Hi,
I answer late but I got the same problem with my Oppo Find X2 lite. After dowonloading the Color 0S11.1 update my phone restarted.
But then I couldn't unlock it. The screen was flashing on and off in a bootloop.
I managed to get in recovery mode using the method described above. Unfortunately I couldn't just remove or restart the update and I had to do a full factory reset. Then the Colors OS 11 update went smooth.
I had also debloated my phone but only a few apps and services. I was very careful. So I have another clue : to me it looked like the phone couldn't load the fingerpint id sensor on start screen.
I wonder if it shouldn't be deactivated before any major updates.
@kibalcic : did you manage to solve your problem ?