I some how ****ed up the mountpoint for /efs on my sm-g361f
Can some one do a "cat /etc/fstab" via twrp terminal and post the mount point please?
simmsdk said:
I some how ****ed up the mountpoint for /efs on my sm-g361f
Can some one do a "cat /etc/fstab" via twrp terminal and post the mount point please?
Click to expand...
Click to collapse
I found out by looking at the log file when booting into recovery.
The text flows fast past, so i had to video it, and pause to find it.
/efs is mounted at /dev/block/mmcblk0p6
Related
I am using Terminal Emulator on the phone (because my PC is screwed up). I am trying to copy a directory from the sd card to /system/media/audio directory on the ROM.
I am able to get rw access to the ROM by typing in..
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
then I am trying to copy the file by typing..
cp -r /sdcard/download/ringtones /system/media/audio
It gives me an error saying "Cannot allocate system memory"
does anybody know what that means? How can do this?
you can't copy across mount points. At least, I think that may be what's happening.
You cant write to system from a droid itself....need to use recovery
Hi folks,
This isn't about mounting as a usb drive or anything; I'm trying to gain rw access to /system, but my usual command for that - "mount -o remount,rw /system" - returns the following:
Mount: not found.
Any idea why that would be? This is running CM7 off an sdcard.
try prepending busybox to the command line: "busybox mount yada yada"
Hey, that totally worked! Why did that make a difference?
symlinks not setup right i guess
I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
MrLadoodle said:
I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
Click to expand...
Click to collapse
I had a similar problem once and I fixed it by restoring an old nandroid backup, I was never able to figure out what caused it.
I had the same issue when I installed the ota2 update, then tried to reroot. I think I was able to change permissions by installing, then opening superuser app.
Im on OTA1.
Hello,
I've got the same problem. With the following programs i have read/write access to /system only for seconds:
Esexplorer, file manager hd, root explorer, total commander , especially: adb shell
Strange thing: i have no problems with permissons when using x-plore or titanium backup.
(Currently OTA2)
Installing superuser again does not fix anything.
I have the same problem here (OTA2) :-/
A workaround I found is to chain the remount-command with the command you want to execute on /system:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /system && cp /sdcard/Download/kernel_modules/cifs.ko /system/lib/modules/
# ls /system/lib/modules/
bcm4329.ko
cifs.ko
scsi_wait_scan.ko
Brilliant!
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
So, basically you are without an Android launcher or file manager?
If you made a backup with NookManager, restoring it is your best bet. If not, make sure to do so once this is sorted out. Backup early and often.
Do you have wireless ADB working? You can install (or reinstall) apps that way. Or, if you have the Market working, install any file manager that will work. That will give you access to folders again and you can copy over apps via USB and then use the file manager to install them.
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
Have you tried downloading the Relaunch.apk file via a web-browser? Once the download is completed you should get a prompt on whether you want to install it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:19 PM ----------
gsms said:
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
Click to expand...
Click to collapse
To mount /system as read+write:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
After you're done with copying over the desired file into /system, just reboot the nook to revert the mounting back to read-only.
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
Click to expand...
Click to collapse
The mount command line I provided is the correct command for your purpose. Note that the command is to be entered on the NST itself after you get on it using "adb shell" command.
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
The folder permission 755 is inoperative since the filesystem itself is still being mounted read-only.
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
I have been able to successfully achieve this with this command:
mount -o remount rw /system
The command is simpler and thus I am less likely to make a typo.
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
gsms said:
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
Click to expand...
Click to collapse
Make a backup
A few days ago I was having some problems with my phone and lineage 14.1 so I decided to reflash the ROM, only to notice it wouldn't boot. I then decided to install the stock 6.0.1 firmware through odin, but when I rebooted the device, it just stayed on the samsung galaxy a3 screen. I managed to boot the device with a 4 part 5.0.2 polish firmware, which is bloated and doesn't remember wifi passwords, so I decided to try to reinstall the 6.0.1 firmware, thinking I had fixed my phone. I just ran into the same problem as the first time.
This time I noticed that when I booted into recovery, there was an error mounting /efs ("E:failed to mount /efs (invalid argument)"). Going through the internet I found many ways to fix the problem but none worked for me. The one I saw most people had success with was one that involved using some commands in adb, which failed for me.
The commands where:
adb shell
su
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1
reboot
all the commands up to "mount -w -t ext4 /dev/block/mmcblk0p1" worked fine, but this one got the error: can't find /dev/block/mmcblk0p1 in /etc/fstab
Does anyone have any idea how I can fully fix the device and mount /efs to be able to install a fully working firmware?
btw, I was using this tutorial:
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
and at the end it says that if you're not sure which particular mmcblk0p* EFS mount point to use, you should use the command mount to see which one is he EFS mount point, but I can't seem to find which one to use after using 'mount'.
The mount commant prints:
~ # [6nmount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=700004k,nr_inodes=153395,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=700004k,nr_inodes=153395)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p24 on /system type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type ext4 (rw,seclabel,relatime)
How am I supposed to know which one to use?
You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.
ashyx said:
You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.
Click to expand...
Click to collapse
Is there a specific reason why the repair firmware works but other stock firmware or rom flashed after that don't. Shouldn't the repair firmware fix the problem?
I think I already tried formating the data partition after flashing a stock firmware, but I'll give it another try in a few days as I have a lot of stuff to do right now.
If this method doesn't work, using the same commands I stated previously on the block I get from -laR /dev/block should work right?
Sorry, I don't know that much about partitions, blocks and all that deep and advanced android stuff, I had never run into a problem like this when flashing roms and kernels previously, I don't even know what caused tha problem on the first place...
Thanks for helping!
ashyx said:
You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.
Click to expand...
Click to collapse
I found the block for the efs partition (/dev/block/mmcblk0p13) with your command, but when running the previous commands on it, I still get the "mount: can't find /dev/block/mmcblk0p13"
I already factory data reset my phone a couple of times after the problem occured the first time, and it didn't do anything. Any other ideas why something like this would happen?
EDIT: When I rebooted my phone I noticed my wifi was working (before this, all my wifi passwords would get erased on reboot) and when I checked the /efs folder on root explorer I noticed it was full, not like before. Seeing this I decided to try and install the stock firmware again and it worked!
Thank you so much for your help, looks like I just had to find the right block all along...
Result