flash via odin, make sure you have selected correct firmware for your phone csc(country code)...
nb: for a7 lite android 11, android 12 , and android 13cvl5, bootloader rev version is still same.. so you can downgrade your phone with lower android version...
All that "mod" does is replace literally two .jpeg images the system shows when booting. If you decompress it, you'll see the charging images intact and since the file only has images, that means the rest of the bootloader is untouched. No idea what really happened in your case.
well i did this, to take off the spash screen
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param
I did the same thing and bricked my device pretty hard
Have you tried reflashing whole firmware again
If that did not work then use mtkclient to flash whole firmware again, that worked for me
I can dm you instructions if you want
Successfully flashed pure android 13 GSI hurray!
I've minimized the otatools so it can be preserved easier than full 300mb archive it's now 4mb archive (7zipped)
mega.nz
I may also see if i can rewrite tar-md5-script-tool in bash so this can be used on linux and fully automated, i just don't like the batch scripts
Although i did not test it, this is basically all the batch script does, it's much more readable and concise in shell i don't know why they wrote it in batch..
I've minimized the otatools so it can be preserved easier than full 300mb archive it's now 4mb archive (7zipped)
3.74 MB file on MEGA
Although i did not test it, this is basically all the batch script does, it's much more readable and concise in shell i don't know why they wrote it in batch..
Code:
$ tar --create --format=gnu -b20 --quoting-style=escape --owner=0 --group=0 --totals --mode=644 -f AP_TAR_MD5_CUSTOM.tar *.lz4
$ md5sum -t AP_TAR_MD5_CUSTOM.tar >> ./AP_TAR_MD5_CUSTOM.tar
$ mv AP_TAR_MD5_CUSTOM.tar AP_TAR_MD5_CUSTOM.tar.md5
Last edited:
What's the difference between tar and md5. Odin didn't see it. All mine is md5 and odin see it.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8Hi everyone, this is a short guide on how to flash a GSI on the A7 Lite (without TWRP).
Its a nice little tablet for the price but it doesn't have a very powerful SOC and for me the One UI is barely usable on this device. The launcher and the whole system UI feel extremely laggy, but apps generally run fine.
I tried phhusson's custom Android 12 GSI and the device was almost resurrected. Much much less UI lag and the battery life is the same as stock ROM. The only thing i found not working is MTP but i don't need it.
Since i saw a couple users here asking about GSIs i decided to make a very simple guide.
As always do this at your own risk. You may brick your device. You will void your warranty.
Follow the guide only if you know what your are doing. Read each step carefully and avoid copy pasting stuff randomly.
I won't go deep into details as i believe you should have some basic knowledge if you decide to do this.
The procedure sould work for both T220 and T225 (i tested it on a T220).
I did this on Windows using WSL for some of the steps.
Sources
Thanks to @kkoo and @Brepro1 for the useful info
- https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
- https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
Requirements
- Unlocked bootloader
If you haven't done this already follow the steps in parts 1-2 from:
[TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods
While some of these instructions are copied...
forum.xda-developers.com
- Latest official ROM
I used T220XXU1AVE1 for EUX region
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download
Samsung Galaxy Tab A7 Lite Firmware Download...samfw.com
- Download your preferred GSI
I used AOSP 12.1 v414 with gapps from phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project...
github.com
- Clean vbmeta.img from Google
Tools
- lz4
- simg2img
[DEV][Tools] simg2img for Windows
Hello, although I'm working in Linux (VM too)...
forum.xda-developers.com
- lpunpack and lpmake
- tar-md5-script-tool
Use the attached tar-md5-script-tool.zip
Steps
1. Extract official ROM files (BL, AP, CP, CSC)
2. Extract AP .tar.md5
3. Decompress the extracted super.img.lz4
Code:lz4 -d super.img.lz4 super.img
4. Convert the sparse super.img
Code:simg2img super.img super.ext4.img
5. Unpack super.ext4.img
Code:lpunpack super.ext4.img
I got 4 partitions in my image (should be the same for all T220/T225 ROMs):
- odm.img
- product.img
- system.img
- vendor.img
6. Replace system.img with your GSI (rename it to system.img)
7. Get the size of all partitions and the size of the original super.ext4.img (not the sparse super.img)
Code:stat -c '%n %s' IMG_FILE.img
8. Repack super.img
Code:lpmake --metadata-size 65536 \ --super-name super \ --metadata-slots 2 \ --device super:ORIGINAL_SUPER_IMG_SIZE \ --group main:SUM_OF_ALL_PARTITIONS_SIZES \ --partition odm:readonly:ODM_PARTITION_SIZE:main \ --image odm=./odm.img \ --partition product:readonly:PRODUCT_PARTITION_SIZE:main \ --image product=./product.img \ --partition system:readonly:SYSTEM_PARTITION_SIZE:main \ --image system=./system.img \ --partition vendor:readonly:VENDOR_PARTITION_SIZE:main \ --image vendor=./vendor.img \ --sparse \ --output ./super_new.img
Replace ORIGINAL_SUPER_IMG_SIZE, SUM_OF_ALL_PARTITIONS_SIZES, ODM_PARTITION_SIZE, PRODUCT_PARTITION_SIZE, SYSTEM_PARTITION_SIZE, VENDOR_PARTITION_SIZE with the values you obtained in step 7.
Read lpmake docs for a more detailed expalation of the args used above:
9. Compress the repacked super_new.img
Code:lz4 -B6 --content-size super_new.img super_new.img.lz4
10. Compress the clean vmbeta.img
Code:lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
11. Extract tar-md5-script-tool.zip
12. Put all the *.img.lz4 files extracted from AP .tar.gz in tar-md5-script-tool dir
13. Replace super.img.lz4 and vbmeta.img.lz4 in tar-md5-script-tool dir with your repacked and compressed super_new.img.lz4 (rename it to super.img.lz4) and the clean compressed vbmeta.img.lz4
14. Run batch.bat in tar-md5-script-tool dir
You will find the new AP .tar.md5 in the temp-folder subdir
15. Flash your custom AP .tar.md5 with Odin along with BL, CP, CSC from original ROM
16. Reboot into recovery and do a factory reset
17. Done2
Happy testing
GSI: lineage-19.1-20220613-UNOFFICIAL-arm64_bvS-vndklite.img
https://www.filehosting.org/file/details/8249475/GSI-Lineage-19.1_SM-T225_THL_T225XXU1AVB2.zip2
No, your base is not the problem. That particular version of A12 CherishOS uses PHH v415 which has issues booting for our devices. Only PHH v414 or v416 GSIs like this one boot for us (it works for VJ2 firmware, tested it myself). Sadly I don't see any other developer releasing an A12 v416 based GSI like the one I linked to so yes, that's what we have for now until the newer A13 GSIs pick up the v416 patches hopefully.2Successfully flashed GSI with magisk on my T220 following the OP's procedure. MTP is not working as the OP said. However, I can use my flash drive so I don't really miss MTP.
I chose "system-squeak-arm64-ab-vndklite-gapps-secure.img.xz" for GSI. "Treble Info" app can tell you what image would be compatible with your device.
If you want to use a different launcher like Nova instead of the default one, change the "Smallest width" setting from 600 to 598 in Developer options to hide the annoying taskbar.
AOSP-Mods and "Project Themer - Android 12+" work fine for me.
Here is my build for my device SM-T220 (SM-T220_EUX_T220XXU1AVE1):
GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Custom AP: https://www.filehosting.org/file/details/7045394/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Custom AP with Magisk patch: https://www.filehosting.org/file/details/7045714/magisk_patched-25101_cauJQ.tar
You can extract BL and Home_CSC from SM-T220_EUX_T220XXU1AVE1.
Notes: My device is actually SM-T220 XAR, but I have been updating it with SM-T220 EUX firmware versions without any issue.
