Related
When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
beani45 said:
When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
Click to expand...
Click to collapse
It sounds like the partition got mounted to /data/sdext2 as read-only somehow. It doesn't matter what the actual file permissions are if the partition is not mounted as read/write. Try one of the following commands to see how it is mounted:
Code:
#If using a terminal emulator on your phone
mount
#If using adb on your computer
adb shell mount
#Here's the output I get:
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,errors=continue)
/dev/block/mtdblock4 on /data/dalvik-cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on [B][COLOR="Red"]/data/sdext2[/COLOR][/B] type ext2 ([B][COLOR="Red"]rw[/COLOR][/B],noatime,nodiratime,errors=continue)
/dev/block/vold/179:4 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:4 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
If yours says "ro" instead of "rw", you might have to modify the link2sd mounting script in /etc/init.d/
I would also suggest posting this in the Link2SD thread so more people, including the dev, can help you figure it out.
I too am having a similar problem, except when trying to create a link. The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working. I checked in the link2sd thread u posted above, but found no answer to this problem after reading thru 94+ pages.
Help...please...
Bling_Diggity said:
The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working.
Click to expand...
Click to collapse
Please post the output from the mount command so it will help us figure out how the link2sd script needs to be modified if that is the problem. It would be good if you could attach or post the contents of the link2sd script also. The easiest way might be to just open up either a terminal emulator or use an adb shell through your computer for two commands(filling in the appropriate script name):
Code:
su
cat /etc/init.d/LINK2SD_SCRIPT_NAME
Copy that output and post it here. If you get a read-only error, look below on how to remount /system as r/w and try again.
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes. Another option is using adb. You can pull a copy of the script to your computer, edit it, then push it back. From a terminal/cmd prompt on your computer with adb set up:
Code:
#pull script to your current directory
adb pull /etc/init.d/LINK2SD_SCRIPT_NAME
#now edit the script then push it back and give correct permissions
adb push ./LINK2SD_SCRIPT_NAME /etc/init.d/
adb shell
su
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
Another option would be to use a terminal emulator on your phone:
Code:
su
cp /etc/init.d/LINK2SD_SCRIPT_NAME /sdcard/
#access the sdcard using a usb cable with your computer, edit the script, and disconnect from the computer
cp /sdcard/LINK2SD_SCRIPT_NAME /etc/init.d/
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
If you get read-only errors while trying to do any of the steps, you'll need to remount the /system partition as read/write. From terminal emulator or in adb shell:
Code:
su
mount -o remount,rw /system
Problem solved. Apparently something happened that caused Clockworkmod to create my partition in Read-Only mode. Couldn't figure out how to change that to R/W, so I did a complete wipe of everything (including SD card), changed over to Amon Ra, repartioned using it, reloaded everything back on to the SD card, re-flashed CM7/gapps, then booted and reinstalled L2SD. Works perfectly now. Not sure why CWM created my partition in read-only mode...but Amon Ra didn't have that issue...so I guess I'll be sticking with it from now on.
MongooseHelix said:
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
Click to expand...
Click to collapse
i seem to be getting closer with this solution but in terminal emul i'm entering
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
blkwhk said:
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
Click to expand...
Click to collapse
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
doktornotor said:
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
Click to expand...
Click to collapse
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
blkwhk said:
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
Click to expand...
Click to collapse
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
doktornotor said:
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
Click to expand...
Click to collapse
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
blkwhk said:
didn't use CWM, used minitools on PC
Click to expand...
Click to collapse
Never heard about minitools. Try something better next time. In case you wonder why FAT32 sucks then, first of all, it has no concept of permissions at all, so any process can write and delete the files there, and second, the filesystem gets corrupted all the time on unclean unmount.
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
I used minitools as well to create a FAT32, but still keep getting I/O mount-script-creation error when trying to load up link2sd.
I will say it again - do NOT use the fricking FAT32.
Same for me
Well, i just had the same problem.
To solve it, i just rebooted my cellphone (cuz i'm a lazy boy who doesn't like code lines^^).
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
link2sd failure
Erikdeperik said:
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
Click to expand...
Click to collapse
still failure when create link manually or automatic,...
......................................................................
any other sollution???
Uppppppppp. SAME problem.
I also noticed my error says /data/sdext2, but my partition type if ext4. Should that be a red flag?
I was getting an error specific to the dalvik-cache (/data/sdext2/dalvik-cache) claiming that it was read only. I used root explorer to try and change permissions for the folder, but root explorer was unable to (on a side note I WAS able to change permissions for the /data/sdext2 folder). I ended up using root explorer to edit the link2sd script..
MongooseHelix said:
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes.
Click to expand...
Click to collapse
turns out my script included the /dev/block/vold/179:2 line AS WELL AS the /dev/block/mmcblk0p2 line.. however both were showing "rw". I removed the /dev/block/mmcblk0p2 line and added mount -t vfat -o rw /dev/block/vold/179:2 /data/sdext2/dalvik-cache
works like a charm now =D
Thank you MongooseHelix and everyone else for your help!
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
Worked for me too...No formats no nothing...thanks!
Solved ! Failure Link2SD package invalid
For friends who are having problems with the "Create Link" in Link2SD, here I will try to help resolve the problem, because some days I also mess around with "Failure Link2SD package invalid" on my phone. And here's how:
previously, ROM I use is miniROM with Stock Kernel, and Sandisk 8Gb MicroSD Class10
1. Create Partition as follows:
• FAT32 = 6.50 Gb *create as primary
• Ext2 = 600MB *create as primary
• Linux Swap = 200MB *create as primary
#Put MiniTool to create partitions, search on google for a tutorial
2. Link2SD *can use whatever version, I use the latest version V3.7.3
Download Link2SD only from Playstore, do not use version Link2SD Cracked / Mod, remember only from Playstore. If you are using a version of Crack / Mod then bound to fail in the Create Link in Link2SD, and it is based on my experience these days.
If you want Link2SD full version, try using Lucky Patcher. But I do not use it that way, because this is enough for me.
Sorry for my bad english, i used Google Translate to translate my language, (Indonesia to English) :silly:
#Screenshot on Attachment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
htc one s tmobile us
I have bootloader and fastboot unlocked
I have recovery (official cwr touch) and adb functionality
I have ROM and adb functionality
Its the first build of cm9 without 1. sdcard mount 2. USB_lun0 3 mobile access or 4 wifi. I know... pretty ****ty place to be. But it is what it is
I've been trying to 1 create symlink between system and sdcard and then mount it.... so I can push a ROM to it and then flash it...or so I can push my backup file back in it and then mount with clockwork and restore... I even tried pushing a modaco ROM to /data/ and then try "recovery --update_image /data/mod.zip" but of course cwr isn't amon-ra and will not allow for flashing from anyplace but sdcard
I can write **** to sdcard....I just cannot get it mounted in recovery or Usb .I wiped my sdcard from fastboot "clear storage" and have tried many things. But that's irrelevant because do have my original Nannie saved to my computer...
I can write/push/files to sdcard... I just cant get the phone to see it.
I need help to 1 access sdcard and boot a normal ROM or 2 fastboot a Nannie back in but that's not possible without plain .img files or 2 somehow boot a ROM from a partition I can see...
I've tried many many things. I can remount it gives me rw when I remount... but the phone or the computer cannot see this...yet.
I even tried RUUing the euro version and of course that failed. I just need to flash a different ROM and the trick is getting the phone or recovery to mount sdcard.
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HWxxxxx recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HW408152 recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
recovery --flash_update mod.zip
recovery --flash_update mod.zip
exit
exit
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount
mount -o rw,remount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
~ #
Sent from my Amazon Kindle Fire using xda premium
maybe you should use code tags in the future to distinguish it from normal text. your post is a little bit confusing because of it's length ...
now to your issue:
boot into cwr
select "mounts and storage" -> "mount /sdcard"
now you can push files to /sdcard/
adb push rom.zip /sdcard/
I get Error to mount sdcard when I try to get CWR to get a file off sdcard
and when I try to mount usb -
Error - no ums_lunfile found
Sorry for being so verbose and wordy, the problem is simple, cant mount, cant get to usb.
Trying to create symlink but I dont see a vold file in here... so I am trying to make one...
this blows -----
only thing left for me to do is wait for RUU or find a boot.img and a system.img to fastboot in.
is there anyway to convert the cwr ext4 backups into .img's?
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork? any other recoveries for the htc one s? amon?
this blows!! if I can find a usable vold.fstab to use or some way to mount sdcard in recovery I would be all set!! but theres no way to mount sdcard or even ums_lunfile.
Will have to either figure something out but I would appreciate direction. thanks.
im on gtalk at joshcues
Can you boot into the os? If you can have you tried automount from the market. No experience with a phone with no external sdcard yet so i don't know if that will help at all tbh. My wife just got one so i guess I'll be learning now
automount just saves you a couple steps when you plug the device into the computer -- so you dont have to enable usb mount..although i am now trying a bunch of apps.
Yes I can boot into OS -- ive been trying different vold files... no luck so far. I can install any app I want, Ive been using stericsons Remount and Android Root Toolkit Beta https://play.google.com/store/apps/details?id=sa.root.toolkit&feature=search_result to quickly remount rootfs as rw... but it never sticks -- still, they are helpful... at least i have full adb control and am able to play with droid explorer because i am all adb'ed out for now.
if only I could at least enable wifi or get the radio going.. i would be fine with the phone without a sdcard... its kind of funny... but yes i can boot into OS, but
androidcues said:
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork?
Click to expand...
Click to collapse
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
[URL="http://pastebin.com/UMtJK88h"][URL="http://pastebin.com/xBH4Wge3"]http://pastebin.com/YUsCQsrf[/URL][/URL]
Ive got data/sdcard symlink set up and mounted. But recovery cannot flash or restore from data/sdcard. The first time I had the regular mnt/sdcard that I restored from.... but this time I cannot find mnt/sdcard.
Made link to /system/sdcard but cant make it pop up in recovery...
All thats left for me is to find either the fresh rom waiting to be flashed OR the two backups waiting to be restored that reside on sdcard. So, the last thing to do is to get sdcard to freaking pop up in clockwork recovery.
i got somewhere... but not quite at the finish line. Any suggestions? do I need to rebuild the sdcard file system from scratch? Will check back sometime this week... but golly...
jodue said:
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
Click to expand...
Click to collapse
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
androidcues said:
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
Click to expand...
Click to collapse
as i said before ... why don't you just make a link /sdcard that points to /data/sdcard ?
ln -s /data/sdcard /sdcard
how would you do that? can I create a link using adb? I'm in the same situation except that I formatted my system folder because I had no idea mounting wouldn't work (I"m coming from a different phone).
Thanks in advance.
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
jodue - I can (and have) link I can see sdcard file (with a modaco rom zip waiting on it, as well as clockwork/backup/2012-5-1xxxx) from the following links -
/data/sdcard
/system/sdcard
i sometimes have them written as mnt/sdcard but they never survive a boot.
I unable to mount sdcard in recovery using either or both of those links
I do not (yet) know how to manually add a ums_lunfile to a ROM that does not yet have it incorporated.
I have played with the permissions, looking at my other devices and seeing how other versions of ROMs have different permissions on the same app I am missing a vital switch that will allow Clockworkmod to see the sdcard. The phone may not be seeing the sdcard but it is definitely there, but cant I try to create a link between the Recovery and the sdcard?
I have messed with the vold.fstab and build.prop files in many many different ways (always restoring to default files after each attempt)
I do not (yet) know how to enable wifi on a ROM that does not yet have it incorporated.
I do not (yet) know how to enable bluetooth on ROM that does not yet have it incorporated.
I do not (yet) know how to enable the mobile connection on a ROM that does not yet have it incorporated.
So either I am going to figure out the top three items, or I am going to figure out how to mount my sdcard or have Clockworkmod recognize my SDcard so it can simply 1. restore back to normal or 2. flash a proper zip file.
It is like this phone is on perpetual vacation unless a number of things happen.... kind of funny...Id really like to fix it before the RUU comes out because once it does.. thatll be a lot of searching (Im now trying the Bing search engine because Google didnt find the answer) for nothing!
LuckyMethod said:
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
Click to expand...
Click to collapse
did you mount and as root?
it's probably the best and simplest solution for you guys to reflash with a stock RUU. i am sure that it's possible to restore a backup from the state you are in however it's hard without actually having the device in front of me ^^
good luck!
bored of waiting for ruu -- another effort
allrighty just logging some more efforts to my morbid problem - the goal was to boot into recovery and then mount..
mount /dev/block/mmcblk0p36 (36 wasnt there, tonight it was mmcblk0p34) /sdcard
or
mount -o bind /data /sdcard
i was able to make both succeed (in recovery) but clockwork did not agree, so thus unable to mount sdcard in recovery so I could restore or flash a proper rom.
I then tried flashing diff recoveries... to eliminate the off chance that it was a problem with particular cwm builds... i flashed stock recovery and then tried to make it flash rom from "internal" storage but of course HTC has that stock recovery looking for very specific files... so my "update.zip" went nowhere (pushed to both /data and /system as im not surre where it flashes from....
then i tried the modaco unofficial cwm nontouch recovery -- that did not want to mount...
then i tried the official cwm nontouch 5831 recovery (the touch recoveries take up space and I cant see the logfile in those)
i think i got somewhere with the mounting in recovery -- i wasted too much time trying to mount in runtime (upon boot) --
next ideas or where shall I go from here? Im not done by any means... anyone happen to know exactly what file the STOCK recovery is looking for when it tries to "flash update from internal storage"
any ideas, i will try. Heres a bunch of pastebins...http://pastebin.com/eTJuJuy9 and http://pastebin.com/0vUdaLvB and http://pastebin.com/qUSJMLpn and http://pastebin.com/fGkHzgbw and i am going to try some more on my windoze 8 system at home because the usb twatholes on this machine are pretty much unreliable.
steps -- I could find out if my mounting and binding needs more followup, I could find a system.img to fastboot I could find a way to flash from /data I could find a way to freaking mount another external drive I could pray like crazy that AmonRa gets a HTC One S and puts his flashable-from-anyplace-other-than-sdcard awesomeness on it....but thats about as crazy as the thought of a HTC guy dropping in here and asking me if I would mind testing his RUU.
cheers and thanks for whatever ideas you have no matter how crazy they sound. Waiting for a RUU is about as much fun as waiting for water to boil.
this is resolved.
lesson to be learned -- flashing an alpha build of a "work in progress" rom without the ability or proper OS to create your own .img files is going to 1. break things 2. cause silly threads like this, 3. force you to learn a lot more about android file systems and 4. wait for a RUU that may never come
xkonni was so kind to make me an updated system.img and accompanying boot.img from which I flashed through fastboot and then that was that.
htc sense makes no sense... but it makes no sense to recklessly flash files without reading the thread itself!! although I am just overjoyed I dont have to see sense again!
hey,
i have the identical problem and i am trying hard to solve this. but till now, i wasnt´t successfull. Is it possible that i use the files? It seems worth a try.
thx
---------- Post added at 11:44 PM ---------- Previous post was at 11:13 PM ----------
i now see that it is impossible to resore any nandroid backup in recovery, because CW doesnt find the sd-card, mounting and usb mounting doesnt´t work,too.
but the crazy thing is: after formating the sd-card i have access in windows but still not in recovery
So, let me get this straight --
You had this same issue -- could not get clockwork to see sdcard much less mount it or access sdcard?
When you were in Android you could not see sdcard or system would not see sdcard?
When you were in ADB you could see sdcard and mount it but it would never stay mounted? Did you try #mount -o bind? did you try to create link to sdcard? (of course did you mount as read/write first?) If so, let me know
You PM'd me and told me about a successful RUU you found that solved it... thats great -- but do you know why trhe problem happened in the first place?
The first time.. it was probably because I flashed a total alpha rom and shouldnt have...
but now.. it happened after I was already established..
I dont know why it happened.... I just know how to get out of it. Last night I got the flash itch and wanted to see what MIUI was up to and once again I ventured out into miui and once again I got bit hard. All of a sudden (I may have accidentially erased sdcard from one of those settings or wiped it) I could not see sdcard.... so i boot into clockwork and lo and behold.. clockwork was up to its old tricks of "cant mount sdcard!!!" and "no umslun0file!!!!" so I was like wow, whats going on?
I want to know WHY this is happening... the "fix" is there, but i dont know why this is happening.
Two things -- 1. This kind of problem has existed but most devices have removable sdcards. so its easy to give up and get a new sdcard.. etc... (problem doesnt get solved it gets trashed) but now... this problem needs to be resolved.. is there a defect? if so.. then how can we resolve these defects without having to replace the entire phone?
partitioning
yesterday... while in CM9... I decided that I wanted to try a repartition. So i pull all files from sdcard onto my desktop. Then I tried to format sdcard with Windows 8. Bizarre thing -- the computer could mount sdcard and all.. but then I got an error when I tried to do a simple format with Windows it wouldnt do it... I shrugged and booted into recovery and had clockwork do the partition...
i set my partition limits and then it proceeded to partition.. but it was "finished partitioning" less than 2 seconds later. I thought that was odd it should take at least a few moments. So maybe Clockwork could not partition or it did not? I dont know yet.
What benefit do phones with built in solid state drives or nonremovable sdcards have? Whats the point? I never had an issue with any of the dozens of sdcards -- some failed, but i simply got a new one or fixed it.
Whelp, I screwed up my filesystem. So I was messing around with commands and tried to remount /data and /cache in rw mode.
I used this command
mount -o remount,rw /
Forgot to finish typing and pressed enter, and it mounted the rootfs into rw mode.
Tried to fix so I ran
mount -o remount,ro /
Probally shouldn't have done that now that I think about it.
It mounted all of the partitions in ro mode including the sdcard.
So I was like lets go to recovery and do a nandroid restore, well it somewhat worked. It fixed all the partitions, I think, except /sdcard
Now when I try to: mount -o remount,ro /sdcard I get an error saying there is no such object.
Same with mount -o remount,ro /storage/emulated/0
Is there a command to fix this or do I need to reflash firmware?
Back in 5.1.1, I was able to mount the system partition.
Now in 7.0, I couldn't mount it anymore without making my phone crash
I've tried different methods...
Code:
mount -o rw,remount -t ext4 /system
This crashes my phone
Code:
mount -o rw,remount,rw -t ext4 /system
This reports back "...Device or Resource busy"
So then I was thinking that something might be using that directory so I tried to make a system mount point in /mnt, thinking as processes depend on /system, I must make another mount point
So I did, this time, "mount" says system is mounted with "ro,seclabel,relatime,norecovery" as it's option. so when I changed it to "rw,seclabel,relatime,norecovery", it doesn't mount, with no errors
So I tried, with system mounted on /mnt/system,
Code:
# mount -o rw,remount -t ext4 /dev/block/sda18 /mnt/system
(don't worry I know you can do ".../platform/xxxxxxxx.ufs/by-name")
This ALSO crashes my phone
So I pretty much gave up, and looked online, and all I found was the same process, but nothing on "this crashes my phone" or any other.
Agreed
I had the same problem. Hard lock up of phone.
how did u get root via adb??
DDwhite said:
how did u get root via adb??
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s6/general/unlock-bootloader-t3688594
I am trying to edit my gps.conf because of some accuracy problems but before I can push the new one I need to make the system rw first. When I try to remount it I get the following errors:
FP4:/ # su
FP4:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
FP4:/ # mount -o rw,remount /
mount: '/dev/block/dm-8'->'/': I/O error
When I try just remount the following happens:
C:\platform-tools>adb remount
Skipping /system for remount
Skipping /system_ext for remount
Skipping /product for remount
Skipping /vendor for remount
Skipping /odm for remount
remount failed
disabling verity ends in the error "Device is locked. Please unlock the device first" - Even though that is not the case.
I read somewhere that this is bad news but I am unsure. I cant even install busybox apk because it fails to write to system.
I have never tried to touch the system partition before so I am unsure how I killed something, if that is actually the case.
Do you guys have any idea how to fix this? Thank you!