[ROM][OFFICIAL][13][OnePlus Nord/avicii] Pixel Experience [AOSP]

[princen41]

I'm facing a lot of heating issues having it installed only yesterday and fast charging is also not working.

I also faced heating issue. Fast charging is also not working. Due to this I switched to oos 12 again.

 

[FusionGFX]

I also faced heating issue. Fast charging is also not working. Due to this I switched to oos 12 again.

did you perform a wipe to install OOS 12?
I want to avoid losing all my data and setting everything up twice within one week...

 

[princen41]

did you perform a wipe to install OOS 12?
I want to avoid losing all my data and setting everything up twice within one week...

I wiped my data. You can try backup with app migrate rom backup. It will create flashable zip file of your data. Flash new rom then format data with internal storage. Then flash data backup file.
I don't try this, but after searching on Play Store, I found this app.

 

[Klappp]

did you perform a wipe to install OOS 12?
I want to avoid losing all my data and setting everything up twice within one week...

I don't know why you're making this the dev's problem. The rom is still under development and in it's early stages. There's bound to be bugs and need to wipe the data.
Instead of making these replies and asking the dev to speed up the process, use a stable rom until this one is ready.

 

[FusionGFX]

I don't know why you're making this the dev's problem. The rom is still under development and in it's early stages. There's bound to be bugs and need to wipe the data.
Instead of making these replies and asking the dev to speed up the process, use a stable rom until this one is ready.

I understand you point, but introducing such a massive issue as an OTA-upate to an already great working ROM is unfortunate...

 

[hoopyguy]

I've just installed the newest update.

I now have got my beloved gesture navigation back, however:

If I patch the boot image with magisk and flash it via fastboot, and then reboot, I again lose gesture navigation. The option for it disappears in the settings:

With patched boot image:

If I flash the original boot image again, it comes back:

This is a bummer, since I'd like to use ACC on my phone.
Regarding my school wi-fi I will report back on Monday whether that works. There were some wi-fi fixes after all.

Fingerprint reader seems to work faster now!

Thanks for the update!
Cheers
Jan

 

[Gagn_agrawal]

Pixel launcher taking large chunks of battery, await a fix in pe plus

 

[hermesjconrad]

I have managed to install the 20230201 build on OOS12 firmware. I used the provided PE recovery, which I booted with fastboot boot <path.to.recovery.file>. If I just flashed the recovery, and tried to boot it, I got the image was destroyed screen.

Could someone who is on previous PE13 ROM on OOS11 firmware, and has reliable backup, try to upgrade firmware using this ZIP from the firmware thread, then install the 20230201 build, and report back if they could do it without losing data? Or someone who upgraded the ROM, and now has the Wifi/LTE broken try the ZIP, if it fixes the problems?

Just flashing the firmware from the firmware thread did not resolve my Wifi issues with PE13.

 

[hermesjconrad]

Finally I went the recommended route, MSM Tool -> OOS 10 -> OOS 11 -> OOS12 -> Orangefox recovery, PE13, and I confirm that WiFi works again, as does 5G.

Time-consuming but I guess it's worth it in the long run.

Thank you for your work!

 

[streetking.cl]

Finally I went the recommended route, MSM Tool -> OOS 10 -> OOS 11 -> OOS12 -> Orangefox recovery, PE13, and I confirm that WiFi works again, as does 5G.

Time-consuming but I guess it's worth it in the long run.

Thank you for your work!

I tried to do that, but from OOS12 it wouldn't let me flash any recovery, trying and trying I ended up bricking the phone and restoring it with msm tools. How did you flash the room? it occurs to me that maybe you put the recovery from OOS11 and then in OOS12 you already had the previous one, or it wasn't like that?

 

[gllark]

I tried to do that, but from OOS12 it wouldn't let me flash any recovery, trying and trying I ended up bricking the phone and restoring it with msm tools. How did you flash the room? it occurs to me that maybe you put the recovery from OOS11 and then in OOS12 you already had the previous one, or it wasn't like that?

Did you unlock your bootloader again? Because MSM-Tool does lock it after finishing.

 

[hermesjconrad]

I tried to do that, but from OOS12 it wouldn't let me flash any recovery, trying and trying I ended up bricking the phone and restoring it with msm tools. How did you flash the room? it occurs to me that maybe you put the recovery from OOS11 and then in OOS12 you already had the previous one, or it wasn't like that?

I installed OrangeFox after upgrading to OOS12. However, I used the inofficial OrangeFox build from here and I flashed the OOS12 variant (NOT FBEv1 or FBEv2). I executed the pre-OOS12 script, but not sure if this actually was necessary.

 

[hermesjconrad]

Did you unlock your bootloader again? Because MSM-Tool does lock it after finishing.

Yes, the MSM Tool relocked my bootloader.

So, not sure if this helps, but I try to list the complete set of steps I performed here. Some of it might be cargo cult as I don't understand in detail what every component does :

1. Use MSM Tool to download OOS10 stock in Qualcomm EDL mode
2. OTA to OOS11
3. OTA to OOS12
4. Activate possibility to OEM unlock bootloader in OOS12 developer options, plus activate USB debugging
5. Reboot to fastboot (adb reboot fastboot)
6. fastboot flashing unlock on laptop while phone in fastboot to unlock bootloader
7. fastboot boot Orangefox - the OOS12 variant (this starts the recovery without flashing it)
8. adb shell into recovery, execute pre-install shell script (not sure if this step is necessary, not sure what the script does)
9. Reboot to fastboot
10. Fastboot flash Orangefox (OOS12 variant) to flash the recovery
11. Reboot to recovery
12. adb shell into recovery, execute post-install shell script (not sure if necessary and did not work).
13. Format data
14. Sideload PE13
15. Switch the slot to active in the recovery, following Orangefox recommendations
16. Reboot

 

[gllark]

Yes, the MSM Tool relocked my bootloader.

So, not sure if this helps, but I try to list the complete set of steps I performed here. Some of it might be cargo cult as I don't understand in detail what every component does :

1. Use MSM Tool to download OOS10 stock in Qualcomm EDL mode
2. OTA to OOS11
3. OTA to OOS12
4. Activate possibility to OEM unlock bootloader in OOS12 developer options, plus activate USB debugging
5. Reboot to fastboot (adb reboot fastboot)
6. fastboot flashing unlock on laptop while phone in fastboot to unlock bootloader
7. fastboot boot Orangefox - the OOS12 variant (this starts the recovery without flashing it)
8. adb shell into recovery, execute pre-install shell script (not sure if this step is necessary, not sure what the script does)
9. Reboot to fastboot
10. Fastboot flash Orangefox (OOS12 variant) to flash the recovery
11. Reboot to recovery
12. adb shell into recovery, execute post-install shell script (not sure if necessary and did not work).
13. Sideload PE13
14. Switch the slot to active in the recovery, following Orangefox recommendations
15. Reboot

Just in case you were not successful to flash a custom recovery:
You can check the state of your bootloader by

fastboot oem device-info

I don´t know if your command "fastboot flashing unlock" is working, but I first checked on "OEM unlock" in developer options and unlocked my bootloader afterwards by

fastboot oem unlock

Hope this helps!

 

[hermesjconrad]

Just in case you were not successful to flash a custom recovery:
You can check the state of your bootloader by

fastboot oem device-info

I don´t know if your command "fastboot flashing unlock" is working, but I first checked on "OEM unlock" in developer options and unlocked my bootloader afterwards by

fastboot oem unlock

Hope this helps!

For me the flashing unlock command did the trick, but only after the OEM unlock in the developer options of course.

 

[punitsnaik]

I dirty flashed it over PixelExperience plus 12. I was previously using PE+12 on OOS12 firmware. Everything works very smoothly for me. Didn't even had to reset. Battery backup is also very good and no heating issue. Jio 5G is also working. Kudos to the developers.

 

[paul1st]

1) Does Android Auto work?
2) Does Google Wallet work?

 

[StokedKush]

I dirty flashed it over PixelExperience plus 12. I was previously using PE+12 on OOS12 firmware. Everything works very smoothly for me. Didn't even had to reset. Battery backup is also very good and no heating issue. Jio 5G is also working. Kudos to the developers.

Hey I am also on PE 12+ currently. Did you clean your ROM ? or just Applied the Update from PE Recovery?

 

[hermesjconrad]

1) Does Android Auto work?
2) Does Google Wallet work?

1) Works for me.
2) The menu is there and I can enter a credit card, but my bank does not support it, so I cannot test if actual payment works.

 

[punitsnaik]

Hey I am also on PE 12+ currently. Did you clean your ROM ? or just Applied the Update from PE Recovery?

I updated to 13 from adb sideload using the new recovery, without wiping anything. Try it only if you are using OOS12 Firmware, otherwise you might not get network