Related
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
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
Hi a friend gave me her phone. Only thing I can do is load bootloader. No recovery and no OS. Just bootloader.
I can get it recognized by fastboot devices on my pc. I can get it to reboot into fastboot
When I try to flash recovery.img I get message FAILED (remote: Permission denied)
Anyone have any ideas what can be done?
Try Asus flash tool and a raw image. I believe you can find what you need in the resources thread.
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Try Asus flash tool and a raw image. I believe you can find what you need in the resources thread.
Click to expand...
Click to collapse
Thanks I just finished trying it. I got the same message that permission denied.
Maybe I need to unlock bootloader? But can't get into the OS.
lollyjay said:
Thanks I just finished trying it. I got the same message that permission denied.
Maybe I need to unlock bootloader? But can't get into the OS.
Click to expand...
Click to collapse
extract raw file. place adb fastboot in same folder. open command prompt in same folder and run following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
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
Thanks @sukhwant717 I will try this today and report back.
@sukhwant717 I don't know how to extract a .raw file
Nvm I just remembered that I just change raw to zip :silly:
OK here's what happened :
2. fastboot oem erase_osip_header OKAY
3. fastboot oem erase_token FAILED (remote: unknown OEM command)
4. fastboot oem start_partitioning OKAY
5. fastboot flash /tmp/partition.tbl partition.tbl FAILED
(remote: Permission denied)
lollyjay said:
OK here's what happened :
2. fastboot oem erase_osip_header OKAY
3. fastboot oem erase_token FAILED (remote: unknown OEM command)
4. fastboot oem start_partitioning OKAY
5. fastboot flash /tmp/partition.tbl partition.tbl FAILED
(remote: Permission denied)
Click to expand...
Click to collapse
Are you running these commands as administrator?
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Are you running these commands as administrator?
Click to expand...
Click to collapse
Derp!
lollyjay said:
Derp!
Click to expand...
Click to collapse
Is that derp on me or you? Lol
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Is that derp on me or you? Lol
Click to expand...
Click to collapse
Me. Hopefully I can blame it on my age
lollyjay said:
Me. Hopefully I can blame it on my age
Click to expand...
Click to collapse
Lol. I'm not a youngin myself.
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Is that derp on me or you? Lol
Click to expand...
Click to collapse
Still getting unknown oem command after "fastboot oem erase_token"
Bottom line: Even as Administrator Still getting "Permission denied"
Looks like I'm screwed :crying:
I tried placing a twrp backup on the sd card, then fastboot boot twrp.img and got into twfp recovery.
When I tried to restore the backup I get message "Cannot restore System - - mounted read only" Dammit
Also tried adb sideload of stock firmware. Proceeds to writing splashscreen image, but then gives:
mount: failed to mount /dev/block/by-name/system at /system: Device or resource busy
symlink: some symlinks failed
Updater process ended with ERROR: 7
lollyjay said:
Also tried adb sideload of stock firmware. Proceeds to writing splashscreen image, but then gives:
mount: failed to mount /dev/block/by-name/system at /system: Device or resource busy
symlink: some symlinks failed
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
have smoke n make a brew
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
timbernot said:
have smoke n make a brew
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Click to expand...
Click to collapse
I'm having both :crying:
The phone was free and worth every penny
lollyjay said:
I'm having both :crying:
The phone was free and worth every penny
Click to expand...
Click to collapse
Try flashing .184 raw file in your bootloader from here http://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
or quicker ,this one > .184 > 5th one down https://yadi.sk/d/FijRoAVJtvRiG
and with the flashtool in above my first link,with mediafire links , fastforward in video to 2:17 mins in to flashing in flashtool procedure in bootloader - remember to tick erase data ....
if doesnt work - remove flashtools and try the xFSTK in above link and full procedure
Thanks @timbernot but now all I get when I press the power button is two vibrates and totally blank screen.
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
baudoux said:
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
Click to expand...
Click to collapse
How did you think to flash LineageOs in boot where TWRP used to be?
Anyway if you didn´t complete this disastrous attempt you could solve it restoring mdtp partition that is a kind of gpt for other devices.
Flash it in both slot using fastboot. Then you´ll can know which partition is active, if the system yet still alive you´ll can boot on it or boot temporarily to TWRP to do your stuff but if not then you´ll need to restore one or more partitions flashing again the whole stock rom through MiFlash tool.
SubwayChamp said:
How did you think to flash LineageOs in boot where TWRP used to be?
Click to expand...
Click to collapse
this was a typo, and I got lost in the process
SubwayChamp said:
Flash it in both slots using fastboot.
Click to expand...
Click to collapse
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
baudoux said:
this was a typo, and I got lost in the process
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
Click to expand...
Click to collapse
Sorry for delay, yes, in both partitionn you have to flash mdtp, is to restore the table partition.
And about LOS I think you need to read a bit more or you'll have a thermonuclear reaction some day (just kidding) Custom roms come in form of zip and contain scripts that are prepared for developers to can unpack and flash files in the right place so don't worry about it.
First restore your partitions and the next is a ready-to-go.
SubwayChamp said:
yes, in both partitionn you have to flash mdtp, is to restore the table partition.
First restore your partitions and the next is a ready-to-go.
Click to expand...
Click to collapse
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
baudoux said:
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
Click to expand...
Click to collapse
You´ll find it inside the stock rom.
SOLVED
flashing mtdp_a and mtdp_b did not help, I hat to flash the stock rom again and start the process from scratch
other problems showed up:
I had to downgrade twrp to 3.3.0 to avoid error 7 while flashing LINEAGE OS
and then upgrade it again to 3.3.1 fo avoid error 64 while flashing GAPPS
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.