[MOD][XPOSED]Google Play Store (2013/07/05)

dark_saian

Senior Member
Jan 13, 2009
90
11
0
Make sure you run the line that goes
mount -orw,remount /system

That should remount /system as read/write.
I can't do that. Even entering adb shell is returning an error.

Code:
[email protected]:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ # mount -orw,remount /system
sh: mount: not found
127 [user=1901967]@androi[/user]d:/ #
As a result, I was able to install su and busybox, but busybox isn't working.

[CODE @android:/ $ su
sh: /system/etc/mkshrc[8]: id: not found[/CODE]

The weirdest thing is at the time the line above appear in the terminal, I have a message on the TV screen saying "Superuser granted to shell", which is confirmed by the Superuser app log.
 

gianptune

Senior Member
Oct 10, 2010
212
87
0
I can't do that. Even entering adb shell is returning an error.

Code:
[email protected]:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ # mount -orw,remount /system
sh: mount: not found
127 [user=1901967]@androi[/user]d:/ #
As a result, I was able to install su and busybox, but busybox isn't working.

[CODE @android:/ $ su
sh: /system/etc/mkshrc[8]: id: not found[/CODE]

The weirdest thing is at the time the line above appear in the terminal, I have a message on the TV screen saying "Superuser granted to shell", which is confirmed by the Superuser app log.
You've broken something somewhere along the way. Did you happen to follow one of the many poorly written 1-click-fail-scripts floating around the Ouya forums? It seems that /system/etc/mkshrc is calling for the program `id` which is usually a symlink in /system/bin/id that points to /system/bin/toolbox. Maybe you did something to break the id symlink or the toolbox binary it points to. `mount` is also *usually* a simlink from /system/bin/mount to toolbox. this says you somehow broke that one, too.

At any rate, it looks like you are actually getting a root shell, hence the '#' prompt.
 
Last edited:

dark_saian

Senior Member
Jan 13, 2009
90
11
0
You've broken something somewhere along the way. Did you happen to follow one of the many poorly written 1-click-fail-scripts floating around the Ouya forums? It seems that /system/etc/mkshrc is calling for the program `id` which is usually a symlink in /system/bin/id that points to /system/bin/toolbox. Maybe you did something to break the id symlink or the toolbox binary it points to. `mount` is also *usually* a simlink from /system/bin/mount to toolbox. this says you somehow broke that one, too.

At any rate, it looks like you are actually getting a root shell, hence the '#' prompt.
I did try the following scripts :
- http://forum.xda-developers.com/showthread.php?t=2272266 for rooting my Ouya
- the one provided at the beginning of this topic for the Google Play hack
- http://forum.xda-developers.com/showthread.php?t=2295645 and this one in an unseccessful attempt to flash a CWM based recovery.

After all that, I did several factory resets but found that the Google Play and Google Settings apps were still installed since they are system apps.

How can I do a true reset of the firmware, which will hopefully solved my broken root problem ?
 

muriani

Senior Member
Nov 3, 2009
98
14
0
I did try the following scripts :
- http://forum.xda-developers.com/showthread.php?t=2272266 for rooting my Ouya
- the one provided at the beginning of this topic for the Google Play hack
- http://forum.xda-developers.com/showthread.php?t=2295645 and this one in an unseccessful attempt to flash a CWM based recovery.

After all that, I did several factory resets but found that the Google Play and Google Settings apps were still installed since they are system apps.

How can I do a true reset of the firmware, which will hopefully solved my broken root problem ?
Basic answer, you'll need to reload the stock image from recovery.
You can get the latest Ouya stock image from https://ouyafw.skumler.net/

I don't know if you can use the stock recovery to flash it, the first thing I did was get CWM installed before I touched anything on mine.
Someone else might know more on that.
 
  • Like
Reactions: dark_saian

elmerohueso

Senior Member
Nov 29, 2010
568
224
0
Provo
Installed XPosed, rebooted, and now I just get a black screen. I still do have ADB access, though. I'll probably have to grab one of the OTAs and flash it (which means I need to find a keyboard). Any tips on an easier method?
 

mikeones42

Senior Member
May 10, 2008
58
25
0
I have installed Xposed and this play store mod but I am getting connection timed out when launching the play store. Here is my logcat. http://pastebin.com/5Tp6y0nM

Edit

I went back into Exposed are re-ran the installer and then rebooted. Once the ouya came back up I went back into google play and the license agreement screen appeared. Once I accepted the license, google play store loaded without issue.
 
Last edited:

evaporic

Senior Member
Aug 3, 2011
100
14
0
Detroit
I can't do that. Even entering adb shell is returning an error.

Code:
[email protected]:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ # mount -orw,remount /system
sh: mount: not found
127 [user=1901967]@androi[/user]d:/ #
As a result, I was able to install su and busybox, but busybox isn't working.

[CODE @android:/ $ su
sh: /system/etc/mkshrc[8]: id: not found[/CODE]

The weirdest thing is at the time the line above appear in the terminal, I have a message on the TV screen saying "Superuser granted to shell", which is confirmed by the Superuser app log.
Working Perfectly!!
You may need to avoid ADB so you don't run into errors.
Instead:
1. Sideload xposedinstaller and install from ES File explorer
2. open XposedIntaller, click install/update then reboot
3. Sideload Mod_PS4Ouya.apk
4. open XposedInstaller and enable PS4Ouya
5. reboot
6. sideload google apks in files to push folder
7. use file explorer to move apks to system app
8. change permissions of sideloaded apks to chmod 644
9. Reboot
 

Oscar_david

Senior Member
Apr 12, 2012
275
53
0
App demonstration videos aren't working for me. Is this a known issue, or am I missing something?

thanks.


edit: probably related to: Youtube not working for me since I installed the Play Store.

Sent from my OUYA Console using xda app-developers app
 
Last edited:

Kavex

Member
Jul 8, 2013
16
4
0
Working Perfectly!!
You may need to avoid ADB so you don't run into errors.
Instead:
1. Sideload xposedinstaller and install from ES File explorer
2. open XposedIntaller, click install/update then reboot
3. Sideload Mod_PS4Ouya.apk
4. open XposedInstaller and enable PS4Ouya
5. reboot
6. sideload google apks in files to push folder
7. use file explorer to move apks to system app
8. change permissions of sideloaded apks to chmod 644
9. Reboot
Lol funny thing is I did this very way too
 

robinscp

Senior Member
Feb 20, 2012
80
7
0
I am having a few issues with es file explorer having permission to paste files into the system/app folder.

Any ideas?

Sent from my GT-I9100 using xda app-developers app
 

robinscp

Senior Member
Feb 20, 2012
80
7
0
I forgot to use the tools section of es to make the system folder writable. That got it working.

Sent from my GT-I9100 using xda app-developers app
 

Disrespective

Senior Member
Apr 10, 2010
52
6
0
Wellington
How do you run a .bat file from ES Explorer/Root Explorer? When I go to run it, it just opens in a text editor or asks me what I want to open it in. I feel like i'm missing something obvious?
 

backlund

Senior Member
Aug 11, 2008
71
12
0
Is anyone else having a number of issues with some apps force closing as soon as you start them? It appears that any apps that use Googles Ads seem to crash. Checking logcat seems to indicate that there are some pieces of Google's ad framework still missing. Here's an exception from a movie trailer app I downloaded. Other apps that have Google ads crash with similar exceptions.

FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start activity ComponentInfo{sk.wayout.amtfree/sk.wayout.amt.AppActivity}: android.view.InflateException: Binary XML file line #9: Error inflating class com.google.ads.AdView
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2059)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)
at android.app.ActivityThread.access$600(ActivityThread.java:130)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:110)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #9: Error inflating class com.google.ads.AdView
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:687)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:830)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:736)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethod(XposedBridge.java:624)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:455)
at android.view.LayoutInflater.inflate(Native Method)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:256)
at android.app.Activity.setContentView(Activity.java:1868)
at sk.wayout.amt.AppActivity.onCreate(AppActivity.java:121)
at android.app.Activity.performCreate(Activity.java:5021)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2023)
... 12 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 29 more
Caused by: java.lang.NoClassDefFoundError: android.gesture.GestureStore
at com.google.ads.internal.j.a(SourceFile:41)
at com.google.ads.AdView.a(SourceFile:544)
at com.google.ads.AdView.a(SourceFile:398)
at com.google.ads.AdView.<init>(SourceFile:126)

... 32 more
 
Last edited:

Silverbulletncsu

Senior Member
Jun 7, 2012
63
20
0
Raleigh
Working Perfectly!!
You may need to avoid ADB so you don't run into errors.
Instead:
1. Sideload xposedinstaller and install from ES File explorer
2. open XposedIntaller, click install/update then reboot
3. Sideload Mod_PS4Ouya.apk
4. open XposedInstaller and enable PS4Ouya
5. reboot
6. sideload google apks in files to push folder
7. use file explorer to move apks to system app
8. change permissions of sideloaded apks to chmod 644
9. Reboot
Did this and got everything up and running. Thanks BTW.

But now @ every boot and @ random intervals I get "Unfortunately Google Play Services has stopped." Although the apps will all run, except Pandora and Chrome.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone