Hey guys, sorry if this is a dumb question, but I cannot for the life of me get root working again and was wondering if anyone had any ideas to my problem.
While on 7.1.1, I was running magisk v8 with phh super user just fine, along with ElementalX (I know I know, not built for 7.1 but I wanted the unlocked bootloader SafetyNet patch so I installed and the previous vendor image). Magisk stopped passing SafetyNet, so I disabled phh in magisk, uninstalled magisk, and reflashed my boot image. Boots normal. Try flashing the latest supersu, and it bootloops. I used fastboot to restore everything except user data, and tried again but nothing. Just bootloop. Same if I try flashing ElementalX. What am I doing wrong that was different from before?
I'm thinking something was leftover in the userdata partition that messes with the modified boot image?
I can live without root, but I just wanted sultanxda's safetynet patch
Related
Hello,
I spent all day trying to find an answer to my problem, hope that you guys will help me
So, first of all, I'm on Mi Max 4/128, MIUI 8.2.3.0, unlocked BL.
What I need to do is root this device, add some apps as system apps and, since I use some apps which are quite keen on checking the SafetyNet, get rid of the root or hide it while keeping the changes I made while rooted.
I installed TWRP, flashed SuperSU, modified what I wanted, unrooted using the SuperSU GUI... And on the restart it started bootlooping, showing only the MI logo.... The only way out of this bootloop is to install the SuperSU again or clear the Data in TWRP, both of which defeat the purpose.
Tried with Magisk, hoping to simply hide the root... But it seems that MIUI won't fully pass the SafetyNet verification. Also after uninstalling it's all the same story with bootloops.
Next, after unrooting I tried flashing just the stock recovery.img and boot.img via fastboot, no luck there...
From what I've managed to find out, it's all caused by the forced dm-verity encryption. So one of the options for me would be to flash a modified kernel/boot.img that would not force the encryption, I guess? (I'm still a little hazy on the subject, correct me if I'm wrong ) Tried to do it, but I can't for the life of me find the modified boot.img or kernel for the latest Helium MIUI
Do you have any sugestions?
Okay, I figured it out! All it takes to avoid a bootloop after the unrooting is to flash this script:
https://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
Unless anyone's got an idea how to hide the root with Magisk on MIUI, thread can be closed
Hi,
Even I'm facing the same issue. I'm on stock ROM and unrooting from SU caused bootloop. Now, I restored the nandroid backup and the Redmi 3s prime is booting. However, I would like to unroot it. Can we simply disable Dm-verity from TWRP before unrooting from SU? Or disabling Dm-verity will cause any issue?
The boot.img patcher I mentioned in the second post does just that, it deletes the dm-verity. Try it out
I recently installed RR in Asus ze551ml, and just discovered that magisk manager is not working. I badly needed Magisk manager, to use NFC in the various payment apps, but it's not working. It is saying that Magisk has not been installed. I tried flashing Magisk v14.0 manually, through recovery mode, but it went into recovery loop. That's just unexpected. Same thing happened when I tried to install Magisk in CM 14.1, which I was previously using. Please help me to find a solution.
Stuck on recovery loop
How did you manage to pass through recovery loop. I have some data on my phone memory that i need so i can't fully flash it with stock. Please suggest me something
Solution
After flash magisk you need to flash VerifiedBootSigner.
I resolved by this way
PS Sorry for my english
When flashing Magisk in ZE551ML, you must sign up Magisk before flashing. Or, you can flash Magisk then flash the script here
rex_agamidae said:
How did you manage to pass through recovery loop. I have some data on my phone memory that i need so i can't fully flash it with stock. Please suggest me something
Click to expand...
Click to collapse
I simply flashed the RR rom over it without wiping anything. It worked.
Hi all, I had just updated my phone to DP2 (clean install, full wipe using system image ppp2)
I've got TWRP installed as well. After flashing magisk 16.4 zip, the phone goes into a bootloop. Any thoughts or suggestions on how to solve this?
agentxq49 said:
Hi all, I had just updated my phone to DP2 (clean install, full wipe using system image ppp2)
I've got TWRP installed as well. After flashing magisk 16.4 zip, the phone goes into a bootloop. Any thoughts or suggestions on how to solve this?
Click to expand...
Click to collapse
I had a similar issue. Certain magisk version seem to not play well with DP2. Try flashing Magisk beta 15.3.
I solved it by uninstalling my old magisk modules using uninmod (I believe). It couldn't boot because of some module I still had activated
Humpie said:
I solved it by uninstalling my old magisk modules using uninmod (I believe). It couldn't boot because of some module I still had activated
Click to expand...
Click to collapse
That wasn't it, i had no modules. I fixed it though.
Here's my mistake:
I did a clean wipe as i had to unlock_critical. I was on the January patch. This removed everything, and i went ahead and flashed the ppp2 image for pixel 2 xl without flag thinking it wasn't necessary (mistake?)
I then went ahead to setup the phone, and transfer my titanium backup files into the phone (mistake i believe).
My issue arises.
I went back and reflash the ppp2 image with the -w flag again.
Booted into the phone, skipped every step possible in setup until i got to the lock screen.
Boot into bootloader, and loaded twrp.img
flashed twrp.zip, magisk16.4.zip in the temp twrp image
rebooted and it loaded. :laugh:
Hopefully this is helpful to others trying to do the same thing!
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
theburrus1 said:
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
Click to expand...
Click to collapse
It's only possible to install twrp if you also install a GSI. Twrp will not work on stock. Magisk is also incompatible with twrp, the two can never be installed together no matter what. This is a magisk problem. Magisk uses the recovery partition, so it can use mirrors to make changes (systemless root). Twrp also needs to occupy the same place, because twrp is a custom recovery. Because of this conflict, they can't coexist. Magisk needs you to boot into "recovery" to boot the normal OS with root, and twrp needs you to boot into recovery to operate normally. So it's one or the other.
Unless the developer of Magisk decides to use system root, all newer devices will continue to have this problem. I highly doubt that will change anytime soon. The foundation of Magisk is built on being systemless, and so are all the modules for it.
If you want to use magisk, install the app, and patch your boot.img with it as "recovery", then flash it with fastboot. You must always "reboot recovery" to keep root afterwards.
Hello everyone,
so my Oneplus 5T broke a week ago and I bought another one for 80 bucks on Ebay. I tried to root the Phone with TWRP 3.5.2_9.0, OOS 10.0.1 and Magisk 22.1.
I disabled force encryption on my previous 5T without a problem, but now when I install Magisk with the ROM, no matter if I flash it over TWRP or flash the patched boot image over fastboot, I can access the internet, but can't download anything. It worked after I booted just the ROM and then flashed the boot image over fastboot.
Now I can't get the disable force encryption to work. When I try to flash the Zip over TWRP the phone doesn't boot at all. Also the device behaves laggy, even after multiple reboots.
Then I tried installing OOS 9.0.11, then Magisk and then my disable force encryption zip over TWRP 3.4.0 and it worked immediately.
Can somebody tell me how I can get the root with disabled force encryption on OOS 10.0.1? It worked previously with TWRP 3.5.0_9.0, but now it doesn't.
Thanks for any answer in general.
I don't know why but it works now