Related
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
a.brooding.mage said:
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
Click to expand...
Click to collapse
Now all we need is TWRP and we'll have Xposed and custom rom support
shahmir_k said:
Now all we need is TWRP and we'll have Xposed and custom rom support
Click to expand...
Click to collapse
For TWRP: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
I will get this tab.
BTW, can it install Samsung Game Tuner?
mingkee said:
I will get this tab.
BTW, can it install Samsung Game Tuner?
Click to expand...
Click to collapse
Yes... Game Tuner installs & wokrs good.
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Nerd10 said:
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Click to expand...
Click to collapse
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
shahmir_k said:
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
Click to expand...
Click to collapse
Thanks, where can I find the stock firmwares?
Here is another problem
Is OEM unlock in Developer Section required to install patched kernel and TWRP with Odin?
I can't find it even it's updated.
Does anybody know if this rooting method will work with T-585 on Android 7.0 (January 2018 update)? I guess KNOX will be triggered, right?
Yours
WeT-Klb
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
mingkee said:
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
Click to expand...
Click to collapse
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Delgoth said:
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Click to expand...
Click to collapse
I tried to flash modified kernel or TWRP with Odin and I got error
Only official software can be installed.
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Barsky said:
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Click to expand...
Click to collapse
I have that original boot.img and magisk modified one.
There's a 7 days waiting period after you turned it on the first time regardless reboot or not.
I will make a instruction how to root and I will post kernel and modified kernel.
mingkee said:
I have that original boot.img and magisk modified one.
Click to expand...
Click to collapse
I didn't realize it was so effortless to pull the boot.img out. BUt, until I have that oem unlock option in there, doesn't matter.
Come on, 14 days
Finally, mine has successfully rooted with Magisk.
I will post a guide.
Trouble rooting SM-t380
shahmir_k said:
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
When I try to flash the archived boot.tar via Odin it just hangs and sits there. Any help would be much appreciated. Thank You.
If there's anyone out there with some experience of rooting, and your reading and wanting to know if it's possible to update to the very latest Android 9 Pie on the Samsung Galaxy Active Tab2 (SM T395).
https://www.sammobile.com/samsung/g...are/SM-T395/BTU/download/T395XXU4CSF1/275287/
Well I can confirm it's possible as I have just done it. :good:
Make sure OEM unlock is on > developers page
Make sure USB debugging is on
Make sure FRP lock is off i.e no google accounts attached to device
Install Magisk apk on your device and patch the boot.img ( remove the boot.img from the boot.img.LZ4 file from the stock AP)
Software needed to remove the boot.img file from the LZ4 file - https://glamourrom.eu/how-to/extract-lz4-image/
Convert the patched boot.img into a recognisable MD5.tar file
Software needed to make MD5.tar file - http://www.droidthunder.com/convert-img-to-tar-md5/
Then reflash the patched boot.img using Odin on PC.
You DO NOT NEED TO RE COMPRESS TO LZ4 file !
Your device will show a verification reset page, all data on your device will be reformatted. :crying:
Nice quick and easy method for those of you who know what your doing
If you don't know what your doing, then don't try.
Happy rooting :good:
Hi tsam19,
Thank you for your guide.
With extracting the lz4 image, do you extract it to boot.img or boot.img.ext4?
When I try to reflash the patched boot.img it freezes on boot.img. any ideas?
I know Magisk can be flashed via TWRP, and that is the preferred way for me, usually. But on Magisk 19.3 I don't see an option to patch the boot.img without flashing the Magisk installer zip from TWRP. I just want to patch the img and flash it via Odin (I have a Samsung device, fastboot not available on those). I would like to keep the recovery as stock and system partition unmodified with dm-verity enabled. That way I can just use system less modules.
I normally prefer Phh's Superuser or SuperSU, I like old fashioned, traditional root without systemless or modules. But there are some tests I would like to run, and modules I would like to try.
Thanks!
It's right there if you press the install button and choose "Install"... If it it isn't on your setup you need to provide more information.
And both phh's and SuperSU are systemless root.
My setup:
Samsung Galaxy Note 4 N910F (international unbranded variant, latest stock Marshmallow firmware)
When I press install in Magisk Manager, it only offers the option to download a zip, no boot.img patching. I need the output file as tar or tar.md5, not img, so it can be flashed with Odin (no need for TWRP if flashed that way).
You're right, Phh is systemless, but it doesn't offer modules. SuperSU can be systemless or forced as system-installed.
So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.
Didgeridoohan said:
So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.
Click to expand...
Click to collapse
Hi, I am confused. I did use Manager 7.3.5 with Magisk 19 and now latest 20 .
When I use "select and patch a file". Use a stock boot.img file from my Tab 4 8.0 T330 Android v5.1.1 last version available. Whilst patched file is being created, a message flashes on screen img or tar file can be selected.
The problem is there is No option to "select img or tar file in output" as was the case in earlier versions of Manager v5 or 6. Which I previously used to create either patched img or tar files.
I have created different img files using the same original boot.img, only created using different Manager updates as they are created and released. Each time a new version creates a different file size.
Therefore you comment "tar file option is no more". WHY NOT.???
Next comment Just pick the file and let the Manager do the rest". Please explain or provide link to method you are referring to.
Another Question. Can I use an earlier img or tar file created on earlier Manager version with the latest Magisk version to install Magisk 20 on the Tablet. I have also used "img to tar to md5" convertor software and use ODIN to update the patched boot file, or install TWRP and use patched img file.
Any comments would be appreciated. Cheers
@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.
Didgeridoohan said:
@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.
Click to expand...
Click to collapse
Hi, Didgeridoohan, Thanks for your reply.
So I understand that if I use boot.img it will convert to patched.boot.img or patched.magisk.img.
If I use boot.tar it will convert to patched.boot.tar or patched.magisk.tar.
Question 1: So you are now saying I have to use another app to convert img to tar before patching or after patching.
Seems to me a backward function of your latest Manager, when previously you had a choice to select which option you received as the output file. So much extra time and effort to achieve the same result.
Question 2: This the case then I have to install latest manager and reinstall older version that worked. Create patched file as tar. Use ODIN to install patched boot file.
Do I need to rename magisk to boot, so ODIN will accept the patched tar file.
I use latest ODIN 13 on my Samsung Galaxy Tabs 4 & S4 and Phones S3, S4, & S8.
Question 3: Will older version created Tar file work with latest version Magisk to Root device, Then update both Magisk and Manager as normal when updates are released.
Or do I root using same version Magisk and Manager that created the patched boot file, then update to latest version.
I have successfully updated Stock and RR or Lineage OS Firmwares for years.
Samsung devices do not allow sideload installs and ODIN is so easy to use to install updates or new versions for all devices.
I also used other methods to root devices ie TWRP, Flashfire, but now Magisk is updated regularly, Hide Apps works on 7.1 thru 10, whereas old apps don't work past Android 4.4.
Thanks for your assistance, Cheers BJ.
@BeeJ1109 I know very little about Samsung so I can't really answer most of your questions, but wouldn't the file be a tar file to start with?
Anyway, if you wish for some functions to work differently than they currently do I would suggest opening a feature request issue in GitHub (with a detailed description of what you want).
Any solution?
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.
walty80 said:
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.
Click to expand...
Click to collapse
Hi.
Use Magisk Manager to create a modified stock boot.img. as you have mentioned.
What I do is search for Windoows PC "img to tar converter" app. on Google search.
Lots will be found. They a small executable batch file. Which you Right click on the "convert tar".exe file to run on a Windows PC.
Best one will have Input and Output directories. You can inset your patched boot .img file, you have just downloaded for your device. Add this file into Input directory of the app using Windows Explorer File Manager. May have to setup the location of resultant output directory. Then run Img to Tar converter . The application will convert your patched_boot img file into a patched_boot.tar file.
That newly modified .tar can now use ODIN. To install patched_boot.tar onto your connected device via PC USB port using the Latest version of ODIN 3.14.1.
Hope that helps. CHEERS
I have root on my SM-T295 A8 tablet!!
See my new post: How to Install TWRP and Root T295
Update 19 March 2021
Tested on T295XXU3BUC3 ROM
Prerequisites:
Bootloader unlocked - search forums.xda-developers for instructions how to do this.
OEM unlock on. In Settings/developer options, OEM Unlock slider should be to the right.
I see people still trying to patch files to get root.
If you flash the TWRP posted by @Talich52, with reboot unchecked you can install Magisk from TWRP.
1. If prerequisites met: install Android 9 bootloader through ODIN
2. Reboot to system
3. Go into download mode.
4. Open ODIN and in the AP slot put TWRP (see attachment below)
5. Uncheck auto reboot
6. Flash TWRP
7. Press vol dn + pwr keys.
8: When screen goes blank, press vol up + pwr keys.
9. Keep holding down both keys after reboot.
10. Tablet will reboot again.
11. When Samsung logo appears stop pressing pwr key.
12. When bootloader msg appears, release vol up key, quickly press & release pwr key, and quickly press vol up key until in TWRP.
13. You will then format (NOT WIPE) data. Answer yes to the format prompt
14. Clear dalvik/cache if prompted
15. Install Fix_vendor_9.0.zip or Fix_vendor_10.0.zip. See attached files.
16. Clear dalvik and cache.
17. Reboot back into recovery.
18. Install magisk - see attached
19. Reboot into system. May reboot again - that's okay
20. Enjoy!!
Updated (23 March 2020) my Tab A with XXS3ATB2 and got it rooted!!
Attached AP.tar file is for XXU2ASL3 only.
T295-Magisk-AP.tar
Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!
If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.
Basic instructions
PLEASE READ ALL OF THIS BEFORE STARTING!! VERY IMPORTANT!!
Here are the steps to root your tablet:
Make a backup of you apps & data before doing this. This procedure will
wipe all you data.
Go to settings.
Select software info
Tap build number 7 times to get into developer mode
Go back to main settings page.
Scroll to bottom and select developer mode
In middle of page find OEM unlocking
Make sure slider is all the way to the right (should say allow bootloader to be unlocked)
Unlock bootloader:
1. turn off tablet
2. press and hold down vol up & vol down keys together
3. insert usb cable (should already be connected to computer)
4. when bootloader screen appears, release all keys
5. press and hold vol up key for 5 seconds, then release
6. read instructions on screen to unlock bootloader (this will wipe all your data)
After reboot, go through normal setup.
Now for the hard part.
You need to download the complete ROM you have installed on your Tablet.
It will be better if you have the same ROM version as I do in post in this post (#1).
You need to unzip the ROM so you can flash it in ODIN.
If you are on the same ROM version as in my post #1, then you can just download my rooted files.
Unzip my downloaded root files zip file.
Unzip the downloaded ROM files.
In the AP* file, you need to replace my files in the zip: boot.img, recovery.img & vbmeta.img
Start ODIN. Select files for BL*, AP*, CSC* & CP*
For CSC file, select HOME_CSC*
*** Uncheck auto reboot ***
Flash ROM.
After flashing ROM. press vol dn + pwr key
As soon as screen goes blank press vol up key and hold
When get into recovery, select data wipe, then reboot
Set up phone as you normally would.
After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.
Do It Yourself Instructions
You need to do some research before doing this. This is NOT a walk you by the hand tutorial. You need to learn some things before following these instructions. Learn how to use lz4.exe. Learn how to use simg2img. Learn how to make a .tar file.
Make a backup of you apps & data before doing this. This procedure will
wipe all you data.
Go to settings.
Select software info
Tap build number 7 times to get into developer mode
Go back to main settings page.
Scroll to bottom and select developer mode
In middle of page find OEM unlocking
Make sure slider is all the way to the right (should say allow bootloader to be unlocked)
Unlock bootloader:
1. turn off tablet
2. press and hold down vol up & vol down keys together
3. insert usb cable (should already be connected to computer)
4. when bootloader screen appears, release all keys
5. press and hold vol up key for 5 seconds, then release
6. read instructions on screen to unlock bootloader (this will wipe all your data)
After reboot, go through normal setup.
Now for the hard part.
You need to download the complete ROM you have installed on your Tablet.
Extract ROM files
Extract system.*.lz4, recovery*.lz4 and vbmeta*.lz4
Use tar to make an AP.tar file with the 3 above files. **Search the Internet if you do not know how to use tar.
Copy the AP.tar file to your phone. It is better to use adb push to prevent file correuption.
Install Magisk Manager from Play store.
Run Magisk Manager. Select install Magisk. Choose Select and Patch a file. Follow directions on screen to patch the AP.tar file.
Once the AP.tar file has been patched, use adb to pul the file to yur computer.
Extract the file from the AP.tar file.
Now come the hard part:
You cannot edit .lz4 directly. You have to decompress them. After decompressing system*, use simg2img to decompress the sparse file. Search the Internet if you do not know how to do this.
Now we make our modified files so they will flash in ODIN.
Instructions:
I used hex editor neo - a windows 10 app
I opened the stock kernel & recovery files in hex editor neo
I opened the Magisk modified kernel & recovery files in hex editor neo
I copied the modified kernel & recovery code onto their respective stock files in hex editor neo
I saved the stock files & closed hex editor neo.
I used cygwin to create a tar file: boot.img, recovery.img, vbmeta.img plus other files in original AP*.MD5 file.
You should also flash all ROM *.MD5 files (BL, CP, CSC) per Magisk instructions.
New AP.tar contents:
boot.img
dtbo.img.lz4
meta-data
recovery.img
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img
vendor.img.ext4.lz4
I used Odin to flash the tar file
Flash ROM.
After flashing ROM. press vol dn + pwr key
As soon as screen goes blank press vol up key and hold
When get into recovery, select data wipe, then reboot
Set up phone as you normally would.
After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.
After installing Magisk:
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Please follow my instructions and the install instructions from Magisk web page.
Magisk Installation
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?
J.Michael said:
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?
Click to expand...
Click to collapse
In answer to your question, basically, yes.
I only flash the 3 files in the .tar file
I am on a Windows 10 laptop. Only 3 files need to be modified by Magisk: boot.img, recovery.img, vbmeta.img
I use Hex Editor Neo for overlaying the modified kernel and recovery files..
At the end of these 2 stock files is code that needs to be there, thus the 65 MB file size.
So I open the stock .img files (boot, recovery) in Hex Editor Neo, and copy the modded boot, recovery code into each stock .img file..
I use cygwin to create the .tar file, then flash with ODIN 3.1.14
Where does this leave you with respect to booting? Do you have to hold down buttons like you're trying to boot to recovery, then let go at the right time, to boot with Magisk active? Have you booted "normally" since you installed Magisk? Is Magisk still active? Have you shut down completely and then rebooted?
Wu's writeup says, when he's patching an AP file, to install to recovery, the boot.img is patched to "remove the signature of the image to prevent soft bricks". He doesn't explain why the signature would cause a soft brick with an unlocked bootloader and a nulled-out vbmeta. If you're restoring the original signature, it seems like you're flirting with the situation he was trying to avoid.
Will you be posting in the main Magisk thread. Aside from the news of another success, the details of your solution might help Wu improve the automatic patching enough to make manual adjustments unnecessary.
J.Michael said:
Where does this leave you with respect to booting? Do you have to hold down buttons like you're trying to boot to recovery, then let go at the right time, to boot with Magisk active? Have you booted "normally" since you installed Magisk? Is Magisk still active? Have you shut down completely and then rebooted?
Wu's writeup says, when he's patching an AP file, to install to recovery, the boot.img is patched to "remove the signature of the image to prevent soft bricks". He doesn't explain why the signature would cause a soft brick with an unlocked bootloader and a nulled-out vbmeta. If you're restoring the original signature, it seems like you're flirting with the situation he was trying to avoid.
Will you be posting in the main Magisk thread. Aside from the news of another success, the details of your solution might help Wu improve the automatic patching enough to make manual adjustments unnecessary.
Click to expand...
Click to collapse
No keypress is required for booting to maintain root.
I have tried this multiple ways: shutdown/boot & reboot - still have root.
I have not posted in main Magisk thread yet. Can you give me a link to the main thread where I can post this information?
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
This is the General Discussion thread. I've seen references to github for reporting bugs. github might be a better bet for providing technical information about how patching should be implemented.
J.Michael said:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
This is the General Discussion thread. I've seen references to github for reporting bugs. github might be a better bet for providing technical information about how patching should be implemented.
Click to expand...
Click to collapse
Thanks for the link. I have posted to the Magisk forum.
Well, besides the possible outcomes, I tried the method and it worked for me. I'm not loosing magisk between boots too, not touching system apps but I can install modules and get root.
So, thank you very much for the finding!
Gartrax said:
Well, besides the possible outcomes, I tried the method and it worked for me. I'm not loosing magisk between boots too, not touching system apps but I can install modules and get root.
So, thank you very much for the finding!
Click to expand...
Click to collapse
You're welcome. Enjoy your Tab A now that you have root.
gcrutchr said:
I have root on my SM-T295 A8 tablet!!
Attached boot.tar file is for XXU2ASL3 only.
T295-Magisk-AP.tar
Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!
If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.
Click to expand...
Click to collapse
You must have a unlocked bootloader to proceed. How did you overlay the files?
secretwolf98 said:
You must have a unlocked bootloader to proceed. How did you overlay the files?
Click to expand...
Click to collapse
Instructions moved to Post #1
In unlocking the bootloader, does it have any negative side? I remember on my sasung s5 before that i would loose what they call knox and not be able to restore permanently. How abiut in the 2019 tab?
amnher said:
In unlocking the bootloader, does it have any negative side? I remember on my sasung s5 before that i would loose what they call knox and not be able to restore permanently. How abiut in the 2019 tab?
Click to expand...
Click to collapse
Probably the same situation. I do not care about knox. I do not care about Samsun Pay.
I have not tested anything to restore knox.
gcrutchr said:
Probably the same situation. I do not care about knox. I do not care about Samsun Pay.
I have not tested anything to restore knox.
Click to expand...
Click to collapse
Attempting to restore Knox would be a waste of time because it is impossible. When you think of Knox, think of the manufacture warranty. Once you void the warranty, it's a goner.
secretwolf98 said:
Attempting to restore Knox would be a waste of time because it is impossible. When you think of Knox, think of the manufacture warranty. Once you void the warranty, it's a goner.
Click to expand...
Click to collapse
My understanding is knox is not installed on the T295
gcrutchr said:
My understanding is knox is not installed on the T295
Click to expand...
Click to collapse
According to the off site, the tablet has a Knox
Some user use the file from #1 and have this error(about security)
only official released binaries are allowed to be flashed after reboot
gcrutchr said:
My understanding is knox is not installed on the T295
Click to expand...
Click to collapse
The T29x and T51x has knox.
secretwolf98 said:
The T29x and T51x has knox.
Click to expand...
Click to collapse
Yea...just checked in priv-app folder.
I read somewhere the T29x series did not have knox...must have read wrong...ha, ha
And what we have?
How I can solve the problem with "Only official released binaries are allowed to be flashed"?
Alloc777 said:
And what we have?
How I can solve the problem with "Only official released binaries are allowed to be flashed"?
Click to expand...
Click to collapse
Did you unlock bootloader?
Did you toggle OEM unlock in settings/developer options?
hello there ..
plz hlp how i cat update software with keep rooted
Unroot and go back to stock.
If it's running well... leave it alone.
You'll have to root again probably.
So it's a waste of time to update it and lose the Root unless there is a major upgrade like Android 12.
As Samsung has NO full project treble there are no a/b partitions. So you can't update and keep root. You need to use ODIN to update and then root again which takes about 5 minutes. Just don't wipe your storage with Odin
If you have rooted with magisk it is easy.
Download latest firmware and extract it.
Copy file starts with AP_xxx to phone.
Open magisk and select install
Select option "Select and patch file"
Browse to AP_xxx file which you have copied to phone and patch it.
Locate file normally named as magisk_patched-xxxx.tar to PC again.
open odin and add files to their specific slot.
For AP slot used magisk patched file
For CSC there are two files, here you need to select which have HOME_CSC file not CSC.
If you flash only CSC this is wipe your device so Use HOME_CSC file.
Once flashing process complete, your device will reboot and Voila.
Enjoy upgraded firmware with root retained and without data wiped.
P.S. While coping file to or from device, use adb push or pull respectively as some user report corrupted file while coping it through MTP.
have you found a solution to root galaxy s21 5G us? 6 bit security?