Related
For those who do not have access to a computer I achieved root on Kit Kat without a PC by following these steps :
All needed items will be linked below.
Root device using kingroot (will not trip Knox) if you are only wanting root for basic root apps (greenify etc.) then this is all you need to do. Have fun! (Just remember anything that changes the /system partition significantly such as xposed will trip Knox.)
To install superSU instead of kingroot/kinguser (will trip Knox)
Install flashify from the play store
Use flashify to install twrp (this step trips Knox)
Download SuperSU zip
Remove kingroot and the included kinguser app (follow instructions from kingroot thread)
Reboot into recovery and install SuperSU zip
OR :
After installing twrp just download a ROM (and if needed gapps) of your choice and flash.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461 for kingroot English.
https://play.google.com/store/apps/details?id=com.cgollner.flashify flashify play store link
For SuperSU zip google is your friend
hotrodwinston said:
For those who do not have access to a computer I achieved root today without a PC by following these steps :
Root device using kingroot (will not trip Knox)
(Tablet is now technically rooted but most people prefer SuperSU and to not have incompletely translated apps controlling root access)
Install flashify from the play store
Use flashify to install twrp (will trip Knox)
Download SuperSU zip
Remove kingroot and the included kinguser app
Reboot into recovery and install SuperSU zip
OR :
After installing twrp just download a ROM (and if needed gapps) of your choice and flash.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461 for kingroot English.
For SuperSU zip google is your friend
Click to expand...
Click to collapse
You've just negated the whole point of using kingroot, not tripping Knox.
You could have simply rooted using twrp or cfauto root without kingroot at all. I know it saves connecting to a PC, but that is trivial.
Kinguser supersu app is fully English and has no problems as a supersu replacement. I used it for months.
ashyx said:
You've just negated the whole point of using kingroot, not tripping Knox.
You could have simply rooted using twrp or cfauto root without kingroot at all. I know it saves connecting to a PC, but that is trivial.
Kinguser supersu app is fully English and has no problems as a supersu replacement. I used it for months.
Click to expand...
Click to collapse
Some people don't have a PC - this method would let them install custom roms or install xposed without needing a PC.
hotrodwinston said:
Some people don't have a PC - this method would let them install custom roms or install xposed without needing a PC.
Click to expand...
Click to collapse
I agree but then you stated about flashing supersu and twrp which would trip Knox and sort of made the first part of your informative post pointless, that's all.
Also flashing roms will also trip Knox, so again negates the point of rooting with kingroot.
ashyx said:
I agree but then you stated about flashing supersu and twrp which would trip Knox and sort of made the first part of your informative post pointless, that's all.
Also flashing roms will also trip Knox, so again negates the point of rooting with kingroot.
Click to expand...
Click to collapse
I see your point - will modify the op to reflect different goals of rooting - my use of kingroot was to obtain root knowing I was going to trip Knox to install a custom rom as I do not have a PC to run Odin.
Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.
If you have a computer and can downgrade to 4.4 kingroot should work then
djide said:
Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.
Click to expand...
Click to collapse
I had never heard of that tool. Did it work well on KK ? Looks like there are newer versions that could work with Lollipop. My only concern is that it is all in Chinese and I don't know how reliable it is
I saw in another thread that someone had success using KIng Root on the AT&T variant. I have tried several times and on several different days, but as of yet King Root will not work for me on the SM-T807V. This is the Verizon variant. Some folks have speculated that King Root might work on Lollipop if you have the Exynos chip and not the Snapdragon. Unfortunately, or fortunately, for me, I have the Verizon with the different chip. I believe I also read that Sprint variants also have Snapdragons.
Elbrin said:
I saw in another thread that someone had success using KIng Root on the AT&T variant. I have tried several times and on several different days, but as of yet King Root will not work for me on the SM-T807V. This is the Verizon variant. Some folks have speculated that King Root might work on Lollipop if you have the Exynos chip and not the Snapdragon. Unfortunately, or fortunately, for me, I have the Verizon with the different chip. I believe I also read that Sprint variants also have Snapdragons.
Click to expand...
Click to collapse
Sprint does have snapdragon, but their bootloaders are unlocked in which they can flash anything they want. Sucks that kingroot doesn't work onm Verizon
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sprint does have snapdragon, but their bootloaders are unlocked in which they can flash anything they want. Sucks that kingroot doesn't work onm Verizon
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I'm not sure whether the failure for it to work is the exploit itself or user error.
It has worked both on my exynos tab s t805 and my snapdragon m8.
Both running kitkat.
Earlier versions have worked on other devices I own.
I can't see what would be different exploit wise with the Verizon device.
It took me a few goes for the exploit to work and most importantly the device will reboot at least once and then continue the exploit, so must not be touched after the reboot.
My advice here is to set the screen timeout to at least 10 mins, so it can be monitored after it reboots.
Also it needs to be kingroot v4. Another point is that if the app root fails then it's worth trying the desktop version as, from past experience, this has worked when the app hasn't.
Yes but in my opinion the app is interesting because it makes it possible to keep the Knox counter at 0×0. Using the desktop version installs another recovery and triggers Knox. But it looks like the team is working hard to make it functional for devices on lollipop. I hope we will see progress for the tab s
I have tried both the desktop and the mobile version and both met with the same results -no root. The common thought now seems to be, from my readings, is that Verizon has a locked bootloader which might be more of the issue versus the difference in the chip. Oh well, I will just have to be patient with Tab S and just enjoy my rooted S6 Edge.
Sent from my SM-T807V using XDA Free mobile app
Elbrin said:
I have tried both the desktop and the mobile version and both met with the same results -no root. The common thought now seems to be, from my readings, is that Verizon has a locked bootloader which might be more of the issue versus the difference in the chip. Oh well, I will just have to be patient with Tab S and just enjoy my rooted S6 Edge.
Sent from my SM-T807V using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader is irrelevant as the exploit doesn't involve the bootloader. Not only that it works on the bootloader locked att model.
Keep root after update ??
hello just wondering if after king root gains root would I be able to update from Samsung update in settings ? And if It does let us update from setting will it remove or patch over the root exploit..! Thanks...
-Ahmed- smt700 (wifi 0nly)
As far as Knox is not tripped, I believe you should but you will lose root in the process.
Sent from my SM-T700 using Tapatalk
djide said:
Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.
Click to expand...
Click to collapse
Downgrade to kitkat, root with king root then flash lollipop stock official fw with flashfire, with injects supersu option
Really kingroot works?
Joker87 said:
Downgrade to kitkat, root with king root then flash lollipop stock official fw with flashfire, with injects supersu option
Really kingroot works?
Click to expand...
Click to collapse
I have not read any posts from anyone that has been able to root a VERIZON (caps used for emphasis ) Tab S (SM-T807V) with King Root or Kingo.
Sent from my SM-T807V using XDA Free mobile app
Op updated with more info regarding different steps if you just want root or want to go further and install xposed or custom Roms.
Sorry for taking so long to update - real life got in the way.
Has anyone found a method to replace kingroot with supersu without tripping Knox? I have tried the same steps that worked on my s6 on here and that didn't work. Worked only right after completing the process but when I reboot I lost root.
If you received the OTA firmware update like I did, you probably loss root access and it's now very hard to re-root. This is because Samsung updated the Knox partition and also the firmware.
What does this means?
Even if you flash an older version of your firmware, Knox partition will remain the same and you still won't have root access.
NOTICE: Root might be easy for some, but Xposed is really tricky to install on this device. Please backup all your files from your internal storage because there are minor chances your device might go into a boot loop, meaning you WILL have to flash a firmware again, this DOES NOT means you need to wipe your device, but it's always better to be prepared for the worst.
If you have no problem installing Xposed on your E7, this post is not for you! This is only if you received the OTA update!
1. ROOTING YOUR PHONE
- Install Kingo Root on your computer and follow the step by step instructions, just make sure to enable USB debugging from the developer options on your device and click accept when prompted to connect with your computer. You will have to wait from 5 to 20 minutes for the software to try multiple ways to root your device, sometimes it is really fast and sometimes it takes a while, it really depends on your firmware so if you fail to gain root access just go ahead and try another firmware from Sammobile. I use E700HXXU1AOAC_E700HUUB1AOAC_TPA and works really well, this is the firmware for Panama and it's NOT the newest one, however it has worked quite well for me. // CF Auto-Root used to worked before, however, after the update it is no longer working on this device :crying:
NOTICE: Disabling Knox voids your warranty and removes a very cool feature from your phone. Without Knox, anyone can steal your device and become its new owner. Why? Well, Knox links your device to your account only, no one else can use it unless having your user and password from Samsung, even after a full factory reset! So please keep this in mind, I'm willing to sacrifice this because I love Xposed.
2. DISABLING KNOX
- Now that you have Root Access, you need to install SuperSU to disable KNOX. Just go to the play store, download SuperSU, open it and grant root access to it using Kingo Root. You should now be prompted to Disable Knox and obviously you have to accept that!
3. OPTIONAL - Removing Kingo
- Download Titanium Backup from the Play Store so that you can remove your old Kingo User app... you won't need it anymore because you now have SuperSU. You can also uninstall Kingo App :good:
That's it! Rooted and without KNOX you can now install Xposed with no problems! No need for custom recoveries, just follow the classical procedure.
If you need help installing Xposed now that your device is properly rooted and without Knox, make sure to visit the other posts for more details.
AndreLopez360 said:
If you received the OTA firmware update like I did, you probably loss root access and it's now very hard to re-root. This is because Samsung updated the Knox partition and also the firmware.
What does this means?
Even if you flash an older version of your firmware, Knox partition will remain the same and you still won't have root access.
NOTICE: Root might be easy for some, but Xposed is really tricky to install on this device. Please backup all your files from your internal storage because there are minor chances your device might go into a boot loop, meaning you WILL have to flash a firmware again, this DOES NOT means you need to wipe your device, but it's always better to be prepared for the worst.
If you have no problem installing Xposed on your E7, this post is not for you! This is only if you received the OTA update!
1. ROOTING YOUR PHONE
- Install Kingo Root on your computer and follow the step by step instructions, just make sure to enable USB debugging from the developer options on your device and click accept when prompted to connect with your computer. You will have to wait from 5 to 20 minutes for the software to try multiple ways to root your device, sometimes it is really fast and sometimes it takes a while, it really depends on your firmware so if you fail to gain root access just go ahead and try another firmware from Sammobile. I use E700HXXU1AOAC_E700HUUB1AOAC_TPA and works really well, this is the firmware for Panama and it's NOT the newest one, however it has worked quite well for me. // CF Auto-Root used to worked before, however, after the update it is no longer working on this device :crying:
NOTICE: Disabling Knox voids your warranty and removes a very cool feature from your phone. Without Knox, anyone can steal your device and become its new owner. Why? Well, Knox links your device to your account only, no one else can use it unless having your user and password from Samsung, even after a full factory reset! So please keep this in mind, I'm willing to sacrifice this because I love Xposed.
2. DISABLING KNOX
- Now that you have Root Access, you need to install SuperSU to disable KNOX. Just go to the play store, download SuperSU, open it and grant root access to it using Kingo Root. You should now be prompted to Disable Knox and obviously you have to accept that!
3. OPTIONAL - Removing Kingo
- Download Titanium Backup from the Play Store so that you can remove your old Kingo User app... you won't need it anymore because you now have SuperSU. You can also uninstall Kingo App :good:
That's it! Rooted and without KNOX you can now install Xposed with no problems! No need for custom recoveries, just follow the classical procedure.
If you need help installing Xposed now that your device is properly rooted and without Knox, make sure to visit the other posts for more details.
Click to expand...
Click to collapse
AndreLopez360 You got OTA update? how? now ur device E700H run Android 5.1?
I checked my device to update but I got massage that told me "the latest updates have already been installed." so HOW u got android 5.1 on E700H?
Which rom are u using?
AndreLopez360 said:
If you received the OTA firmware update like I did, you probably loss root access and it's now very hard to re-root. This is because Samsung updated the Knox partition and also the firmware.
What does this means?
Even if you flash an older version of your firmware, Knox partition will remain the same and you still won't have root access.
NOTICE: Root might be easy for some, but Xposed is really tricky to install on this device. Please backup all your files from your internal storage because there are minor chances your device might go into a boot loop, meaning you WILL have to flash a firmware again, this DOES NOT means you need to wipe your device, but it's always better to be prepared for the worst.
If you have no problem installing Xposed on your E7, this post is not for you! This is only if you received the OTA update!
1. ROOTING YOUR PHONE
- Install Kingo Root on your computer and follow the step by step instructions, just make sure to enable USB debugging from the developer options on your device and click accept when prompted to connect with your computer. You will have to wait from 5 to 20 minutes for the software to try multiple ways to root your device, sometimes it is really fast and sometimes it takes a while, it really depends on your firmware so if you fail to gain root access just go ahead and try another firmware from Sammobile. I use E700HXXU1AOAC_E700HUUB1AOAC_TPA and works really well, this is the firmware for Panama and it's NOT the newest one, however it has worked quite well for me. // CF Auto-Root used to worked before, however, after the update it is no longer working on this device :crying:
NOTICE: Disabling Knox voids your warranty and removes a very cool feature from your phone. Without Knox, anyone can steal your device and become its new owner. Why? Well, Knox links your device to your account only, no one else can use it unless having your user and password from Samsung, even after a full factory reset! So please keep this in mind, I'm willing to sacrifice this because I love Xposed.
2. DISABLING KNOX
- Now that you have Root Access, you need to install SuperSU to disable KNOX. Just go to the play store, download SuperSU, open it and grant root access to it using Kingo Root. You should now be prompted to Disable Knox and obviously you have to accept that!
3. OPTIONAL - Removing Kingo
- Download Titanium Backup from the Play Store so that you can remove your old Kingo User app... you won't need it anymore because you now have SuperSU. You can also uninstall Kingo App :good:
That's it! Rooted and without KNOX you can now install Xposed with no problems! No need for custom recoveries, just follow the classical procedure.
If you need help installing Xposed now that your device is properly rooted and without Knox, make sure to visit the other posts for more details.
Click to expand...
Click to collapse
i have downgraded to kitkat
and rooted by kingroot
good a root acsess also and super user granted the permisson now which sdk version zip have to download
This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk
Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/
shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk
Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?
dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.
russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!
efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.
Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?
Other than Titanium Backup, I don't have any apps that regularly require root. On the other hand, I find an increasing number of apps that refuse to run on a rooted phone.
I'm running SM-910T stock 5.1.1, with systemless root now.
I would be happy to run unrooted for 99% of the time if I could easily get to root to perform a backup, and on occasion for certain file maintenance tasks.
Is there any way to get temporary root (directly without Odin or flashing from recovery), perform rooted tasks, and then reboot back to an unrooted state?
I've searched here and it appears most mentions of temporary root are device specific work-arounds for phones with locked bootloaders. Is there a general approach that would apply to the Note4?
timg11 said:
Other than Titanium Backup, I don't have any apps that regularly require root. On the other hand, I find an increasing number of apps that refuse to run on a rooted phone.
I'm running SM-910T stock 5.1.1, with systemless root now.
I would be happy to run unrooted for 99% of the time if I could easily get to root to perform a backup, and on occasion for certain file maintenance tasks.
Is there any way to get temporary root (directly without Odin or flashing from recovery), perform rooted tasks, and then reboot back to an unrooted state?
I've searched here and it appears most mentions of temporary root are device specific work-arounds for phones with locked bootloaders. Is there a general approach that would apply to the Note4?
Click to expand...
Click to collapse
If you are on 5.1.1 KingRoot app or( kingoroot pc version)will root temporary but once your reboot you will lose root.you have to reroot again on every reboot.
But i am not sure this will keep your device status official.
Trex888 said:
If you are on 5.1.1 KingRoot app or( kingoroot pc version)will root temporary but once your reboot you will lose root.you have to reroot again on every reboot.
But i am not sure this will keep your device status official.
Click to expand...
Click to collapse
When KingRoot and kingoroot came out a few years ago, I recall reading that they were possibly security or privacy risks themselves. Have they been around long enough to clear their reputation, and now the community is confident they do not have hidden malware or undesirable functionality?
Also, I'm not concerned about "official" status, such as warranty bit and Knox - I am primarily wanting to support apps that refuse to run if they detect root.
timg11 said:
When KingRoot and kingoroot came out a few years ago, I recall reading that they were possibly security or privacy risks themselves. Have they been around long enough to clear their reputation, and now the community is confident they do not have hidden malware or undesirable functionality?
Also, I'm not concerned about "official" status, such as warranty bit and Knox - I am primarily wanting to support apps that refuse to run if they detect root.
Click to expand...
Click to collapse
I think your confusing KingRoot with KingoRoot
majicmazo said:
I think your confusing KingRoot with KingoRoot
Click to expand...
Click to collapse
Yes I am confused. First how many of these are there? KingRoot, KingoRoot, kingoroot pc version. Are all three different? Which are APKs, and which are PC software?
It looks like https://kingroot.net/ is both APK and Windows, and goes by the name KingRoot.
Also https://www.kingoapp.com/ calls itself KingoRoot, and also offers APK and Windows software.
Most important, which are reputable/trustworthy?
timg11 said:
Yes I am confused. First how many of these are there? KingRoot, KingoRoot, kingoroot pc version. Are all three different? Which are APKs, and which are PC software?
It looks like https://kingroot.net/ is both APK and Windows, and goes by the name KingRoot.
Also https://www.kingoapp.com/ calls itself KingoRoot, and also offers APK and Windows software.
Most important, which are reputable/trustworthy?
Click to expand...
Click to collapse
Once upon a time there was kingoroot, it got a bad reputation for malware... Then came kingroot which I haven't heard anything bad about... I have personally used it its a little annoying because the UI is in Chinese but pretty easy to figure out the buttons... I'm not sure about the the site kingo app but kingroots site is
https://kingroot.net which is what you're looking for... Download to a pc, plug in, run. Disclaimer: i never used it on this phone i can just tell you there's no malware on it... I do not in any way guarantee you the safety of your device with any root method... Rooting is always at your own risk no matter how you do it.
---------- Post added at 12:42 AM ---------- Previous post was at 12:13 AM ----------
Trex888 said:
If you are on 5.1.1 KingRoot app or( kingoroot pc version)will root temporary but once your reboot you will lose root.you have to reroot again on every reboot.
But i am not sure this will keep your device status official.
Click to expand...
Click to collapse
I think this is where the confusion started Kingroots pc app is called KingRoot-Pc NOT kingoroot PC they are 2 different Apps..
Kingroot here https://kingroot.net/ both APK and PC version called KingRoot
And Kingoroot is here https://www.kingoapp.com/ once again offering both an android and PC version
While often confused they are NOT the same or even the same team despite what some forums claim you can look at both websites about section
https://www.kingoapp.com/about.htm
https://kingroot.net/about/
They are in fact 2 septate teams with similar names. Now Kingoroot once had a bad reputation for malware, I think that they have since then got better but I haven't used them in quite some time...Kingroot on the other hand has always been safe at least from malware.
A few preliminary notes:
Phone: LG K7, k330
Apps I've installed: SuperSU, KingRoot, Root Browser, Cheat Droid, BusyBox KingRoot(PC Version)
I've tried KingRoot from manual download on my phone, this claims to have been successful root.
I opened my Root Browser to modify game/save files and it said, effectively
App Restrictions AAAAAA==
So next I tried bringing in SuperSU, BINARY IS OCCUPIED.
Clicked "How to solve".
Told me to unlock bootloader.
Went to lge.developer stuff, I made an account, every time I sign it it auto logs me out I can't click the button Start Process (or whatever it said).
Downloaded Kingo ROOT on my computer, failure. Phone froze on FIRMWARE UPDATE 0% (waited 30 minutes and nothing changed, app seemed frozen on PC).
I started my phone with Kingo ROOT with fastboot, tried a few things(I have no idea what, just some copy and pastes, fastboot and OEM stuff, bootloader).
So when I boot my phone now it says Bootloader STATE: Unlock Bootloader!!
So, I don't know if that worked, but even with KingRoot I still can't edit any of my saved games (Idle Blacksmith is the game I want to hack really)
My old phone I just downloaded 1 apk, and I could edit any damn prefs, and change in game values without a problem (Except server side games)
I have not been able to modify any game data due to the App Restrictions AAAAAA== message keep coming up.
So, this whole lge.developer instruction is impossible, I CAN NOT login for more than 2 seconds without auto log out.
So hopefully someone can get me just to changing some local PREFS without the app restrictions block.
Anyone?
danny29992 said:
A few preliminary notes:
Phone: LG K7, k330
Apps I've installed: SuperSU, KingRoot, Root Browser, Cheat Droid, BusyBox KingRoot(PC Version)...
Click to expand...
Click to collapse
There's an area within the XDA Forum that's specific to your device and it took me about 3 minutes to locate the following threads that is of value to your specific device.
In addition, the first thread should be where you should be posting this question too.
[ROOT] [REF] LG K7 install SuperSU without Kingroot (lgms330 and lgk330) by ledzepman71
OFFICIAL TWRP for the LG K7 (Metro/T - Mobile)
I wish you the best of luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
Ibuprophen said:
There's an area within the XDA Forum that's specific to your device and it took me about 3 minutes to locate the following threads that is of value to your specific device.
In addition, the first thread should be where you should be posting this question too.
[ROOT] [REF] LG K7 install SuperSU without Kingroot (lgms330 and lgk330) by ledzepman71
OFFICIAL TWRP for the LG K7 (Metro/T - Mobile)
I wish you the best of luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
I've looked this over a few times and it's still not making sense.
To get TWRP I need root.
Therefore, going to the first link falsifies the "without root" claim.
Going through the post, it describes booting in bootloader mode, which doesn't identify how,
or where to get the files/downloads I need for it.
So again, still not clear instructions, and no visible way to do it.
danny29992 said:
I've looked this over a few times and it's still not making sense.
To get TWRP I need root.
Therefore, going to the first link falsifies the "without root" claim.
Going through the post, it describes booting in bootloader mode, which doesn't identify how,
or where to get the files/downloads I need for it.
So again, still not clear instructions, and no visible way to do it.
Click to expand...
Click to collapse
All I want to do is edit my game data so I can break through whatever restriction prevents me from seeing the int/string values, which is the apprestrictions=AAAAAAAAA
and a whole slew of letters after it.
Just checked the LGE login, whenever I click START Unlocking bootloader, it just automatically logs me back out.
This is the recommended way that SuperSU attempts to use. Therefore, since KingRoot and SuperSU are non-congruent, rooting the K7 can not be successfully done, such that the bootloader doesn't unlock.