yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] TheSayaMan:
Will definitely get this done. Thank you.
[OnePlus 9 Pro] MrSinister:
If you can make a build today i can test it. I'm going back to OOS now.
[OnePlus 9 Pro] TheSayaMan:
I pushed a update already today. This will require some extra work and time. I will include it in my next build but it won't be today.
[OnePlus 9 Pro] Nerv4root:
Have rtl8812au driver in kernel?
[OnePlus 9 Pro] Aballamis:
little confused. I have unlocked LE2125 and am updating to stock f.17 A13. Will I still need to run the flashfirmware.bat to go to c.66???? It just seems counterintuitive to NEED to be on A12 or A13 but if on A13 you MUST flash the flashfirmware.bat to rollback to A12.

also, ive had issues in the past flashing magisk.apk/magisk.zip from recovery, and have been stubbornly avoiding update past magisk 23.0 and flashing 21.4 via twrp to avoid this new overcomplicated payload.bin dumper stuff. So far, I have updated my cheeseburger A5000 to A13 and 21.4 no longer works but as it is Aonly the boot.img is extractable without dumping. So, thats basically the very long way of asking if flashing Magisk 25.2 via recovery from your included recovery has been confirmed to work???

much thanks in advance
[OnePlus 9 Pro] TheSayaMan:
Magisk works fine and since you will have c63 and newer on both slots, you will not need to run the flash firmware but you will need to run the recovery bat file to install recovery. As a first time install, you can use twrp instead to go to this and it will work no problem but do not use TWRP on updates unless you plan on wiping because it will cause problems.
[OnePlus 9 Pro] Aballamis:
thank you for prompt response!

so, i could use the twrp-3.7.0-12.1-2-lemonadep to install ROM and Gapps & Magisk?
[OnePlus 9 Pro] TheSayaMan:
Yes, go to twrp, factory reset, and install ROM. After it done, go advanced wipe, wipe data and type yes, this will ensure you have a clean install. Reboot to twrp and install ROM again to make sure there are no errors, if so reboot and try again. When it's done, reboot to twrp to install gapps. Use mine, cuz other gapps may cause issues on updates. Then reboot to system. You can then reboot TWRP to install magisk. When flashing ROM, make sure you check automatically install TWRP, if you wish to keep twrp, because it will be overwritten after flashing ROM and will need to be re-installed before reboot.
[OnePlus 9 Pro] Aballamis:
many thanks!
[OnePlus 9 Pro] Aballamis:
last thing and i swear ill leave you alone . . .lol, been doing this for 6 years, feel like a noob again.

tried to install twrp, the official wont mount data (possibly because i'm in f.18) and the unofficial 3.7.0-12.1xxxx will boot but touchscreen doesn't work. others in that thread having similar issues. i even used your los recovery to sideload the unofficial twrp zip instead of booting the .img, still no touchscreen.

my question to you is, i downloaded a twrpinstaller.zip from your file repository. what's the deal with that? can i just sideload it from your recovery?
[OnePlus 9 Pro] TheSayaMan:
No touchscreen means firmware not on both slots. Flash my firmware flasher and that will fix the problem. And your not bothering me in the least, keep asking for help, I'll here for you.
[OnePlus 9 Pro] Aballamis:
I just tried to flash ROM with your recovery and it gave error:recovery: for device OnePlus9Pro but expected lemonadep

Then I was like, hmm, so I reboot to bootloader and flashed the firmware flasher and it gave errors for all partitions except modem_a & modem_b
[OnePlus 9 Pro] TheSayaMan:
Well that explains it. You have a Oneplus9 device and this ROM and thread is for the Oneplus9 Pro
[OnePlus 9 Pro] Aballamis:
The error says

Fastboot: error: could not check if partition <> has slot all

For all but modem_a & modem_b

I've got the MSM posted for my device, maybe I should do that and try again
[OnePlus 9 Pro] Aballamis:
No I've got a 9 pro
[OnePlus 9 Pro] Aballamis:
I just edited my post, I meant expected lemonadep. Durn auto correct
[OnePlus 9 Pro] TheSayaMan:
This ROM will only work on LemonadeP OnePlus9 Pro, it appears you have the Lemonade OnePlus9, so your device is not compatible with this ROM.
[OnePlus 9 Pro] TheSayaMan:
Ok it happens. You can use this then.
[OnePlus 9 Pro] Aballamis:
No, I have a Oneplus9 pro, lemonadep. The autocorrect changed what I typed to lemonade before I noticed
[OnePlus 9 Pro] TheSayaMan:
Yes, you can try MSM back and start over if you want. All OnePlus 9 Pro variants work with this ROM. I have the T-Mobile variant and others have Global and it works.
[OnePlus 9 Pro] Aballamis:
so i'm unppacking the msm but i hae global. i think where i may have goofed is not installing f.18 to both slots. i simply updated using the ota's until it was up to date. in your OP you state that A12 or A13 fw be installed on BOTH slots, but on your t-mobile you can msm back to 11 then flash the c66.

so, if i msm back to 11 on global oneplus 9 pro, do i need to update it thru ota to A12 BEFORE flashing the firmwareflasher.bat????

if so, how do i update to A12 or A13 on BOTH slots before continuing on to twrp or your recovery?
[OnePlus 9 Pro] TheSayaMan:
You can try just using the flasher from a11 but it might not work. Works for me with T-Mobile variant.
[OnePlus 9 Pro] Aballamis:
I'm going to try that if it doesn't work I'm downloading the twrp restore
[OnePlus 9 Pro] TheSayaMan:
Ok let me know. Since that restore is based off of Global, you will be fine.
[OnePlus 9 Pro] Aballamis:
I tried the twrp f.18 restore first. After boot to twrp, factory reset, restore, format data, switch slot, reboot to twrp . . . And the touchscreen wouldn't work on twrp anymore to repeat restore process on slot b.

I'm using msm again. I dunno if its f.18 has a touchscreen issue. Or if it's not having firmware flashed to both slots, then instructions are wrong, as there is no way to have fw flashed to both slots before rebooting to twrp to restore on slot b.

Funny thing, last time when I had upgraded to f.18 using Ota before flashing twrp, the unofficial wouldn't work w/touchscreen but the official would. This time doing the restore I was using the official. Doesn't make sense.

I'll msm back to 11, then use firmwareflasher.bat without twrp and see what happens.
[OnePlus 9 Pro] Aballamis:
fastboot: error: Could not check if partition abl has slot all

fastboot: error: Could not check if partition aop has slot all

fastboot: error: Could not check if partition bluetooth has slot all

fastboot: error: Could not check if partition cpucp has slot all

fastboot: error: Could not check if partition devcfg has slot all

fastboot: error: Could not check if partition dsp has slot all

fastboot: error: Could not check if partition engineering_cdt has slot all

fastboot: error: Could not check if partition featenabler has slot all

fastboot: error: Could not check if partition hyp has slot all

fastboot: error: Could not check if partition imagefv has slot all

fastboot: error: Could not check if partition keymaster has slot all

Sending 'modem_a' (208892 KB) OKAY [ 6.873s]

Writing 'modem_a' OKAY [ 0.618s]

Sending 'modem_b' (208892 KB) OKAY [ 5.844s]

Writing 'modem_b' OKAY [ 0.564s]

Finished. Total time: 14.015s

fastboot: error: Could not check if partition multiimgoem has slot all

fastboot: error: Could not check if partition oplus_sec has slot all

fastboot: error: Could not check if partition oplusstanvbk has slot all

fastboot: error: Could not check if partition qupfw has slot all

fastboot: error: Could not check if partition qweslicstore has slot all

fastboot: error: Could not check if partition shrm has slot all

fastboot: error: Could not check if partition splash has slot all

fastboot: error: Could not check if partition tz has slot all

fastboot: error: Could not check if partition uefisecapp has slot all

fastboot: error: Could not check if partition vm-bootsys has slot all

fastboot: error: Could not check if partition xbl_config has slot all

fastboot: error: Could not check if partition xbl has slot all

Press any key to continue . . .

this is what I got using your firmwareflasher.bat, straight from going back to 11 from msm.

this is the same thing that happened when i tried to use it before from f.18

thoughts???
[OnePlus 9 Pro] Aballamis:
I am noticing that in bootloader, "Product Name" is lahaina, which is the codename for the qualcomm board. I think this may be why when i tried to sideload the ROM it didn't work. I saw this in the "Nameless AOSP" ROM thread. if i remember correctly, the earlier builds were using the codename "lemonadep" but the newer builds used "lahaina".
[OnePlus 9 Pro] TheSayaMan:
Yea mine says the same thing. It might also be that your doing it on 11 and you have the Global variant which won't allow it. Try updating to A12 then try it.
[OnePlus 9 Pro] TheSayaMan:
Try also the firmware flasher from here and see if it works. I may have to update directions but no one else is having issues.

This will also install recovery so you can skip the recovery install in the OP.

https://sourceforge.net/projects/crdroid/files/lemonadep/8.x/firmware/OnePlus%209%20Pro%20C.63%20Firmware%20flasher.zip/download
[OnePlus 9 Pro] Aballamis:
Thank you again. I wanted a 10 series, but opted for the 9 pro only because I have gotten so used to and rely on features of root/customOS, as I said before I've been doing this for quite some time. Nowadays things have gotten so complex that one must really stay on top of the status quo and I have not. But I am quite surprised at the difficulties I'm facing. The touchscreen issue with twrp is one thing - as I've noticed several others in the thread for the unofficial twrp saying the same thing. However, they were all on f.18 A13, and the OP/author of thread said he isn't familiar with OOS13 and hasn't tested it yet and will look into it.

So, I will continue to try different things, including the flasher linked above and also updating via ota to A12 but not continuing on to f.18. I just don't know how to get the same OTA fw on both slots, but we'll cross that bridge when we come to it.

One thing I'm worried about is that my 1+9pro is brand new. I just got it from best buy. With the recent OPPO merger and OnePlus' decisions with kernel source & msm for 10 series, I'm just worried they've implemented something in later build date models of the 9 pro or something that's causing me grief.
[OnePlus 9 Pro] TheSayaMan:
If they did implement something, it would get wiped away when you msm back so I don't know how that's possible. I updated to f.18 with my T-Mobile variant that I converted to a Europe then did local updates to f.18 Global so I'm on same stock firmware. The only thing I can think of, is the specs are still different on my phone, that it works for me.
[OnePlus 9 Pro] Aballamis:
When I attempted to use your firmwareflasher.bat the first time I was on f.18 and encountered the same errors for all partitions except modem_a & modem_b.

But I will continue to try things until I get profit. Profit, or refund from best buy, lol.

Also, I thought about fastboot enhance program and possibilities.

Or could I try your firmwareflasher.bat from fastbootd? Or does it require different commands? Not too familiar with fastbootd
[OnePlus 9 Pro] TheSayaMan:
If you use fastboot enhanced or even payload dumper, you end up with the same boot.img, vendor_boot.img and dtbo.img that I already supplied inside the recovery flasher to install recovery.
[OnePlus 9 Pro] gillim74:
Extract the firmware zip copy its contents into your adb folder.if it dont flash that way from bootloader use custom recovery and put the phone in fastbootd mode from recovery and flash.
[OnePlus 9 Pro] Aballamis:
The error im getting is "could not check if partition < > has slot all", so my guess is that it will flash, but the .bat flasher was written with commands to flash each partition file to "all" slots for that partition, and for whatever reason it says it can't check if partition has slot all. So I may be able to manually flash each partition file. I just don't know if each and every one would be like "fastboot flash abl_a abl.img" "fastboot flash abl_b abl.img" and so on.

I thought about using fastbootd, just wasn't sure as to what the possible outcomes might be.
[OnePlus 9 Pro] TheSayaMan:
Did you try the c.63 firmware instead?
[OnePlus 9 Pro] gillim74:
Thats how i got it to flash other wise itwould error out.
[OnePlus 9 Pro] Aballamis:
No, not used to so many roadblocks, ill look for that fw.
[OnePlus 9 Pro] Aballamis:
You mean fastbootd or manually?

If manually, am I on the right track with "fastboot flash <partition>_a <partition>.img" "fastboot flash <partition>_b <partition>.img"?
[OnePlus 9 Pro] TheSayaMan:
I posted it before on above posts. I updated the OP instructions with the c,63 firmware flasher. Try that.
[OnePlus 9 Pro] Aballamis:
Many, many thanks.

I've never had anybody, much less a thread author/dev be so responsive and helpful. Not even close. I do appreciate it.
[OnePlus 9 Pro] TheSayaMan:
No problem, anytime. Hopefully you can get it working. Let me know.
[OnePlus 9 Pro] Aballamis:
I will. I just had to msm back again as I was going into crashdump mode at every boot. Maybe bc of trying to flash c66 with your .bat from a11.

Going to unlock BL, then try the c63 flasher 1st. If no luck, ill probably ota to A12 (although the ota states f.17 fw but doesn't update to that right away, you have to go thru several updates, all stating the same fw, to get to f.17), then use your recovery flasher and from there go to fastbootd and try your firmware flasher. As I believe that's what gillim74 meant in his last post that he had to do to get it to work. Then, if necessary, ill extract the c66 from your bat and flash them all manually to a & b.
[OnePlus 9 Pro] TheSayaMan:
Flash the firmware flasher by starting in the bootloader. c.63 will do all the work for you including booting to fastbootd to flash the critical partitions. It will also install the custom recovery.
[OnePlus 9 Pro] Aballamis:
Ok. I just got done unlocking BL after update to A12. But it was the 1st update to get me to 12 so I imagine the last A11 is on other slot. We'll see what happens.
[OnePlus 9 Pro] Aballamis:
Profit! At least with the c63. No errors in flashing.

I assume I can use the crdroid los recovery to sideliad the rom. Well, I'm gonna and see what happens.
[OnePlus 9 Pro] TheSayaMan:
Yes, it will work. My ROM uses crDroid and LineageOS sources and dependencies, so your fine. I removed the c.66 flasher. Doesn't work with all the variants as it turns out.
[OnePlus 9 Pro] Aballamis:
PROFIT!

Yea your ROM def uses crDroid, says it everywhere.

Thanks again, I'm to the moon right now. I'm prolly still gonna f*** it up again a little, I've got some mods I gotta at least try. And we'll see what happens as far as unofficial twrp. Not sure if I can sideload zips of other mods. Like Dolby digital plus by repey6, latest ver says A11 but it works on my 1+5 with LOS20.

Meant to ask a while ago, is there a native call recorder? If no, do you have any idea if the OOS dialer will work to enable recording? I can always use the magisk mod one, but the native one I've used b4 built into the dialer on RR A10 on my 7pro is just sooo convenient.
[OnePlus 9 Pro] TheSayaMan:
There is a default recorder on the ROM, though I never really tried it for that purpose to be honest and not on the dialer. I can definitely see about implementing one in it, no guarantees. I would also be careful with twrp. It doesn't play nice on my updates but as far as other things, you can test it. I tried flashing blue spark kernel with twrp and bricked and had to flash latest update again with custom recovery to recover from it.
[OnePlus 9 Pro] jamescable:
GitHub - chenxiaolong/BCR: A Basic Call Recorder for rooted Android devices

A Basic Call Recorder for rooted Android devices. Contribute to chenxiaolong/BCR development by creating an account on GitHub.

github.com
[OnePlus 9 Pro] TheSayaMan:
That works, thank you sir
[OnePlus 9 Pro] Aballamis:
The BCR will definitely work, however, upon looking in the dialers settings, under sounds & vibration, there are options for call recording audio format and auto call recording, so I'd imagine it is in there
[OnePlus 9 Pro] TheSayaMan:
New update: 01/14

Upgrade from Android 13.0 to Android 13.1

I am still working on the minor issues. I couldn't publish a test build because upon further testing, my phone went into crash dump hard brick mode and had to MSM back. That also included trying to build the ROM with gapps included. That will be a lost cause unless I can get help.
[OnePlus 9 Pro] mettis88@gmail.com:
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

Please Changelog for rom?
[OnePlus 9 Pro] TheSayaMan:
First 13.1 build

- Updated to January 2023 security patches (android-13.1.0_r20)

- Launcher3: Move memory info to bottom by default

- Launcher3: InfoBottomSheet: Fix NPE with AppTransitionManager

- Add support for Lockscreen clock fonts

- Add support for GMS switch for ParallelSpace

- Fixed Youtube application when moving to PIP animation

- Fix black screen issue due to wallpaper decoding exceptions

- Fixed wallpaper selector

- Styles: Use user fonts for Material UI themes

- Override system fonts with user-selected overlays

- Small changes to VolumePanel

- Small changes to status bar icons

- Small refinements to Settings

- Updated bionic

- Updated translations
[OnePlus 9 Pro] TheSayaMan:
GitHub - MikeSaya1/Lineage

Contribute to MikeSaya1/Lineage development by creating an account on GitHub.

github.com

github repository published to public

Forked from crDroid
[OnePlus 9 Pro] rogermxl:
Would be so great to have a TG group :)
[OnePlus 9 Pro] TheSayaMan:
I'm looking into that next
[OnePlus 9 Pro] psychemisha:
It seems gpay broken on last build
[OnePlus 9 Pro] TheSayaMan:
Did you local update from a previous build or clean flash current?
[OnePlus 9 Pro] psychemisha:
Something was wrong with the bank side i tried today all fine
[OnePlus 9 Pro] TheSayaMan:
Ok good
[OnePlus 9 Pro] psychemisha:
Can we get propper heptics in this like on nameless or derp?
[OnePlus 9 Pro] TheSayaMan:
Doubtful. I tried merging my build before to include gapps in my build, using nameless and it resulted in a crash dump and I couldn't publish the build. But when I have more time, I can try messing around with it further and see what I can do.
[OnePlus 9 Pro] TheSayaMan:
Update 01/18:

Minor changes to status bar icons

Made changes to advanced color control using my wife's OP8T which works on her phone running Pixel Experience. Implemented it to work on OP9 Pro.

Long press on fingerprint scanner is still broken.
[OnePlus 9 Pro] vipinpvarghese:
Flashed the latest build.... So far excellent.... Hats off to @TheSayaMan for regular updates to the ROM. No other ROMs updated so frequently here like yours....
[OnePlus 9 Pro] TheSayaMan:
I appreciate the kind words. Thank you!
[OnePlus 9 Pro] MrSinister:
@TheSayaMan Any news on prebuilt gapps build?
[OnePlus 9 Pro] HessNL:
So this is working with oos 13? If yes I'm willing to try it and is it also flash able with twrp adb sideload?
[OnePlus 9 Pro] TheSayaMan:
Use twrp only on fresh installs otherwise you will have problems as the directions state. Makes no difference whether you sideload or not.
[OnePlus 9 Pro] TheSayaMan:
Yes, working on stock 13, no to using twrp unless you want problems, read the instructions!!!!! I state how to retain twrp if you want it
[OnePlus 9 Pro] TheSayaMan:
I tried and gave up. You can still avoid boot errors anyway without prebuilt gapps and not everyone wants gapps.
[OnePlus 9 Pro] TheSayaMan:
Update: 01/20

Synced updated LineageOS & crDroid GitHub repositories
[OnePlus 9 Pro] TheSayaMan:
Done

WatchDogs

Rom development

t.me
[OnePlus 9 Pro] kodayoda713:
Any chance you could include SF Display Pro font as a font option? I can extract the APK from Nameless if that helps. Not sure exactly how that's implemented, but would love that option. Rom is wonderful and thanks for all you do.
[OnePlus 9 Pro] TheSayaMan:
Don't know anything about it so yes, send me the apk, I'll have it added on. With the apk, that is easy to do. I plan on pushing another update tomorrow, so the sooner you can, the sooner I can add it on.
[OnePlus 9 Pro] kushsix:
Can you add the extra fingerprint animations from Evolution? It's only like 3 or 4 I think.. but anyways, killer builds man. Smooth as silk homie.
[OnePlus 9 Pro] TheSayaMan:
I will see what I can do.
[OnePlus 9 Pro] kodayoda713:
Is the latest (1/21) build safe to update to?
[OnePlus 9 Pro] TheSayaMan:
I am updating now and I will let you know. I've been busy with work. That build is a incremental automatic self build. The only change from 01/20 is the build date, so I would think it will be ok but I never assume. I'll let you know.
[OnePlus 9 Pro] kodayoda713:
No problem, take your time. Thank you sir
[OnePlus 9 Pro] TheSayaMan:
It works fine. Sorry for the late reply. Long day at work and I totally forgot.
[OnePlus 9 Pro] jamescable:
Can you direct me to the livedisplay commit?
[OnePlus 9 Pro] TheSayaMan:
Update: 01/22

Repository updated to version 2b54c23

This is going to be more difficult than I thought. Something obviously from the source, base, dependencies, something is preventing it from being added. The build kept failing even after several attempts and even after trying to move things around. I need to find out what it is, and have it removed so it will allow that but at the same time, I can't allow it to cause more problems with something else potentially. I had to basically delete today's build or everyone would end up in crash dump mode like myself.
[OnePlus 9 Pro] jamescable:
Ouch, well....can you link me to the github commit for it?
[OnePlus 9 Pro] TheSayaMan:
My GitHub is listed in OP
[OnePlus 9 Pro] jamescable:
😂 I have no idea how to navigate github to find the commit for livedisplay
[OnePlus 9 Pro] TheSayaMan:
Right now it's not there because if anyone tries building it, with it there, it will cause a crash dump. Live Display is basically part of where I get the ROM source. It would be in Android, hardware, (ROM source), in my case Lineage, and Livedisplay.
[OnePlus 9 Pro] bbortel93:
Great rom, thank you!

I've only just flashed about an hour ago, I've only run into one issue so far. The double line lock screen clock is overlapped. Any suggestions?
[OnePlus 9 Pro] unosison90:
Hi, I've been on the release version of this rom and would like to update. I'll just use OTA via local storage, right? No additional steps/wipes? Thanks and great work!
[OnePlus 9 Pro] TheSayaMan:
Correct as listed in OP, if you have magisk and want twrp recovery, you can flash the twrp zip as a magisk module after rebooting update. Don't use twrp to update, you will have boot errors.
[OnePlus 9 Pro] TheSayaMan:
I don't have this issue. Maybe some one else can confirm this. It might be device/variant specific.
[OnePlus 9 Pro] David_#27:
I assume there's no alive telegram group...

The one listed in the OP doesn't contain anything.
[OnePlus 9 Pro] TheSayaMan:
The group is new and does not have any activity as of yet. You can download the app on your phone and join the group if you want. There are currently 21 subscribers.
[OnePlus 9 Pro] TheSayaMan:
I am working on a gapps included build which is taking extra time. So the next update might be awhile. This is to avoid boot errors for those who wish to use twrp recovery.
[OnePlus 9 Pro] TheSayaMan:
I previously stated doubtful but it will be included. I'm working on a gapps included build that will also include this.
[OnePlus 9 Pro] kodayoda713:
Was wondering if you or anyone experience a boot animation glitch when switching to QHD resolution? It's harder to notice with the watchdogs boot animation, but it basically glitches smaller for a brief second towards the end of the animation
[OnePlus 9 Pro] bbortel93:
Yeah I'm getting it too. Doesn't bother me though.
[OnePlus 9 Pro] TheSayaMan:
Sure does, known minor bug, shouldn't be much of a concern.
[OnePlus 9 Pro] kodayoda713:
For sure, just checking if I was alone haha. Thanks