Oh, I always keep mine at FHD but when I switched to QHD I saw the same issue.Good idea.
Looks like the spacing issue goes away if I set my screen to Full HD, but it always comes back if I set it to Quad HD.
Oh, I always keep mine at FHD but when I switched to QHD I saw the same issue.Good idea.
Looks like the spacing issue goes away if I set my screen to Full HD, but it always comes back if I set it to Quad HD.
I soft bricked my Oneplus 8 Pro.
As an experiment, I tried to patch boot.img myself. however, it gives me bootloop.
Then I downloaded the patched boot.img by g33gz.
sudo ./fastboot devices
[sudo] password for j:
0e4b5a39 fastboot
As always, thanks. Nice to see that in the mix of all of these new phone launches we are sticking around. I'm tempted to 'upgrade' but there's no clear move from the OP8 to me.I've attached the non-patched and patched boot.img's for IN2025_11_F.62
Yeah, the OP8 Pro I have is still more than capable for what I'm doing.As always, thanks. Nice to see that in the mix of all of these new phone launches we are sticking around. I'm tempted to 'upgrade' but there's no clear move from the OP8 to me.
I did the complete uninstall and the triggered reboot as well but when I go and attempt to update, it gets through the whole process but then gives me an error when I go to complete the update (pressing the reboot button)I completely uninstalled Magisk which forced a reboot. Then took the ota successfully followed by another reboot. Everything seems fine but I haven't sat down to boot your patched imaged and patch my own.
Weird, so I got it to work by enabling the option that installs the update on reboot + disabling debugging in the developer menu. Then I rebooted the phone by holding the power button and selecting the reboot option...I did the complete uninstall and the triggered reboot as well but when I go and attempt to update, it gets through the whole process but then gives me an error when I go to complete the update (pressing the reboot button)
I havent even gotten to flash the patched image yet![]()
Glad you got it to work. I've noticed two things that I'm pretty happy about since the update.Weird, so I got it to work by enabling the option that installs the update on reboot + disabling debugging in the developer menu. Then I rebooted the phone by holding the power button and selecting the reboot option...
worked after that![]()
Were you able to install the buds 2 pro manager app from the play store?Glad you got it to work. I've noticed two things that I'm pretty happy about since the update.
1) battery life is noticably better. Even the graph in the batter section is showing a flatter slope vs my last 12 hours without changing my habits.
2) I ordered buds pro 2 and couldn't adjust them (anc and other advanced settings) on the previous build.
No. In the past with my OnePlus buds z, it was baked into the os. Upon arrival of the pro 2s last week I was saddened that options to tune them were missing in the standard Bluetooth menu, until today's update.Were you able to install the buds 2 pro manager app from the play store?
I had to grab the APK elsewhere for that...
Anyone loose google pay recently. Stopped working for me today. Have the latest safetynetfix 2.40 installed.
As always, thanks. Nice to see that in the mix of all of these new phone launches we are sticking around. I'm tempted to 'upgrade' but there's no clear move from the OP8 to me.I've attached the non-patched and patched boot.img's for IN2025_11_F.62
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this...forum.xda-developers.com
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download...forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Just wanted to let you know that this worked on my IN2025I can boot the patched global image via ADB and then pull and patch my own US boot image right? I have an IN2025 and the global is IN2023 right?
You have to completely uninstall Magisk... it's a pain in the butt to update now because you'll need your PC to flash the modified boot.imgAnyone else have issues updating to C21? Every time I try manually updating using the system update app it gets to 32% and fails. I turned off all magisk modules and restored image within magisk first.