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.
Hey, so my oneplus 2 was having some trouble so I got instructions from here
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449/
I followed it correctly and got to color OS...
But, then I flashed some oneplus ONE files by mistake.
target reported max download size of 536870912 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.387s]
writing 'modem'...
OKAY [ 0.432s]
finished. total time: 1.819s
target reported max download size of 536870912 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.050s]
writing 'sbl1'...
OKAY [ 0.024s]
finished. total time: 0.074s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.040s]
writing 'dbi'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.050s]
writing 'aboot'...
OKAY [ 0.027s]
finished. total time: 0.077s
target reported max download size of 536870912 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.040s]
writing 'rpm'...
OKAY [ 0.025s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'tz' (325 KB)...
OKAY [ 0.040s]
writing 'tz'...
OKAY [ 0.025s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.040s]
writing 'rpm'...
OKAY [ 0.025s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'tz' (325 KB)...
OKAY [ 0.040s]
writing 'tz'...
OKAY [ 0.025s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.040s]
writing 'LOGO'...
OKAY [ 0.025s]
finished. total time: 0.064s
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.267s]
writing 'oppostanvbk'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.286s
target reported max download size of 536870912 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.268s]
writing 'recovery'...
OKAY [ 0.106s]
finished. total time: 0.374s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.463s]
sending sparse 'system' (518655 KB)...
OKAY [ 12.599s]
writing 'system'...
OKAY [ 4.229s]
sending sparse 'system' (515023 KB)...
OKAY [ 12.493s]
writing 'system'...
OKAY [ 4.952s]
sending sparse 'system' (184809 KB)...
OKAY [ 4.555s]
writing 'system'...
OKAY [ 1.804s]
finished. total time: 41.094s
target reported max download size of 536870912 bytes
sending 'boot' (7272 KB)...
OKAY [ 0.218s]
writing 'boot'...
OKAY [ 0.073s]
finished. total time: 0.291s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (10432 KB)...
OKAY [ 0.277s]
writing 'cache'...
FAILED (remote: size too large)
finished. total time: 0.326s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.254s]
sending 'userdata' (141075 KB)...
OKAY [ 3.435s]
writing 'userdata'...
FAILED (remote: size too large)
finished. total time: 4.704s
rebooting...
finished. total time: 0.060s
Since then neither does it turn on. Nor is there fastboot boot.
It isn't recognized by Linux or windows.
No vibration on power button or ANYTHING.
PLEASE HELP ASAP.
try enter qualcomm recovery mode by hold volume up while connecting to usb cable on pc..the phone's screen will show nothing..you just to check whether if detected or not in your pc..if yes,you continue the below procedure:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
same issue here nvidia is really pissing me off
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
rodalpho said:
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
Click to expand...
Click to collapse
For me that works by limiting chunk size. But after flashing and reboot I get "No command" or gets stuck on Logo Screen NVIDIA
Did you flash vendor.img afterwards? I try re-flashing the entire series from flash-all.sh in sequence. To get back to fastboot mode, try Nvidia's hardware instructions here.
http://developer.download.nvidia.co...ATV_2017/5.0.0/HowTo-Flash-Recovery-Image.txt
pendragon666 said:
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
Click to expand...
Click to collapse
I would advise you to quickly download DRM Info from the PlayStore, If you can, and verify you still have Widevine L1 Status. It might not be a big deal if you don't use Netflix, or Amazon. But other outfits like NBC which is free, also use this to protect their Content, and will prevent you from viewing such if your not in compliance.
I know this as I myself got into the same but of trouble between Experience 3.x, and 5.x on my Pro. I managed to get a different Device, and have since made a backup of first few Partitions of my SSHD on my Shield to cover my ass in the eventual case that it should ever happen again.
Though I'm not sure how that's going to be relevant info for a 16Gb eMMC user though.
The flashing worked with chunk limiting.
I think my updating failed after i flashed that zip i mentioned in the first post because of wrong keys. When i flashed the update with twrp it said something along those lines and failed.
Everything back to normal now.
Thanks for the solution.
I had to sparse system and vendor images with -S 50M to get it to work.
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>
{
"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