AnonVendetta said:

When I used the vbmeta, I always flashed it on top of a stock firmware that had been flashed with Odin. After leaving download mode, it didn't even try to boot Android. It just took me straight to stock recovery with a message saying I would need to reset. I expected this, having done it numerous times already. Not sure what's going on in your case.

If it only took you to Android, then maybe you had flashed that file before. Which means no signature change. I was never able to boot into android with the vbmeta I've linked, without a reset.

When I was initially trying to get twrp installed, I used the old vbmeta that was different from the one you used. I put it in the AP slot and it did exactly what you described in your case. I guess at this point, I could just flash twrp again and install magisk from there and then try to change the recovery file in /vendor to keep it from changing to stock.

SavXL said:

When I was initially trying to get twrp installed, I used the old vbmeta that was different from the one you used. I put it in the AP slot and it did exactly what you described in your case. I guess at this point, I could just flash twrp again and install magisk from there and then try to change the recovery file in /vendor to keep it from changing to stock.

Patching your boot image is the recommended way of installing magisk on Samsung devices, not from TWRP. It also says this on magisk's official help pages. Installing from recovery may also work, but it's less than ideal.

Installing Magisk

You dont need to patch the entire huge AP firmware file, if you have already flashed the firmware package and are just wanting to root. Use these instructions to patch boot.img only (will still get you fully rooted, and you'll be flashing a much smaller file):

Patch boot.img

the boot.img also needs to come from the same firmware, dont try to use others. Best to use a boot.img whose version exactly matches the firmware.

Patching the entire AP is apparently only necessary if you want to upgrade without losing root.

The recommended order I use when installing a new Android version:

1. Flash full official firmware with Odin (I always do clean flashes only, never upgrades that don't require wiping data)

2. Boot android, connect to net, enable developer options, make sure OEM unlocking is enabled

3. Flash vbmeta in Odin

4. Reset again, and redo step 2

5. Flash Magisk. Once you are back in Android, you can use magisk to reboot to download mode

6. Flash twrp in Odin.

7. Boot twrp, flash @ianmacd's Samsung multi disabler zip (I do this mainly to disable forced encryption of data partition, if you want it then skip this. But you won't be able to do backups of data from TWRP without them being huge).

8. While you're still in twrp, do this so Android doesn't overwrite your TWRP with stock recovery.

Prevent stock recovery from coming back

9. Do a factory reset from TWRP/format data (to remove any encryption on data partition)

After this you are done, boot Android and set things up to your liking.

My process takes an hour to finish at most. It can seem a little slow the first time around. I've been doing the same thing for months and it has always worked, so I'm not changing it.

AnonVendetta said:

@robroy90: You shouldnt need to start from scratch. Just do steps 6, 7 (optional, but if you do this then you must format data/factory reset to remove encryption), and 8 from my post directly above yours. Tar the recovery.img and flash in Odin.

We have the exact same model and i'm also running Android 12 CVA5 firmware, so my steps should work for you.

Thank you very much, I appreciate that! I will give it a go then!

emko7 said:

Any chance this would work on the Tab S8+ 5G?

No.

AnonVendetta said:

Patching your boot image is the recommended way of installing magisk on Samsung devices, not from TWRP. It also says this on magisk's official help pages. Installing from recovery may also work, but it's less than ideal.

Installing Magisk

You dont need to patch the entire huge AP firmware file, if you have already flashed the firmware package and are just wanting to root. Use these instructions to patch boot.img only (will still get you fully rooted, and you'll be flashing a much smaller file):

Patch boot.img

the boot.img also needs to come from the same firmware, dont try to use others. Best to use a boot.img whose version exactly matches the firmware.

Patching the entire AP is apparently only necessary if you want to upgrade without losing root.

The recommended order I use when installing a new Android version:

1. Flash full official firmware with Odin (I always do clean flashes only, never upgrades that don't require wiping data)

2. Boot android, connect to net, enable developer options, make sure OEM unlocking is enabled

3. Flash vbmeta in Odin

4. Reset again, and redo step 2

5. Flash Magisk. Once you are back in Android, you can use magisk to reboot to download mode

6. Flash twrp in Odin.

7. Boot twrp, flash @ianmacd's Samsung multi disabler zip (I do this mainly to disable forced encryption of data partition, if you want it then skip this. But you won't be able to do backups of data from TWRP without them being huge).

8. While you're still in twrp, do this so Android doesn't overwrite your TWRP with stock recovery.

Prevent stock recovery from coming back

9. Do a factory reset from TWRP/format data (to remove any encryption on data partition)

After this you are done, boot Android and set things up to your liking.

My process takes an hour to finish at most. It can seem a little slow the first time around. I've been doing the same thing for months and it has always worked, so I'm not changing it.

Click to expand...

HI. Some questions:

1. how to find (and determine) what official firmware you have currently installed?
2. where to find your OEM firmware (links)?
1. where do you get vbmeta, link?
2. how to verify OEM unlocking is enabled?

Hopefully you can clarify. Thanks.

Michael Carleone said:

HI. Some questions:

1. how to find (and determine) what official firmware you have currently installed?
2. where to find your OEM firmware (links)?
1. where do you get vbmeta, link?
2. how to verify OEM unlocking is enabled?

Hopefully you can clarify. Thanks.

The firmware version you're running should be listed in the Settings app in the About section (it's on the same screen as the build # info).

You can get your firmware from Frija. I also use galaxyfirmware.com and SamFW.

The neutralized vbmeta I use is at vbmeta. Use the vbmeta_disabled.tar file, flash it in Odin in the userdata slot, not AP. You will most like have to do a data wipe/factory reset after flashing this, Android probably won't boot. It's a 1 time thing, vbmeta will stay neutralized unless you flash an official firmware. So, backup any important info beforehand.

You can check the status of OEM unlocking in developer options. If it's disabled and grayed out (can't be toggled), you're fully unlocked. You won't be able to flash amy thing other than stock images, unless this is disabled.

arlequin2k3 said:

Hello ,
I'm out of topic but I would like to know if a twrp would be in progress for the S8, S8+ and S8 ultra tablets. Thank you for your reply .
@+

Probably, but as you said yourself, wrong topic. The Tab S8 has its' own subforum on XDA, best to post your question there.

Techguy777 said:

I have the tab S6 and just updated to one UI 4.1 and I'm trying to figure out how to flash TWRP. Every time I hit the button combos to cause a reboot volume down and power up I end up in RDX mode since the update any help would be nice.

This is a Galaxy Tab S7 Subforum.

AnonVendetta said:

@robroy90: @ianmacd posts newer versions of his Android 12 TWRP in his Telegram channel. I suggest you install the app, register a free account, and subscribe to the channel (it's mentioned on first post of this thread). Right now I'm using a newer build than the one you mentioned. My suggestion is to get the img from there instead of his AndroidFileHost link. They usually have bugs fixed. Just rename it to recovery.img and tar it, same as usual.

If you want to update your TWRP in the future, no need to use Odin. Just put it on tablet and flash the img from within TWRP (it has an img flash option built in).

Would you happen to know the channels name or link I will definitely check those two or one group out thank you

AnonVendetta said:

@Y2Ne1: Android 12 is definitely rootable, I did it myself. And since you have a Tab S7+, TWRP should work too. No TWRP for Tab S7 (non plus), only root. That's part of the reason I bought the plus model instead.

I've downgraded to Android 11 BUJ3, because some things on 12 werent working as expected.

I can't remember the name of @ianmacd's TWRP channel, but you can find it in his 1st post on his Tab S7+ TWRP thread.

Thank you so much man I really appreciate the info hopefully I can contribute to the tabS7+ community along with 5G