My device is Samsung Galaxy Tab 10.1. I've tried Task ROM and now the AOKP ROM on it. I found the same problem on both ROMs.
What I have been trying to do was changing the permissions of a .ini and a .sh file in /data/data/some app folder/ after I modified the files. I used ES File Explorer to change the permisions of those two files from rw-rw-rw- to r--r--r--. But after making the change, I found myself still able to edit them and save the changes. How can this happen? Am I doing anything wrong?
I tried to ADB sideload in stock recovery, but error message was returned http://forum.xda-developers.com/showthread.php?t=2404509
CWM install wasn't successfull
I also tried to copy Bravia.zip to root of devices filesystem via ADB plugin in Total Commander. When copying was finished, device was robootet but Bravia Engine wasn't appeared in display settings.
Is it possible to install zipped updates this way or unable to install Bravia2.zip to Xperia L at all?
I didnt use modified rom with Bravia engine and other modifications because I read that wifi not working with it...
adb sideload and flashing .zip does not work on stock kernel. Btw, the bravia2.zip(from this post: http://forum.xda-developers.com/showthread.php?t=2418639) is NOT a flashable zip. I succesfully installed bravia using the following method(on stock rooted .36 firmware):
1) Extract the .zip to your sdcard of your phone
2) download a root explorer(eg:root browser: https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree )
3) then in the root explorer on your phone, go to your sdcard in the bravia folder and copy the swiqi.apk(in app) to your phone in the folder \system\app. after placing the file here, long-tab the swiqi.apk and change the permissions to -rw-r-r.
4) repeat this for all the files in the bravi folder. the files in etc. go to \system\etc and the files in lib go to \system\lib(dont forget to change the permissions.
5) now the last step is to mod your build.prop file on your phone. Again use a root explorer to do this. navigate to \system\ there will be a file called build.prop. open it. at the very bottem under all the other lines add these 2 lines:
ro.service.swiqi2.supported=true
persist.service.swiqi2.enable=1
Don't forget to leave an empty space under it, then save the file, reboot, and it should work. I have included a screenshot of my build.prop file.
hope this helped, good luck
Thank you, Thank you, Thank you!
[clicked thanks button]
I have rooted my P3113 and have clockwork mod recovery 6.0.2.7 because that one is the only one to work properly. also i have superuser (chainfire) installed. my su binary has been updated and i have flashed my ROM with cyanogenmod 10.1.3 stable. I should be able to copy and/or move files to the root folder. yet it says that it has read only permissions. i tried to chmod it to be able to write to it but the it errors and says read only file? is there any way to fix this? or a way to force it into the root folder?
What are you using the move/copy the files? Is it a file explorer app? Have you tried moving files using ADB?
I need your help, I successfully rooted my LG Velvet 5G with TWRP and Magisk. Now I want to edit files with a root browser / file manager. But it doesn't work with a single file browser despite root rights! If I want to change xml files, it does not work in spite of the set write and read rights! Even if I extract the XML and edit it on the PC and then want to insert it back into the system, it is there, but it is then empty. Is there still write protection in spite of root? It's Android 10. Please help me. best regards
The partition where the files you want to operate on as 1st thing of all things must be mounted as RW.
Many thanks for the answer. How do I install the source code (kernel) I haven't done it yet. can it be because of that? mount as rw is not successful. Here are the instructions, did I forget something? Https: //forum.xda-developers.com/t/recovery-3-5-0-caymanlm-lm-g900em-unofficial-twrp-for-lg-velvet-5g. 4193275 /
This is my first time rooting my phone (tried rooting an o+ phone but couldn't unlock the bootloader) and I want to know how to my get phone's firmware. I tried using the Samsung Firmware Downloader but it won't accept my model and region.
I've tried using SuperSu to root but Root Checker says root access wasn't properly installed. What do I do now? Can I download a different firmware from a different site and is it safe? Does showing my pda code safe?
Edit: Forgot to mention I've already flashed TWRP.
Excuse me but what is your region and model number
tech-mаn said:
Excuse me but what is your region and model number
Click to expand...
Click to collapse
Never mind, I manage to download the firmware and root my phone thanks to Samsung Downloader. I wasn't able to download it at first because I keep using XXU (the one I saw in *#1234#, samsung firmware) as my region but it was actually XTC (I checked Software information in the About Phone).
Ok
if twrp is installed
root the phone with magisk
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
Maybe it'll work
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
first root your device
then use mt manager to access build.prop file
i tested this in my sm-t585 with lineage os custom rom
alireza9082 said:
then use mt manager to access build.prop file
Click to expand...
Click to collapse
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
MasterKwonKaichi said:
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
Click to expand...
Click to collapse
as i said
use mt manager to save changes in build.prop
Since our system is F2FS you can't modify system it stays RO you can make a magisk module yourself to modify build prop also don't use supersu rooting is very easy just flash twrp then flash magisk. I'm making a custom rom which I'm hoping to release soon that's ext4 but I'm limited by time and the recent events from where I live so I can't give a ETA