Hi guys,
I'm cooking a WM6.1 ROM with a small set of applications using osKitchen Zero v1.33.5. This gives me lots of free space on the user partition. I have been searching for way to redefine the partition sizes and shrink the user data partition, but haven't found any information regarding this.
Does any one know how to do this or is it even possible?
Thanks
jlsaraiva
Any reason to shrink it?
The idea is to use the remaining space to create the android partitions and boot android with haret from the WM partition. Having both WM and Android on NAND.
Well, that's the thing you can't do via ROM. At least I think so. You need some extra storagemanager drivers.
sounds intriguing though at first - moving the ext2-partitions to nand and telling haret to look for them there instead on sd. you'd still have to boot winmo first, but android would be faster. "semi-nand-flash", kinda.
but thinking about it - not enough internal memory for two os on the x1.
Dont think this is possible just yet. Like your thinking of having two os on internal memory but especially with us poor EURO 512mb devices I dont think it could cope. It would also mean a resdign of haret.exe as it looks for android on SD card.
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
jlsaraiva said:
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
Click to expand...
Click to collapse
This could be a nice idea as you could in theory have android running on nand with out the limitations of either magldr or clk. You would be hard pushed to get a sense build running, but a gingerbread version would be cool! I assume you really have to strip down WM to get it to fit?
I remember looking into this a long time ago before magldr came out and found out some registery keys that could run hart.exe and clard.exe for you with out any user input. I'll see if I can digg them up for you!
I removed almost all EXT packages plus some microsoft apps like office, windows live etc...
But all this falls short if we can't resize the WM partitions.
I've been looking into re-partitioning the NAND on my Xperia X1, so I could increase the storage space when using a smaller rom, but I also have not found a way to do it.
I was originally hoping there was an app, either in Windows mobile, or android, that would work as a partition manager, but I have only found apps that will partition SDcards.
Another option I'm thinking of is using a linux partition manager in android, or using a full blown linux on my phone and using a linux partition manager that way.
I've also thought of using mtty, but I don't know any commands that will let me manipulate the partitioning.
I actually have no idea if any of this will work out, I don't know how the whole boot-procedure works, so I don't know if the bootloader expects the WM-rom partition to be at a certain address, or if it just goes to a certain partition, regardless of the starting and ending positions.
Related
Hey guys,
I'm going to try making an Android ROM. It will be a bare-bones WM ROM with the necessary Android files built in.
It will run Haret at start up, but you have the choice to not run it if you don't choose to. (in case Android acts up).
I'm booting up Android right now from my ROM (not SD card).
I'll let you guys know how it goes
PLEASE REPLY WITH THE SIZE OF YOUR DATA IMAGE!!!!
awesome, sounds good.
I'm definitely game. Let us know when you've got it up!
How big is everyone's data file?
i just wanna be clear on what you're doing here. so, you could take your SD card out and still run android, correct?
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
data.img is 128mb.
128 MB here
128 Mb for me!
Okay, I think they are all set to 128MB, and then say how much is free. Right now it has space for the 128MB.
I am going to make it copy the files from the SD card to /Program Files/Android, and then have Haret start (with the option to run or not).
I am not seeing a super large speed boost, but it is a little faster, and seems to be more stable.
craig0r said:
i just wanna be clear on what you're doing here. so, you could take your SD card out and still run android, correct?
Click to expand...
Click to collapse
Correct
craig0r said:
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
Click to expand...
Click to collapse
It is a little faster (since it isn't using the SD card), and is a lot more stable for me.
Would it be feasible to run a script in WinMo to check to see if there is a newer version of the android files and prompt to update them if the files are newer?
what filesystems are you using for the system and data? Are you using file-backed storage or direct access to the memory device? You won't see as much of a speedup if you are using file-backed storage...
You also will want to modify initrd to change the memory settings, I can do that for you if you like...
derekwilkinson said:
Hey guys,
I'm going to try making an Android ROM. It will be a bare-bones WM ROM with the necessary Android files built in.
It will run Haret at start up, but you have the choice to not run it if you don't choose to. (in case Android acts up).
I'm booting up Android right now from my ROM (not SD card).
I'll let you guys know how it goes
PLEASE REPLY WITH THE SIZE OF YOUR DATA IMAGE!!!!
Click to expand...
Click to collapse
Are you putting a yaffs2 partition on the nand flash for data or using a loop mounted file on top of tfat. How about the system image? There should be a significant speedup from using the nand flash. Also, how are you passing the partition information to the kernel?
craig0r said:
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
Click to expand...
Click to collapse
True, it isn't an android rom... but most of the slowness we're experiencing is due to a slow bus interface to the SD card, and slow write speeds to the SD.
If properly accessing the internal memory, there should be significant speed increases.
EDIT: By the way, if you are just using an ext2 data.img sitting on the tfat partition, you are likely to see bad things happen to your internal memory.
ext2 doesn't do wear leveling, and the internal flash controllers also don't do wear leveling. TFAT is set up to do it, but if you are just reading it as FAT, it won't do it... you want to access the memory directly and set up a yaffs2 partition.
vilord said:
what filesystems are you using for the system and data? Are you using file-backed storage or direct access to the memory device? You won't see as much of a speedup if you are using file-backed storage...
You also will want to modify initrd to change the memory settings, I can do that for you if you like...
Click to expand...
Click to collapse
Honestly, I just made a super small ROM so it could run the Android files more stable (since it isn't on the SD card).
How can I have direct access to the memory device?
well to start, how do you get to the files now?
I'm going to guess that you turned on kernel support for the internal memory, which makes it show up like a block device, then you are mounting the windows TFAT userdata partition, then mounting system.img and data.img as loop.
What you would do for direct access isn't all that different...
Right now you have a *very* small windows rom, which leaves a large space for userdata. You'd need to force the tool to leave an open space at the end of the flash, then you'd use a linux tool to mkfs.yaffs in that open space. It is similar to a hard disk (with a different partition table), except that you want to use yaffs or jffs2 to enable wear leveling.
vilord said:
well to start, how do you get to the files now?
I'm going to guess that you turned on kernel support for the internal memory, which makes it show up like a block device, then you are mounting the windows TFAT userdata partition, then mounting system.img and data.img as loop.
What you would do for direct access isn't all that different...
Right now you have a *very* small windows rom, which leaves a large space for userdata. You'd need to force the tool to leave an open space at the end of the flash, then you'd use a linux tool to mkfs.yaffs in that open space. It is similar to a hard disk (with a different partition table), except that you want to use yaffs or jffs2 to enable wear leveling.
Click to expand...
Click to collapse
I took a Vogue ROM, stripped everything out, and copied the Android files from my SD card to the device.
Did you change the initrd and zImage at all? I would think you'd need to change them to tell the loader to look at the internal memory instead of looking at the SD card...
soo when will this rom be ready? also will the base system be winmo 6.1 or 6.5?
fixxxer2008 said:
soo when will this rom be ready? also will the base system be winmo 6.1 or 6.5?
Click to expand...
Click to collapse
When I get everything running as fast as possible.
I'm about to write the scripts to make everything work easier
(like copy your current default.txt and data images to the device so you keep your data) and maybe automatic updates (haven't decided how i'll make it work yet).
This is probably a daft question but the TmoUS HD2 has 1gb ROM, so when we create partitions for CWR why dont we use the entire 1gb? It has an additional 500+mb of RAM to allow everything to run smoothly. What am I missing here? Why is 400mb the recommended size? Doesnt that just leave 600mb going to waste?
Thanks for any clarification.
It may not necessarily be daft, but it certainly is in the wrong forum.
You are completely not understanding how things works, you are messing ram with rom, you are messing cwr partitions with sd partitions..you are messing system partition with userdata partition.. summarizing: you are doing so much confusion that you will dont know also your name in some minutes
And, btw, wrong section.
btw I'm in a kind mood today:
When you flash CWR, all your availabe ROM will be used for data storage. The "400mb thing" is just for system partition, where the build will be stored
If you se a build that uses SD to store data, your availabel ROM is wasted also if you still need to use the 400mb thing (or less if the build is smaller)
Your RAM are never touched from those things.
First, not sure why this is the wrong section as it directly related to NAND/CWR, but thank for the psudo moderation.
Rafpinga: I'm not concerned with SD partitions, Don't use them as I have no need, but i gather the gist of your answer is that my 400mb ROM partition is strictly for the system (OS files) and the remainder of the 1gb will be used for data? That makes more sense.
So I basically have 1gb of ROM (700 something formatted), 400 is used for system/OS and the remaining 300 something is available for apps etc..?
Ok, I thought I had my answer but apparently not. How am I confusing NAND and SD partitions? I don't use SD partitions at all? I use NAND partitions only as far as I can tell. What did I miss? I didn't even mention SD partitions in my OP.
I have a 400mb System partition, which is on NAND, the remainder of my NAND is used for data correct? My SD card is irrelevant to this setup correct? I don't even need an SD card inserted for my setup to work...
If i'm confusing the two perhaps someone would explain how rather than just *****ing about the thread!.... If it's in the wrong place I'm sorry and I'm sure it'll get rightfully moved but that shouldnt negate trying to get an answer.
OK, you're all over the map, but lets do the quick rundown.
A partition is a chunk of named memory-space. aka c: in windows or the swap file in linux.
SD cards and internal ROM are essentially hard disks that can be written to. The ROM needs to be flashed, while the SD cards internally flash too. What you can do is partition either of them and name the partition. You can also choose the filesystem that a particular partition uses. Internal ROM for android needs to be partitioned into a proper linux filesystem with proper formatting to operate. One of the partitions is userspace, another is "system". SD partitions are extensions to the linux operating system and as such should not be considered "bad". Really, the more memory the better.
Random Access Memory (RAM), i believe some type of DDR in this phone, is a volatile memory that clears upon restart. It's only used during normal operation and never stores your Android.
Read-Only Memory (ROM) is NAND in this case. There is a large misnomer on these forums about NAND. They meant to call it Internal NAND. ROM, the 1gb, is where ALL operating system files are stored. You flash the bootstraps and system partitions once, then all your stuff is stored in a separate portion of the ROM.
NAND is the storage technology used to manufacture most consumer read-only memory(ROM). SD cards and the internal memory both use NAND type memory, the difference between the two is the bus speed between the internal NAND and the CPU.
On the TMOUS HD2, there is 1,000mb of space in the ROM. A 400mb system partition would leave 600mb for things like the swap file and the user data portion. In some cases, ie EU version, a 400mb system partition would eat the ~500mb available ROM, so developers figured out a way to partition the SD card and effectively expand the ~500mb to 1,000mb and beyond. APP2SD+ was the final solution.
The TMOUS when partitioned properly will have a huge amount of headroom for the Android to excel. Nothing really goes to waste as long as you use a TMOUS compatible ROM.
Next time, ask in the right forum and you'll get the answer you wanted without all the hassle.
Thank you. I really appreciate that explaination and again, sorry for being in the wrong forum.
Sent from my HTC HD2 using XDA App
Ok, now that the whole NAND/RAM/CWR thing is cleared and little badgering, I'll move this thread to the Q & A section. If you see a thread in the wrong section, just report it. Once you've posted the question in the wrong thread, there is nothing the OP can do to move it. So if you can answer then please do. This way when a MOD moves the thread to the correct place it has some useful information. So I'm deleting the SPAM/light Flaming and moving this along.
noellenchris
HD2 Forum MOD
Is there a way to do this? I currently have a dual boot of WP7 in NAND and SD android. Not being able to share data is kind of a bummer.
If there isn't already a way, I am thinking of taking this on as a development project, is there anyone knowledgeable about writing applications to mount file systems that can point me to something I can start with?
Thanks
I think mounting the Wp7 partition in Android will be absolutely useless, from what i read about wp7 storage management, it seems that the SD Card partition is used by WP7 in raid mode, so data is shared and written across both nand and sdcard partition as if both were just one single storage memory (for faster operation)..so even if mounting the partition in android was possible we could not read the data from it (because it's not all there..) and if we copy files to the wp7 partition, the wp7 OS would not recognize it after reloading the sdcard...even worse we might even loose all the data from the original wp7 partition, because MS has blessed us with an inteligent OS autorecovery system..meaning if data is found to be different or corrupted in filesystem (raid system..actually) WP7 will automatically reformat the storage partiton to restore phone functionality. Remember those annoying WP7 resets?!
hypothetically if you could get an SD android build to read NAND somehow then it could read the full raid partition, but this is pretty unlikely.
how about the other direction? that is getting WP7 to read the FAT32 partition.
babablue said:
how about the other direction? that is getting WP7 to read the FAT32 partition.
Click to expand...
Click to collapse
Seems like WP7 Couldn't read or write on FAT32 or every other File system. It's Awkward.
What the hell were WP7 Developers thinking?
they wanted to be like Apple.
Hi,
how are you today? For me good, thanks for asking, ha ha ha hanb
It's alredy my second thread for today, all problems, wow.
So I will try to explain, like in the thread before, I got HTC HD2 and I have Mdeejay eVo on my sd card and I launch Android from WM6.5.
The Android which I use have already the data_1024 folder, inside data.IMG file which it use for storage the Androids apps, but from my research I find the news to some how edit my microsd card and set-up a Partition which be the sobstitute of the data_1024.
I will be glad to know HOW?
Like I said, I got my Android on sd and I try for a week to find the solution with no success, I try to make a ext3 partition on sd of 2048mb but the android do not see that partition. I can't flash anything because on my ROM is WM 6.5.
I also will be glad to make another data_2048 folder with inside data.IMG file, if the Partition can't be done.
Please guys let me know how do I have set-up the partition for the Android?
Thanks.
hmmm not really sure here, but you can make a back up of your SD card then use minitool partition to partition & create EXt3/ Ext 4 / Fat 32 partitions, try the links below they might help
mengfei said:
hmmm not really sure here, but you can make a back up of your SD card then use minitool partition to partition & create EXt3/ Ext 4 / Fat 32 partitions, try the links below they might help
Click to expand...
Click to collapse
before post here I already saw your thread and like I said I do not have MALGDR on my phone or CWM, also I don't know which type of partition need my Android but I am sure is not the last type of Androids which they have the folders; kernel, META-INF, sdcard (inside NativeSD) and system folder. My Android is whit rootfs.img with external data_1024 folder for storage system.
I used Gparted live and I made a partition of 2048mb of ext3 partition but the Android do not see the partition because somehow I can't make a link to it.
I want more storage for my Android and delete data_1024 folder so I try to figure out, with some help, how to do that?
Any ideas?
Use toporesize app on pc to expand your present data img size without losing present data. . To get more space. .No need for ext 3 and all
Search for topo resize
If youwant to use apps 2 sd or link 2sd app from market to use ext 3.. Then you can move apps to sd ... That is for nand installs. . You don't need that on sd builds. ...
You try native sd builds. . Fastest ever.sd builds. . You can boot from wm also . You need ext4 partition for it. ..
sent from my galaxy note 2 (7100)
pakure said:
Use toporesize app on pc to expand your present data img size without losing present data. . To get more space. .No need for ext 3 and all
Search for topo resize
If youwant to use apps 2 sd or link 2sd app from market to use ext 3.. Then you can move apps to sd ... That is for nand installs. . You don't need that on sd builds. ...
You try native sd builds. . Fastest ever.sd builds. . You can boot from wm also . You need ext4 partition for it. ..
sent from my galaxy note 2 (7100)
Click to expand...
Click to collapse
Thanks mate, this is something great!
So I do not need a special partition for my android, good to know.
I know the last Nand Androids are good but I have old phone with old Android and he work fine, I try to put Native SD Android on my sd but too complicated and I do not have so much time. At the moment I find Mdeejay very fast and good, I tryed AmeriCan Android, CM7 and 10 and really I am not comfortable with them like with Mdeejay, so it's ok like that. ! problem solver, I just try to update my kernel - http://forum.xda-developers.com/showthread.php?t=1976835 - and I am ok.
Thanks.
pakure said:
Use toporesize app on pc to expand your present data img size without losing present data. ....
Click to expand...
Click to collapse
End of the Party, Guys, I was happy to soon!
I used toposize to made data.img for my android but I got problems.
If I resize data.img system partition, first of all, I got the error on e2fsck (see the pic) and i have to click ok to compleate the operation and after that I put the data.img into Anrdoid forlder and I replace the original (backups before) but the Android do not turn on, he stuck in HTC Logo.
If I made a clean data.img with ext3 system partition and I replace the data.img into the Android folder, he do not turn on and he stuck in Android logo.
If I use the original data.img from the package the Android turn on normally.
Do I forgot to do something? Do I missing something?
sorry, I forgot the pic.... here we go...
eclyptos said:
sorry, I forgot the pic.... here we go...
Click to expand...
Click to collapse
you are keeping data .img in a folder?...data.img should be in android folder..no further subfolders...and delete that stupid ext3 partition..you dont need it.
try native sd..it is very simple (for you to dual boot with windows mobile):
you need ext4 partition..use minitool partition manager to create it
then put selected rom zip (like pacman hd2 rom..."the best rom") on sd card
put 4ext recovery folder on sd card..open it , click clcrad and haret inside...follow screen instructions to install rom
Reboot and boot the ROM by executing the usual clcrad and haret stuff inside the NativeSD folder.
thats it.
pakure said:
you are keeping data .img in a folder?...data.img should be in android folder..no further subfolders...and delete that stupid ext3 partition..you dont need it.
Click to expand...
Click to collapse
ohh, well, yes, the data.img is in Android folder, not subfolders or external folders, I said so because in my package of Mdeejay are 2 folders, Android and data_1024. The data_1024 is all ready done to make a fast boot instantly but if I do not use it Android make the clean data into his root folder.
About the partition you get confused a little bit because when I used toporesize to made a clean data.img file to use it in android folder, the app ask me in which system the file have to be, ext2, ext3 or NONE. So no 1 of this data.img worked.
I hope I clarifide, I do not have ext3 partition on sd, is the data.img. that's all.
pakure said:
try native sd..it is very simple (for you to dual boot with windows mobile):
you need ext4 partition..use minitool partition manager to create it
then put selected rom zip (like pacman hd2 rom..."the best rom") on sd card
put 4ext recovery folder on sd card..open it , click clcrad and haret inside...follow screen instructions to install rom
Reboot and boot the ROM by executing the usual clcrad and haret stuff inside the NativeSD folder.
thats it.
Click to expand...
Click to collapse
I don't know about that, currently I have a working Android (not jet set-up like I want too) but I will see if I sholud do all this stuff. I am not so deep in this stuuf and just reach when I reach now, get me tired. So I take in the consideration you advice but now I have to have 1 android working well.
Ok, some bad news:
I did in different way to set-up my storage image, I let Android to made a clean data.img into his folder, after he finished installation and start running well I take the data.img of 1GB and with toposize I resize the image to 3GB. Like I said before, he give me this crap error but I really do not understand why? If Android made a clean data.img in his folder which errors can be made?
So I click ok anyway and made this file and I replaced the 1GB with 3GB with unclarifide done error fix.
He works for feew hours, smooth and fast, I start installing appps and games. Like many games they ask for downloading some updated files so I start downloading 450mb for 1 game and after 20 minuts Android crashed and he do not turn on anymore, he stuck in Android logo.
Are you sure this crap "TOPOSIZE" working? or it's just ME?
Guys, please help, I get confused and I don't know how to do it.
Today I also try install on my android Chainfire and i can't install plugins for low storage so after few hours of serching I find this thread http://forum.xda-developers.com/showpost.php?p=16457164&postcount=14723 but after read what they saying I do not understand anymore which system file I have to resize to get more space AND to make working chainfire which I really need right now for few games!
Someone can tell me which files I have to resize? How? or Post the right thread? please.
Like everyone here, I have the famous HTC Leo. A friend installed Android on NAND, the 2.3.4 with the mod-HyperDroid CM7-v2.1.0.
This is a great device, but the more I use it, the more I have less internal memory.
At first, I installed a lot of applications, I was full of things and I ended up filling the internal memory. I moved the more applications possible on the SD card, but the internal memory ended up being full. So I uninstalled applications not too useful, and applications more useful, clean caches, remove data, but it is still too small. My system tells me that I only have 217.3 Mb total internal memory and while I hardly more than application system installed, I only have 21.3 MB available. Now, I know that this model has double.
I do not understand: what is this devilry? Where is my memory? How can I resume normal operation until all the memory is gone and my phone becomes unusable?
I can't be the only one to whom it happens, right?
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
samsamuel said:
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
Click to expand...
Click to collapse
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Click to expand...
Click to collapse
so, pretty much exactly what i described, then....
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
Click to expand...
Click to collapse
So, I don't really need to use this. I just can install a new ROM on my NAND after making extending place on my SD for the 'dataonext', can't I?
I have to choose a dataonext ROM (with french version) and make new partition on my CD card. I'm saving all the SD card data's just now (with luckyBackup, because I'm on ubuntu PC).
My problem is find a good ROM for my needs. So, I have HSPL 2.0.8 and MAGLDR. How can I find the rom radio number? I need this information to choose the good ROM. Any advices about good ROM for my needs?
r no need to change the radio,,, if magldr works then the radio is fine.
samsamuel said:
r no need to change the radio,,, if magldr works then the radio is fine.
Click to expand...
Click to collapse
I bought a new 16 GB SD card to try the method of post 1843062. I am trying to format as it should, and tonight or tomorrow, I'm trying to see if I can install the script without too much risk, I am not a very experienced user of ROM for HD2 and, in addition, as I'm 100% Linux Ubuntu, I saw that many procedures are more complicated or impossible to run from a Linux desktop.
Thank you for all your help and I'll let you know.
I need to understand.
I have a EU HD2 with HyperDroid CM7 installed on it.
Like many people here, my memory became too small over time. So I look for a solution and I was guided to this thread. While speaking, I read everything I could understand (and frankly there really is too much to read and understand, here ) and I ended up deciding to adopt the solution Kokotas.
So I bought a new SD card (16GB class 10 Duracell - I know, Duracell is a brand of batteries ...) and I formatted properly Gparted as shown, with one primary partition of 12 GB fat32 I named /données (French for datas) and a second primary partition 4 GB Ext4 I named /data.
Then I primed to install the script Kokotas (but I have not yet done so, this is the trick!) And there: surprise!
I suddenly 4 times more free memory internally (from 20 MB to 80 MB), but it is still the same overall size!
I wonder how it is done, because it's been months that I want to release the NAND memory, I deleted almost all my applications downloaded without great effect and there, before installing the solution Kokotas, hop, I have the place!
I run Nautilus on my HD2 connected via USB and what do I see? in the partition /data in ext4, records were Cres /app /app-private and /dalvik-cache.
What does that mean? My ROM can do one DATAtoEXT 2011 alone, when she sees a partition SD / data?
Do I install the script Kokotas or it is not worth it?
Do I flash a new ROM (I thought MIUI-MIX_3.3.1, but I'm not sure it's a good idea) without risk, in short I need to understand what happens with my phone.
Thank you.
(Sorry for my english : this is the fault of Google translation )
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
orangekid said:
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
Click to expand...
Click to collapse
I thought NAND is better for battery's management...
Monolecte said:
I thought NAND is better for battery's management...
Click to expand...
Click to collapse
I didn't see any great battery improvement with NAND.
ROM flashing don't work
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Monolecte said:
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Click to expand...
Click to collapse
use the nand toolkit
samsamuel said:
use the nand toolkit
Click to expand...
Click to collapse
With an Ubuntu PC?
After miles of thread reading here, I won against the machine!
I have something like a new phone.
Thank you everybody.
If I can do it, anybody can do it!
ubuntu or windows will be fine.
The NAND Toolkit is a Windows software... so...