yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Can you please tell me your EXACT steps? I may say what you need to correct.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
I do appreciate your help! But I already did in that post #61 an hour ago that you responded to 😅
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Try Pwr+VolUp+VolDown. Not Pwr+VolUp.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
Mentioned above somewhere that unfortunately it doesn't work.

Holding down all three I'll get a vibrate and then see the "Samsung Galaxy Tab A" normal boot screen. If I keep holding all three it'll just keep power cycling in somewhat random intervals (between 0-10 seconds). If I release only the power button it'll sit there for 20 seconds or so and then go to SAMSUNG screen and then boot as normal (sometimes in safe mode).
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
If not a single device is switched to unlock mode and replacing the cable does nothing, then I suggest checking it on another computer! By the way, on the current what OS?

PS I think I understood what the error is and it's in an incomplete instruction.So, Turn off the device, Wait 1 minute, press both volume buttons + and - , and while holding them pressed, connect the cable from the computer.We continue to hold both buttons and a blue screen will appear in a few seconds :)
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
{{extremely long string of expletives removed}}

Ok, so...

I had tried two different computers. I mean, c'mon, that's like the first thing when diagnosing problems right?

Both computers were coincidentally set up similarly. Older laptops, used for mucking around and all sorts of tablets and phones have passed through their hallowed USB halls. Various fastboot and manufacturer specific drivers have been installed.

@Talich52 before responding to you, I was thinking "ok fine, I'll try one more computer - my wife's - since I've never done anything messy on that one".

Booted up into the bootloader unlock screen first damned try. All 4 of the tablets that I've been playing with. There's not even a catch to it. Just press both buttons and plug in the USB cable. You don't even have to wait a minute or anything like that.

So - clearly - something to do with the drivers must intercept whateverthehell the tablet uses to "detect" a computer plugged in to kitckstart the unlock process...

So, in the end, thank you everyone for your suggestions and patience. I can't believe in the end it was this stupidly simple.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Nice! Did you manage to install ROOT with this guide?
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
So followed the guide to the letter. Got into TWRP first try. Directories were encrypted. Used SD Card, no problems. Installed Magisk and Multi Disabler. But on reboot, it gets to the screen with only the SAMSUNG text and just hangs. I just tried to reinstall the FW, will let you know.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I know whats the problem. You must disconnect your cable, and then turn it on yourself. Don't let the cable turn it on, because this is stuck on SAMSUNG logo.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
No dice. No matter what it seems to just hang on that screen. Who knows how much I messed up when trying the dozens of things before lol.

I'm going to try reflashing from scratch, will let you know!

I have a patched full AP file from Magisk that I'll try to load in the AP slot as well. Let's see.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
🥳 GREAT SUCCESS 🎉 ... kinda

Not sure what ultimately did it. Loaded the Magisk patched AP and all of the files except the BL. Boots fine now. Added Magisk APK and it rebooted and voila have root! What a fun journey.

I lost TWRP because I forgot to put the multidisablerer thingy back on. Walked through all the steps again to get TWRP 3.7 on, got into TWRP fine, loaded the multidisabler, reboot, and it's back to locking up at the SAMSUNG screen. No cables attached through the entire process. I'm trying on another device, going to do a FULL reinstall of the latest FW and walk through your steps again to see.

BTW if you want any test devices let me know. I have ... a lot ... of them and don't mind bricking a few if it helps the cause.

This one device feels really slow though. I accidentally loaded CSC_HOME into USERDATA slot once and after that it feels like this one crawls. I'll keep playing with it to see.

BTW what Font/Density do you use? I'm trying 0.8 and 180. It's not bad at this, can fit a lot on the screen.

I also have some SM-T307U's with Knox locked down. Now if I could only figure out how to root those 🤣
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Weird. Which screen hangs??? First or second? First= Samsung Galaxy Tab A logo

Second= SAMSUNG only logo

If it is the second, doesn't it work to wait little longer? I think you already tried.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
What you also can try: Go to TWRP > Wipe Data. Someone had the exact same problem and this was its solution.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
@Telek
[Samsung Galaxy Tab A series Guides, News, & Discus] TadashiRui:
I had a trouble shooting question. I followed the steps exactly and after everything with successful the tablet is stuck on the Samsung load screen any ideas
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Try to wipe data in TWRP. After that, boot into the system and wait 10-20 minutes. When it has been reset, samsung logo may take longer to go away.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Nice it worked well afterwards! Weird, actually I didn't need to wipe any partition and it still worked.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
I really appreciate all of the work that you put into this, so I wanted to help out any way that I could. Hopefully these details will help others who get into the same problem. Feel free to update your first post so that others know as well.

I still have a lot of virgin tablets left, so let me know if there is any other experimentation. I don't know who built TWRP but there may be some fixes needed there. Unfortunately I don't have time to try to fix it myself. I didn't even need a dozen tablets rooted but it's fun to try to figure this stuff out lol.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Ok, but auto reboot directly boots the tablet, and the user is not prepared to enter the twrp recovery?
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I fixed the storage issue by reparing and/or resizing the Internal Storage partition.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
So the user just needs to be paying attention. I mean flashing TWRP only takes a few seconds, so it's not like you're grabbing a coffee anyway 😅

Click to flash, and watch your tablet. As soon as you see it reboot, press the buttons.

FYI even if you leave auto reboot off, you don't need to do power+voldn to reset. You can just press and hold power+volup until it resets, that way you don't have to change the keys as it is rebooting.
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
Hmm ... Why come up with a new way to install TWRP and fix errors if there is a long-known way to do it?

So, flash the TWRP file and the patched vbmeta.img file, enter TWRP, install a multidisabler that disables encryption. And in order for TWRP to have access to memory, you need to do format data - yes (not wipe data!) And reboot into TWRP. Install Magisk.zip and boot into the system... That's it! :)
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
Because this device seems to be different. The main OS wants to overwrite the recovery partition and makes it very difficult to have non-standard stuff, despite allowing us to unlock the bootloader.

We were also hoping that you wouldn't need to format data again - why should that be necessary? It's not even touching the data partition, or it shouldn't be. If it's a problem, why doesn't the installer do it?
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
If you do not plan to use TWRP and only need Root rights, then with an unlocked bootloader, you need to do this:

1) patch the boot.img & vbmeta.img file

2) the received file is flashed via ODIN as part of the AP

We boot into the system, update the Magisk application or install Magisk.apk and use Root rights :) In this case, all current data will remain, the memory will be encrypted...

You can install TWRP using Root rights or through ODIN. But for TWRP access to memory, you need to disable encryption! For this, a multidisabler is installed so that the memory is not encrypted on reboots. And to decrypt the memory, it is made from TWRP format data with a set of the word yes. wipe data will not decrypt the memory, but only clear it, so we do format data ...

Regarding the features of the device:

1) there is no need to embed Magisk in the recovery section, as on new smartphone models ...

2) the bootloader can be unlocked, but with 10 and 11 androids there will still be a ban on installing a custom kernel or custom recovery ... Only with the android 9 bootloader, respectively, you can install TWRP and Root-rights. Fortunately, on Android 11 of the T290 model, the bootloader is version 3 and you can replace it with the bootloader of Android 9 of the same version 3 ...

4) with the android 9 bootloader, the device boots and works on android 10 and 11 and it's fantastic! However, the charging of the turned off device does not work, more precisely, there is no picture with percentages, the device freezes on loading ... At the same time, I absolutely do not understand the meaning of charging the turned off device;)
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Good that you say that, but flashing and patching the AP, it did make my device stop working. After a successful flash, the device boots up in a warning screen saying "SECURE_CHECK_FAIL: boot.img", or is this because I most not flash the BL?
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
My device didn't need to. It just worked by flashing TWRP, installing all ZIPs and done. Not needed to wipe and/or format data or unselect any box in ODIN. I just tried to use the steps how I flashed it.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
On the TWRP thread, I also saw a version of Multidisabler for Samsung devices that KEEPS encryption. This way you should also keep encryption. Here:
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Will add and update some things soon!
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I added and changed some stuff. Hope it will help others!
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
If the full firmware of Android 11 was installed, then the bootloader, even when unlocked, will not allow you to flash a custom kernel or recovery ... You need to change the bootloader to Android 9, but in fact there are only 2 files from BL, this is aboot.mbn & vaultkeeper.mbn, which I posted earlier and I'll add it again:
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I will keep TWRP. It has some good functions and features, so keeping it is better. (for me atleast).
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I will add some issues and maybe a certain way to report an issue. If one of you guys have an issue, feel free to report them.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I added an issue tracker repository on GitHub. Here can issues be reported.
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
Current data is lost though when you unlock the bootloader. So this is really only relevant or helpful in the (probably extremely rare) situation where you unlocked the bootloader, started using the device again for a while with the stock firmware, and then later decided to finally root your device.

Regardless do we know why installing TWRP breaks the data partition?
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
You just don't know how it works. If you install TWRP, then there will be no access to the memory, since the memory is encrypted. To disable encryption, use a multidisabler, and to decrypt the memory, you must execute format data with the word yes. Then reboot into TWRP for the changes to take effect and install Magisk.zip. .. You can not install TWRP, but only install the patched Magisk kernel and vbmeta. There will be Root rights and the same RootExplorer will work Without data loss ...

P.S. About unlocking the bootloader. You can unlock it and use the device for a long time, updating the current firmware and even changing the version of Android - the bootloader will remain unlocked ... The process of rooting with a patched boot.img does not require a data reset, which I emphasized above ... and TWRP is far from everyone needed, because there are still no custom ...
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
But what I meant is installing TWRP should only replace the recovery partition. Why should just installing TWRP modify the data partition at all, regardless of whether or not it is encrypted? I have not seen that on any other device that I have used TWRP on. Having access to the data partition doesn't matter, it only matters if you modify it.

Also my point about unlocking is how many people would unlock (which wipes), then use their device for a while without doing anything else? I would bet low single digit percentages. Almost always you unlock then do something immediately since you just wiped the device. It's going to be exceedingly rare to unlock, have it wiped, restart using it, then decide later to finally do something with the unlocked bootloader.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
True. Many people would unlock the bootloader and immediately flash something. The data partition should not be modified by flashing TWRP. The only ones which can modify the data partition are in this case Magisk and Multidisabler, as they do change some files. But, they only change the system partition, right???
[Samsung Galaxy Tab A series Guides, News, & Discus] Telek:
I need to double check, I could be wrong. Looking at my notes I might have always done TWRP + multidisabler because without doing multidisabler you lose TWRP, which would explain why the data partition is destroyed. Let me find another device and try it with only TWRP and all ODIN options unchecked. I'm pretty sure that I did try that, but the system will overwrite TWRP with the stock recovery on first boot.

If so, then this makes sense and is by design. TWRP itself isn't the problem, but if you want to keep TWRP we currently use multidisabler which not only prevents the stock recovery from replacing TWRP, but also removes decryption on the data partition which does require a reformat.
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
Yes, yes. If you flash TWRP and reboot the device, the stock recovery will be restored. Therefore, after uploading TWRP, you need to immediately enter it and apply multidisabler ... And what kind of breaking of the data section are we talking about? When formatting a partition, the memory is decrypted, but its size does not change ... Or are you using some crooked TWRP that breaks something?

Try the attached TWRP
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
That's the older version for Android 9 kernel. Version 3.7.0 exists for this device, which is for the latest kernel.
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
I have a model SM-T295, the combined firmware 11 of android is installed. The main part of the AP is from T295C for China, so the model is listed as T295C. The modem from the firmware for Korea is T295N, and the regional part of the firmware for Indonesia is the XID region, respectively, there is a regular recording of conversations. The bootloader is from Android 9, there are Root-rights ... And most importantly, the old TWRP version 3.5.2 is installed, which works great :)

Happy New Year!
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Ok, but I just use the latest version.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
There is no chance this device gets Android 12? My A12 just got it's second Android update with Android 13/OneUI 5.
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
@Talich52: Can you explain a little bit further ? The reason why I'm asking: New TWRP possible ?

Can't we have an TWRP just based on the A11 boatloader, means without rolling back aboot and vaultkeeper to A9 ?
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
I have written many times, I will say it again. Bootloaders 10 and 11 of android, even when unlocked, do not make it possible to flash (install) any custom files. TWRP or the patched kernel must be digitally signed by Samsung, which is impossible ... :(

P.S. What is the difficulty of replacing the bootloader, more precisely 2 files from 9 android? At the same time, the device works at 100%, except for charging in the off state ...
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
Hhhmm, there at least a dozen of Samsung devices out there shipped with bootloaders >= 10 ..

How did their TWRP maintainer solve the digital signation ? Maybe I'm wrong, but there should be a way to to that ... ;)
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
Nothing .. @Magendanz did that, but some devices just show a black screen :mad: with the 2 A9 BL files (as you can read the linked thread) ...
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
The problem is not in TWRP, but in the bootloader! Only the bootloader 9 of the android model T290 / T295, when unlocked, makes it possible to install a custom kernel and custom recovery (TWRP).
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
Yes, I am aware that the latest release of the T290 model has such a property. It didn’t happen before, what Samsung did there, I don’t know ...

P.S. It is useless to call Samsung to change something, since support for the T290/T295 model is over...
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
And who exactly testet that on T290 devices shipped with BL >=10 ?
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
The current topic is new and does not contain such messages. Read other topics on T290/T295

https://xdaforums.com/t/root-for-sm...4jNE5oFkZfukn6OGZyQQ-1666371132-0-gaNycGzNDVE
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Now I think of something, could you check if the device can be updated using the A/B partition? If it doesn't work, I could add that issue to the list and say that the device can only be updated over Samsung ODIN if that's the case.
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
After install TWRP I have black screen. I can see the screen using Mirror software on my PC!

What's the best option to get my display back on the tab?
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
We don't know yet. But we know the problem,

Some of these devices came with Android 10. And doesn't really like the one for Android 9...

This is were the issue occurs. It shouldn't iccur on device that came with Android 9.
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
Me and at least 7-8 other guys do have the same issue .. :cry:

What is interesting is that you can see the screen by using a 'mirror software' .. How do you manage that ?

And what do you see there exactly ?

Btw: You can get back your screen by flashing stock rom with Odin .. means you have to boot into download mode by holding VOL UP and VOL DOWN simultaniously while plugging the USB cable into your PC and then you have to push to VOL UP Button .. the device should be recognized by Odin and you can flash back the stock rom
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
I'm not sure which Android it was shipped with. It's about two years old. What about if I downgrade it to Android 9? I don't need 10/11 for what I intend to you use it for.
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
Using mirror software called "BotIt Project" It just works over adb. No need to install any apk. I was very surprised that it worked even though because of black screen on the Tablet! (I can upload link if you want it. It's difficult to find a working link online)

I was able to restore it with Stock rom so at least I have it back working.
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
A link would be great ... (y)

And what did you see on the 'mirrored' screen while the device scree was black ?

Edit: Sorry, I guess the above screenshot is the mirrored screen of your device, right ?
[Samsung Galaxy Tab A series Guides, News, & Discus] 2faraway2:
If it was shipped with >= A10 then I would suppose you'll get also the black/blank screen after flashing the A9 stock rom .. But since you know how to fix the black/blank screen (by installing the latest A11 stock) you can easily try that ;)
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
Sent you a Gdrive link. Yes, that was a screenshot from the Tab. You would think that the black screen on Tab would transfer onto the PC but it didn't. So maybe that info can be useful in someway to get Twrp working down the line.
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
Cool I will test some Roms later and let you know.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
So a fix would be to flash TWRP, then use mirroring to set ot up and check if magisk works, and then flash stock rom?
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Guys, is there really no way of flashing it on the Android 11 bootloader? It looks like only the vaultkeeper and vbmeta need to be patched. Can't these files just be extracted, modified a bit and then it works?
[Samsung Galaxy Tab A series Guides, News, & Discus] Talich52:
The problem is not in the vaultkeeper and vbmeta files. The vaultkeeper file can be taken from android 9, and the vbmeta file is patched by Magisk. This was done, but the problem remains, since the bootloader itself, and this aboot.mbn file from android 11 does not allow you to install any custom files.The aboot.mbn file is digitally signed by Samsung, which prevents it from being modified... :(
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
I've made some major changes to the XDA thread.
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
Guys, I am going to tweak the thread another time. Styling it a bit more, and also adding a few sections.
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
Bootloader Oem is missing. I have tried the date trick at least 50 times. Any other way to get it back?
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
How did it happen?
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
After the first attempt of installing Twrp. I had the black screen issue. Flashed stock ROM then to get back to normal. Now when I go into download mode it says OEM is on and OEM is missing in developer settings. Not greyed out. I did unlock the bootloader before I tried Twrp
[Samsung Galaxy Tab A series Guides, News, & Discus] Minionguyjpro:
You may have activated VaultKeeper, which flashes from TWRP back to stock recovery. I should try waiting for a week or so, or try to set the date to earlier or further forward.
[Samsung Galaxy Tab A series Guides, News, & Discus] chuckens:
Ok thanks I will try that out.
[Samsung Galaxy Tab A series Guides, News, & Discus] LedTV1:
Hi. any idea ti root this tabled? if after flash aboot i get black screen(