Database Users

how to bypass flyme os pattern lock on meizu m2 note

i've read similar problems with other users who sought help from the meizu-flyme websites but they won't respond with anything better than a canny reply that they will be looking into it. it's been months since this problem popped up and its amazing that nobody finds anything that specifically addresses this particular product. someone suggested that it is the manufacturer that can provide a valid and lasting solution to this by providing the source code of the os. but even so, i am just a curious cat daring to get killed or be delivered by its boldness. i just can't believe that it is so difficult to gain access to my m2 note again even as it keeps me from doing so and still receive phone calls from it and let me listen to my music with it. No modifications were made to it except perhaps getting root access but I am not sure if debugging was activated before i was shut out from getting in due to this flyme lockscreen pattern that id completely forgotten! i did try the new security flaw that's just been discovered wherein you try to put in a very long string when making an emergency call with it. But when i get to the next step in using the camera, it just won't show the notification shade where i can proceed with what is expected to be done to crash or hang the unit! there is a factory mode that i can boot into but i find no suggestions on what i can do from there. in fact i can even upgrade it successfully (i can watch it go through the process) and it would later inform me that it was successfully done but still the pattern lock would still be there! before it locked me out i managed to link it to my wifi so it is actually online but i don't know how good that is if it could solve my problem at all.

First impressions

I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.

Backing up the ROM
I found SP Flash Tool v5.1632 for Linux and I've been practicing saving chunks of ROM from my bricked phone. I should be able to grab the recovery portion of the new phones' ROM tomorrow.
Based on the scatter.txt file I've found for the Gionee S8 AmigOS Marshmallow ROM, recovery starts at 0x8000 and is no more that 16Mb is size. So, in theory, I should be able to grab that range of the ROM and flash it using fastboot back to my bricked unit. I'm using the word "bricked", but its far from that, I should just say "unbootable" to be more clear.
Earlier today I was trying to get MTK droid tools to detect my Blu Pure XR so I could extract the scatter file, but It never was detected. All the drivers installed ok, so maybe its not compatible, I'm not sure yet. I'll get back onto that after my first unit is back up and working, hopefully tomorrow.
Edit: I just found a modified MTK Droid Tools for 64bit cpu phones, I'll give this a try too.
Edit next day: I got the second phone this morning. I used SP Flash Tool to grab the recovery.img portion of the new phone, then I used fastboot to flash it to the damaged phone, and it worked fine. The bootloader unlock/relock caused the phone to wipe itself and then re-encrypt the file system, so I lost a few test photos, no big deal. FWIW, I could have flashed the recovery back to the damaged phone using SP Flash Tool, but I wanted to make sure it worked with fastboot, which it did.
Heres the recovery.img for those that may need it and don't have two phones
View attachment xr-recovery.zip
Monday or so my mom gets her phone, so I'll be able to test LTE on AT&T with her SIM card. I just got 34Mbs download on a speed test (T-Mobile), which is is fine, considering all the naysayers reviewing on Amazon who didn't have the guts to buy the phone, saying LTE wouldn't work at all.

I just heard of this device today. I wonder how quick Android 7.x can be flashed over to this, but for $299 it's a good looking phone.

It may be a while since there's not much activity happening on this device yet.
I'm focusing on creating a rooted boot.img right now, as I'll be happy with 6.0 and root. I plan on having this done today. I've never created a custom twrp recovery, but I may try that next.
I need to figure out how to prevent the full wipe after oem unlocking/relocking, that's a real pain having all my setup deleted after every test, as it makes it hard to use the phone while developing.

Got root
Firstly, I'm still learning about Mediatek based devices, so I feel like a noob again. I haven't edited a ROM in several years and there's a lot of crap info on the internet. Most articles that write up "how to root a phone" basically say "Install twrp, then supersu", yeah, thanks
After struggling with all the selinux controls in 6.0, I switched to hack mode. As per phhusson's super-bootimg script, I used his sed technique to force the init in boot.img to not enforce security policy and added his bits to init.rc to load su. I put su and in system.img along with a suid root shell just in case. Its working, I have SuperSu installed, and it pops up to ask me to grant permissions. It won't update its su binary, I've got some permission problem there, but it's not a show stopper. Also,I found its easiest to just leave the bootloader unlocked while testing, I just have to get used to the annoying boot message and 5 second delay.
This week I'll start from scratch and document the procedure I used and hopefully make it repeatable for anyone else who may want to try it. Maybe someone will just port twrp and save me the time of learning how to do it
Some notes on the software I used:
Windows:
* SP Flash Tool with a bogus scatter file to grab the stock ROM sections of my phone as the Linux version would timeout reading large ranged of flash.
Linux:
* mktool to unpack/repack the boot.img
* loopback mounted the system.img to add su to it.
* used img2simg to convert system.img to a sparse image
* fastboot to flash the boot & system images to the phone.

AT&T Speed Tests
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!

rotohammer said:
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
Click to expand...
Click to collapse
Hi theer just curious on how you get it to root then??

Thanks for potentially inspiring some activity here regarding this phone. It looks like an impressive device, but I won't pull the trigger until there're some solid rom options.

Hey brother hope you r doing well. Glad to see this thread with the smartphone similar to mine. My phone is symphony helio s20, mtk6755 helio p10 processors, 4gb ram 64gb rom with the similar system.img and boot.img of gionee s8 & blu pur xr.
I was desperately looking for a pre rooted rom or a custom, custom recovery and rooting tool for almost 2 months, requested so many times all around this site, but unfortunately didn't get any respons (really frustated). I just badly need to root my device but I'm just a noob on modding and tweaking with Roms. I got my stock rom from Service Center, when I bricked my phone flashing a custom recovery. Later I tried all the method found all over the website but non of them are working only misleading. Bricked my phone several times but luckily I managed to reflash the stock rom by sp flash tool. Please keep this good work up and help us root our devices without any hassle. You are doing a really great work so keep it up bro!
Here is the link of my stock firmware with sn write tool if you need it for anything bro.
Best regards
https://drive.google.com/open?id=0BywTv6KKZO4jX3BMMGRGVUFRa28
http://www.mediafire.com/download/7...N_Writer_tool_exe_v1.0_1604.00_All_In_One.rar
http://www.mediafire.com/download/pa2f3wqpf24t0db/Helio_S20_flashtool.zip

thanks in advance
Hey guys, thanks a lot for all your info and everything you posted Could you be so kind to describe how did you root your Pure XR devices??? Big hug from Cuba

I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.

Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?

bailsafe said:
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Click to expand...
Click to collapse
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.

Tikerz said:
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
Click to expand...
Click to collapse
This was a Gionee S8 originally, which only supported FDD-LTE bands not in use in the USA. It's a miracle they got FDD-LTE in here at all, I guess, but if you're gonna sell in the US market... they really need more bands.
Rotohammer said:
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Click to expand...
Click to collapse
That's probably your best bet. I'm surprised KingRoot wouldn't work, even on the newer updates...

hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?

orlandotisk said:
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
Click to expand...
Click to collapse
Press left button to bring up the running apps list, long press the button with 3 rectangles in it, then press "Clean white list". Here, you press"Add into white list" and choose "messenger" and any other apps you don't want "auto cleaned".
For example, my white list includes Alarm Klock, K-9 mail, CSipSimple, Silence (all apps that I want running all the time)

rotohammer said:
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Click to expand...
Click to collapse
Hey bro how are you? How's family? I hope that everything is well for you and yours. Basically I just wanted to say thanks for sharing such great info. And I'm really glad that there's someone who's onto something like einstein. I just hope that you can figure out a way to get root with your own custom build of twrp recovery using chainfire's supersu to work with this smartphone. Cos that'll be super-awesome right? But I'm just a noob so all I can do is just wish you the best of luck. So best of luck until you crack the code. And I have complete faith in you. You will achieve it I know that for sure. Wish you and yours all the best. And thanks again in advance. Peace!

Does anybody succeed rooting ?
Please share the method!!

so no one knows how to root?

rotohammer was able to achieve root and said he would get back to us with the method on how it was done, but he hasn't posted it yet...

What circumstances exactly are activating FRP?

At first, I'd like to thank all participants and developers for making this forum possible! I am still absolutely excited about the stuff which is offered and discussed here.
Having said this, I hope I don't get flamed for the following silly question:
I am confused about the FRP on Samsung phones in general and especially the Galaxy S5 (G900F) and would be grateful if somebody could explain what circumstances exactly activate the FRP. I have read many threads, especially on this forum, about how to circumvent the FRP on the Galaxy S5 (after accidentally having flashed and not knowing the Samsung account credentials). But I haven't found a thread which explains exactly when FRP gets activated.
Currently, I do not have a problem with FRP. But I really want to avoid that I have such a problem one day. For certain reasons, I just have bought two brand new Galaxy S5 (G990F, DBT version without branding / lock), one for my wife and one for me.
I did flash LineageOS 14.1 (current version as per the time of writing this) on both phones. I did not create a Google or Samsung account yet, so FRP can't be active yet (as far as I have understood).
One of my understanding problems is that some forum threads / tutorials / posts state that FRP gets activated if there is a Google account, and that others state that it must be a Samsung account. Again, others state that it must be Google / Samsung account together with an active fingerprint or unlock pattern (if this is the right term - I am not a native English speaker). This is very worrying, hence the questions:
- Under LineageOS 14.1 on the G900F, can FRP get active at all?
- If yes, what are the exact circumstances / combinations of conditions which activate it?
- Finally, is there a way to disable it in the first place, i.e. before a Google / Samsung account is created, or before any of the condition combinations which could activate it occurs? In other words, is it possible to globally disable it so that it can't be enabled any more? I would have no problem with rooting, if that would be necessary to achieve that goal. My wife is fantastic, but I won't guarantee that she does not create a Google or Samsung account, does disable the FRP after doing so, or does write down the credentials after doing so
Thank you very much for any explanations ...

Galaxy S5 does not use FRP, it uses Reactivation Lock.
The first refers to Google account, the second - to Samsung account.
RL does not activate by itself, only if you turn it on in the settings.
Some used phones are sold with a kind of RL "bypass" and RL may be activated if you reflash such phone.
But RL can be completely turned off on S5 in a relatively easy way that's why I don's see a cause for concern.
P.S. Are you a virus?

@bbsc Thank you very much for taking the time!
You state that I can turn off RL easily. Do I need a stock ROM to do so? In LineageOS 14.1, I did not find the respective setting, probably because LineageOS does not know about Samsung oddities. Did I miss something?
P.S. No, I am not a virus. Al least, I hope so. Actually, I don't know exactly what I am, and, if anything, how many of them or how much of it.
Joking apart: I am always using random strings as my user name (if it is this why you asked ).

D9yHyi8Fe3mo1YgM said:
At first, I'd like to thank all participants and developers for making this forum possible! I am still absolutely excited about the stuff which is offered and discussed here.....
Click to expand...
Click to collapse
Solely for elaborating what @bbsc has also correctly stated, Here's just a little/brief definition of both...
~ Google FRP (Factory Reset Protection): This is intended for those who may have had (unfortunately) their device lost or stolen and the FRP is there to prevent others from activating your device if they had reset the device to factory settings without the true owners permission. Only someone with your Google account information can use/activate the device.
~ Samsung Reactivation Lock: This is also intended for those who may have had (unfortunately) their device lost or stolen and this security option is tasked to prevent others from activating your device. Once the owner decides to activate this option, this feature will demand the individual to enter the Samsung account credentials for the true owner (the one who had activated this option) after the device was factory reset.
There's more to it but, I believe that this covers the basics of them both as well as the differences between the two.
I hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

D9yHyi8Fe3mo1YgM said:
You state that I can turn off RL easily. Do I need a stock ROM to do so?
Click to expand...
Click to collapse
I don't state YOU can turn it off easily.
I state it CAN be turned off relatively easily. You may want to have a look at my thread about RL on SM-G900V (locked bootloader). It's not you case, but yours is easier.
You can try, of course.
First, look if it really is turned ON. It's clearly seen on the display in Odin (download) mode.
It it's ON and you do know the credentials then just flash any stock firmware and you will be asked these credentials when following Samsung Startup Wizard.
If it's ON and you do NOT know the credentials then flash an early 4.4.2 firmware, bypass Samsung Startup Wizard with one of the known tricks and login to ANY Samsung Account. You will be able to turn RL OFF after this.
P.S. Thank you for the explanation about random char string .

@Ibuprophen Thanks for the explanation ...

BTW, you have LOS installed and this means a custom recovery installed too.
RL blocks custom recovery flashing, so your phone should have RL turned OFF.

bbsc said:
I don't state YOU can turn it off easily.
Click to expand...
Click to collapse
I see. Then we had a misunderstanding. I have assumed that you were relating to some way to disable RL *before* it has been triggered since this is what I had been interested in, i.e. some setting in the OS like: "In the future, prevent all users from activating RL".
But I have now understood that you were relating to how to repair the phone when the RL already is active. When doing my homework (i.e. before asking here), I already had read several threads about that ... it does not seem to be complicated. Fortunately, I don't need to do this.
Coming back to my "problem": Thank you very much for the tip that the status is visible in the download mode. On my phones, it clearly states that it is not active. I had expected that because otherwise I would have had problems with installing TWRP and LineageOS.
But there are still questions left:
Just to be sure: I have understood the difference between FRP and RL, but I am not sure if the situation with the stock ROM is the same as with LineageOS. Could somebody please clarify?
In other words, if I use nothing else than LineageOS in the future, can I be sure that nor RL nor FRP will trigger one day given the fact that RL is currently not active?
In other words again, I have understood that the phone does not use FRP with the stock ROM. But LineageOS is more Google than Samsung, hence I am worried if FRP possibly could be triggered from within LineageOS. Could that be possible?

SM-N910A, Android 6.0.1, Just need to work via WiFi

Daughter had her Note 4 replaced a few months ago, and it had just been sitting there. Earlier this week got a DJI Spark, and the flight controller requires an Android or iOS phone. Got tired of pulling the case off and on MY phone (S8+), so figured I could use hers as a WiFi-only, dedicated device.
My main concern is that I don't think we ever got the phone formally unlocked by AT&T. I've gotten around that so far just by pulling out the sim. It doesn't seem "happy" about it, but hasn't stopped me configuring the phone to do what I need so far - though it would be nice to be able to uninstall all the AT&T apps that are on there even after a full reset/wipe.
So wondering if there is:
A) Some way to unlock this old thing so I can rest easy it won't have an issue waking up one day
B) A more recent ROM and/or security updates (while it mainly will access the Drone/Receiver WiFi I presume I need to still connect to the home LAN occasionally for app updates)
C) Anything I could flash to make it less of a phone and more of a small tablet (since that's how I'll be using it)
Thanks in advance!

If you are saying the phone is locked to AT&T and you want it unlocked then see here:
https://www.att.com/deviceunlock/#/
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.

terminator911 said:
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.
Click to expand...
Click to collapse
Ah... well that's too bad. I like that the phone has a replaceable battery, which makes it almost worth keeping as long as possible for that. Will try your suggestion on the other. Thanks anyway!

Screen turns on when plugging in for charge / High Volume warning Mods?

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