1. Are you ready for the Galaxy S20? Here is everything we know so far!

Installing Google Play via Android Studio (while rooted)

Discussion in 'Android Development' started by altjx, Jun 27, 2019.

  1. altjx

    altjx Member
    Thread Starter

    Hi guys,

    I have been going through hell and back over the last week trying to get Google Play installed on Android Studio. Of course there are images that come with Google Play pre-installed, but I cannot root those images using adb root.

    Therefore, I have installed an Android image in Android Studio that supports Google APIs and have been trying to manually push OpenGApps onto the image. This has been a nightmare. I finally got it to work and now a few days later Google Play is no longer installed and the Pixel Launcher just keeps crashing.

    Here's what I've tried thus far:

    I ran into an installer that someone wrote in bash over here https://gist.github.com/cunneen/1c0d9717f8ce5ea76900ba32fa037047 and tried to replicate the results manually. Last week, things were fine. However, today, I have tried repeating the process since Google Play decided to uninstall itself.

    Here's the error that I'm running into along the process:

    Code (Text):
    1. [myuser@mbp.local:...x86-9.0-stock-20190618/Core]$ "${ANDROID_HOME}/emulator/bin64/e2fsck" -f "${HOME}/.android/avd/${AVD}.avd/system.img"                  8:11AM/06.27
    2. e2fsck 1.42.13 (17-May-2015)
    3. ext2fs_open2: Bad magic number in super-block
    4. /Users/myuser/Library/Android/sdk/emulator/bin64/e2fsck: Superblock invalid, trying backup blocks...
    5. /Users/myuser/Library/Android/sdk/emulator/bin64/e2fsck: Bad magic number in super-block while trying to open /Users/myuser/.android/avd/Pixel_2_API_28.avd/system.img
    6.  
    7. The superblock could not be read or does not describe a valid ext2/ext3/ext4
    8. filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
    9. filesystem (and not swap or ufs or something else), then the superblock
    10. is corrupt, and you might try running e2fsck with an alternate superblock:
    11.     e2fsck -b 8193 <device>
    12. or
    13.     e2fsck -b 32768 <device>
    This seems to be the only hiccup that I've encountered now when trying to re-install Google Play onto this Android image. I have tried the previous step, which is to copy the Android system image from $ANDROID_HOME/system-images/android-28/google_apis/x86/system.img to replace the system.img in the AVD folder, but I still get this error.

    Has anyone been able to successfully accomplish this, or is this not even possible? It seems that when I ask this question on StackOverflow, there's crickets... as if no one ever does this or something.
     

    Advertisement

  2. ocnbrze

    ocnbrze DON'T PANIC!!!!!!!!!

Loading...
Similar Threads - Installing Google Play
  1. Missingphy
    Replies:
    13
    Views:
    335
  2. OM2
    Replies:
    4
    Views:
    280
  3. theartfullodger
    Replies:
    3
    Views:
    422
  4. MagicMM
    Replies:
    11
    Views:
    608
  5. John C Snell
    Replies:
    5
    Views:
    190
  6. Moriss23
    Replies:
    2
    Views:
    914
  7. KBU2
    Replies:
    10
    Views:
    634
  8. ken williams
    Replies:
    2
    Views:
    659
  9. Muhammad Waleed
    Replies:
    0
    Views:
    3,649
  10. greenmark
    Replies:
    1
    Views:
    1,358

Share This Page

Loading...