Related
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Jacks0n said:
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Click to expand...
Click to collapse
Are you able to go with ADB through the directories?
and yeah, false Section! Q&A would be better
I am having the same issue. I actually just got my phone back from Samsung support (which is real ****ty) because the SD card started having I/O issues.
According to the ticket information they replaced the PCB.
Anyway, I immediately installed Clockwork recovery and transferred the latest Blandroid rom to the root of the SD card. No matter what I do I cannot mount the SD card from the recovery menu or format it from the recovery menu. Mounting USB storage works fine, though.
Hiya I got the same problem
Any salutation yet ?
Yeah. Don't format the internal storage with clockworkmod etc.
I have that issue I cant even open phone now
albundy2010 said:
Yeah. Don't format the internal storage with clockworkmod etc.
Click to expand...
Click to collapse
Hi The phone just stuck in boot logo I can patch iso file from adb though but I cant mount or even wipe devlink cache I dont know what to do ?
Did you ever get this resolved? If so, can you tell me how you did it?
Jouten said:
Did you ever get this resolved? If so, can you tell me how you did it?
Click to expand...
Click to collapse
1.power off...on it back...test it
2.plug your usb cable, boot into recovery..will heard usb sound from your PC, if does not work, try several times plug the usb untill you get usb sound...unplug, then reboot...
3.fresh install ROM...
Yeah, don't mess with the internal memory. I semi-bricked a Droid Incredible one time doing that. It ended up making all the internal partitions FAT. Took me hours to fix it. Be careful. I am afraid to even do it on my crespo4g. When I mount it in gparted running Linux Mint, the internal sd card showed up as not partitioned. I didn't even think about trying to partition it thinking back on the Incredible.
A solution, at least, for flashing/updating roms
Just happened to me, using CM9 after enabling the encryption I can't access the /data /sdcard paths. It would be nice to be able to read them but for me the biggest problem was how to update to the latest CM9 nighty.
In the end I've tricked the clockwork recovery to think the cache partition is the sdcard. I'll post the method in case someone find it useful.
1. Tranfer the update to the cache partition.
- Normally big enough, wipe it from the cwm if there is not enough space
adb push update-cm-9-20120305-NIGHTLY-crespo-signed.zip /cache/update.zip
2. Log into the phone and mount cache to sdcard.
adb shell
mount /dev/block/mtdblock4 /sdcard
3. Go into the cwm option to flash the uploaded package, it wont give you the mount error as we already mounted /sdcard
4. After the update log again and clear the update package, and unmount /sdcard
adb shell
rm /cache/update.zip
umount /sdcard
As long as you don't have to wipe you can continue updating and using your encrypted storage without much trouble
Help, internal storage not showing
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Hi i flash locky another CWR AND IT'S FIX LUCKY ME B^)
Sent from my Nexus S using xda app-developers app
getting SD card back
rellivisit said:
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Click to expand...
Click to collapse
I have had no luck using multiple methods to partition sd card with Nexus S. Each time I can view the modified fat32 partition from windows, add files etc, but cannot be recognised from within CWM recovery.
Left me unable to reflash roms etc.
The only thing which has worked for me is to use mini tool for windows and mount usb storage from recovery. Do a refresh from mini tool and it should come up in the list of drives. delete the partition(s) you find there (not your notebook ones of course), and reformat it as fat 32.
CWM>Advanced>Reboot recovery, move over your rom to the sd card, then try to find it in CWM, should now show up :fingers-crossed:
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S (US, T-Mobile, manufactured Dec. '10)
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've tried all the recommended procedures garnered from the first 10 or so pages in google, xda, cyanogem forum, etc:
Restore from nandroid: Not possible, can't mount the SD,
Wipe/Reset: can't wipe /media as sd card won't mount,
partition sd card from within Clockwork: indicates success but does nothing,
format from within clockwork: unable to mount,
repartition using adb: works, parted can see them, I can move files to from, but the phone will not mount,
clearing fstab: no effect,
Fastboot works, but I don't have the proper images. ADB works, as do the installed utilities. Have not tried ODIN as again, I don't have the proper images. Should I attempt to compile my own images from source?
Update: SOLVED, Microsoft Windows. To whom it may concern: I was able to mount the /dev/block/platform/s3c-sdhci.0/by-name/media from two different laptops running OSX and Fedora/Ubuntu then successfully been able to partition them with fat32 as the ClockworkMod (and maybe Cyanogen?) expect with 0 progress. Then I pulled out an old Windows machine, installed the JDK/ADK's +tools and performed the same procedure and that time it worked. I'm uncertain as to what particular quality a 'genuine' Windows formatting provides, but either this phone or the particular software combination I'm running require it. I was able to mount & re-partition the /sdcard in Clockwork, then manually remove rebuild them and upgrade to ext4 using tune2fs as usual. In the interim for work and such, I had to find a surrogate (for the SIM) and could only find and old k750i (which still had a full charge and worked flawlessly all day, btw). Wow phones used to be small.
I think I was missing something about the way ClockworkMod handles fstab, because everytime I would modify it specifically to the specs I passed to parted while creating the partitions with mkpartfs, it would either ignore or overwrite them. So be careful messing with the sd-card, the S's aren't like the One's in the sense that if you screw it (the sd-card) up or it goes bad you can't just take it out and format it in another machine/phone, you have to appeal to ClockworkMod. ODIN $ucks by the way, I found fastboot to be much more effective.
If you format the sd partition ext4, then you should change the fstab too.
from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
to from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard ext4 rw
or from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard auto rw
The 2nd last entry there is the file system type.
Likely, this would have solved your problem.
Of course, I don't know, whether the recovery has the vfat type in fstab. You might have to change it there too. On my linux box auto works very well in fstab.
Of course, if you partition your sd partition ext4, you won't be able to use it as usb memory from windows. (At least I am pretty sure you can't, haven't tried)
Well of course I couldn't let it die, I went back and started tinkering again now that I have a way back. I can't change the fstab it seems, whatever I change it to gets over written everytime either Clockwork or the Rom starts. It's weird, I know I'm missing something and I don't know much about CWMod. (had Amon_Ra on the N1, which had the nifty fsupgrade script)
The 2nd last entry there is the file system type.
Likely, this would have solved your problem.
Click to expand...
Click to collapse
I'm quite familiar with unix style fs and fstab, it's the stubbornness I'm not used to. I'm also spoiled by vi and nano. CW has some nice scripts built in as well though.
Hello!
My problem basically is that i can't use Link2sd - i'm currently running the latest CronosX mod - because it can't create the mount scripts. I keep getting the following error:
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: device or resource busy
i have a trascend class 10 8gb SD, i have a 6,5 gb Fat partition and the rest is EXT2 (now). I formatted it with minitool partition magic.
I have googled the problem for days now, seems i found nothing useful..
so far i tried:
ext3, ext4 -- then still couldn't create mount scripts, but i also had the following error msg in OR:
"can't mount /dev/block/mmcblk0p2 (invalid argument)"
although in SD utilities when checking the ext partition it recognised as EXT4 or EXT3..
with ext2 it seems working as of i don't see that msg..
still no link2sd. I read in the mod's forum that the app is supported, so it can't be the problem.. or is it?
Same issue, resoved by using FAT32
I had the exact same issue you're having. I tried using EXT2,EXT3, and EXT4 but couldn't get it to work. I finally got it working by using a FAT32 partition.
I know this may sound a bit dumb (like myself in android technicals) but
1. Do you have the specific kernel modules loaded to recognize these filesystems?
2. Are the devices attached to the PC with memory card access? [should not be].
3. Maybe you should try partitioning with a linux distro or some specific tool (might want to check out some instructions.
I am operating Link2SD with a fat16/32 partition (I don't know which )
I have same problem does someone solved it ?
i had no solutions whatsoever.. currently i'm using the mod's built in app2ext
i made an ext2 partition which i transformed into ext3 with openrecovery.. now i have an app folder which is automatically used to store my apps.
no link2sd for me anymore :\
although i have some other issues for i'm about to open a new thread
I found the solution : http://forum.xda-developers.com/showthread.php?t=1713478
linksd mount solved
with the phone plugged in to pc/mass storage i formatted the ext2 partition again. in link2sd mount in ext4.
cwkhong said:
with the phone plugged in to pc/mass storage i formatted the ext2 partition again. in link2sd mount in ext4.
Click to expand...
Click to collapse
Mount as ext4 is not a problem. It should work.
Sent from my XT720 using xda app-developers app
how you can solve this problem, is to make the second partition a active partitons with MiniTool Partition.
When de second disk is a active partition it wil boot before the boot of the system.
reply post ext 4
bSptya said:
Hello!
My problem basically is that i can't use Link2sd - i'm currently running the latest CronosX mod - because it can't create the mount scripts. I keep getting the following error:
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: device or resource busy
i have a trascend class 10 8gb SD, i have a 6,5 gb Fat partition and the rest is EXT2 (now). I formatted it with minitool partition magic.
I have googled the problem for days now, seems i found nothing useful..
so far i tried:
ext3, ext4 -- then still couldn't create mount scripts, but i also had the following error msg in OR:
"can't mount /dev/block/mmcblk0p2 (invalid argument)"
although in SD utilities when checking the ext partition it recognised as EXT4 or EXT3..
with ext2 it seems working as of i don't see that msg..
still no link2sd. I read in the mod's forum that the app is supported, so it can't be the problem.. or is it?
Click to expand...
Click to collapse
you must re-partition your sd card, BUT, just do it for your sd-ext only:
with Partition magic
1. delete your sd-ext partition (JUST YOUR SD-EXT PARTITION)
2. create partition
3. set as Primary
4. and CHOOSE ext4!!,
5. ok and then,
6. Apply
I hope this will help you..:good:
bSptya said:
Hello!
My problem basically is that i can't use Link2sd - i'm currently running the latest CronosX mod - because it can't create the mount scripts. I keep getting the following error:
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: device or resource busy
i have a trascend class 10 8gb SD, i have a 6,5 gb Fat partition and the rest is EXT2 (now). I formatted it with minitool partition magic.
I have googled the problem for days now, seems i found nothing useful..
so far i tried:
ext3, ext4 -- then still couldn't create mount scripts, but i also had the following error msg in OR:
"can't mount /dev/block/mmcblk0p2 (invalid argument)"
although in SD utilities when checking the ext partition it recognised as EXT4 or EXT3..
with ext2 it seems working as of i don't see that msg..
still no link2sd. I read in the mod's forum that the app is supported, so it can't be the problem.. or is it?
Click to expand...
Click to collapse
I had the seem problem and I solved creating 3 partitions. The first is not utilized but it must be create because as the Link2Sd as the AndroidOS search the data partition in the second (or last for AndroidOS) partition. I have created the first more small as Linux Swap, the second in ext2 fot Link2SD and the third in Fat32 for SD-Ext Data.
So the App works fine.
Sorry for my English.
Much Appreciated
thenotec said:
I had the seem problem and I solved creating 3 partitions. The first is not utilized but it must be create because as the Link2Sd as the AndroidOS search the data partition in the second (or last for AndroidOS) partition. I have created the first more small as Linux Swap, the second in ext2 fot Link2SD and the third in Fat32 for SD-Ext Data.
So the App works fine.
Sorry for my English.
Click to expand...
Click to collapse
No apologies necessary, i believe you were clear enough, well what do you know i must say inverting the order does seem to work
1. swap 2. Ext and 3. Fat/ Fat32
yabubonnah said:
No apologies necessary, i believe you were clear enough, well what do you know i must say inverting the order does seem to work
1. swap 2. Ext and 3. Fat/ Fat32
Click to expand...
Click to collapse
if i do that then i cant connect my usb storage to my PC, cuz if you create partitions with minitool, only the first partition is read as usb storage, so if you make the first part e.g. a swap file, then PC wont see your usb storage when plugged in via usb... and in minitool i see all partitions without drive letters, just .* sign after i format and create partitions.... and nothing helped me with mount script error either...
link2sd mount script error resolved
cwkhong said:
with the phone plugged in to pc/mass storage i formatted the ext2 partition again. in link2sd mount in ext4.
Click to expand...
Click to collapse
sir tnx for this info... error already resolved... thanks again so much...
Connect Phone to PC in Mass Storage Mode
Open MiniPartition Tool
Format the 2nd Parition as EXT4
Disconnect the Phone
Open Link2SD and you will see acript created and mounted already (for apps in SD card)
easy solution work for me ;D
after create partition ext 3 , just go to root file manager and change system file from read only RO to read write RW and recreate mount script on link2sd . hope it works happy new year!
NaraRockingMyAce said:
you must re-partition your sd card, BUT, just do it for your sd-ext only:
with Partition magic
1. delete your sd-ext partition (JUST YOUR SD-EXT PARTITION)
2. create partition
3. set as Primary
4. and CHOOSE ext4!!,
5. ok and then,
6. Apply
I hope this will help you..:good:
Click to expand...
Click to collapse
I had the same problem and had been looking for a solution until I found your help. Just want to thank you for this. It helped a lot! Fixed my problem :good:
Hi, I have a same problem.
But before I repartition the ext2 how can I save the content? My previlus installed apps will not work, I think in this case.
final solution
backup your sdcard and format it
recreat 2nd partition ex4
congratulation :good:
Solved!
Zachary57 said:
I found the solution : http://forum.xda-developers.com/showthread.php?t=1713478
Click to expand...
Click to collapse
Zachary had the solution for me! Just convert link2sd to system app (function of link2sd, after that my phone crashed and restarted) and clear the ext3 or ext4 partition (or reformat). I used Minitool Partition Wizard under windows. Don't forget to select primary partition!
the g330 comes with a reasonable storage. But there is not enough space for apps on /data. The internal sd-card got a lot of space. resizing /data (part. 18) may be critical and requires another recovery image. So my idea is to log in the phone, start fdisk /dev/block/mmcblk0, delete internal sd-card partition (19), then create a e.g. 1 GB partition with ext4, which I will mount on /data/app, and give the rest to a new partition 20 for internal sd-card.
I think this approach is more fail-save and can be done quite fast. I have to change just init.rc to add one mount and vold.fstab. Has somebody tried this?
yes, i know, the dalvik-cache and /data/data will still load the /data partition, and app2sd would save the same space from /data. But app2sd needs one mount for each app (at least in GB), so booting takes very long time and I have to wait until I can launch an app.
I read sometimes, the kernel get the offsets of the partitions of flash as parameters when booted - so some offsets would be wrong when I change the partion table. This would cause to fail mount /data/app - what about this?
rregn said:
the g330 comes with a reasonable storage. But there is not enough space for apps on /data. The internal sd-card got a lot of space. resizing /data (part. 18) may be critical and requires another recovery image. So my idea is to log in the phone, start fdisk /dev/block/mmcblk0, delete internal sd-card partition (19), then create a e.g. 1 GB partition with ext4, which I will mount on /data/app, and give the rest to a new partition 20 for internal sd-card.
I think this approach is more fail-save and can be done quite fast. I have to change just init.rc to add one mount and vold.fstab. Has somebody tried this?
yes, i know, the dalvik-cache and /data/data will still load the /data partition, and app2sd would save the same space from /data. But app2sd needs one mount for each app (at least in GB), so booting takes very long time and I have to wait until I can launch an app.
I read sometimes, the kernel get the offsets of the partitions of flash as parameters when booted - so some offsets would be wrong when I change the partion table. This would cause to fail mount /data/app - what about this?
Click to expand...
Click to collapse
I tried this and it works
its for g300 but it works on g330
http://www.htcmania.com/showthread.php?t=428466
sorry, its in spanish haha use the google tranlator
xals1997 said:
I tried this and it works
its for g300 but it works on g330
http://www.htcmania.com/showthread.php?t=428466
sorry, its in spanish haha use the google tranlator
Click to expand...
Click to collapse
Did i get the idea? You use link2SD (from Bülent Akpinar) , but instead of using a 2nd partition of the external SD-card with ext2, you use the internal SD-card for link2SD?
But i heard that link2SD need a ext2/3 partition? Also, in my version of link2SD there is:
mount -t ext2 -o rw /dev/block/vold/179:2 ...
btw. how is /system/etc/install-recovery.sh triggered
Hello!
Recently I recevied "Encryption Unseccesful" message on my phone. I tried to restore backup, but twrp says: "failed to mount /data". So, internal storage is dead. Found this. But cant find "repartition" menu in the cwm.
Questions is:
1. Do I need older versions of cwm to repartition sdcard? (If you have one, please share )
2. Is there any ways of recovering phone?
Thanks in advance!
no, just go to TWRP, Wipe, Format internal sdcard
sandpox said:
no, just go to TWRP, Wipe, Format internal sdcard
Click to expand...
Click to collapse
tried this, but I think internal storage is corrupted. Is there a way to use sdcard as internal storage?
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
I made 2 partitions on sd:
4gb fat32
4gb ext4
But I cant bind /data to this ext4 partition. Can you help, please?
What i did:
With TWRP's terminal:
Code:
mount -t ext4 /dev/block/mmcblk1p2 /data
- Invalid argument (dunno why)
Code:
ln -s /dev/block/mmcblk1p2 /data
- but on phone boot i receive same "encryption unsuccesful" screen.
Edited /etc/fstab - same result.
Files and mount after reboot turn back to its previous condition.
Also installed stock ROM - same message screen.
[/QUOTE]
I got advice that i must do this things with init.d scripts. How can I do this? Already tried "xda's app2sd scripts" but they works if phone completely boots in OS.
remosam said:
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
Click to expand...
Click to collapse
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
blind_aquila said:
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
Click to expand...
Click to collapse
asked sostk or noname
@blind_aquila
try to flash stock rom with odin