NexusHD2 Android Forum

Hi,
I have flashed my HD2 almost two years ago and did not touch the software since then.
The current setup is as follows:

HSPL: 2.08
Radio: 2.15.50.14
cLK: 1.5.0.1 (HBOOT-1.5.0.1 ?)
CWM: 5.0.2.6

Partition table:
- recovery = 5 MB
- misc = 1 MB
- boot = 5 MB
- system = 200 MB
- cache = 5 MB
- userdata = 205 MB

SD card: 16 GB class 10, partition1: FAT32 12GB, partition2: EXT3 2GB

On the top of that there is ROM: CyanogenMod-7-20121021-NIGHTLY-bravo[TyphooN_v3.8.9-cLK]. As far as I know this is NAND based rom which has implemented APP2SD functionality.
I would like to change ROM into NexusHD2-KitKat-CM11.0 V4.3 but have no idea where to begin. I guess there is no need to start over from HSPL flashing, so how can I proceed?
Thanks a lot for any suggestions and thoughts.

Best regards,
Bart

gites wrote:Hi,
I have flashed my HD2 almost two years ago and did not touch the software since then.
The current setup is as follows:

HSPL: 2.08
Radio: 2.15.50.14
cLK: 1.5.0.1 (HBOOT-1.5.0.1 ?)
CWM: 5.0.2.6

Partition table:
- recovery = 5 MB
- misc = 1 MB
- boot = 5 MB
- system = 200 MB
- cache = 5 MB
- userdata = 205 MB

SD card: 16 GB class 10, partition1: FAT32 12GB, partition2: EXT3 2GB

On the top of that there is ROM: CyanogenMod-7-20121021-NIGHTLY-bravo[TyphooN_v3.8.9-cLK]. As far as I know this is NAND based rom which has implemented APP2SD functionality.
I would like to change ROM into NexusHD2-KitKat-CM11.0 V4.3 but have no idea where to begin. I guess there is no need to start over from HSPL flashing, so how can I proceed?
Thanks a lot for any suggestions and thoughts.

Best regards,
Bart

At the least you will have to re-partition your device since today's ROM's require a larger (possibly much larger) system partition. You should look into and decide if you will be using an all NAND installation or a DataOnEXT installation. You likely should consider the second choice since your device is no loger brand new (probably has bad some blocks in NAND). You can also try a NativeSD installation which would allow you to keep your existing setup while testing a new ROM though this was never my personal choice.

Good luck!

Thanks NyLimited. I go for DataOnEXT definitely. Few more Qs:
1. What should partition map look like in that case? ...I'm asking both for NAND and SD card.
2. What kind of tool should I use for NAND repartitioning?
3. What should be cleaned up and when (dalvik-cache, etc.)
FYI... I do not bother about current image / data - they may be swept out totally.
BR / Bart

I recommend you resize your system partition to 400 MB. You can use HD2 NAND toolkit: http://forum.xda-developers.com/showthr ... ?t=1090783.

Using HD2 NAND Toolkit I could define only system partition size (80 - 450 MB) and cache size (5 or 44 MB). How can I change the rest i.e. recovery, misc, boot, userdata. I would like to do everything as suggested for [Jan. 21, 2014][ROM][KK][4.4.2][720p] NexusHD2-KitKat-CM11.0 V4.3 [Kernel: tytung_jellybean_r2], i.e.:

misc ya 1M
recovery rrecov|ro|nospr 5M cwm_recovery_leo.img
boot yboot|ro 5M
system ya 280M
cache ya 2M
userdata ya|asize|hr allsize

Do I have to run Task29? ...and when? Does this remove everything (including cLK, CWM and radio) from all partitions or just wiping some user data?

gites wrote:Using HD2 NAND Toolkit I could define only system partition size (80 - 450 MB) and cache size (5 or 44 MB). How can I change the rest i.e. recovery, misc, boot, userdata. I would like to do everything as suggested for [Jan. 21, 2014][ROM][KK][4.4.2][720p] NexusHD2-KitKat-CM11.0 V4.3 [Kernel: tytung_jellybean_r2], i.e.:

misc ya 1M
recovery rrecov|ro|nospr 5M cwm_recovery_leo.img
boot yboot|ro 5M
system ya 280M
cache ya 2M
userdata ya|asize|hr allsize

Do I have to run Task29? ...and when? Does this remove everything (including cLK, CWM and radio) from all partitions or just wiping some user data?

Soren gave you good advice. First, no you don't have to task29. However I do recommend you read symbuzzer's excellent pinned thread which details identifying bad blocks and formating your NAND with different method's. After reading you can decide if you want to task29 or not.

If you plan on a DataOnExt install whatever space you don't allocate for '/system' goes unused and is wasted. None of Tytung's ROMs use the cache partition as it's just a symlink to the '/data' partition. So using the toolkit, a good selection would be the settings you have above, but with system increased to 400-450MB. This way if you have any bad blocks, which most HD2s have at this point, you won't have problems with it bootlooping or mysterious errors due to lack of '/system' space. Trust me, using extra space for '/system' will most assuredly save you heartache later. The vast majority of installation problems we see on this board are because of problems with '/system' partition being too small due to bad blocks.


Edit: Let me add that if you go with DataOnExt you need to create an EXT3-4 partition (I prefer ext-4) on your SD that's large enough to hold whatever apps you'll run plus any other file that is written to '/data' during installation. You'll want 500MB - 2GB in size, with larger giving more room for installed apps.

I hope this helps

Ciao

Thanks Odysseus, yes, it does
My current SD configuration looks like this: 16 GB class 10, partition1: FAT32 12GB, partition2: EXT3 2GB. I doubt if I will ever cross the border of 2GB for apps but I'll repartition it to have second partition with 4GB and EXT4 - just to be on the safe side
I have read thread regarding Task29 and still I have no idea if this is necessary or not. My guess is NOT because I do NAND repartitioning thus all data are wiped off from NAND. Does it make any sense?
BR / Bart

gites wrote:Thanks Odysseus, yes, it does
My current SD configuration looks like this: 16 GB class 10, partition1: FAT32 12GB, partition2: EXT3 2GB. I doubt if I will ever cross the border of 2GB for apps but I'll repartition it to have second partition with 4GB and EXT4 - just to be on the safe side
I have read thread regarding Task29 and still I have no idea if this is necessary or not. My guess is NOT because I do NAND repartitioning thus all data are wiped off from NAND. Does it make any sense?
BR / Bart

I'm sure you'll find 2gb is plenty of space. When combined with the space for /system it's like having 2.5gb internal storage. Many new handsets don't have that amount of space. Plus you could always push a few of your most essential favorite apps into /system since there's now extra space.

As to task29, if you don't have problems then don't bother with it. Every time you full format or task29 you put more wear and tear on your nand. Each memory block only has so many read and write cycles before failure. The more you use the less remaining cycles. Once a block fails it's irreparable, so this is a case where the less you do or can get away with, the better.

Edit: Let me add along the same line of thought, once you are satisfied with your NAND partitioning scheme, then with future updates don't repartition just wipe them. Wiping is less destructive and reduces wear vs partitioning and reformatting which is more taxing on your NAND. The less unnecessary wear the better for these wonderful, but now aging devices.

Ciao

I agree with you Odysseus - NAND should be treated carefully, especially in such outdated device like HTC HD2 Nevertheless I have to do repartitioning because new images will not fit into my 200 MB system partition. I hope expanding system partition up to 400 MB and installing future images as "NAND + DataOnEXT" will prevent all hardware related problems with NAND chip.
Damn, how I like this phone

gites wrote:Thanks NyLimited. I go for DataOnEXT definitely. Few more Qs:
1. What should partition map look like in that case? ...I'm asking both for NAND and SD card.
2. What kind of tool should I use for NAND repartitioning?
3. What should be cleaned up and when (dalvik-cache, etc.)
FYI... I do not bother about current image / data - they may be swept out totally.
BR / Bart

I would make a few changes. I see you have already received some good advice so this just adds a few extra thoughts to it.. Yes, a 400 MB system partition should serve you well. My suggestion, however, would be:

Code: Select all

misc ya 1M
recovery rrecov|ro|nospr 10M recovery-raw.img
boot yboot|ro 10M
system ya 399M
cache ya 3M
userdata ya|asize|hr allsize

Note that I changed

1. the size of the recovery partitionto 10 MB. This will allow you to use different recoveries, such as current CWM or TWRP, most of which require more space than the old partition size. Don't forget that the name of the file specified may be different, depending on what you use.
2. I also changed the boot partition upward although that is an overkill. Still, since you now have plenty of space, why not.
3. Since tytung's ROMs don't use the cache partitionyou can reduce it.

The SD card.. if you are concerned with a 2 GB partition for data, make it 3. It will be easier to use that than a second partition. My personal preference was always EXT4 (not 3). It does not sound like you need help with it but if you should there is a section on card partitioning in my SD thread (below).

If you repartition NAND there is nothing to clean up since you just wiped the entire device and probably the card as well. Dalvik is automatically wiped by a new ROM now - no need to do anything about it.

soren wrote:I recommend you resize your system partition to 400 MB. You can use HD2 NAND toolkit: http://forum.xda-developers.com/showthr ... ?t=1090783.

That is pretty much what I had on my HD2 when I was using it.

gites wrote:I have read thread regarding Task29 and still I have no idea if this is necessary or not. My guess is NOT because I do NAND repartitioning thus all data are wiped off from NAND. Does it make any sense?
BR / Bart

NO! Do not waste your time doing Task 29! It is an old myth which does not want to die (sigh)...

Odysseus wrote:As to task29, if you don't have problems then don't bother with it. Every time you full format or task29 you put more wear and tear on your nand. Each memory block only has so many read and write cycles before failure. The more you use the less remaining cycles. Once a block fails it's irreparable, so this is a case where the less you do or can get away with, the better.

Amen!