[SOLVED] SCH-I605 Stuck on Boot Screen. Help?
I was using CleanROM for the longest time. I've actually been using it for so long I can't quite remember how I got the phone unlocked in the first place. I want to say I used a combination of the Note 2 Toolkit and CASUAL to get there. I've been trying to get back to stock and now I'm stuck at the Samsung Galaxy Note 2 boot screen. I can get into Download Mode but I can't access Recovery at all. I've been using Odin(Which is where I messed up at). Things I've tried so far:
All of these will say they pass, but when the phone reboots, it still gets stuck at the Samsung Galaxy Note 2 boot screen.
Tried flashing the VRALJ from stockroms.net
Tried flashing philz touch recovery
Tried flashing both stock firmwares from sammobile.com for the SCH-I605.
I'm currently at a loss as to what to do now.
Any help is much appreciated. Thank you.
UPDATE: Ok, now when I try with one of the stock firmwares Odin gets to where it says Nand Write Start!! and it fails. Fails when flashing the Philz Touch Recovery as well.
UPDATE 2: Tried a different version of Odin. This time using Odin v3.09 and tried the VRALJB stock rom, it got to flashing the recovery.img then went to sboot.bin and failed.
UPDATE 3: Ok, using Odin v3.09 flashed philz touch recovery with Nand Erase All selected and T Flash selected. It went through successfully and am now able to boot to recovery. Seems that I was just using the wrong version of Odin3...I think...I hope...lol
UPDATE 4: Ok, so that didn't work. I was able to get into the stock recovery. But was unable to boot into android itself. Figured it's because there was nothing on it, attempted to flash a stock rom, and it still failed at sboot.bin. Attempted to reflash philz touch recovery, still fails. I'll keep trying different things, but I'm running out of things to try until I hit that insane moment where I try everything again expecting different results.
UPDATE 5: Ok, so I'm blind...or somehow didn't come across this thread before. But it helped me to fix the issue...so yeah. Thread link: http://forum.xda-developers.com/show....php?t=2120726