Develop Bugs

Trying to use ADB to flash_image on Desire Z

Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?

You get that error from which of those commands ?

From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?

Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?

Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App

I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?

steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.

Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>

Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.

I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.

Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.

steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?

Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?

Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.

steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.

[Q] I'm worried I killed my phone

I decided earlier today that I'd try to root my one X, but I wound up screwing up to the point that I'm lost. I accidentally wiped the system while in recovery, and when I rebooted, it kept looping. By pressing the power/down button, I can get into the bootloader, and from there into recovery. In the recovery, I was able to look around using a file manager but only found empty folders.
I used adb push to try to get a rom onto the phone, but I'm not able to flash it. When I go to reboot, it informs me that there's no OS installed.
If anybody has any idea what I can do, it would be much appreciated.

im assuming you already unlocked your phone
1.Enter fastboot by holding power + volm down.
2.Select fastboot
3.plug in USB
4.flash recovery with the command: 'fastboot flash recovery <name of recovery here>
5.flash the boot.img that came with the ROM, usually it's located within the zip file
6.erase cache using command: 'fastboot erase cache'
7.select Hboot to return to main menu
8. go to recovery
9. wipe data/factory reset, wipe cache, wipe dalvik from advanced options, format system from mounts and storage menu
10. in mounts and storage, select mount usb
11. copy over ROM zip
12. Install from ZIP
13. reboot system
PS. your phone is only bricked if it can't turn on. obviously it's not going to boot up if there is nothing to bootup, lol

Just ensure your recovery is a recent version, like clockworkmod 5.8.4.0, otherwise mounting won't work.

Thanks for the quick reply. I don't entirely understand how to flash the recovery, however.
I assume I'm running the command on the computer. How do I know what to type in as the recovery?

Mate, did you even do your research before attempting any of this?
Anyway,
Make sure you got HTC sync installed, also Android SDK
1/ Open to a command prompt by going: start -> type in cmd
2/ browse to your folder containing fastboot and adb using the 'cd' command
e.g. My fastboot folder is located at "C:/htc/fastboot" so I would type: 'cd C:/htc/fastboot'
If you're using the one from SDK it could look like C:\Users\Steven\AppData\Local\Android\android-sdk\platform-tools
3/ enter the commands -fastboot flash recovery ...., fastboot flash boot.... etc.

Not nearly as well as I should have. I learned the hard way I guess. Thanks for putting up with my cluelessness though.
I've done as you said, but when I tried to boot into the recovery, I got stuck on it looping the "htc quietly brilliant" screen.

You sure you flashed it Successfully?
and downloaded clockworkmod from here?
http://forum.xda-developers.com/showthread.php?t=1594819

Code:
D:\Android>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
< waiting for device >
sending 'recovery' (5742 KB)... OKAY [ 1.021s]
writing 'recovery'... OKAY [ 1.506s]
finished. total time: 2.528s
D:\Android>fastboot flash boot boot.img
sending 'boot' (4988 KB)... OKAY [ 0.885s]
writing 'boot'... OKAY [ 1.257s]
finished. total time: 2.142s
D:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.116s]
finished. total time: 0.116s
Could it be that I have a bad boot.img? I'm using one out of the renovate 8.1.0 ROM.

I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?

seaneschen said:
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
Click to expand...
Click to collapse
what command are doing? to unlock i mean
or better yet run through the steps u do to unlock bootloader

ali3nfr3ak said:
what command are doing? to unlock i mean
Click to expand...
Click to collapse
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev

seaneschen said:
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
Click to expand...
Click to collapse
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2

elmonen said:
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I have the US version.

seaneschen said:
I have the US version.
Click to expand...
Click to collapse
i would suggest that you post this in the in the AT&T, Rogers HTC One X, Telstra One XL forum as thiforum is for the international one x

Oh my....... never noticed. Please don't use Clockworkmod and instead use TWRP, you might brick

Toolkit Rooting Question FAILInvalid Command"

I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick

put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058

I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.

is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img

It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.

waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2

I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?

crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.

/sdcard not mounting

dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard

Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app

1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?

Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????

amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!

zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.

zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse

Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance

zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread

samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks

just do this: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening

*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus

[Q] Nexus 7 2013 Problems...

A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!

I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Any other suggestions..?

Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...

PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?

that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?

PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7

Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..

tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later

PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7

i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow

LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?

There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7