I donno your case btw. Try whatever you can do without data wipes first.
Remember that magisk sometimes cause issues after reflashing stock. If you had it before, then you should have after too.
Remember that magisk sometimes cause issues after reflashing stock. If you had it before, then you should have after too.
Reboot to fastboot "fastboot reboot fastboot" and try again
Note that SmartPack-Kernel Manager is no more in extras section
Last edited:
Yeh forgot that I've removed that recommendation. Re-included it.
@eldho Plz follow installation instruction clearly without trying stuff yourself.
Last edited:
UPDATE
On Android 13 (AOSP-td) some phhusson fixes need to be modifiedAs @bobtear1 faced bluetooth audio output issues, make sure to disable Misc/Force disable A2DP Offload
To fix camcorder, 3nable Misc/Force Enable Cam2API HAL3
Updated OP post configuration too.
Last edited:
I fixed that by enable this Qualcomm/alternate audio policy setting. ThanksI have voice issue in facebook messenger app on Pixel Experience GSI how to fix
Only two steps,
fastboot reboot fastboot & fastboot flash system <gsi.img>*Need to reboot couple times for old dalvik cache to flush out.
*A12->13 not dirty flashable (wiping required).
If you're trying different A13 GSIs, I recommend sticking with Andy's LOS light for now, as it's the only A13 GSI that's patched everything to daily drive.
Last edited:
Sure. But there are some other GSIs that currently don't load overlays, as they still haven't got overlay matching patches. So you might get brightness dimming & status bar offsets without it.
Here's the report for the current GSI development state. This is to keep this thread alive.
MERRY JINGLE CHRISTMAS
- Phhusson now moved from his personal builds to CI/CD builds (testing, automated) which is now called TrebleDroid (AOSP-TD).
- But he still hasn't decided to ship secure builds yet (which help pass CTS & magisk compatibility)
- Lot of AOSP-TD based builds have been released by many developers/builders, which some also happened to have secure builds. Links are in the OP.
- A13 forks are still in development stage. So you might experience couple of bugs here & there.
- As of now, the last stable A12 builds held to November sec patch. Beware if you still on Nov patch, since it has a serious security vulnerability (CVE-2022-20465) that allows anyone to unlock your encrypted device through sim PUK reset, which has been patched on December sec patch.
- Andy's maintaining his own phh treble patchset builds which he calls LineageOS Light. It might or might not be dirty flashable over other TD based builds.
- The current overlay state is the same as of last year. If anyone have any requests regarding overlay modification, plz do.
android_13.0.0_r14 ci-20221219 (system-td-arm64-ab-vndklite-vanilla), securized, magisk rooted, microg moduled & passing safety net via kdrag0n fix & redfin props.MERRY JINGLE CHRISTMAS 
Last edited:
Can't either
Attachments
can i use yours without first step of flashing stock firmware__ im using custom rom PE 13 but wanna use gsi for first time
GSI uses vendor & vendor_boot partitions of stock. ROMs modify those so you can't boot up with em.
What could be the reasons you're trying gsis? If they're the ones from OP, then you might try.
the reason is i never try a gsi and want to lear how to install on any phone, and im a bored of custom rom, i always love LO and want to try as my daily drive , cuestion what means OP
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯
Yes. But this thread exists due to the following reasons:
- You don't wanna fear about devs stop shipping updates.
- You don't wanna re-flash your custom recovery / kernel after each update.
- Unlike some ROMs, no clean flashes necessary after you update.
- You don't wanna be a flashoholic / beta tester of a ROM maintainer.
- GSIs are like Linux Distros. Flexible, hasslefree & minimal.
- All GSIs support signature spoofing out of the box.
- ROM updates modify all the partitions (boot, recovery, kernel, system, vendor, etc). A GSI update is just a system partition that updates "only" the system, that runs upon stock firmware.
- ROMs might pass safetynet out of the box. But for GSIs, you must root & use magisk modules to achieve that.
- You can't flash gapps on vanilla GSIs, as you do on vanilla ROMs. You must use bgS/bgN GSI variants.
- For now, GSIs have to be installed via fastbootd, as recoveries still yet to support logical partitions. So you need computer available when you update or change them.
PREREQUISITES
- Stock ROM (fastboot)
- MicroG (for vanilla)
- vbmeta.img (from google)
- SafetyNet Fix (thanks to kdrag0n)
- TrebleDroid (thanks to phhusson)
- Pixel Experience (thanks to ponces)
- More to test from here
INSTALLATION
NOTE:I'm assuming you've already unlocked bootloader, backed up your data & know all the technical consequences of flashing & modding.
- Download / extract all prerequisites in one place.
- From stock firmware, edit
flash_all_except_data_storage.bat/sh& modify last line tofastboot reboot fastboot - Enter fastboot mode
{vol_down+power},connect to PC & flash firmware using above edited script. When device enters fastbootd, from terminal/cmd execute : fastboot erase userdatafastboot flash vbmeta vbmeta.imgfastboot flash system <gsi-file.img>(ignore INVALID SPARSE warning)fastboot reboot& make sure your GSI boots up. Power off & return to fastboot again.fastboot boot <twrp-file.img>, head to Advanced & run flash current TWRP to make recovery persistent across reboots.- Finally Magisk (for root, safetynet fix, additional modding, etc).
BUG_1:Don't touch the screen while booting to avoid touch issues after you boot (this bug occurs only on custom kernels).
BUG_2:Don't set up password on startup wizard. Instead, set it up later & then disable Android Setup app if it exists. Else it'll crash fingerprint settings.
UPDATE / DIRTY FLASH HOW ?
fastboot reboot fastbootfastboot flash system <new-gsi.img>& reboot twice
POST CONFIGURATION
- Enable the following Settings > Phh Treble Settings:
- Qualcomm features / Use alternate camera profile & audio policy
- Misc features / Disable audio effects
- IMS features / Force the presense of 4G calling & Install IMS Apk for Qualcomm vendor from notification panel.
- Setup magisk, hide the app, enable Zygisk & Enforce Denylist.
- Use SafetyNet-Fix module to pass safetynet. Still won't pass? Try Pixel-Props (redfin) that ensures fingerprinting.
- microG module if you chose vanilla variant (Safetynet works. Most of the banking apps work except gpay).
NOTE:Flash custom kernels only through your custom recovery. Flashing through kernel managers (FKM, SPKM, etc) is not suggested.
MAGISK NOT WORKING ?
In this case, the GSI you selected isn't securized (comes with su bydefault). Through TWRP, do
mount -o rw /dev/block/mapper/system_a /system_rootfrom terminal-
Code:
rm /system_root/system/xbin/su rm /system_root/system/bin/phh-su rm /system_root/system/etc/init/su.rc - Or instead, you can use recovery's file manager to delete the above files. Then reboot.
EXTRAS
My Recommendations for great experience:
- SPKM to set
GPU > GPU Governor > Performance(fixes UI lags) - Lawnchair / Quickswitch for launcher customization with gesture navigation support.
- Lineage Dialer for built-in call recording (push into
/product/priv-app/Dialer/Dialer.apk). - ANXCam for MIUI camera's post processing.
- GCam for google camera's post processing.
- Aurora Store / Droid for microg users.
- Kiwi Browser for chrome extensions support.
- Migrate to backup / restore user apps & data, incase you lose your setup.
3
I don't really care. Discuss anything mate. This thread is all about gsi support for community.it is okay for us to give review about the GSI that we have been tested ? or better on the other thread ? asking for an opinion here
The more you guys talk, the more better.
(just dont private msg. I want all discussions to be public
)3Here's the report for the current GSI development state. This is to keep this thread alive.
- Phhusson now moved from his personal builds to CI/CD builds (testing, automated) which is now called TrebleDroid (AOSP-TD).
- But he still hasn't decided to ship secure builds yet (which help pass CTS & magisk compatibility)
- Lot of AOSP-TD based builds have been released by many developers/builders, which some also happened to have secure builds. Links are in the OP.
- A13 forks are still in development stage. So you might experience couple of bugs here & there.
- As of now, the last stable A12 builds held to November sec patch. Beware if you still on Nov patch, since it has a serious security vulnerability (CVE-2022-20465) that allows anyone to unlock your encrypted device through sim PUK reset, which has been patched on December sec patch.
- Andy's maintaining his own phh treble patchset builds which he calls LineageOS Light. It might or might not be dirty flashable over other TD based builds.
- The current overlay state is the same as of last year. If anyone have any requests regarding overlay modification, plz do.
android_13.0.0_r14 ci-20221219(system-td-arm64-ab-vndklite-vanilla), securized, magisk rooted, microg moduled & passing safety net via kdrag0n fix & redfin props.
MERRY JINGLE CHRISTMAS
3
If you want to gain more space (≈ 200mb) in system you can delete 2 folders safely without problems :
/system/system_ext/apex/com.android.vndk.v28/
and
/system/system_ext/apex/com.android.vndk.v29/
Already did it in DSSI builds without issues.
