I recently rooted my phone, and one of the first things I wanted to do was to get rid of the goddamned annoying sound that plays every time I dock my phone to charge.
From what I understand, all I had to do was rename or delete /system/media/audio/UI/ChargerPluggedIn.ogg
So I appended .bak to the filename just in case something went wrong, and it just so happens that something went wrong.
Now the phone no longer plays the original sound effect, of course, but instead of staying silent as I had expected, it starts playing the default Sony Ericsson ringtone nonstop!
To add insult to injury, there's no apparent way to shut it up except for a reboot.
I'm clueless as to why it's behaving this way. Please help, it's driving me nuts.
Phone: Z3 Compact (D5833) unlocked
Rooted and upgraded to stock Sony FW V23.4.A.1.232 following this guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
SuperSU Free V2.46
BusyBox Free V1.24.1-Stericson
Modifications: Xposed framework for LP V75 SDK22 ARM
Installed Xposed modules: Should be irrelevant, because I disabled all modules in attempt to isolate root cause, was still able to reproduce the issue will all modules disabled (yes I rebooted)
I used ES Explorer (granted SuperSU permissions) to perform all system file modifications.
Aside from renaming the original ogg file, I also tried creating a new blank file with the same name (ChargerPluggedIn.ogg) to act as a placeholder and maybe fool the system into thinking that the file exists, didn't work.
Does Sony CID have anything to do with my problem? I have not flashed RICDefeat.zip since I seem to have read somewhere that there's no longer any Sony CID issue with the latest firmware. I may be wrong?
I must admit I am frustrated that I have the ability to root and flash ROMs (albeit just following guides, but successful nonetheless), but am unable to disable a little sound effect. Argh...
Search for "Ultimate Sound Control" in PlayStore, worked for me
replace the file with the mute.ogg attached (unzip and rename it)
DeusEx80 said:
replace the file with the mute.ogg attached (unzip and rename it)
Click to expand...
Click to collapse
Thanks, this worked!
Still would like to know why simply deleting the file doesn't work for me, although I suspect I will never find out.
I had the same problem and i resolved in this way.
It seems that if it doesn't find the file or cannot reproduce it, the phone starts to play the default ringtone.
On others phones, it doesn't happen
Hi,
Since my Nexus 5 I'm used to flashing a custom script to remove system apps and push new ones.
Here is the file I'm currently using: CF-signed.zip (port from Nexus 5).
With my OP3T I can't use this script since it doesn't remove the mentioned apps and I have a weird bug. Actually I can't use the physical buttons, expand the QS tiles...
I guess it's a problem with the META-INF folder (cert, manifest, update-binary... I don't know).
If someone is using such a script please share it. I'll use it as a base for my own tweaks.
Thanks.
EDIT: I finally kept my old N5 structure and it's working flawlessly.
I've been trying to read Magisk modules documentation and I've made a few personal modules to replace/add files, but how to remove files?
For instance, what do I need to do in a module to remove some system app like it was never installed?
Use this:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#remove-folders
It'll be like all files in the target folder is deleted.
@Didgeridoohan That's it, thanks. How do I mark your answer as accepted?
Thank you.
With all the respect to topjohnwu, the linked answer is not 100% precise. If you replace system files with the empty copies, their functionality will be disabled of course, but their existence in the system will still be detectable, though the files cannot be considered as "really deleted". I can personally think of at least few scenarios when the above makes difference.
For example, there is a popular issue with Netflix not working at all on many devices with tampered boot partition (and tampering boot partition is unfortunately
required when installing any systemless root solution like Magisk...) due to the fact that the HD playback DRM library located at /system/lib/liboemcrypto.so (or /vendor/lib/liboemcrypto.so) cannot access DRM keys located in Trusted Zone and fails to do its decoding job. The popular solution is to delete the liboemcrypto.so from the system, then device shall stop trying to play HD content via non-functional HD DRM engine and it shall switch to SD DRM mode which is not dependent on hardware decoding. In result, Netflix will start to work (in SD only mode, though, but it's more than nothing...).
In above scenario, replacing liboemcrypto.so with empty file with the same name will not work. That's because Android assumes that the HD DRM is available basing only on the liboemcrypto.so existence, without checking its content or size.
My own solution when making a Magisk Module which aims to delete some file is to override that file with its copy (and its content does not really matter, it might be 1:1 copy of original as well as 0 bytes empty file...) and additionally: to set its permissions to 000 - it can be easily achieved by editing the permissions part of module's config.sh when creating a module. After installing and enabling such a module, the subject file will still exist, but it won't be seen by the system and apps at all, as the 000 permissions make it absolutely forbidden to interact with the file at all, in any way, by any user (including "system") except root.
In the summary: approach proposed above should guarantee not only that the selected files functionality will be disabled but also that the system and third party user apps shall consider that files as totally non-existent, which i find a real equivalent of deleting the file.
I'm not sure I understood everything you said but the solution above works for my use case. For instance, I have this on my module:
Code:
REPLACE="
/system/priv-app/InCallUI
"
And after enabling my module and rebooting the device, browsing to /system/priv-app/InCallUI/, there's only one file there, ".replace". The .apk from that app is not available/visible anywhere. Launchers to do not detect this app, apps which list installed apps (user or system) do not show this "removed" app.
For all intents and purposes, it works for what I personally want to achieve.
Hi there!
I'm trying to create my first module. I've got a OnePlus 7t Pro, and I'm currently running an AOSP ROM. I've just come from another AOSP ROM which I had terrible battery life with, but I loved some of the features, including having access to the OOS camera app, so I wouldn't have to rely on GCam all the time.
I looked through the files and found files (that I am assuming that allow the camera to work) in the following directories:
system/priv-app
system_ext/lib
system_ext/lib64
system_ext/priv-app
I created a barebones Magisk module with these files, retaining their original structure, and it caused a boot loop.
Even if I try to keep it as barebones as possible and have just the camera.apk in the "system/priv-app" folder, I boot loop.
Where am I going wrong?
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
I performed all operations from lineage 19.1 with magisk 25.1 full root and used mixplorer.apk root enabled.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
doesnt the factory images contain the files?
i can give you the files but i dont know if it is safe to do it or not (what information does it provide, etc. im not familiar with these kind of stuff)
YKS_Gaming said:
doesnt the factory images contain the files?
Click to expand...
Click to collapse
No they are stored on /mnt/vendor/persist.
pls?
Pixie 4 XL said:
No they are stored on /mnt/vendor/persist.
pls?
Click to expand...
Click to collapse
Thank you so much.
As for your concerns, official updates have broken sensors before and users have shared these files with no consequences to the author.
See this thread as an example.
FIXED - Android 10 - Sensors Bug
EDIT 5 In addition to the two methods highlighted below, I'm sharing a third method which was brought up in the thread. This one is much easier, however, root is required. This method works for many, however, it is not confirmed by me. Again, no...
forum.xda-developers.com
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
i was finding this thread goona try it now hope it helps
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
hello thnx for sharing
i had also missing files so merge them as you instructed from root explorer apk but when i restart all the files removed again and back to previous condition
pls help!
rooman1803 said:
hello thnx for sharing
i had also missing files so merge them as you instructed from root explorer apk but when i restart all the files removed again and back to previous condition
pls help!
Click to expand...
Click to collapse
i press on r/w but not mounted
how i can mount it as r/w
rooman1803 said:
i press on r/w but not mounted
how i can mount it as r/w
Click to expand...
Click to collapse
Are you still stuck?
Pixie 4 XL said:
Are you still stuck?
Click to expand...
Click to collapse
yup can you give me the backup of persist.img of 4xl i think restoring will fix it thnx in advance
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
I performed all operations from lineage 19.1 with magisk 25.1 full root and used mixplorer.apk root enabled.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
I meet same problem, I cannt use fingerprint in Mi 12 Pro. Where to find persist img? I tried to install firmware but it can't. Please help me.