5,600,429 Members 33,015 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Bricked, recovered, OTA'd, bricked again. HELP!

Tip us?
 
skiahmutt
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
Default [Q] Bricked, recovered, OTA'd, bricked again. HELP!

I got a Note 2 yesterday, bought it used. I turned it on, everything seemed normal. I took it to Verizon, they activated it for me in the store, and while I was there, the lady activating it also accepted an OTA software update. I have no idea what version I was on, or what the OTA was. When I got home, the phone shut down as part of the OTA, and everything appeared normal. The little android with a box screen came up, cycled through the progress bar, etc. However, when it was done, the phone rebooted, and froze on the "Samsung Galaxy Note II" screen. I gave it a while, then battery pulled, tried everything I could think of. Couldn't get into the recovery menu. It would get to Odin, but that was it. Anyways, after a very stressful night working on it, I found the thread here:

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

I downloaded the "Alternate Restore Mirror" link, put the phone in download mode, and installed from Odin on my computer. The phone booted up, everything worked beautifully.

Then, tonight at work, I checked for software updates, and was informed that there was an available update. I downloaded and installed it(I think the phone said it was 7MB?), and THE SAME THING HAPPENED. Phone is frozen on the "Samsung Galaxy Note II" screen. I plugged it into my laptop, put it in download mode, and did exactly what I did this morning. Odin says everything was successful, and reboots the phone. But it hangs on the "Samsung Galaxy Note II" screen, no matter what I do. I've tried searching, and followed every guide on how to unbrick it I can find, but no matter what software package I use, it fails on "sboot.bin". The only one that will work and not fail is the "Alternate" in the link above, but when I use that one I still have a bricked phone.


I -really- need advice here, guys. I'm in way over my head.
 
skiahmutt
Old
#2  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
So, a little more information. If I have a ROM that doesn't have an sboot.bin attached to it, it will write just fine and not show any errors. However, the phone will hang up on the "Samsung Galaxy Note II" screen. If I write a ROM that tries to write sboot.bin, it fails. Every time.
 
Jiggabitties
Old
#3  
Jiggabitties's Avatar
Member
Thanks Meter 22
Posts: 68
Join Date: Apr 2011
Location: Michigan
Maybe try following the "return to stock" section of this thread:

http://forum.xda-developers.com/show....php?t=2024207

This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
 
skiahmutt
Old
#4  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
Quote:
Originally Posted by Jiggabitties View Post
Maybe try following the "return to stock" section of this thread:

http://forum.xda-developers.com/show....php?t=2024207

This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
I did. When it tries to write either image, it fails on sboot.bin. Every image that includes sboot.bin fails on sboot.bin so far. I -really- don't know what to do.
 
viper31573
Old
#5  
Senior Member
Thanks Meter 101
Posts: 457
Join Date: Aug 2012
Location: port st lucie
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
 
skiahmutt
Old
#6  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
Quote:
Originally Posted by viper31573 View Post
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.

So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
 
viper31573
Old
#7  
Senior Member
Thanks Meter 101
Posts: 457
Join Date: Aug 2012
Location: port st lucie
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you

Sent from my SCH-I605 using Tapatalk
 
skiahmutt
Old
#8  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
Quote:
Originally Posted by viper31573 View Post
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you

Sent from my SCH-I605 using Tapatalk
No worries. Thanks for the effort at least!
 
skiahmutt
Old
#9  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Dec 2013
Okay, a bit of an update... I unzipped and removed sboot from a couple of the ROMs I have, and they flashed successfully, but the phone still hangs on the "Samsung Galaxy Note II" screen... I feel like I'm on the verge of figuring this out, I -know- it's got something to do with sboot now.


Can I write JUST a bootloader to the phone without writing anything else? If so, how?
 
mike7728
Old
#10  
mike7728's Avatar
Senior Member
Thanks Meter 24
Posts: 101
Join Date: Nov 2012
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Intelligently Place Contacts on Your Home Screen with CallWho Widget

There are plenty of ways to get your contacts to show up on your … more

Control TWRP from within Android with TWRP Coordinator

You may recall that back when TWRP2 introduced a couple of years ago, it brought with … more

Keep Track of Everything Your Device Does with Event Logger

Regardless of their OS choice, computing power users generally share one common … more

A More Competitive Spin on the Addictive 2048 Puzzle

You may recall that a few weeks ago, we talked about a rather interesting take on … more