Mate 20 lite

[Assistenza68]

Ho un Mate 20 lite come nuovo, mia figlia non ricorda la sequenza blocco schermo e nemmeno account Google, volevo formattare ma al momento che devo digitare yes per confermare, la tastiera tach del telefono non risponde a nessuno tocco come posso risolvere non mi interessa se perdo tutti i dati. 

[admin]

@Assistenza68 Ciao e Benvenuto.

Ti scrivo qua sotto alcuni passaggi che forse non hai ancora tentato per il rispristino quando da dispositivo non si riesce.

1. Scarica ADB
   Vai su https://dl.google.com/android/repository/platform-tools-latest-windows.zip e scarica ADB (parte di Android SDK).
   Estrai la cartella ZIP in una posizione sul PC (es. C:\platform-tools).

2. Collega il telefono
   Collega il Huawei Mate 20 Lite al PC con USB.

3. Apri terminale
   Vai nella cartella estratta (platform-tools).
   Clic destro > "Apri nel terminale" (o PowerShell/CMD).

4. Verifica connessione
   Digita: adb devices e premi Invio.
   Deve apparire "List of devices attached" con l'ID del Mate 20 Lite (es. non "unauthorized"). Se no, prova altro cavo o riavvia ADB.

5. Entra in recovery
   Digita: adb reboot recovery e premi Invio.
   Il telefono entra in modalità recovery.

6. Esegui reset dalla recovery
   Nel menu recovery (naviga con Volume +/-, seleziona con Power):
   Seleziona "Wipe data/factory reset".
   Conferma "Yes".
   Al termine, seleziona "Reboot system now".

Il Mate 20 Lite si riavvia come nuovo. Almeno dovrebbe.
Facci sapere come va

[Assistenza68]

@admin
PS C:\Users\assistenza\Desktop\platform-tools-latest-windows\platform-tools> .\adb devices
List of devices attached

PS C:\Users\assistenza\Desktop\platform-tools-latest-windows\platform-tools>

ecco cosa mi dice quando digito adb device
list device attached non esce nulla ho provato anche a cambiare cavetto, comunque il telefono è acceso con blocco schermo sequenza che non ricordo, ho notato che è inserita modalita' aereo. il telefono deve essere spendo e con cavo inserito?

[Assistenza68]

@admin
( se digito solo adb ecco cosa mi dice.)
PS C:\Users\assistenza\Desktop\platform-tools-latest-windows\platform-tools> .\adb
Android Debug Bridge version 1.0.41
Version 36.0.2-14143358
Installed as C:\Users\assistenza\Desktop\platform-tools-latest-windows\platform-tools\adb.exe
Running on Windows 10.0.26200

global options:
-a listen on all network interfaces, not just localhost
-d use USB device (error if multiple devices connected)
-e use TCP/IP device (error if multiple TCP/IP devices available)
-s SERIAL use device with given serial (overrides $ANDROID_SERIAL)
-t ID use device with given transport id
-H name of adb server host [default=localhost]
-P port of adb server [default=5037]
-L SOCKET listen on given socket for adb server [default=tcp:localhost:5037]
--one-device SERIAL|USB only allowed with 'start-server' or 'server nodaemon', server will only connect to one USB device, specified by a serial number or USB device address.
--exit-on-write-error exit if stdout is closed

general commands:
devices [-l] list connected devices (-l for long output)
help show this help message
version show version num

networking:
connect HOST[:PORT] connect to a device via TCP/IP [default port=5555]
disconnect [HOST[:PORT]]
disconnect from given TCP/IP device [default port=5555], or all
pair HOST[:PORT] [PAIRING CODE]
pair with a device for secure TCP/IP communication
forward --list list all forward socket connections
forward [--no-rebind] LOCAL REMOTE
forward socket connection using:
tcp:<port> (<local> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
dev-raw:<character device name> (open device in raw mode)
jdwp:<process pid> (remote only)
vsock:<CID>:<port> (remote only)
acceptfd:<fd> (listen only)
forward --remove LOCAL remove specific forward socket connection
forward --remove-all remove all forward socket connections
reverse --list list all reverse socket connections from device
reverse [--no-rebind] REMOTE LOCAL
reverse socket connection using:
tcp:<port> (<remote> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
reverse --remove REMOTE remove specific reverse socket connection
reverse --remove-all remove all reverse socket connections from device
mdns check check if mdns discovery is available
mdns services list all discovered services

file transfer:
push [--sync] [-z ALGORITHM] [-Z] LOCAL... REMOTE
copy local files/directories to device
-n: dry run: push files to device without storing to the filesystem
-q: suppress progress messages
-Z: disable compression
-z: enable compression with a specified algorithm (any/none/brotli/lz4/zstd)
--sync: only push files that have different timestamps on the host than the device
pull [-a] [-z ALGORITHM] [-Z] REMOTE... LOCAL
copy files/dirs from device
-a: preserve file timestamp and mode
-q: suppress progress messages
-Z: disable compression
-z: enable compression with a specified algorithm (any/none/brotli/lz4/zstd)
sync [-l] [-z ALGORITHM] [-Z] [all|data|odm|oem|product|system|system_ext|vendor]
sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
-l: list files that would be copied, but don't copy them
-n: dry run: push files to device without storing to the filesystem
-q: suppress progress messages
-Z: disable compression
-z: enable compression with a specified algorithm (any/none/brotli/lz4/zstd)

shell:
shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...]
run remote shell command (interactive shell if no command given)
-e: choose escape character, or "none"; default '~'
-n: don't read from stdin
-T: disable pty allocation
-t: allocate a pty if on a tty (-tt: force pty allocation)
-x: disable remote exit codes and stdout/stderr separation
emu COMMAND run emulator console command

app installation (see also adb shell cmd package help
install [-lrtsdg] [--instant] PACKAGE
push a single package to the device and install it
install-multiple [-lrtsdpg] [--instant] PACKAGE...
push multiple APKs to the device for a single package and install them
install-multi-package [-lrtsdpg] [--instant] PACKAGE...
push one or more packages to the device and install them atomically
-r: replace existing application
-t: allow test packages
-d: allow version code downgrade (debuggable packages only)
-p: partial application install (install-multiple only)
-g: grant all runtime permissions
--abi ABI: override platform's default ABI
--instant: cause the app to be installed as an ephemeral install app
--no-streaming: always push APK to device and invoke Package Manager as separate steps
--streaming: force streaming APK directly into Package Manager
--fastdeploy: use fast deploy
--no-fastdeploy: prevent use of fast deploy
--force-agent: force update of deployment agent when using fast deploy
--date-check-agent: update deployment agent when local version is newer and using fast deploy
--version-check-agent: update deployment agent when local version has different version code and using fast deploy
(See also adb shell pm help for more options.)
uninstall [-k] PACKAGE
remove this app package from the device
'-k': keep the data and cache directories

debugging:
bugreport [PATH]
write bugreport to given PATH [default=bugreport.zip];
if PATH is a directory, the bug report is saved in that directory.
devices that don't support zipped bug reports output to stdout.
jdwp list pids of processes hosting a JDWP transport
logcat show device log (logcat --help for more)

security:
disable-verity disable dm-verity checking on userdebug builds
enable-verity re-enable dm-verity checking on userdebug builds
keygen FILE
generate adb public/private key; private key stored in FILE,

scripting:
wait-for[-TRANSPORT]-STATE...
wait for device to be in a given state
STATE: device, recovery, rescue, sideload, bootloader, or disconnect
TRANSPORT: usb, local, or any [default=any]
get-state print offline | bootloader | device
get-serialno print <serial-number>
get-devpath print <device-path>
remount [-R]
remount partitions read-write. if a reboot is required, -R will
will automatically reboot the device.
reboot [bootloader|recovery|sideload|sideload-auto-reboot]
reboot the device; defaults to booting system image but
supports bootloader and recovery too. sideload reboots
into recovery and automatically starts sideload mode,
sideload-auto-reboot is the same but reboots after sideloading.
sideload OTAPACKAGE sideload the given full OTA package
root restart adbd with root permissions
unroot restart adbd without root permissions
usb restart adbd listening on USB
tcpip PORT restart adbd listening on TCP on PORT

internal debugging:
start-server ensure that there is a server running
kill-server kill the server if it is running
reconnect kick connection from host side to force reconnect
reconnect device kick connection from device side to force reconnect
reconnect offline reset offline/unauthorized devices to force reconnect

usb:
attach attach a detached USB device
detach detach from a USB device to allow use by other processes
environment variables:
$ADB_TRACE
comma/space separated list of debug info to log:
all,adb,sockets,packets,rwx,usb,sync,sysdeps,transport,jdwp,services,auth,fdevent,shell,incremental
$ADB_VENDOR_KEYS colon-separated list of keys (files or directories)
$ANDROID_SERIAL serial number to connect to (see -s)
$ANDROID_LOG_TAGS tags to be used by logcat (see logcat --help)
$ADB_LOCAL_TRANSPORT_MAX_PORT max emulator scan port (default 5585, 16 emus)
$ADB_MDNS_AUTO_CONNECT comma-separated list of mdns services to allow auto-connect (default adb-tls-connect)

Online documentation: https://android.googlesource.com/platform/packages/modules/adb/+/refs/heads/main/docs/user/adb.1.md

PS C:\Users\assistenza\Desktop\platform-tools-latest-windows\platform-tools>

[admin]

e se digiti direttamente "adb reboot recovery"?
Emette qualche errore?

[Assistenza68]

@admin ha detto in Mate 20 lite:

reboot recovery

PS C:\Users\assistenza\Downloads\platform-tools-latest-windows\platform-tools> .\adb reboot recovery

• daemon not running; starting now at tcp:5037
• daemon started successfully
  error: no devices/emulators found
  PS C:\Users\assistenza\Downloads\platform-tools-latest-windows\platform-tools>

[kaffeine]

Ciao, in quello stato ADB probabilmente non può aiutarti: se il debug USB non era già attivo e autorizzato prima del blocco schermo, adb devices resta vuoto anche con cavo e driver corretti. Il telefono acceso ma bloccato non basta.

Io proverei prima solo le combinazioni fisiche per entrare in recovery/eRecovery Huawei e fare il wipe da lì, usando Volume/Power. Se neanche la tastiera/touch in recovery risponde, il problema è più basso livello e ADB non lo sblocca.

Qui ho riassunto anche la differenza pratica tra ADB, recovery, sideload e rollback: https://androidlab.it/android-17-qpr1-beta-3-pixel-installazione-rollback-guida-2026/