Development Paranoid Android Topaz Beta 1 - Poco F3/Mi 11X/ Redmi K40

Search This thread


Senior Member
It doesn't seem that you can "fastboot boot" a recovery at all on this ROM.

You might have to flash it via "fastboot flash boot recovery.img", and then run "fastboot reboot recovery".

BTW: why would you want to use a Beta 11.1_1_5_A12 release that has been superseded by a subsequent Stable release?
Fastboot boot worked for me with TWRP
  • Like
Reactions: Ultraschorsch


Recognized Developer
May 5, 2014
Greater London


May 17, 2015
Just wanna say thanks guys! This rom is the best I've seen so far in terms of speed, responsiveness and stability!
Very good rom in terms of speed battery life and responsiveness thouogh I had some strange reboots at night which disabled my alarm clock x( .

Not rooted... So still beta I think... I tried to get a crash report but could not identify anything (probably do not know enough how to :) )
Need to wait for next release I believe.

Great work by the way.
Thanks to support our device

ps: It seems than stable releases already exist for other devices (eg berylium)
omg just released (02/17) in fact .
i submitted to the Telegram group to get notified as soon as the release come.
I hope it will come soon :)

Last edited:
  • Like
Reactions: RootedLee


Recognized Developer
May 5, 2014
Greater London
Does this mean in plain language that we cannot flash the PA via OF or TWRP correctly?
Until a proper vendor_boot-as-recovery build of OrangeFox is released, yes.

I was able to flash it with the standard OrangeFox builds (coming from another ROM). But I wouldn't recommend it. Once you have flashed it, you would be then need a vendor_boot-as-recovery build, else you will get all the problems that have been described.


Senior Member
Sep 29, 2007
Is this rom in development still? Is been more than a month from last release. I want to use it as daily driver.
It is still in development, yes. But PA isn´t known for their rapid updates. If you´re looking for a solid ROM with amazing battery life, this could be your daily driver. If you´re looking for weekly or monthly updates, this might not be for you.
  • Like
Reactions: duttyend and Suhaas


Senior Member
Jan 20, 2018
Installed Topaz 1 Stable (from website)

First impressions: This is stupidly fast, raw android experience with Google Apps pre-installed. I've tested almost every ROM out there nothing feels this snappy. Best first impressions I've had on alioth.

Will be trying out this rom for a while, I'll report any issues I encounter.

This thread should probably be re-done with a better more long-term title as it's no longer in beta.
With better instructions, a non-broken image, etc..
Last edited:


New member
May 6, 2023
Poco F3 - M2012K11AG

Little rom reviser, rom very fluid, duration is similar to the use I had with MIUI.

AOSPA comes with the google go camera is good but I prefer the port of gcam or the version of the Leica camera, the sound is heard a little canned, you miss the equalizer of miui or dolby I do not know what possibility there is to include this and if it does not go against the "philosophy" of the rom as happens with lineageos.

Finally customization is little perfect for me, many like a system full of features but if you prefer something more basic and functional this rom is perfect for you.


The first boot I encounter an infinite cycle of reboots the solution was to use a different carrier as the main one, it is a known bug that certain phone carriers probocan a bug with the networks of the bit and in some roms cause reboots.

The health application in
>get help quickly > get started > start setup >next.
It doesn't go past this button I've noticed it on other roms so maybe it's something in the app.

It would be interesting that people try to reproduce errors try to reproduce the errors that I have and see if it is something general or a bug of mine, if someone knows how to make a log of errors could send it or teach me to me.

Many thanks to the developer and the Paranoid Android team.


Senior Member
Feb 17, 2022
Snapchat doesn't work on latest version (Stable 1, April). Known bug but no fix yet.

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    So, in case if i want to move from a "Vendor boot as recovery rom" to a "normal boot as recovery rom" like say lineage.

    What should be done?

    You imply that flashing a boot recovery will trash the boot partition. So a normal recovery will trash the boot partition.
    I don't just imply. I state it categorically as a fact.

    What to do in such cases?
    The most straightforward way to recover the brick for most people would be to flash a MIUI fastboot ROM, using the Mi Flash tool. This is of course a drastic solution (and people must be careful to not accidentally re-lock the bootloader in the process).

    There is a less drastic solution, but this is not realistic for most people, because it involves already having some good, flashable images from the vendor_boot ROM (boot.img, dtbo.img and vendor_boot.img). For those who have them, all that is needed is to boot to bootloader, and then flash those images:

    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot flash vendor_boot vendor_boot.img
    fastboot reboot recovery
    This should make both the vendor_boot ROM and its recovery bootable again.
    Been on this rom since May 3rd (Topaz Stable) from and I can't say I've faced a single issue, even rooted without trouble. Still the smoothest experience I've had and probably also the best battery life I've had on Poco F3 across lots of roms!

    That said there's no instructions on the website and this post really sucks with that, so newbies beware.
    Can anybody else provide usage impressions on this ROM? I'm tempted to jump over from CrDroid because Paranoid Android has AptX Adaptive support.

    Also support the idea of making this an [OFFICIAL] thread.

    Do we need to install this recovery before flashing the ROM? Will it cause problems with backing up/restoring my current CrDroid?
    @DarthJabba9, thanks, OK, so if I'm understanding this right, and I wanted to backup CrDroid, and install Paranoid Android, I would have to:

    1. Make relevant backups of CrDroid using the standard OrangeFox.
    2. Save these somewhere on my PC or whatever.
    3. Format and factory reset my device.
    5. Flash Paranoid Android.
    6. Without rebooting anything, flash the vendor_boot OrangeFox.
    7. Reboot to recovery.
    8. Format data.
    9. Boot into Paranoid Android and play around with it.
    That should work.

    But - depending on what happens when you first try to boot the ROM (ie, if it just returns you to recovery), you might have to format the data partition using "fastboot -w" at the bootloader prompt.

    Also, sometimes (depending on the ROM) it works better to reboot straight into the ROM's recovery, after step [5], and then do a factory reset there, then boot into the ROM and configure it, before having a modified step [6] - reboot to the ROM's recovery, and flash the vendor_boot OrangeFox using adb sideload.

    There can sometimes be an amount of trial and error involved.

    Then, to go back to my initial CrDroid:

    10. Format and factory reset my fastboot? Or in vendor_boot OrangeFox?
    11. Flash standard OrangeFox in fastboot.
    12. Restore CrDroid backup.
    Nope. It is more complicated than this. You have to do a completely clean flash of crDroid (and GAPPs if you were using that) using the current vendor_boot OrangeFox. Then flash the standard OrangeFox, reboot to OrangeFox, format data, and then reboot to system. After this you can reboot to OrangeFox and restore the crDroid backup.

    This seems super complicated and easy to mess up...
    It is. Another Google bright idea ...

    The most important thing to remember is that, once you are running a vendor_boot ROM, you must not flash a standard recovery until you have first flashed a standard ROM.
    Try changing kernel
  • 13

    We are very excited to announce the first beta of Paranoid Android Topaz, based on Android 13.

    On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.

    Our builds are based on the Code Linaro Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.


    We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.

    You can donate on the link below:


    Device-specific issues
    Does not have HBM mode


    Make sure you've latest platform tools for Android.
    Make sure you've installed latest Android 12 based firmware from your region.


    You can always get our Alpha builds from our website Paranoid Android website

    Note: GMS is included and custom kernels are NOT supported the kernel says it supports PA!


    Fastboot Method

    • Make sure your data is backed up
    • Unlock your bootloader, and in bootloader mode follow the next command
      fastboot format:f2fs --fs-options=casefold,projid,compress userdata (Wipes the entire device as well as userdata)
      fastboot update aospa-topaz-beta-*
    • Reboot to system
    Recovery Method
    • Reboot to Recovery.
    • Factory reset.
    • Install PA zip package.
    • Reboot to system

    Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.

    Kernel Source

    Important / Useful links
    Paranoid Android Twitter
    Paranoid Android Channel (Telegram)
    Paranoid Android Download Channel (Telegram)
    Paranoid Android Community (Telegram)
    Ok, thank you for your warning :)
    This ROM uses vendor_boot-as-recovery. That is the cause of all the issues with custom recoveries.
    Does this mean in plain language that we cannot flash the PA via OF or TWRP correctly?
    Until a proper vendor_boot-as-recovery build of OrangeFox is released, yes.

    I was able to flash it with the standard OrangeFox builds (coming from another ROM). But I wouldn't recommend it. Once you have flashed it, you would be then need a vendor_boot-as-recovery build, else you will get all the problems that have been described.
    Yes, before and after, tried a couple of times, if you wanna flash from recovery I would sugest to use the rom's stock recovery
    Well, I flashed it successfully with OrangeFox (my current working build - I haven't tried with the latest released version, but I don't see how that would make a difference).

    I guess that the trick is to format data before flashing the ROM, and, immediately after flashing the ROM, reboot OrangeFox (ignoring any errors that might be shown), and then format data again. Then reboot to system (again ignoring any errors be shown).

    BTW: I flashed it successfully two different times, just to satisfy myself that the first success wasn't a fluke (it wasn't a fluke).