How To Guide [TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods
- Thread starter xbt-
- Start date
Got a Tutorial? I tried to downgrade from 13 to 11 and it gave me issuesI have downgraded from 12 multiple timesnever had an issue
I guess it won't work for me then as when I used the PatcheD Odin. It won't let me downgrade from 13 to 11 (probably due to the Security Level reference)
I believe that it was complaining about the Different Security Levels (From 5 to 3)
Damn so stuck on latest then
Any news about rooting that image? Can't get the phone to boot normally when AP or boot img is patched with magisk
Damn so stuck on latest then
Any news about rooting that image? Can't get the phone to boot normally when AP or boot img is patched with magisk
1.Don't try to up or down across your No.1,2,3 it's will brick your device.
2.About root , not sure , because I stop update with 1.
Edit- SOLVED, I was using the wrong Firmware, got the correct Firmware from samfw.com and it rooted without any issues.
----------------
Running into an issue Rooting with Odin, Failing on the Patched AP Step
a7 lite - android 13 - T220XXS3CWD1 - USA
OEM and Bootloader unlocked
Downloaded Firmware XAR-T220XXS3CWD1-20230411200511 for the boot.img
Using the latest Magisk from github to patch the boot.img
Used 7z to put the boot.img to boot.img.tar
When I try to use Odin3 v3.14.1 OR Odin3 v3.14.1_3B_PatcheD it produces the error I quoted above.
Anyone able to help or point me in the right direction. I've been working on troubleshooting this for several hours without any success.
edit- I understand the most obvious answer is magisk_patched-26100_fBShc.img aka my patched boot.img is incorrect but I don't believe it because I went through the process of creating the patched boot.img twice, step by step to make sure it worked.
I even saved the Magisk Log File.
The non-patched boot.img is Size: 26.9 MB (28,236,284 bytes) / size on disk: 26.9 MB (28,237,824 bytes)
----------------
Running into an issue Rooting with Odin, Failing on the Patched AP Step
a7 lite - android 13 - T220XXS3CWD1 - USA
OEM and Bootloader unlocked
Downloaded Firmware XAR-T220XXS3CWD1-20230411200511 for the boot.img
Using the latest Magisk from github to patch the boot.img
Used 7z to put the boot.img to boot.img.tar
When I try to use Odin3 v3.14.1 OR Odin3 v3.14.1_3B_PatcheD it produces the error I quoted above.
Anyone able to help or point me in the right direction. I've been working on troubleshooting this for several hours without any success.
edit- I understand the most obvious answer is magisk_patched-26100_fBShc.img aka my patched boot.img is incorrect but I don't believe it because I went through the process of creating the patched boot.img twice, step by step to make sure it worked.
I even saved the Magisk Log File.
The non-patched boot.img is Size: 26.9 MB (28,236,284 bytes) / size on disk: 26.9 MB (28,237,824 bytes)
Last edited:
***********WAS ABLE TO ROOT IT!!!**********
So I used the bitfrost app, download the 4 hoarseman, BL AP CSC and HOME,
did the little run around back and fourth with creating the boot.img.tar ill admit i only loaded the boot.img.tar into the ap and clicked start, thats when the vbmeta failed,
EDIT- tried i unplugged the tab leaving it on the download screen and reconected reset odin and plugged in the BL boot.img.tar the CSC and it failed in seconds, so flash pit going to try with the samfw file, im following the instructings and not updating my tablet btw. is that a problem maybe ?and it failed due to vbmeta? so im downloading the files from Samfw and trying to recreate i had to flash the pit and wipe the device as we speak for the second time to be able to access it.
EDIT-Just used the Samfw AP create the boot.tar from the magisk and plugged it in AP. CUSTOM Binary Blocked due to OEM Lock: boot
so i renamed it boot.img.tar unplugged tab, reset odin, put it in AP and ran and still failed.
I am clearly missing a step here guys???
with that said just checked my android is at 13 idk if that matters. i am however not finishing the setup like mentioned, and am able to unlock oem with the 10 day back trick and turn wifi off again.
This particular model seems to be a headache for me???
Im attaching the extracted boot, I have not patched with magisk yet freshly pulled with xarchive from the boot.img.lz4, if some one could make this ready for me with magisk and what ever need be for rooting and so i can just plug it in to the AP I would greatly appreciate that!!
So I used the bitfrost app, download the 4 hoarseman, BL AP CSC and HOME,
did the little run around back and fourth with creating the boot.img.tar ill admit i only loaded the boot.img.tar into the ap and clicked start, thats when the vbmeta failed,
EDIT- tried i unplugged the tab leaving it on the download screen and reconected reset odin and plugged in the BL boot.img.tar the CSC and it failed in seconds, so flash pit going to try with the samfw file, im following the instructings and not updating my tablet btw. is that a problem maybe ?and it failed due to vbmeta? so im downloading the files from Samfw and trying to recreate i had to flash the pit and wipe the device as we speak for the second time to be able to access it.
EDIT-Just used the Samfw AP create the boot.tar from the magisk and plugged it in AP. CUSTOM Binary Blocked due to OEM Lock: boot
so i renamed it boot.img.tar unplugged tab, reset odin, put it in AP and ran and still failed.
I am clearly missing a step here guys???
with that said just checked my android is at 13 idk if that matters. i am however not finishing the setup like mentioned, and am able to unlock oem with the 10 day back trick and turn wifi off again.
This particular model seems to be a headache for me???
Im attaching the extracted boot, I have not patched with magisk yet freshly pulled with xarchive from the boot.img.lz4, if some one could make this ready for me with magisk and what ever need be for rooting and so i can just plug it in to the AP I would greatly appreciate that!!
Last edited:
OK guys, giving back: I successfully patched (thru Magisk) the AP files of the current (newest) stock for Tab A7 Lite.
Flashed on my Tab and confirmed root.I hope someone else might enjoy.
The attached archive (as per ususal) contains only the two files that are patched. Replace in the AP_T220XXS1BVJ2_CL24599155_QB58664678_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS12.tar.md5 archive you may obtain safely through Bitfrost the way I did.
Use the BL and CSC tar's as you get them through the Bitfrost download.
(There is no CP (Cell Processor) file for WiFi tablet).
Enjoy!
Last edited:
I was able to correct.
XAR-T220XXS3CWD1
Open AP
Extract Boot.img from Boot.lz4
Patch Boot.img with magisk
transfer MagiskPatched to PC
Rename boot.img
Use 7zip to add it to archive and make it tar
Which now turns it from boot.img
To boot.tar
Rename boot.tar
To
Boot.img.tar
Open ODIN as administrator
Plug the boot.img.tar into AP and flash.
I'm usually met with:
CUSTOM Binary Blocked due to OEM Lock: boot
Or sometimes it vbmeta.
Turned out that even though I had got the OEM checked and unlocked whenever I woukd boot into download mode it didn't supply the option to unlock the bootloader until I booted into safe mode unchecked and rechecked the OEM unlock and restarted. Then then feature was available to unlock.
Download Firmware:
XAR-T220XXS3CWD1
Open AP
Extract Boot.img from Boot.lz4
Patch Boot.img with magisk
transfer MagiskPatched to PC
Rename boot.img
Use 7zip to add it to archive and make it tar
Which now turns it from boot.img
To boot.tar
Rename boot.tar
To
Boot.img.tar
Open ODIN as administrator
Plug the boot.img.tar into AP and flash.
I'm usually met with:
CUSTOM Binary Blocked due to OEM Lock: boot
Or sometimes it vbmeta.
Turned out that even though I had got the OEM checked and unlocked whenever I woukd boot into download mode it didn't supply the option to unlock the bootloader until I booted into safe mode unchecked and rechecked the OEM unlock and restarted. Then then feature was available to unlock.
Last edited:
I was able to fix this issue as well.
I seems that the message sent in termux to disable to message for the boot loader somehow was blocking my BL.
Little Worried, everything worked great! however when i got to the termux step, idk what happened but after i rebooted expecting to see the message no longer there, when it boots up its a black screen and highlighte at the top is this: Set Warranty Bit : boot
Ive already tried repair apps, boots straight to that, wiped cache and factory reset, boots to this, i flashed the patched boot tar again, boot up to that, even flashed a pit file, any ideas?
I seems that the message sent in termux to disable to message for the boot loader somehow was blocking my BL.
Little Worried, everything worked great! however when i got to the termux step, idk what happened but after i rebooted expecting to see the message no longer there, when it boots up its a black screen and highlighte at the top is this: Set Warranty Bit : boot
Ive already tried repair apps, boots straight to that, wiped cache and factory reset, boots to this, i flashed the patched boot tar again, boot up to that, even flashed a pit file, any ideas?
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from @nevertechdose. Parts II & III are mostly copied from @thatha's guide. Part V is mostly @razs.originals guide. Parts IV, VI, VII, VIII, IX, X, XI, etc are my guides.
Special thanks to @thatha for their guide & T225 files, @Talich52 for their post & T220 file, @realbbb for their post & odin files, & @nevertechdose for their OEM Unlock guide. Also to @razs.originals for their bootloader warning removal guide.
I. Get OEM Unlock to show up (If it doesn't show already. If it shows, skip to Part II.)
- Factory Reset Device (Sorry but this will happen when you unlock & root anyway, and has to be done first.)
- Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later). (You can still during setup decline to provide sensitive info - just select the first two bubbles and accept - and you can also still turn off the three privacy sharing buttons.)
- I did not change any settings when I booted in, just proceeded to step 4.
- Enable developer options and disable automatic system updates from there.
- Disable automatic software update. Settings > Software Update > turn off.
- Connect to a WiFi network.
- DISCONNECT from internet after a few seconds. You'll see it trying to update things in the pull down menu, disconnect from internet, you don't want it to update anything. It just needs to be connected long enough to update the day and time to the correct day and time, and register your device. If it didn't work, it didn't register your device yet.
- For me, it did get to the point where there was a notification that said, "Finish setting up your Tab A7 Lite." DO NOT finish setting anything up, but do make sure internet is disconnected. Ignore notification, but you should see that.
- Go to General > Date and Time settings and select for the time to be set manually (don't touch time zone). Set the date to be EXACTLY 10 days BEHIND from your current date.
- Go to Developer Options, and OEM Unlock should be there!
If it still doesn't work, you may have to go to extreme measures, but I didn't have to. But first just make sure you did the above steps EXACTLY.
Go here for extreme measures if you did EXACTLY like above and still didn't work (my instructions above were a bit different) https://forum.xda-developers.com/t/a7-2017-w-binary-9-rmm-state-unlock.4057831/post-82049513
II. Unlock bootloader (Thanks @thatha)
- Enable developer options by going to Settings > About Tablet > Software information > and tap "build number" 7 times
- Go to Developer options, turn on OEM Unlock (If it doesn't show up, skip to Part III and then come
- Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
- Long-press Volume Up key to enter Device Unlock mode
- Press Volume Up key to confirm and unlock the bootloader
III. Create your device's patched boot (You can skip this if you have one of the 3 devices with the files in part IV.1 below.)
- Download your firmware from samfirm or other source (I didn't have to do this, so I can't instruct on it)
- (On PC) Extract
boot.img.lz4fromStock AP...tarfile, then copy it to Tab - (On Tab) Install ZArchiver to extract
boot.imgfromboot.img.lz4 - (On Tab) Install Magisk and patch the
boot.imgthat you have just extracted from step 3 - (On PC) Copy
magisk_patched.img(inTab\download) to pc, rename it toboot.img - (On PC) Use 7zip to pack
boot.imgfrom step 5 intoboot.img.tar
IV. Root Tab A7 Lite
- Download correct boot.img.tar for your device (For
T220XXU1AUJ1it'smagisk_patched-23000_acKsR.tar), it will probably be a zip, if so you'll need to unpack it to a tar (you can use 7zip for that). The two T225 files were pulled from here. The T220 file (my device) was pulled from here. I inserted and attached them for future proofing and to make it easier for you.
You can find your device under Settings > About Tablet > Software information > Build Number. Mine is a Wifi model Tab A7 Lite, model T220 4GB/64GB, my build is T220XXU1AUJ1.
The files below are direct links to the attachments in this thread (take CAREFUL note of the T220 or T225 in the name - they are different).
For T220XXU1AUJ1:
For T225XXU1AUJ1:
For T225XXU1AUL1:
For T220XXU1AUL2:
If you don't have one of the above 3 devices, then follow the Part III guide above to create the correct boot.img.tar file. DON'T FLASH THE ABOVE IF IT IS NOT YOUR DEVICE!
- Get Odin 3.14.1. (All 3.14.4 are FAKE!) The exact one I used was Odin3 v3.14.1_3B_PatcheD. Get it from here ONLY! https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I also attached the same file to this post. Download from the other page if you don't trust me.
- Boot into Download Mode
(If you're stuck at SetupConnection in Odin, it's because you have to run it from Download Mode, it won't run while device is on.)
- Power off device
- Hold Volume Up & Volume Down buttons at the same time, connect USB cable, keep holding until you see the screen.
- Press Volume Up to go to Download Mode
Here's a video for this device on how to do it and what it looks like (credit goes to the maker of the video, not me):
- Open Odin as Administrator (Right-click > Run as Administrator)
- Click AP and find the file magisk_patched-23000_acKsR.tar (for T220XXU1AUJ1). NOT THE ZIP. And not the raw boot file(s). Has to be the tar.
If successful, it wlil say this:- <ID:0/008> Added!!
- <ID:0/008> Odin engine v(ID:3.1401)..
- <ID:0/008> File analysis..
- <ID:0/008> Total Binary size: 32 M
- <ID:0/008> SetupConnection..
- <ID:0/008> Initialzation..
- <ID:0/008> Get PIT for mapping..
- <ID:0/008> Firmware update start..
- <ID:0/008> NAND Write Start!!
- <ID:0/008> SingleDownload.
- <ID:0/008> vbmeta.img
- <ID:0/008> boot.img
- <ID:0/008> RQT_CLOSE !!
- <ID:0/008> RES OK !!
- <ID:0/008> Removed!!
- <ID:0/008> Remain Port .... 0
- <OSM> All threads completed. (succeed 1 / failed 0)
- Device will reboot. It will say bootloader unlocked continue, so press Power button like it asks. You will see a screen with red text warning you it's been altered.
- It will not boot. Don't worry it will reboot again, same thing as step 6. Now it fails and asks you to Factory Data Reset. Ignore the errors it's telling you, and Yes, go ahead and click Factory Data Reset (you have to).
- It will go through step 6 again, this time, after a few minutes it will boot up into Android and prompt you to setup device. Success!
V. Remove Bootloader Warning ⚠ (thanks to @razs.originals for their guide & file)
@razs.originals provided a guide and the needed file, but their guide was slightly lacking for those less experienced, so I'll expand it slightly to be more precise what to do. This removes all the bootloader unlock warnings on boot.
- Get the free app Termux.
- Download the up_param.tar file and move it to download folder (internal storage) - it might be the default location, if not then it should be here:
/storage/emulated/0/Download/up_param.tar - Open Termux, and then type the next series of lines of code (press enter in between each line):
su
cd /
Code:dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param - Now reboot, and the bootloader warning screens should be gone!
VI. Install/Update Magisk on Tab A7 Lite
Magisk will exist in apps, but clicking on it asked me to update but nothing happened. If that's the case for you too, then:
- Download Magisk latest version from their official Github. (DO NOT DOWNLOAD FROM ANY OTHER SOURCES!) I included the apk from the github page here for future proofing and reference, I am using Magisk 24.1 which worked.
- Install the APK. Open file manager if you need to and then find it in Downloads or wherever you downloaded it.
- Open Magisk, it will ask you to update. Choose "Direct Install (Recommended)" and then click Let's Go in the top right.
- It will flash the image and then say All Done!, then you can click the Reboot button in the bottom right.
- You can now check root by installing any app that needs root, for example Titanium Backup which is an essential one for me. There's also OandBackupX, which is a free and open source fork of Titanium backup.
- You will be greeted with a Superuser popup if you are rooted, so grant permissions and you can see you are rooted! Congratulations!
- Nothing special is needed on reboot, if you ever reboot your device, it just reboots as normal and stays rooted. Congratulations on completing the guide! Please remember to like this if you liked the guide (only if you liked it), so I know I am helping.
VII: Install LSPosed (Successor to Xposed) on Tab A7 Lite
- Download LSPosed latest version from the official Github.
- Make sure to choose the Zygisk version (e.g lsposed-vx.x.x-xxxx-zygisk-release.zip).
- Why Zygisk? Because Riru is retired. You don't need it anymore.
- Don't worry about downloading any Zygisk or Riru. Riru is retired and Zygisk is now integrated in Magisk. - Copy the zip file to your device.
- Open Magisk, go to Modules, click Install from Storage, and find the zip you just copied for lsposed zygisk version.
- Click Reboot button in the bottom right when it's finished.
VIII: Activate Zygisk (Successor to Riru) on Tab A7 Lite
- You're not done yet. Now go into Magisk, click Settings button in the top right.
- Scroll down and enable Zygisk (Beta).
- Below that, enable Enforce DenyList.
- Below that, click Configure DenyList.
- In the top right, click the 3 dots menu and check the box Show System Apps.
- Select Google Play Services by checking the box.
- Tap on Google Play Services to open all the items for it, and enable all the items for Google Play Service.
- For anything else you deny in the DenyList that you configure, Zygisk will not work for it, because you denied it. So in the future if you want to disable Zygisk for anything else, this is how. But if you don't konw what this means, don't worry about it.
- That's it! Now go ahead and reboot your device by holding the Power button for a couple seconds and clicking Reboot (If you choose Power Off by accident then it won't reboot without you turning it back on )
- On reboot, it will ask if you want to add a home page shortcut. Choose YES, because it won't show in your apps, so you want an easy way to access LSPosed.
- Open Magisk and click on Modules to see that LSPosed is active! Congratulations you now have LSPosed installed and working!
IX: Xposed Modules for LSPosed
I recommend a couple mods for LSPosed. There aren't a ton yet for Android 11 and less for Android 12.
- Browse the Xposed Repository, because you apparently can't from within LSPosed.
- Note - Don't use any modules you don't know what they do. - Recommended Module: GravityBox [R] (For Android 11) - Allows you to do lots of customizations. (Enable dark theme for GravityBox under the About at the bottom, after you activate it using steps 5 and 6.)
- Recommended Module: DarkTricks (For Android 11) - More customizations and tricks. Nothing "dark" about it, just the user's name.
- Recommended Module: FireFds Kit [R] (For Android 11) - Activate Advanced Power Menu, Disable restart confirmation, Date in Status Bar, etc.
- Recommended Module: App Settings Reborn (For Android 11)
- Allows you to set custom DPI per-app. I used it to put Swype into tablet mode using these settings: DP: 175, Screen (dp): 1080x1920) - To install, just copy to your device, and browse to the apk through file manager, and install it.
- When you install, you will get a notification, "Module is installed but not activated". Either click on the notification and Enable, or open LSPosed, go to Modules, click on the greyed-out modules, and click Enable on each module you want to activate.
- Then reboot to activate the module. If you don't reboot, then the module isn't going to work when you click on it, but it will after you restart.
X: Install Shamiko (Magisk Hide Alternative) & Momo [Both In Development ALPHA (Pre-Beta)]
Magisk Hide was permanently removed from the latest versions of Magisk. The alternative is Shamiko, although it's still in development. Install at your own risk.
Momo simply checks your environment for your knowledge. It can help detect if you successfully hid Magisk.
- Shamiko Development Version: https://t.me/magiskalpha/438
- Momo Development Version: https://t.me/magiskalpha/379
- Install Shamiko using Magisk like you did in Part VI: Go to Modules, Install from Storage, Find the Shamiko .zip file, Install, Reboot.
- Install the Momo APK. You can open it right away.
More details on Shamiko & Momo: https://xiaomiui.net/a-new-method-for-hiding-root-is-on-the-way-2720/
XI: Tweaks
- Disable tablet mode in apps universally:
- Go to:
Settings > Developer Options > Drawing > Minimum width - Set to 598 (Default 600)
- Go to:
- This will disable the annoying tablet mode, browsers and other apps look weird. Yandex had search bar at top, no extension support, and no dark theme. This hack brought everything back.- Will not affect size or resolution at all. It will just trick apps into displaying in normal phone mode.- You can also disable on a per-app basis using xposed module in the above section.- Turn off animations (Optional):
- Go to:
Settings > Developer Options > Drawing >- Window animation scale: 0.5
- Transform animation scale: 0.5
- Animator duration scale: None
- Go to:
I will add more later if I find anything else major, and also if a working TWRP is released and I find it, I will post it in a new section here.2
Don't worry found it it's because its in Urkraine
Download Galaxy Tab A7 Lite SM-T220 (SEK) T220XXU1AUL2 in Samfw - Samsung firmware download
Galaxy Tab A7 Lite SM-T220 (SEK - Ukraine)...samfw.com
2
