hello, I've owned a Xiaomi Mi 9T for over a year now and I've had one issue with it, which was a boot loop, and I believe I figured out why it occurred. My phone was still working well after a year, but I was trying out some themes from the theme store and I applied an IOS theme to my startup and system, so I decided to restart to refresh my phone, and when I did, it didn't come back on and was stuck on the MIUI startup logo, so I started researching and discovered it was a boot loop, which made me panic. When I tried to do a recovery, there was no option to backup my data or anything because of Xiaomi recovery, which sucks, wish I had TWRP but anyways, I tried several methods to get my phone to come on back like leaving it to die and then charging to hope it comes on back but that also didn't work, I had backed up most of my stuff up a point in time so I was left with the last option of Reset, which i did the other day. My phone had no software problems and was running smoothly before I restarted it, so it was the IOS theme that caused this, and I want to warn xiaomi users out there to make sure to backup your data regularly to a hard drive and the xiaomi cloud, and to do backups before you restart and update your software, because your phone going into bootloop is very bad and will have you panicking.
Thank you for reading.
Related
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.
Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!
maybe just can let 9.0 install , looks like is the only way that u have for a dayle phone
Mig979 said:
Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!
Click to expand...
Click to collapse
You can install stock Pie via Mi Flash tool.
Sent from my Mi A1 using XDA Labs
So I've finally got to upgrade from A10 to A11. I was unable to follow the guides for doing local upgrades, because of my previously mentioned "No changelog" and "System Update Installation Failed" message the moment you selected the upgrade package. I tried multiple downloads and verified hashes, this wasn't a corrupted download. So I ended up having to Wipe data to get to a stock A10 and then upgrade using local upgrade. That was Sunday. Since then, I've rooted, restored my apps, lived happily on A11....for about 1-2days before I'd wake up a bootloop. The phone would just be sitting on the spinning Oneplus logo without me knowing why we got here. Even stranger, I had NoLimits installed, so I should be seeing that instead of Oneplus.
Attempting to fastboot boot any of my boot images still keeps me in a boot loop, not much to do other than to wipe and try again....So wipe, on A11 stock, root, restore apps and go on my way....Worked great yesterday. again all apps were restored, things were working, no issues. And then I woke up this morning to find issues with Facebook app (images not loading). Okay, whatever, something may be corrupt, just wait for an update from them. Multiple apps in Playstore need an update, great...do those. But then Oneplus Gallery refuses to update...hmmm. Catlog/Logcat refuse to open with insta-crashes. Facebook nolonger has the corrupt image issue, it just insta-crashes.......uh oh......maybe a reboot?.....rebooted and then stuck on NoLimits bootscreen for about 2 minutes....after 2 minutes it reboots and I'm back to being stuck on Oneplus boot image.
So I'm out of ideas now. about to wipe and go back to A10, because I can't for the life of me find a connection to all of this and its getting tedious to restore apps (especially 2fa apps).
Any help would be appreciated.
Hi!
I have had annoying bootloops when making a call.
It connects to a call and then boom, goes dark and reboots by its self. Very annoying.
I have 2 SIM cards on use, dont know If that matters.
Iam suspecting the network connection change during call -setting has something to do with it...
Hope there is an update coming soon to fix this.
Yea I have 2 sims as well (TMo and GoogleFi) so that's an interesting point. We finally now have dual-sim (US/Glo).
I'm currently testing out how long i can go with my current setup: Just A11 + Root + NoLimits....wait about 2-3days, then try LuckyPatcher (best way I know to remove ads), 2-3days, and then continue testing other ideas).
Hello guys
I've recently upgradded my OnePLus 8Pro wtih OOS13 (IN2023_11_F.64: (IN2023_11.F.64_2640_202304111218), and I already regret it
Afer booting, it takes 2-3 minutes of up time and my hone reboots - I don't know why. I can't even drop stock firmware image to the phone, because it's resetting during copying
Can I re-flash the ROM again with fastboot or OrangeFox recovery safely? What's your advice?
I'm thinking of going back to OOS11 because I'm missing many faetures, like call recording, GPay (I'm rooted), but atm all I wish is stable phone
Any advice would be appriciated
Lucas
You could try MSM - but that will wipe all your data.
Not to be the bearer of bad news here, but I had the same thing happen on my 1st 8P last year, on OOS 11 without any recent changes or updates. First it started rebooting every few minutes, then it got stuck on the little green Android dude and wouldn't boot at all any more.
I used MSM and got it up and running again ... for about 10 minutes, then it started over with the rebooting.
I ended up selling it for parts/as is/broken because nothing I did got it back to normal, so it probably had some hardware issue.
I absolutely hope that's not the case for you, so maybe try MSM and see it that works