Database Info

[GUIDE] Merging updated system apps with old one, GET MORE FREE MEMORY!!

(Preface for noobs : /system and /data are two different partitions. Freeying up /system won't get you more intrenal memory, but /data does. Old apks rest in /system and updated versions placed in /data. You can replace the old apks using newer versions)
I heared Titanium Backup PRO does something like, but you can do this with any File Explorer with ROOT access. Its works 100% for Android Gingerbread 2.3.x , try on other versions.
### Do it on your own risk, I am not responsible for anything ###
1. Update the desired app to the latest version from Google Play Store
2. Open File Manager, Enable ROOT_ACCESS, remount /System as writable
3. Goto /system/app and backup the desired apk to sdcard
4. Goto /data/app and copy updated apk
5. Paste into /System/app
6. Note down the filename of old apk and delete the old apk
7. Rename the new apk into the old filename
8. You may encounter a FORCE CLOSE if the app was running in background
9. The updated apk in /data/app will be removed automatically
10.Restart your device, Done!
I replaced Playstore, Maps, Google Search ect..
Example: For PlayStore, updated apk will be com.android.vending-1.apk, and old apk is vending.apk
Hit thanks it it works, Thanks

thanks, nice guide! All is ok (PlayStore, Terminal Emulator), but if I merge last version of "Google Play Service", then Gmail or Maps shows the message "Unknown issue with Google Play services" when I open them... do you know how to solve? thanks in advance
p.s. configuration in signature

Better use Link2SD. It makes the integration of updates into system seamless. Rebooting the device is optional (restart only if you encounter errors).

thank you for your suggestion! I tried TitaniumBackup but it gives me the same error, then now I'm trying with Link2sd and it works well, BUT the new apk file is in system/app instead of system/priv-app, and its name is "com.google.android.gms-1.apk" instead of "PrebuiltGmsCore.apk"... can this create some problems in future?
EDIT: I tried moving to the priv-app folder and renaming the apk to be identical as before and it seems to work... for now...

It's the package name, it won't create any problems. There is no need to rename the app to match the old one. Default location when converting to system app is in /system/app. I don't know if you can change the location, but you can move it manually to /system/priv-app thru root explorer. Just restart the device afterwards to eliminate FC errors.

System "semi" Writable?

I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.

FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.

I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through

Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android

[Q] SDfix and Z3

Hello All,
I have issue regarding Titanium Backup and my Z3.
My Z3 is rooted, Titanium has Root access but when i try to specify the Sd card as backup support i have a message telling me i don't have permissions to write on the Sd card.
I try SDfix app but the result is a failed....
I also try to edit my platform.xml file with Es File explorer but i'm unable to save the modification. (Here the modification i try to input).
<permission name="android.permission.WRITE_EXTERNAL_STORAGE">
<group gid="sdcard_r"/>
<group gid="sdcard_rw"/>
<group gid="media_rw"/></permission>
Any idea to fix this issue ?
I'm in stock ROM with 5.0.2 Lollipop build 23.1.A.0.690

regygys said:
Hello All,
I have issue regarding Titanium Backup and my Z3.
My Z3 is rooted, Titanium has Root access but when i try to specify the Sd card as backup support i have a message telling me i don't have permissions to write on the Sd card.
I try SDfix app but the result is a failed....
I also try to edit my platform.xml file with Es File explorer but i'm unable to save the modification. (Here the modification i try to input).
<permission name="android.permission.WRITE_EXTERNAL_STORAGE">
<group gid="sdcard_r"/>
<group gid="sdcard_rw"/>
<group gid="media_rw"/></permission>
Any idea to fix this issue ?
I'm in stock ROM with 5.0.2 Lollipop build 23.1.A.0.690
Click to expand...
Click to collapse
Have you tried reinstalling titanium/es file explorer after updating the platform.xml?
Might help as the apps permissions may not have been implemented correctly if apps didn't have write access to the SD card upon install.

ozzy lion said:
Have you tried reinstalling titanium/es file explorer after updating the platform.xml?
Might help as the apps permissions may not have been implemented correctly if apps didn't have write access to the SD card upon install.
Click to expand...
Click to collapse
Thanks for the reply.
unfortunately the issue is i cannot modify the plateform.xml manually or with the SDfix App.....

I just checked in ES File explorer and the root explorer case was not checked.
The thing is when i'm checking it it tell me that my device is not rooted (my device is rooted i have SU on it and granted ES File explorer root access from the SU menu).
As the Z3 is rooted with the root exploit of the 23.0.A.2.93 downgrade maybe it's a limitation.
Any idea ? (I try also to reinstall ES File explore with same result)

regygys said:
Thanks for the reply.
unfortunately the issue is i cannot modify the plateform.xml manually or with the SDfix App.....
Click to expand...
Click to collapse
Sorry, I misread the OP.
I'm not sure how to get around it, my suggestion was just a guess but I know google have prevented play store apps for having write access to the SD card by default.
I believe the usual way around this is to use exposed framework but I'm not sure if this is functional on Z3 running 5.x yet.

Try copying platform.xml to sdcard and copy it to computer, make modifications, and copy it back. Then use Aroma File manager in recovery, rename original platform.xml to platform.xml.bak for just in case. and copy the file from sdcard and change permissions to rw.r..r.. and you are set. Remember to mount system in recovery before starting file manager.

jassalmithu said:
Try copying platform.xml to sdcard and copy it to computer, make modifications, and copy it back. Then use Aroma File manager in recovery, rename original platform.xml to platform.xml.bak for just in case. and copy the file from sdcard and change permissions to rw.r..r.. and you are set. Remember to mount system in recovery before starting file manager.
Click to expand...
Click to collapse
Hello thank you for the reply.
It's a good idea but xperia Z3 with stock rom do not have any recovery mode. If you install any recovery partition, you void warranty (that's not a big deal) and you cannot use DRM anymore (Photo are crapy)

regygys said:
Hello thank you for the reply.
It's a good idea but xperia Z3 with stock rom do not have any recovery mode. If you install any recovery partition, you void warranty (that's not a big deal) and you cannot use DRM anymore (Photo are crapy)
Click to expand...
Click to collapse
That's completely untrue. You can install recovery WITHOUT losing warranty and WITHOUT losing DRM keys

gregbradley said:
That's completely untrue. You can install recovery WITHOUT losing warranty and WITHOUT losing DRM keys
Click to expand...
Click to collapse
Just what I was about to say, check gieroot and nut dual recovery.

I going to check "nut dual recovery" i was not aware about this trick.
My phone is already rooted.

jassalmithu said:
Try copying platform.xml to sdcard and copy it to computer, make modifications, and copy it back. Then use Aroma File manager in recovery, rename original platform.xml to platform.xml.bak for just in case. and copy the file from sdcard and change permissions to rw.r..r.. and you are set. Remember to mount system in recovery before starting file manager.
Click to expand...
Click to collapse
I try this solution and it's working now.
Thank you

RESOLVED: Unable to change file permissions (Is this a SuperSU issue?)

I have Unlocked my device using this for reference. Where I Unlocked, Flashed TWRP, then flashed firmware NXT_C900B162 & SuperSU. Worked as expected, except for the theme issue. Next day, to change my ROM, I flashed TWRP, flashed C185B190 and SuperSU on my NXT-L29. All well so far, except the theme issue.
Now I am attempting to fix the missing theme issue faced by others here. As suggested in the same thread, I tried Root Explorer (Paid) and allowed Root access. I also went to root of System partition and changed permissions to RW. Now I need to change permissions for the folder which is inside Data folder in Internal Storage.
However when I try to change the permissions of a file or folder, I get the following error.
"Permissions change was not successful. Please note that some file systems do not allow permission changes."
What is the issue? How do I fix this?
Is this a case of my SuperSU not being the correct one when I flashed second time with stock ROM? I used SuperSU from over here which was for NXT_C900B162.
Update:
Trying to add more info for someone to help me out here.
In these steps I am using ES File Explorer. This is what I am trying.
1. Open ES -> Select Root Explorer -> Tap on it again -> Select Mount R/W -> Select All.
2. Select any file -> File Properties -> Has 3 properties -> Readable, Writeable, Hidden -> Next to them there is an option to edit (Available only for some folders).
I next checked for which folders these options are available. Here is what I observed.
1. With SD Card or Internal Storage, options to edit are NOT available . Checked multiple folders within them.
2. I immediately go to /storage, and check the folder emulated. These options are available.
3. Within /storage, I check the folder which contains my sd card items. These options are NOT available.
3. I then navigate int /storage, and check folder "0", these options are NOT available.

I resolved this myself. Was looking at the wrong Data folder at the wrong path!
Man, I wasted almost an entire day.

Go to / data/media/0/ folder
The best n easiest way to do it is...
If u want to change the permission of file in your internal storage then just open root explorer ( I assume it already rooted) navigate to /data/media/0/(yourfolder)/(yourfile)
N long press n change the permission..Voila good u did it!!
This is basically due to some of them have Fat32 Filesystem format while they r in storage/sdcard which are different than Linux/UNIX file system permissions!
So if u go through /data/media/0/ then it's in ext3/ext4 format which is why u can change the permissions!!😄😃

No longer able to copy files to /System

Recently had some issues with my device that caused me to to come back from a soft brick. Since then I have not been able to copy or replace files in the /System directory.
Items that have been tried and do not result in access:
Re-flash ROM (RR)
Taken back to stock image and then Re-flashed ROM (RR)
Flashed a new version of Magisk
Tried mounting the /system and making rw
Used RootExplorer and ES to change permissions to rw (chmod 777)
With all these, I try and overwrite files in system and they fail. Items with non conflicting names will appeared moved, but upon reboot all files are missing.
Ultimately what I am trying to do is move additional .ogg files into the media folder within system.
Any and all help appreciated.
Edit: Finally was able to mount /system and replace/add files after fully uninstalling Magisk and then flashing Magisk-v16.1(1610).zip

If I understand correctly, you can't modify /System with Magisk. With SuperSU, you can.

shopealope said:
If I understand correctly, you can't modify /System with Magisk. With SuperSU, you can.
Click to expand...
Click to collapse
yes you can modify /system with magisk. I do it all the time. Usually delete some aosp apps I don't need and they are in system/apps.