Related
This is just a simple build.prop mod to fix the fingerprint back to the working ERE27 one used in CM. Everything in Settings still shows FroYo, but the Market sees you as ERE27 & thus gives you your protected apps back
To install run this from the directory you unzip the file to:
ADB Method:
Code:
adb remount
adb shell rm /system/build.prop
adb push froyo.prop /system/build.prop
adb shell reboot
Then, once it reboots, go into the dialer, and type
Code:
*#*#CHECKIN#*#*
which is
Code:
*#*#2432546#*#*
for those of you who are too lazy to read the letters
A message should pop up into the status bar after a few seconds depending on your connection speed saying checkin succeeded.
Now you're good to go, open Market and download away
EDIT: Since I know some of you will wonder what this does, it just changes the ro.build.fingerprint & ro.build.description settings back to ERE27. This alone would normally be enough, but you're depending on luck to when you next check in. Dialing that code in the Dialer will force a checkin.
EDIT 2: Thanks to Shafty023 here is a method for the shell:
LINUX SHELL METHOD
Copy froyo.zip to /sdcard, then open a Terminal shell on your phone
Code:
su
mount -o remount,rw /system
cd /system
mv build.prop new.build.prop
unzip /sdcard/froyo.zip
mv froyo.prop build.prop
rm /sdcard/froyo.zip
reboot
Upon booting back up, open Dialer and type in the following code
Code:
*#*#2432546#*#*
Once you see a notification in the notification bar that says checkin succeeded you can now open Market and are done.
Nice! Trying it now.
EDIT: Working great so far. Thanks!
athereal said:
Nice! Trying it now.
EDIT: Working great so far. Thanks!
Click to expand...
Click to collapse
testing it in a few minutes too.... [UPDATE: works like a charm!]
Nice job Geniusdog254! really nice
thanks!
Thanks, works great!
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Part Four said:
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Click to expand...
Click to collapse
Use one of the root file explorers to unzip the file, delete the old build.prop, put the new one in, and then type the command in the dialer
Works like a charm, thanks!
Worked great, THANK YOU!!!!!
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
dudebro said:
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
Click to expand...
Click to collapse
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Mikey1022 said:
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Click to expand...
Click to collapse
yeah, I was wondering if it worked because I was getting checkin failed.
bluehaze said:
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
Click to expand...
Click to collapse
Apps don't have to be updated to take advantage of JIT at all. They can be optimized but they can be optimized without JIT too. There are no different versions. JIT just converts the Java/Dalvik code into native code at app launch, instead of running it through the slower virtual machine. Its like C++ vs Java on a desktop, the native code (C++) is much faster when executed.
The only thing this will lead to is when apps start showing up in the Market as 2.2+ only, but by that point Google will have updated the market to recognize the new footprint.
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
Pure calender widget (agenda) is a protected app taht doesnt show up in the 2.2 market
Edit: Works perfect! Thanks.
If you are having problems with the checkin, make sure your on 3g and not WiFi.
Mi|enko said:
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
Click to expand...
Click to collapse
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Geniusdog254 said:
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Click to expand...
Click to collapse
Yea, im not getting any of the GameLoft games.
serialtoon said:
Yea, im not getting any of the GameLoft games.
Click to expand...
Click to collapse
Even after this?
So I have to send my phone in to Tmo - I'm having accelerometer issues so they're sending me a new one. I've unrooted and have removed everything else but I can't remove the MCR SCRIPTS that was installed when doing the lag fix. Can you guys help? Thanks!
solution
I had the same problem, used one click root program to root my vibrant again. Then I downloaded "super manager" from the market. opened super manager went to apk, scrolled to the bottom found mcr scripts destonation ( system/app/ase_mcr_r25.apk) then I downloaded "terminal emulator" from the market. Open terminal emulator and type;
$su
# rm -r /system/app/ase_mcr_r25.apk
This removed it for me, make sure you verify the location on your phone. I'm not sure if it would be the same for you.
hope this helps
Hondatech44 said:
I had the same problem, used one click root program to root my vibrant again. Then I downloaded "super manager" from the market. opened super manager went to apk, scrolled to the bottom found mcr scripts destonation ( system/app/ase_mcr_r25.apk) then I downloaded "terminal emulator" from the market. Open terminal emulator and type;
$su
# rm -r /system/app/ase_mcr_r25.apk
This removed it for me, make sure you verify the location on your phone. I'm not sure if it would be the same for you.
hope this helps
Click to expand...
Click to collapse
worked great, THANKS!
had to install a diff terminal emulator as the one listed FC on Vibrant Rooted. But was able to remove MCR.
Also worked for me. I was looking everywhere to figure this out. Thanks for your information.
No, this isn't a joke. But I got my Google Music invite yesterday morning and just finished uploading my whole music library to the cloud just now. Then I decided to try out streaming music from the Google Music app I downloaded from the Market, with the help of MarketEnabler (this app isn't available outside the US).
Every song that isn't on my SD card crashes when I try to stream it via WiFi or 3G. This was an extremely frustrating problem. I searched a bit online and found three threads on three separate forums (DROID forums, one locally here in General, and the Google Mobile forum) with the solution being to enable ads.
Now, I read somewhere that this ROM has adblocking by default. I tried searching the ROM thread with the queries, "adblock", "ad", and "adfree" to no avail. My memory's a bit fuzzy as always, so this might not have been true. Can someone verify for me that Blay0's ROM actually blocks ads? And if so, can I be shown how to remove it? Pretty please?
Once again, this is no joke. I've provided a legitimate reason as to why I'd like ads turned on. Music's quite important to me, gets my life rolling.
Thanks everyone for the help!
EDIT: I find it a bit strange that the solution requires ads to be enabled, despite looking at screenshots of the app running on other phones and ROMs. Nonetheless, it seems to work. Interesting how that works.
To enable ads, replace the content of /system/etc/hosts with
127.0.0.1 localhost
EUGH IT DOESN'T WORK, but thanks for the quick reply, and it might actually work for some Americans!
For future reference, for anyone who actually uses the search function and digs this thread up, I flashed this:
http://forum.xda-developers.com/showthread.php?t=741435
Asovse1 said:
EUGH IT DOESN'T WORK, but thanks for the quick reply, and it might actually work for some Americans!
For future reference, for anyone who actually uses the search function and digs this thread up, I flashed this:
http://forum.xda-developers.com/showthread.php?t=741435
Click to expand...
Click to collapse
COol and this worked for you?
Yep, ads on. Tons of "em too.
Sent from my HTC Legend using XDA App
Asovse1 said:
Yep, ads on. Tons of "em too.
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
Would you have an updated link or post them here... coz the links expired...
thanks
Enable ads as I said above.
To disable ads, get an up to date hosts file
from the link to the hosts server (still works
And replace the file with this script:
adb reboot recovery
+/+/ then +/+/
adb shell mount /system
adb push hosts /system/etc/hosts
adb shell chmod 644 /system/etc/hosts
adb reboot
doubleup said:
Enable ads as I said above.
To disable ads, get an up to date hosts file
from the link to the hosts server (still works
And replace the file with this script:
adb reboot recovery
+/+/ then +/+/
adb shell mount /system
adb push hosts /system/etc/hosts
adb shell chmod 644 /system/etc/hosts
adb reboot
Click to expand...
Click to collapse
i'm S-ON... so i dont think i can modify the files...
i tried it for gps.conf... and it FC everytime
you can replace any system file via recovery
you can do it manually or you get an update zip
written by someone that will do the same thing
Hey guys, I came up with a basic set of tools which I find useful. You may redistribute , include in any custom ROMs and/or distributions.
This includes:
Rewrite /default.prop for ADB
Install and deploy busybox in /system/xbin
install bash, ipctool, strace, tcpdump, and viewmem binaries.
To install, you must be rooted.
Unzip the attached file
place it on your nook.
cd to the folder you installed
Run the following
Code:
sh /sdcard/BHT/run.sh
Please note, I use Android Market app QuickSSH to get into my nook terminal, your results may very.. I hope someone else grabs these files and makes it all more user friendly. I've got too many other things going on.
I encourage other developers to include these valuable debugging tools in their packages.
You, sir, are a monster! You get my vote.
Sent from my Nexus S using xda premium
AdamOutler said:
Hey guys, I came up with a basic set of tools which I find useful. You may redistribute , include in any custom ROMs and/or distributions.
This includes:
Rewrite /default.prop for ADB
Install and deploy busybox in /system/xbin
install bash, ipctool, strace, tcpdump, and viewmem binaries.
To install, you must be rooted.
Unzip the attached file
place it on your nook.
cd to the folder you installed
Run the following
Code:
sh /sdcard/BHT/run.sh
Please note, I use Android Market app QuickSSH to get into my nook terminal, your results may very.. I hope someone else grabs these files and makes it all more user friendly. I've got too many other things going on.
I encourage other developers to include these valuable debugging tools in their packages.
Click to expand...
Click to collapse
I can turn this into an apk, if you don't mind. By turn on adb with this method, adb will be rooted and the device will still be allowed to sleep?
brianf21 said:
I can turn this into an apk, if you don't mind. By turn on adb with this method, adb will be rooted and the device will still be allowed to sleep?
Click to expand...
Click to collapse
By all means. Please do.
My vote too. I just hope after you win that you keep up the great work on the Nook Tablet. The last two weeks or so have looked very promising towards getting custom roms on here and a lot of that has to do with Adam's hard work along with a few others
Nearly all of these are already in snowball-mod, but I'll include ipctool, and viewmem for the next release.
cfoesch said:
Nearly all of these are already in snowball-mod, but I'll include ipctool, and viewmem for the next release.
Click to expand...
Click to collapse
How did you get default.prop reread into memory? The only think I can see is the 2nd init hijack? Am I missing something a lot easier?
brianf21 said:
How did you get default.prop reread into memory? The only think I can see is the 2nd init hijack? Am I missing something a lot easier?
Click to expand...
Click to collapse
Note, I said "nearly all". I don't really see though how changing /default.prop would keep over reboots... rootfs is stored in memory and recreated every time, isn't it?
I've added the binaries to NT Hidden Settings. I have not implemented /default.prop swap yet. I have to play with hijacking init before I do. Thanks again.
brianf21 said:
I've add the binaries to NT Hidden Settings. I have not implemented /default.prop swap yet. I have to play with hijacking init before I do. Thanks again.
Click to expand...
Click to collapse
cool. where are you hosting that binary? I currently have a mirror set up at nook1.adamoutler.com for easy access... When someone gets a new device, they need to download 3 things onto their device to make it a real tablet.. nook1=hidden settings, nook2=homecatcher, nook3=market.. I may change 3 to launcherpro, but hidden settings is the number1 tool required for the nook Tablet.
AdamOutler said:
cool. where are you hosting that binary? I currently have a mirror set up at nook1.adamoutler.com for easy access... When someone gets a new device, they need to download 3 things onto their device to make it a real tablet.. nook1=hidden settings, nook2=homecatcher, nook3=market.. I may change 3 to launcherpro, but hidden settings is the number1 tool required for the nook Tablet.
Click to expand...
Click to collapse
Homecatcher? I mean, I understand if you want to keep using the B&N store and stuff, but if you don't care about the B&N stuff, then the hacked SystemUI.apk is a way better option than Homecatcher.
But then, you're advancing "launcher pro", while I would more generally say "any non-B&N launcher"...
I added another option to nt hidden settings to run adb as root. It doesn't require a reboot and it automatically turns off auto mount. I am using nemith's adbd.
remount / as rw
stop adbd
replace /sbin/adbd
remount / as ro
setprop to turn off auto mount
start adbd as root
It's not persistent after reboot, but it works and doesn't kill the battery. I am not going to bother with hkvc's hijacking init method, because it looks like you, hkvc, bauwks, and nemith will be able to replace the os soon. Thanks.
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"