Strange case of a self-renaming block partition - Eee Pad Transformer Q&A, Help & Troubleshooting

Strange case of a self-renaming block partition - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi,
I've been lurking and searching for a while here on the forums and have been Googling for solutions to my problem as well. I have Debian Kit (can't post URLs as of now so you'll have to Google it) set up on my TF101, because I needed the GNU Toolkit as Busybox is lacking and I'm doing some LaTeX editing on the command line as well. I've actually successfully set up Debian Kit in the past, though I just resorted to installing everything in a ~2GB loopdisk file inside my internal storage. I've recently recovered my TF101 from a soft brick and when I was setting up Debian Kit again I thought of installing it on an external microSD instead since 2GB seems a little too small for my needs.
So I partitioned a 16GB microSD as follows: I created a 12GB ext3 partition (this is where Debian will go) and the rest as a FAT32 partition (I never thought of using around 16GB for a small Debian install residing inside Android anyway).
I set up Debian, but I noticed that everytime the tablet went to sleep, either automatically or through my intervention, all the inactive USB storages and external SD cards get unmounted by the tablet. Since my ROM (ARHD, which is based off the stock ASUS ROM) only "natively" recognizes FAT32 and NTFS partitions, my ~4GB FAT32 partition was affected by the annoying auto-umount/remount. However, I noticed that whenever it does, my 12GB partition appears to be affected as well, and for some reason I couldn't find my Debian install anymore (partition seems to be missing), though a reboot fixes the problem.
I got tired of this so I repartitioned the microSD such that its entirety will be formatted as an ext3 partition. I installed Debian again and now I noted that whenever my tablet goes to sleep the ext3 partition no longer gets unmounted.
The problem is not solved however. After an unspecified and probably random period of time in inactivity, the block partition of the external SD where Debian is installed somehow "renames" itself into the next available label for it in /dev/block. I can't clearly describe it through words without using too many paragraphs so here's a couple of outputs (I can't post screenshots because of the 10-post rule):
During normal usage (block device of the external SD card is boxed):
Code:
[email protected]: /dev/block $ ls
*
*
*
mmcblk0 <- this is my internal storage
mmcblk0p1
*
*
*
mmcblk0p7
mmcblk1 <- my external microSD
mmcblk1p1 <- the 16GB ext3 partition
*
*
*
And here's an ls of /dev/block when Debian suddenly goes MIA:
Code:
[email protected]: /dev/block $ ls
*
*
*
mmcblk0 <- this is my internal storage
mmcblk0p1
*
*
*
mmcblk0p7
mmcblk2 <- my external microSD
mmcblk2p1 <- the 16GB ext3 partition
*
*
*
Whenever my microSD goes by another block device Debian goes haywire (it's now just running of my RAM), and even if I restart it, it doesn't fix the problem, so I have to reboot everytime this happens. It doesn't happen as frequently as it did before I repartitioned the microSD such that the entirety of it is now an ext3 partition, but it's still quite annoying to have to reboot every few hours or so.
I'm not exactly looking for a solution here, I'm just trying to find out what's going on so that I can look for the solution on my own. I'm hoping that this is just an annoying problem (ASUS actually calls them "features") with my ROM, and if that's true I'm just going to move to a ROM that isn't based off the stock ASUS ROMs.
Any help and insights would be appreciated.

The reason for this is fairly simple, as far as the os is concerned the sdcard should be removable, so when it goes to sleep it tells the kernel "hey, that device can sleep too and save some more power" but because debian was still mounted, and running from that partition the mmcblk1 marker is effectively unavailable, same thing happens if you unplug a usb drive from your computer and replug it quickly under linux without safely unmounting it first, it will start jumping up the lettering from sdb->c->d etc

Is there a way to stop making the kernel automatically unmount the sdcard? Because constantly unmounting and remounting Debian sounds like a terrible chore.

Related

Apps onto SD - problems ive had and things that have helped [for noobs]

Ok, so since I went from my nice name brand 4GB class4 to a patriot 4GB class6 I have had all kinds of issues trying to get my apps to my SD. When ever I tried to reformat the card through windows vista or win7 it would disconnect, and when trying to launch computer management it would freeze until the phone was disconnected. I would also connect it, right click to format, i would get the popup asking if Im sure I want to format the card, and then when you click format it would fail immediately and the phone would disconnect as external media. So nothing I could do could reformat the card even tho at the time there was a 3.5GB FAT32/.4GB ext2 so I stuck it in Ubuntu. Same weird issues trying to format with GPartition. So I tried Partition manager which would only allow me to delete all the partitions and create ext2 but whenever I would create a FAT32 it would fail at the last 90% of the job and the phone would disconnect form the comptuer, I could then reconnect it and complete the job. I tried this about 20 times after number reboots in Vista and Win7 to no avail. I tried every updated ROM with every type of Apps2sd conversion and nothing is working, everything keeps installing to the phone even after all the commands are successful in the terminal. Finally this morning I got to work and tried with XP and it formatted first try, and now I am midway through resetting everything up. My major issue is that once I install a new build it will work until I setup the apps on the sd card, once I do that I hang on the second slpash screen.
In short I dont know what is going on but I wanted to report my issues incase anyone else was having similar problems. It would seem XP is my savior but that seems really odd.

I have the same issue in Vista. If I need to format the card I just use a reader instead.

Symptoms:
- SD card not recognized by Windows Vista or Windows 7
- If SD card is detected if you right click > format, that operation will instantly fail and the SD card will become disconnected.
- Opening Admin Tools > Computer Management > Disk Management will hang until you disconnect the SD card
- SD comes up as unallocated and needing a format but any attempt to format it will fail
- After installing Apps2sd it hangs on second splash screen
- After installing Apps2sd it hangs on android logo
- Cyclic Redundancy Check error when copying files to SD
- Phone and computer both not recognizing the SD card
Attempted fixes:
- Installing JFv1.5
- Installing 1.5Hr3Apps2sd
- Installing Dudes Apps2sd
- Installing everything imaginable from radios to RC29 and re-rooting
Chain of events that worked:
- Installed JFv1.5 - get a fresh download, install and wipe. You can do this by using another SD card, putting your SD card in another computer, or using a combo of adb or fastboot. Depending on how I messed up my phone determined which of those ways I could do it.
- Format your whole SD card to FAT32 - Same as above, depending on your situation you may need to use a card reader or a computer with linux or Paragon partition manager. I had more issues in Vista and Win7 than XP just FYI incase thats an option to you.
- Split your partition into FAT32/Ext2 - Take your total card size formatted to FAT32, mine was 3.8GB and I wanted .4GB (400MB) so in the below coding where it says "size" I used 3400M, make sure you use a capital M, for more info on this topic click here. Then, with an internet connection open up your terminal emulator and type each line and then enter:
su
cd /data
wget http://64.105.21.209/bin/lib/droid/sdsplit
chmod 555 sdsplit
/data/sdsplit -fs size -nc
reboot
Click to expand...
Click to collapse
- NOTE - The above 2 steps can be skipped if done in Paragon Partition Manager (which I owe thanks for saving my SD card when the Disk Management in all versions of windows and Gpartition in ubuntu failed to see the card, but not PPM)
- Part 1 of 2 for setting up Apps2sd - First step is to download this file. Extract those 2 files onto the FAT32 (windows visible) partition of your SD card. Then open up your terminal emulator and type out each line and hit enter:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/init.rc /data/
cp /runme.sh /data/
cp /sdcard/a2sd.sh /data/
reboot
Click to expand...
Click to collapse
- Part 2 of 2 for setting up Apps2sd - Once fully rebooted download this file and copy the AppstoSD2.apk to your SD card. With a file manager program (ASTRO for me) install AppstoSD2 off of your SD card. When it is done launch the program and select, Copy Apps to SD. Once that is done your phone will reboot. Once its back up and running choose the second option, Copy dalvik-cache to SD. Once that is done you will need to manually reboot.
- DONE!!! - Once I was done rebooting my phone now reports as having ~400MB of internal storage and it feels much snappier. I hope this guide helps someone.
Huge props to Stericson and MarcusMaximus for their help in fixing my phone. I suspect others may run into similar issues not knowing you need to split the sd card, then create those links with init.rc and a2sd.sh, and THEN install the appstosd program so maybe this will help someone else.

Update: Phone froze during a call, I pulled the battery, and it hung at the second splash screen, and the JF1.5 update.zip file on the SD card could not be found. I went and found my old reliable SanDisk 2GB, put the update on it from my computer, flashed, wiped, and once everything was good to go I tried to put the 4GB class 6 card I have been using but now the phone, linux, xp, vista, win7 all fail to recognize the card at all. I dont know what happened but my issues started when I got that card. I am taking the new Patriot 4GB class 6 card back to fry's and Im running my 4GB class 4 that I had before I upgraded. Everything is setup now and working fine so hopefully I just had a bad SD card.

I wouldnt use the phone to format your sd card. I had no issues formating on vista, winxp, win7 when using a sd card reader. I think it has something to do with the fact that you dont have direct access to the sd card when formating from the phone. I think Android just mounts the /sdcard partition and makes it writable through the usb. if that is the case then you dont have access to the partition tables on the card. Not a linux or android guru, just a theory.

1: Don't try to format the sd card using your computer when it's in your phone, if you need to format it, use a card reader.
2: ext2 isn't readable by Windows, so if your ext2 partition isn't showing up on the computer, that's normal.

i had haykuro adp 1.5 but flashed jf 1.5 to put apps on sd and its stuck on tmobile g1 screen.

Yes! The easiest way for me was throwing the card into my Ubuntu laptop and both the FAT and Ext2 partitions pop up on the desktop so you can backup or partition them easily.
And when my card crapped out last night and I put the class 4 back in I was not recognized on any computer but I could at least format it from the phone. From there Partition manager could see the drive and partition but the format was invalid. I then ran the SDSplit method and was able to get the partitions visible in Ubuntu (but not in Windows). From there I copied files (wallpaper, ringtones, etc.) to the SD card and rebooted and when it came back up Windows was able to see the files on the SD and now everything is setup again and good to go.

I have had 2 Patriot 4gb Class 6 cards that both have bad sectors within the first month...as well as randomly getting "bad_removal" from my phone with them. And then it finally losing the filesystem!
I am now using a Kingston 4GB Class 4 card and havent had any issues in 2 weeks.
Patriot isn't all that bad but I think these cards are duds.

Hi,
Just wanted to add:
I purchased a kingston 16 gb class 2 from ebay - working apps to sd no problems. I used it for 1 month.
Then I upgraded to an Adata 16 gb class 6 from newegg.com. Using it for 2 weeks now with no problems. Apps to sd and dalvik-cache to sd.
My firmware Haykuro 5.02H r4.
These 2 brands seem to be reliable.

I just ordered the A-Data 16GB cl6 card off newegg.com. When I get it I will see what happens and report back.

Partitioning - I'm baffled

I've looked through all the tutorials and read an obscene amount of how-to's, yet I can't figure out partitioning. Tried it from the SDK on a mac and pc and got some sort of path error right from the start. I've tried disk utility on a mac but I am confused on what entries I need to make. Same goes with disk manager on a PC. I've also tried Ubuntu with no luck (got an error). You name it, I've tried it and now I'm exhausted. All I am trying to do it partition a 4GB card to get a linux-swap of 128MB for one of the hero ROMs I want to try...If someone could show me the entries I'd need to make for size for the 3 partitions, that would be great. Any guidance would be greatly appreciated.

Boot into recovery, create a partition.
Boot ubuntu, get the gnome partition editor
Resize the partitions as you need them.
Done.

If you were to flash Amon Ra's recovery it has an option to partition your sd card for you. I'm not exactly sure how much it would set the swap at, but I'm sure you could find it with a little searching. Here's the link to the recovery http://forum.xda-developers.com/showthread.php?t=530492

This is for a 8gb
adb shell
# parted /dev/block/mmcblk0
print
rm 1 (make sure you back up sdcard)
rm 2
rm 3
mkpartfs primary fat32 0 7599
mkpartfs primary ext2 7599 7604
mkpartfs primary linux-swap 7668 7732
quit
# reboot recovery
this is making the linux swap 128mb.

I use the method mentioned above:
adb shell
# parted /dev/block/mmcblk0
print
rm 1 (make sure you back up sdcard)
rm 2
rm 3
mkpartfs primary fat32 0 7599
mkpartfs primary ext2 7599 7604
mkpartfs primary linux-swap 7668 7732
quit
Click to expand...
Click to collapse
Here are some tips though on how to get these numbers...
1. You MUST have the SDK installed correctly with the drivers so you can initiate the adb command and communicate with the device.
2. Partition in Recovery mode. Either Cyanogen or Amon_Ra... I use Cyanogen, so I can't speculate as to how to do this with Amon_Ra
3. BACK-UP YOUR SD CARD, this WILL WIPE YOUR CARD!!
Ok, once you are in recovery, go into the shell:
adb shell
Once there, mount the card with parted:
parted /dev/block/mmcblk0
Once there, get your SD Card Information:
print
This will give you the size of your SD Card and list the partitions that currently exist on it. The number is gives you for SIZE is what you need to go off of, NOT ALL SD CARDS ARE THE SAME!!!
Be sure to remove any parititions that are there already (use the rm # command (# being the partition number you want to remove)).
The 8MB card above stops at 7732 where my 8GB card stops at 8053, so keep an eye on the numbers!!
Ok, now you have to work backwards... If you wanted to make 3 partitions, you work from back to front with the numbers:
For my card, since it ENDS at 8053, and I want a 128MB linux-swap partition, I simply take 8053 - 128 = 7925, so the THRID partion will be:
mkpartfs primary linux-swap 7925 8053
Now I have a 500MB ext3 parition so I take 7925 - 500 = 7425 which makes the SECOND partition:
mkpartfs primary ext2 7425 7925
And then the remaining space is for FAT32:
mkpartfs primary fat32 0 7425
So you will actually run them in the reverse order:
FAT32 > ext2 > linux-swap:
mkpartfs primary fat32 0 7425
mkpartfs primary ext2 7425 7925
mkpartfs primary linux-swap 7925 8053
Click to expand...
Click to collapse
You can adjust the numbers however you want for space assignment.
Once you are done, you should (unless the ROM dev states otherwise) upgrade the ext2 partition to ext 3.
In parted type:
quit
This will drop you to the shell and then type:
upgrade_fs
Wait for this to complete and you now have FAT32 + ext3 + linux-swap
Hope this helps explain it some!

this android and me how to is the best ive seen has pictures and step by step, made partitioning a breeze http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/

Thanks for the help guys. I'll keep trying but I haven't been able to get the ADB working via the SDK. I know I am doing something wrong with the path because its not even letting me get past the initial command. By the way, I have the Amon Ra recovery and I believe it auto-partitioned 32MB. I need 98, possibly 128.
On the bright side, I just received a replacement phone because my first mytouch was defective and giving me horrible reception (BEFORE I ever tried messing around with it). So, now I have two phones, one of which I can mess around with.

staunty said:
I've looked through all the tutorials and read an obscene amount of how-to's, yet I can't figure out partitioning. Tried it from the SDK on a mac and pc and got some sort of path error right from the start. I've tried disk utility on a mac but I am confused on what entries I need to make. Same goes with disk manager on a PC. I've also tried Ubuntu with no luck (got an error). You name it, I've tried it and now I'm exhausted. All I am trying to do it partition a 4GB card to get a linux-swap of 128MB for one of the hero ROMs I want to try...If someone could show me the entries I'd need to make for size for the 3 partitions, that would be great. Any guidance would be greatly appreciated.
Click to expand...
Click to collapse
staunty said:
Thanks for the help guys. I'll keep trying but I haven't been able to get the ADB working via the SDK. I know I am doing something wrong with the path because its not even letting me get past the initial command. By the way, I have the Amon Ra recovery and I believe it auto-partitioned 32MB. I need 98, possibly 128.
On the bright side, I just received a replacement phone because my first mytouch was defective and giving me horrible reception (BEFORE I ever tried messing around with it). So, now I have two phones, one of which I can mess around with.
Click to expand...
Click to collapse
Staunty: I was in your position yesterday. I'm thinking about making a write up for noobs solely about partitioning, simply because until you do it, the language and way to do it was extremely hard to find. Here is how I did it:
I could not get ADB to work at all, not sure why but I get an error every time I try to mount or find my device in console, I've heard of ADB problems on windows 7 and even tried a fix to no avail. Realizing ADB was out of the question, I needed to format the SD card outside the phone. I did not have a card reader, so I drove to best buy and for 19.99 purchased a card reader for my pc. It is by rocketfish and comes in a red box in case you go my route. Thankfully it reads micro SD cards WITHOUT a converter to normal SD. If you have all the materials, time to format the card.
Because Android needs a linux-swap and EXT2 or EXT3 partition for what we're doing, windows can't format the card correctly without using ADB. The workaround is to use linux. You don't have to install linux, you can just burn it onto a CD and boot up with it for a 1 time use to format your SD card. If you don't have a CD burner like myself, you can use a USB drive. I went to www.linuxmint.com and downloaded linux mint for free. Mint is like ubuntu but extremely user friendly. It comes with Gparted, the partition editor. In mint, there is a search bar right in the program menu. Search for partition or Gparted and it will show up. Put your card into the card reader. Select your SD card from the drop down window in Gparted. Look for the "device" with 3.69gb of available space, thats your 4GB SD card. Right click each partition and select "unmount". Once your entire SD card is "unallocated" you're ready to divide up your memory card into partitions.
You stated that you have a 4 gig card. I'm assuming it's the stock class2 mytouch card. Thats the card I'm using as well, so I'll give you my numbers. Just an FYI, I decided to use a very large EXT3 and very large swap as I've heard not having enough swap can lead to lag so I decided to be overly generous, you can change these numbers to whatever you want. I also left some space unpartitioned just to be on the safe side since this was my first time partitioning the card.
Right click on Unallocated and select new at the top. We're going to do your FAT32 first. In the middle box on the left that says "Size" type 2900, I believe it asks you for the # in mb. If it asks for GB just type 2.9. On the lower right hand side, select FAT32 and then less ok. The second partition we'll make is an EXT3 partition. Most other methods can't directly create an EXT3 partition, however Gparted does let us do this. Lets take advantage while we can. Right click again on unallocated and fill in 575 for size. This time select EXT3 from the drop down menu. Hit create. Last and certainly not least, our Linux-Swap partition. Create a new partition again, fill in 225 for the size and select Linux-Swap for the partition. After you've created all 3, click the green check mark above the white partitioning area. You will get a message that all data on the card will be lost. Click yes. Wait for the computer to create the new partitions on the card and then viola, you've partitioned your SD card without ADB. I apologize if any of this seemed long winded or condescending, however I simply wanted to write out every possible step because I know at one point I really wanted to see something as step by step as this.

Mr. Nefarious said:
Staunty: I was in your position yesterday. I'm thinking about making a write up for noobs solely about partitioning, simply because until you do it, the language and way to do it was extremely hard to find. Here is how I did it:
I could not get ADB to work at all, not sure why but I get an error every time I try to mount or find my device in console, I've heard of ADB problems on windows 7 and even tried a fix to no avail. Realizing ADB was out of the question, I needed to format the SD card outside the phone. I did not have a card reader, so I drove to best buy and for 19.99 purchased a card reader for my pc. It is by rocketfish and comes in a red box in case you go my route. Thankfully it reads micro SD cards WITHOUT a converter to normal SD. If you have all the materials, time to format the card.
Because Android needs a linux-swap and EXT2 or EXT3 partition for what we're doing, windows can't format the card correctly without using ADB. The workaround is to use linux. You don't have to install linux, you can just burn it onto a CD and boot up with it for a 1 time use to format your SD card. If you don't have a CD burner like myself, you can use a USB drive. I went to www.linuxmint.com and downloaded linux mint for free. Mint is like ubuntu but extremely user friendly. It comes with Gparted, the partition editor. In mint, there is a search bar right in the program menu. Search for partition or Gparted and it will show up. Put your card into the card reader. Select your SD card from the drop down window in Gparted. Look for the "device" with 3.69gb of available space, thats your 4GB SD card. Right click each partition and select "unmount". Once your entire SD card is "unallocated" you're ready to divide up your memory card into partitions.
You stated that you have a 4 gig card. I'm assuming it's the stock class2 mytouch card. Thats the card I'm using as well, so I'll give you my numbers. Just an FYI, I decided to use a very large EXT3 and very large swap as I've heard not having enough swap can lead to lag so I decided to be overly generous, you can change these numbers to whatever you want. I also left some space unpartitioned just to be on the safe side since this was my first time partitioning the card.
Right click on Unallocated and select new at the top. We're going to do your FAT32 first. In the middle box on the left that says "Size" type 2900, I believe it asks you for the # in mb. If it asks for GB just type 2.9. On the lower right hand side, select FAT32 and then less ok. The second partition we'll make is an EXT3 partition. Most other methods can't directly create an EXT3 partition, however Gparted does let us do this. Lets take advantage while we can. Right click again on unallocated and fill in 575 for size. This time select EXT3 from the drop down menu. Hit create. Last and certainly not least, our Linux-Swap partition. Create a new partition again, fill in 225 for the size and select Linux-Swap for the partition. After you've created all 3, click the green check mark above the white partitioning area. You will get a message that all data on the card will be lost. Click yes. Wait for the computer to create the new partitions on the card and then viola, you've partitioned your SD card without ADB. I apologize if any of this seemed long winded or condescending, however I simply wanted to write out every possible step because I know at one point I really wanted to see something as step by step as this.
Click to expand...
Click to collapse
Dude, thanks for the detailed info. However, I finally figured out what was happening with the SDK...Maybe you're having a similar issue. First of all, I went with the 2.0 initially but was having some sort of error that I found others to be having. I scrapped the 2.0 and went with the 1.6 SDK. Dropped it on C:\ and renamed it (rename it whatever you want). That solved issue 1 and my command prompt found the right path. Issue 2 was needing to delete any and all HTC drivers in my system. After I did that, I plugged the phone back in an reinstalled the drivers that popped up with plug and play. Problems solved. Only problem I now have is remembering which ROM for which I was doing all this. Seriously, I've looked at and read about so many that they all sound the same. We should collaborate on this noob tutorial, I knew nothing whatsoever about 2 days ago and have spent countless hours figuring out stuff that is relatively simple in hindsight.

or try amon ra's preview of his new recovery, it has dynamic partitioning http://bit.ly/aXCh8

I am in the same boat. I have used Gpartition Live CD, Amon RA's Recovery 1.2.3. After partitioning the SD (4GB Class 4), when I put it in Windows XP via a SD adapter, it says the SD is not formated. The same happens when I use my phone. They phone sees the SD memory as "Blank Media".
Anyone have any ideas what I am getting wrong?

themetatron said:
or try amon ra's preview of his new recovery, it has dynamic partitioning http://bit.ly/aXCh8
Click to expand...
Click to collapse
That's what I use and it works best for me.

[Q] SD Card refuses to mount in Ubuntu 13.10 when plugged in as USB Mass Storage

My device is a BLU Studio 5.0S (GSM Arena link in my sig for the exact phone, model D570a
My ROM is a modified variant of the stock from BLU, that I made myself
The SD card in question is a 8GB SDHC Class 4 card.
When I physically take the card out of the phone, put it in an SD adapter, and put it in my laptop (running Ubuntu 13.10 64bit), it is just fine, and I can read, write, execute, etc. with no problems whatsoever.
When I hook the phone up to the computer via USB, I can get into the phone's memory (1.4GB) just fine, but when I try to mount the 8GB SD card, I just get this message:
Code:
Error mounting /dev/sr1 at /media/k2trf/8GB C4: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sr1" "/media/k2trf/8GB C4"' exited with non-zero exit status 32: mount: block device /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
The only difference betwen the arguments on the internal storage and the SD is the GID -- for the internal storage it is 1023 (which doesn't coorespond to anything), but for the 8GB SD card it is 1015 (which is sdcard_rw).
Mounting it shows GID 1000 (which would be the group id for my account, 'k2trf' on the computer.
That's the only difference between the two I can see on the device. Since there are both entries for /dev/sr0 and /dev/sr1 in my /dev/, I can safely assume that sr0 is the internal memory (which is working perfectly), and sr1 is the SD card (which seems to have a bad superblock?).
This confuses me, because physically putting the SD card in the laptop, it's completely fine, and there's no super block issues that I've been able to find, so I have to assume that it's the superblock controlling the sdcard in the phone that's bad (/dev/block/void/179:33) -- is there a way I can go about rewriting the superblock somehow for just that partition?
I've already tried doing it like I would on the laptop for other flash memory (using mke2fs and e2fsck), but I guess busybox doesn't include those commands (which would make a bit of sense, I can't imagine those are simple or small functions).

[Q] How to correctly partition 64GB SD card for use in Link2SD?

Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".

SonyXperiaz1s said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD

LS.xD said:
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD
Click to expand...
Click to collapse
Ah man, I can't tell you how happy I am that someone (you!) actually answered me about this, I've been going everywhere on XDA today. And no worries, I've been using a cardreader, leaving it in the phone just sounds like asking for trouble. And yup, tried that already. Just to repeat back: I made the card partitioned to FAT32 first. Then, after that, I resized it to free up 1024MB. For the first attempt with this method, I tried EXT2 because I wasn't certain if my kernel supported EXT4. And I made sure that the EXT2 partition was behind the FAT32 one. They were both made primary. I made sure my phone was off, and after Minitool did its magic and finished up I put the card into the phone, and rebooted. I launched Link2SD (after clearing its data first, so it would act as a fresh install), and got the onscreen prompt, and selected EXT2. And boom, once again was the annoying mount script error. I tried again, wiping the card and doing everything over identically, except trying it with EXT4 (because why not, eh?) and selecting EXT4 when Link2SD prompted. Same error. I would give it a go (with a smaller card) in my Sony Xperia Z1s, but I thought I read somewhere that Link2SD and Sony doesn't play nicely with each other..? Mainly, I would only want to try that to rule out that it's not user error, but rather an issue with the device. For that matter, I've also got an old Samsung Galaxy Proclaim on 2.3.6 that is also rooted. Perhaps if I'm feeling adventurous, I'll see if I can get it working there. Unrelated side note: How strange that my old Proclaim can read 64gig cards, but my Xperia freaks out with anything above 32! :laugh:

Alright, heres an update for this thread.
The mount script is successful for my Samsung Galaxy Proclaim, but is not on my Huawei Ascend Mate 2, even when the process is done identically.
Wondering why Link2SD seems to hate my HAM2 so much.

Bump

I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.

I dont understand what you did here. May you explain please.
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
I didnt really get what the steps where to partition my sd card. Like you i have a cheap/no brand 64 Gb Micro Sd card and im unsuccessfull with partitioning it. May you please help me. And in advance Thank You :good:

First let me state that my initial SD card was a Chinese 64GB "fake". Check if yours is also one with RMPrepUSB. Fakes report themselves as having 32GB or 64GB capacity whereas, in reality, they only have a fraction of the reported capacity.
I then purchased Silicon Power SD cards with 32GB and 64GB capacity. I then followed the procedure mentioned above and everything works just fine.

You are brilliant!
I have been having the exact same problem and have spent hours pulling my hair out trying to overcome this issue. Your fix was brilliant as so far it seems to have solved the problem!
One note, I was trying many different methods of partitioning and formatting. This method WILL NOT work with the Aparted app. Mini Tool was the way to go.
Thank You!!!

OK - Here's the thing...
OK, I did this and even posted how it finally worked and got rid of the "mount script error." However, it now seems that because the fat32 partition is now third in line, it looks like Link2SD is now trying to save all the data on the ext4 partition and not the fat32 partition.
When I do the "Link to SD" operation, it seems like it's putting everything on the second partition which is the ext4, but I don't see a change in the space used on the fat32. Am I missing something...?

Maybe the device can't support ext2...
Hi, I got similar problem with you. I've also tried to do partition in reverse order, swap first, then ext2, then fat32. It didn't work. However, when I select repair for the ext2 in Aparted, it said
The super block cannot be read or does not describe the correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the super block is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b8193 <device>
Click to expand...
Click to collapse
So now I'm looking for ext2.ko for Xiaomi Redmi Note but haven't found it anywhere.

regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
Will your method works on a 128gb sd card?

I was doing this in fact today, after reading this blog. I was having a helluva time because my Sophone i6 Plus has no regular Settings app, it's laid out like an iPhone Prefs app. The settings I needed are usually under "Storage" in a regular settings app. I was able to repartition my 32gb card on-device with aParted, but I could NOT get Links2SD to detect it, even after setting up the 2nd ext4 partition.
Mainly, after setting up the partitions in aParted, you have to switch your main write disk to internal before rebooting, else Link2SD will spit out whatever you have done. After the device reboots, the main write disk will be set to your first SD partition. After that you should be able to start Links2SD and it will prompt to set up your ext4. Then, Apps2SD will stop give you the message that it can't find the 2nd partition. Scroll down to the bottom of the blog and then the bottom where the comments start or use this link, my response should be visible. It's just a question of doing things in a specific order.
One thing that is mentioned in the tutorial is that for large cards, you should not use Fat32 for the main partition, but ext2 instead.

I've been trading a few emails with Vicki the creator of apps2SD. The best way to set this up is to link the user apps to the SD card but keep the data, the internal data on the internal partition. She said you can put the external data on the SD card but I kept both on internal and everything runs great now.

Great!! This worked perfectly for Link2SD. But now the FAT32 3rd partition isn't showing up in any of the file explorer, backup, etc. apps. What did I miss or still need to do? Thx.

Still lost
Okay I might be a complete dummy but I'm still not understanding or maybe I know it's just not working for me if you could tell me I'll maybe put a picture of the partitioning using minitool from left to right size of the first primary partition size of the second primary partition size of swap file size of any damn thing for that matter it seems you guys tried to explain or try to help but you explain it in a matter that only makes sense to somebody who does nothing but this I'm a old slow and it's stupid truck driver but I would really like to get my SD card working so I can have more storage I do like to play on these things please help

zombunny said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Hi sorry sorry would you mind doing a tutorial on YouTube please this would be most helpful. Thank you in advance.

[Q] Is fat32 the only filesystem supported for microsd?

I tried formatting to ext4 and the phone did not recognize the card. Just wondered if anyone else had sucessfully tried any other filesystems?
Right now 64GB microsd's seem to be the best deal and name brand versions can be found as cheap as $20-25 where 128gb cards will still cost you $70+ and usually involve rebates at the lower end prices.

Exfat and fat32. I have mine formatted to fat32.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk

Applications that can write to SD card can only write to a SD card format to FAT 32. The system file manager can write to Exfat, but that's it.

Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app

jvs60 said:
Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Syncthing is the same way...you should still be able to use the kitkat workaround though which is to save your files to a folder under the android\data\<appname> folder on the sdcard since each app has access to it's own data area.

I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app

jvs60 said:
I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Try this: http://www.instructables.com/id/How-to-bypass-Android-44-KitKat-external-SD-write-/

damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...

keyra74 said:
damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...
Click to expand...
Click to collapse
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37

famewolf said:
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37
Click to expand...
Click to collapse
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad

keyra74 said:
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad
Click to expand...
Click to collapse
Blame google, not Alcatel. The external sd card issue is due to Lollipop..
That app makes the same change...you can uninstall it after it modifies the file. Simpler for me to just edit the file and push the change.

I'm on exfat on a 64gb. Works fine.

The 200gb I had in my g3 worked just fine.
Just realized the card cost more than this phone...

scatoclysm said:
I'm on exfat on a 64gb. Works fine.
Click to expand...
Click to collapse
+1

My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.

maigre said:
My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.
Click to expand...
Click to collapse
Really not much of a benefit to exfat over fat32...especially if you set cluster size when formatting. I also read about some folks having permission issues writing to the exfat till they reformatted. The samsung 128GB I put in my idol3 worked like a champ.

NooB....Thank Google lollypop for sdcard problems. U can write to sdcard with some apps not all if the code is written for this.

It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people

DarkZell666 said:
It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people
Click to expand...
Click to collapse
Or just keep it formatted as fat32 and skip the above which was my choice.

Just my two cents - why would you want to format SD to ext4? Journaling filesystems don't work very well with flash drives, cells die much quicker.

Database Info

welcome