I tested it on the G7 lake, automatic brightness, nfc, facial unlocking don't working
Maybe you should use either erfans newer builds, or quack phhtreble, probably has bettaer supportI tested it on the G7 lake, automatic brightness, nfc, facial unlocking don't working
Maybe you should use either erfans newer builds, or quack phhtreble, probably has bettaer support
@erfanoabdi,
Thanks to you & simonsmh - I was able to boot Android R Developer preview (Pixel-AB-R-20200222-ErfanGSI.img-0514) on my OP3. No Wi-Fi or Mobile connection. To be expected from the first DP.
:highfive::good::good::highfive::
hi.
i have the oneplus 6t can you give me the link to the guide you followed?
is your device a/b?
I flash 3 gsi img but without luck to boot it on realme 2 rmx1809...it either stuck on boot logo or just dosent boot...any tips or guide
Why are you using old betas on the 3a?it seems that i can't install some kind of apps , is that a storage problem ?? my device pixel 3a
Why are you using old betas on the 3a?
You know that official Android Q is avaliable for the 3a and 3aXL?
Oh okay
How did you flash it ??
How did you flash it ??
Did your device get the official beta ?
Because I tried to flash latest 11 GSI on my phone's Q's boot and vendor. It didn't boot.
Can you tell me how did you do it ??
Oh. You flashed erfan's port. That's why. I was trying to boot Google's Android 11 beta 2 GSI.install Q july patch , then :
fastboot erase system
fastboot flash system Generic-erfan.img
fastboot -w
fastboot reboot
/*
* 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.
*/
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb push C:\Users\<userName>\.android\adbkey.pub /data/misc/adb/adb_keys
CANNOT LINK EXECUTABLE "/vendor/bin/hw/rild": cannot locate symbol "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE" referenced by "/vendor/lib64/[email protected]"...
grep -r "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE"
Binary file lib/[email protected] matches
Binary file lib64/[email protected] matches
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]"
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
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.
1) reboot into TWRP and flash the DP5 GSI.
2) reboot into the OS.
Simple as that.
Known bugs confirmed by a number of 5/t users:- 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!
- 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)
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