Questions about Unlocking or Recovering from a Soft Brick? LOOK HERE BEFORE POSTING!!

[ArcelasTheNoob]

ODIN fails at Modem.bin. I have tried 13 times

I have read everything on this site, and just about every other site on the web. Every answer is the same. "Try again" As I work in IT, I am very familar with this "fix", as I use it every day for a variety of issues.

Just one question: If I have tried it 13 times, using every port, every ODIN version, etc., is my phone just toast? Do I have an $800 paperweight now?

I tried the Root66 stock VRALJB 4.1.1 12/2/12, and it worked. Sort of. I now am back on stock but I cannot get past the eternal activating with Verizon screen. Any ideas?

 

[droidstyle]

I have read everything on this site, and just about every other site on the web. Every answer is the same. "Try again" As I work in IT, I am very familar with this "fix", as I use it every day for a variety of issues.

Just one question: If I have tried it 13 times, using every port, every ODIN version, etc., is my phone just toast? Do I have an $800 paperweight now?

I tried the Root66 stock VRALJB 4.1.1 12/2/12, and it worked. Sort of. I now am back on stock but I cannot get past the eternal activating with Verizon screen. Any ideas?

did you try booting into recovery and wiping data

 

[Rojo623]

All of a sudden stuck on boot screen. TWRP Recovery still accessible. No ROMs working

Out of nowhere my phone is stuck on the "Samsung Galaxy Note 2" boot up screen on my Vzw Note 2 and no Beans ROMs are getting through. I can still access my files through TWRP, but can't get past the Samsung Galaxy Note II startup screen. Flashed Beans build 19, 20 and 21 so far, with no luck. Been doing a Dalvik and cache wipe, and most recently did a full factory reset. - no luck, still stuck on the boot screen.
Any thing else I can try? Anyone ever had this issue? any help would be appreciated.

 

[droidstyle]

Out of nowhere my phone is stuck on the "Samsung Galaxy Note 2" boot up screen on my Vzw Note 2 and no Beans ROMs are getting through. I can still access my files through TWRP, but can't get past the Samsung Galaxy Note II startup screen. Flashed Beans build 19, 20 and 21 so far, with no luck. Been doing a Dalvik and cache wipe, and most recently did a full factory reset. - no luck, still stuck on the boot screen.
Any thing else I can try? Anyone ever had this issue? any help would be appreciated.

odin back to root66, wipe data, then flash back to beans.

 

[Rojo623]

odin back to root66, wipe data, then flash back to beans.

Thanks! gonna try this soon but was hoping to avoid it.

 

[pspslyspy]

Root66 is what bricked my note 2 back when I w was having issues. Be careful.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

 

[Rojo623]

Root66 is what bricked my note 2 back when I w was having issues. Be careful.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

Actually was able to save myself. Just flashed stock ROM like 3 more times and just waited overnight with the screen on the boot. It eventually went through and now was able to flash back to Beans. Made no sense, but I'm back up and running. thanks all for your suggestions.

 

[pspslyspy]

Feels amazing when you get it figured out and working huh?.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

 

[spartn1]

Still having trouble getting casual to work

Never shows connected.

[ERROR]There was a problem while excuting the command. C:\Users\SPARTA~1\AppData\Local\Temp\CASUALSpartandad-2013-08-17-08.32.37\adb.exe devices

seems to be what it keeps saying

I'm sure I am doing something stupid but can't figure it out.

---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------

I am using windows 8. Seems to be a drivers issue but I have removed all drivers and still nothing

 

[droidstyle]

Root66 is what bricked my note 2 back when I w was having issues. Be careful.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

root66 didnt brick anything...user error did.

 

[pspslyspy]

root66 didnt brick anything...user error did.

Nope your very wrong!

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

 

[spartn1]

Okay now I am back to stock and ready to try this again

I also had a problem with root66 but it could very well be user error. I was able to get back to stock, doing ota update now, then will try again to do 1 click.

 

[droidstyle]

Nope your very wrong!

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

then it was a bad download.

 

[pspslyspy]

Nope your very wrong!

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

That is prolly closer to right as I tried 6 different times 2 days ago to make sure I was doing it right, and everytime I got the red droid after followed by error from verizon.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

 

[droidstyle]

That is prolly closer to right as I tried 6 different times 2 days ago to make sure I was doing it right, and everytime I got the red droid after followed by error from verizon.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

well being that file has been downloaded over 1k times, you are the first person to claim it bricked your device...so whats that tell ya?

 

[pspslyspy]

well being that file has been downloaded over 1k times, you are the first person to claim it bricked your device...so whats that tell ya?

Read back in this thread, there is others, also google search it, there is over 100 that have said it has messed up their phone after multiple tries.

SCH-I605 rooted, custom boot loader, still deciding on which rom to use.

 

[droidstyle]

i have read the thread, i am the one who wrote it. root66 didnt brick anything. you do not know the definition of brick evidently. some have been stuck in a bootloop that required a
data wipe from recovery.

 

[coma73]

I can only seem to post here, so sorry if wrong place.

I had root and I was rommed I tried to install a version of p.a. that was supposedly for twrp and somehow could no longer get into recovery or to flash.

Eventually I ended up with the Verizon error.

Anyway now I'm on the right track I hope but I cent get Odin to recognized the zip files I downloaded.

I tried redownloading and unzipping using 7 zip a few times.

Any ideas?

Bye the I'm on vramc3

 

[droidstyle]

I can only seem to post here, so sorry if wrong place.

I had root and I was rommed I tried to install a version of p.a. that was supposedly for twrp and somehow could no longer get into recovery or to flash.

Eventually I ended up with the Verizon error.

Anyway now I'm on the right track I hope but I cent get Odin to recognized the zip files I downloaded.

I tried redownloading and unzipping using 7 zip a few times.

Any ideas?

Bye the I'm on vramc3

you need to restore the driver for odin. there is a link for it at the bottom of section 1b in the guide.

 

[nh97103]

I am rooted, unlocked, and on 4.1.1 VRALJB. Can someone please provide a link to the update.zip for the latest update to 4.1.2? Having a little trouble finding this. Or can I just use Odin and flash it like it says to on section 1b here: http://forum.xda-developers.com/showthread.php?t=2024207 ? I want to be 100% sure as to not screw anything up.

Thanks in advance!