Develop Bugs

[Q] Copying files to /system | S-ON | HTC One X

I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.

adb remount
adb push filename /system/xbin
Sent from my HTC One X

You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app

realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .

Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.

KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)

realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?

KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.

realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590

realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .

make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.

NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.

Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.

[CWMR ZIP] ICS Keyboard backlight fix

First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE

Awesome!

does not work for me...

Worked perfect here, that fixes my only serious issue with the ICS rom.

I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.

does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing

The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.

Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.

Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was

Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium

Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!

Can anyone help me with this via step by step?

I could use a little help as well
Sent from my SGH-I927 using xda app-developers app

Yea, i could use some help too, after re-writing over the existing file didn't work

OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.

Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch

ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man

LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?

Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister

Hummm is their gonna b a flashable zip for this ?

Android 6.0 - SD Card access

Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.

Well, it seems Google is really retarded regarding SD Card access, changing API every other version:
http://stackoverflow.com/questions/32129716/how-does-storage-access-change-on-android-6

Radek Hulán said:
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Click to expand...
Click to collapse
i used the old Kitkat fix for my brief period on 6.0, but i rolled back to 5.1 for the time being, battery drain was too much.. here

Well, not going to root my device to gain basic features such as being able to delete photos Camera app put on SD card.
This is insane.

(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data

Thanks Radek for this!!!

Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
interesting. i see on some lines there are twrp. so this method can only be used with G4 variants that has twrp? CMIIW
i'd really like to try this on my H818P but there's no TWRP for the variant yet...

Good work mate
Requires root ?

It does not require root, but you must have unlocked bootloader.
Odesláno z mého LG-H815 pomocí Tapatalk

Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks

Continue working this metod?
Sorry for me bad english xD

[email protected] said:
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Click to expand...
Click to collapse
Download TWRP for LG G4, run it:
https://twrp.me/devices/lgg4h815.html
In TWRP, select Mount > System, from menu, and continue according to these instructions.
ADB is part of Android SDK tools:
http://developer.android.com/sdk/index.html#Other

I don't know if it is the same problem but I believe it is, so my problem is that I can transfer files from SD to internal but it doesn't work the other way around, I don't want to unlock my bootloader so is there anything else I can do? Thanks

any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP

Nazdar Radku,
the solution is known feature of MM (adopt external storage), but biggest dissadvantage of this, is that you cannot use SD card in other devices anymore - not only in PC using some reader, but not even in other LG-ie your lg g4 broke....no way to get your data back. For some reason LG didnt include this functionality of MM yet. 2nd disadvantage is slowing down your device, as acces, R/W ops are quite slower. And I agree with googles approach to SD card - they want to "protect" users is foolish - you cannot protect stupid people, they should make it as default but keep option for advanced users to access storage as before KK for advanced user as it could be done with KK & LP using that media_rw grp hack.

coolmaster121 said:
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Click to expand...
Click to collapse
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.

rick09 said:
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
Click to expand...
Click to collapse
I resolved the issue by basically booting back in to TWIRP, flashing the stock image again. (didnt loose any files as I didnt do a wipe)
Then ran through the commands from the previous post. But the "set" did not work for me. I then downloaded the build.prop file to the desktop using the "get" command and edited it with wordpad, saved and then sent over the edited file, followed the rest of the permissions and it worked fine then.

Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.

rick09 said:
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
Click to expand...
Click to collapse
Just tried, it, does not seem to work. it changes the value, says I need to restart, but after restart it goes back to false

Lg G4 SD card as internal storage
Can someone tell me a little more detail on this im new to this and trying to figure it out for myself what software do I need and how to do this to my 2 lg G4's

Replacing Boot Animation Without Rooting

Disclaimer: I am not responsible for bricking your device or bootloop. Also, note that modifying /system will break OTA update. So, please try it at your own risk.
1. Download any bootanimation and make sure to change the name to bootanimation only. You can get it from here. Link: https://forum.xda-developers.com/and...nware-t3721978 (Credit goes to @mauam)
2. Go to device settings/Developers option and turn on USB debugging
3. Make sure you have ADB tool installed properly in your computer.
4. Connect your device to the computer using the USB cable.
5. Now open ADB tool folder and paste the bootanimation zip file here.
6. On the same ADB folder, press shift+right click and open command box.
7. Type: adb shell mount /system
8. Now type: adb push bootanimation.zip /system/media
9. Type: adb shell unmount /system
10. Type: adb shell reboot

hi,
Link: https://forum.xda-developers.com/and...nware-t3721978 is not working. Can you please restore it?

sylarm said:
hi,
Link: https://forum.xda-developers.com/and...nware-t3721978 is not working. Can you please restore it?
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/android/themes/alienware-t3721978

Question After Root, Cannot Mount System as R/W !!

I'm trying to copy some notification and ringtones to the system_ext/media/audio folder with no luck. Anyone can point me to an easy to follow guide to do so ?

You can't mount system_ext since it 's an EROFS partition. EROFS partitions can't be modified.

Mdardir2002 said:
I'm trying to copy some notification and ringtones to the system_ext/media/audio folder with no luck. Anyone can point me to an easy to follow guide to do so ?
Click to expand...
Click to collapse
You can do this with ADB or ROOT. Here is how:
but Back Up your data to a safe place just in case.
With ADB:-
(copy folders with notifications and ringtones to pc)
1. Set Up 10 seconds ADB Installer on your PC.
2. Install Custom Recovery on your Phone, like TWRP.
3. Boot into TWRP Recovery and connect your Phone to PC.
4. Open CMD in your PC.
5. Type/Enter these commands:
adb root (starts adb with root permissions)
adb devices (checks if your Phone is connected)
adb push <notification location/path on PC> system_ext/media/audio/notification/ (for notifications)
adb push <ringtone location/path on PC> system_ext/media/audio/ringtone/ (for ringtones)
6. Reboot into system and Enjoy!
With ROOT:-
1. Install Magisk Root on your Phone.
2. Install Root Explorer and grant root permissions to it.
3. Copy Paste as you do in any other file manager.
Hope it helps!

Maybe a Linux OS could mount it r/w.

aiSanaul said:
1. Set Up 10 seconds ADB Installer on your PC.
Click to expand...
Click to collapse
I highly recommend NOT to use this! These binaries are 7-8yo and very, very outdated. Download and unpack the current version of Google's Platform-Tools.
aiSanaul said:
5. Type/Enter these commands:
adb root (starts adb with root permissions)
adb devices (checks if your Phone is connected)
adb push <notification location/path on PC> system_ext/media/audio/notification/ (for notifications)
adb push <ringtone location/path on PC> system_ext/media/audio/ringtone/ (for ringtones)
Click to expand...
Click to collapse
For the last step /system_ext has to be mounted r/w (TWRP mainscreen > Mount) and that's not possible. Another way is to use TWRP's file explorer for this.

WoKoschekk said:
I highly recommend NOT to use this! These binaries are 7-8yo and very, very outdated. Download and unpack the current version of Google's Platform-Tools.
For the last step /system_ext has to be mounted r/w (TWRP mainscreen > Mount) and that's not possible. Another way is to use TWRP's file explorer for this.
Click to expand...
Click to collapse
I c this phone works differently...

aiSanaul said:
I c this phone works differently...
Click to expand...
Click to collapse
Not the phone but the file system does. A good option is to mount and then modify the image with Linux (Linux knows EROFS).

WoKoschekk said:
Not the phone but the file system does. A good option is to mount and then modify the image with Linux (Linux knows EROFS).
Click to expand...
Click to collapse
um.. my phone don't have this folder in root partition. Only have /system.
Nokia 1

EROFS | Android Open Source Project
source.android.com
For RW you have to convert erofs to ext4
WoKoschekk said:
Not the phone but the file system does. A good option is to mount and then modify the image with Linux (Linux knows EROFS).
Click to expand...
Click to collapse

ChrisFeiveel84 said:
EROFS | Android Open Source Project
source.android.com
For RW you have to convert erofs to ext4
Click to expand...
Click to collapse
oh so this was the problem.... Thanks.

aiSanaul said:
You can do this with ADB or ROOT. Here is how:
but Back Up your data to a safe place just in case.
With ADB:-
(copy folders with notifications and ringtones to pc)
1. Set Up 10 seconds ADB Installer on your PC.
2. Install Custom Recovery on your Phone, like TWRP.
3. Boot into TWRP Recovery and connect your Phone to PC.
4. Open CMD in your PC.
5. Type/Enter these commands:
adb root (starts adb with root permissions)
adb devices (checks if your Phone is connected)
adb push <notification location/path on PC> system_ext/media/audio/notification/ (for notifications)
adb push <ringtone location/path on PC> system_ext/media/audio/ringtone/ (for ringtones)
6. Reboot into system and Enjoy!
With ROOT:-
1. Install Magisk Root on your Phone.
2. Install Root Explorer and grant root permissions to it.
3. Copy Paste as you do in any other file manager.
Hope it helps!
Click to expand...
Click to collapse
I know the method with root will not work even after granting root permission. It says folder is read only...

JPower123 said:
Edit: I'm sorry this was a misclick on my phone... I don't think I can delete messages lol.
Click to expand...
Click to collapse
Report your post and type "delete this" in it. Mods will delete as soon as they see.

WoKoschekk said:
You can't mount system_ext since it 's an EROFS partition. EROFS partitions can't be modified.
Click to expand...
Click to collapse
Then what is a root good for if you can't do anything on the root

Mdardir2002 said:
Then what is a root good for if you can't do anything on the root
Click to expand...
Click to collapse
You can still modify the system partitions with Magisk. That's no problem. Magisk is a systemless root method.
During the boot process a non-root device detects all partitions that are stored on your eMMC storage chip and provides them as "block devices" in the directory /dev/block/*, where each partition is listed as "mmcblk0p1" (partition 1), "mmcblk0p2" (partition 2) and so on.
The fstab file (/vendor/etc/*fstab*) tells then the system where each partition gets mounted as a file system on /root:
Code:
/dev/block/mmcblk0p65 /system
/dev/block/mmcblk0p64 /vendor
...
and so on
BTW: This is the way Linux is booting up, too.
Magisk manipulates that boot process by creating a tmpfs (temporary file system) in the directory $MAGISKBASE.
For devices running up to Andoid 9:
$MAGISKBASE=/sbin
For device with Android 10+:
$MAGISKBASE=/dev/[RANDOM PATH]
(run magisk --path in a privileged shell to get the path)
In this directory Magisk implements own block devices (mirrors) that are getting mounted, e.g. in /sbin:
Code:
/sbin/.magisk/block/system /sbin/.magisk/mirror/system
...
and so on
That means, what you can see with your root explorer app in the directory /system is not the same content as physically stored on the partition of your eMMC chip! It's the content of Magisk's own block device in a tmpfs. Additionally to that, Magisk mounts at the same time all modules installed to do its modifications.
That's the meaning of "systemless root".
As you can see, it's not necessary to have /system rw with Magisk installed.

or simply convert EROFS to ext4. because for overlayFS the kernel must support overlayFS
to convert there is a zip that is simply flashed via magisk and then executed via terminal
MFP, DFЕ, RO2RW, for Android 10+
Update channel @mfpupdate
t.me
Not testet on op 11

ChrisFeiveel84 said:
or simply convert EROFS to ext4. because for overlayFS the kernel must support overlayFS
to convert there is a zip that is simply flashed via magisk and then executed via terminal
MFP, DFЕ, RO2RW, for Android 10+
Update channel @mfpupdate
t.me
Not testet on op 11
Click to expand...
Click to collapse
Thanks, it's good to know that there is a way to convert. I honestly will not test it. it's not bothering me that much and I also heard that EROFS is faster than ext4. but if someone else tried it let us know..