Database Users

[RESOLVED] assistance needed - chmod /data/data/

Hi guys, I recently used the 'fix permissions' option in ROM Manager, which caused my SMS contact pictures to disappear. I then was trying to fix this by doing:
Code:
su
chmod 666 /data/data/com.android.providers.contacts/files/*
in Terminal Emulator on the device and dropped it right at :
Code:
su
chmod 666 /data/data/
anyways, long story short......./data/data/ is now 666, the device just constantly force closed eveything and is now in a constant boot loop. So any advice in the best way to fix this? I have tried booting into recovery and doing 'fix permissions' but this does not fix it.
Would fastboot allow me to connect to PC and chmod /data/data/ to the correct permissions? (and what would those be??) Or is it screwed and do I need to factory reset?
Many thanks for any hrlp guys

Have you tried re-flashing your ROM form recovery, this should reset the permissions

To be honest I'm new to Android and don't know which img that would be or how to go about doing it. Would doing this wipe any of my data? I was hoping there would be a simple way of getting a terminal through my pc and chmod from there (if I knew the correct permissions).

fubofo said:
To be honest I'm new to Android and don't know which img that would be or how to go about doing it. Would doing this wipe any of my data? I was hoping there would be a simple way of getting a terminal through my pc and chmod from there (if I knew the correct permissions).
Click to expand...
Click to collapse
fix permissions will do it for the files within the folder so if it where that simple I think it you would have fixed it 666 gives read/write permissions to everyone so I don't see that would have caused your problems, what ROM are you currently running? If it's a custom one simply reflash it, which should preserve all your Data if not you may need to run an RUU for your vendor/market which will wipe everything

ghostofcain said:
fix permissions will do it for the files within the folder so if it where that simple I think it you would have fixed it 666 gives read/write permissions to everyone so I don't see that would have caused your problems, what ROM are you currently running? If it's a custom one simply reflash it, which should preserve all your Data if not you may need to run an RUU for your vendor/market which will wipe everything
Click to expand...
Click to collapse
Thanks for the reply, I'm running stock ROM with eng hboot, recovery obviously and custom kernel. The reason I ask about fastboot chmod is because I'm not 100% 'fix permissions' is working via recovery.
Also, just for knowledge sake, what .img would be for what from my backup?
- .android_secure.img
- boot.img
- cache.img
- data.img
- nandroid.md5
- recovery.img
- system.img

Re-reading your original post, something weird is going on here as running 'fix permissions' shouldn't have caused any grief in the first place, possibly your OC is too aggressive for your CPU? (although it shouldn't be).

Plenty of people have come across the same issue when running 'fix permissions' from ROM Manager. It causes contact pictures to not display in the SMS apps in some cases.
Also, I remember running an option from recovery and it did nothing (even though reported completed) hence why I want to overrule the fix permissions from CM Recovery 2.5.1.3 and try to run commands into the device someway (via fastboot if possible or another method).
I just need to know what permissions should be for /data/data/ and how I would go about running commands to the device. And failiing that, what .img would be needed flashed to get a working device again with as little data lost as possible nd how to go about flashing it... fastboot or recovery update.zip?)

fubofo said:
Plenty of people have come across the same issue when running 'fix permissions' from ROM Manager. It causes contact pictures to not display in the SMS apps in some cases.
Also, I remember running an option from recovery and it did nothing (even though reported completed) hence why I want to overrule the fix permissions from CM Recovery 2.5.1.3 and try to run commands into the device someway (via fastboot if possible or another method).
I just need to know what permissions should be for /data/data/ and how I would go about running commands to the device. And failiing that, what .img would be needed flashed to get a working device again with as little data lost as possible nd how to go about flashing it... fastboot or recovery update.zip?)
Click to expand...
Click to collapse
assuming you are running cM 2.5.1.3 recovery?, have you a nandroid backup to fall back ON, restoring that, from recovery, would be my first step. If not Modaco has a stock ROM that you could try flashing from recovery which should retain your data

ghostofcain said:
assuming you are running cM 2.5.1.3 recovery?, have you a nandroid backup to fall back ON, restoring that, from recovery, would be my first step. If not Modaco has a stock ROM that you could try flashing from recovery which should retain your data
Click to expand...
Click to collapse
Yeah I have backups but from a while ago (first boot to be honest lol). But what should I restore and how? (system.img or data.img? as its /data/data/ that seems screwed)

fubofo said:
Yeah I have backups but from a while ago (first boot to be honest lol). But what should I restore and how? (system.img or data.img? as its /data/data/ that seems screwed)
Click to expand...
Click to collapse
Not sure how a partial restore would go, I normally do a full restore via recovery

OK so I have managed to get it working again. Ran backup form recovery which seemed to allow me to gain adb shell once the backup was completed. From there I chmod 777 /data/data/ and this allowed me to boot the device.
Everything seems to be gone, like contacts and such, but my apps are all there inc. Titanium backup. I have restored all system data from the Titanum backups and am currently running Rom Manager 'fix permissions' to see if that will add the correct permissions to /data/data/ again.
Hopefully I just now need to add my Google / exchange / etc. accounts again to be back to normal.
[UPDATE] - everything now seems to be working fine (except the original SMS contact pictures issue) and my entire device is back to the way it was last week (from Titanium backup I presume).
[UPDATE 2] - have now successfully ran chmod 666 /data/data/com.android.providers.contacts/files/* (after Rom Manager 'fix permissions' and reboot) and SMS contact pictures are all working again. Everything is syncing now so should be back to normal soon!!
on a side note, this obviously shows there is an issue with fix permissions, looks like it needs updated.

I too had the "contact picture" issue after performing the mentioned "fix permissions" command in ROM Manager. By the way, I simply fixed it by manually re-assigning the picture for each contact -- fortunately I have just a couple dozen contacts with picture so it didn't take too long.

capt_harlock77 said:
I too had the "contact picture" issue after performing the mentioned "fix permissions" command in ROM Manager. By the way, I simply fixed it by manually re-assigning the picture for each contact -- fortunately I have just a couple dozen contacts with picture so it didn't take too long.
Click to expand...
Click to collapse
Yeah I tried that too first but it didnt seem to work for me, removed image then reassigned for a number of contacts but nothing worked. It's fixed now so I'll just let this die here for future similair issues.

Titanium Backup Zip Restore

Having an issue after installing the zip created with titanium backup pro. This is the first time attempting to use this feature so maybe I'm doing something wrong. I've created the 2 different zips with my 2 sets of apps with the application. Confirmed they're both of proper sizes for the number of apps.
I go install the ROM (jellybeer) and Gapps and the zip for just titanium backup app. I reboot into the system and all is fine. Go into titanium backup, give it su permissions. Reboot to recovery.
Now I can install the app zips I created with titanium backup and it says successful install. Clear cache and reboot,and it never boots into the system. It just sits at the boot animation. I've let it sit for 2 hours and it never does boot.
Any suggestions?

Its a common fact that you should not restore system apps or data that includes settings from the old rom.
What 2 different sets of apps would you be referring to?
Sent from my Galaxy Nexus

Pirateghost said:
Its a common fact that you should not restore system apps or data that includes settings from the old rom.
What 2 different sets of apps would you be referring to?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Not restoring any system data or apps. Just my 3rd party apps. I have one zip with my 3rd party apps where I want to restore their data as well. And them another zip where its just the app with no data, like Google+ and Google keep since they auto restore their data.

So no one else has any ideas?

M3drvr said:
So no one else has any ideas?
Click to expand...
Click to collapse
Fix permissions?

BobbaLouie said:
Fix permissions?
Click to expand...
Click to collapse
I'll give that a try.

BobbaLouie said:
Fix permissions?
Click to expand...
Click to collapse
Okay I tried this and still no go. ROM will just sit at the boot animation. Any other suggestions?

I've always preferred to restore from the tibu folder on the sdcard after installing the ROM then installing Tibu from the Play Store. Works great.

Help needed to remove Xposed from 5.0

Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?

ImjuzCY said:
Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?
Click to expand...
Click to collapse
have you tried to clear the data from the playstore and let it rebuild the services ??

krazierokz said:
have you tried to clear the data from the playstore and let it rebuild the services ??
Click to expand...
Click to collapse
I did, for many times

ImjuzCY said:
I did, for many times
Click to expand...
Click to collapse
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.

krazierokz said:
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.
Click to expand...
Click to collapse
Tried that too but that was for the "normal" official xposed alpha. The way the devs set xposed on samsung touchwiz is different. We flash a different version of xposed framework.
Many of the original files you listed I don't find it (almost all). I think the only way to totally remove it is a full wipe

well good luck with your problem bud , i tried Sorry we could not determine the issue.... Long weekend !

Do u still need help?
From my s4 Powered by
Prism barebone v15

shiruuu.samad said:
Do u still need help?
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I already did a clean install. But help is still welcomed to help those who needs help

ImjuzCY said:
I already did a clean install. But help is still welcomed to help those who needs help
Click to expand...
Click to collapse
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15

shiruuu.samad said:
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I tried this but I still can't install apps larger than 1mb. Apps that are smaller than 1mb installed perfectly. I don't get fc BTW. I got error -504 from play store. I Googled about it and the error is due to lack of space in /cache partition. I checked the partitions and proved it. Only 800kb free in cache partition but play store needs to download apks to cache before installing. Even restoring titanium backups made during xposed is installed to a clean installed rom can cause that. So I did a clean install without any backups restored.
I tried clearing cache before, it's emptied when I cleared it, but it fills up when optimising app and I don't think I can skip optimising app after clearing cache.

Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck

RubbaBand said:
Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck
Click to expand...
Click to collapse
Yes I was lazy I backed up after installing the apk before flashing the zip. So that backup is somehow unusable. I already did a fresh install .

Titanium Backup Help I9505

thanks to the brilliant efforts of all the members here at xda forums I was able to root my Samsung galaxy s4 i9505 bought may 2014 out of warranty (didn't need even though had no root) bought may 2014 successfully all things work fine my question is that:
titanium backup detects both backup directories as valid shows all the files but says with extSdCard shows a red folder saying "This folder is not writeable" what's the deal here and how to fix it
additional question not related to this topic exactly but better than starting another thread
I didn't use triangle away and don't give a fudge about knox counter but would really like to remove knox and all its components from phone
the stuff that's on the phone is taking a lot of space and I want some of it back
any help would be appreciated
Samsung Galaxy S4 GT-I9505 Qualcomm Snapdragon 600
Lollipop 5.0.1 Official Rom
Kernel Version: 3.4.0-5978264 [email protected] # ! (CF Auto Root)
Running Latest CWM for I9505

Angel-King said:
thanks to the brilliant efforts of all the members here at xda forums I was able to root my Samsung galaxy s4 i9505 bought may 2014 out of warranty (didn't need even though had no root) bought may 2014 successfully all things work fine my question is that:
titanium backup detects both backup directories as valid shows all the files but says with extSdCard shows a red folder saying "This folder is not writeable" what's the deal here and how to fix it
additional question not related to this topic exactly but better than starting another thread
I didn't use triangle away and don't give a fudge about knox counter but would really like to remove knox and all its components from phone
the stuff that's on the phone is taking a lot of space and I want some of it back
any help would be appreciated
Samsung Galaxy S4 GT-I9505 Qualcomm Snapdragon 600
Lollipop 5.0.1 Official Rom
Kernel Version: 3.4.0-5978264 [email protected] # ! (CF Auto Root)
Running Latest CWM for I9505
Click to expand...
Click to collapse
Enter titanium backup preferences and go to the "backup folder location" setting. Next, touch the "storage provider" and select something else, like documents provider if available.
This may fix that problem.
As for knox, just do a Google search on what apps belong to knox and delete them with titanium backup.

GDReaper said:
Enter titanium backup preferences and go to the "backup folder location" setting. Next, touch the "storage provider" and select something else, like documents provider if available.
This may fix that problem.
As for knox, just do a Google search on what apps belong to knox and delete them with titanium backup.
Click to expand...
Click to collapse
as I understand using your method does show the backup location in extSdCard
but the entire root directory containing system file i.e.
/storage says not writeable
/storage/extSdCard not writeable
/storage/emulated/ not writeable
but
/storage/emulated/0
/storage/emulated/legacy
are accessible by TB here it says <<Create New Folder>>
I'm going like this {} trying to solve this over and over navigating file path changing locations
also does freezing BusyBox would effect this
or is it affected by SuperSU's Mount namespace separation
I'm very confused and frustrated because finding an alternative to TB would be a miracle

Angel-King said:
as I understand using your method does show the backup location in extSdCard
but the entire root directory containing system file i.e.
/storage says not writeable
/storage/extSdCard not writeable
/storage/emulated/ not writeable
but
/storage/emulated/0
/storage/emulated/legacy
are accessible by TB here it says <<Create New Folder>>
I'm going like this {} trying to solve this over and over navigating file path changing locations
also does freezing BusyBox would effect this
or is it affected by SuperSU's Mount namespace separation
I'm very confused and frustrated because finding an alternative to TB would be a miracle
Click to expand...
Click to collapse
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.

GDReaper said:
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.
Click to expand...
Click to collapse
wil try it tomorrow

GDReaper said:
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.
Click to expand...
Click to collapse
sdfix worked I OTA updated to lollipop so all is good user apps are able to write on extSdCard

Titanium Backup Not Restoring

Hey all,
I have Titanium Backup setup with root and access to my backup folder. When I do a restore job however it just hangs at 0%. Is it just outdated SU Bimaries that will do this or is there something else im missing ?
Cheers

do you have busybox installed?

Nope, That itself seems to fail to install under standard directories unfortunately.

Did you tried to backup and restore from internal SD?

That is a fair comment, I will see if it works from Internal SD.

panzerscope said:
Hey all,
I have Titanium Backup setup with root and access to my backup folder. When I do a restore job however it just hangs at 0%. Is it just outdated SU Bimaries that will do this or is there something else im missing ?
Cheers
Click to expand...
Click to collapse
Set SELinux to permissive and try restoring again.
https://forum.xda-developers.com/android/apps-games/app-selinuxtoggler-t3574688
Worked for me when having the same issue.