Related
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
Hello.
Does anyone know the actual contents of this OTA update that was released today 11/29/17? After the horrible time Samsung and Android gave me after the Note7 fiasco I have become very untrusting of them. The first Note8 OTA update left me with little options relating to rollback and such things.
I would like to know what is exactly in this update. The page I found is vague. The information they leave for the average consumer is always vague.
If no one knows, can anyone lead me to where I can find more information about this particular update?
So that leaves me at this point. If I install this update will it limit my options as for Odin, custom firmware, etc?
So all that Samsung tells me can be found here: http://doc.samsungmobile.com/SM-N950U1/ATT/doc.html
Thank you in advance for any and all assistance. It is always appreciated.
Have not seen any issue's so far on this OTA.
Head over to sammobile dot com, to read more.
In short:
"In addition to the November security patch, the update brings improved performance in the Calendar, Gallery, Voice Recorder, and Reminder apps, a new secure Wi-Fi function, and a fix for an unexplained Samsung DeX error. The firmware version is N950FXXU1BQK6, and at upwards of 840 MB, is among the biggest OTA updates that don’t bring a major Android version upgrade that we have seen"
Safe? It will, at least temporarily, block any attempt at root. If you're running a Substratum theme, it's best to uninstall it before running the update, based on the experience of those who got the October update. Do not reinstall apps that were backed up while running the theme.
Thank you. I am going to Sammobile right now to read more about it.
douger1957 said:
Safe? It will, at least temporarily, block any attempt at root. If you're running a Substratum theme, it's best to uninstall it before running the update, based on the experience of those who got the October update. Do not reinstall apps that were backed up while running the theme.
Click to expand...
Click to collapse
Is it designed to block rooting?
Can you still do the WiFi hotspot trick. Where you try to sing into a hotspot with wrong password then turn on hotspot and quickly turn off WiFi. Can't live without that.
ConcernedCustomer said:
Is it designed to block rooting?
Click to expand...
Click to collapse
The method for rooting Snapdragon phones won't work with updated firmware.
ConcernedCustomer said:
Is it designed to block rooting?
Click to expand...
Click to collapse
Yes it blocks current SamFail method. The U2 bootloader also cannot be downgraded once installed.
sefrcoko said:
Yes it blocks current SamFail method. The U2 bootloader also cannot be downgraded once installed.
Click to expand...
Click to collapse
Thank you for explaining. I was wondering if I would be able to rollback to original stock firmware after updating.
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
douger1957 said:
The method for rooting Snapdragon phones won't work with updated firmware.
Click to expand...
Click to collapse
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
pospower said:
Can you still do the WiFi hotspot trick. Where you try to sing into a hotspot with wrong password then turn on hotspot and quickly turn off WiFi. Can't live without that.
Click to expand...
Click to collapse
What this about? First time I'm hearing about this. Is it like getting free internet or something? If the instructions are anywhere on this website would you be so kind as to post the link here.
ConcernedCustomer said:
Thank you for explaining. I was wondering if I would be able to rollback to original stock firmware after updating.
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
Click to expand...
Click to collapse
Not 100% sure to be honest, but you can maybe try disabling security updates in settings/security menu or maybe disabling/freezing "software update" through an app like TitaniumBackup.
Check the SamFail thread for more info:
https://forum.xda-developers.com/showthread.php?p=74074361
I have the unlocked Note from Samsung on Verizon's network. Currently, tethering works straight out the box. Can anyone confirm that this update does not break this? Thanks
I probably wont update until Oreo...
BlueFox721 said:
I probably wont update until Oreo...
Click to expand...
Click to collapse
That's what I'm trying to hold out for. I have not as of yet experienced any glitches or problems of any kind so I don't see why an update is justified. Just give us Oreo!!! It should've been pre-built into the Note8.
sefrcoko said:
Not 100% sure to be honest, but you can maybe try disabling security updates in settings/security menu or maybe disabling/freezing "software update" through an app like TitaniumBackup.
Check the SamFail thread for more info:
https://forum.xda-developers.com/showthread.php?p=74074361
Click to expand...
Click to collapse
Thank you very much. I'm looking into it for more information now....
Took the update. So far so good. OpenVPN and MS RDP working fine as usual. I was a bit worried as I've read reports of updates screwing up WiFi. I've recently tried these apps on three new Samsung devices and had disconnect issues with all. Oddly, one was a dex using Ethernet - maybe this will fix that, I'll test it. Btw the other devices were a Chromebook pro and a galaxy tab a.
Upgraded to oreo on note 8 n950n
Volte and video phone deleted from dialer as they have on any past update. No biggie. Get into ims settings. Either through hidden kt menu or shortcut lite
But now ims settings requires a one time passcode
And supplies a key code that correlates to a password
No idea where to get key from.. please help!
T Mobile sucks without volte
In my country, the carrier requires you to take the device to activate VOLTE, maybe you need to go in person with your device to your carrier service center
When I was on Oreo I couldn't even access IMS settings on my F. Phone INFO/Shortcut Master wouldn't find the IMS settings menu for me. But I'm rooted & T-Mobile CSC still activated VoLTE & Wifi calling fine for me. But whatever, I'm back to Nougat & won't be running Oreo until things get worked out.
shouren04 said:
When I was on Oreo I couldn't even access IMS settings on my F. Phone INFO/Shortcut Master wouldn't find the IMS settings menu for me. But I'm rooted & T-Mobile CSC still activated VoLTE & Wifi calling fine for me. But whatever, I'm back to Nougat & won't be running Oreo until things get worked out.
Click to expand...
Click to collapse
How did you go back to Nougat from Oreo? Wouldn't that trip the Knox flag?
I know you are rooted, however just asking if I downgrade will I hit the Knog flag. I am extremely concerned as I am registered to my Org email and other apps which requires no trip of Knox flag along with no root.
Please suggest.
Thanks.
deepakrsarangi said:
How did you go back to Nougat from Oreo? Wouldn't that trip the Knox flag?
I know you are rooted, however just asking if I downgrade will I hit the Knog flag. I am extremely concerned as I am registered to my Org email and other apps which requires no trip of Knox flag along with no root.
Please suggest.
Thanks.
Click to expand...
Click to collapse
You can flash back to Nougat & flashing official FW in Odin should not trip Knox but I'm not taking any responsibility if somethig happens.
I have Exynos with TWRP installed so my Knox is already tripped. I switch back & forth from Oreo & Nougat with nandroids in TWRP.
shouren04 said:
You can flash back to Nougat & flashing official FW in Odin should not trip Knox but I'm not taking any responsibility if somethig happens.
I have Exynos with TWRP installed so my Knox is already tripped. I switch back & forth from Oreo & Nougat with nandroids in TWRP.
Click to expand...
Click to collapse
Thanks. Unfortunately I read from somewhere that even downgrading ROM trips knox. Not sure though. In case someone who has already tried please confirm.
Additionally if I flash G950U1 official ROM on a G950U phone would that still trip knox?
deepakrsarangi said:
Thanks. Unfortunately I read from somewhere that even downgrading ROM trips knox. Not sure though. In case someone who has already tried please confirm.
Additionally if I flash G950U1 official ROM on a G950U phone would that still trip knox?
Click to expand...
Click to collapse
I've never heard that either. Generally if you are are flashing official FWs in Odin Knox will not be tripped. And as you probably know you can't flash anything in Odin that is not for your specific device so Knox shouldn't be tripped.
I didn't realize you have a S8 since you are posting in the Note 8 forum but it should be the same. You can flash the unlocked FW on a carrier device but you have to use the PrinceComsy modified Odin to do so. Still it should not trip Knox. What's mainly important is you have to flash FWs with the same version bootloader you are on now. You can not downgrade BL, even if you tried Odin will not let you.
shouren04 said:
I've never heard that either. Generally if you are are flashing official FWs in Odin Knox will not be tripped. And as you probably know you can't flash anything in Odin that is not for your specific device so Knox shouldn't be tripped.
I didn't realize you have a S8 since you are posting in the Note 8 forum but it should be the same. You can flash the unlocked FW on a carrier device but you have to use the PrinceComsy modified Odin to do so. Still it should not trip Knox. What's mainly important is you have to flash FWs with the same version bootloader you are on now. You can not downgrade BL, even if you tried Odin will not let you.
Click to expand...
Click to collapse
Thanks a lot. Since Note 8 and S8 has almost similar in everything apart from few hardware enhancements in Note 8, from firmware prospect both should be considered as same..
But I read in one of the thread in XDA forum that after Oreo upgrade the bootloader has been changed and you can't downgrade.
As you confirmed if the Odin doesn't even allow FWs which would not be officially compatible then that is an awesome idea. My fear is and always be with KNOX trip since a lot is dependent on that including my work profile email and stuff.
If you/someone knows a way to turn on IMS service switch in Oreo then I won't require downgrade. Essentially I need the VoLTE to turn ON.
Tuff luck it is.
deepakrsarangi said:
Thanks a lot. Since Note 8 and S8 has almost similar in everything apart from few hardware enhancements in Note 8, from firmware prospect both should be considered as same..
But I read in one of the thread in XDA forum that after Oreo upgrade the bootloader has been changed and you can't downgrade.
As you confirmed if the Odin doesn't even allow FWs which would not be officially compatible then that is an awesome idea. My fear is and always be with KNOX trip since a lot is dependent on that including my work profile email and stuff.
If you/someone knows a way to turn on IMS service switch in Oreo then I won't require downgrade. Essentially I need the VoLTE to turn ON.
Tuff luck it is.
Click to expand...
Click to collapse
Yes Oreo has a new bootloader but you can still go back to Nougat, but latest Nougat. When they say you can't downgrade BL, you can't downgrade versions.
I don't know what variant you have but for example, I have F. Latest Nougat is 3BRB5 or 3BRA8. Oreo is 3CRC1. The 5 digit from the end is the BL version. If the number is the same, you can flash. If the number you have now is higher than a FW you wish to flash tbat has a lower number, you can't, that's what is meant by can't downgrade BL.
Oreo, IMS setting, yes I do know how to launch it. I'm assuming you are Using Phone INFO or Shortcut Master & can't launch. But with Shortcut Master you still can. Instead of launching 467 as you normally would, click on Explore instead to open App Explorer. From there click the second option, IMS Settings will launch.
If you have a N & have the passcode issue as mentioned in this thread, that I don't know anything about. Although I believe I remember a post somewhere that someone posted the codes.
shouren04 said:
Yes Oreo has a new bootloader but you can still go back to Nougat, but latest Nougat. When they say you can't downgrade BL, you can't downgrade versions.
I don't know what variant you have but for example, I have F. Latest Nougat is 3BRB5 or 3BRA8. Oreo is 3CRC1. The 5 digit from the end is the BL version. If the number is the same, you can flash. If the number you have now is higher than a FW you wish to flash tbat has a lower number, you can't, that's what is meant by can't downgrade BL.
Oreo, IMS setting, yes I do know how to launch it. I'm assuming you are Using Phone INFO or Shortcut Master & can't launch. But with Shortcut Master you still can. Instead of launching 467 as you normally would, click on Explore instead to open App Explorer. From there click the second option, IMS Settings will launch.
If you have a N & have the passcode issue as mentioned in this thread, that I don't know anything about. Although I believe I remember a post somewhere that someone posted the codes.
Click to expand...
Click to collapse
Thanks for this detailed info.
Apologies for being so naive. Mine is 2CRC5 Oreo. Unfortunately I don't know which variant you referred when you say F or N.
But going by your instructions I tried and got an error while invoking the 2nd option i. e. imsserviceswitchactivity. I assume this is related to rooting as it says " su not found. "
If yes, then please suggest me something without rooting to enable the ims switch.
Attached here the screenshot of the error message. Please help.
deepakrsarangi said:
Thanks for this detailed info.
Apologies for being so naive. Mine is 2CRC5 Oreo. Unfortunately I don't know which variant you referred when you say F or N.
But going by your instructions I tried and got an error while invoking the 2nd option i. e. imsserviceswitchactivity. I assume this is related to rooting as it says " su not found. "
If yes, then please suggest me something without rooting to enable the ims switch.
Attached here the screenshot of the error message. Please help.
Click to expand...
Click to collapse
Ah I forgot you have S8, that's why I'm not familiar with 2CRC5. F & N are international models. You have a U which is US.
Says su not found which means you need root access to open it. I don't know of any other way. Be sure to verify with the S8 guys before trying to go back to Nougat. Guys on Note 8 have done it but I wouldn't want you to brick your phone in case something is different with the S8.
Since you have a U, that's got me thinking. Are you using your carrier's firmware? If yes VoLTE should already be enabled if they support VoLTE.
---------- Post added 04-07-2018 at 12:00 AM ---------- Previous post was 04-06-2018 at 11:51 PM ----------
In Settings/About Phone under Service Provider SW Ver, what is you CSC (XXX/XXX/XXX)?
shouren04 said:
Ah I forgot you have S8, that's why I'm not familiar with 2CRC5. F & N are international models. You have a U which is US.
Says su not found which means you need root access to open it. I don't know of any other way. Be sure to verify with the S8 guys before trying to go back to Nougat. Guys on Note 8 have done it but I wouldn't want you to brick your phone in case something is different with the S8.
Since you have a U, that's got me thinking. Are you using your carrier's firmware? If yes VoLTE should already be enabled if they support VoLTE.
---------- Post added 04-07-2018 at 12:00 AM ---------- Previous post was 04-06-2018 at 11:51 PM ----------
In Settings/About Phone under Service Provider SW Ver, what is you CSC (XXX/XXX/XXX)?
Click to expand...
Click to collapse
Yeah mine is US model G950U S8 Sprint branded, officially network unlocked by Sprint.
The CSC in my case is SPR/XAA/SPR. I haven't changed the carrier firmware yet in fear of Knox trip. SPRINT does have VoLTE but through their CallingPlus app in beta, not native VoLTE calls.
Moreover after network unlock I moved to India and through IMS settings I did enable VoLTE and enjoyed native calls with Indian operators. After upgrade to Oreo on March 16th, the IMS switch was auto disabled and the ims application didn't get invoked. So now stuck in a no man's land.
Is there any other method (adb or something else) to enable VoLTE?
deepakrsarangi said:
Yeah mine is US model G950U S8 Sprint branded, officially network unlocked by Sprint.
The CSC in my case is SPR/XAA/SPR. I haven't changed the carrier firmware yet in fear of Knox trip. SPRINT does have VoLTE but through their CallingPlus app in beta, not native VoLTE calls.
Moreover after network unlock I moved to India and through IMS settings I did enable VoLTE and enjoyed native calls with Indian operators. After upgrade to Oreo on March 16th, the IMS switch was auto disabled and the ims application didn't get invoked. So now stuck in a no man's land.
Is there any other method (adb or something else) to enable VoLTE?
Click to expand...
Click to collapse
Oh man, totally didn't expect that one. Unfortuantely in your case the only way I know is to root which is out of the question. I could be wrong but I don't think there is anything that can be done through adb, generally it's enabled by CSC. Hopefully the dev for Phone INFO/Shortcut Master will figure out how to get the secret codes working with Oreo.
shouren04 said:
Oh man, totally didn't expect that one. Unfortuantely in your case the only way I know is to root which is out of the question. I could be wrong but I don't think there is anything that can be done through adb, generally it's enabled by CSC. Hopefully the dev for Phone INFO/Shortcut Master will figure out how to get the secret codes working with Oreo.
Click to expand...
Click to collapse
The other way could be downgrading to 7.0, where the IMS setting was accessible. My fear is knox trip, if not I can downgrade. What would you suggest?
deepakrsarangi said:
The other way could be downgrading to 7.0, where the IMS setting was accessible. My fear is knox trip, if not I can downgrade. What would you suggest?
Click to expand...
Click to collapse
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?
shouren04 said:
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?
Click to expand...
Click to collapse
Thanks. I tried the app earlier too. The VoLTE option is not there. I don't want to downgrade unless I find a way to enable it.
I have searched over internet a lot and found mixed responses about KNOX tripping during downgrade or any unofficial try related to firmware.
I will wait for next few days for any help regarding the VoLTE enabler app or procedure. If not, I have the Nougat latest firmware ready with me(as you suggested earlier - same bootloader version). Eventually I have to go back. VoLTE is a must for me use this device in India with 4G connections.
Hope you may show some new light towards this fix.
shouren04 said:
Yeah, the knox part is the questionable part as obviously it can't be reversed if tripped. I don't want to say something & mistakenly have it trip. But as we talked about flashing in Odin back to Nougat should not trip knox however you stated you read otherwise?
Click to expand...
Click to collapse
Finally I downgraded to the latest Nougat ROM available for this device. Everything was smooth. I was able to enable VoLTE as we discussed. Thanks to you for providing me confidence.
I'll still wait for anyone confirming IMS app invoke on Oreo (without Root) before upgrade. Till then Happy with Nougat ROM.
Thanks again.
deepakrsarangi said:
Finally I downgraded to the latest Nougat ROM available for this device. Everything was smooth. I was able to enable VoLTE as we discussed. Thanks to you for providing me confidence.
I'll still wait for anyone confirming IMS app invoke on Oreo (without Root) before upgrade. Till then Happy with Nougat ROM.
Thanks again.
Click to expand...
Click to collapse
Nice, good to hear! :good:
I did ask the dev for Phone INFO/Shorcut Master about Oreo support for the secret codes. He's aware of the issue & said he'll try to find a way to fix it. Hopefully he figures it out.
shouren04 said:
Nice, good to hear! :good:
I did ask the dev for Phone INFO/Shorcut Master about Oreo support for the secret codes. He's aware of the issue & said he'll try to find a way to fix it. Hopefully he figures it out.
Click to expand...
Click to collapse
Thanks. Many of us are waiting for this fix btw. There are several threads on this on XDA.
I too hope for an efficient fix soon.
Hi, I have cracked the password for the otp key, you can get the java program from below
https://1drv.ms/u/s!AnEZ2ptLoUQKgfV6fNSZIyQlf-cC5Q
Your pc must have Java installed.
1. run the java program by:
java OTP_Cracker yyit4(replace this key with your otp key)
the program output should be：
key:yyit4 pwd:1406604358
key:yyit4 pwd:1405418437
key:yyit4 pwd:1404232516
key:yyit4 pwd:1403046595
key:yyit4 pwd:1401860674
key:yyit4 pwd:1400674753
One of the pwd should be ok for the key. Entering the pwd in your phone then you can get in the volte settings.
https://www.tmonews.com/2019/03/t-mobile-galaxy-note-9-android-pie-update/
From the source :good:
Good News for those who have waited, according to t-Mobile news
""Following the T-Mobile Galaxy S9 and S9+ getting Android Pie a couple of weeks ago, it’s now the Galaxy Note 9’s turn to get a piece of Pie.
T-Mobile has updated its Galaxy Note 9 support page to show that the Android 9.0 Pie update will begin rolling out today, March 1st. The update is version N960U1UEU1CSB3 and is 1671.6MB in size.
In addition to Android 9.0 Pie, Galaxy Note 9 customers can expect Samsung’s new One UI user interface. It includes an updated look that moves interactive elements toward the bottom of the screen so they’re easier to reach, which should be especially useful on the Note 9 and its 6.4-inch screen. Samsung has added a night mode to its One UI as well.
Also included in this update is a new e911 call flow, says T-Mobile, along with a compass calibration fix and a BYOD update.
T-Mo does say on its Note 9 support page that the update “will not be available to all customers right away”, so it may take a few days to make its way to your phone. If you’d like, you can manually check for the update by going into Settings > Software update > Download updates manually. Be sure to let us know when your T-Mobile Galaxy Note 9 gets its Android Pie update!""
Does anyone know what the "BOYD update" means?
microbespecialty said:
Does anyone know what the "BOYD update" means?
Click to expand...
Click to collapse
"BYOD" Bring your own device.
rsfinsrq said:
"BYOD" Bring your own device.
Click to expand...
Click to collapse
Sorry. I should be more specific. I know what BYOD means. The question I am trying to ask is what exactly does this update do with regards to "BYOD update"?
microbespecialty said:
Sorry. I should be more specific. I know what BYOD means. The question I am trying to ask is what exactly does this update do with regards to "BYOD update"?
Click to expand...
Click to collapse
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/
I was already updating just under 3 hours ago. I dislike the location of the time clock, how they moved it to the left side. I hope there's a fix.
rsfinsrq said:
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/
Click to expand...
Click to collapse
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.
microbespecialty said:
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.
Click to expand...
Click to collapse
I believe you will get the T-Mobile boot screen and a couple T-Mobile bloat apps.
microbespecialty said:
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.
Click to expand...
Click to collapse
The BYOD features such as carrier boot screen only applies to the carrier branded models. The unlocked U1 models will remain unbranded when switching carriers.
---------- Post added at 08:04 AM ---------- Previous post was at 07:52 AM ----------
rsfinsrq said:
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/
Click to expand...
Click to collapse
Sweet. Been trying to explain this to people. Didn't think to look for an official Samsung document!
I have seen reports that the update will apply carrier specific apps and boot screen based on the sim card you have inserted at the time of updating.
See this thread;
https://forum.xda-developers.com/galaxy-note-9/how-to/n960usqu1csaa-official-ota-update-pie-t3895831
rsfinsrq said:
I have seen reports that the update will apply carrier specific apps and boot screen based on the sim card you have inserted at the time of updating.
See this thread;
https://forum.xda-developers.com/galaxy-note-9/how-to/n960usqu1csaa-official-ota-update-pie-t3895831
Click to expand...
Click to collapse
Only on the carrier branded models. It will NOT apply a carrier boot screen to the unbranded models. They have a different build number.
The T-Mobile document listed the wrong build number for their release. T-Mobile pushed N960USQU1CSB3.
The unlocked, unbranded U1 model will get N960U1UEU1CSB3 (most likely).
Mr. Orange 645 said:
The unlocked, unbranded U1 model will get N960U1UEU1CSB3 (most likely).
Click to expand...
Click to collapse
Meanwhile, can N960USQU1CSB3 be flashed to the N960U1?
Gary02468 said:
Meanwhile, can N960USQU1CSB3 be flashed to the N960U1?
Click to expand...
Click to collapse
Yes it can. Use Patched ODIN and flash the full firmware file. Just realize you will get carrier bloat such as the carrier boot screen and preloaded apps.
Mr. Orange 645 said:
Yes it can. Use Patched ODIN and flash the full firmware file. Just realize you will get carrier bloat such as the carrier boot screen and preloaded apps.
Click to expand...
Click to collapse
Great, thanks! And if I do flash N960USQU1CSB3 to my SM-N960U1, can I keep my apps, data, and settings (similar to an OTA update) if I use CSC_HOME?
Gary02468 said:
Great, thanks! And if I do flash N960USQU1CSB3 to my SM-N960U1, can I keep my apps, data, and settings (similar to an OTA update) if I use CSC_HOME?
Click to expand...
Click to collapse
Most likely, but back up everything just in case. I recommend back up with Samsung Cloud and Smart Switch.
Mr. Orange 645 said:
Most likely, but back up everything just in case. I recommend back up with Samsung Cloud and Smart Switch.
Click to expand...
Click to collapse
Flashing my unlocked SM-N960U1 to N960USQU1CSB3 went smoothly and the new firmware shows up as Official in the Settings|Status. All my data and apps were preserved, just like an OTA update.
However, if I try now to check manually for OTA updates, then after it says "Checking for updates..." for a few seconds, instead of then telling me I'm up-to-date, it says "Your current software version isn't supported. Visit a service center."
Does that mean I'm not going to get the next OTA update? And if so, is there any way to fix it? (My model number is now listed as SM-N960U, and service provider SW ver is TMB/TMB/XAA.)
Gary02468 said:
Flashing my unlocked SM-N960U1 to N960USQU1CSB3 went smoothly and the new firmware shows up as Official in the Settings|Status. All my data and apps were preserved, just like an OTA update.
However, if I try now to check manually for OTA updates, then after it says "Checking for updates..." for a few seconds, instead of then telling me I'm up-to-date, it says "Your current software version isn't supported. Visit a service center."
Does that mean I'm not going to get the next OTA update? And if so, is there any way to fix it? (My model number is now listed as SM-N960U, and service provider SW ver is TMB/TMB/XAA.)
Click to expand...
Click to collapse
I'm on T-Mobile and mine just says I'm up to date. Not sure why it would say your software version isn't supported. You may need to factory reset since you went from U1 to U firmware.
Mr. Orange 645 said:
I'm on T-Mobile and mine just says I'm up to date. Not sure why it would say your software version isn't supported. You may need to factory reset since you went from U1 to U firmware.
Click to expand...
Click to collapse
Oh well. I was hoping to avoid that. What if I flash the CSC_OMC instead of HOME_CSC? I've read that for TMO, CSC_OMC won't cause a factory reset. Do you think it might fix the update problem?
Alternatively, if I wait for the unlocked version of CSB3 and then flash that, would that return my device to being able to receive future unlocked OTAs?
Gary02468 said:
Oh well. I was hoping to avoid that. What if I flash the CSC_OMC instead of HOME_CSC? I've read that for TMO, CSC_OMC won't cause a factory reset. Do you think it might fix the update problem?
Alternatively, if I wait for the unlocked version of CSB3 and then flash that, would that return my device to being able to receive future unlocked OTAs?
Click to expand...
Click to collapse
You can try CSC_OMC. It used to cause a factory reset, but I've also heard it doesn't anymore.
If you go back to the U1 firmware when Samsung released Pie, then it should put you back on OTA path, but again you may need to factory reset.
Mr. Orange 645 said:
You can try CSC_OMC. It used to cause a factory reset, but I've also heard it doesn't anymore.
If you go back to the U1 firmware when Samsung released Pie, then it should put you back on OTA path, but again you may need to factory reset.
Click to expand...
Click to collapse
If I try CSC_OMC now, would I flash that by itself (having already flashed the other components), or would I reflash everything over again? And would I still omit USERDATA?
Update 1: I did flash CSC_OMC by itself now, and it didn't wipe my apps or data, but it also didn't fix the OTA-check problem.
Update 2: I did a factory reset. Now the software update properly says up-to-date.
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
What's the model number?
Sm-n960n. Korean exynos model, 512gb.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Bober_is_a_troll said:
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
Click to expand...
Click to collapse
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
joshw0000 said:
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
IqD said:
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
Click to expand...
Click to collapse
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Click to expand...
Click to collapse
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
bober10113 said:
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
Click to expand...
Click to collapse
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Click to expand...
Click to collapse
point taken on the FRP lock but the real point I was making is that the system status is bogus:
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted).
Click to expand...
Click to collapse
bober10113 said:
point taken on the FRP lock but the real point I was making is that the system status is bogus:
Click to expand...
Click to collapse
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
Or this comment:
" I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
And your screenshot really doesn't tell me anything. It's possible to have an unlocked bootloader AND official firmware at the same time. The operating system and bootloader are two different things. It's only when you modify the system that you have to hack the status to make it say official.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
Click to expand...
Click to collapse
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
edit
and the photo of my device status was just a way to show how i know device actual status and bootlaoder state aren't linked. especialy when rooted devices can spoof software status but none cane spoof fuse state in DL mode. so not sure why you are trying to convince me of something i just proved. u can say u agree next time.
bober10113 said:
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
Click to expand...
Click to collapse
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Click to expand...
Click to collapse
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
IqD said:
I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros.
Click to expand...
Click to collapse
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
What a troll.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
What a troll.
Click to expand...
Click to collapse
that's the spirit!
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
no confusion on my part. i read and understood you correctly the 1st time around.
at first glance your device looks ok but...
additionally, there are ways to check if the device is off a lease with a ESN check. meaning if someone sold you a device still on contract. some sell contractual phones and after a period of time they will get blacklisted since the contract is never payed off fully. so device would appear to work fine and one day they just stop getting a signal and esn/imei get blacklisted.
side note:
surprised that this was not brought up earlier in the conversation as a factor to watch out for by some "experianced in the field flipping devices" user instead of stating the obvious like device status and the unreliable means to check it. especialy since, said user stated buying and selling hundred and even thousands of phones...!? ESN state would be no. 1 in the check list if things to watch out for.
anyways back to the current case, there are ESN/IMEI check services in the web to see status of device: stolen, still on contract...etc. i cannot provide any suggestion to these services unfortunately. this is something you need to check yourself or ask around.
good luck
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
Reading this thread I've come to the conclusion that you should sell your rootable and boot unlockable device and buy a locked down USA model.
Thank me later. Least you'll be able to sleep well now.
Sent from my SM-G975U using Tapatalk
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
It's about as safe, in terms of spyware, as you'll ever get from a used phone. I would assume you checked the ESN before buying it but if not, run a check with swappa.com/esn and checkesnfree.com to make sure it's clean. Screenshot the results and save them. Depending on your carrier you can likely run a check on their website and/or call support and ask them as well. As with any unlocked phone, know that you may not get all of the features that a carrier branded phone would have (i.e. I couldn't get WiFi calling working on a Korean S10 on Verizon).
Sent from my SM-N960U using Tapatalk