[Samsung Galaxy Tab A7 Lite] tom.android:
*Didn't work with magisk and A12.​

-》Test GSIs with DSU First​

IF It works well

-》 Use Native CustomAP (permanent installation)

If new GSI error​

-》Just Reboot (back to Stock)

First, try to install the VegaBobo App apk only, if that works well for you, nice, keep using it!

!Happy using try to test New GSIs Now :love:🥰😘🤪🤩

-》-》Because of very boring about new installation for testing New GSI A13. ( used too many hours for restored back, too long for create our CustomAP.)​

then find the easy way to....bypass​

A simple app made to help users easily install GSIs via DSU's Android feature.

-》-》This process don't need CustomAP, No TWRP, No Fastboot.)​

Except want to mod System.img by using CustomAP.

-》-》 I will shortly explain Step by Step tutorial here! ​

-》》SAM didn't supported DSU mode with its devices, it is difficult to used DSU together with Stock Sam ROM.

We highly recommend using this app with Stock ROM, some Custom ROM builds may also work fine.

Everyone can sideload New GSI for testing without erasing your based OS Android Firmware. or Used it to be your second OS. (2IN1) OR MORE depending on Storage space.​

***There are some side-effect, but no time to read all Dev documents.

Thank to VegaBobo​

This is not DSU inside your Developer Options​

(DSU implement) then you can choose and select any GSIs ​

( local not in Google Server) that you love but it required your Unlocked Bootloader device.​

->>Pleases read Doucuments of Developer during using my tutorial ​

GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.

A simple app made to help users easily install GSIs via DSU's Android feature. - VegaBobo/DSU-Sideloader

github.com

this video show , i have another GSI running along with Based stock ROM.

More than Dual Boot ​

( GSIs + Stock A11 ROM) ?​

Requirements​

Unlocked Bootloader

VegaBobo DSU Sideloader app

GSI ( A11, A12, A13) only [not lower than version of based AndroidOS.11]

GSI Example will be "ArrowsOS-12.1-arm64_bvN-Unofficial (2.55GB ) extracted .img because there are limited 20-40% rule for working storage.(Storage of Our Tab a7 lite = only 32 GB (may be happy with your 64 GB) , about Stock may occupier about 10 GB with A11).

After this i will calculates restrict storage area for 32 GB.

if you want to test GSI with ROOT , recommend bgS or bvS varient. (if you don't known about "variant bgS , bvS please consult GSI Dev.)

Step

1. Download DSU Sideloader app at https://github.com/VegaBobo/DSU-Sideloader ( New V2.01)

you want below variant.

app-release.apk: DSU Sideloader application, recommended, support both, rooted and unrooted devices.

I will uses Unrooted mode. (clean testing)

LADB ( local adb shell app) >>local-adb shell.zip (my attach)

Not known about LADB look this.

2. If you are working with Tab A7 Lite Android 12 , must downgrade to STOCK Android 11 ( Checking your Bootloader version before downgrading.)

(All variant VegaBobo DSU Not working on Stock A12 of Tab A7 Lite. Test with my SM-T225)​

3. Install ladb.apk > then open Developer options>Wireless debugging >Pair device with piring code , and connected your tab with wifi internet.

-Open multitask 2 windows > one for LADB , the other for Pairing Code

-Pair ladb with (port number and pairing code)

4.Download GSI ( any you like but must obey the rule 20-40% the rest capacity of your storage.)

->My test drive for working booted GSI list is... ( All supported exFAT) ( Some need to mod offline-charging.)

Note: I don't have any problem with FAT32 , just want to fullfill my sd_card.

-》List of Android 12, 12L​

✓ Pixel Experience Plus 12.1 v414

Release Pixel Experience Plus 12.1 v414 · ponces/treble_build_pe

Sync with June sources of PE+ Sync with AOSP 12.1 v414 (thanks @phhusson)

github.com

✓ SparkOS

Gsi_projects - Browse /v415-Aug/SparkOS-12.6-Experimental at SourceForge.net

sourceforge.net

✓ ArrowOS

Gsi_projects - Browse /A12.1/ArrowOS-12.1/19102022 at SourceForge.net

sourceforge.net

✓ crDroid

Gsi_projects - Browse /A12.1/crDroid-8.10/16102022 at SourceForge.net

sourceforge.net

✓ CherishOS

xiaomemeindex.com

✓ SuperiorOS

xiaomemeindex.com

✓ Project Blaze

Release Android 12L · ChonDoit/treble_blaze_patches

CHANGELOG | Initial and latest Release | Fixed Safety Net | Fixed things which exist on source but not on final product (Amazing, right?) | Broken as expected | Enjoy as it or GTFO Why so big image...

github.com

✓ AOSP PHH

Release AOSP 12.1 v415 · phhusson/treble_experimentations

July security patch

github.com

Example

https://xdaforums.com/t/howto-insta...416-plus-final-version.4520063/#post-87742367

LIST of BOOTed BUT NOT SUPPORTED exFAT GSIs

✓ lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.img.xz

Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net

sourceforge.net

-》List of Android 13​

PixelExtended 13

https://sourceforge.net/projects/thegsis/files/PixelExtended/PixelExtended-13-arm64_bgN-UNOFFICIAL.img.xz/download

5. Pre-Setting up DSU.

- install and configure

- must select Enable Unmount SD and Keep screen on during process.

- Operation mode will detected rely on you have root or not. if not it use ADB

View attachment 5753405

Warring about storage restriction ( Let you install anyway but finally fail.)

View attachment 5753407

n in storage Only ) ***Don't used sd-card final process will fail. ( warring for 32GB device)

View attachment 5753413

configured before install GSI ( warning Extract you GSI IMG file to SD CARD for save your internal storage.) (if not) Final process will fail. again.:p(n)

View attachment 5753423

Don't set specific Userdata size if you used big GSI file size.《《 let it be (default 2GB ) ,cause we use to boot testing not for real use.

Let's app auto calculate size for Image size.

-》》 if you plan on using the GSI long term make sure to set your userdata to a reasonable size because your gonna want to install apps and download things.

( App will restrict to uses your storage itself with maximum size ,depened on remain space.)

(if not) Final process will fail. again. :p(n)

Extract GSI Downloaded file. >>>to keep in your sd card.>> in format of IMG (Save your installation time )

Select your GSI for installing by click inside installation box.

Installation process beginning.....show you progress status.

6. How to disconnect your SD-Card during installation process.Why ? How?

(if not ... DSU can't success install but echo..to debuging log... not installed.

(if not ) Final process will fail. again. :p(n)

Very important step , normally it automatical happen.

A lot of failure , no warning about you errors . except final debugging log. bra bra. :ROFLMAO:😅

App will disconnect sd card when finish preparing image file. and reconnect automatically also.

Step ( in this process)

1>Select img file to install.

*Remember to use GSIs compatible with your architeture, vndk implementation..

View attachment 5756193

2 >show you configured before installation.

View attachment 5753883

3>preparing image file (Don't close display or leave out) ** important

ADB: Default operation mode when other modes aren't available

Only prepare selected image to be installed via DSU system-app

Requires adb command to start installation (which will invoke DSU system-app to install the prepared file)

Took your time about 7-10 minutes ( set screen timeout longer + don't turn away from this page.)

View attachment 5753977

If no spaces left

View attachment 5758999

4 >(you will be prompted to run a shell script to invoke DSU installation activity)

- Click button See commands and copy text.

View attachment 5753975

5 >copy command text

- Cluck button Copy text in below box

View attachment 5753885

6 >paste Copy command from 5 to execute with LADB

View attachment 5753897

7> Result of command. Unmount SD Card.

View attachment 5753971

8.>Once installation finishes, Android creates a persistent notification allowing you to boot into "Dynamic System" (GSI installed via DSU), and you can boot into installed GSI, without touching your system partition, or breaking the "real userdata" partition.

View attachment 5753887

THE LAST PROCESS OF INSTALLATION.

( Dynamic system updates) you must waitting till Discard & RSTART BUTTON EMERGED.

Final processing

Select -》 restart button togo into new GSI environment if it can boot.

if not >> DSU will reboot into normal Stock system , (you must discart to delete remain failure system yourself)

Select -》 discard button from noti menu to destroy this system and came back to normal Stock system.

View attachment 5753967

View attachment 5757089

​

7. no need step 4-6​

Not Recommend

-》Shizuku. ok it the same thing .LADB​

View attachment 5756885

Shizuku: When running app with Shizuku (Obtained when Shizuku permission is granted)

Same as ADB, however, it does not require to run any adb command

Support tracking installation progress ¹ ² ³

Support installation diagnostics (if a common error is detected, it may give you useful information) ¹ ³

AFTER INSTALLED​

I will collect storage usage information. because this is one thing that break for GSI Bootable problem beside of GSI Compatible Problem itself.

Maximum used storage.

View attachment 5759005

Step to uses Sticky Mode​

( make Dual Boot OS)​

** Must reboot dynamic system first.

by click restart button of DSU notification. setting up new GSI and click restart DSU for caming back to Based System from notification menu.

1. enable by command

gsi_tool enable

2. Restart device. ( *not uses restart DSU button at notification.) Uses device power-off btn.

3. from now on when we restarts device it will bring you to GSI OS not back to Base OS.

4. How to exit this mode. boot to base OS (by click restart button from DSU update Notification) when you came back to based OS then use this command

gsi_tool disable

Explain in details​

Multiple boot cycles (until discarded) by enabling sticky mode, or have it used for only one boot cycle by disabling sticky mode.​

**The Sticky Mode**​

(This is native features of Google DSU.)

if you don't use the sticky feature, once you reboot the phone/tab it goes back to your regular stock OS or whatever you were running on before and you will lose everything in the GSI that you have not saved to external media/sdcard/cloud.

If you use the sticky feature you can reboot the tab/phone and retain the GSI

installation.

Reboot to Dynamic System. (Stock ROM A11)

use this command on adb:

adb shell gsi_tool enable

or from local adb shell:

gsi_tool enable

or from local rooted shell (eg. Termux on rooted GSI):

su -c 'gsi_tool enable'

Output using command >

gsi_tool enable

View attachment 5753649

When sticky mode is enabled (on base OS), device will always boot into dynamic system, instead of device's original system image.

To disable, use the same command, instead of enable , use disable

such as

gsi_tool disable

Then restart system.(not restart dsu).

Resources:-

Native Google DSU For Developer

--》GSIs can be installed via DSU without root access, using ADB, running some commands, you can read more about installation process here: https://developer.android.com/topic/dsu

Android 13 GSI Download and Install on Your Phone! [Dual boot]

The latest Android 13 Beta is out for Google Pixel devices. In this post, let us see how to download and install Android 13 GSI

shakeuptech.com

Continue..:coffee: