stuck on "pixel is starting" fix - Google Pixel 2 Guides, News, & Discussion

Thanks for stopping by,
I've had this issue a few times now where I'd restart the phone and would be stuck on the "pixel is starting" message for hours and while googling could only find a factory reset would fix the issue. So instead of resetting for the forth time I figured what do I have to lose if I had to reset anyway. Finally got it to start up without a reset. Here's what I did.
1.reboot into twrp
2.advanced>fix recovery boot loop>reboot
3.reboot back into twrp>flash magisk
4.profit!
Hope this helps anyone that runs into this.

I've always been able to three finger salute it and it boots up. Shouldn't ever take more than a minute or two.
Sent from my Pixel 2 using Tapatalk

Update:
Was able to reproduce the never ending pixel is starting.
Turns out it was the fingerprint unlock after reboot tweak I use.
Turned it off and issue is fixed. Turned on the issue returns.
Think it may have to do with the encryption after fp are entered.
Really enjoyed not having to enter a pin on start up. I can live without it though.

I flashed Magisk without TWRP and I was stuck on the "Pixel is Starting" on my Pixel 3. I found this thread.
I turned my screen off, let it sit for a minute, then turned it back on and it said it needed to be unlocked. I did it again, then used my Fingerprint to activate the "unlock" screen you see after a fresh reboot.
It let me put in a pattern and opened fine.
So yeah I think it does have to do with encryption \ Fingerprint but it looks like that way just let me beat it -- hope that works for someone.

Related

Pattern changed by itself?

Hi,
Has anyone ran into this issue where the pattern changed itself or no longer worked? I definitely did not update or change it. All of sudden today, it just stopped taking it. Initially, I was able to unlock with my fingerprint. However, when I went into lock screen settings to try and figure out what's the issue, it prompts of course for the pattern. It then of course said it was incorrect and then told me to try again. Now I'm currently locked out 60 minutes and my fingerprint doesn't work anymore either! This is such an annoying bug and have no idea how this came about since I haven't updated or downloaded any new apps. I've also rebooted several times as others have stated, and the problem persists..
This worked for me!
itsxiao said:
Hi,
Has anyone ran into this issue where the pattern changed itself or no longer worked? I definitely did not update or change it. All of sudden today, it just stopped taking it. Initially, I was able to unlock with my fingerprint. However, when I went into lock screen settings to try and figure out what's the issue, it prompts of course for the pattern. It then of course said it was incorrect and then told me to try again. Now I'm currently locked out 60 minutes and my fingerprint doesn't work anymore either! This is such an annoying bug and have no idea how this came about since I haven't updated or downloaded any new apps. I've also rebooted several times as others have stated, and the problem persists..
Click to expand...
Click to collapse
Hey- I had the same issue happen to me yesterday. I was able to accidentally find a solution by following these steps
1. Turn off your Android device.
2. Press and hold the "power", "volume down", and "bottom" buttons simultaneously. ...
3. Release the buttons once your Android device is powered on.
4. A Warning screen will appear, press the volume down option to cancel and (restart phone)
5. Phone will restart and ask for your pin, the original pin should now be working again.
6. Add your other fingers to the scanner! - at least that's what I did

S5 SM-G900F : Black screen/Boot loop; Help?

tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits

Stock 7.1.2 stuck in boot loop, fix doesn't work, can only get to fastboot

This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
chmmr said:
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
Click to expand...
Click to collapse
I have the exact same issue. I run the same version operating system as you have an unlocked bootloader otherwise have not modified the typical system install. I did already have the fix applied from an earlier incident but now it is boot looping and won't stop. I have red threads here and there that have advised to apply heat to the phone and that might get it to boot at least to get your data off. Myself I have had no such luck with this technique but perhaps it will work for you otherwise I have since moved on to the OnePlus 6t. A very awesome replacement not to mention at a decent price for more horsepower and storage
Sent from my ONEPLUS A6013 using Tapatalk
Just in case it helps anyone with this phone and issue, I was able to get a couple more boots out of it, enough to rescue some data, by doing the "15 minutes in the freezer in a ziploc bag" trick.
RIP Nexus 6P, shame about the BLOD!

Random boot loops on new Redmi Note 7 (Stock 10.3.5 MiUI non root)

Saturday night, I plug my 1 week old phone on the charger at 9%. I power off the phone and see the battery charging animation. I turned it back on as usual but this time my phone did something I've never seen before.
It started bootlooping!
I was like what the hell.
It loaded up to the lock screen and then rebooted. This happened over and over again for about an hour.
After googling, I found a thread about a Redni Note 5 pro having the same issue.
The solution was to hold power and Volume down until the phone rebooted to recovery.
After doing that, I was presented with the option to reboot to system, wipe phone (which I definitely didn't want) and connect to My Assistant.
I chose the first option and sure enough....my phone was stuck in a boot loop once again.
This is my first Xiaomi phone. It's not rooted at all and has locked bootloader on the stock 10.3.5 ROM. Fresh out the box...just a few apps, some photos and texts.
I've seen stuff like this before happen with rooted phones but never on a brand new non rooted phone.
Fortunately (and with lots of prayer), I was able to let the phone battery drain out completely since it wouldn't power off.
Sunday morning, I plugged it back on the charger and to my surprise, I saw the battery animation only this time!
After charging fully, I turned it on and saw it bootlooping again. After 5 mins, I decided to remove both my SIM tray with both SIM and micro SD.
THIS time, the phone stopped bootlooping entirely! Again....what the hell was my question ?.
Normally, my nerves are steel but yesterday, they were more like spaghetti lol
Against my own judgement, I wanted to test if it was my own SIM card causing the issue or if my micro SD card caused the issue.
I placed the SIM try back in with each card 1 by 1 however, the phone immediately started bootlooping on it's own right from system!
I've never seen this before with any other phone or brand I've used in the past.
This activity occurred again and again regardless which card was inserted. With no cards, the phone worked normally.
I decided, you know what, at this point, I'm going to back up my data during and factory reset since now I have access.
Thank God that worked!
After many hours of backing up data, factory resetting my phone and then restoring everything on Mother's Day ( which meant working around free time and planned activities with my Wife), I am happy to say my phone is back working normally with the same SIM card and Micro SD as if nothing happened.
Fluke or not, definitely going to be watching this phone carefully to see if the problem is gone for good.
I will say this, when I first took the phone out the box last week, I turned it on and watched it update to MiUI 10.3.5. Normally I factory reset my phones after updates to be safe but since the phone was still new, I did not factory reset this time. That could be the reason it did this...I'm still not sure.
Sometimes I power my phones off, connect the charger and turn them on. For years I've never had an issue or doing it this way. For a few days I didn't have an issue with my Redmi Note 7 either. After this experience, I will stop doing that entirely.
My question is, have any of you encountered random random boot loops with any of your Xiaomi products? How did it occur and how did you fix it?
Got the same problem, fixed it the same way
tiguy99 said:
Saturday night, I plug my 1 week old phone on the charger at 9%. I power off the phone and see the battery charging animation. I turned it back on as usual but this time my phone did something I've never seen before.
It started bootlooping!
I was like what the hell.
It loaded up to the lock screen and then rebooted. This happened over and over again for about an hour.
After googling, I found a thread about a Redni Note 5 pro having the same issue.
The solution was to hold power and Volume down until the phone rebooted to recovery.
After doing that, I was presented with the option to reboot to system, wipe phone (which I definitely didn't want) and connect to My Assistant.
I chose the first option and sure enough....my phone was stuck in a boot loop once again.
This is my first Xiaomi phone. It's not rooted at all and has locked bootloader on the stock 10.3.5 ROM. Fresh out the box...just a few apps, some photos and texts.
I've seen stuff like this before happen with rooted phones but never on a brand new non rooted phone.
Fortunately (and with lots of prayer), I was able to let the phone battery drain out completely since it wouldn't power off.
Sunday morning, I plugged it back on the charger and to my surprise, I saw the battery animation only this time!
After charging fully, I turned it on and saw it bootlooping again. After 5 mins, I decided to remove both my SIM tray with both SIM and micro SD.
THIS time, the phone stopped bootlooping entirely! Again....what the hell was my question .
Normally, my nerves are steel but yesterday, they were more like spaghetti lol
Against my own judgement, I wanted to test if it was my own SIM card causing the issue or if my micro SD card caused the issue.
I placed the SIM try back in with each card 1 by 1 however, the phone immediately started bootlooping on it's own right from system!
I've never seen this before with any other phone or brand I've used in the past.
This activity occurred again and again regardless which card was inserted. With no cards, the phone worked normally.
I decided, you know what, at this point, I'm going to back up my data during and factory reset since now I have access.
Thank God that worked!
After many hours of backing up data, factory resetting my phone and then restoring everything on Mother's Day ( which meant working around free time and planned activities with my Wife), I am happy to say my phone is back working normally with the same SIM card and Micro SD as if nothing happened.
Fluke or not, definitely going to be watching this phone carefully to see if the problem is gone for good.
I will say this, when I first took the phone out the box last week, I turned it on and watched it update to MiUI 10.3.5. Normally I factory reset my phones after updates to be safe but since the phone was still new, I did not factory reset this time. That could be the reason it did this...I'm still not sure.
Sometimes I power my phones off, connect the charger and turn them on. For years I've never had an issue or doing it this way. For a few days I didn't have an issue with my Redmi Note 7 either. After this experience, I will stop doing that entirely.
My question is, have any of you encountered random random boot loops with any of your Xiaomi products? How did it occur and how did you fix it?
Click to expand...
Click to collapse
Hello,
today I got the same issue as you stated above.
I tried to remove the SIM card (while the phone is on) and the phone brought me to the startscreen instantly. Inserting the SIM card caused the bootloop again ..
I googled this issue and found this thread,
went into the Recovery mode (Power + Volume Up) and did the Data Wipe.
Consequently, I could start the phone with my SIM card without problems ..
Later I found out, that removing the "Telephone"-permission from the "Contacts and dialer" app caused the bootloop.
(On my Stock 10.3.4 MiUI non root)
Greeting,
Dorian Rec
Dorian Rec said:
Hello,
today I got the same issue as you stated above.
I tried to remove the SIM card (while the phone is on) and the phone brought me to the startscreen instantly. Inserting the SIM card caused the bootloop again ..
I googled this issue and found this thread,
went into the Recovery mode (Power + Volume Up) and did the Data Wipe.
Consequently, I could start the phone with my SIM card without problems ..
Later I found out, that removing the "Telephone"-permission from the "Contacts and dialer" app caused the bootloop.
(On my Stock 10.3.4 MiUI non root)
Greeting,
Dorian Rec
Click to expand...
Click to collapse
Adding all permissions in contacts& dialer is the solution - you saved my day!
man ... it saved my life thanks a lot. it 100% worked.
That is awesome!
Glad I could help out.
Talk about scary situation....caused by a simple glitch in Miui 10.3.5.
Wonder if the fixed it with the updates...
To scared to update right now since everything has been running smoothly since on my 10.3.5 phone.
Can anyone else share of this problem still occurs on newer versions?
Dorian Rec said:
Hello,
today I got the same issue as you stated above.
I tried to remove the SIM card (while the phone is on) and the phone brought me to the startscreen instantly. Inserting the SIM card caused the bootloop again ..
I googled this issue and found this thread,
went into the Recovery mode (Power + Volume Up) and did the Data Wipe.
Consequently, I could start the phone with my SIM card without problems ..
Later I found out, that removing the "Telephone"-permission from the "Contacts and dialer" app caused the bootloop.
(On my Stock 10.3.4 MiUI non root)
Greeting,
Dorian Rec
Click to expand...
Click to collapse
tiguy99 said:
That is awesome!
Glad I could help out.
Talk about scary situation....caused by a simple glitch in Miui 10.3.5.
Wonder if the fixed it with the updates...
To scared to update right now since everything has been running smoothly since on my 10.3.5 phone.
Can anyone else share of this problem still occurs on newer versions?
Click to expand...
Click to collapse
10.3.6 PFGEUXM here - no glitch so far
Hi mine went on a bootloop but I have removed my sim and SD card and it continues to be on bootloop. Since I have a lot of data I can't do wipe data. Can you guys help me
Hello,
I am having the same issue of boot looping on my Redmi note 7 PRO. I also want to enter boot menu so atleast I can do anything, but doing force shut down (Volume down+power) I came across "FASTBOOT" mode. To get out of that I pressed and hold the power button for a while and it went again in a boop loop. Can you guys please help, I am still not able to turn it on.
Greeting,
Akash Parmar.
Akashparmar1999 said:
Hello,
I am having the same issue of boot looping on my Redmi note 7 PRO. I also want to enter boot menu so atleast I can do anything, but doing force shut down (Volume down+power) I came across "FASTBOOT" mode. To get out of that I pressed and hold the power button for a while and it went again in a boop loop. Can you guys please help, I am still not able to turn it on.
Greeting,
Akash Parmar.
Click to expand...
Click to collapse
most probably removing the "Telephone"-permission from the "Contacts and dialer" app is causing the bootloop - remove SIM and data card, start phone, fix the settings issue the get back the SIM
bootloop on my global version of redmi note 7
BThis last monday after all day work. I sat down and watch on youtube and after a few minutes my phone suddenly went black and when i turn it on it gets stuck on the logo redmi by Xiaomi then turns off.up until now i cant Open my phone. Pls help me resolve this matter. Thanks
[email protected] said:
BThis last monday after all day work. I sat down and watch on youtube and after a few minutes my phone suddenly went black and when i turn it on it gets stuck on the logo redmi by Xiaomi then turns off.up until now i cant Open my phone. Pls help me resolve this matter. Thanks
Click to expand...
Click to collapse
did you take off the card memory and sim?
Hi,
I am also facing the same problem since yesterday ecening, when I turn restarted my phone it gets stuck on the logo redmi by Xiaomi then turns off.up until now i cant Open my phone.
Also, I am unable to enter the fastboot or fatory reset menu as the fastboot menu ony flashes for a second and it again goes into the infinite loop.
Pls help me resolve this matter, any poiner would be appreciated. Thanks
hbhasin said:
Hi,
I am also facing the same problem since yesterday ecening, when I turn restarted my phone it gets stuck on the logo redmi by Xiaomi then turns off.up until now i cant Open my phone.
Also, I am unable to enter the fastboot or fatory reset menu as the fastboot menu ony flashes for a second and it again goes into the infinite loop.
Pls help me resolve this matter, any poiner would be appreciated. Thanks
Click to expand...
Click to collapse
How you solved this issue?
It's MIUI 11.0.1 still the same problem
Ok I updated my phone to MIUI 11.0.1 it still has the same problem but thanks to everyone in this thread I
finally fixed this problem that kinda scared the crap out of me.
Thanks Everyone
I did not know this was a thing until last night. I'm on MIUI 11.0.9
My phone restarted out of nowhere and then my flash light came on by itself, gps was turning on by itself and the reboot/switch off screen kept coming and going, little while later it went into the loop. wouldn't even get to the android screen, i couldn't go into recovery mode either it was so bad. I let it die last night and after seeing this thread i plugged it in, and took out the sim (no memory card). So it seemed to work, though the torch and reboot/switch off screen did show up but nothing like yesterday where it kept interrupting me while i was trying to backup my data. Luckily i do a manual back up regularly.
I changed the "Telephone" permission and it went into the bootloop immediately. It turned on, and i started to backup the last of my data and it went into bootloop again. It's been 10 minutes now.
I noticed it seemed to go into bootloop every time i turned off gps,cell data, or was clearing files from my phone. Honestly i thought i was being hacked. Any suggestions on what I can do?
Srushti97 said:
I did not know this was a thing until last night. I'm on MIUI 11.0.9
My phone restarted out of nowhere and then my flash light came on by itself, gps was turning on by itself and the reboot/switch off screen kept coming and going, little while later it went into the loop. wouldn't even get to the android screen, i couldn't go into recovery mode either it was so bad. I let it die last night and after seeing this thread i plugged it in, and took out the sim (no memory card). So it seemed to work, though the torch and reboot/switch off screen did show up but nothing like yesterday where it kept interrupting me while i was trying to backup my data. Luckily i do a manual back up regularly.
I changed the "Telephone" permission and it went into the bootloop immediately. It turned on, and i started to backup the last of my data and it went into bootloop again. It's been 10 minutes now.
I noticed it seemed to go into bootloop every time i turned off gps,cell data, or was clearing files from my phone. Honestly i thought i was being hacked. Any suggestions on what I can do?
Click to expand...
Click to collapse
Try turning off the call logs premission in the contacts app
Srushti97 said:
I did not know this was a thing until last night. I'm on MIUI 11.0.9
My phone restarted out of nowhere and then my flash light came on by itself, gps was turning on by itself and the reboot/switch off screen kept coming and going, little while later it went into the loop. wouldn't even get to the android screen, i couldn't go into recovery mode either it was so bad. I let it die last night and after seeing this thread i plugged it in, and took out the sim (no memory card). So it seemed to work, though the torch and reboot/switch off screen did show up but nothing like yesterday where it kept interrupting me while i was trying to backup my data. Luckily i do a manual back up regularly.
I changed the "Telephone" permission and it went into the bootloop immediately. It turned on, and i started to backup the last of my data and it went into bootloop again. It's been 10 minutes now.
I noticed it seemed to go into bootloop every time i turned off gps,cell data, or was clearing files from my phone. Honestly i thought i was being hacked. Any suggestions on what I can do?
Click to expand...
Click to collapse
It looks like a hardware problem, if your phone gets into bootloop even there is no sim card - try to change to the other position for the sim card
same issue
gosh scared the xxxx out of me too! I was uninstalling updates uninstall to my redmi note 7 cause too little space and it went into reboot loop. removed sim and giving permission works. I wonder how to do it if removing sim didn't help me boot! how would j have been able to add back permission. what's worrying was I didn't remove any permissions , I only did uninstall updates to all xiaomi apps
---------- Post added at 01:58 AM ---------- Previous post was at 01:52 AM ----------
tiguy99 said:
Saturday night, I plug my 1 week old phone on the charger at 9%. I power off the phone and see the battery charging animation. I turned it back on as usual but this time my phone did something I've never seen before.
It started bootlooping!
I was like what the hell.
It loaded up to the lock screen and then rebooted. This happened over and over again for about an hour.
After googling, I found a thread about a Redni Note 5 pro having the same issue.
The solution was to hold power and Volume down until the phone rebooted to recovery.
After doing that, I was presented with the option to reboot to system, wipe phone (which I definitely didn't want) and connect to My Assistant.
I chose the first option and sure enough....my phone was stuck in a boot loop once again.
This is my first Xiaomi phone. It's not rooted at all and has locked bootloader on the stock 10.3.5 ROM. Fresh out the box...just a few apps, some photos and texts.
I've seen stuff like this before happen with rooted phones but never on a brand new non rooted phone.
Fortunately (and with lots of prayer), I was able to let the phone battery drain out completely since it wouldn't power off.
Sunday morning, I plugged it back on the charger and to my surprise, I saw the battery animation only this time!
After charging fully, I turned it on and saw it bootlooping again. After 5 mins, I decided to remove both my SIM tray with both SIM and micro SD.
THIS time, the phone stopped bootlooping entirely! Again....what the hell was my question .
Normally, my nerves are steel but yesterday, they were more like spaghetti lol
Against my own judgement, I wanted to test if it was my own SIM card causing the issue or if my micro SD card caused the issue.
I placed the SIM try back in with each card 1 by 1 however, the phone immediately started bootlooping on it's own right from system!
I've never seen this before with any other phone or brand I've used in the past.
This activity occurred again and again regardless which card was inserted. With no cards, the phone worked normally.
I decided, you know what, at this point, I'm going to back up my data during and factory reset since now I have access.
Thank God that worked!
After many hours of backing up data, factory resetting my phone and then restoring everything on Mother's Day ( which meant working around free time and planned activities with my Wife), I am happy to say my phone is back working normally with the same SIM card and Micro SD as if nothing happened.
Fluke or not, definitely going to be watching this phone carefully to see if the problem is gone for good.
I will say this, when I first took the phone out the box last week, I turned it on and watched it update to MiUI 10.3.5. Normally I factory reset my phones after updates to be safe but since the phone was still new, I did not factory reset this time. That could be the reason it did this...I'm still not sure.
Sometimes I power my phones off, connect the charger and turn them on. For years I've never had an issue or doing it this way. For a few days I didn't have an issue with my Redmi Note 7 either. After this experience, I will stop doing that entirely.
My question is, have any of you encountered random random boot loops with any of your Xiaomi products? How did it occur and how did you fix it?
Click to expand...
Click to collapse
I cannot thank you enough!!
charles2020 said:
gosh scared the xxxx out of me too! I was uninstalling updates uninstall to my redmi note 7 cause too little space and it went into reboot loop. removed sim and giving permission works. I wonder how to do it if removing sim didn't help me boot! how would j have been able to add back permission. what's worrying was I didn't remove any permissions , I only did uninstall updates to all xiaomi apps
---------- Post added at 01:58 AM ---------- Previous post was at 01:52 AM ----------
I cannot thank you enough!!
Click to expand...
Click to collapse
Anytime!
Glad I can help
tiguy99 said:
That is awesome!
Glad I could help out.
Talk about scary situation....caused by a simple glitch in Miui 10.3.5.
Wonder if the fixed it with the updates...
To scared to update right now since everything has been running smoothly since on my 10.3.5 phone.
Can anyone else share of this problem still occurs on newer versions?
Click to expand...
Click to collapse
Seems like this problem exists on MIUI 12.5 too. I haven't tested the fix yet.

Need fix for screen lock not getting recognized

2 years ago I rooted my Redmi note 7s using TWRP and Magisk. Since then i haven't been able to setup any screen lock or fingerprint lock because the phone just refuses to recognize it as correct. Upon resetting, when the setup wizard asks to setup fingerprint, the sensor doesn't respond at all but when the screen is turned off i can turn it back on when touching the fingerprint sensor. I have been using it without a lock without any issues but now i have decided to give it for exchange so i need to fix this problem. When I rooted, I flashed magisk and a file called disable dm-verity. Looked everywhere online but can't see any relation between dm-verity and screen lock so i am pretty much clueless about what caused this issue. Factory resetting the phone doesn't help either. Hope someone has a solution for this or some insight as to what's causing this.
shawns7 said:
2 years ago I rooted my Redmi note 7s using TWRP and Magisk. Since then i haven't been able to setup any screen lock or fingerprint lock because the phone just refuses to recognize it as correct. Upon resetting, when the setup wizard asks to setup fingerprint, the sensor doesn't respond at all but when the screen is turned off i can turn it back on when touching the fingerprint sensor. I have been using it without a lock without any issues but now i have decided to give it for exchange so i need to fix this problem. When I rooted, I flashed magisk and a file called disable dm-verity. Looked everywhere online but can't see any relation between dm-verity and screen lock so i am pretty much clueless about what caused this issue. Factory resetting the phone doesn't help either. Hope someone has a solution for this or some insight as to what's causing this.
Click to expand...
Click to collapse
Try with this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

Categories

Resources