Database Develop

[Q] Fastboot flash error - FAILED (remote: unknown command)

Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.

same here

Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825

neverdies said:
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP

jmang98 said:
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
Click to expand...
Click to collapse
what steps have you done so far?
ie: unlock/root/flash recovery?

itsJohnuno said:
what steps have you done so far?
ie: unlock/root/flash recovery?
Click to expand...
Click to collapse
Same problem....

Did anyone who was having this problem end up finding a fix?

This is a problem I have too, need a fix.

Still need a solution. Is this due to lollipop? Cuz back then I was able to unlock the bootloader. LG L90 D415

BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
D405_v20a_patched_aboot??
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
EDIT:
Did you flash D405_v20a_patched_aboot if not, you need to flash D405_v20a_patched_aboot

i also have same poblem d415

me too...same problem D415 tmobile version

Does anyone with this problem have an lg d-415 and android with root? Because I think these commands in a terminal emulator or in an adb shell will fix fastboot:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Or if that doesn't work try this >> https://forum.xda-developers.com/lg...ick-hard-bricked-l90-variants-t3173429/page24
I think this problem is caused by people not unlocking the bootloader.

Same error on LG D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.

aixhinnn said:
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
Click to expand...
Click to collapse
How did you enable fastboot, what commands did you run?

0000.0000.00 said:
How did you enable fastboot, what commands did you run?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.

aixhinnn said:
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
Click to expand...
Click to collapse
Did you try volume down+ power to factory reset and see if that fixes it?

im having this problem too, but on an lg v10 tmobile

17mm said:
im having this problem too, but on an lg v10 tmobile
Click to expand...
Click to collapse
This problem is strange and I'm not sure if it has a solution.

0000.0000.00 said:
This problem is strange and I'm not sure if it has a solution.
Click to expand...
Click to collapse
what i did was get lg bridge and mobile support, let if flash the most current update then used this method to root on the latest 30c update https://forum.xda-developers.com/tm...901-nougat-t3773942/post76711778#post76711778
twrp flashed fine, magisk installed flawlessly, now rooted on latest official update with all kinds of goodies to play with :good:
oh and with magisk you pass safetynet aswell so all good.

Phone Semi-bricked

Hello all!
So recently I was playing around with my G4, and decided to see if i could boot into fastboot mode. Turned out I could: theandroidsoul.com/lg-g3-fastboot-mode-61660/, but it would remove download mode in the process. It was totally useless. I couldn't run any commands and so I decided to put download mode back. I rebooted my phone, a notification caught my eye, and I completely forgot to put it back.
Fast forward a couple days, and my phone starts to run at 2 miles per hour. So, I factory reset, losing root and recovery in the process. That still didn't fix it, and now the camera, all speakers, and microphone don't work. Now, I can't replace download mode without root, so I cant run the LG Flash Tool. I'm starting to lose my mind over this. Please help!

Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.

MrSteelX said:
Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.
Click to expand...
Click to collapse
I can, but that unfortunately requires download mode, which I removed(oops).

jlynch630 said:
I can, but that unfortunately requires download mode, which I removed(oops).
Click to expand...
Click to collapse
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.

MrSteelX said:
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.
Click to expand...
Click to collapse
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.

jlynch630 said:
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.
Click to expand...
Click to collapse
Your only hope is to get fastboot to work then or lg service center

MrSteelX said:
Your only hope is to get fastboot to work then or lg service center
Click to expand...
Click to collapse
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?

jlynch630 said:
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?
Click to expand...
Click to collapse
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.

MrSteelX said:
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.
Click to expand...
Click to collapse
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)

jlynch630 said:
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)
Click to expand...
Click to collapse
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img

MrSteelX said:
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img
Click to expand...
Click to collapse
I didn't, but I enabled it and tried again, and it still didn't work.

try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.

MrSteelX said:
try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.
Click to expand...
Click to collapse
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s

jlynch630 said:
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
Click to expand...
Click to collapse
Did you make a backup of laf?

Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?

jlynch630 said:
Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?
Click to expand...
Click to collapse
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.

MrSteelX said:
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.
Click to expand...
Click to collapse
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s

jlynch630 said:
Which partition?
Click to expand...
Click to collapse
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
jlynch630 said:
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s
Click to expand...
Click to collapse
fastboot erase laf.img
fastboot flash laf laf.img
try that.

MrSteelX said:
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
fastboot erase laf.img
fastboot flash laf laf.img
try that.
Click to expand...
Click to collapse
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running

jlynch630 said:
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running
Click to expand...
Click to collapse
At this time, I am unable to help you out. You should get into contact with Jcase or Autoprime. They know a lot more about this and may be able to help fix this laf.
fastboot erase laf

Fastboot Recovery? Getting g.co/ABH Error On Boot

I flashed the Android Wear 2.0 OTA update and now the watch won't boot. I get the "Device Software Can't Be Checked For Corruption" error and it's telling me to go to g.com/ABH.
It won't go into recovery mode, but will go into fastboot mode. I grabbed the stock images from here, and flashed the stock boot, system, and recovery imgs, but the error persists.
https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Am I screwed? Or is there something I could do to recover?
Thanks.

Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk

Wait for about 10 seconds when the warning appears. The watch will continue it's boot after 10 secs.

TonySuperPony said:
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Click to expand...
Click to collapse
I thought I had initially. I hadn't turned the watch on for a while, but decided to get it set up yesterday when I saw news of the 2.0 update hit. It originally had the first firmware on it and wouldn't update to 2.0 (adb would fail to find the watch).
So, I flashed MWF76 from the link in my earlier post. And that worked properly -- the watch booted normally, set up the apps, the right build number was showing, etc.
When that was done I tried to flash the 2.0 update again. And this time the watch was being recognized properly with adb. The flash procedure seemed to go without a hitch, but I got the g.co/ABH error on first boot.
And if you let the watch sit for 10 seconds, it only boots into Fastboot mode. You can't enter recovery. If you try to enter recovery with the vol-down+power button combo, you see recovery for a split second and then it goes right to fastboot.
At the moment it appears the bootloader is locked again.

Still experimenting. Hoping someone with more knowledge may be able to help.
Fastboot oem unlock reports that the bootloader is already unlocked.
Tried flashing all of the IMGs in MFW76 and these flash successfully:
boot
system
recovery
modem
asusfw
But when trying to flash these, the flash fails because it says the bootloader is locked. Trying fastboot oem unlock again reports the bootloader is unlocked, but still can not flash these...
devinfo
factory
misc
modemst1
modemst2
oem
splash
Tried fastboot flashing unlock_critical, and the watch shows part of a message, but I can't see if there's anything to do on...pressing the top or bottom buttons changes the color of the bg.

Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.

yilun said:
Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.
Click to expand...
Click to collapse
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?

re: flashable AW 2.0 zip file
BigWopHH said:
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?
Click to expand...
Click to collapse
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!

Misterjunky said:
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!
Click to expand...
Click to collapse
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"

re: adb sideload
BigWopHH said:
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"
Click to expand...
Click to collapse
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!

Misterjunky said:
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!
Click to expand...
Click to collapse
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.

BigWopHH said:
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.
Click to expand...
Click to collapse
I'd try to get the watch running 1.5 first via fastboot.

See my post in the other thread linked here, specifically my edits.
I did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata"

I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?

re: not booting properly
AndyKir said:
I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?
Click to expand...
Click to collapse
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!

Misterjunky said:
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!
Click to expand...
Click to collapse
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.

AndyKir said:
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.
Click to expand...
Click to collapse
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.

Misterjunky said:
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.
Click to expand...
Click to collapse
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?

re: fastboot bootup
AndyKir said:
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?
Click to expand...
Click to collapse
You must have flashed the wrong boot.img (which is the kernel)
Make 100% sure that you are flashing the correct kernel and
don't issue the command "fastboot format userdata".
All you need is:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
then oem lock bootloader
What was the exact filename of the ziip file
which had the 3 IMG files in it?
Here is the link for the zip file which contains the correct IMG files in it:
https://www.dropbox.com/s/tz9bg5fggpfn2q6/swift_partition_dump_part1_MWG68.zip?dl=1
unlock bootloader, flash the three img files, lock bootloader
and issue this fastboot command: " fastboot reboot "
Don't flash anything else and don't format anything...
Good luck, have a great day!

Misterjunky, thank you for your replies!
I`ve downloaded your files from Dropbox, put it in c:\adb\correct\ folder, and run next commands in PowerShell
PS C:\adb> fastboot oem unlock
...
(bootloader) The bootloader is already unlocked!
OKAY [ 0.006s]
finished. total time: 0.007s
PS C:\adb> fastboot flash boot C:\adb\correct\boot.img
target reported max download size of 262144000 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
OKAY [ 3.222s]
finished. total time: 4.263s
PS C:\adb> fastboot flash recovery C:\adb\correct\recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.043s]
writing 'recovery'...
OKAY [ 3.150s]
finished. total time: 4.195s
PS C:\adb> fastboot flash system C:\adb\correct\system.img
target reported max download size of 262144000 bytes
erasing 'system'...
OKAY [ 1.134s]
sending sparse 'system' (254201 KB)...
OKAY [ 8.468s]
writing 'system'...
OKAY [ 26.695s]
sending sparse 'system' (149469 KB)...
OKAY [ 5.016s]
writing 'system'...
OKAY [114.570s]
finished. total time: 155.890s
PS C:\adb> fastboot oem lock
...
(bootloader) Locking bootloader...
(bootloader) Device Locked!
(bootloader) Locking bootloader done!
OKAY [ 0.023s]
finished. total time: 0.024s
PS C:\adb> fastboot reboot
rebooting...
finished. total time: 0.008s
PS C:\adb>
After reboot, I still in Fastboot mode - nothing is changed.

Request OEM unlock Huawei P10

Hi all,
I have an incorrect firmware installed for my P10 and lots of things are not working (oreo 8.0). I want to re-flash or rollback to other firmwares but problem is I can't get into TWRP anymore. flashing it doesn't work and although I see in fastboot Phone Unlocked and FRP unlock i have the idea it has to do with the OEM unlock not working properly. It's also not available in the developer options. What;s exactly the link to huawei's page where you can request your phone unlock ID ?
Thanks

Whats not working ?
What is it saying when flashing something through fastboot ?

virusdunil said:
Whats not working ?
What is it saying when flashing something through fastboot ?
Click to expand...
Click to collapse
When I go into the bootloader and want to flash TWRP I get following message:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16494 KB)...
OKAY [ 0.552s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.566s

What is the ADB command youre using ?

virusdunil said:
What is the ADB command youre using ?
Click to expand...
Click to collapse
fastboot flash recovery_ramdisk twrporeo.img
and my twrp oreo name is twrporeo.img

Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img

virusdunil said:
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
Click to expand...
Click to collapse
Same problem...:
C:\Android>fastboot flash ramdisk twrporeo.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16494 KB)...
OKAY [ 0.532s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s

i did a mistake...its really recovery_ramdisk
Look Here...
TWRP

virusdunil said:
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
Click to expand...
Click to collapse
I already tried that but no success. Did a factory reset and now the bootloader is locked again. How can I unlock the bootloader again?
Thanks

1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?

virusdunil said:
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
Click to expand...
Click to collapse
First of all, I've tried to update from Nougat to Orea via Blackballs method in this thread https://forum.xda-developers.com/p10-plus/development/oreo-update-thread-l29c432-t3729907 with the firmware mentioned there
What is not working:
I've managed to do the first part (oreo install), but:
- SImcard has 'No service
- Can't flash TWRP
- Bootloader / phone locked in Fastboot
- I can't remember how I unlocked the P10 last year (I have a P10 L09-VTR, rebranded to L29-VTR and now 'working' on a VKY P10 plus rom)

Hot to unbrick MiA2

Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks

https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

Writing devcfg_a failed
Flashing is not allowed forum critical partition

b1gb1ng said:
Writing devcfg_a failed
Flashing is not allowed forum critical partition
Click to expand...
Click to collapse
fastboot flashing unlock_critical

b1gb1ng said:
Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks
Click to expand...
Click to collapse
https://en.miui.com/thread-3052407-1-1.html

Daha3ker said:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
when I launch this command it is not recognised, I just have a list of commands in fastboot
what should I do?

fastboot -w
Be warned, it will wipe your device.

Sift said:
fastboot -w
Be warned, it will wipe your device.
Click to expand...
Click to collapse
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"

Grooverit said:
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"
Click to expand...
Click to collapse
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

minnuss said:
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
well, I updated the newest adb, now the command seems to work, but after "fastboot flashing unlock_critical" I still have this:
PS C:\android-sdk\platform-tools> fastboot flashing unlock_critical
OKAY [ 0.034s]
Finished. Total time: 0.035s
PS C:\android-sdk\platform-tools> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s
no unlock why?
---------- Post added at 03:26 PM ---------- Previous post was at 02:55 PM ----------
it was my erorr, sorry
thanks for the advice, I unlocked and than flashed stock rom after booting in edl mode
I still have to check if I still have bootloader unlocked as I get advise on start screen

Grooverit said:
I still have to check if I still have bootloader unlocked as I get advise on start screen
Click to expand...
Click to collapse
Yes it is still all unlocked.
And if you wish to thanks someone on this forum, use the thanks button in the down right corner of the post that helped you. :good:

You should visit Xiaomi service centre. They will unbrick your phone without any charge.