Whenever I switch my phone on, I get a message in a white box that says something about making sure the battery cover is firmly in place.
....And....
Whenever I unplug my charger, a similar box mentioning the charger port cover appears......
Let's face it, this advice ain't rocket science is it, and to be honest, they are annoying.........
Is there any way of getting rid of them?
I am rooted, so if I have to modify some text in build prop or something similar I can........
Thanks in advance......Keith...
Sent from my rooted Kn0x0 SM-G900F S5
I believe theres something you can edit to remove them, i forget what it is but you can google. There are also a number of xposed modules that do this as well.
Sent from my SM-G900A using Tapatalk
Rakuu said:
I believe theres something you can edit to remove them, i forget what it is but you can google. There are also a number of xposed modules that do this as well.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Lol.....xposed sounds the better option as I already use rootcloak for some rather "sensitive" apps.....cheers fella......
BTW do you know what the modules are called?
Sent from my rooted Kn0x0 SM-G900F S5
Wanam, theres one on the play store called xposed g-touchwiz.
Sent from my SM-G900A using Tapatalk
Cheers fella.....works perfectly......
Sent from my rooted Kn0x0 SM-G900F S5
Having trouble getting rid of these popups on rooted stock lollipop.
Solutions like the the popupdisablerzip don't seem to work anymore and the the xopsed framework won't work either (yet).
Any more ideas, short of a custom rom?
yonster said:
Having trouble getting rid of these popups on rooted stock lollipop.
Solutions like the the popupdisablerzip don't seem to work anymore and the the xopsed framework won't work either (yet).
Any more ideas, short of a custom rom?
Click to expand...
Click to collapse
I wouldnt take any of this as fact since i dont have lollipop, but i'd think they havent found the files yet. It's safe to assume the zip or the options in the module just edit the file that makes them appear, not just supress them some how. So you'll most likely have to wait, shouldn't take long though.
Sent from my SM-G900A using Tapatalk
Related
So, I have a Galaxy S5, obviously, it's through Verizon and is running 5.0 and it's a G900v, i've poked and proded around looking for ways to root, i've come up with Towelroot, but it doesn't support my device, and i've been told CF Auto Root, when I looked into that apparently my device, G900v, isn't supported with that either, so it is possible at all to root this at this point in time. I also apologize if I overlooked another thread asking this or for a way to do this but I did search around and those are the only 2 options I kept getting.
I believe you may be able to downgrade, towelroot, and flashfire up to lollipop, you might be stuck on lollipop though, check the verizon s5 section theres some threads there for it.
Sent from my twi5ted SM-G900A using Tapatalk
Rakuu said:
I believe you may be able to downgrade, towelroot, and flashfire up to lollipop, you might be stuck on lollipop though, check the verizon s5 section theres some threads there for it.
Sent from my twi5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yeah I figured there's no way without downgrading to 4.4.4. I may do that, i'll need to look around on how to do that.
Exmix said:
Yeah I figured there's no way without downgrading to 4.4.4. I may do that, i'll need to look around on how to do that.
Click to expand...
Click to collapse
This might be a good place to start http://forum.xda-developers.com/showthread.php?t=3068546
Sent from my twi5ted SM-G900A using Tapatalk
Rakuu said:
This might be a good place to start http://forum.xda-developers.com/showthread.php?t=3068546
Sent from my twi5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
Awesome, thanks, I'll give it a shot and post back when I get to it tonight probably.
Rakuu said:
This might be a good place to start http://forum.xda-developers.com/showthread.php?t=3068546
Sent from my twi5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
The only issue with this is, my phone hasn't been rooted at all. So I can't use this one either. =\
Exmix said:
The only issue with this is, my phone hasn't been rooted at all. So I can't use this one either. =\
Click to expand...
Click to collapse
Well you can sniff around in that sections, ots specific to g900v so you have an exponentially higher chance of finding your answer there.
Sent from my SM-G900A using Tapatalk
Welp I did it! Got it rooted by downgrading to 4.4.4, flashing to NCG, Rooting with Towelroot, then Flasking to NK2. SO now just to find the right ROM to get back to Lollipop.
Incase you guys wanted to do it as well.
http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
Is the link I followed. I in no way take credit, just sharing how I myself achieved ROOT.
Application thread http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Install version 71 for arm64 devices and remmeber to backup just in case it doesn't go smoothly for you
Edit: Some are reporting that it only works for t-mobile and international models
I can confirm v71 is not bootlooping on my H811 and it is working!!!
Woo! Thanks for the heads up. Now using gravity box to Center my clock and hide my alarm icon lol
Sent from my LG-H811 using XDA Free mobile app
Working for me on the H811 as well. Finally!
Sent from my LG-H811 using Tapatalk
Now if only we could get a locked BL installable version that would really make a bunch of ppl's days.
Wooooooooooooooot youtube adblock here I come.
djkinetic said:
Now if only we could get a locked BL installable version that would really make a bunch of ppl's days.
Click to expand...
Click to collapse
Ye so only h815 and tmobile can use xposed. Lucky i have 815 works flawless.
Activadee said:
Ye so only h815 and tmobile can use xposed. Lucky i have 815 works flawless.
Click to expand...
Click to collapse
Yea most likely Locked BL users will need Safestrap recovery or Flashfire.
snowlin said:
Woo! Thanks for the heads up. Now using gravity box to Center my clock and hide my alarm icon lol
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
I installed gravitybox, but it doesn't open.
failax said:
I installed gravitybox, but it doesn't open.
Click to expand...
Click to collapse
On my lg , gravitybox started after reboot.
Thank you so much for letting us know! I am now running on my h811 amplify and deeper greenify module as well
Anyone know if this works on the VS986 (Verizon) model?
Sent from my VS986 using Tapatalk
chubbrock said:
Anyone know if this works on the VS986 (Verizon) model?
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
It’ll work. The tricky thing is getting it installed without a custom recovery.
chubbrock said:
Anyone know if this works on the VS986 (Verizon) model?
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Read the OP
Sent from my G4 using your mom
Dennisg34 said:
Read the OP
Sent from my G4 using your mom
Click to expand...
Click to collapse
I did. Says for arm64 and some are reporting it works on tmobile and international versions but nothing confirmed so... That's why I asked
Sent from my VS986 using Tapatalk
shoes22 said:
It’ll work. The tricky thing is getting it installed without a custom recovery.
Click to expand...
Click to collapse
I was able to get all the files into the proper dir but I'm not sure if I set the permissions correctly on a couple of the files, at any rate it resulted in the phone hanging on boot animation. 810 variant.
You need to install xposed through twrp, which is currently only available for select H815's and H811's. There is a theory similar to the way most people achieved root to get xposed, where you get a system image with xposed installed already and flash it, but I can't really comment on its validity.
I'd only be concerned if an xposed module causes some sort of bootloop and you can't do much other than flash a system img which means you lose a lot of data. No working recovery is risky
Sent from my LG-H815 using Tapatalk
AhsanU said:
You need to install xposed through twrp, which is currently only available for select H815's and H811's. There is a theory similar to the way most people achieved root to get xposed, where you get a system image with xposed installed already and flash it, but I can't really comment on its validity.
I'd only be concerned if an xposed module causes some sort of bootloop and you can't do much other than flash a system img which means you lose a lot of data. No working recovery is risky
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
The permissions still need to be set properly with a slipstreamed system image i believe, hopefully someone with more experience tries it out.
Is there a way i can install xposed mannually with a locked bootloader? I have the h815 model and i cant unlock the bootloader.
Worked on my H811.
Best modules list???
Sent From My LG G4
I'm rooted,running xposed.tried turbo charger for first time today... It's definitely not working. Phone charging VERY slow... Is there an option or setting somewhere I may have disabled?
Sent from my XT1575 using Tapatalk 2
I had the same problem. I rooted. Installed xposed was running just some mods and the phone would only charge in usb mode. Slow as hell. Even with the provided quickcharge plug. I tried going back to stock. I had to RMA mine for a new one. There must have been something that got changed by xposed and the mods I ran . I could not figure out what happened and am not sure about rerooting and installing xposed again.
Sent from my XT1575 using Tapatalk
Seriously? Sound's horrible... I'm in the process of tinkering with exposed.I really hope that's not the issue
Sent from my XT1575 using Tapatalk 2
Xposed working fine with quick charge. Did you try with the included stock charging?
I had xposed and quick charging worked for me. But I only has the drm and greenify module installed
Sent from my XT1575 using Tapatalk
Hmm. OK, I'm going to disable amplify and stock USB debugging and see...
Really wishing I would have tested before rooting
Sent from my XT1575 using Tapatalk 2
I had amplify,ifont,and some others that were suggested here. Like I said, I can't pinpoint it to xposed because even going back to stock and back to a backup before xposed did not help.
Sent from my XT1575 using Tapatalk
Hasherx1 said:
I had amplify,ifont,and some others that were suggested here. Like I said, I can't pinpoint it to xposed because even going back to stock and back to a backup before xposed did not help.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Try disabling iFont.
I got a replacement from Amazon for the same problem. Turned out that my original charger was the issue.
Stryder5 said:
Xposed working fine with quick charge. Did you try with the included stock charging?
Click to expand...
Click to collapse
Could you please tell me what modules are you using . i am planing to install xposed. I don't want to loose my turbo charging.
Thanks
its charger issue replace it
gulshanstrider said:
Could you please tell me what modules are you using . i am planing to install xposed. I don't want to loose my turbo charging.
Click to expand...
Click to collapse
No, Xposed won't cause you to lose your turbo charging. There is already a thread about which Xposed modules are compatible with Android 5.1. Just follow that thread. If you have any problems with turbo charging, check to see if your original stock charger works.
FYI,I fixed mine by toggling USB debugging. Also enabled mock locations... Not sure which of those did the trick, but its working
Sent from my XT1575 using Tapatalk 2
Stryder5 said:
No, Xposed won't cause you to lose your turbo charging. There is already a thread about which Xposed modules are compatible with Android 5.1. Just follow that thread. If you have any problems with turbo charging, check to see if your original stock charger works.
Click to expand...
Click to collapse
anyway you can please link to that thread?
eyecon82 said:
anyway you can please link to that thread?
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/xposed/modules/discussion-xposed-modules-5-1-lolipop-t3075257
it is really annoying
Noob_Boob said:
it is really annoying
Click to expand...
Click to collapse
Only on rooted models. Xposed nosafevolunewarning or gravitybox for example, or whole custom rom with fix.
S7E powered by Echoe™ v5
We need a better answer than this. Rooting isnt an option for everyone, and from what ive seen, might not be possible with this phone without causing major issues.
What do you mean "We need a better answer"?!?
This is the only way to disable the warning, you have to root!!! If you cannot or do not want to root then you have to live with the warning!
+1 rooting + something like xposed (for instance) is the only way.
I have xposed installed and nosafevolumewarning doesn't work for me...
DareDevil01 said:
I have xposed installed and nosafevolumewarning doesn't work for me...
Click to expand...
Click to collapse
Xtouchwiz or gravity box app in xposed.
Sent from my SM-G935F using Tapatalk
Good day all,
I noticed several cluttered threads in Q&A that are becoming more of a discussion than question and answer format.
I wanted to make this thread as a one stop shop for all things Root and Bootloader related for the G-930T (Tmobile Galaxy Note 7).
Please discuss root, bootloader and work with each other in here.
Please do not discuss the bounty in here, and do not clutter the bounty thread with casual conversation about root.
Cheers,
Baja
Sent from my SM-N930T using XDA-Developers mobile app
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
SBERG117 said:
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
Click to expand...
Click to collapse
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
dirtymindedx said:
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
jason504 said:
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
he said Samsung pay...two separate paying system
Chord_Hugo87 said:
he said Samsung pay...two separate paying system
Click to expand...
Click to collapse
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
not possible if you trip knox and in order to get root you need to trip knox.
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
One of them is from Google and doesn't care about Knoxx and the other is from Samsung and does care about Knoxx. Two completely different things. The Samsung Pay not working after Knoxx is tripped has been going on for a year as of tomorrow. The systemless root that doesn't trip Knoxx is one thing but as soon as you start flashing, kiss Samsung Pay goodbye.
Yep, and worst of all. Once it's tripped, Samsung pay will never work again on that device
Sent from my SM-N930T using XDA-Developers mobile app
Luckily for me, if root becomes available its a no-brainer. Samsung pay doesn't support my bank, and I won't have a credit card. Even if Samsung Pay would work for me, it would still be an easy choice to have root instead. I would like to play around with altering the speaker volume, deleting bloatware, making tweaks, ad blocking, etc.
Did anyone ever get the files that Beans asked for over to him?
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Rx8Driver said:
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
In order for you to flash anything to any bootloader, it needs to be unlocked. With it locked Odin says it can't. So till the note 7 gets unlocked (in time) we have to wait. Phone only few days old, be work around soon.
drum747 said:
Did anyone ever get the files that Beans asked for over to him?
Click to expand...
Click to collapse
Good question
@BeansTown106 did you ever get a Tar?
Sent from my SM-N930T using XDA-Developers mobile app
It appears this guy is in the process of getting the stock firmware uploaded
http://forum.xda-developers.com/showthread.php?t=3444003
Sent from my SM-N930T using XDA-Developers mobile app
ethanscooter said:
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
Click to expand...
Click to collapse
That is true. Android 7 Nougat will have more security features that Samsung is going to take advantage of with the Galaxy Note 7. That may make unlocking bootloader and rooting even more difficult.
-
It looks like the sprint guys have obtained an engineering bootloader/kernel. Someone may be able to do something with this for us..
Sent from my SM-N930T using XDA-Developers mobile app
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
jovy23 said:
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
Click to expand...
Click to collapse
Bro, please stop trying. This is obviously far above your skill level.
1. There is no way to convert a kernel to an "engboot."
2. The bootloader is LOCKED, so anything you do to the kernel's ramdisk will obviously not work because the whole point of dm-verity and a locked bootloader, among other things, is to stop the modification of system images, including the kernel ramdisk. Surely you didn't think it would be as easy as unpacking the boot.img, changing the ro.secure value from 1 to 0, then repacking..... did you?
3. The kernel doesn't "check" for anything MD5 related.
4. The bootloader is rejecting your changes, not the kernel.
5. Nothing you do to the boot.img, no matter how many devs you have, will do any good.
Hang tight, guys. We're trying everything we can.