[AT&T Samsung Galaxy Note II] idoit:
Oh boy, now I'm late in the bandwagon! :)

I haven't sent it to get JTAG'd yet. woo tat sound like a doctor for surgery or something :D

I don't know what MK5 is (Now I know: PDA: I317MVLUCMK5) but yea, it was a Bell I317M to begin with. Here is what happened to this little boy/girl:

Stock ROM 4.1.1 -> Upgrade Stock ROM 4.3 -> Root it -> Flash 4.1.1's modem from a Rogers ROM to unlock the carrier and then flash back the original modem after unlocked (as a side effect of this, it used to show Rogers when you pull down the menu with two fingers whereas before unlocking the carrier, it was Bell) -> Experience with OmniROM -> Liked it -> Installed OmniROM 4.4 -> Update OmniROM with nightlies ----- As far as I remember, it was most updated OmniROM 4.4.2 before death.

Yes, it is I317M pit file.

Based on my answer to item #1, what do you think? is it still Bell? or Rogers?!!! :confused:

Yes indeed. Again refer above for sequence of modifications to the phone.

Yes.

I'll answer this again in half an hour, I'll test it again to confirm.

Update: here are the results (as you can see, with all of Odin version, it is same, no mention of NAND write failure):

With Odin3 3.04 using i317m.pit (and yes I always run Odin with admin privileges):

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003>

<ID:0/003> Re-Partition operation failed.

<ID:0/003> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)

With Odin3 1.3 (it is same log as above, no NAND write failed):

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003>

<ID:0/003> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

With Odin3 3.09 (it is same log as above, no NAND write failed):

<ID:0/003> Added!!

<ID:0/003> Removed!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

With Odin3 1.85 (it is same log as above, no NAND write failed):

<ID:0/003> Added!!

<ID:0/003> Removed!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003>

<ID:0/003> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

All true. I have both download mode and recovery, although recovery mode is useless at this point as I said, not much I can do when I'm in TWRP.

Yes I used i317m from your first post in your pit thread http://xdaforums.com/showthread.php?t=2609871 Do you have one for Bell I317M as well?

Absolutely. [MENTION=2918361]dicksteele[/MENTION] and [MENTION=3105785]rangercaptain[/MENTION] are extremely helpful. Blessings to them both.

Shall I flash it with heimdall? (Odin's flashables are in *.md5 I believe, eh?) Also remember, I can't flash anything in my TWRP. so ...

I'm willing to experiment with this brick. Whatever it takes. It's actually a learning process for me too. So yea, I'm willing to do any sort of magical tricks on this poor phone to resuscitate it. And also, speaking of param, if i317m is same with i317, what can go wrong if I just flash the i317 one?! :)

Let me survey how to extract tz from my phone first. Back in a bit. Thanks a looot. :)

Update: Alright, in my TWRP, I can't do anything so I can't extract tz.img via TWRP. Are there any other ways?