[HD2 Android Q&A, Help & Troubleshooting and Genera] Pie21:
Hi guys, and before anything else, I'm so sorry. I've broken all the rules of making a backup and NOT trying to flash a phone after midnight. It won't happen again. I'm praying that this is second nature to you guys now though and you can save my backside :o.

I'm attempting to flash tytung's amazing-sounding Jelly Bean ROM for my HD2 512MB. I've tried to do everything I've read, but as a bit of a ROM noob paging through some fairly techy threads I'm sure I'm missing a step or three. I've previously flashed a tytung ICS CM9 ROM, so I've done all the rooting stuff before. Here's what I've done this time:

Back up important data (though not the actual ROM).

Format 16GB SD card (FAT32).

Partition SD card into 1GB Ext4 and 15GB FAT32, both primary.

Copy ROM zip and kokotas' initrd_patcher_v2 zip onto FAT32 partition.

I was also following this video a bit, so I added 4EXTRecovery as well.

As per video above, ran Task 29 to clean things up (probably unwarranted)

Boot into Magldr 1.13, set 4EXTRecovery as the SD boot dir.

Boot to SD, into 4EXTRecovery.

Install ROM from zip, choosing NAND + Ext option.

Complete, reboot into Magldr.

Be unsure about boot settings... set to Securecrt_JB_kernel maybe?

Boot from SD card into reboot loop.

Boot from NAND, receive "no boot sources".

Give up, surrender for assistance.

I'm hoping I have a guardian xdangel out there who can answer a few simple questions for me. I'm very happy to provide more information that you probably need, but I need some rest for now.

Ultimately, do I boot from NAND or SD (in Magldr)?

If NAND, why does "Boot AD NAND" currently come up saying "no boot sources"?​

If SD, to what do I set the AD SD Dir in Magldr? What loader am I missing to boot into Android?​

The 4EXTRecovery log says something about cache partition not found; does this mean I've messed something up in the partitioning?

I thought I'd try setting the SD dir to "Securecrt_JB_kernel.20120924_22_34_with_initrd_for_NAND_DataOnEXT", since it sounded promising (cant remember where I found it), but it just gets me into a reboot loop. Is this totally the wrong thing to be using?

Could the reboot loop be something to do with system partition sizes? I tried reinstalling the ROM following a repartition to 400MB main and 45MB cache, and it didn't magically fix everything (still booting from that Securecrt kernel).

I remember flashing a ruu_signed.nbh file last time, but not really know what for. Do I need to do something like that here?

UPDATE: HAHAHA oh man I think it's working. I think the main issue was not repartitioning the system after naively running Task 29. Even though the ROM installer appeared to fail the second time, somehow booting from NAND has the little CyanogenMod spinny logo. Yep, there it goes! Quite slow, but functional. If anyone would still like to comment, I'd love to hear from you, and perhaps reinstall a little more effectively.

If you're feeling really generous, a list of tools needed to get through the installation would be fantastic so I don't use 'too much'. I'm sure there's more to it than just the ROM and kokatos' thing, but the development thread assumes some non-trivial familiarity with the whole process.

So again, please forgive me, but I could sure use some help :angel:.