Install Google Now on ICS Rooted Devices

This guide walks you through installing the Google Now experience on an Android 4.0 Ice Cream Sandwich device that is rooted. While Google Now was designed for Android 4.1+, this method uses a modified APK and a build.prop tweak to make it work on ICS. You’ll need a rooted device, a file manager with root access, and a way to push files via ADB or an on-device terminal.

What You’ll Need

• A rooted Android device running Ice Cream Sandwich (4.0.x).
• A custom recovery (like ClockworkMod or TWRP) – recommended for backup, but not strictly required.
• ADB and Fastboot tools installed on your computer (or a root-enabled file manager and terminal emulator on the device).
• The Google Now APK (specifically the “GoogleSearch.apk” from Android 4.1.2 or a compatible modded version). You can find these on XDA-Developers forums.
• A text editor to modify build.prop (or use a root file manager with a built-in editor).
• USB debugging enabled on your device (Settings > Developer Options).

Step-by-Step

1. Back up your device. Boot into recovery and create a Nandroid backup. This is critical because modifying system files can cause boot loops if something goes wrong.
2. Download the Google Now APK. Get the correct version for your screen density and architecture (most ICS devices are ARMv7). Save it to your computer or directly to your device’s storage.
3. Enable USB debugging and connect to your computer. Go to Settings > Developer Options > USB debugging. Connect your device via USB and verify ADB sees it by running adb devices in a terminal/command prompt. You should see your device listed.
4. Push the APK to your device’s /system/app folder. Open a terminal/command prompt on your computer and run:
   
   adb push GoogleSearch.apk /sdcard/
   
   Then, using ADB shell, copy it to /system/app:
   
   adb shell

su

mount -o rw,remount /system

cp /sdcard/GoogleSearch.apk /system/app/
   
   If you prefer, you can use a root file manager on the device to copy the APK to /system/app.
5. Set correct permissions. In the same ADB shell, run:
   
   chmod 644 /system/app/GoogleSearch.apk
   
   This ensures the APK is readable by the system.
6. Modify build.prop. Open the file /system/build.prop with a root text editor (or pull it via ADB, edit, and push back). Find the line that starts with ro.build.version.sdk and change the value from 15 to 16. Also, find ro.build.version.release and change it from 4.0.x to 4.1.2. Save the file. This makes the system report itself as Jelly Bean to the Google Now app.
7. Reboot your device. After the changes, reboot normally. The system will take longer to boot the first time as it rebuilds caches.
8. Test Google Now. Once booted, find the Google Search app (it might appear as a new icon or replace the existing search bar). Long-press the home button or swipe up from the bottom on the home screen (if supported) to trigger Google Now. If it doesn’t open, try opening the app manually from the app drawer.
9. If it force-closes, clear app data. Go to Settings > Apps > Google Search > Clear data, then try again.

Common Mistakes

• Wrong APK version: Using a Google Now APK from a newer Android version (like 4.2+) often fails on ICS due to missing APIs. Stick to a 4.1.2 version or a specifically modded ICS-compatible build.
• Incorrect permissions: If the APK is not set to 644 (rw-r–r–), the system will not recognize it and may cause a boot loop or the app simply won’t appear.
• Forgetting to remount /system as rw: If you get a “read-only file system” error when copying, you forgot to run mount -o rw,remount /system.
• Editing build.prop incorrectly: A typo in build.prop can prevent your device from booting. Always double-check the lines you changed.
• Not clearing data after install: The Google Search app may have cached old data from the previous version; clearing data avoids conflicts.

Tips

• Use a file manager like Root Explorer or ES File Explorer with root access to make the file copying easier if you’re not comfortable with ADB.
• Keep a copy of the original build.prop on your SD card so you can revert if needed.
• If Google Now cards don’t update, ensure your device has a stable internet connection and that Google location services are enabled.
• Consider freezing or removing the old search app (if separate) to avoid conflicts.
• Some ICS ROMs have a different search bar; you may need to add a Google Search widget to the home screen to access the new app.

Troubleshooting

• Boot loop: If your device gets stuck on the boot logo, boot into recovery and restore your Nandroid backup. Then redo the steps more carefully, double-checking the build.prop changes.
• Google Now force closes: Clear the app data (Settings > Apps > Google Search > Clear data). If that fails, reinstall the APK with correct permissions. Also ensure the build.prop changes are exactly as specified.
• Google Now doesn’t appear: Make sure the APK is actually in /system/app and not /data/app. Also, check that the app is not disabled in Settings > Apps.
• Search bar is missing: Long-press the home screen, select Widgets, and add the Google Search widget. If that doesn’t work, reboot again.
• Voice search not working: Google Now on ICS may not support voice input properly. You may need to install a separate Google Voice Search APK from the same era.
• System UI crashes: If you see “Unfortunately, System UI has stopped,” your build.prop change may have caused a conflict. Revert build.prop to original and try a different Google Now APK.

Frequently Asked Questions

Will this work on any ICS device?

Mostly, but devices with heavily customized ROMs (like TouchWiz or Sense) may have additional issues. It works best on stock or AOSP-based ROMs.

Do I need to be rooted?

Yes, because you need to write to /system and modify build.prop, which requires root access.

Will Google Now updates break it?

If you update the Google Search app from the Play Store, it may overwrite the modified version and stop working. Disable auto-updates for the app.

Can I revert to the original search app?

Yes, restore your Nandroid backup or replace the GoogleSearch.apk with the original one from your ROM and revert build.prop changes.

Is it safe to change build.prop?

It’s safe as long as you make only the two changes described and keep a backup. Incorrect changes can cause boot issues, but they are reversible with a backup.

Why does Google Now sometimes show no cards?

Cards depend on Google’s servers and your activity. On ICS, some card types may not be supported due to missing APIs. Ensure your Google account is synced.

Related

• Zune vs iPod: Key Differences Explained
• Fix Encrypt iPhone Backup Option Greyed Out
• Check If Windows Firewall Is Blocking an App