Though I could download and install Graffiti on my Gtab , I cannot select it as an input method. A message warns that personal data may be collected, and if I'm sure I want to use the input method. However, after tapping ok, Graffiti remains unchecked. Another similar app gave the same results. Google gesture search seems to work, so I'm hoping someone here might know how to fix this.
(using: TnT-Enhanced v3.1.4b)
Update Edit:
I am getting the same problem with the gingerbread keyboard.
Hello...
I had the same issue and gaspra over at this post gave me the answer... Hope this helps you out. BTW, there is a free version of Root Explorer in the market.
http://forum.xda-developers.com/showthread.php?t=993752
you will need a root explorer, it's on app market but not free.
From Root Explorer, open the /data/app/ folder and you will find the
keyboard you just installed. Then copy the apk file to /system/app, note
this is where you need the Root Explorer to change the permission for
/system folder from R/W to R/O (allowing permission to write in this folder
by user).
Do a restart once you finish copying the file. The new input method
should be enabled by default then.
Alternatively you can use "adb" tool from Android SDK to transfer the
apk file if you don't have a copy of Root Explorer.
adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.
I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!
Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!
This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl
Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works
I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you
Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
183.amir said:
Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
Click to expand...
Click to collapse
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
imminentwill said:
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
Click to expand...
Click to collapse
I think this should either be provided by Google Hangouts app or we need to use a custom framework.
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Okay, so you changed the Emoji in your conversation to match your keyboard. What if I wanted to go the other way ’round and skin my keyboard Emoji to match what’s in the conversation?
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
herwegan said:
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
Click to expand...
Click to collapse
Well... I don't know. In my post, I basically just remove the emojis that HTC put in the Android system and let it fall back on the original emojis in KitKat, which is the same as the Hangouts.
If there is an emoji font inside the whatsapp APK, then it might be possible to rename it to "AndroidEmoji-htc.ttf", and put it in /system/fonts/. This way, your phone would think it's loading the HTC emojis, but in reality it would be the whatsapp emojis. Might be possible with any emoji font pack actually.
thank you this worked perfectly!
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
is there a way to do this without having root?
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
robgee789 said:
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'd love to find a non rooted solution as well. Anyone got any ideas?
IIIMik3 said:
I'd love to find a non rooted solution as well. Anyone got any ideas?
Click to expand...
Click to collapse
I also need a non rooted solution for my HTC One M8. This is driving me crazy.
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
Obviously I have not rooted yet. What type of root does this require to have permissions to do this? Thanks in advance.
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
still hoping for a non-root solution to this. :fingers-crossed:
Me too mate but I don't think it's gonna happen
Sent from my HTC One using Tapatalk
Just run the weaksauce root for your HTC One M8 guys and you'll have no problems following the OP's instructions- literally takes 1 minute to root, 30 seconds to change the emoticons and you are good to go!
I rooted on my first day picking up the M8 and it's been awesome since
JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
IIIMik3 said:
still hoping for a non-root solution to this. :fingers-crossed:
Click to expand...
Click to collapse
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
trjlive said:
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
Click to expand...
Click to collapse
Ah, thanks for this! I'm glad I was able to get it to work with root explorer before this, but I'm glad I know how ES works now.
Hello everyone
I just want to get feedback on something... I use Go SMS Pro, but people using hangouts that I speak with, because I use the emoji provided by the app (iPhone emoji), they don't get most of them, which is very annoying... has anyone faced this? Is this happening just because of the emojis not being integrated? (If I press the button for emojis on the app, I get iPhone' s emojis, but not if i use the SwiftKey shortcut...)
Btw, I tried sending about 50 emoji. Hangouts got 25... :S
Sent from my GT-N5110 using XDA Free mobile app
hi again
I have small problem that I find quite annoying
Xperia SP on android 4.3 (....1.207 rom)
device is rooted with towelroot + SuperSU,
no matter which file manager with root capability I use and go into SYSTEM folder
and either create new folder and delete it, or copy something from SD to system Audio folder
things get broken...
Folder cannot be deleted even if its newly created, and has nothing init
nothing cannot be copied in Audio folder, as everything gets erased by ... system ?
and my annoyance goes to, if its rooted OS, and I as user have "full access"
why are these things happening ?
is there something I need to learn of how android deals with stuff specially ?
As far as i can remember, i haven't faced this issue in my past (was ages since i last used stock ROM). But i can safely say it might be related to your actual file manager. Can you list me the file managers you used?
I would also recommend trying to use Solid Explorer Classic for the sake of testing, and also Fx File manager.
Basically, when you want to do a change in the system directory, the system partition must be remounted as read-write because the folder resides on a different partition. Android by default mounts system partition as read-only on boot. A file manager is responsible to remount the system partition to read-write before performing an operation on the system partition, and i believe this is where the problem occurs - if the files aren't being copied.
If you can copy the folders but unable to delete, this is most likely a permission issue, and the file manager was probably isn't properly using its root rights.
Please respond with your test with Fx or Solid Explorer classic. You may also try Solid Explorer 2.0 if you wish. NOTE: Please enable Full Logging in SuperSU settings. I'd like to see what is going on (you can too).
Also it is worth to know that although root gives you ultimate rights to modify or alter the OS, there are always technical problems which are caused by various reasons. Plus, there are even barriers of which root power can't even do. For an ultra simple comparison, you can't use root to somewhat modify an app's source code live. But of course, root gives much more freedom to do things compared to no root.
ah yes, you were right, it did depend on file manager after all
tho for unknown reasons 5 of 6 all needed supersu acceess and had root capability, but nothing to operate
I finally found (blue) root explorer, and this one can do it all, sorry for opening this thread
I jumped bit late with whole android thing
So this is for any phone that is rooted. I kind of stumbled on it by just modifying/deleting entries inside of com.google.android.projection.gearhead. I use mixplorer cause its the easiest most user friendly.
1. Open mixplorer and navigate to /data/data/com.google.android.projection.gearhead/files/phenotype/shared/
2. Open gh.phenotype.pb as text with the in app code editor
3. Search for
AppValidation__blocked_packages_by_installer
4. Delete the line of the app your trying to use and save the file.
5. Press and hold on the file and select I on the top.
6. Change owner to root 0 and set permission to rw 600 if it's different.
That's it. My file hasn't updated since February 21 and I continually update Android auto and won't lose any app like obd2aa or fermata and the like. Hopefully it'll work for you too.
Hello, I have looked in the folder /data/data/com.google.android.projection.gearhead/files/phenotype/shared/, but I don't have the gh.phenotype.pb file as you can see in the screenshot. Can it be in another folder? Thank you
Nick_Gl said:
So this is for any phone that is rooted. I kind of stumbled on it by just modifying/deleting entries inside of com.google.android.projection.gearhead. I use mixplorer cause its the easiest most user friendly.
1. Open mixplorer and navigate to /data/data/com.google.android.projection.gearhead/files/phenotype/shared/
2. Open gh.phenotype.pb as text with the in app code editor
3. Search for
AppValidation__blocked_packages_by_installer
4. Delete the line of the app your trying to use and save the file.
5. Press and hold on the file and select I on the top.
6. Change owner to root 0 and set permission to rw 600 if it's different.
That's it. My file hasn't updated since February 21 and I continually update Android auto and won't lose any app like obd2aa or fermata and the like. Hopefully it'll work for you too.
Click to expand...
Click to collapse
Hello, I have looked in the folder /data/data/com.google.android.projection.gearhead/files/phenotype/shared/, but I don't have the gh.phenotype.pb file as you can see in the screenshot. Can it be in another folder? Thank you
Buy Xiaomi
Check out these:
- King Installer - Install packages "as Google Play" to work around restrictions (Root optional)
- Android Auto - Xposed Unlocked - Bypass even more restrictions (Root required)