Can't unroot, stuck on MI Logo. - Xiaomi Mi Note 2 Questions & Answers

Hello. I rooted my phone using this guide en.miui .com /thread-415853-1-1.html
Everything works good, but then I tried to move an app to system with Link2SD but it said "write error no space left on device" and system space was 100%. I moved some system apps to user apps to make space (Mi Cloud, Mail, Calendar) but the problem persisted so I decided to leave it alone and not do anything. I then proceed to unroot by uninstalling with Magisk Manager, reboot and it got stuck on Mi Logo. I even left it for several hours but nothing happened.
I found out that if I enter fastboot and then TWRP, I can flash Magisk again, reboot, and it is not stuck on MI Logo anymore, the system boots perfectly and all my files and apps are there same as before. But how can I unroot without getting stuck on MI Logo? Is there a problem with Magisk or something? What else can I try?
I'm thinking my best choice is to flash the Mi ROM again using TWRP, is that correct? Any help would be appreciated, I'm still learning about this.
Currently I have MIUI Global 8.5.5.0 Stable (MADMIED) and I just downloaded the zip file of that rom.

Ok I worked it out. I'm going to post my solution in case someone else has the same problem.
Since I was able to boot system normally if I flashed Magisk again, I did that, made a backup of my whatsapp chats and saved a backup of my files in MI Account.
Then I reboot TWRP recovery, wipe all (factory reset) and flash my ROM MIUI Global 8.5.5.0 Stable (MADMIED). Phone started, root was gone, restored my backup.
Then I reboot again TWRP, flash Magisk and Phh SU and everything else in the guide linked above. Installed Link2SD, deleted some system apps (Youtube, Google Play Movies and Music and some others), and then I was able to move the app I wanted to system.
Rebooted phone to system. Then uninstalled Magisk from Magisk Manager, reboot phone, and everything worked ok!

Thanks, im planning on flashing twrp and magisk, so this could become handy ?

Try flashing these, worked like a charm for me.
https ://android file host. com /?fid=889964283620756562
https ://android file host. com /?fid=745425885120731943
just remove the spaces and you are ready to go!

Found a better Solution!
If you are stuck on the MI logo after the unroot that's because of the verity check of the ROM. So if u could boot into the custom recovery(TWRP) then just simply flash the lazy flasher zip file and then you are good to go, the ROM will normally boot with all of your files and apps.

Related

Xiaomi Mi A1 Bricked, inifnite loop, I really don't know what's happening :( HELP

Hi, I have owned my Xiaomi Mi A1 like 5 days ago, and after a day I had it in my hands I rooted the device with Magisk 14.1 in TWRP, well, after I day I rooted the phone the update of oreo just realesed and my cellphone was avalible to install it, so I decided to unroot my phone, and there is where the ALL the problem started... Seems like when I flashed Magisk it didin't make a backup of the original boot.img so when I flashed the magisk uninstaller it didn't boot into the phone, it sent me to recovery again, so I tried installing the Magisk installer again and it let me boot.
After watching that I tried to flash the latest ROM in MiFlash but it just didn't do nothing, it flashed in 1 second and nothing happened to the phone.
Yesterday after all of that happened I tried to update the phone manually while rooted with TWRP, I found a backup of oreo of TWRP, so I restored that backup in TWRP and it booted me to oreo finally, after booting it to oreo I decided to go back to TWRP to restore my data backup of Nougat to restore all my apps and that stuff but when I booted into recovery it asked for decrypt my storage (as always), so I tried to decrypt it with the pattern I always used before and it just didn't let me, it just failed I don't know why, I booted into the system again trying to remove that stuff but it just didn't let me, the button to remove it was unavalible, it just let me remove my pattern to unlock the phone, so I removed it to see if it would work and it just make the things worse, I booted into recovery again and it didn't let me again, so I tried to boot into system AGAIN and it just didn't let me, just infinite loop, and recovery just removed, so I booted into recovery with fastboot mode and it didn't ask me for any decryption, it just let me in, but without mounting my internal storage, it just didn't, I tried to wipe the data option and after that it worked again, internal storage appeared again, after it I flashed the recovery into both slots.
Well, the last thing I did is restore the backup of oreo again that I found in XDA, but it just give me infinite loop, it's been like half of hour or more "booting", I'm so frustated and worried about this, tell me that there is a solution for this, the phone is literaly new, just five days with it... That version of magisk literally ruined my phone, lol
Ok mate, I suggest you go back to the last factory fastboot Xiaomi source. You flash this with the MiFlash tool.
The first file you need is the latest fastboot rom. This is in the tgz/tar format.
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
Extract this tgz and the subsequent tar file so that you get a directory (containing .bat files and an image folder).
Download MiFlash2017-7-20-0.zip - it must be this version.
Get your phone into fastboot mode with at least 25% battery charge.
Follow the instructions to use MiFlash here https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
Good luck!

Stuck in recovery

So i probably did something stupid.
I wanted to root my oneplus 5, so i updated it to last oxygenos 5.0.1 and copied all necessary stuff to pc.
After that unlocked the bootloader, got the phone to fastboot and flashed twrp 3.2.1-0.
Somewhy i couldn't access internal storage from twrp, it said its 0 mb and sdcard folder was empty, however i put magisk 15.3 there before, so i googled for a while and found that it probably couldn't mount storage. so this is where i probably did stupid thing by formating and fully wiping the phone. after that i could mount the storage, but the files were gone so i just put them there again. After that installed magisk and booted to system only to find myself in recovery again. So i though that i completely wiped the phone with the rom, so i downloaded the latest oxygenos and put it on the phone to install from twrp but it just doesnt install. returns error 7, which is, as google says, has somehting to do with asserts, it suggested to remove them form updater-script file, but opening it doesnt show any asserts in it. So here i am with phone with twrp and no rom at all. What do i do? Please help
tl;dr: I have OnePlus 5 with twrp 3.2.1-0 after complete wipe, and it cant install oxygenos because of error 7
Edit: only after posting noticed that there's a help thread, sorry for that. problem is not fixed though
Try a different TWRP.
update
thanks for suggesting different recovery. first tried older versions of twrp with no success, then tried twrp blu spark and it got a different error, something to do with unlocked bootloader. so i edited updater-script file and it installed normally. so i now have a clean oneplus 5 with oxygenos 5.0.1
will try to install magisk again, hopefully wont wipe everything again
update
yeah, everything worked. installed magisk and got root. but it always says 'install' inside magisk manager, is this normal?
saw that it should say 're-instal' in yt videos
It's normal.
Magisk updates regularly, those YouTube videos don't get updated.
I bumped into the same problem as mentioned by hyro28..
Please explain how to "update updater-script file " -- where is the file found, how to update it? I am new to this, would appreciate detailed instructions -- links, written instructions, videos, etc Thanks!

Can't Boot after OTA Open Beta 5 -> 6

Hi, I just dirty flashed my phone through OTA from OB5 to OB6. I currently can't boot into my phone, but recovery and everything works.
I'm using twrp 3.2.1.0 codeworx. I can boot into my lockscreen but the moment it loads it says "Shutting down". If I install Magisk 16.0 it just tries to boot, then fails and jumps to recovery.
At least my data isn't encrypted anymore, but what can I do about this? When I try to sideload the OB5 ROM it says can't read zip.
Also it's interesting how my recovery gets reset every time that happens.
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
SventraPopizz said:
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
Click to expand...
Click to collapse
Thanks for the suggestion. I also feel a feeling that it's substratum because I made the mistake of updating with layers still installed. I tried flashing the substratum rescue zip, both legacy and non-legacy, and also deleting the file as you suggested but I'm still getting that immediate "shutting down" error.
chazarss said:
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
Click to expand...
Click to collapse
For my personal experience, I took the OTA and had no problems rebooting. I'm also fully stock with no root or custom recovery; I don't know if that affected my flash and reboot. I bought my OP5 used from Swappa. When I got it, I clean flashed the OB5 and then today I took the OTA for OB6.
I was on ob05, twrp 8.71. Received ota, full zip, on the phone. Dirty flash workt fine for me. Phone booted ok. Of course, recovery was gone. Reflash recovery. Reboot to recovery. Flash Magisk 16. All ok.
Bootloop was caused by https://forum.xda-developers.com/oneplus-5/themes/op5-oos-oreo-official-fix-blue-3rd-t3727238/ for me. After disabling the module with https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 it's booting properly

My device is stuck at fastboot after rooting it and updating Magisk

I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.
Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.

Accidentally wiped Internal Storage in TWRP... Any possible fix to get partitions or anything back?

I attempted to install LineageOS 17.1 on my Mi A1, but while wiping storage, I accidentally also clicked Internal Storage and wiped it too. Now, I tried to restore my backup but when I go to restart to turn on my Mi A1, it gets stuck in a boot loop. I also tried using XiaoMiFlash and the original ROM to get all the firmware settings to stock. Now, I tried also installing custom ROM again, LineageOS 17.1 but it also gets stuck in a boot loop. Is there anything else I can do?? I'm very frustrated... I hope my device isn't completely bricked. Any help is appreciated.
I need help pls asap said:
I attempted to install LineageOS 17.1 on my Mi A1, but while wiping storage, I accidentally also clicked Internal Storage and wiped it too. Now, I tried to restore my backup but when I go to restart to turn on my Mi A1, it gets stuck in a boot loop. I also tried using XiaoMiFlash and the original ROM to get all the firmware settings to stock. Now, I tried also installing custom ROM again, LineageOS 17.1 but it also gets stuck in a boot loop. Is there anything else I can do?? I'm very frustrated... I hope my device isn't completely bricked. Any help is appreciated.
Click to expand...
Click to collapse
Welcome to XDA!
Its not recommended to open more than 1 thread on same topic, please have a read of the forum rules and most importantly, enjoy your stay!
It should be ok with mi flash tool
lafactorial said:
It should be ok with mi flash tool
Click to expand...
Click to collapse
I have already tried that, the only issue now is that the Custom ROM after installing (LineageOS 17.1) will not boot properly. Maybe this is because I skipped TWRP Recovery? Well, I don't know why but TWRP Recovery zip will not copy into phone storage. it is originally .img file, but the guide I'm following has .zip file so I converted into zip via Windows Explorer (file manager). But, it does not copy and when I use img to zip website converter iand it does copy, but it says "invalid zip file format" once flashing.
One thing I should note, the backup does work now. I had a typo when making the folder so it wouldn't work. Backup does work now, but something really stupid is happening. When I go to turn on screen lock, it will keep looping me into "which type do you want to choose, fingerprint + pin, password, pattern" after completing the process. If I don't choose fingerprint, it finishes but the screen lock isn't effective. Any help on this?
I need help pls asap said:
I have already tried that, the only issue now is that the Custom ROM after installing (LineageOS 17.1) will not boot properly. Maybe this is because I skipped TWRP Recovery? Well, I don't know why but TWRP Recovery zip will not copy into phone storage. it is originally .img file, but the guide I'm following has .zip file so I converted into zip via Windows Explorer (file manager). But, it does not copy and when I use img to zip website converter iand it does copy, but it says "invalid zip file format" once flashing.
Click to expand...
Click to collapse
You cannot just convert that image file into a zip file like that.
Where did you get that twrp file from?
If you want to install twrp, you need to flash the twrp.img file via fastboot, then sideload the twrp.zip via trwp.
(maybe just flashing the img file works too, but I often read that you have to do both).

Categories

Resources