Alright so i'm new here and would like to explain my situation.
I have a HTC Raider 4G, Bell provider on the newest software. I wanted to root my device and i noticed i needed to unlock it, so i did and it went off without any errors. Then i looked for the newest most updated thread i could find on rooting a HTC Raider and followed it's instructions, it worked perfectly...or so i thought. I rebooted my phone and found superuser app installed, which should be a good thing but no matter how many times i use Root checker etc, i still get the message saying my phone isn't rooted.
Q:So i was wondering if someone could fill me in if there was a spot i missed or if i need to do something else.
I'm still new to this so i might now understand every term you throw at me.
Try downloading a root required app like titanium backup or ad away and see if it works.
I have a Sprint HTC One (M7) that I rooted a while ago. On the first screen you get when you boot into recovery, it says Unlocked and S-Off. I'm using TWRP Recovery v2.8.3.0. I also use ROM Manager, and have installed a few different ROMs until I found one I liked, with no problems. My current ROM is CyanogenMod 5.0.2. I have superuse v3.1.3 (46). When I try to access Titanium Backup I get an error message that says "Sorry, I could not acquire root priveleges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command. I cant' figure out what the problem is. Can anyone help?
Hey all,
I have a HTC one M7, i had to recently send it off for repair due to battery and camera issues. It has now returned fixed... but updated.
It has S-ON and the latest hboot (1.66???) and from what i've read, is not possible to get S-off at this time unless paying for a service online.
I have rooted it using DEVunlock, flashed a custom recovery and ROM but im finding it soo very hard to do anything with 'root access' for example, game killer need root access and when granted, says "root privelege is needed" although superSU has granted it access, Amplify a battery app needs root and cannot obtain it even it has been granted and Xposed installer cannot install without manual recover (which seems to goto recovery and do nothing...)
From what i can understand, i do have root i think? but why can't i install any apps that require root? is it due to it being S-ON?
what can i do? really not sure what to search for and whats its called
bump
stevey88 said:
Hey all,
I have a HTC one M7, i had to recently send it off for repair due to battery and camera issues. It has now returned fixed... but updated.
It has S-ON and the latest hboot (1.66???) and from what i've read, is not possible to get S-off at this time unless paying for a service online.
I have rooted it using DEVunlock, flashed a custom recovery and ROM but im finding it soo very hard to do anything with 'root access' for example, game killer need root access and when granted, says "root privelege is needed" although superSU has granted it access, Amplify a battery app needs root and cannot obtain it even it has been granted and Xposed installer cannot install without manual recover (which seems to goto recovery and do nothing...)
From what i can understand, i do have root i think? but why can't i install any apps that require root? is it due to it being S-ON?
what can i do? really not sure what to search for and whats its called
Click to expand...
Click to collapse
Download Root Checker from Play Store to check to see if you are properly rooted. If not, then re-install your custom recovery (TWRP includes root). What I generally do is install SuperSU right after I install TWRP.
majmoz said:
Download Root Checker from Play Store to check to see if you are properly rooted. If not, then re-install your custom recovery (TWRP includes root). What I generally do is install SuperSU right after I install TWRP.
Click to expand...
Click to collapse
okay, ive downloaded it and its confirming that i have root access, i have a feeling it could be something to do with s-on...
stevey88 said:
okay, ive downloaded it and its confirming that i have root access, i have a feeling it could be something to do with s-on...
Click to expand...
Click to collapse
You can have root access and S-ON at the same time. So, it is not S-ON. Update SuperSU and see if it does not fix the issue. If not, you might want to install Busybox you can get if from the Play Store as well.
majmoz said:
You can have root access and S-ON at the same time. So, it is not S-ON. Update SuperSU and see if it does not fix the issue. If not, you might want to install Busybox you can get if from the Play Store as well.
Click to expand...
Click to collapse
Thank you for your replys!, the only reason i mention about S-ON is because ive been through this trouble before, i just cant remember what i did to fix it, i think it was due to it being a HTC my friend said, hence why i have a feeling it could be due to S-ON locking me out of certain parts of the phone.
I think i have the latest SuperSU v2.46, i installed busybox which also made no difference, still dont have access to lots of stuff...
stevey88 said:
Thank you for your replys!, the only reason i mention about S-ON is because ive been through this trouble before, i just cant remember what i did to fix it, i think it was due to it being a HTC my friend said, hence why i have a feeling it could be due to S-ON locking me out of certain parts of the phone.
I think i have the latest SuperSU v2.46, i installed busybox which also made no difference, still dont have access to lots of stuff...
Click to expand...
Click to collapse
If you have SuperSU installed and you can open it from the app drawer and the same with BusyBox then you have root. It might be the programs you are trying to run are not compatible with your phone or OS version. If that is the case then if you are S-ON or S-OFF it will not make a difference.
Hi, all. I have the D415 T-mo version of our phone and for some reason the past couple days I have been losing root access. Rooted using King Root. All I have to do is run it again but it's a bit annoying. Any thoughts on what could be causing this?
I think I figured it out, but would like confirmation. There's a process on T-Mo phones called com.tmobile.pr.adapt 2.0.0 that I granted root access to at one point and through a bit of research it's a tattletale process that reports back to T-Mo and tells them what you have installed, if you're rooted, if you have unknown sources checked, etc. Would that be killing my root, and if so is it safe to remove through Titanium?
Hi all.. I am having some issues with both rooting and modding my build.prop.
My ultimate goal right now is to have a stable root, on essentially stock rom, with a modded/bypassed native tether app (I have unlimited data and verizon blocks it). I am having issues with both processes, and if anybody can help it would be greatly appreciated!
First, I am having a ton of trouble with the temp root process; I am using Kingroot, and although I have been able to gain root successfully, it seems completely random when the process works and when it doesn't. About a quarter of the time, the root seemingly works.. the rest of the time, I either get force crashes on all running apps until system reboot, I am told I have root but cant access system files still, or the root fails altogether. Perhaps there is a flaw in my process? I also have been unable to update the SU binaries.. I have tried using both the latest stable and beta APKs from Chainfire. Is there a specific process that someone has used more successfully, order of installations, etc?
Secondly, when I have gained root successfully, I have been trying to add a line into my build prop to bypass the tether subscription check, which I believe will work.. but whenever I reboot my phone, it overwrites my saved changes to Build.prop. I will successfully get r/w (Using root explorer btw), mod the build.prop just adding in a single line, save, and then reopen confirming that the changes stuck. However, when I reboot, the stock Build.prop comes right back. I have also attempted to copy a modded brand new build.prop into /System instead, which also appeared to work, but ends with the same problem on reboot.
Please note that if possible I want to keep running stock, I do not want to have to flash a modded rom.
TL;DR - Root is finnicky, SU binaries won't update and build.prop resets to stock on reboot even after confirmed edits.
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the input..
I was hoping to avoid unlocking the bootloader, but I suppose I might as well. Kingroot does give me root, even if unstable, and Root Explorer tells me I have right access to /system.. plus, I can see that the changes have been implemented to build.prop, so it doesn't really make sense to me how/why it would revert to the stock build.prop on a reboot. Oh well.
The ROM checks the system on reboot. If it sees a change it reverts to what it was.
To fix that you need write protection disabled. Which twrp can do on an unlocked boot loader
Sent from my XT1254 using XDA Free mobile app
I may be wrong but I don't think you need to install TWRP to get rid of kingroot. I didn't feel like installing twrp partially because I'm lazy and partially because I dont plan on installing any other rom any time soon. Anyway, what I did was install kingroot, pay my $25 to sunshine and unlock the bootloader, then ran a script to remove kingroot an install supersu. The result was a perm rooted phone with super-su.
Maybe root checker is lying when it says i have root but adblocker can write to the hosts file so i don't think it is.
Kingroot cannot gain u permission for edit system partition. It only gain permission for run some script, program, it not true root, form what i read then even flash root by mofo, we still can't edit system partition
So u need unlock your bootloader
Okie Dokie smokie. I'm not here to convince anyone, I'm just letting you know what worked for me. I have su persistent in /system/xbin and have never installed TWRP. Root lives through reboots and superSU is installed and processing root requests. Kingroot is gone off the device. Feel free to PM me. I would be interested to see if it works without an unlocked bootlaoder. As i said, I unlocked with sunshine but never installed TWRP.
Are you sure recovery doesn't just check the recovery partition and restore it if it finds it has been modified. I have seen that behavior in the past very often. It seems a little wonky that every time the system boots it would check the whole /system partition.
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
As I said, I think you may be mistaken. i am looking through the script i used to replace kingroot. What does TWRP modify to allow persistent recovery. I wonder if booting into recovery will wipe out the persistent root. A normal reboot does not effect it. Maybe build.prop gets restored while other files do not. As i said, my hosts with adblockign persists through reboots.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1
I did not write the script i used and take no credit for it. Lets get that out of the way.
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I don't doubt that is your experience. I was sharing mine. I rebooted into recovery and root stayed. What i am saying, with confidence because i have done it, is that you do not need to install TWRP to keep root persistent through reboot.
Here is the script i ran.
http://pastebin.com/w7MqXBZZ
After looking more my best guess is that the Sunshine process disabled nand lock which is why i am able to write to the system partition.
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Cryptrix said:
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Click to expand...
Click to collapse
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Not Quite
cstone1991 said:
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the rest of the users on my line were on a very outdated plan, so Verizon blocked both the free hotspot on the current plans for limited data users, and my option to pay for it on my own line. So instead I spend two hours on the phone convincing them to put the other lines on a "sub-plan", and upgrade them collectively to an Everything More, while mine is singular on the cycle but technically still on the same plan. And NOW I have the option to pay.
Now I just need to figure out how to utilize my upgrade without losing Unlimited data..
I said this a few posts up, it may be of no concern now.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1.
You need root and you need to run it every time your phone is rebooted but ti works to bypass the entitlement check.