Install Official Android 4.3 ROM On Nexus 4, 7, 10 & Galaxy Nexus

Android 4.3 Jelly Bean is the tech equivalent of pulling a beloved hoodie out of storage: a little dated, definitely comfortable, and somehow still kind of awesome.
If you’re reviving a Nexus 4, Nexus 7, Nexus 10, or Galaxy Nexus and want the official Android 4.3 software (not a custom ROM),
you’re in the right place.

This guide covers the two “official” ways Google intended:
Full OTA sideload (often safer, usually no wipe) and
Factory image flashing (the clean-slate, wipes-everything method).
I’ll keep it practical, explain what each method does, and call out the gotchas that make people whisper “why won’t fastboot see my device?” into the void.

What “Official Android 4.3 ROM” Actually Means

Factory Images vs. Full OTA Packages

When people say “official ROM” for Nexus devices, they usually mean one of these:

• Factory image: A set of system images (boot, system, recovery, radio/bootloader where applicable) that restores your device to a stock Google build.
  This method typically requires an unlocked bootloader and erases data.
• Full OTA package: A signed update ZIP you apply through stock recovery using adb sideload.
  This often avoids unlocking the bootloader and usually avoids a full wipeassuming your system is close enough to stock for the update checks to pass.

Why Android 4.3 Was a Big Deal (Back When Dinosaurs Roamed)

Android 4.3 introduced features like restricted profiles on tablets (great for shared devices),
Bluetooth Smart / Bluetooth Low Energy support, and OpenGL ES 3.0 improvements for graphics.
It also brought a bunch of performance and stability refinements that made Jelly Bean feel smoother overall.

One reality check: Android 4.3 is from 2013. Many modern apps won’t support it anymore, and security expectations have changed a lot.
Still, for collectors, offline media devices, retro dev testing, or simply bringing old hardware back to life, it’s a fun projectlike restoring a classic car, except smaller and with more USB drivers.

Pre-Flight Checklist (Do This Before You Touch a Command Line)

1) Back Up Anything You Like

If you flash a factory image (and/or unlock the bootloader), expect a full data wipe. That includes photos, downloads, game saves, and those precious text messages from 2014.
Sync what you can to your Google account, copy media to a computer, and don’t assume “I’ll be careful” counts as a backup strategy.

2) Charge the Device (And Your Patience)

Aim for 60% battery or more. If the device powers off mid-flash, it can become harder to recover.
Also: use a reliable USB cable and a direct USB port (not a wobbly hub that disconnects if you breathe near it).

3) Install Platform-Tools (ADB & Fastboot)

You’ll use ADB for sideloading OTAs and fastboot for factory images.
Google packages these in the Android SDK Platform-Tools.
Extract them somewhere simple like C:platform-tools (Windows) or ~/platform-tools (macOS/Linux).

4) Know Your Device Codename (Seriously)

The #1 flashing mistake is downloading the wrong image. Nexus devices use codenames, and some models have variants.
Here are the common ones you’ll see for Android 4.3-era builds:

• Nexus 4: occam
• Nexus 7 (2012): nakasi (Wi-Fi) / nakasig (mobile)
• Nexus 10: manta
• Galaxy Nexus: maguro (GSM), plus carrier variants like toro/toroplus depending on model

If you can boot into the bootloader, you can often confirm with:

Method A: Sideload the Full OTA (Often the Safest “Official” Way)

If your goal is “get Android 4.3 on here” with minimal drama, OTA sideload is usually the best first attempt.
It typically does not require unlocking the bootloader, and it often keeps your data intact.

When OTA Sideload Works Best

• You’re using stock recovery (not TWRP/CWM).
• Your device is not heavily modified (root, altered system apps, custom kernel can cause verification failures).
• You downloaded the correct full OTA ZIP for your exact device/build.

Step-by-Step: ADB Sideload Android 4.3

1. Download the official Android 4.3 full OTA ZIP for your device from Google’s OTA repository pages.
   Make sure it matches your device codename and intended build (Android 4.3 builds are commonly labeled with build IDs like JWR66V).
2. Put the ZIP in your platform-tools folder (or note the full path to it).
   Rename it to something simple like update.zip to avoid typing errors.
3. Boot into recovery mode.
   Usually: power off, then hold Volume Down + Power to enter the bootloader, then select Recovery.
   If you see the Android robot with a warning, open the recovery menu (often Power + Volume Up).
4. In recovery, choose: “Apply update from ADB”.
5. On your computer, open a terminal/command prompt inside the platform-tools folder and run:

   You should see a device listed as sideload (or similar). If you see nothing, it’s usually drivers/cable/port.

6. Start the sideload:

   Don’t panic if the progress bar appears to pause at certain percentagessome recoveries display progress in a weird way.

7. When it finishes, select Reboot system now.
   First boot after an update can take several minutes. If it feels long, that’s normal; if it feels like a full-length movie, give it a bit more time before you assume it’s stuck.

Common OTA Sideload Problems (And What They Usually Mean)

• “signature verification failed”: The ZIP is corrupt, not the right package, or recovery isn’t stock.
  Re-download and confirm you’re using an official signed file.
• Status 7 / assert failed: You’re trying to apply a package that doesn’t match your device, variant, or expected base build.
  This is the OTA politely saying, “Nice try, but no.”
• ADB says “device not found”: Usually USB drivers (Windows), a bad cable, or a flaky port.
  Try a different cable/port and ensure platform-tools are current.

Method B: Flash the Factory Image (The Clean Slate Option)

If you’re rooted, running a custom recovery, stuck in a boot loop, or you just want a fresh official Android 4.3 install,
flashing the factory image is the gold-standard reset button.
The trade-off: you’ll typically need to unlock the bootloader, and that usually means a full wipe.

What You’ll Need

• The correct Android 4.3 factory image for your device (from Google’s factory image repository).
• Platform-tools installed (fastboot + adb).
• USB drivers on Windows (if fastboot doesn’t detect the device).

Step-by-Step: Unlock & Flash Android 4.3 Factory Image

1. Enable Developer Options (if you can boot Android):
   Settings → About (phone/tablet) → tap Build number seven times.
   Then enable USB debugging and (if available) OEM unlocking.
2. Boot into the bootloader (fastboot mode).
   Often: power off → hold Volume Down + Power.
3. Connect USB and confirm your computer sees it:

   If it returns a device ID, you’re in business.

4. Unlock the bootloader (this wipes data on these older devices):

   Confirm the unlock on the device screen using the volume/power keys.
   If you can’t unlock due to carrier restrictions, you may be limited to OTAs or the specific variant images allowed.

5. Extract the factory image.
   You’ll usually download a .tgz (or .tar) that contains another archive plus flashing scripts.
   After extracting, you’ll often see files like flash-all.bat (Windows) or flash-all.sh (macOS/Linux).
6. Run the flash script from inside the extracted folder:
   • Windows:
   • macOS/Linux:

   Do not unplug the device while flashing. This is the part where impatience becomes a personality trait you regret.

7. When it finishes, the device should reboot. Give it time for the first boot.

Optional (But Smart): Re-Lock the Bootloader

If you’re returning to a stock, official setup and you don’t need an unlocked bootloader anymore, relocking improves security on a daily-use device.
For many older Nexus devices, the command is:

Device Notes: Nexus 4 vs. Nexus 7 vs. Nexus 10 vs. Galaxy Nexus

Nexus 4 (occam)

The Nexus 4 is generally straightforward with factory images. Just be sure you’re flashing the correct “occam” package.
Android 4.3 also brought attention to Bluetooth Low Energy support on Nexus 4 specifically, which is a fun little historical footnote if you’re pairing sensors.

Nexus 7 (2012): nakasi vs. nakasig

This is the classic trap: nakasi is Wi-Fi; nakasig is the mobile radio variant.
Flashing the wrong one is a quick route to a bad afternoon.
If you’re unsure, verify via bootloader product info or check the model details in Android before starting.

Nexus 10 (manta)

The Nexus 10 factory image is bigger and can take longer to flash and boot.
Also, because it’s a tablet often used as a shared device, Android 4.3’s restricted profiles feature is especially relevant here.
If you unlock the bootloader, expect the “wipe” behavior and plan accordingly.

Galaxy Nexus (maguro and friends)

The Galaxy Nexus is where “variant awareness” matters most.
GSM models are typically maguro, while carrier models can differ.
Official Google images and OTAs may exist for specific variants and build fingerprints, so double-check you’re using the right package.
If your device is carrier-locked in a way that blocks unlocking, OTAs may be your only official path.

After You Install Android 4.3: A Quick Post-Flash Checklist

• Verify the version: Settings → About → confirm Android 4.3 and the build number (often something like JWR66V for early 4.3 builds).
• Let it settle: After a major flash, Android may spend time optimizing apps and syncing accounts.
  Performance often improves after the first hour of setup.
• Restore carefully: If you’re restoring apps/data, do it in stages.
  If something weird happens, you’ll know what caused it.
• Keep expectations realistic: Some modern services won’t behave like it’s 2013 again.
  That’s not your faulttime is undefeated.

FAQ: The Questions Everyone Asks (Usually at 1:00 AM)

Will installing Android 4.3 make my old Nexus “fast” again?

It can make it clean again, which often feels fasterespecially if you’re coming from a cluttered install or a buggy custom setup.
But don’t expect miracles. The hardware is older, storage is slower than modern devices, and app compatibility is limited.
Think “restored classic,” not “brand-new flagship.”

Can I downgrade if I don’t like it?

With Nexus-era devices, it’s often possible to move between builds using official factory images, assuming you can unlock and flash.
Just remember that downgrading can wipe data and isn’t always friendly to apps expecting newer services.

What’s the safest method if I’m nervous?

Start with full OTA sideload if your device is stock enough to accept it.
If that failsor your device is in a boot loopfactory images are the most reliable “back to stock” tool.

Real-World Experiences: What It’s Like Installing Android 4.3 Today (About )

Installing Android 4.3 in the modern era is a little like using a VHS rewinder in 2025: it still works, it’s oddly satisfying, and it makes you wonder why you own it… until you do it and grin anyway.
Most people’s first “experience” isn’t the flashing itselfit’s the setup: finding a reliable cable, making sure the computer recognizes a device from a decade ago, and remembering that fastboot won’t respond to encouragement like “please, buddy.”

A common moment of victory is seeing fastboot devices return an ID. It’s small, but it’s the difference between “I am a competent human” and “I have become a USB troubleshooting specialist against my will.”
On Windows, the experience tends to involve driverssometimes the correct driver installs instantly, and sometimes Windows insists your Nexus is a “mysterious rectangle” that cannot be understood.
Switching USB ports (especially avoiding loose front-panel ports) often feels like superstition, but it works often enough to become a ritual.

When sideloading an OTA, people frequently expect a smooth, cinematic progress bar. What they get is a progress number that appears to stall, then jumps, then stalls again.
Recovery mode UI is not here to entertain you; it’s here to get the job done and then stare at you silently.
The best experience tip is simply: don’t touch anything, don’t unplug anything, and let the process finish.
The most consistent “success story” is the boring one: correct file, stable cable, patient operator.

Factory images, meanwhile, feel like the “power wash” of Android maintenance. Once you unlock the bootloader and run the flash script, it’s astonishing how reliably a device can return to a known-good state.
The emotional arc is predictable: nervousness when you hit Enter, mild panic when the screen reboots mid-process, relief when the script completes, and then the long, quiet wait for the first boot.
That first boot is the moment many people misjudgeon older hardware, it can take long enough to feel suspicious.
But once the lock screen finally appears, it’s deeply satisfying in a “I fixed a thing with my hands” kind of way.

The funniest real-world detail is what happens next: you install two apps, realize half the modern ecosystem has moved on, and then repurpose the device into something charmingly specifican offline music player, a kitchen timer with an enormous screen, a kids’ drawing tablet (with restricted profiles!), or a nostalgia machine for old Android UI.
In the end, the “experience” isn’t just about Android 4.3it’s about rescuing useful hardware from the drawer of forgotten gadgets and giving it a second life.

Conclusion

Installing the official Android 4.3 ROM on a Nexus 4, Nexus 7, Nexus 10, or Galaxy Nexus is totally doableand still one of the cleanest “learn by doing” projects in Android land.
If you want the least risky path, try full OTA sideload first. If you need a true reset, use the factory image method, accept the wipe, and enjoy the clean reboot.
And if you unlock the bootloader for flashing, consider relocking it afterward if your goal is a stable stock setup.