[Q] Stock restore Fail at sboot.bin

[rdeckerr]

**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.

For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264


*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***

Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.

Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.

*** Is it posible the OTA update made the stock recovery image incompatable? ***

Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207

----- ODIN LOG -----
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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)
----- END ODIN LOG -----

ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.

I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.

I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?

Thanks in advance.

 

[rdeckerr]

Under the root66 image the phone is only registering 4 gigs of available space.

 

[exmeaguy]

Junior member, where did you find the alternate restore method?

 

[rdeckerr]

Junior member, where did you find the alternate restore method?

http://forum.xda-developers.com/showthread.php?t=2040264

Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.

 

[exmeaguy]

Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.

---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------

The file extension ends with XZ, which Odin said was not a PDA file.

 

[rdeckerr]

Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.

---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------

The file extension ends with XZ, which Odin said was not a PDA file.

It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.

Hope this helps.

 

[exmeaguy]

Thanks Junior member I will try that.

 

[kintwofan]

Thanks Junior member I will try that.

I'm curious why you keep calling him junior member?

Sent from my SCH-I605 (AKA NOTE 2)

 

[exmeaguy]

Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.

 

[rdeckerr]

Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.

hahahaha

Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!

 

[exmeaguy]

I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?

 

[rdeckerr]

I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?

Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).

I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.

So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.

 

[w4rped]

http://forum.xda-developers.com/showthread.php?t=2040264

Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.

Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!

I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.

 

[universexda]

Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?

 

[kintwofan]

Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?

No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.

Sent from my SCH-I605 using Tapatalk 2

 

[jlegros]

**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.

For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264


*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***

Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.

Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.

*** Is it posible the OTA update made the stock recovery image incompatable? ***

Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207

----- ODIN LOG -----
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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)
----- END ODIN LOG -----

ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.

I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.

I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?

Thanks in advance.

Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.

 

[universexda]

No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot

The alternate restore won't attempt to restore the bootloader to stock right?

 

[kintwofan]

The alternate restore won't attempt to restore the bootloader to stock right?

That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.

Sent from my SCH-I605 using Tapatalk 2

 

[aka113]

Same problem

I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.

 

[kintwofan]

I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.

Did you actually read any of this thread? We got his phone working.

Sent from my SCH-I605 using Tapatalk 2