Database Develop

[NO LONGER ACTIVE] Sprint T817P ODIN Flashable OEM Software

ODIN FLASHABLE STOCK FIRMWARE
For the Samsung Galaxy Tab S2 - SM-T817P
**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
These are untampered, unaltered, original firmware in the event that you need to recover from a soft brick or otherwise desire to / need to restore to out-of-box.
NOTE THIS WILL NOT RESET THE KNOX WARRANTY VOID COUNTER.
This will only restore original Samsung firmware
I will add links to new versions when they are released.
DOWNLOAD LINKS:
USE PASSWORD: XDAdevelopers
Password is case sensitive
5.1.1 - OL1 - Released December 23rd 2015 - Link Deleted
5.1.1 - OJ5 - Released November 11th 2015 - Link Unavailable
5.1.1 - OH6 - Initial Version Released September 11th 2015 - Link Deleted
Use ODIN 3.10.7 which can be downloaded at http://androidcentral.us/2013/11/download-odin/
** IF RESETTING, OR RECOVERING FROM A SOFT BRICK, After Flashing, boot to recovery and perform a factory reset or manually wipe /data and /data/media **

Thanks for this, alwwys good to have a copy of the stock firmware on hand.

**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
**** UPDATE: JUNE 16 2016 - For personal reasons, I will soon be unable to host the flashable tars or any other files. June 30 I will be removing download links. I encourage you to download now. If anyone else wants to host or start a new thread, be my guest. If you host, I would be more than happy to link here.
Otherwise, June 30th, All links will be removed and I will be asking XDA Mods to close and/or delete this thread. Sorry for the inconvenience.

What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?

P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?

typefortytardis said:
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?
Click to expand...
Click to collapse
T815 is actually the LTE model, so not much different to the t817p.
Don't know why anyone would want to flash carrier firmware to an international model anyway unless they are attempting to use it with that network?
Unfortunately this is not always possible due to differences in the radio.

I'm adding a password due to bots downloading the file.
The Password is: XDAdevelopers

P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.

GidiK said:
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.
Click to expand...
Click to collapse
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go

typefortytardis said:
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go
Click to expand...
Click to collapse
Not my tool, I was just pointing to the thread of the tool I used to download the firmware for the T815.
For T817P, SPR, the OJ5 seems indeed to be known in OTA mode, but not available for download yet; this also happened for T815 and that delay lasted about a day.

Does anyone have a OJ5 stock odin tar for SM-t817? I have twrp but the boot.img provided put me in a boot loop & I didn't make a backup like a noob.
Edit : Actually I think it was the super su zip (BETA-SuperSU-v2.52.zip)
The tablet is not usable @ all & it's actually a Christmas present for my son that I just wanted to setup & get going. So plz anyone with the file can use smart switch to download it would be greatly appreciated.
Thanks in advanced

Nvm, I'm on OJ5 (sprint variant t817p) & everything including boot.img & su zip work on the latest update. :highfive:

I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?

liquidhaste said:
I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?
Click to expand...
Click to collapse
I still have not had a chance to update mine. I am not certain why, but newer softwares for a lot of samsung devices have been hard to come by lately *suspiciously looks at Samsung*. Also I am out of town til the 20th of January.
As far as frp lock, or "Factory Reset Protection", you forgot to go into developer settings and enable "OEM Unlock".
It is basically like Samsung's 5.0 "Reactivation Lock", except this is enabled by default and encompasses KNOX verification. It cannot be circumvented now. HOWEVER.... there are TWO THINGS I can think of you can try (If anyone else has anything to add, please do)
1.) Try using the OH6 ROM with ODIN. Yes it's one edition older but it might work. I bricked by Galaxy Note5 after going to the latest firmware and forgot to disable FRP Lock (by enabling "OEM Unlock" under developer settings). Reflashing with ODIN worked. Then Flash your recovery, go into recovery, and format /data /system and /cache and dump the Dalvik/ART cache. Then boot back to download mode and re-flash the same ROM. Upgrade to most recent via OTA, then re root.
It worked when I ran into FRP lock errors with my note 5. it might work for you. It will not let you do anything that is not official samsung. Be prepared to log in with your samsung account info once you finally boot if you registered that before you bricked.
2.) Go to a Sprint store, pretend you're a tech illiterate and say after your cousin or someone messed with it, that happened. Sprint (most locations and employees anyways - try another if one fails) stick with the original pro-development attitude towards Android and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped)
TRY #1 first. It fixed my note which was bricked by FRP.

*Meant to type OH6 not AA1. That was a place holder while I typed (and tried to find the version info)

I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.

typefortytardis said:
[...] and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped).
Click to expand...
Click to collapse
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong

Depressed T.Bear said:
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong
Click to expand...
Click to collapse
You do not. Once KNOX is tripped, your warranty is void. You are no longer eligible to turn in a claim.
However, certain carriers (however they organize their purchasing contracts) have it to where they are authorized to process, handle and fulfill the warranty. Sprint is one of those carriers in the US. And a lot of times you have in store agents that either do not get paid enough to care or otherwise still hold true to the original pro development spirit of Android.
I personally replaced 3 Galaxy S5 devices that had KNOX tripped. That store started actually checking my KNOX thing and didn't let a 4th happen so Samsung probably did not credit them, but my account was never charged back. I did it a 4th time at another Sprint store.

liquidhaste said:
I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.
Click to expand...
Click to collapse
Then yes if you did not trip KNOX, you should have no problem pretending to be tech illiterate and having them swap it out for you or reflash it for you.
If they reflash, take it home and use Samsung SmartSwitch to do an "erase / initialization / reset" (however it is worded). Sprint might also be too lazy and just use the romfile and not the reset romfile which is equivalent to a "dirty flash". So go home and use Samsung Smart Switch to start fresh.
Then make sure you enable "OEM Unlock" under development settings next time you attempt root.

ashyx told me I should find someone with this tablet and the newest update that is still on a stock firmware, if they can possible make a backup of the boot.img and system.img using TWRP. This should help others who are stuck with the issues i'm reading on this post as well as the tablet I'm trying to fix now.
Thanks for reading

SM-N920F (Actually SM-N920A) on 3 UK - updating from 5.1.1 to MM and beyond

*Utter noob alert!*
tl;dr - can i update to MM 6+ without totally screwing my phone and entering a whole world of pain?
Proud owner of mongrel SM-N920A purchased from HK via eBay. Device has no branding on hardward / software other than Samsung.
Settings > System > About Device shows model number = SM-N920F. LIES!!!!!
Phone INFO *Samsung* apk shows it's really an SM-N920A
I've attached output from Phone INFO showing 'General', 'CSC', 'Firmware' and 'Android' info.
Having read over threads on Sammobile and here on XDA, it appears some people are losing anything from mobile reception & data to full on apocalyptic bricking. Most of these posts are from earlier in 2016 so I'm wondering, now we're further down the line and the dust has settled, whether there's any consensus on best way forward to get Marshmallow / Nougat and beyond - if at all.

Anyone out there able to offer help and guidance?

Please :crying:

Ah come onnn! Someone here must be able to help!?

dmlargo said:
Ah come onnn! Someone here must be able to help!?
Click to expand...
Click to collapse
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.

murtaza02 said:
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.
Click to expand...
Click to collapse
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated

dmlargo said:
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated
Click to expand...
Click to collapse
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.

murtaza02 said:
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Click to expand...
Click to collapse
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
murtaza02 said:
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.
Click to expand...
Click to collapse
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1

dmlargo said:
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1
Click to expand...
Click to collapse
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.

murtaza02 said:
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.
Click to expand...
Click to collapse
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy

dmlargo said:
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy
Click to expand...
Click to collapse
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.

murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?

dmlargo said:
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?
Click to expand...
Click to collapse
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.

murtaza02 said:
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.
Click to expand...
Click to collapse
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one

dmlargo said:
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one
Click to expand...
Click to collapse
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.

murtaza02 said:
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.
Click to expand...
Click to collapse
But doesn't that mean it'll be region locked / potentially losing network connection?

dmlargo said:
But doesn't that mean it'll be region locked / potentially losing network connection?
Click to expand...
Click to collapse
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.

murtaza02 said:
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.
Click to expand...
Click to collapse
Cool. I'll have a look this weekend. Fingers crossed.
After that I'll have a go a re-rooting using something similar to: https://www.search4roots.com/how-to-easily-root-samsung-galaxy-note-5-sm-n920a-marshmallow-6-0-1/

murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and pretty straight guide
really
the only "issue" is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization ..what is sure is that the phone was running bit cleaner before . ( i.e. no extra icons , no recording or "AT&T video call " icon available on phonecall screen when calling ..just an example among some things i noticed besides some at&t apps in the home screen )
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a

boodi said:
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and guide
the only thing is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a
Click to expand...
Click to collapse
Package Disabler Pro. It's a paid app. You can use it to disable (not remove) some bloatware that's preinstalled by Samsung and AT&T.
No root possible, so you can't remove the apps.
Sent from my SM-G935F

SM-N960F/D Odin flashing - blunder after blunder.... :(

Ok... So where to begin...
I've searched the threads for a few days now and tried several flashing methods and tools, but I'm having no luck. So please bare with me, and I will get into it...
I recently purchased a new Note 9 international unlocked model. I was super excited and ready to get it running. Except, I started it up and then no Bixby Voice. Unlike most, I prefer to use it and find it helpful to me regularly, so I'd like to keep it. Anyway, when pressing the button I received the much noted "Bixby Voice is not available in your country" message. Well, I found from Samsung support live chat, that this is because of two reasons. One, I currently live in Japan. Two, the phone is a Singapore model phone. My immediate thought was "Oh, ok well, I'll just flash it with another country's firmware then". Seemed easy enough. I flashed it with firmware baring an OXM csc, and after booting up I noticed the the VoLTE feature that was not select-able before was now able to turned on. "Ooow, extra win!" I thought, but of course same issue with bixby. So I searched and found a csc for a location that has bixby is available and is also a carrier unlocked Exynos chipset firmware (XEU). I flashed this, but guess what... still no Bixby Voice. Frustrated, I began looking into changing the Sales code. Using the *#272*IMEI# code and found that MM1 was the sales code for some reason. I changed this to XEU and the phone rebooted. I restored and then tried Bixby Voice again... same. Except, I noticed I also lost the VoLTE option completely. It doesn't even show in the menu bar anymore. I tried the code again to change the sales code back, but now I get error "Connection problem or invalid MMI code." So now, I lost that too. "To hell with it", I thought. I'll flash it back to the old firmware... nope. Now I get:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
This will sometimes change slightly if I try to flash a single part of the new firmware, BL, AP, CSC, etc...
I have done some research and found via the serial number that the firmware I should have installed is: N960FXXU1ARH5_N960FOXM1ARGD_N960FXXU1ARGC_N960FXXU 1ARH5_XSP (according to the Chimera Mobile tool)
I've obtained this, but I still get the same Revision error. I found that the one last one I successfully flashed is a newer version than the others. So now what can I do? Is it possible I can just manually manipulate the CSC details? I rooted the phone and got ES Explorer going, set all the access rights to R/W but I cant find the /System/CSC folder that people keep going on about. Did they do away with that on the Note 9?
It looks like I also have some regional troubles with the Play store too.
WTH... I'm really not sure what to do here. Can anyone please help? I'll be satisfied if I can just get it back to the stock firmware...

Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.

who uses bixby use google assistant for peats sake!!!"!!!!

willhemmens said:
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
Click to expand...
Click to collapse
Hi willhemmens! Thanks for replying back.
I was also speculating the same thing about having to wait for the revision, but I know the people here are significantly more knowledgeable, so I thought I'd try to pick some brains. My first though was that there must be something in one of the package files that identify to the phone what "version" it is, and then perhaps that can be modified and then re-packaged. But if that were the case, this would be the best place on the planet to verify that. I have tools to un-package and repackage, maybe I'll make a duplicate copy and tinker around in it.
It looks like everyone is complaining about it. It's been a while since I rooted a device (7 years maybe?), so I hadn't realized Samsung took a dump in the downgrade pool. I also found some other new 'glorious' features they've graced us with-after the fact of course. Now, when I un-root... it's still flagged as modified! Woohoo. ....Fricken' KNOX. Now all of the nifty Samsung apps are blocked. Is it just me, or has Samsung turned a little extra Ass-hat recently?
Anyway, I guess I'll have to deal with this lame iOS quality version of Oreo until then... By the way, off the top of your head do you know where I can go to keep an eye out for that update to happen? All I know is SamMobile.com
Thanks again.

mikey_sk said:
who uses bixby use google assistant for peats sake!!!"!!!!
Click to expand...
Click to collapse
Hi Mikey! Yeah, I suppose your right. I've just been using it a lot and have gotten accustomed to it. Plus I enjoy creating my own custom Bixby voices, attitudes, and responses. Bixby on my Note 8 has split personality.
Luckily she doesn't randomly laugh in the dark like Alexa. If she did she'd fly out the window like a Note 7.

csc was omc and now odm.

bober10113 said:
csc was omc and now odm.
Click to expand...
Click to collapse
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.

VetteMike69 said:
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
Click to expand...
Click to collapse
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?

VetteMike69 said:
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
Click to expand...
Click to collapse
Ah sorry, nevermind... I was able to make a ps1 for it instead. I'm good one decoding and encoding the XMLs now.

@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file

yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
Click to expand...
Click to collapse
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw

bober10113 said:
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
Click to expand...
Click to collapse
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!

hkalltheway said:
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
Click to expand...
Click to collapse
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.

yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
Click to expand...
Click to collapse
Hi @yakapa40!
Thank you, this looks like it'll be a bit more convenient than the one I made previously. I'll put it on record for next time. Luckily I was able to find what prevented me from flashing the older revision CSC and modify that. So now I was able to use Odin to drop down my PDA and CSC while keeping the newer Bootloader and Baseband. I guess it's a bit of a Frankin'-Firm now. Whats weird though, is that now my knox sometimes shows tripped and sometimes doesn't; sometimes root checker fails and sometimes it passes.
I wonder if I grazed on something that's related to the knox handler... Nagh... probably just wishful thinking. Still weird though.

bober10113 said:
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
Click to expand...
Click to collapse
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.

VetteMike69 said:
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
Click to expand...
Click to collapse
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.

bober10113 said:
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
Click to expand...
Click to collapse
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!

hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
well then root might be food for you.
have a read at Dr Ketan roms thread for the root procedure and details of what it involves.

hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.

bober10113 said:
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
Click to expand...
Click to collapse
I'm currently with fido but thinking of switching to freedom mobile. Still too worried about all this rooting stuff that it seems the best thing to do is stay away from now and choose from one of the 2:
1- use wifi calling / VoLTE by getting the rogers/fido phone directly; that phone will not have dual sim capability
2- forget wifi calling / VoLTE and use this dual sim version, which has a lot of advantages while traveling
Seems like I'll stick to the 2nd option for now. Thanks for the help!

Need help with flashing firmware on Note 9 (noob question)

I have Note 9 (SM-N960U1) unlocked in USA. I am currently on AT&T.
I seem to have many dead spots inside my house so want to enable wifi calling but found out that I need to flash carrier specific firmware on my phone. As I am complete noob, have some questions:
1) What does flashing a firmware does? Pros? Cons?
2) I am currently on Android 10 (One UI 2.0 Build QP1A.190711.020.N960U1UEU3ZSL2). If I flash a new firmware, will my phone be downgraded to a lower version of Android?
3) If answer to @2 is Yes, how will I get latest Android updates? Will it depend on Samsung or AT&T?
4) Last but not the least, HOW THE HELL I FLASH THIS FIRMWARE?
Any help will be a great help. I have a interview on Friday so don't have much time to get this fixed.
TIA.

1) Flashing is a way to manually install or update firmware or operating system through the bootloader. This provides a way to restore the devices operating system during an emergency or failed OTA Update etc. The cons of this however is it is quite easy to mess up your device if you don't know what you are doing. And Flashing different firmware that is not originally meant for your device easily carries this risk. The bootloader is what tells your device how to boot the operating system and happens before any user interaction knock on wood you theoretically corrupt the bootloader or somehow mess it up you are left with a 1000 dollar doorstop. Im not sure how a carrier's firmware would react on an unlocked phone. I personally wouldn't risk it but it's up to you. I'm pretty sure that other users here have tried it you should look around and do your research. Remember this would not only be changing Android this would also change the CSC and Modem.
2) Android 10 has not yet been released for the Note 9 so I would assume that you are on the beta. You would need to factory reset and downgrade to Android 9 before flashing ATT's firmware.
3) Carrier's handle OTA updates. However im not sure you would even receive OTA's anymore.
4) You need to use Odin3 and get the firmware from somewhere like sammobile.
In conclusion I personally would advise you to contact ATT with your problem. Considering your interview tomorrow if something did for some reason go wrong you most likely wouldn't have time to fix it.

UndeadAnarchy said:
1) Flashing is a way to manually install or update firmware or operating system through the bootloader. This provides a way to restore the devices operating system during an emergency or failed OTA Update etc. The cons of this however is it is quite easy to mess up your device if you don't know what you are doing. And Flashing different firmware that is not originally meant for your device easily carries this risk. The bootloader is what tells your device how to boot the operating system and happens before any user interaction knock on wood you theoretically corrupt the bootloader or somehow mess it up you are left with a 1000 dollar doorstop. Im not sure how a carrier's firmware would react on an unlocked phone. I personally wouldn't risk it but it's up to you. I'm pretty sure that other users here have tried it you should look around and do your research. Remember this would not only be changing Android this would also change the CSC and Modem.
2) Android 10 has not yet been released for the Note 9 so I would assume that you are on the beta. You would need to factory reset and downgrade to Android 9 before flashing ATT's firmware.
3) Carrier's handle OTA updates. However im not sure you would even receive OTA's anymore.
4) You need to use Odin3 and get the firmware from somewhere like sammobile.
In conclusion I personally would advise you to contact ATT with your problem. Considering your interview tomorrow if something did for some reason go wrong you most likely wouldn't have time to fix it.
Click to expand...
Click to collapse
Thanks a lot for your help mate..cheers

rockstar283 said:
I have Note 9 (SM-N960U1) unlocked in USA. I am currently on AT&T.
I seem to have many dead spots inside my house so want to enable wifi calling but found out that I need to flash carrier specific firmware on my phone. As I am complete noob, have some questions:
1) What does flashing a firmware does? Pros? Cons?
2) I am currently on Android 10 (One UI 2.0 Build QP1A.190711.020.N960U1UEU3ZSL2). If I flash a new firmware, will my phone be downgraded to a lower version of Android?
3) If answer to @2 is Yes, how will I get latest Android updates? Will it depend on Samsung or AT&T?
4) Last but not the least, HOW THE HELL I FLASH THIS FIRMWARE?
Any help will be a great help. I have a interview on Friday so don't have much time to get this fixed.
TIA.
Click to expand...
Click to collapse
You have SM-N960U1 with One UI 2.0? Did you just buy it used? You are on bootloader 3, so you cannot flash another firmware with bootloader less than 3.

Question Wont boot after root

Hi all. Succesfully rooted my S8 Tab Ultra and was running fine for the past week.
Just rebooted the tablet and its showing "Custom Binary(boot) Blocked due to remaining installment balance" I've read around the forum and apparently its for people who haven't paid for the device fully which I have, paid in full on pre order.
The only way it seems to get it to boot is to flash the original firmware my model is SM-X900NZAFXAR and I can't find the firmware does anyone know how I can get the tablet to boot?
Tried Samsung support but they didn't help

Hello! Get SamFirm at https://samfirmtool.com/ (v0.5.0 is the latest), for model put SM-X900, for Region put XAR. I haven't received mine yet (not until the middle of next month), but this is the closest I could find to what should be the correct firmware. Click "Check Update", then click "Download". It's been too long for me away from Samsung - I don't remember if it matters if you let it decrypt automatically or not. The answer should become apparent, though. At worst, you'll just have to redownload the firmware with the option to decrypt unchecked in SamFIrm.
You can check your CSC (Region) by (copying/pasting someone else's instructions):
go to settings - about - software information - service provider SW ver. The region code (CSC) will be written there.
I don't know if your CSC will match XAR. I don't find anything for XAA or XAS yet in SamFirm.
Good luck! This is concerning since I had planned on rooting mine.

Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers

Jono0907 said:
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Click to expand...
Click to collapse
You got the latest Samsung drivers installed, as linked to in the SamFirm\Samsung Driver subfolder? (link leads to https://samsungusbdriver.com/category/download)

Wait... Is OEM Unlock still enabled in Dev Options? It might be salvageable even though you have locked the bootloader...

Thank you edor for the help the tablet is running again now however it is unrooted now and the OEM unlock option is missing. The USB fault was resloved using a different PC not sure whats going on with my laptop.
Once in download mode i was able to download the XAR version of the Tab S8 Ultra fimrware from SamFirm and reflash with Odin which brought it back.
I'm not sure if running XAR csc will cause problems? I am in the UK I think my csc originally was OXM which is the universal one but cant find an OXM version at the moment.
fkofilee I actually locked the bootloader from the download mode menu which i shouldnt have. I don't have the option now so think I need to wait for the OEM unlock to show in settings.
For anyone else who has the "Custom Binary(boot) Blocked due to remaining installment balance" Need to reflash back to original firmware to boot and apparently it will re-check in 7 days so cannot be rooted in that time.
I have an open ticket with Samsung to try and find out why my tablet thinks it has finance. The confirmed on the phone that it was paid in full.
I wonder if the S7 Bootloader that i rooted had anything to do with it. Will retry with the bootloader when i can and report back.

@Jono0907 I'm glad you got it back working. I apologize if the XAR firmware has anything to do with your OEM unlocking not being available. Thank you for the advice for myself and for others to follow if we encounter the same problem. You had used the S7 bootloader? I would expect that to be the problem but as I said, I'm rusty on Samsung, and totally unexperienced in Samsung tablets - I only know what I've read in this section so far.

My tablet is working because of your advise so I'm happy. Found the EUX firmware which feels like it should be what my tablet should be running so will flash that and see if Unlock comes back. Tried all the tricks with date/time to try and trick it but no luck.
Also was going to add my experience with Samsung support. He agreed that if the tablet was wrongly reporting it was in finance then it wouldn't have been my fault but also said Samsung would not help because I had rooted the device. He didnt talk about reflashing firmware just said that I needed to send it to them for a new motherboard to repair Knox at a cost of at least $400(£300)

I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks

It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it

ivanox1972 said:
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
Click to expand...
Click to collapse
I want clearly explanation, I don't know about this.

Jono0907 said:
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
Click to expand...
Click to collapse
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?

emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Sorry mate never done the HOME CSC flash I've always been happy to wipe the device hopefully someone here knows?

emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.

lloydsw said:
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
Click to expand...
Click to collapse
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.

roirraW edor ehT said:
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
Click to expand...
Click to collapse
Yup, worked fine on my S8. Sigh of relief!