heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
re: auto updates
Smokie Smokerson said:
heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
Click to expand...
Click to collapse
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Misterjunky said:
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Click to expand...
Click to collapse
Thanks for the reply dude.
I'd love to do that, but i dont see how this is possible since the phone doesnt boot up at all anymore.
Any ideas?
Maybe your battery is dead? Because it's known issue on Galaxy S4 phones.
Try another charger.
I tried with my wife's S4 battery and my colleague's S4 battery.
Also tried with 3 different charges that came with the S4, no dice... :/
I had to take it back to the store, it was under warranty still.. they are sending it back to Samsung and will get it back in 2-3 weeks, same phone repaired or a refurb i guess.
After doing more search and with the help of some falks from #Android @ EFNET, we came to the conclusion that its an issue with the EMMC chip just like the first generation of Note 2 and S3.
What's pissing me off is that Samsung fixed the issue on Note 2 with a new patch of phones, so newer phones didnt have the EMMC issue as far as i can tell. SO why the hell would they still use it for the S4 is beyond me.
Just a word of advice, if this happens to anyone, make sure you run a backup as soon as it boots back up the first time.
In my case, it booted 3 times by removing the battery and putting it back and froze 3 times, there was no 4th.
If i tried to backup the phone the first or second time it booted, i could still have my data to be restored on the new repaired phone.
This should be marked as closed unless some other people with the same issue want to discuss it here.
Hi everyone, after trying everything I could to fix this phone I don't know what to do anymore so I'm here asking for other options.
So the story is, I was just using my phone as I usually would that day and it just randomly turned off and won't turn back on anymore.
(it randomly turned off before a couple of times but it would always turn back on)
- It won't go into recovery mode or any other of the 'modes' (I tried all the different combinations of pressing the keys).
- It's not a battery issue as I've tried my battery on my brother's phone (he has a Note 4 too) and it worked fine and I tried his battery on mine and it wouldn't work.
- I tried the 'drain' method (removing the battery and holding the power button for a minute or more).
- I tried using multiple cables to charge my phone nothing worked.
I didn't drop my phone, wet it, root it or anything and it was working fine the day it happened until it just powered off by itself. When I plug it in my laptop it would make
a sound indicating I've plugged something in but nothing happens. It was version 5.1.1 model SM-N910F.
TLDR; Is there a way to somehow recover the files in the internal phone memory?
This is happening to me as well, also started in February. I'm suspecting a hardware issue. Tried it ALL but rooting. In the past 30 minutes my phone has booted and rebooted itself till it died. If someone can confirm it is a hardware issue. Maybe it's time to unite and get it fixed for free. ~Tamarnouche
Recovering data from a brain dead phone may not be possible, as it probably need some internal component replacement which may erase the data(Mostly). Have u tried connecting it to pc? Better give it to service immediately. Good Luck.
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
HXOY said:
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
Click to expand...
Click to collapse
I have the same problem with my Note 3. Only if I keep the battery out for a long (over 24 hours) time I can see the boot logo. So if you find a solution to this kindly don't forget to tag me, will really appreciate it.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone
Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.
Currently I can turn on the phone, but after I turn the screen off, it won't come back on again
Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.
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
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.