bootloop after weeks of normal usage - Xiaomi Mi Mix 2S Questions & Answers

bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?

EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?

Have you tried re-flashing with MiFlash?

Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.

THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed

Related

[Q] Memory leak or something else?

So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.

Still Reboots in Marshmallow

Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.

MOTO G custom ROM weird bug/problem

Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
?? Yep i know this thing few symptoms were shown on my osprey so it happened to me bz i just to test many custom rom and many time there residue remain uncleaned even after many twrp formats (it weird but i think this happens) so try clearing your intenal storageand (no need to clean memory just remove it) even remove you sim crad and memory cards
flash a recovery from your current recovery if there is not update just reflash the current recovery and then just make it a reboot to recovery ( msg will pop up no os found but there will be no issue if you're rebooting directly to the recovery)
So after reboot put your memory card in phone where you will store your rom and gapps ( if memory not detected just reboot to recovery one more time) puff install things let your sim cards in enjoy your rom
If this thing failes go install stock firmware its an ultimate solution
i finally flashed the stock os, hopefully no issues now!
yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
The same issue happened to me yesterday
So, now I am trying to clean flash the custom rom first
I've been running a Lineage OS PIE version on my Moto G3 2015(Osprey) XT 1541 for several months now and not a single problem.I think it's a Fantastic Custom rom that you might like to try,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
Note:
Before installing any Custom rom do a,"Nandroid" backup and then a Factory Reset.
Then once the rom has installed and before setting the phone up do another,"Factory Reset".
I've found this the best way to make sure the install is really good and clean

[HELP NEEDED] Semi-Bricked Oneplus 7 Pro After Substratum theme went awry

I was messing around with substratum themes until I applied one that caused my display to act strange, and possibly the device itself, I cannot seem to boot into either recovery or bootloader modes, the boot animation seems to come on at random, adb doesn't work, and when I hold the power key I get the same Ui element issues (Moving up and down at random) but with stock android reboot, shut down, and lock down buttons. Is there anything I can do or did I brick my oneplus?.
If it helps any I'm on android Q 10.0.2 on a GM1917 with TWRP and Magisk.
turns out holding all the buttons landed me in recovery mode
I'm so lucky holy hecc
nevermind now my /SDCARD/ is empty
woooooooooooooo
I got twrp to view /sdcard/substratum by rebooting twrp, then flashed the rescue zip, and now i'm booted, this thread is now my story of fixing this issue of anyone has to fix theirs!
This is why I love OnePlus. It's like a continuation of the Nexus line. I've had to rescue my phone twice. Yesterday I got a crash dump. Would not boot. If tinkering with software is your thing, this is the phone to get.
tropical cactus said:
This is why I love OnePlus. It's like a continuation of the Nexus line. I've had to rescue my phone twice. Yesterday I got a crash dump. Would not boot. If tinkering with software is your thing, this is the phone to get.
Click to expand...
Click to collapse
As much as I enjoy having a phone that works I do love living on the edge
happened to me when I applied theme for system ui.
that's amazing how unstable oneplus7pro can be.
and there only one way to fix it which involves format.
even safe mode does not help.
no i fixed mine i flashed both rescue zips didn't work so i uninstalled substratum wiped data to all rebooted and reinstalled substratum and same themes went to substratum and they was there to uninstall if not goto data/data and delete themes heres pics of where they are and delete substratum folder kmanager whatever you have
I appear to have got myself into the same problem, and apparently I do not have twrp installed (it was before, but I guess I forgot to flash it again after OTA).
I am rooted but adb now says its device unauthorized and I have no way to authorize it.
How screwed am I? Is there some way I can connect to an external monitor or something? I dont have a recent backup and would lose about a months worth of stuff if I did a reset.
PS: OS loads but all i see is my background flashing. No way to enter pin or fingerprint. Phone also decided to remove usb debugging authorization after 10.3.3 update.
Could have just reflashed ROM in twrp also. Or factory reset which would uninstall all theme.apks

Question Stucked in bootloop

Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
EDIT #2: At 20.11.2022. At around end of october this issue started repeating out of nowhere. And then suddenly stop,
Then the phone bricked. Sent for warranty and just got it back.
Turns out that motherboard died and was the cause.
gol_galad said:
Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thanks, will follow this to make back up and in case it occurs again.
Managed to resolve this problem by draining up my battery due to constant restarts(obviously can't pull out battery). After that happened, connected my phone to normal charger, juiced it up to 10% and phone started just fine.
I have tried to recreate this problem, however it didn't occur again.

Categories

Resources