Stock S8 (UK, Three) - CTS profile fail - Samsung Galaxy S8 Questions and Answers

I purchased a refurbished S8 (SM-G950F) from Argos eBay a few months ago. Phone seemed in perfect cosmetic condition, but the software side of it has started to annoy me.
I couldn't get banking apps to work correctly, then found out that when running Safety Net I get "CTS profile match - Fail". I've done nothing to it (root, ROMS etc), so can only assume it's something to do with the bootloader in the refurb process?
Also, weirdly, in "About Phone", the "My Phone Number" is totally different to mine.
Phone is currently on Nougat. Would it have had Oreo installed OTA if it was passing Safety Net?
What options do I have with regards to making it pass CTS profile match? Would flashing a new stock ROM be a waste of time if the bootloader has been modified?
Thanks in advance.

Sounds like the bootloader has been unlocked, try using magisk and magiskhide to hide root from your banking apps. Works for me on the Halifax banking app

Trying to install TWRP via Odin (to then get me to installing Magisk) but I'm going round in circles.
Everything I read online says you don't need a PIT file in Odin, but this is what mine is showing (JOdin3 on Mac OS, FYI)
Downloaded TWRP file and added to PDA section
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click Start, and get this popup
If I select a PIT it tells me I have I to re-boot phone, but when I re-boot into Download mode, it won't connect in Odin!

So it took me a bunch of attempts and a few times where I thought I'd soft-bricked it, but managed to install Magisk (and updated to Oreo in the process)
Ended up borrowing a legit Samsung cable, and doing it all on a Windows machine.
Also now have Google Pay working and fingerprint login on my banking app

Related

Dropbox gives me a "storage full or unavailable"

Not sure what the cause is, just got my 7 yesterday.. stock rooted, aokp, doesn't make a difference- dropbox doesn't work and just gives the error "Storage full or unavailable"..
Doing a search, the only thread that mentioned it was "[ROM]| Glazed JellyBean|Version 1.1.2|Glazed Mods|Custom Animations|Speed|" and it had to do with an error in the rom, not my issue.
I've tried reinstalling the app, factory reset, flashing aokp(from stock rooted)- none have had a working dropbox, but I can't find any other posts that others have had the same issue.
I also have a few error 492 when downloading a few apps from market(like dead trigger), not sure if it is related..
Is dropbox looking for an external SD?
And "Protect usb storage" is NOT checked in developer options, just in case someone asks.
All I did was unlock bootloader, root.. nothing that should keep dropbox from working.
Although Im on stock but unlocked bootloader and rooted i have had the play store error and i just restarted and it worked fine since, dropbox i cant help mine logs in fine and i can use it perfect
Sent from my Nexus 7 using Tapatalk 2
My issue seems to be more than just drop box.. stock gallery app closes immediately after showing this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As I said, pretty sure I didn't do anything to cause this.. I'm assuming there's a way to flash the original software that will repartition the device(like flashing HTC phones with ruu, or Samsung with Odin)?
I haven't had a lot of time to look into these things since o got it yesterday, so if anyone has a quick possible solution is appreciate it!
Edit: I'd like to know if this process([Guide] Returning to Stock and/or Unbricking your device) http://forum.xda-developers.com/showthread.php?t=1781250 actually repartitions everything.. but I decided to go trade this one out for another one rather than beat my head on a wall with an issue no one else appears to have. Still worth finding out.
Sent from my Nexus 7 using xda app-developers app

Axon 7 Nougat Root

Hello guys.
What is the status about the root / bootloader unlock for Axon 7 running nougat?
these are the specs of my phone right now, and to be honest, after many years of being an iPhone owner I feel kinda lost regarding the root techniques.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WizeMan said:
Hello guys.
What is the status about the root / bootloader unlock for Axon 7 running nougat?
these are the specs of my phone right now, and to be honest, after many years of being an iPhone owner I feel kinda lost regarding the root techniques.
Click to expand...
Click to collapse
NP just read Controllerboy's guide if you have an A2017G.
But before that, be warned about 2 things:
Your data will be wiped after you unlock the bootloader, and if you unlock it you'll probably be wiping and trying ZIPs every once in a while, so get used to backing up stuff and using Google for contacts etc.
That guide was for Marshmallow I think. You can download version B10 or B11 from ZTE's website, then unpack it until you get an update.zip (it should come as a zip with a bunch of numbers, and inside it there's a zip matrioska'd inside). Put it on the root of your internal storage (root means outside of any folder) and go to Settings the Updates. It should find the zip and install it. After that go to Developer options (to enable it go to About phone and tap Build number a buncha times, then it should appear above About phone) and enable Enable OEM Unlock. Now you have Marshmallow and can use the guide.
Another way is doing all the procedure up there but using axon7toolkit instead of that guide. Never used it for this procedure but it should work just fine and do the same. You can get more experience from using the guide though, and that experience may come in handy if you ever tinker too much

Device owner already set before purchasing?

I did a factory reset and wiped the cache, several times in a row last night, because I got sick of a few things and wanted to run a test.
I wanted to install IceBox Apps Freezer. You don't need root, so long as you set it to be 'Device Owner' using ADB shell:
Code:
adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
The app says to remove all accounts associated with the device in order for that to work. On our tablets (all models) this isn't possible. So I had to find out a way that would clear all 'device owners.' Google itself is very specific about how this is to be done: Factory reset.
Caution: If provisioning has already started, affected devices must be factory reset first.
Click to expand...
Click to collapse
Since I did that, and didn't register the tablet with Amazon, Managed Provisioning shouldn't apply. However, I followed all the steps, made sure WiFi was and still is off and went into ADB and this is what I got in return:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Trying to set device owner but device is already provisioned
Click to expand...
Click to collapse
Um what? Is that even legal?
have you seen anyone having success with Amazon devices?
it's possible they didn't include this feature
yossijoe said:
have you seen anyone having success with Amazon devices?
it's possible they didn't include this feature
Click to expand...
Click to collapse
As far as I can tell, through all possible methods to gain Device Owner, Amazon has provisioned the devices, en mass, before they are even purchased. Likely done with NFC which is included on the Fires, but is another piece of software Amazon blocks us from accessing and or using. Even a factory reset and attempt to add device owner on language selection screen failed.
IMHO this really should be illegal. What the hell did we actually buy then if we don't own these?

Gapps is bugged / TWRP does not recognize its own backup (x722)

hello, I require your help to operate my cell phone, I'll tell you step by step what I've done... [it is obvious that my native language is not English]
first, i installed TWRP following this tutorial https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
second, backup the complete system with twrp 3.1.1-0 (O.S. 5.8.0.20S Stable, android 6.0.1, Banggood international version). This left me a folder full of files which twrp does not recognize when I want to install that backup again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
third, Install the ROM by following this tutorial https://forum.xda-developers.com/le...ent--and-mods/stock-eui-5-8-20s-x722-t3680624 Something seems strange to me that when I run the .bat, the phone reboots in a couple of seconds and the only change I see is that it installs the original recovery, since everything else stays the same, even the system version (EUI version: 5.8.001D (Dev))
Finally install S.U. official (all correct), and OpenGApps, use the Stock and Nano (ARM64, Android 6.0) versions, and both show error when starting the system,
does not allow me to do anything (attached image).
So here I am, with a new cellphone, without being able to restore the copy made with twrp, using a EUI developer version, and without being able to install the Gapps.
---I would greatly appreciate your help---
I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), It could not start because asked for a false password, then, without deleting anything, i installed from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
https://forum.xda-developers.com/showpost.php?p=74129299&postcount=41
How can I end the post?
Kaidodal said:
I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), I could not start because I asked for a password and it did not accept it, then, without deleting anything, install from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
How can I end the post?
Click to expand...
Click to collapse
Great news. You don't need to do anything. You've done your part. :good: Just leave it up for people in the future to look at and learn from.

Magisk Manager beyond version 18 won't run on SM-G950F with stock OREO ROM

Geniuses,
I've been trying to get Magisk Manager 23 running on my S8 and can't seem to figure out what's going wrong. I've installed the Oreo (8.0) stock ROMS with Odin and successfully rooted the phone using Magisk both with and without TWRP. Root works and even SafetyNet checks pass, but the Manager will not come up, it just stays stuck at the Home screen as if I have yet to install it. I should mention, any version of Magisk prior to 19 seems to work fine, but I need some of the plug-in features from 21+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tjunck said:
Geniuses,
I've been trying to get Magisk Manager 23 running on my S8 and can't seem to figure out what's going wrong. I've installed the Oreo (8.0) stock ROMS with Odin and successfully rooted the phone using Magisk both with and without TWRP. Root works and even SafetyNet checks pass, but the Manager will not come up, it just stays stuck at the Home screen as if I have yet to install it. I should mention, any version of Magisk prior to 19 seems to work fine, but I need some of the plug-in features from 21+
View attachment 5398069 View attachment 5398089 View attachment 5398097
Click to expand...
Click to collapse
I'm an idiot! =)
What happened? How did you resolve it?
There is no worse thing on the internet than people posting, "oops fixed it" without them telling how they did it!
For prosperity
kIERO's said:
What happened? How did you resolve it?
There is no worse thing on the internet than people posting, "oops fixed it" without them telling how they did it!
For prosperity
Click to expand...
Click to collapse
Bottom line is it's working fine. topjohnwu's installation instructions are not clear if you haven't been keeping up with each release, but this is how it works now...see the little floating menu of icons on the bottom of the third screen I posted...thats how you get to everything I thought was missing.

Categories

Resources