Looking back I cant recall ever updating this phone's OS or Baseband. But yet I read all over the place that Samsung and Sprint like to automatically update at random.
A few months back when 4.4.2 came out I noticed that my phone decided to automatically update itself and the moment it rebooted all hell broke loose. All the phone would do is boot showing the "Samsung" logo than the "Galaxy S3" logo right after. The phone would reboot itself right away than it would boot the exact same way, this time locking up on the "Galaxy S3" logo. The whole time also vibrating.
I am unable to boot into recovery mode, volume up + home button + power button. At the top left corner of the "Samsung" screen it shows "booting recovery" then immediately goes right to the "Galaxy S3" screen and reboots again.
I am able to boot to download mode, volume down + home button + power.
So far I have tried using ODIN's v3.09/3.07 to load stock firmware's for the original 4.0.4, 4.3, and just in case it actually updated 4.4.2. Every time I try to load them through ODIN I get...
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is where I'm stuck and at a loss. From what I have been reading all over XDA, as long as I can still boot to download mode I still have a chance. I am really crossing my fingers here because being a Disabled Veteran I can't afford the money to get a new phone outside of my current contract time. And there is no way the wife and I can share the Note 3, lol.
-Semper Fi
A few months back when 4.4.2 came out I noticed that my phone decided to automatically update itself and the moment it rebooted all hell broke loose. All the phone would do is boot showing the "Samsung" logo than the "Galaxy S3" logo right after. The phone would reboot itself right away than it would boot the exact same way, this time locking up on the "Galaxy S3" logo. The whole time also vibrating.
I am unable to boot into recovery mode, volume up + home button + power button. At the top left corner of the "Samsung" screen it shows "booting recovery" then immediately goes right to the "Galaxy S3" screen and reboots again.
I am able to boot to download mode, volume down + home button + power.
So far I have tried using ODIN's v3.09/3.07 to load stock firmware's for the original 4.0.4, 4.3, and just in case it actually updated 4.4.2. Every time I try to load them through ODIN I get...
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is where I'm stuck and at a loss. From what I have been reading all over XDA, as long as I can still boot to download mode I still have a chance. I am really crossing my fingers here because being a Disabled Veteran I can't afford the money to get a new phone outside of my current contract time. And there is no way the wife and I can share the Note 3, lol.
-Semper Fi