yashsingh1/xdaforums huggingface dataset:
[OnePlus 9] pawelmiernik:
It's tedious but download the firmware flasher utility. In bootloader make note of which slot is active, run the flasher utility (choose no to flashing modem) and when it's done go back to bootloader, switch slots and run the flasher utility again, when that's done go back to bootloader and flash PEX boot.img, vemdor_boot.img, dtbo.img go into recovery and flash PEX zip. Also name your images with a prefix for which rom you're using, I've had it happen where I had dtbo mixed up with another rom and kept scratching my head why things weren't working. Just prefix your images something like pex-dtbo.img and nameless-dtbo.img and so on if you're constantly switching between roms like me.
[OnePlus 9] shadabkiani:
Looks to me that data wipe was successful anyway. I'm on crDroid and I think I had some error too when factory resetting from recovery, data wipe was complete nevertheless. I proceeded with flashing and everything was good.
[OnePlus 9] pifubaro:
How can I check the active slot in fastboot mode?

What command do I use to change slots?
[OnePlus 9] pawelmiernik:
Google is your friend, this is stuff you should familiarize yourself with before you attempt flashing custom software on your phone, I suggest you Google basic adb and fastboot commands or use --help command for both and go over the information they provide. Good luck!
[OnePlus 9] mattie_49:
Stock kernel op9 na lemonade 5.7 PE. Battery profile in K-profiles. This is over 2 year old device and I charge to 100 every time and get down low before recharge. Still killing it.
[OnePlus 9] jmadiaga:
i think bec PEX does not CPU throttle. i tested it with CPU Throttling Test
[OnePlus 9] mattie_49:
fastboot --set-active=other

This no longer works on 9 series because of the jacked up super partition. 8 series is last that you could jump around with. Have stock on slot _a and custom on slot _b and wipe data and boot into whatever you wanted. Very handy
[OnePlus 9] shadabkiani:
Does OP8 have super_a and super_b? Or does it not have super at all?
[OnePlus 9] mattie_49:
Yes individual super partitions.
[OnePlus 9] ralf979:
V5.8 is Out!

Ota pushed and changelog in second post

Enjoy the Pex!!
[OnePlus 9] STRUZZIN:
5.8 is working great so far.

Thank You :)
[OnePlus 9] Lagarde:
I've had major problems with literally every other rom I've tried...except this one. This one works amazingly. Absolutely stunning work!

The only bugs I've found (and they're REALLY minor and I 100% don't care about them):

- Google thinks my phone is a Pixel 5

- Google Maps on computer won't send maps to the phone, unless I send it as an SMS (choosing the phone from the list doesn't work).

That's it. Literally everything else has been perfect!!!
[OnePlus 9] shadabkiani:
Google thinking it's a Pixel isn't a bug actually; it's intentional. You will have added benefits like unlimited Photos backup and other stuff if you own a Pixel.
[OnePlus 9] mattie_49:
It's unlike anything I've ever seen for a OnePlus device. All the op8 roms I ever ran were riddled with bugs as well. When I had that device. I just got tired of side loading just to find out then having to return to stock. Everything on 5.8 works perfectly . Battery profile on K-profiles is perfect way to run device as well. Nice to have a custom that actually works more efficiently than stock but with all the stock oos cam goodies. Nice home screen for sure.
[OnePlus 9] shadabkiani:
How did you get VoLTE to work? I tried a guide but couldn't get it to work.
[OnePlus 9] mattie_49:
Flashed the build and connected to data. Verizon sim on OnePlus device uses Volte to aquire data.
[OnePlus 9] zeroelcapo:
Hi, thank you for this amazing ROM!! really loving it! The only downside is battery life is getting really bad, it just drains out doing nothing.. even disabling evething, "mobile data always on", "battery saving mode", etc, any tips? Thanks!
[OnePlus 9] Lagarde:
I had that for the first 24hrs, like most roms when first installed. I turned off AoD (changed it to "when picked up") and battery life shot up to about 24-28hrs of moderate use.

If you also use something like https://xdaforums.com/t/module-snap...g-low-power-high-efficiency-update-1.4487565/ you can get a couple days out of one charge. Right now with PEX and that low-power module for magisk, I'm getting about 40-48hrs with moderate use.
[OnePlus 9] zeroelcapo:
Sounds promising!! Ill just keep using it for a couple days, anyway that snapdragon module sounds great! Ill totally try it, thanks! =D

PD- no idea what PEX is lol
[OnePlus 9] Lagarde:
Sorry, I'm an abbreviation junkie. PEX = Pixel EXtended =)
[OnePlus 9] caca13:
I have an issue where sometimes when I boot into the OS, it glitches out with a black screen, flashing the statusbar and the navigation bar below, making me shut it off and boot it again. It fixes itself within 1-3 restarts. Is this a known glitch? If so, what do I turn off to prevent it?
[OnePlus 9] shadabkiani:
Are you on the correct firmware, i.e. F.18 required for this ROM?

By the way, I am on F.21 currently and all is perfectly well for me. You can try different firmwares from here. Once downloaded, extract the zip, boot your phone in bootloader mode, and run bat file.

Also try to perform a factory reset before sideloading the ROM.
[OnePlus 9] caca13:
So I installed F.18, formated data and sideloaded the ROM again. It turns out this bug only occurs when you install magisk via recovery. I tried installing magisk via flashing a patched boot image, but system just refused to move on from the "unlocked bootloader" message, a.k.a it doesn't boot into the system. Conclusion is, magisk causes this, I'm not sure why. If anyone else with magisk can share their experience, that'd be great.
[OnePlus 9] shadabkiani:
DO NOT flash Magisk directly. The recommended and proper way is to

temporarily boot

the patched boot.img, and then Direct Install option from Magisk app. By this method, Magisk app will automatically backup the original stock boot.img, so at a later stage if you decide to unroot, you can simple go to Magisk app, choose Uninstall and Magisk will recover the original boot.img. Use this command from fastboot to temporarily boot the patch (assuming you already have patched boot.img from Magisk):

fastboot boot <your_patched_boot.img>

Notice that there is no fastboot flash boot in the command.

Use Magisk v26.1. I had no problems with it.
[OnePlus 9] caca13:
So flashing magisk directly (installing the magisk app, patching the boot.img I extracted from the ROM zip, patching it via Magisk and then flashing it in fastboot) works. I guess I just needed to be on F.18. No need for temporary booting if you're on F.18 apparently. I tried doing that too, but it gave me the same issue. Bottom line is, flash the patched boot.img directly with F.18.
[OnePlus 9] shadabkiani:
What do you mean by "no need for temporarily booting if you're on F.18 apparantly"? It doesn't matter what ROM you are on, what firmware, what OOS..... The recommended way to root OnePlus 9 is to patch boot.img from Magisk app, then temporarily boot that patched image from fastboot, and from the Magisk app gain permanent root by it's Direct Install option.

I just went to Syberia ROM today, but I was on this PixelEntended ROM for the past week. I had root with Magisk 26.1. No problems for me. I had Zygisk enabled. Hid the Magisk app (option from within the app). Had 2 modules (ACC and Universal SafetyNet Fix Mod).
[OnePlus 9] caca13:
What I mean is that you can just patch your boot.img in magisk, go into bootloader and straight up go "fastboot flash boot <patched image>.img" and reboot and that's it. I don't know about the recommended way, but doing it like that works just fine after flashing F.18.
[OnePlus 9] shadabkiani:
So you can boot your phone after flashing Magisk patched image from fastboot? You wrote above that system would not boot after flashing..

P.S. Flashing boot directly from fastboot still works. But the problem with that would be that Magisk would not backup the original boot.img. So you won't be able to restore image from Magisk if at a later stage you decide to unroot. Well, why would you need to unroot? Because if you are on OOS and there is an update, it will fail to proceed because of tampered (patched) boot.img, hence before proceeding with OTA, you would need to restore original boot.img. That is where temporarily booting and then rooting method pays off. By the way, you can restore original boot.img by flashing if you didn't go with temporary boot method.
[OnePlus 9] mattie_49:
This method is only needed if your running stock rooted oos. Sideloading magisk through recovery works perfectly fine on Pex,Lineage all other aosp builds I've used. No need to have stock boot.img on aosp. Ota updates install fine rooted. Only if your running custom builds though.
[OnePlus 9] shadabkiani:
Yes. That's why I keep writing 'recommended way'. It's not the only way.
[OnePlus 9] caca13:
My bad, it sounded confusing. I meant it didn't boot before I flashed F.18, but just flashing it worked on F.18
[OnePlus 9] zjyoti:
Battery backup is terrible, averaging about 2~3 hrs of SoT. Device keep getting hot with normal daily use idk why. Running snapdragon scaling module extreme efficiency mode, But no luck. Battery dies in about 12~15hr of normal use. It takes about 70~90 minutes to full charge with the original power brick and cable. Lost warp charging,I guess. Any solutions anyone?
[OnePlus 9] Lagarde:
1) Have you had it installed and running for 24+ hours? It takes that long to settle in. The first 24hrs, my battery drain was insane.

2) Haven't tried the extreme scaling module, but low-power one has been working very well for me. Phone doesn't even get warm in games.

3) On mine, it doesn't say warp charging, but it goes from 0-100% in about 40 minutes. First 50% charge takes about 10 minutes. That's about in-line with normal warp charging.

All in all, sounds like possibly a bad install or wrong firmware version if I were to guess. The only thing that seems to draw power painfully fast on mine is AOD, which was bad even on stock. As of right now, mine's been off-charger for 26 hours, during which time I've taken 5 calls, played a few web games for a short time, and sent about a dozen emails...sitting at 86% battery.
[OnePlus 9] zjyoti:
Hello,

1) I've been running it for about 72+ hours but no luck! :(

2) Phone getting warm just with normal use.

3) I know it would not say warp charge; however, charging time is not normal.

I was in LE2115 f.21 firmware. I installed it from the Sourceforgenet (PixelExtended-5.8_lemonade-13.0-20230507-1328-OFFICIAL.zip) but don't know about the firmware. however, it shows LE2110 in my settings now. Can you point me in the right direction for firmware, please?
[OnePlus 9] shadabkiani:
Your problems might be because of firmware.

You were on F.21 fimware, however, it must have been on 1 slot only (whether a or b). We don't know what slot were you on and slot you flashed ROM on. Most porbably, you sideloaded and it flashed on the other slot. Anyway, that was just information.

What you should do now is download the firmware from the link in first post where you downloaded the ROM from. Look for the firmware folder and download F.18. That is what's recommended. Download it, extract it, put your phone in bootloader moder, and run the bat file from firmware. When asked about modem, choose No. This will flash F.18 firmware on both slots.

Next you just proceed with flashing ROM as usual. I would strongly suggest doing a clean flash by factory resetting and formatting data from recovery before flashing.

P.S. I used this ROM with F.21 firmware on both slots with no such problems.
[OnePlus 9] zjyoti:
Hi, thank you for your suggestion. However, i may sound noob,but how can i flash on both slots? Should I flash it twice, each time changing the default slot name?
[OnePlus 9] shadabkiani:
The bat file will automatically flash to both slots. You don't need to worry. Just make sure the process goes smooth till the end.
[OnePlus 9] by_BenjamiN:
There is no game mode. where can i download ?
[OnePlus 9] shadabkiani:
I'm not on this ROM currently, but I think I remember there is Game Space. There is no launcher icon, but it's somewhere in the Settings. You can search in Settings.
[OnePlus 9] by_BenjamiN:
Game mode removed in last build
[OnePlus 9] zjyoti:
What is the kernel you are using? Or are you using default kernel in the pex rom?
[OnePlus 9] Lagarde:
I use the default kernel. Only changes from pex stock I made are rooting, adding the underclock module, and turning always on display to only when picked up. With those changes, I get about 2-3 days on my phone, with only a few oddball quirks that I've run into (some audio buzz, a few sounds that don't mute properly in silent mode, etc...nothing major).
[OnePlus 9] windowslucker:
I cant seem to get root access working.

What i tried ( with F18 Firmware and F21 Firmware):

Flashing boot.img, vendor_boot.img and dtbo.img then

1. adb sideload rom.zip, downloading Magisk.apk from Git and renaming to .zip and flashing via recovery

2. adb sideload rom.zip, installing Magisk.apk, patch boot.img and flashing patched boot.img

3. adb sideload rom.zip, installing Magisk.apk, patch boot.img and temporarly boot boot.img

All steps above are resulting in a bugged out UI with flashing statusbar and minimize icon on the bottom.

Sometimes flashing/temp booting the patched boot.img results in "Stuck on black screen with Onplus Logo and "Fastboot Mode" font"

Flashing Rom.zip without any Magisk modifications and the System boots fine or is this an rom bug?

Is there a detailed guide on how to root the device? im currently kinda stuck :-(

Edit
[OnePlus 9] shadabkiani:
Start over and do a clean flash like this. Flash boot.img, dtbo.img, vendor_boot.img. Reboot to recovery. Factory reset and format data. Sideload the ROM zip. Boot up the system. Then install Magisk 26.1. Patch boot.img. Temporarily boot the newly patched image. When system boots up, open Magisk app and choose Direct Install.
[OnePlus 9] windowslucker:
Do i need a specific base Version of the Standard OS? I reseted my entire phone with the MSM Tool which was Android 11.

When Flashing Firmware 18 in this state im stuck in QUALCOMM CrashDump Mode

Edit: Yes you need at least Android 12 to get not stuck

Edit2: Just like before, i completly reseted my phone with MSM then updated to Android 12 and followed your steps. But im Stuck in the "Fastboot Mode" screen which is centered and above the OnePlus Logo is shown. Im slowly loosing my nervous :D

Edit3: I tried flashing crDroid, but i was stuck at exact the same error behaviour. Then i changed over to Magisk25.2 which worked instantly. Magisk26.1 is somewhat buggy and not working for me, thanks for the help!!
[OnePlus 9] shadabkiani:
Refer to my post in crDroid thread.
[OnePlus 9] qbfreak:
Why can't I access diag mode from dialer on this rom?
[OnePlus 9] shadabkiani:
OEM codes don't work on custom ROM, generally. You have to be on stock OOS firmware.
[OnePlus 9] zjyoti:
Does this ROM support T-mobile?
[OnePlus 9] STRUZZIN:
It does I been using it on T-mobile.
[OnePlus 9] kjsanjay:
Just installed for the first time last night. All good except, my SMS backup for some reason isn't getting restored from google backup. As per google, the phone is showing up as Pixel XL.

Any idea on how to get around it?
[OnePlus 9] applyscience:
Just a heads up, My messenger broke completely with the latest play update. uninstalling update made it go right back to functional.

Adding messsanger to the magisk DenyList may also fix it (never had to do so before) but for now i am just rocking with the update not applying.
[OnePlus 9] shadabkiani:
You mean Facebook Messenger or Google's SMS Messages app?
[OnePlus 9] ralf979:
Hi Guysssssss!!!

V5.9 is OUT

since all the source has been rebased once again (thanks google), cleanflash is recommended

be careful because you need to update the firmware, so follow the guide and the changelog in the second post !!

Enjoy The PEX!!
[OnePlus 9] applyscience:
I applied the update over OTA so I am already on 5.9 (and without the utility applied, obv) . Came on here because calls screening doesn't work. Everything else is perfect, though.

my firmware was updated in April before switching to extended again, but assuming the utility to flash is what enables call screening/spoofing?

either way, I tried to flash utility 5.9 zip dirty in PXE recovery and received

ERROR: recovery: failed to find update fianary META=INF/com/google/android/update-binary

so then i updated the safetynet-fix mod variant mattie had me use to get call screen to work on this ROM in April. Hoping that could maybe get it to work. . It just updated 3 days ago and comes with a strong variant now. i just updated the regular and , again, everything works fine but call screen.

Maybe strong would help or maybe the utility + strong, idk. Im good for the night. Ill just clean flash when i have free time, but honestly, I am not sure a clean flash will avoid the error i got above.
[OnePlus 9] applyscience:
lol this maintainer's telegram is something else. Giving me attitude for updating the phone on OTA (the file he sent out via OTA) and for doing so without "reading first" (the file sent out OTA with no OTA notes/data)

Whatever, my phone works. its just so stupid they utilized the OTA and did so without documenting it properly and then tries to call me out for not jumping onto his blog every time there's an update.

if you push out OTA, expect people to use OTA (duh) and if OTA is problematic, consider not sending it that way (or at the very least, use it properly and document the title/notes field with a fair warning/any data at all. the update was released over OTA with no information in its menu
[OnePlus 9] ralf979:
in the options there is always the changelog

this time it didn't work, during the umpteenth rebase of all the source, the push of the changelog didn't work (maybe, because I couldn't check)

anyway before flashing, read the changelogs that are always posted here on XDA and on the telegram posts of the releases
[OnePlus 9] AlmaGHWOR:
Hi!!

Tested last version with clean installation (I had problems with OTA update) and everything works except:

-Slow Motion camera doesn't work, camera crashes.

-No volume media control anywhere.

Former version has both.

Other things work fine.
[OnePlus 9] BrauliX:
Unfortunately in my device i have same issue then other roms, IMEI's are changed to 00010..... anyone with that issue too? Im on LE2110. I tried with IN and Eu firmware, but still fake imei. Eve start from beginning with MSM toll converting to LE2115, fter flash rom my device cames to LE2110 again
[OnePlus 9] shadabkiani:
LE2110 gets updates of Global. I have it too and my IMEIs are good. What happens when you use MSM Tool Global to revert back to OOS11, do you still get corrupt IMEI? Also, what about fastboot (bootloader) menu's Show Barcode option?
[OnePlus 9] TheLod:
Many LE2110 user have this issue on all custom rom. MSM restore or flash older build (prior to 20230610) will get good IMEI back like for now on latest lineageOs build too. Hope custom rom based on lineage will be also fixed this issue soon.
[OnePlus 9] BrauliX:
Its not the first time someone says imei are good, but when they check imei on about phone and in the box when phones came, realize imeis are not.the same
[OnePlus 9] BrauliX:
Can you comfirm that plz to tell us who have imei issue
[OnePlus 9] BrauliX:
And one more thing, your LE2110 is 4G or 5G??
[OnePlus 9] shadabkiani:
Is there such a thing as 4G in OnePlus 9? I thought all Snapdragon 888 were 5G. Mine is 5G too.
[OnePlus 9] TheLod:
For my part LE2110 with IMEI issue for all custom rom bluid after 20230610, expect for latest lineageOs (20230723).

I have 5G enable on option but no subscribe to an 5G plan (only 4G).
[OnePlus 9] shadabkiani:
Firmware 13.1 is required, but on sourceforge, only F.18 is available for download. I know you shared a link to 13.1 firmware in the second post, but it's on mega.nz. It would be great if you kindly upload upcoming build's firmwares on sourceforge's firmware folder to have them in one place. I generally download builds straight from sourceforge and if there's a new firmware, I would be able to know from there too.. Just a humble suggestion.
[OnePlus 9] shadabkiani:
@TheLod @BrauliX I have LE2110 and I flashed the latest build 20230721 of PixelExtended ROM and my IMEIs are good. I downloaded the ROM zip. Then extracted its payload.bin with Payload Dumper Go in order to get boot.img dtbo.img vendor_boot.img. Then I flashed these 3 images from fastboot (bootloader). Rebooted to recovery. Factory reset and wiped data. Rebooted to recovery again. Sideloaded the firmware zip provided in 2nd post (mega.nz link). When it asked about modem, I chose No by pressing Vol-. Then rebooted to recovery again. Sideloaded ROM zip. Then rebooted to recovery again and sideloaded ROM zip once again to have it on both slots (not really necessary though). All done and rebooted the phone.
[OnePlus 9] ralf979:
the firmware is not mine, so it stays where you see it in the guide of the second post.
[OnePlus 9] testguest:
I did a clean install of the latest version and firmware. Everything is fine except connecting the device to a computer. It isn't recognized in the device manager and the options for filetransfer, USB tethering, MIDI etc. on the device are greyed out. It's only charging, as if it's connected to a wall socket.
[OnePlus 9] RealMrCactus:
Is there a way to change the boot animation
[OnePlus 9] ralf979:
Hello Guys,

PEX development for lemonade/p is dropped

I can't work on many things anymore.

I don't stop the development of the source, but only for these two devices.

many already know, but for those who are not aware, on lemonade/p I will continue with another rom

here the links for LEMONADE and LEMONADEP

Thanks
[OnePlus 9] shadabkiani:
Yes. Temporarily boot the TWRP or OrangeFox Recovery. Mount /product. Make it r/w with terminal command. Then copy your new bootanimation to /product/media folder. Reboot and enjoy.
[OnePlus 9] shadabkiani:
Sad 😪
[OnePlus 9] RealMrCactus:
Last I checked I couldn't mount my filesystems to my PC but I can try
[OnePlus 9] shadabkiani:
Who said anything about mounting to PC? You just mount from recovery. Then you can access files in that particular filesystem from recovery's file manager. Otherwise, that filesystem will show you nothing.
[OnePlus 9] RealMrCactus:
okay so my bootanimation is in product when i got to vendor in the recovery file manager the product folder is empty even though about every root file manager ive used shows the media folder and then the bootanimation in there
[OnePlus 9] RealMrCactus:
mb i forgot to mount it but still when i try to copy it it tells me it failed
[OnePlus 9] shadabkiani:
Just mounting the /product isn't enough. You have to make it rewriteable as well. So, open Terminal from recovery and run this command:

mount -o remount,rw /product

Then you can copy/replace new bootanimation from File Manager. If that fails too, you can copy/replace from Terminal command too. Just make sure to copy the new bootanimation to internal storage. Now run this command:

cp /sdcard/bootanimation.zip /product/media

Reboot and it should be new bootanimation.
[OnePlus 9] RealMrCactus:
> mount -o remount,rw /product

New-PSDrive : Parameter cannot be processed because the parameter name 'o' is ambiguous. Possible matches include: -OutVariable -OutBuffer.

At line:1 char:7

nvm im stupid
[OnePlus 9] RealMrCactus:
okay so i can get the bootanimation.zip in there but orangefox corrupts it
[OnePlus 9] shadabkiani:
What does it mean? You mean when you copy bootanimation to internal storage and it gets corrupted right away? Or do you mean after you copy it to /product/media and it gets corrupted then? How do you know your bootanimation is corrupted anyway? New bootanimation doesn't show on startup and simple Android bootanimation shows? Have you edited zip file in any way? I don't understand, please expand.
[OnePlus 9] RealMrCactus:
I'm assuming it gets corrupted when I copy it.

I know it's corrupted because it doesn't show and all my file managers tell me it's corrupt