Database Info

[Q] cp_modem.bin

So here is the rundown. I flashed GC 1.9RC2.3 and was getting some force closes. Tried Data/Factory Reset and that still didn't fix the issues. So now I'm trying to reflash GC 1.9 FE to restart over and ODIN has been stuck on cp_modem.bin for the past 20 minutes.
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> dbdata.rfs
<ID:0/004> lte_modem.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> cp_modem.bin
Is this normal? I don't remember it taking this long to flash the previous time.

WilliamKingX17 said:
So here is the rundown. I flashed GC 1.9RC2.3 and was getting some force closes. Tried Data/Factory Reset and that still didn't fix the issues. So now I'm trying to reflash GC 1.9 FE to restart over and ODIN has been stuck on cp_modem.bin for the past 20 minutes.
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> dbdata.rfs
<ID:0/004> lte_modem.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> cp_modem.bin
Is this normal? I don't remember it taking this long to flash the previous time.
Click to expand...
Click to collapse
Are you using the PDA button? Did you reinsert the battery after Odin recognized your phone?

sounds like slow USB connection...try another usb port.. preferably a rear port...the modem does take a bit to flash and progress shows on device for modem

Yes I am using PDA and I have been using ODIN since my Vibrant and never had to take the battery out to flash. As far as moving the USB to a different port, if I cancel out the install right now will I be perma-bricked?
Update: So I switched USB ports and it flashed pretty quickly. I guess the port on the front wasn't cutting it.

let it go if the staus bar is moving on your device...otherwise you dont really have a choice but to turn Odin off and start over...but I guess 'YES" you can brick your device

chiahead52 said:
let it go if the staus bar is moving on your device...otherwise you dont really have a choice but to turn Odin off and start over...but I guess 'YES" you can brick your device
Click to expand...
Click to collapse
Yeah I was nervous as hell to stop the download. I just closed ODIN out first and then took out the battery. Crossed my fingers and hoped for the best. I'm glad it went through the second time because I would've been pissed if I had to send my phone off.

The only time I've seen bricks is when something happens in odin to interrupt the flashing of boot.bin

hazard209 said:
The only time I've seen bricks is when something happens in odin to interrupt the flashing of boot.bin
Click to expand...
Click to collapse
Thanks for the knowledge. Hey Hazard I noticed your name in the credits of GC 1.9RC2.3 when I flash it. Could you check out my other question regarding the G-Talk app and any suggestions you have about it would be great.

Can anyone tell me what this means?

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_KD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> param.lfs
<ID:0/003> factoryfs.rfs
<ID:0/003> data.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I get this constantly trying to flash odin PDA_KD1.tar.md5
I notice that when I boot up it only has 30mb of internal memory available.. any reason as to know why?
*************************
UPDATE!!!!!
12:17AM Central
I have fully restored my rom with Mr. bkoon1218 assistance!!!
Here's what I did just in case anyone runs into what I did. I will say what mistakes I had done and then give my resolutions that couldn't have been possible without the assistance of these awesome members!
1. I was curious on flashing a custom recovery to my device, STUPIDLY I did not read or research anything regarding this phone.
2. I flashed Cmenard with heimdall-suite-1.1.1-win32 thinking that it would give me a recovery because I thought that I had the Samsung Galaxy *Vibrant*
3.Two days stressfully googling and googling for corrections and mistakes other may have done like me I had no choice but to ask myself.
I started off in the Vibrant section and a guy helped me out with flashing the rom but still nothing. Given instructions I felt my phone was done. I would get glitches and a nasty pixelated boot.
4. I researched my phone model number on the back of my phone and realized my phone wasn't the Vibrant.. Then it banged my head when another emailed me saying it was weird that my Samsung Vibrant was a 4g device lol.
5. I then moved to Samsung Galaxy S 4g and proceeded to find help along with the research I had done.. I even tried all the Odin updates thinking that could've made the difference.
*Resolution*
1. THANKS TO ALL FOR HELPING FIRST OFF ALL!!! YOU ARE ALL GREATLY APPRECIATED!! Next! A BIG THANKS! to * bkoon1218 *
for providing me with a helpful link where I read and understood what this rom was for. LINK - http://forum.xda-developers.com/showthread.php?t=1129933
2.Downloading Hawk.zip file I then used Winrar to extract it and there are four files!
-1.SGH-T959V-CSC-TMB.tar.md5
-2.Sgs4g.pit
-3.T959VUVKC1-Phone-CL932707.tar.md5
-4.T959VUVKC1-REV00-ALL-low-CL933594.tar.md5
3. I tried Odin 1.85 and it didn't work for me however I now know the reason why and what's funny is it happend accidentally.
I forgot to uncheck Re-Partition and I thought it would immediately softbrick my phone!! I started to see however it doing it's magic!
I said "ahh might as well let it go through the process I'll just one click unbrick my phone if it doesn't do it again..". By the way I used Odin 1.7.
and poom!!!! I got a pass!!! *This was only with Checking the box Re-Partition!*
4.So I am now fully fresh back to stock and unrooted and I am done. I decided to write this for any others that go through the same problem I did. I don't mean to take anybody's credit or anything I just want other to look this up when they accidentally flash their phone with a different rom and are as lucky as I am.
**MY ENDING RESULTS**
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 is valid.
<OSM> T959VUVKC1-Phone-CL932707.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> factoryfs.rfs
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> modem.bin
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
THANK YOU ALL AND GOOD LUCK TO YOU ALL!!!!!

The lack of internal memory could be due to the amount of apps you have installed. I'm wondering if that lack of free memory is causing the problem? what ROM is currently on it (prior to you trying to flash)?
Sent from my SGH-T959V using XDA App

What rom are you trying to flash? You should try again with a different USB port after doing a battery pull and putting the phone back into download mode.

PDA_KD1.tar.md5
That's the Rom I'm flashing and it keeps failing on me.
I tried flashing it like three times again and now it just keeps vibrating every three seconds!! Its getting really annoying! Any other Odin stock Roms I can try?
At the moment I'm only rooted and have stock recovery.

Instead of flashing KD1, try KC1. Here's the link to it.
http://forum.xda-developers.com/showthread.php?t=1129933
There's only one download link in there. The .pit file goes into PIT. REV00 goes into PDA. Phone goes into PHONE. CSC goes into CSC. Do NOT change any of the settings in Odin.
KC1 gives you a 100% clean slate, so it'll remove root and CWM and it'll leave you with a stock Froyo ROM. It'll even restore Froyo bootloaders. In the event you screw something up, just Odin KC1 and it'll remove the gremlins.

bkoon1218 said:
Instead of flashing KD1, try KC1. Here's the link to it.
http://forum.xda-developers.com/showthread.php?t=1129933
There's only one download link in there. The .pit file goes into PIT. REV00 goes into PDA. Phone goes into PHONE. CSC goes into CSC. Do NOT change any of the settings in Odin.
KC1 gives you a 100% clean slate, so it'll remove root and CWM and it'll leave you with a stock Froyo ROM. It'll even restore Froyo bootloaders. In the event you screw something up, just Odin KC1 and it'll remove the gremlins.
Click to expand...
Click to collapse
Thanks a bunch. I really appreciate it. I've tried stock KC1 but I never used the pit and all the other files! Every thread I'd search for said only PDA. I've now learned something new. Thank you! I will try later tonight and to everyone that has been reading my questions A humongous thanks to you All!! You guys are the reason why this site is so helpful!

coldcrush390 said:
Thanks a bunch. I really appreciate it. I've tried stock KC1 but I never used the pit and all the other files! Every thread I'd search for said only PDA. I've now learned something new. Thank you! I will try later tonight and to everyone that has been reading my questions A humongous thanks to you All!! You guys are the reason why this site is so helpful!
Click to expand...
Click to collapse
Let us know how that works for you.
On another note, I always use KC1 as a base ROM to Odin back to Froyo. There's nothing cleaner than that.

bkoon1218 said:
Let us know how that works for you.
On another note, I always use KC1 as a base ROM to Odin back to Froyo. There's nothing cleaner than that.
Click to expand...
Click to collapse
I am currently setting up everything now to try once again thank you!

Ok so now I have flashed the files in the Hawk.zip and still getting the same fail at the end of the flash. I think I'm just gonna keep doing this until it will finally go through... what do you think?

Glad to know you got it resolved.
Btw, KC1 is supposed to have Re-Partition checked. Just remember that you almost never change the settings in Odin once you put in the proper files. I think this KC1 is the only one that has it checked though.
Now that you're on a clean slate again, have fun with GB.

coldcrush390 said:
Ok so now I have flashed the files in the Hawk.zip and still getting the same fail at the end of the flash. I think I'm just gonna keep doing this until it will finally go through... what do you think?
Click to expand...
Click to collapse
You can also follow my GB starter pack if you want to wind up on GB at the end of this. It'll be simpler. You can click the link on my signature.

[Q] Dorked up my Charge

I was attempting to follow the root instructions on the FP1 updated thread for rooting my my charge. (step 5)
This is my first time doing this so I picked up ODIN 1.85, the PIT file from IMNUTS and the 302 blue CWM link on the post. I followed instructions and got a fail. Now when I try to boot the phone I get an image of a cell phone and computer with an exclamation mark. I used the PDA setting as instructed. The error I got relates to not having a good pit or something. Did I download a corrupted file? any help restoring my phone to function would be appreciated.
ALSO: output
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 0302_charge_recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)

sometimes bad downloads do happen. try and download the PIT again, and remeber u only want re-partition checked in Odin, uncheck the other two. The PIT file MUST go in the PIT tab and the .md5 MUST go in the PDA tab, if you put it in one of the other tabs, well, UR ****ED! SO DONT DO IT!
No worries tho man, just try again and welcome to the world of a rooted Charge!
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
your phone got disconnected, thats the problem. just happened to me too. make sure ur connected to the usb in the back of ur computer. once connected put the phone down, in a place where it wont move, these connections can be quite delicate so any slight movement could cause a lost connection, and a FAIL in ODIN.

I changed usb ports and nothing. It still fails at about the 3/4 mark. when I do a test extract of the bin file I get a message about an incomplete block. I dont' have the md5 for the file so I'll start looking
just tried flashing a stock file... again with the removed command. I wonder if my cable is bad?

orcrist86 said:
I changed usb ports and nothing. It still fails at about the 3/4 mark. when I do a test extract of the bin file I get a message about an incomplete block. I dont' have the md5 for the file so I'll start looking
just tried flashing a stock file... again with the removed command. I wonder if my cable is bad?
Click to expand...
Click to collapse
Do you have the battery in when flashing? If not put it in.

You guys saved my bacon, I've installed superuser, though I'm going to let CWR die for now. I want to get tethering operational and let eclipse and the others put out a revision or two of the debloated fp1 before I fully rom up my phone.
I'm looking forward to my doing my homework on the beach thanks to this thing.

nitro already posted an eclipse fp1 debloated rom. just go to the topic that says its all the fp1 roms.

Having slept on it I may try the declared rom tonight. Thanks again guys.
Sent from my SCH-I510 using XDA

Using a stock cable is very important and unforgiving...solves most issues.
Now...if you are new to rooting/roms, etc... You jumped in at a less than stellar time....with new ota update...some kinks not ironed out yet
Sent from my SCH-I510 using XDA

I was a pro on my old droid eris. But the use of odin is still new to me. I actually don't have beef with touch wiz so de bloated roms appeal.
Sent from my SCH-I510 using XDA

Need some help plez.

Ok so yesterday I recieve this phone in my store, Galaxy s6 Edge. Customer donates no charge. I root phone last night. Accepted the OTA but didn't install. the phone acts weird last night, goes to black screen after sleep. etc etc. I go to restart phone this AM and it says FAP LOCK ON. Not sure if i messed with something in the development settings or what not. So i Download stock SPR-G925PVPU1AOCF-20150415164450.zip
I try to flash using ODIN. Phone shows up "SW REV. Check Fail Device 2, Binary :1" I am so lost and confused. :

melston1987 said:
Ok so yesterday I recieve this phone in my store, Galaxy s6 Edge. Customer donates no charge. I root phone last night. Accepted the OTA but didn't install. the phone acts weird last night, goes to black screen after sleep. etc etc. I go to restart phone this AM and it says FAP LOCK ON. Not sure if i messed with something in the development settings or what not. So i Download stock SPR-G925PVPU1AOCF-20150415164450.zip
I try to flash using ODIN. Phone shows up "SW REV. Check Fail Device 2, Binary :1" I am so lost and confused. :
Click to expand...
Click to collapse
Why root then try to download an OTA? You cant install an OTA if you are rooted. It has to be totally untouched stock rom/boot partition, etc.
Not sure what issue you may have created. You should have only DOWNLOADED The OTA files to be stored. It sounds like no installation was initiated. It likely would have errored out on you and said OTA could not be applied had you been rooted. Perhaps the OS later auto-installed the OTA updated and causes this issue. There is relevant discussion to this same error here: http://forum.xda-developers.com/showthread.php?t=2489980
Sounds like you soft-bricked it in which case its a pretty easy fix. See here: http://forum.xda-developers.com/showthread.php?t=2483380
btw, all of this takes 5 seconds of searching. :crying:

Alpine- said:
Why root then try to download an OTA? You cant install an OTA if you are rooted. It has to be totally untouched stock rom/boot partition, etc.
Not sure what issue you may have created. You should have only DOWNLOADED The OTA files to be stored. It sounds like no installation was initiated. It likely would have errored out on you and said OTA could not be applied had you been rooted. Perhaps the OS later auto-installed the OTA updated and causes this issue. There is relevant discussion to this same error here: http://forum.xda-developers.com/showthread.php?t=2489980
Sounds like you soft-bricked it in which case its a pretty easy fix. See here: http://forum.xda-developers.com/showthread.php?t=2483380
btw, all of this takes 5 seconds of searching. :crying:
Click to expand...
Click to collapse
where is pit for this phone?

melston1987 said:
where is pit for this phone?
Click to expand...
Click to collapse
SPR-G925PVPU2BOF7-20150702235910.zip - Upple.it
it seems to be progressing...half way through. FINGERS crossed:good:

melston1987 said:
SPR-G925PVPU2BOF7-20150702235910.zip - Upple.it
it seems to be progressing...half way through. FINGERS crossed:good:
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU2BOF7_G925PSPT2BOF7_G925PVPU2BOF7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

melston1987 said:
where is pit for this phone?
Click to expand...
Click to collapse
Where did you get the PIT file?

Can't restore note 5 to stock

I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed

I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/

no firmware seems to be working. I also tried a new cable and a few ports. No change.

tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.

Are you using 3.10.7?

I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.

Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk

I've done it by using teamwin, also by holding pwr + home + volume down

guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to

Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.

So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.

Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.

Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..