Related
I've been racking my brain trying to figure out what the cause of this is and it is extremely frustrating at this point. I've written a few scripts to automate some things that I would like to do on my phone and moved them into /system/bin. They would all instantly be deleted. I've just about given up on the issue of actually using scripts because of this, but now even moving a simple .mp3 file to use as a ringtone won't work.
I moved my .mp3 file into the /system/audio/media/ringtones folder. It copies over successfully and then it is instantly deleted. What gives, and how do I fix this?
/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.
KiraYahiroz said:
/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.
Click to expand...
Click to collapse
Strange, I distinctly remember not flashing any kind of .zip on my Nexus 7. All I did was root it and I was able to read/write to system as long as I granted permissions through SuperUser. Is that not the case with this phone?
If not, where else can I move script files and ringtones in order to use them?
Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.
Just drop your ringtones, notifications or alarms in the corresponding folders on the sd card. No need to put in system anymore.
Sent from my HTC One using xda app-developers app
I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app
KiraYahiroz said:
Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.
Click to expand...
Click to collapse
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
lampel said:
I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?
raphytaffy said:
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?
Click to expand...
Click to collapse
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app
RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.
There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
raphytaffy said:
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.
Click to expand...
Click to collapse
S-ON is a security measure that does prevent writing to certain areas but I don't think it will affect writing to /system on this phone as long as the kernel allows it.
RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Click to expand...
Click to collapse
lampel said:
There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
Click to expand...
Click to collapse
No worries, I found a thread for the kernel module that will allow system writes. If anyone else is looking for the same solution, the thread is here: http://forum.xda-developers.com/showthread.php?t=2230341.
Thanks for the help everyone!
Hello guys
I am at 4.4.4 rooted and I just realized that I cannot install a custom bootanimation on my Z1. I tried with recovery, manually, with app but nothing. Pls help me
mitsosJL said:
Hello guys
I am at 4.4.4 rooted and I just realized that I cannot install a custom bootanimation on my Z1. I tried with recovery, manually, with app but nothing. Pls help me
Click to expand...
Click to collapse
You know there's just one solution to this, and it takes time..
ruggyboss said:
You know there's just one solution to this, and it takes time..
Click to expand...
Click to collapse
Which?
mitsosJL said:
Hello guys
I am at 4.4.4 rooted and I just realized that I cannot install a custom bootanimation on my Z1. I tried with recovery, manually, with app but nothing. Pls help me
Click to expand...
Click to collapse
It seems to me that you have problem either of your root or correct permission of bootanimation you try to install. What happened when you try to install it?
kulvertti said:
It seems to me that you have problem either of your root or correct permission of bootanimation you try to install. What happened when you try to install it?
Click to expand...
Click to collapse
I'm rooted and it isn't the permissions
I even deleted the original bootanimation and when opened again the folder it was there again
mitsosJL said:
I'm rooted and it isn't the permissions
I even deleted the original bootanimation and when opened again the folder it was there again
Click to expand...
Click to collapse
You used file explorer to check out your /system/media folder right? which one? But if you delete something there it not supposed to be there if you have correct rw permission there. I first think that it could be problem with bootanimation you try to install but if you can't delete something there for good I guess first look at your permission to write that folder.
kulvertti said:
You used file explorer to check out your /system/media folder right? which one? But if you delete something there it not supposed to be there if you have correct rw permission there. I first think that it could be problem with bootanimation you try to install but if you can't delete something there for good I guess first look at your permission to write that folder.
Click to expand...
Click to collapse
I tried many and different bootanimations not just one and with different ways. I'm rooted and I use the root browser and the permissions are right. But the when I delete the original bootanimation or overwrite it after entering the media file it is there. (when I tried with recovery I got an error)
mitsosJL said:
I tried many and different bootanimations not just one and with different ways. I'm rooted and I use the root browser and the permissions are right. But the when I delete the original bootanimation or overwrite it after entering the media file it is there. (when I tried with recovery I got an error)
Click to expand...
Click to collapse
May I ask if you can change anything else in that folder in away it last after reboot?
kulvertti said:
May I ask if you can change anything else in that folder in away it last after reboot?
Click to expand...
Click to collapse
Basically no and yes. I moved the audio folder it moved successful but when I got back it was both at the moved and original location.
It's like the system generates the missing files by it self
mitsosJL said:
Basically no and yes. I moved the audio folder it moved successful but when I got back it was both at the moved and original location.
It's like the system generates the missing files by it self
Click to expand...
Click to collapse
I was suggesting factory reset.. Anyway have you tried another root file manager? (i use root explorer and everything works here, but you should try several apps)
ruggyboss said:
I was suggesting factory reset.. Anyway have you tried another root file manager? (i use root explorer and everything works here, but you should try several apps)
Click to expand...
Click to collapse
Nope I prefer staying with the original bootanimation than doing factory reset
mitsosJL said:
Basically no and yes. I moved the audio folder it moved successful but when I got back it was both at the moved and original location.
It's like the system generates the missing files by it self
Click to expand...
Click to collapse
Root again. Use "Easy Root Tool". If it stuck cleaning part just run it again and you should be good.
I was trying to change Xperia S bootanimation last year. Ending up to find that problem is much deeper then basic root and root explorer.
Didn't find the way how to apply custom one.
As I remember is somehow connected with bootloader or kernel
Sent from my C6903 using XDA Free mobile app
Don't know about Xperia S but with Z1 I can change bootanimation. I use X-plore by Lonely Cat Games with r/w rights and have zero problems.
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Changing the boot animation had nothing to do with kernel or bootloader, you just have to change the bootamimation.zip in system /media
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Changing the boot animation had nothing to do with kernel or bootloader, you just have to change the bootamimation.zip in system /media
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is 1
What should I do to fix it?
mitsosJL said:
It is 1
What should I do to fix it?
Click to expand...
Click to collapse
Root your device again. Go here [ http://forum.xda-developers.com/showthread.php?t=2784900 and follow instructions from OP.
Flash this https://www.dropbox.com/s/hvzh6ztcuur3vzw/disable_ric_file.zip
Sent from my C6903 using XDA Premium 4 mobile app
Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.
mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.
You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition
Hi folks,
Using stock OOS (4.1.6 from last year) and the stock camera, I get a green screen instead of the picture for any picture taken with A-HDR mode, which seems to be the default and I can't get it to persistently turn off.
Anybody else seeing this, and is there a fix? I've updated to a recent version of the camera without solving it (though, if I open camera, and change to HDR instead of A-HDR, it works for a while).
PRobably time to update my OS but everything else is working...
Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
rdNNNN said:
Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK
Click to expand...
Click to collapse
Frankenscript said:
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
Click to expand...
Click to collapse
HOT DAMN!
That seems to have fixed it. No idea why, but THANKS MATE!
may i know how to fix this? what build.prop file? can someone guide me step by step on this?
Frankenscript said:
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
Click to expand...
Click to collapse
/system/build.prop is definitely installed with 0644. There is no conspiracy "they", who changed the shipped permissions, but it has been done by you. Most probably: build prop editor, copy build.prop with something, that doesn't honor the perms of the existing file, but unlinks and recreates the file with a umask of 666 (i.e. esexplorer) or a flashable zip manupulating build.prop. This list is far way from completeness.
BTW: you'd also check (and fix if necessary) the selinux context!
SlaJaZz said:
may i know how to fix this? what build.prop file? can someone guide me step by step on this?
Click to expand...
Click to collapse
As you can see above, many things can go wrong when messing with build.prop. As long as you don't know what you are doing, I highly recommend to enpower yourself to check and change permissions on a system file by knowledge. For now do a clean flash (including format of system), and all system files will have the shipped (and correct) permissions and sepolicy context - until you do something, that changes these.
I was using a ROM with Android 8.1 but after returning to the NovaOS (Nougat) ROM whenever I try to add any secure lock screen method (PIN / Pattern / Pass) the settings application force closure. After trying to set Pattern method the settings app just force close, but after trying to set PIN/Pass method it actually set the pin but also force close and I cannot try again to set others methods because it ask for the pin and keeps closing.
This happens in any TW or Stock based ROM. But in AOSP/LineageOS ROMs works normally.
Things I already have tried:
* Full wipe
* Reinstall at least 5 different ROMs
* Installing ROMs with and without root/gapps
* Format /system and /data
* Encrypt and decrypt phone/Microsd card.
* Changing Kernel
* "Fix contexts" in TWRP
* Smash the phone to a wall
I do not know what I can do to solve this problem, I don't want to use my phone without a secure lock/fingerprint or use Oreo ROMs, can someone help me?
Maybe try flash stock firmware using odin first and then try other roms.
Even after flashing Stock Rom through Odin the problem persists, omg...
Tried flashing Stock and doing full wipe after too but no sucess...
I think some protected/secure partition are messed up, because I noticed now my wifi password are not being saved after a reboot too, and after I flashed Stock Rom via Odin and phone reboots to Stock Recovery to finish the process, at this point I get a error in recovery like "cannot find /misc partition", I dont know if this is normal or not.
Here is more detailed logs from adb logcat, honestly I'm starting to get afraid of this not being possible to solve, please guys, I need help, there so much experts and experienced people here, you are my last hope
AeonGV_ said:
Even after flashing Stock Rom through Odin the problem persists, omg...
Tried flashing Stock and doing full wipe after too but no sucess...
I think some protected/secure partition are messed up, because I noticed now my wifi password are not being saved after a reboot too, and after I flashed Stock Rom via Odin and phone reboots to Stock Recovery to finish the process, at this point I get a error in recovery like "cannot find /misc partition", I dont know if this is normal or not.
Here is more detailed logs from adb logcat, honestly I'm starting to get afraid of this not being possible to solve, please guys, I need help, there so much experts and experienced people here, you are my last hope
Click to expand...
Click to collapse
Did u change permissions of efs folder in root directory?
Give full permissions to efs folder
MarkTejo said:
Did u change permissions of efs folder in root directory?
Give full permissions to efs folder
Click to expand...
Click to collapse
Dude, you saved me, I already had lost my hopes , the directory you mentioned was really missing permissions, I just did what you said and the problem was solved, I really wanted to be able to retribute what you did for me, I'm very grateful to you, thank you bro, you're awesome!!!
AeonGV_ said:
Dude, you saved me, I already had lost my hopes , the directory you mentioned was really missing permissions, I just did what you said and the problem was solved, I really wanted to be able to retribute what you did for me, I'm very grateful to you, thank you bro, you're awesome!!!
Click to expand...
Click to collapse
Your welcome bro
Thanks alot
MarkTejo said:
Did u change permissions of efs folder in root directory?
Give full permissions to efs folder
Click to expand...
Click to collapse
Man u just saved me..... thak you so so so much.... you are the best....
Thanks to mark Good job!
AeonGV_ said:
Dude, you saved me, I already had lost my hopes , the directory you mentioned was really missing permissions, I just did what you said and the problem was solved, I really wanted to be able to retribute what you did for me, I'm very grateful to you, thank you bro, you're awesome!!!
Click to expand...
Click to collapse
Hi guys,
I have the same problem and I have not been able to give the permissions to the efs folder, I'm using root eplorer and giving rw permissions.
The efs folder handles these 0771 permissions and I try to change it to 0775 but when restarting the phone the changes are not applied.
please help:crying:
Same issue here, is it possible to make the change persistent through reboots? I can't set screen locks :/
MarkTejo said:
Did u change permissions of efs folder in root directory?
Give full permissions to efs folder
Click to expand...
Click to collapse
galaxy note 9(n960n) problem solved, thanks!