yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] sombionix:
After doing some testing all morning, I believe we found what is causing the issue with the internal/external sdcard mounting which has plagued all Vibrant 2.2 roms. As many of you have seen, there have been a couple fixes posted. For some of you, after flashing the fixes, its resolved your issue. However, for some, its simply reversed the sdcard issue by either not showing the external sdcard at all, write protecting the sdcard, or limiting the amount of data that can be transferred.

Cause of the problem:

1. For starters, both of the leaked vold.config and vold.fstab files were written incorrectly. They were not corresponding with each other and also had missing information. This was causing the first set of issues from the first 2.2 rom.

2. After the first fix was posted, we noticed it simply reversed the sdcard mounts, and also limited the data to the ex-sdcard.

3. The second fix posted listed both sdcards, however write protected the ex-sdcard.

4. After further inspection last night, I followed the paths that the vold files were calling. Which are: sys/devices/platform/s3c-usbgadget/gadget/lun#

I noticed that in the directories, there was lun0 and lun1. The vold files were calling lun1 and lun2. I simply adjusted the vold files accordingly, flashed the fix and it worked! Both external drives displayed in the correct order, both as removable drives as they should.

I sent the fix to a team member, after flashing, his issue reversed, and he no longer could see the external drive, only the internal. I had him follow the vold paths like I did. Again, it is: sys/devices/platform/s3c-usbgadget/gadget/

His devices was calling lun0, lun1, and and extra file, lun2. I asked him what kernel he was running, and turns out he was running one of our experimental kernels that uses I9000 source code. I was using the stock Vibrant 2.2 kernel. After further examination, we found the the Vibrant kernel creates lun0 and lun1. I9000 sourced kernels creates lun0, lun1, and lun2. Therefore, the specific mounting fix is dependent upon which kernel you are using. That's why these fixes have been hit and miss for many of you. They have worked for many of you, while not working for other.

In short, the vibrant 2.2 kernel generates 2 lun files, lun0, lun1. The 2.2 kernels based off of I9000 source is generating 3 files, lun0, lun1, lun2. So, you have to have the correct vold files depending on which kernel you are using.

We've tested this back and fourth all morning and from what we can see, this is definitely the cause of the issue. Below, I've posted 2 flashable.zip files. One to flash if you are using a stock Vibrant 2.2 kernel. Another to flash if you are using a 2.2 kernel based off of the I9000 source. Please test and let me know if it works for you. So far its worked for all of us.

FLASH THIS IF YOU ARE USING A STOCK VIBRANT 2.2 KERNEL

FLASH THIS IF YOU ARE USING A 2.2 KERNEL BASED ON I9000 SOURCE
[Vibrant Android Development] go_l_den:
Awesome, great work som! Could this possibly have anything to do with the 1/20 internal SD whipes that have been occuring with your new lag fix kernel? Regardless, it'd be great to know where the team is on fixing that issue. Thanks,

Go_L_Den
[Vibrant Android Development] miikey_:
Is Onyx based on the stock Vibrant kernel or i9000 source kernel?
[Vibrant Android Development] sombionix:
No, the wiping issue has nothing to do with this fix. The wiping is kernel related as far as we can tell. Being that the ULF we did was the first port to the vibrant, it was very experimental and contains dragons.

Nonetheless, let me know how this fix goes for ya.
[Vibrant Android Development] sombionix:
If it doesn't say it has the ULF kernel, than yes, its the stock kernel.
[Vibrant Android Development] krylon360:
Here is how you can tell if you are based on Stock or i9k

When you boot up, do you just see a Vibrant logo and only a Vibrant logo until the bootanimation kicks in? if so, you are stock.

When you boot up do you see a Vibrant Logo, then a i9k Logo or the famous Team Whiskey Logo, then the bootanimation? if so, you are i9k based.
[Vibrant Android Development] moonfire711:
Thanks guys. This clears up the mystery I was having with the mount fix. I am not a dev and have done little coding in my day, but I was thinking this may have been the case after investigating the vold files. Great job tracking this down to keep us all happy and to keep your lunch money. :D
[Vibrant Android Development] Mr. Apocalypse:
so let me get this right before i **** this up cuz im a dumbass......

ONYX 4.2 is i9k based right....so i flash the one for i9000???
[Vibrant Android Development] amd_203:
It depends on the one you chose, as stated above. It you chose Onyx 4.2 with stock kernel then you choose the stock kernel one. If you got Onyx with the Universal Lagfix then you choose the i9000 version.
[Vibrant Android Development] miikey_:
ULF Onyx is i9000 based
[Vibrant Android Development] IMDVDfreak:
If I am using Asura 2.03 which one I have to use?
[Vibrant Android Development] noelarino:
I tried it on my unit. It did not work I still get the incorrect parameter message. Im using the unoficial 2.2 rom from eugene.
[Vibrant Android Development] oka1:
Awesome

Thanks for finding this excellent detective work..... :cool:
[Vibrant Android Development] beeroatsnp90x:
So is this fix supposed to fix the 2gb max ex-storage problem also? It did fix the mount issue and now both storages are detected however external still shows 2gb.
[Vibrant Android Development] blinksilver:
worked as advertised.
[Vibrant Android Development] Deleted member 2371530:
Mines showing up but only 2gb should I try the other one bayb?
[Vibrant Android Development] texasrocket:
I'm running axura 2.0.4 with a12 kernal. I used the i9000 fix and it looks like it fixed mine but it is adding a 3rd device. So I now have 'removable disk H: removable disk G: and cddrive F:' when I unplug the usb all 3 of those disappear. anyone else getting this?
[Vibrant Android Development] krylon360:
Thats because the i9k mounts a CDDRIVE for a media player.

It's normal with i9k kernels.

That is what LUN0 is on the i9k

LUN1 is Internal SD

LUN2 is External SD
[Vibrant Android Development] krylon360:
depends on the kernel. if you see a i9k logo, or any other logo besides the vibrant logo, you will need the I9K mount fix.
[Vibrant Android Development] texasrocket:
alright thinks for clearing that up.
[Vibrant Android Development] :
Mines is a vibrant logo then it says android so which is mine?
[Vibrant Android Development] roguespy0:
Worked for me. Thanks for all of your hard work.
[Vibrant Android Development] roguespy0:
I have the Vibrant Logo and I used the first one that says for all 2.2 Vibrant kernals and it worked.
[Vibrant Android Development] jdarzi:
Macnut R12 - A12 Kernel. No go. :(
[Vibrant Android Development] Icedorb217:
Thanks worked like a charm after figuring out what my computer was doing wrong!
[Vibrant Android Development] TJD319:
I updated to the first JK2 release and applied eugene's sd fix. Never once did I have an issue with SD mounting but Im all about making my phone perfect so I applied regardless and still running great.

Thanks for your work man!
[Vibrant Android Development] mikey98277:
Works great on Macnut R12 with the stock Kernal that was put out a few days ago for it.
[Vibrant Android Development] ScratchSF:
@Sombionix - Thanks for doing the research to nail down the root cause of the problem. Also, I don't know if this is real or imagined, but it seems like my phone is snappier since I flashed the update. Not seeing a change in Quadrant scores (which I know don't amount to much). But it does seem like certain UI screens render much faster than before I applied the fix. Wondering if you made other changes that might have resulted in a performance improvement?

Thanks again!
[Vibrant Android Development] sl0play:
Thank You Sombionix! I bet their still trying to figure that out at T-Mobile :D
[Vibrant Android Development] Stromkern:
Hi, could someone put some mirrors please? Or what can I do to download this file from Team Whiskey's page? Every time that I try to download any file from their page I always have the same error that say "Not file found" or that the page doesn't exist anymore, thanks in advance for your help, sorry for my bad english too.
[Vibrant Android Development] sl0play:
http://www.mediafire.com/?zs50nf3z68hqce3 i9k

http://www.mediafire.com/?cpdgqs5fmmq1lhf stock
[Vibrant Android Development] :
But I flashed his stock kernel he posted which do I put lol I'm so confused
[Vibrant Android Development] sl0play:
Flip a coin dog! I'll bet your 2:1 its heads!
[Vibrant Android Development] :
Lol did that already bro and I flashed the stock one but now my sd card reads but it's only reading like 2gb when I really have a 8gb
[Vibrant Android Development] Mr. Apocalypse:
ok...just wanted to make sure.....thanks som....it works as stated..now have read/write access in the external sd card...but is there still supposed to be the "CD Drive mounted on my PC?
[Vibrant Android Development] :
Help Me ! With my post above
[Vibrant Android Development] mr2t32:
Both links to i9k.
[Vibrant Android Development] bobbbb:
I have the AOSP 2.2 unofficial ROM that's also on this site, so which one do i download?
[Vibrant Android Development] stolen_pillow:
The external sd mounts again but the internal is still a no go. At least it doesn't cause my mac to flip out like before. For a while whenever I tried to unmount the external card it would cause both processor cores to run at or near full capacity until I had to do a hard reset. That doesn't happen anymore. I'll try it out on Win7 later today and see whats up with that. For now I just use an sd adapter to do transfers and move the files with ES file explorer.

BTW, just wanted to say thanks for all your hard work. I'm using Onyx 4.2 with all the crazy goodies and it works great. I did have to Odin back to stock once, but it was my own damn fault for not paying close enough attention. Thanks again!
[Vibrant Android Development] bobbbb:
Finally got this to work, had to download via the browser for my phone, then install via cwm. It changed my M drive to G, and gave me some wierd K drive that has files like lost.dir and android.secure, not sure what these are, but the fix worked otherwise!

Thanks for your hard work!
[Vibrant Android Development] Ashex1:
Excellent detective work!

I have the reversed mount points and interestingly I like it that way since I usually only access the internal memory. If I want to preserve this how would I need to modify the conf files in the zip? I don't think switching the lun pointers will do the trick.
[Vibrant Android Development] rbtady:
Thank you for this :) I used the stock for the AOSPish rom. I can see the internal SD, but if I try to open anything on the external SD it the device is not ready and not accessible. I haven't been able to open any file from my external SD card since I've tried froyo roms.
[Vibrant Android Development] tsiah:
Do we flash from ROM manager inside android or from recovery?
[Vibrant Android Development] Mr. Apocalypse:
flash from recovery....
[Vibrant Android Development] tsiah:
Kinda what I figured. There's the option to apply update from SD through clockwork though so I thought ...maybe ;)
[Vibrant Android Development] Stromkern:
Hi thank you so much for the links but both are for the i9K version and I need the stock files, thanks again for your help.
[Vibrant Android Development] sl0play:
Doh!

Fixed :)
[Vibrant Android Development] Sonnislav:
Thanks for this awesome fix!
[Vibrant Android Development] dougstoner:
So, might be having a noob moment here...but, when I boot into clockwork recovery, and try to install zip from sd card, I get an error "failed to mount sd card". If I can't mount my sd card, how to I install a zip from there?
[Vibrant Android Development] mr2t32:
with the recent sd mounting fix, the external is still only showing up as 2.2 in disk management. Everywhere else it shows the correct size. Not sure what you did with the ULF kernel and the fix for it, but that had fixed the issue 100%. When i tried out ULF w/ the mount fix, it showed the correct size in disk management. Other than that, everything is mounting fine and working.
[Vibrant Android Development] Icedorb217:
Does the fix stop working if your battery full shuts down?
[Vibrant Android Development] luvbug1977:
Worked well for me! Thank you all for your hard work.
[Vibrant Android Development] sl0play:
Be sure you unplugged your USB cable first. Also you need to copy the file to your internal SD card. You cant flash from external.
[Vibrant Android Development] smartmind:
Firstly , thanks for your marvellous work!

Secondly, I have a few questions to ask:

1. I am using Eugene's unofficial rom with a SD fix, can I use the stock rom fix one?

2. I have done one click lagfix, shall I remove the OCLF and then flash the fix?

3. Shall I use clockrecovery or the original recovery to flash the fix?
[Vibrant Android Development] Janis:
I lost my icons that I have referenced in an ini file for both my drives, but the PC reads contents and seems to mount just fine. The phone, though, doesn't read the contents of either of two external cards I've put in it. It gets the size right, Root Explorer tells me how much space is actually used and left, as it would if I could see the files & folders, but it looks empty.

I may be having a related problem, I might just be on the shallow end of the bell curve, or I may just be making this up, but I'm having a 10%/hr battery drain, and the culprit in SystemPanel appears to be kswapd0 (page referencing something or other). Voodoo issue? I always disabled before flashing, I think once I forgot if I did it, and I did it twice. But it might not be, and I thought it might just be helpful to post it here.

If you want the whole story

It was suggested I try OCLF, I plan on that.

I'm also getting to have more patience with noobs. It really does take a chunk of time & effort to get up to speed on some of this stuff.
[Vibrant Android Development] jakill:
Aosp 1.1

i have the AOSP 1.1 Froyo Rom and I wanted to know wheich one of the two sd fix should i put on the phone i have not changed the kernal.
[Vibrant Android Development] baillou2:
Is this supposed to work for Axura 2.3? Because I flashed the zip file and I'm still having the same problems. The external sd shows as 2.4 gb when in fact is should be 16 gigs, and when I transfer large files they don't show up, and they also seem to erase other files in the process.

Thanks for any help.
[Vibrant Android Development] mulcahyd:
Your bootscreen will help you determine. Ok.
[Vibrant Android Development] frankencat:
It works as far as mounting on my PC but now I can't mount the internal storage on my car stereo. I usually mount the drive and play .mp3's off the phone through my stereo via usb. Not a biggie but I would like it to work like it did with 2.1 ROMS. :)
[Vibrant Android Development] epakrat75:
Here's some potentially daft questions...

I've been running STOCK ODIN TMO JK2 for a while now. Never have had a problem mounting either internal or external SD on a computer. Reading and writing have been fine.

I don't seem to have been plagued by this. How can I manifest this behavior to verify whether it needs to be patched? Should I just ignore this fix? If ain't broken, don't fix it?

Thanks! :D
[Vibrant Android Development] frankencat:
Indeed.

.....
[Vibrant Android Development] kponti:
Worked like a charm for me! thanks a lot!
[Vibrant Android Development] baillou2:
UPDATE:

Now, all of a sudden, the sd card DOES mount, it even shows the correct size and everything. This is after having flashed the zip/and rebooting about a day ago.

BUT when I try to transfer files to the external sd card I get error messages saying there was a "problem creating "***" directory, input/output error". And after disconnecting from the computer, the external sd reads as empty. All of my 1000 songs are gone.

What is going on?
[Vibrant Android Development] baillou2:
NEW UPDATE: I think I got it working. I had to reformat the microsd (FAT), put it in the phone and rebooted. Now it seems to read fine. Still messing with it to make sure.

But maybe reformatting the file system is the key!

NOPE: Same problem as before. When I transfer files onto the external sd it erases others that are already there. What's interesting is that it puts them all in a directory called. LOST.DIR. I never created this directory and it seems to be full of everything that I put on the card except now the files are all renamed as random numbers.

NEW UPDATE: So the best thing I can do to work around this is to reformat the external sd in ext4. This seems to make the filesystem stable at least. But it won't mount when connected to my computer (I run linux so it shouldn't be a problem). But at least I can transfer files to the internal then from the internal to the external. Bit of a pain, but it's all I can do.
[Vibrant Android Development] lphillips80:
I have obsidian V3 and I flashed the mounting fix stock kernel and says it installed I then rebooted and went back into recovery and i still cannot install from ext sd. this is getting very frustrating. Any help will be greatly appreciated.
[Vibrant Android Development] krylon360:
We have NEVER been able to flash anything from Ext-SD in CWM. It's always been Internal.

Not really sure what this issue is here.
[Vibrant Android Development] smartmind:
Anyone could help me with my quetions? Any help will be appreciated!!

Secondly, I have a few questions to ask:

1. I am using Eugene's unofficial rom with a SD fix, can I use the stock rom fix one?

2. I have done one click lagfix, shall I remove the OCLF and then flash the fix?

3. Shall I use clockrecovery or the original recovery to flash the fix?
[Vibrant Android Development] tsiah:
When flashing a new rom, (Axura 2.0.4 to 2.0.5) does this fix need to be flashed again?
[Vibrant Android Development] jay661972:
I used the stock kernel and still showing bad parameter. Do i need to reboot this twice? I'm using Obsidian V4.2 with Black theme froyo. Thanks
[Vibrant Android Development] Deezy88:
i have tried everything and this sd card error perameter incorrect 0x80070057

i have tried everything and this sd card error perameter incorrect 0x80070057 keep happending

and i flash the fix and i still get the ext sd thing,can some one plz help me
[Vibrant Android Development] Reyland:
Axura 2.0.5 already includes the fix!!
[Vibrant Android Development] tsiah:
NVM.... I just read the change log for 2.0.5. This fix is included :D

lol :p I just noticed.
[Vibrant Android Development] baillou2:
Not for me it doesn't :(

UPDATE: Actually I think it seems to be working well. It still shows as 2.4 GB when it's actually 16 GB, and the first time I transfered some files to test it I got a message that said "transferring files to sd card, please wait" or something like that, and nothing happened. No files once I checked through the phone. But after that it seems to work fine.
[Vibrant Android Development] kurts220:
I am using Obsidian v5 BETA with stock kernal. After flashing the stock kernal fix, I can traverse into about half my directories on the ext SD card (directories that begin with the letters 'A' thru 'M'). When trying to access directories that start with 'N' thru 'Z' I get the invalid parameter error. Any thoughts?
[Vibrant Android Development] baillou2:
I have no idea personally. I'm having similar trouble. My directories disappear whenever I add new files via usb. So a temporary way around is to just transfer stuff onto your internal sd and then from there to the external with astro or root explorer. The important thing is to NEVER access the external sd when you plug your phone into your computer. In fact I immediately unmount it.

It's not a fix but it helps.
[Vibrant Android Development] kboater:
i saw someone earlier in this thread with the same problem, but it never got answered.

I cant flash this in clockwork recovery because it says it cant mount when trying to choose zip from SD (internal)

so I am trying to use this to fix my problem (i cant flash anything in clockwork recovery) because it says it cant mount when i try to choose a file to install.) so this fix wont work for the same reason, when I put it on my internal (by using Astro to copy from external) in clockwork i cant choose a file to install....

EDIT:

never mind. fixed.
[Vibrant Android Development] serendipityguy:
I have the same rom, neither works.

If you flash the stock vibrant fix, it will do nothing, can see the correct sizes, but you cant copies files to external card.

If you use the i9000 fix, it will not help either. After flash, you will not see the external card (thinking all of your files are toasted)!

So you flash back the stock vibrant fix, and you are able to see the external card, but you still can not copies files over to external card (at least you can view your files again :confused:)
[Vibrant Android Development] Deezy88:
me too,i haven't got no help what so ever,for something so easy,still not working for us,i have send stuff through a usb reader
[Vibrant Android Development] slycon:
Can you post how you fixed this?
[Vibrant Android Development] Deezy88:
he did on page 1,but its not working for everybody.it not working for me and i tried so much times...im about buy a usb reader,this is crazy.some one plz help us out throughly on how to fix this.
[Vibrant Android Development] genaropr:
thank you soo much
[Vibrant Android Development] Lithium98:
Applied the fix and it's mounting just fine. The only issue I'm having is when any media on my sd card that I play finishes playing, the player (video and music) freeze up. Any thoughts?
[Vibrant Android Development] striperskipper:
I'm running obsidian 4.2 with a stock kernel on my vibrant. When I try to flash the mounting_fix_vibrant22.zip i get this message "e:can't open /sdcard/mounting_fix_vibrant22.zip(bad). Any ideas. I searched the thread on the error but it turned up nothing.
[Vibrant Android Development] eweo911:
Try re-downloading it. You may have a corrupted file.
[Vibrant Android Development] jdub1911:
Worked perfect on my obsidian v4.2 w/stock kernel.

I had the problem where it couldn't find the file, what i did was mount to my pc, put the fix zip on my external sd, internal sd (where my obsidian zip is), and one in the main folder where my update zip is. Then of course make sure to install zip from sd card and it finally found it, though i'm not sure which one exactly. I'm sure someone can clarify which folder it needs to be in.
[Vibrant Android Development] jdub1911:
duplicate post
[Vibrant Android Development] Bandage:
Ok, I know this has been covered in various iterations...but haven't found an answer for this exact issue, so apologies for the rehashing if solved.

Am running Onyx 4.2 Stock...no lag fixes, etc.

When dragging files from Win7 to external SD card (with phone connected to PC) I get this error = Error 0x80070057 : The parameter is incorrect.

I did install the SD card fix (for stock).

What's bizarre is that I can move files on phone from internal to external no problem (move from internal folder to external folder using the standard Vibrant File Manager App). Only issue is trying to load files to external SD from Windows.

UPDATE: looks like it's the same problem as others...shows as 2.2Gb instead of 16GB, but only when the card is in the phone. I removed it, popped it in card reader for my pc, and shows correct size. Gonna do a full reformat and see what happens.
[Vibrant Android Development] striperskipper:
I can find the file fine and downloaded it twice. still the same error.
[Vibrant Android Development] crxforya:
I read all 9 pages and only saw one post about incorrect parameter error codes. I am able to view both drives as removable drives however I can only transfer files from cpu to internal. External keeps telling me incorrect parameter. Have I fried the external sd card, or is this issue related to the problems w/ mounting on the 2.2 roms?

Thanks for help
[Vibrant Android Development] crxforya:
Let me know how this goes for you. Did not work for me??