-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIUI 12.5.4.0 update causes bootloop #154
Comments
Most of those are safe to remove. What you can do is use an online diff tool to compare the two files. Also you should be able to backup and restore contacts and so on from Google/SIM card. |
yeah my contacts etc. weren't saved to google or sim card. Idk if I am the only one who had this problem. With the new update, every time I debloated my phone, it got stuck on bootloop. So, I reduced the packages this time and didn't have any issues. And yeah they were safe to remove before, I had like 60 packages uninstalled already. |
Same here, after got February security update (MIUI v12.5.3.0). Glad it's just my secondary phone. |
@gdnzz @chapters1000 I checked the diff. Are you saying that removing any of the following packages causes bootloop on MIUI 12.5.4.0+ ?
Can you both confirm this list ? The first 4 seem strange. |
I don't know if this helps: https://piunikaweb.com/2021/04/19/miui-12-miui-12-5-bloatware-can-now-be-removed-directly-from-browser |
sorry... i can't. |
I mean... you were right! MIUI is a horror. |
Xiaomi Poco X3 Pro NFC, Android 11: Seems like updating MIUI does break some stuff. Updating from MIUI 12.5.5 to some MIUI 13.x did cause a soft brick and had to wipe data and return to 12.5.5. All of these (except
Wouldn’t recommend removing |
I can't test again, this is my main phone. But yeah, I shared the lists |
Oh someone already addressed the issue, closing it #169 |
- Update incorrect description - Removing this package causes a bootloop on MIUI 13+
Thanks for your help! |
- Update incorrect description - Removing this package causes a bootloop on MIUI 12.5.4+
Yes, can confirm. Got a boot loop when removing |
New Release This is a really big release with a huge review of the recommendations. There should be a lot less issues like this (even though this is really weird that |
@0x192 Thank you so much for developing this app, it is really useful and very well built! Just started using it a few days ago and am now considering staying with a debloated Mi 10 Lite for some time before unlocking and switching to a Custom ROM like lineageOS 19. Usually I start unlocking a new Xiaomi phone as soon as I get it, but your tool makes it possible to at least consider staying with MIUI, since it is one of the best official ROMS, except for the ridiculous amount of bloat, telemetry and spyware which your app helps to remove without crashing the phone. Wish you and the team the best of luck! @KarlRamstedt @rar0ch |
I dunno if I'd call it a team, I just try to help out sometimes 😅 |
Poco x3 nfc
I will tell it from the beginning. So, my already debloated phone (around 60 packages) got a system update (MIUI 12.5.4.0, security update apparently) and I installed the update. Then the phone restarted itself to finish the update, but it entered bootloop. I tried fixes and etc. but didn't work, so I had to factory reset. After setting the phone up again, I debloated (around 30 packages) and restarted the phone again to see if the bootloop was due to debloated packages, and boom, another bootloop. After another factory reset, this time I only uninstalled the apps that showed in app drawer and play store and restarted the phone(I didnt uninstall built-in system packages etc.) . This time there wasnt bootloop. So, if your phone is debloated, dont update it. And if you are going to update, make backup of your files, contacts etc.
HERE IS THE PACKAGE LIST THAT CAUSED THE BOOTLOOP AND THE ONE THAT DOESNT CAUSE BOOTLOOP IF YOU HAVE THE SAME ISSUE AFTER UPDATING
safe to uninstall.txt
caused bootloop.txt
DAMN xiaomi, you caused me to lose my contacts and 2fa
The text was updated successfully, but these errors were encountered: