Related
Congrats to all who figured out the rooting process on NT. The NT has a measly 1gb media partition and over generous 11gb data partition. Can more experienced developers look into gparted-live-0.10.0-3.iso and e2fsprogs-1.41.14.tar.gz to use as tools to repartition the NT? I do not have a NT yet. I have a rooted emmc CM7.1 NC oc'd to 1.225gHz. I appreciate and respect all the effort that goes into this project. I used the develop financial apps for a big US bank.
hwong96 said:
Congrats to all who figured out the rooting process on NT. The NT has a measly 1gb media partition and over generous 11gb data partition. Can more experienced developers look into gparted-live-0.10.0-3.iso and e2fsprogs-1.41.14.tar.gz to use as tools to repartition the NT? I do not have a NT yet. I have a rooted emmc CM7.1 NC oc'd to 1.225gHz. I appreciate and respect all the effort that goes into this project. I used the develop financial apps for a big US bank.
Click to expand...
Click to collapse
Looks like it won't be necessary...
http://forum.xda-developers.com/showthread.php?t=1355969
Necessary no, but definitely desired.
Sent from XDA Premium app CM7.1
Not even desired if storage is really not partitioned, as it now appears.
unsivil_audio said:
Necessary no, but definitely desired.
Sent from XDA Premium app CM7.1
Click to expand...
Click to collapse
At best, repartitioning will give you an additional 1GB of space, and probably break the ability to ever do a factory restore or load additional updates when they are released by B&N.
I think we need to wait for an unlocked bootloader or at least an accessible CWM with bootable workaround (like on the Droids) before we start messing with the filesystem.
Current configuration allows 11gb for purchased apps, movies, books, music from Amazon app store, BN app store or Google market. Only 1gb is allowed for end user loaded music, books, movies etc. If you have over one thousand song music collection (5gb) you want loaded to NT you will need to use a microSD card. You cannot load an HD movie in the 1gb media partition. The old NC partition scheme had 5gb media and 1gb data. The newer NC partition scheme (blue dot) has 1gb media and 5gb data. Most users will not utilize the 11gb for purchased apps.
Thank you hwong for my case in point.
Sent from XDA Premium app CM7.1
hwong96 said:
Current configuration allows 11gb for purchased apps, movies, books, music from Amazon app store, BN app store or Google market. Only 1gb is allowed for end user loaded music, books, movies etc. If you have over one thousand song music collection (5gb) you want loaded to NT you will need to use a microSD card. You cannot load an HD movie in the 1gb media partition. The old NC partition scheme had 5gb media and 1gb data. The newer NC partition scheme (blue dot) has 1gb media and 5gb data. Most users will not utilize the 11gb for purchased apps.
Click to expand...
Click to collapse
You can add custom search paths to some media players to scan /data/media (or whatever you want to call it). You might even be able to setup a symlink. You can also open the files (large movies, etc) directly from a file manager like Root Explorer.
I do see your point, though, how the layout is different from the NC. I'm using a 32gb memory card so I guess this isn't an issue for me.
The data partition is ext4 formatted whereas the media partition is vfat formatted. When the NT is connected to a computer via USB, the vfat system is what the user sees for loading his own content. I do not think the ext4 partition shows up as a drive on the computer.
thread moved..
Thread moved to general section ..
So, ext4 cant be used ? Can't have books and videos, etc stored in it ?
hwong96 said:
The data partition is ext4 formatted whereas the media partition is vfat formatted. When the NT is connected to a computer via USB, the vfat system is what the user sees for loading his own content. I do not think the ext4 partition shows up as a drive on the computer.
Click to expand...
Click to collapse
What about in a linux distribution like ubuntu? I know that windows doesn't read ext4 (unless 3rd party drivers are installed) nor the first partition (if the nook tablet is really partitioned, that is).
You can store files on the EXT4 partition and access them through a file manager, but it won't appear as a drive on your computer when you connect it. You would have to copy files to an SD card, then from the SD card (plugged into the Nook) to the /data partition.
I'm working on a way to create a "virtual" FAT filesystem within /data that would be mounted to /media instead. This would allow you to use around 10GB for media (while leaving 1GB for /data). The best part is that it doesn't require any repartitioning or reformatting and can be easily undone.
If you can't wait for that virtual mount to work (which sounds super cool, by the way; would a different approach be to look at the smb.conf in the Samba server for Android and share /data via Samba over the network? I've read the 'stock' samba server can't share linux filesystems, but I can't help but wonder if that can't be overridden in .conf) you can do some fugly hacking like I did on the NST:
On the NC and NST, /data is an android-only vanilla filesystem
/mnt/media is the filesystem that is swapped out of Android for copying in from Windows.
On a rooted device where /data is not full, you can use fdisk (or busybox fdisk in case you have not symlinked busybox to the commands it supports) to shrink /data. I would do this over a wireless connection, so that you don't get involved in both partition editing and unmount/remount at power on.
If the /data partition is the LAST partition listed by /mount, you can delete it and resize it hot very easily.
delete it.
hit n
create the 'new' partition as a smaller size.
w to write your changes.
You get an error about the kernel still using the old partitioning. You don't care. Reboot, and your /data partition has shrunk. Now might be a good time to run fsck on that new, smaller paritition. You'll get a warning about running fsck on a mounted disk. On a device with a resized partition and no actual filesystem damage, this has not been an issue for me. YMMV.
Then you would need to delete and recreate /mnt/media to the desired size, toggle the partition label to make it a fat filesystem, reboot, confirm that those boundaries worked also, and then run mkfs.vfat (if I'm remembering correctly) on your new partition.
The tricky bit is getting the partition order correct in a complicated filesystem like this one.
On the NST, you don't actually have to get everything just right.
I found that out by happy accident - I wanted to resize /data and /media there, and they are partition 6 and 8 respectively.
The first time I did it, I was confused about which set of notes described what. When the device failed to start 8 times, it looked at the world and realized a reimage was needed, and formatted the available ext fileystems as /data and /cache, and the fat filesystem as /media.
I did not realize this until quite recently, when I needed to reimage my NST to apply update 1.1, and lo and behold: the partition table after reimaging from stock was not in the order I'd ultimately imposed on it the first time.
I do not know how robust the recovery on the NT is.
Seems to me this is a great time to find out - but I would only muck around with the /data and /media and not touch anything below those, and I don't have one of the NTs so my money's not at risk.
mmcblk0p10 is media vfat partition
Mmcblk0p11 is data ext4 partition
Here is how you repartition /data and /media partitions using Gparted and e2fsprogs as done by a Kindle Fire owner. Methodology is same for Nook Tablet.
http://forum.xda-developers.com/showthread.php?t=1388996
hwong96 said:
Here is how you repartition /data and /media partitions using Gparted and e2fsprogs as done by a Kindle Fire owner. Methodology is same for Nook Tablet.
http://forum.xda-developers.com/showthread.php?t=1388996
Click to expand...
Click to collapse
Partitioning seems different as that Extremely Well done set of instructions for a fire only seems to use GParted which I don't believe understands the partitions on th NT???
I could very easily be wrong and if you tried and were successful doing this on an NT then I apologize and want to buy you a case of beer for your efforts to help us all on the NT.... just I'm skeptical as NT doesn't use traditional FS layout or format as far as I believe...
If this worked for you PM me with some proof and your paypal and I'll pay up with thanxs added... else I just felt obliged to question and put my money where my mouth is to save others from at a min. soft bricking their NT...
I still haven't picked up an NT yet so I did not try this yet.
For discussion only.
I would think the repartitioning process is simpler than the Kindle Fire since the /media(vfat) and /data(ext4) partitions are at the end of the SD. Gparted does not create ext4 partitions. Gparted can create ext2 partitions and e2fsprogs changes ext2 to ext4 if I follow the logic correctly. My first step would be to make a backup of the /data partition. Then I would delete /data partition. Then I would increase the /media partition using GParted. Then I would create the /data partition as ext2 using GParted. Then using commands in e2fsprogs to convert format to ext4. Then restore the /data backup from the first step.
Here is the NT partitions from NookDevs
http://www.nookdevs.com/Dump_NookTablet_Partitions
hwong96 said:
Gparted does not create ext4 partitions.
Click to expand...
Click to collapse
Not yet! An update to it today actually has gparted displaying the partition correctly (it wasn't before? I thought it had ok support for ext4 partitions before, or since 2009ish), so pretty sure they're working on it. I'd be inclined to wait for official support over making ext2 partitions tbh
hwong96 said:
Here is how you repartition /data and /media partitions using Gparted and e2fsprogs as done by a Kindle Fire owner. Methodology is same for Nook Tablet.
http://forum.xda-developers.com/showthread.php?t=1388996
Click to expand...
Click to collapse
Has anyone tried it? I wish to try, but don't understand how to make those binaries work, coz KF used CWM, which we don't have yet! Can anyone direct me?
i couldnt paste a large file to the internel memory like a .mkv video
is there is a way to convert it to ntfs or another way ????
Android 2.3.7 does not support NTFS file format, which means you are "forced" to use FAT32, which means up to 4GB per single file. Split mkv file to 2 (or more) files if need be.
Cholek3 said:
Android 2.3.7 does not support NTFS file format, which means you are "forced" to use FAT32, which means up to 4GB per single file. Split mkv file to 2 (or more) files if need be.
Click to expand...
Click to collapse
Partially right.
The kernel itself does support NTFS - stock. That's how you can mount NTFS drives in USB-OTG mode. However, the OS itself isn't set to be able to format the partition as NTFS (with extra options and extended testing, i did actually, see DoomLord's MSD thread). Unless there is a third-party app or tweak that modifies how android boots and mounts internal SDCard, and by using non-MTP mode, chances are you are stuck at the moment.
kazuni said:
Partially right.
The kernel itself does support NTFS - stock. That's how you can mount NTFS drives in USB-OTG mode. [...]
Click to expand...
Click to collapse
You cannot mount NTFS drives with the stock kernel.
Sent from the Delta Quadrant using a transwarp conduit.
I bought 64 gb card and it works on samsung stock galaxy s3 rom BUT when i switched to Cyanogen10 mod it started showing damaged card,
I know it is because the stock has driver for that card,
My question is has someone ported or can someone please port the driver from stock and make it workable on custom roms.
Thanks.
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Alright trying hopefully this works and doesnt screw up my card.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
didnt work now the phone doesnt even show damaged card, its acting like card is not even inserted.
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Click to expand...
Click to collapse
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Click to expand...
Click to collapse
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
i used easeus partition: i deleted partition first and made new one with fat32 file system,
which didnt work, after that i deleted the partition again and formatted using stock galaxy s3 rom and it works again but limited to stock rom only like before.
atleast the card isnt dead.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
ill try this software as well.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
I didnt get a chance to try Hp software i cant across this other software and it work.
Thank you though
d4fseeker said:
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Click to expand...
Click to collapse
Thanks, though I realised this - the whole reason I need a 64GB card is to copy movies onto there, because I travel a lot... many of them are over 4GB, which is the issue I have with using FAT32.
d4fseeker said:
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
Click to expand...
Click to collapse
Maybe I should look at ext3 instead, though then I'd have problems putting it straight into my Windows machine. Though, exFAT has been 100% stable for me so far.
many of them are over 4GB
Click to expand...
Click to collapse
Ok that is a problem for FAT32. You didn't mention it so I assumed you mistook the 32 in FAT32 for 32GB as many people do.
Maybe I should look at ext3 instead
Click to expand...
Click to collapse
Since you should never need to remove or directly access the card (MTP mode or File transfer through 'Samba Fileshare' App) that should be a solution. For your own computers, you could use the following driver:
http://www.fs-driver.org/
It allows read-write access to EXT2. EXT2 being EXT3 without journaling support (and thus fully backwards compatile) that could do the trick.
Pententially you'll need to re-enable the journal again through tune2fs on the Smartphone after having used an EXT2-driver. Not sure though since the journal is only relevant until a clean dismount is made.
You should however also be able to load the NTFS-module in the kernel or recompile the CM10 kernel with the required options.
If you need to plug the SDcard into your computer a lot, that may be the only solution until Gokhanmoral is back.
I dont know if there is already info on this subject, but i recently got a sandisk 64G mSD and it didnt even seem to last a year - kept getting into 'read-only' mode for some reason..... i though it was my KKDS_1.4 (4.4.4) rom, link2sd and all the other stuff there, but dont know if that's the case kept having to do the following to get it out of read only mode :
Plug SD into windows and :
Start > Run > cmd
type "diskpart" -> runs diskpart.exe from system folder
type "list volume" -> now you see all your connected drives, see which one is the drive
type "select volume #" -> # being the letter of your drive
type "attributes disk clear readonly" -> removing the protection
Then open your SD, you can now edit, delete, move files.
However this didn't seem to last long... and think the SDcard on its last leg - even though i didn't use it much.... i did have a ton of pictures, videos, programs and music on it but still had about 12G free but was really slow - even though its one of the SanDisk Ultra 64G XC I (UHS Class 1).... Granted I do use Link2SD and have partitioned the card as follows [59G Fat, 4G ext4, 1G Swap], but cant account for things taking so long, and then sometimes finding the card in read-only mode.
Anyhow... from my reading i dont think android will even use the 'swap' space i made, so on future SD I plan on a 4G ext4 (for second partition) with the remaining 60G as a FAT32, ExFat, or NTFS - for my KitKat (4.4.4) Device - will one filesystem be better an any other for the first partition (windows / linux compatible) - im thinking NTFS (reliable & windows compatible) but not sure if KK supports write mode to NTFS filesystem? There is also ExFat - but not sure about android support for that either... Know many people suggest raw FAT but just not possible with todays bigger cards so kinda seem stuck with FAT32.
Regressing and getting to the heart of my post here, I was wondering if there has been any long term studies of Which mSD Cards last longer and transfer data pretty fast? Perhaps there are ones more reliable... thought Sandisk was pretty good (my USB 3.0 SanDisk Extreme 64 GB Flash Drive kicks butt) I know the technology is different but the 64G Ultra SDXC was UHS Class 1. (so at least class 10)... but its only a year old and already giving me trouble... what are the better cards out there -- and what filesystem should the first partition be set to to make it last (and usable in a windows [or linux] environment) ?
I did read over a few good posts :
http://forum.xda-developers.com/showthread.php?t=1544156
and http://forum.xda-developers.com/showthread.php?t=1150369
as well as a few other places here , here , here , and here
Im starting to think that since im using Link2SD perhaps class 10 card not optimal for the ext4 r/w , but i do use the primary partition quite a bit (like a flash drive ans dont want to wait eons while transferring all my tunes and videos etc to phone.....
Has anyone done any research into these issues? Are there any cards the use SLC nand? or just last longer?
Can anyone comment on any of this.
steve_77 said:
Anyhow... from my reading i dont think android will even use the 'swap' space i made, so on future SD I plan on a 4G ext4 (for second partition) with the remaining 60G as a FAT32, ExFat, or NTFS - for my KitKat (4.4.4) Device - will one filesystem be better an any other for the first partition (windows / linux compatible) - im thinking NTFS (reliable & windows compatible) but not sure if KK supports write mode to NTFS filesystem? There is also ExFat - but not sure about android support for that either... Know many people suggest raw FAT but just not possible with todays bigger cards so kinda seem stuck with FAT32.
Click to expand...
Click to collapse
I just answered on the other thread, but I wanted to add that AFAIK Android doesn't support NTFS (at least not without serious jigging) and I think exFAT is close to the same situation. Why? These are proprietary Microsoft formats (arguably FAT32 is as well, but it is based on the standard FAT16 and has been opened up considerably) that even for a Linux system have to go through hoops to get the drive to properly write (well, not too bad, install the ntfs-3g package).
I have a 128 GB microsd and I do not want FAT32 on it. I have MIUI 8 (Android 5.1.1) with 3.10.49 kernel, TWRP 3 and root. For some reason mount doesn't work at all, it always produces error "Invalid argument". I tried replacing it with one from BusyBox but it didn't help. Some forum guys told me that I should add the card to fstab (which AFAIK is located inside boot.img), and edit the config of vold (which is located I have no idea where). Also this. All I understood from there is that there is some storage_list.xml and I should edit it. Again, searching through forums led me to this path framework-res.apk\res\xml\storage_list.xml.
But still! I have no idea where this framework-res.apk is located and how do I unpack-repack it.
All info that I'm desperately trying to extract from google is outdated or related purely to cyanogen >_< Please give some instructions
You wrote you don't want FAT32. Other filesystem than that isn't supported by MIUI which is why you won't succeed to show your card content by editing anything. You need a 3rd party libs with your filesystem support.
See here, worked for me http://forum.xda-developers.com/showthread.php?p=61142640
or install a custom app with your filesystem support (eg. Paragon NTFS).It works either.
Sent from my phone by Tapatalk
Dude, that's the f$#@ed up part, you see.
> If you use KitKat
And I'm using 5.1.1 which is technically lollipop.
I'm seeking for a support as close to native as it can be, so I'm not involving any "mounting" crapware, especially Paragon's products, I'm fed up with their ext4 4 windows driver which gave me countless BSODs and corrupted files.
You said that MIUI doesn't support anything but FAT32, but that's not 100% true. It by default supports only FAT32 for external storage. But at the same time it mounts internal storage (which is of course in ext4) no problem. So I guess it's not *unable* to use ext4 (or f2fs, which is AFAIK supported by any kernel after 3.10.*) for external storage, it's just not enabled by default, and the question is how do I properly use that ability of android to mount ext4 (and/or f2fs)
UPD: I have to apologize for posting "also this" in the initial post w/o actually giving the link, here it is.
This is what seems actually related, but I'm too noob to understand what am I supposed to do to mount the damn card
First, the ROM and/or (especially) kernel should have F2FS support, then ramdisk should be modified with fstab edited so it could mount F2FS partitions at boot.
Other than that, it's impossible.
Sent from my ASUS_Z00A using XDA Labs