Screwed up bootloader - how do I restore? sboot.bin causes Odin to fail

pendraggon87

Active member
Nov 6, 2012
29
0
0
So - I foolishly followed a website that gave instructions on rooting, without a warning about unlocking the bootloader. I rooted the phone, no problem there, and then tried flashing TWRP recovery. And that is where it all broke down. I got the Verizon triangle of doom, telling me unauthorized software. So ok, I restored by using the stock ROM. But wait! It did not work, because it would constantly fail in Odin when it got to sboot.bin! The workaround I found was to use imnuts alternate rom which leaves the bootloader alone (does not do anything with sboot.bin). However, I cannot do anything in ODIN which requires a bootloader file - I tried using casual to root/unlock, but I get a mean message of:
"HellNo
IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET! "

And while I agree with the message, if anyone has a method of restoring stock recovery, and stock bootloader, that would be amazing. Thanks!
 
So - I foolishly followed a website that gave instructions on rooting, without a warning about unlocking the bootloader. I rooted the phone, no problem there, and then tried flashing TWRP recovery. And that is where it all broke down. I got the Verizon triangle of doom, telling me unauthorized software. So ok, I restored by using the stock ROM. But wait! It did not work, because it would constantly fail in Odin when it got to sboot.bin! The workaround I found was to use imnuts alternate rom which leaves the bootloader alone (does not do anything with sboot.bin). However, I cannot do anything in ODIN which requires a bootloader file - I tried using casual to root/unlock, but I get a mean message of:
"HellNo
IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET! "

And while I agree with the message, if anyone has a method of restoring stock recovery, and stock bootloader, that would be amazing. Thanks!

Sorry I didn't read the whole thing through. .. Are you using the new versions of casual found here http://forum.xda-developers.com/showthread.php?t=2118348
[Jailbreak][Root][Recovery] CASUAL One-Click -- update 17MAR13:Windows/Linux
?

From my Galaxy Note 2 via Tapatalk
 
So I downloaded the stock rooted image (first link). However, something is effed up with the bootloader (in that, trying to run Casual to unlock it, I get the error. If I try using the Casual bootloader package for Odin, it fails at sboot.bin (in fact, everything fails at sboot.bin if that exists). So while having root is nice, my recovery is messed up (in that it does not boot to any recovery) and I cannot flash a rom.


Flash stock rooted file found here

http://forums.androidcentral.com/showthread.php?t=232525
[How to][VZW GNote2] Root/Rom via Odin w/video

This should get you running again
From my Galaxy Note 2 via Tapatalk

EDIT: I am able to actually get into stock recovery. Please ignore that part. However, I still have bootloader issues (i.e. I want to unlock it so I can use custom ROMs).
 
So I downloaded the stock rooted image (first link). However, something is effed up with the bootloader (in that, trying to run Casual to unlock it, I get the error. If I try using the Casual bootloader package for Odin, it fails at sboot.bin (in fact, everything fails at sboot.bin if that exists). So while having root is nice, my recovery is messed up (in that it does not boot to any recovery) and I cannot flash a rom.




EDIT: I am able to actually get into stock recovery. Please ignore that part. However, I still have bootloader issues (i.e. I want to unlock it so I can use custom ROMs).

If you can wait I can remotely try and unlock it for you if you are willing but I won't be able to do this until my bosses leave from work

From my Galaxy Note 2 via Tapatalk
 
Sorry I didn't read the whole thing through. .. Are you using the new versions of casual found here [Jailbreak][Root][Recovery] CASUAL One-Click -- update 17MAR13:Windows/Linux - xda-developers
[Jailbreak][Root][Recovery] CASUAL One-Click -- update 17MAR13:Windows/Linux
?

From my Galaxy Note 2 via Tapatalk
*hugs* - I did not see R400! I just used it, and it apparently succeeded. However, what is a way for me to test this without bricking the phone? Try putting TWRP again and seeing if there is an error? The progress bar did not complete.
 
So the status bar is stuck near the end, it said upload of recovery and bootloader successful.

Ending session...
Rebooting device...
Releasing device interface...

waiting for device

and now it is just hanging.
 
*hugs* - I did not see R400! I just used it, and it apparently succeeded. However, what is a way for me to test this without bricking the phone? Try putting TWRP again and seeing if there is an error? The progress bar did not complete.
If you succedded then TWRP is already installed , turn off your device and press and hold volume up+Home button then press and hold power, continue to hold all three until Team win log pops up
 
I rebooted the phone, and everything seems to be working awesomely now! It apparently boots into TWRP by default, but thats no biggy. yay! Now I can try some custom roms. Day well spent :)

- - - Updated - - -

If you succedded then TWRP is already installed , turn off your device and press and hold volume up+Home button then press and hold power, continue to hold all three until Team win log pops up

One question I have is that - I have a message that there is an OTA update. Am I able to download those?
 
I rebooted the phone, and everything seems to be working awesomely now! It apparently boots into TWRP by default, but thats no biggy. yay! Now I can try some custom roms. Day well spent :)

- - - Updated - - -



One question I have is that - I have a message that there is an OTA update. Am I able to download those?

I wouldnt bother especially if you are going to put a custom rom onto the device.
 
I rebooted the phone, and everything seems to be working awesomely now! It apparently boots into TWRP by default, but thats no biggy. yay! Now I can try some custom roms. Day well spent :)

- - - Updated - - -
One question I have is that - I have a message that there is an OTA update. Am I able to download those?

No you should not download an OTA (or apply the OTA if it's already downloaded). Use Titanium backup or a similar program to freeze/disable the update program SDM 1.0 as soon as possible (disabling from the Note 2 Settings Application Manager only works until you reboot). An OTA applied to a phone with a non-stock recovery like TWRP or CWM would almost certainly soft brick the phone. It would probably be pain to get out of. It might even hard brick the phone and then all you'd have is a paperweight. If you want the latest OTA features, either flash a custom rom like Bean's Jellybeans or flash a stock rooted rom that doesn't affect the bootloader like one of Bean's stock rooted roms. These roms have the latest OTAs in them. Both can be found in the Verizon Galxy Note 2 Android Development sub-forum at xda-developers.com.
 
Last edited:
I was actually dumb enough to let my device install the OTA Update to 4.22 on my Nexus 7. I had just hours earlier flashed stock and unlocked the bootloader, unrooted. The problem is now I can't actually get into bootloader mode. I'm stuck on the update screen with the green android and the thing blue status bar. Using volume down/up and power only reboots the device to google logo (with unlock symbol) and then back to the eternal update install. Is there anyway I can fix this? I've also tried to reboot bootloader through the Toolkit, no luck.

Any help would be AWESOME! Thanks!
 
I was actually dumb enough to let my device install the OTA Update to 4.22 on my Nexus 7. I had just hours earlier flashed stock and unlocked the bootloader, unrooted. The problem is now I can't actually get into bootloader mode. I'm stuck on the update screen with the green android and the thing blue status bar. Using volume down/up and power only reboots the device to google logo (with unlock symbol) and then back to the eternal update install. Is there anyway I can fix this? I've also tried to reboot bootloader through the Toolkit, no luck. Any help would be AWESOME! Thanks!
Have you pulled the battery?