Development [ROM][OFFICIAL] [OOS CAM] Pixel Extended ROM V5.9 Android 13.0 [Lemonade][21.07.2023]

[shadabkiani]

What I mean is that you can just patch your boot.img in magisk, go into bootloader and straight up go "fastboot flash boot <patched image>.img" and reboot and that's it. I don't know about the recommended way, but doing it like that works just fine after flashing F.18.

So you can boot your phone after flashing Magisk patched image from fastboot? You wrote above that system would not boot after flashing..

P.S. Flashing boot directly from fastboot still works. But the problem with that would be that Magisk would not backup the original boot.img. So you won't be able to restore image from Magisk if at a later stage you decide to unroot. Well, why would you need to unroot? Because if you are on OOS and there is an update, it will fail to proceed because of tampered (patched) boot.img, hence before proceeding with OTA, you would need to restore original boot.img. That is where temporarily booting and then rooting method pays off. By the way, you can restore original boot.img by flashing if you didn't go with temporary boot method.

 

[mattie_49]

So you can boot your phone after flashing Magisk patched image from fastboot? You wrote above that system would not boot after flashing..

P.S. Flashing boot directly from fastboot still works. But the problem with that would be that Magisk would not backup the original boot.img. So you won't be able to restore image from Magisk if at a later stage you decide to unroot. Well, why would you need to unroot? Because if you are on OOS and there is an update, it will fail to proceed because of tampered (patched) boot.img, hence before proceeding with OTA, you would need to restore original boot.img. That is where temporarily booting and then rooting method pays off. By the way, you can restore original boot.img by flashing if you didn't go with temporary boot method.

This method is only needed if your running stock rooted oos. Sideloading magisk through recovery works perfectly fine on Pex,Lineage all other aosp builds I've used. No need to have stock boot.img on aosp. Ota updates install fine rooted. Only if your running custom builds though.

 

[shadabkiani]

This method is only needed if your running stock rooted oos. Sideloading magisk through recovery works perfectly fine on Pex,Lineage all other aosp builds I've used. No need to have stock boot.img on aosp. Ota updates install fine rooted. Only if your running custom builds though.

Yes. That's why I keep writing 'recommended way'. It's not the only way.

 

[caca13]

So you can boot your phone after flashing Magisk patched image from fastboot? You wrote above that system would not boot after flashing..

P.S. Flashing boot directly from fastboot still works. But the problem with that would be that Magisk would not backup the original boot.img. So you won't be able to restore image from Magisk if at a later stage you decide to unroot. Well, why would you need to unroot? Because if you are on OOS and there is an update, it will fail to proceed because of tampered (patched) boot.img, hence before proceeding with OTA, you would need to restore original boot.img. That is where temporarily booting and then rooting method pays off. By the way, you can restore original boot.img by flashing if you didn't go with temporary boot method.

My bad, it sounded confusing. I meant it didn't boot before I flashed F.18, but just flashing it worked on F.18

 

[zjyoti]

Battery backup is terrible, averaging about 2~3 hrs of SoT. Device keep getting hot with normal daily use idk why. Running snapdragon scaling module extreme efficiency mode, But no luck. Battery dies in about 12~15hr of normal use. It takes about 70~90 minutes to full charge with the original power brick and cable. Lost warp charging,I guess. Any solutions anyone?

 

[Lagarde]

Battery backup is terrible, averaging about 2~3 hrs of SoT. Device keep getting hot with normal daily use idk why. Running snapdragon scaling module extreme efficiency mode, But no luck. Battery dies in about 12~15hr of normal use. It takes about 70~90 minutes to full charge with the original power brick and cable. Lost warp charging,I guess. Any solutions anyone?

1) Have you had it installed and running for 24+ hours? It takes that long to settle in. The first 24hrs, my battery drain was insane.
2) Haven't tried the extreme scaling module, but low-power one has been working very well for me. Phone doesn't even get warm in games.
3) On mine, it doesn't say warp charging, but it goes from 0-100% in about 40 minutes. First 50% charge takes about 10 minutes. That's about in-line with normal warp charging.

All in all, sounds like possibly a bad install or wrong firmware version if I were to guess. The only thing that seems to draw power painfully fast on mine is AOD, which was bad even on stock. As of right now, mine's been off-charger for 26 hours, during which time I've taken 5 calls, played a few web games for a short time, and sent about a dozen emails...sitting at 86% battery.

 

[zjyoti]

1) Have you had it installed and running for 24+ hours? It takes that long to settle in. The first 24hrs, my battery drain was insane.
2) Haven't tried the extreme scaling module, but low-power one has been working very well for me. Phone doesn't even get warm in games.
3) On mine, it doesn't say warp charging, but it goes from 0-100% in about 40 minutes. First 50% charge takes about 10 minutes. That's about in-line with normal warp charging.

All in all, sounds like possibly a bad install or wrong firmware version if I were to guess. The only thing that seems to draw power painfully fast on mine is AOD, which was bad even on stock. As of right now, mine's been off-charger for 26 hours, during which time I've taken 5 calls, played a few web games for a short time, and sent about a dozen emails...sitting at 86% battery.

Hello,
1) I've been running it for about 72+ hours but no luck!
2) Phone getting warm just with normal use.
3) I know it would not say warp charge; however, charging time is not normal.

I was in LE2115 f.21 firmware. I installed it from the Sourceforgenet (PixelExtended-5.8_lemonade-13.0-20230507-1328-OFFICIAL.zip) but don't know about the firmware. however, it shows LE2110 in my settings now. Can you point me in the right direction for firmware, please?

 

[shadabkiani]

Hello,
1) I've been running it for about 72+ hours but no luck!
2) Phone getting warm just with normal use.
3) I know it would not say warp charge; however, charging time is not normal.

I was in LE2115 f.21 firmware. I installed it from the Sourceforgenet (PixelExtended-5.8_lemonade-13.0-20230507-1328-OFFICIAL.zip) but don't know about the firmware. however, it shows LE2110 in my settings now. Can you point me in the right direction for firmware, please?

Your problems might be because of firmware.

You were on F.21 fimware, however, it must have been on 1 slot only (whether a or b). We don't know what slot were you on and slot you flashed ROM on. Most porbably, you sideloaded and it flashed on the other slot. Anyway, that was just information.

What you should do now is download the firmware from the link in first post where you downloaded the ROM from. Look for the firmware folder and download F.18. That is what's recommended. Download it, extract it, put your phone in bootloader moder, and run the bat file from firmware. When asked about modem, choose No. This will flash F.18 firmware on both slots.

Next you just proceed with flashing ROM as usual. I would strongly suggest doing a clean flash by factory resetting and formatting data from recovery before flashing.

P.S. I used this ROM with F.21 firmware on both slots with no such problems.

 

[zjyoti]

Your problems might be because of firmware.

You were on F.21 fimware, however, it must have been on 1 slot only (whether a or b). We don't know what slot were you on and slot you flashed ROM on. Most porbably, you sideloaded and it flashed on the other slot. Anyway, that was just information.

What you should do now is download the firmware from the link in first post where you downloaded the ROM from. Look for the firmware folder and download F.18. That is what's recommended. Download it, extract it, put your phone in bootloader moder, and run the bat file from firmware. When asked about modem, choose No. This will flash F.18 firmware on both slots.

Next you just proceed with flashing ROM as usual. I would strongly suggest doing a clean flash by factory resetting and formatting data from recovery before flashing.

P.S. I used this ROM with F.21 firmware on both slots with no such problems.

Hi, thank you for your suggestion. However, i may sound noob,but how can i flash on both slots? Should I flash it twice, each time changing the default slot name?

 

[shadabkiani]

Hi, thank you for your suggestion. However, i may sound noob,but how can i flash on both slots? Should I flash it twice, each time changing the default slot name?

The bat file will automatically flash to both slots. You don't need to worry. Just make sure the process goes smooth till the end.

 

[by_BenjamiN]

There is no game mode. where can i download ?

 

[shadabkiani]

There is no game mode. where can i download ?

I'm not on this ROM currently, but I think I remember there is Game Space. There is no launcher icon, but it's somewhere in the Settings. You can search in Settings.

 

[by_BenjamiN]

Game mode removed in last build

 

[zjyoti]

What is the kernel you are using? Or are you using default kernel in the pex rom?

1) Have you had it installed and running for 24+ hours? It takes that long to settle in. The first 24hrs, my battery drain was insane.
2) Haven't tried the extreme scaling module, but low-power one has been working very well for me. Phone doesn't even get warm in games.
3) On mine, it doesn't say warp charging, but it goes from 0-100% in about 40 minutes. First 50% charge takes about 10 minutes. That's about in-line with normal warp charging.

All in all, sounds like possibly a bad install or wrong firmware version if I were to guess. The only thing that seems to draw power painfully fast on mine is AOD, which was bad even on stock. As of right now, mine's been off-charger for 26 hours, during which time I've taken 5 calls, played a few web games for a short time, and sent about a dozen emails...sitting at 86% bat

 

[Lagarde]

What is the kernel you are using? Or are you using default kernel in the pex rom?

I use the default kernel. Only changes from pex stock I made are rooting, adding the underclock module, and turning always on display to only when picked up. With those changes, I get about 2-3 days on my phone, with only a few oddball quirks that I've run into (some audio buzz, a few sounds that don't mute properly in silent mode, etc...nothing major).

 

[windowslucker]

I cant seem to get root access working.
What i tried ( with F18 Firmware and F21 Firmware):

Flashing boot.img, vendor_boot.img and dtbo.img then
1. adb sideload rom.zip, downloading Magisk.apk from Git and renaming to .zip and flashing via recovery
2. adb sideload rom.zip, installing Magisk.apk, patch boot.img and flashing patched boot.img
3. adb sideload rom.zip, installing Magisk.apk, patch boot.img and temporarly boot boot.img

All steps above are resulting in a bugged out UI with flashing statusbar and minimize icon on the bottom.
Sometimes flashing/temp booting the patched boot.img results in "Stuck on black screen with Onplus Logo and "Fastboot Mode" font"

Flashing Rom.zip without any Magisk modifications and the System boots fine or is this an rom bug?
Is there a detailed guide on how to root the device? im currently kinda stuck :-(

Edit

 

[shadabkiani]

I cant seem to get root access working.
What i tried ( with F18 Firmware and F21 Firmware):

Flashing boot.img, vendor_boot.img and dtbo.img then
1. adb sideload rom.zip, downloading Magisk.apk from Git and renaming to .zip and flashing via recovery
2. adb sideload rom.zip, installing Magisk.apk, patch boot.img and flashing patched boot.img
3. adb sideload rom.zip, installing Magisk.apk, patch boot.img and temporarly boot boot.img

All steps above are resulting in a bugged out UI with flashing statusbar and minimize icon on the bottom.
Sometimes flashing/temp booting the patched boot.img results in "Stuck on black screen with Onplus Logo and "Fastboot Mode" font"

Flashing Rom.zip without any Magisk modifications and the System boots fine or is this an rom bug?
Is there a detailed guide on how to root the device? im currently kinda stuck :-(

Edit

Start over and do a clean flash like this. Flash boot.img, dtbo.img, vendor_boot.img. Reboot to recovery. Factory reset and format data. Sideload the ROM zip. Boot up the system. Then install Magisk 26.1. Patch boot.img. Temporarily boot the newly patched image. When system boots up, open Magisk app and choose Direct Install.

 

[windowslucker]

Start over and do a clean flash like this. Flash boot.img, dtbo.img, vendor_boot.img. Reboot to recovery. Factory reset and format data. Sideload the ROM zip. Boot up the system. Then install Magisk 26.1. Patch boot.img. Temporarily boot the newly patched image. When system boots up, open Magisk app and choose Direct Install.

Do i need a specific base Version of the Standard OS? I reseted my entire phone with the MSM Tool which was Android 11.
When Flashing Firmware 18 in this state im stuck in QUALCOMM CrashDump Mode

Edit: Yes you need at least Android 12 to get not stuck

Edit2: Just like before, i completly reseted my phone with MSM then updated to Android 12 and followed your steps. But im Stuck in the "Fastboot Mode" screen which is centered and above the OnePlus Logo is shown. Im slowly loosing my nervous

Edit3: I tried flashing crDroid, but i was stuck at exact the same error behaviour. Then i changed over to Magisk25.2 which worked instantly. Magisk26.1 is somewhat buggy and not working for me, thanks for the help!!

 

[shadabkiani]

Do i need a specific base Version of the Standard OS? I reseted my entire phone with the MSM Tool which was Android 11.
When Flashing Firmware 18 in this state im stuck in QUALCOMM CrashDump Mode

Edit: Yes you need at least Android 12 to get not stuck

Edit2: Just like before, i completly reseted my phone with MSM then updated to Android 12 and followed your steps. But im Stuck in the "Fastboot Mode" screen which is centered and above the OnePlus Logo is shown. Im slowly loosing my nervous

Edit3: I tried flashing crDroid, but i was stuck at exact the same error behaviour. Then i changed over to Magisk25.2 which worked instantly. Magisk26.1 is somewhat buggy and not working for me, thanks for the help!!

Refer to my post in crDroid thread.

 

[qbfreak]

Why can't I access diag mode from dialer on this rom?