[Verizon Samsung Galaxy Note II] Luminair:
Hi guys! Just got the phone. Doing a once-over to see what's up. Will follow-up with what I find!

---------- Post added 20th June 2013 at 12:16 AM ---------- Previous post was 19th June 2013 at 11:33 PM ----------

Follow-up:

Process:

Download Odin, I605_VRALJB_Restore.tar (extracted with 7zip), and sch-i605-16gb.pit from droidstyle's guide.

Install Samsung drivers, plug in phone via OEM cable directly into motherboard

Run Odin as Administrator; options are as follows:

After pressing Start, phone hangs as follows:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I605_VRALJB_Restore.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<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> Get PIT for mapping..

On download mode, phone states following:

Product Name: SCH-I605

Custom Binary Download: No

Current Binary: Samsung Official

System Status: Custom

Developer Mode: No

The last line leaves me a bit iffy, but if the phone is getting nuked by Odin then it shouldn't matter. Phone doesn't boot into Android, so I can't pop in there and turn it on. Thoughts? Thanks all!

---------- Post added at 12:36 AM ---------- Previous post was at 12:16 AM ----------

Additionally, when attempting to flash just a file in the PDA slot, I get the following (trying CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 this time):

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<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> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL!

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

---------- Post added at 12:49 AM ---------- Previous post was at 12:36 AM ----------

Attempting to flash TWRP from Odin gives the following:

<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> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL!

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

---------- Post added at 01:27 AM ---------- Previous post was at 12:49 AM ----------

No USB Debugging is definitely part of the problem. I'd be able to use the Note 2 Toolkit if it was enabled (at least I assume that's the case as it asks for USB Debugging before proceeding).

---------- Post added at 01:48 AM ---------- Previous post was at 01:27 AM ----------

Call me crazy, but considering Nand Erase All checked - ramifications? Potential hard brick, I know. If that doesn't work, JTAG time?