OnePlus 11 Convert to OXYGENOS (CPH2447)
**** Flash at your own risk ****
Download and unzip: ONEPLUS_11_PHB110_CONVERT_TO_GLOBAL_CHP2447
https://drive.google.com/file/d/1BxTwECQLW3Cx636vwjUjqrrLAQMhDt8q/view?usp=sharing-------------------------------------------------------------
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
Run $ fastboot flashing unlock
{
"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"
}
Reboot back into bootloader
OPEN ROM FOLDER
RUN FLASH_ALL.EXE
Wait processing
Fomat data
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
This is the rom from ace 2 op11r
Why this flash on the op11
Mobile_Slution said:
OnePlus 11 Convert to OXYGENOS (CPH2447)
**** Flash at your own risk ****
Download and unzip: ONEPLUS_ACE_2_CONVERT_TO_11R.zip
ONEPLUS_ACE_2_CONVERT_TO_11R.zip
drive.google.com
-------------------------------------------------------------
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
Run $ fastboot flashing unlock
View attachment 5852335
Reboot back into bootloader
OPEN ROM FOLDER
RUN FLASH_ALL.EXE
Wait processing
Fomat data
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
View attachment 5852329
Click to expand...
Click to collapse
ChrisFeiveel84 said:
This is the rom from ace 2 op11r
Why this flash on the op11
Click to expand...
Click to collapse
The file has been updated
A huge thank you for your effort. Does OTA update work on your converted rom?
hilary trump said:
A huge thank you for your effort. Does OTA update work on your converted rom?
Click to expand...
Click to collapse
no bro. ota not support
Mobile_Slution said:
no bro. ota not support
Click to expand...
Click to collapse
Thanks!!!
Can I succeed with this fastboot rom?
Is it possible to update with local files?
ryshd296 said:
Thanks!!!
Can I succeed with this fastboot rom?
Is it possible to update with local files?
Click to expand...
Click to collapse
I flashed it, and now I'm sharing it here
What if i revert to phb110 from cph2447 and install stock color os, am i able to get ota updates then ? Im talking about color os updates
BratoMo225 said:
What if i revert to phb110 from cph2447 and install stock color os, am i able to get ota updates then ? Im talking about color os updates
Click to expand...
Click to collapse
yes
Mobile_Slution said:
yes
Click to expand...
Click to collapse
How am i gonna do that
Mobile_Slution said:
OnePlus 11 Convert to OXYGENOS (CPH2447)
**** Flash at your own risk ****
Download and unzip: ONEPLUS_11_PHB110_CONVERT_TO_GLOBAL_CHP2447
https://drive.google.com/file/d/1BxTwECQLW3Cx636vwjUjqrrLAQMhDt8q/view?usp=sharing-------------------------------------------------------------
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
Run $ fastboot flashing unlock
View attachment 5852335
Reboot back into bootloader
OPEN ROM FOLDER
RUN FLASH_ALL.EXE
Wait processing
Fomat data
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
View attachment 5852329
Click to expand...
Click to collapse
On what version is it based of ? Does it have the automatic brightness calibration going crazy bug ? Does the different color modes work ?
Lunisi said:
On what version is it based of ? Does it have the automatic brightness calibration going crazy bug ? Does the different color modes work ?
Click to expand...
Click to collapse
CPH2447 is description
I want to back to color os , but I'm getting bootloop
Hi, i followed your instruction and ended up in a bootloop. A lot of the flash failed with the message:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Allesa said:
Hi, i followed your instruction and ended up in a bootloop. A lot of the flash failed with the message:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Click to expand...
Click to collapse
you have critical partitions flashing not unlocked
fastboot unlock critical
Has anyone installed cph2447_11_A.08 ? Whats new ? Are there bugs with display scale, auto brightness? display color changes?
BratoMo225 said:
Has anyone installed cph2447_11_A.08 ? Whats new ? Are there bugs with display scale, auto brightness? display color changes?
Click to expand...
Click to collapse
NO, I flashed it from cos to oos, if I install it, the phone will brick
gabriel.amg said:
I want to back to color os , but I'm getting bootloop
Click to expand...
Click to collapse
bootloop is mainly due to the oplusstanvbk.img
you miss flashing it?
BratoMo225 said:
Has anyone installed cph2447_11_A.08 ? Whats new ? Are there bugs with display scale, auto brightness? display color changes?
Click to expand...
Click to collapse
i just did it and it's the same result as with a.08, still have all the issues you mentioned.
flashing oplusstanvbk.img from cos is still needed to fix boot loop afterward.
oprocks said:
i just did it and it's the same result as with a.08, still have all the issues you mentioned.
flashing oplusstanvbk.img from cos is still needed to fix boot loop afterward.
Click to expand...
Click to collapse
Did you do factory reset after? You should try that and see
Related
{
"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"
}
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.
Thank you very much!
https://i.imgur.com/71t8xrY.png
https://i.imgur.com/qebNB0C.png
https://i.imgur.com/ubxYZsN.png
https://i.imgur.com/gsbaG2K.png
https://i.imgur.com/xIW8llN.png
https://i.imgur.com/Fzrdhwt.png
Awesome!!
yay. now to get more dev support behind this!
excellent! Please, try to put up a github repo for it, if not already
Hopefully it works fine.
If HTC rolls out kernel sources, I might try some blind development, as I don't have the device, but wanna support it.
Should you need to unlock the official htcdev before they can put?
mapleshadow said:
Should you need to unlock the official htcdev before they can put?
Click to expand...
Click to collapse
Yes, unlock then you can boot it.
Thanks for this! Going to try and get it up and running later today - Need to unlock the BL first.
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Any idea what's going on?
aurelienlux said:
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
Any idea what's going on?
Click to expand...
Click to collapse
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
http://featuresunlocker.com/root-install-twrp-recovery-htc-u11/
Yet sent from my amazing silver U11
jauhien said:
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
Yet sent from my amazing silver U11
Click to expand...
Click to collapse
I didn't flash since I wanted to test it out before using the fastboot boot command recommended in the original post. However this does not seem to work. I wanted to get twrp running so I could use magisk for root
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
aurelienlux said:
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
Click to expand...
Click to collapse
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
tbalden said:
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
Click to expand...
Click to collapse
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
Click to expand...
Click to collapse
OK, that's very professional. :good:
Just others be aware that you should make sure you have a way backwards.
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
Click to expand...
Click to collapse
That would be fantastic and very good of you if you could share it. Many thanks!
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
sabpprook said:
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
View attachment 4342230
Click to expand...
Click to collapse
Looks like you're building in android 7.1 for Oreo decrypt, won't work without the needed sepolicy changes and plat/non_plat contexts, please check the current gerrit updates for the standard HTC U11:
TWRP vold_decrypt patch: https://gerrit.omnirom.org/c/26652/
EDIT2: U11 Oreo decrypt device tree changes needed for a 7.1 build: https://gerrit.twrp.me/c/2756/
If you end up with decryption successful, but it doesn't actually mount /data, then you may even need an updated kernel https://gerrit.twrp.me/c/2761/
which is what we needed. EDIT: Obviously that's a U11 kernel update not a U11+ one, so don't try to use that kernel
Some things will still get changed. I also recommend you build in real DEBUG mode, the straces have much more info than a log or dmesg. by using TW_CRYPTO_SYSTEM_VOLD_DEBUG := true
Prot02018 said:
That would be fantastic and very good of you if you could share it. Many thanks!
Click to expand...
Click to collapse
There you go: https://drive.google.com/open?id=1nkzK_wbSgC6HSlOsNqOc79f94p7v_3wz
That's version 1.05.400.13. I managed to decrypt it successfully using the latest RUU Decryption Tool on Windows. I have a decrypted boot.img and system.img but I haven't yet uploaded those to my drive.
Waiting for your Good news.
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
By following this guide your warranty is void obviously and you will lose all data
0. Go to settings, accounts, remove your google account
1.Go to https://www.asus.com/tw/Phone/ROG-Phone-II/HelpDesk_Download/
{
"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"
}
Download vbmeta.img
https://drive.google.com/open?id=10DzVAr_HDc95jPYXkb0O6ZWf7f8FoIg1
Download the most recent GSI
https://github.com/phhusson/treble_experimentations/releases
(ensure it is system-quack-arm64-ab-gapps.img.xz if you want google apps or system-quack-arm64-ab-vanilla.img.xz if you don't)
Extract the .xz file
2. Load up the apk from Asus
3. Agree to terms
4. Press unlock (you must be on wifi)
5. Wait until the device is back at the initial setup
6. Power off
7. Hold down vol up + power until you are at a screen which says power off/reboot/enter recovery/restart boot loader
8. Ensure you have adb and Fastboot setup
8a e.g. on a MacOpen a terminal run
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
then after
brew cask install android-platform-tools9. Connect a USB to the phone via the side port
10. Check Fastboot is working
fastboot devices11. If you can see your device
type the following
fastboot --disable-verity --disable-verification flash vbmeta Leave a space after vbmeta, then drag and drop the vbmeta.img file into the terminal window
12. If successful
type
fastboot erase system13. Type the following
fastboot flash system Leave a space after system, then drag and drop the extracted img file NOT the xz into the terminal window
14. Wait
15. Once done
16. type
fastboot reboot17. Wait
18. BOOT WILL FAIL
19. Use the arrow keys and power to select factory reset
19. Use the arrow keys and power to select Yes
Your device will now boot into current android.
Thanks to @suzook and @reg66 for pointing me in the right direction.
Thanks for the mention dude!! Glad you got it working and for the tutorial...
Hi, Compare to stock rom, what kind of experience with gsi? Anything didn't work? Pros and cons if you can mention. Thx
Great to see this development. Hopefully we can get 120Hz running someday, and we'll be set.
GeekGod said:
Great to see this development. Hopefully we can get 120Hz running someday, and we'll be set.
Click to expand...
Click to collapse
It's working on pixel experience.
suzook said:
It's working on pixel experience.
Click to expand...
Click to collapse
Do you a link of Pixel Experience ROM for ROG Phone 2?
suzook said:
It's working on pixel experience.
Click to expand...
Click to collapse
Got a link?
IS this google all apps for CN rom ?
whats difference with ww rom ?
is 120hz working?
No. It treble not support special devices
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
hkbazzi said:
is 120hz working?
Click to expand...
Click to collapse
No. It treble not support special devices
biboFx said:
IS this google all apps for CN rom ?
whats difference with ww rom ?
Click to expand...
Click to collapse
There is no difference with GSIs (the g stands for generic) works as is on both.
The distinction between WW and CN is only relevant to stock ASUS firmware
GeekGod said:
Got a link?
Click to expand...
Click to collapse
Full GSI list inc pixel experience
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
MANICX100 said:
Full GSI list inc pixel experience
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
doesint want to boot at all
just google logo screen forever
rowihel2012 said:
doesint want to boot at all
just google logo screen forever
Click to expand...
Click to collapse
Did you factory reset as per the OP? Initial boot will fail he says...
heobanhki said:
No. It treble not support special devices
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
No. It treble not support special devices
Click to expand...
Click to collapse
WRONG.
reg66 said:
Did you factory reset as per the OP? Initial boot will fail he says...
Click to expand...
Click to collapse
no that isworking fine but no 120hz or 90
just wanted to try pixel exp 9 becuse it has 120hz support but always stuck to google logo
rowihel2012 said:
no that isworking fine but no 120hz or 90
just wanted to try pixel exp 9 becuse it has 120hz support but always stuck to google logo
Click to expand...
Click to collapse
Bummer, ask suzook..
rowihel2012 said:
no that isworking fine but no 120hz or 90
just wanted to try pixel exp 9 becuse it has 120hz support but always stuck to google logo
Click to expand...
Click to collapse
Install Magisk along the way to enable root, also... there's no 90 or 120Hz here.
Hello, i want to know, if someone can answer me.
What is GSI?
What can GSI do?
This is some kind of daily driver or something?
What we lost if we put this rom?
Can this method be used with the original rog phone? I'm interested in getting Android Q. :fingers-crossed:
{
"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"
}
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 deviceBased on Android 12What works?Pretty much everything.Known issuesYou tell meDON'T FLASH GAPPS, THEY'RE ALREADY INCLUDEDDonateHereTranslationHelp with project translationStay tunedOur blogDownload Link for OnePlus 9 ProROMRecovery (Boot.img)Device Chat
INSTRUCTIONSMake sure you are on latest OOS 11 (11.2.10.10)Reboot to bootloaderFlash the provided boot.imgReboot to recoveryFormat data in the recoveryADB sideload PixelROM.zipReboot
Android OS version: 12
Security patch level: FEB 2022
Kernel Source code: Link
Trees Sources :
8350-common
Lemonadep
Source code : https://github.com/PixelExperience
ROM Developer: YouLop09
Special thanks to:Chandu, Edward, Karthik, vjs pranav.
Finally. Hope this goes official. Nice job!
Need to have Bootloader unlocked or not.
Thank u so match
dariodamico said:
Need to have Bootloader unlocked or not.
Thank u so match
Click to expand...
Click to collapse
Yes, you need to have it unlocked
Wow this is incredible!
But i am noob in the new style of flashing custom roms, when i saw a videotutorial i will flash it
adrisanfe said:
Wow this is incredible!
But i am noob in the new style of flashing custom roms, when i saw a videotutorial i will flash it
Click to expand...
Click to collapse
You must be on A11 OOS or any custom rom A11 OR A12. Doesn't matter.
Steps what I did and how I install the rom and root.
Steps:
1. Go to bootloader and use following cmd: fastboot flash boot filename.img (provided by the developer in the 1post recovery.img)
2. Go to option in bootloader and use volume key to choose the reboot to recovery.
3. Once you are in recovery, go to factory format and click factory format data wipe. It will wipe you internal and external storage with formatting data meaning you will lose everything.
4. Go to Apply Update and use following cmd: adb sideload romname.zip and click entre, it will take 10 to 12 mins depending.
5. Once install successfully reboot to system and enjoy the rom.
Steps for root what I used instead of using payload and extracting boot.img. Easy steps root successful.
1. Once you are booted into system successfully and stepup everything as you would.
2. Go to bootloader by holding down volume down and power button. You will enter bootloader menu.
3. You CANNOT root your phone with given recovery in the first post. So, what I did I use the recovery img from DrepFest rom, it's build for A12 it should be safe to use. TWRP is compatible with A12 as of right now.
4. Go to bootloader use cmd: fastboot flash boot DrespFest recovery.img and click enter and reboot to recovery.
5. Now you will entre DrespFest recovery A12.
6. Go to Apply update and use following cmd: adb sideload rootfilename.zip (it's magisk 23). It will root your phone with Magisk 23, but you can update Magisk 24.1 manually without issues.
I have attached Magiosk 23. It can be sideload through recovery of LOS recovery or DrespFest recovery.
Enjoy rom and root.
Congrats brother! Looks good!
Any chances to non-gapps build?
Will try this later, congrats!
Is there anyway to get call recording in this ROM . Thanks
dariodamico said:
Is there anyway to get call recording in this ROM . Thanks
Click to expand...
Click to collapse
not for now
Will it work if I dirty flash from Drespfest A12 to PixelExperience?
vipinpvarghese said:
Will it work if I dirty flash from Drespfest A12 to PixelExperience?
Click to expand...
Click to collapse
Yes
Warrkill said:
Any chances to non-gapps build?
Click to expand...
Click to collapse
No, Pixel Experience always have gapps.
Any chance to non pro ,just OnePlus 9
xarcom said:
Any chance to non pro ,just OnePlus 9
Click to expand...
Click to collapse
soon
ROM looks great, UI is beautiful. Unfortunately, it drains my battery drastically it might be time for a phone upgrade.
pls help I'm having error with ads Sideload gives me "failed to find updated binary META-INf" pls help
edit: sorted it out, Safari extracting the zip file right after the download of the rom and recompiling it gives error so I used chrome to dl and it is going all good
Tried this this morning for a short time, runs really well and feels amazing however once I turned off wifi I could not get it to turn back on.
Whenever I tried it would crash the system and ask to close the ui.
Reverted back to stock before I had to take to go to work
kevrae said:
Tried this this morning for a short time, runs really well and feels amazing however once I turned off wifi I could not get it to turn back on.
Whenever I tried it would crash the system and ask to close the ui.
Reverted back to stock before I had to take to go to work
Click to expand...
Click to collapse
Just a little off-topic, there is a tutorial somewhere of how to go back to stock?
LE2125_11_F.16 : GOOGLE Drive link
MD5 : B20450405F31E6644373746DA2050B55
SHA-256 : 80ca7ea84dc0fa859ae5e097c8047639091fdc28f919b891e909eb18c3ff7c01
CRC32 : 91731EB9
boot.img and magisk patched boot.img in the link.
what is the easiest way to get out of a custom rom and go to oos a13?
I already made this change once and I had to flash the msm to oxygen 11, then update 2x via OTA and then install the oxygen 13 local update.. I find it unnecessarily time consuming, could there be a way to flash msm in more up-to-date versions of oxygen
1thomas said:
what is the easiest way to get out of a custom rom and go to oos a13?
I already made this change once and I had to flash the msm to oxygen 11, then update 2x via OTA and then install the oxygen 13 local update.. I find it unnecessarily time consuming, could there be a way to flash msm in more up-to-date versions of oxygen
Click to expand...
Click to collapse
I think you have no choice and this is the safest way to switch from a custom rom to oos a13 it's MSM TOOL, be careful to backup your files beforehand.
use this MSM Tool Oxygen package OS 11.2.10.10 (global).
When the installation of the F16 version is complete
For information the unlocking of the bootloader delete the setting for the zram.
Once the rom is installed (LE2125_11_F.16), the bootloader unlocked and your phone rooted, you can reactivate the zram by performing these commands (in bold) :
note: you must enable usb debugging to run the adb shell command.
C:\adb>adb shell
OnePlus9Pro:/ $ su
OnePlus9Pro:/ # resetprop persist.sys.oplus.nandswap.condition true
OnePlus9Pro:/ # echo 1>/sys/block/zram0/hybridswap_dev_life
1|OnePlus9Pro:/ # reboot
{
"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"
}
buu'buu said:
I think you have no choice and this is the safest way to switch from a custom rom to oos a13 it's MSM TOOL, be careful to backup your files beforehand.
use this MSM Tool Oxygen package OS 11.2.10.10 (global).
For information the unlocking of the bootloader delete the setting for the zram.
Once the rom is installed (LE2125_11_F.16), the bootloader unlocked and your phone rooted, you can reactivate the zram by performing these commands (in bold) :
C:\adb>adb shell
OnePlus9Pro:/ $ su
OnePlus9Pro:/ # resetprop persist.sys.oplus.nandswap.condition true
OnePlus9Pro:/ # echo 1>/sys/block/zram0/hybridswap_dev_life
1|OnePlus9Pro:/ # reboot
Click to expand...
Click to collapse
How do I disable zram? And why would you do that? I have always used the msm tool without any problems, I had never heard about it
1thomas said:
How do I disable zram? And why would you do that? I have always used the msm tool without any problems, I had never heard about it
Click to expand...
Click to collapse
Nothing to do with MSM.
I just want to say that once you finish installing the F16 version, then unlocking the bootloader causes you to lose the RAM setting. If you don't need this option, you don't have to do anything.
buu'buu said:
Nothing to do with MSM.
I just want to say that once you finish installing the F16 version, then unlocking the bootloader causes you to lose the RAM setting. If you don't need this option, you don't have to do anything.
Click to expand...
Click to collapse
oh yes i got it, thanks for the info
1thomas said:
oh yes i got it, thanks for the info
Click to expand...
Click to collapse
Ok we understand each other now
Boot Image
Here's a Magisk boot image that boots with modules disabled to recover from a bootloop. Someone will need it...
CSnowRules said:
Boot Image
Here's a Magisk boot image that boots with modules disabled to recover from a bootloop. Someone will need it...
Click to expand...
Click to collapse
Thank you so much
Sorry but can you upload another place? Please
The original Boot.img.....
kovacsabesz said:
Sorry but can you upload another place? Please
The original Boot.img.....
Click to expand...
Click to collapse
First post
how to switch coloros 12.1 to oos13 ?
It looks like twrp is now working with android 13 properly...
what other backup tool could you recommend?
Swift Backup from playstore
sweet been using f11 all week ! wonder if launcher crashing issue is fixed
How do I install this?
I'm currently on OOS11 and can't install 12 because that breaks touchscreen. Oh and my fastbootD mode remains without driver, device shows up as LE2123.
bmaggot said:
How do I install this?
I'm currently on OOS11 and can't install 12 because that breaks touchscreen. Oh and my fastbootD mode remains without driver, device shows up as LE2123.
Click to expand...
Click to collapse
What do you mean by breaks touchscreen, I don't understand. Touch screen no longer responds to touch?
buu'buu said:
What do you mean by breaks touchscreen, I don't understand. Touch screen no longer responds to touch?
Click to expand...
Click to collapse
Correct. Had to use MSM but it's version 11.
bmaggot said:
Correct. Had to use MSM but it's version 11.
Click to expand...
Click to collapse
Yes, MSM 11.2.10.10 is the latest version for oxygenOS. Then you will only have to do all the incremental updates, it's a bit of a long process but it's clean.
buu'buu said:
Yes, MSM 11.2.10.10 is the latest version for oxygenOS. Then you will only have to do all the incremental updates, it's a bit of a long process but it's clean.
Click to expand...
Click to collapse
I wonder if it's possible to do a full clean install of this somehow. I just tried to do incremental and one successful update and then LE2123_11.C.47_1470_202203102117 also broke my touch.