Database Develop

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

T713 used; MDM and FRP issues

Hello all, i have searched endlessly on this site and didnt quite find my answer. Or didnt understand what to do, as i am not up to speed to what everything means. A little background...
i bought a used t713 not knowing it was "bricked?" (MDM/FRP). When i first powered it on i was unable to do anything as the home screen does not allow anything to be done. The message "Device turned off, contact IT" appears. Cant access settings nor turn it off.
In my desperate attemps to do a hard reset without being able to turn it off, i reset the tablet then pressed the combination of keys and got it to the "andriod recovery" screen. Tried to "wipe data/factory reset" but was not successful due to mdm. What makes my case unique is that i cant access anything such as setting so any youtube vids or other posts does not really help. Aside from the fact that i do not understand what anything means... Odin vs flashing vs rooting vs etc.
Can anyone provide a solution where a total newbie can follow the instructions?
Please see the attached photos for issues and tablet software version. ***once i figure out how***

So i cant figure out how to post the pics but below is the info from the "Android Recovery" screen
samsung/gts28vewifixx/gts28vewifi
7.0/NRD90M/T713XXU2BQD3
Also, i was able to ender the download mode, which i figured is Odin mode. From there i can see the following options:
FRP LOCK: ON
Secure Dowload: Enable.
with the info provided above what would be my first step?
Flash via odin? Then do a FRP bypass?

If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly

h​
Beut said:
If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly
Click to expand...
Click to collapse
Is there any specific odin version to use? From reading there are a few places to get Android 6... sammobile?

The Odin version is not important as long as it’s close to the latest one. Search Google FRP bypass you will see many discussions from this forum. Read carefully what others did, you will see it’s a piece of cake.
You need to read In order to see mistakes others did too and why they failed.

I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN. I've also used the newest firmware available from Sammobile. Notta. I am so very very frustrated. There are about a bazillion people with this situation and I cannot find a one that has managed to bypass the FRP lock. If you know how to help, OMG, I would be sooooooooo very grateful. I'm not new to flashing. I have rooted many phones, flashed many ROMS, very familiar with TWRP and Superuser and Chainfires cfautoroot. Is there any hope? Of do I just smash the heck out of this thing and burn it to a puddle of plastic in the middle of my living room????

CanadaHugh said:
I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN.?
Click to expand...
Click to collapse
You should be patient , FRP is a joke as long as you know how. In order to bypass, you should be specific what build you currently have.
Forget the Android 7 because most methods which don't use OTG cable are not working. The best way is downgrade to Android 6.
I don't have this model but the most popular methods are using Talk Back to open chrome, Hot Spot to create new users, and using Assist to open chrome.
You see a lot of youtube videos which are not working because most posters don't understand a method only work with certain build and model.
As long as you can open Chrome to download needed apps , FRP will be gone . I can bypass FRP on 5 different Samsung tablets so it's not a rocket science as long as you know which method works and uses it.
This is an example of method using Talk Back
https://www.youtube.com/watch?v=fhP_egvc6v0

Thank you for taking time to reply. I've seen this exact message you pasted here. I've tried to do all 3 possibilities offered with no success. I have current os of nugat. I've got backup from sammobile. Also used Odin to attempt downgrade to 6...fail because ftp lock prevents flash in odin. Tried talk back. ..the L during tutorial is prevented. So, for me anyway, this is rocket science! Please allow me the dignity of being able to read, search, view, attempt. ...every conceivable avenue for solution.
My device is SM-T713 running latest update of Nougat with FRP lock on. I do not know the previous user name and password so can not bypass FRP. Does this explanation clarify my dilemma? Do you possibly have a blueprint of the rocket science? Most of the Web results lead to dead end spams.

I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.

Again, thank you for taking time to reply. I sincerely appreciate your efforts.
Sent from my SM-N900W8 using Tapatalk

As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.

Beut said:
As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.
Click to expand...
Click to collapse
Thank you for taking time to explain the joke

Seriously, this security lock is a joke as I can do with ease on different Samsung tablets. Read this forum you will see, newbies would have troubles to unlock their tablets
but eventually they are able to bypass this FRP lock. So again, it's not a rocket science, you need to be patient and try different methods.
I started the same like yours, didn't know what to do. However, by learning and practicing, I do actually see it's a piece of cake as long as you understand which method can apply to a certain build or OS.

Beut said:
I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.
Click to expand...
Click to collapse
So i downloaded odin, samsung drivers and 7zip. As well as APK6 firmware (latest Android 6 fw i found on updato). From the APK6 download, there was only one tar.md5 file. Question is should i find fw that has the 3 seperate files or running the one i have in AP should work?

Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.

Beut said:
Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.
Click to expand...
Click to collapse
So i was able to downgrade the firmware to APK6, with only the AP file but i was greeted with an "to start up device enter password" message. Something i havent seen before... not same lock screen
Tried to do factory reset and failed due to mdm.

https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.

Beut said:
https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.
Click to expand...
Click to collapse
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?

Gamma35 said:
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?
Click to expand...
Click to collapse
Are you on marshmallow now or nougat?

ashyx said:
Are you on marshmallow now or nougat?
Click to expand...
Click to collapse
I am on marshmallow.

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!

AP files for flashing NC2?

I am attempting to follow the steps here to root my Android 5.0. I'm on step "1. Install stock NC2 (Instructions are all over)."
Indeed they are all over—and all different, too. I have downloaded files from Rootedi474's directory named N900AUCUCNC2 Stock Odin Files. In it there are two AP files:
AP-ATT-KOT49H.N900AUCUCNC2-Kernel.tar.md5 (10.1 MB)
and
AP_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5 (2GB)
Unfortunately, there is no ReadMe file. What's the purpose of these two files? The size of the files implies I can't just pick one at random to fill into the AP slot in Odin3.
I hope to fill all 4 file slots in Odin3, because I saw a comment somewhere that doing it with just one slot filled is the "old way." It's long past 2015 when most of the resources for the Note 3 were made available.

I found something that implied to use the big file and it worked. Of course, now I get "App not installed" trying to install towelroot. I learned one thing, though. I'm never getting a phone from AT&T again.

GregJ7 said:
I found something that implied to use the big file and it worked. Of course, now I get "App not installed" trying to install towelroot. I learned one thing, though. I'm never getting a phone from AT&T again.
Click to expand...
Click to collapse
If you only flashed the big file (AP) and you was on 5.0, you need to flash the other three files too.
BL https://androidfilehost.com/?fid=96042739161891602 CP https://androidfilehost.com/?fid=96042739161891603 CSC https://androidfilehost.com/?fid=96042739161891604 once you flashed the files you should have no problem installing towel root to root your device. If you flashed anything else, I would say flash all 4 files as showed in below link.
Picture https://forum.xda-developers.com/showpost.php?p=60551361
Whole thread https://forum.xda-developers.com/no...3-lollipop-t3100657/post60551361#post60551361

Thanks. I did flash all 4 files. On one iteration I followed that up by flashing the AP Kernel file provided. I tried 3 different posters' processes to get a rooted 5.0, but towelroot failed the dozen times I tried it as did Magisk and Kingoroot. So after trying and retrying variations for a dozen hours, I am resigned to using Android 4.4.2 (to achieve my goal of eliminating ad-presenting bloatware). Towelroot and Magisk also failed with 4.4.2, but Kingoroot has worked every time—which is great, except some software used following the flash doesn't work with Kingoroot (such as FlashFire, and Titanium Backup Pro gives a warning).
Prior to accidentally receiving the AT&Ts OTA update to 5.0, Towelroot worked fine, so I just have no idea what the problem is. I am currently removing bloatware by hand (from published lists) from my 4.4.2 rooted with Kingoroot. It's good enough for my main goal. Ideally, I could flash Oreo or Pie and root it, but my reading implies that's not possible. Pity I can't use a soldering iron or snips to unlock the bootloader.
Off Topic: What I and a ton of other people really need is a flowchart of the boot process with restrictions noted. Like for Windows: "On power on, the CPU starts executing the BIOS, which cannot be replaced because part of it is in ROM on the motherboard. The BIOS chooses a boot method (user-changeable), then starts executing the boot sector for the OS being booted to, etc." It's probably taken 100 hours of reading to indirectly figure out that "Recovery" is a noun, not a verb, that refers to the Firmware BIOS (for which there is a ROM copy in case restoration is needed) [for the N900A], etc.

GregJ7 said:
Thanks. I did flash all 4 files. On one iteration I followed that up by flashing the AP Kernel file provided. I tried 3 different posters' processes to get a rooted 5.0, but towelroot failed the dozen times I tried it
Click to expand...
Click to collapse
The towelroot I always used https://androidfilehost.com/?fid=1395089523397892819

That version worked! Thanks.

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!