It was just the other day when it came out that complications with Qualcomm licensing was keeping Google from posting the binaries and full factory image for the new Nexus 7 tablet. The issue was so irksome that Jean-Baptiste Quéru (JBQ), Google's Android open source manager, decided to leave that post. Well, that must have lit a fire under someone, because Google just posted the image and drivers for the Razor hardware.

2013-08-09 17_53_58-Factory Images for Nexus Devices - Android — Google Developers

The system image is based on JSS15J, and it clocks in at 340MB. This should contain everything you need to flash a 2013 Nexus 7 back to stock. The binaries contain drivers from Asus, Broadcom, and Qualcomm. In fact, it looks like everything is there – graphics, camera, sensors, the whole package. Each of the binaries is a small download, with Qualcomm's being the largest at about 17.6MB.

2013-08-09 17_53_42-Binaries for Nexus Devices - Android — Google Developers

Note the typo "Nexus 17"

Now that we've got the image and binaries, custom ROM development can really take off. No word yet on whether or not JBQ will be staying on at the Android Open Source Project. We've reached out to him for comment and will update if we hear back. In the meantime, grab the files at the links below.

[Nexus 7 (Razor) Factory Image, Drivers]

Ryan Whitwam
Ryan is a tech/science writer, skeptic, lover of all things electronic, and Android fan. In his spare time he reads golden-age sci-fi and sleeps, but rarely at the same time. His wife tolerates him as few would.

He's the author of a sci-fi novel called The Crooked City, which is available on Amazon and Google Play. http://goo.gl/WQIXBM

  • cabbiebot

    WOW! That was fast. Obviously JBQ is a valuable employee and I have no doubt his sentiment was shared among many at Google.

  • JLishere

    Razor? I always thought the N7 (2013) was called Flo for some reason. Am I wrong? When did that happen?

    • David Margolin

      yeah, kinda confused cause pa calls it flo...

      • Niall Burnes

        "Razor" is the codename from Google/Asus. "Flo" is the board name. Same for "Nakasi/Grouper" "Occam/Mako" etc,

        • Metroview

          Well I just learned something new tonight. I always wondered why some system APKs in my Nexus 4 had "Occam" as part of their filenames.

    • Otto Prime

      it's product and device name. razor and flo.

      • JLishere

        okay so razor is the build name, and flo is the device name? similar to occam (build name for N4) and mako (device name for N4)?

        • someone755

          No, it's device codename and board name. Razor is the tablet, Flo is the board. Mako is the board, Occam is the phone. Same with Gnex, Maguro is the board, other things are phone names.

    • JJ

      It's a much better name than "grouper" or any of the other silly fish names they came up with. Although "mako" was pretty cool.

      • Matthew Fry

        I like Manta.

      • someone755

        Groper is the name of the T3 board. The device is a Nakasi. Or Nakasig for the 3G version.

        • hp420

          lol Freudian slip :)

      • hp420

        They always use sea creatures for the names.

      • Simon Belmont

        I like grouper and tilapia. Those names always made me want to go to Red Lobster.

        Yup. I'm relating tablets to food.

    • Sam Hollis

      Looking at build.prop, the board's name is flo, device name is razor.

  • Mauricio Andres Najera Osorio

    I hope this help JBQ return to his natural enviroment: AOSP

    • hurrpancakes

      So you hope he'll return to AOSP ASAP?

  • YBinnenweg

    "Nexus 17" that's odd.. I think Google derped a bit there :P

    • Mauricio Andres Najera Osorio

      odd? Razor doesn't ring any moto bell?

      • YBinnenweg

        Uhh..? What does that have to do with Google's 'Nexus 17'?

  • http://www.androidpolice.com/ Artem Russakovskii

    Lulz: http://i.imgur.com/q1ITGVc.png

    Nexus 17 FTW!

    • YBinnenweg

      Hey I was first..! :P

    • hurrpancakes

      I'd buy a 17 inch tablet

      • Ray

        Enjoy carrying that baby around! :P

        • DennisHeffernan

          Hey, this is America. More is better and too much is just right! 30" tablet? NO PROBLEM! Strap it on my back, baby! ;)

      • hp420

        Me too. I'd use it as a desktop pc!

    • CoreRooted

      Holy crap! I know that Google moves pretty quick, but we're already at 17?! Damn. I was just getting 7.2013 all setup! LOL

    • David Margolin

      now fixed

    • UndergroundWire

      Trying to play catchup to the Chrome release cycle.

  • Hidetomaru

    Now we need a JBQ factory image so we can restore him in AOSP again :(

    • 16bitz0r

      Now that's Priceless!

    • New_Guy

      Love you...


      Will this fix the faulty GPS? =/

  • Joshua

    For the record, I would buy a 17" Google brand laptop any day.

    • someone755

      Laptop, okay. But a tablet with no keyboard dock?

      • Joshua

        No, probably not that. I think above 12", tablets become inconvenient to use using pure touch and a keyboard and mouse become necessary, so you may as well use a laptop. In between 10 and 12 inches, though, I think a hybrid device could work very nicely. That's why I'm waiting for the 11.6" Asus Transformer Book Trio to see if OEMs can finally pull off such a hybrid correctly.

  • MrRageQuit

    Finally. Its too bad JBQ had to ragequit just to get the ball rolling.

  • garry

    didn't see that coming actually. shoutouts to whoever had the balls on the food chain at google to get this done after JBQ shed some public light on it.

    faith in android and google slightly restored.

  • Sir_Brizz

    I really hope this means JBQ gets back to his post. Who else would run AOSP with the kind of care he has??

  • cypressious

    The factory image isn't that important for custom firmware development. Here's a good read on that topic from a CyanogenMod contributor: https://plus.google.com/u/0/101093310520661581786/posts/4xjCuwNAjTd

    • Simon Belmont

      It's important for people that want to get their device back to 100% stock before selling it. Or, if they screw it up beyond belief.

      Nice read, though. Thanks.

  • Simon Belmont

    Glad to see this rectified. I hope that JBQ would perhaps consider coming back to his post at AOSP because he's a valued asset there.

    This is probably good news for the Nexus 5, if it ends up using a Snapdragon 800 SoC. All this "no posting of factory images or binaries" got me worried that the N5 would befall the same fate and I'm keen on acquiring one.

  • Mike

    I'm gonna miss JBQ. He definitely had a pair. He loved Google, the Nexus lineup, open source, and his users so much he put his job, no his dream career on the line for his company, his users, and most importantly his passion. I barely knew him but all us Android geeks and devs miss him like a brother. I told a guy I helped provide support with for his ROMs through FAQs and forum support that JBQ had quit, and there were so many expletives flying off the walls from both of us, and then silence. I'll never forget this man that had the balls to put his whole life on the line for open source. A true brother. )-;

    • Justin W

      I don't believe he's leaving the Android division. I think he's just done being the maintainer of AOSP.

      • Mike

        Well I hope this man quickly gets a new job. We love to focus on tech so much (I freaked out too) but I would hate to see a guy that cares so much for AOSP leave a good paying career at Google. I don't blame him for quitting AOSP, but I want him and the family to have a roof over their head. (it would be cruel irony to see a man who has put his career on the line for the community live in a box; if he cared so much for us, imagine how he must love his wife and kids). I doubt someone that talented would be unemployed for that long, but I'm just trying to show my affection for a brother who shown the same affection towards fellow geeks. I wish him luck. Hell, if he needed cash and list his job, I'd donate to him. He'd find a good job in no time.

  • Andrew

    When a grown man can quit his job in a hissy fit is praised, I often feel like I must be living in the Matrix.

    In other news, glad to hear the binaries and image have been released. I never doubted they would be.

    • jordanjay29

      He didn't quit in a hissy fit. It was more like he washed his hands of the project, after months of trying to convince Google to do just what they've done now.