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?
Coming soon: Full access to the 2.x market.
Progress is being made to bring the new market to the NC (less the FC permissions or APK signature issues.) Check posts towards the end of this thread for more info.
UPDATE - Version 1.1a - 4/27 - NOW WITH MORE ROOT!
I'm happy to announce that I now have a much improved version of apk-enabler all packaged up and ready to install. This version will work much better than the last one, and should provide much better application compatibility.
Version 1.1a:
Major update...
* Added Edify code to clean up old versions before installing or re-installing (either version)
* Updated su (version 2.3.6.1 - thanks dascud)
* Updated and relocated Superuser.apk (now lives in /data/app so updates will not complian about it being a "system application" anymore.)
* Added Zeam 2.9.2 to /data/app
* Added NookColorTools to /data/app
* Added SoftKeys 3.06 to /data/app (in case anyone needs this - some apps don't display the nook status bar properly.)
* Added latest busybox binary to /system/bin
* Added a crapload of symlinks to busybox functions in /system/xbin. Almost everything works now (grep, mount, etc) without having to run through busybox or toolbox. (thanks RileyGrant)
* I have attempted to perma-enable adb by setting the adb_enabled value in /data/data/com.android.providers.settings/databases/settings.db. Unfortunately it appears that this setting is ignored - at least when auto mounting is enabled. See notes below.
Notes:
Now that we have busybox and a current version of su, we now have what resembles a "normal" android shell environment. More apps should work with the updates, and we can now get a shell (then su) via adb. You can also run the Android Termainl app and su from there.
Also, since Zeam and SoftKeys now baked in, the first boot will now ask for your preference of default launchers (Home, SoftKeys, or Zeam.)
To get ADB working, you need to update your drivers, and play with settings in NookColorTools (development section) to enable USB debugging.
I have validated this install via a fresh install and over-top of existing installs. The only requirement is that the Nook has been turned on and registered. You can flash this over older versions, the script cleans up cruft from prior runs before installation.
Original Post:
So I went about fooling around with the stock 1.2 ROM, and like many I was frustrated by the lack of certain apps in the Nook app store. So here's a little work-around until we get a properly rooted solution in place:
What this hack does:
* Updates the SQLite Settings Database (data/data/com.android.providers.settings/databases/settings.db) with a hacked version, enabling the install_non_market_apps and adb_enabled settings.
* Installs a version of "su" in /bin and /xbin.
* Installs busybox to /system/bin and sets symlinks for most shell commands in /system/xbin
* Installs SuperUser.apk, SoftKeys_3.06.apk, NookColorTools_0.2.apk, and zeam-2.9.2.apk to /data/app (you may uninstall any of these if you wish.)
* With these in place, the stock browser (and other Market apps) are fully capable of downloading, launching, and installing .apk files of your choosing.
Is this safe? What if I brick my Nook?
The Nook Color bootloader will boot anything you throw at it. There are no signature checks anywhere, and even their own code is signed using test keys. If you get a bad flash or whatever, you can always boot your Clockwork SD card and restore from there. Remember - this is not a phone - there is no subsidy or baseband to protect. So, no there's no S-ON, locked boot loader, or any of that other silly crap the carriers do to screw their customers. You can flash forwards, backwards, sideways, whatever you want, as long as you can put it on an SD card.
Overall, this is no more dangerous than running a stock android device with the "Unknown Sources" setting enabled. Nothing is happening yet that is uncharacteristic of a "standard", vanilla android device.
That said, you should probably make a backup while you are running Clockwork, just to be on the extra-safe-side.
So, is this a full ROM that I can use to flash the 1.2 update?
No. This is a stand-alone update to 1.2 that overwrites one file and adds two others. You need to have 1.2 up and running in order to use this.
How to install...
First, you must have a microSD card already flashed with ClockworkMod. I'm not getting into that, you can find a good guide in this post:
http://forum.xda-developers.com/showthread.php?t=987735
(thanks fpga_guy)
NOTE - THIS WILL ERASE YOUR SD CARD - SO YOU MIGHT WANT TO PICK UP A CHEAP 2GB CARD FOR THIS.
* Once you have Clockwork set up, drop the attached zip in the root directory, and reboot your Nook Color. Once Clockwork is booted:
* Select "install zip from sdcard", then "choose zip from sdcard"
* Select "Yes - Install apk-enabler-1-1a-signed.zip". The install process will begin promptly.
* Once flashed, you will be prompted to Reboot,
* The Nook OS will almost certainly crash on the first reboot - I'm not sure why as of yet... If it does, hold the power button until the Nook powers off completely, then turn it back on. It should continue to boot normally after this point.
* Once you are back up, you can use the browser to download and run .APK files from anywhere. Some apps do not work, others do. Fortunately for us, Superuser.apk is one that does
As for launchers, you will not see your installed apps in the Extras area of the stock launcher - B&N is doing something shady here... Instead, you will need to install another Launcher. Zeam seems to work well, while ADW doesn't.
Once Zeam is installed, you can hit the "Home" button and select it as your Launcher (permanantly, if you like...) This is where you'll see all of your downloaded apps.
I have attached the flashable zip file, plus links to SuperUser.apk and Zeam. Use the built-in Nook browser to install both of these to your device. Once you download an APK file, tap the notificaiton in the lower left corner and select "Package Installer." The usual Android install screen will appear, and you know what to do from there...
What's not working?
Probably lots of things. I know ADW doesn't work, and the open source Terminal emulator doesn't either... Superuser.apk detects SU, which is a good thing. It isn't "full root access" until I hack /etc/fstab to mount /system r/w (probably tomorrow.) B&N hacked up the frameworks pretty bad for this, so there are probably lots of issues with non-market apps. However, this should open the door to someone willing to port Nookie Froyo (or something similar) over to the stock 1.2 ROM.
Credit where credit is due:
First, thanks to everyone on XDA, the official Nook forum, CyanogenMod, NookDevs, some kind folks on IRC who helped me sort out the partition layout, some helpful folks in this thread, and probably 20 others that I'm forgetting. This would not have been possible without your help.
Where do we go from here?
I suspect we will have something more like Autonooter in a day or so... However, this is a fully usable solution for the time being. You have su, busybox, Superuser, SoftKeys, and a Launcher.
Also, someone needs to look into getting side-loaded apps onto the home-screen and/or into the Extras screen. My fear is that B&N is checking signatures there - but hopefully I'm wrong on that one....
Version 1.1a: apk-enabler-1-1a-signed.zip (1.28mb)
md5sum: 65267cf3314d7fae829881970d70b444
http://www.mediafire.com/?bb7o66282bqfp6q
Apps known to work:
Superuser
Zeam
SoftKeys
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
ES file explorer
Pulse (with widgets)
Facebook
Evernote
Remember The Milk
Subsonic
WP Clock - Live Wallpapers are enabled by default - the Google Maps and WP Clock live wallpapers appear in the stock Nook Home settings
Free Dictionary
TV.com
TuneIn Radio
Winamp
LastPass
Xmarks
Dolphin
DocumentsToGo
cVolume
FancyWidget
Google Voice
ReadItLater
Button Savior
Dropbox
Adobe Reader
TerminalEmulator
Apps known not to work:
Any version of GApps. Especially those packaged for Gingerbread. This is a B&N issue.
ADWLauncher
aldiko (via kingsjack)
other Input Method (via kingsjack)
appmonster (via kingsjack)
gscript lite (via kingsjack)
GApps don't work because framework.jar needs to be ported from another release. B&N broke it.
Alternative keyboards and things like that will probably break (again, due to dependancies that have been broken by B&N.)
Fortunately, B&N left enough of the package installer intact to allow us to get this far.
(feel free to add to this list, I'll only test what I personally plan to use.)
Thanks for getting off market working
Sent from my SPH-M910 using XDA App
Zero to sixty in no time flat. Gracias Senor, now I can dual boot this and the incredibly speedy cm7 builds and have the best eReader on the market and a super great 7 inch tablet to boot.
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
kingsjack said:
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
Click to expand...
Click to collapse
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
HamNCheese said:
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
Click to expand...
Click to collapse
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
kingsjack said:
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
Click to expand...
Click to collapse
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
HamNCheese said:
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
Click to expand...
Click to collapse
without this Options
kingsjack said:
without this Options
Click to expand...
Click to collapse
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
HamNCheese said:
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
Click to expand...
Click to collapse
thank u work
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
GabrialDestruir said:
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
Click to expand...
Click to collapse
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....
What you describe is simply a tweak to /etc/fsatb and possibly some changes here and there in some init scripts. It shouldn't be a difficult update, re-mounting file-systems isn't exactly the hardest thing to do in Linux.
The big headline here is "load apps from untrusted sources" - something that the Nook Color is physically incapable of doing out-of-the-box. In fact, their plan is exactly the opposite. Entangle the user with app purchases that they can't get anywhere else, and cannot transfer in or out of the Nook ecosystem. That problem is solved for now, and it should do what 90% of users want right out of the box.
We can discuss the next phase after evaluating the changes to frameworks and whatnot that will get Gapps and other crucial stuff up and running - that will prove to be a more difficult task than simply breaking in to the stock system. Judging by work that was done for previous iterations of Autonooter, there are enough framework changes that it's going to take some time to work out the details.
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
GabrialDestruir said:
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
Click to expand...
Click to collapse
Hmmmmm.....guess I'll have to spring for root explorer and dig through logcat to see what's going on. It could totally be some goofy B&N thing that's screwey on this one device. More after the break....
HamNCheese said:
Apps known to work:
Superuser
Zeam
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
Apps known not to work:
ADWLauncher
TerminalEmulator
(feel free to add to this list, I'll only test what I personally plan to use.)
Click to expand...
Click to collapse
Please explain how you got amazon appstore on there. I signed in on mazon had it send me the link on the nook to download it which i did. When i clicked on it brought up chice to run with app installer or package installer of which one gave me a parse error and the other did nothing.
Any ideas?
So, is this a full rom that I can flash my 1.1 nook into 1.2?
HamNCheese said:
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
Click to expand...
Click to collapse
Hint.. They already have in this thread.
HamNCheese said:
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....[/B][/B][/I]
Click to expand...
Click to collapse
installing rom manager and running fix permissions should set all the right files to rwxrwx--- shouldnt it? i havent installed the update cuz im happy with cm7 so i cant test it..
Sent from my NookColor using Tapatalk
Good work Ham. The apps used to show after rebooting under the Extras section(Now called Apps), they are not now after the framework butchering they did. However, I installed Applanet and all I had to do was a search on the device and there it was. It launched fine and downloaded apps no issue.
I was wondering if anyone has figured out a way to get HULU to work. Thanks!
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
erick161 said:
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
Click to expand...
Click to collapse
Hulu does not work in webOS.
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
they blocked the new method too?
both WebOS and Cm7 works with Hulu....same method (mod flash and change user agent)
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
erick161 said:
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
Click to expand...
Click to collapse
Ahh never knew there was a fix for the fix.
Edit: Mind linking?
was working till the webOS upgrade to 3.0.4
this workaround was working until the new webos 3.0.4 the new update...the patch says ” could not find area to patch (unknown file version)
claptop dot com/2011/08/make-hulu-work-on-hp-touchpad/comment-page-1
I fixed hulu with a patch for 3.0.4...
It's an alpha, it's quick and dirty, but it works. Find the patch itself here:
forums DOT precentral DOT net/3218146-post139.html
For some reason I can't upload it here (maybe not enough posts or something).
Ok, after much annoyance and a couple webOS doctors, I think I FINALLY have an all-in-one fairly idiotproof patch...
WARNING!!!!!! If you have already done this patching process manually, this patch MAY NOT WORK! You may break your flash player if you run this patch after having performed the manual work and require a visit to the webOS doctor! DO NOT RUN THIS PATCH UNLESS YOUR TOUCHPAD IS COMPLETELY BACK TO STOCK ON IT'S USER AGENT AND FLASH IDENTIFIER STRING.
Please note, this is an ALPHA patch. It will likely throw an error or two but it should work. You should be able to run this patch and it will install the hulu user agent fix AND the flash fix without requiring a reboot. Again, this is an ALPHA patch and I am not responsible if you install it and it magically borks your touchpad. This will do nothing a webOS doctor won't fix, so gauge your willingness to test this patch on whether or not you'd be ok running a doctor if things go wrong.
To install:
Step one: Download the file attached to THIS post and EXTRACT (unzip) it to an easy to find spot (like your desktop).
Step two: "send" this file (tools > send file) using webosquickinstall to /media/internal
OR: put the touchpad into USB mode and drag/drop this EXTRACTED file to your touchpad (that will automatically put it in the /media/internal directory)
Step three: open a linux command line (tools > linux commandline) in webosquickinstall
OR: open a terminal window on the touchpad itself in xterm (you will need to install xecutah, xserver, and xterm from preware to do this).
Step four: type this exactly into the terminal window:
/media/internal/hulu
The device will very likely pop an error or two (again this is an ALPHA patch), but it should finish up without any real trouble in under 30 seconds. There is NO reboot required.
TADA, HULU works once more! Your app catalog is now broken.
If it's still not working (black screen on videos) you need to remove any adblocking patches you have (adblock or max blocker), delete cache/history/cookies in the browser, and reboot the touchpad. Now Hulu will work.
When you want to fix your app catalog so you can download new programs, go back to the linux command line again (in webosquickinstall) and type:
/media/internal/hulu uninstall.
This will break hulu and fix your app catalog. It'll take 30 seconds or less to complete and you're back in business.
The patch will stay on the device, so you can easily flip back and forth from hulu installed and uninstalled.
Perhaps he doesn't want to subscribe??
There are patches and fixes etc etc for other phones, and I'm sure ultimately its all the same.. its just like the WebOS packages.. Im sure you can apply it on the touchpad, but I haven't done it or anything.. this is to allow you to watch it within a browser of course.. app is great if you pay for it..
Ya Im a poor college kid so I was really wondering what was the latest and greatest modded flash zip file. There are a few million online and I didnt want to have to flash 20 before I got one that worked. In the end I was able to find one that works like a charm so thanks guys!
Hulu!
Uninstall what ever version of adobe flash (if any). Search Vgeezyflash 74 in google, it should be the first post on a "toshiba Thrive" forum. Download the modified adobe flash 11 .apk ("apk" is file for you noobs. Install, and reboot for good luck. Then open the android stock browser (i could never get it to work right on any other), change the user agent to IE6 and delete all cookies, etc. This process worked for me on the Touchpad and on my Nook Color.
or...just go to
Code:
http://download.hulu.com/huludesktop.swf
tested...working on webos
Hulu working
Have you hit the upgrade prompt?
it seems to work better if you click ignore...but still works either way
hulu on WebOS
takes a few tries but it will go eventually - I've tried either way as well - sometimes shows crash in the middle of the episode and you have to start over - as well as restarting the instance randomly - hit Menu and select TV - starts to spool and eventually will take you to start again
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
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"