Development Paranoid Android Topaz 1 - Nothing phone (1)

Search This thread

Patman86

Member
Oct 24, 2022
16
2
How do we get back to 1.1.4 EEA when the tool on Github don't work?

Can't just use fastboot flash 1.1.3 update like this rom.

EDIT i figured it out, if people have trouble it is
1 download super.image from https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
2 https://github.com/sh4tteredd/nothing-phone-1-tools and download the fw file. edit download.ps1 to get url, then extract using the https://forum.xda-developers.com/t/...one-1-update-04-08-2022.4470155/post-87185467 and put files into image folder
3 boot into fastboot and do fastboot reboot bootloader , i edit flash_all.bat and copy paste commands, do fastboot -w then fastboot --set-active=a after do fastboot reboot fastboot and continue to copy paste all the commands from the list until you come to fastboot reboot bootloader and fastboot --set-active=b and fastboot reboot fastboot then after those you gotta do super image again flash, then fastboot reboot fastboot and do fastboot flash abl_b ./images/abl.img and so on until you are done on b
 
Last edited:
  • Like
Reactions: thuva06
View attachment 5735149

We are very excited to announce the alpha 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 Organization 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.

Notice

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:

Donate

Device-specific issues

* LDAC playback is broken.
* Some HDR videos might lag after a few seconds of playing.
* Small freeze at bootanimation.


Requirements

Make sure you've latest platform tools for Android.

Download

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

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

Changelogs

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.

Paranoid Android Topaz released

Instructions


  • Unlock your bootloader, and in bootloader mode follow the next command

    fastboot update aospa-topaz-alpha-*-image.zip

    After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)

Kernel source
Kernel source

Important / Useful links

Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)

Cheers and #StayParanoid!
I tried to follow the instructions, but it got stuck during the reboot in the command fastboot update *-image.zip . It got back to the Nothing OS splash screen and then load the normal setup of a brand new Nothing Phone 1. I don't know what to do next. Please help
 

nickholtus

Senior Member
Aug 26, 2011
2,407
2,468
Using this rom now for 2,5 days.


First of all: much better experience than stock.


Few things i noticed:

* Random glitches in ui and video (hard to discribe, looks like an old television with no signal, we call it "snow") this happen on 1/4 to half of the screen

* Random reboot (happened 2 times)

I dont know if logcat or something would help in solving/finding the problems.

If i see a reliable way to reproduce these problems to help find the cause i will post it here.
 

MrUrgit

Senior Member
May 20, 2010
199
74
Melbourne
HTC Desire
HTC One (m7)

Patman86

Member
Oct 24, 2022
16
2

marcii-ec

Member
Apr 13, 2018
25
5
Stukenbrock
Bugs i have identified:
Android Car only shows a black screen
Paypal App starts and closes directly
Some Display Glitches
Sometimes the screen turns black and only a restart solves it.

If i can help with logs or something, especially for that Android Car Problem, please tell me.
 

ivandife

Member
Jan 17, 2018
33
7
Samsung Galaxy Note 9
hello, I was in european NothingOS 1.1.4 and updated to this Paranoid Android with "fastboot update" and now I can't get back to NothingOS. I have tried:
flash utilities
Manually flash file by file extracting payload.bin from 1.1.3 but I can't "upgrade" to a minor version and there is no European 1.1.4 full ROM
I stayed in Bootloop for a while but I was able to install Paranoid Android by downloading the recovery version and installing it file by file extracting the payload.bin file but that's all I could get. I can't get back to NothingOS at all.
 

ivandife

Member
Jan 17, 2018
33
7
Samsung Galaxy Note 9
How do we get back to 1.1.4 EEA when the tool on Github don't work?

Can't just use fastboot flash 1.1.3 update like this rom.

EDIT i figured it out, if people have trouble it is
1 download super.image from https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
2 https://github.com/sh4tteredd/nothing-phone-1-tools and download the fw file. edit download.ps1 to get url, then extract using the https://forum.xda-developers.com/t/...one-1-update-04-08-2022.4470155/post-87185467 and put files into image folder
3 boot into fastboot and do fastboot reboot bootloader , i edit flash_all.bat and copy paste commands, do fastboot -w then fastboot --set-active=a after do fastboot reboot fastboot and continue to copy paste all the commands from the list until you come to fastboot reboot bootloader and fastboot --set-active=b and fastboot reboot fastboot then after those you gotta do super image again flash, then fastboot reboot fastboot and do fastboot flash abl_b ./images/abl.img and so on until you are done on b
hi, I have this problem, can you explain me step by step, Im not that professional and my English is not good, sorry and thank you. I dont fully understand the step 2.
 

AntoXik72

Senior Member
Feb 27, 2013
110
53
I'll follow the tutorial but it doesn't work for me because I'm in european 1.1.4 so I want to understand how he did it
I was euro 1.1.3 when I did it, 1.1.4 is the same, in fact, you don't really have to care your version when following the tutorial. Flashing the super.img make your phone brand New. So from wichever version you are, you Can follow it
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Is there any chance to get nothing camera in this rom in future
    When everything works as intended!
  • 34
    Frame 30-70.png


    We are very excited to announce 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 Organization 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.

    Notice

    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:

    Donate

    Device-specific issues

    * You tell us


    Requirements

    Make sure you've latest platform tools for Android.

    Download

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

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

    Changelogs

    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.

    Paranoid Android Topaz released

    Instructions


    • Unlock your bootloader, and in bootloader mode follow the next command

      fastboot update aospa-topaz-alpha-*-image.zip

      After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)

    Kernel source.

    Important / Useful links
    Paranoid Android Twitter
    Paranoid Android Channel (Telegram)
    Paranoid Android Download Channel (Telegram)
    Paranoid Android Community (Telegram)

    Cheers and #StayParanoid!
    5
    Paranoid Android Topaz Alpha 2 is out!

    This update includes the following device specific changes:


    Fixed 5G indicator on statusbar and improved data connectivity
    Fixed UDFPS on lockscreen
    Improved vibration haptics

    For download links you can find the links in the next tweet (not available on website for infrastructure problems):

    Tweet


    #StayParanoid
    3
    Updated PA A1 to A2 :

    1/ Step 1 > Bootloader (Fastboot)
    Code:
    c:\Android>fastboot update aospa-topaz-alpha-2-phone1-20221019-image.zip
    --------------------------------------------
    Bootloader Version...:
    Baseband Version.....:
    Serial Number........: 8xxxxxxx
    --------------------------------------------
    extracting android-info.txt (0 MB) to RAM...
    Checking 'product'                                 OKAY [  0.002s]
    Setting current slot to 'a'                        OKAY [  0.007s]
    extracting boot.img (96 MB) to disk... took 0.531s
    archive does not contain 'boot.sig'
    Sending 'boot_a' (98304 KB)                        OKAY [  2.748s]
    Writing 'boot_a'                                   OKAY [  0.167s]
    extracting dtbo.img (24 MB) to disk... took 0.073s
    archive does not contain 'dtbo.sig'
    Sending 'dtbo' (24576 KB)                          OKAY [  0.664s]
    Writing 'dtbo'                                     OKAY [  0.038s]
    archive does not contain 'dt.img'
    archive does not contain 'pvmfw.img'
    archive does not contain 'recovery.img'
    extracting vbmeta.img (0 MB) to disk... took 0.001s
    archive does not contain 'vbmeta.sig'
    Sending 'vbmeta' (8 KB)                            OKAY [  0.001s]
    Writing 'vbmeta'                                   OKAY [  0.001s]
    extracting vbmeta_system.img (0 MB) to disk... took 0.001s
    archive does not contain 'vbmeta_system.sig'
    Sending 'vbmeta_system' (4 KB)                     OKAY [  0.001s]
    Writing 'vbmeta_system'                            OKAY [  0.001s]
    archive does not contain 'vbmeta_vendor.img'
    extracting vendor_boot.img (96 MB) to disk... took 0.237s
    archive does not contain 'vendor_boot.sig'
    Sending 'vendor_boot' (98304 KB)                   OKAY [  2.657s]
    Writing 'vendor_boot'                              OKAY [  0.283s]
    extracting super_empty.img (0 MB) to disk... took 0.001s
    Rebooting into fastboot                            OKAY [  0.001s]
    < waiting for any device >
    Sending 'super' (4 KB)                             OKAY [  0.001s]
    Updating super partition                           OKAY [  0.019s]
    Resizing 'odm_a'                                   OKAY [  0.004s]
    Resizing 'product_a'                               OKAY [  0.004s]
    Resizing 'system_a'                                OKAY [  0.005s]
    Resizing 'system_ext_a'                            OKAY [  0.004s]
    Resizing 'system_b'                                OKAY [  0.004s]
    Resizing 'vendor_a'                                OKAY [  0.004s]
    Resizing 'vendor_b'                                OKAY [  0.004s]
    archive does not contain 'boot_other.img'
    extracting odm.img (1 MB) to disk... took 0.015s
    archive does not contain 'odm.sig'
    Resizing 'odm_a'                                   OKAY [  0.005s]
    Sending 'odm_a' (1568 KB)                          OKAY [  0.046s]
    Writing 'odm_a'                                    OKAY [  0.096s]
    archive does not contain 'odm_dlkm.img'
    extracting product.img (1786 MB) to disk... took 14.842s
    Invalid sparse file format at header magic
    archive does not contain 'product.sig'
    Resizing 'product_a'                               OKAY [  0.005s]
    Sending sparse 'product_a' 1/7 (262116 KB)         OKAY [  7.673s]
    Writing 'product_a'                                OKAY [  0.454s]
    Sending sparse 'product_a' 2/7 (262124 KB)         OKAY [  7.725s]
    Writing 'product_a'                                OKAY [  0.442s]
    Sending sparse 'product_a' 3/7 (262124 KB)         OKAY [  7.709s]
    Writing 'product_a'                                OKAY [  0.444s]
    Sending sparse 'product_a' 4/7 (262128 KB)         OKAY [  7.706s]
    Writing 'product_a'                                OKAY [  0.430s]
    Sending sparse 'product_a' 5/7 (262116 KB)         OKAY [  7.723s]
    Writing 'product_a'                                OKAY [  0.449s]
    Sending sparse 'product_a' 6/7 (262140 KB)         OKAY [  7.725s]
    Writing 'product_a'                                OKAY [  0.445s]
    Sending sparse 'product_a' 7/7 (250948 KB)         OKAY [  7.405s]
    Writing 'product_a'                                OKAY [  0.448s]
    extracting system.img (923 MB) to disk... took 8.025s
    Invalid sparse file format at header magic
    archive does not contain 'system.sig'
    Resizing 'system_a'                                OKAY [  0.005s]
    Sending sparse 'system_a' 1/4 (262108 KB)          OKAY [  7.662s]
    Writing 'system_a'                                 OKAY [  0.454s]
    Sending sparse 'system_a' 2/4 (262120 KB)          OKAY [  7.721s]
    Writing 'system_a'                                 OKAY [  0.459s]
    Sending sparse 'system_a' 3/4 (262116 KB)          OKAY [  7.700s]
    Writing 'system_a'                                 OKAY [  0.448s]
    Sending sparse 'system_a' 4/4 (156524 KB)          OKAY [  4.622s]
    Writing 'system_a'                                 OKAY [  0.359s]
    extracting system_ext.img (565 MB) to disk... took 4.721s
    Invalid sparse file format at header magic
    archive does not contain 'system_ext.sig'
    Resizing 'system_ext_a'                            OKAY [  0.004s]
    Sending sparse 'system_ext_a' 1/3 (262116 KB)      OKAY [  7.697s]
    Writing 'system_ext_a'                             OKAY [  0.446s]
    Sending sparse 'system_ext_a' 2/3 (262140 KB)      OKAY [  7.559s]
    Writing 'system_ext_a'                             OKAY [  0.429s]
    Sending sparse 'system_ext_a' 3/3 (53244 KB)       OKAY [  1.570s]
    Writing 'system_ext_a'                             OKAY [  0.223s]
    archive does not contain 'system_other.img'
    extracting vendor.img (857 MB) to disk... took 7.361s
    Invalid sparse file format at header magic
    archive does not contain 'vendor.sig'
    Resizing 'vendor_a'                                OKAY [  0.004s]
    Sending sparse 'vendor_a' 1/4 (262100 KB)          OKAY [  7.707s]
    Writing 'vendor_a'                                 OKAY [  0.461s]
    Sending sparse 'vendor_a' 2/4 (262124 KB)          OKAY [  7.700s]
    Writing 'vendor_a'                                 OKAY [  0.452s]
    Sending sparse 'vendor_a' 3/4 (262140 KB)          OKAY [  7.702s]
    Writing 'vendor_a'                                 OKAY [  0.449s]
    Sending sparse 'vendor_a' 4/4 (88768 KB)           OKAY [  2.635s]
    Writing 'vendor_a'                                 OKAY [  0.285s]
    archive does not contain 'vendor_dlkm.img'
    archive does not contain 'vendor_other.img'
    Rebooting                                          OKAY [  0.000s]
    Finished. Total time: 197.003s

    2/ Step 2 > Update Magisk Boot Patched
    Code:
    c:\Android>fastboot boot magisk_patched-25205_96FMZ.img
    Sending 'boot.img' (98304 KB)                      OKAY [  2.721s]
    Booting

    3/ Step 3 > Boot Success
    Apply Root after Boot Successfuly
    Code:
    Open Magisk :
    Magisk > Install > Direct install (Recommanded) > "Let's Go"
    "All done!" > Reboot


    BUG : I use 2 SIM and now on Alpha 2 there only one Signal for the "prefered Data" SIM and not the other SIM