Development Paranoid Android Topaz 6 - Nothing phone (1)

Search This thread
By:
Advanced…
B

breizhim

Member
Feb 28, 2008
12
2
Hi,

I got Nothing 1.5.2 rooted on my phone. I don't want root anymore, and want to flash Paranoid.

1) does the flash work whith a rooted phone ?

2) will i loose root on the flashed rom ?

Thank you
 
S

shafigk1511

New member
Apr 25, 2023
1
0
Hi outlook in my work apps is not suggesting email addresses in this ROM. Rest all is working fine and smoothly. Glymph I don't use so not an issue though phone ring glymph lights aren't working for me.
 
pankspoo

pankspoo

Senior Member
Jun 27, 2013
1,878
992
in front of ENCHILADA
zelos156 said:
New update out. Security Patch Level: 2023-04-05

Updated to lastest kernel sources
Added call and notifications patterns
Added Music Visualizer / Disco Mode to Glyph Performance improvements and bug fixes.

Click to expand...
Click to collapse
Where are calls and notification patterns I did not found it under glyph
zelos156 said:
New update out. Security Patch Level: 2023-04-05

Updated to lastest kernel sources
Added call and notifications patterns
Added Music Visualizer / Disco Mode to Glyph Performance improvements and bug fixes.

Click to expand...
Click to collapse
Where are calls and notification patterns I did not found it under glyph
 
  • Like
Reactions: Skye.life
nontheoretical

nontheoretical

Senior Member
Sep 6, 2016
71
64
New Orleans
Samsung Galaxy Tab S6 Lite
Nothing Phone 1
pankspoo said:
I think they didn't have sounds, they are just glyph interface not synchronised with ringtones I am correct or not?
Click to expand...
Click to collapse
The patterns are there not the sounds, but you can download the sounds yourself and put them on the internal SD card and use them in parallel. It's less elegant this way, but still workable. Doesn't bug me as I have the phone on vibrate at all times anyway.
 
Last edited:
bariz143

bariz143

Senior Member
Dec 11, 2009
2,206
411
Samsung Galaxy Z Fold 5
Why am i getting this message when trying to flash the latest ROM?

"Slot Change is not allowed in merging state"

And with TOPAZ 3 i get this message

Bootloader Version...: 00872-LAHAINA-2.487493.1
Baseband Version.....: 00781-LC_ALL_PACK-1
--------------------------------------------
archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt
 
Last edited:
P

phrozenwire

Senior Member
Nov 24, 2008
163
4
Pune
@herna Very good and stable ROM. Only issue I noticed is with brightness settings. The sensor calibrated brightness is too low in low light. The screen looks very dim in low light and doesnt really light up as it used to on the original ROM. Even if you manually up the brightness it is not optimal and the screen still looks dark. I have experienced this on other Custom ROM's as well. Any fix for that.
 
V

vincenzoscala

Member
Jan 4, 2011
7
2
Hi guys, I'm on stable 3.0 - want to update to stable 3.1 - which procedure I need to follow?
It is possible to do update without use of fastboot commands thru pc?
Thanks in advance!
 
T

the_raz

Member
Oct 28, 2015
15
0
Just tried flashing aospa-topaz-3.1 with fastboot update successfully according to the terminal. using latest adb/fastboot but just reboots to bootloader fastboot mode. After first update flash I entered recovery and factory reset it and then proceeded to run the command again in which it flashed the b_slot (might've been my fault for changing it in order to be able to entering recovery mode since it didn't work in slot a). Anyways I tried the same, it flashed the b slot and I entered recovery once again and ran the command again - doesn't boot. I've not set the a slot to active and I've flashed it again (after factory reset) but it just boots up into the fastboot mode.. Any ideas?

fastboot update aospa-topaz-3.1-phone1-20230521-image.zip -------------------------------------------- Bootloader Version...: 00872-LAHAINA-2.487493.1 Baseband Version.....: 00781-LC_ALL_PACK-1 Serial Number........: c91203f0 -------------------------------------------- extracting android-info.txt (0 MB) to RAM... Checking 'product' OKAY [ 0.002s] Setting current slot to 'a' OKAY [ 0.001s] extracting boot.img (96 MB) to disk... took 0.591s archive does not contain 'boot.sig' Sending 'boot_a' (98304 KB) OKAY [ 3.396s] Writing 'boot_a' OKAY [ 0.322s] extracting dtbo.img (24 MB) to disk... took 0.113s archive does not contain 'dtbo.sig' Sending 'dtbo' (24576 KB) OKAY [ 0.797s] Writing 'dtbo' OKAY [ 0.031s] archive does not contain 'dt.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.007s] extracting vbmeta_system.img (0 MB) to disk... took 0.000s archive does not contain 'vbmeta_system.sig' Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s] Writing 'vbmeta_system' OKAY [ 0.007s] extracting super_empty.img (0 MB) to disk... took 0.001s Rebooting into fastboot OKAY [ 0.002s] < waiting for any device > Sending 'super' (4 KB) OKAY [ 0.001s] Updating super partition OKAY [ 0.017s] Resizing 'odm_a' OKAY [ 0.004s] Resizing 'product_a' OKAY [ 0.004s] Resizing 'system_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.008s archive does not contain 'odm.sig' Resizing 'odm_a' OKAY [ 0.004s] Sending 'odm_a' (1384 KB) OKAY [ 0.041s] Writing 'odm_a' OKAY [ 0.116s] extracting product.img (1930 MB) to disk... took 12.778s Invalid sparse file format at header magic archive does not contain 'product.sig' Resizing 'product_a' OKAY [ 0.004s] Sending sparse 'product_a' 1/8 (262120 KB) OKAY [ 8.193s] Writing 'product_a' OKAY [ 0.454s] Sending sparse 'product_a' 2/8 (262124 KB) OKAY [ 8.435s] Writing 'product_a' OKAY [ 0.451s] Sending sparse 'product_a' 3/8 (262128 KB) OKAY [ 8.281s] Writing 'product_a' OKAY [ 0.415s] Sending sparse 'product_a' 4/8 (262124 KB) OKAY [ 8.452s] Writing 'product_a' OKAY [ 0.448s] Sending sparse 'product_a' 5/8 (262124 KB) OKAY [ 8.349s] Writing 'product_a' OKAY [ 0.453s] Sending sparse 'product_a' 6/8 (262136 KB) OKAY [ 8.181s] Writing 'product_a' OKAY [ 0.468s] Sending sparse 'product_a' 7/8 (262100 KB) OKAY [ 8.330s] Writing 'product_a' OKAY [ 0.449s] Sending sparse 'product_a' 8/8 (135544 KB) OKAY [ 4.623s] Writing 'product_a' OKAY [ 0.320s] archive does not contain 'product_services.img' extracting system.img (1140 MB) to disk... took 7.783s Invalid sparse file format at header magic archive does not contain 'system.sig' Resizing 'system_a' OKAY [ 0.004s] Sending sparse 'system_a' 1/5 (262108 KB) OKAY [ 8.895s] Writing 'system_a' OKAY [ 0.447s] Sending sparse 'system_a' 2/5 (262120 KB) OKAY [ 9.056s] Writing 'system_a' OKAY [ 0.454s] Sending sparse 'system_a' 3/5 (262104 KB) Resizing 'odm_a' OKAY [ 0.004s] Sending 'odm_a' (1384 KB) OKAY [ 0.044s] Writing 'odm_a' OKAY [ 8.884s] Writing 'system_a' OKAY [ 0.439s] Sending sparse 'system_a' 4/5 (262140 KB) OKAY [ 8.655s] Writing 'system_a' OKAY [ 0.454s] Sending sparse 'system_a' 5/5 (114976 KB) OKAY [ 3.916s] Writing 'system_a' OKAY [ 0.318s] archive does not contain 'system_other.img' extracting vendor.img (875 MB) to disk... took 5.718s 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 (262088 KB) OKAY [ 8.759s] Writing 'vendor_a' OKAY [ 0.450s] Sending sparse 'vendor_a' 2/4 (262124 KB) OKAY [ 7.976s] Writing 'vendor_a' OKAY [ 0.441s] Sending sparse 'vendor_a' 3/4 (262140 KB) OKAY [ 8.744s] Writing 'vendor_a' OKAY [ 0.438s] Sending sparse 'vendor_a' 4/4 (106828 KB) OKAY [ 3.611s] Writing 'vendor_a' OKAY [ 0.260s] archive does not contain 'vendor_other.img' Rebooting OKAY [ 0.000s] Finished. Total time: 191.429s [/CODE] Factory resetting in recovery says: ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/by-name/metadata because /system/bin/tune2fs is missing ERROR: recovery: Open failed: /metadata/ota: No such file or directory Formatting /data... Formatting /metadata... Data wipe complete. Will test to adb sideload the recovery option aswell. EDIT: Sideloading the zip ended in:" [ICODE]adb sideload aospa-topaz-3.1-phone1-20230521.zip Update package verification took 90.2 s (result 0) Installing update... ERROR: recovery: Error in /sideload/package.zip (status 1) Install from ADB completed with status 1. Installation aborted.

Going to try 3.0 and see if that makes a difference.
EDIT:Same result.
Went back to 1.1.7 using nothing-phone-tools (still bricked) and tried flashing fastboot update aospa-topaz-alpha-*-image.zip, unfortunately still same results as earlier tries :/
 
Last edited:
Xyrocos

Xyrocos

New member
May 27, 2023
1
1
bariz143 said:
Why am i getting this message when trying to flash the latest ROM?

"Slot Change is not allowed in merging state"

And with TOPAZ 3 i get this message

Bootloader Version...: 00872-LAHAINA-2.487493.1
Baseband Version.....: 00781-LC_ALL_PACK-1
--------------------------------------------
archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt
Click to expand...
Click to collapse
fastboot snapshot-update cancel

And after that try again. I had same issue. Also had issue with running newer platform tools so ran 33.0.3

Download Platform Tools for Android SDK Manager

Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net androidsdkmanager.azurewebsites.net
 
  • Like
Reactions: bariz143
You must log in or register to reply here.

Similar threads

A
General Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Replies
1K
Views
148K
A
AnotherM1m
aswin_a_s
Development PixysOS v6.3.1OFFICIAL for Nothing Phone 1 [android 13 QPR3] [STABLE]
Replies
130
Views
32K
B
bono666x
A
Question Gcam for Nothing phone 1
Replies
48
Views
39K
M
meuhmeuh51
Pho3nX
How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)
Replies
248
Views
37K
E
EzerchE
Sib64
  • Sticky
Question [HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly
Replies
417
Views
35K
A
AnotherM1m

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    S
    Shuyin10
    After a week of using NOS 2.0, I can say that I prefer Paranoid!
    Autonomy, no difference (between 5 and 7h SOT depending on use)
    Better design on Paranoid

    No bugs on either side, so there's no point in me staying with NOS
    View
    1
    T
    texrex10
    It's working ok so far for me only been using it a few hours tho.
    shibin_948 said:
    How is the new Topaz 9 working for you guys? any bugs and how is the overall stability and performance?
    please do share some screenshots too if possible. Thanks in advance.
    Click to expand...
    Click to collapse
    It's working fine for me so far, only been using it a few hours.
    View
  • 43
    herna
    herna
    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!
    View
    8
    herna
    herna
    Reserved
    View
    6
    herna
    herna
    Reserved
    View
    5
    herna
    herna
    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
    View
    4
    zelos156
    zelos156
    New update out. Security Patch Level: 2023-04-05

    Updated to lastest kernel sources
    Added call and notifications patterns
    Added Music Visualizer / Disco Mode to Glyph Performance improvements and bug fixes.

    View

New posts