Android Alliance

I'm downloading them again to make sure that they didn't get corrupted transfering them from work computer to home computer

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


Same thing flashing just the AP file. Like I said, I'm downloading the firmware again just to test and make sure

MartianMonkey wrote:<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


Same thing flashing just the AP file. Like I said, I'm downloading the firmware again just to test and make sure

Here is a list of things to check and recheck in this thread. viewtopic.php?f=34&t=557&hilit=Odin

Sent from my SAMSUNG-SM-N930A using Tapatalk

Also, here in this thread a guy reinstalled the drivers and that worked. viewtopic.php?f=37&t=516&hilit=Odin

Sent from my SAMSUNG-SM-N930A using Tapatalk

I see on the other thread that Win10 might have issues, trying on my work laptop that has Win7 on it
Fingers crossed.

MartianMonkey wrote:5151 I see on the other thread that Win10 might have issues, trying on my work laptop that has Win7 on it
Fingers crossed.

No doubt yo. Fingers crossed. I'd double check the drivers too. =]

Peace to the Alliance, got 3 day doomsday countdown from Sprint, joined to see if trying something different might help since my own skills & other pk disablers havent helped....

Well tried again and failed again, I guess I'm gonna have to give up my Note7

MartianMonkey wrote:Well tried again and failed again, I guess I'm gonna have to give up my Note7

Did you try switching your usb mtp to ptp?

Sent from my SAMSUNG-SM-N930A using Tapatalk

did earlier but I will try again, I noticed on my phone screen it has
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
after it fails in odin

I switch the usb mtp to ptp under developer options correct?

MartianMonkey wrote:I switch the usb mtp to ptp under developer options correct?

Correct.
I'm hoping that it isnt that they encrypted the bootloader. I'm looking into a few things. This is also happening to some others. So, it may take a little time. But, don't give up just yet. =]

Sent from my SAMSUNG-SM-N930A using Tapatalk

MartianMonkey wrote:I switch the usb mtp to ptp under developer options correct?

If you could send me some pics somehow it would help.

Sent from my SAMSUNG-SM-N930A using Tapatalk

I just read this article (first paragraph) about how users can continue to charge their Note7 after depleting the battery down to 0% Is this true? Doesn't sound right. If so, it could help those who got the update.
https://www.sammobile.com/2017/01/05/ve ... re-update/

Show us your driver's when you plug in you note