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?
Related
Hello! I've searched all over the internet about this but haven't found any usable information about this. I was thinking about storing music files etc on the ext partition on my SD-card. I've a 8GB sdcard with a 64MB swap, 1024MB FAT32 and rest of the space goes to an ext2 partition. The problem is, how do I acess the ext2 partition in the phone? I know it is placed in /system/sd. But it seems it is only the super-user who has access to this folder. Is it possible to symlink the folder to another place and make it accessible for the user?
Every info I find is about storing apps on the ext-partition, which works. But having 6GB space for apps feels very overkill. FAT32 seems to be quite limited to speed when copying files, and also it have size limit of files.
The easiest and most recommend way to solve your problems is to repartion your card to:
0M swap (no use for swap on hero)
512M ext2 (see below)
rest as FAT (over 7G for your music)
If you plan on having every single one of the apps on the market you can give the ext2 partition 1024MB, no need to give it any more. There are numerous problems that can arise from having larger ext2 partitions, just of the top of my mind if you do have more data on the ext2 partition larger than your FAT free space you can't do a nandroid backup, you'll end up storing too much stuff on the ext partition which is usually wiped on ROM update and replacement, and it is much harder to access these files, as opposed to the FAT partition which is can be mounted as a USB drive to your PC.
Finally note I said ext2, and not ext3/ext4 because Ext3/4 are journaling file systems which are NOT suited for flash devices. They also have much more CPU overhead then ext2. Finally not all ROMs/kernels support ext3/ext4 and for a good reason!
BTW, please post questions in the either the Q&A or general sections. This is the DEVELOPMENT fourm.
Good luck.
Thanks for your reply, and sorry for posting in the wrong forum, which is quite obvious when I see it now!
Moved to Q&A as not development
erasmux said:
The easiest and most recommend way to solve your problems is to repartion your card to:
0M swap (no use for swap on hero)
512M ext2 (see below)
rest as FAT (over 7G for your music)
If you plan on having every single one of the apps on the market you can give the ext2 partition 1024MB
Click to expand...
Click to collapse
+1, Yeppers, wow a 6gb ext... That is some serious overkill,why?
Sent from my phone.
I was thinking to use the ext partition as a storage of music etc instead of the fat32 partition. The ext-partition is faster to copy files on, especially if you get a 32gb card and maybe you want to transfer big files. If I remember it right FAT32 table doesn't allow file-sizes more the 4GB, and it is also slower to copy to or from.
Any linux operating system should be able to read the ext partition on your sd card, or a program such as gparted is another thing to look into. Remember you can boot to linux without installing the operating system (boot from CD). Ubuntu or Knoppix is a good one to check out if you're new to it all.
Hehe, I think you did misunderstand my main question. The question is how to read the ext-partition directly from the phone with a file-manager (i.e. Astro File Manager). Not from a computer, from the phone, in the phone.
Vantskruv said:
Hehe, I think you did misunderstand my main question. The question is how to read the ext-partition directly from the phone with a file-manager (i.e. Astro File Manager). Not from a computer, from the phone, in the phone.
Click to expand...
Click to collapse
O in that case you have no chance lol. AFAIK there isn't any program designed for this purpose.
Vantskruv said:
Hehe, I think you did misunderstand my main question. The question is how to read the ext-partition directly from the phone with a file-manager (i.e. Astro File Manager). Not from a computer, from the phone, in the phone.
Click to expand...
Click to collapse
Well it depends where your ROM mounts it. I think most ROMs mount it to /system/sd, so you can use any file explorer with root permissions to browse there (i.e. ES File Explorer).
Is it possible to repartition my SD card to use EXT4 instead of FAT32, with the Fascinate? I'm currently running an EB01 kernel and a custom EB01 build. I'm just not sure how to do this part, as I've never done it before. I've seen it done for other devices, but I don't think it has come up here yet. This isn't really a debate on if I should or should not make it EXT4, just on how to do it.
That's what a voodoo kernel does.
Sent from my SCH-I500 using Tapatalk
JoeDat said:
That's what a voodoo kernel does.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm running the EB01 voodoo kernel, and yes it obviously has support for EXT4 since that is the FS it uses.
My question though is how can I mount my SD card to be recognized when I format it to EXT4 too?
Ah crap. I should have read your post more than once. Mundane detail. Just call me Michael Bolton.
Sent from my SCH-I500 using Tapatalk
If you don't have anything on your SDcard you mind deleting (or could just back it up), you could always try repartitioning it, and then seeing if Android is able to mount it.
If it doesn't automatically work, it shouldn't be too hard to modify the system to work (either by switching it from using 'vfat' to 'auto' or 'ext4')... it's just a matter of finding out where to change it.
There's no reason why it wouldn't, I guess... worst case you use command line mount tool to mount it manually every boot
That's what I thought too, that it would work inherently, but I partitioned/formatted the entire thing to EXT3 and it was not able to be recognized. I think either A) there is no built-in module for EXT3 support, or B) I'm just not doing it right.
Could be that I used a Windows tools to do the job to get EXT3, and I'm having trouble finding one to do EXT4, and I can't find any tools/scripts to convert EXT3 to EXT4 for Android.
If you format the sdcard to anything other than FAT32, Windows will not be able to read it when you try to mount it on your PC. I'm not sure if there are any utilities available that allows Windows to directly mount EXT filesystems or not, but I would be very afraid of data loss with a configuration like that.
What is the reason you want to convert it? Is it the file size limit of FAT32, or something else?
Posted from my EB01 SuperClean Fascinate with Voodoo
ivorycruncher said:
If you format the sdcard to anything other than FAT32, Windows will not be able to read it when you try to mount it on your PC. I'm not sure if there are any utilities available that allows Windows to directly mount EXT filesystems or not, but I would be very afraid of data loss with a configuration like that.
Click to expand...
Click to collapse
There's been an ext2 (possibly 3/4, but all are backwards compatible long as you don't use extents on 4) driver for Windows for a number of years. There's also a number of tools that can allow you to open ext2/3/4 file systems and modify them, without actually having to mount them.
ADB would also still work, so would an app that provides access to the sdcard via webdav/ftp/sftp/etc.
What is the reason you want to convert it? Is it the file size limit of FAT32, or something else?
Click to expand...
Click to collapse
Speed should improve by quite a bit, as well as greatly increased reliability (although the windows. Ext2/3/4 also support far larger files than fat32, of course, so if you like your raw-DVD rips or 1080p ultra-high-quality bollywood movies, there would be an obvious benefit by removing that restriction. I don't believe the ext family of file systems support it (but I could be wrong about ext4), but tail packing would greatly improve efficiency if you have a massive number of small files (reiserfs has it, btrfs might also- not sure).
Personally, it doesn't seem like there's enough of a benefit to really do it, especially if you're not using Linux... other than the desire to do it for the sake of doing it... which, considering where we are, that's pretty much enough of a reason to do anything.
Until I can find a good way to automount the FS every boot I wil probably stay with FAT32. I played around with different methods last night quite a bit and it turned into much more of a hassle than I liked. I really regret not having it however, because of the loss of speed.
I'm opening a new thread as this is really the work of verygreen, racks11479, j4mm3r, stilger, and rookie1.... and I've hijacked their threads enough as I only did minor repackaging to put this together as a hopefully generic template image...
This is but an attempt to create a mostly generic SDcard template for installing all versions, as base for Froyo, CM7, or Honeycomb as an SDcard install...... Most of the features best lend themselves to CM7 as verygreen's Alternate (uAltImg/Ram) allows installing and upgrading all current variants of CM7... but with Recovery as CWR 3.0.1.0/Ext3/4 with verygreen's installer/upgrader as uAltImg/Ram it can handle all your CM7 variant install and upgrade/migrate to SDcard needs...
The generic 2GB expandable image is available from;
http://dev-host.org/aewwoavj437z/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
I suspect/hope that this thread will fade fast from the first page but just hope it will be useful for folks when modeling and building generic SDcard bootable versions...
EDIT: For folks who just want to update just their existing SDcard boot partition and get this boot functionality
I removed the files you shouldn't change from an existing /boot dir and zipped up the rest and posted this zip in my dropbox
http://dl.dropbox.com/u/6922721/jtbnet-modified-bootfiles.zip
Just have your SDcard mounted as /boot on your PC and extract this zip to it to get the same boot options as my card...
The layout of the current .v6 template SDcard to allow it to fit on a 2GB minimum size card is;
Part. # Name FStype Alloc. size Free Space
1 /boot FAT32 149MB 120MB
2 /system EXT3 462MB 455MB
3 /data EXT3 964MB 948MB
4 /sdcard FAT32 39MB 38MB
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
CM7 Install Example by User stilger
with comments added by jtbnet and xdabr:
----------------------------------
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v6)
http://dl.dropbox.com/u/6922721/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Use Easeus Partition Manager to extend the 30MB 4th FAT32 /sdcard partition to fit your current SDcard
4. Once the card is written, place the cm7 zip in the root of the boot filesystem.
(Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
http://mirror.teamdouche.net/?device=encore
5. Place the gapps zip of your choice in the same "boot" filesystem.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip
6. Place SDcard in your Nook.
7. Turn on Nook.
8. Hit N button when it says Press any key for menu.
9. Choose SD and Alternate as your boot option
10. Let it finish. It says it will reboot but usually hangs for me so I give it 10 seconds after the screen goes black and long press the power button until it starts up...
11. Boot into CM7
TIP: To have rooted stock eclair version nook use the same sdcard partition (#4) as you use when booting on an SDcard bootable you can make one simple edit to the stock eclair /system/etc/vold.conf...
There are 2 definition blocks in the file... the first is for mount of internal eMMC partition 8 as /media, while the second block is to mount the 1st sdcard partition as /sdcard... to change this so that the 4th partition on the SDcard gets mount to /sdcard just Add a line;
partition 4
in the second block with your favorite editor like Root Explorer, or via adb pull,edit,push of the vold.conf file... and reboot...
I.E.:
## vold configuration file for zoom2
# modified for encore
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
partition 4
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
bobshute said:
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
Click to expand...
Click to collapse
Sorry Bob... I uploaded the wrong image... Had a long day at work today so just getting to uploading a fresh image... this one IS 2 GB with larger/150MB /boot but a very small 4th /sdcard partition, and has formated system and data so won't boot to CM7 anymore but it's much cleaner...
Only thing this 2GB image only zips down to 800MB... strange as the wrong card I uploaded last night was a 4GB card I was testing with and with lots of data on system and data and it zipped down to 300MB... but this one is cleaner and does boot to CWR 3.0.1.0 as recovery and verygreen's CM7 install/updater as Alternate boot...
It's taking forever to upload so I may not be able to update the link in the original post till the morning as already well after midnight now...
bobshute said:
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Click to expand...
Click to collapse
You are correct on what it has for uRecImg/Ram and uAltImg/Ram and yes Racks' 3.0.0.6 is Ext4 Only.... thus why I wanted to update to 3.0.1.0/Ext3 and Ext4...
That wrong 4GB upload from yestrday was the test card I had expanded and tested installing CM7 RC4 with UI tweaks to test VG's installer and then restored system and data from my normal card's backup to test CWR 3.0.1.0... so I mixed up the cards when I made the image and uploaded the expanded test 4GB version instead of the original blank 2GB version I started with...
Updated OP with cleaned up file...
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
jtbnet said:
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
Click to expand...
Click to collapse
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
Before:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 458925 0 100% /system
/dev/block/mmcblk1p3 972436 972436 0 100% /data
Click to expand...
Click to collapse
Used recovery to format /data and /system.
After:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 8238 426992 2% /system
/dev/block/mmcblk1p3 972436 16424 906616 2% /data
Click to expand...
Click to collapse
Booted into alt boot after copying zip files to /boot again and everything installed fine.
stilger said:
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
...
Used recovery to format /data and /system.
.
Booted into alt boot after copying zip files to /boot again and everything installed fine.
Click to expand...
Click to collapse
THANX
I had been just deleting the filler files in CWR (/system/zerofile and /data/zerofile) instead of formatting... BUT I think I have found the answer... I need to zerofill to cause the 2 partitions to compress reasonably... BUT if I create the files then sync,umount,re-mount then delete the files, sync, umount this frees space by freeing the inode but shouldn't actually touch the zerofill'd now freed space... so compression should be the same without the files...
I'll give this a try and upload v5 later hopefully...
EDIT: finally found time to upload v5... well mirror is still in process... /data and /system now empty and result is even a few bytes smaller...
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
xdabr said:
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
Click to expand...
Click to collapse
Check racks11479's thread for a good number of SDcard installable versions...
http://forum.xda-developers.com/showthread.php?t=998861
I do hope to find time to update the second post in this thread with some much better explanantion... but in short...
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
verygreen said:
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
Click to expand...
Click to collapse
THANX...
I did think of that... after the fact... but the free space on those 2 partitions is <150MB which at the expected 4 to 1 compression I'm seeing would only save another ~35MB... so I didn't bother try and re-upload.... as less than 10% expected improvement... IF I need to upload another version I will include this in that version though...
I'd tend to agree with you on "your target compressed size should be the size of all real files on the card + a little bit." but the actual Used space is ~100MB, Total Space = 2GB, Unused space is thus around 1.9GB... so compression (1/5-1/4) really STINKS on this... but I'm not sure why as I've tried winzip and gzip with multiple levels of compression...
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
xdabr said:
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
Click to expand...
Click to collapse
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Perfect recipe; thank you, stilger! Just what I (and likely lots of others) needed to know. I'll probably try this tonight.
I love this place.
stilger said:
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Click to expand...
Click to collapse
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
jtbnet said:
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
Click to expand...
Click to collapse
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
stilger said:
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
Click to expand...
Click to collapse
THANX... Added your steps as an example in the Second post...
Hi, in the Nook Development forums, I found this post from Albert Wentz: http://forum.xda-developers.com/showthread.php?t=1439630
But unless I'm confused, I believe there are many other posts with other roll-your-own instructions? Such as: http://forum.xda-developers.com/showthread.php?t=1466583
All I want to do is build the SD card for my kid's nooks (versus paying $20 to N2A) so I can boot to it to run Android just like the N2A card. Does anyone know which post N2A may have followed to build their version? Or is Al's post the most modern build? Or the 2nd URL I list?
I'm quite technical so know I can do this, I just need to know which is the latest and greatest, or if there are many diff build customizations, which, let's say, is the most popular ? I mainly care that it has Google Play and Amazon App stores, and that I can sideload ebooks, mp3's,videos. If it comes with other apps, fine, but I'm fine with downloading,installing any I wish afterwards.
And.....some posts mention you don't have to modify your nook at all, just boot to the SD card, but others say it modifies the Nook (roots it), so that if you ever had to return it you'd have to restore it (hence best to back it up beforehand). Which is correct???
Al's method works fine. Anything you mentioned that you wish to try will work. I ran boot to SD android rom for several months before I took the plunge and rooted my 8gb Nook to a full android tablet.
It in no way modifies the internal workings of your Nook. The Nook allows booting to the card by design. Just use a Sandisk card of 8gb or more for best results and all you need is a class 4 speed rating. Believe it or not, a class 10 doesn't work as well.
YMMV
Good luck and have fun with it!
jaxn51 said:
Al's method works fine. Anything you mentioned that you wish to try will work. I ran boot to SD android rom for several months before I took the plunge and rooted my 8gb Nook to a full android tablet.
It in no way modifies the internal workings of your Nook. The Nook allows booting to the card by design. Just use a Sandisk card of 8gb or more for best results and all you need is a class 4 speed rating. Believe it or not, a class 10 doesn't work as well.
YMMV
Good luck and have fun with it!
Click to expand...
Click to collapse
OK thanks, so if I understand you, rooting is a separate method, as in my 2nd URL referenced. (and in reading that, the SD card is only used to flash (or pull) the image from, to put onto your Nook.) I don't know about backup, but I don't think I want to mess with the stock OS for now. Maybe if B&N abandons it. I guess I don't see it as a big deal that my kids will need to reboot each time to toggle between nook OS and Android.
I read that about the Class4 vs 10. I think I even read posts about class 10's not only running slow, but acting really buggy? Is that right?... One of our SD cards is a 16GB class 4 and a 8GB class 6. Anyone heard if class 6's have any issues?
Extremely easy process to build a card similar to N2A to run a very stable CM10 from:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
dtetner water
asawi said:
Extremely easy process to build a card similar to N2A to run a very stable CM10 from:
iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Ooops!
I just realized both URLs I posted (even 1st one from Albert) mention rooting.(altering tablet) My mistake. Ok, so where's the mainstream single post on XDA forums that describes the most popular non-root (boot to SD) process? I'd rather follow a post off XDA website. And if I have issues, maybe fallback to that URL you gave me, although his English is not so great, so afraid I might get lost in his partitioning instructions. I also don't have a Linux box at home (re: his mention of EXT4) although I have been trained on/worked with Linux some. Although running Jellybean since it's the latest & greatest sounds nice....although I've read enough articles from mainstream tech sites that state it's a bit too buggy? I'm sure ICS is plenty good enough and all apps support it.
Whats the difference between CWM (clockwork mod) and CM (cyanogen)? Wikipedia just says "The CyanogenMod source code repository also contains the ClockworkMod Recovery"
Click to expand...
Click to collapse
The step by step you'll find somewhere here on XDA actually is the work of the guy I posted to. So my link is the source. That "Iamafanof" blogger is the person "Succulent" you'll see referred to here at XDA. Entirely up to you of course, but I don't see why you wouldn't at least check it out.
Edit:
You do not need a Linux system and I don't know what gave you the idea you would. The process is extremely simple: Download a rather large file, burn it to an sd-card, expand one partition (optional but recommended).
asawi said:
The step by step you'll find somewhere here on XDA actually is the work of the guy I posted to. So my link is the source. That "Iamafanof" blogger is the person "Succulent" you'll see referred to here at XDA. Entirely up to you of course, but I don't see why you wouldn't at least check it out.
Edit:
You do not need a Linux system and I don't know what gave you the idea you would. The process is extremely simple: Download a rather large file, burn it to an sd-card, expand one partition (optional but recommended).
Click to expand...
Click to collapse
I thought that because as far as I'm aware, the EXT4 that he mentions (for P3 Data1) is a linux type partition. (unless some Windows partitioning tool can create it I'm not aware of) I'm willing to try his steps. So I guess you'd recreate the "P3 FAT32 SDCARD" partition the same size as it was before then? And the P4 (EXT4) you'd resize, as you mention, to take advantage of all the rest of the space on your 8 or 16GB card. But what free tool under Windows can create EXT4 ?
baytee said:
And the P4 (EXT4) you'd resize, as you mention, to take advantage of all the rest of the space on your 8 or 16GB card. But what free tool under Windows can create EXT4 ?
Click to expand...
Click to collapse
You do not have to create any EXT4 partition. Nor any other other kind of partition. All you have to do is expand the FAT32 partition. MiniTool is free and will do that for you.
http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
Edit: And, FWIW, I went and checked. Mini Tool can also create EXT4 partitions, should you want to.
I got that image onto the SDcard, it now has 4 partitions:
BOOT 249MB (FAT32)
350MB (EXT3) 91% used
600MB (EXT3) 3% used
SDCARD 713MB (FAT32)
13GB Unallocated
So I would right click partition "SDCARD", extend it to the 13GB.
But, in his post he mentions one partition (P3,DATA1, which MiniTool doesn't show any partition labeled as such, but I assume he's just talking about the 3rd partition (the 600MB Ext3 partition) being used to store just apps & app data. (I assume since it's EXT3 which is compat w/linux i.e. Android) If so, what do you think..is 600MB enough for downloading/installing lots of apps? Or is it wiser to extend it to maybe 2 or 4 or even GB? For example I have the Humble Bundle games for Android Tablet. The installs (APK) are huge...anywhere from 30-200MB themselves..... I assume their post-install size takes up a different amount of space (more) than the APK itself, just as with Windows EXE installers? And if I recall correctly I believe once installed, you can del the APK... Anyhow, I'm emailing the company to see what install reqs for disk space are, since all they list the APK size.
Only you know how large data partition you need but it sure looks like you need it larger than 600.
So, to add some sort of instructions:
Delete partitions 3 and 4 (the 600 and 713 MB ones)
Apply changes (top left)
Create a new partition 3. Make it EXT4, Primary and the size you want
Apply changes
Create a new partition 4, FAT32, primary to pick up whatever is left unallocated
Apply changes
Don't forget to "apply changes"
baytee said:
...
But, in his post he mentions one partition (P3,DATA1, which MiniTool doesn't show any partition labeled as such, but I assume he's just talking about the 3rd partition (the 600MB Ext3 partition) being used to store just apps & app data. (I assume since it's EXT3 which is compat w/linux i.e. Android) If so, what do you think..is 600MB enough for downloading/installing lots of apps? Or is it wiser to extend it to maybe 2 or 4 or even GB? For example I have the Humble Bundle games for Android Tablet. The installs (APK) are huge...anywhere from 30-200MB themselves..... I assume their post-install size takes up a different amount of space (more) than the APK itself, just as with Windows EXE installers? And if I recall correctly I believe once installed, you can del the APK... Anyhow, I'm emailing the company to see what install reqs for disk space are, since all they list the APK size.
Click to expand...
Click to collapse
Although all apps downloaded from Google Play will reside on /data partition, many apps keep their data separately in the internal user-media partition or on the external SDcard (the 4th /sdcard partition in your case). For example, I have a video game app which takes ~30MB for itself in /data but ~350MB for data storage on the SDcard. The Titanium Backup app works the same way. So you'll have to anticipate not just the app's storage size requirement but also its targeted partition for data storage.
Does this also work for CM 12?
Can these instructions be used with CM12 Lolipop?
panamamike said:
Can these instructions be used with CM12 Lolipop?
Click to expand...
Click to collapse
Yes, if you can find a CM12 ROM image that was specifically compiled to run on SD.
Sent from my BN NookHD+ using XDA Premium HD app
digixmax said:
Yes, if you can find a CM12 ROM image that was specifically compiled to run on SD.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Where can I find that ROM image? I haven't had much luck finding such a ROM, I haven't seen that specified.
panamamike said:
Where can I find that ROM image? I haven't had much luck finding such a ROM, I haven't seen that specified.
Click to expand...
Click to collapse
I am not aware of any CM12 SD-based ROM build for the Nook Tablet, but you can find CM11 SD-based builds for the NT at https://iamafanof.wordpress.com/category/nook-tablet-2/.
Beware, this guide is more or less untested, it will interfere with stuff like memory encryption and OTA or other firmware updates. You have been warned, I assume no warranties for bricked phones, SD cards or lost data.
Many cheap-ass Mediatek phones ship with Android 4.4.2 or later and only ridiculous amounts of internal storage (2GB in my case, CAT B15Q). That may be enough for basic apps, but as soon as you install Navigon or other data-heavy apps (or WhatsApp with a load of videos) you're going to run out of space in no time - and because Google is a bunch of fools, they disallowed app installations to SD cards entirely in 4.4!
So, we're going to move /data in its entirety to our nice huge SD card and be able to use even bigger apps on small phones. It might be possible that this guide works on other phones, but that depends on how they boot and where the fstab and init.rc reside!
Prerequisites:
Mediatek-based 4.4.2 or later phone with root access in recovery (boot it in recovery, run adb shell, therein run id. If it says root, all fine. If not, install CWM)
A large enough SD card (I chose a 32GB card with a 50:50 split between /data and the "external sd card")
Solid Linux knowledge, one Linux PC and one Windows PCs. I urge you to NOT use any kind of VM unless you have experience with USB passthrough.
spFlashTool and the Mediatek drivers from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774, for a flashing guide see http://forum.xda-developers.com/android/help/howto-firmware-flashing-cat-b15q-t2989627
mtkdroidtools from https://www.androidfilehost.com/?fid=23501681358558543 on the Windows PC
mtk-tools from https://github.com/bgcngm/mtk-tools on the Linux PC (no, Cygwin does not work, it messes up the permission bits), cloned on an ext4 partition (not sure if ext2/3 can handle the extended permission bits...)
a network connection between the PCs or a USB stick to transfer files
Take the sd card out of the phone and insert it into your computer. Many laptop SD slots don't like SDXC (>4GB), you might need e.g. a Huawei 3G stick or a SDXC-compatible USB dongle.
Repartition the SD card using Acronis Disk Director, gparted or whatever you're familiar with. The first partition must only be resized (this is the FAT partition), the second partition is a ext4 (!) partition. Both MUST be primary partitions. Acronis and other tools on Windows might require a reboot to repartition SD cards. I recommend a 50:50% split, but if you're heavy on apps or their data, you might go for a 25% FAT: 75% EXT4 split.
Boot your phone into recovery, connect to it with adb in a root shell.
Assuming your data partition is at /dev/mmcblk0p8 (look in /fstab to find it out, followed by mount /data and ls /data to verify), execute the command "dd if=/dev/mmcblk0p8 of=/dev/mmcblk1p2", wait until it is finished. This can take up to ten minutes or more, depending how much data there is.
Shut down the phone, take out battery and SD card.
Insert the SD card into your Linux machine, run resize2fs /dev/sdb2 (or wherever the ext4 sd card partition ended up, check it in dmesg) as root so that the filesystem grows; then eject the SD card and put it back into your phone
Readback your BOOTIMG partition, transfer it to the linux PC (or, if you already have a boot.img for your current firmware, use this one)
On the Linux PC, open a rootshell (to avoid permission issues when building the ramdisk).
Run "./unpack-MTK.pl /path/to/bootimg"
"cd boot.img-ramdisk" (directory might be named different, depending on how you named the bootimg dump file)
Using a text editor, edit the "fstab" file(s) (there might be multiple, with suffixes): From (adjust if needed)
Code:
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
to:
Code:
/dev/block/mmcblk1p2 /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
Now, edit the init.rc file (beware, other .rc files in the ramdisk root might also contain mount commands!).
Search for "on fs_property:ro.mount.fs=EXT4" and again replace /[email protected] (or whatever the node for /data had been) with /dev/block/mmcblk1p2 in the commands in this block (should be fsck, tune2fs,ext4_resize and mount).
Repack the boot image: ./repack-MTK.pl -boot boot.img-kernel.img boot.img-ramdisk/ /path/to/newboot.img
Transfer newboot.img to the Windows PC and flash it using spFlashTool
boot your phone, look in Settings->Memory to see if it went OK!
If the memory view didn't change, also modify the other blocks of on fs_property, in case your device does not use an ext4 rootfs (but yaffs or ubifs instead).
Functionality
It is a good idea, but
Are I still have part of it as external storage?
If yes, it means I can not remove it because there are some apps used it.
If no, it means I will not have external storage anymore!
e.ahmedmahfouz said:
It is a good idea, but
Are I still have part of it as external storage?
If yes, it means I can not remove it because there are some apps used it.
If no, it means I will not have external storage anymore!
Click to expand...
Click to collapse
The SD card is now both internal and external storage! You are not able to remove it because else your system will not boot anymore.
harddisk_wp said:
The SD card is now both internal and external storage! You are not able to remove it because else your system will not boot anymore.
Click to expand...
Click to collapse
what if the sd card is damaged ?
Can my phone boot again..or will booltloop
madthinker said:
what if the sd card is damaged ?
Can my phone boot again..or will booltloop
Click to expand...
Click to collapse
If you manage to kill your sdcard while you have my sdcard hack installed, then the phone will bootloop until you insert a new sd card partitioned just like the old one. Then it will act like you had factory-resetted it.
Alternatively you can always reflash original boot.img/recovery.img and use the phone with limited internal memory.
harddisk_wp said:
If you manage to kill your sdcard while you have my sdcard hack installed, then the phone will bootloop until you insert a new sd card partitioned just like the old one. Then it will act like you had factory-resetted it.
Alternatively you can always reflash original boot.img/recovery.img and use the phone with limited internal memory.
Click to expand...
Click to collapse
i see, thanks to explain me :good:
There is another way to get more space: Link2SD (2.- euros) with a second partition on your external SD-card exactly like shown above (ext4 partition, primary).
The advantage is, that if the sdcard is faulty the system still runs, just the apps which are symlinked to the ext4 partition won't run.
So I use this for all these not absolutely important apps which needs lots of internal memory, e.g. kindle bookreader, Amazon, WhatsApp etc. I dont use it for all apps, most importantly not for any app, where there is no alternative. Last week my two years old 64 GB MicroSD card (SanDisk, with warranty 10 years) in my SGS4 stopped working and this could happen all the time. They are not that reliable I think, that I would put my system on it.
I did this now with the Cat B15Q of my friend.
EDIT: and she has now more than 1 GB free internal space
I think this is the best solution, 2 GB for the pure ROM and the system apps is more than enough and all user apps go to the external sd-card (2nd partition).
good day!
hope you can help me.
what if i want vice versa? because my phone's default storage (0) is sd card.and i want my default storage will be its internal since it is 32gb rom. tried all ways but i think the answer is its boot.img. thank you..hoping for a help