Database Users

How to fix some of problems in 2.1 from based on eris/may fix other roms???

just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)

these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway

lv2bll said:
these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway
Click to expand...
Click to collapse
x2 but thanks for the effort.

Great info, but can you edit the title of the post? It seems a bit harsh to flipz. All these guys deserve the utmost respect for doing these ROMs and not asking for much from us.
Just my 2 cents, thanks again.

wow people are sensitive. he's not bashing flipz...

rank78 also posted the links to the files needed for these fixes, i think it would be a good idea to post them on the first post of this topic

Great
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?

Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
Tried the MMS fix on Darch's 2.1 ROM... no luck.

link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908

rank78 said:
link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908
Click to expand...
Click to collapse
Thanks Rank- How do I get the 11 MDN number from my phone?

Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
its just 1, area code, phone number = 11

Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
I believe it is your phone number 1-234-567-8901 that is 11

Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post

rank78 said:
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post
Click to expand...
Click to collapse
Many thanks, but I was able to push the file to the destination. About the MMS, i did as instructed, still didn't help at all. I am not able to mms pics out either.
I am on Darchdroid V1 2.1

You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.

rulermon said:
just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)
Click to expand...
Click to collapse
There still needs to be appropriate quit and .quit statements added in to get out of sqlite3 and shell.

ripleys said:
You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.
Click to expand...
Click to collapse
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?

Kykiskly said:
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?
Click to expand...
Click to collapse
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.

Mistamike17 said:
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.
Click to expand...
Click to collapse
Ok but after that statement, what goes after, cuz since we are in the sqlite3 telephony.db, we cant adb reboot from there. What is the command to close/save the statement. I tried .quit, exit, adb reboot and no success.
how do we know that by doing the above statements the change took effect?
1) update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=1+area code + cell #' where name='Production'; *1+area code + cell '*
2)http: //mms.sprintpcs.com/servlets/MMS

This also worked on Souffle!!! Thanks guys!
Code:
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot

[SOLVED] Reinstall Launcher.apk after Root?

Hey can someone please tell me how to reinstall the original home (Launcher.apk) i tried installing via astro with no luck.
where do i have to push the file too? can someone post instructions, thanks.
EDIT: NVM this is what i did and it worked:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/Launcher.apk of=/system/app/Launcher.apk
adb shell dd if=/sdcard/apps/Launcher.odex of=/system/app/Launcher.odex
adb shell chmod 644 /system/app/Launcher*
adb shell reboot

Mod. edit: not dev related, moved to general
changed your title to signal an available solution, hope you don't mind

BULL3TPR00F said:
Hey can someone please tell me how to reinstall the original home (Launcher.apk) i tried installing via astro with no luck.
where do i have to push the file too? can someone post instructions, thanks.
EDIT: NVM this is what i did and it worked:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/Launcher.apk of=/system/app/Launcher.apk
adb shell dd if=/sdcard/apps/Launcher.odex of=/system/app/Launcher.odex
adb shell chmod 644 /system/app/Launcher*
adb shell reboot
Click to expand...
Click to collapse
Where do have I to enter those command line please ?

in any cmd prompt

Draken Korin said:
Mod. edit: not dev related, moved to general
changed your title to signal an available solution, hope you don't mind
Click to expand...
Click to collapse
yeah sorry about the wrong section, i figured it would be helpful in the dev section for people who had just finished rooting and wanted to reinstall the original home.
but thats cool, and no problem with the title change.

I don't know if you want it or not, but the free ADW launcher is quite a lot nicer. More features and feels really fast.

BULL3TPR00F said:
in any cmd prompt
Click to expand...
Click to collapse
I get a adb not found...
I'll try with another terminal app...
And the ADW launcher with the root is horrible (and the icon to show all hap is deleted when I put my finger on T_T)), I installed zeam launcher for the moment...
There isn't a way to exec all those command live at one time ? (like .bat for windows)

Vilam said:
I get a adb not found...
I'll try with another terminal app...
And the ADW launcher with the root is horrible (and the icon to show all hap is deleted when I put my finger on T_T)), I installed zeam launcher for the moment...
There isn't a way to exec all those command live at one time ? (like .bat for windows)
Click to expand...
Click to collapse
You will need the Android SDK to be able to use adb... and your phone has to be in 'debug' mode (Settings>Applications>Development>USB Debugging should be checked)

Hi i just used root explorer and copied the two files to system/app/
then changed permission to rw-r--r--
then rebooted phone and it worked

ADB Push

I searched around and couldn't get a clear answer. I'm a noob at anything command prompt/terminal related.
I was screwing around with adb last night after figuring out that I can remove program .apks with the rm <com.whatever.program> command. I got a little trigger happy and removed things that I don't use, just to test it out. I made a nandroid backup before I started. The phone runs fine, but now the Market won't download anything. It just sits on the Starting download... screen.
One of the .apks I removed was GmailProvider.apk. Whether this is the problem or not, I'd like to reinstall it for practice. I can always nand restore later.
So my question is... How can I use adb push to reinstall an apk?
I tried:
Code:
adb push C:\GmailProvider.apk
adb install C:\GmailProvider.apk
adb install C:\GmailProvider.apk \system\app
And about every variation of the 3, in and out of the adb shell.
It didn't work, and I'm at a loss to do anything else. So does anyone have any suggestions?

You have to push it abs then give it permissions.
So after pushing the apk give it permissions by doing this.
Code:
Adb push C:/gmailprovider.apk /system/app/gmailprovider.apk
adb shell
Chmod 775 /system/nameofapp.apk
Exit
Adb reboot
Your phone needs to be rebooted so I added the adb reboot, but you can just turn it off and on like you would normally or use that command.hope it helps.
Sent from my Eris using XDA App

Code:
# Chmod 775 /system/GmailProvider.apk
Chmod: not found
What's Chmod do, anyway?
EDIT: Forgot to cd to the directory...lemme try again.
EDIT2: Same error.

Okay, I tried:
Code:
# install /system/app/GmailProvider.apk [-cdDsp]
With no errors. Lemme see if it worked.
EDIT: I can see it, but the Market still isn't downloading apps. Lemme try an actual program.

Raikalo said:
Code:
# Chmod 775 /system/GmailProvider.apk
Chmod: not found
What's Chmod do, anyway?
EDIT: Forgot to cd to the directory...lemme try again.
EDIT2: Same error.
Click to expand...
Click to collapse
Ok I see two things that might be wrong with what you did.
Try not capatalizing the first letter(Not sure if this is a big deal but better to make sure.) and fix your path, GmailProvider.apk should be in the system/app folder.
Code:
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
The chmod command (abbreviated from change mode) is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes
EDIt:
Raikalo said:
Okay, I tried:
Code:
# install /system/app/GmailProvider.apk [-cdDsp]
With no errors. Lemme see if it worked.
EDIT: I can see it, but the Market still isn't downloading apps. Lemme try an actual program.
Click to expand...
Click to collapse
Yea you might be able to see it but the app might not have the right permissions to be used. Therefore it might be the reason why you can't download apps from market.

Excellent.
Code:
adb push C:/GmailProvider.apk /system/app/GmailProvider.apk
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
Worked like a charm. The capitalization was required; it gave an error without it. I installed Gmail.apk again using the same method and ran the program, and it worked. Thanks!
EDIT: GASP! Market works.
You're a lifesaver. Well, ROMsaver. I guess this means that GmailProvider.apk and gtalkservice.apk can't be removed from the phone.

Raikalo said:
However, the Market still won't download. Hm.
Click to expand...
Click to collapse
I just want to take this moment to make a Public Service Announcement: Everyone please remember to do a Nandroid backup before making any changes to your /system area.

Raikalo said:
Excellent.
Code:
adb push C:/GmailProvider.apk /system/app/GmailProvider.apk
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
Worked like a charm. The capitalization was required; it gave an error without it. I installed Gmail.apk again using the same method and ran the program, and it worked. Thanks!
However, the Market still won't download. Hm.
Click to expand...
Click to collapse
Don't know what to tell ya, you can start adding back the apks you deleted or do that nand restore since you already know how to install back a system apk, so you learned what you wanted
EDIT: I see you got it to work so that's good news, but like Nestor pointed out always use nand backup before you do any changes to the system area, I've learned to do this the hard way lol.

It's a good reminder
Thanks a ton guys I'll nand backup in a few to have a better restore point.
Learning android-related things ftw!

Oh, one more thing.
I saw something about adding an Environmental Variable to windows that involved adb? Could someone explain that?
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
Click to expand...
Click to collapse
There's an example. I tried this and it didn't do anything.

Raikalo said:
Oh, one more thing.
I saw something about adding an Environmental Variable to windows that involved adb? Could someone explain that?
There's an example. I tried this and it didn't do anything.
Click to expand...
Click to collapse
i think Thefuzz4.net explained this better
To make life easier, lets add a global path to the android SDK tools. Right-click My Computer > Properties,
click on Advanced, then click on Environment Variables.
Doubleclick on PATH, then at the end of the Variable value, add a semi colon ";" and then c:\AndroidSDK\tools
Doing The above ^^ will let you run adb from anywhere on your computer, like your desktop. You won't have to change to the directory and the run adb anymore, you can just run adb from anywhere on the command prompt. Its basically a little trick for us lazy people that hate having to "cd C:/android/tools" before running adb.

Does anyone know of a good resourse for adb and/or shell commands. Every time i try to goole it i just get links to different forums with just basic stuff, push, pull, ect. Id like to find something much more complete including chmod and the like
Sent from my Eris using XDA App

Thanks t2. Makes sense now. I hate CDing to the directory, so shortcuts are also ftw.
@above -- couldn't find a real resource so I resorted to asking specific questions on xda. if you find a resource lemme know.
ALSO -- chmod 775 /system/app/RandomProgram.apk.....what does the "775" do?

Raikalo said:
Thanks t2. Makes sense now. I hate CDing to the directory, so shortcuts are also ftw.
@above -- couldn't find a real resource so I resorted to asking specific questions on xda. if you find a resource lemme know.
ALSO -- chmod 775 /system/app/RandomProgram.apk.....what does the "775" do?
Click to expand...
Click to collapse
the different numbers are different permission settings. I forgot the other numbers, but their are others that set the applications for different permissions in the system. Someone correct me if I am mistaken though.

Finally found some explanation of chmod at catcode.com/teachmod/ . not sure if it directly applies to andriod, but seems to make sense to me now
Sent from my Eris using XDA App

wrong thread

Unroot the vibrant

I want to root but want to be reassured I can unroot for warranty purposes.

In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk

JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.

Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed

mmm easy
Ahh, easiest root/unroot makes me happy

Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.

bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?

Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..

skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?

ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice

mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?

where can I find the terminal On my pc?

temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.

bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?

Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks

temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.

hopefully this will help when people want to unroot if the update won't work without unroot

keyboard install problems nook 1.2 rooted

I can't seem to get any other keyboards to work. I have a stock NC 1.2 that was rooted first with MiniRooter (I think it is called) that OC'd it with the 1.2 GHz Kernel and then I MN with the most recent one as it had more options I wanted. But I can't seem to get a keyboard to work.
I have the gingerbread keyboard and thumb keyboard apk's and put them both in system/app with Root Explorer, reboot and nothing, I have tried to manually install them by clicking and using the package installer, nothing. Don't know what is up. none of them show up in the nook color tools under keyboard, but they show up in the manage programs...

anyone? It doesn't seem to make sense and I don't know enough about Android to troubleshoot.

all i have to do to try new keyboards is:
1) download new kb from the market.
2) install the new kb.
3) go into settings and make sure the keyboard is checked.
4) go to a text field and long press.
5) keyboard options will appear.
6) check the kb you want to use.
thats it. thats all i have to do for a new keyboard.
not sure about pushing the kb apk into syetem/app maybe its best to just install them.

boxcar8028 said:
all i have to do to try new keyboards is:
1) download new kb from the market.
2) install the new kb.
3) go into settings and make sure the keyboard is checked.
4) go to a text field and long press.
5) keyboard options will appear.
6) check the kb you want to use.
thats it. thats all i have to do for a new keyboard.
not sure about pushing the kb apk into syetem/app maybe its best to just install them.
Click to expand...
Click to collapse
my problem is that when I go into settings it isn't there to be checked..

I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.

KWKSLVR said:
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.
Click to expand...
Click to collapse
when I get a chance I will give it a go. Thanks

KWKSLVR said:
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.
Click to expand...
Click to collapse
I can't get the first part to work, it says not found. Where do I put the apk? I have it on c: on my comp.

Omega Ra said:
I can't get the first part to work, it says not found. Where do I put the apk? I have it on c: on my comp.
Click to expand...
Click to collapse
Which part specifically doesn't work?
Are you getting that after typing:
Code:
adb push <application_name>.apk /system/app
If so, try typing
Code:
adb kill-server
and try again
The apk is in the right place if it's in root on C: (and it is). Typing cd \ is pointing adb to look into C: for the apk you're trying to install. It's probably not the cleanest way to do it, but I've just always done it that way so people might wanna paint me silly.

KWKSLVR said:
Which part specifically doesn't work?
Are you getting that after typing:
Code:
adb push <application_name>.apk /system/app
If so, try typing
Code:
adb kill-server
and try again
The apk is in the right place if it's in root on C: (and it is). Typing cd \ is pointing adb to look into C: for the apk you're trying to install. It's probably not the cleanest way to do it, but I've just always done it that way so people might wanna paint me silly.
Click to expand...
Click to collapse
okay, let me try the kill server thing

Omega Ra said:
okay, let me try the kill server thing
Click to expand...
Click to collapse
no go, still says not found. I even renamed the apk to make sure I knew how many spaces and such...nothing...
hang on, I was in adb shell, went to normal root, I have to mount it as r/w first...
how do I do that lol
EDIT: Nevermind, I used rootexplorer to get it r/w and now the keyboard is there thanks a lot!

Are you in recovery or is your nook booted up?
Reboot your Nook and try
Code:
adb kill-server
again. Then
Code:
adb start-server
And attempt to install again. If that doesn't work, if your nook is still booted up (not in recovery), try:
Code:
adb remount
and try to install. If that doesn't work, try:
Code:
mount -o rw,remount
If you're trying to do this with your Nook booted into recovery, try:
Code:
mount -o rw,remount /dev/block/mtd3 /system
to get read/write and go from there.

Omega Ra said:
EDIT: Nevermind, I used rootexplorer to get it r/w and now the keyboard is there thanks a lot!
Click to expand...
Click to collapse
I almost suggested that, but it seemed so janky. But what works, works!
Glad you got it running!

KWKSLVR said:
I almost suggested that, but it seemed so janky. But what works, works!
Glad you got it running!
Click to expand...
Click to collapse
yeah, but sadly I had a beta of thumbkeyboard that was expired lolol, then put in perfect keyboard and that didn't show at all...ugh..lol