MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA!Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT!
What does not work?Fingerprint
face unlock
native camera app(Use gcam)
no notification slider
no modular refresh rate
no auto brightness(Not yet will be implemented)
no 5g(no worry no one uses it yet so)
maybe more let me know if you found a solution so i can add it under this post
I'm working on a overlay to fix some things for this device
What do I need?A Unlocked bootloader Follow below.
Stock zip download this with oxygen updater(enable advanced mode and download your version)
Oneplus drivers Here
Latest Fastboot Enhance Here
And a GSI of choice you can get Here or Here dot os works good with this phone
Choose AB GSI and you don't need slim(Low system volume device's) or vndklite(For older device's)
Unzip and put all the things in a folder.
Start with installing the Usb drivers
and connection device to your computer. (no need to disconnect till your set)
If your in windows use
Code:
cmd
Unlocking Bootloader (This will wipe device)
Go to Settings/About device/Version and tap the build number/version until you see your already a developer.
Spoiler: screen
{
"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"
}
Go to Settings/Additional settings/Developer options and enable OEM unlocking
Spoiler: screen
On your Computer open fastboot tool folder and open a terminal there and type
adb devices
Accept on your phone
adb reboot bootloader
wait till boot
fastboot flashing unlock
device will ask you to confirm if you want to unlock Confirm this
Spoiler: screen
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Spoiler: screen
Preping device for GSIOn your computer open fastboot tool folder and open a terminal there and type
adb reboot bootloader
Wait till boot
fastboot reboot fastboot
you will see a screen with Chinese and languages as options don't do anything here.
On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
than click on your device and go to partitions
Spoiler: screen
To make space for our new OS we need to make space so we are going to remove the old firmware left after update's
In the petitions tab type -cow and delete these volume's, Yes all volumes this will not affect your device
Spoiler: screen
Skip all above if you already on a GSIThe flashing of the GSI Make sure your GSI is a .img Unzip if its a xz/zip file
Now open fastboot tools folder and start a terminal there
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system Gsi.img
Spoiler: screen
wait till finished than on the phone click English and Format data and wait till it boots.
Spoiler: Pixel experience
Spoiler: CherishOS
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader
fastboot boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
reserve
Back to stock
Very simple aslong you dont mess around with other partitions
Open the fastboot tools folder and start a terminal.
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system
fastboot flash system THE_SYSTEM_IMG_BACKUP_YOU_EXTRACTED
fastboot flash vbmeta vbmeta.img(Will remove gsi flash ability)
fastboot flash boot boot.img(Will remove root)
wait till finished than on the phone click English and Format data and wait till it boots. and your back to ****ty ColorOs
Absolutely what we need
Have anyone tried GSI on OP 10 T. Wanted to get a sense of this before I jump on.
Good man
I'll flash in the morning.
Cheers.
dladz said:
Good man
I'll flash in the morning.
Cheers.
Click to expand...
Click to collapse
Which one you took? Working fine so far?
I'm gonna make a overlay for our device this may box some issues and bugs
MrScarl3t said:
I'm gonna make a overlay for our device this may box some issues and bugs
Click to expand...
Click to collapse
Overlay?
lovesetcpu said:
Which one you took? Working fine so far?
Click to expand...
Click to collapse
I actually updated to beta 2, I couldn't help myself..tbh it's really good I'd recommend it.
Proximity sensor doesn't work for me or auto brightness but everything else is superb.. you can update directly from 12 to 13 using the update APK..
If you check the beta update thread on xda in this 10 pro section and you'll see it.. look for post #55
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
dladz said:
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
Click to expand...
Click to collapse
Honestly it was pretty good overall. As mentioned in OP, finger print, DTW, face unlock, auto brightness, VOLTE (my requirement as my network works on that for voice), doesn't work.
Besides these fairly good, passes safety net without root, (may pass even with it), fast charging ( didn't exactly time it or measure, but was fairly close to the stock ultra fast charging experience), and the beautiful fluid AOSP experience, 120 hz rr and the performance was somewhat better than stock, at least for gaming. Got 2800+ on 3d mark extreme and got 95% stability on the stress test. FYI - OP 10 T
alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
MrScarl3t said:
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
Click to expand...
Click to collapse
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
alanzaki073 said:
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
Click to expand...
Click to collapse
The name is org.codeaurora.ims don't know where it's located
I wish that it became more stable!
I can't stand with ColorOS 13 [OxygenOS 13] !!
Any luck on VOLTE?
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
yo-less said:
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
Click to expand...
Click to collapse
How was the experience?
Why you back to OxygenOS?
Related
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
This is f*cking awesome. Thank you for your efforts. Will install asap and bring some feedback.
Is it working ? Any custom roms then ?
Please provide custom ROM the official ROM is no less than terrible and bad.
Finally compiled TWRP with decryption support, added in first post
hammad5507 said:
Please provide custom ROM the official ROM is no less than terrible and bad.
Click to expand...
Click to collapse
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
descarao81 said:
I recommend the one made by Francko76.
Click to expand...
Click to collapse
Can you share a link to the Roms you mentioned ?
thanks
descarao81 said:
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
Click to expand...
Click to collapse
benjieb said:
Can you share a link to the Roms you mentioned ?
thanks
Click to expand...
Click to collapse
what rom is Francko´s build? if you have a link, can you share it please?
Sorry to ask, is this vbmeta patched only for this device or can i installed in others device ?
Please share the links
Please share links for the Franko's build.
and also is there any custom pie rom available??
Pls share if any.. I am very unsatisfied with the global rom. Pls help.
@alexei sir, can you make custom kernel or give way to our devices gets exfat support ?
this is twrp for Lenovo Z6 (not pro) ?
geepnozeex said:
this is twrp for Lenovo Z6 (not pro) ?
Click to expand...
Click to collapse
No this is Twrp for Z6 Pro ( L78051 )
Very tempted to get this phone... has anyone try with phh’s GSI? Does under screen scanner works?
alexeei said:
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
Click to expand...
Click to collapse
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
threeeye said:
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
Click to expand...
Click to collapse
NVM, just updated the adb tools and now everything is good
Restore stock bootloader?
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
benjieb said:
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
Click to expand...
Click to collapse
Here is the "The boot loader is unlocked..." screen:
{
"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"
}
And here's the boot loader:
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Do you try flash qfil rom after lock bootloader?
Well I'm sure I rooted successfully... The latest one V5.13 Android11 with Magisk V22.0 but I don't know the problems I faced screenshots only those are twrp one and everything is fine.... Only problem I face is Those encrypted language in twrp even I flashed DM-Verity too...but not works anyways in phone internal storage and in OTG usb storage showing properly...names & folders.any coz I want to slove those encrypted things for my future!
Spoiler
{
"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"
}
{Mod edit: Spoiler added for better scrolling experience}
NubiaNinja said:
Well I'm sure I rooted successfully... The latest one V5.13 Android11 with Magisk V22.0 but I don't know the problems I faced screenshots only those are twrp one and everything is fine.... Only problem I face is Those encrypted language in twrp even I flashed DM-Verity too...but not works anyways in phone internal storage and in OTG usb storage showing properly...names & folders.any coz I want to slove those encrypted things for my future!View attachment 5269469View attachment 5269471View attachment 5269473View attachment 5269475View attachment 5269475View attachment 5269477
Click to expand...
Click to collapse
Use adb command try to unlock bootloader
1. adb reboot bootloader
2. fastboot oem nubia_unlock NUBIA_NX629J
3. Reboot device and after that u will see warning bootloader have been unlocked
4. Done. Try entering twrp and check if the file encrypted.
Cynexc said:
Use adb command try to unlock bootloader
1. adb reboot bootloader
2. fastboot oem nubia_unlock NUBIA_NX629J
3. Reboot device and after that u will see warning bootloader have been unlocked
4. Done. Try entering twrp and check if the file encrypted.
Click to expand...
Click to collapse
After entering twrp u have to wipe internal storage partition. Make sure u backup important files.
You need to wipe internal storage. Is auto rotate working for you on 5.13 rom?
Yes it's working now I'm not encrypted anymore feel free to use Twrp.... Thankyou @Cynexc @danishajaz and yes my auto rotation working in every rom cn global even gsi treble roms too..even I find something like this is gsi treble rom Rotation angles idk much about it but ur problem is everywhere I saw ur auto rotation hope this will help u..gsi treble rom!I'm using right now..
FYI, i was using v5.13 ROM as daily driver, but gyro not working.
What i was doin Wiping all of the things except system in twrp.
No clue how to fixing that.
never00miss said:
FYI, i was using v5.13 ROM as daily driver, but gyro not working.
What i was doin Wiping all of the things except system in twrp.
No clue how to fixing that.
Click to expand...
Click to collapse
So after wiping system did gyro start working?
danishajaz said:
So after wiping system did gyro start working?
Click to expand...
Click to collapse
Wiping system = wiping your OS, not only gyro is not working, but your device too
never00miss said:
Wiping system = wiping your OS, not only gyro is not working, but your device too
Click to expand...
Click to collapse
I'm sure os can be installed again in any case
Hi, I am naveen from India..
Finally, @RZaR2001 helped me to upgrade my NRM3 from android 9 to android 11, and i am very thankful to him for guiding me and really enjoying this Upgrade as well..
Now the Major issue where i need help-
Screen mirroring is not working
Wireless projection option is there on notification bar's menu
But not working
I dont know why
Has anyone tried ever to mirror his android screen after upgrading?
And find a loophole in this android 11 regarding screen mirroring
If u go to settings and scrolldown you wont find any option named CONNECTION PREFERENCE
But If you go and search CAST in settings SEARCH BAR, u will get that option under settings/connection preference/cast/cast
I selected that and finally atleast i was able see that screencast option to enable from there and can see my samsung tv there and unfortunately my tv says RED MAGIC 3 IS UNABLE TO CONNECT. TRY CONNECTING YOUR MOBILE INSTEAD.
Seems like, default miracast or screencast has been disabled in chinese rom, They have their own WIRELESS PROJECTION APP which never finds my Tv, and shows the same msg "no device found nearby, try installing lebo screen projection client on tv".
But yes, i can screencast YOUTUBE directly from the app, there it gets connected so don't know how to get this sorted out..
If anyone of you has faced these issue or have any solutions against that, please guide..
NubiaNinja said:
Yes it's working now I'm not encrypted anymore feel free to use Twrp.... Thankyou @Cynexc @danishajaz and yes my auto rotation working in every rom cn global even gsi treble roms too..even I find something like this is gsi treble rom Rotation angles idk much about it but ur problem is everywhere I saw ur auto rotation hope this will help u..gsi treble rom!I'm using right now..
Click to expand...
Click to collapse
Is that legion rom gsi? Fan and triggers work?
NubiaNinja said:
Well I'm sure I rooted successfully... The latest one V5.13 Android11 with Magisk V22.0 but I don't know the problems I faced screenshots only those are twrp one and everything is fine.... Only problem I face is Those encrypted language in twrp even I flashed DM-Verity too...but not works anyways in phone internal storage and in OTG usb storage showing properly...names & folders.any coz I want to slove those encrypted things for my future!
Spoiler
View attachment 5269469View attachment 5269471View attachment 5269473View attachment 5269475View attachment 5269475View attachment 5269477
{Mod edit: Spoiler added for better scrolling experience}
Click to expand...
Click to collapse
Can you share the files you used to root and twrp for a11 am on cn 5.16 not sure what I need I need the right Gapps to.
{
"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"
}
PixelExperience for Pixel 3 / 3 XL [blueline/crosshatch]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website (blueline)
Download from PixelExperience website (crosshatch)
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 12
Security patch level: December 2021
Build author/Device Maintainer: ReallySnow
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Installed on my crosshatch, running great so far
Many thanks for bring PE to Pixel 3 XL.
Hopefully it will be official.
what's the difference with the android version we officially got? It would be great for the next updates that will not be on the pixel 3
Gustavo_s said:
Installed on my crosshatch, running great so far
Click to expand...
Click to collapse
Hi Gus,
is the VoLTE & VoWiFi working ???
In my country Pixel is not in the list of the supported device from the carrier, therefore i am unable to get them working. But i have Mi A1 with official PE 11 (no root) both volte & vowifi work like a charm.
Since Google had stopped updating pixel 3 xl from Nov 2021 might as well go for the custom rom.
edkmho said:
Hi Gus,
is the VoLTE & VoWiFi working ???
In my country Pixel is not in the list of the supported device from the carrier, therefore i am unable to get them working. But i have Mi A1 with official PE 11 (no root) both volte & vowifi work like a charm.
Since Google had stopped updating pixel 3 xl from Nov 2021 might as well go for the custom rom.
Click to expand...
Click to collapse
My carrier doesn't support VoLTE too, so it never worked for me even on stock rom
Gustavo_s said:
My carrier doesn't support VoLTE too, so it never worked for me even on stock rom
Click to expand...
Click to collapse
Thanks for your respond.
Actually my carrier support VoLTE & VoWifi but not the phone model. As mentioned when using the same sim card with Mi A1 with PE 11 it works.
Gustavo_s said:
Installed on my crosshatch, running great so far
Click to expand...
Click to collapse
How do you compare this with stock on crosshatch?
Sorry for asking this as it seems I should probably a already know but....
What is the procedure for fishing this?
Is it a fastboot installation method?
Or does it require a lineage boot image?
Sorry if these questions are noobish.
shaemasa said:
How do you compare this with stock on crosshatch?
Click to expand...
Click to collapse
Same features, a bit smoother and better memory management. Most important for me is up to date security patches.
rhewins2268 said:
Sorry for asking this as it seems I should probably a already know but....
What is the procedure for fishing this?
Is it a fastboot installation method?
Or does it require a lineage boot image?
Sorry if these questions are noobish.
Click to expand...
Click to collapse
download latest twrp for crosshatch
unlock your bootloader
in your PC using fastboot: fastboot boot twrp.img
in twrp, select adb sideload, connect phone to your PC
in your PC using adb: adb sideload lineage.zip
do not reboot, in twrp do a factory reset (it was probably already reset when unlocking bootloader)
reboot
done
BTW safetynet and cts are ok using latest magisk stable, selecting all apps on magisk hide allowed me to use banking apps and microsoft intune portal
Good to hear that and how about the bugs: notification shade and notification dismiss? Are you able to dismiss notifications with single click? I know those do exist in official A12 (stock) but since you have been in to this, I thought ask about those bugs.
One more question...again i believe i know the answer....
Should I be on the latest firmware 12.0.0 (SP1A.210812.015, Oct 2021)?
shaemasa said:
Good to hear that and how about the bugs: notification shade and notification dismiss? Are you able to dismiss notifications with single click? I know those do exist in official A12 (stock) but since you have been in to this, I thought ask about those bugs.
Click to expand...
Click to collapse
There is a "dismiss all" button in the notification shade. On my pixel 4a on stock rom the notification shade sometimes gets bugged colors, i haven't noticed this issue yet on 3XL with this ROM. Might be because i haven't used it enough for the bug to show up.
rhewins2268 said:
One more question...again i believe i know the answer....
Should I be on the latest firmware 12.0.0 (SP1A.210812.015, Oct 2021)?
Click to expand...
Click to collapse
yeah i think so, flash the latest stock then this one
Gustavo_s said:
There is a "dismiss all" button in the notification shade. On my pixel 4a on stock rom the notification shade sometimes gets bugged colors, i haven't noticed this issue yet on 3XL with this ROM. Might be because i haven't used it enough for the bug to show up.
yeah i think so, flash the latest stock then this one
Click to expand...
Click to collapse
Is it daily drivable and what about the SOT?
So i tried getting Twrp to boot but it just kept hanging on the twrp splash screen. So i downloaded the latest LOS 18.1 recovery and flashed it. Then rebooted into LOS recovery. Did a factory reset and ADB sideloaded this rom and it seems to have worked.
Great job! Love this rom! Definately daily drivable! Safetynet passes out of the box and still after magisk root. (Flashed Magisk v23.0 23000 zip in recovery)
Cool!
Thank you for PixelExperience build based on Android 12!
This error was later fixed. Skip down to the numbered list in this post to see method to switch from stock A12 and perform upgrades.
Error 21 when sideloading the zip. TWRP also would not proceed past splash screen and other thread sources suggested recovery. Method I just tried:
Recovery mode (Power + Volume down to enter Fastboot mode - volume keys to scroll and power button to select Recovery Mode - Power + Volume up (reovery mode shows after approx 10 seconds hold)) > Apply update from ADB > "adb sideload PixelExperience.zip"
Running A12 already via OTA so attempting this really for the security patches. TWRP 3.5.2.10-0-crosshatch.img. ADB 31.0.3-7562133.
Could I just dirty flash using another (earlier) verion of TWRP or do I actually need to wipe data/factory reset in recovery mode? Or am I missing something else entirely?
EDIT: after all the helpful responses from others here, this is what got this ROM installed on my crosshatch device which was previously running A12 factory image SP1A.210812.015.
1. adb reboot bootloader (I did this via commandline. It is hardware accessible too but not what I used this successful time)
2. fastboot flash boot --slot b lineage-18.1-XXXX.img (this step not required when later updating PE)
3. on the device used up/down hardware keys to switch to recovery mode and select the option using the power key
4. device then shows android laying on its back and required power + up key held down (after several seconds release the up key) to enter recovery mode. This in particular required several attempts before the lineage recovery kicked in. It's jazzy purple so was quick to spot when successful. (this step not required when later updating PE)
5. factory reset device - other users mention not doing this is problematic and was also my experience. You won't be sad for long trust me. (this step not required when later updating PE)
6. update via adb on device recovery mode (when later updating PE it will have switched to its own recovery instead)
7. back in computer commandline "adb sideload PixelExperience-XXXX.zip"
8. (this step is no issue when simply upgrading PE) at around 47% progress the device then complained about signature being unsigned and that the install would be a downgrade. Had to do this to gain ADB sideload access. Switched answer to YES for both. Progress % didn't change but eventualy 2/2 steps completed. I had to do this step several times too. No idea why but across all devices over the years it's a shared experience when installing a new ROM. No gain with pain!
9. final step on the device was to remove the USB cable and choose to restart via the lineage recovery menu (or if upgrading PE it's of course "Reboot system now") - if you updated check the new security patch date in settings >> about phone >> android version >> note the android security update details.
So far everything working but just neeed to understand getting Magisk back for my workflow. EDIT: Got magisk working using the payload-dumper-go method as outlined here https://www.xda-developers.com/how-to-install-magisk/
I used the l later LOS
rossmurray said:
Error 21 when sideloading the zip. TWRP also would not proceed past splash screen and other thread sources suggested recovery. Method I just tried:
Recovery mode (Power + Volume down to enter Fastboot mode - volume keys to scroll and power button to select Recovery Mode - Power + Volume up (reovery mode shows after approx 10 seconds hold)) > Apply update from ADB > "adb sideload PixelExperience.zip"
Running A12 already via OTA so attempting this really for the security patches. TWRP 3.5.2.10-0-crosshatch.img. ADB 31.0.3-7562133.
Could I just dirty flash using another (earlier) verion of TWRP or do I actually need to wipe data/factory reset in recovery mode? Or am I missing something else entirely?
Click to expand...
Click to collapse
I used the latest LOS 18.1 recovery.
Thank you!
Alright guys,
I'm not a developer, nor am I a tester. I was just looking for something AOSP. While I found what I was looking for, I was not completely satisfied. Though the following GSI rom is extremely stable.
So, what I'm going to do in this thread is, document my process and how I got it working. I will however revert back to miui after documenting it. So cannot help you further with any issues and you're on your own.
Now let me start by stating my requirements, which will explain why I went with Android 11 rather than 12.
Requirements that must be satisfied:
1. Daily Driver
2. Stable Camera
3. No Throttling
4. No general issues with sensors
5. Sound should works great
6. Customization goodies like those of crdroid/rr/havoc (important)
7. Wifi,Bluetooth,mobiledata should all be working smoothly including 5G
8. Vibration should work
9. Good battery life
10. No over heating
11. TWRP support for android 11
Mind you, the GSI rom out of the box was ticking everything above. Which got me excited, so I quickly transferred the necessary data.
{
"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"
}
So it was completely stock Pixel Experience Android 11. Now the reason I chose this over android 12 was so I could use GravityBox along with this. Once the root was up and running, quickly installed Gravitybox. This allowed me to customize a number of things which I really needed:
Once all the customizations were done, I was getting closer to my final goals. Also, the gravitybox customizations did not cause any issues and were super stable with no heating issues etc.
I downloaded sensor testing apps, went through each and every single setting and option in the phone and figured all the major problems that I could see.
Problems in the rom:
1. Whatsapp call has echo (for the other person) when you use it on speaker phone
2. Fingerprint Sensor stays awake all the time, which means, if you touch it accidentally, it will get unlocked/wake the screen.
3. Viper4android does not seem to be getting installed but this seems more of an v4a issue.
4. Yup, thats about it, literally everything else works perfectly.
Links:
MIUI 12.5.10 [Global]: https://bigota.d.miui.com/V12.5.10.0.RKDMIXM/miui_VILIGlobal_V12.5.10.0.RKDMIXM_c6ffabfb05_11.0.zip
vbmeta file: [ Attached under the post ]
Pixel Experience GSI: https://github.com/ponces/treble_bu...ence_arm64-ab-11.0-20211009-UNOFFICIAL.img.xz
TWRP Android 11: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download
LSPosed Zygisk Build: https://github.com/LSPosed/LSPosed/releases/download/v1.7.2/LSPosed-v1.7.2-6379-zygisk-release.zip
Gravitybox: https://repo.xposed.info/module/com.ceco.r.gravitybox
Installation:
The install is similar to what @bhammler mentioned in his post, so I will just copy paste the instructions.
Here are my new steps:
1. fastboot flash_all vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
2. let it reboot to the setup screen and turn it off
3. fastboot boot twrp.img (no need to install)
4. update through twrp to miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12.0.zip [ Use miui 12.5.10 fastboot instead ]
5. it shows some errors, but it's still booting up to the setup screen. Turn off
6. From now on: everything in FastbootD (fastboot reboot fastboot)
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (see attached extracted vbmeta from MIUI 13) [ Extract from miui 12.5.10 (attached below) ]
8. fastboot erase system
9. fastboot flash system PixelExperience_arm64-ab-slim-12.0-20220221-UNOFFICIAL.img [ pixel experience android 11 instead ]
10. fastboot reboot recovery
11. wipe data in Mi Recovery
12. reboot and done
Click to expand...
Click to collapse
After doing the above process, we can further go ahead and install twrp as well for which the guide from @TheRomFan can be followed:
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
Click to expand...
Click to collapse
1. Once the twrp is installed as well. Go ahead and root the system as you would normally. (make sure to reboot into system after flashing twrp to check if everything is going good).
2. Flash lsposed zygisk build.
3. install Gravitybox for R.
Conclusion:
Overall, the experience for daily driver is extremely stable and with no issues. But unfortunately, the ocd maniac inside me is annoyed by the fingerprint waking up issue. So i will be going back to miui and patiently wait.
But if you guys dont mind that issue, the entire process i did is neatly presented above. And this can be used as a really good daily driver!
Hopefully this post helped.
Thats all, enjoy your phone!
~ NoUsernameSorry
Great thanks for that. I was wondering, how is the infamous xiaomi proximity sensor behaves in that rom? Did you tested?
Pichulec said:
Great thanks for that. I was wondering, how is the infamous xiaomi proximity sensor behaves in that rom? Did you tested?
Click to expand...
Click to collapse
It seems to work fine from my testing. With gravitybox, you have further proximity settings you can tinker with, so thats an advantage.
nousernamesorry said:
It seems to work fine from my testing. With gravitybox, you have further proximity settings you can tinker with, so thats an advantage.
Click to expand...
Click to collapse
Can you shed some light on gravity box? Never heard about it.
Pichulec said:
Can you shed some light on gravity box? Never heard about it.
Click to expand...
Click to collapse
Its basically a collection of tweaks for the rom.
Hello, I would like to install recently I learned to install by adb this gsi method is the same? I have the 11t pro
Follow instruction and tested the GSI.
First thing I noticed, that there is no 120hz even under phh tweak setting, only forced-60hz.
Secondly, DT2W is not working either.
Else, everything else seems good. The rom is extremely lightweight.
When you say stable Camera do all 3 camera's work?
How is battery life in general? How much SOT do you get on average every day? Does the device heat up at all compared to stock?
lethallunatic said:
When you say stable Camera do all 3 camera's work?
How is battery life in general? How much SOT do you get on average every day? Does the device heat up at all compared to stock?
Click to expand...
Click to collapse
Everything is absolutely stable. You need the gcam xml config to use all the three cameras. You can find that in the telegram group.
Battery life is similar, if not better. Like i mentioned. I am not using it, due to minor issues I was having. If you dont mind those issues, its stable and good as a daily driver.
Please read the thread, theres no heating as well. All the information is mentioned in the thread.
Trocxel said:
Hello, I would like to install recently I learned to install by adb this gsi method is the same? I have the 11t pro
Click to expand...
Click to collapse
If you follow the steps correctly, you should be good.
Does this have a working OTA?
gsus said:
Does this have a working OTA?
Click to expand...
Click to collapse
no this is the last android 11 release
Few things to keep in mind before starting the process:
If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.
You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.
[English] Written Instructions:
(Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
[Chinese] Written Instructions:
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
Video Tutorial:
Downloads Links:
80W_C.15_OOS_Android13
150W_C.15_OOS_Android13
You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.
Download link for ColorOS:
150W_ColorOS_C.17_Android13
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 3.
If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
I
6cdh said:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-com partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 2.
If you completed step 2, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
Click to expand...
Click to collapse
In the Step #7, it should be *-cow partitions, No?
yashaswee1708 said:
I
In the Step #7, it should be *-cow partitions, No?
Click to expand...
Click to collapse
Ah, yes, it's a typo. edited.
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.
{
"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"
}
sSjBlueVN197 said:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
Click to expand...
Click to collapse
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
yashaswee1708 said:
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
Click to expand...
Click to collapse
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
sSjBlueVN197 said:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
Click to expand...
Click to collapse
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
yashaswee1708 said:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
Click to expand...
Click to collapse
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
sSjBlueVN197 said:
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
Click to expand...
Click to collapse
Try factory reset from recovery?
sSjBlueVN197 said:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Click to expand...
Click to collapse
If you can boot in fastboot do the process again. I'll share the zip once again
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
after flashed OOS, can I re-lock bootloader?
sSjBlueVN197 said:
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
Click to expand...
Click to collapse
Let me know if the issues are fixed
sSjBlueVN197 said:
after flashed OOS, can I re-lock bootloader?
Click to expand...
Click to collapse
You can but the process is a bit complicated, on recent updates some time the phone is bricking when we run the query fastboot flashing lock.
So I won't recommend it. Until we can find a easier way.
yashaswee1708 said:
Let me know if the issues are fixed
Click to expand...
Click to collapse
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
sSjBlueVN197 said:
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
Click to expand...
Click to collapse
So currently everything is okay?
yashaswee1708 said:
So currently everything is okay?
Click to expand...
Click to collapse
yup, everything is OK
80W_C.15_OOS_Android13 it's for Ace racing bro?