Root Checker - RCTD? - LG V40 Guides, News, & Discussion

Anyone know if the v40 runs root checker? Is this something we need to disable after rooting?

Yes, I forget what it's called, but it is somehow disabled so that the phone fully boots up. Part of the rooting service, I suspect.
Sent from my LM-V405 using Tapatalk

Einsteindks said:
Yes, I forget what it's called, but it is somehow disabled so that the phone fully boots up. Part of the rooting service, I suspect.
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Found it - Here it is in case anyone roots their phone and needs to disable the lg root checker
https://forum.xda-developers.com/showpost.php?p=79842731&postcount=2

It is odd that I just happened to stumble into this while searching for information about the real-time-clock (rtc) on my V40. Until now, despite a fair bit of reading in these device forums I had not noticed or heard about this. Thanks! Is there some way to make this sticky or to stand out more to those like me? If so, that would be great.

Related

Disable vibration when unlocking through active notifications?

Does anyone know of a fix or app that will disable vibration (and haptic feedback universally across the phone) when unlocking through active notifications?
I love the moto x, but the way it vibrates all the time really annoys me. Friggin hate how OEMs force that into the ROMs. Thanks for any help. You all rule.
2d
Anyone have an idea?
2d
There is no way to remove the vibration from active notification
Sent from my XT1058 using xda app-developers app
I had the phone when it first came out and the vibration used to drive me crazy. I will say I picked it up the other day and with the KITKAT update the vibration is now barely noticeable.
It really drives me nuts too. I loathe haptic response. It just makes a slick phone feel stupid.
I'm thinking there has to be some kind of app that will override system wide haptic control. I just am unaware of it. Does anyone know of an app like that? I am rooted.
2d
I'm thinking more like modifying the apk to disable this. Haven't looked at it yet.
Sent from my XT1060 using Tapatalk
jmill75 said:
I'm thinking more like modifying the apk to disable this. Haven't looked at it yet.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
The problem for me is that it's a Republic Wireless Moto X and I don't believe the build for it has been released or is even in the wild. If it was, getting an altered version would be my top priority.
Coming from a rooted, unlocked, CM 10.2 running LG Optimus G, having something that can't be disabled is REALLY annoying.
Thanks for the comments. If anyone knows of an app or anything else related to this, I'd be super appreciative.
2d
2disbetter said:
The problem for me is that it's a Republic Wireless Moto X and I don't believe the build for it has been released or is even in the wild. If it was, getting an altered version would be my top priority.
Coming from a rooted, unlocked, CM 10.2 running LG Optimus G, having something that can't be disabled is REALLY annoying.
Thanks for the comments. If anyone knows of an app or anything else related to this, I'd be super appreciative.
2d
Click to expand...
Click to collapse
I hear ya....I have the RW one too. I've never had an un-rooted Android device before. Took me a while to figure out why there were ads on stuff! I never saw them before. LOL Hopefully we'll get a safe, easy, reversible root soon, and I get get ad-blocking and Titanium Backup back!
jumphour said:
I hear ya....I have the RW one too. I've never had an un-rooted Android device before. Took me a while to figure out why there were ads on stuff! I never saw them before. LOL Hopefully we'll get a safe, easy, reversible root soon, and I get get ad-blocking and Titanium Backup back!
Click to expand...
Click to collapse
Root exist. JCase's works just fine, and exactly as described. While I haven't checked I'm pretty sure the same reverse unroot process works on it as well. Haven't checked though.
Hopefully Motorola fixes it themselves, but a nice custom stock rom would be really nice as well. Just needs to be RW specific as they have their wifi portion hard written into the system.
2d
2disbetter said:
Root exist. JCase's works just fine, and exactly as described. While I haven't checked I'm pretty sure the same reverse unroot process works on it as well. Haven't checked though.
Hopefully Motorola fixes it themselves, but a nice custom stock rom would be really nice as well. Just needs to be RW specific as they have their wifi portion hard written into the system.
2d
Click to expand...
Click to collapse
I've only had the phone for 2 days, and I'm not quite brave enough to try it yet! I will eventually, once I read that more people have done it, I guess.

Root Tips

Sup guys I have a moto x on sprint and I'm on 4.4.2. I'm not sure if I want to root. I just heard some people getting great battery life and I'm not its just average. Maybe 3 hours screen on with 12 hours total before dead. So I think its some apps giving me wakelocks but I need root to find out now. Also app ops and/or greenify I'm sure will help. Now otherwise the phone is perfect. I'm no noob to root so I know what it is.
What I want to know is what's the easiest way to unlock boot loader, root install recovery and probably do xposed?
Then is there a way to totally revert back to stock with locked boot loader for warranty claims?
Thanks guys
Sent from my XT1056 using Tapatalk
Use this guide to root
http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
You can flash stock firmware again but you cant relock your bootloader.
DaRkRhiNe said:
Use this guide to root
http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
You can flash stock firmware again but you cant relock your bootloader.
Click to expand...
Click to collapse
Cool thanks. So root will cause void of warranty. I have the Motorola esp insurance. Do you think it also voids that? As a cracked screen has nothing to do with root.
Sent from my XT1056 using Tapatalk
Your battery times may be completely normal.....depending on what features you leave on, apps you've installed that access those features.....screen brightness, games, how much you make/get calls, signal strength....etc...etc.
My point is, those times you get aren't necessarily cause of an issue.....could be anything above too. Root won't help on its own.....its setup and usage that determine average battery times.
r.storm85 said:
Cool thanks. So root will cause void of warranty. I have the Motorola esp insurance. Do you think it also voids that? As a cracked screen has nothing to do with root.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Ya I agree. I'm not sure on root yet still checking app settings. Thing is all the apps on my phone are there for a reason. Don't play games and it seems all my settings are good. Im just getting awake time when my screen is off so something is happening and I can't figure it out. Is there anything without root I can use to determine the wake lock?
Sent from my XT1056 using Tapatalk
r.storm85 said:
Ya I agree. I'm not sure on root yet still checking app settings. Thing is all the apps on my phone are there for a reason. Don't play games and it seems all my settings are good. Im just getting awake time when my screen is off so something is happening and I can't figure it out. Is there anything without root I can use to determine the wake lock?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
You pretty much need root to see that stuff....on kit kat anyway.
kj2112 said:
You pretty much need root to see that stuff....on kit kat anyway.
Click to expand...
Click to collapse
Ya that's what I've seen. I really don't want root if I could get another 3-4 hrs of total and another hour of screen on time. And I know it all depends on usage but it seems that isn't too much to ask from this phone when its running right
Sent from my XT1056 using Tapatalk
Look at all the apps you have.
Uninstall any that haven't been updated this year.
???
Profit.
Basically with the restructure of kit kat apps that haven't been updated for it are causing unnecessary wakelocks, basically not closing properly.
SymbioticGenius said:
Look at all the apps you have.
Uninstall any that haven't been updated this year.
???
Profit.
Basically with the restructure of kit kat apps that haven't been updated for it are causing unnecessary wakelocks, basically not closing properly.
Click to expand...
Click to collapse
I'll take a look. Weird is I just switched to art to see how it does and my android is usage went from 20% down to 10%. And its a lot better now. Maybe art really helps on 4.2.2?
Sent from my XT1056 using Tapatalk

Get rid of custom lock pad on reboot

This is what I use to get rid of the custom lock pad sign from the bootloader when you reboot. Some people got it after they rooted and disabled some apps like me. It's in wanam xposed. Below is a pic to show where it is. It works very well. It takes a couple reboots after you enable it for it to take effect. But after that I have not seen it come back at all. Just wanted to share my findings with others. Hopefully it helps others who may have been looking for the same solution.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
First thing i did.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Greycloak42 said:
First thing i did.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
It's good to know, but a flash of the SM-G900A firmware from here on XDA, minus the BL bootloader file, gets rid of that anyway. It's not that big of a deal whether it's there or not, unless you're taking the phone in for warranty service.
shortydoggg said:
It's good to know, but a flash of the SM-G900A firmware from here on XDA, minus the BL bootloader file, gets rid of that anyway. It's not that big of a deal whether it's there or not, unless you're taking the phone in for warranty service.
Click to expand...
Click to collapse
No one said it was a big deal or not. It's sharing of information that is what xda is all about. And since there is no other post in our forum about it, this is why I shared. Has nothing to do with what way is better or being a big deal.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
freebee269 said:
No one said it was a big deal or not. It's sharing of information that is what xda is all about. And since there is no other post in our forum about it, this is why I shared. Has nothing to do with what way is better or being a big deal.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I did this and rebooted mine 5 times.. Never went away. Xposed is working fine because i also added screen shot to menu and the reboot options. but cant get rid of the security lock back to normal.
All i did was that i download the latest supersu from chainfire updated su binary reboot and got that lockpad away
Sent from my SAMSUNG-SM-G900A using Tapatalk
That worked thanks!
So how did you get rid of it exactly?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Install the supersu.apk located in the file i just uploaded and update su binary reboot 3 times and it should have remove the padlock
It's not giving me option to update binary
Sent from my SAMSUNG-SM-G900A using Tapatalk
It's always the same thing every time a new Samsung phone comes out. Maybe I can save some people some time and tell you each phone can and will show the custom lock icon at different times no matter what you do. In other words, if you do something that stops it from showing on your phone, there is absolutely NO guarantee that the same method will stop it from showing on someone else's phone. The scan that selects if the custom status or unlock icon is shown or not occurs on each individual phone at the time of boot. Therefore, depending on the current state of each phone, it might show or not show. The only real way to stop it from showing is through a mod (located in the AT&T S4 section) that actually modifies system files. X-posed modules just cover the icon, so the appearance is just graphical. It works for most (though it isn't truly changing anything), but for some it still doesn't. AGAIN. JUST BECAUSE SOMETHING WORKS ON YOUR PHONE,DOES NOT MEAN IT WILL WORK ON OTHERS...it just might.
glad it worked
viperbe said:
That worked thanks!
Click to expand...
Click to collapse
glad it worked for you.
freebee269 said:
well that's just common sense. and nowhere did i say this will work on everyones phone. i just pointed out an option that worked for me. i shared info that worked for me in hopes it helped someone else out. this is what this community is about right? and i see it worked for someone else also. the best thing you can do is to not reply to this topic if you have nothing to bring to it. and that paragraph you typed brought nothing to this topic but complaining.
Click to expand...
Click to collapse
This forum isn't just about you. Posts like yours FAIL to mention that it might not work for everyone trying it so people that it doesn't work for are left wondering what they did wrong. When in fact, they have done nothing wrong. Mentioning what works for you is great, but stop getting so offensive when someone adds more information or states that your solution might not work for everyone. You should be welcoming the addition of useful information instead of acting like "nothing was brought to YOUR thread" because you didn't know about it or mention it. A little research about X-posed and SysScope should be done by anyone wanting to permanently get rid of the custom lock icon.
Not only did I mention that X-posed might not work for some, but I also mentioned a permanent modification to get rid of the custom icon instead of just covering it up with X-posed modules. Now how exactly did my paragraph have nothing to do with this topic?
scott14719 said:
This forum isn't just about you. Posts like yours FAIL to mention that it might not work for everyone trying it so people that it doesn't work for are left wondering what they did wrong. When in fact, they have done nothing wrong. Mentioning what works for you is great, but stop getting so offensive when someone adds more information or states that your solution might not work for everyone. You should be welcoming the addition of useful information instead of acting like "nothing was brought to YOUR thread" because you didn't know about it or mention it. A little research about X-posed and SysScope should be done by anyone wanting to permanently get rid of the custom lock icon.
Not only did I mention that X-posed might not work for some, but I also mentioned a permanent modification to get rid of the custom icon instead of just covering it up with X-posed modules. Now how exactly did my paragraph have nothing to do with this topic?
Click to expand...
Click to collapse
you win man. i'm not on xda to pump my chest and try to sound better than others. i'll leave that to you. i only shared what i found that worked. as i said you could have just moved on instead of starting an argument. but i'm not going to continue to give you attention with this. so anything you have to say from here on out i wont be able to see. have a good night.
Thread is closed at the request of the OP.
XDA appreciates all who share knowledge of things that work, and things that only work for some. With all the different devices and multitudes of "add-ons", what works for some people, might not work for others.
Cheers
MD

Is the reason people can't find a stable root for US LG G4's cause of an unknown boot

Just browsing on signal strength app and saw that a boot loader was unknown and wondered if it was keeping blocking root stability?
Sent from my LG-H811 using Tapatalk
UktenaWarrior28 said:
Just browsing on signal strength app and saw that a boot loader was unknown and wondered if it was keeping blocking root stability?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
It probably shows that because it is a brand new phone and the app doesn't have the bootloader in it's database. just a guess
root has already been achieved in multiple ways, on all carrier devices. We are just waiting on the devs to release now.
Thank you for the reply. I was kinda curious about why mine shower no boot loader.
Sent from my LG-H811 using Tapatalk
Has anyone heard any news? I keep looking and have found nothing new.
DattKiddKFC said:
Has anyone heard any news? I keep looking and have found nothing new.
Click to expand...
Click to collapse
I don't understand why they don't release the root method with an "at your own risk" disclaimer. A good number of us root users cut our teeth on the original HTC Dream and understand the involved risks.
Sent from my toaster
blackknightavalon said:
I don't understand why they don't release the root method with an "at your own risk" disclaimer. A good number of us root users cut our teeth on the original HTC Dream and understand the involved risks.
Sent from my toaster
Click to expand...
Click to collapse
I'm pretty sure the devs want to release the dummy-friendly version, like myself, who knows nothing about root but would like to try it.
xfearlz said:
I'm pretty sure the devs want to release the dummy-friendly version, like myself, who knows nothing about root but would like to try it.
Click to expand...
Click to collapse
I'll take the step-by-step version where you have to read the instructions at least twice before going through with it. It'll remind me of the old days.
Sent from my toaster
Tomyk89 said:
It probably shows that because it is a brand new phone and the app doesn't have the bootloader in it's database. just a guess
root has already been achieved in multiple ways, on all carrier devices. We are just waiting on the devs to release now.
Click to expand...
Click to collapse
From the research I've done, I've yet to see any proof that devs have achieved root on all carriers. Where did you find this information?
I have yet to see it done on a T-Mobile, Verizon and Sprint variation. I have seen it done on a AT&T phone. I am patient enough for the root
Sent from my LG-H811 using Tapatalk
thenewbigmack said:
From the research I've done, I've yet to see any proof that devs have achieved root on all carriers. Where did you find this information?
Click to expand...
Click to collapse
I agree. I'd love to see someone that has achieved root comment.
blackknightavalon said:
I don't understand why they don't release the root method with an "at your own risk" disclaimer. A good number of us root users cut our teeth on the original HTC Dream and understand the involved risks.
Sent from my toaster
Click to expand...
Click to collapse
They do not have it.
Sent from my SM-G920T
ambervals6 said:
They do not have it.
Sent from my SM-G920T
Click to expand...
Click to collapse
Agreed. If root were available, even if the devs didn't feel it was ready for prime-time, we'd know about it. The fact that nobody has actually seen a rooted 811, pretty much proves that root has not been achieved.
There is a root method that does work. Its not prime ready. But there are articles ststimg root was achieved on an U.S. variant G4. As I stated before the dev bricked the first phone from the unstable root. After his second attempt he was sucessful. So how can justify there is no root for G4 stable or unstable?
Sent from my LG-H811 using Tapatalk
UktenaWarrior28 said:
There is a root method that does work. Its not prime ready. But there are articles ststimg root was achieved on an U.S. variant G4. As I stated before the dev bricked the first phone from the unstable root. After his second attempt he was sucessful. So how can justify there is no root for G4 stable or unstable?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Not sure if this was directed at me or not, however.... There is clearly root for a "U.S. variant G4". There is clearly no root for the H811/T-Mobile variant. Nobody has claimed to see it either (that I am aware of).
ShermCraig said:
Not sure if this was directed at me or not, however.... There is clearly root for a "U.S. variant G4". There is clearly no root for the H811/T-Mobile variant. Nobody has claimed to see it either (that I am aware of).
Click to expand...
Click to collapse
just because you haven't experienced it, doesn't mean it doesn't exist. Look at the female orgasm for example. Just believe.
The only thing I can see why one carrier may take longer is only the fact that carrier has just added something in a file that made it harder to exploit. But it has never really been that way.
Sent from my LG-H811 using Tapatalk
UktenaWarrior28 said:
There is a root method that does work. Its not prime ready. But there are articles ststimg root was achieved on an U.S. variant G4. As I stated before the dev bricked the first phone from the unstable root. After his second attempt he was sucessful. So how can justify there is no root for G4 stable or unstable?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
As I've said, devs should release it with an "at your own risk" disclaimer.
Sent from my toaster
blackknightavalon said:
As I've said, devs should release it with an "at your own risk" disclaimer.
Sent from my toaster
Click to expand...
Click to collapse
I was agreeing with you and telling the others that there is one
Sent from my LG-H811 using Tapatalk
Root achieved. Go get it. Already rooted and install TWRP on mines. http://forum.xda-developers.com/g4/...-tmo-vzw-intl-variants-soon-root-lg-t3164765/

Greenify behaving wonky on this handset...

Got my phone delivered yesterday. So far very impressed. No issues, except for one app issue. Greenify behaves wonky on this handset. When I go in to hibernate apps, it seems to stall during the hibernation process. It *looks* like instead of force stopping the app, it does something with moving the app to SD card. I say that because I can "see" it pressing the move to sd button, instead of the force stop button. It's weird. Anyone else notice this?
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
ItGuyJax8430 said:
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
Click to expand...
Click to collapse
No. Never figured it out. I also posted on the Slickdeals thread and someone there confirmed the same thing. I just uninstalled it until someone finds a workaround. Honestly though, I'm not super worried about it. I'm getting between 5-6 hours of SOT without it.
ItGuyJax8430 said:
Did you ever figure this out, I didn't notice any issues with it. I just rooted mine today and plan on using the Greenify rooted. I'll let you know if I see a difference.
Click to expand...
Click to collapse
Can you give me the idea to root your phone? Is it Unlock bootloader, then twrp/cwm, then root?
Thanks
quyvinh said:
Can you give me the idea to root your phone? Is it Unlock bootloader, then twrp/cwm, then root?
Thanks
Click to expand...
Click to collapse
Check out the guides tab, it has a great guide in getting rooted and unlocked.
Sent from my VIVO XL using Tapatalk

Categories

Resources