Database Users

Help! soft brick while upgrading to update 3.0

TLDR/update: false alarm, after a pc reboot. and leaving the shield unplugged for a few min. i was able to "adb reboot bootloader" then reflash with fastboot, all good now. mods feel free to delete this bs...
i downloaded the official 3.0 recovery image from nvidia and commented out the bit to flash there recovery so i could keep twrp just like i have previously w/o issues. now im stuck and cant seem to access the bootloader by holding the power button, adb, or fastboot. what other options do i have? flashing from update.zip on sd card?
Code:
./flash-all.sh
< waiting for any device >
target reported max download size of 67108864 bytes
sending 'staging' (3091 KB)...
OKAY [ 0.091s]
writing 'staging'...
OKAY [ 0.152s]
finished. total time: 0.243s
target reported max download size of 67108864 bytes
sending 'boot' (21772 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.024s]
finished. total time: 1.551s
rebooting...
finished. total time: 0.059s
< waiting for any device >
sending 'system' (1578475 KB)...
FAILED (command write failed (Protocol error))
finished. total time: 0.000s
target reported max download size of 67108864 bytes
erasing 'vendor'...
OKAY [ 0.164s]
sending sparse 'vendor' (65498 KB)...
OKAY [ 1.606s]
writing 'vendor'...
OKAY [ 3.285s]
sending sparse 'vendor' (65472 KB)...
OKAY [ 1.582s]
writing 'vendor'...
OKAY [ 2.895s]
sending sparse 'vendor' (65532 KB)...
OKAY [ 1.611s]
writing 'vendor'...
OKAY [ 3.437s]
sending sparse 'vendor' (48152 KB)...
OKAY [ 1.196s]
writing 'vendor'...
OKAY [ 2.448s]
finished. total time: 18.223s
rebooting...
if it didnt sent the reboot command i could have seen the error and hopefully fixed it. guess i gave nvidia too much credit for error detection in there script.

P8 Lite ALE-L21 bootloop or dead

Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?

as far as i can see,you have flashed system.img and he work,now try again to flash via adb only system.img,wen is done,run command fastboot reboot an remove usb cable from phone and press and hold on volume button up to enter in recovery mod,once in recovery wipe data factory reset and wipe cache,it wiil delete all your memory phone,but it my work,so good luck

Hello Cristi,
Thank you for reply, i will try to flash only with system.img and then reboot.
Then I'll come back with the result.
There any other method to flash full memory ? (e.g. with SP_Flash_Tool ) Delete all data and then complete installation with full fw?

Bad News,
After I flash adb only with system.img and then reboot, push volume + & power, only light red light flashing slower.
Is possible that the bottom Volume UP, may not work

Do you have a NAND backup through TWRP?
What FW are you trying to flash?
What happened so that it shows this?

Try to flash with other version ... try to flash with b170

@ - Hello oziboy;
I don`t have a backup and i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common));
I don`t know the history .... the device has got to me so broken
@ - Hello VladHD;
i will try , thk for info.

Hi....
try first to flash with fastboot firmware b049 or b052,
when finished flashing then factory reset and wipe....
then local update 171 or 170....

ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
you can try here http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977

I did get another motherboard, and now the phone is total functional.

K
Sent from my ALE-L21 using XDA-Developers mobile app

ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
My p8lite phone also soft bricked can you tell how did you unlocked your boot loader?

I use this method:
- Open Huawei Product ID Generator, then complete:
Product Model: U8815,
Product IMEI: imei from sim1;
and now you have Product ID generated;
now, Connect your phone via data cable to PC;
Switch it off and then by pressing volume down and power together make it in fastboot mode (in this mode you will see "Phone locked" in green color at bottom of screen)
- enter https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail login with ID facebook or create an account; and then complete with:
Product Model: U8815 - like Huawei Product ID Generator;
Product Serial Number: 16 characters ; will be found on the box of device or type command "fastboot devices", when you connect the phone in fastboot mode (volume down + power botton);
Product IMEI: imei from sim1 ;
Product ID: the code generated from Huawei Product ID Generator program;
Verification code: characters from picture;
and then submit; if everything is OK, the code will be generated;
type command: "fastboot oem unlock **************** "
where ************** is code generated on emui.huawei.com;
Good luck

ingerul_danutz said:
I did get another motherboard, and now the phone is total functional.
Click to expand...
Click to collapse
Where did you buy new motherboard?

Huawei Y6 (2018) , Impossible debrand?

I flashed the phone with fastboot with a non-branded STOCK ROM, file by file, when the phone was rebooted, it was branded TIM Italy, why?
Is it possible that fastboot, despite the video results, did not flasha anything?
I tried several ROMs without success.
Code:
D:\Cellulare\adb-and-fastboot>fastboot flash cust debrand\CUST.img
Sending 'cust' (134830 KB) OKAY [ 5.832s]
Writing 'cust' OKAY [ 3.059s]
Finished. Total time: 8.928s
D:\Cellulare\adb-and-fastboot>fastboot flash kernel debrand\KERNEL.img
Sending 'kernel' (45749 KB) OKAY [ 1.629s]
Writing 'kernel' OKAY [ 1.009s]
Finished. Total time: 2.676s
D:\Cellulare\adb-and-fastboot>fastboot flash ramdisk debrand\RAMDISK.img
Sending 'ramdisk' (11205 KB) OKAY [ 0.414s]
Writing 'ramdisk' OKAY [ 0.273s]
Finished. Total time: 0.726s
D:\Cellulare\adb-and-fastboot>fastboot flash recovery_ramdisk debrand\RECOVERY_RAMDIS.img
Sending 'recovery_ramdisk' (27893 KB) OKAY [ 0.998s]
Writing 'recovery_ramdisk' OKAY [ 0.630s]
Finished. Total time: 1.676s
D:\Cellulare\adb-and-fastboot>fastboot flash system debrand\SYSTEM.img
Sending sparse 'system' 1/6 (468550 KB) OKAY [ 19.835s]
Writing sparse 'system' 1/6 OKAY [ 12.017s]
Sending sparse 'system' 2/6 (513679 KB) OKAY [ 20.851s]
Writing sparse 'system' 2/6 OKAY [ 11.767s]
Sending sparse 'system' 3/6 (515737 KB) OKAY [ 20.873s]
Writing sparse 'system' 3/6 OKAY [ 12.012s]
Sending sparse 'system' 4/6 (517855 KB) OKAY [ 21.453s]
Writing sparse 'system' 4/6 OKAY [ 12.797s]
Sending sparse 'system' 5/6 (521377 KB) OKAY [ 21.275s]
Writing sparse 'system' 5/6 OKAY [ 11.808s]
Sending sparse 'system' 6/6 (57052 KB) OKAY [ 2.236s]
Writing sparse 'system' 6/6 OKAY [ 1.276s]
Finished. Total time: 222.547s
D:\Cellulare\adb-and-fastboot>fastboot reboot
Rebooting
Finished. Total time: 0.004s
D:\Cellulare\adb-and-fastboot>

ShieldTv (2015 16gb) stuck on boot logo

Hi, I have a shield Tv 2015, 16gb version. Few weeks after the upgrade at 8.2, the shield stopped working with a black screen. I unplugged the power, and from that point on, it's stuck in the 4 rolling circles boot logo (before composing the android word).
I went into fastboot and I tried to flash the image using the instructions here:
https://forum.xda-developers.com/shield-tv/general/guide-how-to-flash-recovery-image-t3321404
I took the NVIDIA SHIELD ANDROID TV 2015 Recovery OS Image (8.2.0).
Everything seems worked fine, at least as far as fastboot was telling me, but after I rebooted, it was same as before, still stuck on the boot logo, like if I have not flashed anything.
Any advice on how to proceed? Is it bricked and there is nothing to do?
Here is the log from the flashing:
Code:
./fastboot flash staging blob Mon Oct 26 18:22:51 2020
Sending 'staging' (6589 KB) OKAY [ 0.183s]
Writing 'staging' OKAY [ 0.283s]
Finished. Total time: 0.533s
./fastboot flash boot boot.img 547ms  Mon Oct 26 18:23:35 2020
Sending 'boot' (10406 KB) OKAY [ 0.258s]
Writing 'boot' OKAY [ 0.429s]
Finished. Total time: 0.737s
./fastboot flash recovery recovery.img Mon Oct 26 18:27:46 2020
Sending 'recovery' (17342 KB) OKAY [ 0.467s]
Writing 'recovery' OKAY [ 0.693s]
Finished. Total time: 1.175s
./fastboot flash system system.img Mon Oct 26 18:29:05 2020
Sending sparse 'system' 1/55 (32764 KB) OKAY [ 0.865s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 2/55 (32764 KB) OKAY [ 0.871s]
Writing 'system' OKAY [ 1.289s]
Sending sparse 'system' 3/55 (32764 KB) OKAY [ 0.868s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 4/55 (32764 KB) OKAY [ 0.858s]
Writing 'system' OKAY [ 1.303s]
Sending sparse 'system' 5/55 (32764 KB) OKAY [ 0.846s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 6/55 (32764 KB) OKAY [ 0.877s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 7/55 (32764 KB) OKAY [ 0.869s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 8/55 (32764 KB) OKAY [ 0.868s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 9/55 (32764 KB) OKAY [ 0.877s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 10/55 (32764 KB) OKAY [ 0.872s]
Writing 'system' OKAY [ 1.288s]
Sending sparse 'system' 11/55 (32564 KB) OKAY [ 0.846s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 12/55 (32764 KB) OKAY [ 0.875s]
Writing 'system' OKAY [ 1.285s]
Sending sparse 'system' 13/55 (32764 KB) OKAY [ 0.852s]
Writing 'system' OKAY [ 1.288s]
Sending sparse 'system' 14/55 (32764 KB) OKAY [ 0.858s]
Writing 'system' OKAY [ 1.282s]
Sending sparse 'system' 15/55 (32764 KB) OKAY [ 0.854s]
Writing 'system' OKAY [ 1.286s]
Sending sparse 'system' 16/55 (32764 KB) OKAY [ 0.868s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 17/55 (32764 KB) OKAY [ 0.866s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 18/55 (32764 KB) OKAY [ 0.869s]
Writing 'system' OKAY [ 1.291s]
Sending sparse 'system' 19/55 (31776 KB) OKAY [ 0.825s]
Writing 'system' OKAY [ 1.255s]
Sending sparse 'system' 20/55 (32764 KB) OKAY [ 0.859s]
Writing 'system' OKAY [ 1.281s]
Sending sparse 'system' 21/55 (32764 KB) OKAY [ 0.864s]
Writing 'system' OKAY [ 1.296s]
Sending sparse 'system' 22/55 (32764 KB) OKAY [ 0.864s]
Writing 'system' OKAY [ 1.296s]
Sending sparse 'system' 23/55 (32764 KB) OKAY [ 0.856s]
Writing 'system' OKAY [ 1.284s]
Sending sparse 'system' 24/55 (32764 KB) OKAY [ 0.857s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 25/55 (32764 KB) OKAY [ 0.857s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 26/55 (32764 KB) OKAY [ 0.857s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 27/55 (31776 KB) OKAY [ 0.843s]
Writing 'system' OKAY [ 1.257s]
Sending sparse 'system' 28/55 (32764 KB) OKAY [ 0.873s]
Writing 'system' OKAY [ 1.287s]
Sending sparse 'system' 29/55 (32764 KB) OKAY [ 0.879s]
Writing 'system' OKAY [ 1.301s]
Sending sparse 'system' 30/55 (32764 KB) OKAY [ 0.858s]
Writing 'system' OKAY [ 1.282s]
Sending sparse 'system' 31/55 (32764 KB) OKAY [ 0.871s]
Writing 'system' OKAY [ 1.289s]
Sending sparse 'system' 32/55 (32764 KB) OKAY [ 0.856s]
Writing 'system' OKAY [ 1.284s]
Sending sparse 'system' 33/55 (32764 KB) OKAY [ 0.856s]
Writing 'system' OKAY [ 1.284s]
Sending sparse 'system' 34/55 (32764 KB) OKAY [ 0.859s]
Writing 'system' OKAY [ 1.301s]
Sending sparse 'system' 35/55 (31776 KB) OKAY [ 0.847s]
Writing 'system' OKAY [ 1.253s]
Sending sparse 'system' 36/55 (32764 KB) OKAY [ 0.864s]
Writing 'system' OKAY [ 1.296s]
Sending sparse 'system' 37/55 (32764 KB) OKAY [ 0.867s]
Writing 'system' OKAY [ 1.293s]
Sending sparse 'system' 38/55 (32764 KB) OKAY [ 0.867s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 39/55 (32764 KB) OKAY [ 0.861s]
Writing 'system' OKAY [ 1.299s]
Sending sparse 'system' 40/55 (32764 KB) OKAY [ 0.872s]
Writing 'system' OKAY [ 1.288s]
Sending sparse 'system' 41/55 (32764 KB) OKAY [ 0.856s]
Writing 'system' OKAY [ 1.284s]
Sending sparse 'system' 42/55 (32764 KB) OKAY [ 0.868s]
Writing 'system' OKAY [ 1.292s]
Sending sparse 'system' 43/55 (32764 KB) OKAY [ 0.864s]
Writing 'system' OKAY [ 1.296s]
Sending sparse 'system' 44/55 (32764 KB) OKAY [ 0.857s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 45/55 (32764 KB) OKAY [ 0.866s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 46/55 (32764 KB) OKAY [ 0.869s]
Writing 'system' OKAY [ 1.291s]
Sending sparse 'system' 47/55 (32764 KB) OKAY [ 0.879s]
Writing 'system' OKAY [ 1.301s]
Sending sparse 'system' 48/55 (32764 KB) OKAY [ 0.847s]
Writing 'system' OKAY [ 1.293s]
Sending sparse 'system' 49/55 (32764 KB) OKAY [ 0.897s]
Writing 'system' OKAY [ 1.283s]
Sending sparse 'system' 50/55 (32764 KB) OKAY [ 0.860s]
Writing 'system' OKAY [ 1.300s]
Sending sparse 'system' 51/55 (32764 KB) OKAY [ 0.872s]
Writing 'system' OKAY [ 1.288s]
Sending sparse 'system' 52/55 (32764 KB) OKAY [ 0.862s]
Writing 'system' OKAY [ 1.298s]
Sending sparse 'system' 53/55 (32764 KB) OKAY [ 0.866s]
Writing 'system' OKAY [ 1.293s]
Sending sparse 'system' 54/55 (32764 KB) OKAY [ 0.866s]
Writing 'system' OKAY [ 1.294s]
Sending sparse 'system' 55/55 (19700 KB) OKAY [ 0.531s]
Writing 'system' OKAY [ 0.789s]
Finished. Total time: 117.518s
./fastboot flash vendor vendor.img 1.9m  Mon Oct 26 18:32:31 2020
Sending sparse 'vendor' 1/12 (32764 KB) OKAY [ 0.863s]
Writing 'vendor' OKAY [ 1.294s]
Sending sparse 'vendor' 2/12 (32764 KB) OKAY [ 0.865s]
Writing 'vendor' OKAY [ 1.295s]
Sending sparse 'vendor' 3/12 (32764 KB) OKAY [ 0.871s]
Writing 'vendor' OKAY [ 1.289s]
Sending sparse 'vendor' 4/12 (32764 KB) OKAY [ 0.869s]
Writing 'vendor' OKAY [ 1.291s]
Sending sparse 'vendor' 5/12 (32764 KB) OKAY [ 0.871s]
Writing 'vendor' OKAY [ 1.289s]
Sending sparse 'vendor' 6/12 (32764 KB) OKAY [ 0.875s]
Writing 'vendor' OKAY [ 1.285s]
Sending sparse 'vendor' 7/12 (32764 KB) OKAY [ 0.869s]
Writing 'vendor' OKAY [ 1.291s]
Sending sparse 'vendor' 8/12 (32764 KB) OKAY [ 0.862s]
Writing 'vendor' OKAY [ 1.287s]
Sending sparse 'vendor' 9/12 (32764 KB) OKAY [ 0.875s]
Writing 'vendor' OKAY [ 1.285s]
Sending sparse 'vendor' 10/12 (32764 KB) OKAY [ 0.872s]
Writing 'vendor' OKAY [ 1.278s]
Sending sparse 'vendor' 11/12 (32764 KB) OKAY [ 0.876s]
Writing 'vendor' OKAY [ 1.294s]
Sending sparse 'vendor' 12/12 (29924 KB) OKAY [ 0.799s]
Writing 'vendor' OKAY [ 1.210s]
Finished. Total time: 25.826s

Development Paranoid Android Topaz 2 - Nothing phone (1)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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!

Reserved

Reserved

hell yeah

Thanks a lot for your hard work and to all those who contributed!

herna said:
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
* Some carriers might indicate 4G on the status bar when it's actually 5G.
* 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 stable firmware flashed on both slots before flashing the ROM.
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)
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
Click to expand...
Click to collapse
After a try, "archive does not contain android-info.txt"

The long awaited release. Can't wait to flash it after work

AntoXik72 said:
After a try, "archive does not contain android-info.txt"
Click to expand...
Click to collapse
You need to flash the file that ends in -image.zip
Search for fastboot button on the website, or download -image.zip from Telegram or mirror.

herna said:
You need to flash the file that ends in -image.zip
Search for fastboot button on the website, or download -image.zip from Telegram or mirror.
Click to expand...
Click to collapse
Gotcha, flashed it, perfectly working, thanks again

Flash day, easy step
Will feedback soon
Thanks for the job PA Team, first custom rom for the Nothing 1, congratulation
Code:
c:\Android>fastboot update aospa-topaz-alpha-1-phone1-20221015-image.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 8xxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.003s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (96 MB) to disk... took 0.510s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.764s]
Writing 'boot_a' OKAY [ 0.189s]
extracting dtbo.img (24 MB) to disk... took 0.066s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.653s]
Writing 'dtbo' OKAY [ 0.044s]
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.002s]
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.002s]
Writing 'vbmeta_system' OKAY [ 0.001s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.236s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (98304 KB) OKAY [ 2.632s]
Writing 'vendor_boot' OKAY [ 0.224s]
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.018s]
Resizing 'odm_a' OKAY [ 0.004s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'system_ext_a' OKAY [ 0.005s]
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.100s]
archive does not contain 'odm_dlkm.img'
extracting product.img (1786 MB) to disk... took 10.701s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.004s]
Sending sparse 'product_a' 1/7 (262116 KB) OKAY [ 7.639s]
Writing 'product_a' OKAY [ 0.457s]
Sending sparse 'product_a' 2/7 (262124 KB) OKAY [ 7.709s]
Writing 'product_a' OKAY [ 0.370s]
Sending sparse 'product_a' 3/7 (262124 KB) OKAY [ 7.737s]
Writing 'product_a' OKAY [ 0.359s]
Sending sparse 'product_a' 4/7 (262128 KB) OKAY [ 7.720s]
Writing 'product_a' OKAY [ 0.353s]
Sending sparse 'product_a' 5/7 (262116 KB) OKAY [ 7.702s]
Writing 'product_a' OKAY [ 0.378s]
Sending sparse 'product_a' 6/7 (262140 KB) OKAY [ 7.732s]
Writing 'product_a' OKAY [ 0.425s]
Sending sparse 'product_a' 7/7 (250948 KB) OKAY [ 7.396s]
Writing 'product_a' OKAY [ 0.459s]
extracting system.img (930 MB) to disk... took 8.265s
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.615s]
Writing 'system_a' OKAY [ 0.446s]
Sending sparse 'system_a' 2/4 (262124 KB) OKAY [ 7.719s]
Writing 'system_a' OKAY [ 0.437s]
Sending sparse 'system_a' 3/4 (262108 KB) OKAY [ 7.675s]
Writing 'system_a' OKAY [ 0.449s]
Sending sparse 'system_a' 4/4 (163116 KB) OKAY [ 4.804s]
Writing 'system_a' OKAY [ 0.341s]
extracting system_ext.img (565 MB) to disk... took 4.734s
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.693s]
Writing 'system_ext_a' OKAY [ 0.466s]
Sending sparse 'system_ext_a' 2/3 (262140 KB) OKAY [ 7.501s]
Writing 'system_ext_a' OKAY [ 0.458s]
Sending sparse 'system_ext_a' 3/3 (53124 KB) OKAY [ 1.586s]
Writing 'system_ext_a' OKAY [ 0.247s]
archive does not contain 'system_other.img'
extracting vendor.img (840 MB) to disk... took 7.566s
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 (262096 KB) OKAY [ 7.724s]
Writing 'vendor_a' OKAY [ 0.462s]
Sending sparse 'vendor_a' 2/4 (262124 KB) OKAY [ 7.716s]
Writing 'vendor_a' OKAY [ 0.437s]
Sending sparse 'vendor_a' 3/4 (262140 KB) OKAY [ 7.718s]
Writing 'vendor_a' OKAY [ 0.439s]
Sending sparse 'vendor_a' 4/4 (71624 KB) OKAY [ 2.118s]
Writing 'vendor_a' OKAY [ 0.226s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.000s]
Finished. Total time: 189.064s
c:\Android>
PA 13 ON ^^
Yes Baby

Want to flash this as I've been looking forward to this for a while. But it's my single use device so I am telling myself to wait till it's out of alpha

@herna
Thanks a lot for Paranoid Android A13
Support for german users
Dashboard - LOS-Legacy®​Deine Android Community

How can I use "fastboot erase system" for clean system partition?

Some Screenshots for curious people
1st Feedback, especialy for users want keep N1P Stack Features / Apps, READ BEFORE :
Good points :
+ A13
+ Smooth, really a true Android Pure experience
+ Pixel Lovers you will be happy
+ Beautiful AoD
+ Bluetooth, Dual SIM, Geolocalisation+ working fine
+ NOTHING Camera Working perfectly (but only the v12.0.00.98.03 (first release)]
Bad points :
- No LDAC Audio but also no APTX and others, using apparently AAC by default (don't care in my case, my headset don't using)
- No Glyth for Ringtones/Notifications (Only settings for charging/Battery level)
- Some random visual Glitch / Artifact
- Camera is complete but really basical, there a lot features missing in comparaison N1P Camera Stock (BUT Read in Good points, NOTHING Camera can be installed!)

How to make sure that i have latest firmware on both slots?

xtcislove said:
How to make sure that i have latest firmware on both slots?
Click to expand...
Click to collapse
You don't have to, I flashed this on 1.1.3 update, working fine.

Dunno if it's a bug or not but fastboot button on website downloads non -image.zip version. Downloaded from telegram and it's all good. Thanks!

Awesome build. But far from complete guys. Only flashed it because of A13

fastboot update aospa-topaz-alpha-1-phone1-20221015-image.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 32c1a920
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.003s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (96 MB) to disk... took 0.272s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.159s]
Writing 'boot_a' OKAY [ 0.187s]
extracting dtbo.img (24 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.780s]
Writing 'dtbo' OKAY [ 0.037s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
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.000s
Rebooting into fastboot OKAY [ 0.002s]
< 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.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.006s
archive does not contain 'odm.sig'
Resizing 'odm_a' OKAY [ 0.005s]
Sending 'odm_a' (1568 KB) OKAY [ 0.044s]
Writing 'odm_a' OKAY [ 0.103s]
extracting product.img (1786 MB) to disk... took 5.427s
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 [ 8.959s]
Writing 'product_a' OKAY [ 0.457s]
Sending sparse 'product_a' 2/7 (262124 KB) OKAY [ 8.286s]
Writing 'product_a' OKAY [ 0.430s]
Sending sparse 'product_a' 3/7 (262124 KB) OKAY [ 8.747s]
Writing 'product_a' OKAY [ 0.440s]
Sending sparse 'product_a' 4/7 (262128 KB) OKAY [ 8.190s]
Writing 'product_a' OKAY [ 0.438s]
Sending sparse 'product_a' 5/7 (262116 KB) OKAY [ 8.791s]
Writing 'product_a' OKAY [ 0.441s]
Sending sparse 'product_a' 6/7 (262140 KB) OKAY [ 8.600s]
Writing 'product_a' OKAY [ 0.440s]
Sending sparse 'product_a' 7/7 (250948 KB) OKAY [ 8.109s]
Writing 'product_a' OKAY [ 0.419s]
archive does not contain 'product_services.img'
extracting system.img (930 MB) to disk... took 2.976s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.003s]
Sending sparse 'system_a' 1/4 (262108 KB) OKAY [ 8.350s]
Writing 'system_a' OKAY [ 0.456s]
Sending sparse 'system_a' 2/4 (262124 KB) OKAY [ 8.074s]
Writing 'system_a' OKAY [ 0.438s]
Sending sparse 'system_a' 3/4 (262108 KB) OKAY [ 8.665s]
Writing 'system_a' OKAY [ 0.455s]
Sending sparse 'system_a' 4/4 (163116 KB) OKAY [ 5.349s]
Writing 'system_a' OKAY [ 0.331s]
archive does not contain 'system_other.img'
extracting vendor.img (840 MB) to disk... took 2.663s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/4 (262096 KB) OKAY [ 8.631s]
Writing 'vendor_a' OKAY [ 0.451s]
Sending sparse 'vendor_a' 2/4 (262124 KB) OKAY [ 8.849s]
Writing 'vendor_a' OKAY [ 0.434s]
Sending sparse 'vendor_a' 3/4 (262140 KB) OKAY [ 8.708s]
Writing 'vendor_a' OKAY [ 0.412s]
Sending sparse 'vendor_a' 4/4 (71624 KB) OKAY [ 2.444s]
Writing 'vendor_a' OKAY [ 0.152s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.000s]
Finished. Total time: 158.629s
reboot to fastboot mode
can someone help me

Looks pretty awesome, great work