open dialer and enter this code *#*#8736364#*#*
if you use apk manager to decompile an apk and look inside AndroidManifest.xml
you can find all sorts of secret codes but be careful I found one that instantly does a factory format including the internal sd card.
example:
Code:
<intent-filter>
<action android:name="android.provider.Telephony.SECRET_CODE" />
<data android:scheme="android_secret_code" android:host="8736364" />
</intent-filter>
just enclose the numbers with *#*# before the numbers and #*#* after the numbers.
tried it and it didnt update Similar thing was posted in a different thread. Anyone able to get it to update?
it was about 10min before I got a notification that there was an update.
I tried it and think it works. I am unable to receive an update because I have my vibrant on att network. Do you know the correct device manager settings for t-mobile
Sent from my SGH-T959 using XDA App
Related
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
(Problems with Google Apps might be solved with editing packages.xml and replacing apks. see EDIT 3 bottom)
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install
Titanium Backup
com.keramidas.TitaniumBackup
OR
ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Go for the Apps list.
on Titanium Backup
Tap Backup/Restore
OR
on ROM Toolbox Lite
Tap App Manager
then Tap All Apps
4.
App which its names written Red are on /system/app on apps list.
5.
Find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
Press Uninstall
if you can't find, swipe left or right - it might be there.
8.
Wait until uninstall finishes...
9.
Reboot Your Phone NOW.
It's Done.
There's a one more step if you want to use them is:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
EDIT 1---------------------------------------------------------------------------------------------
for someone having poor(? disconnects too often) data reception,
please check this thread about build.prop Fast Dormancy:
t t p : / / forum.xda-developers.com/showthread.php?t=1684604
EDIT 2---------------------------------------------------------------------Sept. 21th, 2012
>> Oops, I forgot to tell reboot your phone. also, wrote about steps for titanium
EDIT 3------------------------------------------------------------------------Oct. 1st, 2012
>> Found something weired with Google apps by myself. so I edited again.
due to some reason you can't update or Install some Google apps like Google Play Service, etc.
1.
extract apks from gapps package 20120429
if you don't have it, Google it.
2.
go to recovery.
3.
mount /system/as writable.
4.
replace corresponding apks in system/app/
(Incldue MarketUpdater.apk: if you want to keep Play Store updated. and.. included Play Store App from gapps 20120429 IS OUTDATED.
DO NOT REPLACE GoogleBackupTransport.apk: this shares signature with the ROM's so do not replace it otherwise it will be NOT AVAILABLE on your phone.)
if you extracted the gapps package in folder gapps,
Shift-Click upper folder on tree view.
and open command window here
in command-prompt:
adb push /gapps /system/apps
Replacing apks done however you have more steps to do for replaced apks start working.
(optional)
you can unmount /system/ because you have finished replacing apks.
5.
mount /data/as writable.
6.
pull out packages.xml
in command-prompt:
adb pull /data/system/packages.xml
7.
open packages.xml in text editor
(IMPORTANT: DO NOT SAVE files on windows notepad or something else displays all of lines as single line because lack of UNIX support)
8.
Delete shared-user element has name=com.google.uid.shared.
then save.
you have to delete whole element this might look like:
<shared-user name="com.google.uid.shared" userId="10000">
<sigs count="1">
<cert index="1" />
</sigs>
<perms>
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.youtube" />
<item name="android.permission.INTERNET" />
<item name="com.google.android.providers.gmail.permission.WRITE_GMAIL" />
<item name="android.permission.WRITE_SYNC_SETTINGS" />
<item name="android.permission.BROADCAST_STICKY" />
<item name="com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.MASTER_CLEAR" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.ACCESS_DOWNLOAD_MANAGER" />
<item name="com.google.android.providers.gmail.permission.READ_GMAIL" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="com.android.providers.im.permission.WRITE_ONLY" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" />
<item name="com.google.android.gtalkservice.permission.SEND_GTALK_DATA_MESSAGE" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.READ_SYNC_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="com.android.providers.im.permission.READ_ONLY" />
<item name="android.permission.WRITE_SECURE_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser" />
<item name="android.permission.CALL_PHONE" />
<item name="com.google.android.gtalkservice.permission.GTALK_SERVICE" />
<item name="com.android.vending.INTENT_VENDING_ONLY" />
<item name="com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
</perms>
</shared-user>
Click to expand...
Click to collapse
9.
put packages.xml back to your phone.
in command-prompt:
adb push packages.xml /data/system/packages.xml
10.
set its permission rw-rw-r-- as it was.
in adb shell:
# chmod 664 /data/system/packages.xml
# chwon system.system /data/system/packages.xml
(optional)
to check permission has set:
# ls -e /data/system/packages.xml (if -rw-rw-r-- is okay first char is for a directory)
11.
Reboot Your Phone NOW.
It's Done.
Fails to install from Play store
AtomosVE said:
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Tap App Manager
4.
Tap All Apps
Like Titanium, App which its names written Red are on /system/app on apps list.
5.
find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
press Uninstall
8.
wait until uninstall finishes...
It's Done.
There's a one more step if you want to use them:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
Click to expand...
Click to collapse
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Oops, I forgot something..
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
Oh, Forgot to tell rebooting your phone after uninstalled app. Hope you enjoy Facebook
Yowhy said:
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Click to expand...
Click to collapse
Thanks for telling them reboot is need. I was forgot but Now, Corrected
If anyone has tried to use an OTG to back up with Titanium Backup you know that if you select a folder on your OTG drive Titanium Backup will say it's not writable even if you can write to it using other methods.
I was looking into this last night because I wanted to back up everything to my 64GB sd card using the meenova OTG adapter (http://www.meenova.com)
Anyway to be able to have TiBU write to it all you have to do is add a lne in an xml file.
YOU MUST BE ROOTED:
Go to /system/etc/permissions
open up platform.xml
look for the line
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
and add the line
Code:
<group gid="media_rw" />
So now it will look like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Save the file, reboot and then fire up TiBu and navigate to the folder on your OTG drive and it will now work and the message saying it's not writable will be gone.
Anyone tried this?
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Jade Eyed Wolf said:
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Click to expand...
Click to collapse
You don't have to buy it. This process will work with any otg. But they are reputable. They had a huge kickstarter campaign and was reported on by a few of the sites (that's how I first found out about it)
Sent from my Nexus 7 using Tapatalk 4
GoClifGo05 said:
Anyone tried this?
Click to expand...
Click to collapse
Yes, I did and it works perfectly. But hey if you don't feel like I'm creditable and need a 2nd opinion then be my guest.. I don't really have the reputation of posting nonsense
Sent from my Nexus 7 using Tapatalk 4
I'm not calling you out at all! Lol don't get defensive. I just got my x today, DE and just reading around. Please don't take offense.
Sent from my DE Moto X
GoClifGo05 said:
I'm not calling you out at all! Lol don't get defensive. I just got my x today, DE and just reading around. Please don't take offense.
Sent from my DE Moto X
Click to expand...
Click to collapse
I'm not offended. I'm just saying.. If it didn't work I wouldn't have posted it. On Nexus devices using stick mount you don't need to do this but with the native otg with the moto x Titanium backup will say the folder on the otg drive is not writable.
Sent from my Nexus 7 using Tapatalk 4
Have an N7, got you. Well.... thanks for the tip.
Sent from my DE Moto X
Jade Eyed Wolf said:
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Click to expand...
Click to collapse
Wouldn't take my money. Hitting add to cart didn't do nothing.
Sent from my XT897 using XDA Premium 4 mobile app
graffixnyc said:
If anyone has tried to use an OTG to back up with Titanium Backup you know that if you select a folder on your OTG drive Titanium Backup will say it's not writable even if you can write to it using other methods.
I was looking into this last night because I wanted to back up everything to my 64GB sd card using the meenova OTG adapter (http://www.meenova.com)
Anyway to be able to have TiBU write to it all you have to do is add a lne in an xml file.
YOU MUST BE ROOTED:
Go to /system/etc/permissions
open up platform.xml
look for the line
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
and add the line
Code:
<group gid="media_rw" />
So now it will look like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Save the file, reboot and then fire up TiBu and navigate to the folder on your OTG drive and it will now work and the message saying it's not writable will be gone.
Click to expand...
Click to collapse
If rooted and do like you described, then the apps like ES file manager can write file into SD card? Thanks.
Permission Denied
So I have root access and gave root permission to es file manager but whenever I try to save the file I'm unable to. What could be going on? What's going on?
Whenever I try this my whole system goes to hell. I end up having to reinstall system, not even deleting the line off the file and rebooting works.
On my Nexus 6 I have a Flash Drive connected via OTG, I am using StickMount to mount it in the file system, I can use it without any problem from TWRP, RootExplorer, Media Players, etc. The Flash drive is formatted using FAT32. When I try to configure Titanium Backup to use it as the destination folder for backup, I can get to the folder where the drive is mounted but the option "Use the current folder" is dimmed and I cannot press it to select the folder, please any help or guidance will be appreciated, thanks
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
this line is unavailable but i found this one :
<permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
is it the same thing ???
falciatrice10 said:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
this line is unavailable but i found this one :
<permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
is it the same thing ???
Click to expand...
Click to collapse
I have the same case. WRITE_MEDIA_STORAGE is in place as well as both permissions, and it doesn't solve the problem. Added WRITE_EXTERNAL_STORAGE tag, didn't help either.
I found a correct solution on ( SURPRIIISE! ) Titanium Backup Troubleshooting FAQ
31. External SD Card problems (This Folder is NOT Writeable)
Since Android 4.4 and above, the SDCard permissions have been changed on how it is granted to an application. A quick way to fix this is by using SDFix application.
There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below). Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder – not to the entire card! In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/ Lastly, go to the preferences of TitaniumBackup, choose “Backup folder location” and choose the above specified folder.
Finish.
Click to expand...
Click to collapse
It works!
ShurV said:
I found a correct solution on ( SURPRIIISE! ) Titanium Backup Troubleshooting FAQ
It works!
Click to expand...
Click to collapse
Thank you! It works for me.:good:
Hi!
I have S4 I9505 with KitKat 4.4.2
I tried to fix writing to external storage for all apps as described here:
http://forum.xda-developers.com/showthread.php?t=2687734
I modified the file, restarted phone.. and now I have no internet, no wireless, no bluetooh, I cannot see my storage (neither internal or sd card), mz pc wont recognize the storages... I cannot make any backup, because I cannot write to any storage..
And, no, I haven"t done any backup of that file...
I tried to reedit but no succes...
Maybe someone can upload the original file?
Or do you have any suggestions?
eltigre4jc said:
Hi!
I have S4 I9505 with KitKat 4.4.2
I tried to fix writing to external storage for all apps as described here:
http://forum.xda-developers.com/showthread.php?t=2687734
I modified the file, restarted phone.. and now I have no internet, no wireless, no bluetooh, I cannot see my storage (neither internal or sd card), mz pc wont recognize the storages... I cannot make any backup, because I cannot write to any storage..
And, no, I haven"t done any backup of that file...
I tried to reedit but no succes...
Maybe someone can upload the original file?
Or do you have any suggestions?
Click to expand...
Click to collapse
you need to set permission to rw-/r--/-r--
make sure you only edit
<permission
name="android.permission.WRITE_EXTERNAL_STORAGE"
>
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
add only <group gid="media_rw" /> as above and save
if you only done this edit to your platform.xml then proceed to set permission as below
1. open root explorer
2. goto system>etc>permisson and mount folder as R/W
3. long press on platform.xml click permission
4. check
owner read and write
group read
others read
and click ok and reboot your phone
Hey guys, I recently found out that my external SD card was not writable so I looked up how to fix this.
I found instructions to go into my platform.xml file in my system/etc/permissions folder
and added this line where instructed:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
I was doing this using ES File explorer and when I tried to save it, it said "Save Failed!". I closed the app and reopened the platform.xml file and my previous edit seemed to be still there.
This is where the issue begins:
After rebooting my phone, a bunch of popups start coming up on startup with the following "Unfortunately, [app] has stopped."
I figure that this might be a permissions screw up on my part. I am now unable to access many apps and when I open ES File Explorer again, it gives me the error: "Cannot Start Streaming Server" and it shows an empty folder for almost every directory.
Any suggestions or help would be appreciated. I have tried flashing CWM onto my phone as well but when I try to go into recovery mode, I get stuck on the screen where is displays Samsung Galaxy S5. As I was getting desperate, I was trying to factory reset but it doesn't seem like this is an option anymore seeing as I can't get into recovery mode. I am currently downloading the stock firmware and planning to flash that using Odin but I am hoping it doesn't come to that as well.
Model: S-G900H
EDIT: Just tried flashing stock firmware using odin and it is still no good. Desperate for any suggestions.
EDIT2: Factory Reset and its working now
Same problem with SGS4
Hello,
I faced the same problem with my Samsung Galaxy S4. Factory reset solved the problem. However, it would be better if this could be avoided/solved without doing a reset.
any other solution?
have anyone found any other solution to this?
I don't wanna factory reset cuz all my apps, data, settings in internal sd and now i can't back it up cuz can't read it from my phone
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
schelleursli said:
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
Click to expand...
Click to collapse
It appears from the photographs that your Nook is not recognizing Launcher8 as a launcher app, but instead as a regular app. Are you able to view Launcher8 from ReLaunch's app drawer?
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
schelleursli said:
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
Click to expand...
Click to collapse
Yes, "All applications" is ReLaunch's app drawer.
I don't know exactly how to fix this, but let me do some research, and I'll get back to you.
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Renate NST said:
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Click to expand...
Click to collapse
Thanks for that, I've tried fiddling with the Manifest but I always either get a non working application with an entry in the Home menu or a working application with no entry in the Home menu to choose as default.
If you feel like having a look, this is the default manifest that is in use by launcher 8: pastebin.com/K8BknQuk (I'm not allowed to post links yet)
I do not have the android sdk installed or anything prepared to run ADB on my nook, I'll look into that at some point if the manifest fiddling doesn't work out.
The AndroidManifest.xml looks fine, which is to be expected.
Maybe you "picked" the wrong application at some point?
That's all in /data/system/packages.xml
Check preferred-activities in there.
You can always delete that whole section, as long as you do it cleanly.
Thanks for the continued help. I've had a look at packages.xml preferred-activities looks like this:
Code:
<preferred-activities>
<item name="com.lx.launcher8/.AnallLauncher" match="100000" set="4">
<set name="com.bn.nook.home/.HomeActivity" />
<set name="com.lx.launcher8/.AnallLauncher" />
<set name="com.lx.launcher8/.Home" />
<set name="com.harasoft.relaunch/.Home" />
<filter>
<action name="android.intent.action.MAIN" />
<cat name="android.intent.category.HOME" />
<cat name="android.intent.category.DEFAULT" />
</filter>
</item>
</preferred-activities>
I can turn off my nook and turn it on again then launcher 8 starts by default, but if I press the "n" button on the nook and then press home on the touch-screen I still only get the choice between ReLaunch and the default nook Home. I've also tried completely resetting my device restoring an old unrooted backup then root it again and set it up from scratch, same problem.
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Deafcyclist said:
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Click to expand...
Click to collapse
Yep, that's Nook Touch Mod Manager. It comes pre-installed with NookManager and my 1337 ROM, but it can also be installed manually with some modified framework-related .jar files.
Thanks for the tip, sounds like a good workaround for now.
edit: I see I need a running build environment for that, will see if I can get this to work on my virtual machine.
edit2: got it working
Oh, the "n" button?
B&N has that hardwired to do some B&N specific intent.
This problem has been solved many different ways.
My solution is to patch where the problem is, com.android.internal.policy.impl.PhoneWindowManager (in android.policy.jar).
This just makes the "n" key a normal Home key.
Code:
apktool d android.policy.jar -o C:\AP
mergesmali /v C:\AP PhoneWindowManager.smali PhoneWindowManager$HomeButtonHandler.smali
apktool b C:\AP -o android.policy.jar
Check the mergesmali link in the signature, a zip of the patches is there too.
No it was the "Home" menu button you open by pressing the "n" button. But with Nook Touch Mod Manager I've managed to change the behaviour of said "Home" even though Launcher 8 still wasn't shown as a choice. Thanks for all the help.