Development Paranoid Android Topaz 1 - Nothing phone (1)
- Thread starter herna
- Start date
I already told you, you just have to follow the unbrick tutorial. Choose a super.img, it doesn't matter if it's 1.1.4 or 1.1.3 as long as it's Euro. if you don't do that, the utility tool will never work.
So first the super.img and then the tool, right?
I think that's what I did but I'll try again.
Yes, and when you flash super partition, make sure to have the same log as the one posted in the 1st post. This would mean you have successfully restored your vendor, system etc partitions
Exodusnick
Senior Member
Screen recording not possible .
It also starts running but nothing is recorded and nothing is saved
It also starts running but nothing is recorded and nothing is saved
Помощь! После прошивки телефон показывает ошибку "нажмите и клавишу для выключения" и не может нигде загрузиться. Как лечить или купить новый?
Mod translation: Help! After the firmware, the phone shows the error "press and key to turn off" and cannot boot anywhere. How to treat or buy a new one?
Mod translation: Help! After the firmware, the phone shows the error "press and key to turn off" and cannot boot anywhere. How to treat or buy a new one?
Last edited by a moderator:
Paranoid Android Topaz 1 - Nothing phone (1)
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...
forum.xda-developers.com
Не надо купить новый. (You don't need to buy a new phone)
The important step to restore stock firmware is flashing the super.img first.
After the firmware, it is not covered by the PC, fastboot devices doesn't bother him...Paranoid Android Topaz 1 - Nothing phone (1)
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...
Не надо покупать новый. (Вам не нужно покупать новый телефон)
Важным шагом для восстановления стоковой прошивки является прошивка super.img.
Attachments
Exodusnick
Senior Member
Honestly i can't tell you. I haven't tested that and revert back to stock 1.1.6 now
Exodusnick
Senior Member
Well when you press and hold the power button + volume down it should boot into bootloader.
Well I guess when you're not able to boot into bootloader there is no way to unbrick the device.
Exodusnick
Senior Member
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
-
34
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!5Paranoid 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
#StayParanoid3Updated 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
New posts
-
-
( How to ) convert a bootanimation zip to qmg file ?- Latest: El Kevin navaja veloz
-
-
