Develop Bugs

I think I bricked my New Nexus 7

I'm new to the forums and I've been searching and reading all over for help. This was my first time rooting. I was trying to flash a rom in TWRP and somehow erased everything, no OS or anything. Now when I boot up it only says google. It won't load past that. I can get into the fastboot screen but the adb options don't work. And now since trying two different tool kits to flash to stock image, I can't get on TWRP anymore. Any help would be great thanks. I'm not even sure what I did but I can try to add more information. Thanks

You can boot in fastboot and flash it back to stock.
I see Google hasn't posted the factory images out there yet, your tablet is fixable, but you need the image. Maybe someone else can chime in with a image I haven't found yet. BTW, you can fastboot flash the recovery if its a .IMG file to get that back.
Note: you'll need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2

trssho91 said:
Can you boot into fastboot mode by holding all three buttons for 5 seconds with the device off? It doesn't need a os or recovery just as long as you didn't kill the bootloader. Once in fastboot just flash it back to stock.
Download your image here: https://developers.google.com/android/nexus/images
Don't freak out yet, its hard to brick a nexus device
Edit, I just saw you said you can get fastboot. Use the link I posted to download your image, if you need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
Click to expand...
Click to collapse
Obviously ADB would not work in fastboot. Erasing your ROM and recovery is no where near being bricked. You get into bootloader by holding Power + Volume down. Google has not released the official image package yet so flash the stock images from these -
http://forum.xda-developers.com/showthread.php?t=2381438
http://forum.xda-developers.com/showthread.php?t=2381582

I'll try this all out in the morning. It's getting late here. Thank you and I'll be back to give you all an update!

You could even skip flashing the stock recovery and reflash TWRP. Rename it "recovery.img" put it in platform-tools... Then:
fastboot flash recovery recovery.img
TWRP should be flashed. Install a stock deodex or odex ROM and wipe data before install. Should be good.
But, everyone else's solutions will also work too (ie you are NOT bricked )
Sent from my Nexus 4 using Tapatalk 4 Beta

I need help also im trying to restore with the images but its hanging when i get to the flash system part it just sits there and i dont have a system to bootup to if i wanted to what can i do ??
Okay i guess i just had to wait a lil bit longer its finally flashing the system
Sent from my Nexus 4 using Tapatalk 4 Beta

I think I'm having some problems trying to download things in the correct folders, seeing as I don't understand most of the lingo. I used a all in one tool to unlock the bootloader and root but when I tried putting things in the folder it wouldn't load properly. I deleted everything off of my pc and I'm going to redownload everything and try again.
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.

You're just gonna have to own up and install the SDK. It only takes a few commands once it's downloaded.
http://developer.android.com/sdk/index.html
Sent from my Nexus 4 using Tapatalk 4 Beta

Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.

Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
Yea thats correct zedomax made a zip on here that only has the files u need
Sent from my Nexus 7 using Tapatalk 4 Beta

Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
+1 I didn't know somebody compiled that for the new N7. I was mostly trying to get this fellow to shy away from the toolkits - not that they're bad... But when they mess up, it's a headache to recover.
Sent from my Nexus 4 using Tapatalk 4 Beta

When I post on here I think its better to assume I'm posting to a noob rather assuming they know something they don't and making their situation more stressful. The SDK is a blanket install and you know everything is there. For someone inexperienced its better than: get this driver, and this one, and these files...move them here..you get the idea.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.

Anisak said:
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
Click to expand...
Click to collapse
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.

zeppelin101 said:
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
Click to expand...
Click to collapse
Oh disregard my last comment. I got it to work! Thank you everyone for the help!

Anisak said:
When I type fastboot devices nothing comes up. And I can't seem to unlock or lock it now. (Was testing that command)
Click to expand...
Click to collapse
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
I am also attaching fastboot drivers which I hope will work
Good luck

Hnk1 said:
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
Good luck
Click to expand...
Click to collapse
I'm on windows 7 but I did read about something about being on admin and that did the trick. Before it wasn't letting me run anything and not warning me to do so either. But I got it! Thanks to everyone for the help and advice. :victory:

[Q] HELP! Bricked

I used Freegee ( the new version) and i unlocked and installed cwmod 6.0.4.5
it was successful,
bootloader was unlocked
cwmod recovery was installed
but the problem is
when i boot my phone, it shows GOOGLE, NOT LG
my phone is LGE975
then the kernel crashes
i tried using kdz but kernel crashes too
i can only access cwmod
what should i do? i dont have files inside my phone, but the recovery files are in my computer
HELP PLEASE

additional information on the bootloader
fastbootmode
Product name - mako
VARIANT - mako 32GB
HW Version - rev11
BOOTLOADER VERSION - MAKOz10f
BASEBAND VERSION - N/A
CARRIER INFO - None (i didnt insert SIM)
SERIAL NUMBER -
Signing - Production
Scureboot enabled
lock state unlocked
if im not mistaken, mako is for google nexus 4 right?
My Phone is LGE975, not nexus 4, did freegee somehow messed the bootlader? how can i fixed this becuase this looks like the real problem here
Please help, this is the first that freegee messed up my phone i have been using freegee numerous times but this update messed it up, (i reunlocked the bootloader becuase i had to reset to factory settings)

I don't know if new freegee using nexus bootloader, but dont get alarmed.
Goto recovery and
adb push rom.zip /sdcard/0
Sent from my LG-E975 using Tapatalk
---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------
Google logo comes when you flash nexus boot loader
Sent from my LG-E975 using Tapatalk

atifsh said:
I don't know if new freegee using nexus bootloader, but dont get alarmed.
Goto recovery and
adb push rom.zip /sdcard/0
Sent from my LG-E975 using Tapatalk
---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------
Google logo comes when you flash nexus boot loader
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
ADB cannot recognize the device
i tried to push the file but
it says
error: device not found

kabeshis1923 said:
ADB cannot recognize the device
i tried to push the file but
it says
error: device not found
Click to expand...
Click to collapse
well if while in recovery adb devices show no device, fix your drivers.

atifsh said:
well if while in recovery adb devices show no device, fix your drivers.
Click to expand...
Click to collapse
IT WORKED!!! I was under the impression that i had already installed the adb drivers, but I was clearly wrong! you made me think twice! im now running on CM 10.2 and its working perfectly!. THANK YOU THANK YOU!!

simmilar problem
kabeshis1923 said:
I used Freegee ( the new version) and i unlocked and installed cwmod 6.0.4.5
it was successful,
bootloader was unlocked
cwmod recovery was installed
but the problem is
when i boot my phone, it shows GOOGLE, NOT LG
my phone is LGE975
then the kernel crashes
i tried using kdz but kernel crashes too
i can only access cwmod
what should i do? i dont have files inside my phone, but the recovery files are in my computer
HELP PLEASE
Click to expand...
Click to collapse
I have a similar problem. I have an lg optimus G e975 and wanted to instal cm10.2. I had done it before, but this time i installed RomManager and from there i flashed CWM but when i rebooted into recovery i had an error message, so i installed the recovery from the latest version of FreeGee, wich seems to have problems. It did It succesfully and I reload into recovery, but now i'm stuck in the recovery mode and I don't know what to do.
I'm kind of new in this things beccause when i did it the first time i did'nt have any trouble with the RomManager.
I dont understand what is "adb push rom.zip /sdcard/0"
Help Please!

lukatico said:
I have a similar problem. I have an lg optimus G e975 and wanted to instal cm10.2. I had done it before, but this time i installed RomManager and from there i flashed CWM but when i rebooted into recovery i had an error message, so i installed the recovery from the latest version of FreeGee, wich seems to have problems. It did It succesfully and I reload into recovery, but now i'm stuck in the recovery mode and I don't know what to do.
I'm kind of new in this things beccause when i did it the first time i did'nt have any trouble with the RomManager.
I dont understand what is "adb push rom.zip /sdcard/0"
Help Please!
Click to expand...
Click to collapse
Learn how to use adb else flash stock kdz and be happy with that.
Stay away from RomManager
Sent from my LG-E975 using Tapatalk

atifsh said:
Stay away from RomManager
Click to expand...
Click to collapse
I second that. Use it if you are an adventurous type; otherwise, steer clear.

kabeshis1923 said:
IT WORKED!!! I was under the impression that i had already installed the adb drivers, but I was clearly wrong! you made me think twice! im now running on CM 10.2 and its working perfectly!. THANK YOU THANK YOU!!
Click to expand...
Click to collapse
I have installed the USB DRIVER from the LG website, but still have the "error: device not found" message. where did you obtained the drivers?

lukatico said:
I have installed the USB DRIVER from the LG website, but still have the "error: device not found" message. where did you obtained the drivers?
Click to expand...
Click to collapse
I thought so too before, but you still haven't installed the ADB driver for your LG
Go to this link, and follow the instructions to install the drivers
http://forum.xda-developers.com/showthread.php?t=1830108
after installing the driver for ADB, connect phone and go to custom recovery
then do this command using ADB
adb push (name of rom.zip) /sdcard/0
BTW you should have the rom.zip inside the adb folder to make the command work
there lots of guides on how to use the adb push/pull function, just search the internet and refer to those.

kabeshis1923 said:
I thought so too before, but you still haven't installed the ADB driver for your LG
Go to this link, and follow the instructions to install the drivers
http://forum.xda-developers.com/showthread.php?t=1830108
after installing the driver for ADB, connect phone and go to custom recovery
then do this command using ADB
adb push (name of rom.zip) /sdcard/0
BTW you should have the rom.zip inside the adb folder to make the command work
there lots of guides on how to use the adb push/pull function, just search the internet and refer to those.
Click to expand...
Click to collapse
Thank you very much! I'ts solved! You Rock! Now the problem is that Wifi is not working, wich didn't hapend the first time I installed Cyanogenmod

[Q] Won't Boot, Won't Flash Factory Image

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

Fastboot flash always fails with "Permission denied"

So no matter what image (recovery, boot, system) I try to flash I get the same error of "Permission denied". Model ZE551ML.
I've unlocked my bootloader and previously had TWRP recovery, but while trying to upgrade to .63 by Fastboot flashing method, I got the above error and now it's soft bricked. I managed to get the stock recovery back from within TWRP, but even it won't apply signed updates (fails with Status 7). So I can't flash any of the stock images nor TWRP again, and I'm in a constant bootloop. Any help or suggestions are welcome!

Well, slight progress. It seems that even with the error message the TWRP image somehow flashed successfully, so I'm restoring my last backup now. However, I still don't understand why the other images keep failing... I will keep working on it, but still need some ideas, please.

Read through the thread started by weeset in q&a it should give you all the information you need to get things going again,
Sent from my ASUS_Z00AD using Tapatalk

jimchee said:
Read through the thread started by weeset in q&a it should give you all the information you need to get things going again,
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Well, after the backup was restored I was up and running again, so I applied the update to .59 by putting the zip on an SD card, then I took the update to .63 OTA.
However, any attempt to flash a .img file still results in the "Permission denied" failure from Fastboot. I can only flash images by the dd command in ADB or Terminal Emulator. The thread you referenced above didn't address how to fix that.

I think that your bootloader is corrupted, have you tried flashing the droidboot.img from bootloader? Only thing that makes sense, I have had no trouble flashing even after I bootlooped but your running now so point would be mute till you need to flash something again.
Sent from my ASUS_Z00AD using Tapatalk

jimchee said:
I think that your bootloader is corrupted, have you tried flashing the droidboot.img from bootloader? Only thing that makes sense, I have had no trouble flashing even after I bootlooped but your running now so point would be mute till you need to flash something again.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Flashing the droidboot.img from bootloader using Fastboot command also results in Permission denied failure:
target reported max download size of 536870912 bytes
sending 'fastboot' (14780 KB)...
OKAY [ 0.676s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.830s
Click to expand...
Click to collapse

That is odd
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
If it were my phone I would probably sideload the full .63 Rom when it is available from ASUS
Sent from my ASUS_Z00AD using Tapatalk

jimchee said:
That is odd
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
If it were my phone I would probably sideload the full .63 Rom when it is available from ASUS
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I actually sideloaded .59 before updating to .63, and that worked fine, but still getting the fastboot flash permission error before and after.
I can dd the fastboot partition with the droidboot.img just fine with no errors, so I did that with the .63 version. However, that still didn't resolve the fastboot flashing error.

I have the same "permission denied" error with fastboot, and my bootloader is NOT unlocked. Searching around on google I found other people reported the same error on different phones, but none of the suggestions, such as "fastboot erase cache" changed anything for me.
It still mostly works, though. I can boot into TWRP tethered from fastboot, and at one point I flashed an older version of the stock recovery from fastboot. It gave the error, but worked. I was not able to flash the full OS image from fastboot. I had to go into stock recovery and sideload it.

I don't have any idea what's causing that error I haven't been able to duplicate it on my phone at all, the only flashing error I encountered do far was with sideloading because I was using an older version of adb and fastboot. So I am stumped I can maybe find a phone with this problem near me and work on it myself.
Sent from my ASUS_Z00AD using Tapatalk

If I remember correctly you need to use the latest fastboot and this error is caused by not using proper fastboot

this is quite strange - i get the same error, but the action actually takes place...

I have the exact the same problem. Small procedures will work fine, but anything large like flashing system.IMG will actually fail. This has been bothering me a lot and it seems more and more people have it now so its an actual problem.

Okay that makes sense regarding the version of fastboot,
This is latest version
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
Sent from my ASUS_Z00AD using Tapatalk

jimchee said:
Okay that makes sense regarding the version of fastboot,
This is latest version
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Did using that version of fast boot solve the issue?
I had a near panic attack yesterday when I soft bricked my zf and couldn't flash anything using softboot.
Thank god regular recovery worked but I still prefer to have a working fast boot.

jimchee said:
Okay that makes sense regarding the version of fastboot,
This is latest version
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
maxlifan said:
Did using that version of fast boot solve the issue?
Click to expand...
Click to collapse
No, that version gives the same error for me. I also get the error using the latest version downloaded from Google through the Android SDK on Linux.
I don't know how to debug anything on while in fastboot mode, but if anybody can point me to some information I can try and figure out what's happening.
The bootloader/fastboot screen shows:
Code:
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - 0094.0177
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
That is exactly what it shows, including the fake serial number. I don't remember what the bootloader said before the error started. It might have been the exact same thing. I have tried flashing a new bootloader, but of course that gives the same error, so I don't know if it's working or not.

That's normal for the bootloader screen not sure why it doesn't read properly, funny cause my Nexus 7 2012 actually reads properly in bootloader
Sent from my ASUS_Z00AD using Tapatalk

1) Try using a different USB Cable. Sounds silly, but I've had all kind of funky problems in the past, and sometimes the USB Cable is the problem.
2) Use a different PC/fastboot Setup.
If it works on a different PC then you know something is wrong with your drivers/Fastboot environment.

Shad0wKn1ght93 said:
1) Try using a different USB Cable. Sounds silly, but I've had all kind of funky problems in the past, and sometimes the USB Cable is the problem.
2) Use a different PC/fastboot Setup.
If it works on a different PC then you know something is wrong with your drivers/Fastboot environment.
Click to expand...
Click to collapse
I've tried on my work and home computers (Linux), from Windows (using the binaries linked earlier in this thread), and from a Mac. I tried a few different USB cables at home plus the one at work. I appreciate the suggestions, because it's always possible that those of us with this problem are making the same easy mistake..
Because the error is "remote: permission denied" (or something like that) my guess is that it's a response from the phone. I just don't know anything about the technical details of the bootloader to start debugging it. Does anybody know what filesystems are mounted in the bootloader? Are they purely memory resident, or is it actually mounting something in flash that could be corrupted?

I personally think our fast boot is broke. Or corrupt. Is there a way to flash fast boot with stock recovery or without unlocking boot loader? Or flashing using ADB?

Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm

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 ?