Il Forum è consultabile solo in modalità lettura. Per domande o consigli iscriviti al nostro GRUPPO FACEBOOK / COMMUNITY cliccando qui

[RISOLTO] LG G2 bloccato!!! (va in recovery e download mode ma non si accende)

Discussione in 'Modding LG G2' iniziata da iuhgfdwqz, 29 Lug 2014.

  1. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    l'installazione dei driver di per se va a buon fine ma appena collego il telefono non me lo riconosce come lg g2 :(
     
  2. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Questo sia in download mode che in recovery?
     
  3. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    in download mode non lo rileva proprio... in recovery lo rileva ma non lo riconosce :'(
     
  4. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Hai riprovato con i comandi adb da recovery? Hai anche provato a vedere se Ubuntu lo rileva in recovery?
     
  5. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
  6. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
  7. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    ora ubuntu con i comandi adb mi trovato il telefono, qual'è il comando per spostare la rom da installare?? (dovrebbe essere adb push ma non ho capito il funzionamento: come fa a sapere quale file mettere sul telefono??)
     
  8. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Scarichi una rom qualsiasi, la posizioni sul desktop poi digiti:
    adb push file percorsofile
    Al posto di percorsofile inserisci il percorso della rom =)
     
  9. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    nel mio caso sarebbe: adb push file /home/ubuntu/Desktop/CloudyG3_1.2.zip
    giusto??

    Cmq con quel comando il terminare mi risponde con: error:closed
     
  10. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Sì, ma ho dimenticato un pezzo, ci vanno i :
    Quindi il comando è: adb push file: /home/ubuntu/Desktop/CloudyG3_1.2.zip
     
  11. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    Sempre error: closed
     
  12. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Puoi farmi uno screen del terminale?

    Prova con adb push file: /home/ubuntu/Desktop/CloudyG3_1.2.zip: /sdcard/
     
    Ultima modifica: 30 Lug 2014
  13. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    allora: con la prima versione del comando succede questo: https://imageshack.com/i/pdQlI6Eij

    invece con adb push file: /home/ubuntu/Desktop/CloudyG3_1.2.zip: /sdcard/ ho 3/4 pagine di terminale in risposta...

    ECCOLE:
    ubuntu@ubuntu:~$ adb push file: /home/ubuntu/Desktop/CloudyG3_1.2.zip: /sdcard/
    Android Debug Bridge version 1.0.31

    -a - directs adb to listen on all interfaces for a connection
    -d - directs command to the only connected USB device
    returns an error if more than one USB device is present.
    -e - directs command to the only running emulator.
    returns an error if more than one emulator is running.
    -s <specific device> - directs command to the device or emulator with the given
    serial number or qualifier. Overrides ANDROID_SERIAL
    environment variable.
    -p <product name or path> - simple product name like 'sooner', or
    a relative/absolute path to a product
    out directory like 'out/target/product/sooner'.
    If -p is not specified, the ANDROID_PRODUCT_OUT
    environment variable is used, which must
    be an absolute path.
    -H - Name of adb server host (default: localhost)
    -P - Port of adb server (default: 5037)
    devices [-l] - list all connected devices
    ('-l' will also list device qualifiers)
    connect <host>[:<port>] - connect to a device via TCP/IP
    Port 5555 is used by default if no port number is specified.
    disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
    Port 5555 is used by default if no port number is specified.
    Using this command with no additional arguments
    will disconnect from all connected TCP/IP devices.

    device commands:
    adb push <local> <remote> - copy file/dir to device
    adb pull <remote> [<local>] - copy file/dir from device
    adb sync [ <directory> ] - copy host->device only if changed
    (-l means list but don't copy)
    (see 'adb help all')
    adb shell - run remote shell interactively
    adb shell <command> - run remote shell command
    adb emu <command> - run emulator console command
    adb logcat [ <filter-spec> ] - View device log
    adb forward --list - list all forward socket connections.
    the format is a list of lines with the following format:
    <serial> " " <local> " " <remote> "\n"
    adb forward <local> <remote> - forward socket connections
    forward specs are one of:
    tcp:<port>
    localabstract:<unix domain socket name>
    localreserved:<unix domain socket name>
    localfilesystem:<unix domain socket name>
    dev:<character device name>
    jdwp:<process pid> (remote only)
    adb forward --no-rebind <local> <remote>
    - same as 'adb forward <local> <remote>' but fails
    if <local> is already forwarded
    adb forward --remove <local> - remove a specific forward socket connection
    adb forward --remove-all - remove all forward socket connections
    adb jdwp - list PIDs of processes hosting a JDWP transport
    adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
    - push this package file to the device and install it
    ('-l' means forward-lock the app)
    ('-r' means reinstall the app, keeping its data)
    ('-s' means install on SD card instead of internal storage)
    ('--algo', '--key', and '--iv' mean the file is encrypted already)
    adb uninstall [-k] <package> - remove this app package from the device
    ('-k' means keep the data and cache directories)
    adb bugreport - return all information from the device
    that should be included in a bug report.

    adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
    - write an archive of the device's data to <file>.
    If no -f option is supplied then the data is written
    to "backup.ab" in the current directory.
    (-apk|-noapk enable/disable backup of the .apks themselves
    in the archive; the default is noapk.)
    (-shared|-noshared enable/disable backup of the device's
    shared storage / SD card contents; the default is noshared.)
    (-all means to back up all installed applications)
    (-system|-nosystem toggles whether -all automatically includes
    system applications; the default is to include system apps)
    (<packages...> is the list of applications to be backed up. If
    the -all or -shared flags are passed, then the package
    list is optional. Applications explicitly given on the
    command line will be included even if -nosystem would
    ordinarily cause them to be omitted.)

    adb restore <file> - restore device contents from the <file> backup archive

    adb help - show this help message
    adb version - show version num

    scripting:
    adb wait-for-device - block until device is online
    adb start-server - ensure that there is a server running
    adb kill-server - kill the server if it is running
    adb get-state - prints: offline | bootloader | device
    adb get-serialno - prints: <serial-number>
    adb get-devpath - prints: <device-path>
    adb status-window - continuously print device status for a specified device
    adb remount - remounts the /system partition on the device read-write
    adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
    adb reboot-bootloader - reboots the device into the bootloader
    adb root - restarts the adbd daemon with root permissions
    adb usb - restarts the adbd daemon listening on USB
    adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
    networking:
    adb ppp <tty> [parameters] - Run PPP over USB.
    Note: you should not automatically start a PPP connection.
    <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
    [parameters] - Eg. defaultroute debug dump local notty usepeerdns

    adb sync notes: adb sync [ <directory> ]
    <localdir> can be interpreted in several ways:

    - If <directory> is not specified, both /system and /data partitions will be updated.

    - If it is "system" or "data", only the corresponding partition
    is updated.

    environmental variables:
    ADB_TRACE - Print debug information. A comma separated list of the following values
    1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
    ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
    ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
     
  14. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Allora, prova con quest'altro comando:
    adb push /home/ubuntu/Desktop/CloudyG3_1.2.zip /sdcard/
     
  15. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    error closed... :'(
     
  16. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Allora prova i seguenti:
    adb push file /home/ubuntu/Desktop/CloudyG3_1.2.zip /sdcard
    adb push /home/ubuntu/Desktop/CloudyG3_1.2.zip /storage/sdcard0
    adb push file /home/ubuntu/Desktop/CloudyG3_1.2.zip /storage/sdcard0

    Se non funziona, va in recovery, fai install zip e dimmi se ci sono delle cartelle
     
  17. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    Allora: il secondo comando è l'unico che da error:closed mentre il primo e il terzo mi stampano pagine e pagine di righe (come se il comando non esiste e mi stampa il tutorial dei comandi adb)...
    SE vado su install nella recovery ho un sacco di cartelle: boot,cache,data,datadata,dev,emmc,etc,external_sh,internal_sh,license,proc,recovery,res,root,sbin,sd-ext,sdcard,selinux,supersu,sys,system,tmp (queste sono tutte le cartelle che ho in install)
     
  18. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Allora, proviamo così.
    Digita: cd /home/Ubuntu/Desktop/
    Poi digita: adb push CloudyG3_1.2.zip /sdcard/CloudyG3_1.2.zip
     
  19. iuhgfdwqz

    iuhgfdwqz Baby Droid

    Iscritto:
    14 Ott 2013
    Messaggi:
    40
    "Mi Piace":
    1
    mi sono posizionato nel desktop con cd ma il secondo comando da sempre error:closed
    Che scocciatura, ora che ubuntu me lo legge non riesco a mettere niente :'(
     
  20. Killua96

    Killua96 Power Droid

    Iscritto:
    16 Nov 2013
    Messaggi:
    10.666
    "Mi Piace":
    3.546
    Allora cerchiamo di risolvere quel problema dai i seguenti comandi uno alla volta in fila:
    1) adb usb
    2) adb devices
    3) adb kill-server
    4) adb start-server
    5) adb devices
    Poi riesegui:
    adb push CloudyG3_1.2.zip /sdcard/CloudyG3_1.2.zip