Hi,
I've just installed the imilka's RAM Desire HD v1.0 [A2SD][K:rafpigna 1.7
The problem is now that i made an ext4 partition of 1024 mb but not all my apps are going to my ext4 sd partition.
It seems that after he installed the apps they by half and a half to get the NAND memory and a half to the ext4 partition
also takes after installing an app my internal memory.
This is the manual i followed for installing my rom and make my partition.
From what I read you missed the step about creating a ext3 or ext 4 partition on your sd.
Download gparted live cd and burn it to a cd.
With sd card detected in Windows put in cd and reboot from cd.
Select sd card from top right and check carefully that you have chosen the correct sd!
Delete all partitions and then create fat32 with 1024 mb of free space after.
Then create ext4 partition (both primary)
Click apply.
Reboot normal.
Format Fat32 partition in Windows with 64k clusters.
Copy install files to sd.
Plug in SD and boot phone into magldr, select usb flasher.
Run daf.exe from downloaded zip.
Upon reboot hold power button and select ad recovery.
Choose install zip from sd and navigate to stockhdram1.zip.
If i follow this check on the following link i get a2sd: not found
nickescobedo.com/15/how-to-verify-a2sd-is-working-properly-the-easy-way
which version of the hd2 are you using? eu or tmous?
I'm using the eu version...
also if i go to root explorer and then to the folder:
"/sd-ext/app"
I can see there are a .apk files saved.
If i go to the next path i see the same apk files saved.
/data/app
sd-ext/app-privat is empty btw
Is it possible that he installed the apk files on both partitions?
Mine system memoy increased also after installing root explorer
Hi, I recently installed NAND android build and I'm facing similar problem which I had on SD (this happened to me just 1 out of 3 sd builds). When I want to change my wallpaper (stock walls), I get only few thumbnails and I'm able to set wall only from those which get one. When clicking on those without thumbnails, phone says that my storage is full, although it's a clean and fresh install. Does anybody know what to do about it? Thanks
what build did you install?
NAND is HD2 CoreDroid Desire HD GB V2...and before I used SD MccM 4.5
Danibor said:
Hi, I recently installed NAND android build and I'm facing similar problem which I had on SD (this happened to me just 1 out of 3 sd builds). When I want to change my wallpaper (stock walls), I get only few thumbnails and I'm able to set wall only from those which get one. When clicking on those without thumbnails, phone says that my storage is full, although it's a clean and fresh install. Does anybody know what to do about it? Thanks
Click to expand...
Click to collapse
okay..there has something about the recovery.
different size of ROM use different setting of recovery.
you may decompress the recovery.
for example. Recovery_120M_v3.0.2.4.rar
using TXT to run the (flash.cfg)
comes us:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 120M
cache ya 10M
userdata ya|asize|hr allsize
not very sure it is exactly same to me.
it say that your storage is full, because of your recovery setting.
assume your ROM is 120MB. but your recovery setting is 400MB. your system is using the space more itself. too much space free from the 400.
same like PC. your disk C is using 390GB from 400GB of your whole disk.
main setting is "system ya 120M"
try to make it small by the size of your ROM.
------------------------------------------------------------------------
if u have reduce the space of system. but still storage full.
try to cut up your sd card to help you phone storage.
cut one GB , and format it as ext2 or ext3 to help your phone.
you know android is running under linux system. and ext2 or ext3 is identified by linux.
so..hope it helps.
I formated my SD in FAT32. Ext 3 was then done in CWM (they say it should be like that) and I used 1024/0 ext 3 partition as they instructed in their guide. Probably just some little mistake during the install process. If there's time tomorrow, I'll try to reinstall it and see what happens.
Danibor said:
I formated my SD in FAT32. Ext 3 was then done in CWM (they say it should be like that) and I used 1024/0 ext 3 partition as they instructed in their guide. Probably just some little mistake during the install process. If there's time tomorrow, I'll try to reinstall it and see what happens.
Click to expand...
Click to collapse
all right
good luck~
Hi,
First off if this is answered I am sorry.
I did a lot of searching and was unable to see the answer to this...
I am running CM7.1 off uSD. Install went well, and have no issues. That being said, I am unable to find out where on the card to sideload books. I have booted into CM7.1, turned on USB storage, and have 2 drives appear in win: MYNOOK and CM7 SDCARD. I used the size agnostic image, and it appears that there is only the single partition on the card, and in file explorer, it shows the correct card size for memory, but only the single partition.
The only folders appearing on the card are:
.android_secure
Android
LOST.DIR
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
There is no other partition to repartition (shouldn't have to do that with size agnostic?). I have no problem loading books into the MYNOOK book folder, which I assume is the internal device memory.
Here is my question. How/where do I sideload books to use the storage on the uSD card? Do I have to create the folders somewhere? If so where?
My goal is to utilize the storage available on the card, but be able to read the titles in the stock software. Is it possible to do this without rooting, or do I need to root for any reason to access the right folders on the card for storage?
THANK YOU ALL!!
klewlessnoob said:
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
Click to expand...
Click to collapse
In what way was it not successful? Did the files copy and just can't find them with a reader? If so which reader?
The book I transferred over was not found in the stock software when I opened my library. Is there somewhere specific I am supposed to place it on the card for the Nook to see it? Thanks!
For the stock reader, I think you must use the 1gb area of the internal memory drive, which shows up as a separate drive on your PC when you plug it into the computer. When you are in CM7 and connect to the pc, cancel when it tries to install a device for the NC. Check the notifications on the NC, you need to click a button to enable copying files from your pc, and take care to properly safely remove/eject before disabling that and disconnecting the cable from your pc. Better to get a separate reader and install it from the market (e.g., Cool Reader). You can also install the Nook app from the market, but then books need to go within (possibly in a specific subdir) of the "Nook" folder on SDCARD.
So there is no way to use the card memory to store books if I want to use the stock reader??
Should there have been a "NOOK" folder created on the SD card as part of the CM7 process? Is that a file that the user needs to create? If so, does it go in the same partition as the CM7, as that is the only partition my machine is able to see?
thanks again
Hopefully you'll get more input on this, but I think the point of keeping the Nook stock available (aside from not voiding your warranty) relates to use of B&N books. However you can eject your CM sd card and use another sd card if you want more space for user media for use with the stock app. I thought the media drive was the 1gb area, but now I'm not so sure because on mine the MYNOOK disk is much smaller.
When you are in the stock firmware... you are seeing the boot partition of the uSD...
You can write the boot partition... resize it... then run the installer...
I have done it in the past... set up a 2GB boot partition... then setup the ROM on uSD. You then have a 2GB partition you can use when in stock.
Thanks for the info. I am a bit confused by your suggestion, can you please offer a bit more?
By writing the boot partition, then resizing it, does that mean I can resize now, after I have already set everything up? If so, what do you mean by the installer? Or do you mean I have to wipe the card and start over? If that is the case (start over) do you mean wipe the card, create a small partition for the boot to install on? Would that requre the use of an image that is not size agnostic?
Either way, how do I get the file structure in place on the non boot partition for the nook to see files that are saved there?
Thanks again for any help you can provide!
I have never had luck resizing it after it has been booted in the Nook and all the partitions created...
I have written the size agnostic image to the card... resized the only partition created at that point... then put the ROM on it and booted it in the nook so the installer script (size agnostic recovery) can do the partitioning and install the ROM.
For the question of getting the file structure... I'd have to ask how you wrote the files on the uSD... were you CM or stock?
I had always planned on running cm from the card, so when I wrote the files to the card, I was stock.
If I follow what you are saying, then steps for me to try at this point would be:
1. Reformat card
2. Write the disk image to the card
3. Shrink the single partition on the card (where the image is)
4. Add the CM ROM to same partition as the image
5. Install card and boot device
If this sounds right, I have 2 questions.
What size should the partition be for the image and CM ROM, maybe 2GB?
Will the Nook "see" the non-CM partition and create the file structure for saving files on the 2nd partition at some point? In my searches I saw that in early versions, there was a requirement that the 4th partition on the card be expanded to use for storage, won't I only have 2 at this point?
Thanks again so much for the help!
When you write the image to the card... it will only be about 114 MB.... you will probably want to increase the size to avoid any possible size issues later (with ROM's getting larger)
If you plan to use the stock nook ROM as well as CM7... you will probably want 2 GB boot partition... otherwise if you plan to only run CM7 you probably only want about 250 MB.
You can modify vold.fstab on the stock ROM to use partition 4 of the SD for its SD use... then you could avoid the 2 GB boot partition.
What happens when you use VG's SASD... the boot image is about 114 MB... when you boot it in the nook it creates partitions 2, 3 and 4... 2 and 3 are ext3 partitions, partition 4 is fat... partition 4 is the one set for sdcard in the ROM booted from SD...
This is why you can modify stock vold.fstab to point to partition 4... then both ROM's will be putting stuff on the same partition for "SD Card"
I think I follow that, but my issue is that currently I am unable to see partition 2,3 or 4 which I think is part of my problem.
When I set up the card, I used the SASD method, and all I can see in both win explorer and partition software is the single partition on the card. Should there also be partitions 2,3, and 4? Do I have to do something to make those partitions viewable?
I am not comfortable enough with my skill level to attempt to modify the stock vold.fstab file on the device, and was hopeful that by properly setting up the card, I would be able to keep stock as is, and use the card to multipurpose, ie run cm7 on part and use the remaining space on card to store books to be read in stock firmware. I am still hoping to do that....thanks
As far as only seeing partition 1.... that is a limitation of Windows.
By following the advice pertaining to starting over and increasing the size of the Boot partition immediately after writing the image... before doing anything else... you can provide more space for the stock ROM to use on the SD... it will use partiton 1 (the boot partition) without the other modifications to vold.fstab
ok, confused again
If I start over, write image, then resize that partition with the image, am I going to use the "rest" of the card, NOT in that partition to use with storage? OR am I going to resize the partition with the image to be big enough to use as the partition to put books on?
If it is the former, don't I again run into the problem of how to find the other partitions, or will I create them when resize the first partition after writing the image?
Thank you!
You will only ever see the first partition of the sd card when booting from the stock OS. Also with the card inserted in a usb flash card reader on Windows you can only mount the first partition as a drive letter. But you can see and resize partitions with contiguous unallocated space using MiniTools Partition Wizard.
OK thats good to know. Do you know if the SASD install should have created other partitions when I installed to the card? The reason I ask is that even in Partition Wizard, I am still only able to see the 1 large partition with everything in it.
If I start over again, will I need to use the wizard to create partitions first, then write the image to the resized 2 GB first partition, or should I write image to card, resize the first partition? If the latter, will resizing the first partition autmatically force the other partitions to be seen? I am not sure of this option, as I can't see where in the process the other partitions are created? Is this part of the process when CM7 boots?
Thanks!
Write the image. Safely remove from pc. Reinsert to pc. Use minitool partition to resize the (only, at that point) partition to the size you want. Use Apply in minitool software. Quit minitool and resume with the card setup.
does the minitool at that point (resizing) create the other partitions, or will the card setup do that? Do I have to do anything else to the other partitions to make them visable to the stock nook so that they can be used to access books while in stock os?
The card setup will create the other partitions. The stock os is never going to see anything but the 1st partition. You would need a terminal emulator or rooted file explorer installed in the stock os in order to mount another partition.
If that is the case, that stock os will never see anything other than the 1st partition, then there really is no way to accomplish what I am trying to do, correct?
In other words, put CM7 on the card, then when I want to use stock, boot into stock and have the reader find books saved on the card?
Hello,
there are now a great many solutions on the market over with devices some small internal memory has the apps on the external SD map to link/shift.
At Ace for example only 178 MB are for order for system programs and system-relevant apps. These system-relevant apps (Launcher, Widgets, Google Play…) occupy however a majority of the internal memory.
I had this problem already with my old Archos 101, gen. 8 . There with the development of CM9 for the Archos (Thanks Biscuite) a very good solution developed like one the internal memory without shifts the apps to increase can would like I gladly with you in Ace Thread to discuss.
With the solution on the Archos an image a file produced in then the all system programs and apps to be installed. With the Archos by me a 512 MB large image file was used.
Enclosed a few screenshot it storage allocation of the Archos. I can install my desire apps without problems (without to shift, without supplementary Software, upto 512 MB).
http://forum.xda-developers.com/showpost.php?p=32909358&postcount=1
Since I am not a developer and thus programming cannot operate places I you the question whether this also for Samsung Ace would be feasible.
Try this: http://forum.xda-developers.com/showthread.php?t=2296055
my solution with CronMod-INT2EXT+
Simply the file download, which SD map format completely Fat32, into which revovery fashion go, Advance option, partition SD Card, 1024 MB to select, none swap (with it you format your SD Card in two partitions, 1st Fat32 / 2nd ext3). The file CronMod-INT2EXT+ in the root of the SD copy, into which Recovery fashion go, mount sd-ext, install zip from SD Card to select, then the file CronMod-INT2EXT+ to install, reboot.
File CronMod Int2Ext open, file 40int2ext out copy and in ace under /system/etc/init.d folders insert, now the rights of access in rwx rx x change, save, reboot, afterwards your internal memory with 1024 MB is shown to you.
Functioned very well.
http://forum.xda-developers.com/showpost.php?p=27538212&postcount=1
http://forum.xda-developers.com/showpost.php?p=41846228&postcount=1
Thanks for your support
mika67 said:
my solution with CronMod-INT2EXT+
File CronMod Int2Ext open, file 40int2ext out copy and in ace under /system/etc/init.d folders insert, now the rights of access in rwx rx x change, save, reboot, afterwards your internal memory with 1024 MB is shown to you.
Click to expand...
Click to collapse
can someone rewrite this for me? I don't understand.
paradoxiumwind said:
can someone rewrite this for me? I don't understand.
Click to expand...
Click to collapse
Open the file “CronMod-INT2EXT+_signed.zip”, file 40int2ext copy out, in Ace folder /system/etc/init.d insert, rights for OF ACCESS in rwx rx x CHANGE, save, afterwards your internal MEMORY reboot with 1024 MB is shown to you.
http://forum.xda-developers.com/showpost.php?p=51524943&postcount=52
GUIDE
Hey there,
You want to increase your internal storage. I'll explain you how:
You need to partition your SD-card (You can do this with CWM-recovery 5.x.
After that you need to download the correct kernel patcher by PSN, If you use stock rom I prefer the PSN_batteryextender, you can google for that If you are not on stock, you can try other PSN-Kernel patchers (GOOGLE ;p )
So flash the Kernel, and your current data will be moved to the SD-card, the size of your SD partition is now your Ace internal storage :good:
GI0\/\NNI said:
After that you need to download the correct kernel patcher by PSN, If you use stock rom I prefer the PSN_batteryextender, you can google for that, If you are not on stock, you can try other PSN-Kernel patchers (GOOGLE ;p )
Click to expand...
Click to collapse
I can unfortunately find more patcher no by the CM11.
Can you help me?
thanks
Off course, at this monent there's no CM11 kernel patcher available. But good news! PSN and I are working on it but it needs some bugfixes and testing. I'll tell you when it's finished!
As alternative you can temponarily use Cronmod's INT2EXT scripts, (A little bit slower)
Regardzzzz
Hello, in this thread I'll show you how to move the /data partition to your microSD card in order to increase the storage space, and bypass the speed limits of our poor eMMC memory.
Disclaimer:
I'm not responsible for any data loss or any other kind of problems. Follow the tutorial and everything will be fine. In case of problems, reflash the boot.img of your ROM or reflash the whole ROM and you'll reboot to Android using the usual /data partition.
Pros:
more storage space
slightly shorter app loading times
Cons:
you cannot eject your SD card from your phone when it is turned on
Requirements:
a computer
some kind of adapter to put the microSD into the computer
a 16 GB (or higher), class 10 (or better) microSD
Any recent L (untested), M (tested) or N (tested) ROM and TWRP 3
these two zips: https://www.androidfilehost.com/?w=files&flid=113749
Step 0: prepare the SD card
using your computer, shrink the only partition you have on your SD card and leave at least 6 or 7 GB of unallocated space. Be sure not to shrink too much the first partiton (which will continue to be used as a normal storage partition) because you'll have to store a nandroid backup in it! This is why I recommend you to use a 32 GB SD card. Then create a new partition using the unallocated space. If you're using Windows or OS X, create a fat32 partition, if you're using Linux, create an ext4 partition.
Step 1: patch the recovery and backup, then restore
In the AFH folder I posted in the requirements you'll find two zips. Download them and reboot to recovery, then take a nandroid backup of your /data partition and store it on your SD card (TWRP will automatically use the first partition of the SD card, the one with all your current content). Now flash twrp_fstab_patcher.zip. Power off your phone and then turn it on and boot into TWRP. Now go to Wipe > Advanced Wipe > select Data > Change Filesystem > choose ext4 or f2fs (as you prefer). Confirm and check that the Data partition has been formatted to the chosen filesystem. Restore the backup you've made.
Step 2: migrate the data of the internal storage
Reboot to Android and using a file manager that lists both of your SD card's partitions (FX works for me) and copy all the content of your internal storage (photos, music, app data etc.) to *2nd_sdcard_partition*/media/0.
Step 3: patch the kernel
Now you're ready for the last step. Flash kernel_fstab_patcher.zip and reboot. The end!
Warning: you need to reflash kernel_fstab_patcher.zip after you change/update ROM/kernel otherwise your phone will use the "old" data partition! Similarly, you must flash twrp_recovery_patcher.zip each time you update TWRP 3 (this doesn't happen very often).
Well, I hope I put all the needed info in this thread, I'll keep it updated with my latest suggestions etc. If you have got problems, report them. If you find something that doesn't make any sense in this post, tell me. Enjoy!