Database Develop

Internal SD card failing after 2.2 Rogers update?

Im having issues with the internal SD card after the update. So is Dennishwc
http://forum.xda-developers.com/showpost.php?p=10484065&postcount=1057
Via Windows 7 64 "Error 0x80070057:The parameter is incorrect 'for file copy and 'The file is too large for the destination file system' when I try to make a folders.
When I try to format in Windows, it shows capacity only as 2.19GB rather than 13gb or whatever it should be. Same occurs on a Win XP laptop I tried, but explanation of the errors are more general but seem to be the same.
Seems it might be this issue that 2.2 caused for the SGS Vibrant ?
http://forum.xda-developers.com/showthread.php?t=860328
http://forum.xda-developers.com/showthread.php?t=846384
Could just be the SD card failing unrelated to the update, but I have no idea. Seems I can copy to an external SD, and then copy via the phone to the internal SD. Odd.
I have tried format via Windows, which resulted in 2.19gb size, but phone reboot reset it to 13gb. Format via phone did not resolve either.
Any fix that will work? or is it borked.

I'll repost my question here.
Did you try the "format internal-sd" from CWM recovery ?

No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.

rye&ginger said:
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
Click to expand...
Click to collapse
Download Rom Manager from the market and run it. Click on install clockworkmod recovery. Then you can reboot into recovery. Please see the clockworkmod thread for more info
Sent from my SGH-I897 using XDA App

Don't forget to root first. I had a pain rooting this JL1. I spent 20 minutes playing with JL1 and I couldn't stand the lagginess. I'm sure lagfix would've helped, but I just went to a custom ROM instead.

Tried superoneclick only once and I'm rooted even went as far as unlocking it. Also, my phone isn't affected by the sd card bug. I can transfer files bigger than 2.19 Gb and it's showing the full size in Windows. Froyo runs flawless so far even though it's still not clear whether it's official or not.

Hmm, that's an odd one indeed.
Curious - I took a look at the 2 threads that Rye pointed out and one seems to be about external sd issues and the other about the mounting issues with 2.2 vibrant kernels. Doesn't seem like the problem you are having is either one of those... Could be but didn't seem that way upon review.
Did you happen to try and restore any backup after upgrading to 2.2 or anything? Can't imagine what would cause it but seems like it's getting mounted strangely or something... Surprised that a format internal sd wouldn't fix it in recovery...
Second question - what Samsung drivers / driver pack are you using on your Windows 7 x64 install? Wondering if the driver is failing to recognize the file system type and is causing Windows to treat it as a file system that shouldn't accept a file larger than 2+GB...

I havent noticed any problems with the size of the file. What happened with mine is that i transfered a couple of movies (about 3 or so) and then transfered about 4 gigs of music. halfway through the music it started giving me the error. after that, even transferring individual mp3 or pictures would result in an error. The internal sd card showed up on my computer as having 8gig free. after that i ran the check disk (by right clicking, going to properties then tools). my computer found errors and corrected them. after that, the internal sd card showed up as only having like less than a hundred mb left

Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19gb.
Im about to do the CWM recovery format and will post the results.

If you are using the Rogers 2.2 update with no kernel modifications then the CWM will not work for you.
The Froyo kernel from Samsung comes with Recovery 3e which RomManager can not replace for 2e as 3e requires digitally signed packages.
consider (i have not tried):
- root device
- adb shell
- su
- backup any files you need on /sdcard to /sdcard/external_sd
- use the format commands to re-format /sdcard
-- probably mkfs.vfat or the like.

rye&ginger said:
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19GB.
Im about to do the CWM recovery format and will post the results.
Click to expand...
Click to collapse
Yea, really not sure if the drivers are a problem or not. When I checked mine, running the Rogers 2.2, it shows the same as what yours does in the format utility - 2.19GB. That is odd because it seems to set the filesystem type as FAT32 which can easily handle the 13.0GB size of the volume. The properties in Windows show 13.0GB w/ about 11.0GB on my disk that is available...
Regardless, I would be hesitant to format or repair that disk within Windows. Who knows if there is something within Android that is put there as a translation layer that maybe Windows isn't seeing / reading correctly through the driver, etc. I'm sure someone does know but I'm not that guy so if anyone call fill in the details...
And, after just testing on my own system... bang, same issue trying to copy a 900MB file to it... Hmm, this just got interesting.
Going to check a couple of other things, will post result.

I had this exact same issue. The only fix for it that I could find was to do a complete restore of the stock rom. Oh well, nice to have a fresh phone.

Hmm, this is not a fun problem.
Just tested formatting the volume - from within the running phone only, mind you - and the result is strange. After copying everything from my SD card to my computer, with no issues, I unmounted the USB, formatted the card through the settings / sd card storage menu / format internal sd card. Took about 30 seconds after which point I reconnected the device, windows picked it up and I mounted it, recopied about 2GB worth of data to the card with no issues at all. Added an additional 500MB file to it with no issues. Disconnected the device from within windows using the safe removal tray tool, turned off usb connection on the device and then unplugged it. Remount the usb device and windows sees it no issues but I can't copy a single item or create a folder on it. Exact same errors as what Rye described and I encountered the first time.
So, seems like after a fresh format the sd card can be mounted in windows, ONCE, and then all hell breaks loose.
Why??? Will keep testing but looking like I need to move back to my previous di11igaf's ROM. Can't work like this...
Interested in what you find, Rye.

Oh btw, i am able to transfer files with no problems if i connect to the pc in media player mode. I have problems when i am in mass storage and kies connect modes

Riker2k, good stuff. I have no news, Im stuck where I am unless I swap the kernel it seems as I cant use CMW Recovery to format.
This is over my head, so I will for now probably just do a format, load up the card via Windows, and then use the external card to slowly add items when I want to and transfer over to the internal through the handheld. Ghetto. Either our Sd cards will get worse and die, or more people will have issues and it will get patched I guess?
Dennishwc, I will try media player mode but I think it did nothing when I connected that way the other day. I didnt mess with it much though. I need mass storage to use iSyncr app though, but there is a wi-fi add-on that may help me avoid that.

Well I just tried the format and dump a lot of stuff via Windows idea, and it only did about 2.2gb before the error stopped the fun. It did this twice, so this is is EXACTLY at the 2.19gb capacity that Windows is seeing in the format utility. So, I do have some news.
Again, this is over my head as to what to do next.

Has anyone tried moving files over via adb and see if you hit a 2.19GB limit?

I am having the same issue when copy files while connected in USB Mass Storage Mode (consistent).
On the plus side, I also tried connecting in USB Kies Mode, and I have yet to see this error. Copying is slower; but, it seems to work.
This could be a workaround for folks getting the error in Mass Storage Mode.
I am running Rogers 2.2 (all stock) and rooted with SuperOneClick.

i'm having the exact same problem. if i pick "mass storage" i can't copy anything over hte internal sd card, but if i use "media play" option, i can do it without any problem. i guess that's a temporary solution

i'm having the same problem, though the size and free space of the internal storage shows up correctly in my system.
i can also copy files no problem to the external SD when in mass storage mode.

[Q] [Request] Need a way to boot 2nd partition (SDext) during boot time

Hi there,
So my N1 is rooted and has SuperOSR rom installed. The native app2sd that comes with the rom failed to work, so I disabled it and went back to the method I was using on CM7, Link2sd. I need a method to move apps/cache/lib files to sd-ext, as the tiny internal storage on the N1 is insufficient to hold even a 10th of the apps (and their data) that I have installed. And Link2sd has, at least in the past, been the perfect option to do so.
At first, all seemed well after installing and setting up Link2sd. Mount scripts were created with no problems, apps/cache/lib files all moved over to sd-ext without a hitch. Everything was going really well. Until I rebooted. Then, all hell broke loose.
The problem is this - for some reason, the second partition (sd-ext) is not being mounted during boot time. I'm not sure why, as this is exactly what the Link2sd mount scripts are supposed to accomplish. A Link2sd "mount warning" notice confirmed this problem, saying that "since 2nd partition was not mounted during boot time, linked apps will be invisible to the system until quick reboot". Indeed, every app that I had linked was not visible to the system, and most widgets on my homescreen showed only the message "problem displaying widget".
Luckily, a way to temporarily fix this is by simply quick-rebooting the rom. This will get the linked apps to show up again. But the problem is, widgets are still dead, input method gets reset (goes back from Swiftkey to native Android keyboard), and SMS gets reset back to the standard android SMS app. Of course, all of this can be changed back, but it takes time and effort to load each individual widget and restore each individual input/sms setting. It's really not practical every time you have to reboot your phone that you have to:
1. Quick-reboot the rom
2. Change input method back to Swiftkey
3. Manually restore every widget on your home screens
4. Change sms app back to Go sms.
So, my question is, how do I avoid having to do all this? I've already tried the "re-create mount scripts" option on Link2sd, but it doesn't matter. Still have the same errors upon rebooting phone every time. I'm pretty sure this means that the Link2sd mount scripts are either not being created correctly, or are being deleted every time the phone reboots. How do I fix this? Trying to get in contact with the developer of the app (bakpinar) has proven unsuccessful.
Does anyone know of any other scripts that I can flash/install that will successfully and consistently mount the 2nd partition (sd-ext) during boot time? I'm fairly certain that this is all I need, as everything else with Link2sd has been working correctly. Thanks in advance for any advice!

Ok, so since I haven't gotten any responses on this, I'm going to attempt two methods that i THINK might remedy this issue. The first one is this:
Method 1:
1. Full wipe and reinstall of SuperOSR rom
2. Format sd-ext to ext3 filesystem (found out that rom's native app2sd program wouldn't work due to my sd-ext partition being FAT32)
3. Enable rom's native apps2sd option upon booting.
4. Reboot
5. Install Link2sd from market, enable dex/lib file linking ONLY (native apps2sd program only moves app files, not dex or lib). Going to be interesting to see what link2sd says about the mounting scripts...
6. Reboot, collect results.
The 2nd method I'm going to try is this.
1. Full wipe and reinstall of SuperOSR rom.
2. Flash DTAPPS
3. Boot into ROM
4. Download and install test applications
5. Collect results
I'm not sure if either of these methods will work, however I know the 2nd method worked for CM. I will update a bit later as to which method (if any) fixed the issue. Sorry for the double post.

I commented to the ROM cook nelo360 a while back that there are some strange sd-ext mounting issues. If you look at the dmesg as it boots, it does post some strange error messages. Essentially, ext3 mounts as ext2, and ext4 mounts as ext3. Despite it not mounting as the proper format type, it still works.
Since the ROM is pulled off of AOSP, as CM is too, sort of, much of the same apps2sd apps probably work decently well.
Definitely need an ext3 or ext4 partition. As I'm understanding your post, that did not happen initially, and is crucial to many apps2ext to work, including the built-in one.

Really? Ext4 as 3 and ext3 as 2? Well that would explain why Link2sd was having issues. Hmm.
What I ended up doing was fully wiping the phone, flashing the rom, and then immediately afterwards flashing DTAPPS. Using the GUI interface found on the market, I moved apps to sd-ext and cache to sd-ext as well. The result has been mixed. While there was noticeably more space initially to install apps (something like 190mb internal), that space has declined at almost as fast a rate as when I had no apps2ext of any sort installed at all. This makes me think that while DTAPPS successfully moved some of the initially installed apps over to the sd-ext, it hasn't been moving any new ones i've installed or their cache files. I tried re-moving apps/cache with the gui interface and by using the old-fashioned terminal emulator method, but had no success. Still looking at about 100mb free space on internal. Considering that I only have about 1/4 of the apps installed that I usually have installed on my phone at any given time (I use A LOT of apps), it's become apparent that soon I am going to run out of space again.
As I can't find any method to fix this, I'm afraid I'm going to have to call it quits with this ROM and try something else. Which is a real shame, because stability-wise this ROM beats Cyanogenmod and other ROMS I've tried hands down, while not sacrificing many features. I guess for a user who doesn't use a lot of apps or need a lot of space for them, this ROM would be ideal. Unfortunately, I'm not that type of user.

One problem I've found is that with any automatic apps2sd/ext system is the control of what is actually on the SD vs. internal memory is hard to work out.
With the built in apps2sd, which you seem to have trouble with, not every app was transferred to ext. I found that with the built in system, my internal memory kept dropping until it hit 25 mb or so. However, it never really dropped below that. Everything I kept installing probably went to the ext partition. I installed a lot of apps, and it wasn't an issue. (But you're right, it may not be as many as you want).
I didn't have a great way to check this though. Root explorer showed both the data/apps/ folder and the sdcard/ext folder linked together, so it just listed everything together. I'd have loved a way to actually manually transfer whatever apps were on internal memory to ext, but never found an easy way to do so, or even to confirm what was in which directory.
So even though it looks like the internal memory is steadily and quickly dropping, if you continue to install, and have the two directories appropriately linked (sorry, I don't know what the difference between all the different kinds of scripting apps2sd are), I don't think you'll run out of space as quickly as you think you will.

[Q] CM10 and AOKP - Internal, SD card and USB storage mapping broken

I've got a Samsung Galaxy Note n7000. I've hopped around a bit, but recently I've tried to move (back) to JB based CM10 (nightly) and also AOKP (JB Milestone 1).
For both CyanogenMod and AOKP, I quickly came across the issue that most apps can't see any storage folders. This includes:
-Browser and Chrome can't save files as there's 'No storage'.
-Google Maps won't cache anything.
-The camera and gallery won't work because they can't see any storage.
-When I plug the phone in to a PC via USB, the phone is identified, but no storage folders come up, regardless as to whether I'm using MTP or MS.
-In the system settings under storage, it can see the 2GB for my app Data partition. It says there's a 32GB SD card available, but under the Internal Storage heading, clicking 'Mount SD card' flashes up something in the notification bar before looking like nothing happened. There's nothing about the internal ~10GB partition either.
However, if I go into a file browser, I can see both the internal storage mapped as /storage/sdcard0 and the SD card mapped as /storage/sdcard1. I believe this is how JB is now mapping storage now? Why is it confusing itself?
Note:
-I can see the storage in CWM without issues (although internal and SD might be reversed???).
-I can read the files fine from a file manager, so there's nothing wrong with the SD card as far as I can tell. It works fine in an SD card reader too.
-I tried AOKP first after a full wipe (factory, data, davlik), hit the issue. Tried CM10 which was the same. Tried AOKP again with a factory wipe before and after flash and it still didn't work.
I've been trying to find a solution for nearly 2 weeks now! Please help before I give up and flash back to a Samsung based ROM!
For history:
I've had the GNote unlocked for a while and I've played with a few ROMs including CM9, earlier releases on CM10 without any issues. For the past couple of months I went back to an ICS TouchWiz based ROM as I thought the only way to get an MS Exchange email email app with full device encryption was to use Samsung's.... anyway, found an app that'll do it for me without suffering the slow down of encrypting the whole phone AND putting TouchWiz on, so I thought I'd try to go back to a 'pure' ROM until I ran into the above problem... Is it because I previously had the phone fully encrypted? I can see the folders now though.... AAAARRRRGGH!

...
Just in case it was an issue that has been fixed recently.... I tried ParanoidAndroid for the Note (v2.54 10 Nov 2012)... same issue. I did a factory reset, cache wipe and davlik wipe before and after flashing. Still both internal and SD storage are mapped so the apps and System settings can't see them.
What is wrong?

Update 2...
I tried flashing the following ROMs:
-A TouchWiz based ICS ROM (Sweet v5)
-A stock based ICS ROM (CM9.1)
-A TouchWiz based Jelly Bean ROM (Rocket Bean V2)
-Re-flashing CM10 nightlies
In every case both the internal and SD storage can't be seen in System>Storage.
What have I done???? Have I somehow screwed up the formatting on both the internal and SD card, yet CWM can read it??? Any ideas?

im on a XXLS7 based rom and its in
/storage/extSdCard
/storage/sdcard0
may be you want flash a stock GB or ICS rom again using Odin and start fresh

I haven't tried Odin yet... but when I was about to, I discovered something. I installed Titanium Backup. Instead of complaining I didn't have any storage (like all other apps), it complained that my storage directory wasn't writeable...
How do I check what the permissions are? What should they be? How do I fix it?!!!
Thanks.

Hi!
I have the same issue.
I'm currently on RocketRom V3 but I had the issues with others roms before.
I have a temporally fix: using root explorer, set the permission from r/o to r/w for the folder /mnt/sdcard
But after a while (fews minutes), it turn back to r/o, I don't know who/why.

Same here. Thought it was me!
Started when I switched to jb leak.
Says storage us full when I try to open camera,etc, even though it's not true
Sent from the man hiding in your attic.....

Ok, I found an fix that works for me
It looks that I had a bad file/folder/whatever on my internal storage, so the system put /sdcard (internal memory) on read only as it notice the bad thing.
Formating sdcard or emmc from cwm didn't work, full wipe neither, formatting internal from android settings neither, but I manage to mount internal SD on my computer using mass strorage (UsB switcher is included on Rocket V3 to switch from MTP to Mass storage)
Once mounted in Windows, I did a full format (fat32) of the internal memory, and so far it works!

I re-formatted my SD card in a memory card reader. I've put it back in the phone and now when I plug my phone in to my PC and select USB mass storage, the SD card comes up in Windows and I can write to it! Woot!
At the moment I still can't write to my internal storage (which means most apps still complain). It appears as a drive in Windows via USB, but I can't open it. I'll try Feyris' RocketRom suggestion later.
Any guess as to why this has happened? Anything to do with the fact I had full-device encryption on the phone before????

Is there any way to sawp the card location as on im on jb its taking external card as internal default location..As i am having class 4 sdcard so itz slowing down the system

Feyris said:
Ok, I found an fix that works for me
It looks that I had a bad file/folder/whatever on my internal storage, so the system put /sdcard (internal memory) on read only as it notice the bad thing.
Formating sdcard or emmc from cwm didn't work, full wipe neither, formatting internal from android settings neither, but I manage to mount internal SD on my computer using mass strorage (UsB switcher is included on Rocket V3 to switch from MTP to Mass storage)
Once mounted in Windows, I did a full format (fat32) of the internal memory, and so far it works!
Click to expand...
Click to collapse
When I put my Rocket V3 into the mac with usb switcher it mounts two drives. Both, however, are part of the internal SD card. It does not mount the proper external sd card. One is titled sdcard of the drives just called sdcard, the other is called storage (which has folders sdcard0, extSdCard, and usbstorageA-F). Should I format them both? Do I need to recopy all the files back onto the sdcard before booting up again?
Thanks!
Edit: I was either totally confused (most likely) or somehow I managed to fix my issue (less likely)...so I am ok now.

Internal Storage Mount
So I am having a similar issue.
I have an Evo 4g LTE running CM10 (cm-cfX-20120904-OFFICIAL-jewel)
I tried upgrading to the 11-13 build from get.cm site. I factory reset, wiped delvik, installed .zip from external sd card, installed gapps (gapps-jb-20121011-signed) wiped delvik again, rebooted, everything came up like it should, but I had no mobile data connection. All of my settings said unknown. So I rolled back to the (cm-cfX-20120904-OFFICIAL-jewel) build. Everything was working fine again, except I went open CWM v 5.8.3.5 from my app drawer and noticed message "you need sd card to run clockworkmod" so I went to sys settings > storage > internal storage (not mounted > mount storage and it attempts to read the data, but then does nothing. No error message or anything. I can't get my computer (windows 7) to read my internal storage so I can't format (which I have already done before)
I'm getting really frustrated as I have searched everywhere for the fix and have found nothing. If anyone has any idea I would greatly appreciate it.

Finally got around to spending a few hours on this yesterday to try to fix my 'missing' internal storage...
As suggested by nokiamodeln91 (cheers mate), I used Odin to go back to a stock ROM. Steps:
-Did a CWM backup of my current my current favourite ROM (I also used Titanium and SMS backup, but didn't need it in the end).
-Found an appropriate Samsung factory ROM. I went back to 2.3.6 as it's supposed to be safer. (For the n7000, make sure you choose an early one and not 'L' series or it's harder to root.)
-Used Odin to write the factory ROM. Note I only wrote the ROM, I didn't flash the modem, PIT, etc.
-Confirmed that I could see both my internal storage and my SD card (and also confirmed that a factory fresh install from Samsung looks and feels as ugly as I remembered).
-Used an 'update' hack to give me root.
-Installed CWM again.
-Simply restored my CWM backup of my favourite ROM...
In reality I went down several dead-ends... but I eventually got it all working again.

Guigsy said:
Finally got around to spending a few hours on this yesterday to try to fix my 'missing' internal storage...
As suggested by nokiamodeln91 (cheers mate), I used Odin to go back to a stock ROM. Steps:
-Did a CWM backup of my current my current favourite ROM (I also used Titanium and SMS backup, but didn't need it in the end).
-Found an appropriate Samsung factory ROM. I went back to 2.3.6 as it's supposed to be safer. (For the n7000, make sure you choose an early one and not 'L' series or it's harder to root.)
-Used Odin to write the factory ROM. Note I only wrote the ROM, I didn't flash the modem, PIT, etc.
-Confirmed that I could see both my internal storage and my SD card (and also confirmed that a factory fresh install from Samsung looks and feels as ugly as I remembered).
-Used an 'update' hack to give me root.
-Installed CWM again.
-Simply restored my CWM backup of my favourite ROM...
In reality I went down several dead-ends... but I eventually got it all working again.
Click to expand...
Click to collapse
Dude! you are insane...Got my S2 4.1.2 working, thanks to you.. tried for 3 days back to back until i stumbled on your solution.
Thanks so much.

A BIG Thanks to Guigsy & nokiamodeln91
Long story short is I broke the screen to my GNote 2 which is on its way to Samsung for repair (A little under US$200 round trip). When I removed the battery to get the emie number there was "goo" oozing out the back from the screen I suspect.
Anyway, turned on my GNote 1, which hasn't seen the light of day since last October and booted to discover that it wasn't working right. I tinkered for quite an embarrassingly long time to where I found myself in the same situation as others here. No write access to the internal storage on my CWM rooted GNote.
Although I had a nand backup, I ended up using ODIN to flash LT4 Germany, lost root as a result. went back in to Download mode and used ODIN to install PhilZ-cwm6-XXLT4-OXA-5.00.5.tar the exact same way, booted into CWM recovery and flashed PhilZ-cwm6-XXLT4-OXA-5.00.5-sigend.zip and was good to go. Issue definitely resolved.
I did not have root after installing the PhilZ-cwm6-XXLT4-OXA-5.00.5.tar via ODIN but I was able to enter CWM recovery where I then installed the ZIP version. As I had fixed my issues I was able to copy over the ZIP version to my Ext SD card B4 going into recovery mode (Yup, one of the symptoms for me was not being able to copy to the external SD card when the phone was connected to my PC either).
Rebooted signed in and was quickly synching my apps, settings etc. I would have felt comfortable using the nand backup I had originally but since this solution brought me up a few versions of Android, I just did a fresh setup.
Had it not been for XDA and our friends here, I would have formatted, factory reset and who knows what else trying to fix this.
Thanks much,
Claude H.

[Q] Jacked up Touchpad after attempting "internal storage" increase

I posted this on rootzwiki, but I'm hoping someone here will help guide me back.
I have CM9 installed, which was working great except that I kept having "not enough memory" errors when trying to install apps from the Market.
I went to the CM7 sdcard problem fixes thread, found here:
http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/
These fixes work for CM7 and 9, so there is no compatibility issue there.
I attempted to expand the data partition by 1gb by flashing the correct .zip. However, after waiting 1.5 hours, with no change in the screen, I was forced to reboot it. I don't think I was too mistaken for thinking otherwise. No error message was given.
Now:
1. It reboots into CM9 okay, except the "checking SDcard" sign is on forever. Thus no access to the SDCard.
2. It won't reboot into WebOS anymore. It stays at the hp icon. This is most concerning to me, because to me it implies that something more than then Android install is broken now.
3. In Clockwork Recovery, it won't allow me to restore! Selecting that option just freezes CWM. However, it will allow me to browse the sdcard contents when selecting "install from zip"
4. From CWM, I can mount USB access and see all contents of the SDCard.
5. I did some searching, and one post suggested removing fsck_msdos from system/bin. I did this, which allowed me to access the SDCard in CM9 as this circumvented the SDcard checking. This obviously is not the right solution, so I restored it.
Next steps please?
I've got backups so the data isn't so important.
I think the sdcard partitioning is wonky due to the aborted memory expansion attempt, so I'm not sure running ACMEuninstaller will fix that.
I'm thinking I attempt to run ACMEUninstaller first, followed by WebOSdoctor if it won't boot into WebOS?

Take a look at this guide : http://forum.xda-developers.com/showthread.php?t=1426244

Yup, ended up doing that and looks like it's doing well.
Basically jacked up the storage partition so badly there were an infinite # of errors. Because WebOS uses that same storage for some of its files, couldn't boot either.

I've had to do it 3 times already.
It's a big PITA, but it works....... If your partitions get fracked, I've found this to be the best option.

Can't mount internal SD Card after installing Albinoman887's 1/12/14 KitKat Rom

So I have installed several versions of this ROM since it began, however when I upgraded to 1-12-14, all went well except my internal SDcard will not be recognized. This means I can't use the camera or Titanium Backup, etc. However, I can see and use the external sd card w/o any issue. Upon every boot I get the icon saying that I need to format SDcard0, but it never completes, only soft reboots and the icon is gone until the next full reboot. I flashbooted boot.img twice after doing a FULL wipe. I have tried reinstalling 3 times doing FULL wipes every time, still get the same. When I boot into recovery and try to wipe SDcard, I get an error saying
can't mount /dev/block/mmcb1k0p36 (Invalid argument)
Error mounting /internal_sdcard/!
Skipping format
I have also just tried the new 1-15-14 build and get the same results. I have fastbooted the boot.img each time. Please help. I have installed many ROMs on this device before w/o ever an issue. What did I do wrong and how do I fix it? TIA!

Reboot recovery
Mount USB storage...
Plug phone into computer...
Let windows format corrupt partition...
Profit
Sent from my Vivid 4G using Tapatalk

Just putting another method which worked for me (one time issue and fix, so it's a crap-shoot). I don't have the luxury of connecting to a computer via usb for anything except charging.
-properly flash a sufficiently different ROM (I had kitkat, so I flashed ICS)
-start ROM up, check if fixed (mine was not)
IF NOT FIXED, CONTINUE
-mount the SD card in your recovery (mine is WCX recovery)
-reboot your phone into the ROM
This method worked for me. I saw in a different forum that when this happens it's usually because a file that describes the partitions gets corrupted and that because ICS and GB partition the SD cards and internal storage in a different way than Jellybean or Kitkat, that flashing a different ROM (if problem is on ICS/GB, then flash KK/JB, and vice versa) will force an overwrite of the file in question.
This is not as easy as rignfool's method, and once my charge port arrives in the post, I will abandon this method and use Windows to repair the partition like a sane person
Also, it seems like all my media on the internal storage has been wiped, but wutevr :/

Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/

Yuskow said:
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Click to expand...
Click to collapse
If this is directed at me, this happened after I installed the March 17th or 18th nightly (put a new one on every once and a while). And to be completely fair, I had accidentally selected factory reset in hboot (thought it was highlighting recovery, boy was I pissed).
The problem (or so I've read) with installing another kitkat/jellybean ROM is that the SD card is mounted the same (/storage/sdcard0, and external SD is only /storage/sdcard1) as opposed to ICS/GB (I only remember that you access external SD through /sdcard/ext_sdcard or something to that extent). Only when the SD cards will be mounted at differing locations will the system re-write the files specifying mount points.