How To Guide [TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods

Search This thread

tom.android

Senior Member
Jul 12, 2016
1,081
347
If this helps, here is how the device behaves ever since I installed the magisk patched boot.img through Download Mode/Odin as instructed by the OP: https://photos.app.goo.gl/ytELZzhw5ymhyGTc9

And this is how Odin looked when doing it:

View attachment 5738715
Download mode is your tab screen when you connected with odin.

IMG_20220924_210501.jpg

check your KG status ???
 
Last edited:

HackxBox

Member
Feb 25, 2012
14
1
London
Download mode is your tab screen when you connected with odin.

View attachment 5738823
I don't see a way to enter download mode again, as I said in my original comment and evident from the video the device boot-loops and does not seem to respond to any button presses - holding power does not turn it off, and holding vol up/down while plugging in the cable does nothing. My only hope is to be able to do that when the boot-loop drains the battery and it switches off.
 
Last edited:

tom.android

Senior Member
Jul 12, 2016
1,081
347
I don't see a way to enter download mode again, as I said in my original comment and evident from the video the device boot-loops and does not seem to respond to any button presses - holing power does not turn it off, and holding vol up/down while plugging in the cable does nothing. My only hope is to be able to do that when the boot-loop drains the battery and it switches off.
Did not heard sound from computer when connected with usb cable ?

then press power + v down = restart and when screen off , press both vol up + vol fown + insert usb cable imediatly
 

HackxBox

Member
Feb 25, 2012
14
1
London
Did not heard sound from computer when connected with usb cable ?

then press power + v down = restart and when screen off , press both vol up + vol fown + insert usb cable imediatly
No indication on the computer and whatever I do it seems the device does not respond to any button press or combo. I think it's totally bricked. My only hope now is to try to enter download mode when the device drains it's battery.
 

tom.android

Senior Member
Jul 12, 2016
1,081
347
No indication on the computer and whatever I do it seems the device does not respond to any button press or combo. I think it's totally bricked. My only hope now is to try to enter download mode when the device drains it's battery.
sorry to heard that, most flashing with Home_CSC will effected like this.
 

HackxBox

Member
Feb 25, 2012
14
1
London
sorry to heard that, most flashing with Home_CSC will effected like this.
Okay, so there is a development - by some miracle and still not sure how, but I manage to reproduce it by randomly pressing Power and Vol up while it's showing the Bootloader unlocked message, I managed to get into Android Recovery!

20221020_140834.jpg


However, things don't look good:
- Reboot to bootloader just shows in red "Entering fastboot mode..." and that's it.
- Apply update from ADB throws some locale errors and adb devices in cmd comes up empty, and after holding power I get a robot with exclamation mark in it
- Wipe Data/Factory Reset and Wipe Cache seem to work but did not change the situation at all - tablet still boot-loops and no evident way to enter Download Mode
- Mount /system throws "Failed to open '/dev/block/dm-0' : No such file or directory"
- View Recovery logs shows some logs and I can read them but there is no option to do anything with them
- Run graphics test show the robot with a spinner and a percentage bar which turns into a robot with a warning and returns to Recovery menu
- Run locale test throws "Failed to load locales from the resource files"
- Power Off works, which gave me a bit of hope, only to realise even from off state holding Vol Up/Down and plugging in the cable does nothing, just like it did nothing before
- Repair Apps immediately restarts the device back to boot-loop state

I also noticed while the device boot-loops it sometimes shows "[ERROR] CMDLINE overflow" in the bottom left corner under the Bootloader Unlocked message.

If anybody has any suggestions, they'll be greatly appreciated, but without ADB working, I don't see if anything else can be done.

20221020_141814.jpg
20221020_141656.jpg
20221020_142245.jpg
20221020_141954.jpg
 

Attachments

  • 20221020_141814.jpg
    20221020_141814.jpg
    1.5 MB · Views: 47
Last edited:

onlineginger42

New member
Oct 23, 2022
1
0
i followed step by step when i got to V. Remove Bootloader Warning i messed something up and now my tablet is just black i can still get in download mode just don't know how to fix from here.

I FIxed my issue by flashing the og bootloader all is well :)
 
Last edited:

el7145

Senior Member
Mar 21, 2012
474
127
NY
Samsung Galaxy Tab A7 Lite
I FIxed my issue by flashing the og bootloader all is well :)

This happened to me as well, freaked me out. I didn't use this guide, but did use the up_param zip....I unlocked my bootloader, installed magisk, transferred my ap files to tablet, patched with magisk, transferrred patched files back to PC and flashed with odin, had full root, downloaded and used the commands with termux, rebooted and had a nice black screen to greet me. Like you said, easy enough to get back into download mode and flash.

I didnt use any of their files except the up_param. I didnt bother to flash the twrp for this device (T220), seems way too buggy atm

To be honest, all the up_param does is replace that warning screen with a blank black screen, ur not really getting rid of the warning (speeding up boot to system)
 
  • Like
Reactions: Aethera

PaveKoo

Member
Mar 11, 2021
6
0
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.
  1. Get the free app Termux.
  2. 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
  3. 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
  4. Now reboot, and the bootloader warning screens should be gone!
Hi!
Needed some help for my pathtetic tryind to root or edit my tablet....
Firstly next procedure is what I want to achieve.... I want my tablet to turn on when charger cable is connected and turn off when charger is unplugged.
My target is to put that tablet in a car, using it as a navigator and obd meter...
So I have two different tablets... Samsung Tab A7 Lite with android 12 :rolleyes: and Lenovo Tab M10 HD 2. gen...
I can´t get that possibly easiest way to work neither of tablets... I mean that " Fastboot oem off-mode-charge 0" command...
That didn´t work either of the tablets... both tablets oem unlocked and usb debugging allowed...
So next step what I tried, was root those tablets... Yea I know... seems very desperate :)
At this point I can´t even root the Lenono... but somehow I think I managed to root the Samsung....
I bought that Lenovo also, because I know that Samsung doesn´t accept those fastboot commands and thought that Lenovo is easier to modify / root. But not for me...

Next part should have been to try those "commands" ...
#!/system/bin/sh
/system/bin/reboot

But I don´t even know how to do that... :unsure: Do I need some app/ apps to do that...
Don´t know how to add or edit those scripts.... don´t know pretty much anything....
I downloaded some file explorer so I can see root files... or at least something in the tablet...

Then I followed that quoted instruction to remove that "Bootloader warning"
Then everything went wrong.... Yea, I know that I should have to quit way way earlier....
So I downloaded Termux... downloaded that up_param.tar file... copied it to download folder and typed to termux those lines.....
I think´you guess the result.... No the whole tablet remains black... maybe its trying to boot.... sometimes little backlight is visible althought the screen remains black... so no boot... or at least visible boot for me...
I can boot it to Odin mode... so it isn´t totally dead...
So is there any way to remove that script in odin mode... or something other way to do.... I tried to flash that modified boot.img file in odin again... everything went well.. at least it said "All threads completed (succeed 1 / failed 0)

Hope you understand even some part of my doings or my writings and can help me...
Thanks in advance!!
 

boschie

Member
Mar 28, 2007
22
3
Gramsbergen
Hi,

Thank you for the Tutorial.

Everything went great at my end until the reboot from Termux trying to remove the Bootloader Warning.
After reboot it got in a dark bootloop.
It got out of there by plugging in the USB and then hold Volume Down + Power button for a looooong time.
It then gave a warning: set warranty bit: boot
I unplugged the USB, then hold Volume Up + Volume Down at the same time and plugged it back in again. It then booted into Download Mode.

BTW, I have a new SM-T220 EUX (Europe version) and created my own patched boot as in III.
Although it was new, before I started this Tutorial it ran all the updates through the normal channels, no accounts however, not Google nor Samsung.

Tried to flash the same boot.img.tar again but gets in the bootloop again.

So now I'm searching for the original boot.img.tar that is needed to get the device working again.

h3n3
 

boschie

Member
Mar 28, 2007
22
3
Gramsbergen
Hi,

Thank you for the Tutorial.

Everything went great at my end until the reboot from Termux trying to remove the Bootloader Warning.
After reboot it got in a dark bootloop.
It got out of there by plugging in the USB and then hold Volume Down + Power button for a looooong time.
It then gave a warning: set warranty bit: boot
I unplugged the USB, then hold Volume Up + Volume Down at the same time and plugged it back in again. It then booted into Download Mode.

BTW, I have a new SM-T220 EUX (Europe version) and created my own patched boot as in III.
Although it was new, before I started this Tutorial it ran all the updates through the normal channels, no accounts however, not Google nor Samsung.

Tried to flash the same boot.img.tar again but gets in the bootloop again.

So now I'm searching for the original boot.img.tar that is needed to get the device working again.

h3n3
Oke,
I went and put the whole original firmware on the tablet via Odin, all four files. So now its back to the standard tablet again.
Maybe when I have the time for it I'll try it again or perhaps when someone puts a custom AOSP rom out there I'll give it a shot. For now I'm going as far as I can go without accounts and see if it will do what I want it to do.

Thanks again for the tutorial!

h3n3
 

boris099

New member
Aug 12, 2021
3
0
Thanks guys,

Really great - Not so easy but was successful :)

Now we only need a cool ROM, like Lineage
 

boris099

New member
Aug 12, 2021
3
0
Important one question is remaining
When I switch on the updates, will it update? Will it overwrite root?
 

fire_mane

New member
Dec 20, 2022
2
1
I am having issues with step 3 - create patched boot
I have samsung build T220XXU1BVGB
I have downloaded from 2 different sources the firmware for this device, they all come with 4 .md5 files
however the steps in the guide say to - extract a lz4 from a tar file? I don't appear to have a tar file that I know of.

edit: think i've got it rooted now I just had to read through a bit of the responses.
 
Last edited:
I managed to complete everything but when i overwrote the up_param the tablet began bootlooping and tried flashing with odin didnt help, resorted to MTK stuff (bad idea) now my tablet wont respond to anything and just shows up as MTK Device in device manager, i'd appreciate if anyone could help if there is any hope at all
 

tom.android

Senior Member
Jul 12, 2016
1,081
347
Sorry to hear that , warring red or yellow text is a good sign to declare bad conditions had happened to your device , not necessary to conceal it from yourself. my advice for this situation is contact service center.
 
Sorry to hear that , warring red or yellow text is a good sign to declare bad conditions had happened to your device , not necessary to conceal it from yourself. my advice for this situation is contact service center.
I have managed to unblock it kinda, but only thing im able to is get SP Flash to flash some things i cannot write to most partitions as secure boot is always on even with using mtk bypass, and so rebooting or anything just makes the device restart and go between Preloader and MediaTek USB device
 

CarrotcruncherUK

New member
Dec 26, 2022
3
1
Solved ! LOL

This guide is pretty good but what isnt clear is how to tell exactly which T220XXXXXXXXX model you have, IA went into andoid setting setting and all mine says is SM-T220
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Warning: Step V. Remove Bootloader Warning causes bootlop on SM-T220 running T220XXU1CVL7_T220OXM1CVL7_XAR. Had to reflash entire system via Odin to recover.
    Well yeah, because that file was designed for an Android 11-based bootloader and not the Android 13 you're running. To recover, you only had to reflash the BL (bootloader) Odin file for your firmware. There's another thread with the right up_param file for A13.
    1
    Can you please put a warning in Step V or a link to the Android 13-compatible up_param? Thanks!
    Already replied to you in the other thread. I cannot edit the original post because I'm not the original poster.

    Yes, it is a cosmetic change.
  • 19
    While 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.)
    1. Factory Reset Device (Sorry but this will happen when you unlock & root anyway, and has to be done first.)
    2. 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.)
    3. I did not change any settings when I booted in, just proceeded to step 4.
    4. Enable developer options and disable automatic system updates from there.
    5. Disable automatic software update. Settings > Software Update > turn off.
    6. Connect to a WiFi network.
    7. 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.
    8. 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.
    9. 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.
    10. 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)
    1. Enable developer options by going to Settings > About Tablet > Software information > and tap "build number" 7 times
    2. Go to Developer options, turn on OEM Unlock (If it doesn't show up, skip to Part III and then come
    3. Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
    4. Long-press Volume Up key to enter Device Unlock mode
    5. 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.)
    1. Download your firmware from samfirm or other source (I didn't have to do this, so I can't instruct on it)
    2. (On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to Tab
    3. (On Tab) Install ZArchiver to extract boot.img from boot.img.lz4
    4. (On Tab) Install Magisk and patch the boot.img that you have just extracted from step 3
    5. (On PC) Copy magisk_patched.img (in Tab\download) to pc, rename it to boot.img
    6. (On PC) Use 7zip to pack boot.img from step 5 into boot.img.tar

    IV. Root Tab A7 Lite
    1. Download correct boot.img.tar for your device (For T220XXU1AUJ1 it's magisk_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!

    2. 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.

    3. 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):

    4. Open Odin as Administrator (Right-click > Run as Administrator)

    5. 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)
    6. 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.

    7. 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).

    8. 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.
    1. Get the free app Termux.
    2. 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
    3. 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
    4. 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:
    1. 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.
    2. Install the APK. Open file manager if you need to and then find it in Downloads or wherever you downloaded it.
    3. Open Magisk, it will ask you to update. Choose "Direct Install (Recommended)" and then click Let's Go in the top right.
    4. It will flash the image and then say All Done!, then you can click the Reboot button in the bottom right.
    5. 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.
    6. You will be greeted with a Superuser popup if you are rooted, so grant permissions and you can see you are rooted! Congratulations!
    7. 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
    1. 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.
    2. Copy the zip file to your device.
    3. Open Magisk, go to Modules, click Install from Storage, and find the zip you just copied for lsposed zygisk version.
    4. Click Reboot button in the bottom right when it's finished.

    VIII: Activate Zygisk (Successor to Riru) on Tab A7 Lite
    1. You're not done yet. Now go into Magisk, click Settings button in the top right.
    2. Scroll down and enable Zygisk (Beta).
    3. Below that, enable Enforce DenyList.
    4. Below that, click Configure DenyList.
    5. In the top right, click the 3 dots menu and check the box Show System Apps.
    6. Select Google Play Services by checking the box.
    7. Tap on Google Play Services to open all the items for it, and enable all the items for Google Play Service.
    8. 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.
    9. 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 ;))
    10. 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.
    11. 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.
    1. 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.
    2. 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.)
    3. Recommended Module: DarkTricks (For Android 11) - More customizations and tricks. Nothing "dark" about it, just the user's name.
    4. Recommended Module: FireFds Kit [R] (For Android 11) - Activate Advanced Power Menu, Disable restart confirmation, Date in Status Bar, etc.
    5. 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)
    6. To install, just copy to your device, and browse to the apk through file manager, and install it.
    7. 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.
    8. 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.
    1. Shamiko Development Version: https://t.me/magiskalpha/438
    2. Momo Development Version: https://t.me/magiskalpha/379
    3. Install Shamiko using Magisk like you did in Part VI: Go to Modules, Install from Storage, Find the Shamiko .zip file, Install, Reboot.
    4. Install the Momo APK. You can open it right away.
    Official Telegram: https://t.me/s/magiskalpha (Find latest versions here on the Telegram page. I had to use actual Telegram to download them. So I attached the apks above.)

    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)
    - 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

    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.
    4
    Hello

    I leave the boot.img patched with magisk

    ROM this XXU1AVB2 and device is SM-T225
    2
    how did you find T220XXU1AUL2 stock firmware region code OXM
    it's really hard to find
    Don't worry found it it's because its in Urkraine




    2
    I got a 4GB/64GB (top model) T220 on sale from the Best Buy ebay page for only $150!

    Sams Club and Costco have the 3GB/32GB model on sale right now for only $130!
    Picked up the 3GB/32GB model on Amazon for $119 this week.
    1
    It worked for me