I picked up a Verizon HTC One on release day, and was lucky enough to unlock the bootloader that night. Outside of unlocking the bootloader, I did install the CWM recovery, installed the SuperSU binary, and have used a few applications that require root (Titanium Backup, Light Flow, ROM Manager and WiFi Tether).
What I don't understand (and have never experienced before) is the com.android.phone application asking for root access seemingly at random times. It's happened twice now, both when the phone wasn't being used. Any idea what this could possible be?
I haven't installed any custom ROMs, or even debloated, so it wouldn't have to deal with either of those scenarios.
Thanks for the help!
calebspronk said:
I picked up a Verizon HTC One on release day, and was lucky enough to unlock the bootloader that night. Outside of unlocking the bootloader, I did install the CWM recovery, installed the SuperSU binary, and have used a few applications that require root (Titanium Backup, Light Flow, ROM Manager and WiFi Tether).
What I don't understand (and have never experienced before) is the com.android.phone application asking for root access seemingly at random times. It's happened twice now, both when the phone wasn't being used. Any idea what this could possible be?
I haven't installed any custom ROMs, or even debloated, so it wouldn't have to deal with either of those scenarios.
Thanks for the help!
Click to expand...
Click to collapse
I don't know if it's the same thing or not but I keep getting a root request from SIM Toolkit at exactly midnight. I don't think it happens every night I remember it happening 2 or 3 times now but I always just hit deny
Edit: Nevermind. There's a thread about the SIM Toolkit one here: http://forum.xda-developers.com/showthread.php?t=2424072
this is an odd issue as I have my phone in airplane mode and had it happen.
I think it's trying to reboot the phone? I've seen it too. I just deny it
Sent from my HTC One using Tapatalk 4
So, I guess this is a dead issue? I've set SuperSU to auto deny the request, but still keeps happening (today, in fact) and two other times since I rooted and unlocked bootloader about 2 months ago. Running stock CREDO (Sprint), which is essentially the same as Developer Edition. No branded crapware as far as I can tell. No issues arise from the request, but it bothers me that this happens.
Sent from my HTCONE using Tapatalk
WookieFan said:
So, I guess this is a dead issue? I've set SuperSU to auto deny the request, but still keeps happening (today, in fact) and two other times since I rooted and unlocked bootloader about 2 months ago. Running stock CREDO (Sprint), which is essentially the same as Developer Edition. No branded crapware as far as I can tell. No issues arise from the request, but it bothers me that this happens.
Click to expand...
Click to collapse
You are in a Forum devoted to the Verizon model of the HTC One. So how does Sprint come in to the picture?
Related
I just bought my LG G3 this past weekend and I still want to experience the stock feel and get used to it. I think I'll wait a little while before I root. Maybe a month-ish...if i can hold out that long.
digitallure said:
I just bought my LG G3 this past weekend and I still want to experience the stock feel and get used to it. I think I'll wait a little while before I root. Maybe a month-ish...if i can hold out that long.
Click to expand...
Click to collapse
Bought the phone, went home, install necessary drivers and root the phone, all within the space of 2 hours. :victory:
Can you try to add new contacts? Add field.... Events.... Mime FC after click events.
Open any existing contact which has birthday (event) also FC.
bajasolid said:
Bought the phone, went home, install necessary drivers and root the phone, all within the space of 2 hours. :victory:
Click to expand...
Click to collapse
LOL Nice!!! :good:
digitallure said:
I just bought my LG G3 this past weekend and I still want to experience the stock feel and get used to it. I think I'll wait a little while before I root. Maybe a month-ish...if i can hold out that long.
Click to expand...
Click to collapse
If I were you, I would root while you can. Verizon is notorious for patching root exploits with updates. With rooting, it doesnt wipe anything nor make any changes unless you install apps that make the changes. I would root and install SU and that would be it if I were you. Because you could wake up one morning and accidentally approve an update and then you cant root again until another exploit is found.
Rooted with TowelRoot while I was walking out of the store.
bajasolid said:
Bought the phone, went home, install necessary drivers and root the phone, all within the space of 2 hours. :victory:
Click to expand...
Click to collapse
+1. Rooted before I even setup the phone.
Got the phone and went home and set everything up, got in the bed for the night and looked up the root process and I rooted the device with TowelRoot as I was falling asleep.
I really think there's a fundamental misunderstanding as to what root is. I rooted my phone immediately, had it since launch day on T-Mobile, but aside from some minor changes to the status bar and installing cf.lumen to save my eyes at night, it's a stock phone.
"Rooting" your phone doesn't mean installing a custom ROM and making a load of build.prop edits. It just means giving yourself access to the root directory, meaning the system files. Your computer comes with root access right out of the box.
I rooted the G3 because I just don't like the fact that I'm at all limited in how I use my own device that I bought for full ticket price. If I drop $600 on a phone I should be allowed to do whatever I want with it.
Had it about 3 hours then rooted. Benefits of rooting are excellent!
After a few days because I bought Tasker.
droidkevlar said:
If I were you, I would root while you can. Verizon is notorious for patching root exploits with updates. With rooting, it doesnt wipe anything nor make any changes unless you install apps that make the changes. I would root and install SU and that would be it if I were you. Because you could wake up one morning and accidentally approve an update and then you cant root again until another exploit is found.
Click to expand...
Click to collapse
Note taken.
SomeGuyDude said:
I really think there's a fundamental misunderstanding as to what root is. I rooted my phone immediately, had it since launch day on T-Mobile, but aside from some minor changes to the status bar and installing cf.lumen to save my eyes at night, it's a stock phone.
"Rooting" your phone doesn't mean installing a custom ROM and making a load of build.prop edits. It just means giving yourself access to the root directory, meaning the system files. Your computer comes with root access right out of the box.
I rooted the G3 because I just don't like the fact that I'm at all limited in how I use my own device that I bought for full ticket price. If I drop $600 on a phone I should be allowed to do whatever I want with it.
Click to expand...
Click to collapse
I know what root is... It comes from a plant
About 2 weeks after I bought it. Bought it on release so ya wanted to try it out a little, then got so frustated with the lag so, root remove bad stuff etc etc ART = almost lagfree. Still waiting for unlocked bootloader tho.
5 minutes. Root does t change stock feel just unlocks the door of greatness
Sent from my LG-D851 using XDA Premium 4 mobile app
Got huge problems while updating to 10g caused by rooting the phone with Purpledrake.
Had to go the way with PC-Suite and "repair update errors" to get the 10g
Without that step Phone reboots with message "Root detected, no update"
So, in the moment I´m using the 10g without root waiting for 10i which should be released soon.
Maybe I´ll root the the phone again after next update.
About a day, because I refuse to use an Android phone anymore without Xposed. It's really changed the way I use my phone for the better. No more rom flashing, just stock rom with Xposed and I'm good.
i had to wait about 3 mins had to do setup then root
I rooted the next day. Had to get rid of all that bloatware ASAP!!
20 minutes haha. Used towel root.
I believe an android phone should be rooted as a default. so it's my 1st action.
the first thing I allways do with my new android is rooting it.
After rooting I start setting it up.
on my new tablet and my G3 it took me seconds with towelroot.
Hey,
Been experimenting over the past few days now that I have a 4.4 phone for Verizon...What is the best temporary root program? after a while it seems my phone either loses root, or it isn't fully rooted (features not optional or working) with KingRo.
KingRo is the easiest, with KingRoot the phone shuts down or restarts itself, if i try to install supersume it also reboots or freezes.
Any other ideas? I have done the install via SP Tools and that is no better. after a few hours i lose root acccess and have to reboot. Even if i do a soft reboot i still loose root.
I think that is why they call it temporary. I too use kingroot. When my phone boots it is gone. It doesn't take Long for my phone to reboot when trying to use root functions.
Sent from my SM-N910V using Tapatalk
Someone posted something in the 'New Note 4 owner' thread about a possible permanent root. I checked it out earlier today, and from what I read, for our phone (those with a Verizon retail Note 4) it's meant for Lollipop 5.0.1. It provides a link to the Odin and root file downloads you'd need. I haven't tried it myself yet, but I'm remaining skeptically optimistic. Sadly, there haven't been new posts to that thread since my last one at 2:10pm today. Hopefully, someone will give it a shot this weekend, and if not I may try it on Monday. I'd just have to update to the 5.0.1 version of Lollipop first. I need my phone for work, so that's mainly why I haven't delved into it yet.
No way that root for lollipop works permanently when we cant root 4..4
I'm just looking to see if everryobe is having the same trouble as me with kingroot or KingO, perhaps one program iss better than the other,
Of the newer android phones, which one is the best that is rootable> if i decide to switch to a permnanent rooted phone
anyone>
Any phone Not from Verizon almost. Verizon locks down the boot loader.
Sent from my SM-N910V using Tapatalk
no suggestions?
???
I have being trying to log in to Pokemon go for the last week and I'm constantly getting failed to authenticate, someone has mentioned that it may not be because of the servers but because I'm rooted. Had any one else has this issue and if so I heard safety net mentioned and that magisk can resolve this issue where do I get magsik
Sent from my HTC 10 using Tapatalk
I haven't logged into Pokemon Go in ages and did so just a few minutes ago. I too can't get into my account. I suspect it has to do with them blocking rooted devices. In my opinion, this is a terrible strategy because in an attempt to block cheating, they've locked out a whole section of people who root their devices and have no interest in cheating. I just said '**** it' and uninstalled the app. Yes, there are ways to try and trick it, but you're going to need to jump through a ton of hoops and mess with all sorts of settings and to me, that's not worth it at all.
I've heard magisk you simply turn off root in settings with safety net support like you would for Android pay and it works anyone done this and can this be done with a custom rom
Sent from my HTC 10 using Tapatalk
just got it working with xposed. magisk + systemless xposed doesn't work anymore, but chainfire's suhide + SuperSU works with it.
Magisk doesn't work anymore and you can't have xposed on the phone. You have to flash a special superuser that hides itself, I will try and find the link for you.
Follow these steps at the beginning of the thread, works for me.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396/post69021494#post69021494
They made this change about a month ago. Rejects jailbroken iphone users as well.
Might as well ask this here since it's somewhat related. I just got an HTC 10 a few days ago and one of the most common things everyone is saying in regards to root is that you need to make sure that forceencrypt is on or something or else you lose cell signal or whatever. Do Magisk/suhide/systemless root methods have this problem or do I just install everything normally? I need to catch me some Pokemans.
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.
I searched the forums and it looks like running a bootunlocker for this AT&T phone might brick it. Has anyone successfully rooted this variant? Thanks.
scragglejaw said:
I searched the forums and it looks like running a bootunlocker for this AT&T phone might brick it. Has anyone successfully rooted this variant? Thanks.
Click to expand...
Click to collapse
I just got one of these yesterday (I had a t-mobile one before, but the screen broke a week or so ago) and thought it should be just as easy to root and put CWM or TWRP on it and then a custom rom with root, but I have been seeing conflicting information. It seems that there are only temporary ways to root it? Not sure what is different from the N910A and my old N910T, but obviously there must be something.
m374llic4 said:
I just got one of these yesterday (I had a t-mobile one before, but the screen broke a week or so ago) and thought it should be just as easy to root and put CWM or TWRP on it and then a custom rom with root, but I have been seeing conflicting information. It seems that there are only temporary ways to root it? Not sure what is different from the N910A and my old N910T, but obviously there must be something.
Click to expand...
Click to collapse
the n910a is not root able, and has a locked boot loader. the thing is locked down tight. you can get temp root on older version of android, but its buggy.
this is what I came to look for too
Kingroot isn't working at the moment either
And uhh.. since y'all are kinda talking about it.. a boot loader unlock & root are not the same thing..
Boot Loader unlock would be nice too but there are plenty of devices out there stock rooted that still have a locked Boot loader..
Retarded device
I got a developer edition N910V from Samsung so nice having unlocked bootloader but I got a N910A for stupid cheap and when in download mode says custom but doesn't have a lock on boot screen and the damn thing shuts off for no reason. Got the device it was in safe mode I flash with Odin and it has acted strange. I flashed it 3 times and the last time on boot says AT&T upgrade previously it would just show the android and wouldn't go into recovery without showing upgrading. Is there a possibility that the person I got from tried to root caused issues with the device and maybe it's kinda rooted... also can I clone my aboot from my N910V to this device possibly making it a Frankenstein?.....Noticed a thread called AT&T note 4 keeps freezing and rebooting that others are claimin to have the same issue... is this related and the reply about using wakelock has seamed have fixed the issue. Does this mean the processor is going out and can it be fixed? I can't let mu retarded friend use this device like this he will end up doing something and ***** about it continuing to reboot while writing a text. Thank you for your help.