For those of you who got the Market working, there is a Market update that is getting released. I installed it on my HTC HD2, but the same file would not work on the Nook. I did some searching and found one that works on the Galaxy Tab w/stock Eclair. It works on the NC!!
Requirement: You MUST have a working market. Follow this thread or this thread for more excellent info (and work) on enabling the Market.
Simply replace the Vending.apk in /system/app/ with this file (rename it Vending.apk first), reboot, and you are good to go! I would recommend backing up the original Vending.apk so that you can replace it if anything should go wrong for you.
You can use Root Explorer with /system/app in r/w mode, but it is simple to do via adb as well:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Vending.apk /system/app/oldVending.apk
adb push Vending.apk /system/app
adb reboot
**If you have problems, simply delete the Vending.apk, and replace it with the oldVending.apk
There is a newer version of the Market posted by devis and Xhorder in this post. Please use it instead. It fixes the weird star artifacts of this version. Instructions are exactly the same.
DO NOT simply click it to install. If it happened to work for you that way, you were lucky. You really should replace the Vending.apk with this file. Also, I saw one user report that the search function didn't allow Market searches. I believe they are the only one with that issue, and I'm not sure how they installed this. I assume they did not follow instructions, as my guide backs up the original file, and the person with the issue is asking for the orig apk. So, YMMV, but follow this instructions, and you should be fine.
Sweet! Worked for me. Danke, Herr Bimboy.
Very nice!
I actually found that the new market apk you provided installs fine as an update (no replacement of /system/app/Vending.apk needed). I opted for that as the safer option.
Thanks again!
Works very well! Very nice interface.
One issue: The "OK" and "Update" buttons are sometimes just slivers at the top of the screen. Doesn't prevent it from working though. You just have to be careful with your clicking.
Adding: This version doesn't have the problem of not listing all of the apps when you're in portrait mode. It simply works. And when you tell it to install/update an app, it does it RIGHT FRIGGIN' NOW and I mean Fassssst!
Thanks! Works great.
One question - Is there any way to get the fingerprint from the tab w/eclair? This would potentially give us access to some tablet-specific apps, like WSJ...
The new auto nooter installs he mew market ffor you...
Pinesal said:
The new auto nooter installs he mew market ffor you...
Click to expand...
Click to collapse
Awesome! I was hoping the script would get updated to include this.
FYI: Those considering updating to this version, it puts buttons up top where you can barely press them for confirmations.
-CC
EDIT: as mentioned by johnopsec above post
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
barrosd12 said:
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
Click to expand...
Click to collapse
I just did a search for Zeam in the Market and it came up fine for me. So does pinball.
barrosd12 said:
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
Click to expand...
Click to collapse
The old market did that too. I don't think we'll see a fix for that before a Froyo port. The upper search link doesn't always work either. The Market is expecting the upper status bar to be on the top of the screen, and we do not have that.
I wondered if that was just on mine lol , frustrating
So frustrated! I finally get my market working today and then I try this upgrade and it won't work. So I try to go back to the old one and it has stopped working too. I don't get what I did wrong. Of everything I did to get my nook rooted and working, this was the simplest part.
New version won't work in mine either. After accepting the agreement, it just closes.
Market 2.26 is supposed to be for Froyo+ only. How did you guys get it to Work?
Switched back to old Market.. everything is ok again
Tried this, got to click "accept" and then it vanished. Back to old market for me too.
I updated it with Astro and it worked fine. It's better to install apk's with Astro than others methods.
Guys, as I mentioned, do not just adb install, or click do a normal install. Save out your /system/app/Vending.apk and use this file to replace it, after renaming it Vending.apk. Then reboot.
I also tried simply installing it, and the Market app would only briefly flash or I could get to the catalog but not get to the details page of any app without force closing. That's why you should back up the Vending.apk file.
So, REPLACE the /system/app/Vending.apk, reboot and you'll be fine.
First, rename the file to Vending.apk
Use adb:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell cp /system/app/Vending.apk /system/app/oldVending.apk
adb push Vending.apk /system/app/
adb reboot
king conan said:
I updated it with Astro and it worked fine. It's better to install apk's with Astro than others methods.
Click to expand...
Click to collapse
I did this too, I just saved it to my mircoSD card and open Astro, clicked on the .apk and ran upgrade and everything works great now. My market is working 100%
I guess Astro knows what is doing because before update it warns about you' re updating a system app.
Pinesal said:
The new auto nooter installs the new market for you...
Click to expand...
Click to collapse
Is this confirmwed that auto nooter (Windows version) does include the newer Market app?
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Thank you very much. It works well.
I'm curious... what did you modify to get the Talk.apk to work?
Could you post a link on how to replace the keyboard? I think you rename the new one latinime.apk and place it somewhere...
Sent from my LogicPD Zoom2 using Tapatalk
No, you need to go to /system/app/ and rename LatinIME.apk to something else and then install the multitouch keyboard APK I linked to and reboot. That's it.
Mistar Muffin said:
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Click to expand...
Click to collapse
All hail the Muffin Man!
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
rxr said:
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
Click to expand...
Click to collapse
That's why you need to switch keyboards
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Ellerbestyle said:
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Click to expand...
Click to collapse
Did you also apply the hack to enable Gmail and Android Market previously posted by Mistar Muffin? I believe those steps are a prerequisite to get GTalk to work.
Hmm...this is where I am...gmail/market all set, original talk application didn't work, so I renamed the talk apk's to end in bak, so they wouldn't be running in the background.
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
graymulligan said:
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
Click to expand...
Click to collapse
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
works great. thanks, muffin!
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
can permissions be changed within root explorer?
on vending.apk, for example, long press to get to the permissions option. Theres a 3x3 grid with 'read' 'write' 'execute' as columns and 'user' 'group' 'others' as rows.
edit: dont mean to get off topic but my market worked when i checked all the boxes in the row 'user' then rebooted. so maybe that works for talk as well.
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
I renamed them to .apk, from .bak. I had changed them rather than moving or deleting them, and meant that I had renamed them to their original names. Which still makes no sense...lol.
I didn't think to change the permissions...I had it sitting at rwx-r-r, swapping to rwx-rx-rx did the trick. Thanks for putting up with stupid questions, your help is greatly appreciated.
Link issues
The "talk.apk" link doesn't work for me; I've tried copying and pasting the link on both Google Chrome and also on IE9, chrome says the site doesn't exist and IE does nothing (acts as if I just clicked the refresh their default homepage).
UPDATE: Hotaru has made some updates to the KB apk. this wont work right off the bat though for NC.
Step 1. Download the latest keyboard from here.
Step 1: You must rename you existing GB keyboard or remove it.
Step 2: Then use Root Explorer OR adb push to copy the file to /system/app
Step 3. Click on the gbkb.apk and install it
Step 4. Use Root Explorer and come back to /system/app and modify permissions of the apk file like this
Code:
[SIZE=4][COLOR=Blue]
Read Write Execute
User X X
Group X
Others X
[/COLOR][/SIZE]
Step 5: Reboot your NC and select the new keyboard in NCTools
Detailed steps for installing gingerbread keyboard on NC
A big thanks to hotaru for porting the keyboard to 2.1, ne0fhyk for the keyboard app & nookDev team for all tips..
This post is written on the following assumptions:
1. You have Nook Color
2. You have a firmware 1.0.1 (1.0.0 may work, but i haven't tested this keyboard with it)
3. Rooted it with Autonooter for 1.0.1 - BTW if you used Auto-Nooter, you will have Droid-X keyboard as default NOT the Stock Keyboard.
Step 1. I would recommend that you download the gingerbread 2.1 keyboard (gbkb.apk) from hotaru as there may be updates..
Step 2. --OPTIONAL-- Install Keyboard Manager developed by ne0fhyk (You really don't need this since Autonooter has NCTools app which can be used for the same purpose. the only advantage this tool has is that you can use 2 different keyboards for portrait & landscape ;P)
To install:
1- Download the app (KeyboardManager.apk) on your device sdcard.
2- Using Root Explorer, move the apk file to /system/app
3- Using Root Explorer, edit the file permissions like below:
-- User: 'Read/Write' checked
--Group: 'Read' checked
--Others: 'Read' checked
4- Exit Root Explorer
Step 3. Backup, remove & install Gingerbread keyboard ( You dont have to remove your old keyboard if you have the keyboard manager installed. so u can choose between autonooter droidx kb if required)
Open your command prompt or console and remount /system as writable.
HTML:
adb shell
#mount -o remount,rw /dev/block/mmcblk0p5 /system
#exit
Copy the default keyboard (LatinIME.apk) from /system/app as a backup, as we will be removing this file shortly.
HTML:
adb pull /system/app/LatinIME.apk LatinIME.apk
Transfer your keyboard APK to /system/app
HTML:
adb push gbkb-2.1.apk /system/app
Now we have to Remove LatinIME.apk
HTML:
adb shell
# cd /system/app
# rm LatinIME.apk
# exit
Alternatively, you can rename the LatinIME.apk if you do not wish to delete it, as this will enable you to freely switch back to the stock keyboard layout.
HTML:
adb shell
# cd /system/app
# mv LatinIME.apk KeyboardBackup.apk
# exit
Now Reboot NOOKcolor & enjoy Gingerbread keyboard...
HTML:
adb reboot
See the screenshot below
Once you bring the keyboard up touch the setting button (2nd from lower left) and you'll see the settings screen. you can switch to the droidx keyboard from here but not back. Vibrate dont work yet...
UPDATE: For people having trouble with the keyboard
When you followed the steps and removed the LatinIME.apk without backing it up, you can still get from the post below. After you "push" LatinIME back into /system/app, reboot the NC & follow the instructions (THANKS TO wtd966)
Reinstall the gbkb-2.1.apk using root explorer and it'll work. Here are the steps:
HTML:
Step 1. Using Root Explorer Navigate to /system/app.
Step 2. Click on your GingerBread keyboard apk: gbkb-2.1.apk
Step 3. Click install.
Once re-installed long click in a text field untill you get the option to select input method.
Re-select GingerBread keyboard.
very cool will give it a go after dinner
edit
Woot Got it working thanks to the guide
Thanks my dude!
Worked great for me once I learned to follow directions and not pretend like I knew what I was doing... I love it, great keyboard and doesnt go into full screen mode when in landscape. Much appreciated!
Thanks so much!
I do plan to use this keyboard, but just a quick question--would this work for any keyboard .apk, such as Shapewriter or Swiftkey?
Well I am not so lucky. I followed your instructions to the letter, but now I have no keyboard at all. When I open Keyboard manager the only keyboard listed is in fact GingerBread .... so I check the box, but when I go to type inside any application NO KEYBOARD shows up at all. And I did not back up LatinIME.apk either so I am screwed.
What can I do ?????
Thibor69 said:
Well I am not so lucky. I followed your instructions to the letter, but now I have no keyboard at all. When I open Keyboard manager the only keyboard listed is in fact GingerBread .... so I check the box, but when I go to type inside any application NO KEYBOARD shows up at all. And I did not back up LatinIME.apk either so I am screwed.
What can I do ?????
Click to expand...
Click to collapse
grab the keyboard from the Sideload_Update. It's in system/app/
Thibor69 said:
Well I am not so lucky. I followed your instructions to the letter, but now I have no keyboard at all. When I open Keyboard manager the only keyboard listed is in fact GingerBread .... so I check the box, but when I go to type inside any application NO KEYBOARD shows up at all. And I did not back up LatinIME.apk either so I am screwed.
What can I do ?????
Click to expand...
Click to collapse
Ok I found a copy of LatinIME and pushed it. It works... but the GB keyboard still wont run for me even tho I select it in keyboard manager. **shrug**
Thibor69 said:
Well I am not so lucky. I followed your instructions to the letter, but now I have no keyboard at all. When I open Keyboard manager the only keyboard listed is in fact GingerBread .... so I check the box, but when I go to type inside any application NO KEYBOARD shows up at all. And I did not back up LatinIME.apk either so I am screwed.
What can I do ?????
Click to expand...
Click to collapse
Sorry for these questions. but it'll help me solve your problem
1. I want to make sure that you did not INSTALL the apk but did an "adb push" to /system/app
2. did u enable r/w instructions for the keyboard manager?
3. the keyboard can also be changed with "NookColor Tools". If you rooted with AutoNooter, you can see this app
4. always reboot after the process.
5. also can you please let me know what firmware version u have on your NC?
Thibor69 said:
Well I am not so lucky. I followed your instructions to the letter, but now I have no keyboard at all. When I open Keyboard manager the only keyboard listed is in fact GingerBread .... so I check the box, but when I go to type inside any application NO KEYBOARD shows up at all. And I did not back up LatinIME.apk either so I am screwed.
What can I do ?????
Click to expand...
Click to collapse
CocoaGoddess said:
Thanks so much!
I do plan to use this keyboard, but just a quick question--would this work for any keyboard .apk, such as Shapewriter or Swiftkey?
Click to expand...
Click to collapse
Sorry.. both these keyboards do not work.. but Gb is awesome in its own way...
Thibor69 said:
Ok I found a copy of LatinIME and pushed it. It works... but the GB keyboard still wont run for me even tho I select it in keyboard manager. **shrug**
Click to expand...
Click to collapse
I had the same problem. I reinstalled the apk using root explorer and it worked. Maybe it will work for you. Here are the steps:
Navigate to /system/app.
Click on your GingerBread keyboard apk: gbkb-2.1.apk
Click install.
Once re-installed long click in a text field untill you get the option to select input method.
Re-select GingerBread keyboard.
Good Luck!!
may want to sticky this because i was having the same issue as well
Thanks for the.heads up up, i love this keyboard on my evo... What was your starting point prior to install? Freshly auto nootered 1.01? Xboxes auto script? I think some of the files might be different for those with the modded droid x kb.
madrascafe said:
Just saw a post on XDA elsewhere by hotaru where he posted the GB keyboard for 2.1
Was able to install it and am putting it thro the works.
here are the steps... PLEASE FOLLOW THEM unless u wanna screw up the keyboard. no harm thou, you can always recover.
1. Go HERE and download the keyboard 2.1 - THANKS Hotaru
2. Now go HERE and follow the instructions to install the Keyboard Manager. This is a very cool manager as u can manage the landscape & portrait separately
3. Now head over to NookDevs and backup your LatinIME.apk as described and push the apk you downloaded from step 1.
4. reboot & enjoy
I will write a detailed step-by-step instructions in a bit but wanted to share the excitement..
Click to expand...
Click to collapse
Many thanks to madrascafe. Follow the instruction and the keyboard and keyboard manager work well.
Sent from my LogicPD Zoom2 using XDA App
wtd966 said:
I had the same problem. I reinstalled the apk using root explorer and it worked. Maybe it will work for you. Here are the steps:
Navigate to /system/app.
Click on your GingerBread keyboard apk: gbkb-2.1.apk
Click install.
Once re-installed long click in a text field untill you get the option to select input method.
Re-select GingerBread keyboard.
Good Luck!!
Click to expand...
Click to collapse
That worked perfectly! I was trying to do this with Astro, but there was no install option (only Launch). With RE, i was able to reinstall like you said, and it works great!
norkoastal said:
Thanks for the.heads up up, i love this keyboard on my evo... What was your starting point prior to install? Freshly auto nootered 1.01? Xboxes auto script? I think some of the files might be different for those with the modded droid x kb.
Click to expand...
Click to collapse
Yup.. freshly auto nootered 1.0.1.. haven't tried autoscript yet..
madrascafe said:
Yup.. freshly auto nootered 1.0.1.. haven't tried autoscript yet..
Click to expand...
Click to collapse
Autonooter now has NC tools installed with the option to choose the keyboard. Why would we need need to add Keyboard Manager? Is landscape not enabled with NC Tools?
Thanks!
norkoastal said:
Autonooter now has NC tools installed with the option to choose the keyboard. Why would we need need to add Keyboard Manager? Is landscape not enabled with NC Tools?
Thanks!
Click to expand...
Click to collapse
you're right.. no need for the KBM... old habits die hard .. i've also mentioned NCtools in my post..
Great got it working, one question.
I got it working, but every time the keyboard changes from landscape to portrait a pop up says
"Exception caught: java.lang.SecurityException: using null token requires permission android.permission.WRITE_SECURE_SETTINGS"
Is this normal or do I need to change permissions on something?
kevinpc said:
I got it working, but every time the keyboard changes from landscape to portrait a pop up says
"Exception caught: java.lang.SecurityException: using null token requires permission android.permission.WRITE_SECURE_SETTINGS"
Is this normal or do I need to change permissions on something?
Click to expand...
Click to collapse
kevin.. i recommend that you start from scratch.. i.e. restore to stock firmware and use autonooter.
1. not sure how you rooted ur NC? did u use autonooter?
2. make sure u have superuser pack in your NC.
Ok (after rooting) here is how I installed GApps (Market, Google Framework, etc) on the Nook Tablet, as well as the steps I took to stabilize everything...
1. Downloaded GApps package from goo-inside.me and extracted files.
2. Deleted the setupwizard.apk file from the set of extracted files (in the system\app folder).
3. Copied "system" folder from extracted files to tablet via USB.
4. Used Root Explorer to remount /system and copy files into their designated locations, and also set permissions (644) on all copied apk's in /system/app folder.
5. Rebooted.
6. Ran the market, signed in with my Google account, and downloaded/installed Superuser. Ran the binary update within the app.
7. Install any additional apps from Android Market.
8. Profit.
Known issues...
1. If setupwizard.apk ends up on your tablet you will not be happy.
2. A factory reset is recommended after installing GApps (though probably not necessary).
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
this is a second good news after rooting!
anlong:
Use either wireless adb found here: https://market.android.com/details?id=siir.es.adbWireless
or use debugging toggle found here: http://code.google.com/p/secure-set.../detail?name=ADBWidget-0.2-alpha.apk&can=2&q=
^ instructions for that:
Download ADBWidget.apk
Copy ADBWidget.apk to /system/app (you can use root explorer or something.)
Add ADBWidget to your home screen
Anlog,
I was able to get SuperUser installed following the directions on the other discussion! Thanks for much for all your hard work.
Working on getting Google Apps installed right now.
Update: Well I have SuperUser on my Nook, but whenever I try to copy anything to \system\app it tells me I don't have permissions. Looks like I can't get root to actually run.
run chmod 4755 /system/bin/su
which version of Gapps do I need Cyanogen 6 MDPI?
Make sure root is fully working before you try to install GApps. Use the latest ones for CM7 (I think its from August). You need to remount /system as RW before copying the files and setting permissions. Root Explorer lets you do all of that.
All of this could be done with an ADB script as well, but I won't have time to write one today. Anyone?
anlog said:
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
Click to expand...
Click to collapse
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Drewmungus said:
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Click to expand...
Click to collapse
Do not install chainfire! I just tried it and it boot-looped, had to force factory restore.
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
bkerk25 said:
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
Click to expand...
Click to collapse
What gapps did you use?
I used the cyanogen 7 universal gapps.
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
theundeadelvis said:
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
Click to expand...
Click to collapse
I ran into issues copying the whole folder over. I am currently running the google market though.
do everything one step at a time, install the googleframework first (from the directions on the kindle page), then do the market. I ran into the first time through the market would not actually connect so I rebooted the NT.
*note*
each time you reboot your NT you need to go in and what appears is toggle the usb debugging off then on, same with the "auto mount", and I did the unknown sources as well (not sure if this is necessary). It appears a reboot resets the flags and our menu isn't actually writing the settings so you have to toggle it.
Push comes to shove, start over with fresh reboot. It took me a few times (as it probably did others as well).
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
JoeM01 said:
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
Click to expand...
Click to collapse
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
suicideclown said:
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
Click to expand...
Click to collapse
It needs go in system/apps
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
i'm copying from the system/apps directory (unzipped gapps files), to where on the nook?
I tried copying the files into several locations, but nada.
this is literally the last thing need to knock out for me to be set until the days of ported roms.
please. halp (lelu dallas, multipass).
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
that part is clearly stated but using root explorer and getting it to mount doesnt seem to work properly on my device. I have root and superuser. titanium backup works fine. for some reason root explorer on es explorer says it fails every time
-1 Go download latest Gapps and extract the contents to your HD. There will be two folders, one of which is "system."
-2 In the system folder there will be more folders, one of which is "app." Inside of app are all the system APKs.
-3 Detele SetupWizard.apk
-4 Now copy the app folder to the root of your NT SD card via USB.
-5 Next step you need to use ADB or Root Explorer...I used Root Explorer.
-6 Open root explorer, then go to sdcard and you should see the APP folder you copied.
-7 Once there, hit menu -> multi select > then put a check mark to what you want copied then hit the copy button.
-6 now hit back untill you're back in the root
-8 Then navigate to system, and at the top you should see button "Mount RW" hit that button.
-9 Then go into the App folder, and hit paste.
-10 All the selected APKs are now in the system/app folder.
-11 Now you need to give each of the copied apps permission by long-clicking on it till a menu comes up, hit permissions, then check all the check boxes next to "Owner"
-12 After you did that to all the apps hit the "mount RO" button on top of the screen
-13 Reboot the NT.
That should do it...hopefully I havent missed anything.
Now that the dump is out, im hosting the gmail apk again! enjoy!
here it is guys, the newest Gmail 4.2 Reported to be working for Android 4.0+, rooted devices only. If you are having issues with 'waiting to sync', clear app data under settings and try again
Installation Option 1:
uwdus said:
Uninstalled old apk with Titanium -> Reboot -> Installed new Gmail apk with explorer -> Reboot - Done
Click to expand...
Click to collapse
Installation Option 2:
The Gmail 4.2 APK is signed by Google, but with a different key than the one in the Play Store (we checked the signatures - they differ). One is probably the test key and the other the production key. For this reason, you can't simply install it as an update and therefore need to be rooted with the ability to mount the /system directory for writing in order to remove the existing Gmail APK.
OK, let's get down to it. You'll probably need ADB installed on your computer (here's an easy way that doesn't require downloading the Android SDK). There is a chance that this might work without ADB by just removing the APKs mentioned below and installing the new one, but it didn't seem to work reliably for everyone. This should, though:
1. Download Gmail 4.2 from one of the mirrors above.
2. Rename it to Gmail2.apk.
3. Make a Nandroid backup in case something goes wrong (this is always a good thing to do before messing with your device).
4. Delete (or move if you want to save the APKs) all other versions of Gmail. Usually there are 2 or 3 copies. One will be in /system/app (that's the original Gmail that was pre-installed on the device) and there may be a few in /data/app (these are the updates installed from the Play Store). They'll be called "Gmail.apk," or "com.google.android.gm-[number].apk," An easy way to tell is to look for the Gmail icon.
5. You may need to delete the .odex files matching the APKs in step 4 too, if you have them. Neither I nor Artem had to do this, but there are many different ROMs out there, and we're trying to cover all bases. Ignore this step and only come back to it if something doesn't work later.
6. Reboot. Once you do, you should have no Gmail as far as Android is concerned.
7. You can try to install the Gmail 4.2 APK you downloaded at this point by tapping it in your favorite file explorer (move the APK to your device first, of course). If that doesn't work, or if you prefer ADB, fire up a command line and type adb install Gmail2.apk.
If you get an error message, you probably didn't delete all copies of Gmail. If you don't feel like playing with ADB for Step 7, I've also gotten it to work by just copying the APK to /data/app, but that's not as fool proof as "ADB install".
Click to expand...
Click to collapse
get it here
Video review courtesy of qbking added
original link: http://www.androidpolice.com/2012/1...ed-gmail-4-2-apk-with-pinch-to-zoom-and-more/
Ur always finding something cool...good job maan !!
Sent from the boulevard of shattered Screen!!
Perry977 said:
Ur always finding something cool...good job maan !!
Sent from the boulevard of shattered Screen!!
Click to expand...
Click to collapse
Lol...np bro, enjoy!
Sent from my SGH-T999
1-up for u thanks
bump, apk is back in the OP!