Related
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).
Hi
ok I read about Titanium back-up, also saw this by Jus10o:
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
BTW, what is the .odex file for?
Can I also use Root Explorer to simply go into the System/apps directory and remove (ie delete) apks (provided I know what I am doing of course!)
I know this topic has already been covered here and there but it would be nice to have an exhaustive tutorial/fixed topic on the matter...
Thanks a lot
Beng7
BenG7 said:
Hi
ok I read about Titanium back-up, also saw this by Jus10o:
BTW, what is the .odex file for?
Can I also use Root Explorer to simply go into the System/apps directory and remove (ie delete) apks (provided I know what I am doing of course!)
I know this topic has already been covered here and there but it would be nice to have an exhaustive tutorial/fixed topic on the matter...
Thanks a lot
Beng7
Click to expand...
Click to collapse
1st, don't post junk like this in dev.
2nd, ODEX file is just the optimised program code, and the APK holds the resources.
You should delete matching APKs and ODEX files at the same time and it's fine.
There's hardly need for a tutorial, as it's so painfully easy.
BenG7 said:
Hi
ok I read about Titanium back-up, also saw this by Jus10o:
BTW, what is the .odex file for?
Can I also use Root Explorer to simply go into the System/apps directory and remove (ie delete) apks (provided I know what I am doing of course!)
I know this topic has already been covered here and there but it would be nice to have an exhaustive tutorial/fixed topic on the matter...
Thanks a lot
Beng7
Click to expand...
Click to collapse
I wouldn't just remove the apps like that, its far better in my opinion to use titanium backup and freeze the apps, then you know that if you accidentally break something on the phone by freezing an app you can just unfreeze it and everything will be fine. Whereas if you had just deleted it then you wouldn't be able to do that.
John
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
I used root explorer to move some system apk & its corresponding odex file from /system/apk to sdcard. I rebooted and found that I have moved some essential app like the stock dialer (it wasn't possible to figure out from the apk name). So now the dialer was gone. I then moved them back from sdcard to /system/app using root explorer thinking that it would undo the mess.
However the apps didn't come back, for example the dialer. The phone still tells me that there is no dialer.
What do I need to do?
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Gregrin said:
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Click to expand...
Click to collapse
I didn't move anything from any other directory. I moved back each and every file to /system/app that I had moved from it earlier. Still no luck.
I didn't delete anything in this process. I don't see dialer in app drawer either.
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Markuzy said:
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, umpteen number of times.
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
RavinduSha said:
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
Click to expand...
Click to collapse
Yes, you are so right.
The apk permissions have screwed up after all the moving. I issued ls -l command in adb shell and this is what I found out.
-rw-r--r-- 1 root root 3973 May 7 2012 HTMLViewer.apk
-rw-r--r-- 1 root root 8784 May 7 2012 HTMLViewer.odex
----rwxr-x 1 system sdcard_r 562553 Feb 9 04:31 LatinIME.apk
----rwxr-x 1 system sdcard_r 327896 Feb 9 04:31 LatinIME.odex
-rw-r--r-- 1 root root 14569 May 7 2012 LiveWallpapersPicker_gles20.apk
-rw-r--r-- 1 root root 21392 May 7 2012 LiveWallpapersPicker_gles20.odex
LatinIME.apk is the keyboard with screwed up permission.
Now how do I fix it? What command do I issue?
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
You can also change permissions in Root Explorer itself. Hold down on the files, choose permissions and tick the first column and the first box of the second one. Leave the rest blank and press ok. That's it. If it still doesn't show, reboot. Fixing permissions in recovery does exactly this, but for all files in /system/app, /data/app and /data/data. Every time you copy something to /system or /data, you have to set the right permissions. Either in a root explorer app, adb shell, terminal emulator or fixing permissions in recovery.
LatinIME is the stock Android keyboard btw.
Sent from my Desire HD using xda premium
calisro said:
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
Click to expand...
Click to collapse
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
sashank said:
LatinIME is the stock Android keyboard btw.
Click to expand...
Click to collapse
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
sashank said:
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can see two apks in my phone with dialer icon.
Phone.apk (& Phone.odex)
TelephonyProvider.apk (& TelephonyProvider.odex)
How do I get back the dialer? This is a dual sim phone and only the stock dialer gives the option to select sim before dialing. None of the market dialers provide this option.
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
RavinduSha said:
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
Click to expand...
Click to collapse
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
ontherocks62 said:
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
Click to expand...
Click to collapse
advanced section. look through. it should be self explanatory.
ontherocks62 said:
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Click to expand...
Click to collapse
the dialer is Phone.apk
calisro said:
advanced section. look through. it should be self explanatory.
Click to expand...
Click to collapse
Fixed permission. Still dialer doesn't appear. :crying:
ontherocks62 said:
Fixed permission. Still dialer doesn't appear. :crying:
Click to expand...
Click to collapse
reflash the rom. easy peasy. next time careful what you delete! sry guy.
if u have a backup just restore only system partition
RavinduSha said:
if u have a backup just restore only system partition
Click to expand...
Click to collapse
I have a backup. Unfotunately, I took a backup after messing up. So after re-flashing it with the backup, it boots in the messed up state.
I downloaded one gingerbread Phone.apk yesterday. I renamed the Phone.apk and Phone.odex in my phone to Phone.apk.bak & Phone.odex.bak. Then copied the downloaded Phone.apk to /system/app. Then fixed permissions via recovery and rebooted.
To my horror, not only did the dialer didn't appear, but also the phone wouldn't detect the sim cards. It would say no connection available...
So Phone.apk is affecting other stuff too. So I deleted the new Phone.apk and renamed the .bak to its original names, fixed permissions via recovery and rebooted. The phone still wouldn't detect the sim cards.
Then I went back to recovery, cleared Dalvik cache & user data, and performed clear data & factory reset. After reboot, the phone started detecting the sim cards again.
So this leads me to believe that something else other than permissions has a role to play.
I have a OnePlus 3T running Nougat 7.1.2 and OxygenOS. I simply edited the carrier_label in the extended status_bar.xml in the opsystemui.apk, and then replaced the old opsystemui.apk. I changed the permissions to rw-r-r (that's correct, right? I'm not really sure, little new at this). Now when I boot my phone, I just get a black screen. But if I hold the power button the options for power and reboot still show up. I'm guessing I need to replace the opsystemui.apk with the old one or fix the permissions, right?
I used twrp and superuser to root my phone, and I can still access the boot/recovery menus. So I can still access the phone using terminal and adb shell, can anyone give me step by step directions on how I can fix my phone? Or at least point me in the right direction? the systemui was located in system/priv-app/opsystemui/opsystemui.apk but it doesn't show up in the system/ folder when i type "ls" or "cd priv-app".
Edit: Oops, just found out you have to mount the system/ folder in rw mode, I can access the priv-app folder now. How do I reset the permissions, and what should i set them too?
Edit2: I set the permissions to 755 (rwxr-xr-r). Still not working...
Can anyone help?
iLaysChipz said:
Can anyone help?
Click to expand...
Click to collapse
Try deleting any folder in /data/data that has systemui in it also on MM there's a file in /data/user/system/0/permission.xml or something similar see if that's on nougat and try deleting it also you prob shouldn't modify any apk with out being deodexed
Sent from my LGLS676 using Tapatalk
Edit and permissions should be set to 644 on apk directory's are 755