OK, not that much of a noob (or at least dont think I am!) have been playing with android for some time, and have decided to cook up my own rom based on DesireHD. After some failures I now have a good stockish rom that I like and will release once i can sort out a few problems that I have.
I want to go down the CWM .zip route so I can release updates easily, off to the forums I went with a few questions... hours and hours of searching and researching and a few test runs later... have even more questions!!!!
1. EuroHD2 (Leo512) has 512mb ROM > how much of that ROM is actually available?
2a. When does the kernel load the SD-Ext partition?
2b. With CMW Recovery do you have to set a "userdata" partition when using SD-Ext data, or can you get away with not setting one?
3. Does CMW support using SD-Ext userdata
4. Is the 400m CMW Recovery only for the Leo1024?
5. What is the maximum size for the "system" partition on Leo512?
6. What is with all the questions??????
As you can see, many questions. Most have come from searching the forums and becoming more and more confused with it all!!
Please help!
SquithyX said:
I want to go down the CWM .zip route so I can release updates easily, off to the forums I went with a few questions... hours and hours of searching and researching and a few test runs later... have even more questions!!!!
Click to expand...
Click to collapse
Good idea.
SquithyX said:
1. EuroHD2 (Leo512) has 512mb ROM > how much of that ROM is actually available?
Click to expand...
Click to collapse
All of it.
Partitions:
misc 1MB
recovery 5MB
boot 5MB
system 150MB to 350MB
cache (optional, but people like 10MB)
userdata (whatever that remains, 350MB system partition size = 50mb userdata)
SquithyX said:
2a. When does the kernel load the SD-Ext partition?
2b. With CMW Recovery do you have to set a "userdata" partition when using SD-Ext data, or can you get away with not setting one?
Click to expand...
Click to collapse
yes, sadly, you still need the userdata partition, you can go around it by creating another partition on the SD card, and call it userdata, I am assuming that works too. So now your SD has userdata, sd-ext, fat32 partitions.
SquithyX said:
3. Does CMW support using SD-Ext userdata
Click to expand...
Click to collapse
urm, that's not CMW's job, that's your job.
You can either use DATA2EXT method which puts all userdata in SD card, ext2/3/4 partition or A2SD+ which puts all your data on the SD card, minus I don't know what, because it keeps reducing and I never figure out what. I am lazy to use adb.exe to go check.
SquithyX said:
4. Is the 400m CMW Recovery only for the Leo1024?
Click to expand...
Click to collapse
Yes, because you really ran out of space. 350MB system partition, gives you less than 50MB of userdata partition provided you have 10MB of cache partition.
I was wondering that...
So if I create a "userdata" partition on the SD card the system should use that... meaning no userdata partition on the NAND... meaning SD-Ext and Data2SD features are not needed?
But then surly if it was that easy somebody else would have done it?!
The layout I am thinking is:
NAND/
--/misc (1mb)
--/boot (5mb)
--/recovery (5mb) *Is this needed? - Is this not for the recovery programs that we have on SD?
--/system (350-400mb) *theoretically upto 491mb as no userdata on NAND
--/cache (10mb)
SD/
--/userdata (1gb) *Could be bigger, but have read that it can cause corruption if over 2gb
-Fat32 (leftovers)
But all of this comes back to Q2a. When does the kernel load SD partitions?!
Other idea is to set the "userdata" in NAND to set size and grow the "system" partition and carry on using SD-Ext and Data2SD for internal storage, something like:
NAND/
--/misc (1mb)
--/boot (5mb)
--/recovery (5mb)
--/cache (10mb)
--/userdata (50mb)
--/system (leftovers) *441mb
SD/
--/Ext (1gb)
-Fat32
But then does the "system" partition have to be created 4th and wont work if created last???? And what about all the plastic trees, where do they go?! My head hurts, i'm cold and there are wolfs after me!
I am guessing that creating userdata on sd card might work, but I don't know how your build mounts partitions, so that is your job too.
but you should read up on data2sd, data2ext, a2sd+ and a2sd
No, you can move the partitions around, it worked for me.
Related
Ok, now im wondering, is the cache directory in system supposed to be connected to the cache partition that gets flashed in some roms?
For example, say i look at my root dir on my phone, i go to data and it lists the used and free which combined, is the auto sized amount of my data partition, if i go to system,the used and free combined is tha size of teh system partition i have (i used cwm and in my case its 410M) now i flashed a cache partition (of 10M) so i had assumed that the cache dir in root was linked to my cache partition, so the amount used/free combined would be 10M, but instead its the same size as of my data partition.. so i know that its using that partition instead..
is it supposed to be like that?
what use is the cache partition?
also, does anyone think there would be a benefit if the system partition was in ext3 format instead of yaffs? i know that most oem roms come with the system partition set in ext3 format, would that ever be possible with magldr?
thanks.
Anybody got 2 cents they can throw in?
cmon, any answer at all would be nice from anyone..
It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).
Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount) and for Read Only. Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.
greg17477 said:
It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).
Click to expand...
Click to collapse
hey first, THANK YOU for commenting. ok, thats interesting, i have always seen it suggested to use a 10 -40 mb cache partition, ive also heard that market can have some weird effects such as not being able to download if the cache partition was too small.. thats why i assumed that it was used by the system in some way
nightcraw said:
Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount). Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.
Click to expand...
Click to collapse
i asked that since i have seen most of the oem roms using ext3 and assumed it offered some benefit speed-wise. all phones use nand of the same type yeah? so whats the benefit of using ext3 when yaffs2 preforms much better on it?
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~
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
archibrid said:
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
Click to expand...
Click to collapse
You've got it completely the wrong way around, the /system partition is where the actual OS is installed, so the smaller the /system partition, the greater the internal storage which remains, which is thus usable for apps.
Smaller partition = more storage.
hello everyone
I have my htc hd2 several times already reinstalled with android,
Until recently, no problems but now after installing setup by rebooting I went to see internal storage 0.0 B free therefore can not install apps.
Have different android versions even tried it first did.
When I go back to windows I see free internal memory.
I also used MTTY_ver_1.42 and badblock that I had got away.
Do hspl 2.08, radio 2.15, magldr 1.13, cwm-recovery 5.0.2.6.
android versions I have tried are:
NexusHD2-Gingerbread_V3.3a-(Android 2.3.7)
TouchWizMOD_v2.1
NexusHD2-Jelly Bean-CM10.1_V2.4
One-S v1.1
Slimroms_LeoV8.0.
Who can help me?
What is your setup? Are you using "DataOnEXT"? NativeSD? Do you have an EXT partition on your sdcard? What's the system partition you created?
Marvlesz said:
What is your setup? Are you using "DataOnEXT"? NativeSD? Do you have an EXT partition on your sdcard? What's the system partition you created?
Click to expand...
Click to collapse
I use DataOnExt have ext4 partition of 4Gb system partition of 400 MB cache 5Mb sd card 32Gb.
agt925 said:
I use DataOnExt have ext4 partition of 4Gb system partition of 400 MB cache 5Mb sd card 32Gb.
Click to expand...
Click to collapse
Resize your system partition to 300 and try again.
Marvlesz said:
Resize your system partition to 300 and try again.
Click to expand...
Click to collapse
I've tried a system-size of 300 Mb, but remains the same
0.0 Kb internal memory still no app installed
agt925 said:
I've tried a system-size of 300 Mb, but remains the same
0.0 Kb internal memory still no app installed
Click to expand...
Click to collapse
Wait, what do you mean by "go back to windows"? How do you have windows and still able to install android in the NAND?
I mean back to the original ROM install windows again.
When I look at memory I see that there is free memory.
If I then continue walking to android is set up from the outset, I see all the steps after the installation of internal memory 0.0 Kb
agt925 said:
I mean back to the original ROM install windows again.
When I look at memory I see that there is free memory.
If I then continue walking to android is set up from the outset, I see all the steps after the installation of internal memory 0.0 Kb
Click to expand...
Click to collapse
... I'm confused.. Where exactly do you see this 0kb? And why are you even looking at it? And why would you even flash WinMo after having Android? They have don't share internals. In fact, installing WinMo erases Android and its bootloaders. (Unless you're running NativeSD, which yet again, resides in the sd card and is NOT affected by the internal storage)
If you can't install apps, maybe the 4GB partition is full? (though I doubt that)
But have you tried a fresh install? (formatted SD card, all partitions?)
if I have installed android and I look at settings and memory than I see in internal memory 0 Kb stand when I want to download an app I get the message that I have no free internal memory.
The reason I had installed the original windowsrom was because I wanted to completely put out android again, I had the idea that it might be good what went sadly was not.
I formatted my sd card several times already and ext4 partition remains the same.
I also tried native but also the same.
agt925 said:
if I have installed android and I look at settings and memory than I see in internal memory 0 Kb stand when I want to download an app I get the message that I have no free internal memory.
The reason I had installed the original windowsrom was because I wanted to completely put out android again, I had the idea that it might be good what went sadly was not.
I formatted my sd card several times already and ext4 partition remains the same.
I also tried native but also the same.
Click to expand...
Click to collapse
Your problem is weird, it's not common. You must be doing something wrong but I fail to figure out what. I searched but all I could find is "resize partition, format and reflash" and "thank you! everything works now!".
Try this: http://forum.xda-developers.com/showpost.php?p=38960831&postcount=5
EDIT:
What do you mean by "ext4 partition remains the same" ? You must format that as well using A PC.
Marvlesz said:
Your problem is weird, it's not common. You must be doing something wrong but I fail to figure out what. I searched but all I could find is "resize partition, format and reflash" and "thank you! everything works now!".
Try this: http://forum.xda-developers.com/showpost.php?p=38960831&postcount=5
EDIT:
What do you mean by "ext4 partition remains the same" ? You must format that as well using A PC.
Click to expand...
Click to collapse
I use my PC to an ext4 partition to get the message but can not mount during install, I use mini tool partition wizard.
I have tried TWRP recovery.
But unfortunately still not the solution
OK, try this: Completely format the sd card and create only 1 FAT32 partition, don't create an EXT partition. Now insert the card into your phone and boot into recovery, go to "Partition SD card" and choose 2GB and (if asked) choose ext4. Choose 0 swap and select OK/next.
Now make sure your NAND is partitioned correctly (system & cache), then copy the ROM and flash it from recovery, choose DataOnExt. Report back.
I made 1 partition on my sd card of 32Gb. made there in TWRP after 1 ext4 partition of 4GB nand to due to the overview of the android ROM.
misc ya 1M
recovery rrecov | ro | nospr filesize recovery raw.img
boat yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr Allsize
NexusHD2-Jellybean-CM10.1_V2.4 installed.
but unfortunately.
agt925 said:
I made 1 partition on my sd card of 32Gb. made there in TWRP after 1 ext4 partition of 4GB nand to due to the overview of the android ROM.
misc ya 1M
recovery rrecov | ro | nospr filesize recovery raw.img
boat yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr Allsize
NexusHD2-Jellybean-CM10.1_V2.4 installed.
but unfortunately.
Click to expand...
Click to collapse
Okay, now I have no more ideas. If you're doing everything right, it should work immediately. Here is a quick guide on how to install android nand. I'm sorry, that's all I could do, I couldn't help.
You should wait for other suggestions, but in the meantime you can follow that guide and see if it works.
Marvlesz said:
Okay, now I have no more ideas. If you're doing everything right, it should work immediately. Here is a quick guide on how to install android nand. I'm sorry, that's all I could do, I couldn't help.
You should wait for other suggestions, but in the meantime you can follow that guide and see if it works.
Click to expand...
Click to collapse
no problem thanks for thinking I continue to try things.
I tell you when I'm moved forward
Yet again been trying.
What I noticed is that when I look at internal memory he says 0.0 Kb and when I look at apps and then run I see at 192 Mb ram used 219Mb free.
Now I understand there is nothing more of who can help me?
agt925 said:
Yet again been trying.
What I noticed is that when I look at internal memory he says 0.0 Kb and when I look at apps and then run I see at 192 Mb ram used 219Mb free.
Now I understand there is nothing more of who can help me?
Click to expand...
Click to collapse
No, the RAM has nothing to do with your internal. Have you followed the guide I linked you to?
Also, try to delete an app (a preferably big one) and see if your NAND gets any more free.
Hi,
Short / long story:
I have long time unused HTC HD2.
With Android (NexusHD2-KitKat-CM11.0_V4.5.zip is the file which I found in backup, so I assume this is what I install - sorry, it was long time ago.
Some time ago I need microSD card so I took it from my HD2, I did backup only windows FAT32 partition.
Now, I need to run my HD2 , I have install microSD 2 GB (800 MB FAT32 + 1GB Ext4) but is not working correctly.
It starting I can install Teamviewer, but when I need to install HTC module for teamviewer it's telling me that is not enough storage.
Quite often is restarting and after restart not keeping any settings (wi-fi) app installed (teamviewer) it's resetting each time to factory settings.
In Settings - Storage shows 'Total space' - Available 0.00 bytes
I did what is instructed on this webpage but it didn't help http://android.stackexchange.com/qu...mory-in-android-nand-roms-cannot-install-apps
Can anybody advise me which is the easiest way to make my HD2 working properly? Means have enough memory to do anything.
The purpose of restoring my HD2 is working as a router, tethering machine. I need to share internet from mobile network for smart TV and Tablet over wi-fi. It will be unattended so I need remote control access (team viewer host).
I'm open for a suggestion of changing the ROM if there is something reasonable easy and described (as I'm not big ROM expert). i've seen a ROM list for HD2, is too long.
Thanks in advance for your help.
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Robbie P said:
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I did Ext4 by MiniTool Partition under Windows primarily.
And later in recovery, I have setup 1024MB and swap = 0 M.
It didn't help.
Should I mount it or so?
Update:
I have a look in log in nand - recovery and it's says that my second partition is Ext3 not Ext4.
And there is no way to change it.
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Robbie P said:
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Click to expand...
Click to collapse
It says on the top bar screen 'CWM-based on Recovery v5.0.2.6' but was install with ROM so should be fine.
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Robbie P said:
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Click to expand...
Click to collapse
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
badzi0r said:
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
Click to expand...
Click to collapse
Here's the solution:
http://forum.xda-developers.com/showpost.php?p=38956440&postcount=4
Thank you