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 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.
So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
Cant find valid operating system
The device will not start
Click to expand...
Click to collapse
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
When you say 'adb', do you mean you're trying to use the command 'adb' when you're in fastboot? At the risk of stating the obvious, you need to use 'fastboot' command when you're in fastboot mode. 'adb' is only used when you're in recovery or in the actual android system. Otherwise you may wish to try a different fastboot version (sometimes that matters).
Javi22 said:
So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
Click to expand...
Click to collapse
TOOL_ALL_IN_ONE_1.1.1.3.zip it's the solution,Block again from here and you can start over
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
So my problem now is to unlock the bootloader
Javi22 said:
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
So my problem now is to unlock the bootloader
Click to expand...
Click to collapse
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Badger50 said:
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Click to expand...
Click to collapse
Thank you! But still the same...:
Code:
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>
Javi22 said:
Thank you! But still the same...:
Click to expand...
Click to collapse
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Badger50 said:
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Click to expand...
Click to collapse
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Javi22 said:
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Badger50 said:
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks but I can not get into recovery, the same screen:
Javi22 said:
Thanks but I can not get into recovery, the same screen:
Click to expand...
Click to collapse
Can you get into fastboot mode? If so you can then run deuces bootloop tool.
https://www.google.com/url?sa=t&sou...AxAB&usg=AOvVaw02czE3zeVK5sKbCe6V9L2v&cf=1
Hello guys:
One month ago i bought a Redmi note 8 pro, when it comes after a long time (almost 3 weeks) it comes with bootloader opened so i couldn use for example NFC pay. I looked for information to lock the bootloader i followed steps and bootloader was closed but phone was bricked too, so only can put smarthphone in fastboot or in recovery mode. I tried flash some roms by Fastboot using CMD in pc but appears this message
C:\adb>fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.004s
that was expected because bootloader is closed, but now i dont know if its posible to unlock bootloader and flash a new rom or beeing bootloader closed, flash a new rom for unbrick the phone.
To solve this problem I heard something abou autoriced xiaomi accounts and something about waiting seven days for unlock but i dont know nothing about it.
Thank you guys.
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I have tried to flash with fastboot and with miflash pro, and it always fails, I imagine that the flash tool will do the same as miflash pro and it will also fail, I will try anyway.
Thank you.
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I'm sorry for answering late, but I'm very busy with the current health situation.
What I have done is focus on unlocking the bootloader, and later will flash a new rom.
To unlock the device i have download "mi flash unlock tool"
Software recognice my phone
Click on "unlock">"unlock anyway">"unlock anyway"
Verifying device-ok
Unlocking-Fail
Couldn´t unlock
Please add your account in MIUI´s Settings > Developers option > Mi Unlock status
This way doesnt work.
I try by fastboot and cmd commands
Fastboot devices
Ok is connected and recognized
fastboot oem device-info
...
time 0.002s
Failed (remote: Unknown command)
fastboot oem unlock
...
time 18.455s
FAILED (Remote: GetVar Variable Not Found)
(Smartphone disconect and rebboy on recovery mode)
And well...I dont know what to do now.
It won't unlock because your device is already unlocked. You need to flash stock rom from custom recovery. Install custom recovery via adb. when you go back to stock rom device will be oem locked again. Also original account that was used to oem unlock device may be required that is why it might be failing.
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919 (useful software here)
After flashing stock rom In fastboot try
Linux: adb fastboot-linux oem lock
OSX: adb fastboot-mac oem lock
Windows: adb fastboot-windows.exe oem lock
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
How unlock the bootloader?My HTC U20 5G no download mode in bootloader !!!!!
Try
fastboot oem get_identifier_token --- error
fastboot flashing unlock --- error
fastboot oem unlock --- error
Yes I have the same problem. I thought it was Win 10, so I tried Win 7 as well, but got the same error there too.
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
iourikil said:
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
Click to expand...
Click to collapse
Yes, both options are activated (at least in my case).
Both commands "fastboot flashing unlock" and "fastboot oem unlock" result in "FAILED (remote: 'unknown command'), fastboot: error: Command failed".
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
Click to expand...
Click to collapse
It also works with the U19e, very annoying that they changed it.
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
Click to expand...
Click to collapse
In U20 fastboot can't use this way and In bootloader no download mode to select. >"<
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
for anyone that might come across this problem. I had the same issue trying to use fastboot to relock my bootloader. Found the answer on another forum. I was using adb to reboot to fastboot mode to run the command. This was the problem. I needed to reboot to the bootloader to run the command
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Hi there,
Just wanted to check in and see if anyone has managed to get bootloader unlocked?
Or is the htc u20 out of luck....
arcslt18 said:
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Click to expand...
Click to collapse
can you teach me how to do that?
thank you
mofish said:
can you teach me how to do that?
thank you
Click to expand...
Click to collapse
Hi, Just manually enter the fast boot mode with power key+Volume Up or Down depending upon the model and make, You can search this online how to enter Bootloader mode for one particular device. Once you are in Bootloader, Try Fastboot mode and Enter your commands. Should work
Anyone figure this out on Nord n200 5g T-Mobile variant? Please help