Develop Bugs

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

[HELP] Unable to flash raw file using Asus Flashtool (GPT command failed)

Hi All,
Good day.
Need some help regarding the error I encounter when flashing raw file. The fastboot in my ZF2 text also turns to red which I guess there's something wrong with my zf2. Also when trying to use XFSTK downloader, I get error also. Kindly refer to the images below. Hoping someone could help me regarding this. Thank you so much.
Btw, my phone is currently on Stucked Asus Logo.

Can u boot into stock recovery?

yakub234go said:
Can u boot into stock recovery?
Click to expand...
Click to collapse
Always looping in error and Installing update when I enter recovery mode.

pinuno said:
Always looping in error and Installing update when I enter recovery mode.
Click to expand...
Click to collapse
very first of all stay away from xfst if you are able to go into fastboot
download raw firmware. after that i will tell you commands you have to run step by step

I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.

pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
just go to fastboot and run following commands. don't use flash tool.
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
fastboot oem unlock
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
first boot may take long time. so have patience

GPT = Grand Partition Table
Beyond my knowledge unfortunately .
Keeping an eye on this thread to see if theres a fix .
Can you describe how you got into this state ?

pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
Maybe the file u r flashing is corrupt

pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
check your personal message folder

Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,

pinuno said:
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
Click to expand...
Click to collapse
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?

ygwstr said:
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
Click to expand...
Click to collapse
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.

ygwstr said:
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
Click to expand...
Click to collapse
no way to fix until you have UFI box or any other emmc repair box

sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.

ygwstr said:
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
Click to expand...
Click to collapse
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked

sukhwant717 said:
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
Click to expand...
Click to collapse
Thank you
I hope you find another solution to this problem.

sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Hi, i have the same problem.
Is there a solution, now?
Thanks

Bad Key written in Bootloader warning screen.

I have unlocked bootloader. And flash the official recovery to get Naugat OTA but after updating. I am seeing "ID : bad key " instead of "ID : N/A" which is written in previous version of OS.
Any one know what it really meant.?

Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.

GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
I tried but still it shows bad key.. but it's ok until my device boots in system succesfully
.

GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?

S3V3N said:
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
Click to expand...
Click to collapse
Pretty sure everyone has this with an unlocked bootloader.

ok thx

xxBrun0xx said:
Pretty sure everyone has this with an unlocked bootloader.
Click to expand...
Click to collapse
definitely not.

Am facing same problem. Bad boot image.. Looking for stock boot image

kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
did you find the solution iused twrp and i had no problem after installing the Russian ROM im getting this message

kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.

G4liant said:
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
Click to expand...
Click to collapse
I mean 'bad key' instead of showing "N/A"

kdagia said:
I mean 'bad key' instead of showing "N/A"
Click to expand...
Click to collapse
You need to flash modified logo.bin ...That's it

Same, and cant seem to flash at all
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock

[email protected] said:
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
Click to expand...
Click to collapse
I have exactly the same problem, has it been able to solve it?
How to solve it?

Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.

thoros1179 said:
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
Click to expand...
Click to collapse
Try typing "fastboot oem fb_mode_clear" inside the bootloader.

Nokia 3.2 Europe version stuck in bootloader

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
Thanks

same bro idk how to fix it could someon please help?

try the next command
fastboot getvar current-slot
Click to expand...
Click to collapse
if it says _a or _b then its good and you should be able to flash images if it says unknown you should try the command
fastboot set_active=a
Click to expand...
Click to collapse
edit: second command was wrong should now work.

thegamingcat13 said:
try the next command
if it says _a or _b then its good and you should be able to flash images if it says unknown you should try the command
edit: second command was wrong should now work.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot: b
finished. total time: -0.000s
second command not working
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active=a
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Phone stuck in fastboot

does anyone have recovery files for nokia 3.2 or stock image

my nokia 3.2 bootloader version is blank. how can i recover from this. i am stuck

Anyone has got a solution for this?

just flash it via fastboot and all will be well. just use fastboot flash boot boot.img, fastboot flash system system.img. with this format you'll be able to boot your phone again.

I have the same problem.I was in twrp and i tapped on recovery and now every time i want to exit to my system,i go back to the bootloader and for about 2 hours i was trying to fix this and now i did the fastboot oem lock and im on the screen where i need to lock my bootloader and i tried to go up or down but the buttons dont work,anybody got an acutal solution for this?

smure said:
just flash it via fastboot and all will be well. just use fastboot flash boot boot.img, fastboot flash system system.img. with this format you'll be able to boot your phone again.
Click to expand...
Click to collapse
how do you do that?

smure said:
does anyone have recovery files for nokia 3.2 or stock image
Click to expand...
Click to collapse
here you go https://gsmusbdriver.com/nokia-3-2

hi, I have here a Nokia 3.2 stuck in bootllop,
I tried to wipe/factory reset from recovery menu, but I still get a bootloop?
I have not even enabled developer settings from it.

How to do a Flash_All on global BE2011?

Sorry for the simply question, but I'm confused.
I've unpacked the 11.0.3 payload.bin and wrote a flash_all.bat for my BE2011
Unlocked bootloader
But when I try to run the first command `fastboot flash abl abl.img` it says `FAILED (remote: 'Flashing is not allowed for Critical Partitions`
Any tips?

You need to enter fastbootd with fastboot reboot fastboot.

thomaskmaagaard said:
fastboot reboot fastboot
Click to expand...
Click to collapse
Okay I'll try this now.