Database Info

HELP Bootloader unlocked without code!!!!!

Hello,
i have a big problem yesterday i made the update to 560.
After this i want to root it i tried it with Kingroot *windows*.
After 50% the phone rebootet and show Fastboot screen and *Phone Unlocked*
So i thinked why not, so i tried to root with this
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
but CMD shows me only
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp_3.0
.2_mate7_6.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (11924 KB)...
OKAY [ 1.219s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.234s
Then i tried to relock bootloader but i have no Key. And i had not unlocked my Phone with a key....... whats wrong

you should take unlock code
Sent from my HUAWEI MT7-L09 using Tapatalk

If you need an unlock code this solved it for me,
Use king root, followed by Honor Tuner app
This is how I did it, couldn't figure out how to use Huawei site either
Follow this guide
http://forum.xda-developers.com/mate-7/general/unlock-code-via-honortuner-t3217651
All credits to that thread
Good Luck

KingRoot doesn't work for me on marshmallow. Oh well.

Have you tried using the android apk, not the windows application

funboomer2005 said:
Hello,
i have a big problem yesterday i made the update to 560.
After this i want to root it i tried it with Kingroot *windows*.
After 50% the phone rebootet and show Fastboot screen and *Phone Unlocked*
So i thinked why not, so i tried to root with this
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
but CMD shows me only
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp_3.0
.2_mate7_6.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (11924 KB)...
OKAY [ 1.219s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.234s
Then i tried to relock bootloader but i have no Key. And i had not unlocked my Phone with a key....... whats wrong
Click to expand...
Click to collapse
your system partition is corrupted,
Extract system.img from B560 firmware,
Flash system.img
hopefully it will be ok

Sorry for that late Post it helped. THX

Problem With flashing TWRP recovery

After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked

Maybe lock it and unlock again.

gm007 said:
Maybe lock it and unlock again.
Click to expand...
Click to collapse
the problem is that i cant do any operation on Bootloader including locking bootloader...

ezraiil1 said:
the problem is that i cant do any operation on Bootloader including locking bootloader...
Click to expand...
Click to collapse
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem unlock *********
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot devices
AHK7N16B18003212 fastboot

What version of fastboot do you have?

5[Strogino] said:
What version of fastboot do you have?
Click to expand...
Click to collapse
Minimal ADB and Fastboot

ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
try to revoke usb debugging then enable again

eddmecha said:
try to revoke usb debugging then enable again
Click to expand...
Click to collapse
it doesnt work...

ezraiil1 said:
it doesnt work...
Click to expand...
Click to collapse
have you tried with a different cable & pc?how about your drivers?is it the lastest?

I had the exact same problem. Disable everything related to "Find my phone" and restart. TWRP will flash after this.
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse

eddmecha said:
have you tried with a different cable & pc?how about your drivers?is it the lastest?
Click to expand...
Click to collapse
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.

Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Thank you everybody,all of you were Useless xD
love u all.
Cya!

[Need Help]Unable to flash recovery for Mate 9 Oreo, android 8.0

My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?

Ahlangwolf said:
My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?
Click to expand...
Click to collapse
The bootloader is not unlocked, you must block with fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader

jftorrente said:
The bootloader is not unlocked, you must block with fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader
Click to expand...
Click to collapse
And make sure to go to Developer options when booted and enable OEM unlock.
Both Phone and FRP must be unlocked in fastboot

ante0 said:
And make sure to go to Developer options when booted and enable OEM unlock.
Both Phone and FRP must be unlocked in fastboot
Click to expand...
Click to collapse
The same happened to me, I checked and it appeared unlocked but it did not let me install the recovery. so I relocked it and unlocked it and that's how it worked

jftorrente said:
The same happened to me, I checked and it appeared unlocked but it did not let me install the recovery. so I relocked it and unlocked it and that's how it worked
Click to expand...
Click to collapse
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.

Ahlangwolf said:
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.
Click to expand...
Click to collapse
:good::good::good::good:

Great, now read the Forum Rules on posting, moved out of the Development Section....
Ahlangwolf said:
My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?
Click to expand...
Click to collapse
Ahlangwolf said:
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.
Click to expand...
Click to collapse

do i have to execute this? fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader , what is the xxxxxxxx? TIA

you must be disable find phone and fingepin

Failed remote command not allowed custom Rom (twrp)

Hi.
I've been trying to flash twrp my Huawai Mate 8 for a couple of weeks. I keep getting the error I mentioned in the title. The bootloader is unlooked, frp is looked. USB debugging is enabled. OEM is grey.
Android version 7.0, emui version 5.0.1. I've been using the official twrp and used adb files and fastboot from other sources as well as official files. The phone is NOT rooted.
Here is the full message:
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22142 KB)...
OKAY [ 0.470s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.477s
I would appreciate any help as this problem has bugged me for so long by now. Thanks!!

Google pixel 1 stuck in fastboot!

Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...

SAMPPLE said:
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.

Homeboy76 said:
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Click to expand...
Click to collapse
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.

SAMPPLE said:
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
Click to expand...
Click to collapse
What did you try to exit fastboot?

Homeboy76 said:
What did you try to exit fastboot?
Click to expand...
Click to collapse
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...

SAMPPLE said:
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
Click to expand...
Click to collapse
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.

Homeboy76 said:
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Click to expand...
Click to collapse
I know I tried a lot of things to make it work... but nothing... Anyway thank you for helping me

put it in the freezer for an hour and tell me what happens, mine booted up with that, just put it in properly (all phone holes covered)