For the first time, I tried to install Magisk using its standard method. So I went to https://topjohnwu.github.io/Magisk/install.html
In the first parts, I came across this sentence and was a little confused:
"If you are using a Samsung device that is launched with Android 9.0 or higher, you can now jump to its own section."
My device is Samsung Galaxy J7 Core (J701F) with its latest update, namely Android 9. But this device was released with Android 7.
Which way should I proceed now? And if I continue the first method, the device data will be deleted?
@topjohnwu
…
Related
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
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
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
bardell3600 said:
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
Click to expand...
Click to collapse
Thanks for this,
I am looking to breath some life into my wife's S2 8.0. Where did you get the March 18 firmware? I looked on Sam Mobile and I cannot download it as I am not a premium member. Her tablet is already on the July 2019 version which is what I downloaded this morning just to have on hand ( I am also in Canada)
**Update - I found a link to the firmware you mentioned and downloaded it**
Do you mind sharing the link to the download? thanx
RJC_68 said:
**Update - I found a link to the firmware you mentioned and downloaded it**
Click to expand...
Click to collapse
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
pas7771 said:
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
Click to expand...
Click to collapse
It may have been this site
Galaxy Firmware - Samsung Galaxy Tab S2 8.0 (SM-T713)
Samsung Galaxy Tab S2 8.0 Android tablet. Announced Jul 2015. Features 8.0″ Super AMOLED display, Exynos 5433 chipset, 8 MP primary camera, 2.1 MP front camera, 4000 mAh battery, 64 GB storage, 3 GB RAM.
galaxyfirmware.com
We have sold all our android devices and gone back to Apple so I cannot be 100% sure.
Hope this helps
Please help me and tell me how to root and from here exacttly to download the necesary files what i need and are corecttly , thanks!
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
aIecxs said:
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
Click to expand...
Click to collapse
aIecxs said:
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
Click to expand...
Click to collapse
help me with that man please https://forum.xda-developers.com/t/s10-g973f-problem-hash_mismatch-3-help-me-please.4537157/
assuming bootloader is unlocked successfully, create vbmeta_disabled.img and flash from Heimdall
[RECOVERY] TWRP 3.3.1 for Galaxy S10 Exynos series [G970F/G973F/G975F/G977B]
Preamble After TWRP first appeared for the S10 range of devices, it quickly became clear that there were some major issues with the initial builds. Many users were understandably frustrated at losing the ability to boot their device after...
forum.xda-developers.com
aIecxs said:
assuming bootloader is unlocked successfully, create vbmeta_disabled.img and flash from Heimdall
[RECOVERY] TWRP 3.3.1 for Galaxy S10 Exynos series [G970F/G973F/G975F/G977B]
Preamble After TWRP first appeared for the S10 range of devices, it quickly became clear that there were some major issues with the initial builds. Many users were understandably frustrated at losing the ability to boot their device after...
forum.xda-developers.com
Click to expand...
Click to collapse
create vbmeta_disabled.img how or from here i download or ? im new on that i really dont know or understeand
no download, create yourself like described in first post. search for 'vbmeta' in browser and read how to
edit: found download link for vbmeta_disabled.img
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.