Database Develop

stuck at samsung galaxy note n-7000

after i wrongly flshed criskelo rom(isntantly flashed rom in cmw whit out anything i forgoted ) my phone can't boot!
stuck at samsung galaxy notetryed every rom and...
after wrongly..! i followed root galaxy note .com steps exactly
event can't boot whit parandroid rom that i did tryed befor that!
trying too unroot to STOCK GB whit ODIN http://rootgalaxynote.com/galaxy-note-unroot/how-to-unroot-galaxy-note-gt-n7000/

kamranhaghighi said:
after i wrongly flshed criskelo rom(isntantly flashed rom in cmw whit out anything i forgoted ) my phone can't boot!
stuck at samsung galaxy notetryed every rom and...
after wrongly..! i followed root galaxy note .com steps exactly
event can't boot whit parandroid rom that i did tryed befor that!
trying too unroot to STOCK GB whit ODIN http://rootgalaxynote.com/galaxy-note-unroot/how-to-unroot-galaxy-note-gt-n7000/
Click to expand...
Click to collapse
Flash gb rom by using PC ODIN. After flashing gb rom go to recovery and wipe data and cache. Try this method.

ty but can u give me a link? i jsut founded this http://forum.xda-developers.com/showthread.php?t=1424997
i can't download but i did 1 time and can't pause and download speed is 2kb/s:| its 3:50 am and i jsut waiting for linK plz somone give me one tomarow i most go for my wimax because it had delay for 8 days and still waiting

any GB/\ ROM? i tryed a rocket rom GB from CWM but still stuck anyway im download ODIN version and waiting to download!
or stock?

kamranhaghighi said:
any GB/\ ROM? i tryed a rocket rom GB from CWM but still stuck anyway im download ODIN version and waiting to download!
or stock?
Click to expand...
Click to collapse
You must flash stock GB rom only, using odin.

jeetu1981 said:
You must flash stock GB rom only, using odin.
Click to expand...
Click to collapse
+1, yes PC ODIN only
Dont flash ics rom and do the wiping in data, it will hardbrick your phone. WARNING DONT WIPE IN ICS RECOVERY DATA OR FACTOCRY RESET OR DO NANDROID IT WILL SUPERBRICK YOUR PHONE.o

ok can u give me a link plz fast! and superbrick is unfixable?

kamranhaghighi said:
ok can u give me a link plz fast! and superbrick is unfixable?
Click to expand...
Click to collapse
This link might be helpful....its a pre rooted gb rom thread, can b used in pc odin....
All d best...!!!:good::good::good:
XDA Thread:
http://forum.xda-developers.com/showthread.php?t=1535025

thanks downloading no wipe

GOD WHY? all links are from hotfile ;( unluky badly unluky

this http://forum.xda-developers.com/showpost.php?p=25289773&postcount=207 saved me
i'm following this video now whit my 4-10kb/s net speed:| it takes 1h to load i can't wait for my wimax!
http://www.youtube.com/watch?v=ehXcnqntsro

afte that i see someting like isntalling updates than it stuck at galaxy note n7000 again
can i return my phone? some 1 help me plz

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
thats log but still stuck at samsung galaxy note n-700 logo
PLZ i wont lose my 1300$ expancive device

kamranhaghighi said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
thats log but still stuck at samsung galaxy note n-700 logo
PLZ i wont lose my 1300$ expancive device
Click to expand...
Click to collapse
Stuck at Samsung logo is normal if you flash GB rom over ICS, just go to recovery (vol up+ home + power) and perform wipe and reboot.
As you are on Gingerbread now, it is safe to perform full wipe in stock recovery.

jeetu1981 said:
Stuck at Samsung logo is normal if you flash GB rom over ICS, just go to recovery (vol up+ home + power) and perform wipe and reboot.
Click to expand...
Click to collapse
This will solve your issue
Sent from my GT-N7000 using xda premium

THANKS REALLY but if not work can i pm u?^_^

did a wipedata/factory reset in stock recovery but still stuck at samsung galaxy note GT-N7000

kamranhaghighi said:
did a wipedata/factory reset in stock recovery but still stuck at samsung galaxy note GT-N7000
Click to expand...
Click to collapse
replied to your pm, please check it.

and one mroe thing
i did this! Nandroid Backup and Restore:
You are able to do Full Nandroid Backups on CF-Root Kernel. But you have to restore them using Abyss Kernel 4.2!!!
If you try to Restore with CF-Root, your Restore will hang up and you will at least lose Root
(befor lfashing GB whit odin!

waiting to recive ur repalay! it takes long time whit irans net:S

Odin help please!!!!

Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks

EFCLEE said:
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
Click to expand...
Click to collapse
Did you select the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.

jeetu1981 said:
Did you selected the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
Click to expand...
Click to collapse
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?

EFCLEE said:
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
Click to expand...
Click to collapse
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.

jeetu1981 said:
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
Click to expand...
Click to collapse
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!

EFCLEE said:
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
Click to expand...
Click to collapse
Cool... Consider urself lucky this time
And click on thanks is better than million thanks, lol
Sent from my GT-N7000

[Fixed] First time rooting, accidentally flashed wrong ROM what to do from this point

EDIT: Rebooted my computer and phone and it flashed fine. Thank you for all the help. I'm off to explore the world of custom roms.
Finally decided to root my phone and install CM9 from GB 2.3.6 with the LA4 Kernel. Downloaded everything I needed as per Post 3 of this thread. Accidentally flashed the newer kernel instead of the pre rooted ROM.
Realizing my mistake, I tried flashing the correct ROM and PC Odin gives me a failure. The phone won't boot, it just stays stuck on the Galaxy Note N7000 Logo with an exclamation mark at the bottom.

Check if you have cwm (power+home +volume up) If so then flash this get the standard version, then go advanced options and reboot recovery...
After that do all wipes data/cache/Dalvik cache then flash the cm9 for n7000,then flash cm9 GApps then reboot...
After the system boots to android set it up and download triangle away and use it to get rid of the yellow triangle
If you don't have cwm then download a stock GB rom and flash it via odin... Start from scratch
Cheers
Tapatalking on my GT-N7000

what is the error pc odin giving you?

Don't quite remember anymore since it was from this morning. All I recall is the little box on the top left going red.
Could I try replicating the problem or do I risk damaging my phone?

odin won't damage the phone. As above poster said check if you have cwm, else use Odin again

nokiamodeln91 said:
odin won't damage the phone. As above poster said check if you have cwm, else use Odin again
Click to expand...
Click to collapse
No, I don't have CWM so I've been downloading a stock rom since I saw that post should take an hour with glorious third world internet. In the meantime should I fish out that error message you requested or is it not worth it at this point?

If you need all data back and everything to be working I would recommend you to flash back the same ROM you had earlier using odin.
Go back to Square 1.
Then root it from Dr Ketan's post.

as you downloading the rom. you are going to use Odin again. Let know the error

Yeap, another fail while using PCOdin.
Going to install samsung USB drivers from the file in this thread and get rid of Kies.
Here's the stuff from the little window.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/007> Added!!
Edit: Tried again after reinstalling drivers. Still no go.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

great

Bricked Phone after trying to downgrade to 4.4.2 using odin

upgraded to 5.0 but then decide to see if I could downgrade and I bricked my phone trying to use Odin with the 4.4.2 files. Any suggestions or anyone going thru something similar?

Is it a hard brick? Can you get in recovery or download? What were your steps? With the Note 3 L update, we are able to go back to 4.4.2 and 4.4.4 via ODIN. What did you download. This info will be a big help to see if we can go back to KK from L.

Atomic Virus said:
upgraded to 5.0 but then decide to see if I could downgrade and I bricked my phone trying to use Odin with the 4.4.2 files. Any suggestions or anyone going thru something similar?
Click to expand...
Click to collapse
Try flashing this file in Odin, it does not contain the bootloader so it should flash successfully: G900A_Downgrade_to_NCE

I can get to download menu but after I run Odin 3.09 and use the recovery files AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar SYS REV.
I get the following error:
Check Fail Refer 2 > Binary 1
Secure Check Fail: system
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

muniz_ri said:
Try flashing this file in Odin, it does not contain the bootloader so it should flash successfully: G900A_Downgrade_to_NCE
Click to expand...
Click to collapse
Let me try it. Will report back.

Atomic Virus said:
Let me try it. Will report back.
Click to expand...
Click to collapse
Still getting same error.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_Downgrade_to_NCE.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persist.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Atomic Virus said:
Still getting same error.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_Downgrade_to_NCE.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persist.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Very sorry to hear that. A BestBuy Samsung Experience or AT&T shop can likely get you back up and running.

muniz_ri said:
Very sorry to hear that. A BestBuy Samsung Experience or AT&T shop can likely get you back up and running.
Click to expand...
Click to collapse
No worries. Might wait it out for a bit maybe someone will come across a similar situation.

muniz_ri said:
Very sorry to hear that. A BestBuy Samsung Experience or AT&T shop can likely get you back up and running.
Click to expand...
Click to collapse
Great news I am back up and running. I went ahead flash the G900A_OC4_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+) from your other thread.

Atomic Virus said:
Great news I am back up and running. I went ahead flash the G900A_OC4_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+) from your other thread.
Click to expand...
Click to collapse
OK, I see now how you bricked....the kernel for the NCE .tar you first flashed updated successfully causing the brick because your system at that point was 5.0.

muniz_ri said:
OK, I see now how you bricked....the kernel for the NCE .tar you first flashed updated successfully causing the brick because your system at that point was 5.0.
Click to expand...
Click to collapse
That is correct! Thanks for your help.

Atomic Virus said:
That is correct! Thanks for your help.
Click to expand...
Click to collapse
I did the same thing you did what exactly did you do to get it to boot back up?

Fitz110 said:
I did the same thing you did what exactly did you do to get it to boot back up?
Click to expand...
Click to collapse
I went ahead flash the G900A_OC4_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+). Which you can get off this thread. http://forum.xda-developers.com/att-...-2015-t3021120 Sorry for the late responds.

Atomic Virus said:
I went ahead flash the G900A_OC4_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+). Which you can get off this thread. http://forum.xda-developers.com/att-...-2015-t3021120 Sorry for the late responds.
Click to expand...
Click to collapse
Okay thanks and the link is dead do you think share the file with some way?

Fitz110 said:
Okay thanks and the link is dead do you think share the file with some way?
Click to expand...
Click to collapse
Here
http://forum.xda-developers.com/showthread.php?t=3076803

OPOfreak said:
Here
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
Thanks but i think that's a updated version of the file presented in that post I was trying to get the original file

Fitz110 said:
Okay thanks and the link is dead do you think share the file with some way?
Click to expand...
Click to collapse
As a junior member, and it's not just you but quite a few, you really need to read and do some research on your phone before you turn it into a very expensive paperweight.
The link I provided took about 5 seconds in this very forum.
Plus doing your reading and research before asking will save you a ton of flaming. Just some friendly advice from someone that's been there done that.

Atomic Virus said:
Great news I am back up and running. I went ahead flash the G900A_OC4_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+) from your other thread.
Click to expand...
Click to collapse
so what was the exact process? do you mind making it clear for other users? thanks.

Fitz110 said:
Thanks but i think that's a updated version of the file presented in that post I was trying to get the original file
Click to expand...
Click to collapse
No it isn't that's where you will get the Stock partitions he was talking about

OPOfreak said:
No it isn't that's where you will get the Stock partitions he was talking about
Click to expand...
Click to collapse
Okay thanks , my apologies.

Can't Unroot Note 4 5.1.1 using ODin

For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858

Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?

I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything

Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...

Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7

mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future

mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"

waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..

mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too