Related
Hi,
I have sucessfully moved my apps and caches to my 1.6gb ext2 partiton on my 8gb sd card.
I would like to back up the ext2 partition in case my sdcard fails.
How do I do this in windows xp?
Thanks
I'd love to find out how to do something similar. I just got an 8 GB card that I'd like to replace my 2 GB card with, basically, I'd like to clone the whole thing over.
Anyone have any ideas? I can do XP or Linux, just curious what software would be able to do the best job of replicating the card from one to the other.
Attach the card to your computer with an adapter (not the phone as it will be mounted by android). Download and install ext2ifs from here. You will now be able to see the files on the ext2 partition and can copy/paste them to where ever you would like.
Thanks, but I've had no luck with ext2ifs and memory cards. They even address it in their troubleshooting section:
I have a device with a removable media, for example a USB memory stick, a Compact Flash Card, a magneto-optical drive etc., which has a partitioned format and has more than one partition. When I insert that media, a drive letter appears for the first partition, but not for all the remaining partitions of the media. When I open "IFS Drives" of the control panel, the considered device appears as a hard disk drive, but there is no partitioning scheme shown for it. How can I create drive letters for the remaining partitions of that removable media? (USB hard disk drives are not affected.)
There is an unsatisfactory answer only: it is not possible.
Windows creates (and deletes) all the drive letters for pure removable devices or removable medias itself. Because the Ext2 IFS software need not to create them, it intentionally does not show any partition scheme for that drive.
Windows creates a drive letter for the first partition of the considered media, but not for the remaining ones. (Windows NT4, 2000 and even XP behave the same way in that regard).
You will run into the same problem if you have a removable media partitioned with two partitions of the FAT type on a computer, which has not installed the Ext2 IFS software! So there is one straight advice only: do not use removable media with more than one partition with Windows.
I'm guessing (someone else could correct if wrong) that if I were to just do the basic copy from one card to another - that would suffice?
If I just took the card, created two partitions (FAT32 and EXT2FS) on the larger card, then copied over all the files in both - that would work just fine?
Strange, I've never experienced any issues with ext2ifs, but yes a simple copy paste of both partitions has been all i needed. Just make sure to copy any hidden files as well.
Can we back it up using Ubuntu Live CD and just upload them to a new sd cards ext2 partition?
yes, but you would need multiple card readers.
andonnguyen said:
yes, but you would need multiple card readers.
Click to expand...
Click to collapse
Why can't you save it to the hard drive, replace the sd card, access the ext2 partition and upload the files that you backed up?
Although I'm not very familiar with Ubuntu, when I tried it last time it didn't even allow me to have access to the app and app-private folders within the partition.
What do I need to do to be able to back it up to the hard drive so I can try to upload it to another SD?
Hi,
Thanks for the suggestion.
But when I installed the driver, I can still see just the fat32 partition not the ext2 partition.
I am using a sdhc usb card reader so it is not connected to the g1.
It is like the ext2 partition does not exist through windows xp.
But when I put the card back in the g1 the files are taking up space through ternminal emulator. So the ext2 partiton does exist but still not accessable through windows.
Any other ideas?
jsunkist146 said:
Attach the card to your computer with an adapter (not the phone as it will be mounted by android). Download and install ext2ifs from here. You will now be able to see the files on the ext2 partition and can copy/paste them to where ever you would like.
Click to expand...
Click to collapse
bestwebs said:
Hi,
Thanks for the suggestion.
But when I installed the driver, I can still see just the fat32 partition not the ext2 partition.
I am using a sdhc usb card reader so it is not connected to the g1.
It is like the ext2 partition does not exist through windows xp.
But when I put the card back in the g1 the files are taking up space through ternminal emulator. So the ext2 partiton does exist but still not accessable through windows.
Any other ideas?
Click to expand...
Click to collapse
what comes up when you use
"busybox df -h" in the terminal emulator?
make sure you see something like "/dev/mmcblk0p2 (partition size) (used) (available) (used %) "/system/sd"
If not then that's the problem.
Hi,
In my phone , I do have that ext2 line /dev/mmcblk0p2
size 1.4gb - used 49 meg - free 1.3 gb
sdcard line /dev/mmcblk0p1
size 6.2 gb - used 5.2gb - free 981 meg
Thanks for the reply.
Binary100100 said:
what comes up when you use
"busybox df -h" in the terminal emulator?
make sure you see something like "/dev/mmcblk0p2 (partition size) (used) (available) (used %) "/system/sd"
If not then that's the problem.
Click to expand...
Click to collapse
If you're on Linux it is trivial to get the files off, if you'd like to make an exact image you can use the dd command. I suggest grabbing a live CD, as it will be a much easier process than making windows see ext partitions.
crater said:
If you're on Linux it is trivial to get the files off, if you'd like to make an exact image you can use the dd command. I suggest grabbing a live CD, as it will be a much easier process than making windows see ext partitions.
Click to expand...
Click to collapse
I have the Live CD, but can you elaborate on the "dd command" exactly. I'm a Linux noob and wouldn't mind backing up the partition. Last time I tried, I couldn't even get permissions to open the files no less copy them.
Thanks.
Insert the two SD cards into USB SDHC card readers. Launch the free MiniTool Partition Wizard program. Copy the ext2 partition you want to transfer on the first SD card to an unallocated area on the second SD card. MiniTool Partition Wizard under Windows does "see" multiple partitions on a USB drive even though Windows doesn't assign letters to those drives and they are invisible in Windows Explorer.
To increase the size of the ext2 partition on either SD card, use the Linux program GParted. Boot up with the GParted Live CD/USB iso file. Run GParted to resize the ext2 partition. (MiniTool Partition Wizard can move but not resize an ext2 partition.)
This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Pinging this thread for IMPORTANCE
I very much hate FAT32, yet am forced to keep using it in my external SD card on phone in the same way. I would love to see all devs add full ROM support for reformatting and mounting external SD cards with full suite of OS supported file systems. How is it OS supports EXT4 yet I am still bound to FAT32 on SD card !!!!????
This is very important to me, and should be to you all too. we need file system journaling and large file support!
Wouldn't hurt to build in advanced visual presentation for formatting/converting any partition on phone from/to all supported types with ability to setup swap partitions. I know I ask for a lot.
------Running--------
SPH-D710, Starburst ROM v2.0, EK02 modem, custom startup screen/sounds
---------------------
cpgeek said:
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Click to expand...
Click to collapse
I wanted to convert my external sdcard to ext4 so I can create a symbolic link. Mainly because one of the apps I use won't see the sdcard (devs tell me it's because the tf700 isn't using mass storage drives apparently) and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
I formatted the card with minitool partition and the TF700 wouldn't mount it. It shows up in settings > storage as a MicroSD with a Mount option but this simply does nothing. Having trawled through some thread someone provided this script to mount an ext4 card.
Code:
mkdir /Removable/MicroSD
mount -o noatime,nodiratime -t ext4 /dev/block/mmcblk1p1 /Removable/MicroSD
chmod -R 777 /Removable/MicroSD
Which should be done at each boot. This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did). Then I tried an .apk file and it wouldn't install, giving an error. I also used Rom toolbox to specify Apps2SD destination to the external but trying to install anything will give "not enough space" error.
So I am stumped.
As I am rooted but NOT unlocked I can't install a rom which might be the solution but I'd like to know if what I'm trying to do is possible without that.
I find it odd that the TF700 can't deal with an ext4 partition since it can happily deal with them on the internal. I'm confused so any clear explanation of the situation would be welcome.
louiscar said:
and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
Click to expand...
Click to collapse
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
louiscar said:
I formatted the card with minitool partition and the TF700 wouldn't mount it.
Click to expand...
Click to collapse
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
louiscar said:
This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did).
Click to expand...
Click to collapse
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
_that said:
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
Click to expand...
Click to collapse
Ok although I don't understand the Fuse fs (still trying to get to grips with basic unix stuff), I did think that symlinks were used internally.
_that said:
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
Click to expand...
Click to collapse
Ok I'll give that a go.
_that said:
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
Click to expand...
Click to collapse
Yes, I've just done the OTA to .25 a few days ago.
So basically what you are saying is that there's no reason why an external MicroSD formatted as Ext4 shouldn't work with the TF700?
Many thanks for the quick reply. I'm going to get gparted and give this a go.
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.