Accessories CustomAP 2022

Search This thread

zenitsu man

Senior Member
Jul 29, 2022
so i will be having martial arts classes soon they end in night so any method will be tested tomorrow im sorry i dont reply and appreciate for helping me

Senior Member
Jul 12, 2016
NEW Android 12 TODAY
Screenshot_20220810-113713_Vivaldi Browser.jpg

Screenshot_20220810-114117_Vivaldi Browser.jpg

Howto install

FOR someone who loves easy install GSI , now no TWRP for A12. And vendor.img A12 not suitable for GSI 12/L . Then A11 is your friend.


!!!! if you are boring charging with Warranty Bit effect ( Charging with the device powered off ) then New A12 is your best choices.

I had only installed clean A12 , clear cache one time and performance is good for now. ( increase virtual RAM ) . Display color for media is my favorite.

Battery: normal consumption. Not good or bad

Screenshot_20220810-121626_Device care.jpg

My 2 favorit are always " WAVELET" + "PowerAmp Equalizer"


Screenshot_20220810-123532_Poweramp Equalizer.jpg

Try to make 3 apps working together simultaneously.(mx player + wavelet + poweramp Equalizer)
Screenshot_20220810-124820_Poweramp Equalizer.jpg

Screenshot_20220810-125631_Vivaldi Browser.jpg

US/Canada devices has no oem unlock toggle!

How to get OEM Unlock option back for Non US/Canada device?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Last edited:

zenitsu man

Senior Member
Jul 29, 2022
i talked with dev zillion he said that it stuck in mediatek preloader if we flash the bootloader agian it will be fixed but i cant figure out how to enter brom mode

Senior Member
Jul 12, 2016

Senior Member
Jul 12, 2016
Brom mode must have enable Debugging in developer option.

You must use this method.

Unlock bootloader without fastboot
But the first thing you must do is. STEP 1: Enable USB Debugging and OEM Unlock

If you have fastboot ( from TWRP mode ) may be possible , but you didn't install TWRP.
Last edited:

zenitsu man

Senior Member
Jul 29, 2022
bro i think i can escape from this problem i made the scatter file using a tool it works its valid and when trying to flash with sp flash tool it begins but i said you about the connecting and disconnecting thats the issue it will stop in between because it disconnects


  • 1660124261377.png
    193.9 KB · Views: 17

zenitsu man

Senior Member
Jul 29, 2022
i fixed connecting disconnecting but sp flash tool give random errors because maybe samsung devie use secure boot i am so frustrated uhhhhhhbbhhuhuhhhuh

Top Liked Posts

  • There are no posts matching your filters.
  • 2

    Part 1​
    :Step by Step:

    Create CustomAP framework file For

    GSI Flashing with Odin.

    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

    wsl --list --verbose
    Ubuntu-20.04 Stopped 1

    ----> you are on wsl1

    >>> Howto update it to WSL2 if you have installed Ubuntu ?

    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
    Conversion complete.

    test after converted .

    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.

    Find Where to Stored installation Files.
    here: (open windows show hidden file)

    FOR WSL1

    For WSL2 >>>you can access to home directory from windows (Windows 10 build 18342) like this :


    ## make a shotcut to desktop (for easy copy and paste , sharing files between WIN and LINUX)



    New fresh install with WSL2 >

    Ubuntu 20.04.5 LTS

    >> How?

    Check win10 with WSL1 or not

    C:\Windows\System32>wsl --list --verbose

    Ubuntu-20.04 Stopped 1

    ----> you are on wsl1

    Howto update to be "WSL2" 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

    Checking for updates...
    No updates are available.
    Kernel version: <----wsl2

    3. RUN in CMD

    wsl --set-default-version 2

    Then install Ubuntu.


    Test: loop device.
    Open Ubnutu terminal

    cd /dev
    ls -l | grep -v tty

    [email protected]:~$ cd /dev
    [email protected]:/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
    [email protected]:/dev$
    (you will saw loop command.)



    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

    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

    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)

    you can install LZ4 from Ubuntu Console with

    sudo apt update
    sudo apt-get -y install lz4
    sudo  apt install liblz4-tool

    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/

    sudo lz4 -d super.img.lz4  super.img

    2.4)COMPARE with using "lz4" between Ubuntu and Windows


    CONCLUSION of Beginning step.​

    ( 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​


    **First of all the super.img file might be in sparse format so we need to make it raw image. By Using "SIMG2IMG"

    sudo apt-get update
    sudo apt-get install simg2img

    sudo  apt-get install img2simg

    After install execute this command.

    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

    or download from attach file belows this tutorial (

    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

    chmod +x imjtool


    5) Extract sub partition within our "SUPER.RAW"

    By execute this command
    ./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 :-

    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:

    stat -c '%n %s' IMG_FILE.img

    :- do it for all partitions files.

    stat -c '%n %s' system.img
    Exam output---system.img 308 951 4496

    stat -c '%n %s' vendor.img
    Exam ouputt----vendor.img 718 503 936

    stat -c '%n %s' product.img
    Exam output----product.img 118 811 8528

    stat -c '%n %s' odm.img
    Exam output----odm.img 434 9952

    7.5 ***size of the "original super.raw"
    stat -c '%n %s' super.raw
    Exam output----super.raw 609 432 3712


    ✓ Repacked modified sub-partition back​

    8) Repacked new super.img.

    8.1 fill in "img partition size" formular (parameter) to your prepared command below


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


    with the values you obtained in step 7.

    Download & extract : OTATOOLS to /home/username/
    here: **We only want to use "lpmake" from its.

    *** 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...
     chmod +x otatools/bin/lpmake
    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!!***

     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

    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

    lz4 -B6 --content-size super_new.img super_new.img.lz4

    10). Compress the clean vmbeta.img

    Download Clean vbmeta.img from Google

    lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4

    (From Attachment download.)

    11). Down& Extract "" 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
    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.


    >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
    1. extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
    2. create compress one file xxx .tar with 7zip
    3. move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
    4. install magisk.apk on you tab a7 lite
    5. patch the tar file. (with magisk manager)
    6. result magisk-patch file at Tab a7 :-Download folder.

    Recommend: Default R/W GSI " by Nazim"

    My Examples

    If you can't booted "VNDK Lite" variant but want to uses mount Read/Write .
    Part3 -Create CustomAP Tutorial.
    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?
    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. :coffee:
    You misunderstood my post. I am talking about the headphone jack, not Bluetooth but wired headphones.
    I never used Bluetooth with Sony. Used only wired.
    Try to setup GSI here
    -Samsung features
    Enable stereo audio mode
    Enable extra sensor

    -Misc features
    Use alternate way to detect headsets
    Disable audio effects

    and reboot
    So yours doesn't output sound along with the speakers? Anything specific I need to setup at the phh settings? I only know how to fully fix Bluetooth but never managed to do the same for wired audio.
    Try it ..will work . I only uses Bluetooth with Samsung buds 2 only. Sony with wired.

    <<<< Note PE v.415 BUG NOT BOOT FROM MEDIATEK>>>>​

    Easy & Quick RESTORE FROM (Any GSI) BACK TO (STOCK with TWRP)

    !!! If you are already on the A11 (Pure Stock)
    !!! Bootloader unlocked.

    (Forced Restart to Download mode.)--from system failure

    Press key combo ( Power + vol up + vol down ) until blank screen then release power button but still press and hold ( Vol up + Vol down ) + connect USB cable to Computer. ( Download mode)

    0. Download the actual FW A11 with Frija or samfirm or Bifrost, and extract
    it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.

    1. Flash the FW A11
    - BL + AP + CP + CSC ( clean data)
    - put (TWRP + vbmeta_disabler)dot tar in USERDATA slot.
    and click "Start"

    • Default Odin Auto reboot to system.

    But Your device will reboot but it will not boot into system as "vbmeta signature" has changed.

    2. When Auto Boot into TWRP mode from step 1. TAB screen may be black , you must activates it by press power then volumn.

    Insert USB OTG attach mouse. wait for mouse detecting.

    In your TWRP Recovery menu.

    • Go to Advanced > Terminal, type: multidisabler. Click Enter.

    • Go back to Main menu , Wipe > Format Data > type yes.

    Option<<<Install the Magisk.apk with TWRP >>>

    3. Boot---->System


    From your Computer

    1. INSTALL "Android Bootloader interface" Driver. (Download from First page OP)

    Note: very important bootloader driver for used fastboot of the twrp.
    Android Bootloader Interface Drivers are needed for your PC to identify the device connected in Fastboot Mode and hence execute the desired Fastboot Commands.

    2. Copy & paste "Platform tools" to C:/ and copy &paste GSI.img into this folder. ( "vbmeta.img" IF NOT FOUNDED , PLEASE EXTRACTED FROM YOUR AP FILE)

    3. Run Cmd or Open cmd.bat from inside folder platform tools ,

    adb reboot fastboot
    >>>tab will auto reboot to "TWRP fastoot mode" (ignored black screen)

    fastboot devices
    .>>>Output screen will show your tab S/n

    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

    fastboot erase system

    fastboot flash system yourGSI.img
    >>> ignored invalid spare 'system' header magic
    >>> divided PE system image file into parts suitable for write to dynamic tab
    > system partition.

    fastboot -w
    >>>This will also erase your internal storage.

    fastboot reboot recovery
    >>>>>>Booting to TWRP

    from TWRP menu
    wipe --->format data --->yes
    reboot System

    Now meet PE.


    Detail: download OP: !!! Want more detail , please download Ain1.jpg
    Pixel Experience 12.1 v415.1 ( not boot on mediatek )

    >>>>>>>Tools Resources.<<<<<

    Download: (TWRP225 + vbmeta_disabler).tar

    PE+ PixelExperience_Plus_arm64-ab-vndklite-12.1-20220613-UNOFFICIAL.img.xz

    PE PixelExperience_arm64-ab-vndklite-12.1-20220612-UNOFFICIAL.img.xz

    A Magisk module to:
    • Hide tablet taskbar pill (Long press to hide, for Android 12.1+)
    • Fix tablet taskbar height (for PixelExperience 12.1)


    can you upload the vbmeta file that you used?
    I am doing all the steps, but it stays stuck on the TWRP (it is booting again and again to TWRP).

    Is there any other step to do?

    I am trying to install GSI PE for sm-t225n, which pixel experience version should I use?