Hi guys,
I'm currently trying to manipulate the file /data/system/packages.xml in order to make Android start one of my apps with another user id. However, this doesn't work because it seems that Android recreates the file completely when shutting down the system which means the old user id is being written back into the file.
Without rebooting, changing the file's contents (or even deleting it completely) doesn't do anything either, it seems that the contents are being loaded into the memory on boot.
What I need are your ideas on how I can make my app run as another user (or edit the file permanently) I need this because I want to access another app's non-exported service.
Thanks in advance!
edit: Even if I try editing the file and then shutting down the system unexpectedly (One X, holding down power for like 10 seconds without using the software shutdown), the file is being restored after reboot. When I check the file in CWM after a normal shutdown, it's also back to normal. So I guess Android rebuilds it on shutdown AND on boot.. or something?
edit2: I just tried the following: Rebooting into CWM, editing /data/system/packages.xml from there, checking file contents (worked), rebooting system - file contents restored. I'm starting to think that this isn't the file I have to edit. But which one is it?
edit3: Tried editing /data/system/packages.list instead, didn't work either. The file is also being restored to the original state.
- Android 4.1.1, CM10, German
did u managed anything?got same issue
Related
Hello all,
I have written a script to push as file to my TB and it works kind of...I just want to know why it is not functioning as it should.
Here is what I am attempting to do.
Since my HTC weather does not have my city listed and my weather is always way off, I hacked the HTC weather database to add my city. And it works great.
So I wanted to create a weather_update.zip to install using CWM to do all of this for me if I changed roms and to allow others to use it as well.
the file goes into the /data/data/com.htc.provider.weather/files directory.
My script mounts data, pushes the file, changes the appropriate permissions, then unmounts.
It works as intended because I can see the file using adb prior to reboot.
However, after a reboot, the file is overwritten by the original. I can even delete the file completely, reboot and it is rebuilt. So my modified file does not stick.
BUT, if I use root explorer and copy the file to the correct directory and change permissions, my modified file works even after a reboot.
I don't understand why it works one way but not another.
Is there a step I am missing in the updater-script?
Any help would be appreciated....
Thanks,
Scott
UPEngineer said:
Hello all,
I have written a script to push as file to my TB and it works kind of...I just want to know why it is not functioning as it should.
Here is what I am attempting to do.
Since my HTC weather does not have my city listed and my weather is always way off, I hacked the HTC weather database to add my city. And it works great.
So I wanted to create a weather_update.zip to install using CWM to do all of this for me if I changed roms and to allow others to use it as well.
the file goes into the /data/data/com.htc.provider.weather/files directory.
My script mounts data, pushes the file, changes the appropriate permissions, then unmounts.
It works as intended because I can see the file using adb prior to reboot.
However, after a reboot, the file is overwritten by the original. I can even delete the file completely, reboot and it is rebuilt. So my modified file does not stick.
BUT, if I use root explorer and copy the file to the correct directory and change permissions, my modified file works even after a reboot.
I don't understand why it works one way but not another.
Is there a step I am missing in the updater-script?
Any help would be appreciated....
Thanks,
Scott
Click to expand...
Click to collapse
I could be way off base here but wouldn't you have to recursively delete the original to keep it from rebuilding?
dbu said:
I could be way off base here but wouldn't you have to recursively delete the original to keep it from rebuilding?
Click to expand...
Click to collapse
LOL, what I was thinking too, but it doesn't seem to work, unless I am doing it wrong.
If I replace the file and reboot, the original rebuilds.
If I delete the file completely and reboot, the original rebuilds.
If I replace the file using root explorer after phone has booted and then reboot, my modified file sticks.
That is what I can't figure out. Why it sticks after OS has loaded but rebuilds if the same file is placed before reboot.
And I can't figure out where the file is being rebuilt from.
Uggggg.
I downloaded the new Stage UI from another thread. I shoved it onto my SD and attempted to just replace the current stage UI apks but it gave me "application not installed"
I deleted the Stage UI files in titanium backup and made sure they were gone in the system app folder. I rebooted and attempted to re-install from the SD card but the phone still acts like the files are there (gives me are you sure youwant to replace the application?)
I then just moved all the files into system>app with root explorer and rebooted. still nothing.
Anyway around this?
Have you tried copying the new files to the correct locations and setting the permissions (check to see what the other apps have)? Make sure you have a backup before messing with the files.
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
bump... anyone have any ideas?
replace the altered xml with a original/stock one..
If u have a backup
abhinavp649 said:
replace the altered xml with a original/stock one..
If u have a backup
Click to expand...
Click to collapse
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Gakuseinozen said:
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Click to expand...
Click to collapse
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
abhinavp649 said:
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
Click to expand...
Click to collapse
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Gakuseinozen said:
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Click to expand...
Click to collapse
This was not successful. Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
I have also posted this issue on another general forum, so apologies if this is deemed cross-posting!
My smartphone is running a stock Lollipop C6833_14.5.A.0.242_Customzied Germany.ftf ROM flashed using Flashtool, but is rooted with KingRoot and I have a dual recovery flashed and working properly.
Following that downgrade I found that my phone no longer had either a phone or alarm tone. When I try and change the alarm tone or ringtone or even notifications in settings I am presented with the file explorer. The sound selector shows nothing. File Commander is able to see and access the files, and they do not appear to be corrupted and I also tested them in my media player.
They were not in the SD card media folder, but were in tact in the system/media/audio folder in their respective folders. So I copied all the individual folders within the audio folder across to the corresponding media folder on the SD card. But that did not work either...
After searching various sites for help I managed to find instructions to download and flash Xperia Lollipop Media Sounds.zip, which I tried to do with TWRP recovery, but this failed with an error message I could not read.
I wondered whether if I were to just flash the system file from the same ROM it would restore the media file settings? Any help would be very much appreciated, as I have no way of hearing when I receive incoming calls, and my alarm does not work either. The audio seems to function fine in third party apps, so there is no physical issue as far as I know.
I also read a recommendation to copy the files across while connected to a PC, via USB, but my computer is a Mac and it does not seem to be able to access the SD cards as external drives in the same way as they appear in a PC.
Sony technical support basically told me that the only solution is to use repair within the Sony Bridge for Mac app, but I don't want to lose root, as the latest firmware upgrade is impossible to root. I really need help on this please!
Be aware that you have to set the correct file permissions after moving them to the /audio folder. The ringtones and alarm tones should be in the folder you just wrote, meaning they're on the system partition.
Just long-press or something on the audio-folder (depending on the file explorer you're using), tap "properties", and then set the permissions to 6-4-4, which is RW-R-R, or:
[x] [x] [ ]
[x] [ ] [ ]
[x] [ ] [ ]
Then reboot.
Hi Klaoss, many thanks for replying. However I have checked the permissions. The permissions for the actual files are RW-R-R, but in fact the folder permissions seem to be even more open: drwxr-xr-x, does that sound correct? I am talking about/system/media/audio/alarms, camera, notifications, ringtones and ui, which all have the same permissions.
Uh Oh! I just checked the permissions in the /storage/emulated/0/media/audio folder are non existent! Maybe this is why it is necessary to use the PC to copy the files, in order to retain the file and folder permissions? Is it also something to do with the actual formatting of the SD partition? Thanks for your patience
Just checked mine (on 5.1.1) and it does indeed look like the folders are drwxr-xr-x, while the files themselves are rw-r-r.
Also, yeah you could try that. That might actually work. Just remember to reboot after each change.
Thanks, but to be clear, do the files need to also be in /storage/emulated/0/media/ as well as in the /system/media/audio, or are they superfluous? Because if they are not needed, then I am not going to achieve anything by going to the trouble of copying the files within a PC environment.
Also, is there no way of copying files within Android without losing the permissions?
No idea, but I've always added and removed audio files from the system partition, but I know apps like Zedge and stuff adds them to the list when downloaded, so I'm guessing that 3rd party apps use the media folder on the internal memory, and not on the system partition, which requires root. So I would probably just let that folder alone, and concentrate on the system folder. Check the permissions and see what happens.
Change the permission on one or two files (incl. the folder), reboot and see if the file/files you just edited are showing up in the ringtone list. If yes, then change the permissions on the rest of them.
I have no idea what to change the system folder permissions to...remember that they were set to drwxr-xr-x. I think it is more important to be able to provide access to third party apps, that way I could temporarily choose ringtones etc using those. However I cannot access the permissions for the folder of the internal memory via my file explorer apps, even with full root access. That has to be a contributory factor to the problem. I wonder, would you mind having a look at the permissions for these folders on your device and telling me what they are compared to the system version?
Also, I would like someone else's take on this, would anyone else care to comment please?
OK, same problem, different tack: can anyone please tell me which partition I would need to reflash from a ROM or TWRP backup to restore the system media sounds and settings to original without losing my data or root? Also does it need to be the same ROM version, or can I flash a different ROM, but still a version of Lollipop? For example, could I simply extract the relevant partition from the recent 5.1.1. ROM, or would I then lose root too, or could it come from a 5.0.1 ROM, but slightly different from the one presently installed? I have several TWRP backups, but unfortunately for some reason they included the TA information (ta.mmc.win) which causes a bootloop when I try and reboot the system after flashing, and I have yet to find a way to exclude them from the restore process.
Hi,
I own a No.1 D5+ (smart watch - runs a standard Android 5.1, not Android Wear). The watch works well enough for what I had in mind when buying it, but there is one annoying thing: during bootup and shutdown it plays a melody at full volume regardless of the volume settings.
My plan was to root the device and delete / replace the file containing the melody. I searched for instructions specific to my model but couldn't find much, so I tried my luck with Kingoroot. That seems to have worked, though the root explorer app installed during the process still says it's not rooted, contrary to what the Kingoroot says.
Anyway, I tried renaming / deleting / overwriting the file both through Android Studio's Device Explorer and via adb shell, but always get an error "remote Read-only file system".
I'm guessing that means the /system/ folder is in ROM and can't be changed, or could it still be a software write protection? Is there anything else I could try to silence booting/shutting down?
I'm pretty new to all this, so any help is appreciated!