ADB + Fastboot Motorola moto E32 error - Android Q&A, Help & Troubleshooting

Commande d'erreur CMD.
$ Démarrage rapide oem_unlock_get_data
Failed (commend unlock cmd)
Mod translation:
CMD error command.
$ Quickstart oem_unlock_get_data
Failed (commend unlock cmd)

---

Le commande est:
Code:
fastboot oem get_unlock_data
Please stick to English. You've taxed my French capability inordinately.

---

enael said:
Mod translation:
CMD error command.
Click to expand...
Click to collapse
Greetings. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

---

that's what I did but I got errors yet I have the tool, SDK. the Motorola and Google usb oem driver.

---

enael said:
... I got errors ...
Click to expand...
Click to collapse
Code:
fastboot oem help
fastboot oem get_unlock_data

---

Code:
adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem get_unlock_data
...
FAILED (remote: unknown cmd.)
finished. total time: 0.016s
PS C:\Users\Enael\Desktop\adb+fastboot>

---

enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
How old is this device? What is it?

---

the device is released in 2022

---

And fastboot oem help
A quick Google shows:
Thanks for providing this. Upon checking, the device is not supported by this bootloader program.
Regards,
Jess
Motorola Support
Click to expand...
Click to collapse

---

PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem help
...
FAILED (remote: unknown cmd.)
finished. total time: 0.031s
PS C:\Users\Enael\Desktop\adb+fastboot>

---

enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
I guess that Motorola screwed you.
This is my Moto G Power (2021), not that much more pricey a Motorola.
Code:
C:\>fastboot oem help
(bootloader) config...
(bootloader) hw...
(bootloader) partition...
(bootloader) blankflash
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) bp-tools-on
(bootloader) bp-tools-off
(bootloader) qcom-on
(bootloader) qcom-off
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) cid_prov_req
(bootloader) off-mode-charge
(bootloader) read_sv
(bootloader) show_screen
OKAY [ 0.016s]
Finished. Total time: 0.016s

---

It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?

---

enael said:
It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools
It's good to update, but I don't think it will make a difference.
Fastboot does some filtering locally so that fastboot self-destruct doesn't go anywhere.
OTOH, fastboot oem self-destruct should be passed to a device (but probably won't do anything).

---

Spoiler
Code:
fastboot getvar all
(bootloader) frp-state: Protection
(bootloader) serialno: ZY32FTTJFM
(bootloader) secure: true
(bootloader) socidp2: d311d921e088b588bda2f11f7e42ce46
(bootloader) socidp1: e2f7cb94c69577917f8bf8468753667c
(bootloader) tokenp1: 5a5933324654544a464d000000000000
(bootloader) lcs: 5
(bootloader) max-download-size: 0x36000000
(bootloader) is-userspace: no
(bootloader) version: 1.0
(bootloader) battery-voltage: 3825
(bootloader) battid: SB18D34202
(bootloader) cpu: T606 AB
(bootloader) radio: EMEA
(bootloader) hwrev: PVT
(bootloader) ram: 4GB SAMSUNG LP4X M5-M8=01 08 00 12
(bootloader) ufs_sn: 0036003300370061003000390031003100380066003200380000
(bootloader) ufs: 64GB SAMSUNG KM5P9001DM-B424 FV=0300
(bootloader) storage-type: UFS
(bootloader) ufs_ffu.change_count: 0
(bootloader) ufs_ffu.vice_flash_retry_count: 0
(bootloader) ufs_ffu.vice_flash_fail_count: 0
(bootloader) ufs_ffu.vice_flash_count: 0
(bootloader) ufs_ffu.flash_retry_count: 0
(bootloader) ufs_ffu.flash_fail_count: 0
(bootloader) ufs_ffu.flash_count: 0
(bootloader) unlock_raw_data: c19012e8c1849b5bcd7088a7364fd182
(bootloader) sku: XT2227-2
(bootloader) build_type: user
(bootloader) product_model: Hawaii
(bootloader) product_name: hawaii
(bootloader) ro.build.version.incremental: 9fe5d
(bootloader) ro.carrier: reteu
(bootloader) imei2: 000000000000000
(bootloader) imei: 000000000000000
(bootloader) persist.radio.multisim.config: dsds
(bootloader) fingerprint(3):: s
(bootloader) fingerprint(2):: S31.335-20-2/9fe5d:user/release-key
(bootloader) fingerprint(1):: motorola/hawaii_reteu/hawaii:11/ROR
all: Done!!
Finished. Total time: 0.084s
Hello everyone, I finally managed to get the info from my phone but I see that the FRP protection is active, is that a problem?