[ROM][11][OnePlus8Pro] PixelExperience [AOSP]

[TheUndertaker21]

I'm unable to boot this
I tried with pixel room installer and the instructions
Just keeps rebooting back to bootloader
Crdroid boots up fine
And the previous version did.
I'm not sure what's wrong with this one

 

[TaranS2001]

How are the Vibrations/Haptics with this rom. Are they as crisp as OOS?

 

[ctonylee1965]

Had 2 QUALCOMM crash dumps today out of the blue. Phone was just idle, I picked up to check something and the dreaded screen was staring at me. Rebooted everything fine, then a few hours later same thing. Reset network/cell settings, so far it hasn't happened again. Anyone experiencing this? Might have to go back to OS if it keeps happening. Really loving this ROM hopefully there's a fix.....

 

[luigifan3]

Hello, has someone had problems with haptic feedback on this ROM? Because with mine it is not working, only the vibration.

 

[Gary_Forth]

I've tried following the guide for ROM installation using ROMinstaller and manual flash each image step by step. After command reboot bootloader reboot phone switch on with pixel recovery screen and PC do not recognize the phone back to continue installation.


Sending 'recovery' (98304 KB) OKAY [ 2.165s]
Writing 'recovery' OKAY [ 0.316s]
Finished. Total time: 2.566s
Sending 'boot_b' (98304 KB) OKAY [ 2.160s]
Writing 'boot_b' OKAY [ 0.293s]
Finished. Total time: 2.536s
Sending 'dtbo' (24576 KB) OKAY [ 0.541s]
Writing 'dtbo' OKAY [ 0.070s]
Finished. Total time: 0.637s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Invalid sparse file format at header magic

Can somebody share a guide with a different approach?

 

[mapester]

I've tried following the guide for ROM installation using ROMinstaller and manual flash each image step by step. After command reboot bootloader reboot phone switch on with pixel recovery screen and PC do not recognize the phone back to continue installation.


Sending 'recovery' (98304 KB) OKAY [ 2.165s]
Writing 'recovery' OKAY [ 0.316s]
Finished. Total time: 2.566s
Sending 'boot_b' (98304 KB) OKAY [ 2.160s]
Writing 'boot_b' OKAY [ 0.293s]
Finished. Total time: 2.536s
Sending 'dtbo' (24576 KB) OKAY [ 0.541s]
Writing 'dtbo' OKAY [ 0.070s]
Finished. Total time: 0.637s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Invalid sparse file format at header magic

Can somebody share a guide with a different approach?

Check your fastboot drivers. I had a simular issue where mine would fail at the fastboot reboot fastboot comand.

I uninstalled the Oneplus fastboot drivers and installed the google ones from the Android Studio SDK.

then afterwards test the fastboot reboot fastboot command. if that works reboot to bootloader and run the rominstaller.bat

 

[cjx11111]

That's what install instructions say in his telegram group.

make sure oos 11 available in both slots
$ adb reboot bootloader
$ fastboot -w (this will wipe your data)
$ fastboot flash recovery recovery.img
$ fastboot reboot fastboot
$ fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash system_ext system_ext.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot

I think A10 recovery wouldn't work.

how to make oos 11 available in both slots？

 

[Kollachi]

how to make oos 11 available in both slots？

Install same ota.zip with updater.

 

[cultofluna]

...

 

[nyzoli72]

I'm unable to boot this
I tried with pixel room installer and the instructions
Just keeps rebooting back to bootloader
Crdroid boots up fine
And the previous version did.
I'm not sure what's wrong with this one

same sh... i don't know why

 

[nyzoli72]

now i started again from the dust and now it's ok,

 

[[email protected]]

now i started again from the dust and now it's ok,

how?

 

[chandra1.jd]

February update recap
* Added on screen gestures customization for supported devices
* February security patch
* Under the hood improvements

Sideload working : both rom and magisk

 

[marko94]

February update recap
* Added on screen gestures customization for supported devices
* February security patch
* Under the hood improvements

Sideload working : both rom and magisk

Last build is really stable.. so smooth, no issues, no noticable bug. L1 on Netflix even with root and unlocked bl Nice work dev

 

[greatestandroidfan]

Argh!!! What a trip... This is how it worked for me after MSM the damn thing TWICE!
MSM worked only on an ~10years old laptop with USB 2.0port. No chance with MS SurFace, ASUS Zenbook...
Came from OOS v15.E.33_OTA_0330 for IN2023. Prepwork:
- most recent ADB from Google
- copy-partitions.zip
- Recovery & ROM from Post #1
- payload_dumper-win64.zip
- MagiskManager-v8.0.7.apk
- put an unlocked SIM in the phone

- Did every single step with this instruction to the T.
- Unlock the bootloader only works with an unlocked SIM installed. Don't forget to "OEM unlock" in the dev options
- After installation enable dev options & USB debugging again
- To get Magisk working with Root, follow this instructions, step 1 & 3. Use boot.img from Pixel Experience 11 payload.bin, NOT from OOS 11

Hope this helps someone else to save a ton of time

 

[dladz]

Argh!!! What a trip... This is how it worked for me after MSM the damn thing TWICE!
MSM worked only on an ~10years old laptop with USB 2.0port. No chance with MS SurFace, ASUS Zenbook...
Came from OOS v15.E.33_OTA_0330 for IN2023. Prepwork:
- most recent ADB from Google
- copy-partitions.zip
- Recovery & ROM from Post #1
- payload_dumper-win64.zip
- MagiskManager-v8.0.7.apk
- put an unlocked SIM in the phone

- Did every single step with this instruction to the T.
- Unlock the bootloader only works with an unlocked SIM installed. Don't forget to "OEM unlock" in the dev options
- After installation enable dev options & USB debugging again
- To get Magisk working with Root, follow this instructions, step 1 & 3. Use boot.img from Pixel Experience 11 payload.bin, NOT from OOS 11

Hope this helps someone else to save a ton of time

I wonder if using a USB multi adapter hub would lower the power and allow it to work on your surface? Essentially reducing USB 3 to 2.0.

Just a thought

Might be worth trying next time

 

[marko94]

Argh!!! What a trip... This is how it worked for me after MSM the damn thing TWICE!
MSM worked only on an ~10years old laptop with USB 2.0port. No chance with MS SurFace, ASUS Zenbook...
Came from OOS v15.E.33_OTA_0330 for IN2023. Prepwork:
- most recent ADB from Google
- copy-partitions.zip
- Recovery & ROM from Post #1
- payload_dumper-win64.zip
- MagiskManager-v8.0.7.apk
- put an unlocked SIM in the phone

- Did every single step with this instruction to the T.
- Unlock the bootloader only works with an unlocked SIM installed. Don't forget to "OEM unlock" in the dev options
- After installation enable dev options & USB debugging again
- To get Magisk working with Root, follow this instructions, step 1 & 3. Use boot.img from Pixel Experience 11 payload.bin, NOT from OOS 11

Hope this helps someone else to save a ton of time

Don't use anything of this..you don't need payload anymore. After oos on both slots, just flash PE recovery, factory reset, side load PE rom ,boot to system, reboot to recovery, side load magisk and that is it..

 

[dladz]

Don't use anything of this..you don't need payload anymore. After oos on both slots, just flash PE recovery, factory reset, side load PE rom ,boot to system, reboot to recovery, side load magisk and that is it..

You can still patch an IMG and boot it, it's good practice to know what payload dumper is and how to use it.

Relying on someone else isn't forward thinking in my eyes.

So long as it works, each to their own.

 

[laampui]

With the latest beta build, Sometimes the screen is black. Hold the power key can pop up power off menu. The only thing I can do is select the reboot option to resolve this issue.

 

[laampui]

Battery charging is fine, but the text here is wrong.