Can anyone make a video of this guide ?
i am on T225XXU1BVGB, but my tab is government locked...
its frustrating...
i am on T225XXU1BVGB, but my tab is government locked...
its frustrating...
Accessories CustomAP 2022
- Thread starter tom.android
- Start date
The problem is not using my step by step tutorial but this case is how to unlocked your bootloader ?. make sure you are in 100% unlocked , if not >>>such as KG Prenormal or KG Broken State will bricked your device or can't go into recovery mode.
(Owner networks provider lock , Government lock >>>Don't uses CustomAP. )
>> Video tutorial about Step by Step CustomAp is not suitable for me, it is easy enough to read and follows my step.
KG = knox guard
Last edited:
Could you please tell me how can i unlock my bootloader 100% ?
i was doing this way... (pics)
is it the right way ? or should i do something else.
or will i be able to unlock my bootloader as its Government locked?
Attachments
have you tried to extract A12 super? i can only extract system, i don't know why the tool doesn't extract other stuff, i guess because simg2img convert theimage to only 1.6 GB (that should be system only, i'm not sure)
Your tab will automaticaly boot into TWRP mode, TAB screen may be black , you must activates it by press power then volumn.
which way to get into TWRP since Im just getting stuck at black screen
make sure you patch AP .md5.tar with magisk v25 only. and you can access TWRP with "adb reboot recovery"
TWRP FOR Android 11 Device SM-T22x
No touch supported.Used only (TWRP 's Fastboot)Mode.
》》FIRST TIME INSTALLATION
Howto install TWRP For SM-T225
# Patch Samsung AP Firmware via Magisk v24.0 ( patched entire AP file)
1. Install Magisk.apk on your device SM-T225 with select no update checking, and transferred AP_xxx.tar.md5 from computer to your tab.
2. Patch Samsung AP Firmware via Magisk Manager.
( Once done, the newly created magisk_patched.tar file will be present under the
Downloads folder on your device.)
3. you may now transfer this patched TAR file to the folder on your PC where other extracted firmware files (AP, BL, CP, CSC, and HOME_CSC) are present.
4. FLASH it with ODin as usual by used magisk_patched.tar file at AP slot .
5. REBOOT SYSTEM Quick SETUP < NO NEED INTERNET>
6. Power Off and press Volum up +Volumn down + USB for boot into Download mode
7. FLASH TWRP.tar from https://github.com/DevZillion/android_device_samsung_gta7lite/releases at "AP slot"
But this time set Odin option NO Auto- REBOOT, yes do it yourself with key press ( power + volumn up).
## if you can't use keypress but reboot to the system , you can use cmd " adb reboot recovery "
When had access to twrp menu
Go to Advanced > Terminal and type "multidisabler" (without quotes", then data wipe.
Now reboot into system, after completing first setup of the device reboot into TWRP again to see if you can see the contents of your Internal Storage, you should, if yes you have successfully disabled Samsung encryption of internal storage.
NOTE: If you wish to install TWRP without rooting, there are numerous pitfalls to consider. For example, a stock device is protected by Android Verified Boot. This is implemented as a vbmeta partition that contains cryptographic digests for verifying the integrity of boot.img, recovery.img and other partitions/images. Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
》》》》》》》》》》》》》》》》》
Last edited:
This is a tablet which was issued to some government office and some how IDK how you got it, now either you can call them and send this back to them, or you have to hire somone online to take this lock off there are so many online websites doing this for money just google it, without that you cant do anything to it.
after flashing patched Magisk file can I just stop here without putting the TWRP and use tablet as its with root? what are the advantages of having the twrp since there is no ROM and encryption still going to be there?Working but no offline charging.
1. Root ( by patch boot.img with magisk ) is not depended on TWRP.
2. We can uses Fastboot of TWRP for flashing GSI (system) because Sam devices have not using Fastboot mode.
3. if you don't uses fastboot or twrp for flashing tools , the only thing left is odin.
Go to customize your sam device with odin if you want.
Last edited:
End of CustomAP Starting with FastbootD tutorial.
bro i am in A13 ONE UI BUT I CANNOT GO BACK TO PREVOIUS A11 AND A12 IF I WANT TO USE VB META ISSUE PLZ HELPPP
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Part 1:Step by Step: Create CustomAP framework file For GSI Flashing with Odin.by tom.android
Modified from @abg95a
Flash a GSI on the A7 Lite (without TWRP)
Update for add loop device in WSL2
( **will slow-down Win10 )
[ not recommend if you don't want to modified your system.img ]
>> Check WSL version.
Open CMD with Administrator
C:\Windows\System32>NAME STATE VERSIONCode:wsl --list --verbose
Ubuntu-20.04 Stopped 1
----> you are on wsl1
>>> Howto update it to WSL2 if you have installed Ubuntu ?
C:\Windows\System32>Code:wsl --set-version Ubuntu-20.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Conversion complete.
test after converted .
C:\Windows\System32>NAME STATE VERSIONCode:wsl --list --verbose
Ubuntu-20.04 Stopped 2
----> Now you are on wsl2
====End Update WSL1 with WSL2 ====
✓ LINUX Installation
Ubuntu Subsystem 20.04.5 LTS
OPEN microsoft store , Select Ubuntu version and click install.
After
Find Where to Stored installation Files.
here: (open windows show hidden file)
FOR WSL1
\Users\username\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu20.04LTS_\LocalState
For WSL2 >>>you can access to home directory from windows (Windows 10 build 18342) like this :
\\wsl$
## make a shotcut to desktop (for easy copy and paste , sharing files between WIN and LINUX)
Resources: https://askubuntu.com/questions/759...t-directory-in-windows-subsystem-for-linux-an
====================================
New fresh install with WSL2 >
Ubuntu 20.04.5 LTS
>> How?
Before:
Check win10 with WSL1 or not
C:\Windows\System32>wsl --list --verbose
NAME STATE VERSION
Ubuntu-20.04 Stopped 1
----> you are on wsl1
Howto update to be "WSL2"
1.open windows10 update
setting--windows update---Advanced option = open receive update
After Download Update from Microsoft.
2. open windows system---command promp--Administrator mode
cmd> wsl --update
output
Checking for updates...
No updates are available.
Kernel version: 5.10.102.1 <----wsl2
3. RUN in CMD
Code:wsl --set-default-version 2
Then install Ubuntu.
Test: loop device.
Open Ubnutu terminal
Code:cd /devCode:ls -l | grep -v tty
(you will saw loop command.)tom@DESKTOP-PA2DE4E:~$ cd /dev
tom@DESKTOP-PA2DE4E:/dev$ ls -l | grep -v tty
total 0
crw-r--r-- 1 root root 10, 235 Oct 14 15:49 autofs
drwxr-xr-x 2 root root 40 Oct 14 15:49 block
drwxr-xr-x 2 root root 80 Oct 14 15:49 bsg
crw------- 1 root root 10, 234 Oct 14 15:49 btrfs-control
drwxr-xr-x 3 root root 60 Oct 14 15:49 bus
crw------- 1 root root 5, 1 Oct 14 15:49 console
crw------- 1 root root 10, 62 Oct 14 15:49 cpu_dma_latency
crw------- 1 root root 10, 203 Oct 14 15:49 cuse
lrwxrwxrwx 1 root root 13 Oct 14 15:49 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 Oct 14 15:49 full
crw-rw-rw- 1 root root 10, 229 Oct 14 15:49 fuse
crw-r--r-- 1 root root 1, 11 Oct 14 15:49 kmsg
crw------- 1 root root 10, 237 Oct 14 15:49 loop-control
brw------- 1 root root 7, 0 Oct 14 15:49 loop0
brw------- 1 root root 7, 1 Oct 14 15:49 loop1
brw------- 1 root root 7, 2 Oct 14 15:49 loop2
brw------- 1 root root 7, 3 Oct 14 15:49 loop3
brw------- 1 root root 7, 4 Oct 14 15:49 loop4
brw------- 1 root root 7, 5 Oct 14 15:49 loop5
brw------- 1 root root 7, 6 Oct 14 15:49 loop6
brw------- 1 root root 7, 7 Oct 14 15:49 loop7
drwxr-xr-x 2 root root 60 Oct 14 15:49 mapper
crw------- 1 root root 1, 1 Oct 14 15:49 mem
drwxr-xr-x 2 root root 60 Oct 14 15:49 net
crw-rw-rw- 1 root root 1, 3 Oct 14 15:49 null
crw------- 1 root root 10, 144 Oct 14 15:49 nvram
crw------- 1 root root 108, 0 Oct 14 15:49 ppp
crw-rw-rw- 1 root root 5, 2 Oct 14 16:56 ptmx
drwxr-xr-x 2 root root 0 Oct 14 15:49 pts
brw------- 1 root root 1, 0 Oct 14 15:49 ram0
brw------- 1 root root 1, 1 Oct 14 15:49 ram1
brw------- 1 root root 1, 10 Oct 14 15:49 ram10
brw------- 1 root root 1, 11 Oct 14 15:49 ram11
brw------- 1 root root 1, 12 Oct 14 15:49 ram12
brw------- 1 root root 1, 13 Oct 14 15:49 ram13
brw------- 1 root root 1, 14 Oct 14 15:49 ram14
brw------- 1 root root 1, 15 Oct 14 15:49 ram15
brw------- 1 root root 1, 2 Oct 14 15:49 ram2
brw------- 1 root root 1, 3 Oct 14 15:49 ram3
brw------- 1 root root 1, 4 Oct 14 15:49 ram4
brw------- 1 root root 1, 5 Oct 14 15:49 ram5
brw------- 1 root root 1, 6 Oct 14 15:49 ram6
brw------- 1 root root 1, 7 Oct 14 15:49 ram7
brw------- 1 root root 1, 8 Oct 14 15:49 ram8
brw------- 1 root root 1, 9 Oct 14 15:49 ram9
crw-rw-rw- 1 root root 1, 8 Oct 14 15:49 random
crw------- 1 root root 251, 0 Oct 14 15:49 rtc0
brw------- 1 root root 8, 0 Oct 14 15:49 sda
brw------- 1 root root 8, 16 Oct 14 15:49 sdb
crw------- 1 root root 21, 0 Oct 14 15:49 sg0
crw------- 1 root root 21, 1 Oct 14 15:49 sg1
lrwxrwxrwx 1 root root 8 Oct 14 15:49 shm -> /run/shm
lrwxrwxrwx 1 root root 15 Oct 14 15:49 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Oct 14 15:49 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Oct 14 15:49 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root root 1, 9 Oct 14 15:49 urandom
crw------- 1 root root 7, 0 Oct 14 15:49 vcs
crw------- 1 root root 7, 1 Oct 14 15:49 vcs1
crw------- 1 root root 7, 128 Oct 14 15:49 vcsa
crw------- 1 root root 7, 129 Oct 14 15:49 vcsa1
crw------- 1 root root 7, 64 Oct 14 15:49 vcsu
crw------- 1 root root 7, 65 Oct 14 15:49 vcsu1
drwxr-xr-x 2 root root 60 Oct 14 15:49 vfio
crw------- 1 root root 10, 238 Oct 14 15:49 vhost-net
crw------- 1 root root 10, 63 Oct 14 15:49 vsock
crw-rw-rw- 1 root root 1, 5 Oct 14 15:49 zero
tom@DESKTOP-PA2DE4E:/dev$
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
GET START>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>✓ Get " super.img" from inside Stock AP File
by Extract (super.img.lz4) file by Windows or Linux.
For Windows
Download lz4 for win and extract into C:\AnyName
from https://github.com/lz4/lz4/releases
1) extract "super.img.lz4" from Stock AP Firmware file with 7zip, into lz4 folder.<AnyName>
2) go into folder lz4_win64_v1_9_4 and run CMD
Code:lz4 -d super.img.lz4 super.img
copy output " super.img" to uses with Ubuntu at /home/username/
>>>>>>>>>>>>≥>>>>>>>>>>>>>>>>>>>>>>
For Linux:
✓ launch Ubuntu terminal( console) from Start menu
2.1) Option We can uses LZ4 from linux, process same as (Step 1-2 for wins)
Ubuntu
you can install LZ4 from Ubuntu Console with
Code:sudo apt update sudo apt-get -y install lz4 or sudo apt install liblz4-tool
note
lz4 [option] input output
lz4 -d (d= decompress)
lz4 -dc ( c=concatenate )
2.2) Option Extract "super.img.lz4" from Stock AP framework file.
and paste it to /home/username/
2.3)
Code:sudo lz4 -d super.img.lz4 super.img
2.4)COMPARE with using "lz4" between Ubuntu and Windows
CONCLUSION of Beginning step.
WE CAN GETS " SUPER.IMG" FROM TWO WAYS , WINDOWS OR LINUX.
( windows from step 1-2 ) or. ( Linux from step 2.1 -2.3)
***We will use 'super.img' to begin our modification.✓ unpacking super.img
3.) Turn sparse format To RAW
Ubuntu
**First of all the super.img file might be in sparse format so we need to make it raw image. By Using "SIMG2IMG"
Code:sudo apt-get update sudo apt-get install simg2img
I'm
ok
Code:sudo apt-get install img2simg
After install execute this command.
Code:sudo simg2img super.img super.raw
✓Extract subpartition out from "SUPER.RAW"
4) Tool for extract partition. ( very important tool for show "group schema" which used to specific parameter option for lpmake.)
4.1) Download imjtool
http://newandroidbook.com/tools/imjtool.tgz
or download from attach file belows this tutorial (imjtool.zip)
4.2) extract "imjtool" from archive imjtool.tgz to /home/username/
*note for short i renamed it to 'imjtool'
4.3) then give it permission with command
Code:chmod +x imjtool
5) Extract sub partition within our "SUPER.RAW"
By execute this command
Code:./imjtool super.raw extract
It will extract sub-partitions (4 img files ) in the folder "/home/user/extracted"
- system.img
- vendor.img
- product.img
- odm.img
✓ Modify Stock "system.img" by Changes with GSI-"system.img"
6) Choose your favorite GSI. ( Recommend PHH Treble- GSI )
Download from :-
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
6.1) Extract Downloaded archive & Replace "system.img" with your GSI img
(rename it to system.img over-written the old file.)
6.2 )
Move all img files (6.1)
from /home/username/extracted folder into /home/username/
7.) Get each partitions file size.
we can do it by:
Code:stat -c '%n %s' IMG_FILE.img
:- do it for all partitions files.
7.1Exam output---system.img 308 951 4496Code:stat -c '%n %s' system.img
7.2Exam ouputt----vendor.img 718 503 936Code:stat -c '%n %s' vendor.img
7.3Exam output----product.img 118 811 8528Code:stat -c '%n %s' product.img
7.4Exam output----odm.img 434 9952Code:stat -c '%n %s' odm.img
7.5 ***size of the "original super.raw"
Exam output----super.raw 609 432 3712Code:stat -c '%n %s' super.raw
✓ Repacked modified sub-partition back
8) Repacked new super.img.
8.1 fill in "img partition size" formular (parameter) to your prepared command below
explanation:
explanation:
Prepared command "LPMAKE" parameter
sudo ./otatools/bin/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:readonlyRODUCT_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
Note:
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.
====================
8.2
Download & extract : OTATOOLS to /home/username/
here:**We only want to use "lpmake" from its.Google Drive - Virus scan warning
drive.google.com
*** If you have a problem when used command " sudo ./otatools/bin/lpmake --metadata-size 65536 \ bra bra bra
Error message: Command not found.
Do this...
orCode:chmod +x otatools/bin/lpmake
Code:chmod -R +x otatools
> exit terminal and Login Back again
8.3) execute prepared formular (8.1) with this command
Note: Numeric are my Example only.
1. Fix partition size ( odm + product + vendor )
434 9952 + 118 811 8528 + 718 503 936 = 1,910,972,416 + (new system.img )= Sum of all 4 partition.
2. Fix All partition ( super.raw) = 609 432 3712
***DO NOT COPY!!***
explanation:
Code:sudo ./otatools/bin/lpmake --metadata-size 65536 \ --super-name super \ --metadata-slots 2 \ --device super:6094323712 \ --group main:5000486912\ --partition odm:readonly:4349952:main \ --image odm=./odm.img \ --partition product:readonly:1188118528:main \ --image product=./product.img \ --partition system:readonly:3864137728:main \ --image system=./system.img \ --partition vendor:readonly:718503936:main \ --image vendor=./vendor.img \ --sparse \ --output ./super_new.img
OUTPUT SHOW:-
lpmake I 09-11 03:32:54 36 36 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
lpmake I 09-11 03:32:54 36 36 builder.cpp:1012] [liblp]Partition product will resize from 0 bytes to 1188118528 bytes
lpmake I 09-11 03:32:54 36 36 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 3864137728 bytes
lpmake I 09-11 03:32:54 36 36 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 718503936 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
**lpmake expand partition success. Resize from 0 bytes to 9999999 bytes
**ignored Invalid sparse file format at header magic
✓Compress repacked modified new super.img
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
Download Clean vbmeta.img from Google
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Code:lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
Win10
(From Attachment download.)
11). Down& Extract "tar-md5-script-tool.zip" to C;\
11.1 extract all *.img.lz4 files (from AP Stock) to. C:/ tar-md5-script-tool folder
12) 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)--->output from step 9
and the clean compressed
vbmeta.img.lz4. ------> output from step 10
13) Run Win Batch File For Packing Custom AP file (tar.md5) for Odin
Run batch.bat in tar-md5-script-tool folder
[You will find the " AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5"
in the temp-folder subdir]
***Don't Rename
14) Final Flashing with ODin
...14.1) Device must installed Stock Firmware. (No root)
* No bad critical conditions happened when you are on STOCK ROM.
... 14.2) OEM Unlock [Developer options] must gray out but
. enable on position.
... 14.3) KG State Must be "Checking state" status.
( if kg state = Broken ) = you must have goto flash Pure stock firmware
again and this time uses ONLY "CSC" factory reset
. *NO used Home_CSC
After finished odin fashing must connected internet, check "kg status"
again )
...14.4) Flashing all files at once, don't ignored any slot.( AP+BL+CP+CSC)
except USERDATA
(Odin will shrink non-slot data size automatically)
...14.5) After Device reboot
(1st) show android robot - remove old system
(2nd) Due to new vbmeta.img has changed from stock , tab will reboot to
Recovery menu , you must select its factory reset menu manually.
...14.6) Click Magisk icon app to update
" Upgrade to full Magisk to finish the setup. Download and install"OK
- Magisk app will not reboot but update itself. But if you open app
again it will asked to reboot for addition upgrade.
>AP SLOT : AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
>BL Slot : BL Stock.md5
>CP SLOT: CP Stock.md5
>CSC Slot: CSC Stock.md5 ------> (Don't uses HOME_CSC)
>USERDATA Slot: magisk_boot_vbmeta_patch.tar
✓ How to create Magisk patch for boot.img + vbmeta.img
- extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
- create compress one file xxx .tar with 7zip
- move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
- install magisk.apk on you tab a7 lite
- patch the tar file. (with magisk manager)
- result magisk-patch file at Tab a7 :-Download folder.
Recommend: Default R/W GSI " by Nazim"
My Examples
https://xdaforums.com/t/6-prerequisites-for-tab-a7-lite-gsi-installation.4503647/#post-87550627
If you can't booted "VNDK Lite" variant but want to uses mount Read/Write .
Part3 -Create CustomAP Tutorial.
2
1. Root ( by patch boot.img with magisk ) is not depended on TWRP.
2. We can uses Fastboot of TWRP for flashing GSI (system) because Sam devices have not using Fastboot mode.
3. if you don't uses fastboot or twrp for flashing tools , the only thing left is odin.
Go to customize your sam device with odin if you want.1
I never used Bluetooth with Sony. Used only wired.
Try to setup GSI here
-Samsung features
Enable stereo audio mode
Enable extra sensors
-Misc features
Use alternate way to detect headsets
Disable audio effects
and reboot1
Try it ..will work . I only uses Bluetooth with Samsung buds 2 only. Sony with wired.1How to Patch Samsung AP Firmware via Magisk
In this guide, we will show you how to patch...droidwin.com
