Issues with ODIN 3.07 on Note 2

QuantumInteger

New member
Sep 24, 2013
2
0
0
Hello, I have a Sprint Note 2 (SPH-l900). Recently, Sprint has been rolling out the 4.3 update for my version of the Galaxy Note 2. Impatient with their release schedule, I did some google search and discovered that a user on the XDA forum has leaked the firmware update
Sprint Samsung Galaxy Note II 4.3 OTA Update - xda-developers

I downloaded the file but the version of ODIN I was using (3.09) was new and I may have used the third option (PHONE) and choose the sboot.bin file from from the 4.3 zip file I got off the XDA forum. Now my Note 2 is stuck on boot. I tried using an older version of ODIN (3.07) because I thought 3.09 was a bit confusing to use. I downloaded the stock firmware for the SPH-L900 from SamMobile, put the phone into recovery by turning it off and booting it up by holding power, home button, and volume up at the same time. I used the PDA option to load the stock firmware and all went well until I got to the sboot.bin and I get this error message:

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L900VPAMC2_L900SPTAMC2_1090526_REV04_user_low_ship.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> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

And I get this error message on my Note 2
http://i.imgur.com/600eMD1.jpg

At this point, my phone is brick. If I boot up again, it'll tell me that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Kies is all but useless since it doesn't recognize my phone. I can get out of this screen by loading the sboot.bin file or the CF-Auto-root-t0ltespr-t0ltespr-sphl900.tar.md5 file but I'll still be stuck on boot screen. Anybody got any idea for me to dig myself out of this predicament?
 

Trending Posts

Forum statistics

Threads
956,708
Messages
6,969,579
Members
3,163,599
Latest member
Marabishi