Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.
Hi Guys,
Forgive the noobie Question; I am searching, but I’m after verification and advice;
I’m very new - I’ve just purchased myself a Pixel 2XL 128Gb today.
I’m coming from a Note 4, that had Magisk and systemless Xposed. (And TWRP)
From what I’ve researched so far, I can install root via Magisk, following this procedure;
https://www.xda-developers.com/how-to-unlock-bootloader-and-root-the-google-pixel-2-and-pixel-2-xl/
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176
And possibly get Xposed via here;
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 (anyone know which version?)
My questions are, for those who have a Pixel 2 XL, and are Rooted/Xposed..
1) Are these the best guides to follow?
2) Should I back anything up (EFS/IMEI etc) before I do any modding? If so, how? (when it’s unrooted / locked)
3) Is there any point having TWRP?
(I used to use this for backup / restore / flashing, but I can flash stuff via ADB, is there any advantage to having it?
I would like to update OS as updates come along, but if TWRP is going to cause issues, then I can go without..)
4) is it safe to use Xposed? I have a few modules I want to continue using, but read it can cause issues. What’s the safest way to set this up.
5) Is there anything else I should know / consider before I set this up / unlock / root / xpose etc?
6) Should I stay on stock, or change Kernel? Which Kernels are considered the best for the 2XL?
(I may have more questions..)
Thanks in Advance!
Brik
BrikHaus said:
Hi Guys,
Forgive the noobie Question; I am searching, but I’m after verification and advice;
I’m very new - I’ve just purchased myself a Pixel 2XL 128Gb today.
I’m coming from a Note 4, that had Magisk and systemless Xposed. (And TWRP)
From what I’ve researched so far, I can install root via Magisk, following this procedure;
https://www.xda-developers.com/how-to-unlock-bootloader-and-root-the-google-pixel-2-and-pixel-2-xl/
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176
And possibly get Xposed via here;
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 (anyone know which version?)
My questions are, for those who have a Pixel 2 XL, and are Rooted/Xposed..
1) Are these the best guides to follow?
2) Should I back anything up (EFS/IMEI etc) before I do any modding? If so, how? (when it’s unrooted / locked)
3) Is there any point having TWRP?
(I used to use this for backup / restore / flashing, but I can flash stuff via ADB, is there any advantage to having it?
I would like to update OS as updates come along, but if TWRP is going to cause issues, then I can go without..)
4) is it safe to use Xposed? I have a few modules I want to continue using, but read it can cause issues. What’s the safest way to set this up.
5) Is there anything else I should know / consider before I set this up / unlock / root / xpose etc?
6) Should I stay on stock, or change Kernel? Which Kernels are considered the best for the 2XL?
(I may have more questions..)
Thanks in Advance!
Brik
Click to expand...
Click to collapse
Dang! That's a lot of questions! Lets see....
1. Look at this guide...https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
2. Backup EFS after twrp is installed.
3. I like twrp to backup/restore and flash kernels and magisk. Monthly updates won't harm twrp, you just install it again.
4. Many use exposed without issue. Follow the guide you already have.
5. Make sure you unlock _critical when you unlock the bootloader.
6. I like custom kernels. Flash kernel is the most popular, and is updated regularly.
7. Next question ?
Badger50 said:
Dang! That's a lot of questions! Lets see....
1. Look at this guide...https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
2. Backup EFS after twrp is installed.
3. I like twrp to backup/restore and flash kernels and magisk. Monthly updates won't harm twrp, you just install it again.
4. Many use exposed without issue. Follow the guide you already have.
5. Make sure you unlock _critical when you unlock the bootloader.
6. I like custom kernels. Flash kernel is the most popular, and is updated regularly.
7. Next question ?
Click to expand...
Click to collapse
Thank you very much Badger50! I'm very keen to play with this, but obviously don't want to brick it!
What's the best 'Order of operation'?
Unlock > Flash TWRP > Backup > Flash Magisk > Flash Kernel > Flash Xposed?
BrikHaus said:
Thank you very much Badger50! I'm very keen to play with this, but obviously don't want to brick it!
What's the best 'Order of operation'?
Unlock > Flash TWRP > Backup > Flash Magisk > Flash Kernel > Flash Xposed?
Click to expand...
Click to collapse
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Badger50 said:
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Click to expand...
Click to collapse
Awesome! Thank you!
Badger50 said:
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Click to expand...
Click to collapse
Systemless Xposed still trips safetynet right?
darkfire404 said:
Systemless Xposed still trips safetynet right?
Click to expand...
Click to collapse
That is correct.
sublimaze said:
That is correct.
Click to expand...
Click to collapse
Is there any way to avoid xposed tripping safetynet? Or do I have to go with a custom kernel like Flash?
BrikHaus said:
Is there any way to avoid xposed tripping safetynet? Or do I have to go with a custom kernel like Flash?
Click to expand...
Click to collapse
You use xposed you will trip safety net.
p70shooter said:
You use xposed you will trip safety net.
Click to expand...
Click to collapse
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
BrikHaus said:
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
Click to expand...
Click to collapse
The Devs are always working on things for xposed and magisk, so maybe someday a true fix can be found. However, as of now, it's either...don't use exposed and use your banking apps, or, use xposed, and pull out your credit card :good:
NVM
BrikHaus said:
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
Click to expand...
Click to collapse
If you depend on Google Pay or an app that requires SafetyNet validation, then you can't use Xposed. The purpose of SafetyNet is to check the integrity of the system, and installing Xposed framework changes that. There is no way around it.
However, some Xposed mods are available as Magisk modules, which remain hidden from SafetyNet. Open Magisk, tap the hamburger menu at top left and check the "Downloads" list. If the mod you want is not listed, then you must install Xposed and give up SafetyNet. Unfortunately, that is just the way it is.
I understand why people prefer using their bank's phone app instead of using a web browser.
But I don't use my bank's app because if I lose my phone, I don't want the person that finds it to know I which bank I use. That is just one step closer to someone gaining access to my account.
Huge Thanks for your reply @Badger50!
Managed to sucessfully install TWRP, Magisk, Flash Kernel and xposed, all without issue.
Cheers Mate, very appreciate your answers & tips.
Not fussed to lose SafetyNet. Still use cards when shopping, and much prefer xposed functionality.
Hey Guys,
I got a System message that says my XL tried to install a critical update and failed.
I assume this is because I'm running the FLASH kernel.
My question is do I need to flash this, or will the patches be incorporated into a FLASH release at some point?
Do other people bother with these? or just swipe away?
Cheers!
B
BrikHaus said:
Hey Guys,
I got a System message that says my XL tried to install a critical update and failed.
I assume this is because I'm running the FLASH kernel.
My question is do I need to flash this, or will the patches be incorporated into a FLASH release at some point?
Do other people bother with these? or just swipe away?
Cheers!
B
Click to expand...
Click to collapse
Having been rooted since root was available on my P2XL, I've never had one of those notifications. Then again, I have automatic updates turned off in developer options. Are you on the May release?
Badger50 said:
Having been rooted since root was available on my P2XL, I've never had one of those notifications. Then again, I have automatic updates turned off in developer options. Are you on the May release?
Click to expand...
Click to collapse
I believe so.
Kernel version
4.4.127-FlashKernel-Taimen-v2.30 (clang version 7.0.0)
[email protected] #1
Sun Apr 8 04:05:46 MST 2018
BrikHaus said:
I believe so.
Kernel version
4.4.127-FlashKernel-Taimen-v2.30 (clang version 7.0.0)
[email protected] #1
Sun Apr 8 04:05:46 MST 2018
Click to expand...
Click to collapse
The kernel won't make any difference with those notifications. Just shut them off. By May release I meant the OS build number.
Badger50 said:
The kernel won't make any difference with those notifications. Just shut them off. By May release I meant the OS build number.
Click to expand...
Click to collapse
Apologies !
it's
OPM2.171019.029
BrikHaus said:
Apologies !
it's
OPM2.171019.029
Click to expand...
Click to collapse
No worries. Are you ok April or May security patch?
Just got my S9 all set up just they way I like it. But part of the way I like it means knox has been tripped which means no more OTA updates for me. Is there a preferred method to keep my device up to date without having to go through flashing TWRP and all those other steps some of us like to do?
Only by flashing a new custom ROM from TWRP, if you are stock and want to keep stock you'll have to flash the updated stock with ODIN then flash TWRP again afterwards
phrosyn said:
Just got my S9 all set up just they way I like it. But part of the way I like it means knox has been tripped which means no more OTA updates for me. Is there a preferred method to keep my device up to date without having to go through flashing TWRP and all those other steps some of us like to do?
Click to expand...
Click to collapse
I'm currently all stock still.. what are the things you have done to get it set up the way you like it?
b_rad_1983 said:
I'm currently all stock still.. what are the things you have done to get it set up the way you like it?
Click to expand...
Click to collapse
First I installed TWRP to give me a really nice backup and restore solution
Then, I used TWRP to flash a custom rom and also Magisk
Then, I use Magisk to install YouTube Vanced (no-ads)
Magisk also provides a root-like access for me to install ad-away and remove any bloatware that I don't like
Finally, I sometimes experiment with different things through the time I have the phone
Which rom did you choose?
b_rad_1983 said:
Which rom did you choose?
Click to expand...
Click to collapse
Soldiers ROM. It was just a simple no nonsense easy to debloat ROM
Any way to get magisk and TWRP on latest stock firmware?
Yes.
If you want both, you might as well install TWRP first since you need to reinstall Magisk after TWRP.
There are guides on the forum but they tend to focus on one or the other.
For OTA updates you'll need to jump through hoops due to the modified partitions.
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
a1291762 said:
Yes.
If you want both, you might as well install TWRP first since you need to reinstall Magisk after TWRP.
There are guides on the forum but they tend to focus on one or the other.
For OTA updates you'll need to jump through hoops due to the modified partitions.
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
Click to expand...
Click to collapse
Thanks
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks