Nexus 7

Use the restore images to return your new Nexus 7 to a factory state

The factory restore images of Android 4.3 for the new 2013 Nexus 7 have been posted up at Google, allowing folks a path of safe return if they decide to modify the firmware on their device. The images contain a complete backup of the "stock" Android system, and are easily flashed using a computer.

Some hullabaloo has been made, with folks saying we might not ever see these, or starting petitions against parts vendors. It would seem a little patience would have been a wiser choice. 

In any event, if you have a new Nexus 7 and like to tinker, grab them at the link below.

Source: Google. Thanks, Kyle!


Reader comments

New Nexus 7 factory images posted


No kidding. So many people (many of whom, I usually respect and agree with) completely lost perspective. People are always so ready to turn on somebody or something the second they don't get exactly what they want.

"It would seem a little patience would have been a wiser choice."

Is it possible that all that hullabaloo may have spurred the release so quickly?

This is exactly what I was thinking. I have great respect for the writers here at Android Central but I strongly suspect no progress would have been made if people hadn't made a fuss.

Yup, I agree 100%. 24 hours after JBQ's post, the factory images 'miraculously' appear?? This was a damage control move, no questions asked. They saw JBQ's tweet get web-wide headlines and they called up qualcomm, gave them the metaphorical finger (like should have been done in the first place), then went straight to the repo and started building. I'm glad Google decided to take the community's side here. This is a Nexus device. If any one manufacturer who has parts in ANY Nexus doesn't want their code open-sourced they have plenty of opportunity to step in and put a stop to their hardware going in in the first place. Crying about it and threatening legal action after the fact is just utter BS, and shows that they only care about the almighty dollar, knowing that they will get their pockets lined (more) simply because their hardware is (also) in a(nother) Nexus.

I thought the whole point was that Qualcomm had proprietary code in the kernel and couldn't give it up for open source because it would give their competitors access to work that is advanced and their competitors don't have.

JBQ said he knew of this for the past six months and saw it coming from day One, but knuckled under to do his job to the best of his abilities.

I still don't understand why JBQ stepped down, if it was his decision or someone higher up telling him to resign because it always looks better to leave on your decision than to be let go by the bosses

Thank God, sheesh, thank Jerry for spreading the good word about Nexus flashing. B-)

Splattered for your amusement... via the AC App

I like to think that a certain person stepping down wasn't in vain. I know these images were in no small part due to his hard work.

Posted via Android Central App on Manta Ray

I'm sure we have him to thank for every set of factory images that have been released, and I'm worried about who can be found to fill his shoes.

I just think it's a shame that words were put into his mouth, and such a fuss was made over rumors that they weren't coming, instead of the actual reason he gave for leaving — frustration at the amount of work it takes to get these in the first place.

I am just as concerned about the future of AOSP, but at the same time I can't say I was all that surprised to see him go. Surely he must qualify for some kind of sainthood for putting up with what he did there every day.

One man can only take so much. I'm just glad he stuck around as long as he did.

Posted via Android Central App on Manta Ray

I know. The media coverage was pathetic, and it must have been painfully embarrassing for JBQ. He was the best "inside" advocate we had for developer interests, and his presence/enthusiasm will be sorely missed in communities like Google Groups. I've never seen a guy take such heat from people for things he couldn't control - and do it all so politely. He would always have things ready so quickly, as soon as new Android versions were out, and when there were things like kernel source errors--or whatever the case--he corrected it *immediately*. Not many people can fill shoes like that.
The petitions, the boycotts, uggghh. It makes the developer community look so ignorant and inflexible. I fear that these things will become more and more of a thorn in Google's side, to the point where they won't be so accommodating to developers and "tinkerers". They'll always be friendly to app-developers, but wannabe hackers making garbage out of their work is not what Google envisioned for the Android Open Source Project, and it's not why it exists. We all love open (I know you do Jerry), but some people have grown to expect that accommodations for overclocked kernels and endless custom ROMs be Google's main priority and entire reason for existing.
If these individuals don't learn to sympathize with the reality of Google's business responsibilities, Google will quickly lose sympathy and patience for the modding community (in it's current state).
Go ahead fanatical petition signers - rip my statement to shreds.
With all that said, I'm so excited to start building for my new N7. It wasn't totally impossible to compile before or anything, but I'm pleased we won't have to use workarounds in place of Google's official stamp of support.

It was JBQ himself who suggested that factory images were possibly not ever coming:

When will flo get factory images?

JBQ: No ETA, and I don't know if they'll ever be available at all.

What is the reason for this?

JBQ: Same as "[reference to a droid life story about the Nexus 4- Comment gets marked as spam so I had to remove the link]"

JBQ: You'll also note that Google never distributed factory images for Nexus One.

Just to clarify: we're talking both factory images and proprietary binaries here, right?

JBQ: Lemme try to figure out how much more I'm allowed to say on that matter.

And then on G+:
"Well, I see that people have figured out why I'm quitting AOSP.

There's no point being the maintainer of an Operating System that can't boot to the home screen on its flagship device for lack of GPU support, especially when I'm getting the blame for something that I don't have authority to fix myself and that I had anticipated and escalated more than 6 months ahead."

I don't see "Gee I'm frustrated this is taking so long and is so much work." He pretty clearly states it's frustration over not having the images themselves and getting the heat for it (again). While I don't deny some folks might have put words in his mouth, it looks a little like you are doing it now Jerry.

This *should* be a story in the vein of "Developer outcry moves company lawyers to do the right thing," *not* "Gee, all you belly-achers should have just shut up and waited."

I agree. Glad to see it. But like they said in the podcast. We become spoiled. Dump them yourselves lol. Nice to see google respond.

Posted via Android Central App

My 13-day-old N7v2 finally broke my spirit with its latest refusal to turn on, followed by a constant - and I mean you could barely do anything between pop-ups - barrage of force-close notices. I'd unlocked it and put TWRP on, but wanted to return it to stock in case Staples checked it out. Because of the lack of factory images, I was SOL and ended up settling for a wipe and relock.

I come back from the store and about an hour later, the stories start to pop about the images being posted. Nice. Two hours too late. Luckily it didn't matter, but this shouldn't have happened in the first place.