Related
Hi Everyone, I am Pushkar Dua just wanted to share a rooting guide for Nexus 5 Android 5.0.1
As many people Reported that Root has stopped working after the 5.0.1 Update or previous Binaries lead device to Boot Loop,
Please Download Latest Binaries That i am providing here: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
And flash it with TWRP recovery..
Please Use TWRP Version 2.8.1.0 as people reported some problems in latest 2.8.2.0 version.
Downlaload TWRP 2.8.1.0
Please note: if you're having a problem with twrp 2.8.1.0 asking for password..
Please use twrp 2.0.4.5
just reboot to system and you will have root access..
Watch the video for more info and Please Hit thanks or subscribe me on youtube to support me! every bit will be strongly appreciated!
Please Leave your questions BY QUOTING ME
Thanks
Thanks To @Chainfire for making this!
Original Thread for SuperSU : http://forum.xda-developers.com/showthread.php?t=1538053 Root Nexus 5 Lollipop 5.0.1
Hey!
Thanks a lot. Really helped solve my problem!
No problem
This doesn't belong in Development.
Actually i am not sure where should this be.. I'd request modders to please move it to the correct board!
Thanks man!
Delete
Since you've probably lost your custom recovery upgrading to 5.0.1, you can grab the TWRP images for Nexus 5 here: http://techerrata.com/browse/twrp2/hammerhead
I believe you need to use 2.8.1.0 since 2.8.2.0 either doesn't work or is causing problems for many users.
CF-Auto-root is still OK. I just tried
wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
Isn't CF-Auto root adding files from the 5.0 release over the 5.0.1 ? Isn't it safer to wait for a 5.0.1 autoroot?
wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
How did you update from a rooted (with CF-Auto Root) 5.0 to 5.0.1 you just received the OTA and installed it without any problems ?
I like to know because i am on 5.0 stock just rooted with CF_Auto root.
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
I flashed a Custom Rom Using TWRP which doesn't have any root permission...
MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
Yes... Just Flashing with TWRP Is Enough!
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..
pushkardua said:
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..
Click to expand...
Click to collapse
This. I flash with it here since 4.4.4 and it did everything just fine. Not only it is an app to automatically root, but it gives very good hints, and provides lots of others features like installing Apks, getting a adb prompt, and so much more. Greatest third party Android app I have tried. Highly recommended, didn't even had to wait they update it for 5.0.1, as soon I got the 5.0.1 OTA notification, Nexus Root Toolkit was already ready for it.
Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
This is lollipop security, custom recover wouldn't stick, after each reboot it will replaced with stock one, of course there is a way to make it sticky just search the forum.
Sent from my Nexus 5 using Tapatalk
MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.
Molitro said:
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.
Click to expand...
Click to collapse
I had similar discussion with Chainfire:
MrKaon said:
So guys for rooting lollipop on Nexus 5 stock all I need is flashing latest zip with TWRP?
No more need to flash modified kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Chainfire said:
Initial root requires using CFAR. You can update using TWRP afterwards.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Is there anyway to root and still get OTA ?
anttaz said:
Is there anyway to root and still get OTA ?
Click to expand...
Click to collapse
You will get OTA, after Root also, but after updating your root will gone, recovery will replaced by Stock recovery, and if You are decrypted after update
it will get encrypted.
uttam.ace said:
You will get OTA, after Root also, but after updating your root will gone, recovery will replaced by Stock recovery, and if You are decrypted after update
it will get encrypted.
Click to expand...
Click to collapse
Does stock recovery not allow zip flashing?
anttaz said:
Does stock recovery not allow zip flashing?
Click to expand...
Click to collapse
It allows local upgrade, but it has not much flexibility like TWRP.
I've just updated from 4.0.2 to 4.0.3 and here's how my "OTA" was working:
1) Got notification that the update is available
2) Went to XDA to download OOS 4.0.3. full ROM zip, TWRP 3.1.4.1 image and Magisk 11.1 root
3) rebooted to TWRP, flashed new ROM, Magisk root and TWRP image.
As far as I know, that's the only sure way to update your phone while keeping root and TWRP.
Does it pass safety net?
anttaz said:
Does it pass safety net?
Click to expand...
Click to collapse
Yes, it does! With MagiskHide it works like a charm.
Will ota work for cleaning system for say arise sound mod or will have to use full? And does full wipe device clean?
anttaz said:
Will ota work for cleaning system for say arise sound mod or will have to use full? And does full wipe device clean?
Click to expand...
Click to collapse
I'm sorry, i didn't fully understand what you were trying to say here
But i'll take a wild guess and tell you that in TWRP you always need to flash full ROM, not OTA version. Otherwise your phone won't boot.
hrsa said:
I'm sorry, i didn't fully understand what you were trying to say here
But i'll take a wild guess and tell you that in TWRP you always need to flash full ROM, not OTA version. Otherwise your phone won't boot.
Click to expand...
Click to collapse
Along those lines in a way does full ROM zip wipe phone each flash?
anttaz said:
Along those lines in a way does full ROM zip wipe phone each flash?
Click to expand...
Click to collapse
Nope, it never wipes anything other than system, so all your data and apps are safe.
anttaz said:
Along those lines in a way does full ROM zip wipe phone each flash?
Click to expand...
Click to collapse
Does flashing full ROM zip wipe phone with each flash?
Thanks all
Which version twrp to use seen official and a few others in forum for our device??
Hello, sorry for my bad english (German). I installed the update too and now my root, recovery, kernel.... are away. When I try to flash the recovery or other stuff with cmd, is there an error message: FAILED (remote: Partition flashing is not allowed)
Got anyone an idea how i can flash my recovery again?
https://www.androidfilehost.com/?fid=889964283620761169
Grabbed straight from SamMobile. Flash using Odin.
Not for j700t1 though, correct?
AngryManMLS said:
Grabbed straight from SamMobile. Flash using Odin.
Click to expand...
Click to collapse
But how do you root after flashing this Nougat in J700T?
deloj said:
But how do you root after flashing this Nougat in J700T?
Click to expand...
Click to collapse
There's all sorts of knowledge in the thread
https://forum.xda-developers.com/galaxy-j7/j700t-development
Anything you see for the J700T is compatible with the J700T1. The phones are exactly the same minus 4 apps inside the system.
ctindell1981 said:
Not for j700t1 though, correct?
Click to expand...
Click to collapse
Is this Nougat stock rom for the samsung J700T? And how do I root it?
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
There is no such rom for this model in nougat yet
nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.
nimbus22 said:
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.
Click to expand...
Click to collapse
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?
Once it's been on the screen saying t mobile for at least 10 mins, pull battery, boot to stock recovery, mount system, factory reset, reboot. There. Now u will hear t mobile jingle and it will reach set up wiz
nikkosaurus said:
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?
Click to expand...
Click to collapse
I flashed supersu after the dm verity had no problems
benny3 said:
I flashed supersu after the dm verity had no problems
Click to expand...
Click to collapse
Which TWRP version is people using?
https://forum.xda-developers.com/ga...ecovery-galaxy-j7-sm-j700t-t1-t3560342/page30
Same as mm
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
Yes, it does
.
uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
hightech316 said:
Yes, it does
.
Click to expand...
Click to collapse
fullofhell said:
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
Click to expand...
Click to collapse
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.
carlosbalbuena_ said:
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.
Click to expand...
Click to collapse
That is bizarre. I tried official first and nothing would activate
fullofhell said:
That is bizarre. I tried official first and nothing would activate
Click to expand...
Click to collapse
I have all these modules active and it works perfectly
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!