Develop Bugs

[HELP] Apps force closing like crazy

Today I just tried to install some fonts using Root Explorer and all of a sudden I was stuck in boot loops. So I tried to boot into recovery mode and there was an update.zip on my device (probably from when I was originally rooting) which I think the recovery mode ran. After that, I was in clockwork and I flashed a new font.zip file and that still left me in a boot loop state.
I fixed the boot loop by manually changing permissions on DroidSans.ttf and DroidSans-Bold.ttf to match the other fonts and change owner/group to root:root.
This stopped the boot loop but now every time I boot my phone it force closes all my apps that were previously on sd. I'm not sure why this is happening and it might be other apps that are also not on my sd. It is also not showing all of my installed apps and Launcherpro no longer runs and I am stuck with default htc sense launcher. I would prefer to not wipe the entire phone to fix this.
I have tried a different sd card with the same data and I have also tried formatting the sd card and copying my files back on. Still stuck with force close errors. I am not sure what to do at this point. Any help?

Try fix permissions.

I have tried running the fix_permissions script. Didn't seem to work. Unless there's another method you are referring to. I am unable to launch ROM Manager and it seems like all of my apps are 'new' and never launched before from what they show. Including my alarm settings, those are missing too.

Think I'd restore a backup taken prior to all the font changes. You did make a backup, didn't you?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

rigman said:
Think I'd restore a backup taken prior to all the font changes. You did make a backup, didn't you?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
Click to expand...
Click to collapse
I do have a backup but unfortunately its a little bit old and I would rather fix this if possible. It feels like some folder is missing permissions. Because even stock Google talk crashes and market crashes when I try to view an app but I can search around if I want.
Another route I can go is to backup my data for apps and then install a new Rom as I have been wanting to. This would allow me to fix my problems but I need to know what folders I have to manually backup for saves.

Well some good news. After messing around with permissions on some files on the sdcard I was able to restore my notification sound back and also able to make GTalk work properly. So it looks like there is hope yet.
Where do apps store settings such as configuration, db, etc?

It looks as if my data/data partition is wiped? I'm not sure what happened but I guess that means all my app saves are gone.
Am I right to assume that?

I used this application NotEnoughSpace made by a xda member and using it to symlink some of my apps from data partition to a new area on emmc seems to work. However when I try to restore back to my data partition, it doesn't work.
So this leads me to believe that the permissions on my data partition are off and I need to change the permissions, owner, and group for the data partition and all files inside it. The command would be:
Code:
chmod 664 data/*
chown root:root data/*
And run this while outside of the main data folder. As long as the right owner/group is root:root.
Can someone confirm?

[CWM Scripts] Relatively painless backup/mod/restore scripts

Ok, these are specifically for MIUI, but they can easily be adapted to any other rom by editing the shell scripts. I'll explain how they work and it should be fairly apparent how one would need to modify for their particular rom/needs. Don't know if anyone will actually use these, but I thought I'd share. I also think it's a really good example of how CWM can be used for more than just flashing stuff.
So I've been running MIUI for a while now and I'm really happy. One little issue that popped up was every Friday when the rom was updated, the OTA update app icon gained a little "1" badge, indicating an update was available. While it's nice to be notified of the update, I occasionally didn't have the time or interest in updating so the little badge remained. I put that app in a folder, but then the folder had the little 1 badge. After a while, I started deleting the update app after install since I could always download and install updates through ROM Manager just as easily. Then I started deleting the update app from the downloaded ROM zip, along with several other apps I didn't want (Facebook, Twitter, the MIUI FileExplorer, etc) before flashing it. But this entailed downloading the Friday update on my phone, transferring it to my desktop, opening the zip in 7 Zip, deleting the unwanted files, uploading it back to my phone and then flashing. Quite a PITA.
Another issue I ran into was that the built-in MIUI backup app failed to backup my SMS/MMS messages. Actually, I don't know if it was failing to back them up, or failing to properly restore them, but at the end of the day, it wouldn't keep my text messages. I know I could avoid this by just installing each update over the current ROM, but I've always believed cleanly installing an OS helps avoid issues. I prefer to wipe everything, install clean and then restore my data.
So, the solution(s) I came up with was to mod the downloaded ROM zip file right on the phone, and manually backup and restore my data. While it took a little while to get set up, I find it actually works considerably faster and smoother than using MIUI's backup/restore app. I now have 3 simple shell scripts that are run through Clockwork Recovery just like installing any zip - one to mod the ROM after downloading, and two to backup and restore my data. Here they are:
MIUI-Mod.zip
This contains a shell script and a zip binary to handle the adding and deleting of files to/from the downloaded rom zip. When run through CWM, it copies zip and the script to /tmp and runs the script. Because the ROM zip is named differently every Friday, I figured the easiest solution was just to rename it manually. So, this script assumes the ROM zip is named "miui.zip" and is located in the root of the SD card. It's a simply matter to download the ROM on Friday, move it to /sdcard and rename it miui.zip. Here's what the script does in 2 commands:
/tmp/zip -d /sdcard/miui.zip /data/app/Twitter.apk /data/app/Facebook.apk /system/app/Email.apk /system/app/FileExplorer.apk /system/app/Gmail.apk /system/app/MIUI.us_Forums_1.1.2_AdSupported.apk /system/app/Superuser.apk /system/app/Updater.apk /system/app/MIUIStats.apk /system/media/lockscreen/* /system/media/wallpaper/*
/tmp/zip /sdcard/miui.zip /system/app/Gmail.apk
Click to expand...
Click to collapse
The first line simply opens the zip and deletes the listed files: Twitter, Facebook, Email, etc. It also removes all the wallpapers for the lock and main screens (I don't use them, so I didn't want them, but it's a good example of the use of wildcards like *).
The second line adds in the Gmail.apk from my current ROM. The latest versions of the Gmail app included in MIUI lock the mail database, which conflicts with a widget I use, so I just replace it with an older version. Every time I run the script, it removes the included Gmail app and adds in my current one. If you didn't want to add anything to the ROM, you could just delete this line entirely.
Data-Backup.zip
This just runs a shell script that creates a tar file in the root of your sdcard containing the listed files and directories. Tar files retain file permissions and owner information, so everything can be restored seamlessly. Here's how it works, it's pretty simple:
tar -c -f sdcard/backup.tar data/app/com.adobe.flashplayer-1.apk data/data/com.adobe.flashplayer data/app/com.speedsoftware.rootexplorer-1.apk data/data/com.speedsoftware.rootexplorer data/app/com.touchtype.swiftkey-1.apk data/data/com.touchtype.swiftkey data/data/com.android.browser data/data/com.android.deskclock data/data/com.android.launcher data/data/com.android.mms data/data/com.android.phone data/data/com.android.providers.contacts data/data/com.android.providers.settings data/data/com.android.providers.telephony data/data/com.android.providers.userdictionary data/data/com.android.thememanager data/data/com.android.vending data/data/com.google.android.gsf data/data/com.miui.camera data/data/com.miui.notes data/data/com.noshufou.android.su data/system data/misc/wifi
Click to expand...
Click to collapse
This creates the tar file and includes Adobe's Flash player and it's data, Root Explorer and it's data, and SwiftKey and it's data (I paired it down to just these three for this example). After that, it backs up a bunch of other data directories which include the current Browser settings, alarms, launcher settings and home screen layouts including widgets, phone logs, the current theme settings, any MIUI notes, current Wifi connections and, yes, SMS and MMS messages.
Obviously, you'd want to add in your specific apps and data directories. Sure, it takes a little work to set this up, but as I said, backing up is very quick and easy afterwards.
Data-Restore.zip
This just runs a shell script that restores all the files from the backup.tar on your SD card:
tar -xf /sdcard/backup.tar
Click to expand...
Click to collapse
Doesn't need much explanation.
So, the process is:
1-Download the Friday update through ROM Manager, move it to the root of my SD card and rename it to miui.zip
2-Reboot into CWM and run Backup-Data.zip to back up my apps and data
3-Run MIUI-Mod.zip to modify the downloaded MIUI rom
4-Wipe everything (cache/data/system)
5-Install the modded MIUI rom
6-Run Data-Restore to restore apps/data
7-Reboot
It's literally about 5 minutes after downloading the ROM and I'm updated and rebooted with a CLEAN os install and all my apps, data and settings intact, my home screen layouts, keyboard, wallpapers, wifi settings and everything retained.
Some notes:
1-Before running these in CWM, you have to make sure you have system, data and sdcard mounted since the scripts will be reading and/or writing to all of these. When you first reboot to CWM, just go to mounts and manually mount each one. The scripts could certainly be set up to mount them automatically, but mount points vary from phone to phone, and it's not difficult to mount through CWM. Also, after flashing a ROM, the ROM install script may unmount some of these, so before you restore your data, you might have to manually remount.
2-If you're adding anything from your current ROM to the zip (like how I add in my current Gmail.apk), make sure you wipe everything *after* running the mod script, otherwise you're deleting everything and then trying to copy file(s) that were just deleted.
3-I would highly recommend using Notepad++ to edit scripts, since it properly saves Unix line breaks.
4-as always, use at your own risk and a full CWM backup is highly recommended before messing with these.
That's pretty much it. Again, it does take a little while to get set up, but once it is, it's really simple. If you install a new app between updates, you just have to edit the backup script, or you can just keep the scripts maintaining a base setup and reinstall various apps through the market each time. This specific process is probably most useful for ROMs that are updated regularly - nightly or weekly, although I'm sure people can find other uses for running scripts through CWM.
Hope someone might find these useful.

This is really cool. I run Miui and would really like to be able to do a fresh install each week, but hate the hassle of resetting up my phone, even using Titanium backup, it's still a time consuming process. So needless to say, I flash the new rom over top of the old version without wiping just to save time.
So, basically I can open up the data restore zip in 7 zip, add in a few of my apps/data such as Tasker and so forth, close it and flash? If so, that will be great.
Thanks for sharing this!!!

You don't need to touch the Data-Restore.zip, all that does is extract the backup.tar file created with the backup script. What you'd do is open the Data-Backup.zip and edit the backup file (it's just a text file). Add in any of your apps and their corresponding data directories and when you flash the Data-Backup.zip in CWM, it'll back up those files/folders.
To find the files you want to backup, use something like Root Explorer and look in /data/app. There you'll find all the 3rd party apps you've installed. Add each one to the tar command in the backup file just like the ones I included. Then go into /data/data and find each app you want to back up's corresponding data folder. Add them to the tar command too.
Save the file, re-zip it and when you flash it through CWM, it'll back up the new files.

Just what i wanted
I also always install everything from clean system so setting up everything is a pain.
Would this work for Internal storage? I have a Motorola RAZR XT910 and running JBX roms.
Google does install all the apps when i sign in into the new rom but then i always had to move each folder to the correct destination manually using some file explorer. was thinking of making something like this but didnt know how to start. Thanks, I will now try and mod these to suit my phone :good:

[Q] DataSwap by kbeezie

I've flashed the script and turned on DataSwap and contact pictures in messaging app are gone... Any ideas how to revert this?
I'm on Gen.Y VisionX B3.

If you installed Only data swap this would not happen as it only installs one shell script that makes a /data/local/swap
Need more details.
Sent from my T-Mobile G2

Hmmm... I performed a back up, than I fixed permissions via ROM menager. I went to recovery and install your script choosing only data swap. Then I rebooted the phone and noticed that contacts pictures in messages are gone. Is it possible that fixing permissions removed pictures?

mmalyy said:
Hmmm... I performed a back up, than I fixed permissions via ROM menager. I went to recovery and install your script choosing only data swap. Then I rebooted the phone and noticed that contacts pictures in messages are gone. Is it possible that fixing permissions removed pictures?
Click to expand...
Click to collapse
It shouldn't I've done permission fixes myself regularly in the past. Course I don't use rom manager either. Permission fixes should simply go thru the file system and make sure the apps and folders have the proper ownership and permissions.
The dataswap enabler zip if you only picked dataswap (skipped on both sd-ext and sd-swap) would have done:
1) installed an init script to /system/etc/init.d/80dataswap
2) set it's permission to 0750
3) cleared dalvik-cache and /cache (mainly important for the SD-Ext side)
4) done.
It's possible that the pictures in messaging were 'cached', and that they may just need more time to be re-sync'd (though normally they would be cached under /data/data or the SD card if saved permanently).

Ok. I did a clean install and will try to apply your script maybe at the end of this week. Contacts pictures are shown in messages normally right now.
Thanks for your help and assistance

CM7.2 DataSwap
Hello!
I installed in CM 7.2 (kernel 2.6.35.14) DataSwap and did not work
Terminal Emulator and tested it showed Swap = 0
What can I do to be able to activate the DataSwap?
thank you
Frogkiller

Internal storage unavailable after TWRP restore (stock samsung rom, tab 8.4)

FIX: with adb from computer:
adb shell
su
restorecon -v -R /data/media
possible to fix it from android directly with a terminal emulator. Type:
su
restorecon -v -R /data/media
I'll help if I can
Original post:
The restore worked, but the internal storage is unaccessible (stock samsung rom, tab 8.4)
I can access the files in TWRP though. I tried to "fix permissions" in TWRP, didn't help
Any ideas?

I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..

otyg said:
I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..
Click to expand...
Click to collapse
well, thanks for your answer. back to reinstalling
it's a pain though, I have to re-enter all my accounts, xposed, and all xprivacy settings
CM is good, but I have too many issues with it (wifi bad connection, or it won't come out of sleep mode)
*sigh*

Found the solution, if you have the same problem read the first post

Titanium backup unable to get root permission from sytemless superSU

Hello,
First of all, I'm terribly sorry to ask my question here since I'm really not sure this question has its place here, but I'm a bit at loss on where to ask or what to do. Please indulge me and tell me if there's a better place for my question.
I'm using Liquid Remix 9.0.3-20180201 on a OnePlus 3.
I have installed SuperSU 2.82 systemlessly with SuHide.
All of my apps needing root have the right to see SuperSU and are granted root permissions when they ask.
My only problem lies with Titanium Backup. When I start it, it does not ask for root permissions and shows a pop-up saying that it couldn't get root permission, indicated it tried to run "/system/bin/.ext/.su".
If I rename this file, then I see Titanium backup properly asking for root privileges (but I didn't manage to revert back the name in time).
If I reinstall superSU in "sytemfull" mode, then it works properly (but I really want systemless to avoid some games rejecting my participation).
I don't know what to do to address that issue.
I tried to change SuperSU parameters but it didn't helped.
I tried to contact Titanium backup but they ignored my requests.
If any of you have an idea, I'd take it.
I'm not sure I should ask Chainfire because he would tell me that's a Titanium Backup issue, and Titanium Backup could as easily throw away the issue (provided they would acknowledge my queries) in saying that's a problem with systemless SU.
Thanks in advance.

Excelsior82 said:
Hello,
First of all, I'm terribly sorry to ask my question here since I'm really not sure this question has its place here, but I'm a bit at loss on where to ask or what to do. Please indulge me and tell me if there's a better place for my question.
I'm using Liquid Remix 9.0.3-20180201 on a OnePlus 3.
I have installed SuperSU 2.82 systemlessly with SuHide.
All of my apps needing root have the right to see SuperSU and are granted root permissions when they ask.
My only problem lies with Titanium Backup. When I start it, it does not ask for root permissions and shows a pop-up saying that it couldn't get root permission, indicated it tried to run "/system/bin/.ext/.su".
If I rename this file, then I see Titanium backup properly asking for root privileges (but I didn't manage to revert back the name in time).
If I reinstall superSU in "sytemfull" mode, then it works properly (but I really want systemless to avoid some games rejecting my participation).
I don't know what to do to address that issue.
I tried to change SuperSU parameters but it didn't helped.
I tried to contact Titanium backup but they ignored my requests.
If any of you have an idea, I'd take it.
I'm not sure I should ask Chainfire because he would tell me that's a Titanium Backup issue, and Titanium Backup could as easily throw away the issue (provided they would acknowledge my queries) in saying that's a problem with systemless SU.
Thanks in advance.
Click to expand...
Click to collapse
If you are running Oreo and I suspect you are, then only Magisk will solve your problem.
Chainfire is no longer associated with SuperSU, so asking his help may not solve the issue.
And to my knowledge, it is not an issue for TiBU since it runs alright with Magisk.

You are running android Oreo if yes use magisk

Thanks for your answer. I'll try that.

Magisk works or not

https://forums.oneplus.net/threads/cant-open-titanium-backup.529927/
Summary:
- uninstall app
- delete data folder of titanium backup in /data/data.
- reinstall app

Excelsior82 said:
Thanks for your answer. I'll try that.
Click to expand...
Click to collapse
If you still have problems with titanium backup then try using an app called oandbackup its in the f-droid repository its free and works perfect with Oreo.

Newest version of magisk master v22 all in one apk solved my problem.
When patching boot it installs in the /sbin folder.
Go here to get https://github.com/topjohnwu/Magisk/releases/tag/v22.0
Read the install guide. https://topjohnwu.github.io/Magisk/install.html
Do NOT delete the IO file in system/xbin if it is there. Your system needs it.
Titainum backup looks for su in system/bin or system/xbin and won't install.
Look in system/xbin and if you see the file su you need to delete it and titanium backup will then install.
Also if it's in there Magisk will tell you that there are 2 su's and you need to uninstall the other one.
You can type su in terminal to get # then type which su to confirm where su is installed.
To remove su from /system/xbin
In a terminal type su hit enter...then
# mount -o rw,remount /
rm /system/xbin/su
go to the xbin in a file explores to confirm its deleted. if so then reboot
file system should go back to read only.
You can also in a terminal after you confirmed x/binsu is deleted type
su then mount -o ro,remount / to change back to read only.
Titanium backup should install.
I'm not a developer. I've learned from the forums
and by many hours of trial and error.
Hope this helps someone.

james73448 said:
You can also in a terminal after you confirmed x/binsu is deleted type
su then mount -o ro,remount / to change back to read only.
Titanium backup should install.
I'm not a developer. I've learned from the forums
and by many hours of trial and error.
Hope this helps someone.
Click to expand...
Click to collapse
It worked for me .thank you for sharing ur experience