Help Please HELP with Odin

[bzduzit32]

Thanks in advance for reading. It's been a strugle today, and finally I rooted my note 3 (verizon) but now when I power it up it stays on the Verizon screen.
I wasn't able to root it using Odin, and fixing it is the same problem. I rooted it using vroot. Anyway I am using Odin v 1.85 and all it will get to is

<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..

Sometimes it says 0/006 as well as sometimes it fails. It failed all the time when trying to root or was stuck at Mapping. I switched usb cables. Is there anything anyone can please suggest so I'm not out a phone. Under Pda is there a different recovery I can try? Not sure if i downloaded the right one. Thanks so much in advance for reading.

<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Is what I get when it fails..

 

[Rukbat]

I don't know the file names for the Verizon model, but you might want to check the Verizon Note 3 section over at XDA. They probably have a thread on reflashing it to 4.3 with Odin, files included. (They do for the AT&T version.)

If, using the correct files, you still get the failure in writing the NAND, there's a physical failure. Do a factory reset, use Kies to do a reflash or, if that fails, an emergency reflash. If it fails at that point, it can't be read, so bring it back to Verizon and ask them if they can reflash it for you. (They probably won't be able to and will replace it. In the future, use Kingo to root it. It's worked on thousands of Note 3s without tripping Knox.)

 

[bzduzit32]

I don't know the file names for the Verizon model, but you might want to check the Verizon Note 3 section over at XDA. They probably have a thread on reflashing it to 4.3 with Odin, files included. (They do for the AT&T version.)

If, using the correct files, you still get the failure in writing the NAND, there's a physical failure. Do a factory reset, use Kies to do a reflash or, if that fails, an emergency reflash. If it fails at that point, it can't be read, so bring it back to Verizon and ask them if they can reflash it for you. (They probably won't be able to and will replace it. In the future, use Kingo to root it. It's worked on thousands of Note 3s without tripping Knox.)

Thanks so much I appreciate the quick response. If there is any other feedback I would appreciate it. Yes I will use Kingo next time. Still can't believe this happened.

 

[Rukbat]

That's one phone. My first Note 3 was bricked by an OTA (and in a way that set toe OS to "custom". The replacement did exactly what yours is doing. The third one seems to be working well - the only problem is ROM size. I only have 4 Safestrap slots and I want more ROMS in there. (And the ability to switch between 4.3 and 4.4 ROMS.)

 

[bzduzit32]

I agree, I never had problems like I did. I ended up staying up like 9 hours and fixed it. What I did was download the original firmware and during Odin I unplugged it, thought it was stuck, I then got a message that the firmware wasn't installed right (something like that)

So what I did considering I had the right firmware was use the Verizon recovery software that was installed on my pc and it recovered after like an hour and a half.


So now it's rooted, good shape. The thing is im getting a new one on Monday because VZW couldn't do anything and my insurance for it is free if it's a "software problem"

THANKS SO MUCH FOR THE HELP AND INPUT

 

[recDNA]

What is verizon recovery software and where do you get it? I've never heard of a user having this?