yashsingh1/xdaforums huggingface dataset:
[OnePlus 9] applyscience:
a good rule is to always assure you are on the same android release. there are rare occasions when some ROMs are one android release higher (ex. being on OOS12 but flashing ASOP13)can be flashed, but that is usually during the initial release of a new android ROM version.

In this instance, updating OOS to the latest official release, re-rooting and then flashing this ROM is your best bet.

You can do so by utilizing any MSMToolkit to restore factory OS, update it until you're on the latest version, and then root/flash.

While time-consuming, it's the safest starting point when moving to ROMs based on newer android versions.

If you are looking for a faster route and feeling adventurous, there are packages that can be flashed to automatically flash OOS13 to both slots in recovery, which would allow you to just reboot and then flash this ROM, completely bypassing the need to break root, update and reroot.

Exmple: crdroid's Firmware flasher

While saving considerable time, you are removing yourself from the process, (putting your faith in someone else's script) Also, if something goes wrong, not only will you have a harder time pinpointing what is wrong, you are robbing yourself of the wonderful education from just going through it on your own.

TL;DR: if you haven't run any A13 ROMs yet, i would just break your current ROM with MSM, start from scratch with the latest OOS and reroot.

PS. you will need to flash vendor_boot and dtbo.img, along with boot.img with all A13 ROMs on OP9 devices. Easiest thing to do is just dump the payload of all 3 (boot, dtbo and vendor_boot) from any ROMs zip.

you can get this with a payload dump command in java but the easiest way is by utilizing fastboot enchance

PPS. Here is an older full walkthrough i wrote up of the whole process of flashing A12/13 based ROMs on OP9. just be sure to update the filenames for your usecase.
[OnePlus 9] TimmyP:
im ready to go with that, I already have the MSM tool even backups.

Im just curious as to how the Bootloader is unlocked in A13 on Tmobile? Im on global now, so I use MSM to bring me back to stock... but stock locks the bootloader. I had to convert to global, which only converts phones on A11OOS11, which then gave me the option to unlock bootloader without token. On the tmobile firmware, I needed a token to unlock bootloader... Wont I need token to unlock bootloader on A13?

I was told I can take the boot image from MSM after I update over OTA fully, and patch that with magisk and reflash... but am not able to confirm the user had a Tmobile phone when doing this. If the bootloader is locked, I wont be able to flash an extracted and patched boot image.
[OnePlus 9] mizarddo:
I'm sorry if this question is irrelevant here but I need HELP

how can I modify or replace system files on this rom?

I have root with magisk but when I try to paste and replace system files in any file manager I get some kind of error like not enough space or task failed.
[OnePlus 9] shadabkiani:
Are you replacing files, or adding them? With dynamic partitions, this ROM only creates system partition with only a few MBs free. Use Root Explorer and when you navigate to /system/ it will show free space on top. Also, it's better if you share the screenshot of error.
[OnePlus 9] sv-xda:
I have the problem with sound of incoming calls. I hear sound only on my smart watch, not on phone itself. It works well for Default Pixel sounds, but for others groups and those manually downloaded in folder Ringtones - hear correct sound only on smart watch, phone just silent.

Any ideas how to fix?

Phone LE2113, smart watch Garmin Venu 2 Plus, Nameless build from 2023/03/20.
[OnePlus 9] mizarddo:
Thanks for the quick response.

So this is the exact situation:

Just a few days ago the daylight saving rules were changed and basically scraped in Iran so there's no change at summertime. Meaning from now on there will be no +1 hour for this timezone. But this rom does not have an updated tzdata to apply that so I'm getting the wrong time on automatic time setting and manually changing the time makes vpns stop working. They are essential tools here due to heavy limitations and restrictions.

What I wanted to do was manually replacing the tzdata file in this directory with a new one:

/apex/com.android.tzdata/etc/tz

While most file managers just gave an error one of them did delete the 2 original files but failed to paste the new ones.

Root explorer suggests there's more than 3mb available but solid thinks there's none. The two files are around 360kb.
[OnePlus 9] shadabkiani:
From what I understand, apex are temporary filesystems I think.

Hmmm, well, let's check this. Maybe it will get to somewhere. In Root Explorer, create a new empty file (just name it whatever you want) in that folder and see if it still gives you any error. Also create a new file in /system/ and see what happens.

Another idea: Boot TWRP (temporarily by the command fastboot boot your_recovery.img), mount system, and then copy/replace your file.
[OnePlus 9] mizarddo:
I can create empty files. I made a txt file but when I try to write something in it and save, that fails too. Tried the same in the SYSTEM/USR/share folder too. Same result.

Didn't get a chance to try twrp so far
[OnePlus 9] shadabkiani:
Open Root Explorer and navigate to /system/ and see how many Free MBs are there, like in the picture above.
[OnePlus 9] mizarddo:
Basically the same report in all paths.
[OnePlus 9] mattie_49:
Maybe we should get back on track for what the thread is for. To much off topic
[OnePlus 9] shadabkiani:
That's weird. Your /system/ is already mounted as R/W, and there's free space too. Anyway, keep trying. 👍
[OnePlus 9] applyscience:
mizarddo with such a unique situation you find yourself in, you may want to start a thread of your own here in the Op9 section. Not only to keep this thread on the proper subject, but I think many people could benefit, and with its own thread, will be easier to search for by all in the future. (not to mention, give you're issue more exposure and a thread made just for it to troubleshoot it better)

good luck!
[OnePlus 9] mizarddo:
Sure did. Thanks!
[OnePlus 9] YEABOIIIII:
Can you flash this rom from oos 13 f75?
[OnePlus 9] Nhatlienhoan:
After doing a reboot, my phone will freeze itself. It boots ok, and everything seems fine but after a minute or so, the phone freezes and reboot itself and freezes and reboots...

This is the second time it happens. The first was fixed by format and clean install but if I reboot the phone, this happens again. Do you think it's maybe gapps problem??
[OnePlus 9] mizarddo:
Are you flashing gapps separately? If yes then...don't. it's already included with the rom.
[OnePlus 9] Nhatlienhoan:
I don't. I just flash the rom itself cause ai know it's included.
[OnePlus 9] mizarddo:
Do you use any magisk modules that could make trouble?
[OnePlus 9] Nhatlienhoan:
I

I don't think so. All of them were used on my 5t for years. It was mixplorer, viper, safetynet. That's all. No kernel or anything. But I noticed when I reboot and the problem occur, mobile doesn't show signal, youtube vanced lost app. (Actually that's the reason I reboot to see if it solves the problem).
[OnePlus 9] by_BenjamiN:
Will you solve the 4K 60 fps problem?
[OnePlus 9] mizarddo:
You should still try and remove all your modules before reboot to see if the problem persists. Also you don't need the outdated YT vanced module. Just install revanced manager it will let you patch new versions of youtube app yourself. Just install the recommended yt version by the manager before you patch.
[OnePlus 9] Nhatlienhoan:
Will try. I just thought that until vanced doesn't work anymore, I'll change to Revanced. Cause Vanced still works well for me.
[OnePlus 9] Nhatlienhoan:
Remove all modules, removed YT vanced, reboot and it stills froze and rebooted itself after some minutes.
[OnePlus 9] Nhatlienhoan:
I even uninstall Magisk and the problem is still there.
[OnePlus 9] mizarddo:
Have you tried a different rom? Are you sure it's a software issue?
[OnePlus 9] Nhatlienhoan:
I'm not sure if it's a software issue. It never occurs with OOS. But my phone was functioning normally before I was dumb to manually reboot it (saw somewhere that you should reboot your phone sometimes) and this happened.
[OnePlus 9] YEABOIIIII:
This has been an amazing ROM, Than you, but sadly I have to stop using it. Because I dropped my phone in the water while ice fishing, does anyone have a good idea for a new upgrade?
[OnePlus 9] mizarddo:
Don't blame yourself, you couldn't just never reboot it. If OOS works well then at least your unit is fine.

Next thing that crosses my mind is the rom's prequisites. Did you make sure you have the required base OOS installed on both slots before flashing the rom?
[OnePlus 9] mizarddo:
If I had to upgrade I'd have obviously gone for that sweet pixel 7 (not pro)
[OnePlus 9] Nhatlienhoan:
I'm sure all the prequisites were met. Now you mentioned it, sometimes in OOS, I have issue such as QS couldn't expand. I could see the first two rows but couldn't see after. If I access the settings, I can still adjust or access them through settings but not via QS. Reboot usually solves it. It happened once with Nameless too and reboot solved it too.
[OnePlus 9] shadabkiani:
Well, even at stock OOS, bugs might appear after OTAs, so it's recommended to do a factory reset after OTA if there are bugs. Last time I was on OOS, I remember there were bugs like RAM expansion feature could not be opened, OEM unlocking was greyed out with error saying connect to internet even though I already was, and there could have been more that I didn't check. I just did a factory reset and bugs were gone.

So I would suggest you to revert to OOS (through MSM tool), do a the OTAs all the way to the latest, and do a factory reset. Then use your phone for some time and see if you still face any issues. That would narrow down your issues' root causes at least, be it software or hardware.
[OnePlus 9] YEABOIIIII:
I have thought of pixel 7, but i have an ok phone as a backup, so i may wait for the Pixel 8
[OnePlus 9] chandu dyavanapelli:
New build up

Source changelog:

- Merged April security patch with QPR2 rebase (All features are there compared to last build)

- Added System Vibration QS tile to quickly disable all vibrations

- Many underhood code improvement

Device changelog:

- Fixed haptic feedback not working on Eva Kernel

- Kernel upstream to 240

Note: Take backup before flashing this build and if anyone notice any major issue after flashing the new build, then do factory reset.

Gdrive mirror:

Nameless-AOSP_lemonade-13.0-20230415-1619-Official.zip

drive.google.com
[OnePlus 9] mizarddo:
Sounds like a plan, mate! Good luck.
[OnePlus 9] bizkit_120:
My op 9 oos13 stock rom SOT is ridiculous. only about 3 hours ish ,no gaming no social media just Reddit, slack , work email, browsing..

🤔 Thinking about switching to nameless, wondering what sot you guys can get on this rom? Thanks
[OnePlus 9] shadabkiani:
Great. I just installed this ROM for the first time, and I just noticed that the default font is Google's Product Sans; and not that boring Roboto. THAT'S AWESOME. I have been looking for a long time for a ROM that implemented Product Sans right out of the box. Before, I would always replace Roboto font files in /system/fonts with Product Sans ones (I downloaded them from XDA, and there are 20 files) so that every font style (bold italic thin whatever) would be replaced by Product Sans. However, the drawback was that some of the characters were unsupported.

But this ROM has Product Sans as default and all characters are good. So I need to extract these font files. The problem is that I cannot find the actual font files that are actually being used. Now generally files starting with Roboto- in /system/fonts/ are used as default, but not in this ROM, I checked. Even deleting that Roboto-Regular.ttf or replacing with other font file doesn't make a difference. Hence, it is clear that the default font (which is Google Sans) is being picked up from somewhere else. I know there is /product/fonts/ too but the default font is not picked from there either.

So my question is where are the actual default font files (that is Google Product Sans) that are being used in this ROM? Please, this is important. If you could help, I would really appreciate it. I have been looking for this for so so so long (years actually) to get the right Google Product Sans with supported characters, just as in this ROM.
[OnePlus 9] valerii12:
Hello, an error in the Russian version. Some settings menu items are missing. There are no such problems in the English version.
[OnePlus 9] chandu dyavanapelli:
Known, it will be fix in next release.
[OnePlus 9] rawello:
there is no two SOT the same time, every day different SOT, at sunday i have much more SOT than on weekdays, average from 5:00 to 22:00 as 6HR
[OnePlus 9] bizkit_120:
Hello all, few questions related to this rom before i finally onboard, My current stock ROM oos13 op9 except battery draining too fast, everything else works. ,Some key features that I don't wanted to lost as those are too important for me , can anyone pls confirm to me are those listed features works on nameless

Voice recorder - currently using BCR , someone posted on XDA that Google latest patch blocked call recording API again

ViPER

Google Pay

AccA

can't live without lock screen gesture, does nameless come with some build in lock screen gesture

Last dumb question,do I have to flash custom kernel?

Thanks 🙏
[OnePlus 9] mizarddo:
Broke dt2w again. tzdata still not updated. For some reason it broke the pixel launcher mods too.

Going back to previous build for now.

Edit: okaaaay sb had to tell my dumbass I can't downgrade. The boot was unsuccessful but switching to the other slot helped me get back. Stuck on this build for now I guess.
[OnePlus 9] ArniPL:
This never worked for me on this ROM. AOD just goes to "deep-sleep" after a while. When this happens, double tap doesn't work. This also breaks custom AOD brightness.
[OnePlus 9] mizarddo:
I have the custom AOD problem too. But dt2w worked on most builds except this current build and the one before last one.

I didn't even make any change. Went away with an update. Returned with the last update and went away again with this update.
[OnePlus 9] mizarddo:
Found another one on my unit. The power button can't turn on the display BEFORE AOD goes to deep sleep.

Now I have only one method to wake my decice in each state. That'll keep my senses sharp.

That's new
[OnePlus 9] ArniPL:
That doesn't happen to me, but then again I am on the older build. Will wait with the update until the bugs are ironed out.

Weirdly enough, even after AOD enters the deep sleep state, the additional AOD gestures are working fine. So I can set one-tap gesture to "show AOD". Then, when phone is sleeping, I can tap once, and then double tap to wake. So... thrice-tap-to-wake. With a slight pause after the first tap. 😅
[OnePlus 9] mizarddo:
Found another bug. When I swipe up to home on mx player landscape mode, I get 2 clocks And date in statusbar. I use the one in the middle. The one on the left is the glitch.

sb help me go back to last build.
[OnePlus 9] TrumpXi:
Strange, I don't encounter any of the issues you've mentioned, I tested going from YouTube premium playback in landscape to home screen (PiP) does not cause glitches, maybe you are more prone to glitches because you put the clock in the middle of statusbar

If you want to go back, I suggest make a Swift backup and clean flash
[OnePlus 9] towe96:
Hi!

I've been using this ROM for a few days without issues and tried to do the update today. I installed it via the OTA tool and then flashed Magisk again with the "after OTA" option.

Now my phone is stuck in a bootloop, only getting until the Pixel loading screen and then resetting.

I tried changing the slot back to A, but then it doesn't even get to that.

I suppose it's completely shot now and I'll need a factory reset?

I did manage to get it started in safe mode at least...

I did a local upgrade from within safe mode in order to get Nameless back on slot A. Did lose Magisk for a while since that was disabled in safe mode, but that was easily fixable.

Might this be related to a different OOS firmware on one of the slots? If so, is it possible to remedy this now without a full reset and local-upgrading OOS onto both slots?
[OnePlus 9] TrumpXi:
It might as well be a module that is incompatible with QPR2

But if you suspect firmware issues, you can use Florian's firmware flasher https://mega.nz/folder/W7JhwTAT#Yu6cxqvJcAC28cy0m_kkQA to reflash your firmware
[OnePlus 9] towe96:
Yes I believe it's caused by a module at this point. I went to reenable my three modules since I needed systemless hosts again for AdAway and it happened again. The other modules are the Universal Safetynet Fix and Disable Flag Secure.

Will investigate which one broke.

It may have been caused by Disable Flag Secure since other user also reported bootloop with some frequency.

After removing all modules from Magisk and reinstalling them, everything seems to work correctly now.

So, TIL: Remove and reapply "deep" Magisk updates when doing an OTA
[OnePlus 9] bigd2442:
Im having my phone app not connect and immediately close with outgoing and incoming go straight to VM... reboot fixes it. It was happenig about once every day now even with reboot it happened just a few hours later again.

Factory 2125, US Verizon. Nameless full install (20230415) over OTA F17. Nameless kernel, no other changes.

Is this something that anyone else is experiencing?

What steps can i take to try and correct?

*reflash the rom?

*different kernel?

*flash radios?
[OnePlus 9] applyscience:
idk, this broke safety net asap when i updated. mostly everything works though.
[OnePlus 9] shadabkiani:
I am on the latest build, and safetynet is fine. I did a clean flash though.
[OnePlus 9] applyscience:
Lack of Clean is probably my issue.

I msntoolkit my phone a month ago and updated to the latest OOS13 for the first time, prior to rom install (prior was just A12 with recompiled updates in OOS13, not it installed itself.

Also, it's worth noting how magisk just updated to 26.1 and was using Google call screening for years until a few weeks ago.

I will just msm over the weekend, thanks for letting me know.
[OnePlus 9] chandu dyavanapelli:
Hotfix build up

Source Changelog

• Allow to restrict per-app network access

• Added auto high brightness mode on strong light environment

• Added more options to long swipe back gesture (Turn on notification panel/qs panel/volume panel; Turn off screen)

• Adjust lockscreen clock spacing for some fonts

• Fixed Gboard translation

• Fixed crash on some games

• Fixed messy settings on multi users

• Fixed power button cannot wake screen when power button torch is enabled

• Fixed showing double statusbar clock randomly

• Fixed high battery drain on pixel launcher

• Fixed disable hesds up in landscape mode not working

• Fixed GameSpace crashing in landscape mode for some users

• Fixed Russian translation

• Fixed NTFS OTG

• Nameless Launcher: Fixed narrow spacing between docker icons when taskbar is on

• Re-link notification and ringer volume (Follow Google stock now. Would add a toggle in feature)

• Removed scheduled mode for dc dimming

• Switched to StagBin for app crash log upload

• Other fixes that I may forgot

Device Changelog

• Updated blobs from COS F.23
[OnePlus 9] shadabkiani:
@chandu dyavanapelli Could you please tell me where are the default font files (i.e. Google Product Sans) located that are being used in this ROM as default? I know they are not in /system/fonts/ or /product/fonts/. I would really appreciate it.
[OnePlus 9] dsfgear:
Just tried latest build (updated from 0320 build), double tap to wake is still broken.

Also tried factory reset, dt2w still doesn't work..

Going back to 0320 build again.. Really like this rom, hope dt2w could be fixed soon.
[OnePlus 9] Vmo x:
Last update I seem to not be able to download from sourceforge nor being able to download update through the system updater.
[OnePlus 9] rodri_rebag5:
Same, can't download it from anywhere
[OnePlus 9] pawelmiernik:
Both bluspark and eva kernels fix dt2w on this and other roms if you want to be on latest build
[OnePlus 9] Vmo x:
You should try today. The server is back up
[OnePlus 9] mizarddo:
Well, just tried eva on the latest build and...no it doesn't.

Edit: credit where credit is due, bluspark did. Thanks.
[OnePlus 9] pawelmiernik:
5.4.242-eva-r2b2-nqgki-g15f1078e34e2

#1 Wed Apr 26 18:19:30 UTC 2023 is what I have installed and the rom build is TQ2A.230405.003.E1

Nameless-AOSP_lemonade-13.0-20230426-0423-Official and double tap to wake works flawlessly from blank screen and aod if I have it enabled. Check your settings, it might be turned off somewhere.
[OnePlus 9] mizarddo:
It was turned on, it stopped working right after the previous update without me changing anything and it wasn't fixed for me after the hotfix update.

I flashed the bluspark kernel and it fixed dt2w, again, without me changing any setting. So nah it wasn't me.
[OnePlus 9] pawelmiernik:
Great so the kernel did fix it! Next time try latest eva found here https://github.com/mvaisakh/oneplus9pro/releases - the latest one from 3 days ago, as of this writing, has working dt2w also
[OnePlus 9] dsfgear:
You need eva kernel release 2 at least, release 1 doesn't include fix for dt2w:

I'm using release 2 on my phone with latest rom and dt2w works just fine.

This is the one I flashed:

eva-lemonade-210420230315-gcc.zip
[OnePlus 9] firoz990:
hello sir can you please update to lastest versions of all camera of OP9 cause the picture qualities are too bad and more over camera app crashes while taking photos in this update please fix..

ll
[OnePlus 9] rodrigodcf:
Hello, I'm suffering with the battery of the Stock Rom, is this better? Is it compatible with LE2111?
[OnePlus 9] nmh5001:
Latest update doesn't have great battery life and there are issues with the camera crashing. Previous update was quite good.
[OnePlus 9] mattie_49:
I'm almost positive oos cam issues are from throttling. And oos only thing getting good battery life currently.
[OnePlus 9] dsfgear:
Are you using pixel launcher? I used to have battery drain issue with pixel launcher, then I switched to nameless launcher and battery drain is normal. Latest update says pixel launcher's battery drain issue is fixed but I never switch back to test.

Idle drain is about 0.3%/hr according to FKM, with naptime enabled.
[OnePlus 9] pawelmiernik:
hey my man, would you mind posting a link to this nameless launcher you're talking about please
[OnePlus 9] dsfgear:
It's built in, just go to settings, apps and under launcher switcher section, change default launcher to nameless launcher and reboot.
[OnePlus 9] rodri_rebag5:
Any issues with the May update? Haven't seen anyone comment on it
[OnePlus 9] mizarddo:
In

Installed it yesterday. Seems to be nice and stable. Everything is working fine. Now it's just back to the outdated time zone data file which is not an issue for anyone.
[OnePlus 9] chandu dyavanapelli:
New build up

Source Changelog

- Merged May security patch (android-13.0.0_r43)

- Allow to block accelerometer and gyroscope sensors for apps (Settings - Privacy)

- Allow to disable QS pull down on lockscreen

- Allow to use inputmethod haptic feedback with touch feedback disabled

- Fixed app network access on secondary user

- Switched to long press for lockscreen shortcuts

- Removed broken "swipe to wake" option

- Minor fixes and improvements

Device Changelog

- Kernel upstream to 242

- Added four ringtone vibration effects from OOS

- Fixed failed to save the capture pictures in OnePlus camera

- Fixed DT2W for OnePlus 9 device
[OnePlus 9] nmh5001:
Latest update seems to have fixed the battery drain issues as well. Thanks for quickly addressing the issues from the April update!
[OnePlus 9] mattie_49:
T

This is good. Last time I tried build battery drain in background was pretty bad. Do all levels of video work on oos Cam please and ty beforehand. . Slo-mo,4k,8k?