[Q] Bricked, recovered, OTA'd, bricked again. HELP! - Verizon Samsung Galaxy Note II

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/showthread.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.

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.

Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.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.

Jiggabitties said:
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.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.
Click to expand...
Click to collapse
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.

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

viper31573 said:
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
Click to expand...
Click to collapse
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.

skiahmutt said:
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.
Click to expand...
Click to collapse
not sure what else to tell you that would help

viper31573 said:
not sure what else to tell you that would help
Click to expand...
Click to collapse
Well, the best place I can think to start is to nail down exactly what's happening, then try to figure out WHY it's happening. Once I know the what and why, the solution should be apparent. While I'm not against someone chiming in with a fix that works but I don't understand, I'm here to learn, and would like to come to a better understanding of the issue.
First: what is sboot.bin?
Second: do I need a specific sboot.bin for a specific ROM?
Third: what can cause sboot.bin to fail?
Fourth: is there a way to push just sboot.bin to the phone through Odin or other software?
Fifth: am I fixating on sboot.bin when it's not my issue?
Sixth: did you really read my whole post and get to this point? Wow, thanks! I appreciate you taking the time to try and help me, folks like you are what make the community so strong!

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

viper31573 said:
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
Click to expand...
Click to collapse
No worries. Thanks for the effort at least!

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?

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

also try flashing the pit file.

mike7728 said:
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
Click to expand...
Click to collapse
I think it was the 4.3 update. So, what's the knox bootloader, and what ROM can I flash to the phone that'll work with the knox bootloader?

Related

Updating crazyness.

I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!

[Q] [HELP] GT-i9100 Unflashable via ODIN

Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).

[Q] Boot loops, Kies can't update the device, only rom that will boot is CM9...

I'm having strange problems with an I9300 I'm trying to fix for friend. Now unfortunately I end up doing things like this not because I know anything about these things, but because I'm I'm slightly more computer literate than the rest of my group of friends, so I'll apologise now if these are stupid questions, I have searched but could find nothing.
Now last night my friend comes to mine with his phone stuck in a boot loop. Now beyond the fact it already had a custom ROM on it I can tell you nothing except he claims he installed AVG and it happened. So I reboot into Windows, start up Kies, and see what I can do. Which so far has been:
1) Try to perform an Upgrade and Initialisation. Jump through the hoops, end up with the message "This device's version cannot be updated."
2) Ok, that didn't work. Hit sammobile to find a stock rom and fire up Odin. Ohh success...
3) Oh noes, too soon. The Samsung chime cuts off early and it's stuck with a pulsating logo.
3) Ok well maybe a downgrade first? Get a 4.1 stock rom and try again. Odin sees no problems again, the chime plays fully. But nope, it's just a longer boot loop.
4) After much head scratching and just trying random stuff I end up finding CM9.1 will boot fully, but the EFS data is screwed. This is the only rom I've found so far that will boot.
So from where I started I'm closer and if the radio worked this would be fine. Now the only suggestion I've heard to get the radio working is flashing a stock rom through Kies but I have no idea how to get Kies to play along. Any ideas?
Thanks.
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
123c
boomboomer said:
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
Click to expand...
Click to collapse
I did actually try that before flashing 4.3 with Odin and after. Was still stuck in a boot loop... :/
Thanks

"Unauthorized Verizon Software"

So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!
xanderharris86 said:
So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!
Click to expand...
Click to collapse
No, the bootloader can't be unlocked. You can at least get root with saferoot on 4.3.
Or downgrade with mobile tech videos

[Q] S4 bricked, Can't get Odin to work

I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
delsoul6 said:
I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
Click to expand...
Click to collapse
Did you make sure Odin found the S4?
delsoul6 said:
I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
Click to expand...
Click to collapse
You're trying to flash a version that's too old. There's a check in place called rollback protection that prevents you from using older versions of software. I'd try flashing NC5 or NK1 via tar. Let me know if you need more help.
FIXED!
Thanks guys. I really appreciate your input. I was so desperate a actually went to a Verizon store in the morning even though I had no faith they would do anything. I just told them it wouldn't boot after I wiped it and they said we don't fix phones we only give replacements. Thanks for nothing. I saw some people posting that Odin failed on one computer and worked on another so I figured I'd try on my work computer. I downloaded an NK1 .tar file from SamMobile this time instead of the xda thread. It worked the first time. No problems at all. I have no idea why it worked but I'm just thankful it did. My phone is running like new.
delsoul6 said:
Thanks guys. I really appreciate your input. I was so desperate a actually went to a Verizon store in the morning even though I had no faith they would do anything. I just told them it wouldn't boot after I wiped it and they said we don't fix phones we only give replacements. Thanks for nothing. I saw some people posting that Odin failed on one computer and worked on another so I figured I'd try on my work computer. I downloaded an NK1 .tar file from SamMobile this time instead of the xda thread. It worked the first time. No problems at all. I have no idea why it worked but I'm just thankful it did. My phone is running like new.
Click to expand...
Click to collapse
Glad to see the issue was resolved :good:
It's pretty difficult to permanently brick these devices, just takes a little patience and the know-how.
ryanbg said:
Glad to see the issue was resolved :good:
It's pretty difficult to permanently brick these devices, just takes a little patience and the know-how.
Click to expand...
Click to collapse
Agreed! This is the only thing I really like Samsung for is Odin! Now if LG or Moto could put in a form of Odin it would make them way more appealing!

Categories

Resources