Hello,
I have rooted my device A2 using Magisk, then My device installed Dec. update and since the update successfully root access is gone away!
check out this screenshot.
View attachment 4904757
That's normal. You have to root again
Related
Hi,
Till this morning i had rooted Android 6.0.1 (MOB30O) in my Nexus 6. I hadn't updated before because i was lazy, i didn't want to un-root and re-root. But since I've been having battery issues, I decided to give 7.1.1 a try.
I always rooted my device using Wugfresh Nexus Root toolkit... and it always worked great. So, I basically un-rooted my device, using said tookit, and updated it thru OTA. Problem is... I ended up in Android 7.1.1 NGI55D. When I was about to root using NRT, i noticed that last supported version was N6F26U. Also noticed that NRT last version is from September 2016, so i don't know if it is deprecated or what...
So basically, i have a question here: Is it possible to root 7.1.1 NGI55D? If so, can anyone point me to the right direction? I have always used NRT, but i can follow a tutorial and do it manually. Just don't wanna mess things up.
Thanks in advance.
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
ktmom said:
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
Click to expand...
Click to collapse
i need unlock bootloader before to root?
Yep.
Hi, I have been using Magisk for last one month. Everything worked fine. All my root apps worked like a charm. Today I tried to install an OTA update. For which I tried to restore stock boot image with Magisk. After Magisk showed, 'restore successful' message, I tried to install the OTA (April), but I couldn't, it kept on showing installation error.
I then tried to reboot my device but it got stuck in bootloop.
Using MiFlash Tool, I flashed back the stock ROM which restored everything including the bootloader but retained my data (user apps and settings, Magisk and other root apps were also retained.) I then updated my stock ROM with the OTA.
Then with ADB, I unlocked the bootloader and flashed the patched boot image file of April.
After booting up first time after the patch, Initially the Magisk and root checker, both showed me root access, but after a reboot, the root access was gone. The root checker now says - Root access is not properly installed on this device.
Magisk homescreen says, Magisk is Latest Version v16.0 but Magisk is not installed. On clicking the install button, it only shows two options - Download Zip only and Patch boot image file.
What should I do to get back my root access?
You have to reflash Magisk manually after every OTA update.
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom
title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?
Hello,
I have rooted my GPlay and installed TWRP.
Unfortunately my banking app detects the root and refuses to work.
I heard about Magisk which can be used to bypass this.
Can anyone tell me where to get this for my GPlay and how to install it?
I have TWRP 2.8.7.0 hw4c installed and SuperSU Free v2.68 (SuperSU-v2.68-SYSTEMMODE.zip)
Phone:
Model: CHC-U01
EMUI 4.0 Android 6
I've downloaded the Magisk App and try to install. But get this error:
Installation failed
Boot Image patched by unsupported programs
Please restore back to stock boot image
That error message tells you exactly what you need to do... You need to first remove SuperSU. After that you might be able to install Magisk, but you might need to use the patch boot image method, since that TWRP could be a bit too old.
But, even if you get Magisk installed it's not certain that you'll be able to circumvent your banking app's root detection. There are ways of detecting root that Magisk cannot hide. But, you've certainly got a better chance with Magisk than with SuperSu... You'll find some root hiding tips here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Ok. I forget about Magisk.
Thanks to you Didgeridoohan and jwoegerbauer.
Trying to update magisk via direct install using latest magisk manager v23 on rooted S10 on pie.
View attachment 5351001
Install goes well according to this ^
But when I hit reboot, and then hold down power+bixby+vol-up to get back into root mode, it always gives this error when starting magisk app
View attachment 5351005
So the update fails every time.
Since Magisk Manager v23 wont even show the current magisk version- upon downgrading to MM 8.0.7, we see that it never upgraded magisk past 19.4 (19302)
Also the "additional setup" never completes when we try that from 8.0.7, fyi, and the Update button is greyed out too.
View attachment 5351007
What is the next step to getting magisk 20.4+ working with a recent version of the app?
Thanks!