[HD2 Android NAND Development] walts:
I'm using Dorimanx's request as a springboard for one of my frustrations.

If you've been following this thread you know I've been frustrated with random reboots for some time, and that I am trying everything I can to determine how I can put an end to it.

Frustration #1:

I have followed tytung's instructions in post #1 scrupulously. I use only the "vanilla" version of his ROM, except for once when I tried Dorimanx's kernel - to no avail.

I flatter myself that if I had access to source code (well commented!?!?) I could do a better job at making sense of log file entries like this:

[ 219.479003] msm72k_udc: ulpi: write 0x0c to 0x31
[ 219.479034] msm72k_udc: ulpi: write 0x30 to 0x32
[ 219.479064] msm72k_udc: ulpi: write 0x1d to 0x0d
[ 219.479064] msm72k_udc: ulpi: write 0x1d to 0x10
[ 219.479125] usb: notify offline
[ 219.479125] msm_hsusb: enable pullup
[ 219.499450] usb: AC charger
[ 219.519104] usb: lpm enter
[ 219.519104] usb_suspend_phy
[ 219.520141] usb: send connect type 2
[ 219.520141] fsg_set_ums_state: 2
[ 219.520172] batt:online=2
[ 219.520172] [ds2746_batt] cable change to 2
[ 219.520202] batt: ds2784_notify: 0 2 at 218171330646 (2012-02-11 12:47:34.585601831 UTC)
[ 219.520202] batt: charger ON (FAST) at 218171361163 (2012-02-11 12:47:34.585632349 UTC)
[ 254.591369] [D:BATT] V=4108(694) I=136(15a) C=1100.0/1230(fcf) id=4(9f) T=350(ce) KADC=962
[ 254.591400] [D:BATT] acr update: P=895, C=4044.
[ 254.591613] [D:BATT]new RARC=895 C=1100mAh adc=4044.
[ 254.591613] [D:BATT] state change(2->3), full count=0, over load count=0 [1819595192]
[ 254.591644] batt: ds2784_notify: 1 90 at 253242772299 (2012-02-11 12:48:09.657074002 UTC)
[ 254.591674] batt: batt:power_supply_changed: battery at 253242833334 (2012-02-11 12:48:09.657104519 UTC)
[ 276.540008] msmfb_shutdown
[ 276.540008] lcdc_blank: ()
[ 276.540039] sharp_panel_blank
[ 276.631378] Restarting system with command 'recovery'.
[ 276.631469]
[ 276.631500] Restarting Linux version 2.6.32.15 (aaronrichards@ubuntu) (gcc version 4.4.0 (GCC) ) #2 PREEMPT Mon Jan 10 11:24:30 GMT 2011
[ 276.631561]

Maybe not, but I'd like to have the opportunity to try, and to learn.

Frustration #2:

I have a great deal of trouble sorting out what I sarcastically called "Folklore" a few posts back from fact. For example, in post#1, tytung says

Logically that makes sense to me. The idea of Task29 with every re-flash does not. If I understand correctly, Task29 re-formats all of the NAND memory including the boot loader (MAGLDR or CLK) and CWM. Maybe the radio too, maybe not. In any event, if that code is remaining constant and is still functioning, why replace it? Unless, maybe, task29 masks out bad blocks, and flashing the new ROM with CWM does not.

I have searched this and other threads for answers. I have been flashing experimental ROMs on Windows and Android phones for some time. I realize the HD2 is different from "pure" Android phones like the Incredible, in that they need special code to interface with the hardware designed for Windows.

I would like to put together a wiki explaining the details of all the processes we use, and when to use them / not use them. But I need help to do this. Will some of you who have more in-depth knowledge of the hardware and software we use, step up and help me? If I can get some help, I'll try to have a rough draft by the end of February.

PM me if you're interested in helping.

Oh, and if such a wiki exists and I've missed it, just post a link, without flames please. If adding to the Q&A wiki makes sense, I'd be happy to work that way, too, but in a fashion that would not overburden and confuse folks that just want to get a ROM working on their phone.

Walt