Development Paranoid Android Topaz Beta 1 - Nothing phone (1)

Search This thread
Wieless charging working in this rom
Yes work .

IMG_20221103_113101432.jpg IMG_20221103_113043505.jpg
 
Last edited:

demiii

Member
Jul 8, 2018
12
1
1st Feedback
2nd Feedback
3rd Feedback

7h15 SOT - Excellent Battery Life (with AOD disabled)




What is your Operating System ? Windows 7 ?
You must redo these commands with ADB & Drivers updated.




Il you have installed Root module like "Safetynet Fix" it's the reason you have L3 Wide

PA is stock "Certified", not need to use Module for Certified Device/Safetynet
My OS is windows 11, I am using the latest version of ADB and Fastbootd drivers, also using updated android drivers. Tried everything on a Intel and on a AMD device, nothing changd
 
Paranoid Android Topaz Alpha 3 - Official | Android 13 | Nothing Phone (1)

📝 Details:
• Version: #AOSPA #T
• Type: #ROM
• Build: #Official #beta
• Device: #Spacewar
• Updated: 18th Nov 2022

Links:
⬇️ Download (http://paranoidandroid.co/phone1)| Mirror (https://t.me/paranoidaospa/110)
(https://t.me/paranoidaospa/78)📋 Instructions (https://graph.org/AOSPA-Topaz-Spacewar-Flashing-instructions-10-15)
🖼 Screenshots (https://t.me/NothingPhone1/118880?single)
🧵 XDA Thread (https://forum.xda-developers.com/t/paranoid-android-sapphire-alpha-1-nothing-phone-1.4505797/)
📲 Support (https://t.me/stayparanoid)

🪄 Changelog:
• Implemented Face Unlock
• Fixed display corruption
• Improved vibration
• Fixed Bluetooth codecs
• Fixed charging speed
• Improved auto brightness
• Improved boot time,
• Fixed DRM (Widevine L3 for now)
• November SPL
• Known issues (https://forum.xda-developers.com/t/paranoid-android-sapphire-alpha-1-nothing-phone-1.4505797/)

👤 Maintainer: herna, xboxfanj, 33bca, TheCrazyLex
🔔 Updates : @NothingPhone1Updates
🦜 Chat : @NothingPhone1
 

QaulityPro

New member
Nov 12, 2014
3
0
Nothing Phone 1
Can anyone advise on the attempt to update to alpha 3

Im sure drivers are up to date. I didn't have this when updating from alpha 1 to 2.

Any help appreciated, thanks.

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
 

Pho3nX

Senior Member
Jun 13, 2013
2,881
2,083
Nothing Phone 1
Can anyone advise on the attempt to update to alpha 3

Im sure drivers are up to date. I didn't have this when updating from alpha 1 to 2.

Any help appreciated, thanks.

C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
usage: fastboot [ <option> ] <command>

---

Try to copy/past a proper folder contain adb / fastboot files on the c:\ root, don't use adb from a OneDrive synced folder with extracted files from your desktop.
And your line was wrong ;
Code:
C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
instead
Code:
C:\>fastboot update C:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
 

QaulityPro

New member
Nov 12, 2014
3
0
Nothing Phone 1
Try to copy/past a proper folder contain adb / fastboot files on the c:\ root, don't use adb from a OneDrive synced folder with extracted files from your desktop.
And your line was wrong ;
Code:
C:\>fastboot updateC:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
instead
Code:
C:\>fastboot update C:\Users\kabet\OneDrive\Desktop\aospa-topaz-alpha-3-phone1-20221118-image.zip
Thank you, I shall give that a go
 

Black_Sandy

New member
Mar 24, 2020
1
0
why do I get this error message?
>fastboot update C:\Users\....\Downloads\aospa-topaz-alpha-3-phone1-20221118-image.zip

target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
Invalid sparse file format at header magi
archive does not contain 'system.sig'
Invalid sparse file format at header magi
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: d3960
--------------------------------------------
checking product...
OKAY [ 0.004s]
sending 'boot' (98304 KB)...
OKAY [ 2.231s]
writing 'boot'...
OKAY [ 0.202s]
sending sparse 'system' (775407 KB)...
OKAY [ 20.227s]
writing 'system'...
FAILED (remote: Partition not found)
finished. total time: 22.697s
 
Last edited:

marcii-ec

Member
Apr 13, 2018
25
5
Stukenbrock
If someone is interested: I also tried the connection with my car today, it works perfect. I tried it with Android Auto cable and Android Auto wireless, no problems so far.
 

AdiGurjar

Senior Member
Nov 10, 2013
52
15
Jabalpur (M.P)
Bugs I found on PA Alpha 3 for NP1:

1-General Screen flickering
2-Auto brightness is poor
3-Battery life can be improved


Critical bugs:

1-Screen won't wake up at all with power button sometimes when AOD is on, a forced restart is the only workaround. Keeping the AOD off prevents this bug.

2-Excessive screen flickering when typing on low brightness.

3-Call UI is choppy.

Rest the rom is smooth and very responsive, kudos to the devs!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New update beta 1 available

    Changelog
    January 2023 SPL, Improved Glyph, Enforcing SELinux
    1
    No problem, I got a perfect custom kernel to use with Topaz beta 3.
    1
    New update beta 1 available

    Changelog
    January 2023 SPL, Improved Glyph, Enforcing SELinux

    You miss the most important mate :)
    NOS 1.5 base (the first custom rom using 1.5^^)


    Paranoid Android Topaz Beta 1 - Official | Android 13 | Nothing Phone (1)

    January 09, 2023


    PA Beta 1 Changelog (spacewar)

    • Upgraded to January 2023 Security Patch Level and Android 13 Quarterly Platform Release 1
    • Upgraded Nothing binaries to Nothing OS 1.5 Beta
    • Enforcing SELinux
    • Added additional Glyph settings
    • User builds
    • Single Tap to Wake
    • Performance improvements and bug fixes
    1
    @herna At last after falcon moto g, came here to meet you ,
  • 34
    Frame 7.png


    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

    * Some HDR videos might lag after a few seconds of playing.


    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.

    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