Thanks to an idea from the dev of GravityBox, we can now have full LED control on stock with almost any LED control app. I tested it with GravityBox, and a few ghetto LED control apps from the play store and they all worked perfectly!
This also enables the LED to light up when charging.
You can either use the flashable zip, or replace the file manually. To replace it manually download the file attached to this post, place it in /system/lib/hw/ and replace the file that is already there. Make sure it has the same permissions as the other files, and then reboot.
This has only been tested on 5.1.1 (I'm running LYZ28E).
And no, it doesn't blink. Either the CM team hasn't cracked it yet or the LED drivers are just not there to make it blink.
A flashable ZIP has also been added to this post. ZIP created by @spacetaxi
Thanks! Seems to be working fine on LMY47Z as well. :good: Did some quick tests on my Nexus 6 and will try to regularly use it now instead of LightFlow Pro.
Does led blinking work without light flow?
Unfortunately it doesn't seem so.
So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.
OKAstro said:
So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.
Click to expand...
Click to collapse
Because a lot of people have issues with LightFlow since you have to do some really ghetto things to make it work. This guarantees that it will work and allows you to use any app you want.
OKAstro said:
So you still need to install an LED apk besides this?
Click to expand...
Click to collapse
No, this is my setup: Stock rom, rooted, modified lights.shamu.so installed, Xposed installed, GravityBox installed. But: All LED related functions in GravityBox are disabled, so I don't think that GravityBox or Xposed has to be installed. I can enable LED notifications e. g. in K-9 settings - and it just works! No GravityBox, Xposed or LightFlow involved. So if the regarding app supports LED notifications there is no need to use a "LED contol app".
Edit: The led *blinking* does not work. Instead the led is switched on permanently during a notification.
OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.
OKAstro said:
OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.
Click to expand...
Click to collapse
I believe it supports charging indication as well. I thought it was GravityBox doing it but apparently it is the OS.
Your title is a little misleading.
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.
I am running Gravity Box and yes it does work, although LED on N6 sucks
vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?
spacetaxi said:
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?
Click to expand...
Click to collapse
That's a very good point. You could actually just do it in recovery if it supports ADB. You can push files over ADB really easily.
Just a tip. In order to get acurate red green blue colors for LED, instead of picking it, use exact hex value then its not going to mix with over colors
Blue #0000ff
Green #00ff00
Red #ff0000
Will this work in Android M?
jodvova said:
Will this work in Android M?
Click to expand...
Click to collapse
I went ahead and pushed it over using ADB and recovery on my phone running Android M. So far it seems to be working fine, though you won't be able to alter the light without an application that supports it.
A few reasons.
GrayBoltWolf said:
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.
Click to expand...
Click to collapse
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Who was denied warranty with unlocked bootloader? I haven't experienced that on any of my phones yet, even none Nexus devices
vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Google has absolutely no way to tell if you unlocked your bootloader unless you either 1. tell them or 2. send you phone in unlocked.
There have been 0 reports of anyone being denied warranty service on a Nexus device and any that may exist were because the user told Google they were unlocked.
At any rate this mod does not require root, as you can flash it through recovery or over ADB.
Related
This question is mostly aimed at the Devs, but if there's already a thread out there, please simply point me in the correct direction - thanks.
The question: How do we disable the scan that checks /system for modifications and marks the phone as "custom" ?
Disclaimer: I'm not interested in warranty fraud - that's just silly. I just want to be able to run custom kernels or delete bloatware (instead of freezing) and still retain the nice Galaxy S4 logo on startup... not the ugly "Custom" padlock/logo.
As mentioned by @scott14719 in this post, disabling the scan altogether may cause other problems (won't know until we try?). However, it seems clear to us that this scan, upon determining that the /system is indeed customized, throws a red flag that is read by the bootloader upon next startup. My goal here would be to either disable the scan altogether, or somehow permanently disable this red flag.
Not knowing much about the scan itself, here's some more observations that might help:
Most critically, the padlock/"custom" boot screen is NOT triggered until this scan is run and the system is flagged.
The scan runs immediately upon startup and finishes within about 38 seconds of uptime. Might take longer if more files have been added to /system or if more apps are running on startup (and slowing it down).
If you quickly go look at the Device Status in About Phone within the first 38 seconds of startup, you can see that it is "scanning" at this time.
It seems that the scan does not run again until the next system startup.
A custom recovery does not trigger "custom".
A custom kernel triggers the "custom".
Freezing bloatware does not trigger the "custom".
I once uninstalled a lot of bloatware, and this triggered "custom". I haven't checked to see if it's any system apps that trigger it, or if only certain apps are monitored.
Having busybox and/or Superuser properly in-place will trigger "custom".
All this being said, can anyone offer some more insight into this scan, and more ideally: has anyone found a way to disable it?
EDIT:
Thank you everyone for your replies. I've finished a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700
I think that splash screen is compiled into the kernel or aboot on these phones but im not 100% sure, there are a few threads in the s3 area about changing the splash but it requires an unlocked boot loader.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2257058
Sent from my GT-I9505 using xda app-developers app
Try this also.
If code can be located and then changed to report "official" no matter what the scan returns, it would be a huge hurdle.
C13v3r0n3 said:
I think that splash screen is compiled into the kernel or aboot on these phones but im not 100% sure, there are a few threads in the s3 area about changing the splash but it requires an unlocked boot loader.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2257058
Sent from my GT-I9505 using xda app-developers app
Try this also.
Click to expand...
Click to collapse
I believe you are correct in that the only way to remove or modify the boot screen itself would be to have an unlocked bootloader. However, I believe that we should be able to keep it from ever showing the "custom" screen, simply because it's clear that the system doesn't check for "custom" during the time that this screen is shown. Rather, it's fed by a variable or tidbit of code somewhere.
Also, regarding the thread you linked: this of course works fine... until you make any modifications to /system. I've used this method a few times myself, even. But once I uninstall masses of bloatware or install a custom kernel, this method won't work anymore until the changes are restored.
scott14719 said:
If code can be located and then changed to report "official" no matter what the scan returns, it would be a huge hurdle.
Click to expand...
Click to collapse
Without an unlocked bootloader, I believe this is the only way we can accomplish this... apart from preventing the scan to begin with, of course.
Aou, here is an interesting read that I think may, at least partly, apply to our device...
http://forum.xda-developers.com/showthread.php?p=38934760
I haven't had a chance to check the entire thread or the links within that thread but it seems like some people have already put some thought into this. Maybe something can be built on top of this.
**Edit**
It seems that we are definitely thinking about this the correct way. This is a post about the Verizon S3 bootloader unlock but the custom screen is discussed heavily between pages 7 and 12.
http://forum.xda-developers.com/showthread.php?t=1769411&page=7
post 68 seems to show exactly the point where the code for custom or official exists on that phone. I am willing to bet it is very similar on the AT&T S4. However, reading these threads shows me that some very smart guys (including Adam Outler) are way deeper into understanding this than I could ever be. Though, maybe it shows that there is hope for this after all.
Im am sure the local android badasses will figure it out, we have some beast devs around here.
Sent from my GT-I9505 using xda app-developers app
That is interesting - I jumped straight from the S2 to the S4, so I had no idea about SysScope. Out of curiosity, I froze the following two apps and restarted:
EdmSysScopeService.apk
SysScope.apk
Upon restart, I had the "Custom" status. Also, it took a lot longer for the "Device status" to finish Scanning. but now shows custom.
I'll play with this a bit more...
Aou said:
That is interesting - I jumped straight from the S2 to the S4, so I had no idea about SysScope. Out of curiosity, I froze the following two apps and restarted:
EdmSysScopeService.apk
SysScope.apk
Upon restart, I had the "Custom" status. Also, it took a lot longer for the "Device status" to finish Scanning. but now shows custom.
I'll play with this a bit more...
Click to expand...
Click to collapse
Another interesting post...
http://forum.xda-developers.com/showpost.php?p=29227801&postcount=107
and
http://forum.xda-developers.com/showpost.php?p=29244923&postcount=109
Again, this is not from our phone but it seems pretty damn close. This post is from the second link I posted above.
scott14719 said:
Another interesting post...
http://forum.xda-developers.com/showpost.php?p=29227801&postcount=107
and
http://forum.xda-developers.com/showpost.php?p=29244923&postcount=109
Again, this is not from our phone but it seems pretty damn close. This post is from the second link I posted above.
Click to expand...
Click to collapse
It might still be applicable. Going to bed for now, but it sounds like the devs in this thread you linked to have managed to accomplish exactly what I'm after here. I wonder if any of them have posted more details elsewhere...
Again from the Verizon S3 thread...
http://forum.xda-developers.com/showthread.php?t=1781471
This has more to do with the counter, but the areas of code are the same.
Of course, that is if the Verizon S3 has a similar code as the AT&T S4.
**EDIT**
Some more information about Sysscope from the Note II forum. This just helps to show what it scans and why it returns "custom". The code will still need to be located and modified for the S4 (similar as described in one of the links I posted in one of my above posts about the S3) in order to keep the phone as "official".
http://forum.xda-developers.com/showthread.php?t=2285894
This post also helps to show why just freezing, deleting, or modifying syscope will still return a "custom" status. Other processes are at work to make sure syscope is authentic. That is why the code which decides what is returned (after the scan) needs to be modified.
TRY THIS: http://forum.xda-developers.com/showthread.php?p=42062451#post42062451
Aou said:
This question is mostly aimed at the Devs, but if there's already a thread out there, please simply point me in the correct direction - thanks.
The question: How do we disable the scan that checks /system for modifications and marks the phone as "custom" ?
Disclaimer: I'm not interested in warranty fraud - that's just silly. I just want to be able to run custom kernels or delete bloatware (instead of freezing) and still retain the nice Galaxy S4 logo on startup... not the ugly "Custom" padlock/logo.
As mentioned by @scott14719 in this post, disabling the scan altogether may cause other problems (won't know until we try?). However, it seems clear to us that this scan, upon determining that the /system is indeed customized, throws a red flag that is read by the bootloader upon next startup. My goal here would be to either disable the scan altogether, or somehow permanently disable this red flag.
Not knowing much about the scan itself, here's some more observations that might help:
Most critically, the padlock/"custom" boot screen is NOT triggered until this scan is run and the system is flagged.
The scan runs immediately upon startup and finishes within about 38 seconds of uptime. Might take longer if more files have been added to /system or if more apps are running on startup (and slowing it down).
If you quickly go look at the Device Status in About Phone within the first 38 seconds of startup, you can see that it is "scanning" at this time.
It seems that the scan does not run again until the next system startup.
A custom recovery does not trigger "custom".
A custom kernel triggers the "custom".
Freezing bloatware does not trigger the "custom".
I once uninstalled a lot of bloatware, and this triggered "custom". I haven't checked to see if it's any system apps that trigger it, or if only certain apps are monitored.
Having busybox and/or Superuser properly in-place will trigger "custom".
All this being said, can anyone offer some more insight into this scan, and more ideally: has anyone found a way to disable it?
Click to expand...
Click to collapse
As others pointed out throughout the thread, the file responsible for checking the system status at boot is SysScope. There are various ways of trying to "full" the system into believing that it was NOT modified when in fact it was but one that has been working fine on my Note 2 as well as the S4, uses an XPosed Framework module called...yeah, you guessed it, SysScope.
Furthermore, if you're not familiar with XPosed Framework you'll be in for a NICE surprise as, once the framework installed it gives you the possibility of installing many other modules - real goodies, and I mean real goodies!!!
A word of caution: DO NOT INSTALL any version of XPosed Framework prior to 2.1.4- it'll soft brick your S4.
Take a look at the attached screenshot. Needless to say that my phone is heavily customized/modified.
Awesome! I would still like to know how to modify the code manually ( incase people don't want to use XPosed for whatever reason), but this is getting pretty close to the objective and I think will work for most. Thank you.
Here something very interesting. All credit goes to Mr. Impossible. I have not tried this so it should be interesting to see how well it works.
http://forum.xda-developers.com/showpost.php?p=42098246&postcount=729
scott14719 said:
Awesome! I would still like to know how to modify the code manually ( incase people don't want to use XPosed for whatever reason), but this is getting pretty close to the objective and I think will work for most. Thank you.
Click to expand...
Click to collapse
This SysScope Xposed module says its re-enables logcat'ing for SysScope. Maybe with this enabled, you can tell what functions need modifications. But if something else is monitoring SysScope's integrity, the rabbit hole may get pretty deep. The advantage of something like Xposed is that the apps are not modified so something checksum'ing them won't notice anything different.
For what its worth, I restored my device using Odin and rooted it. Followed the common steps to replace SuperSU with Superuser and rebooted a couple of times until the "custom" message was gone. I booted into recovery, installed CM10.1 and never looked back. My phone boots with the standard logo now each time because CM doesn't have SysScope.
romracer said:
This SysScope Xposed module says its re-enables logcat'ing for SysScope. Maybe with this enabled, you can tell what functions need modifications. But if something else is monitoring SysScope's integrity, the rabbit hole may get pretty deep. The advantage of something like Xposed is that the apps are not modified so something checksum'ing them won't notice anything different.
For what its worth, I restored my device using Odin and rooted it. Followed the common steps to replace SuperSU with Superuser and rebooted a couple of times until the "custom" message was gone. I booted into recovery, installed CM10.1 and never looked back. My phone boots with the standard logo now each time because CM doesn't have SysScope.
Click to expand...
Click to collapse
The Xposed module for SysScope does appear to work well. I agree that it would be nice to know how to modify a stock (or TW-based) ROM such that SysScope is removed without the other apps noticing.
I'm thinking that in your case, romracer, the bootloader last knew your status to be "official" - and because SysScope (and other related checks for it) are completely gone, the bootloader has no way of knowing otherwise. Interesting. I wonder if there's something we can do to these handful of apps to "neuter" them, keeping them from reporting to the bootloader that the status is Custom.
Sweet! It worked! No longer showing custom icon!!
Update: I've got a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700
Aou said:
Update: I've got a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700
Click to expand...
Click to collapse
Awesome, I knew you would get it going.
Has anyone been able to automate this procedure to make it more simple? Seems like quite a bit involved to get it done. Would like to see the Custom status gone for good but wouldn't mind a simpler solution
Sent from my GT-I9505 using XDA Premium 4 mobile app
Found two 16GB and one 32gb at staples. Bought them all. 32 is for me and my wife, 16 is for my 5 and 1 year old to share.......the other 16 is sealed and on the auction site, lol.
I LOVE this thing so far. Granted it doesn't do anything My LG G2 doesn't do, but the 7" size is far more comfy to watch a show or browse around on when I'm lounging at home.
Couple cases ordered already, but the big question.....to root or not? To Rom or not (I have the 5.0.2 downloaded but haven't installed yet)..........
No reason to root really for general use.
it works fine right out of the box.
taqulic said:
No reason to root really for general use.
it works fine right out of the box.
Click to expand...
Click to collapse
Agreed.
Felt no need to root mine at any time. Any bloat you dont like can be disabled. :angel:
Don't really need to root if you don't want to, but unlocking the bootloader before you get it all configured how you like probably wouldn't be a bad idea, especially if you think you might root in the future.
It makes rooting and not losing data later much easier.
Well, I'm not a crack flasher by any means, but I also know there's some kernels out there that have the knock knock baked in (I absolutely LOVE the knock knock in my G2), and I always appreciate a cleanrom (used to run that on my HTC Rezound), but I'm thinking root for both mine and my kids so I can install adaway at the very least. I'm just trying to verify if having root without installing a custom recovery will block OTA's because I'd like my kids N7 to be able to receive those.
Fastbird said:
Well, I'm not a crack flasher by any means, but I also know there's some kernels out there that have the knock knock baked in (I absolutely LOVE the knock knock in my G2), and I always appreciate a cleanrom (used to run that on my HTC Rezound), but I'm thinking root for both mine and my kids so I can install adaway at the very least. I'm just trying to verify if having root without installing a custom recovery will block OTA's because I'd like my kids N7 to be able to receive those.
Click to expand...
Click to collapse
It won't "block" the OTA from showing up, but it will most likely fail to install when it verifies files. Do you think you'd want your son to just install the update when it comes out, or just that you'd be able to update it?
It can be done, but the OTA usually requires the /system and /recovery partition to be stock. What I've done is use the factory images from Google to reflash the entire system to upgrade it (went from 4.4.4 to 5.0, a few weeks later 5.0 to 5.0.1 and most recently 5.0.1 to 5.0.2). If you edit the "flash_all" batch file before running it to remove the -w flag near the end, it won't wipe any data. Takes about 60 seconds to flash.
After the factory image is done, I just run Chainfire Autoroot (CFAR) again to get root back and I'm on my way. The whole process takes less than 5 minutes with each update.
Note: flashing factory images and running CFAR both require your bootloader to be unlocked. Unlocking will wipe data. If you don't remove the -w flag in the batch file, your data will be wiped when you flash the factory image.
The biggest reason to root IMO is for ad blocking. I use adaway and it's just such a better experiencing browsing etc. Without ads, especially if you use certain sites that do streaming for TV.
Sent from my Nexus 7 using XDA Free mobile app
I just want the option to upgrade to a newer release if I feel like it. Not so much on my kids N7 as much as mine. I upgraded both to 5.0.2 before unlocking and rooting, both went without a hitch. Kind of impressed with Lollipip........hoping they drop it for the G2 someday. Only downside I've really found is lack of Xposed Framework functionality on 5.0.2 which was a bummer.
And yes, AdAway was the FIRST thing I put on the newly rooted N7's. I may try a rom or two on mine, but I'm pretty happy with it as-is after loading up Beautiful Widgets (had this paid for since like 2010) and Apex Launcher. Only thing I'm really exploring is a custom kernel with the knock knock coding baked in since you apparently can't find it as a Standalone.
I have a G2 also along with my Nexus 7. There is a kernel that has KnockOn and off support just like the G2. It is the Elemental kernel. It uses an Aroma installer in recovery to set the options. I didn't get too fancy with it, like the gesture support and all that... I just use Knock On and the status bar to knock off. I think it also allows swiping the status bar for brightness control, which I do use too.
Then I use either Nova or Action Launcher to set double tap > screen off. Works like a champ. I am running Elemental on the stock Lollipop rom.
Hey! So recently I got a Samsung Galaxy J3 and was wondering if it was possible to get Xposed on it? Flashing a Zip is not an option, by the way.
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
krasCGQ said:
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
darknaio said:
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
Click to expand...
Click to collapse
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
krasCGQ said:
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
I would agree with you, as I had TWRP on my last phone and liked it quite a bit. I just don't know which phone's TWRP to try and how to try and flash it on there. Do I do it through Odin? Theres (if I recall correctly) a TWRP for the Samsung Galaxy J2 and J5, on either side of my J3 (Which it's so odd that the newer phone came out with a "series" number in the middle like that). Which would you suggest I do, J2 or J5, or neither?
darknaio said:
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Click to expand...
Click to collapse
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
darknaio said:
am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick
Click to expand...
Click to collapse
I know what you mean. Every time I restart my phone I have to re-root it if I want to do something with it. Luckily I don't really need root on this phone. Mainly because of the lack of things you can do with it. Hoping to see something come out of this though
EqiiKxDude said:
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
Click to expand...
Click to collapse
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
darknaio said:
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
Click to expand...
Click to collapse
Yeah I mainly used Xposed on my previous phone to make it look more like Lollipop but since this phone comes with it I don't need it as much. And I didn't know you were able to unbrick this phone? I would have saved about $40 if I knew that ? well then yeah we should probably try one of them. I think we should go with the newest one though
Thats what I was thinking, but I don't know which J series came out before the J3 this year or I'd try that one. And yep, luckily able to unbrick it thanks to Odin. Actually unbricked it from even worse than a boot loop, I accidentally destroyed my recovery somehow so I couldn't even boot into that and do a factory reset, but thankfully Odin's separate from the recovery so it still worked. End of the day if you can at least get your phone recognized by your computer and can flash something onto it, flashing stock = unbrick (usually).
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Curtis1973 said:
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Click to expand...
Click to collapse
I have the same thing, temp root that's lost when I reboot. I've already had to go the Odin route with the original firmware so I've got my backup covered. I'm also working with the dev behind Super Sume and he thinks he has the issue resolved, if not he's going to teamview with me to try and get past this. If we manage to solve the problem I'll post the results and subsequent steps here. Hopefully this will lead to root sticking through reboot. If so then at minimum may be able to solve -some- of the problems. Though I don't know if this will fix Xposed not working, as it always caused me to boot-loop in the past (only solved by going into TWRP and rebooting from there) and even if root sticks the only way to flash Xposed according to current theories is to do so from custom recovery, which I haven't found one for this device yet.
Have you been able to get a custom recovery on your J3? If so that would be the other key part to solving a lot of these problems. If I get the Super Sume to work and someone else can manage to get a custom recovery working, maybe that'll be the start of this device's support here =D.
No but I believe by repacking an edited firnware you can add xposed that way.
Curtis1973 said:
No but I believe by repacking an edited firnware you can add xposed that way.
Click to expand...
Click to collapse
Unfortunately I wouldn't know the first thing about editing a firmware, much less be able to add Xposed lol. Could that be a way to manually add custom recovery? Or are we still dependent on someone making a version compatible with this phone?
will need a custom recovery built for the device. with proper root you could then use flashify to install it to the device. root opens the door for everything. temp root will never get much except ability to debloat the device.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
i reached out to chainfire in hopes of cf auto root for the j3. but have not heard back. but does not mean i wont. will see. otherwise i will keep on trying what i can.
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
EqiiKxDude said:
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
Click to expand...
Click to collapse
Ive been seeing that too and ignoring/swiping it away. Not sure what it is though.
my system is edited so im not getting update pushes. probably nothing significant.
Curtis1973 said:
my system is edited so im not getting update pushes. probably nothing significant.
Click to expand...
Click to collapse
Your J3 is modified? Temp root, or something else?
Has anyone received Google Assistant on their phones yet? Just curious.
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.
SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it
I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?
It's here! I literally just this minute got Google Assistant!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?
misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.
Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?
Hey guys.
Really sorry for having to post this again :/
Tried posting my issue in this thread but I think that thread's gone cold.
----
I have a Moto G5 Plus US, Model XT1687
Current ROM Info:
Software channel: retus
Build #: NPN 25.137-33
Security patch: Jan, 1 2017
Baseband: M8953_02.03.07.06R POTTER_NA_CUST
On a whim, unlocked the bootloader. Now id like to lock it back.
I haven't updated my phone / installed any OTA's, phone keeps asking to update to NPNS25.137-33-5, haven't done it.
Does this procedure work for me?
Which ROM should I use?
Id like to relock the bootloader and receive OTA updates as normal on my US variant phone!
Many thanks!
I'm pretty sure Motorola hasn't released stock firmware for the retus version.
Cats_PJs said:
I'm pretty sure Motorola hasn't released stock firmware for the retus version.
Click to expand...
Click to collapse
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..
seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).
Cats_PJs said:
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..
Click to expand...
Click to collapse
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
acejavelin said:
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).
Click to expand...
Click to collapse
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!
seed_87 said:
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!
Click to expand...
Click to collapse
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly
Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.
Cats_PJs said:
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly
Click to expand...
Click to collapse
Oh, wow, I had the (wrong) idea that the SuperSU method was the better one and superseeded magisk. If that works great then awesome I will root using magisk, thanks @Cats_PJs !
easyrider77 said:
Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.
Click to expand...
Click to collapse
Awesome explanation @easyrider77 I will definitely try to root using magisk. Thanks for the warning, don't play Pokemon go and haven't used Snapchat in years so i'm good! I'll try flashing the latest Magisk (v14.0)
One thing tho:
I think I want to (for now anyways) stay stock-ish (stock rom + stock kernel + twrp + magisk).
If I understand it correctly, flashing a custom recovery renders the phone unable to get OTA's (Not that I'd want to apply an OTA update on a modified rooted phone and risk a brick anyways) So, how would one eventually update Android? (Keeping in mind that Motorola hasn't released any retus firmware) Can I flash other non-retus firmwares? (Which wouldn't flash over twrp I think, I would then just loose root and have to flash magisk again, right?)
Thanks a ton guys :good::good::good:
EDIT:
Short xda search pointed me to this official TWRP link, will follow fastboot method to install TWRP.
I'm not sure what exactly stops ota from coming in. I've heard unlocking the bootloader is what causes it, and I've also heard that flashing a custom recovery is what causes it, and I've also heard a custom rom is what does it.
There are options as far as ota goes though, and work the same way, but you'd jsut have to wait. People release flashable ota files all the time, and can be flashed via twrp.
If you want to keep stock, and root that's fine too, but I personally wouldn't worry much about the ota issue at all, because eventually every phone will not get ota as it will lose support, but you can still get the latest and greatest up to date rom with it's features.
Prime examples would be:
Oneplus One,
Oneplus 3
some of the samsung devices like s4
These are just a few, and although they don't receive support officially, they are sporting the brand new android 8 oreo.
Even the samsung s4 has N for it and it came out in 2013 (that's near 5 yrs ago now) and started on Android 4.2.2 (Jelly Bean) and said it was upgradable to 5.0.1 (Lollipop), and now here we are running android 7.1.x.
https://forum.xda-developers.com/galaxy-s4-tmobile/development
(not sure if there were any unlocked variants of that phone at the time as it wasn't a common thing like it is now, that's why I chose the tmobile thread but there are other variants that get it as well)
So when it comes to ota, I personally would not an do not worry about that when I root, that's the last of my worries.
I prefer functionality and customization over ota myself, because most times someone comes out with either an official link to an ota or makes an flashable ota you can flash via twrp, although my semi-educated guess would be if you decide to install the official/stock ota, then it will erase everything you have anyways which can be a pain.
DO keep in mind once you unlock the bootloader, it "officially" voids any warranty and moto does have the option to refuse service if anything goes wrong with the phone, but I have heard some people had no issues and moto took the phone back even when rooted, but that is something you would have to make a choice and live with IF you decided to unlock the bootloader, as there is no way to undo that process.
I have re-locked the bootloader on a moto phone so yes it CAN be re-locked, but........it still gets triggered and moto will know that it's been unlocked even if you re-lock it, because that part is irreversible and cannot be undone, aside from you locking and unlocking it on your side.
As for flashing firmware and all that, make DOUBLY sure you know your phones model number and/or codename, this is key in flashing most anything you do with your phone, because even though a phone may have multiple variants, ie: tmobile, sprint, at&t versions, and even European versions, and the phones are identical in EVERY way hardware wise, you can't just simply pick a rom of choice and use it, it's a matter of knowing what your phones info is.
Example: you cannot take a t-mobile phone rom and flash it's official firmware or it's roms, and updates on a at&t variant, or a metroPCS on a tmobile variant, even though they use the same network, and are the exact same phone and hardware, there are subtle differences and can most likely brick the phone, either hard or soft.
So if I had the US variant of the g5 plus that would be codenamed the same "potter" like the rest, but, the number is different which is XT1687, so I would use that number as my reference, as apposed to the potter name, because there are 3 other variants of that phone which are Amazon Edition and the consumer cellular and of corse the European variants as well, I'm not exactly sure what numbers go with what phones other than the US unlocked variant, but on a quick look the other numbers are XT1684 and XT1685, perhaps someone else with more experience than I have can tell you what those number match up with said phone.
As far as the US variant goes though, I do not want to take a rom or firmware meant for the XT1684 XT1685 and use it on the XT1687 US variant, as it will most likely have bad results, ie: brick of some sort.
That's the main thing you have to worry about, other than that, there isn't much worry. Just do some major research and goggling and read and re-read and read again the directions on the threads at xda as most generally all of them are pretty simple to follow, if you do it step by step.
I recently bought an lg k20 plus phone from metroPCS, have never rooted that phone before and came to xda and followed the rooting thread and rooted it the first time. In a matter of 30 mins I had full root with stock rom (since there are no roms for that phone as of yet) but it is a metroPCS variant, (mp260) and in the case above, this phone is also sold by tmobile, is the exact same phones specs hardware, etc....I could not use the tmobile rom or firmware on this phone.
Hope this helps clear it up some.
Update:
I just bought a 64gb storage/4gb ram US variant of the g5 plus. It brought back some older memories of when I had my other moto, X I think it was, not sure anymore, but I DO remember you can unlock the bootloader as well as re-lock it, but, do keep in mind it still triggers something internally that can't be reveresed, so if moto did decide to check into things, they can tell if it's been bootloader unlocked.
So while you can unlock and lock the bootloader on our side, moto can still tell it's been unlocked, even when re-locked. Just hope if you send it back in they just don't check it and even if they do, hope they don't bother sending it back saying your warranty is void sorry.
Thanks @easyrider77
I used to install custom ROMs on my older phones. Recently though, stock android has gotten pretty good so maybe when this phone loses support I'll try some ROMs. Out of curiosity, what ROM/hacks/kernel do you use?
So, how does this sound:
- Install the OTA my phone's been prompting me to update to (upgrading from NPN25.137-33 to NPNS25.137-33-5 and I think it will then try to update to NPN25.137-83 with an August 1 security patch)
- Install TWRP via fastboot, make a nandroid backup!
- Root with Magisk v14.0
- Looking into maybe changing the boot.img "Your device is not trustworthy" thing
- Adaway! Xposed! Other goodies yay!
- Any other recommendations?
PS: Can Magisk root every firmware released by Motorola for the Moto G5+?
I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.
easyrider77 said:
I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.
Click to expand...
Click to collapse
WIll do, many thanks for all your help guys!
@easyrider77 @Cats_PJs @acejavelin
:good::good::good:
Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck
Cats_PJs said:
Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck
Click to expand...
Click to collapse
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.
easyrider77 said:
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.
Click to expand...
Click to collapse
I really don't have a problem with the sound volume, except when I plug it into my truck. If there's a good song on, and I really want to crank it up, I run out of volume, so I usually turn up the headphone gain in the kernel settings by 3.
I haven't noticed variance between ROM volumes on this phone, but I know on my old note 3 there was definitely fairly large variance between ROMs.