I meant magisk settings. Not System settings.
Yes, tks god thats what I meanI think what he means is that the popup to allow superuser access for an app doesn't appear and access is just declined, even if the magisk settings are correct.
@ghostwalkergamma which Magisk version do you have? Did you keep the preinstalled 17.1 Magisk or did you update it?
What I would try is to boot to TWRP, flash the Magisk uninstaller, and then reflash Magisk again (use 17.1, that works just fine for me)
Yes, tks god thats what I mean
Ok, i would try reflashing this, magisk just ask me to install update for the first time and I dont know that newest version (17.3) is not compatible with our newest patch
Btw, do you have the stock nov patch? I need it just in case something went wrong![]()
Go to Magisk Manager -> Settings and set "Update Channel" to stable, then it shouldn't suggest you to update to 17.3Yes, tks god thats what I mean
Ok, i would try reflashing this, magisk just ask me to install update for the first time and I dont know that newest version (17.3) is not compatible with our newest patch
Btw, do you have the stock nov patch? I need it just in case something went wrong![]()
I haven't used SuperSu for a long time, just want to stick with MagiskPatched and stock you may find here, also from other months.
https://drive.google.com/open?id=1UkFSbOESPdoKlFW6gV1iYqEplhzVwZs7
Regarding Magisk 17.3, I have this version and all is fine. Show first Magisk settings. If all is ok there, try to use Magisk 17.1. Also to be sure, you do not have any other SuperUser way, like SuperSu?
Go to Magisk Manager -> Settings and set "Update Channel" to stable, then it shouldn't suggest you to update to 17.3
Stock Images for November are here: https://forum.xda-developers.com/showpost.php?p=78169095&postcount=44
If you want to install OTA updates, you need to reflash the stock image of your security patch, reboot to Android, do the OTA update, then reboot again and reflash the TWRP image.
Patched and stock you may find here, also from other months.
https://drive.google.com/open?id=1UkFSbOESPdoKlFW6gV1iYqEplhzVwZs7
Regarding Magisk 17.3, I have this version and all is fine. Show first Magisk settings. If all is ok there, try to use Magisk 17.1. Also to be sure, you do not have any other SuperUser way, like SuperSu?
Hi, do you also have the Pre Rooted December version?
Because my phone has December 1 security patch and Prerooted Novemder doesnt work with this.
I can also downgrade my phone but tbh i have no clue how to do it :/
Thanks a lot
hi
I'm running android 8.1.0 with december patch. Just got twrp 3.2.3-1 img, the command "fastboot boot twrp.img" brings up a screen with powered by android written on it and does nothing.
I want to root my phone and don't know what to do.
please help....
While it is possible to patch an image externally I wouldn't recommend it, since that does not give you the convenient ability to get a backup of the stock image at the same timeGiven the fact that "fastboot boot" doesn't work, what we can do to properly patch the boot image with TWRP?
I think our most obvious option is to flash the unactive boot partition and run twrp.img from there and make it patching the active boot partition, right? Is there any better solution like the way magisk does? (as it runs a normal process on android and can patch the image file, not the partition itself)
While it is possible to patch an image externally I wouldn't recommend it, since that does not give you the convenient ability to get a backup of the stock image at the same time
(required for OTA updates). The easiest solution for the enduser is using prepatched boot images. If you want to make images yourself you should use the inactive slot method.
By using a boot image unpacker, replacing the ramdisk image with the one from the installer .zip and repackaging.Stock image is the captured OTA image alreadyHow can I patch it externally?
By using a boot image unpacker, replacing the ramdisk image with the one from the installer .zip and repackaging.
However I have never done that except for some random experiments with it on linux so I can't help you with exact steps unfortunately.
However, if you are talking about the official Pie update (since thats a full OTA), I already have a prepatched image for it
(https://bit.ly/nokia-nb1 in the folder "Boot Images/2018-12"), if that makes it easier for you.
adb reboot bootloader
fastboot getvar current-slot
# x = the slot name the previous command returns (either a or b)
fastboot flash boot_x <path to the downloaded .img>