W / Zip Zip Zip: Impossible d'allouer des morsures X à la décalage 0: Pas d'espace laissé sur le périphérique tout en clignotant une image d'usine sur le pêcheur (Nexus 6P) -- rom-flashing domaine et nexus domain android en relation problème

W/ziparchive Zip: unable to allocate X bites at offset 0 : No space left on device while flashing factory image on angler (Nexus 6P)



0
vote

problème

français

J'essayais de faire image flash usine sur Angler sur mon Nexus 6P. Il y a quelques No space left on device Erreur:

./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [ 0.127s] writing 'bootloader'... OKAY [ 0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img < waiting for any device > target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [ 1.283s] writing 'radio'... OKAY [ 2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device failed to extract 'system.img': I/O error

(espace inséré par moi-même pour une meilleure lisibilité)

Je suppose que cela manque d'espace sur le téléphone.

shell@angler: $ df -h Filesystem Size Used Available Use% Mounted on tmpfs 1.4G 484.0K 1.4G 0% /dev tmpfs 1.4G 0 1.4G 0% /mnt /dev/block/dm-0 3.0G 1.8G 1.1G 62% /system /dev/block/dm-1 196.6M 184.7M 8.0M 96% /vendor /dev/block/platform/soc.0/f9824900.sdhci/by-name/cache 92.9M 1.8M 88.0M 2% /cache /dev/block/platform/soc.0/f9824900.sdhci/by-name/persist 3.9M 740.0K 3.0M 20% /persist /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem 80.0M 47.5M 32.4M 59% /firmware tmpfs 1.4G 0 1.4G 0% /storage /dev/block/dm-2 53.5G 132.9M 52.9G 0% /data df: /mnt/runtime/default/emulated: Permission denied /data/media 53.5G 132.9M 52.9G 0% /storage/emulated

Utilisation 9988777663 version 1:8.1.0+r23-5 de Debian, Android est angler:8.1.0 .

Une idée de ce qui pourrait être le problème?

recherche dans les sources, il échoue dans static void* unzip_file(ZipArchiveHandle zip, const char* entry_name, int64_t* sz)

int error = ExtractToMemory(zip, &zip_entry, data, zip_entry.uncompressed_length); if (error != 0) { fprintf(stderr, "failed to extract '%s': %s ", entry_name, ErrorCodeString(error)); free(data); return 0; }

https: / /android.googlesource.com/platform/system/core/+/androïd-8.1.0_r73/fastboot/fastboot.cfastboot/fastboot.cpp#505

ou dans static int unzip_to_file(ZipArchiveHandle zip, const char* entry_name)

int error = ExtractEntryToFile(zip, &zip_entry, fd); if (error != 0) { fprintf(stderr, "failed to extract '%s': %s ", entry_name, ErrorCodeString(error)); return -1; }

https: / /android.googlesource.com/platform/system/core/+/android-8.1.0_r73/fastboot/fastboot.cfastboot/fastboot.cpp#628

Mise à jour : On dirait que c'est vraiment un manque d'espace sur l'ordinateur portable. Auparavant, j'avais environ 8 Go, que j'ai considéré suffisant. Après clair pour avoir 17 Go et essayer de mettre à jour une image différente image-ANGLER-NMF26F.ZIP, j'ai eu une erreur différente (probablement lié ./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [ 0.127s] writing 'bootloader'... OKAY [ 0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img < waiting for any device > target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [ 1.283s] writing 'radio'... OKAY [ 2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device failed to extract 'system.img': I/O error 0 étant ./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [ 0.127s] writing 'bootloader'... OKAY [ 0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img < waiting for any device > target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [ 1.283s] writing 'radio'... OKAY [ 2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device failed to extract 'system.img': I/O error 1

): ./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [ 0.127s] writing 'bootloader'... OKAY [ 0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img < waiting for any device > target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [ 1.283s] writing 'radio'... OKAY [ 2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device failed to extract 'system.img': I/O error 2
langue Anglaise

I was trying to do flash factory image on angler on my Nexus 6P. There is some No space left on device error:

./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [  0.127s] writing 'bootloader'... OKAY [  0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [  0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img < waiting for any device > target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [  1.283s] writing 'radio'... OKAY [  2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [  0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate  2860210996 bytes at offset 0 : \    No space left on device failed to extract 'system.img': I/O error 

(space inserted by myself for better readability)

I suppose this is lacking space on the phone.

shell@angler: $ df -h                                                   Filesystem                Size      Used Available Use% Mounted on tmpfs                     1.4G    484.0K      1.4G   0% /dev tmpfs                     1.4G         0      1.4G   0% /mnt /dev/block/dm-0           3.0G      1.8G      1.1G  62% /system /dev/block/dm-1         196.6M    184.7M      8.0M  96% /vendor /dev/block/platform/soc.0/f9824900.sdhci/by-name/cache                          92.9M      1.8M     88.0M   2% /cache /dev/block/platform/soc.0/f9824900.sdhci/by-name/persist                           3.9M    740.0K      3.0M  20% /persist /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem                          80.0M     47.5M     32.4M  59% /firmware tmpfs                     1.4G         0      1.4G   0% /storage /dev/block/dm-2          53.5G    132.9M     52.9G   0% /data df: /mnt/runtime/default/emulated: Permission denied /data/media              53.5G    132.9M     52.9G   0% /storage/emulated 

Using fastboot version 1:8.1.0+r23-5 from Debian, Android is angler:8.1.0.

Any idea what could be the problem?

Searching in the sources, it fails in static void* unzip_file(ZipArchiveHandle zip, const char* entry_name, int64_t* sz)

int error = ExtractToMemory(zip, &zip_entry, data, zip_entry.uncompressed_length); if (error != 0) {     fprintf(stderr, "failed to extract '%s': %s\n", entry_name, ErrorCodeString(error));     free(data);     return 0; } 

https://android.googlesource.com/platform/system/core/+/android-8.1.0_r73/fastboot/fastboot.cpp#505

or in static int unzip_to_file(ZipArchiveHandle zip, const char* entry_name)

int error = ExtractEntryToFile(zip, &zip_entry, fd); if (error != 0) {     fprintf(stderr, "failed to extract '%s': %s\n", entry_name, ErrorCodeString(error));     return -1; } 

https://android.googlesource.com/platform/system/core/+/android-8.1.0_r73/fastboot/fastboot.cpp#628

UPDATE: it looks like it's really lack of space on the laptop. Previously I had about 8GB, which I considered enough. After clear to have 17GB and trying to update different image image-angler-nmf26f.zip I got different error (probably related /tmp being tmpfs):

strace -o strace.log fastboot -w update image-angler-nmf26f.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2691 MB)... archive does not contain 'system.sig' archive does not contain 'vbmeta.img' extracting vendor.img (194 MB)... W/ziparchive(109113): Zip: unable to allocate  204079852 bytes at offset 0 : No space left on device failed to extract 'vendor.img': I/O error wiping userdata... Couldn't parse erase-block-size '0x'. Couldn't parse logical-block-size '0x'. mke2fs 1.45.5 (07-Jan-2020) /tmp/TemporaryFile-xaoMGH: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata 
     

Liste de réponses

0
 
vote

Selon les autres est -w est en quelque sorte cassé et doit être remplacé par fastboot erase <partition> , par exemple:

fastboot oem unlock fastboot erase boot fastboot erase cache fastboot erase recovery fastboot erase system fastboot erase userdata fastboot flash bootloader bootloader-angler-angler-03.68.img fastboot reboot-bootloader sleep 5 fastboot flash radio radio-angler-angler-03.81.img

i la fin j'ai suivi Suggestion de Firelord à décompresser 9988777665 (au lieu de clignoter) et flash toutes partitions manuellement:

fastboot flash boot boot.img fastboot flash recovery recovery.img fastboot flash system system.img fastboot flash vendor vendor.img

Remarque: Commandes en cours fastboot erase <partition> n'est pas nécessaire comme 9988777668 Système d'effacement.

 

According to the others is -w option is somehow broken and should be replaced with fastboot erase <partition>, e.g.:

fastboot oem unlock fastboot erase boot fastboot erase cache fastboot erase recovery fastboot erase system fastboot erase userdata fastboot flash bootloader bootloader-angler-angler-03.68.img fastboot reboot-bootloader sleep 5 fastboot flash radio radio-angler-angler-03.81.img 

I the end I followed Firelord suggestion to unpack image-angler-nmf26f.zip (instead of flashing it) and flash all partitions manually:

fastboot flash boot boot.img fastboot flash recovery recovery.img fastboot flash system system.img fastboot flash vendor vendor.img 

NOTE: running commands fastboot erase <partition> is not needed as fastboot flash erase system.

 
 

Questions connexes

0  Utilisation d'un lecteur DVD externe avec Nexus 7  ( Using external dvd player with nexus 7 ) 
J'aimerais pouvoir utiliser mon lecteur DVD externe avec ma tablette Nexus 7, y a-t-il un plug-in pour cela ou un montage? ...

0  Bouton de la maison, bouton récent, notifications, menu déroulant tout arrêté de fonctionner  ( Home button recent button notifications pull down menu all stopped working ) 
J'ai un Nexus 9 exécutant Android 7.1.1 et le bouton Accueil, bouton récent, toutes les notifications et le menu déroulant Top a cessé de fonctionner. Les...

0  Échanger ou fusionner les canaux audio gauche et droit  ( Swap or merge left and right audio channels ) 
Le haut-parleur supérieur sur mon Nexus enraciné 6 a cessé de fonctionner après un accident. Chaque fois que je fais un appel, je dois utiliser des écouteurs ...

1  Nexus 7 2013 WIFI (FLO) BootLoader Unlocklock échoue  ( Nexus 7 2013 wifi flo bootloader unlock fails ) 
J'essaie de déverrouiller le chargeur de démarrage de My Nexus 7 2013 WIFI 32GB (FLO). Je l'ai éteint, appuyé sur le bouton d'alimentation enfoncé + le volume...

4  Serrure à motif de balayage oublié pour Nexus 6P (mais fonctionne d'empreinte digitale!)  ( Forgotten swipe pattern lock for nexus 6p but fingerprint works ) 
J'ai un Google Nexus 6P avec Copperhead OS installé dessus. J'ai oublié le motif de déverrouiller l'écran. Y a-t-il une façon que je puisse récupérer (une par...

0  Messages bloqués dans la zone de notification  ( Messages stuck in notification area ) 
J'ai un Samsung J3 exécutant Android 7. J'ai reçu 2 notifications qui semblent être bloquées dans la zone de notification, aucun moyen de s'en débarrasser. L'...

0  Mon Nexus 6P continue de tourner lorsqu'il est connecté au wifi ou à des données cellulaires  ( My nexus 6p keeps turning of when connected to wifi or cellular data ) 
J'ai 5 mois Nexus 6P et chaque fois que j'allume WiFi ou des données cellulaires, il se redémarre. Cela fonctionne parfaitement bien s'il n'est pas connecté. ...

1  Une application mise en place de ma barre d'état auto-masquer et transparent. Comment réparer? (Nova, UI système)  ( An app put made my status bar auto hide and transparent how to fix nova syst ) 
Ce que j'ai essayé: désinstallez l'application (poche noire) et redémarrez. Aussi essayé: Google. Tous les résultats de la recherche me disent comment cache...

4  Impossible de se connecter au wifi en utilisant nougat  ( Cant connect to wifi using nougat ) 
J'ai mis à jour à Nougat sur mon Nexus 5x. Vous ne pouvez pas sembler se connecter à certains réseaux WiFi, car le bouton Connect reste grisé après avoir sais...

1  Nexus 6P - Correction de "No Commande" avec un bouton de volume cassé  ( Nexus 6p fix no command with a broken volume button ) 
Alors, j'ai brisé mon bouton de volume. Et mon téléphone est entré dans un mode "No Commande" qui ne me permet pas de tourner mon téléphone. Étant donné que...




© 2022 www.demandez.top All Rights Reserved. Questions et réponses Accueil Tous les droits sont réservés