Yes
Pull the boot img from pa patch it with magisk and then reflash it .Wow hey firstly thanks for all of your hard works and keeping root community flowing. I have a few dumb questions as its been a while since ive rooted and flashed roms. 1. I followed instructions in the original post and seem to have flashed rom no problem but i seem to have lost root. is that normal? do i just reinstall magisk? If so am I pulling the boot.img from PA? thanks again
Please don't do that.I've tried and got boot log...
NO. It will soft-brick your device. Please, unless you don't know what you're talking about, don't spread misinformation.
well now
thisPull the boot img from pa patch it with magisk and then reflash it .
is awkwardNO. It will soft-brick your device. Please, unless you don't know what you're talking about, don't spread misinformation.
Cheers guys!!We’re excited to announce the updated Beta build of Paranoid Android Sapphire, based on Android 12L.
We're sticking with "Beta 1" naming to match the status of other PA releases, but rest assured, it is a new build.
The platform had more than PA-specific 500 commits from the last Beta release.
Device-wise, the new build includes the latest arter97 kernel r20.
Please refer to its thread for relevant changes.
The PA device tree also has been modified to support future arter97 kernel builds as well.
Here are some device-specific changes:
- Fixed post boot script applying incorrect tuning values
- Dimensions synced with other custom ROMs
And here are some platform-wise highlights:
- New VRR method implemented to drastically improve battery life
- The memory allocator is now back to jemalloc, which improves performance throughout the system
- Optimized bionic, memory routines (ported by xboxfanj)
- zlib-ng from kdrag0n’s ProtonAOSP to improve performance
- Latest libjpeg-turbo merged to improve imaging performance
- Latest CAF tag merged
As always, there’s a lot more stuff going under the hood, especially the new kernel release.
Enjoy!
A clean flash is highly recommended.
Download link:
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)arter97.com
U should be on latest oos 11. Make sure it's flashed on Both slots. Use latest platform tools. Once you flash the zip . Wipe the data in recovery then reboot into system. Should workI am keep getting rebooted into fastboot menu, even after successfully installing rom. When I pass setup wifi and going to input my Google details, it's keep rebooting into fastboot menu for some reason. I even did factory reset.
I am installing rom after installing OOS 11.10.10, however, I tried with OOS 12 but it did work, it's doesn't goes fastbootd menu to install rom.
Any advice
Did all that, twice. But still getting reboot to fastboot menu for some reason, not sure what is the cause.U should be on latest oos 11. Make sure it's flashed on Both slots. Use latest platform tools. Once you flash the zip . Wipe the data in recovery then reboot into system. Should work
U should be on latest oos 11. Make sure it's flashed on Both slots. Use latest platform tools. Once you flash the zip . Wipe the data in recovery then reboot into system. Should work
Did all that, twice. But still getting reboot to fastboot menu for some reason, not sure what is the cause.
When restarting in fastboot mode, enter recovery mode and format the data. That solved it for me.Did all that, twice. But still getting reboot to fastboot menu for some reason, not sure what is the cause.
It happens that after the flash of the PA, the device automatically restarts. After it starts, turn off and enter recovery mode, and format, then restart.Many, many people if not all people in the Telegram are having this same issue, regardless of the steps we've taken to get it installed, there isn't really a found fix yet. There seems to be less issues with the non-Pro build but Pro users have the most issues
Yes, we've tried that already lolIt happens that after the flash of the PA, the device automatically restarts. After it starts, turn off and enter recovery mode, and format, then restart.
When restarting in fastboot mode, enter recovery mode and format the data. That solved it for me.
Did you format through recovery, or with the command fastboot -w ? Well, what you are reporting happened to me. And before configuring, I just went into recovery mode and did the factory reset. And everything is working perfectly.
-w before flashing, recovery after flashingDid you format through recovery, or with the command fastboot -w ? Well, what you are reporting happened to me. And before configuring, I just went into recovery mode and did the factory reset. And everything is working perfectly.
I'm not using this ROM but when I had that error on Nameless I remember I opened up the app and at the bottom of the screen there is a place where you can select your device. I changed it from the codename to the device name and then I was able to turn it on. Maybe try that?Anyone know why I'm getting this from Energy Ring? I tried changing the name from "OnePlus 9 Pro" to LE2123, still getting the same, is there another definition location for the name?
View attachment 5641223
It works fine on other roms, had to end up using the energy bar instead (up top)
This is how it looks on my device.I don't see any such option anywhere in the app or it's settings
For clarity this is "Energy Ring Universal Edition"