Hey everyone
I've been using the XT1053 Retail US Stock Lollipop Flashable ZIP without issue for quite a while, but decided to update to the modded version 2. So I flashed it, xposed, and supersu again. Booted up, everything was okay. But then it said I needed to update my supersu binary and that I didn't have root, so I went to reboot into recovery and flash supersu once more.
However, now I can't access TWRP and it merely says "no command"
Should I just try installing TWRP again or is there a way to see if it's still installed? It's weird that this happened after flashing a rom
edit: reflashed twrp recovery img, back to normal. Can't explain what caused this though
TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
jhedfors said:
TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
Click to expand...
Click to collapse
I just went back to stock ProjectFI today using fastboot. After initial setup, I went back to fastboot to boot the 3.2.3-1-payton.img, then adb pushed both the twrp-installer-payton-3.2.3-1 and Magisk, installed them both at the same time and rebooted without incident.
EDIT: I used PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Thanks @johnjingle.
Not sure if it was because I had Magisk already installed first that was my issue, but flashing TWRP on a fresh boot image THEN flashing Magisk did the trick.
Yesterday i flashed magisk (using the new method of course) and when i tried to boot it would stop on the miui boot screen. I can go into fastboot and recovery but i dont have twrp installed.
If anybody could help i would be grateful.
Update: The phone now says system is destroyed when i try to boot into recovery, should i just fresh install miui?
Also there is a roll back function that triggers when you install unverified img files so i think the cause is that.
Fresh install worked.
now my device works
I was unlocked and rooted at Indian 12.5.2 ROM for the longest time. Got a notification for 12.5.5 and installed it. That took away root, but that was expected.
Now I've installed official TWRP, but as soon as I install Magisk (either via zip from recovery or patched twrp recovery image via the Magisk app), when I try rebooting to system, phone instead boots back to TWRP with a 'Android Rescue Party Trigger' error.
Happened every single time I've tried above - phone tries booting and then boots to recovery, and only way to boot system again is to install unpatched TWRP recovery, but then there's no root.
What should I do?
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.