Database Info

OOPS, my sd card is messed up

Ok, so i tried out that apps-to-sd script that is on the other thread on here, you know, the one that doesnt require a pc, just the script
well im pretty sure its my fault since others have had success, but as soon as i finished the script, my phones apps all force closed, so i rebooted the g1 and got stuck on flashing android, wiped, got everything back together the way it was before partitioning the card using the script, and now im here
by the way, im using a different sd card from what was in it when i ran the script, its a 4gb class 6, the one im using now is a 2gb class 2
the reason for this is because (here is why i think i messed up) when viewing the sd card from my computer, it shows my used mb's as being 109mb, and available 0mb. now its 109 because i can still use the browser to download files (downloaded jf1.42 from the browser, and used linda file manager to rename it to update.zip when i was trying to find a work around from having to do the wipe)
and paragon has been hanging up on me when trying to get it to start up, could be my ****ty dell, who knows
so now my only problem is, i cant use my class 6 4gb card, and i backed up 3.5gb's of stuff off of it (which definately isnt fitting on a 2gb, let alone its a class 2).
i plan on buying a larger sd card (btw, while your here, care to tell me the largest sd card the g1 can handle? 16gb ok?) but untill then, i really want to use my 4gb, let alone i dont want to toss a 4gb mini sd
any help is definately suggested, and yes, i know whatever mistake i made, is more than likely a noob mistake, hence the "OOPS" in the title, lol
gtalk [email protected] if needed, i get email updates instantly for this thread, thanks in advance

I would repartition/format the card. Then once you are done, use a linux live cd to shrink the partition and add the ext2 partition to it (thats how I have done all of mine).

Darkrift said:
I would repartition/format the card. Then once you are done, use a linux live cd to shrink the partition and add the ext2 partition to it (thats how I have done all of mine).
Click to expand...
Click to collapse
ok before i go into the linux live cd, how do i repartition/format the card? i tried right clicking the drive in my computer and hitting format, but it hangs now wheras it didnt before

go to administrative tools and in there computer management. you will see disk management in there. remove the partition, create a new one (it might let you create it and leave some space, if so, do this, if not, use the full space). once you are done, use linux (gparted worked for me under kubuntu) to resize (if you used full space) and create a second partition (linux, ext2). Windows is best at creating windows partitions, and linux is best at creating linux partitions (go figure) so this is the best (if not longest) solution. you *CAN* try to save some time and do it all in linux, but I find the extra time might save you some headache.

well, now im still stuck, could be my crappy dell, but its all i got at the moment
im in computer management, clicked disk management, and its stuck on "Loading Disk Configuration Information..."
soooo what now? lol

Well, try opening the live cd, remove all partitions, create a windows partition, then try computer management again. Maybe the partition table is corrupted (linux can handle and fix this better). If so, creating a new partition using linux will fix that, then you can go back to windows, delete/remake partition and then go back to linux to create the second partition. I know its a lot of steps, but I really do see better results using windows to create fat and linux to create ext2 file systems.

do i have to run linux off of a cd? and where is the best place to download this

wootroot said:
do i have to run linux off of a cd? and where is the best place to download this
Click to expand...
Click to collapse
http://tinyurl.com/cxenjl

LucidREM said:
http://tinyurl.com/cxenjl
Click to expand...
Click to collapse
ok let me be a little more specific
i understand i need linux
i understand where to find linux, many different forms of linux
this android phone is the closest thing ive ever come to using linux, and i dont know the difference between them
is there a specific version i need?
will DSL do the trick?
where do i go in linux once im running it?
do i have to boot linux like i do windows, or can i just run it from the desktop like i can DSM?
but thanks for the link to google
EDIT: The reason i ask about DSL is because i already have that and can run it from my computer off the desktop, i think its through a emulator, not sure, i only tinkered around with it for a few minutes a couple months ago, but i know i still have it on here, so if you can do this through DSM, and can give me a noob-tutorial to do this, thats great, else point me towards which linux i need
nvm i found help on another forum

wootroot said:
so now my only problem is, i cant use my class 6 4gb card
Click to expand...
Click to collapse
Don't feel bad, I messed up and did the same thing with my 8GB.
I finally got Vista (after a long hang) to recognize it via a USB SD adapter and right-clicked to Format. (Don't try and open it, it'll hang more)
It only said the volume was 6GB but at least the phone recognized it again.
I flashed back to Haykuro's 4.5 build and did the Format SD card from the settings and it recognizes a full 8GB again. Hope it works for you.

2JRo said:
Don't feel bad, I messed up and did the same thing with my 8GB.
I finally got Vista (after a long hang) to recognize it via a USB SD adapter and right-clicked to Format. (Don't try and open it, it'll hang more)
It only said the volume was 6GB but at least the phone recognized it again.
I flashed back to Haykuro's 4.5 build and did the Format SD card from the settings and it recognizes a full 8GB again. Hope it works for you.
Click to expand...
Click to collapse
well i try to do that, and it formats it, but only formats 109mb in fat or ntfs only, wont do fat32
even after i format, even to ntfs, it wont see anymore than the 109
i recently attempted to do a apps to sd card using the script with a 2gb class 6 and that card only has just shy of 4 mbs, out of 2gbs, that can be seen/formatted, also only to ntfs and fat
how did you get it back up to 8gb?
it also doesnt help that my crappy dell is overheating every 10 minutes or so, i was so desperate to get my phone unbricked that when i was downloading the update.zip files i actually put my laptop in the freezer when i was using it and just left the door open lol
any suggestions just throw them here or catch me on gtalk [email protected], ill be on all night on my phone, but im tired of using my laptop on the freezer lol, if anyone posts up here, give me time to get back on here from my phone and reply. thanks in advance
screenshot of my 2gb
{
"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"
}

To get back to 8GB I flashed back to Haykuro's 4.5 build using my other SD.
In the settings it will give you the option to format card from the phone
after unmounting. That restored it to full 8GB.

2JRo said:
To get back to 8GB I flashed back to Haykuro's 4.5 build using my other SD.
In the settings it will give you the option to format card from the phone
after unmounting. That restored it to full 8GB.
Click to expand...
Click to collapse
to make things easy for me since im now just using my phone, can you give me a direct link to the rom? ill download it and rename it using filemanager and flash it
btw, will this wipe out my apps going to this haykura build? because after semi-bricking my phone so many times im tired of re-installing apps lol

http://code.google.com/p/sapphire-port-dream/
am i looking for build4.5-sdcard-signed or build4.5-signed
am i even looking at the right stuff? lol

Just do 4.5_signed, just make sure and Alt+W wipe before install. You'll have to go back to JF.ADP to retry the SDscript anyways. The 4.5_sdcard_signed is for when you already have Apps on SD.
I'm sure there's an easier way, but I have not found any way to format SD from phone aside from this.

if i decided to give up on apps to sd, but wanted to fix my sd card, is this 4.5 stable enough for daily use? ive read some of his blog, and i see he has 5.0, i guess this is all confusing to me since all ive known about so far is JF's stuff, i tried flashing 4.5 and i got the flashing android, im going to try to reflash and see if that fixes it

ok so i cant seem to get any of the builds to work, i tried 4.5, 4.9, 5.0, and 5.1, and each version of each one, and the furthest i get is a flashing android, except for on the 5.0 i get a cool noise, and a HTC Icon in the center of my screen, i guess this is the equivalent of the flashing android for 5.0, could be wrong
do i have to do a full wipe before using these? because i had jf 1.42 rc33 and flashed 4.5, and then 4.9, and then 5.0, then....wait...damn...while typing this and letting 5.0 sit for about 6 minutes it went to the login screen for the g1 (registration), guess im redownloading all my apps now... any reason not to keep 5.0? since its the only one i could get to work so far?

[HOWTO] Repartitioning Your SD Card with GParted Using Ubuntu

XDA user supremeteam256 has written an excellent tutorial on How to Partition SD Card with Ubuntu for Dummies. After reading the tutorial, I asked whether it was possible to repartition an SD card using GParted in Ubuntu without losing any existing data on my ext2 or fat32 partitions (I was not, however, as concerned with my fat32 because it is easily backed up). My goal was to add a linux-swap partition after my existing ext2 partition. Specifically, I wanted to steal 64MB from my ext2 partition and reallocate it to a newly created linux-swap. So, I decided to be the guinea pig and risk losing my data for a greater cause. Well, I didn't end up losing data on either of my partition on either of my phones. I have successfully done this three times--on two G1s and a myTouch.
WARNING: While this worked for me it may not work for you. I am NOT responsible for any and all loss of data that might occur from this process. Proceed at your own risk and ALWAYS back up your SD card before trying this.
Prerequisites
I HIGHLY recommend you first read the tutorial mentioned at the beginning of this post so that you are familiar with installing Ubuntu and using GParted. This tutorial assumes that you have a working version of Ubuntu (I am using version 9.04) on your machine.
Ubuntu
SD Card
Card Reader
Step 1
Open up GParted by clicking System > Administration > Partition Editor. From the drop down menu on the top right-hand side of the GParted screen, selected your SD card. Make sure you select your SD card and NOT your hard drive. You are on your own if you make a mistake here. For this example, I am using a 2GB SD card. Yours may differ so proceed accordingly.
{
"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"
}
Figure 1: Selecting Your SD Card
Step 2
Once your SD card is selected, right click on each partition and select "Unmount" from the list.
Figure 2: Unmounting Each Partition
Step 3
Once you have unmounted each partition, right click on the ext2/3/4 partition on select "Resize/Move" from the list.
Figure 3: Resizing the ext2 Partition
Step 4
In the dialog box that opens, subtract the number of MB from using the down arrow button on the "New Size (MiB)" box. I would like a 64MB linux-swap partition. My SD card is 500MB (Figure 4) so I will click the down button until the "Free Space Following (MiB)" box reads 64 (Figure 5). An important step is to make sure that the box that reads "Round to cylinders" is UNchecked. This is so there is not partition in between the ext2/3//4 partition and the linux-swap since they must be in order (fat32, ext2/3/4, linux-swap). Once you have resized your partition tot he desired amount, click "Resize/Move."
Figure 4: Resize Dialog Box at 500MB
Figure 5: Resize Dialog Box Resized
Step 5
Next, create the linux-swap partition by right-clicking on the unallocated space that you have just taken from your ext2/3/4 partition and select "New" from the list.
Figure 6: Creating a New Partition
Step 6
The dialog box that opens will be similar to the resize dialog box you used in Step 4. In the "New Size (MiB)" box, enter the number of MB you would like your linux-swap partition to be. Then, select "linux-swap" from the "File System" drop-down menu. Make sure that "Primary Partition" is selected from the "Create as" menu. Again, make sure the "Round to cylinders" box is UNchecked. Once done, click "Add."
Figure 7: Selecting the Size of your New Partition
Step 7
Back in the main GParted screen, click "Apply" from the toolbar to apply the changes.
Figure 8: Applying the Changes
Step 8
When asked if you wish to continue, confirm your changes by clicking "Apply."
Figure 9: Confirm Your Changes
Figure 10: Watch Your Progress
Step 9
You should end up with something similar to what you see in Figure 10.
Figure 11: The Result
If you have any questions regarding this process, feel free to post them here. I don't know how much help I'll be as this is not my expertise but I'll do my best to answer what I can. I have learned, however, that there is always someone on the board who seems to have an answer for most questions. So ask away.

Reserved
Reserved for possible future use.

aaronratner said:
Reserved for possible future use.
Click to expand...
Click to collapse
yo, thanks alot bro. i was trying to figure out how to resize my linux swap. i already have a 32 mb linux swap. so, would it be better to delete the linux-swap and do the steps you did or do you just recommend me resizing my linux-swap. currently i have an 8gb class 6 transcend sd card. i currently have about 6.62gb fat32, about 1000mb (if i remember correctly) for my ext3, and 32mb for my linux-swap. thanks

I would--and this is more opinion that previous knowledge or expertise, delete the linux-swap--resize the ext3 and re-create the linux-swap. However, I don't think it would really make a difference which way you go. They are both essentially the same thing. Remember, there is a chance of data loss, particularly if your ext3 partition is full (the free space would have to come from somewhere). I have, however, successfully done this twice, both on a G1 and a myTouch. Hope it works and report back results if you try it.
EDIT: Did it a third time to another G1.

ubuntu and gparted
Ok, dl'ed the iso, burnt it, loaded into live cd, got my 4gb sdcard in the reader, started gparted and tried to follow along with superteam256's partition instructions for dummies (found here : http://forum.xda-developers.com/showthread.php?t=535914. The fat 32 partition gets "created" fine, but when I try to add a second, it gives me an error saying only one can be "primary" and that I have to create an extended partition even if that means removing the primary. So I tried to create just an extended, using the whole card, and then logicals afterwards, which didn't work. I tried to create the ext2/3 (not primary) and add the fat32 after, still gives me the same error.
*EDIT: When the first primary partition is created, it does not give me anything but "New" when I right click so I can't even tell it this one will be "extended".
On a side note, I have tried adb, but for some reason after the frist 2 commands it stops working and I have to reboot, unplug my phone, and then it works...for another 2 commands. I really want to run hero on my rooted mt3g US 32B. So far the only ROM I have been able to load is some weird hacked version of the original OS (it's cool, but I wanna try HERO!!)
Anyone got some commandline (linux preferrably) directions on creating the sdcard partitions and filesystems?
Thanks!

I partioned my 8GB SD with gparted, and apps2SD is working now. But everything is moving to main FAT32 partion. How can I access or use other 3 partitions (ext3, linux-swap, fat32 at end). Any help

ykhehra1 said:
I partioned my 8GB SD with gparted, and apps2SD is working now. But everything is moving to main FAT32 partion. How can I access or use other 3 partitions (ext3, linux-swap, fat32 at end). Any help
Click to expand...
Click to collapse
Access it how? Through the phone? PC? Only the fat32 shows up in Windows and in non-root file explorers on the device. The files on the ext partition are usually located in /system/sd depending on the ROM. This can only be accessed via linux using a root explorer on the device, terminal emulator or ADB.

rmarquez1974 said:
Ok, dl'ed the iso, burnt it, loaded into live cd, got my 4gb sdcard in the reader, started gparted and tried to follow along with superteam256's partition instructions for dummies (found here : http://forum.xda-developers.com/showthread.php?t=535914. The fat 32 partition gets "created" fine, but when I try to add a second, it gives me an error saying only one can be "primary" and that I have to create an extended partition even if that means removing the primary. So I tried to create just an extended, using the whole card, and then logicals afterwards, which didn't work. I tried to create the ext2/3 (not primary) and add the fat32 after, still gives me the same error.
*EDIT: When the first primary partition is created, it does not give me anything but "New" when I right click so I can't even tell it this one will be "extended".
On a side note, I have tried adb, but for some reason after the frist 2 commands it stops working and I have to reboot, unplug my phone, and then it works...for another 2 commands. I really want to run hero on my rooted mt3g US 32B. So far the only ROM I have been able to load is some weird hacked version of the original OS (it's cool, but I wanna try HERO!!)
Anyone got some commandline (linux preferrably) directions on creating the sdcard partitions and filesystems?
Thanks!
Click to expand...
Click to collapse
use the command: fdisk
for instructions how to use fdisk
type fdisk --help(or fdisk -help or something)
or man fdisk

Excellent tutorial. Unfortunately, it doesn't work for me. My SD card is already partioned using ROM Manager / Clockwork Recovery. I currently have 15 GB FAT32 and 1 GB ext2 (I guess).
Running Ubuntu 10.10, I've connected the phone via USB and I can access the FAT 32 partition via Nautilus/Explorer.
Using GParted, I can only see 15 GB of unallocated space (as /dev/sdb). The FAT 32 is not recognized as such and the 2nd partition doesn't even show.
Using the Ubuntu Disk Utility, /dev/sdb is reported as 15 GB on HTC Android Phone but unpartioned.
Any idea of how to proceed without wiping everything and with working on the whole 16 GB?

Formatting SD to FAT32 (need help) =[

I been trying to format my sdhc 4gig, the problem is i'll right click format and it gives me a window stating that i have to enter a disk in the F: drive. . .
Basically I took it step by step.
a. plug in the usb from my comp to my phone
b. mount the phone through the notifications tab
c. navigate to "My Computer" and find the removable disk drive right click and format then i will get the message "there is no disk in the (F drive please insert a disk and try again)
I honestly don't know whats going wrong here
can it be the recent update of android 1.5 to 1.6 the "BIG" transition from cupcake to -_- failnut lol. . . .
So what have done wrong?
Is there a solution to this mess?
and yes I did use the search button. . . .

Google 'Flash Format' (by cnetx). Download the demo, install on your pda, and format that way. Trust me, it'll work. If you like it, buy it.

Farmer Ted said:
Google 'Flash Format' (by cnetx). Download the demo, install on your pda, and format that way. Trust me, it'll work. If you like it, buy it.
Click to expand...
Click to collapse
Well that didn't work. Downloaded what was necessary, connected my phone to the pc. Now it's just stating that the phone has to be connected with the pc even though it is. . .

how about formatting it using a card reader? not from your plugged phone.

TheRem said:
how about formatting it using a card reader? not from your plugged phone.
Click to expand...
Click to collapse
Well im trying to find possible ways to do it w/o having to spend money lol.
On the other hand i do have a laptop, it has a card reader but the thing is. . . is that it crashed over a year ago and won't accept the original OS system so i have to use a cracked version. Leading to a problem where i can't use the built in card reader. Which doesn't sound so fun.
If there is any other alternate ways of avoiding a card read and being able to do it with my phone would be awesome, but i can try and find a card reader in the mean time.
Thank you guys for helping. If you have more possible ways please feel free to post more.

try this freeware...
nueStorageManager:
http://www.nuerom.com/BlogEngine/page/nueStorageManager.aspx
nueStorageManager is a control panel applet that lets you control and fine tune storage on your device. It enables you to format, defragment and scan storage on your device, as well as mount and unmount devices.
Warning: Formatting partitions will cause you to lose all device on that partition. Windows CE will prevent you from modifying operating system partitions (IMGFS, XIP) from this tool, but you can still manipulate the FAT32 storage partition with the tool.

lol nothing again.
It's ok i guess lol.
i didn't see that you edited i shall try this one out. thanx for the help again.
lol i just give up. . . until i get a reader.

Imok said:
Well that didn't work. Downloaded what was necessary, connected my phone to the pc. Now it's just stating that the phone has to be connected with the pc even though it is. . .
Click to expand...
Click to collapse
You need to establish an active sync connection, but if you can't get it working try this: go to the C:\Program Files\Microsoft ActiveSync\CNetX\Flash Format folder on your pc. Copy the 'F4.PPCARM.CAB' cab to your ppc and install it the normal way.

[Q] How to mount SD card for ClockworkMod recovery?

I rooted my TF this morning following androidroot.mobi instructions. Initially I installed the V5 blob and everything worked except bluetooth. I could have sworn I had the updated firmware but when I checked after the rooting process I found that I have 8.2.2.6.1-20110325. So I decided to update to the official 8.2.3.9 version.
I followed ASUS' instructions and got the triangle to notify me of the update. When the TF rebooted I got into CWM recovery and didn't know what to do so I simply rebooted again. Everything was just like before. I decided to try it again but I can't access CWM recovery anymore and the triangle doesn't show up when I insert the SD card (it works on another TF). I can't install CWM recovery from the ROM Manager app either since the TF is not listed.
Then I installed the blob V4 to at least regain BT functionality and it worked. However, I still can't access recovery. Does anyone have any suggestion?
Thanks!!!
EDIT: I can enter CWM recovery now but I can't mount the SD card. The internal memory also seems inaccessible
{
"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"
}

if you have clockwork recovery flashed, to access it... turn off the tf... hold the volume down button and power on... a script should show up on the top left... hit the volume up button and clockwork should boot
hope that helps

That got me into recovery but I can't access the µSD card Copied the Prime! ROM to the SDCARD folder in the eMMC and trying it this way.
EDIT: No luck... still saying "Can't mount /sdcard" Any other suggestions?

Solution found!
The solution was to use a different SD card. There have been similar reports in the Development Threads. So for people coming here through the search function: Try a different SD card or use another Android device to format the one that's not working and try again. Don't give up

funnycreature said:
The solution was to use a different SD card. There have been similar reports in the Development Threads. So for people coming here through the search function: Try a different SD card or use another Android device to format the one that's not working and try again. Don't give up
Click to expand...
Click to collapse
So you're able to access the sdcard from the doc? I can get the microsd card no problem and when I'm booted I can see the sdcard in the mmc/sd/sdhc slot but in cwm I can never see the mmc/sd/sdhc card/slot. Is there a different version of cwm I should be running? currently I have: v3.1.0.1 (solarnz-R3-230511-1902)

no, cmw only sees the microsd card. that's prolly what he meant

Im not able to see my micro from cwm either. Tried 2 sd cards with no luck. Am i missing a step?
Sent from my Transformer TF101 using XDA Premium App

Are either of you using an NTFS-formatted microSD, by chance? Although Prime supports NTFS on the removable storage, CWM will not mount the card if it's not FAT32.

Underwater Mike said:
Are either of you using an NTFS-formatted microSD, by chance? Although Prime supports NTFS on the removable storage, CWM will not mount the card if it's not FAT32.
Click to expand...
Click to collapse
I am not. Some info, I bought this already rooted with prime 1.7. I've spent time with my rooted nookcolor and htc incredible, but this seems to run a bit differently, expected since it is honeycomb. None of my apps read my micro sd, they use the internal memory, I guess its called an internal sd card. But it does detect it as a external storage. I don't know if that why it wont read it, since clock work goes off the sd card, maybe the path isn't right since it labels it different?
I tried two cards and reformatted it in ubuntu and it said it should be compatible with any FAT format. Am I missing something? Once recovery is set up does it work out of the box, or is there a step I'm missing?
I do boot to recovery from holding down the power button, should I buy the app that does it?
Thanks!

actorman46 said:
I do boot to recovery from holding down the power button, should I buy the app that does it?
Thanks!
Click to expand...
Click to collapse
No need to buy the app, your problems is not booting into recovry. It's teh same recovery no matter which method
you use to get there.
Try formatting with sdformatter program on pc.
Sent from my Transformer TF101 using Tapatalk

I've never had a problem with cwm seeing any micro-sd cards, but I can't get it to see the doc sd card slot. Another odd thing ... when I bought my Transformer I bought it with a doc/kb all in one package. A colleague purchased the tablet and then later purchased a doc/kb separately. They are the exact same part number the only 2 differences we can tell so far are 1) I have green mark up or hi ascii marks on my keys and 2) in cwm he can actually use the arrow keys on his kb and I can't
Another thing I found odd ... I flashed a cwm from a linux script and wanted to update to cwm_recovery-3201_roach-tf101-r1.zip so I did the flash from in cwm however my version still shows v3.1.0.1 (solarnz-R3-230511-1902) .... has anyone successfully flashed 3201? and if so how did you do it because I can't get it to work flashing from cwm although it says it flashed fine
Thanks guys!

Okay, well then it has to be a formatting issue. This weekend I'll try it on different computers / programs and report back if one works.
And I'm able to use the doc in recovery. It is wierd that some work and some don't.
Sent from my Transformer TF101 using xda premium

[UPDATE]
actorman46 said:
Okay, well then it has to be a formatting issue. This weekend I'll try it on different computers / programs and report back if one works.
And I'm able to use the doc in recovery. It is wierd that some work and some don't.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/

SpEnTBoY said:
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/
Click to expand...
Click to collapse
See, thats what I was thinking the problem was. Do you do those adb comands while in recovery?
Sent from my Transformer TF101 using xda premium

actorman46 said:
See, thats what I was thinking the problem was. Do you do those adb comands while in recovery?
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I could write something more definitive and in shell but basically I looked in /dev/block for new devices when I plugged the card in ... the "device" is /dev/block/sda but the formatted partition was just /dev/block/sda1
What could be done is a action that shows all non mtdblock devices ion dev block and list them IE:
Code:
for i in `ls /dev/block | grep -e mtd`; do echo $i; done
I'll leave the last one in so people can make fun of me
This is overkill and I haven't tested it on the actual tablet, but it works on my laptop. All I did was change the path to the interpreter and it assumes you'd have busybox installed. Not sure what the shell is in cwm recovery either. The only required "command" is the mount command from adb listed last
Code:
#!/system/bin/sh
dev_list=`ls /dev/block | egrep "sda|sdb"`;
for i in ${dev_list}; do
if [ $i = 'sda1' ]; then
dev=$i;
fi
done
echo "Device /dev/block/$dev found in doc. Would you like to mount? [y/n]";
read response;
if [ "$response" = "y" ]; then
echo "Mounting /dev/block/$dev to /sdcard" && echo "mount /dev/block/$dev /sdcard";
else
echo "Exiting";
exit 0;
fi
that can be done a lot better but just as a one off ... anyway to mount it simply verify /sdcard does "not" show in the mounted filesystems, then:
Code:
mount /dev/block/sda1 /sdcard
There's literally hundreds of ways of doing this and way more efficient ways as well but whatever

ok, that sounds great, but could you be more "noob-friendly"? My recovery can't mount my sdcard :x

I hate to bump an old thread, but it seems as if "Cannot mount SD card in CWM on Transformer Prime" is an unresolved issue.
My SD card was formatted on another android device, it is FAT32, and I am not adb savvy.
I would like to be able to mount the SD in CWM in case I ever have the need. Any non adb suggestions?
Thanks!

Your recovery Must support it, since you have a Prime I'd head over to prime development here: http://forum.xda-developers.com/forumdisplay.php?f=1414
Search for Recovery or CWM or the like.
See if you find a Recovery that specifically states support for External-SD (/removable/MicroSD)

Thanks, Thing, I will check over there.
Via Tapatalk 2 on LG SPECTRUM Broken Out 3.0

How to solve on HTC flyer
SpEnTBoY said:
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/
Click to expand...
Click to collapse
I have a HTC flyer upgraded to Honey Comb. I got unlocked from the HTC dev site. CWM recovery is installed. But not able to flash the superuser zip file from SD card. In fact not even able to back up since SD card wont mount. The HTC flyer does not have SD card slot. it is only the internal SD card. ES file explorer shows a SD card folder in /mnt/sdcard. But CWM recovery wont mount it. Im just at amatuer at all this. So it would be great if you could show me what commands I can use with adb to mount the SD card in recovery.
Any help is greatly appreciated. All other related topics only talk about external SD cards so I'm a little lost.

[MOD] 1-Click Flashable exFAT + NTFS + EXT4 support for CM10.1/AOSP + Partitioned SD!

August 4th 2013 - This script has not been maintained in a while. A big thank you to Captain_Throwback for providing continued support.
This is now minimally supported. Now that CM is adding native NTFS/exfat support, the only thing my script handles is multiple partitions.
July 21 2014 - Thank you n01ce! Please see n01ce's post for a "6.5 Alpha" that may solve some checksum problems with exFAT. I have changed devices, so this thread is for historical purposes/legacy support.
"HELP! I accidentally made my exFat card unreadable!!" -- or-- "I can't see more than 1 partition in windows!!"
Please read the instructions at the bottom of THIS POST HERE. No data will be lost!
"My card was working up until a moment ago but now the phone is showing "card damaged!!"
Re-run the script by typing "fuse-mountsd.sh" as root. The script will attempt to repair and re-mount.
If that fails, run "chkdsk /f" in Windows. Do not reformat until it is the last resort!​
TL;DR: (Flash this), put exFat/FAT32/NTFS/EXT4 sdcard in, reboot.​To remount, type "fuse-mountsd.sh" in a console (or) run using RomToolbox Lite (in /system/xbin/)
Needs to be run every time card is ejected + reinserted -- including when UMS is used
To unmount, type "fuse-mountsd.sh umount" (or if 1 partition) use Storage Manager
Non-customized multi-partitions mounted in /storage/<their name>
​
Uses init.d to fix/mount at boot
Scans for/mounts all useable block devices (with safety checks)
User-specifiable dynamic mount points
~~Create a ".mounthere" file in the partition with the first line "/location/to/mount/at"
~~Use the first line "skip" or "SKIP" to bypass that partition
Rescans for media when you re-mount
Repairs typical exFat damage caused by CM10.1 (with safety nets)
FAT32 support
NTFS-3g support (noatime set to reduce wear)
EXT4/3/2 support (*fuse built into JB/CM10.1) <- (MTP+EXT4 permissions need to be set to media_rw:media:rw 775!!))
Cleans up after itself: disables/enables ADB/root-security to what you set
BUGS:
All -- ntfsfix does not work. Binaries need to be recompiled. Not a major issue only dead weight.
exFAT may prevent deep-sleep. (NTFS on GS3 doesn't seem to have this issue.)
If you use EXT4/3/2, you need to run the following commands to allow the card to be accessed by the mobile-user:
Code:
find /storage/sdcard1/ -print0 | xargs -0 chown media_rw:media_rw
chmod -R 775 /storage/sdcard1/
(or)
find /storage/sdcard1/ -print0 | xargs -0 chown root:media_rw
Other phones -- Post a debug.txt if it works for you.
CM10 (4.1.x) -- Support is experimental. Use at your own risk.
CM 10.1 (4.2.x) -- Implemented RSA Key Signing Fix, works with BOOTICE.exe partitioned cards.
EXPERTS:
Everything is softcoded thanks to the $SECONDARY_STORAGE, $ANDROID_DATA, $ANDROID_STORAGE, $ANDROID_CACHE env variables and get/setprop command. Some locations are hardcoded in the script's "analyzePhone" function as fallbacks.
To custom-map mountpoints, create a ".mounthere" file in the root of each partition. "skip" or "SKIP" = ignore partition at mount, "/your/path/here" will use that path (or the default if bad). Defaults to "$ANDROID_STORAGE/device_id" if directory is invalid. Removes any temporary directories (in /storage/ only) at unmount. YOU HAVE TO CREATE ANY CUSTOM DIRECTORIES OUTSIDE "/storage" YOURSELF -- I set it like that as a security precaution.
To disable "Directory Creation Security", edit the line at the top of the script to say "dirSECURITY=0". This script will remount / and /storage as RW if needed.​
Here is a quick rundown of typical use-cases:
You want one large (exFat/NTFS/ext4) partition:
No customization needed, just flash and go
You want a small FAT32 partition (p1) at the beginning (for firmware/CWM/TWRP) with another big ext4 partition (p2) for your SD card mount. [ Your ROM's vold will mount (p1:fat32) as /storage/sdcard1 automatically. To get it to swap over: ]
Create a ".mounthere" file on (p2) "big" partition with the text "/storage/sdcard1"
This will override Vold and mount the (p2) as external storage. The FAT32 partition will be mounted in /storage/mmcblk1. If you want to mount it elsewhere (even /data/media/0/extSD ! ) simply add another ".mounthere" on the FAT32 partition. (The directory must already exist -- you must make it beforehand -- or disable Directory Security feature.) Be warned - Vold will mount the first partition as /storage/sdcard1 any chance it gets -- even in the background -- unless there is something mounted there already (by this script).
You have (1) partition for a game app you play (internal storage) that you want to rebind, (2) another part you want to rebind OVER an existing directory, and (3) your main storage.
Create a ".mounthere" on (1) with text "/location/of/your/game/app/data"
".mounthere" on (2) with text "/folder/you/want/substituted"
".mounthere" on (3) with text "/storage/sdcard1"
You are a long-hair-hippie Linux developer with 4 partitions, each in a different filesystem, and want them mounted hidden from apps and listed by block device so you know what partition you are on:
No customization needed, just flash and go
SUPPORT:
I can only provide support if you supply me with logs. Do so by typing "fuse-mountsd.sh > /sdcard/debug.txt 2>&1" and opening the Debug.txt in your phone's storage.
It's all automatic now - so if it mounts your modem as writeable and kicks your dog don't blame me. (It excludes dangerous block devices automatically [mmcblk0, /system, mtdblock, etc], but there is always a 1% chance it will miss something.) If it does, report it here so I can fix it.
If you intend to use this with a other ROMs/phones, IT SHOULD STILL WORK. Post any errors or weird behavior.
Code:
Changelog
[I]7.0 - TBA (Make GUI? Fix ext4 permissions automatically? Get paid?)[/I]
6.4 - No longer uses "mount" output (wasn't acting standard-ly. Using /proc/mounts instead)
- [COLOR="Red"]Got rid of conv=notrunc[/COLOR]. Be careful!
6.3 - Bugfix to scrubMount code
6.2 - No longer Experimental / final unstable
- added rough ext2/3 support
6.1 - mount command bugfix
6.0 - Added a bypass for Directory Security, fixed some bugs.
5.9 - Rewrote NOGO code from scratch -- UUIDs ignored
5.8 - (??)
5.7 - Support for Note2 formatted exFat cards + more (0xf4 bug)
5.6 - bug fixed: no longer detects zram/assumes multimount
5.5 - [COLOR="Red"]Experimental support for weird devices[/COLOR]
5.4 - [b]Major bugfix!![/b] Fix fixmyexfat.sh coding fail
5.3 - Fixed "vffat" support. Undid HARD QUIT on bad Nogo, made it a soft one.
5.2 - Increased logging of tables, HARD QUIT if Nogo not found
5.1 - Quick patch to fix dm-* device blacklist
5.0 - [b]SUPPORTS MULTI-PARTITIONED CARDS! Autoscans for block devs! Complete rewrite![/b]
4.1 - Quick patch to check mmcblk1
4.0 - [B]WORKS 100% ON 4.2.2!![/B] My script is the first to achieve this AFAIK
3.3 - fixed a bug detecting existing mounts (related to "non-persistent mount points" issue)
3.1 - added dynamic exFAT repair code
3.0 - added NTFS/ext4 support
1.0 -> 2.0 <Removed>
Attribution credits:
Original thanks go to originator of the method, smitna in the Galaxy S2 forum. Additional thanks go to shardul_seth (Post 23) for compiling the latest version of the fuse-exfat and ntfs-3g binaries for ARM, and of course Andrew Nayenko for his efforts in creating GPL'd exFat code (fuse-exfat on google code).
[HOWTO][exFAT][WORK IN PROGRESS] Mount exFAT formatted drives and cards - smitna
Full NTFS Read Write support for Android (ARM) - shardul_seth
[HOWTO][exFAT][CM10.1] Working 64GB ext sdcard with fuse-exfat (1.0.1) + FIX broken (my original Dev thread)
I believe the term is I "kanged" their binaries. The rest is mine. This is a "mod"/"hack" until CM adds native support. (If ever: exFat)​
DONATIONS:
https://supporters.eff.org/donate , or help a noob by linking to a solution in their thread. :good:
https://plus.google.com/+CyanogenMod/posts/ib5wz8jk1JyOne of the CM Team has flesh eating bacteria! Keep CM alive! (Literally)​

I'm a noob, this looks scary to me. Either way, I needs me some exfat cuz my movies are too large for fat32.
My only question is: Even though this is written for CM10.1 on Verizon s3, might this also work on T-mobile s3 with an AOSP (Android 4.2.2) ROM?
Here's what I'm running:
SGH-T999 (d2tmo)
Android 4.2.2
Kernel: 3.0.62-cyanogenmod-g137df31
ROM: Liquid-JB-v2.1-RC1
Build:liquid-d2tmo-userdebug 4.2.2 JDQ39
I've spent the last 2 days searching and testing to no avail. My sdcard is running hot trying to get files larger than 4gb on it. I've tried formatting to exfat, ntfs, ext4, even hfs+, no success. Paragon and ntfssd apps couldn't mount it either.
Any help on this matter would be greatly appreciated!
Even though this might not work on T-mobile, thank you either way, I'm glad there are people like you developing for 64gb cards.

I wouldn't say I'm a developer, just a scripter with a lot of time on her hands.
lordazoroth said:
My only question is: Even though this is written for CM10.1 on Verizon s3, might this also work on T-mobile s3 with an AOSP (Android 4.2.2) ROM?
Click to expand...
Click to collapse
MAKE A NANDROID. This mod should do nothing permanently harmful anyway: it looks for EXFAT before writing anything.
Carrier doesn't matter. It only depends (1) if your kernel has FUSE support, (2) if it has init.d support and (3) what your Block device is.
I think Google added FUSE by default in JB, and anything based off CM10.1 will have it
Type "echo $SECONDARY_STORAGE" in a terminal emulator. If it displays ANYTHING other than blank it should work.
The Block device is trickier. Type "blkid" as root with with your FAT32 card in and out. The one that disappears is your Card's Block device, and should be /dev/block/mmcblk1p1.
If you have any doubts, don't do it.

HMkX2 said:
I wouldn't say I'm a developer, just a scripter with a lot of time on her hands.
MAKE A NANDROID. This mod should do nothing permanently harmful anyway: it looks for EXFAT before writing anything.
Carrier doesn't matter. It only depends (1) if your kernel has FUSE support, (2) if it has init.d support and (3) what your Block device is.
I think Google added FUSE by default in JB, and anything based off CM10.1 will have it
Type "echo $SECONDARY_STORAGE" in a terminal emulator. If it displays ANYTHING other than blank it should work.
The Block device is trickier. Type "blkid" as root with with your FAT32 card in and out. The one that disappears is your Card's Block device, and should be /dev/block/mmcblk1p1.
If you have any doubts, don't do it.
Click to expand...
Click to collapse
Awesome instructions, very much appreciate it. Looks like it's time to get to work. I checked the zip file thoroughly and cross-checked it with my root directories to see if it overwrites anything and it looks like it just adds stuff. From what I've seen, this is the only game in town so I'll post back once I'm done.
If this does work, this is a godlike zip file and it does something nothing else can do right now

Ok still not mounting properly.
Here's what I did:
Typed "echo $SECONDARY_STORAGE" in a terminal emulator, showed "/storage/sdcard1"
Typed "blkid", showed "/dev/block/mmcblk1p1" only when sd card was inserted under fat32 file format
Formatted sd card to exFAT on PC, inserted back into s3
Flashed CM10.1_exFAT-mountsd_2.0_HMkX2.zip
Ran terminal emulator, typed su >> exfat-mountsd.sh got this:
[email protected]:/ $ su
[email protected]:/ # exfat-mountsd.sh
[exfat-mountsd v2.0] exFat autorepair and mount script for CM10.1 (HMkX2 CORE//XDA)
Automated mounting script for exFat on GS3
/storage/sdcard1 is not mounted. (OK)
Calling [fixmyexfat] on /dev/block/mmcblk1p1 (if needed)
Broadcasting: Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard1 }
Broadcast completed: result=0
[fixmyexfat v2.0] exFat header repair tool (HMkX2 CORE//XDA)
More robust than before!
Usage: /system/xbin/fixmyexfat.sh <block device, eg /dev/block/mmcblk1p1>
[fixmyexfat] Manual target is /dev/block/mmcblk1p1
1+0 records in
1+0 records out
512 bytes transferred in 0.166 secs (3084 bytes/sec)
Segment 1 (0:4) (BAD)
4+0 records in
4+0 records out
4 bytes transferred in 0.012 secs (333 bytes/sec)
Segment 2 (484:4) (BAD)
4+0 records in
4+0 records out
4 bytes transferred in 0.007 secs (571 bytes/sec)
Segment 3 (508:4) (BAD)
4+0 records in
4+0 records out
4 bytes transferred in 0.005 secs (800 bytes/sec)
Check complete!
Check complete, mounting and initializing...
########################## ATTEMPTING COMMAND ##########################
mount.exfat-fuse -o rw,dirsync,umask=0 /dev/block/mmcblk1p1 /storage/sdcard1
Attempting bypass...
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
connected to localhost:5556
List of devices attached
localhost:5556 device
Running ADB commands
FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xa04b8eb5 (expected 0x804d6ce4).
Broadcasting: Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/sdcard1 }
Broadcast completed: result=0
Process complete!
[email protected]:/ #
Not sure how to read this...
Afterwards my notification panel says: "Damaged SD card : SD card is damaged. Try reformatting it."
Tried restarting s3, mounting in storage settings, reformatting in PC. Ran script 4 times on a fresh exFAT format with the same notification error (format was unrecognizable by s3 and PC after running terminal command "exfat-mountsd.sh" [don't worry didn't lose any data ]).
After each format to exFAT on my PC I placed a few images on the card to ensure it was functioning properly, /storage/sdcard1 directory is always empty.
Mounting in settings >> storage generates the same notification error: "Damaged SD card : SD card is damaged. Try reformatting it."
Any ideas?... it is detecting an SD there after mount attempts (despite exFAT format) interestingly enough. Though nothing is detected after a reboot unless another script or settings >> storage mount attempt is performed.
I should mention that I ran a "quick" format when formatting the SD card from Fat32 to exFAT, not sure if that might be relevant.

Hm... well, I can tell you what it means. Quick formatting is fine, I actually prefer it since flash memory has a limited life. Second, "chkdsk /f" in windows will repair your card + data -- the card isn't "damaged", it's just that 4 letters at the beginning were changed. (See: Segment1, Segment2, Segment 3 messages.) My scripts change those 4 letters back, in a safe-ish way.
Unfortunately, without having a hex-dump of your working exFat header I can't say what those four letters should be. I got mine using a program called Hex Editor Neo on what I had available, a Sandisk 64gb class-10, and are what I included in the script. When the letters don't line up like it expects, you get a checksum error.
Without that, there is one single thing you can try - but has a high likelyhood of success.
Use RootBox explorer, navigate to /system/xbin/ and DELETE the file called "fixmyfat.sh".
Turn your phone OFF. Eject the SD card
chkdsk /f the card or quick format it to fix it, put a test file on it from Windows
Put the card in your phone, turn on.The card must be in the phone before it is turned on.
If that works for you, and the card works, you can give me a hex dump pretty easily so I can edit the script. IF it works, and I highly suspect it will, get a hex dump by typing EXACTLY:
dd if=/dev/block/mmcblk1p1 bs=1 count=512 of=/sdcard/working_sd.bin​ <- corrected
That will place a text file in your internal sd card than you can post/send me. Again, thanks for bearing with me, this started out as something for myself then made better in the hopes other people could use it. If you could re-corrupt the card (by unplugging/replugging it while the phone is on) and send me a hex dump of the "Card Damaged" state, even better.

O.O... you are awesome!
I'll get on this right away, and I'd be happy to help any way i can
---------- Post added at 09:19 PM ---------- Previous post was at 08:52 PM ----------
OMG IT WORKS!!! the card mounted
I tried the line of code and it gave me an error:
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/blk/mmcblk1p1 bs=1 count=512 of=/sdcard/working_sd.bin
/dev/blk/mmcblk1p1: cannot open for read: No such file or directory
1|[email protected]:/ #
My /sdcard directory seems to be a redirect to /storage/sdcard0 (i think), i have a lot of these (what appear to be redirects) on my phone now after upgrading from android 4.0.4 to 4.2.2. If I changed the end of that line of code to something like "of=/storage/sdcard0/0//working_sd.bin" (or any similar working directory), might that solve the problem or am I reading that wrong?
Thank you so much, this is... very powerful!
Great work on this!

Double post.

Please check my post for the correct DD command - I typed /blk instead of /block due to habit.
I'm glad it works. As long as you don't re-plug the card while it is on, you will have no problems. If you accidentally DO "corrupt" the card, just "chkdsk /f" in Windows, turn the phone off, put the card in, and turn it on.
And the biggest help you can give would be those headers. (I was looking at the exfat.fsck-fuse code, apparently even THAT can't fix it!) For the time being, I will re-do the scripts to display more information so I can troubleshoot more easily.

HMkX2 said:
Please check my post for the correct DD command - I typed /blk instead of /block due to habit.
I'm glad it works. As long as you don't re-plug the card while it is on, you will have no problems. If you accidentally DO "corrupt" the card, just "chkdsk /f" in Windows, turn the phone off, put the card in, and turn it on.
And the biggest help you can give would be those headers. (I was looking at the exfat.fsck-fuse code, apparently even THAT can't fix it!) For the time being, I will re-do the scripts to display more information so I can troubleshoot more easily.
Click to expand...
Click to collapse
Sounds bad, I don't know why all these companies are sticking with Fat32 after all these years. Fat32 has been obsolete since like 2000, don't we have open source formats like ext4 now? - that's my rant lol. Either way, it works and I got the file. Btw, this file acts strangely on my device, I couldn't see it in windows explorer during plugin and It wouldn't copy to my sd card even though other files seem to be copying fine. Had to email it to myself from my phone. Thank you so much for all your help, let me know if you need anything else
Rename the file and remove .rar extension before use, xda doesn't allow .bin extensions to be uploaded.
Quick question: If I shut the phone down and pull the SD, can I turn the phone back on and use it without the SD while I load the SD up with files, then power off, re-insert the SD and power on again? (like will it automount again?)

Yay!
HMkX2 said:
Please check my post for the correct DD command - I typed /blk instead of /block due to habit.
I'm glad it works. As long as you don't re-plug the card while it is on, you will have no problems. If you accidentally DO "corrupt" the card, just "chkdsk /f" in Windows, turn the phone off, put the card in, and turn it on.
And the biggest help you can give would be those headers. (I was looking at the exfat.fsck-fuse code, apparently even THAT can't fix it!) For the time being, I will re-do the scripts to display more information so I can troubleshoot more easily.
Click to expand...
Click to collapse
Very interesting. I can go on the hunt for headers if you like. I have loads of sd cards.
Oddly enough, I switched to FAT32 even though I'm on a TouchWiz ROM, cause exFAT does not use alternating file allocation tables. When exFAT gets borked, it gets super borked and you have to use chkdsk (or some other brutish method) to retrieve files. When FAT32 gets borked, you can load the last table that was working and elegantly pull your files off the card (no need to muddle through a pile of chkdsk files and find the correct extensions).
Any possibility that this method could be used to mount a more robust file system like ext[2,3,4]? Journaling would be nice. Or some transaction safe file system.
Ta very much,
ALQI

Re: [MOD] Flashable exFAT support for CM10.1 / AOSP roms (external SD)
Great.I'll try it.
Sent from my SCH-I535 using xda premium

lordazoroth said:
Sounds bad, I don't know why all these companies are sticking with Fat32 after all these years. Fat32 has been obsolete since like 2000, don't we have open source formats like ext4 now?
Click to expand...
Click to collapse
Why we have 15 competing standards... "Never attribute to malice that which is adequately explained by stupidity."
Btw, this file acts strangely on my device, I couldn't see it in windows explorer during plugin and It wouldn't copy to my sd card even though other files seem to be copying fine.​Any files you create on the device without "Rescanning for media" will not be visible in the MTP (Mass Tranfer Protocol) "MP3 player-like" abstracted FUSE filesystem. (One reason why people want UMS (USB Mass Storage) "hard drive-like" support, you see things immediately/it's faster.) Get a free program called SDrescan from Google Play, or run the command below(?), to update the MTP index and see files you create ON the device.
Code:
am broadcast -a android.intent.action.MEDIA_MOUNTED -d file://$SECONDARY_STORAGE
am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///storage/sdcard0
...let me know if you need anything else Quick question: If I shut the phone down and pull the SD, can I turn the phone back on and use it without the SD while I load the SD up with files, then power off, re-insert the SD and power on again? (like will it automount again?)​Yes, the mount script will simply fail and there will be a silent error. (I need to code some error checking if you insert a non-exfat card...)
Like I said, if you could intentionally re-corrupt the header by using Storage Manager to "Unmount SD" then "Mount SD", then the DD command, (and rescanning media to copy the file off!) I'd appreciate it. Although, I have a second idea of how to get around that problem in mind.....
alquimista said:
Very interesting. I can go on the hunt for headers if you like. I have loads of sd cards.
Click to expand...
Click to collapse
Thanks but I think the bottom line is (1) there is no working open source exfat.fsck anyway and (2) headers are unique per-device. The proper fix is re-coding vold to not run fsck.msdos on a fsck.exfat card.
Oddly enough, I switched to FAT32 even though I'm on a TouchWiz ROM, cause exFAT does not use alternating file allocation tables. When exFAT gets borked, it getse that wa super borked and you have to use chkdsk (or some other brutish method) to retrieve files. When FAT32 gets borked, you can load the last tabls working and elegantly pull your files off the card (no need to muddle through a pile of chkdsk files and find the correct extensions).
Any possibility that this method could be used to mount a more robust file system like ext[2,3,4]? Journaling would be nice. Or some transaction safe file system.​Yep, that is all 100% true. But I've lost files on fat32 drives as well - and I'd hardly call multiple file tables elegant, especially when they become desynced. NTFS would be a better fix, except for the fact it is a magnetic-media filesystem with journaling/timestamps/excessive writes, and exFAT was designed for flash media in the first place!! Even EXT4 writes too much, EXT2 or EXT4 with journaling disabled is a better solution for integrity, but much worse for flash-life. Nowadays, the value of error-recovery outweighs the limited media life. (This discussion comes up a lot in custom Linux firmwares for routers: DD-WRT NVRAM/Flashdrives)
Shardul_seth, the gentleman that compiled these binaries, has made a package for full NTFS support already using ntfs-fuse3g. (<- link) NTFS-3g is very mature/stable at this point, and installation for our devices is even simpler since we already have FUSE support in the kernel. However, his scripts are to mount USB, not the SD card. Mine does the SD card - all those ADB workarounds - so absolutely could be adapted for mounting NTFS cards. I will work on that when I have some time -- I'd need to figure out how to identify a NTFS card on header alone.
Again, all these methods are HACKS, proper support should be added in the kernel at some point. Someone actually has, and I've been cheering for him. He added EXT4 support to CM10.1, his post and code are here. However, he says it "stalled in code review". For the time being, you have to do all this manually.

Why we have 15 competing standards... "Never attribute to malice that which is adequately explained by stupidity."
Click to expand...
Click to collapse
Nice post lol, I only meant why FAT32 of all choices, these companies must know we're gonna be packing large files at some point, why knee cap us at 4gb when so many formats don't? Universal would be nice but of course it's entirely impractical
Any files you create on the device without "Rescanning for media" will not be visible in the MTP (Mass Tranfer Protocol) "MP3 player-like" abstracted FUSE filesystem. (One reason why people want UMS (USB Mass Storage) "hard drive-like" support, you see things immediately/it's faster.) Get a free program called SDrescan from Google Play, or run the command below(?), to update the MTP index and see files you create ON the device.
Click to expand...
Click to collapse
Thanks for the media scan info, that'll help a lot, I'll try out your suggestions tonight
Yes, the mount script will simply fail and there will be a silent error. (I need to code some error checking if you insert a non-exfat card...)
Like I said, if you could intentionally re-corrupt the header by using Storage Manager to "Unmount SD" then "Mount SD", then the DD command, (and rescanning media to copy the file off!) I'd appreciate it. Although, I have a second idea of how to get around that problem in mind.....
Click to expand...
Click to collapse
Will do, sounds interesting, will there be data loss or just header corruption? second idea in mind?
Also, each time I take the card out of my phone (properly after shutdown of phone) and place it in my computer (vista 64bit ultimate) It asks to check for errors, i'll click continue (confirmation to check), takes 3-5 seconds, finishes with no errors found. If I don't do this the card is write protected. I've made sure only to disconnect from PC after "safely removing hardware" so it appears that usage in the phone is generating the confusion. This doesn't seem to be an issue but I thought it might be worth mentioning

do you enter it correctly?
I get this when running the script:
Code:
BREAK! /dev/block/mmcblk1p1 is not a block-special file/device, do you enter it correctly?
How do I find what block file I need to change to script to?
Thanks for your work

boricua1213 said:
How do I find what block file I need to change to script to?
Click to expand...
Click to collapse
Safest (not easiest) way is to insert your FAT32 card, type "mount|grep vfat". The one you are looking for says "/dev/block/vold___:__" . (Shortcut: "mount|grep vold");
Then type "blkid". The one that's listed twice (UUID or Label) as "vold" is your block device's other name. (/mnt/block/mmc_somethingorother) Both names lead to the same spot.
(or)
Type "blkid" with your card in. Make a list. Remove your card. Type "blkid" again. The one that dissapears is your block device.

Ok got the file, I created 2 files, 1 before and 1 after the force unplug, just in case.
Remember to rename the files without the .rar extension before use

Re: [MOD] 1-Click Flashable exFAT + NTFS + EXT4 support for CM10.1 / AOSP (external S
I am about to embark on this journey and make another attempt at ditching TouchWiz. Does this script make it as if everything is normal as far as apps accessing the SD card go? I assume so, but I'm specifically wondering if I'll still be able to use Directory Bind and if I'll be able to create symbolic links to redirect Google Music to the external SD.
Getting ready to flash and try anyway but figured I'd ask to see if someone knows the answer all ready.

I'll be the first to admit the problem is almost certainly user error on my part but I have been wholly unsuccessful with this mod. I have tried it on Carbon Rom and Paranoid Rom. I guess they both have FUSE support, I couldn't find any confirmation of that on the Rom threads....particularly Carbon.
I flashed the zip in the OP in CWM after installing both Roms clean. I tried installing the zip as soon as I installed the Rom and I tried installing it after doing a full boot up first. Ran the chkdks /f command probably 12 times after each successive failed attempt to get my 64 exFAT card recognized. Said Damaged SD no matter what I tried. I saw the post on Page 1 about deleting the fixmyfat file....tried that too and no go. That tip may no longer be relevant since you've updated the script.
Is there something I am missing? There are lots of posts in this thread about mount commands and adb, but it seems from the OP none of those things are supposed to be necessary.

spearoid said:
Does this script make it as if everything is normal as far as apps accessing the SD card go? I assume so, but I'm specifically wondering if I'll still be able to use Directory Bind and if I'll be able to create symbolic links to redirect Google Music to the external SD.
Click to expand...
Click to collapse
In short, it should. However, exFAT/FAT32 don't support permissions/softlinks like ext4 does. So if you use ext4, just remember to set permissions appropriately! When in doubt, set permissions to 755 root:sdcard_rw or root:media_rw on the external sd.
I have tried it on Carbon Rom and Paranoid Rom. I guess they both have FUSE support, I couldn't find any confirmation of that on the Rom threads....particularly Carbon​Type "mount | grep fuse" in console. If you see "fuse" listed anywhere in the text, you have it. Google added it to JellyBean.
I flashed the zip in the OP in CWM after installing both Roms clean. I tried installing the zip as soon as I installed the Rom and I tried installing it after doing a full boot up first. Ran the chkdks /f command probably 12 times after each successive failed attempt to get my 64 exFAT card recognized. Said Damaged SD no matter what I tried. I saw the post on Page 1 about deleting the fixmyfat file....tried that too and no go. That tip may no longer be relevant since you've updated the script.
Is there something I am missing? There are lots of posts in this thread about mount commands and adb, but it seems from the OP none of those things are supposed to be necessary.​Do me a favor... open a terminal, type "su", then type "fuse-mountsd.sh > /sdcard/debug.txt 2>&1" (no spaces in 2>&1). It will make a "debug.txt" file in the root of your internal storage. Paste the output here. I am 90% certain you have the wrong block device set. 9% certain it is the 4.2.2 ADB thing.
You do not need to delete "fixmyfat.sh" -- those instructions are very old. Was the phone *physically off* when you plugged the SDcard in? Ignore the mount commands/ADB - you should not have to deal with them if you only plug in/unplug the card when the phone is off.
I am nigh certain it has to do with 4.2.2 messing with ADB. Like I said, for now, put in a *working* sd card *before* the phone is turned on and you won't run into that issue.