Hello!
I'm a bit of a noob with the whole Android scene, but I hope to one day be able to fully understand the root process and how magisk works, but as of right now I'm in a bit of a conundrum.
As some of you know, Samsung is pretty rough when it comes to rooting, particularly with the OEM problems and the Knox e-fuse. Dr. Ketan made a fix for the OEM problems, using a special tool which installs magisk 18.
However, I want to upgrade to magisk 20, but I'm not sure if the SM-G965N (S9+, Korean version) can actually run it.
Now, the question:
Does anybody know if I can just install it normally via TWRP like with any other phone? Or I'm stuck on magisk 18 until another developer updates the ketan OEM fix to magisk 20?
And secondly, can I update my phone to Android 10 and still install magisk normally, if the latest version of magisk supports the S9+? A while back they released the Android 10 update in Sammobile, but I don't know if I can flash my phone and still be able to run magisk in it.
Thanks in advance!
EDIT: I used the old Android 8 method (No-verity-opt-encrypt 6.0, RMM Bypass and Magisk 20.3) and it just bricked my device. It was stuck on the Samsung S9+ screen, so that was a no go. Had to revert to my latest backup via TWRP
Related
Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!
I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.
Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...
i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!
Use the latest official TWRP (currently 3.1.0-1). Works just fine.
i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.
I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!
I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!
What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip
Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.
And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?
Hello, first time here but I need some help.
So I wanted to root my P10 (mainly for Viper) and I started digging around here and there (mostly in XDA). I followed few guides (on how to unlock the bootloader, how to flash TWRP, how to root...) but I still can't pull this off. Anyway, straight to the problem:
So as you can see I'm using P10 on Oreo (B360) and EMUI 8.0. I unlocked the bootloader using ADB & fastboot. Then I flashed this TWRP: link
So far everything went smooth and without any errors. I am able to boot into TWRP. So here I'm stuck trying to flash the root.zip (this one). Whenever I try I get the Error: 1 (as mentioned in the thread), however, I read here in XDA that on Oreo flashing boot.img bricks the phone? I saw several threads of people with bricked phones due to flashing boot.img. My question is - what do I do here?
I looked for other solutions like Magisk but from what I understood Viper4Android doesn't work on it.
Anyone... anything? I'd really appreciate any help.
If it's not possible (even though I've seen people with rooted P10s on Oreo...) is there a way I can revert back the changes I did so I can remove the warning message on bootup and possibly have my warranty back?
you Cant root it yet beacose there is no twrp for emui 8, so look and try some methodes root without TWRP
and why you wanna rooot emui 8, there is nothing for it, yet.
What do you mean? I already said I have TWRP and I'm able to boot into it without problems. I even linked the unofficial TWRP I flashed in my first post. Plus I saw few people here that have rooted P10s on Oreo. And finally all I want to install is Viper.
There is this TWRP by @espaciosalter20 : https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449
should work, support for data decrpytion...
I used MAGISK 16 to root my OREO EMUI 8.0 P10
-done....
about super root and supersu working on OREO EMUI 8.0 you have to ask in the ROOT thread.
about viper4android i don´t know..i don´t use it.
I need to get something straight, as I didn't quite get it. So the options for someone who'd like to root his S10 are 3:
1) Rooting with Topjohnwu method: This will get you root on the stock rom, but will keep the default recovery which is pretty much useless if one wanted to flash a custom rom.
2) Rooting with a prepatched version of TWRP and then, if desired, flash any custom rom (compatible with the TWRP version installed). This method is said to be less stable that the previous one.
3) Install TWRP after rooting with john wu method and then using it to flash custom rom.
First of all, is all this correct?
If so, then one has to choose between rooting safely, but keeping his phone stock, or rooting and then installing twrp and then flash whatever he desires.
Hopefully, somebody will be so kind to clarify this that is an unusually complicated situation about rooting this phone! I already regret passing my perfectly rooted S9 to my son
Thanks for whatever help you'll be willing to provide.
Cheers
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Norup58 said:
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Click to expand...
Click to collapse
One more doubt, if I may ask : once rooted the safe way, if I wanted to install twrp I would need to find the build that is compatible with the already patched firmware on my phone? And then only the roms that are exactly for the same build?
This is the most complicated rooting process that I have ever faced. And I've been rooting my phones and tablets since a very long time
Thanks
Last week I bought the Galaxy A90 5G (SM-A9080, China version), and immediately searched for ways of Magisk installation.
Indeed there are multiple articles from Google showning the methods. I tried most of them and regretfully all failed.
Even I followed the instruction from this forum, however, I still failed.
This is because of my current model? Because the current version of Magisk is not updated enough? Because of the mechanism of Samsung's Android 9 OS?
I also got the Galaxy Note8 running Android 9, and the way of Magisk installation on Android 8 and previous ones does not work on Android 9.
I do need Root/Magisk due to my requirement, but there is likely a huge barrier preventing me from the Root.
Thus, there is no possible solution?
jasonc417 said:
Last week I bought the Galaxy A90 5G (SM-A9080, China version), and immediately searched for ways of Magisk installation.
Indeed there are multiple articles from Google showning the methods. I tried most of them and regretfully all failed.
Even I followed the instruction from this forum, however, I still failed.
This is because of my current model? Because the current version of Magisk is not updated enough? Because of the mechanism of Samsung's Android 9 OS?
I also got the Galaxy Note8 running Android 9, and the way of Magisk installation on Android 8 and previous ones does not work on Android 9.
I do need Root/Magisk due to my requirement, but there is likely a huge barrier preventing me from the Root.
Thus, there is no possible solution?
Click to expand...
Click to collapse
I own a A908B (German Version) and I'm on Android 10 running Magisk on Stock OS. This is the tutorial i followed and it works. Since there is no Custom Recovery yet the only thing we can do right now is patch the AP-Image of every single update we get... And be prepared to backup everything you have because it's going tor require a full data wipe
Thanks for your advice.
Last night I upgraded my SM-A9080 to Android 10 and managed to get the phone rooted via Odin3.
yomama163 said:
I own a A908B (German Version) and I'm on Android 10 running Magisk on Stock OS. This is the tutorial i followed and it works. Since there is no Custom Recovery yet the only thing we can do right now is patch the AP-Image of every single update we get... And be prepared to backup everything you have because it's going tor require a full data wipe
Click to expand...
Click to collapse
I updated my s9 ultra to Android 13 a few weeks early. Then I tried to get the root back following the below thread.
Root Guide for Galaxy Tab S8/S8+/S8Ultra
See post #3 for in depth guide ! ->insert usual general disclaimer of liability Required: Odin3_v3.14.1 flash tool Samsung USB Driver installed Frija or something else, to download stock files 7zip or similar 1: Unlock bootloader (will wipe...
forum.xda-developers.com
On that day, the newest magisk version was 25.0, I followed all the steps in the above thread but the device was still bricked (boot loop).
I searched the error log and figured out that this was due to something called "avb flag":
Samsung system init check fstab avb flag cause boot loop · Issue #6141 · topjohnwu/Magisk
Device: Samsung Tab S7 Plus (T976B) Android version: 12 Magisk version name: 25.2 Magisk version code: 25201 For some reason, samsung decided to make their /system/bin/init check for avb flags in f...
github.com
Since I don't have much time on this, I simply did a factory reset and kept using the tab without root.
I am actually not sure whether the "avb flag" is the root cause. The only thing I am sure of is using magisk 25.0 and s8ultra android 13 ROM leads to a boot loop.
Today, I found that magisk is now updated to 25.3, and nobody here mentioned the boot loop.
So, I want to know whether magisk 25.3 is working well with the newest ROM. If it works OK, I will give it another try.
I have a Tab S8 Ultra which was on Android 12 / OneUI 4.1 rooted / Magisk. I just finished updating it to Android 13 (image SM-X906B_2_20221208191241_81t9w4gald_fac) without any dramas. I did a factory reset before flashing the patched AP, not sure if that helped avoid any potential bricks or you were just unlucky.
I'm only on Magisk 25.2 though - I don't see the 25.3 that you mention anywhere. So make sure you're downloading from topjohnwu's GitHub page, not some other sketchy place. That might be a factor.
FerretallicA said:
I have a Tab S8 Ultra which was on Android 12 / OneUI 4.1 rooted / Magisk. I just finished updating it to Android 13 (image SM-X906B_2_20221208191241_81t9w4gald_fac) without any dramas. I did a factory reset before flashing the patched AP, not sure if that helped avoid any potential bricks or you were just unlucky.
I'm only on Magisk 25.2 though - I don't see the 25.3 that you mention anywhere. So make sure you're downloading from topjohnwu's GitHub page, not some other sketchy place. That might be a factor.
Click to expand...
Click to collapse
Well, I think “25.3” is a typo. I always download the magisk APK from github. I also tried a factory reset.
May the issue is already fixed in a way. I'll try it again some time.