Related
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Obscure Reference said:
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Click to expand...
Click to collapse
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
fivecheebs said:
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
Click to expand...
Click to collapse
Yeah, I know.. I had it built in while running CM. Just had an urge to go back to stock for a while and was just wondering what features I wanted actually required root (and xposed).
If anyone else knows of a way, please let us know.
Hi gys, slightly different issue here, but would appreciate any help.
basically the PIN lock does not activate until 30 seconds or so after the phone boots up. So there is no securuty on initial boot up.
Its there if I do a reboot. But not there if I do a startup from fully off.
It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result and have tried several roms.,
Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.
I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
Can Tasker achieve something like this? I have only returned to Android after a 3 years break, any advice is much appreciated!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have that setting enabled. It works on the lock screen where you can swipe to unlock, but not on the darker lock screen, where it shows the time and the outline of your notifications.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
dancooper93 said:
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
Click to expand...
Click to collapse
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
srdjanLeo said:
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
Click to expand...
Click to collapse
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
MilgeS said:
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
Click to expand...
Click to collapse
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
srdjanLeo said:
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
Click to expand...
Click to collapse
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Okay, I see.
Does charging not stop at 80% for you because you are rooted?
artikle said:
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Click to expand...
Click to collapse
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
srdjanLeo said:
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
Click to expand...
Click to collapse
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
dancooper93 said:
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
Click to expand...
Click to collapse
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
srdjanLeo said:
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
Click to expand...
Click to collapse
I am now rooted
What Note 8 ROM did you use?
dancooper93 said:
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
Click to expand...
Click to collapse
I meant "open" as in on lock screen re your above post, the screen after AOD, sorry for any confusion
Same here works after you swipe but not from AOD, every time tutorial I have seen says the same has to be "open" before it will work.
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
scatterthought said:
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
Click to expand...
Click to collapse
That's not true. It still works on a Google Pixel running stock Android with the screen off and not charging. You never had to have it plugged in or charging for that to work. Samsung is the ONLY Android phone I know of that OK Google doesn't work with the screen off.
Source: I've owned the Nexus 6, Nexus 5x, the Nexus 6P, the Pixel XL, a number of Galaxy phones, and a few Motorola's and a couple LGs.
My brother passed away and was using this phone until a couple of weeks ago. I don't have the lockscreen pattern but I'm trying to do a little detective work regarding my brothers last activity. I reached out to law enforcement, but they don't have an active investigation and they suggested that I reach out to his cell provider [Tracfone] which I might try. Of specific interest to me is his text message activity on the day of his death.
Anyhow I scoured the net and tried to beat the lockscreen via emergency dialer, and also tried to connect via adb shell and MTP. I also don't think the device was registered via the samsung tools. I'm at the point where the device told me I have 9 unlock attempts left and it will erase the device after. The lockscreen seems to appear at device power and I think that it might not have booted android completely at this point.
Is anybody aware of a method to bypass the lockscreen which would work on this device so I can look into the details surrounding his death?
Sort of desperate here. There seems to be some software called Dr Fone that claims to have a lockscreen removal. However not sure that it works and on this device.
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =]
phonecapone said:
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =
Click to expand...
Click to collapse
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
veryspecialagent said:
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
Click to expand...
Click to collapse
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
This was before I got into development, so adb isn't enabled, bootloader is still locked, and the phone is not rooted, so I'm skeptical I'd be able to flash. It's also running (I believe) Marshmallow, and most of those "find and delete lock settings" methods were for 4.x Kit-Kat and below. I could be wrong though.
If you have a particular thread in your watch list, I'd be grateful for the link.
I've been all over looking for a solution, hence me posting in here as opposed to creating a thread. Didn't want to reinvent the wheel if I didn't have to.
Despite the above limitations, the device has not received any updates since June 2017, it DOES go into MTP mode when I hook it to my laptop, and I have verified that it is vulnerable to the Mtpwn exploit.
noidodroid said:
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
Click to expand...
Click to collapse
Also, I turned a moto g7 Play into a Nethunter device and had tried Android PIN Bruteforce, but after entering in so many PINs it would make me wait 30 seconds to try again and I couldn't figure out how to get my g7 to keep the screen of the J3 on. Or wake it back up, since it requires you to hit power then swipe the screen.
I ended up wiping it because it had Pie and no workaround for the wifi throttling, and installed Q. It's rooted, but I haven't set up nethunter back up on it yet. I do have an S5 that I has Nethunter, but haven't set it up with HID support yet. Plus, the battery on that would drain too quickly to use for this process.
Hello!
I've been out of the rooting / custom rom game for awhile (last used with my galaxy s5) and I had a couple of questions for the community. I've been looking at rooting my phone and installing a custom rom basically only for these two things that keep bothering me.
1. Phone turns on screen when placed on charger. I won't explain why this annoys me and I've read all the posts where people are like "just set your time out to 30 seconds". I have a long time out because I am a musician and I use the phone at times for reading music. My nightly routin consists of placing my phone on my wireless charger and then pressing the power button to turn the screen off. I'd just like the phone to start charging without turning the screen back on. Minor inconvience I know, but we live in 2019 and I should be able to customize my phone the way I want, right?
2. When I'm listening to music over bluetooth, I try to increase the volume and get the "listening at high volumes..." notification. I would like to disable this permantely. I know that it goes away after hitting okay once, but it comes back after restarting. This is esspecially troubling while in the car and I have to look down at the phone and press the button making it more of a risk than it "helping me with loud volumes".
I remember using roms years ago that addressed these two specific problems and I loved them for that. So my question is, are there any fancy rooted mods I can do to my phone to disable these things, or is there a ROM that specifically addresses these issues I have? Are there files I can delete, or code I can modify? Ideally I can just disable these two things and stay stock, but I'm down for anything at this point.
Running a Unlocked Galaxy S8 SM-G950U1 with Android version 8.0.0.
Thank you for your help XDA community!
-M
mikeymasonic said:
Hello!
I've been out of the rooting / custom rom game for awhile (last used with my galaxy s5) and I had a couple of questions for the community. I've been looking at rooting my phone and installing a custom rom basically only for these two things that keep bothering me.
1. Phone turns on screen when placed on charger. I won't explain why this annoys me and I've read all the posts where people are like "just set your time out to 30 seconds". I have a long time out because I am a musician and I use the phone at times for reading music. My nightly routin consists of placing my phone on my wireless charger and then pressing the power button to turn the screen off. I'd just like the phone to start charging without turning the screen back on. Minor inconvience I know, but we live in 2019 and I should be able to customize my phone the way I want, right?
2. When I'm listening to music over bluetooth, I try to increase the volume and get the "listening at high volumes..." notification. I would like to disable this permantely. I know that it goes away after hitting okay once, but it comes back after restarting. This is esspecially troubling while in the car and I have to look down at the phone and press the button making it more of a risk than it "helping me with loud volumes".
I remember using roms years ago that addressed these two specific problems and I loved them for that. So my question is, are there any fancy rooted mods I can do to my phone to disable these things, or is there a ROM that specifically addresses these issues I have? Are there files I can delete, or code I can modify? Ideally I can just disable these two things and stay stock, but I'm down for anything at this point.
Running a Unlocked Galaxy S8 SM-G950U1 with Android version 8.0.0.
Thank you for your help XDA community!
-M
Click to expand...
Click to collapse
You need a modified Frame Jar so you can be able to have the screen stay off when you put in the charger if you was willing to install xposed I can lead you to a Module that resolves your first issue... For your second issue the same module resolves that issue also
([emoji3590]09-09-18[emoji3590])
You need a modified Frame Jar so you can be able to have the screen stay off when you put in the charger if you was willing to install xposed I can lead you to a Module that resolves your first issue... For your second issue the same module resolves that issue also
Click to expand...
Click to collapse
I'd be way into that! Please lead the way! So if I'm understanding correctly, I will need to root, flash a recovery such as TWRP, install Xposed frameworks as shown here for Oreo (my current OS), install the APK, and install the modules you point me to? Will I need to flash the stock OS again after installing the recovery? Please let me know if the link I added is out of date and if there's a newer thread. Also I am curious as to what the preferred/most up to date rooting method is for an unlocked Galaxy S8 if someone wouldn't mind sharing a link? It seems as there are a few more steps than what I was used to years ago, but I'm definitely down to dig in. Thank you for your help!
-M
PoochyX said:
You need a modified Frame Jar so you can be able to have the screen stay off when you put in the charger if you was willing to install xposed I can lead you to a Module that resolves your first issue... For your second issue the same module resolves that issue also
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
I'm now realizing I may be in some trouble as I've been doing some more digging. Am I correct that because I have an SM-G950U1 Snapdragon US "Unlocked" phone, that I have a locked bootloader and therefore cannot root?
The only thing that looks hopeful I've been seeing is with this guide, but the rom is for Nougat: here
I'd prefer to stay "stock" Oreo if possible.
Can I even install TWRP or Xposed without root on Oreo?
Thanks for your help.
Can anyone help with this? Thanks!
mikeymasonic said:
I'm now realizing I may be in some trouble as I've been doing some more digging. Am I correct that because I have an SM-G950U1 Snapdragon US "Unlocked" phone, that I have a locked bootloader and therefore cannot root?
The only thing that looks hopeful I've been seeing is with this guide, but the rom is for Nougat: here
I'd prefer to stay "stock" Oreo if possible.
Can I even install TWRP or Xposed without root on Oreo?
Thanks for your help.
Click to expand...
Click to collapse