SM-T295 - Finally rooted tablet!! (updated 19-March-2021)

[Minionguyjpro]

I do have TWRP on the device. Though its pain to get to it with the nonsense bootlock warning message getting in the way lol.

Yeah, it is very stupid that the firmware is now signed and can't be edited..., but, if you need to flash an older bootloader which does allow the installation of TWRP and that things, doesn't it also allow modified firmware???

 

[Minionguyjpro]

I do have TWRP on the device. Though its pain to get to it with the nonsense bootlock warning message getting in the way lol.

By the way, does it really take that long to boot the device? My device has a lot of apps and games (SM-T290 model) and still boots very fast, although the apps are installed to an SD card (main reason for root, also use other interesting stuff)...

 

[ebod]

You could try to take a look at this:

How to remove carrier boot logo

Hello, What this post will be covering is in the title; I will be showing you how to remove the carrier boot logo off your samsung galaxy s21 ultra (This should work with pretty much any modern samsung phone) If you don't know how to flash a...

forum.xda-developers.com

Back to another topic I'm confused about. Magisk is sat on my rooted device and was added as part of the instructions I followed in this thread. Somebody else said DON'T update Magisk , others said do....

So see this pic : What do I do? update both listed apps? What about the options on recovery/boot ? preserve force encryption / preserve AVB 2.0/dm-vertity whatever that means

 

[J.Michael]

Back to another topic I'm confused about. Magisk is sat on my rooted device and was added as part of the instructions I followed in this thread. Somebody else said DON'T update Magisk , others said do....

So see this pic : What do I do? update both listed apps? What about the options on recovery/boot ? preserve force encryption / preserve AVB 2.0/dm-vertity whatever that means

Of course some people say update Magisk. There have been changes, some might be good for you. On the other hand, why bother? Why did you install Magisk?

I installed Magisk as the first way I found to get setuser privilege. Maybe the only way. That's all I want.

If you are not trying to use Magisk's other capabilities -- being able to "modify" /system, being able to install "modules" that do magic things -- why bother? Especially since you say you tried once and had problems.

(If you are really interested in updating Magisk, it might be that the version you started with is so old that the direct update through the manager just won't work. You might have an easier time if you uninstall Magisk, restore the original ROM, then install the latest version of Magisk.)

As for your struggles to do what you think should be simple things -- eliminate nag screen, boot when power applied -- I don't think it's a matter of your technical expertise. I think it just can't be done.

 

[ebod]

Of course some people say update Magisk. There have been changes, some might be good for you. On the other hand, why bother? Why did you install Magisk?

I installed Magisk as the first way I found to get setuser privilege. Maybe the only way. That's all I want.

If you are not trying to use Magisk's other capabilities -- being able to "modify" /system, being able to install "modules" that do magic things -- why bother? Especially since you say you tried once and had problems.

(If you are really interested in updating Magisk, it might be that the version you started with is so old that the direct update through the manager just won't work. You might have an easier time if you uninstall Magisk, restore the original ROM, then install the latest version of Magisk.)

As for your struggles to do what you think should be simple things -- eliminate nag screen, boot when power applied -- I don't think it's a matter of your technical expertise. I think it just can't be done.

On the Magisk issue, the only reason its on my tablet is purely because on page #1 of this thread on instruction #18 it said install the Magisk file attached on the header post. Thats literally how its there...not because I was doing anything clever, just following instruction. Totally happy to uninstall it providing I keep root ( can I keep root ..because the moment I trigger uninstall..the first warning I get is that Root will be removed.. ??? )

 

[ebod]

What exactly goes wrong at the installation of the auto boot part? Let's include a screenshot where possible, and some text???

This is the supplied instruction per your recommended thread about the param file, also what my PC session shows when I try. Just the word "soc" and a fresh prompt "gto: / $" whatever that means

Also ,the device is definitely listed when I type adb devices

 

[J.Michael]

On the Magisk issue, the only reason its on my tablet is purely because on page #1 of this thread on instruction #18 it said install the Magisk file attached on the header post. Thats literally how its there...not because I was doing anything clever, just following instruction. Totally happy to uninstall it providing I keep root ( can I keep root ..because the moment I trigger uninstall..the first warning I get is that Root will be removed.. ??? )

The point of this thread was to celebrate being able to get "root". Magisk was the means to obtaining root.

If you want root, do not uninstall Magisk -- keep Magisk.
If all you want is root, I do not think you will be missing anything if you use the old Magisk, so do not update Magisk.

Also, do not allow your tablet to update: It is bad news if a system update is run while the things changed while installing Magisk are changed. It is also possible (likely?) that an update will drag you kicking and screaming to a version of the bootloader that is not even as cooperative as the one that you have now.

 

[J.Michael]

This is the supplied instruction per your recommended thread about the param file, also what my PC session shows when I try. Just the word "soc" and a fresh prompt "gto: / $" whatever that means

Also ,the device is definitely listed when I type adb devices


View attachment 5832179View attachment 5832181

Add the "-l" option to "ls" to get more information:

ls -l /dev/block/platform

If the first letter of a line of output is a "d", the item is a directory. It might be useful to see what's in the directory:

ls -l /dev/block/platform/soc

 

[ebod]

The point of this thread was to celebrate being able to get "root". Magisk was the means to obtaining root.

If you want root, do not uninstall Magisk -- keep Magisk.
If all you want is root, I do not think you will be missing anything if you use the old Magisk, so do not update Magisk.

Also, do not allow your tablet to update: It is bad news if a system update is run while the things changed while installing Magisk are changed. It is also possible (likely?) that an update will drag you kicking and screaming to a version of the bootloader that is not even as cooperative as the one that you have now.

Thanks J.Michael , all above now makes perfect sense to me. Just on the stock rom side, mine is presently on an older "TI4" rom at Andriod 10 from Sept 2020. There are newer ones if I chose to upgrade and try go through the whole root process again, but I remember somebody posting at note saying don't allow bootloader version 4 or 5? otherwise root or bootloader access gets blocked? So going off the enclosed list there is a 'Security Patch level column displaying 3/4/5 values. So am I right to conclude DON'T upgrade beyond rom "UA6" ?

 

[Talich52]

There are newer ones if I chose to upgrade and try go through the whole root process again, but I remember somebody posting at note saying don't allow bootloader version 4 or 5? otherwise root or bootloader access gets blocked? So going off the enclosed list there is a 'Security Patch level column displaying 3/4/5 values. So am I right to conclude DON'T upgrade beyond rom "UA6" ?

Yes, do not update above UA6, because on T295XXU4CUD4 already version 4 of the bootloader cannot go back to 3. And besides, on the 4th and 5th bootloader, even if the bootloader is unlocked, you still cannot install any custom file such as a patched kernel for Root or custom TWRP recovery.

 

[J.Michael]

Thanks J.Michael , all above now makes perfect sense to me. Just on the stock rom side, mine is presently on an older "TI4" rom at Andriod 10 from Sept 2020. There are newer ones if I chose to upgrade and try go through the whole root process again, but I remember somebody posting at note saying don't allow bootloader version 4 or 5? otherwise root or bootloader access gets blocked? So going off the enclosed list there is a 'Security Patch level column displaying 3/4/5 values. So am I right to conclude DON'T upgrade beyond rom "UA6" ?
View attachment 5832407

I advise not updating at all. What new feature or so-called security patch is worth the risk?

I think you are right about which update is the most recent but still at rev. 3 for the bootloader.

There has been talk of using a rev. 3 bootloader file with the other three files from a later ROM when running Odin. Read the thread, it's in there somewhere.

I will leave it to someone like @Talich52 to tell you what, how, and how safe.

 

[Talich52]

There has been talk of using a rev. 3 bootloader file with the other three files from a later ROM when running Odin. Read the thread, it's in there somewhere.

I wrote about it somewhere in this or another topic. You can even upgrade to the latest firmware with bootloader 5, but first replace the aboot.mbn & vaultkeeper.mbn files from Android 9 in the BL part. Then it is possible to rewrite, install TWRP ...
Here is such a modified BL file,use it instead of the regular BL when updating via ODIN :

 

[Minionguyjpro]

I wrote about it somewhere in this or another topic. You can even upgrade to the latest firmware with bootloader 5, but first replace the aboot.mbn & vaultkeeper.mbn files from Android 9 in the BL part. Then it is possible to rewrite, install TWRP ...
Here is such a modified BL file,use it instead of the regular BL when updating via ODIN :

Okay, so I must flash every file as the update like normal, but flash that BL files instead of the other one? Will download it as soon as the update comes available in my country.

 

[Talich52]

Okay, so I must flash every file as the update like normal, but flash that BL files instead of the other one? Will download it as soon as the update comes available in my country.

Yes, yes. Upon the release of the full firmware T295XXS5CWA1 for your region, use the AP; CP; HOME_CSC files and the attached BL file from the firmware zip-archive. For rooting, if the bootloader was unlocked, it is enough to patch the boot.img & vbmeta.img files from the AP part and flash the tar archive with these files via ODIN. Or install TWRP and apply Magisk.zip ... It is possible to save data at the same time if you do not let the device boot before applying multidisabler and Magisk.zip from TWRP.

 

[ebod]

Yes, do not update above UA6, because on T295XXU4CUD4 already version 4 of the bootloader cannot go back to 3. And besides, on the 4th and 5th bootloader, even if the bootloader is unlocked, you still cannot install any custom file such as a patched kernel for Root or custom TWRP recovery.

OK just a quick check. Yesterday to was clear to me that in my image share, I should not attempt to install anything above UK image 'UA6' as that was highest image with Bootloader v#3 ? But there is now other replies saying its possible to get newer Android 11 stock roms ( in UK case 'WA1 ) providing the BL file is swapped out for a modded v3 BL version. Is that correct or am I totally misunderstanding what posts I've seen?

 

[ebod]

Add the "-l" option to "ls" to get more information:

ls -l /dev/block/platform

If the first letter of a line of output is a "d", the item is a directory. It might be useful to see what's in the directory:

ls -l /dev/block/platform/soc

All mumbo jumbo to me but hope this helps :

 

[Minionguyjpro]

I wrote about it somewhere in this or another topic. You can even upgrade to the latest firmware with bootloader 5, but first replace the aboot.mbn & vaultkeeper.mbn files from Android 9 in the BL part. Then it is possible to rewrite, install TWRP ...
Here is such a modified BL file,use it instead of the regular BL when updating via ODIN :

I've tried to change my CSC code using the SamFW FRP Tool without losing data, and it looks like it worked as my device lists 'XER' CSC instead of 'PHN' CSC at 'Software Provider' section. I think I will update tomorrow, also: my phone gives the error "The operating systemm on your device has been modified in an unauthorised way" when I try to search for updates.

 

[Talich52]

But there is now other replies saying its possible to get newer Android 11 stock roms ( in UK case 'WA1 ) providing the BL file is swapped out for a modded v3 BL version. Is that correct or am I totally misunderstanding what posts I've seen?

Yes, that's right. In the modified BL file, the aboot.mbn (bootloader) and vaultkeeper.mbn files are taken from android 9. You do the same replacement when rooting Android 10 ... But if the bootloader of version 4 or 5 is already installed, then the replacement cannot be made. I repeat - you cannot update the bootloader to version 4 or 5 ...

 

[Talich52]

I think I will update tomorrow, also: my phone gives the error "The operating systemm on your device has been modified in an unauthorised way" when I try to search for updates.

On the T290 model, the bootloader has been updated to version 4 and there is no rollback. Therefore, do not update the firmware over the air, only through ODIN with a preliminary modification of the BL file, or do not flash it at all so that version 3 remains.
Even with stock firmware, there will be an error when trying to update due to an unlocked bootloader.

 

[Minionguyjpro]

On the T290 model, the bootloader has been updated to version 4 and there is no rollback. Therefore, do not update the firmware over the air, only through ODIN with a preliminary modification of the BL file, or do not flash it at all so that version 3 remains.
Even with stock firmware, there will be an error when trying to update due to an unlocked bootloader.

Yes, I was not planning to update using OTA. I just wanted to test whether the new CSC could find the new update, so to know that it could work to update using Odin.