Hi, I was trying to unlock the bootloader of my Moto Z3 play (xt1929-4). I had the latest adb and fastboot installd, latest drivers installed. Tried on different computer, linux and win with no success. Below is the error from a linux machine.
fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
And sometimes it says:
fastboot oem get_unlock_data
(bootloader) slot-countxes: not found
(bootloader) slo: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
Here is the getvar
fastboot getvar all
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Other than not being able to unlock bootloader, do not have any concerns with the device and works great. Any help is greatly appreciated.
same issue
have you been able to solve it?
Related
Hi frend.
What do I have!
HTC 626G is written in the phone and on the box.
HTC 626ph on the phone cover.
626G and 626ph = from one box at purchase
CPU MTK6592
Android 4.4.2
build 1.78.401.100 and 1.79.401.100
When you enter commands: fastboot
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar serialno
fastboot out: getvar:serialno FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar product
fastboot out: getvarroduct FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: getvar:modelid FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: getvar:cidnum FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar build-mode
fastboot out: getvar:build-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: getvar:boot-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar security
fastboot out: getvar:security FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: getvar:imei FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem get_identifier_token - error!
$ fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem unlock - error! Unlocked, perhaps?
$ fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7000
)
finished. total time: 110.541s
Click to expand...
Click to collapse
I made backups
Backup HTC 626G 1.79.401.100 (for SP Flash Tool)
Backup HTC 626G 1.78.401.100 (for SP Flash Tool)
Backup HTC 626G 1.72.401.101 (for SP Flash Tool)
Instructions such!
If their upload to the phone via SP_Flash_Tool_v5.1348.01_SEC + download_agent MTK_AllInOne_DA.bin, phone is loaded. but there is no picture on the display (LСD), only backlight.
I have even copied preloader! by command dd if=/dev/preloader of=/mnt/sdcard/preloader.bin count=262144 bs=1 When copying he 256 KB. STOCK 1.79-1.78 Preloader
if it is open WinHEX and to edit the original 114kb (as in 0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4) and downloaded into the phone, it does not start. Not respond to the button.
Upload preloader in Backup HTC 626G 1.03.707.1 (для SP Flash Tool) (0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4)
Phone is turned on. No image, just backlighting. but it works.
There are still a similar patient. After loading TWRP recovery, It hangs on the splash screen HTC and reboots (bootloop). When downloading files from a backup of the original, nothing changes. (bootloop)
I can not understand why I can not get them to work. What else can be done?
Three weeks I can not understand.
I recommend to view a selection of photos on my topic.
Im stuck on erecovery..please help..its a asia pacific version..
I recently tried to update via a sd card (dload folder etc) which went wrong..
Could someone help me please?
The last build number before doing this **** was EVA-L09C636B168
AbhishekS26 said:
Im stuck on erecovery..please help..its a asia pacific version..
I recently tried to update via a sd card (dload folder etc) which went wrong..
Could someone help me please?
The last build number before doing this **** was EVA-L09C636B168
Click to expand...
Click to collapse
Did you resolve the problem?
If not,, can you reboot to Fastboot
(switch off, connect by USB to PC, press and keep pressing Vol-, switch on)
and execute the following commands and copy back their results here, to see what the phone lists about its current status
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
hello i have the same situation and i cant fix my brother phone
how to write these commands??
---------- Post added at 01:05 PM ---------- Previous post was at 12:23 PM ----------
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.015s]
finished. total time: 0.021s
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-product-model
...
(bootloader) EVA-L09
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.000s
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem get-build-number
...
(bootloader) :EVA-L09C900B145
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\salah\Desktop\New folder\SRKToolHuawei-Lod-Chong-V2.0-20161002>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
finished. total time: 0.012s
salah3000esam8 said:
>fastboot oem get-bootinfo
(bootloader) unlocked
>fastboot oem get-build-number
(bootloader) :EVA-L09C900B145
Click to expand...
Click to collapse
If that was your output from Fastboot showing that you're on c900 with open Bootloader, you can try this
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
If you cannot boot to System to transfer files to SD card, you can put SD card to another Android device (as external SD) or use an adapter for PC to load to the SD cards
Hello Guy's!
Iv'e got a Moto x4 and wanted to install/ upgrade to Android Pie. With locked bootloder and original stock rom.
I get a failed and permission denied message in the command prompt.
No i am stuck in a fastboot loop.
I can't ven go to the recovery mode, all i do a allway get back to the fastboot screen.
This moto is the retail 1900-7 version.
Any help would be appreciated!
Thank You!
Do you have acctual Motorola drivers? Commends are correct, this is drivers problem in my opionion. What happens if you type in fastboot while phonw is connected- fastboot device
I have all the drivers installed. But I also got into this situation.
How could this even happen with a locked bootloader?
I tried to unlock the bootloader with the received code, but I did not succeed.
Bilbaobao said:
Do you have acctual Motorola drivers? Commends are correct, this is drivers problem in my opionion. What happens if you type in fastboot while phonw is connected- fastboot device
Click to expand...
Click to collapse
With "fastboot devices" it is recoginised correctly.
retaras said:
I have all the drivers installed. But I also got into this situation.
How could this even happen with a locked bootloader?
I tried to unlock the bootloader with the received code, but I did not succeed.
Click to expand...
Click to collapse
I should have enable the bootloder unlock in dev. options but didn't...
Because the guide i followed was with locked bootloader to upgrade to Pie.
I did not reicive an ota to pie, so i was stuck on 8.0 oktober patch.
The only command that was suxessfull was: fastboot flash partition gpt.bin
Is there any chanche to reverse this command?
Everything else was denied by bootloder prmission.
So actually i think there souldn't be much damage here, or am i wrong...
added: "fastboot getvar all" image to 1st post
Check this thread: https://forum.xda-developers.com/moto-x4/help/fastboot-longer-t3899010
I don't know what ROMs there are for XT1900-7, but I'm sure they're around.
dougo007 said:
Check this thread: https://forum.xda-developers.com/moto-x4/help/fastboot-longer-t3899010
I don't know what ROMs there are for XT1900-7, but I'm sure they're around.
Click to expand...
Click to collapse
Thank you!
Going to try this. :good:
Well, after a bunch of hours i found a soluion...
See command promt:
PS C:\adb> fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.001s
PS C:\adb> fastboot oem fb_mode_set
...
OKAY [ 0.010s]
finished. total time: 0.010s
PS C:\adb> fastboot continue
resuming boot...
OKAY [ 5.330s]
finished. total time: 5.333s
PS C:\adb> fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
PS C:\adb> fastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.010s
PS C:\adb> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.113s]
finished. total time: 0.118s
PS C:\adb> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.257s
PS C:\adb> fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\adb>
I was trying to go back to stock 10 from latest official lineage as I did few times before, but what I get is errors like below:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY225F37PD fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
Then the flashing process hangs.
Has anyone have an idea what may be causing this behavior?
I tried different cables, different PC's (windows and linux), phone boots to lineage, fastboot mode states flashing unlocked, boots to TWRP or lineage recovery so all seems to be fine but obviously isn't.
Anyone else experienced a problem of this sort?
[SOLVED] If anyone is interested I came to this last idea and dug out the oldest laptop we have at home and it came through with minimal adb and fastboot!
No idea why, my bet is that this has to do with USB on three other computers I had used being 3.0 only and a 2.0 on the old ASUS.
Anyways, I'm happy I made it and hope this can help someone looking for a solution to a similar problem.
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
warmachine20 said:
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
Click to expand...
Click to collapse
I have the same device, the same issue.
i have 5033F
the same issue
fastboot flashing unlock_critical
FAILED (remote: 'not allowed in locked state')
Finished. Total time: 0.003s
OEM Unlock enabled in developers option