you have to unlock bootloader
if you can boot on this TWRP file (if screen working) you can copy 2 files on sdcard : Fix_vendor_10.0.zip and magisk.zip
you have to use odin in download mode to flash in AP the TWRP
you can find instructions here : https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
No, Root rights will not give this opportunity
On the T290 model, you can sew at least 9, at least 10, at least 11 android, since so far the bootloader version 3 is everywhere
Please read earlier posts.I have tried rooting with TWRP but i get blank screen. I have also tried to patch the firmware.
I have firmware T290KOO3BUE2/
I have tried different methods, and wondered if i have done something wrong.
I have tried the direct patch the AP, that fails with secure check failed vbmeta, while flashing in download mode, shows on the tablet screen.
I have tried extracting the boot, recovery, vbmeta, making tar, patching them with magisk. dd command to fill the files. Put it all back together, and try to flash, and i get the same secure check failed vbmeta.
I am doing something wrong? It is driving me mad.
Posts say you have to go to recovery and wipe device.
I have tried this
Do i have to let it go to blue screen to erase and go to recovery after? as if i try before that
i do not get the standard recovery page, i get 4 lines saying power off - recovery - fastboot - reboot.
If i go to recovery, it goes to a download mode but with black screen instead of the normal blue screen.
If i choose fastboot, nothing happens, and restarts.
After the erasing screen, i can go to the normal recovery mode, and can wipe -reset it, but no magisk and the firmware boots up ok but without magisk, i have installed the magisk apk, but says NA and tried a root app and fails to get root.
Driving me crazy
The whole purpose of replacing the vbmeta is to MAKE it fail. If it didn't fail, you'd only be able to flash "official" stock images. It is the part of the boot process that checks to make sure the ROM is "official".Please read earlier posts.
SECURE CHECK FAIL: vbmeta
does *not* mean you have failed. I got this message the time I succeeded.
From what I remember, after downloading with Odin, go directly to recovery to wipe data. If Android boots before you wipe data, I think you have failed, and should start over.
Once you have wiped data, you have to meet the challenge of booting towards recovery, without getting to recovery. I think it was @gcrutchr who gave me the tip I needed to find the right moment to release the buttons.
If you get to Android, but there is no sign that Magisk is installed and running, *do*not* go back to Odin. Shut down (Power Off). Try booting again. At least a dozen times. This is a very fussy step. You have to hold the buttons to boot to recovery, because Magisk is in recovery. But you have to release the buttons before Magisk checks them, because that's how Magisk decides between letting recovery boot and run, and Magisk keeping control and booting Android. It is miserable. There is no sign that Magisk is in control until long after Android has booted.
Every time Android comes up (when you are still trying for that first successful boot of Magisk), you have to run the Magisk Manager app. (If you don't see it in your app drawer, you have to install it.) The app has panels that talk about the status of Magisk and of Magisk Manager. More importantly, the first time Magisk is in control, the Manager will say something like "need to do some more setup". THIS is the sign that you have succeeded: You managed to install Magisk, and you managed to trigger it.
This has all been covered, repeatedly. In @topjohnwu 's installation notes. In posts in this (or maybe one of the related) thread. It will be a relatively early post.
UPDATE: I just read a post in the Magisk thread that says (since version 16) Magisk checks for a copy of the Manager and, if necessary, installs a stub. So maybe if you boot and don't find a Magisk Manager app, that *is* a clear sign that you have not triggered Magisk. But if you install the app once (after wiping data), you won't need to install it again, no matter how many times you reboot trying to hit the sweet spot.
Tenho a sensação de que o firmware não está piscando com o AP corrigido.
Eu instalei o firmware e destruí muitos aplicativos, pois desisti de tentar fazer o root
Decidi fazer mais algumas tentativas de root.
Instalei o firmware com arquivos corrigidos do Magisk (sucesso com o odin). Eu faço uma limpeza / reformatação. Tentei iniciar o tablet com recuperação magisk, carregado android.
Nenhum magisk e também os aplicativos que desabilitei, ainda estão desabilitados.
Tentei novamente, Odin flash - sucesso, recuperação - limpar / redefinir - deixar o Android carregar - aplicativos ainda ausentes
Em seguida, tentei fazer o flash do firmware original sem o patch magisk. Odin flash - sucesso, recuperação - limpar / redefinir - deixar o Android carregar - todos os aplicativos estão de volta
Talvez seja por isso que o magisk não está funcionando? Mas se estou tendo sucesso com o odin, por que não está piscando?
really confusing, but from what you said, maybe you started without magisk, this is possible because magisk is initially installed on the recovery partition, as far as I know, that's why that it's interesting to put the TWRP to rootUpdate
I have a feeling the firmware is not flashing with the patched AP.
I installed the firmware, and debloated many apps as i gave up trying to root
I decided to have a few more tries trying to root.
I installed the firmware with magisk patched files (success with odin). I do a wipe/reformat. Tried to start the tablet with magisk recovery, loaded up android.
No magisk and also the apps that i disabled, are still disabled.
Tried again, Odin flash - success , recovery - wipe/reset - let android load up - apps still missing
I then tried to flash the original firmware without the magisk patch. Odin flash - success, recovery - wipe/reset - let android load up - all apps are back
Maybe this is why magisk is not working? But if i am getting success with odin, why is not flashing?
What "other lz4 files"?More updates
I tried to downgrade to T290XXS3ATF1 which worked but blank screen like Twrp
I then flashed -T290XXU3BUC1- which worked and had my screen back.
I then extracted the files for magisk and packed in tar with the other l4z files.
Flashed and Odin (modded) failed
So now I am at an even more loss
Tried all versions of Magisk, including the version CANARY 20.4 (20303) | 7.5.2 (272) (7).
But none of them work
And to restore the device,it is enough to flash the current firmware, or even 3 files are enough: boot;recovery;vbmeta, pulling them out of the AP part of the firmware ...
No one wants to deal with our device...
You can only install TWRP and not get Root rights. But you still need to change the bootloader to the one taken from android 9 and the patched vbmeta file ... You will also need to make format data and install the Fix_vendor_10 patch from TWRP to access memory ...I want to root this tab just so that I can provide signature level permissions to sideloaded apps to make them work (As this tablet has stupid One UI Core, no Good lock modules or Bixby apps work).
Is there a way to provide them signature level permissions or convert them to system apps without root? Can we do that in Twrp by moving .apk files to /system privileged without root? If it is possible just by Twrp and works well then there is no reason for me to root my device.