Database Users

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?

this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App

merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.

skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?

cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.

yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??

rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)

ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it

rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.

skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B

vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.

I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this

Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.

I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help

Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7

Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.

Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App

May god bless you and your children, and your childrens children, and their children!!!!!!!!!

[Q] Stuck with phone ! pc screen. Help?

I was using Odin to install [KERNEL] stock+Voodoo stable 5.x for Vibrant and something went wrong, I'm not sure what but now I am stuck with the phone ! pc screen.
Odin will not recognize that there is a phone there if I just start a download Odin tells me <OSM> All threads completed. (succeed 0 / failed 0)
In another thread (whose fix didn't help me out) I read
masterotaku said:
Because..... "Phone ! PC" is not a hard brick. I've "Phone ! PC" bricked my Vibrant dozens of times.
Glad you've recovered though. It can be a scary screen if you're not used to seeing it!
Click to expand...
Click to collapse
Are there other recovery techniques?

Did you get where it says Download Mode? If not, take the battery out, put it back but don't turn on the phone. Then open Odin load the pit files and pda. The next step with the phone off, hold the volume up and down the same time and plug the usb cable while holding up and down buttons and voila....you will have COM # showing up in your Odin and ready to flash again
Check here :http://forum.xda-developers.com/showthread.php?t=810130&highlight=odin

dany865, following your instructions Odin did recognize that there was a phone attached. 0:[COM5] and I'm flashing the PIT and PDA from the thread you linked me to now. It's a slow moving process!
So slow that I swear it was frozen so I took and chance and closed ODIN, after all what was the worst that could happen I was already staring at a brick, and rebooted the phone. PRESTO, it was back to JI6.
I went straight to MiniKies and put 2.2 on that phone, then spent a bunch of time reinstalling applications and configuring ADWlauncher.
So far all I know for sure that was lost was my finely tuned setup, root access, and a month of SMS messages that were not backed up.
Thank you!

I you are gonna root I would highly recommend to get "Titanium backup pro". It makes the setting up process 10x's faster and has a tin of other great features.

Update Bricked Phone?

Received a OTA update yesterday on my Rooted, Samsung Fascinate. After the update phone hangs on boot screen. Powering the device while holding the volume buttons gives me the Android System Recovery <3e> Screen. On this screen I have a bunch of E: Failed to open Recovery, cache, data kernal etc. (I can give all specifics if needed)
If I press the home button I get what looks like a screen to update the phone (Android Character with Triangle) From here I tried the instructions from the "How to recover from any brick" thread. Neither method is working. Any ideas?
From the boot screen I am also not able to scroll up or down to select a wipe apply update from SD Card etc.
Any help would be appreciated.
Thanks

I don't know how to fix it (don't get discouraged I don't know a lot in this area) but it seems to me if you play your cards right you might be able to complain to verizon and get an early upgrade out of it. A galaxy nexus would look mighty fine in your pocket.

probably a conflict with being rooted when it updated. Odin back to stock and update completely and then re-root.
Sent from my icecream fast

1. Download this file to your PC get you to a rooted ROM with the proper recovery: http://www.mediafire.com/?d0wha8lc1hjxxdf/geewiz-2.3-fullwipe-11302011.tar.md5 (this is the EH03 GeeWiz Odin Package ROM by djp952)
2. Boot phone in download mode by powering phone off, hold down vol button on phone, connect cable to PC (there is no need to remove battery)
3. Open Odin and Place the GeeWiz file you just downloaded into the PDA slot, click Start
4. Your phone should now be on the EH03 GeeWiz ROM
5. If you want to flash a different ROM, download the zip file for the ROM of your choice onto your phone (use the phone to download it), reboot into Recovery (what you booted into before is the stock Samsung recovery, not the Clockwork Recovery you need), choose "install zip from sd card", select "choose zip from sd card", choose the Download folder (the folder in which your zip file should appear), choose that zip file, and install.
6. Profit.
Has anyone seen John Connor?

I gave this a shot, and I am thinking either my phone is not in "Download Mode" if that's possible or its a driver issue. Here is the response I get from Odin V1.83
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> geewiz-2.3-fullwipe-11302011.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I have multiple Samsung Cables (I tried all of them) but it is possible I am not using the one that came with this phone (Could this be an issue?)
I am using windows 7 64 X64 The phone shows up in the in the device manager as LibUsb>Samsung Andriod
On the recovery screen I have noticed if I push the home button it flips between the Android and the Triangle to a screen that shows all the files the boot loader cannot find. Does it matter what screen I am on when I try the upload?
Thanks in advance for any advice for a n00b!

You need to download the Samsung USB drivers for your PC, as it appears to be not recognizing your phone properly. You should be able to find what you need on Samsung's website. Hope this works.
Has anyone seen John Connor?

Ok So I have removed / Re-Installed the drivers on 2 different machines (One Win 7 64 Bit other is Win Vista 64 bit. I get the same results on both machines. Any other ideas?

Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.

mentose457 said:
Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.
Click to expand...
Click to collapse
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!

Found a few threads on Verizon forums. Sounds like there have been a few people run into the same issues. Anyone tried returning a rooted phone to Verizon? If so and they caught it what were the repercussions?

ascottn said:
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!
Click to expand...
Click to collapse
Just to be clear, you are putting the phone in download mode then installing the drivers via zadig right? That should work.
loading drivers in windowz is the most retarded thing in the world. You dont happen to have access to a computer running linux do you? Heimdall works flawlessly in linux.

Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"

ascottn said:
Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"
Click to expand...
Click to collapse
To enter download mode power off your phone, pull the battery, hold the volume down button while plugging in your phone. The screen should show a yellow triangle with the Android guy in the middle.
Sent from my SCH-I500 using XDA App

I have been digging around and I stumbled onto the correct procedure for getting to download mode. I don't know how I missed this *FACEPALM*
I want to say thanks to everyone. I am back up and running. Thanks to all for the help!

Excellent! I was starting to think you had a hardware problem as in a faulty micro USB port on the phone...
Has anyone seen John Connor?

Would just like to add that the 2.3 OTA soft bricked my fathers stock phone. I am now hunting the non rooted file in another thread to odin or heimdal back to 2.2 to alow me to try again.
Verizon LVL 2 says he checked and I am the first customer to report a bricked phone from the OTA to 2.3. Yea... right.

Here is the guide I followed to get my phone back to stock (It includes download links for stock roms.
This is the one part missing from this tutorial. Probably because it assumes that these steps are known if someone has bricked a phone
make sure u have your samsung usb cable plugged into the pc but not into the phone (not yet at least) and make sure u remove your battery.
step 1. hold down the volume down button and continue holding
step 2. whille still holding down the volume down button, plug your phone into the usb cable
step 3. while still holding down the volume down button, pop your battery in.

Cant flash stock 6.01 - needs PIT file!?

Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.

fredphoesh said:
Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.
Click to expand...
Click to collapse
Hi make sure in device manager the com number is the same as the one you see in Odin

pimpdaddy00 said:
Hi make sure in device manager the com number is the same as the one you see in Odin
Click to expand...
Click to collapse
Hi
I don't see how to check that. In Odin, it says COM7 but in device manager, what device am I looking for?
tx Mark

fredphoesh said:
Hi
I don't see how to check that. In Odin, it says COM7 but in device manager, what device am I looking for?
tx Mark
Click to expand...
Click to collapse
Okay go to device manager, look for modem, you shouod see Samsung Usb Modem, right click on that, click properties, go to advanced tab, click advanced port settings, then change to com 7

pimpdaddy00 said:
Okay go to device manager, look for modem, you shouod see Samsung Usb Modem, right click on that, click properties, go to advanced tab, click advanced port settings, then change to com 7
Click to expand...
Click to collapse
Hi
Thanks, yep, both were already on port 7.
I wonder if there is a problem with the motherboard. This is something else I have been reading.
Mark.

fredphoesh said:
Hi
Thanks, yep, both were already on port 7.
I wonder if there is a problem with the motherboard. This is something else I have been reading.
Mark.
Click to expand...
Click to collapse
Hmmm, strange, try redownloading the stock firmware it may have gotten corrupted, if that doesn't work install the latest drivers for the note 4 without it plugged in, then reinstall them with it plugged in

pimpdaddy00 said:
Hmmm, strange, try redownloading the stock firmware it may have gotten corrupted, if that doesn't work install the latest drivers for the note 4 without it plugged in, then reinstall them with it plugged in
Click to expand...
Click to collapse
Thanks mate, I will give it a go.
I had actually downloaded two versions of 6.01 for the uk, one was uploaded in April, the other in June... both have this same issue.
I'm thinking there must be a hardware problem.

fredphoesh said:
Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.
Click to expand...
Click to collapse
Put your phone in download mode and read the first line on top left, it should say 910F. If it doesn't that may be your problem.
In either case you can try the emergency software recovery and initialization from Smart Switch from your pc/laptop .. all you need is a good internet connection and write down your device S/N where you can find this on the back of your phone (beneath the battery).
1. Download and install SmartSwitch from Samsung web
2. Run SmartSwitch from your PC/Laptop
3. On the upper right corner of SmartSwitch you'll find "More" option and click that
4. Choose "Emergency software recovery and initialization" and it will open a new window
5. Click on "Device Initialization" tab
6. Enter your phone Model name... which i pressume SM-N910C and then click "Search"
7. Now enter your device S/N and then click "OK"
8. A new dialog box will show up, click "OK"
9. Another dialog box which will say about initialized version... click "OK"
10. Yes, another dialog box which say that software update and initialization for galaxy note 4 will now start, the "OK" button is greyed out so you can't click it just yet.
11. Put your device to Download Mode
12. Connect your device to your PC/Laptop
13. The "OK" button will turn blue then click it and follow the rest of the procedures.
14. Once it finished, your device will reboot.
All this process will take time depend on your internet connection, good luck...

I've tried that. Kies downloads the ROM then says it's list connection with the phone... And that I should reconnect the phone and try again. The phone doesn't boot at all now, all I can do is get to download mode.
Sent from my Pixel XL using Tapatalk

fredphoesh said:
I've tried that. Kies downloads the ROM then says it's list connection with the phone... And that I should reconnect the phone and try again. The phone doesn't boot at all now, all I can do is get to download mode.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I edited my post with more detailed instructions, however you didn't mention if your phone is a 910F based on download mode.

mangui said:
I edited my post with more detailed instructions, however you didn't mention if your phone is a 910F based on download mode.
Click to expand...
Click to collapse
Hi
I entered download mode, plugged the phone in and Smart Switch says "Unsupported device"

fredphoesh said:
Hi
I entered download mode, plugged the phone in and Smart Switch says "Unsupported device"
Click to expand...
Click to collapse
Well, sounds like defective hardware

Just take out the battery from the phone. There is a label inside the phone, for the model number right there. Did you check that the phone's "reactivation lock" is off?
Take a look at this thread:
https://forum.xda-developers.com/note-4/help/advice-greatly-appreciated-t3620491

Getting this error in Odin: Complete(Write) operation failed.

Been using an old.... make that, ancient SCH-I500 for a few years on Page Plus Cell with no problems. Today, it got stuck in a weird boot loop. Tried booting into recovery mode and that's when it totally died. Right now, I can hook it up to my PC and have the yellow Android icon up and I'm guessing it's in Download mode. I've followed guide after guide after guide here and nothing is working. A lot of the factory ROM links are dead but I found a stock GingerB rom I think and when flashing with Odin, it gets towards the end and I see, "MOVINAND" in yellow but after 5-10 minutes, it dies out with an error about 'write operation failed'.
I'm close to just tossing in the towel and getting a new phone. Because money is tight, I'd like to just reload the factory ROM on this thing and see if I can keep using it. But if I need to buy a new phone, I guess I will.

To save you as long as it is not hard bricked, follow these steps.
Get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
And please make sure you got the drivers and that a COM port does show up in odin.