Related
I want to share the versions of the Market and various Gapps that work for me on Sam's HC EMMC v4.0, 2nd ed. build {Huge props to him, deeper-blue, and others who got HC working on the NC. Without their heroic efforts, I'd be working 4 jobs right now trying to save up to buy a Xoom}
This script is the first one I run after doing a fresh build of HC EMMC, but you should also be able to do it on a stale version of HC as well.
Maps is version 5.0
While I am confident that these files will work for you as well, please remember, individual results may vary---use at your own discretion.
NOTE: The 'GoogleServicesFramework.apk' file in the attached .zip will remove the blue wi-fi icon from Sam's initial build. If you prefer the blue icon over a working Market (My Apps), then DO NOT proceed with the installation!
That being said, please do the following before trudging ahead:
+ Perform a full backup using your bootable CWR SD card [see samuelhalff's thread for instructions on this: http://forum.xda-developers.com/showthread.php?t=947071]
+ Backup each of the original files on your NC that will be replaced by the script
+ See #1 & #2 above...you've been warned
Instructions for Installation:
Extract the files contained within the attached .zip into the same directory as your ADB directory (where your 'adb.exe' file lives). Mine was located here on my computer: C:\android-sdk-windows\platform-tools
Connect your NC to your computer, ensuring ADB is working properly ahead of time
Double-click on the file 'HoneyGAppInstall.cmd' and the script to install the new apps will run
The script will reboot your NC upon completion
Once your NC comes backup from the reboot, you can then login to the Market, select "My Apps" and they should show up right away.
I have also attached the 'build.prop' file I use. This modified file allows me to see tablet apps (NY Times Tablet, More Good News Tablet) and also I can see/download/install both Angry Birds games.
NOTE: The ro.sf.lcd_density is set to 140 in my file. This is not friendly to Zeam and needs to be set to at least 150 for that launcher to work without Force Closing in Portrait mode.
Good luck and let me know if any issues.
EDIT: For those running a build that is not new and already has the original Market setup, would be best to do the following steps after running the Gapps script:
1.) Settings > Manage Applications > All > Market: Clear Cache then Force Stop -- DO NOT Clear Data2.) Settings > Manage Applications > All > Google Services Framework: Clear Data3.) Reboot
~ Razir
Would it be possible to flash the market zip through recovery? Looks like it would work in theory.
I can see all the installed apps on My Apps. Thanks for these files. But I have one problem. My Nook no longer shows up on market.android.com. Anyone else have this problem?
Is Youtube working?
JaysFreaky said:
Is Youtube working?
Click to expand...
Click to collapse
HQ videos don't work. If you disable HQ it works.
Vasanth said:
I can see all the installed apps on My Apps. Thanks for these files. But I have one problem. My Nook no longer shows up on market.android.com. Anyone else have this problem?
Click to expand...
Click to collapse
I don't use that site much, but I did just check it out of curiosity.
I verified it was working by going into: My Market Account > Settings tab. I can see "LogicPDZoom2" with last access of today's date.
bdcrim said:
Would it be possible to flash the market zip through recovery? Looks like it would work in theory.
Click to expand...
Click to collapse
Not being a dev, I don't know how to compile the files I attached and make them flashable.
However, I can tell you that I do have a black-themed Market by Darkslide for my DroidX that is flashable via CWR, but sadly, it did not work for me. I tried it by booting to the CWR SD card. Would have been nice to have the black-themed version.
I also have a flashable version of Zeam, but again, did not work for me.
Now, I have not tried it by going into CWR using Sam's method with his built-in utility. This is because I have not really been able to get that to work 100% of the time and also because it is just so easy to get to CWR via the bootable SD card that I have not really messed with it too much.
I can post the black-themed Market if someone smarter than me wants to take a look at it...might prove useful. I am just not sure if a DX file can be used on the NC
Just let me know and maybe we can figure it out together.
Vasanth said:
HQ videos don't work. If you disable HQ it works.
Click to expand...
Click to collapse
And you have to be pretty fast at disabling that little "HQ" icon in the top-right corner of the screen. From my experience, has to be almost instantaneous by the time it appears on the screen or the video won't load.
360Razir said:
I don't use that site much, but I did just check it out of curiosity.
I verified it was working by going into: My Market Account > Settings tab. I can see "LogicPDZoom2" with last access of today's date.
Click to expand...
Click to collapse
Thanks for checking. I did mess around with the build.prop you provided. I think I messed something up. I will use the file you provided without any changes.
Thanks.
Not being dev minded, I don't know how much help I would be. I was able to extract the apks from the zip file and move them with root explorer, changed permissions and it appears to be holding. Have rebooted twice and still good. Your script in the zip file would not work with cwr since it is windows based, I think. I don't know if the apks would install in recovery without a script, seems like it would not. Anyway, thanks for putting this together. Market works with the apks and the build. prop seems to have helped as well. Thanks again.
360Razir said:
Not being a dev, I don't know how to compile the files I attached and make them flashable.
However, I can tell you that I do have a black-themed Market by Darkslide for my DroidX that is flashable via CWR, but sadly, it did not work for me. I tried it by booting to the CWR SD card. Would have been nice to have the black-themed version.
I also have a flashable version of Zeam, but again, did not work for me.
Now, I have not tried it by going into CWR using Sam's method with his built-in utility. This is because I have not really been able to get that to work 100% of the time and also because it is just so easy to get to CWR via the bootable SD card that I have not really messed with it too much.
I can post the black-themed Market if someone smarter than me wants to take a look at it...might prove useful. I am just not sure if a DX file can be used on the NC
Just let me know and maybe we can figure it out together.
Click to expand...
Click to collapse
bdcrim said:
Not being dev minded, I don't know how much help I would be. I was able to extract the apks from the zip file and move them with root explorer, changed permissions and it appears to be holding. Have rebooted twice and still good. Your script in the zip file would not work with cwr since it is windows based, I think. I don't know if the apks would install in recovery without a script, seems like it would not. Anyway, thanks for putting this together. Market works with the apks and the build. prop seems to have helped as well. Thanks again.
Click to expand...
Click to collapse
You are most welcome and yes, the .zip is not flashable for CWR. XDA will only allow for certain types of files to be uploaded and .zip is one of them, so easier for me to go that route.
Files in the .zip are meant to be extracted into the folder where ADB.exe exists in order for the script to work correctly. As stated in the OP, I have only tested this on a Win7 box, as that is the only platform I have access to at the moment.
Root Explorer will also work, as you already know. So, for those who want to go that route, it is certainly an option. Glad things are working well for you at this point. Thanks for your feedback!
I'm just checking. These are the Android 3.0 gapps from the XOOM, not the 2.3 gapps? (Sorry I'm a little tired and don't have the emmc version installed, I run the SD card version, so I can't test ATM)
kdb424 said:
I'm just checking. These are the Android 3.0 gapps from the XOOM, not the 2.3 gapps? (Sorry I'm a little tired and don't have the emmc version installed, I run the SD card version, so I can't test ATM)
Click to expand...
Click to collapse
2.3, not 3.0.
Just transferred all the apps and the build.prop to a stale build of eMMC 2nd (3 days of use) and other than using root explorer followed the instructions to a T. My apps seemed to work but not thinking I updated maps in the market and now it doesnt work. Tried to uninstall updates in market (didnt seem to even finish the process), replace with my original apk, replace with apk from your zip here, clearing cache and data. Nothing seems to bring it back to life. Anyone else have this problem?
P.S. I think the white wifi icon looks nice.
Sent from my LogicPD Zoom2 using Tapatalk
Just used a combination of Root Explorer and ADB (for the chmod) to use your mod and everything is working great. Thanks a ton for posting this!
Only change I had to make was the LCD Density in the build.prop since I want to use Zeam. I tried using the default launcher but it is so laggy, I just can't.
lospulpo said:
Just transferred all the apps and the build.prop to a stale build of eMMC 2nd (3 days of use) and other than using root explorer followed the instructions to a T. My apps seemed to work but not thinking I updated maps in the market and now it doesnt work. Tried to uninstall updates in market (didnt seem to even finish the process), replace with my original apk, replace with apk from your zip here, clearing cache and data. Nothing seems to bring it back to life. Anyone else have this problem?
P.S. I think the white wifi icon looks nice.
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
Did you get your Maps back and working yet? If not, PM me and we can work on it together, offline. And if we can get it to work, we can post the "method to our madness" here in case others have done the same.
911jason said:
Just used a combination of Root Explorer and ADB (for the chmod) to use your mod and everything is working great. Thanks a ton for posting this!
Only change I had to make was the LCD Density in the build.prop since I want to use Zeam. I tried using the default launcher but it is so laggy, I just can't.
Click to expand...
Click to collapse
Glad all is working for you and that is a good point...I will update the OP to let folks know the build.prop has the LCD Density set at 160, which is not Zeam portrait-mode friendly.
Thanks for the feedback!
Okay, just downloaded the new Amazon Appstore and installed Angry Birds Rio (the first Free App of the Day). Force Close... so I tried both 140 and 160 LCD Densities and still no luck. Tried both of the other Angry Birds (original & seasons) and they force close on all three densities as well.
Any thoughts on why you are able to run them but I can't using the same build.prop? The only thing I had changed from your build.prop was the LCD density, but as I said, even changing it back to match your original setting doesn't make Angry Birds work.
Angry Birds and Angry Birds Seasons work for me. I had to move them to the internal memory. I already tried moving Rio to internal memory, however it still FC's. I can get the game to almost start, but when it's time to start shooting, it FC's. I haven't tried changing the LCD density.
Same issue here with Rio. Tried internal and no dice. Doesn't run at all when on SD.
So I've been having trouble trying to download an app I need. It's available in the stock Barnes & Noble App store as well as on the Android/Amazin marketplace for Honeycomb users. It's called Drawing Pad by Murtha Design and the little kid demands to have it! I've tried installing Froyo, Gingerbread and Honeycomb - my device shows up as "incompatible." I keep getting an error when trying to spoof my build.prop file into thinking it's a Motorola Xoom. I'm getting tired of trying to download this single app - so annoying! Does anyone know if it would be possible to go back to the stock ROM, download it and then save ithe APK onto my PC or SD card? From there install Honeycomb again and then try to install it? Better yet would it be possible for someone to buy it from their Xoom, transfer to SD and share the apk with me? Not sure if that's allowed but I would appreciate it beyond belief -.-
I used the file from here:
http://forum.xda-developers.com/showthread.php?t=1050520
to flash my rooted NC back to stock with CWM. CWM makes it easy to flash new roms with no need of a bootable SD.
Then I registered and whatnot followed by installing all my Nook apps. Once all the apps were installed I flashed MN 4.5.6
Since then I've flashed the newer MN followed by an overclocked kernel and other stuff.
The market will offer to update Nook apps that are on market, do not let the market update the apps.
Also Once everything is set to your liking avoid archiving Nook apps, there is a chance that it will not reinstall due to application space usage. I found that moving apps to SD helps with this, but do not move Nook apps to SD as they will show up as available to install again in Nook apps.
Hi everyone, I flashed my viewsonic gtab with tnt lite 4.4, and everything seems to be working fine, except that the android market thinks i'm using Malata GTablet-TnT-Lite...is there any way to fix this?
Thanks
Quicksilvr530 said:
Hi everyone, I flashed my viewsonic gtab with tnt lite 4.4, and everything seems to be working fine, except that the android market thinks i'm using Malata GTablet-TnT-Lite...is there any way to fix this?
Thanks
Click to expand...
Click to collapse
Actually, it is seeing it correctly, just not the way you want it to be seen. Your gTablet OEM is actually Malata. With the new version of Market, Google has attempted to tighten non-authorized device access. It gets device info from the build.prop file (/system/build.prop). If you are not having problems with limited app selection or downloading, you can leave as is.
If you are having limited app access/download problems then do a search for "market fix". You will probalby find various edits for the build.prop file to trick market into giving you increased access. When I was on stock 4349 (way back when), I edited mine by adding the following line "ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys". I also remember seeing one that recommended changing "ro.product.device=" to "olympus'. To edit build.prop you will need to use rootexplorer or a similar app. As always it would be best to do a backup with CWM before editing system files.
Al
Both of my computers refused to let me change the drivers in the NT.
I was able to get it from 1.4.1 to 1.4.0 and sideload apps. I got cwm into emmc then got ADB launcher working which helped my disposition. I have no use for B&N home, etc.
By determination rather than knowledge; I have it doing what I have been doing on the NC for a year. I also have the reader from B&N (I missed that on the cm7 NC) without having to see the rest of B&N.
What condition should the NT be in before putting cm7 on? How can I tell if the drivers are right for the new cm7? How can I tell if it’s even rooted. This is so embarrassing! I have this thing working so good but I got there in such a convoluted way!
As of right now, the Alpha links to CM7 has been pulled due to an error where it would brick your device when you tried to format an sd card. I'm a noob in the development area, but from what I can gather, as long you have CWM either internally or on an sd card, you would be able to flash CM7 and wouldn't need to update any drivers. The drivers are necessary for adb especially for Indirect's nook and zergy method (http://forum.xda-developers.com/showthread.php?t=1354487) and if you had issues updating the drivers try (http://forum.xda-developers.com/showthread.php?t=1415812) or if you are having trouble seeing the device when you ran the nook&zergy root (http://forum.xda-developers.com/showthread.php?t=1363652) this should help you out. Hope this helps.
If it is rooted, what will the specs say? There should be a way to tell.
Sent from my Nook Tablet
Using Indirect's Nook&Zergy through your computer, your software version would be 9.9.9 because of the OTA block and for me, the wifi Mac Address on my NT says Unavailable.
From what you have said in your previous post, it seems that you only downgraded to 1.4.0 and then sideloaded apps. So just to clarify, do you have any gapps(google apps like market, talk, calendar) on your device? Do you have Superuser? Also if you have rooted your device, if you use es file explorer (free app) and go to settings you can see if you can mount the emmc (internal memory) which require root and super user permission. Or just try using Button Savior app which requires root as well.
That's what I did. I only sideloaded a few apps to see it it worked. But when restarted it only a couple were there. Then the next time I turned it on I saw something load that I didn't recognize, then I was able to download anything I wanted from the market.
It is not rooted but Superuser and Root Explorer works like my rooted NC. I have cmw from Rom Mgr. Button Savior didn't work.
claudiaa said:
That's what I did. I only sideloaded a few apps to see it it worked. But when restarted it only a couple were there. Then the next time I turned it on I saw something load that I didn't recognize, then I was able to download anything I wanted from the market.
It is not rooted but Superuser and Root Explorer works like my rooted NC. I have cmw from Rom Mgr. Button Savior didn't work.
Click to expand...
Click to collapse
For the symptoms you mention i think you got caught by the 1.4.1 update. Oh well!. If you have CWM then boot into it and flash back to 1.4.0 using one of the 2 ROM's offered in this page, copy it to /sdcard/clockworkmod/backup folder and restore from CWM Backup & restore> restore, select the folder and thats it. What i have mentioned here is in my FAQ too.
~ Veronica
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!