What is your blog? I tried to find it via your xda profile, github, etc but didn't find it.
I'm the one who made that TWRP port. I feel like someone with experience doing this could easily get touch working. I just can't seem to pinpoint whatever setting is off. There are folks on xda who have made twrp ports for lots of Samsung devices. If you dm one of them we may be able to get help. My device is out of service for the next few weeks so I can't do further development at the moment.Guys, I was looking for forums about the SM-T500 and ended up finding several, but none that were completely helpful, so I wish we could in this post talk about how to create and actually create a working TWRP, or a way to get to TWRP or other recovery, I'm still a beginner at this, so I need your help.
I saw that one person on this forum: https://forum.xda-developers.com/t/...k-bootloader-root-with-magisk.4185993/page-12
Was able to create a TWRP that towtch screen does not work.
This github: https://github.com/agreenbhm/android_device_samsung_gta4lwifi/releases/tag/v1.0-beta1
PS: I ended up using a translator, so maybe it didn't look as good.
Translated with www.DeepL.com/Translator (free version)
We still do not know just yet since Gapps isn't working atm but you can try by Plugging your Device into the USB slot and download the needed files (Don't do ADB sideload do ADB install)
Enable magisk hide should helpHad to redo this after testing a new rom and going back to stock. However I get safety net check failed not sure what I did wrong other than not factory resetting as I was unable to get into recovery. Any help would be appreciated at this time I have not used magisk before so Trial and Error for me...
(edit) I do appear to have root though so I am not sure why safety net fails check
Thanks for your postings! TWRP-3.5.x_gta4lwifi and CustomROM (LOS) is also my wish for the SM-T500.
That's completely alright. I can understand.
Just for the sake of experimenting, I deliberately rebooted the tablet before completing the additional setup by Magisk to land my Tab A7 to the "Only official binaries are allowed to be flashed (vbmeta)" error.
I will try and explain exactly what happened.
1) This isn't caused by KNOX being tripped or the warranty status string changing its value to 0x1. That will never affect flashing in any way.
2) As I mentioned in my comment, this is caused because Magisk didn't get the chance to patch and disable the important Samsung security features in the kernel. This, in turn, triggers the dreaded "Prenormal KG state". You can verify this from the Download Mode.
When KG state is triggered, it will prevent you from flashing any non-official binary (like the Magisk patched TAR in this case).
3) So, here's what I did to fix this. I force-booted the Tablet back into Download Mode and plugged it into the PC. Then:
And voila! It was rooted without any problems.
- Launched Odin and flashed the official stock FW.
- Rebooted into the OS and skipped the initial setup.
- Connected the tab to WiFi.
- Enabled Developer Options and verified that OEM unlocking was present and greyed out in the ON position.
- Rebooted back into Download Mode.
- Launched Odin again and unchecked "Auto Reboot" within the Options tab.
- Flashed the Patched AP TAR, along with BL and CSC (no CP because I have the WiFi variant)
- Manually turn it off, and boot it straight into stock recovery mode
- Performed a factory reset via the stock recovery and finally rebooted into the OS.
- After the tab booted, I went ahead and did the initial setup (connecting to WiFi, logging into Google and Samsung accounts, and so on).
- Went to the app drawer and launched Magisk. It prompted to install the full Magisk app. So did that.
- Then re-launched Magisk and did the additional setup as prompted. Upon finishing the tab finally rebooted by itself.
As you said, I think it would be a very good idea to mention not rebooting the tablet before the additional Magisk setup is finished. I will do that later today.
v3.14.4 does exist. But I later came to know that it includes a phishy tracking DLL, thanks @realbbb for pointing in his thread.
So, it's best to use 3.14.1. I will mention this in the post as well with the apt download link.
At last, thank you for your message. It means a total win for us as a community. Take care and enjoy your new Lenovo tab. Hope you find some exciting things to do with it as well.
i understand that my T510 is another device but T505 and my Tab have much soft identity and you wrote guide based on original from Magisk creator and i think your advices will be compatible/useful for T510. i will be grateful if you help and give a solution on that problem an some answers for difficult moments)As a summary, after installing Magisk in recovery (starting from power off):
- (Power up normally) → (System with NO Magisk)
- (Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
- (Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
- Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
- Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
- You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
- Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
- If you do land your tablet in trouble, feel free to ask, I shall try my best to help.
Updated on March 2, 2021
- Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
- Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
- Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.
Before you leave, there are a few key things you should note:
- Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
- Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.
Hello acinfo64,Thanks for the replay. But I constantly read here that I have to boot into OS but my problem: "That's not possible!". After flashing (stock or not it does not matter) it does first time boot that is:
- I get a white screen where I can only chose "lets go". I press it
- Next screen I can set my language and on only have the option "Next"
- Then I get a white screen where I can set my country. And the only option I have is REBOOT.
- Then it reboots and after the reboot it continuous with the setup as shown in the video below from position 2.09 on.
So I'm forced to reboot before the OS can be started. So forget the "boot into OS (that is boot to home screen)" because that's not possible without a reboot.