Related
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
So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd
Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.
ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.
Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.
Hello, so i've had this Note 4 for about 2 years, i had no problems with it thus far until recently ( 3 hours ago actually) i was just texting and browsing Instagram and out of no where the screen froze, it became unresponsive and the screen went black and started constantly vibrating so i quickly pulled the battery out and put it back in again, tried to start it again and it got stuck on the Samsung logo, i went for recovery mode and tried to look up latest cashe log and it froze right there too and restarted, pulled battery out and in again, tried to get into Recovery mode for a second time and a dm-verity verification failed error on the lower left corner popped up, i selected "Restart phone" and it got stuck on the Samsung logo again, battery in-out, tried to get into Recovery mode for a third time to do a factory reset but this time it got stuck whilst trying to boot onto recovery, and i had to out-in battery again, tried several times to get into recovery and it didn't work, i just gave up and started searching, then after 14 minutes i decide to give it another try and it normally booted up! i inserted in my PIN and browsed the apps for about 2mins but it froze, again, and the whole cycle kept repeating i let it cool down for 15mins and it boots up normally but freezes again after a few minutes of usage, i noticed that it insanely overheats before freezing (especially right above the SIM card area) and the four CPU cores are showing 2469MHz and on 100% (But that's also the case when the phone just boots up right?), Now i basically can't access recovery mode and i'm stuck with a Freeze-Reboot looped and i'm left with no other option but a full Stock ROM flash, the thing is i can't even get into recovery to do a full wipe before flashing in the ROM, can i just flash in again a TWRP recovery? and is there any way to fix this without having to do a full Stock ROM flash (i Tried the wake lock app it didn't work) and i'm on Android 5.0.1, this has JUST happened today and never before. i'm hoping this isn't a hardware issue.
UPDATE: i have just noticed something rather interesting, the phone immediately freezes and goes nuts with the reboots and failed recovery modes instantly after i connect it to a wifi network, and exactly when it's attempting to "send report", a sending report sign shows up in the notification bar and it immediately screws up the phone until i do another Factory reset, i just did another one without connecting to a wifi network and i've already gone 40mins with it without any issues but perhaps it's just because it's not on heavy usage?
Sounds like you have the eMMC issue.
You can try and reflash with Odin. Get the right version from Sammobile.
Do yu get to download mode in any of the scenarios you describe?
Try WakeLock again and select the level to 4
Having the same issue
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Cybrid013 said:
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Click to expand...
Click to collapse
If you have the Snapdragon version - it's highly possible to have the emmc problem. Which is a bummer and the phone is like dead.
Unless you can buy another 910C motherboard and swap it.
Sorry.
What is short name for emmc?
jjoeshua said:
What is short name for emmc?
Click to expand...
Click to collapse
embedded multimedia controller
Just been having a very similar problem. I posted this elsewhere, but it may be helpful:
"My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1."
Also now downloaded a eMMC bug check that says my eMMC chip is 'sane'. Guess we'll see
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!
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.