On this firmware, Root rights cannot be obtained, nor can TWRP be installed. We need a bootloader from Android 9, and it is 3 versions, rollback (downgrading) of the bootloader is prohibited ...
GrazieSu questo firmware non è possibile ottenere i diritti di root né installare TWRP. Abbiamo bisogno di un bootloader da Android 9, ed è 3 versioni, il rollback (downgrade) del bootloader è proibito ...
PS a proposito, c'è un aggiornamento al firmware come T295XXS 5 CWA1 con la versione 5 del bootloader...
What tutorial?Hi All, After several unsuccessful attempts to flash a new rom, I'm presently back to a rooted stock rom again. Tonight things went south when I tried to update the Magisk file that came as part of this tutorial. Are there any do's & don'ts associated with updating this app? eg what again the option regarding boot? I think I took it and all bombed out :-/
The tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.What tutorial?
I wouldn't update Magisk. Or the Android.
If you want to update, lots of people have success by letting the Magisk manager app perform the update. I have lost track of the different versions of Magisk, and which can update to which. Another approach would be to start over: Whatever you did originally, do it again, but use a newer Magisk manager app apk to do the patching. Nothing changes in Odin. It might not be necessary to do all the wiping and reformatting. If you want to try to preserve your data, make sure you use the CSC file that does not force a wipe. (I think it's HOME_CSC.tar that does *not* force a wipe, but you should really find at least one other source that says the same.)
You do not have the latest version of Magisk. You might have the same version I used four years ago.The tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.
But to be honest, I'm just beginning to conclude its more trouble than is worth trying to update to a newer rom. There is literally too much conflicting information to make sense of , and nobody so far has been able to give me a proven safe method to get me there.
I have Android 10 stock with root, root was my single biggest priority. If you say "I would update Magisk" then I probably just uninstall the app as its pointless being there.
My next priority is to try find out how to dump the stupid Samsung bootlock warning message as basically I need this SM-T295 to just quickly startup on sensing usb power ( is that called fastboot? )
Oh man, just download the latest version from here: https://github.com/topjohnwu/MagiskThe tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.
But to be honest, I'm just beginning to conclude its more trouble than is worth trying to update to a newer rom. There is literally too much conflicting information to make sense of , and nobody so far has been able to give me a proven safe method to get me there.
I have Android 10 stock with root, root was my single biggest priority. If you say "I would update Magisk" then I probably just uninstall the app as its pointless being there.
My next priority is to try find out how to dump the stupid Samsung bootlock warning message as basically I need this SM-T295 to just quickly startup on sensing usb power ( is that called fastboot? )
I'm a bit burned out getting root and then loosing it after trying to update things such as Magisk, then having to start all over again. So I'm just settling with a rooted stock rom as I can't get a dumbed down enough support that gives me confidence to.You do not have the latest version of Magisk. You might have the same version I used four years ago.
But I said "I would *not* update Magisk".
If that's what you meant to say just before you said "probably just uninstall the app as its pointless being there" -- that's a matter of taste: Magisk has other functions, the manager is of some use, but it's trivial to reinstall it when you think you want it. I don't think the app is involved in granting setuser privilege -- but it might be involved in clearing the flag if you inadvertently deny privilege to an app.
A lot of people hate the nag screen. I don't think anyone has been able to eliminate it. You do not have to respond to it, just wait and it goes away.
"fastboot" is a program like "adb" -- it runs on a PC and communicates with a device. It can only be used with a device that supports it. Samsung does not support fastboot -- that's why we have to use Odin.
So, I've found some steps:I'm a bit burned out getting root and then loosing it after trying to update things such as Magisk, then having to start all over again. So I'm just settling with a rooted stock rom as I can't get a dumbed down enough support that gives me confidence to.
Prime focus now is i) getting the device to start up on receiving usb power and ii) although I appreciate its just a warning that times out...I want to drop the Samsung bootlock warning as it just slows startup when the device gets mounted as a piggyback head unit in my Volvo.
I managed to get an old stock rom / non-root LG H850 to fire up on usb power, just need help to do the same for an SM-T295..
1. I have already got firmware as part of recovering from a failed GSI install. I'm on the samfw.com version T295XXU3BTI4 with the appropriate set of AP/BL/CP/CSC tar.md5 filesSo, I've found some steps:
1. Download the firmware for your SM-T295.
2. Download the 7-Zip version from here. NOT THE NORMAL VERSION, as that one has not support for .tar files...
3. Open the BL file from the firmware package using the newly, custom version of 7-Zip.
4. Extract the ``up_param.bin.lz4`` file from the BL file.
5. And then extract the new ``up_param.bin.lz4`` file.
6. And then extract the ``up_param.bin`` file from the new ``up_param.bin.lz4`` folder
7. Open the ``up_param.bin`` file and delete the ``boot_warning.jpg`` and ``svg_orange.jpg`` if they exist.
8. Then right click the ``up_param.bin`` file and select 'Add to archive' from 7-Zip menu.
9. Now create an archive from the file with the format ``tar``.
10. Flash the ``up_param.tar`` file with Odin as BL file.
Clicking the blue 'here' which will open the download link of the custom 7-Zip program. I think you need to download the '7z22.01-zstd-x64.exe' asset, because I think your computer is 64-bit (most modern computers are).1. I have already got firmware as part of recovering from a failed GSI install. I'm on the samfw.com version T295XXU3BTI4 with the appropriate set of AP/BL/CP/CSC tar.md5 files
2. ???? here we go again! Unclear to a newbie, just a link to a page littered with download links. Haven't got a clue where to go / what I should be downloading :-/
OK lets see where this one takes meClicking the blue 'here' which will open the download link of the custom 7-Zip program. I think you need to download the '7z22.01-zstd-x64.exe' asset, because I think your computer is 64-bit (most modern computers are).
Wait, I don't really understand your first part, but I do understand the second one. I guess you want the tablet to boot up when you start your car, and that is possible by editing the file at '/system/bin/playlpm':OK lets see where this one takes me
i) I thought as part of rooting, I replaced a stock tar.md5 file with a new one to get TWRP installed. There's no scenario here of me editing a stock file and then busting the device again due to what was modded for TWRP??
ii) only for info on the other task of auto booting on power/dock , I've found this to pursue, don't know what you to do with it but it shows it can be done : https://forum.xda-developers.com/t/q-power-on-when-plugged-in-boot-when-docked.1187631/
#!/system/bin/sh
/system/bin/reboot
OK lets see where this one takes me
i) I thought as part of rooting, I replaced a stock tar.md5 file with a new one to get TWRP installed. There's no scenario here of me editing a stock file and then busting the device again due to what was modded for TWRP??
ii) only for info on the other task of auto booting on power/dock , I've found this to pursue, don't know what you to do with it but it shows it can be done : https://forum.xda-developers.com/t/q-power-on-when-plugged-in-boot-when-docked.1187631/
Oh yeah, I had the exact same problem. Let me check a bit further to find a fix.Oh well, checked BL file via this new 7ZIP and no sign of a "up_param" file :-/
View attachment 5831071
Wait, I don't really understand your first part, but I do understand the second one. I guess you want the tablet to boot up when you start your car, and that is possible by editing the file at '/system/bin/playlpm':
As part of getting root, I had to add another 'BL' file per the tutorial. So there is a stock BL file and one associated with the root tutorial. But in any case I've looked at both with the 7zip you linked and neither shows an "up_param" file
What system do you use to manipulate the files? (Windows? Linux? Android?)
What is "overlay"? Do you extract the boot.img from the original AP.tar.md5, and from the magisk-patched.tar, copy the magisk-patched-boot.img to the beginning of the original-boot.img, and then replace the boot.img in magisk-patched.tar?
Do you give Odin four files, or just AP? Do you use CSC or HOME_CSC?
If you plan to use TWRP, then you need to disable encryption. To do this, install multidisabler and make format data-yes (no wipe data). Well, then install Magisk.zip for rooting.Many thanks for the recompiled BL file --upgrading done!
Next step will try twrp-3.5 + magisk --for rooting rights.
To root 10 android, you need to install the bootloader from the previous firmware 9 android, and then the rooting itself is the same - either patch the kernel and flash, or install TWRP and root the device from it ... The TWRP option is easier, but there is some difficulty in entering TWRP after it installation ...Better Android 9 or Android 10 to root? Which firmware is better and faster for this device (SM-T295)?
Are there any problems with knox for downgrade or root?
Ok, its been some time since i last played with my SM-T295 and now i am thinking of updating it. Just need @Talich52 , @gcrutchr , @J.Michael or anybody else to help me out so that i dont mess it up !
* First my current status:
Device: SM-T295
Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
CSC: INS
BL VersionL T295XXS3ATB2
CSC: T295ODM3ATC1
Android Version: P-9
* I have already downloaded the latest update (R-11) through Frija - T295XXU4CUF7/T295ODM4CUF8 (INS)
## Now, i know that i need to keep BL version at 3 for root rights. My questions are:
1) Can i replace the BL file (.tar) in R-11 firmware by simply unpacking and repacking the .RAR or it requires linux for .lz4?
2) From which specific firmware should i extract the BL Version 3 file to be used as replacement?
3) Is there any specific Odin version which works best for flashing or should i just use the latest v3.14.1?
3) From what i gather, patching files is no longer required to get root. But i think my preinstalled TWRP will be wiped during update through Odin so i should flash TWRP again ? Will reflashing TWRP also require formatting data again to read storage files?
4) Do i need to flash specific vendor_fix zip for R-11 or can i simply flash multidisabler-samsung-2.7_test zip ?