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
Related
My phone is an Motorola 4G XT1072 Thea. Custom ROM LineageOS 14.1.
I wanted to change SuperSU with Magisk root. I therefore removed SuperSU and rebooted to recovery (TWRP) for flashing Magisk. I got an error code 1 flashing Magisk. I tried to reboot to recovery but I couldn't. It just reboots. It's like my recovery has gone. I can't even do a factory reset. I tried to reinstall TWRP through ADB but it's waiting for device forever. ADB recognizes my device. Anybody got some advice?
I managed to get my recovery back by deleting all moto drivers on windows and reinstalling them, then I could reinstall TWRP through ADB. But I still get error 1 when flashing Magisk. Is that because I need to flash a stock boot.img? If so do I then flash boot.img and thereafter Magisk.zip?
It all depends on what that "error 1" is actually about.
If you didn't restore the stock boot image after removing SuperSU, then that's a likely culprit...
If you want to know for sure you're going to have to share a recovery log with details about the error.
DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.
naveed5700 said:
DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.
Click to expand...
Click to collapse
I need that file too. Can anyone help me to have this?
Hi!
I have pushed my MI 9 into bootloop and need help to get it back working.
The bootloader is unlocked, Magisk and TWRP are installed. I tried to install the latest Universal SafetyNet Fix, but instead of installing it inside Magisk I have "installed" the ZIP with TWRP and wiped the delvik cache. Now the phone is in bootloop.
In the Universal SafetyNet Fix- threat I got the hint to reinstall the stock boot.img, but I am unsure how to do this and which file to use.
Can I just use one of the boot.img linked in this threat, e.g., the one in 10.2.24.0?
[Root images] Boot 10.2.24.0 & 10.2.9.0 & 10.2.26.0
Version 10.2.26.0 Version 10.2.24.0 ------------ > Stock/Root Version 10.2.9.0
forum.xda-developers.com
and install it with fastboot, i.e., "Fastboot flash boot.img" ?
Or is there another solution to my problem, e.g., uninstall the safetynet-fix-v1.1.0.zip ?
Well, I gave it a try, but it doesn't work. Now the phone doesn't even show the MIUI logo anymore. Fortunately, I had made a backup with TWRP before I tried this, and I could reflash the old boot.img with
fastboot flash boot boot.emmc.win
Now at least the MIUI logo appears again, but my original problem is still there, the phone still doesn't boot completely, but resets and goes into twrp.
Problem solved by deleting the safetynet-fix folder. Thanks to Durete for this tip!
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
Durete said:
The easy way....
How to Uninstall Magisk Modules Using TWRP Recovery | DroidViews
Click to expand...
Click to collapse
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?
My phone name and model is redmi 9c (angelica) variant..i will get straight to the point..i installed an updated version of my from 12.0.22 to 12.5.4.0 through orange fox recovery...i flashed the recovery by dirty flashing where i just cleared cache and delvik ART or something...then just flashed the whole update zip file through recovery.. everything was working and no problem then i just thought that i would open the custom recovery and it will not open and will kept itself stuck in recovery image or start image of the recovery not open or closing.. nothing worked until i thought i should just factory reset my phone but it won't factory reset itself and will get stuck on that same custom recovery logo and i had manually force it open like i did by press and holding the power button until it vibrated..it opened like normal shut down or restart...so i my phone couldn't be formatted so what i did was to download the fastboot version of my phone that i had installed and took the recovery.img file and flashed it through another phone through bugjaeger app..since i don't have a pc that all i could do and it worked the stock recovery came back and i can wipe my data if i want....but if i installed the custom recovery.img once again it won't work and will get stuck like that time so i want a solution where i can get custom recovery back again...and i gave my full story because someone might be in a similar position as me and by doing something that i did might just help them and also i want a solution to get my custom recovery back plz someone help me.....
you should know that there is a version of Pbrp Vendor R (Miui 12.5), it is the one that works but has encryption, it is unfortunate but if you have MicroSD you will have no problem installing magisk
wulan17 Custom Recovery
My Android Custom Recovery Builds
www.pling.com