Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
if fastboot flash doesn't work you probably have fastboot locked.
brando56894 said:
if fastboot flash doesn't work you probably have fastboot locked.
Click to expand...
Click to collapse
Thanks mate. Do you know how to unlock fastboot?
ilpolpi65 said:
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Sway327 said:
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Click to expand...
Click to collapse
Are you able to get back into system? If so, run this command with an active ADB connection.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Hi, I was wondering if you were able to fix your tablet. I have this problem right now and haven't found any way of fixing it.
NYCHitman1 said:
Are you able to get back into system? If so, run this command with an active ADB connection.
Click to expand...
Click to collapse
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
viii_xvi said:
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
Click to expand...
Click to collapse
Did you get your tablet to work? I have the same problem
qAnAthemA said:
Did you get your tablet to work? I have the same problem
Click to expand...
Click to collapse
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
viii_xvi said:
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
Click to expand...
Click to collapse
Have you tried to ask Google for a USB bootable recovery + ZIP file ?
Related
Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Rebel908 said:
Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Click to expand...
Click to collapse
You need to unlock it first.
Rebel908 said:
Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Click to expand...
Click to collapse
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
goldflame09 said:
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
Click to expand...
Click to collapse
Tried, fastboot hung at oem unlock, wouldn't do a damn thing. and tried to manually flash factory images via adb as well, same results.
Rebel908 said:
Tried, fastboot hung at oem unlock, wouldn't do a damn thing. and tried to manually flash factory images via adb as well, same results.
Click to expand...
Click to collapse
does this mean however that you can get the fastboot screen to show up?
goldflame09 said:
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
Click to expand...
Click to collapse
goldflame09 said:
does this mean however that you can get the fastboot screen to show up?
Click to expand...
Click to collapse
Yeah I can get fastboot to show up. I've already set it off for RMA though.
Rebel908 said:
Yeah I can get fastboot to show up. I've already set it off for RMA though.
Click to expand...
Click to collapse
oh alright well good luck with it and hope you get a new functioning one
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
I've gotten my Google Pixel 2 XL in a bootloop. When I use Toolkit to flash Factory Stock Image I get "your device is not set" then it goes back to the main menu.
I'd download factory image, extract it and run flash-all.bat
SSJMarkelous said:
I've gotten my Google Pixel 2 XL in a bootloop. When I use Toolkit to flash Factory Stock Image I get "your device is not set" then it goes back to the main menu.
Click to expand...
Click to collapse
This should help you
https://www.google.com/amp/s/www.androidexplained.com/pixel-sideload-update/amp/
ne0ns4l4m4nder said:
I'd download factory image, extract it and run flash-all.bat
Click to expand...
Click to collapse
it says failed.
mackentosh said:
This should help you
https://www.google.com/amp/s/www.androidexplained.com/pixel-sideload-update/amp/
Click to expand...
Click to collapse
nope it didnt work as well. =(
SSJMarkelous said:
it says failed.
Click to expand...
Click to collapse
I would suggest following the instructions listed on Google's site. You can also download the factory images from the same place: https://developers.google.com/android/images
I've bootlooped my phone as well (Google variant, not Verizon) and was able to restore it using the url I included above. One tip though: Back up your userdata (/sdcard) first. flash-all will wipe your userdata. Originally, I tried to restore the factory image by disabling 'wipe', but it wouldn't boot until I included 'wipe'
(I've never used toolkit though so I can't help you with that app.)
Edit: my flashing tool has been moved to it's own post:
[TOOL] Deuces Bootloop-Recovery & Flashing Script
SSJMarkelous said:
it says failed.
Click to expand...
Click to collapse
Did you unlock_critical?
When using flash-all it flashes the bootloader too. As far as I can tell you need to "fastboot flashing unlock_critical" before running "flash-all".
Deuces said:
Try my script: https://forum.xda-developers.com/showthread.php?p=74503983#post74503983
Click to expand...
Click to collapse
Didn't work.
r0adki111 said:
Did you unlock_critical?
When using flash-all it flashes the bootloader too. As far as I can tell you need to "fastboot flashing unlock_critical" before running "flash-all".
Click to expand...
Click to collapse
Tried and it didn't work.
So far i can only access fastboot, recovery mode, and if i do regular boot up it will get stuck at "google".
SSJMarkelous said:
So far i can only access fastboot, recovery mode, and if i do regular boot up it will get stuck at "google".
Click to expand...
Click to collapse
It's better if you give us specifics step-by-step on what you're doing and let us know if there are any steps where you're getting an error on, so we can help to better troubleshoot what you're doing wrong.
fastboot and bootloader mode is all you need. You should be running flash-all from bootloader, not recovery mode. Did you look at the url I posted earlier? Did you update your Android SDK files to the latest version?
Edit: my flashing tool has been moved to it's own post:
[TOOL] Deuces Bootloop-Recovery & Flashing Script
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?
Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error
motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
but are they all the same target as the .img name
Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.
Does anyone have the boot image for the official oxygen os 13 MT2111_11_F.11? Thanks in advance.
Here is it
有也没用，fastboot模式进不去
anbell said:
有也没用，fastboot模式进不去
Click to expand...
Click to collapse
you may use fastbootd mode to flash boot.img if phone is already unlocked. If it is locked, you will probably need to downgrade to get working fastboot and be able to unlock.
penguinus said:
you may use fastbootd mode to flash boot.img if phone is already unlocked. If it is locked, you will probably need to downgrade to get working fastboot and be able to unlock.
Click to expand...
Click to collapse
Can you guide flashing boot.img in fastbootD mode. Fastboot flash boot boot.img is not working.
ptr21 said:
Can you guide flashing boot.img in fastbootD mode. Fastboot flash boot boot.img is not working.
Click to expand...
Click to collapse
Command is the same. Should work. What error it shows?
penguinus said:
Command is the same. Should work. What error it shows?
Click to expand...
Click to collapse
Here. Image is patched with Magisk.
Try cmd instead of power shell. Power shell may need to enter path like
fastboot flash boot .\boot.img
penguinus said:
Try cmd instead of power shell. Power shell may need to enter path like
fastboot flash boot .\boot.img
Click to expand...
Click to collapse
No luck.
Well, I'm not sure what's happening, but normally it should work. The phone currently starts to the system correctly? Issue may be not related to what error shows. Try to reboot the phone, connect it to another port (USB 2.0 is highly recommended) or even try with different PC, update fastboot drivers if possible. From my experience, issues mostly happens because of cable, port or drivers.
penguinus said:
Well, I'm not sure what's happening, but normally it should work. The phone currently starts to the system correctly? Issue may be not related to what error shows. Try to reboot the phone, connect it to another port (USB 2.0 is highly recommended) or even try with different PC, update fastboot drivers if possible. From my experience, issues mostly happens because of cable, port or drivers.
Click to expand...
Click to collapse
Thanks a lot.
Tried with older laptop via USB 2,0.
It worked.
Does anyone have the boot image for F.13? Thanks in advance
damocleas said:
Does anyone have the boot image for F.13? Thanks in advance
Click to expand...
Click to collapse
This thread:
OOS 9RT F.13 Update. BOOTLOADER RETURNS
Here's the F.13 update. The bootloader is back after this update so you guys can root again. https://www.androidfilehost.com/?w=files&flid=337023
forum.xda-developers.com