Related
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2
I've recently updated to V10E. I used to have a rooted device with towelroot.
After upgrade (done via LG PC suite), I lost the root.
I tried to root using PurpleDrake, all screen instructions and actions go fine, but the device is not rooted.
Is there a way to root V10E version at all ?
PurpleDrake - Lite is the only method of rooting this firmware at the moment, and it does work.
If you are having issues then either its your pc, or you not following the instructions that is the problem.
Lennyuk said:
PurpleDrake - Lite is the only method of rooting this firmware at the moment, and it does work.
If you are having issues then either its your pc, or you not following the instructions that is the problem.
Click to expand...
Click to collapse
What PC has to do here?
What kind of instructions are you talking about?
It's a simple ".bat" file that only requires to press Enter twice, that's about it.
Adb does see my phone, USB debugging is on and etc.
Temproot and Permaroot are being applied fine, no errors or anything. But it just doesn't work.
I can print a screen shot if you want.
By doesn't work what are you referring to? If the .bat file says its applying the files fine then it means it transferred the required files to your phone without error, there is then no reason for it not to be present when you reboot?
How do you know it didn't work?
jodvova said:
I've recently updated to V10E. I used to have a rooted device with towelroot.
After upgrade (done via LG PC suite), I lost the root.
I tried to root using PurpleDrake, all screen instructions and actions go fine, but the device is not rooted.
Is there a way to root V10E version at all ?
Click to expand...
Click to collapse
I updated my D855 rooted with towelroot last night via the OTA update and retained root, apart from having to turn xposed back on. The reports of inconsistent results I'm hearing are really odd. Mine's a 16gb model on ee, what's yours?
Sent from my LG G3
Lennyuk said:
By doesn't work what are you referring to? If the .bat file says its applying the files fine then it means it transferred the required files to your phone without error, there is then no reason for it not to be present when you reboot?
How do you know it didn't work?
Click to expand...
Click to collapse
The phone remains unrooted.
I can't install SuperSU nor edit build.prop
Rootchecker says no...
I'm on 32gb model from HKG.
jodvova said:
The phone remains unrooted.
I can't install SuperSU nor edit build.prop
Rootchecker says no...
I'm on 32gb model from HKG.
Click to expand...
Click to collapse
You can't install SuperSU, or when you open super su it fails to find the binary?
I even tried to run your guide to restore the phone (http://forum.xda-developers.com/lg-g3/general/guide-unroot-ota-using-lg-pc-suite-pc-t2802286) and then apply purpledrake but the phone remains unrooted.
Lennyuk said:
You can't install SuperSU, or when you open super su it fails to find the binary?
Click to expand...
Click to collapse
I click install in the play store, it downloads it, says installing... But then aborts with Incompatible update message.
jodvova said:
I click install in the play store, it downloads it, says installing... But then aborts with Incompatible update message.
Click to expand...
Click to collapse
that sounds like a separate issue. You do not need to be rooted to install the app from the Play Store, it just won't do anything if you install it without having root. The fact its not letting you install it is linked to some other issue, are you sure you don't have any other SU apps already installed, if you do remove them all first (including SuperSU if you have that installed) and then reboot before trying to download it again.
Lennyuk said:
that sounds like a separate issue. You do not need to be rooted to install the app from the Play Store, it just won't do anything if you install it without having root. The fact its not letting you install it is linked to some other issue, are you sure you don't have any other SU apps already installed, if you do remove them all first (including SuperSU if you have that installed) and then reboot before trying to download it again.
Click to expand...
Click to collapse
So originally, when I was on v10b and rooted with towelroot I had super su installed.
After that the phone told me there is OTA available which I immediately tried to install.
Since I also had dpi changed, OTA update failed. With that I lost the root, supersu disappeared from applications.
I then upgraded to v10e via LG PC suite. And now trying to root using PurpleDrake.
Super SU shows as not installed in Play Store. Titanium Backup doesn't see such apk installed.
I dont have any other "su" applications installed.
Any suggestions on how to fix it ?
jodvova said:
So originally, when I was on v10b and rooted with towelroot I had super su installed.
After that the phone told me there is OTA available which I immediately tried to install.
Since I also had dpi changed, OTA update failed. With that I lost the root, supersu disappeared from applications.
I then upgraded to v10e via LG PC suite. And now trying to root using PurpleDrake.
Super SU shows as not installed in Play Store. Titanium Backup doesn't see such apk installed.
I dont have any other "su" applications installed.
Any suggestions on how to fix it ?
Click to expand...
Click to collapse
Try to go to menu > settings > apps and see if you can see the SU app there.
Failing that your best option might be to factory reset and then root.
Lennyuk said:
Try to go to menu > settings > apps and see if you can see the SU app there.
Failing that your best option might be to factory reset and then root.
Click to expand...
Click to collapse
It's not there.
Also, as I said before rootchecker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) says the phone is not rooted.
I assume it doesn't use supersu to check whether it's rooted.
That's the output from console.
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D855 ] on [ GLOBAL ] running SW version [ V10e ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
Waiting for device... Found device!
Applying permaroot...
Waiting for system to settle...
Checking if it worked...
Permaroot worked, all done here. Moving on...
All done! Your phone has been successfully rooted.
After you press enter, your phone will be rebooted back to a rooted system.
Please be careful with what you change.
Press [enter] to continue...
Click to expand...
Click to collapse
jodvova said:
It's not there.
Also, as I said before rootchecker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) says the phone is not rooted.
I assume it doesn't use supersu to check whether it's rooted.
Click to expand...
Click to collapse
never used it before, but I would have thought that it would request SU permissions which would require an SU app.
Did a factory reset and root works now.
Someone tell me what it is. I wanna keeo root, lol, dont feel like going through all that
From online research, It's just to fix some bugs and a slight performance increase. I don't know if it will break root because I'm not rooted
Sent from my C6916 using XDA Premium HD app
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
mariussilverwolf said:
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
Click to expand...
Click to collapse
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
TrunkleBob said:
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
Click to expand...
Click to collapse
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
How did you install it easily, i keep getting could not be verified
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
anyway to decompile this update to see what files are there?
im getting could not be verified as well, trying via sony update center on PC, im rooting with xposed as well
arghhh before i was able to use root-cloak on the sony update app and download updates... seems i cant do that anymore. how did you get to install while rooted? @mariussilverwolf ?
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
chriscosta77 said:
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
Click to expand...
Click to collapse
It is broken, on latest minor ota through pc companion update, not restore, and trying to root with easy root but it isn't working
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
nickcaper said:
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
Click to expand...
Click to collapse
I just used my cousin's phone as a tester, it breaks root, haven't tested with supersu pro yet with survival mode
i swear, its like these companies dont want us to use the devices the way we want. A simple thing like root and they make it so hard, even impossible on some models. These companies should know by now that there is a niche which desires freedom like rooting.
if i wanted a frggin phone that didnt have root or a locked os or bootloader id get a dam iphone.
im seriously NOT buying another phone from a store.
ill make sure i get something i can work with the way i want. its already stupid expensive as it is just out the box all locked up and full of bloat wear.
it takes a stupid amount of time and effort just to make these devices do what we want.
which is something that i shoulda got when i paid for it..
looks like i wont be updating sh.... t till i know i can use my device freely.. the way i want.
Unrelated to the root conversation, I'm stock, but my data is acting a bit weird since the update. Did this update change the radios?
Sent from my C6916 using XDA Free mobile app
4.4.4 root
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Your question.
Johann Broseph said:
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Click to expand...
Click to collapse
Please just use the search feature, you can easily find the root method. The root method is even on the first page of this topic.
For reference (since my root access remained post update) here's what I have enabled in SuperSU settings:
* Enable SuperUser
* Show Notifications
* Auto-refresh apps and logs tab
* Enable su during boot
* Mount namespace separation
* Trust system user
* Enable permission warning
* Enable Pro
As I mentioned in a previous thread, root was obtained using towelroot on 4.4.4. I haven't run into any issues with root-check invalidating any installs since. The OTA installed without any error messages. I can inject audio into /system/media/notifications and I can create new folders on the root directory that remain after reboot. Maybe I got lucky? I hope by sharing this that other people can duplicate my findings and we can find a way for everybody to maintain a working root solution after this update.
TrunkleBob said:
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
Click to expand...
Click to collapse
I've been doing some digging and discovered I'm missing a file. Following the original directions for rooting, I created a script and have Script Manager executing it at startup.
The first command is:
Code:
su -c "/system/xbin/kill_ric.sh"
This fails because that file does not exist on my phone. Anyway to get that back?
I had a huge problem with this yesterday and long story short, you cannot use the easy root method if this update is applied. I had to use the flash tool to get the last ftf files and start over from scratch. Avoid this if you can.
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
gqukyo said:
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
Click to expand...
Click to collapse
only way to get the notification off is to go into settins then look for apps then look for update center. click on it and click on the clear cache. only problem now is. you will need an app like sd maid or something that stops that app from starting automatically when the phone turns on. this is what i do.. it works... you wont get anymore notifications unless you manually make it check.... i use sd maid...
Hello everyone,
Today I was able to root the VZW Moto E 2015 with the Kingroot app on 5.1. The Kingroot app said there was a method available and I decided to try it.
Simply install the app on your phone here: http://forum.xda-developers.com/devdb/project/dl/?id=16614
The root sticked for me upon reboot!
**I later found it was a hobbed root. You can't make changes to the system partition but you do have SU capabilities. (like you can run hidden apps and menus or block system apps, not remove them)
I still got root failed
Sent from my SM-G900P using Tapatalk
lvpre said:
I still got root failed
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
You downloaded the latest one right? Keep trying rebooting the device. That is what I had to do.
After 3rd try it worked !!! thanks OP!
Edit: root lost after reboot
...but is it full root, with full /system read-write access? Some people have been able to get hobbled root via Kingroot on 5.0.2, but /system remained read-only.
slinson said:
After 3rd try it worked !!! thanks OP!
Edit: root lost after reboot
Click to expand...
Click to collapse
Keep trying make sure you have latest Kingroot, keep rebooting
xtermmin said:
...but is it full root, with full /system read-write access? Some people have been able to get hobbled root via Kingroot on 5.0.2, but /system remained read-only.
Click to expand...
Click to collapse
I don't know, root checker works. How do I test?
andrewwm said:
I don't know, root checker works. How do I test?
Click to expand...
Click to collapse
Choose a bloatware app that you don't mind losing, such as NFL Mobile. If you "Disabled" it in Settings > Apps, re-enable it.
Install a file manager that has the ability to browse/edit the full filesystem, such as Amaze (https://f-droid.org/repository/browse/?fdid=com.amaze.filemanager) or Root Explorer (in Play Store).
Open up the app and go into /system/app or /system/priv-app and look for the folder related to NFL Mobile (you'll know it's the right folder if the apk inside of it has the NFL Mobile logo). Delete it. If it deletes, that's a good sign. Reboot and see if the NFL Mobile icon is still in the app drawer, and open up the file manager again and verify that the files you've deleted have stayed deleted.
Get hype boiz
xtermmin said:
Choose a bloatware app that you don't mind losing, such as NFL Mobile. If you "Disabled" it in Settings > Apps, re-enable it.
Install a file manager that has the ability to browse/edit the full filesystem, such as Amaze (https://f-droid.org/repository/browse/?fdid=com.amaze.filemanager) or Root Explorer (in Play Store).
Open up the app and go into /system/app or /system/priv-app and look for the folder related to NFL Mobile (you'll know it's the right folder if the apk inside of it has the NFL Mobile logo). Delete it. If it deletes, that's a good sign. Reboot and see if the NFL Mobile icon is still in the app drawer, and open up the file manager again and verify that the files you've deleted have stayed deleted.
Click to expand...
Click to collapse
Wow. Everything fails. Kingroot says I got root and stays upon reboot. Titanium Backup acts like it woks but resets after reboot. Very weird.
andrewwm said:
Wow. Everything fails. Kingroot says I got root and stays upon reboot. Titanium Backup acts like it woks but resets after reboot. Very weird.
Click to expand...
Click to collapse
Yeah, looks like you have hobbled root. While the su binary is installed, the system partition is still in read-only mode. While you'll be able to use apps that only need root privileges to read files/settings, you won't be able to edit the system itself.
Has anybody got it working? What are some signs of it working (i.e. 2 reboots, no reboot, etc.)?
andrewwm said:
Keep trying make sure you have latest Kingroot, keep rebooting
Click to expand...
Click to collapse
It is indeed the latest Kingroot
Also tried for 50+ times maybe, sometimes got root sometimes failed---even if got root, always lost root after reboot
andrewwm said:
Hello everyone,
Today I was able to root the VZW Moto E 2015 with the Kingroot app on 5.1. The Kingroot app said there was a method available and I decided to try it.
Simply install the app on your phone here: http://forum.xda-developers.com/devdb/project/dl/?id=16614
The root sticked for me upon reboot!
**I later found it was a hobbed root. You can't make changes to the system partition but you do have SU capabilities. (like you can run hidden apps and menus or block system apps, not remove them)
Click to expand...
Click to collapse
If someone gets root again, try to run Sunshine (bootloader unlock). You don't have to pay to see if it'll work.
As a heads up, sunshine fails with an error telling you to contact the sunshine support with your IP address if it continues.
Also, was able to back up the existing boot and recovery using flashify. I flashed the typical recovery used for other surnia devices, but when I tried to boot into recovery, it failed.
It got hung up in fastboot and gave check errors.
It did not keep me from booting back into the rom, so I was able to reflash the original recovery after re-rooting.
Yes, is only temporary root for me on 5.1.
I purchased supersume earlier today with the hopes of ridding myself of kingroot, but it immediately force closes. I trust the kr app about as much as I trust esfile explorer now...
Moto e root ,marshamalllow
Hi,I don't know that andriod 5.1 can be rooted by kingo root,so I upgraded to andriod 6.0,after update I tried to root ,the rooting process stops at 70percent,,, so any one help me ,how to root moto e 2015 marshmallow,,,any body have idea
Arunsunny009 said:
Hi,I don't know that andriod 5.1 can be rooted by kingo root,so I upgraded to andriod 6.0,after update I tried to root ,the rooting process stops at 70percent,,, so any one help me ,how to root moto e 2015 marshmallow,,,any body have idea
Click to expand...
Click to collapse
If you have Android 6.0, you do not have the XT1528.
Your device (XT1521 or similar) can be bootloader unlocked and you can install a custom recovery and can flash root.
The device being discussed in this topic (XT1528) cannot be bootloader unlocked.
Hi, I want only simple root I should not want to unlock boot loader and twrp recovery,,, because I don't have pc,, I want to root with phone,,,can you help me regarding this,,,thank you for you response
Arunsunny009 said:
Hi, I want only simple root I should not want to unlock boot loader and twrp recovery,,, because I don't have pc,, I want to root with phone,,,can you help me regarding this,,,thank you for you response
Click to expand...
Click to collapse
Not possible. The only known way to have permanent full root is to unlock the bootloader. Unlocking the bootloader is necessary to make /system mount as read-write.
Yes, I understand.can you please send me the procedure to unlock the bootloader.so no body have mentioned correctly in websites and YouTube... So send me the steps to unlock bootloader and root the andriod
Hello, so basically I've rooted my phone. The root test says the phone is rooted, but some apps that require root don't work (some do). I found out it could be caused by half root. I was not satisfied with it, so I tried to remove the Kingroot app along with the root, but the app reports an error every time. However, the Kingroot app has become "untouchable". It transformed into system app and I can't delete it, because the half root doesn't allow me to do that. I can't even manually delete the su files in root. How can I solve this? I don't have an unlocked bootloader, and I don't even want to, if the situation will allow it. I just want to go back to unroot status (realised it was a mistake trusting in one click root ).
The only "safe" way to remove kingroot it's to flash again stock firmware.
I did 3 times, just download full firmware, same version as you already have, then do a local update.
Hello there...
I suffered form this thing and i factory restored my phone but everytime I do Kingroot stills there.
I tried to install stock firmware but it says installation failed.(I downloaded stock firmware from Huawei's website)
Please help me
ItalianWolf said:
The only "safe" way to remove kingroot it's to flash again stock firmware.
I did 3 times, just download full firmware, same version as you already have, then do a local update.
Click to expand...
Click to collapse
Thank you very much for the reply! I don't really mind having my phone half-rooted, adblock still works, so it isn't a problem, but I suffer from the fact that it's not "complete" (some kind of "perfectionism" lol). I will find out more about flashing the original firmware. I'm afraid I will need to unlock the bootloader, am I right?