yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] PieceofSlice:
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?
[Nexus 7 (2013) Q&A] vparres:
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 :

fastboot flash bootloader bootloader-deb-04.02.img

and

fastboot -w update image-razorg-kot49h.zip

And for the Razor / flo (Wifi version) it will be :

fastboot flash bootloader bootloader-flo-flo-04.02.img

and

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 :D

But don't forget to install drivers, except if you already do this step :D

I hope i helped you.
[Nexus 7 (2013) Q&A] tetakpatak:
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?
[Nexus 7 (2013) Q&A] droidshadow:
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
[Nexus 7 (2013) Q&A] PieceofSlice:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...

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?
[Nexus 7 (2013) Q&A] tetakpatak:
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?

fastboot reboot-bootloader

tetakpatalked from Nexus 7
[Nexus 7 (2013) Q&A] Babaloe:
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..
[Nexus 7 (2013) Q&A] PieceofSlice:
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 :)
[Nexus 7 (2013) Q&A] tetakpatak:
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
[Nexus 7 (2013) Q&A] droidshadow:
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://xdaforums.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
[Nexus 7 (2013) Q&A] tetakpatak:
LOL, good point [MENTION=5032014]droidshadow[/MENTION]!

Hey, [MENTION=5511151]PieceofSlice[/MENTION], 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
[Nexus 7 (2013) Q&A] PieceofSlice:
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;)
[Nexus 7 (2013) Q&A] PieceofSlice:
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

C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found

So I take it I have a problem with ADB or something?
[Nexus 7 (2013) Q&A] tetakpatak:
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)

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.

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
[Nexus 7 (2013) Q&A] PieceofSlice:
Thank you. The top part was very helpful, and I now understand :) I was trying to erase the boot because the tutorial by [MENTION=5527754]codemonkey98[/MENTION] prompted me to... So when doing the commands you've instructed, do I just do "fastboot erase all" to start? Do you have the actual code? :silly::o
[Nexus 7 (2013) Q&A] tetakpatak:
You're welcome, mate :)

Hiting the "thanks" button would be very appreciated if you find my posts helpful.

As I really prefer to flash manually instead of "flash all" stuff, tools etc, I also recommend it:

so, on your place, I would follow the workflow from this guide for nakasi/g (Nexus 7 2012) and just flash the files for your device and use proper file names:

http://xdaforums.com/showthread.php?t=1907796

(I'm the guy who made the video of the workflow)

:D

tetakpatalked from Nexus 7
[Nexus 7 (2013) Q&A] droidshadow:
status?....

So did he fix his issue?

I am want to that the guy is okay!

-droidshadow
[Nexus 7 (2013) Q&A] PieceofSlice:
So when I tried to do this, "fastboot reboot-bootloader" I got another error. Though I'm pretty sure it worked the other day :/

C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot

C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s

I'm almost positive I have all of the files in the right place, and I also updated the SDK...

Also, I had another question. So do you think I should use the command below? It says to do so in the flashing guide.

fastboot erase boot
[Nexus 7 (2013) Q&A] tetakpatak:
[MENTION=5511151]PieceofSlice[/MENTION] it is an unusual error. I would feel better to continue after we can execute this command. Don't use USB 3 for this (only USB 2 or 1). Also definitely try another port. Did you update your google driver to the recent version? The folder with google driver is in your SDK folder. You can find it also separately to download.

As plan B, you could flash a custom recovery like PhilZ or TWRP and wipe all and format data. Maybe fastboot commands will work then....or flash some ROM as zip in the recovery.

Please try to get the fastboot command working, it would be really good. Of course, you could reboot bootloader also mamually (power off, booting with buttons into bootloader mode) but we can't use any error by flashing the bootloader!

Which bootloader version is installed now? Read a bit through that thread by comminus, he has answered many troubleshooting questions there. Maybe you find the answer :)

Yes, this command will erase your kernel. After erasing kernel, userdata, system etc flashing new image on the clean device is very clean install method.

tetakpatalked from Nexus 7
[Nexus 7 (2013) Q&A] droidshadow:
bootloader unlocked?

Okay these errors -> FAILED (command write failed (Unknown error))

are usually associated with a locked bootloader or you need to use a different usb port. Tetakpatak made a good point, are you using usb2 or usb3? Which usb cable are you using? Are you using the stock usb cable that came with your nexus 7 charger? Now i know that you said that you *think* you unlocked your bootloader but maybe did you happen to relock the bootloader or did maybe you never did unlock the bootloader?

Do you remember when you unlocked your bootloader that a message on tablet came up saying you may void your warranty and you have manually swipe on the bottom of the tablet to unlock your bootloader...

Did you do the swipe?

I think you should try unlocking the bootloader again and then make sure your drivers are up to date and that you have the latest SDK package and go from there...

Also tetakpatak is right, most of the times those unknown errors can be solved simply by switching to another usb port...

-droidshadow
[Nexus 7 (2013) Q&A] PieceofSlice:
Well, I got the "fastboot reboot-bootloader" to work... once. When I try it now, it will come up with the same error. I've tried all of your guys' advice, and nothing has worked. I've changed USB ports, and I have all of the drivers installed correctly. I have tried researching for an answer and it seems like it's just an "operator error" but I'm almost positive I'm doing everything right. My bootloader is unlocked and it is version FLO-4.01. I'm using the stock cable too... I don't get why it would work once and then not work anymore..? :confused::eek:
[Nexus 7 (2013) Q&A] tetakpatak:
Such a nasty thing. I am getting ever more angry on this stupid, stupid Windows and its money making on this crappy, idiotic OS! :mad: I kind of suspect some PC configuration, or mod for causing the connection problems. I have seen it and faced it often enough in my life.

I don't know what to recommend you to do now. I know exactly what would I do: install Ubuntu and run fastboot from there. Linux has no problems as it needs no drivers. But I don't recommend you to do so, as if you have never used it yet, it will cost you time to learn how all that works until you can execute fastboot from there.

:(

Maybe you can find somewhere (or you own yourself) an old notebook with 32-bit Win XP installed? In my personal experience, they have aproven to be the most reliable PCs for Android flashing jobs. No matter if Samsung and Odin, HTC, LG, Nexus or whatever....they just flash and flash and seldom they fail (fortunatelly, I have one such at home)

P.S. [MENTION=5032014]droidshadow[/MENTION], mate, you are really such friendly person IMHO :)

tetakpatalked from P5110
[Nexus 7 (2013) Q&A] droidshadow:
fastboot manually?...

What happens when you try booting into fastboot manually with the Volume Buttons and Power button?

If possible could you take a picture of what fastboot looks like and upload it here on XDA or a plage like imugr.com and link us to it.

PS. [MENTION=5051515]tetakpatak[/MENTION] thank you so much brother.

-droidshadow
[Nexus 7 (2013) Q&A] tetakpatak:
He can do that, mate, but he will still need fastboot working to flash stock ROM successfully. I could swear his problems are related to the drivers.

BTW, great idea! [MENTION=5511151]PieceofSlice[/MENTION] should make a photo of his N7 screen after turning it manually into bootloader mode, who knows, maybe we discover something there!

tetakpatalked from Nexus 7
[Nexus 7 (2013) Q&A] deadgiveaway:
Install the generic pda.net drivers ....once i did this no problem running commands from windows 8 ...
[Nexus 7 (2013) Q&A] PieceofSlice:
Well, for the time being, fastboot seems to be working... :o:victory::silly: However, when I try to send commands this is what happens,

Any ideas on why it's doing this?
[Nexus 7 (2013) Q&A] tetakpatak:
At least it starts to work. Does the command "fastboot reboot-bootloader" gets executed?

If yes, now is good point to try another USB cable or USB port.

Please give us feedback.

tetakpatalked from the legendary i9000
[Nexus 7 (2013) Q&A] PieceofSlice:
I just tried to do a flash-all.bat command in the "platform-tools" section, and this is what happened... Also, I have the flo-4.02 bootloader version in the folder with the KOT49H image.

EDIT: I kind of don't want to touch it because I don't wanna mess it up :p But I am using the stock factory cord.

EDIT: Instead of the KOT49H files, I put the 4.4 KRT16S files in the platform-tools folder instead to match the bootloader version on my tablet. Here's what I got,

C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot

C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s

C:\android-sdk\platform-tools>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.01
Baseband Version.....: none
Serial Number........: 04988e98
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7014 KB)...
OKAY [ 0.240s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.163s
Press any key to exit...
[Nexus 7 (2013) Q&A] tetakpatak:
Mate, it looks ever more promissing- though without flashing a compatible bootloader it is normal that the image won't be flashed. (that warning "....doesn't contain....bla bla .sig" is normal)

Wait a minute, do you know which ROM this 4.02 bootloader belongs to?

If I consider by its version number that it could belong to the first released KK factory image, the 4.4!

Can you download that image and if it matches, try to flash that one? Could finally work!

tetakpatalked from the legendary i9000
[Nexus 7 (2013) Q&A] PieceofSlice:
The 4.02 bootloader is in the 4.4.2 KOT49H OS. I'll try what you said and download/ flash the first 4.4 OS. It's weird it's not on the official Google factory image site, but I'll get it from somewhere else though. Let's hope it works:rolleyes::)
[Nexus 7 (2013) Q&A] tetakpatak:
I'm sure you will find it.

But please answer my question if "fastboot reboot-bootloader" command works as it should?

tetakpatalked from P5110
[Nexus 7 (2013) Q&A] PieceofSlice:
Yup, I've found it and it's now downloading. Sorry for not answering your question,"fastboot reboot-bootloader" works fine now. I think what was happening is that after I tried one way of flashing it, it would forget it's in fastboot mode - or something along those lines. I think I figured out I need to manually put it into fastboot mode after each attempt..
[Nexus 7 (2013) Q&A] tetakpatak:
Hey, cool mate :)

So, we have at least growing chances it could work with flashing a compatible factory image.

Honestly, I still kind of fail to understand why it doesn't flash another bootloader.... ???

But let us try to flash now 4.4 factory image. When you unzip the package, you will see bootloader version and big zip file of the factory image. If the bootloader version number matches yours, we will try it this way:

> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata (this would totally erase all your data....you can try also without this command, simply skip this step, but if the flashing will be successful and the device stilldoesn't boot, I fear you will have to repeat this procedure WITH THIS STEP)
> fastboot -w update image-(rest of the file name).zip

tetakpatalked from P5110
[Nexus 7 (2013) Q&A] PieceofSlice:
So the KRT160 download finished, but the bootloader versions do not match. The one in the download is flo-03.14 and the one on my tablet is flo-04.01... Also, when I put the files in "platform-tools" and did "fastboot erase boot" it just froze on "erasing boot"...
[Nexus 7 (2013) Q&A] tetakpatak:
Oh, damn it.... really very frustrating.

Please try to update your USB driver, there is a folder in your new SDK, did you try already?

OK, then regarding bootloader it must be the 4.4.1 image! Actually if the bootloader version diesn't match the ROM, all tries will be in vain.

But just from my "stomach feeling" I really suspect very strongly that all problems still come from the drivers. Please try again, after updating drivers no matter which factory image, with its delivered bootloader (why not this 4.4 image) now this way:

> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader (nameofyourbootloader).img
> fastboot reboot-bootloader
> fastboot -w update image-(rest of the file name).zip

P.S. I think you never wrote: do you have flo or deb? This command is for flo update, deb needs also radio flasing and additional reboot.....

tetakpatalked from N7100
[Nexus 7 (2013) Q&A] PieceofSlice:
Your talking about updating the Google Driver, right? I've already done that through the SDK updater. So then I should try downloading the 4.4.1 KOT49E image, and try that? Oh, and I have the flo.
[Nexus 7 (2013) Q&A] tetakpatak:
Yes.... please try.

I am really confused why it doesn't work so far, it actually really should.... :(

tetakpatalked from N7100
[Nexus 7 (2013) Q&A] PieceofSlice:
Also, do you have a link to the 4.4.1 image, because I can't seem to find one. The couple I've tried are only about 50mb... :confused:
[Nexus 7 (2013) Q&A] tetakpatak:
This is what I have...but I don't see it here:

https://developers.google.com/android/nexus/images#razor

Mate, we can't exclude the possibility that your internal memory is corrupted and nothing works therefore. Did you try if you can lock the bootloader? If you still have guarantee, I think if flashing a factory image diesn't work at all, maybe you should simply lock the bootloader and request another device, or repair of yours.

It is not excluded, that the internal memory is really somehow buggy here. When I have u locked my bootloader, (Flo) the first thing that happened was that my whole /data partition got corrupted and couldn't boot anymore. I have formatted it and unbricked the bootloop.

Short after that I flashed SlimBean 4.3 as I really liked how my N7 works on the latest JB. But after about a week, my Tab one day simply didn't boot anymore, it bootlooped on the SlimBean boot animation. Then I have flashed factory 4.4.2 and right after that Carbon Rom. Now it seems to work stable since.

Strange, huh?

tetakpatalked from P5110
[Nexus 7 (2013) Q&A] PieceofSlice:
Hmm, I see... I can't really seem to find a 4.4.1 download. I think it might be because it was just an OTA patch. I hope my tablet's not busted:eek: I might be able to lock the bootloader, but I bought it used and I doubt it's under any warranty. I know the guy bought it from Best Buy, but I doubt they'd let me return it without any receipt.
[Nexus 7 (2013) Q&A] tetakpatak:
Without receipt, it will be difficult. Can you ask guy you bought it from if he still has it?

Well, give another try and if it doesn't work, the solution could be to try from another PC, Linux or Win XP 32-bit.

If really nothing helps, the service should be able to fix it without bigger problems. It will cost few $ but I consider it to be worth to invest for such a great device.

Yet, I really suspect problem in the drivers.

tetakpatalked from Nexus 7
[Nexus 7 (2013) Q&A] PieceofSlice:
What is your opinion on WugFresh, should I try the toolkit? I've tried already, but haven't been having much luck either. I know there is an option where you can 'force flash' though. Here's what it'll say after I try to flash KRT16S 4.4, notice the bottom...

checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7014 KB)...
OKAY [ 0.233s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.129s

Booting up your freshly flashed stock device...
------------------------------------------------------------------

Wait for your device to finish booting up...

- It may appear to be boot looping; just wait...

- It could take 5-10 minutes; please be patient...

When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.

NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
[Nexus 7 (2013) Q&A] droidshadow:
windows version?...

Is he using windows 8? I know that there are problems with windows 8 + adb/fastboot.

If you are using windows 8 then i would suggest you install the pdanet drivers as someone suggested earlier...

Again if you are on windows 8 is it possible for you to try this whole process on a windows 7 or windows XP/Vista computer? Or even better...could this be tried on a Linux based computer?

With the pictures you have taken (thank you by the way it will help) it seems that adb is processing the commands but unable to transfer or write data.

I would like to see a picture of you booting into fastboot/download mode. I still want to confirm 100% that your bootloader is unlocked.

Are you trying this whole process on a laptop or a big tower desktop style computer?...

If you are using a big desktop computer try using the usb ports on the back of your computer...i know it sounds dumb but it might actually work, assuming you are on windows 7 if you are on windows 8 then we need to work on the drivers,

Don't give up we'll get this figured out!

-droidshadow
[Nexus 7 (2013) Q&A] PieceofSlice:
I'm on Windows 7, and I'm using a tower desktop. I'll try the rear USB ports and see what happens. Here is a picture of the tablet in fastboot mode,

EDIT: The rear USB port didn't work either, the same error occurred.
[Nexus 7 (2013) Q&A] droidshadow:
secure boot enabled?...

I don't have my tablet next to me to boot into download mode to compare but with an unlocked bootloader shouldn't secure boot be disabled?

Or does secure boot enabled have to do with the boot (kernel) and "secure boot enabled" just means the kernel is protected...i forget!

Could this be the problem?...

Definitely try the usb ports on the rear of your tower, that could definitely be your problem!

-droidshadow
[Nexus 7 (2013) Q&A] PieceofSlice:
I'm not quite sure, lol. And the rear USB ports didn't work either, I got the same errors. :rolleyes: