Database Develop

[Q] Specific RUU

Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte

Linte said:
Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte
Click to expand...
Click to collapse
There is a Guru reset here
http://www.htc1guru.com/downloads/stock-rom-downloads/
Read the instructions on how to flash
http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Sent from my HTC One using Xparent Skyblue Tapatalk 2

Thanks for the fast reply.
The problem is: I cannot get into recovery. I tried to flash the the recovery and the boot via fastboot from the corrospending
Guru, but I'll only get an "signature verify fail" error. I hoped for the fitting RUU- version for my 1.29.111.16, because it seems
to me that it may be the easiest solution for my problem.
Greetings,
Linte

Hi. Can you post your actual command and output?

SaHiLzZ said:
Hi. Can you post your actual command and output?
Click to expand...
Click to collapse
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adb>fastboot flash recovery rec.zip
error: cannot open 'rec.zip'
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.062s
C:\adb>fastboot flash rom Guru.zip
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4D.14.3250.26
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.111.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4252mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
C:\adb>
Click to expand...
Click to collapse

First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.

Seanie280672 said:
First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.
Click to expand...
Click to collapse
Again sorry for the late reply, business struck again. :l
To your points: Already installed the latest HTC drivers from their homepage more than four times so far. Im pretty sure I have the latest version and after installing, I deinstalled the Sync Manager, like you told me to do. Still no changes.
I cannot see any developer options, simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Also I got the latest fastboot and adb from the (SDK- Manager) Android Developer Tools- Bundle. That's why I am so clueless about my phone not getting recognized by my PC with "adb devices". Strange thing is, I get the ID of my phone in "fastboot devices"...
Later this da I will try to connect my phone to my new, clean Laptop, with the lastest HTC Drivers and adb/fastboot. Maybe this will help.
Thanks so far!
Linte
Edit: tried it with a clean Laptop, latest ADB, latest HTC Sync (installed and deinstalled) and different USB- slots. No success. Adb sill only says
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
Absoluteley no clue where I go wrong here... :l

Linte said:
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
Click to expand...
Click to collapse
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2

bored_stupid said:
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Hmm...nope. So far I have only used Windows 7. But like I said, no progress at all. Everythings updated, even on a freshly installed system. Different USB- Ports and so on. No success... :l

Tried to get S-OFF and use another RUU
Click to expand...
Click to collapse
You need a working rom to s-off the phone.
simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Click to expand...
Click to collapse
Linte said:
Code:
C:\adb>[B][COLOR="Red"]adb devices[/COLOR][/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
ADB commands only works from a booted OS with usb debugging ON or from custom recovery. So ADB will never output your device is connected if you are not in the OS or in custom recovery. From bootloader, use FASTBOOT commands
i.e:
Code:
fastboot devices
Code:
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED[B][COLOR="Red"] (remote: signature verify fail)[/COLOR][/B]
finished. total time: 2.062s
Click to expand...
Click to collapse
Looks like your bootloader is locked, you need an unlocked bootloader to flash the recovery partition
Code:
[COLOR="Red"][B]C:\adb>fastboot flash rom Guru.zip[/B][/COLOR]
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
This one is a custom rom (reset rom). You can't flash custom rom from fastboot. You can only flash custom rom from custom recovery.
from fastboot, all you can do is
flashing a custom recovery (with bootloader unlocked)
flashing a RUU.zip in ruu mode
flashing a firmware.zip in ruu mode
all roms (except RUUs) are flashed from custom recovery, including guru reset roms.
btw, there is no RUU for your phone.
unlock bootloader
flash twrp recovery 2.6.3.3
download and save this file to the same folder you have adb and fastboot in
open a cmd prompt from you fastboot/adb folder and boot your phone in bootloader mode (fastboot usb)
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb push the guru reset rom to your /sdcard/ from twrp recovery
download this guru reset rom: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/ and save it to your adb/fastboot folder
boot phone in twrp recovery
open a cmd prompt form your adb/fastboot folder
Code:
adb push guru_reset_m7_2.24.111.3.zip /sdcard/
wait for the file to transfer (5-10 min, there is no progress bar, just wait until adb says it complete)
install the reset rom using twrp

Wow! Thanks a lot!
After unlocking my bootloader again I was able to get into recovery. From there it was easy going to install the Guru.zip via sideload ("Install zip" didnt work for some reason, said something similiar to "Couldn't mount /sdcard/". But sideload worked fine.). Updated everything and my phone runs now like it always had!
Again: really, really thanks a bunch! Thought I somehow ruined my phone, but thanks to you all I got it done. I really appreciate your effort in helping me! You guys are awesome.
Greetings,
Linte
PS: I won't do anything stupid with my phone again, learnd this the hard way.

I need advanced help: Problem with XT1068 bootloader. Read in detail the problem pls.

Thanks for your time trying to help me, I REALLY appreciate that​Well, before telling you the problem, here is my device info:
- Moto G 2nd GEN XT1068
- I was in Android 5.0.2 Stock
- Bootloader version 48.83(*)
- CID: 0x000C​The problem: A few days ago, with no reason (haven´t modified NOTHING at all), I turned on my device but it booted in bootloader mode... strange... so I just selected 'Normal powerup', after some seconds in the boot logo, it return to bootloader mode... always!.
Anyway, I siad: I just have to restore my firmware. Problem > I had not unlocked my device´s bootloader. Ok, I am just going to unlock (the same way as always) but, sometimes, when I enter this command mfastboot oem get_unlock_data I get this:
Code:
C:\Users\SebastianD\Desktop>mfastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 5.008s
After many attempts I got my unlock data, then I did what I had to do: I went to Motorola Unlocking Website, entered my string, the code was sent to my e-mail (I did it with 2 e-mail accounts and got the same code), BUT! when I use the command mfastboot oem unlock UNIQUE_KEY I get, ALWAYS, this:
Code:
C:\Users\SebastianD\Desktop>mfastboot oem unlock [my_unlock_code]
...
(bootloader) Unlock code = [my_unlock_code]
(bootloader) unlock data invalid!
FAILED (remote failure)
finished. total time: 9.984s
I talked to Motorola service, but they say they do not have support for this because of their terms and stuff about the bootloader unlocking.
If you are more comfortable with spanish, here you can help me: LINK: Spanish Thread
This is freaking me out! I need help!​

Reserved: To post the solution... if I get a solution.

Reserved: Just in case to provide more information to solve the problem.

Wrong sub forum
Sent from my Moto G 2014 using Tapatalk

Vidhanth said:
Wrong sub forum
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
+1 
 @sebastiandg7 http://forum.xda-developers.com/moto-g-2014/help

I'm even friends with problem XT1068, does not generate the code to unlock only fault as shown below: Unit turns on shortly after return to the screen in AP Fastboot Flash
D:\android-sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 5.027s

I don't know why you have 'm' in front of 'fastboot oem get_unlock_data', anyway the instructions on this page are what I followed.
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728

Broke the Bootloader???

Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.

Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!

5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?

bootloader is locked correct?

SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.

Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry

5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.

Try: fastboot getvar all
Paste the result. Just hide you imei...

5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse

I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????

coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.

the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335

coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks

Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot

the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.

Damn... Try:
fastboot erase cache
And try to boot in twrp again?

5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!

Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?

"FAILED (remote: unknown command)" trying to unlock bootloader

Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.

I'd double check that Allow OEM Unlock in dev options is actually on

ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!

Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.

H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?

Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.

PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.

It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.

hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on

Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing

renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same

Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.

I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.

its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"

Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data

I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.

gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?

WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.

gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.

Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me

Can't unlock the bootloader for "Lake?"

I have done this so many times before without running into this problem. I enabled OEM unlocking through developer options and enabled USB debugging. I use CMD on Windows 10 as "PowerShell" confuses me and won't run "fastboot" commands at all.
I have entered the standard "fastboot oem get_unlock_data" command and the entire command prompt just sits there not doing anything or giving me the code. I have the Motorola G7+ "LAKE" international version which came in spanish/brazil.
My Motorola G6 had no problem with this yet here I am stuck not able to ask the phone to give me the unlock data. Please help me as I have never ran into this problem before so maybe it is a Windows 10 thing?
All the things I have done in an attempt to get this command to output the unlocking data string:
1)Yes, I have enabled OEM unlocking, developer settings as well as USB debugging.
2) Yes, I tried using CMD and the newer POWERSHELL -> Which seems to force me to use "./fastboot" because "fastboot is not recognized without adding the ./ infront of the fastboot command.
3) Yes, I have tried running CMD "as an administrator" which did not work and after entering the unlock code command just hangs on command.
4) Yes, I have tried rebooting the phone, turning those developer settings on/off multiple times.
5) Yes, "Fastboot Devices" does register my phone as actively connected.
6) Yes, the bootloader Log shows that I attempted to use the "Fastboot oem get_unlock_data" command yet nothing happens despite multiple entries in the bootloader log.
7) Yes, I have the proper drivers installed since the device is recognized by Fastboot & ADB.
I honestly have no idea what is making the command prompt hang instead of outputting the get_unlock_data response.
Additional Note:
This is the console output when using the Minimal ADB & Fastboot I downloaded in addition to the "Platform-Tools" folder I placed on C:/platform-tools/
Microsoft Windows [Version 10.0.19041.508]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY226TDKCT fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-suffi: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem help
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse

AndroidGeekCA said:
I have done this so many times before without running into this problem. I enabled OEM unlocking through developer options and enabled USB debugging. I use CMD on Windows 10 as "PowerShell" confuses me and won't run "fastboot" commands at all.
I have entered the standard "fastboot oem get_unlock_data" command and the entire command prompt just sits there not doing anything or giving me the code. I have the Motorola G7+ "LAKE" international version which came in spanish/brazil.
My Motorola G6 had no problem with this yet here I am stuck not able to ask the phone to give me the unlock data. Please help me as I have never ran into this problem before so maybe it is a Windows 10 thing?
All the things I have done in an attempt to get this command to output the unlocking data string:
1)Yes, I have enabled OEM unlocking, developer settings as well as USB debugging.
2) Yes, I tried using CMD and the newer POWERSHELL -> Which seems to force me to use "./fastboot" because "fastboot is not recognized without adding the ./ infront of the fastboot command.
3) Yes, I have tried running CMD "as an administrator" which did not work and after entering the unlock code command just hangs on command.
4) Yes, I have tried rebooting the phone, turning those developer settings on/off multiple times.
5) Yes, "Fastboot Devices" does register my phone as actively connected.
6) Yes, the bootloader Log shows that I attempted to use the "Fastboot oem get_unlock_data" command yet nothing happens despite multiple entries in the bootloader log.
7) Yes, I have the proper drivers installed since the device is recognized by Fastboot & ADB.
I honestly have no idea what is making the command prompt hang instead of outputting the get_unlock_data response.
Additional Note:
This is the console output when using the Minimal ADB & Fastboot I downloaded in addition to the "Platform-Tools" folder I placed on C:/platform-tools/
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Thank you for responding. I appreciate it.
I don't understand what that command did with my phone because it only showed one line about "unlock-data."
Note: When using "Mininmal ADB and Fastboot" the result is nothing happens when using "fastboot getvar all" It just sits there dead in the water. I also tried running it again w/o admin on CMD and it does nothing at all.
The model number is (Lake)XT1965-2 64GB PVT.
This is the output when using CMD(As Admin):
Code:
Microsoft Windows [Version 10.0.19041.508]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:/platform-tools/
C:\platform-tools>fastboot getvar all
(bootloader) Unlock data:

AndroidGeekCA said:
What does getvar all say?
Thank you for responding. I appreciate it.
I don't understand what that command did with my phone because it only showed one line about "unlock-data."
Note: When using "Mininmal ADB and Fastboot" the result is nothing happens when using "fastboot getvar all" It just sits there dead in the water :/
This is the output when using CMD(As Admin):
Click to expand...
Click to collapse
There are some examples of what getvar all should show in my thread.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs

sd_shadow said:
There are some examples of what getvar all should show in my thread.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Then why would my device just be sitting there looking like a moron whenever I run these commands? It's bought from Amazon but is NOT an "Amazon Branded Device." It actually came in Brazillan/Spanish packaging. I got the exact same item when I bought my G6 from the same place on Amazon.
I cannot figure out why this device doesn't want to run these commands or why it just sits there looking stupid....
Is my device just broken or something?
I added a picture of my powershell trying to use the right commands. it is attached to this thread.
Update: getvar all worked finally![/B] The problem is now it doesn't work again. It only worked once and now when I try again it just sits there -.- so I don't get why it works one time but not again...
Code:
PS C:\platform-tools> ./fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200728
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY226TDKCT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 2967F2D2
And when I finally got it to run a second time using "mfastboto" and CMD this is all it sent. It's like it inst running the commands properly...
Code:
C:\mfastboot>mfastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200728
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY226TDKCT
This is the link to the product I purchased: https://www.amazon.ca/Motorola-Unlo...ywords=Motorola+g7+plus&qid=1602083208&sr=8-5

AndroidGeekCA said:
Then why would my device just be sitting there looking like a moron whenever I run these commands? It's bought from Amazon but is NOT an "Amazon Branded Device." It actually came in Brazillan/Spanish packaging. I got the exact same item when I bought my G6 from the same place on Amazon.
I cannot figure out why this device doesn't want to run these commands or why it just sits there looking stupid....
Is my device just broken or something?
I added a picture of my powershell trying to use the right commands. it is attached to this thread.
Update: getvar all worked finally![/B] The problem is now it doesn't work again. It only worked once and now when I try again it just sits there -.- so I don't get why it works one time but not again...
And when I finally got it to run a second time using "mfastboto" and CMD this is all it sent. It's like it inst running the commands properly...
This is the link to the product I purchased: https://www.amazon.ca/Motorola-Unlo...ywords=Motorola+g7+plus&qid=1602083208&sr=8-5
Click to expand...
Click to collapse
You could try reflashing firmware with LMSA
See link in my thread.
Sent from my payton_sprout using XDA Labs

sd_shadow said:
You could try reflashing firmware with LMSA
See link in my thread.
Sent from my payton_sprout using XDA Labs
Click to expand...
Click to collapse
I did not find that folder on my computer. Why would the firmware have a problem when this phone is retail? I am bout ready to just give up and accept that I will be stuck with a locked bootloader. Is there any other reason this would be happen? Such as having Windows 10? I tried hooking up my old computer but it's a nightmare to get working.
Factory reset did not work. Still the same problems. I guess I just have to accept that I bought a phone that cannot unlock bootloader even though I skipped getting the G8+ ONLY BECAUSE G7+ HAD ROMS....
I have never seen this kind of problem before and would love to see if Windows 10 is the problem but I don't have another computer to test it on so....
Update: I just checked the CID given by my phone when getvar worked and it is indeed "unlockable" according to Motorola:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
My CID was 0x0032 which is on the left hand side claiming it can be done.
I really have no idea why this is happening other than it's a Windows 10 problem or that my android updated all the way from 9.0 to 10.0 the moment I got it(through a number of updates.)

AndroidGeekCA said:
I did not find that folder on my computer. .)
Click to expand...
Click to collapse
Just let LMSA flash firmware.
Sent from my payton_sprout using XDA Labs

sd_shadow said:
Just let LMSA flash firmware.
Sent from my payton_sprout using XDA Labs
Click to expand...
Click to collapse
Downloaded LSMA. There must be a major problem because the app tells me this:
"Unable to match the appropriate firmware. Some key information cannot be read from the device."
I am figuring that this is confirmation that someone ****ed this phone's firmware up from the manufacturer or something?
I am trying to force it to use the firrmware I think it needs as my getvar returned "RETLA" as software channel.
What a mess I have never seen this much difficulty in a simple bootloader unlock....I addd a picture of the app screen to attachments.
Update: From what I can see it is now downloading my current firmware. The problem is I noticed the software chanell "RETLA" listed on the phone's hardware information. It looks like it is trying to use the "RETAIL" firmware for some reason whereas I can download the RETLA. So, which one should I be using? The same exact one as on the phone now OR the RETLA downloaded from the mirrorsite from your thread?
I am trying to rescue it now but it is stuck at 41% after it rebooted to fastboot mode.. I upkoaded an image of that as well.

AndroidGeekCA said:
Downloaded LSMA. There must be a major problem because the app tells me this:
"Unable to match the appropriate firmware. Some key information cannot be read from the device."
I am figuring that this is confirmation that someone ****ed this phone's firmware up from the manufacturer or something?
I am trying to force it to use the firrmware I think it needs as my getvar returned "RETLA" as software channel.
What a mess I have never seen this much difficulty in a simple bootloader unlock....I addd a picture of the app screen to attachments.
Click to expand...
Click to collapse
My guess is the android 10 update fail to flash the bootloader correct, I don't know if there is a fix.
You could try flashing firmware with RSD Lite but you will need a Windows 7 pc.
You could try a usb bootable Linux system.
You tried different usb ports and cables?
Sent from my payton_sprout using XDA Labs

sd_shadow said:
My guess is the android 10 update fail to flash the bootloader correct, I don't know if there is a fix.
Click to expand...
Click to collapse
;
UPDATE: I tried fastboot using Fedora Live with the same result. I tried different ports and cables. I fear that what you said must be true or there is some other software/hardware problem. I am honestly very disappointed because it looks like I am locked out of custom flashing completly as well as having to resetup my phone since factory reset didnt help.
If you know anyone who has a similar problem, or someone who could look into this regarding a fix I would appreciate it. Thank you for your help so much. I will still eventually load win7 on my old computer and try but using virtualbox I couldnt get it to accept fastboot devices. Who knows. This sucks very very hard.
You could try flashing firmware with RSD Lite but you will need a Windows 7 pc.
You could try a usb bootable Linux system.
You tried different usb ports and cables?
Sent from my payton_sprout using XDA Labs[/QUOTE]
Could I not just try flashing the bootloader myself using CMD or PowerShell?
I have a second computer but it has to use a HDD I have literally outside the case. I would also need to get Win7 unto a USB. I do have Fedora on USB.
What would I need if I used Fedora bootable usb? How would I flash the bootloader using bootable linux?
Also: Could I use VirtualBox to run win7 for this purpose? rather than another computer?
By the way the version of BL on my fastboot screen is: MBM-3.0-lake_retail-38523c9489-200728 while the firmware that the LMSA downloaded is MBM Version: MBM-3.0-lake_retail-efaf0cccb-200728
Here is the whole information from the firmware file. This firmware looks like it might be the right one considering that it says my model name properly and such and the QPWSxxxxxx is identical to what is there now.
When my phone booted for the first time I was on 9,0 and then the phone updated at least like 7 times until it reached 10.0 and I had not tried to unlock bootloader before than.
Code:
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-14 a5a6c release-keysM636_13.45.02.60R
Modem Version: M636_13.45.02.60R
FSG Version: FSG-660-10.98
MBM Version: MBM-3.0-lake_retail-efaf0cccb-200728
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-14/a5a6c:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.201.22.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPWS30.61-21-14
SW Display Build ID: QPWS30.61-21-14
Build Date: Tue Jul 28 06:56:18 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_xt1965_2_sutel_ds.png
Blur Version: Blur_Version.30.201.22.lake.retail.en.US
Version when read from CPV: lake-user 10 QPWS30.61-21-14 a5a6c release-keys

AndroidGeekCA said:
Could I not just try flashing the bootloader myself using CMD or PowerShell?
I have a second computer but it has to use a HDD I have literally outside the case. I would also need to get Win7 unto a USB. I do have Fedora on USB.
What would I need if I used Fedora bootable usb? How would I flash the bootloader using bootable linux?
Also: Could I use VirtualBox to run win7 for this purpose? rather than another computer?
By the way the version of BL on my fastboot screen is: MBM-3.0-lake_retail-38523c9489-200728 while the firmware that the LMSA downloaded is MBM Version: MBM-3.0-lake_retail-efaf0cccb-200728
Here is the whole information from the firmware file. This firmware looks like it might be the right one considering that it says my model name properly and such and the QPWSxxxxxx is identical to what is there now.
When my phone booted for the first time I was on 9,0 and then the phone updated at least like 7 times until it reached 10.0 and I had not tried to unlock bootloader before than.
Click to expand...
Click to collapse
I would think the firmware file name should look like this
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/
XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip
You can try flashing firmware with fastboot.exe or mfastboot but it seems like trying to manually flash newer moto devices with a locked bootloader just results in errors.
In Settings/about phone/model and hardware
Does it say ?
Model number (sku):XT-1965-2
And you found the software channel in ?
Settings/ about phone
Sent from my payton_sprout using XDA Labs

sd_shadow said:
I would think the firmware file name should look like this
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/
XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip
You can try flashing firmware with fastboot.exe or mfastboot but it seems like trying to manually flash newer moto devices with a locked bootloader just results in errors.
In Settings/about phone/model and hardware
Does it say ?
Model number (sku):XT-1965-2
And you found the software channel in ?
Settings/ about phone
Sent from my payton_sprout using XDA Labs
Click to expand...
Click to collapse
Yes, I found the software channel in the About section. Yes, the model number indeed says the correct model number(xt1965-2.) Everything seems like it is set properly but it just doesnt work. I guess I will attempt to flash the bootloader from the RETLA package.

AndroidGeekCA said:
Yes, I found the software channel in the About section. Yes, the model number indeed says the correct model number(xt1965-2.) Everything seems like it is set properly but it just doesnt work. I guess I will attempt to flash the bootloader from the RETLA package.
Click to expand...
Click to collapse
Try using this first before flash firmware with locked bootloader.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot reboot
Then flash normally
When done use
Code:
fastboot oem fb_mode_clear
Sent from my payton_sprout using XDA Labs

AndroidGeekCA said:
I have done this so many times before without running into this problem. I enabled OEM unlocking through developer options and enabled USB debugging. I use CMD on Windows 10 as "PowerShell" confuses me and won't run "fastboot" commands at all.
I have entered the standard "fastboot oem get_unlock_data" command and the entire command prompt just sits there not doing anything or giving me the code. I have the Motorola G7+ "LAKE" international version which came in spanish/brazil.
My Motorola G6 had no problem with this yet here I am stuck not able to ask the phone to give me the unlock data. Please help me as I have never ran into this problem before so maybe it is a Windows 10 thing?
All the things I have done in an attempt to get this command to output the unlocking data string:
1)Yes, I have enabled OEM unlocking, developer settings as well as USB debugging.
2) Yes, I tried using CMD and the newer POWERSHELL -> Which seems to force me to use "./fastboot" because "fastboot is not recognized without adding the ./ infront of the fastboot command.
3) Yes, I have tried running CMD "as an administrator" which did not work and after entering the unlock code command just hangs on command.
4) Yes, I have tried rebooting the phone, turning those developer settings on/off multiple times.
5) Yes, "Fastboot Devices" does register my phone as actively connected.
6) Yes, the bootloader Log shows that I attempted to use the "Fastboot oem get_unlock_data" command yet nothing happens despite multiple entries in the bootloader log.
7) Yes, I have the proper drivers installed since the device is recognized by Fastboot & ADB.
I honestly have no idea what is making the command prompt hang instead of outputting the get_unlock_data response.
Additional Note:
This is the console output when using the Minimal ADB & Fastboot I downloaded in addition to the "Platform-Tools" folder I placed on C:/platform-tools/
Click to expand...
Click to collapse
Hello,
same problem here, with my moto g7 plus,
fastboot is showing the device, but the phone does not respond on any command like getvar, oem, and so on (but reboot works).
For me, it seems the phone does not like the usb ports on my lenovo-laptop (running with mint 20).
So I connected the phone to my Raspi.
At the Raspi, the phone responded to any fastboot command and i was able to get the unlock data.
But my Moto G5 and Mi A1 are working fine with my laptop and fastboot. Strange !?!

waldbox said:
Hello,
same problem here, with my moto g7 plus,
fastboot is showing the device, but the phone does not respond on any command like getvar, oem, and so on (but reboot works).
For me, it seems the phone does not like the usb ports on my lenovo-laptop (running with mint 20).
So I connected the phone to my Raspi.
At the Raspi, the phone responded to any fastboot command and i was able to get the unlock data.
But my Moto G5 and Mi A1 are working fine with my laptop and fastboot. Strange !?!
Click to expand...
Click to collapse
I found if you are running other terminals besides cmd prompt in windows such as ubuntu or powershell there is a cache file that records device info and connections to usbs which basicallly its just a log but when you get about 50 or so different flashes it slows the processes down.... i sat idle on ubuntu waiting on fastboot get vars to respond 8 mins... also if web browser open at same time there maybe security command preventing

For this problem, it also confused me for a long time.
The solution is very simple, change to another computer!
when i move from DELL G7 to Tower 5810, it ok!

youzi0335 said:
For this problem, it also confused me for a long time.
The solution is very simple, change to another computer!
when i move from DELL G7 to Tower 5810, it ok!
Click to expand...
Click to collapse
Really? I suppose I could give this a go since I am out of ideas and gave up until recently. I have now decided to try and get ths done now that it has finished a couple of security updates. Someone mentioned an update may have failed to complete correctly so now that it has updated twice maybe that problem is gone.
UPDATE: Here is where I am at and where I need help. I am prepared to attempt to reflash the stock rom's bootloader.img as I think someone mentioned that I should try doing that incase the bootloader is ****ed.
The current build version/number/ID is: QPWS30.61-21-18-7
That build number does not seem to match any of the firmware files I find through a google search. Why is it? The closest I can find appears to a Brazillian rom??
I have gotten so confused at this point with these different build numbers and firmware files. Which firmware file should I be using? Does it matter if it is an older build number?
I am ready to attempt flashing the bootloader.img but want to make sure I am using the correct firmware.

I am having the exact same problem. I purchased a Moto G7 plus (XT1965-T) from amazon a month ago and went through the process (documenting my actual steps taken in exact detail) to install Lineage. I had no issues. I ordered a second exact same phone and started the process. When I get to the fastboot oem get_unlock_data nothing happens. Just nothing. The previous commands worked just fine (adb reboot bootloader and fastboot devices). I am using the same computer I used last time. Just to confirm I am issuing the fastboot oem get_unlock_data when the phone is showing the bootloader screen (after issuing adb reboot bootloader). One interesting thing I noticed though on this screen is the the fine print on the phone actually says 'oem locked' even thought I definitely have it unlocked via the developer options. I wonder if that is indicating a problem of some sort?
Anyways, have you found a solution for yourself? I am getting very frustrated as well given that I was able to do this a month ago.

I just got my problem resolved. I switched where my usb cable was plugged into my laptop. I did have it plugged in at the side (and actually tried 2 outlets there) which did not work. As soon as I plugged my usb cable into the back of my laptop it worked. Perhaps you could try the same. I have been trying get this working for hours and now it was as simple as plugging in elsewhere. I hope this helps you find a solution for yourself.