FAILED <Remote: command not allowed> - Off-topic

I try ublock bootloader mate 8 nxt-dl00 6.0 emui 4.1 give me error i try this command fastboot oem unlock xxxxxxxxx is (bootloader code)
FAILED <Remote: command not allowed> any one help me.

Related

[Q] Stuck. RELOCKED & S-ON hboot 1.54 - HELP.

I have a GOOGL001 phone that doesn't seem to be taking RUUs, but I might be doing it wrong. I am UNABLE to enter into my android rom because the phone is relocked, this stops the rom from booting. Recovery is HTC stock, so I am not really able to do anything there. I followed a stupid guide online that led to an error in installing the appropriate stock RUU, and as a result, I have a S-ON and RELOCKED phone now.
I have been trying so far: Fastboot oem rebootRUU, trying to install anything here that says GOOGLE by doing Fastboot Flash Zip RUU.zip.
I am getting the error:
sending 'zip' (506183 KB)... OKAY
writing 'zip'... INFOsignature checking..
FAILED (remote: 12 signature verify fail)
Any ideas anyone? Has anyone ever gotten out of this issue before?
There apparently is a bug that doesn't allow my 1.54 hboot to "Fastboot oem unlock". I have tried this and I have gotten this error:
... INFO[PG_ERROR] htc_pg_part_traverse(839):
INFO invalid traverse range
INFO[PG_ERROR] htc_pg_part_read(1029):
INFO htc_pg_part_traverse failed
INFO[DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
INFOead error!
INFO[DISPLAY_ERR] Can not load custom splash!
INFOLoading custom splash failed!
OKAY
Any help would be appreciated! Thanks
JiraffeLeung said:
I have a GOOGL001 phone that doesn't seem to be taking RUUs, but I might be doing it wrong. I am UNABLE to enter into my android rom because the phone is relocked, this stops the rom from booting. Recovery is HTC stock, so I am not really able to do anything there. I followed a stupid guide online that led to an error in installing the appropriate stock RUU, and as a result, I have a S-ON and RELOCKED phone now.
I have been trying so far: Fastboot oem rebootRUU, trying to install anything here that says GOOGLE by doing Fastboot Flash Zip RUU.zip.
I am getting the error:
sending 'zip' (506183 KB)... OKAY
writing 'zip'... INFOsignature checking..
FAILED (remote: 12 signature verify fail)
Any ideas anyone? Has anyone ever gotten out of this issue before?
There apparently is a bug that doesn't allow my 1.54 hboot to "Fastboot oem unlock". I have tried this and I have gotten this error:
... INFO[PG_ERROR] htc_pg_part_traverse(839):
INFO invalid traverse range
INFO[PG_ERROR] htc_pg_part_read(1029):
INFO htc_pg_part_traverse failed
INFO[DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
INFOead error!
INFO[DISPLAY_ERR] Can not load custom splash!
INFOLoading custom splash failed!
OKAY
Any help would be appreciated! Thanks
Click to expand...
Click to collapse
If their is ever a fix you will find it here (hint you made a big mistake)
http://forum.xda-developers.com/showthread.php?t=2547894

FAILED (remote: Command not allowed)

Hello, I have problems with my sony xperia Z5p (E6853), when I try to unlock bootloader it say: (remote: Command not allowed)
C:\Users\Sampo>fastboot devices
CB5A299119 fastboot
C:\Users\Sampo>fastboot -i 0x0fce oem unlock MY CODE
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
When I check my unlocking status it say (Bootloader unlock allowed: yes)
And I have installed new drivers to my computer, I use win10.
Please help me!
Go to Z5 forum
selailija said:
Hello, I have problems with my sony xperia Z5p (E6853), when I try to unlock bootloader it say: (remote: Command not allowed)
C:\Users\Sampo>fastboot devices
CB5A299119 fastboot
C:\Users\Sampo>fastboot -i 0x0fce oem unlock MY CODE
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
When I check my unlocking status it say (Bootloader unlock allowed: yes)
And I have installed new drivers to my computer, I use win10.
Please help me!
Click to expand...
Click to collapse
Go to Z5 forum, this is only for Z normal

P9 (EVA-L09) Locking Bootloader failure

Hi all,
I have debranded my EVA-L09 from Three UK, so that I can get faster OTA updates (and also to try to participate in future betas) - I'm now successfully on C432B166
However, I'd like to now re-lock my bootloader, but am struggling.
Whenever I boot to fastboot and run "fastboot oem relock ****************", I get the following response:
Code:
...
FAILED (remote: root type is risk)
finished. total time: 0.006s
If I try "fastboot oem lock ****************", I get the following:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
I have tried with "Enable OEM unlock" both enabled and disabled in Developer Options.
Can anyone give me any pointers on how to re-lock the bootloader?
Many thanks!
Sorry to bump an old thread. I'm currently having the same problems @ConfusedTA . Unfortunately I think it's difficult to re-lock bootloader without being on the same firmware that you were on when you unlocked it.
If anybody knows a way of forcing the bootloader to lock it'd be much appreciated!

Can't flash TWRP. I just get 'FAILED (remote: Command not allowed)'

Hi everyone
I'm in a spot of trouble at the moment with my Xperia ZR.
When I try to flash it via ADB, I get 'FAILED (remote: Command not allowed)'.
My phone is rooted and has an unlocked bootloader.
Can anyone help?
-Gabe

Unbrick

Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:
not possible to flash firmware in downloade mode?
mrt box
elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..
Dude, I have the same problem with a P20 Pro since january!
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?

Categories

Resources