Installing updates via ODIN is more reliable than using OTA . And if the loader is unlocked, then the OTA software will not be updated at allYeah its on frijia also but no OTA yet
But yeah its better but I dont have always a working PC due to job here so an OTA will be helpfulInstalling updates via ODIN is more reliable than using OTA . And if the loader is unlocked, then the OTA software will not be updated at all
And the firmware,by the way,is the same as for the XEV Vietnam region.![]()
Friend would it be possible to do a more detailed tutorial on the root procedure, please? I was not able, after countless attempts, to resolve the error of vbmeta.img in odin, in version XXS3ATB2 and XXU3BTFE.I do both! that is, the patch is purely the boot.img file and the patch is the AP.tar file. I get the magisk_patched.img file and magisk_patched.tar file. From magisk_patched.tar, I only need the patched file vbmeta.img, which has a size of 256B. Next, the patched kernel magisk_patched.img needs to be applied to the boot.img stock kernel to have a full size of 64kB, otherwise the file will not be flashed by ODIN. I do this with the HxD program(HEX Editor 2.3) , although there are many options for this action ... The resulting 64kB file (the patched kernel) should be called boot.img. We pack it and the patched file vbmeta.img into a tar archive, I do it TotalCommander.
Select the tar file as part of the AP in ODIN and flash it ... After downloading, update or install MagiskManager.
Root rights received.
P.S. Before flashing, the bootloader must be unlocked ...
It is not necessary to patch the entire AP.tar file, TotalCommander can leave only the files boot.img; recovery.img; vbmeta.img.
TotalCommander can be extracted boot.img from AP.tar
The instruction is quite detailed and it means you are doing something wrong. What version of ODIN? You need version 3.13 or higher. I don’t flash the vbmeta file separately, I pack and flash it together with the patched kernel ... On the T295XXU3BTFE firmware, you will not flash either vbmeta or the patched kernel due to the T295XXU3BTFE bootloader, since the protection is reinforcedFriend would it be possible to do a more detailed tutorial on the root procedure, please? I was not able, after countless attempts, to resolve the error of vbmeta.img in odin, in version XXS3ATB2 and XXU3BTFE.
More important question - have you got a working TWRP for SM-T295 ?@ Talich52
Any idea why Twrp is saying It does not have permission to open /data?
Yes, twrp works. Can mount system and browse all files/folders. Can also format /dataMore important question - have you got a working TWRP for SM-T295 ?
Usually, TWRP cannot mount /data due to encryption not being supported.
Did you try the fix permissions option in TWRP after formatting /data?Yes, twrp works. Can mount system and browse all files/folders. Can also format /data
Actually, error msg is “cannot read /data”. You do not have permission
Please explain...modify twrp or run app or something else?Did you try the fix permissions option in TWRP after formatting /data?
In TWRP advanced options, there is a menu for fixing permissions. It usually fixes file permissions but you can try that. Please take a backup first since it is known to screwup /system boot sometimes !Please explain...modify twrp or run app or something else?
Don't give up when you get an error on the tablet. Go directly to recovery to wipe data. Then struggle to boot not quite to recovery to get Android with Magisk running. Install Magisk Manager and run it and see if it says it has more work to do.Friend would it be possible to do a more detailed tutorial on the root procedure, please? I was not able, after countless attempts, to resolve the error of vbmeta.img in odin, in version XXS3ATB2 and XXU3BTFE.
Thanks. Will try when I get home.In TWRP advanced options, there is a menu for fixing permissions. It usually fixes file permissions but you can try that. Please take a backup first since it is known to screwup /system boot sometimes !
To disable memory encryption, run format data-yes (not wipe data) and install a patch to disable memory encryption .Magisk does not do this on Tab A,it patches the kernel,and the encryption file in vendor/etc.@ Talich52
Any idea why Twrp is saying It does not have permission to open /data?
USB as in USB-OTG ? I am not sure but I remember a fix being applied for phones which lost OTG function due to constant flashing of different ROMs. Will try to search for it.Thanks. Will try when I get home.
What do you know about twrp usb not working?
Does the universal zip for disabling dm-verity and forceencrypt work on this device ?To disable memory encryption, run format data-yes (not wipe data) and install a patch to disable memory encryption .Magisk does not do this on Tab A,it patches the kernel,and the encryption file in vendor/etc.
I don't know,I haven't checked it. On Tab A 8.0 T385, I took as a basis a file from Tab S3 from the respected ashyx and adjusted it to fit the model....Does the universal zip for disabling dm-verity and forceencrypt work on this device ?
USB as in USB-OTG ? I am not sure but I remember a fix being applied for phones which lost OTG function due to constant flashing of different ROMs. Will try to search for it.
Also, kindly share the TWRP you are using if you believe it is stable enough. It would help in creating backup for restoring later if the access issue is sorted
Check the fstabs again. (How many are there in TWRP, stock recovery, stock boot?)USB as in connect computer to tablet.
Attached is the version of TWRP I am testing.
The only thing that works is mounting '/system'. You can use file manager to view all files in system.
Cannot access /data
Cannot access /sdcard
Cannot access /external_sd
Cannot back/restore without access to /sdcard or /external_sd
You can format /data
T295-TWRP.zip
Inside twrp.zip file is twrp.tar. Inside twrp.tar file is recovery.img.
Yes, I can format /data. Afterwards, I reboot system and setup phone starts.Check the fstabs again. (How many are there in TWRP, stock recovery, stock boot?)
My tablet has no "/external_sd". Is that a TWRPism, or a leftover from the original target of the TWRP?
Are you sure you can format /data?
Does this TWRP offer shell access? Can you mount manually?
h t t p s : / / appuals . com/how-to-diy-port-twrp-for-android/Yes, I can format /data. Afterwards, I reboot system and setup phone starts.
TWRP does, but cannot get she’ll in this TWRP yet. Still working on it.
Can not manually mount without shell.