Database Info

[GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update

A simple guide for users which will help them to install TWRP on their S8 after Oreo Update.
This guide is only for Exynos models.
Requirement -
1. PC/Laptop
2. Original Samsung USB Type-C Cable
3. Prince Comsy Odin (Because some users reported on this thread that normal Odin doesn't work)
Instructions -
1. Backup your important data from internal storage before proceeding towards the installation.
2. Now go to Settings - About Phone - Software Information - Tap On Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON.
4. Power off device and boot into download mode.
5. Connect your device to the PC/Laptop.
6. Now Open Prince Comsy Odin and click on the AP option.
7. Choose the TWRP .tar file and press the START button.
8. Now after Odin says PASS, press the VOLUME UP, BIXBY KEY, and POWER BUTTON at the same time until device boots into TWRP recovery.
9. Now allow the modifications and go to WIPE option.
10. Choose FORMAT DATA - Type yes - ENTER.
11. Just Reboot Once Into Recovery Once.
12. Flash no-verity-opt-encrypt.zip.
12. Now Choose INSTALL option and install Magisk or SuperSU.
13. Done!
You can also refer to this video for installation of TWRP - https://www.youtube.com/watch?v=2SqgHFcHLMw
Downloads -
Latest TWRP For Exynos S8 - TWRP 3.2.1-0-DREAMLTE
Prince Comsy Odin - https://drive.google.com/open?id=1enVG5a_ocyjhRlta8AX_0b7LLoHWciVU
No dm-verity - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
SuperSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Credits -
@jesec for TWRP
@topjohnwu for Magisk
@Chainfire for SuperSU
Prince Comsy Odin

The main problem is that most users dont have oem unlock after oreo update (e.g me)

EugenStanis said:
The main problem is that most users dont have oem unlock after oreo update (e.g me)
Click to expand...
Click to collapse
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox

Ruturaj Kadam said:
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Click to expand...
Click to collapse
Flashed official XEO for Poland and still OEM unlock isnt there :/

Does the Oreo update affect the the locked bootloader on the Snapdragon version? I thought it was impossible to install TWRP on the Snapdragon versions of the S8?

I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard

EugenStanis said:
Flashed official XEO for Poland and still OEM unlock isnt there :/
Click to expand...
Click to collapse
Try use AQK7 ( 4 file firmware + re-partition PIT)
In my case I 100% success returned form CRAP to AQK7.
OEM unlock is in dev settings, no RMM and FRP.
Powodzenia ^_^

I'm guessing this is not for the US snapdragon variant.

There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.

Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.

Will822 said:
I'm guessing this is not for the US snapdragon variant.
Click to expand...
Click to collapse
I'm sorry! It was one of my friends who told me the method is same. I'm sorry again. OP edited

iamnotexisting said:
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Click to expand...
Click to collapse
I'm sorry for that! Edited the OP! Got misguided due to one of my friends

Silenus21 said:
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Click to expand...
Click to collapse
Haha yes! Exynos devices are best in performance and battery too.

This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?

168 hours Open my device oem lock on of after twrp flash data storage 0 dm verity flash wipe data

thiagomed said:
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
Click to expand...
Click to collapse
TWRP trips Knox if I'm not mistaken.

i did this guide and everything is went good but when i restarted the phone it went to a softbrick and i had to do a restore...
the error was something on the original binary

to have the OEM option, will I have to go back to crap?

I have just tried this method and booted into TWRP but the screen was totally unresponsive, rebooted and still the same. I had to go back to Oreo.
How do I get around this problem?

dr.vetony said:
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
Click to expand...
Click to collapse
Wipe / format data - " yes"

[Q] Root Canadian galaxy s7

Hello i recently bought a galaxy S7 SM-G930W8 (Canadian / BELL Mobility) and its veen updated to the latest it can which is android 8.0 (oreo) and id really like to root it without havibg to change my stock rom actually id just be glad to get it rooted also the security patch is up2date as of july 1st 2018

The W8 is an exynos model so the bootloader should be unlocked, flash twrp through odin, do a factory reset, reboot to recovery from TWRP itself, flash no-dm-verity zip which should be in your memory card, if you don't have one use mtp in TWRP and copy it to the phone, then install magisk zip and you should be good to go. you can find those two zip files in the forum or just a simple good search.

Did you have any luck rooting the SM-G930W8 on 8.0? I just acquired the Canadian S7 and I'd like to root it, but I know it's different from the American S7's, and all I can find is how to root the Canadian S7 with Nougat.

threehappypenguins said:
Did you have any luck rooting the SM-G930W8 on 8.0? I just acquired the Canadian S7 and I'd like to root it, but I know it's different from the American S7's, and all I can find is how to root the Canadian S7 with Nougat.
Click to expand...
Click to collapse
It doesn't matter which carrier it is, what matters most is the chip and the bootloader, the Canadian variant uses the Exynos soc so the steps are the same just like the international model. Start by unlocking the bootloader and installing a custom recovery, download TWRP for herolte, on your phone enable developer options, then make sure OEM unlock is checked, turn off your phone and boot into Odin, then flash the TWRP image, make sure to uncheck reboot after flash in Odin. Once flashing is done, manually reboot your phone and make sure to enter the recovery mode, do a normal factory reset, the one that asks you to write YES to confirm, then reboot to recovery again, plug your phone to the computer and copy the latest magisk zip then flash it, and that should be it basically.

Salazar33 said:
It doesn't matter which carrier it is, what matters most is the chip and the bootloader, the Canadian variant uses the Exynos soc so the steps are the same just like the international model. Start by unlocking the bootloader and installing a custom recovery, download TWRP for herolte, on your phone enable developer options, then make sure OEM unlock is checked, turn off your phone and boot into Odin, then flash the TWRP image, make sure to uncheck reboot after flash in Odin. Once flashing is done, manually reboot your phone and make sure to enter the recovery mode, do a normal factory reset, the one that asks you to write YES to confirm, then reboot to recovery again, plug your phone to the computer and copy the latest magisk zip then flash it, and that should be it basically.
Click to expand...
Click to collapse
I thought the Canadian variant with Exynos already had an unlocked bootloader? There are already instructions on how to root my exact model, but the assumption is 7.0.
I have rooted other phones before, and sometimes the requirement for a version of Android before rooting is very specific. I have no idea where to start to even verify whether the bootloader is truly unlocked, whether or not I can proceed with rooting despite having a different Android version (in my case, 8.0, not 7.0), etc.

threehappypenguins said:
I thought the Canadian variant with Exynos already had an unlocked bootloader? There are already instructions on how to root my exact model, but the assumption is 7.0.
I have rooted other phones before, and sometimes the requirement for a version of Android before rooting is very specific. I have no idea where to start to even verify whether the bootloader is truly unlocked, whether or not I can proceed with rooting despite having a different Android version (in my case, 8.0, not 7.0), etc.
Click to expand...
Click to collapse
Sorry there, I guess the correct description would be tripping knox rather than unlocking the bootloader, since you're already familiar with the process then I can tell you its totally the same, nougat and oreo aren't different enough for anything to change, allow OEM unlock, install twrp, do a data wipe, reboot to recovery again, install magisk zip and you're good to go. You might need to flash the dm verity bypass before magisk, that's another zip you can download as well.

Magisk for Samsung Galaxy a42

Anyone has tried rooting using Magisk? I just bought this last week. I want to modify the CSC feature so that I can enable auto call recording restriction in my country. That needs rooting. I don't care about the warranty. Anyone?

MaXi32 said:
Anyone has tried rooting using Magisk? I just bought this last week. I want to modify the CSC feature so that I can enable auto call recording restriction in my country. That needs rooting. I don't care about the warranty. Anyone? [ouch sorry mod there was a similar question in Q and A section]. Can you delete this ?
Click to expand...
Click to collapse
Have you tried flashing the CSC of a country that does support call recording? Or does the A42 not support call recording in any country?

ShaDisNX255 said:
Have you tried flashing the CSC of a country that does support call recording? Or does the A42 not support call recording in any country?
Click to expand...
Click to collapse
In India a42 supports call recording but in Malaysia it does not. I think flashing CSC requires root access and that is what Magisk is all about from my first question.

Hi guys,I'm interested too for call recorder on Samsung galaxy a42 5g,any ideas?

where i can find is the Firmware for this phone ? (A426BXXU1ATK4) already search in sam mobile and nothing there yet.
Thanks
Found firmware at
SM-A426B | Samsung Galaxy A42 5G | Firmware Download for Spain | PDA/MODEM: A426BXXU1ATK4 | CSC: A426BOXM1ATK4 — Samfrew.com
Samsung Firmware Download, Model: SM-A426B, PDA/AP Version: A426BXXU1ATK4, CSC Version: A426BOXM1ATK4, Region: PHE
samfrew.com
have OEM Unlocked and ready to go, should I be concerned with Qualcomm secure boot: enable?

i have tryed rooting with magisk with Success,
My process was:
had no luck passing all Ap file to the phone, ... "could not read from device"
so I passed boot.img.lz4 in lz4tool, then flashed the boot.img in magisk and packed a tar with vbmeta and recovery and the renamed magisk_patched .img to boot img,
Try to flash via odin in download mode and it fail in ODIN 3.14.
Any one with success?
Please ignore
I edit this it should be some problem with the cable... and my pc Try it again and it worked. with Magisk

*Notice this will void warranty, and I'm not responsible for any damage you may cause or data loss etc...
Process to root with magisk
requirements:
Oem unlock (develpment mode and in bootloader)
ODIN 3.14
Firmware of the image
lz4tool
7zip
Install Magisk manager.
from the image firmware extract from AP the file boot.img.lz4.
pass this in boot img.lz4 in lz4tool and copy to phone the boot.img
Patch it boot.img in magisk manager
copy magisk_patched.img to pc and rename it to boot.img
use 7zip and create a tar "magisk_patched.tar" with the boot.img , vbmeta and recovery ( extract this to from the original fw AP)
In Odin in slot AP load the magisk_patched.tar and in option untick auto reboot and press start
reboot the phone using the combo keys to go to recovery and wipe/factory reset
let it boot and then your done
install magisk manager again if needed and let it set.

MaXi32 said:
In India a42 supports call recording but in Malaysia it does not. I think flashing CSC requires root access and that is what Magisk is all about from my first question.
Click to expand...
Click to collapse
Do you have a CSC with Indian region?

Penmann said:
Do you have a CSC with Indian region?
Click to expand...
Click to collapse
I need call recorder too,if you know from where I can download firmware with Indian region?

Penmann said:
Do you have a CSC with Indian region?
Click to expand...
Click to collapse
I thought in India it's already been enabled by the carrier CSC. BTW, I live in Malaysia. You need to root your phone with Magisk and then edit the CSC feature to enable call recorder. But remember warranty is 100% void.

MaXi32 said:
I thought in India it's already been enabled by the carrier CSC. BTW, I live in Malaysia. You need to root your phone with Magisk and then edit the CSC feature to enable call recorder. But remember warranty is 100% void.
Click to expand...
Click to collapse
How can help me root?

Quick question for those who rooted this phone: once rooted, you lose the ability to use Samsung Pay, don't you?

Mwyann said:
Quick question for those who rooted this phone: once rooted, you lose the ability to use Samsung Pay, don't you?
Click to expand...
Click to collapse

rootadvisor said:
i have tryed rooting with magisk with Success,
My process was:
had no luck passing all Ap file to the phone, ... "could not read from device"
so I passed boot.img.lz4 in lz4tool, then flashed the boot.img in magisk and packed a tar with vbmeta and recovery and the renamed magisk_patched .img to boot img,
Try to flash via odin in download mode and it fail in ODIN 3.14.
Any one with success?
Please ignore
I edit this it should be some problem with the cable... and my pc Try it again and it worked. with Magisk
Click to expand...
Click to collapse
Did it trip KNOX?

rootadvisor said:
*Notice this will void warranty, and I'm not responsible for any damage you may cause or data loss etc...
Process to root with magisk
requirements:
Oem unlock (develpment mode and in bootloader)
ODIN 3.14
Firmware of the image
lz4tool
7zip
Install Magisk manager.
from the image firmware extract from AP the file boot.img.lz4.
pass this in boot img.lz4 in lz4tool and copy to phone the boot.img
Patch it boot.img in magisk manager
copy magisk_patched.img to pc and rename it to boot.img
use 7zip and create a tar "magisk_patched.tar" with the boot.img , vbmeta and recovery ( extract this to from the original fw AP)
In Odin in slot AP load the magisk_patched.tar and in option untick auto reboot and press start
reboot the phone using the combo keys to go to recovery and wipe/factory reset
let it boot and then your done
install magisk manager again if needed and let it set.
Click to expand...
Click to collapse
What procedure did you use to unlock the bootloader?
Thanks!

SO WHAT DO I HAVE TO DO TO BE ABLE TO ROOT MY AMERICAN VERSION A42 G5 I AM BRAND NEW AT THIS ROOTING THING SO PLEASE TAKE IT EASY ON ME LOL I AM GONNA TRY AND ROOT MY NOTE 9 AS WELL

I haven't rooted my phone yet. It's not useful to root yet as the phone is currently powerful and have OTA update for android 12!
I just got my Android 12 on this phone few days ago.

mroohsoogreat68 said:
SO WHAT DO I HAVE TO DO TO BE ABLE TO ROOT MY AMERICAN VERSION A42 G5 I AM BRAND NEW AT THIS ROOTING THING SO PLEASE TAKE IT EASY ON ME LOL I AM GONNA TRY AND ROOT MY NOTE 9 AS WELL
Click to expand...
Click to collapse
Samsung locks bootloaders in the USA so you won't be able to root by regular means

ShaDisNX255 said:
Samsung locks bootloaders in the USA so you won't be able to root by regular means
Click to expand...
Click to collapse
So when you say root by regular means what do you mean because I'm trying to root my American model but I dont know a way to unless I'm able to unlock the bootloader

Knowledgeispower96 said:
So when you say root by regular means what do you mean because I'm trying to root my American model but I dont know a way to unless I'm able to unlock the bootloader
Click to expand...
Click to collapse
I mean that sometimes exploits are found that allow you to gain root access without the need to unlock the bootloader. To this day I've only seen it be done on S8 and S9 so I think your chances of an exploit like that being released are very slim. There were also paid services to gain special tokens that would allow you to unlock the bootloader but those were pretty expensive, at least like 100 USD. And it's been so long that I've seen them I have no clue if they're still in business.

Question [S21+ SM-G996U/U1/W_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]

Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-G996U/U1/W- Model
USERDATA_AIO_G996_FORCE_WIPE_NO_BL_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
G996USQU4AUGQ_BIT1_SAFE.7z
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G996_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
S21 SM-G991U/U1
S21 Ultra SM-G998U/U1
TWRP Recovery Provide by @Mentalmuso
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G99*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G99*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7

Thank you it worked

Updated files in OP fixed sum bugs. Added new safetynet patch and I think wearable fix now works

..nevermind, worked fine on the first try. thumbs up xD

How To Guide Update Android OS without losing data while rooted.

Full credit to @googlephoneFKLenAsh for the guide for the s7/7+. Reposting here so y'all can see.
There are two ways to do this, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
Firmware can be downloaded here:
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
First and preferred method:​1. Download firmware, extract it and move AP file to rooted tablet.
2. Use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
3. Move that patched Magisk.tar AP back to your computer.
4 Using Odin, flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot.
Second method:​1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.

Is the guide still up to date?

noahthedominator said:
Full credit to @googlephoneFKLenAsh for the guide for the s7/7+. Reposting here so y'all can see.
There are two ways to do this, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
Firmware can be downloaded here:
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
First and preferred method:​1. Download firmware, extract it and move AP file to rooted tablet.
2. Use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
3. Move that patched Magisk.tar AP back to your computer.
4 Using Odin, flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot.
Second method:​1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
Click to expand...
Click to collapse

SERGE4NT said:
Is the guide still up to date?
Click to expand...
Click to collapse
The first method works but step one should read un-rooted and not rooted.

No. This is supposed to say rooted. Read the title of the post. This is for those who want to keep root access and update the system without wiping data.
lewmur said:
The first method works but step one should read un-rooted and not rooted.
Click to expand...
Click to collapse

SERGE4NT said:
Is the guide still up to date?
Click to expand...
Click to collapse
Yes, up to date and latest firmware is available at Samfw

lewmur said:
The first method works but step one should read un-rooted and not rooted.
Click to expand...
Click to collapse
But once you flash to the latest stock, it is no longer rooted. The whole point of using Magisk to mod the AP file, is to get root back.

lewmur said:
But once you flash to the latest stock, it is no longer rooted. The whole point of using Magisk to mod the AP file, is to get root back.
Click to expand...
Click to collapse
Are you trolling? The entire point of the guide is to MAINTAIN root access and update the system. That is why the stock AP is moved to magisk and patched. As the instructions state, if the STOCK ap is flashed it will remove root / wipe the system. Hence why we need to patch it with magisk BEFORE it is flashed to the device.

noahthedominator said:
Are you trolling? The entire point of the guide is to MAINTAIN root access and update the system. That is why the stock AP is moved to magisk and patched. As the instructions state, if the STOCK ap is flashed it will remove root / wipe the system. Hence why we need to patch it with magisk BEFORE it is flashed to the device.
Click to expand...
Click to collapse
No, I'm not trolling. It was my honest belief that you needed to have the same version ROM already installed BEFORE you used Magisk. I have always done that and backed up everything before flashing.
edit: And why would flashing stock wipe anything more the first time, if you flash HOME in CSC? Your method does save having to flash twice but it seems both should work.