3

When I try to install the latest version of Open GApps onto my phone using adb sideload, and the default CM Recovery that comes with CM 13 for the Samsung Galaxy SII (i9100). However, I get the error message, "Failed to set up busybox." The suggested solution, which is to use TWRP recovery instead of CM, I have no idea how to do because I don't know where to find a kernel, with TWRP recovery, that is compatible with CM13. I can't find kernels for CM12, since many of the download links on sites like xda-developers.com are dead.

I tried to install with CM12 and CM13 and I get the same result.

I successfully installed a copy of busybox onto /system/bin. I first tried installing Open GApps via adb sideload however, this failed. Running adb shell, I saw that perhaps busybox was runnable, so I ran chmod +x, and ran busybox, after which I saw busybox's help message. Surprisingly, Open GApps still didn't install for the same reason.

How can I install the Google Apps onto my phone?

  • You don't need a new kernel to use a different recovery. – Matthew Read Mar 1 '16 at 21:11
1

Rahul is right, but I might contribute to this (I also got the i9100 and ran into the same problem). I had the problem that my google apps were already bricked so i could not install any helper apps.

TAKE CARE: This may brick your system if you are not sure what you are doing.

When upgrading CM12.X to 13 you have to install a new gapps version. The problem is, that with CM13 the old recovery system (which you need to install gapps) is being replacedby a new one which lacks the busybox. My solution so far: flash back the old recovery system using Odin (I used clockworkmod as recovery system which has busybox). Download the gapps and latest cyanogenmod on your sd card (zip files) and insert it in your phone. Boot into the recovery. Clean and wipe your system. Install cyanogenmod from zip file and directly afterwards the gapps zip file. This might take some time. Then reboot your system.

CRITICAL NOTES: - When installing cyanogenmod from sd card, your recovery will again be overwritten with the new embedded recovery system cyanogenmod (that one that is lacking the busybox). - If you haven't resized your partitioning, installation of gapps (I used the smallest version called pico) will fail because of insufficient storage. If this is the case, you also have to flash new pit files and format sdcard0 (vfat), system, data, preload and emmc (vfat). Then you may install your custom rom and gapps from recovery.

Links: Pit files different sizings: forum.xda-developers.com/showpost.php?p=60473209&postcount=1106 (pick one with 512MB preload (!) just to be sure) CWM Recovery: http://galaxys2root.com/cwmtwrp-recovery/ Philz Recovery for flashing pit files and formatting filesystems: http://d-h.st/SvM

Unfortunately this procedure have to be repeated once you have to upgrade your gapps. I found no better solution so far...

  • Thanks @Simon! Helpful, but for me, as a novice, not detailed enough, unfortunately... How do I flash a new PIT? How do I format sdcard0 etc? My head is spinning... I would very much appreciate a more step-by-step kind of advice. Thanks a lot! – Thomas Apr 18 '16 at 19:59
  • @Thomas see my additional answer below. This may help you. – Simon Apr 24 '16 at 9:29
2

Okay, I add another answer because the protocol I am attaching differs from what I posted above. This worked for me, I cannot tell if this will work for you; please don't point your finger on me ;) This is meant for all who have a CM CM12.1 Nightly build 2016-01-19 or later installed - including Cyanogenmod's recovery which IS NOT ABLE to install Zip Files. The Procedure also reorganizes your Partition structure.

== Resizing Partitions, Installing TWRP 3.0.2-0, CyanogenMod 13 nightly and OpenGApps Pico on Samsung's Galaxy S2 i9100 using Windows 10. Phone has CM12.1 nightly build 2016-01-19 or later, but no busybox. ==

CAUTION: Following these instructions may brick your device. All steps are performed at your own risk. This protocol was successfully tested on two independent i9100 devices. Initially both devices had CyanogenMod 12.1 with CyanogenMod's "stock" recovery installed (which lacks the busybox). Build > 2016-01-19. This protocoll will install CyanogenMod 13, OpenGApps and TWRP 3.0.2-0 recovery. This recovery should persist even after updating CyanogenMod to the next nightly build (not tested yet, would be nice if soeone could feedback on this!).

NOTE: All steps were performed on a Windows 10 PC. You may encounter different events using an other OS.

PREPARATIONS:

  1. Read this first before executing ;)
  2. Backup all your personal data.
  3. Eject your extra SD-card from your phone.
  4. Get the latest CyanogenMod Nightly Build: http://download.cyanogenmod.org/?device=i9100 -> store the zip on your extra SD-card you just ejected
  5. Get OpenGApps pico: http://opengapps.org/ Make sure that the build date matches the CyanogenMod nightly build date. Store the zip on the SD-card you just ejected.
  6. Get HeimdallSuite_v1.4.0.zip: http://forum.xda-developers.com/attachment.php?attachmentid=3713767&d=1460278689 -> Extract it to a local folder (from now on called c:\localFolder)
  7. Get Samsung_Galaxy_S2_Pit-Files_Collection_All-In-One_2015-05-04.rar - http://forum.xda-developers.com/attachment.php?attachmentid=3293884&d=1430622849 -> store it in c:\localFolder
  8. Extract yor desired system storage layout from the jujst downloaded pit collection archive. I strongly recommend to pick a file from the "I9100_512MB_Preload" subfolder, because those most likely won't cause trouble with CyanogenMod installation. I decided for the following configuration: I9100_2.0GB_Sys-08GB_Data-512MB_Preload.pit --> store this file in c:\localFolder. This file will be called myPit.pit from now on.
  9. Get SAMSUNG_USB_Driver_for_Mobile_Phones.zip: http://forum.xda-developers.com/attachment.php?attachmentid=3713769&d=1460278744 -> double click to install. When you don't install this, you might won't be able to establish a connection between your phone and your PC.
  10. Get MSVC++ 2012 Redistributable x86, vcredist_x86.exe (Heimdall won't open with x64 installed): https://www.microsoft.com/de-de/download/details.aspx?id=30679 -> double click to install. If you don't install this, you most probably will get a dll not found exception when launching Heimdall.
  11. Get latest TWRP recovery: https://dl.twrp.me/i9100/ -> store the img in c:\localFolder. This file will be called as myRecovery.img from now on.

PROTOCOL:

  1. Connect your device (and unlock it, if locked).
  2. Open windows device manager (enter "device manager" in start). In the device manager, ensure that hidden devices will be shown ("View" menu).
  3. Navigate to "Modem" -> "Samsung Modem". Right click -> "Uninstall".
  4. Enter "change device installation settings" in start end select not to auto install drivers at all. This is necessary to prevent Windows 10 using any cached drivers for the setup.
  5. Disconnect your device.
  6. Reboot your system into advanced startup settings menue: Click the Start menu and select "Settings" -> Click "Update and Security" -> Click on "Recovery" -> Click "Restart now" under "Advanced Startup". When after the system reboot the boot menu appears, click "Troubleshoot" -> Click "Advanced options" -> Click "Startup Settings" -> Click on "Restart" -> On the "Startup Settings" screen press 7 or F7 to disable driver signature enforcement. (taken from: http://acer.custhelp.com/app/answers/detail/a_id/38289/~/windows-10%3A-disable-signed-driver-enforcement)
  7. Turn off your phone. Bring it into download mode by holding "Volume Down" + "Home" + "Power" at the same time. A warning screen will appear. Acknowledge with "Volume Up".
  8. Connect your device to your PC. The device is now in download mode.
  9. Open explorer and change to c:\localFolder\Heimdall Suite\Drivers and open zadig.exe
  10. In the "Options" menu tick "List All Devices"
  11. Select "Gadget Serial" from the drop down menu.
  12. Select "WinUSB v6.1.x.x.x" from the value picker and click "Install Driver". The installation should be confirmed with a success dialog.
  13. Close zadig.exe
  14. Bring your phone in the donwload mode again: Disconnect in from power. Reconnect it. Bring it into download mode by holding "Volume Down" + "Home" + "Power" at the same time. A warning screen will appear. Acknowledge with "Volume Up".
  15. Open c:\localFolder\Heimdall\Heimdall Suite\heimdall-frontend.exe
  16. Open the "Utilities" tab.
  17. Click the "Detect" button in the "Detect Device" panel. Make sure the status message says "Device detected"
  18. In the "Download Pit" panel click the "Save As" button. Enter a name like "backup". This is a backup file of your current phone partitioning. Because you are going to change its size, you will not use this file later on. However, this step is necessary to make the phone communicate with your PC, I don't know why...
  19. Then klick the "Download" button in the same panel. If everything was set up correctly, no errors will appear in the status log. Please check.
  20. Bring your phone in the donwload mode again. Disconnect in from power. Reconnect it. Bring it into download mode by holding "Volume Down" + "Home" + "Power" at the same time. A warning screen will appear. Acknowledge with "Volume Up". Yes, this is necessary.
  21. Open the "Flash" tab.
  22. In the "PIT" panel click the "Browse" button and select your myPit.pit (which you extracted from the pit files collection) and tick the "Repartition" checkbox.
  23. In the "Partitions(Files)" panel click the "Add" button.
  24. In the "Partition Details" panel at the "Partition Name" dropdown menu select "Recovery". Ensure that the "Partition ID" field reads "7". Click the "Browse" button in the "File" panel next to it and select myRecovery.img
  25. In the "Sessions" panel, make sure that neither the "No Reboot" nor the "Resume (...)" checkboxes are ticked.
  26. Now click the "RECOVERY" entry in the "Partitions(Files)" panel so that it is highlighted blue.
  27. Click "Start". Hopefully the recovery will be flashed now. You will see progress when the status bar changes. Also check the output for errors. If just nothing will happen, check again if the the "No Reboot" nor the "Resume (...)" checkboxes are unchecked and/or retry.
  28. Bring your phone in the recovery (!) mode. Disconnect it from power. Reconnect it. Bring it into recovery mode by holding "Volume Up" (!) + "Home" + "Power" at the same time. The TWRP Recovery screen will appear.
  29. Navigate to "Wipe" -> "Advanced Wipe". A list of available partitions will appear. (It is important to reformat at least "SDCard" (/emmc) so that it will be recognized by CyanogenMod later (otherwise it will most likely be marked as defect).) Check "Cache", tap "Repair Or Change File System" -> "Change File System" -> "EXT4" -> Swipe. This will force reformatting the partition.
  30. Repeat this step with all other available partitions (some of them like "Android Secure" or "Dalvik" won't work. WARNING: when you still have your extra SD-card inserted, you may see two "SDCard" entries in that list. One of them is your extra SD-card. If you format it, your personal data (as well as the cyanogenmod-nightly and OpenGApps zip files) on it will be lost. At this step, I assume you have no extra SD-card inserted...
  31. Finally, just to be sure that all necessary partitions are clean, navigate to "Home" -> "Wipe" -> "Swipe To Factory Reset".
  32. Navigate to "Home" -> "Reboot" -> "Power Off" to tun off your device.
  33. Insert your extra SD-card with the OpenGApps and CyanogenMod nightly build zip files on it.
  34. Bring your phone again in the recovery mode: Disconnect it from power. Reconnect it. Bring it into recovery mode by holding "Volume Up" (!) + "Home" + "Power" at the same time. The TWRP Recovery screen will appear.
  35. Navigate to "Install" -> "Select Storage" and pick you extra SD-card. Select your CyanogenMod nightly build zip file and swipe to install.
  36. Repeat this step with your OpenGApps zip file.
  37. Navgiate to "Home" -> "Reboot" -> "Power Off".
  38. Turn on your device and let CyanogenMod complete its work. This may take a while (about 10mins).
  39. In CyanogenMod enable development options. Go to "Settings" -> "About This Phone" -> hit "Build Number" seven times.
  40. Protect your recovery from being overwritten: "Settings" -> "Developer Options" -> disable "Update CM Recovery"
  41. Restore your personal data. That should be it.
0

You can get the appropriate GApps at Opengapps. And to install that, just put some custom recovery in your device like TWRP/CWM. I recommend CWM.

Install ClockworkMod Recovery With ROM Manager:

This is the easiest method available and lets you begin the installation using a graphical interface while you are booted into Android, thus you do not have to download the recovery image and enter any commands. This is the recommended method for most users and you should try other methods only if this one doesn’t work for you at all for some reason.

  1. Install ROM Manager on your device. It is an app that basically lets you schedule recovery operations while booted into Android, and has an option for installing the latest version of ClockworkMod Recovery.
  2. Launch the just installed ‘Rom Manager’ on your phone. The first option it gives you should say ‘Flash ClockworkMod Recovery’. Just tap on it and follow the instructions.
  3. Wait patiently while the system reboots and the latest version of ClockworkMod Recovery is installed. Select to reboot the device if it prompts you to.
  4. Once the device reboots into Android, verify that you have the latest version of ClockworkMod Recovery installed by launching Rom Manager. It should now mention in the first option that you have ClockworkMod installed along with its version you’re running, and any updates that might be available. If a newer version is available, tap on that option and follow the instructions to update.

The complete guide can be found at AddictiveTips.

-1

Get older opengapps version. 2016-02-08 works for me. 2016-02-24 does not )

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.