[Q][GSI][A/AB][arm64] Android Q Developer Preview - Treble-Enabled Device Development A/AB ROMS

EXPERIMENTAL AND MOST LIKELY BROKEN
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Android "Q" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 2019, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
[more stable] Pixel: Ported from Pixel 2 firmware (walleye)
Generic: Ported from Google GSI with gapps
GET UPDATES FROM: https://t.me/androidqgsi​
Requirements :
Treblized device with 8.1 or P vendor
Global Bugs :
VoLTE
Device specific Bugs :
...
Instructions :
for A-Only :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Flash FixZygote.zip
Reboot
for AB :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Reboot
Downloads :
Q Developer Preview
Notes :
Fix gapps: install google play services with "adb install"
if images didn't worked properly post your logs(logcat and console-ramoops) on telegram group i'll come for help : @androidqgsi
Logcat without PC: take /data/local/tmp/logs/log
Enable adb before boot using this command in TWRP:
Linux/mac :
Code:
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Win :
Code:
adb push C:\Users\<userName>\.android\adbkey.pub /data/misc/adb/adb_keys
Donate:
My paypal: https://www.paypal.me/erfanoabdi
Tested on:
give me logs if didn't worked, or donate me a device
Tested by myself:
Moto Z (A-only)
Moto X4 (AB)
Thanks
ENJOY!​

---

[DEV-ONLY] Bug Fixing
NVM
Ah actually this is ridiculous to have bug fixing post here, and i hate my port, real P GSI shouldn't done like this. but anyway this is ported from closed source P and i can point in most popular fixable bugs here...​
by looking into logs(adb logcat -b all) if we see :
1) library "libxxxxxxxxx.so" not found
fix of this error is very simple as you guys all know we just need to put needed lib from system image of base rom in https://github.com/erfanoabdi/P_sem...GSI_Patches/Vendor/P Blobs/POST-sGSI_1/vendor
and zip up "POST sGSI 1" with new libs
Feel free to make pull request new libs in github
2) cannot locate symbol :
for example LG RIL error was like this:
Code:
CANNOT LINK EXECUTABLE "/vendor/bin/hw/rild": cannot locate symbol "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE" referenced by "/vendor/lib64/[email protected]"...
a) here we need to find where is unknown symbol located in 8.1 system image
so in terminal goto system/ and :
Code:
grep -r "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE"
output in this case is :
Code:
Binary file lib/[email protected] matches
Binary file lib64/[email protected] matches
(here you may get long list of blobs, only find and grab needed ones)
b) now just copy libs to vendor and rename them
in this case i renamed [email protected] to [email protected]
***important rule keep string name same as original file only replace one letter (a->W)***
c) and sed renamed lib (in my case) :
Code:
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib/[email protected]"
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib64/[email protected]"
we're almost done here
d) now open POST-sGSI_2 and sed "referenced by" lib from error line in log
like this : https://github.com/erfanoabdi/P_sem...ETA-INF/com/google/android/update-binary#L154
e) and zip up "POST sGSI 1/2" with new libs
Feel free to make pull request new libs/hax in github
3) more...

---

NVM
WIKI : https://github.com/erfanoabdi/P_semiGSI/wiki

---

i hope we get a full GSI eventually one P is released, been waiting a while for this. at least now its semi done, it should be easier to create a full GSI for kirin (aka my H9) and MTK devices.

---

Hi, will it support Honor9?

---

I'm waiting for kirin chipset supported gsi

---

Dumpling- Needs mokee vendor

---

waiting support kirin960 and more?
Sent from my Honor V9 using XDA Labs

---

Jamie_oppo said:
Do you need to be a on a treble rom before flashing this?
Ive got a 5t (dumpling) and flashed the open beta which gave treble. Then flashed a normal custom rom. I tried all the zip at this point and no luck decrypted.
Click to expand...
Click to collapse
Same phone here, I flashed the rom, but it reboots every time to the bootloader...

---

ChristiaanP said:
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
Click to expand...
Click to collapse
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots.

---

Jamie_oppo said:
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots
Click to expand...
Click to collapse
I was on OB 11

---

Awesome... btw Currently booting phones
Mi 5 (gemini)
Redmi 4 Prime (markw)
Redmi 4x (santoni)
Redmi 3s/3x/Prime (land)
Zuk Z2 Plus (z2_plus)
Redmi Note 4 sd (mido) (Tested on PE and Lineage-ex vendors)
Lenovo P2 (kunato)
Redmi Note 5 Pro (whyred) (With mokee vendor)
Mi 6 (sagit) LG V30 (h930)
Redmi 5 Plus (vince) (Tested with cardinal-aosp vendor)
Exynos S9+ (Unstable as **** as its not QCOM)
Redmi 4A (rolex) (crDroid Treble)
OnePlus 5/T (Only one user has reported it to work with proof though)(Mokee trees)

---

Bugs for land or all devices!
- half volte is working (only outgoing call and volume for jio left to fix)
- app opening time is extra
None volte users r really lucky
Also jio4gvoice app is not working

---

Update for DP5
THE MEGAPOST OF NOTES FOR THE P GSI HERE
Wiki page: https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5T and https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5 (Thanks to timocapa)
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
Some things to take into consideration before I followed these steps: I was using OB11 as my daily driver since it's release and I have always been encrypted.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install the latest BETA version of Mqgisk
Click to expand...
Click to collapse
Alternative instructions if you are getting kicked back into the recovery with the display log saying "RescueParty", do all of the above but replace step 11 with the steps below (Thanks to @jelousdogs for his method):
11) Flash POST Zip 1,2 (Dont flash zip 3 Yet)
12) Reboot to system (You will see the rom booting and reboot to recovery suddenly)
13) Flash POST zip 3 in recovery and reboot to system
If this STILL does not work, try this: After completing all of these steps, mount vendor partition in TWRP, then use the TWRP File Manager. Copy the build.prop file from the vendor partition to your internal storage (/sdcard) and move it to your PC via MTP in recovery. Add "persist.sys.disable_rescue=true" (without quotes) to the bottom of the build.prop file you have just copied to your PC. Save and transfer it back to your internal storage. Copy the build.prop from your internal storage to /vendor, replacing the original file. Press on the build.prop file in your /vendor partition and press "chmod". Remove all of the "0000" numbers in the text box and type "0600", then confirm the chmod. Reboot to the OS.
Click to expand...
Click to collapse
DIRTY FLASHING DP5 FROM DP4 (Thanks to timocapa):
1) reboot into TWRP and flash the DP5 GSI.
2) reboot into the OS.
Simple as that.
Click to expand...
Click to collapse
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON (Your stock launcher must be working, i.e. not Force Closing, in order for this to work because the new overview app switcher is part of the stock Pixel Launcher).
- Weird software issues like apps not opening, random FCs, settings going blank? Try a factory reset in TWRP and reboot to see if it has fixed any problems!
Click to expand...
Click to collapse
Known bugs confirmed by a number of 5/t users:
- Potato quality camera, you can use GCam to remedy the problem but expect blue dots in HDRmode (OnePlus problem)
- Front facing camera can only be used in OOS camera (wait for official sources)
Click to expand...
Click to collapse
To get rid of the three persistent notifications:
1) install GMS update (https://www.apkmirror.com/apk/googl...2-8-72-100400-202717283-android-apk-download/)
2) Tap on the blue finishing setup notification and connect to wifi, then force close the pixel setup so it re-appears again
3) Go to settings > accounts > sign into google
4) Tap on the blue notification again and you should be able to go further than "pixel is finishing setup" page.
5) Force stop play store to remove the play store persistent notification
Click to expand...
Click to collapse
Hope this helps other OP5/5T users out there who are having trouble booting this.

---

Can someone tell me if boot this rom on mi mix2s It is able for treble rom i tryied to flash but doesnt boot.

---

Reserved for review

---

Boots

---

Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?

---

unrealmac said:
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
Click to expand...
Click to collapse
No

---

ZeroInfinity said:
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly July 15th is what I used)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) install in-call audio fix
13) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install magisk. I recommend this version as it was the only one working for me: https://drive.google.com/open?id=10LV_j43YUmmHNe0PjE_GNo9kkb-1gAnD
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- If you get kicked into recovery and TWRP's display log shows something about RescueParty, flash the POST 3 zip again and rebooting. You might want to try this 2-3 times if it did not work the first time.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON
Bugs that I have encountered personally but may not affect you, need confirmation:
- MTP isn't working, even with the workaround.
- ADB is detected but when doing "adb devices", it will stay on the "connected" status so you can't issue any adb commands via PC.
- Fingerprint not even detected, no option to enrol in security settings.
To get rid of the three persistent notifications:
1) force stop pixel setup in app settings
2) install GMS update (https://apkdot.com/apk/google-llc/g...s-12-8-66-100400-200774163-beta-041/download)
3) when the blue notification appears again, open it and connect to wifi
4) force stop pixel setup again
5) the next time the notification appears, it should allow you to finally finish the setup
Hope this helps other OP5/5T users out there who are having trouble booting this.
Click to expand...
Click to collapse
Thanks! It worked!