- Jan 8, 2023
bro error 04 google drive
Hi there,Hi All, I have just bought a used SM-T295 which I want to use in an old car to hook up to its existing audio system , so that it can auto startup/shutdown etc.
Presently its stock android 10 and I would prefer to root it from the outset.
I here as a newbie and always fall at the first hurdle, more often because I see instructions on XDA only to learn that parameters/events have changed since a guideline was first written. For example on this tab, I've done the multiple tapping to get dev options, and already stuck as there seems to be no OEM unlock option.
So I would greatly appreciate advice on whether ...as of Feb24 are the instructions at the top of this thread still 100% valid to achieve root.
Secondly, if this tab is stock Android 10, ( rom T295XXU3BTI4 ) is there a standard go-to rom upgrade to make it 'better'. Nothing that makes it flakey...only want 100% stable rom upgrades.
Do not update the firmware to version 4 and 5 of the bootloader, otherwise you will not be able to root the device ...if this tab is stock Android 10, ( rom T295XXU3BTI4 ) is there a standard go-to rom upgrade to make it 'better'. Nothing that makes it flakey...only want 100% stable rom upgrades.
Thanks, I've tried the reverse date but unfortunately it wont work, I followed this guide but unsuceesfully https://itoolab.com/unlock-android/enable-oem-unlock-missing/Hi there,
I think you must wait for 7 days, because the device just got installed, and after that you will find the option in developer options. If you don't want to wait, you could try to set the date to earlier or further.
Right now I wish I even knew what was installed on the device. It was bought used off ebay but I've got no reason to believe its ever been modded before. How can I check what version I have? Would this mean doing one of them startups holding the vol+ & power button?Do not update the firmware to version 4 and 5 of the bootloader, otherwise you will not be able to root the device ...
Look at Android Settings -> About -> SoftwareRight now I wish I even knew what was installed on the device. It was bought used off ebay but I've got no reason to believe its ever been modded before. How can I check what version I have? Would this mean doing one of them startups holding the vol+ & power button?
The current version of the bootloader is 3. The letter B means 10 android, C - 11 android.stock Android 10, ( rom T295XXU3BTI4 )
OK thanks for clarifying. So it looks like I can commence root once I manage to get past the initial OEM unlocking hurdle, which could be another week lol. I just hope the instructions in the top post are still valid for use.The current version of the bootloader is 3. The letter B means 10 android, C - 11 android.
You could try the latest LineageOS GSI rom from here, if you want. I recommend you download the 'Treble Info' app from Google Play, and check there whether it is supported. Also look at the section which rom you are going to need for the device.OK next hurdle : I have definitely achieved OEM unlock / unlock bootloader., and started the next steps..
I have installed Odin"3B PatcheD/ModdeD v 3.14.1." and followed instruction step 1/2/3/4/5/6 i.e.
> the BL bootloader file ( presumably in box BL to be ticked )
> the AP TWRP 'tar' file via the AP slot.
But here I am now stuck , for a few reasons possibly
- During a re-boot I keep getting the new frequent annoying Samsung warning message about the fact the device has an unlocked bootloader which interferes things.
- I don't quite have the dexterity to follow the confusing sequence of button pressing
- I'm stuggling to visualise what view/image I should be seeing as all the button pressing is occurring...in other words....the words are in not enough, I need to visually see the sequential events.
Is anyone able to look at these instructions beyond step #5 and either find a YT vid link or illustrate with pics of what I should be seeing.
EG I've I now experienced four different boot screens.
1. The Blue screen achieved by pressing vol up + vol down then plugging in a USB feed
2. The boot screen achieved by pressing vol up + pwr. Is this 'recovery' ?
3. The screen displayed when via opting for 'reboot to bootloader' on previous screen. So is this 'bootloader' or 'download'
4. An options screen overlaid onto the unlocked bootloader warning, I stumbled upon this when trying to follow the complex sequence of button pressing and can't even recall how I got this.
... so when I read 'in download mode' and 'in TWRP' , as a greenhorn I need assistance to join the dots. What do these look like?
Beyond this , I see 'Install Fix_vendor_10.0.zip' and 'Install magisk'. Yes I've downloaded the files to my PC...but I need further explanation on what method/means I use to install.
These instructions are aimed at regular device modders, not occasional passers by. I've attached the images I've described and would greatly appreciate some assistance.
EDIT : I've stumbled further forward into accessing this TWRP thing and changed ment from Russian? to English.
I've installed the 'Fix Vendor 10" and cleared cache. Now I'm on step #15 which says "You will then format (NOT WIPE) data." OK so there are no options on this TWRP menu to format...only 'WIPE'. So what needs to be done to 'Format' per step #15 ??
EDIT 2: Regardless of the step #15 I carried on andTWRP installed the final 'Magisk' file and let it auto reboot.
So for better or for worse, it autobooted and when I checked via 'Rootchecker app...and...yey I gpt root!!
Mote screen pics added in case they help others down the line.
Next for me is finding the best 'go-to' rom to install
Thanks Minionguy, I've just looked on 'Treble Info' app and it tells me 'Generic System Image Found!' and confirms my device supports , image is "system-arm64-ab.img,xz".You could try the latest LineageOS GSI rom from here, if you want. I recommend you download the 'Treble Info' app from Google Play, and check there whether it is supported. Also look at the section which rom you are going to need for the device.
haha yep thanks. This Tab A is destined to be a car mounted unit in an old 2008 Volvo C70.@ebod The nag screen is an unfortunate fact of life with Samsung. In spite of it telling you to press the power button, you can just wait and it eventually goes away. I agree, it is an especial nuisance when struggling to boot to Magisk-in-recovery.
The screen that says "Android recovery" at the top is recovery.
The screen that says "download mode" at the bottom of 8 lines is download mode.
That funny overwriting menu is something I have triggered. I also cannot get it consistently. From the options, I assume it is a backup (secondary; fallback; reserve; emergency) recovery mode. I do not think it is any more capable than the normal recovery mode.
Bottom line: You got it to work. Mazel tov! Now stop poking it before you break something. And never let anything update.
Yes, I meant turn off every automatic update option you can turn off. And set the wi-fi (if any) to "metered" to discourage the ones you can't turn off.haha yep thanks. This Tab A is destined to be a car mounted unit in an old 2008 Volvo C70.
( to illustrate..see this YT vid)
I just knew that a rooted device makes a lot of the complexities of auto-start/auto-stop etc etc possible.
I'm also a newbie to the 'Tasker app' world, but that is key to making the device behave like a head unit and run seamlessly. So I'll hang around to see if a better custom rom is worth installing before I move forward to setting up Tasker on it. I want a fast autoboot on sensing usb power, so that 'nag screen' is a hindrance I'd prefer to do without..
opps finally one more thing .. When you say 'never let anything update' should I literally switch off the software update option' within settings>Software update? Anything else?
You could use any of those versions:Thanks Minionguy, I've just looked on 'Treble Info' app and it tells me 'Generic System Image Found!' and confirms my device supports , image is "system-arm64-ab.img,xz".
I see an option to browse images. Do I continue to action from this app...or via the link you gave ? My device is presently stock Android 10, what version can it reach with 'lastest LineageOS GSI" ?
It should be flashed as a zip in TWRP. I recommend you this one. It has Google apps, but not superuser. I recommend you install superuser later on via TWRP and then Magisk.OK Many thanks Minionguy, yes if its stable I will be happy to go lineage 20. I am UK based so please can you steer me to a suitable safe/stable file, and then what is the method to install (ODIN or via this TWRP boot screen)?? Forgive me whilst I have done this kind of thing before...it was many many years ago back on devices like Galaxy S3. Since then I have had LG/Huawei/OPPO and never had the need/desire to tinker with devices in 8<>10yrs
Right I'm on it , step 1 new rom via TWRP, step 2 will be SU ( link to appropriate file would be greatly appreciated ). Just regarding this 'mgkisk' file, I thought I already installed this as part of the root steps? or do you mean I need to 're-install' after the new rom is added?It should be flashed as a zip in TWRP. I recommend you this one. It has Google apps, but not superuser. I recommend you install superuser later on via TWRP and then Magisk.
You will need to reinstall root, will link the file later. I think that because you use a different rom, you do not need to worry about that.Right I'm on it , step 1 new rom via TWRP, step 2 will be SU ( link to appropriate file would be greatly appreciated ). Just regarding this 'mgkisk' file, I thought I already installed this as part of the root steps? or do you mean I need to 're-install' after the new rom is added?
Finally will this new lineage 20 rom stop any kind of Samsung auto-update which could wipe out all the mods? Or will I have to force / switch off any auto-update settings?
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:
Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
BL VersionL T295XXS3ATB2
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 ?