SCH-I605 Bricked after Clockwork Recovery installed

[Donkey545]

Hi,
I've been having some trouble restoring my SCH-I605 to functionality after a nice surprise bricking yesterday.
-------------------------------------------------------------------------------------------------------------------
History of Incident:
-------------------------------------------------------------------------------------------------------------------

A few months back I managed to get a successful on my Note 2 after quite a bit of work. Everything was great, and I managed to do all of the modifications I wanted on the stock firmware.

Last night I decided it would be a good idea to make a backup of my current setup in preparation for potential tinkering. I installed Clockworkmod's Rom Manager and Recovery apps. In one of them I clicked something like "Fix Permissions" which requested root access and completed successfully. Following this, the phone requested a restart.

Post restart, I received the standard "verizon has ruined your day" message as follows: "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."

-------------------------------------------------------------------------------------------------------------------
I researched the topic and found this thread:
http://forum.xda-developers.com/showthread.php?t=2040264

I have tried each of the firmware downloads including the alternates here, along with a variety of others from similar threads claiming to be stock images or stock rooted.
-------------------------------------------------------------------------------------------------------------------
Throughout this process I have managed to get the ODIN Mode Prompt to read:
-------------------------------------------------------------------------------------------------------------------

ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
RP SWREV: A3

And

ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
RP SWREV: A3
-------------------------------------------------------------------------------------------------------------------
Typical failures during and post flash included:
-------------------------------------------------------------------------------------------------------------------
SW REV. CHECK FAIL. DEVICE: 3 BINARY 2

ODIN v3.07 Readout
...
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

-------------------------------------------------------------------------------------------------------------------

SW REV. Invalid magic string.

ODIN v3.07 Readout

<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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

-------------------------------------------------------------------------------------------------------------------
The second error yields the interesting result of changing the Binary from CUSTOM to SAMSUNG OFFICIAL and replaces the verizon message with the following:

"Firmware upgrade encountered an issue . Please select recovery mode in Kies & try again."

Kies will not connect to the device in this state or ODIN mode, but it does try.

When the Verizon message is present, the usb connection has no activity and thus yields no connection in Kies.

-------------------------------------------------------------------------------------------------------------------
I have attempted making some other .tars with the TAR_MD5_PACKAGER but these pacakges yielded similar results. I can remove the sboot.bin file from the package and get it to install, but the same verizon message comes up. I have tried on multiple ODIN versions and two computers with no change in results.

Any thoughts on what to do now? I have included all the information I think is pertinent. If you need more I can provide it.

Thanks,

Donkey545

 

[Donkey545]

I have managed to get the device to boot past either of the error messages by flashing the OTA 4.4.2 Rom I605VRUFND7_I605VZWFND7_VZW.

-------------------------------------------------------------------------------------------------------------------
I found that rom here

(Cant post URLs Because I am a new member)

androidfilehost /?fid=24052804347837519

-------------------------------------------------------------------------------------------------------------------

The system is hanging at the Verizon logo now, but the fact that it is no longer stuck at the error message is promising. I will attempt so more things to get the system to work..
-------------------------------------------------------------------------------------------------------------------
EDIT:
-------------------------------------------------------------------------------------------------------------------

- Booting in Safe Mode does not remedy the issue.
- Booting into recovery now works!
- Wiping the cache yields no results
-------------------------------------------------------------------------------------------------------------------
Recovery mode information:
-------------------------------------------------------------------------------------------------------------------

Android system recover <3e>
KOT49H. I605VRUFND7

--------------------------------------------------

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.
E: failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E: failed to mount /data/log/recovery_log.txt

-------------------------------------------------------------------------------------------------------------------

I will now attempt a factory reset. I was trying to avoid this, but I probably lost all of my data anyway.

-------------------------------------------------------------------------------------------------------------------
EDIT 2:
-------------------------------------------------------------------------------------------------------------------

The factory reset has successfully un-bricked my phone! I suspect that I will no longer have root, and I definitely lost all of my data. I will confirm these results shortly.