yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] Zenemon:
Hi there. Having some trouble, hoping nothing serious. Read the guide twice and even went through the first 20 pages on this thread to see if any extra notes could be made.

Basically, let me start off by asking if its a problem installing google usb driver for nexus 7 v1 instead of the asus driver? I used the google driver that came with sdk tools and since everything seemed to work, i proceeded with command prompts.

2) When you extract bootloader-grouper-4.23.img, image-nakasi-jwr66v.zip, flash-all.sh, flash-base.sh to sdk platform tools, there is an omitted fifth file (.dat file). Should that not be included with everything else?

3) Heres where my actual problem seems to start.

Where your told to " fastboot flash bootloader bootloader-grouper-4.23.img" I get this error message:

Failed (remote: (invalid state)

4) Now the invalid state error seems connected to next command "fastboot -w update image-nakasi-jwr66v.zip" ( i had to rename to jwr66y.zip as thats what the zip file was called)

which resulted in this message:

"archive does not contain boot sig

archive does not contain recovery sig

not contain system.sig

bootloader version 4.18

baseband na

serial number ......

checking product...

checking version bootloader

failed

device version bootloader is 4.18

update requires 4.23

finished total time 0.210s

Not sure why this is happening because im 99% sure that followed commands to the letter. Seems tied up with bootloader not updating.

Ive really committed here and kind of sweating at this point :s
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Everyone has been reporting that the 4.23 bootloader from nakasi build JWR66Y is not flashing. The bootloader from JWR66V is also 4.23 and I've posted it to Google Drive.

bootloader-grouper-4.23.img.gz

Just decompress it and flash normally

fastboot flash bootloader bootloader-grouper-4.23.img
[Nexus 7 Q&A, Help & Troubleshooting] Zenemon:
Hi Comminus.

Thanks for the prompt reply. Im off to bed (been at this for 6hrs) so havent had a chance to follow through with your link yet.

However, having read more of this thread (40page now lol) got an idea indirectly and decided to install jdq39 (4.2.2) again with bootloader 4.18.

Worked flawlessly.

Will definitely update or reply again tomorrow with fresh attempts at 4.3.

Happened to see you mention around page 25-27 that your were considering creating a guide without use of sdk tools. Im definitely interested.

Part of that is because i didnt really want to install Java. Your guide is very well written but im surprised that google haven't simplified the process

via some stand-a-lone software udate tool.
[Nexus 7 Q&A, Help & Troubleshooting] josephstc9:
if this tutorial is geared towards people who are beginners and can't do it them selves, then why the hell am I so confused? NOT basic step by step instructions. Pisses me off.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
To be fair, it's pretty difficult to help people who only post complaints. Try being more constructive by defining specifically what you're having difficulty with and I might be able to offer some insight.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] josephstc9:
sorry about that. I'm just angry. first off, i'm having to fix stuff google screwed up with 4.2.2. Let me explain, a few months ago, i was in the market for a tablet, I decided on a nexus 7 2012. I knew the next gen one was coming out in a month, but i didn't care, i wanted a tablet, you know how it is. What I didn't know at the time was that a very large number of the nexus 7s running 4.2.2 had insane lag, mine was one of those devices. I rooted the stupid thing right after i got it, thinking that would help me out. Big mistake. Because then i hear that 4.3 fixes the lag almost in its entirety. Well at that point i'm running AOKP. And i read an article that said generally if it's the same brand of custom rom, 99%, it's ok to do a "dirty flash" and just install over the old version. I either did something wrong, which is likely, or i was the other 1%. Either way, all i have access to is the bootloader. So anyways, any help would be IMMENSELY appreciated. Because i sure as hell don't know what i'm doing.

Thanks.

Three months with this thing has made me very crazy. Again i'm sorry for ranting. Should have bought an iPad, jailbreaks have gotten a lot simpler as time has passed.

Thanks.:fingers-crossed:
[Nexus 7 Q&A, Help & Troubleshooting] smokedkill:
I'm trying to go back to stock on the Nexus 7 (2012) wifi edition. I get to "fastboot flash bootloader bootloader-grouper-4.23.img" then when its writing the bootloader it says "FAILED <remote: <InvalidState>>"

Any help would be appreciated. I'm new to the nexus world as I bought my Nexus 7 used about a month ago.

---------- Post added at 03:39 AM ---------- Previous post was at 03:20 AM ----------

Thank you. After reading through pages and pages for an answer to a solution, little did I realize that it would be on the second to last page. I guess I should have went backwards instead before posting. My problem is solved. Thank you
[Nexus 7 Q&A, Help & Troubleshooting] Zenemon:
Same for me, worked after using updated bootloader! Cheers comminus. Got some questions/suggestions regarding some of the guides process.

Questions:

1) Java se jdk - during installation, can u disable "source code" and "public jre". Just need the dev tools, right?

2) In platform tools, can i re-use flash-all.sh, flash-base.sh files for each upgrade or do these need to be changed each time?

a) Is it also ok to leave multiple revisions of boot-loader and android image files in platform folder. No conflict issues? I know you point to files in

command prompts but just wanted to be sure.

b) In sdk manager, should i be updating the packages and google driver upon each new android release?

Suggestions:

1) Had to install 32bit version of java on top of the 64bit when SDK tools couldn't locate the 64bit version. Would save a little time for those of us not in the know

2) Not essential but it created doubt in my mind. Under "driver installation" i wish it was made more clear that you need to use the oem driver

for your device. Somehow i ended up pointing the nexus 7v1 to the google driver in platform tools. Actually worked but this is still contrary to

"Note: If your device is one of the Android Developer Phones (ADP), a Nexus One, or a Nexus S, then you need the Google USB Driver, instead of an OEM driver. The Galaxy Nexus driver, however, is distributed by Samsung (listed as model SCH-I515).

3) In the same section regarding "Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2)" ...this caused some initial confusion. Where it says (see#2) i thought u were referring back to instructions about oem adb drivers. For those not familiar with command prompts, shouldnt it be something like (see image below) with an additional note

that makes readers following guide that "user name" refers to their pc's given name.

4) Although driver conflict or lack of is one of the biggest reasons people have problems when using this guide, its little details like above or

a non functioning boot-loader can also stop you right in your tracks. Would be great if guide could be updated to reflect this, if there actually

considered valid points.

Its a really great guide dude and although it i got past some of these minor hurdles through trial and error, a lot of time was used up in process where some uncertainty set in. I think its great that you want people to better understand the process of whats going on but if there anything like me, i just want transparency and **** to work lol. In 2 weeks from now, i ll forget most of this stuff.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
[MENTION=5185331]Zenemon[/MENTION], thanks for the feedback - all points are valid. Driver hell is a particularly difficult issue in Windows to resolve. I'm hoping the path I've chosen for the next version of the guide will mitigate this issue enough so that it's no longer as big an issue. I'm actually nearly done the second version of the guide, I'm just getting some additional eyes on it for review before I post it. But I can tell you there is no Java or Android SDK setup in the new guide :)
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Sorry about the huge delay in responding. "Dirty flashing" between AOKP and stock or any other rom is never a good idea. Sometimes it's appears to work out, but it can create a lot of issues that are not always obvious. Rule of thumb: switching between different roms means formatting your data.

If you're still at the same place, having access to fastboot, you'll need to get the drivers installed and tools downloaded so you can flash the factory image. Let me know if this is the case and I'll assist you further.
[Nexus 7 Q&A, Help & Troubleshooting] Titankahn:
when i write > fastboot flash bootloader bootloader-grouper-4.23.img i get signature mismatch what is the problem?
[Nexus 7 Q&A, Help & Troubleshooting] Dsummers125:
I got everything down perfectly up to part three, where it is supposed to list my devices' serial number in the command prompt. But all it does is say "List of devices attached" and that's it. There is no list of devices after that even if my Nexus 7 is plugged in. Please tell me how I should proceed after that;

My device probably has usb debugging enabled but at the moment it's softbricked so I can't get pass the google screen to enable it if it isn't. I am uncertain because I accidentally formatted my Nexus 7 and I don't know if they would have reverted it from enabled to disabled.

Or if it's a problem with my drivers, I may need assistance as to what I would have to download.

Edit: It says my Drivers are up to date, I downloaded the ones provided here.

Edit2: In my Command prompt it says, before telling me List of devices attached:

*daemon not running. starting it now on port 5037*

*daemon started successfully*

I don't know if that helps or not.

LAST EDIT: SOLVED!

"When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus. Not exactly obvious why, but I you select the second option "Camera (PTP)" the device is available for debugging. This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise"
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
[MENTION=4094003]Titankahn[/MENTION], the bootloader in the JWR66Y factory image has.. an issue. Replace the one from that factory image with the bootloader from JWR66V.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
MTP and PTP do not matter as long as usb debugging is enabled, and in Android 4.3 you need to provide permission to the computer when attempting an ADB connection. Regardless, the most important thing is that your device is visible to fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] hoopre:
Hi guys,

Please help, i cannot upgrade to 4.3 jwr66y (from 4.3 jwr66v). I even did formated my device to fully stock rom, stock recovery, and unrooted it.

When device restart and attemp install ota update, then image of android laying on its back with red triangle appeared and show ERROR status.

I also tried to FLASH STOCK + UNROOT through nexus root toolkit but nothing happen (the screen stay on fastboot mode without anything happen).
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Ota updates fail because of modified system files, build.prop, kernel, etc.

I posted a solution for this 1 or 2 pages back. http://xdaforums.com/showpost.php?p=45182222&postcount=464

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] Zenemon:
[MENTION=4194102]comminus[/MENTION] Looking forward to the new guide. Wont forget this one as i finally overcame the curse of command prompts. For us lays, flashing factory image via java/sdk and succeeding, is a rite of passage lol.
[Nexus 7 Q&A, Help & Troubleshooting] UltraXUX:
Good work!
[Nexus 7 Q&A, Help & Troubleshooting] GeoffK:
Problem flashing to android 4.3 factory image bootloader failed

have not succeeded. Please see below

How do I fix the bootloader problem

checking version-bootloader… FAILED

Device version-bootloader is ’3.34′.

Update requires ’4.23′.

------------------------------------------------------------------

flash-all.bat

…

(bootloader) Bootloader is already unlocked

OKAY [ 0.020s]

finished. total time: 0.020s

erasing ‘boot’…

OKAY [ 0.023s]

finished. total time: 0.023s

******** Did you mean to fastboot format this partition?

erasing ‘cache’…

OKAY [ 0.045s]

finished. total time: 0.045s

erasing ‘recovery’…

OKAY [ 0.023s]

finished. total time: 0.023s

******** Did you mean to fastboot format this partition?

erasing ‘system’…

OKAY [ 0.050s]

finished. total time: 0.051s

******** Did you mean to fastboot format this partition?

erasing ‘userdata’…

OKAY [ 0.984s]

finished. total time: 0.984s

sending ‘bootloader’ (2100 KB)…

OKAY [ 0.280s]

writing ‘bootloader’…

FAILED (remote: (InvalidState))

finished. total time: 0.408s

rebooting into bootloader…

FAILED (command write failed (No such file or directory))

finished. total time: -0.000s

archive does not contain ‘boot.sig’

archive does not contain ‘recovery.sig’

archive does not contain ‘system.sig’

——————————————–

Bootloader Version…: 3.34

Baseband Version…..: N/A

Serial Number……..: 0

——————————————–

checking product…

OKAY [ 0.020s]

checking version-bootloader…

FAILED

Device version-bootloader is ’3.34′.

Update requires ’4.23′.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
[MENTION=5431139]GeoffK[/MENTION] - Welcome to XDA.

On the first page of this thread, in the first post, at the very beginning, in bold red you'll see this:

Notice: If you are going to flash the nakasi android 4.3 JWR66Y factory image, you will need to download the bootloader from JWR66V and replace the one from the factory image. The bootloader in JWR66Y will fail flashing with a signature mismatch error on the device and InvalidState on fastboot.

Follow the link and download the 4.23 bootloader. Decompress it and replace the copy in the directory where you extracted the JWR66Y factory image.
[Nexus 7 Q&A, Help & Troubleshooting] :
Flashing to stock problem

I sent my N7 into a bootloop, so I tried flashing it back to stock. It is stuck on erasing user data, and I'm not sure where to proceed from here.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Try a different USB port and try formatting user data.

fastboot format userdata
[Nexus 7 Q&A, Help & Troubleshooting] :
I looked around a bit, and recovery can't even mount /data. Is there any way to fix that?
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
It wasn't clear in your last message if you tried using a different usb port or formatting the userdata partition. The mount issue could be related to the erase command failing or it could be caused by it. Either way, trythe format command.
[Nexus 7 Q&A, Help & Troubleshooting] :
I did try it, and with amother port. I waited about 2 hours and the format command still hasn't deleted my userdata.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Definitely shouldn't take that long. A couple more things you can try:

1. Make sure you're using the most recent version of fastboot (included in platform-tools r18.0.1)

2. Try the universal naked driver

3. Use a different computer.
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
I'm having issues with my Nexus 3G (4.3). I wanted to unroot it so I could sell it and used the Nexus Toolkit, following the directions and all went well until it came time for the tablet to reboot. Nothing. I tried deleting the cache and doing a factory reset and you all know what's happened. I' about 6 hours deep with reading and trying different methods and it seems yours may be my last hope - I panicked when I was reading through another thread on xda and the last guy who was having this problem ended up hard bricked - hence why I'm trying your method.

I downloaded jwr66y and have the bootloader-grouper downloaded. I've installed Java, SDK and have the usb drivers downloaded. It's the drivers section that has me stumped.

When I open cmd and run "adb devices" nothing comes up. I tried "adb reboot-bootloader" but no devices are found.

It's hanging on the google logo with the green start arrow and "booting failed" but I've also tried it from the bootloader menu.

When I search for it in device manager it comes up as "google nexus 7 bootloader interface" and says that the drivers are up to date.

I'm worried that the battery will die as I can't turn it off, it just restarts to the same stage. I've tried putting it into bootloader also, but nothing.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Don't worry about adb at this point. Sounds like you're in fastboot mode - it should say so on the screen someplace. If you're not in fastboot mode, power off the device. Once its off, press and hold Volume Down, then press and hold Power. Welcome to fastboot mode.

Concentrate your efforts on fastboot. Start from step 5 under driver installation. Run the command:

fastboot devices

you should be able to see your devices serial number.

If this is working, continue the guide. Let me know if you run in to trouble.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
Thanks for the quick reply! I'll try it now and post how I get on....

---------- Post added at 08:32 PM ---------- Previous post was at 08:27 PM ----------

It seems I'm in "driver hell". :(

I made sure it was in fastboot (says so on the screen) skipped to step 5, copied the cmd prompt "fastboot devices" and got-

'fastboot' is not recognized as an internal or external command, operable program or batch file.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
You just need to locate the fastboot executable. If you've installed the SDK, it will be in the platform-tools directory in your SDK directory.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
Looking on Android SDK Manager, it shows that Android SDK Tools is at rev. 22 but that there is an update available: rev. 22.0.5

I cant find a way to get to the fastboot exe through manager. Apologies for my ineptness. I'm panicking here in case the battery dies (will it keep the charge topped up if plugged into the pc or external charger?)

p.s. I've tried looking for it at the path it shows on the android sdk manager, ie c\users\****\appdata.... but I dont have that on my C drive! Now I'm really confused.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Here's a shortcut:

Download platform-tools and decompress it on your desktop.

Open a command prompt and type

cd \Users\<your user name here>\Desktop\platform-tools

the fastboot executable is in there.
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
Thanks, that's a stage forward - the first progress so far - it shows the serial number.

But as I said earlier, I can't see the SDK directory in the "c\users\****\appdata...." directory - there's no appdata section. But I updated SDK so the tools are 20.0.5 and the platform tools are 18.0.1

I've just looked into something else - could it be the path... c\users\****\.android? if that's the one then I'll go ahead again.

I let the installer put them in its preferred location - I didnt alter anything (that I know of)

Its at this stage that I'm even more wary as I dont want to hard brick it

(I had another look at the nexus toolkit and wug mentions "force flash mode" but then read that if things arent done correctly this can hard brick so I came back on here, updated SDK (or tried to) and waited)
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Yeah, I don't know why you can't find the SDK directory. But at this point, you don't need it.

Since you have the nakasig-jrw66y factory image you can now decompress it and move the contents of the nakasig-jwr66y directory to the platform-tools directory on your desktop.

The bootloader shipped with the jwr66y factory images won't flash correctly. Download the bootloader from jwr66v instead, decompress it and move it to the platform-tools directory.

now run flash-all.bat
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
I did the above, removed the original bootloader image and put in the one from the link that you sent (after decompressing it)...

It ran through and ended with the device bootloader is '4.18' update requires '4.23'

I though that switching over the bootloader images solved that problem?

---------- Post added at 10:21 PM ---------- Previous post was at 10:10 PM ----------

I tried taking a screenshot of the platform tools folder but I cant work out how to attach it on here - I can only see how to link images that are already up on the web - mine obviously doesnt have a url - I'm trying to sort this out.

(You're racking up the "thanks" from me this evening :)

---------- Post added at 10:48 PM ---------- Previous post was at 10:21 PM ----------

I cracked it! :D The problem at the end was that the updated bootloader file was for the wifi only verion, mine's the 3G - I found it on another thread post #17

So I'm up and running. But now I need to reroot the bootloader as the white "unlocked" sign is still showing - I thought that would have been removed when I had flashed the stock image? :confused:
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Glad to hear you're back up and running, but I want to clarify a few things:

The bootloader link I sent you was bootloader 4.23 for Tilapia, better known as Nexus 7 (2012) 3G. The device code for this model is nakasig. This was extracted directly from the nakasig-jwr66v factory image. The bootloader posted on the link you provided is actually the bootloader for grouper - the wifi-only model. Fortunately for you the bootloaders for nakasi and nakasig are identical, I mention this because you do not want to flash images from a different model - that could be really bad.

The lock you see on the boot screen has nothing to do with rooting. That signifies that the bootloader is unlocked. Rooting has absolutely nothing to do with this.

Again, congrats on getting this resolved!
[Nexus 7 Q&A, Help & Troubleshooting] :
Continued issues.

I'm completely at a loss now. I am still stuck in a bootloop, and I can flash almost everything (boot, system, etc.) but I cannot erase, format, or flash the userdata partition. It cannot be mounted in recovery, and I've tried this with multiple USB ports on multiple computers. If anyone could help me here, that would be fantastic.

--Update--

It can now delete the old userdata img file, then send the new one, but it won't write it
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
Thanks again for your help.send that I lucked-out r.e.the bootloader! It's about time I caught a break though.

I need to lock the bootloader for when I sell it. That was what I was initially attempting to do when it all went wrong today. Feel free to give me suggestions that aren't going to take me all day and result in me not eating dinner!
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Locking the bootloader is easy.

1. Boot to fastboot

2.

fastboot oem lock
[Nexus 7 Q&A, Help & Troubleshooting] :
So I've tried a different computer and the drivers you've given me. Basically, if I use the format command, it cannot mount userdata at all. If I use the flash command to try to flash a new userdata image, it erases the original, sends the new one, but then fails to write it. I think I may have messed up the partitions themselves.
[Nexus 7 Q&A, Help & Troubleshooting] woldranger:
I was right to be sceptical that something would be so simple for me....

'fastoot' is not recognized as an internal or external command.....

It's on fastboot and shows up on device manager as "Android Phone".

:( Why does everything have to be so complicated when I do it! But hey, it's not bricked now! (but I do need to lock the bootloader)