I've got two LeEco Le 2 devices: one with ROM AospExtended 6.7, one with Arrow 10.
The problem is: all have the SAME Wifi MAC address ! (00:0A:F5:89:89:FF)
This way they mess up the wireless connection.
The MAC address is always located inside the WCNSS_qcom_cfg.ini file in the path /system/vendor/firmware/wlan/prima
The file is not editable: the system says that it's on a Read-only file system
This path is not present as a mounted file system. Also /system is no more a mount point which could be remounted read write.
Is there a way to change this MAC Address ?
The file /persist/wlan_mac.bin could be an option ?
At the moment it's almost filled with zeros...
devel13 said:
The MAC address is always located inside the WCNSS_qcom_cfg.ini file in the path /system/vendor/firmware/wlan/prima
The file is not editable: the system says that it's on a Read-only file system
This path is not present as a mounted file system. Also /system is no more a mount point which could be remounted read write.
Click to expand...
Click to collapse
Copy that file to /sdcard, edit it, reboot to recovery, mount /system, and copy the file via twrp file manager. It should work that way
WiFi MAC
Already tried: mounted /system in recovery but that path doesn't exist!
There is something different in these new kernels that I still don't understand.
That was the old and easy way... now all is complicated
WiFi MAC
Solved !
Fortunately even with the new kernels and Dynamic Partitions scheme which makes /system/vendor/firmware/wlan/prima path Read Only, the file /persist/wlan_mac.bin still works !
And /persist is still a writable partition... for root users.
It seems that if the file wlan_mac.bin contains some valid values, it overrides the MAC data present inside WCNSS_qcom_cfg.ini.
I advise everyone to change the WiFi MAC address !
If everyone with a custom ROM has the default value 00:0A:F5:89:89:FF, connecting to a public hotspot could generate an huge mess if someone else with another "customized" mobile phone is already connected....
try this
https://forum.xda-developers.com/le-2/development/reset-mac-address-tested-lineage-os-t3918766
Related
Hey there?
I've got a question which I can't seem to find anywhere else and YES I have searched this forum and google. However, I may miss it.
Anyway, I've mapped my android phone as a network drive using Samba and changed the smb.conf file to show the System Root directory as well. However, system root is default set as R/O so to mange files USING my computer I need to change the permission to R/W using a file manager (such as root explorer). This is annoying, as I have to keep doing this in order to write to certail directories.
What I wish to do is create a massive guide on all of this to help out the community, however I need one little bit of information.
I would like the / directory (root) to be mounted as R/W as default so that I can quickly edit files on my PC without having to constantly change it to R/O.
If this has been answered before, I do apologize.
Thanks in advance.
Regards,
xxSHABSxx
EDIT:
To make things a bit clearer.
I want something that will automatically mount my phone's root dir into rw upon boot, without custom apps/having to manually mount as rw everytime it reboots. And yes I understand there are apps that do this.
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it'll stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
kuisma said:
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it's stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
Click to expand...
Click to collapse
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Anyway thanks for the reply!
xxshabsxx said:
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Click to expand...
Click to collapse
Or do like I did, move the root to a real ext3 non-volatile file system instead.
Hi,
I tried changing file permission on one of the folders where I saved my photos to read-only using "Root Browser Lite".
The following error message came up: "Changing permission was not successful. Please note that some file systems do not allow permission changes".
I tried using ES file explorer but it also failed.
Could someone please tell me how I could change the file or folder permission. I wanted to prevent the photos from being accidentally deleted by my children when I let them browse their photos..
My phone I9300 was rooted using CF Auto Root.
Thanks
Get root explorer, it's much better.
Simply long press on a folder and the permissions option is there.
Sent from my GT-I9300 using xda premium
Don't forget to set to rw at the top of root explorer before attempting to change permissions
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
100% work
Try this.....
http://forum.xda-developers.com/showthread.php?t=2038243
this will help you 100%..
qwerty12 said:
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
Click to expand...
Click to collapse
=============
Thank you all for your advice. The file system explanation betw FAT and ext4 fs makes sense. I have BusyBox installed.
Via Terminal Emulator, when I did "chattr -i /data/media/DCIM/Camera", I got a "permission denied".
Is there something that prevented me from this?
I'm running ICS.
Thanks
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
zoot1 said:
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
Click to expand...
Click to collapse
Thanks Zoot1.
I did that.
Image Gallary is still showing /mnt/sdcard/DCIM/Camera as "writeable".
What is the difference between two folders /data/media/DCIM/Camera and /mnt/sdcard/DCIM/Camera?
Thanks,
Note that I used +i in my example invocation of chattr. - removes the attribute; + sets it, which is what you want
Sent from my GT-I9300 using Tapatalk 2
Thanks qwerty12, after 'chattr +i folder name' , I return to root browser lite to change permission on mnt/sdcard/DCIM/Camera, I still get permission denied. What did I do wrong?
Sent from my GT-I9300 using xda app-developers app
Mount System RW
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Vanyna said:
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Click to expand...
Click to collapse
finally its worked for me thx very much dude:laugh::good:
Hi,
I've been fighting with this for weeks, and I can't seem to get it work.
Situation:
I want to make my Xperia T (CM12.1) into a usenet download machine. I'm hoping to download local, and extract external to my share.
So far I've managed to mount the share, but anything I try won't give an App write permission. I've used ES File Explorer in Root Explorer mode to write, which works, but the specific app for usenet downloading doesn't need root, so it can't write to the share.
What I've tried:
Moving the App to system
Gave him all kinds of write permissions
Changed owner and group from system to root and vice versa
Used several kinds of mount commands
Used several mounting locations (folder on SD, folder in /mnt/remote dir, etc)
Adding the user id (uid) to the mount command, to target the mount for this specific user (which the basic terminal app gave me back as something like 1 and another said my uid was 2 for example, so that's wonderful...)
Adding the Domain of the user of the share
This is my mounting script:
Code:
su --mount-master
mount -o unc=\\\\192.168.*.*\\share1,username=Rubenos,password=*****,uid=1,gid=1,rw,nounix,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777 -t cifs none /mnt/network/share1
I'm executing this from the terminal app within CM.
What am I missing here?
Thx!
Bump
Hi. I've had the same issue on Nexus 5.
Looks like the root of the problem is SELinux. You need to flash an insecure kernel and disable SELinux enforced mode.
Obviously it's not a perfect solution and maybe someone will suggest a better idea how to fix it.
Hello everyone,
I’ve a problem with my system folder as I can’t write to it anymore.
Phone: HTC Desire with Android 4.1.1;
rom: https://forum.xda-developers.com/showthread.php?t=2183281
My story: I wanted to try a model specific soft and I made a change of model in the build.prop in the system folder. Everything was ok, but when I edited back the build.prop with ES file editor, it saved the file as a blank file. I then moved the blank file to the SD card with success and tried to copy the build.prop from a backup I’ve done; and I get permission denied…
So far I’ve tried:
- Re-mounting the system folder
- Clearing ES file explorer data to give a SU access again
- Trying the same thing with Terminal Emulator but I’m not familiar with android command line
So now I’ve a phone without build.prop in the system and I suppose it will not be happy about it the next reboot.
My question: How I lost the capacity to write to the system folder, from a theoretical point of view, and how I can clean this mess as a personal matter. As the phone is still up I hope that it’s still possible to solve the problem without having to re-install everything.
If someone is interested by this, I will welcome any help.
Kuroneko
Try
mount -o remount rw system
In terminal.....And then try to copy with terminal itself...Use CP command
Thank for the help but sadly it didn’t make the trick.
I use Terminal Emulator
After several trials with the command I think that I’ve found the correct syntax but at the end it didn’t worked.
Working in the root folder where I put a copy of build.prop:
su
mount –o remount,rw /system
cp build.prop /system/build.prop
>can’t create “/system/build.prop”: Out of memory
I also tried to create a text file in the system folder with Total Commander without success.
I fear that there is a serious **** up in the system, probably with the file handling. Under windows (and dos) I could find my way but I’m not familiar with Linux system, and even less with Android. Under normal circumstance I would reboot the system but without a build.prop in the system directory I fear that it will go even worse.
Any other suggestion?
Kuroneko
PS: I’ve nothing again command line but with a 3.7” touch panel it’s far from fun…
This is due to HTC's read/write protection that is built into the boot.img. You might see if there is a custom kernel for your device that has this flag disabled.
Thank for your answer,
But I’m not sure that I follow you.
If the problem was due to an r/w protection of the boot image, how I was able to modify my build.prop, and later erase it?
If you could explain this it would help greatly as it means that I could re-boot without worry.
Ive been able to decrypt adoptable storage and copy files over from my pc, however i had to chown the media folder to be able to write.
Now on android in a normal file manager the files are 0 bytes and not readable.
I can read them and open them normally with ghost browser as root but not in the stock file manager.
Ive tried to chown -R them back to media_rw:media_rw or system:media_rw but no avail
Somehow I was able to change one folder(including files) back in a test (cant remember how)
Does anyone know if I need to change the files in /mnt/expand/<uuid> or /sdcard ?
KenzooW said:
so does it works?
Click to expand...
Click to collapse
It didnt work for me, at least not yet because i gave up as it was taking to much time there are a few folders with sym links,
Code:
/mnt/expand/<uuid>
/sdcard/
/storage/emulated
/data/media
need to compare all the permissions sometime and replicate it.. It was taking to much time and i found another solution which was to move the folders to a writeable directory after mounting (no change in permissions)
Then on the phone moving it to the right place in ghost file manager. Android has separated the permissions for apps and what not.
Overall its easier just to copy via OTG.
One thing I forgot to mention, that if you're on Linux with the decrypted sd card mounted, you can copy files over directly to the media folder (as #root) without "chown"ing.
I didnt try this but i think that it may work that way since you're not altering existing permission settings