Related
I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.
MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.
Having some guys look into this.
doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L
This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app
not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4
Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK
LOL this works?!? how did nobody ever try this until now.. I'm speechless
If you have rooted your N6P and you are at a store and want to use Google Pay, is there a way of quickly (on the fly as it were ) unrooting the phone,, making purchase and then rerooting?
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Cares said:
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Click to expand...
Click to collapse
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Tried this method on my Nexus 6. It knows I'm rooted, even if I've disabled SU entirely and rebooted.
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
So how do you ensure the system partition is not changed?
kboya said:
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
Click to expand...
Click to collapse
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
teknomar7 said:
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Click to expand...
Click to collapse
I just added my cards. I'll test it out later today. Need to find a store that takes Android Pay
teknomar7 said:
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
Click to expand...
Click to collapse
There's a root without changing system. As I said, have a search about. I read it earlier today or perhaps yesterday. There's a thread about the root without system.
Thanks... found the link.
http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
cool, no worries.
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
ArkAngel06 said:
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
Click to expand...
Click to collapse
Can you still pay after a reboot? Thanks.
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
Lol, I'll have to try tomorrow.
Was this explanation debunked, then?
http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/
You
Aridon said:
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
Click to expand...
Click to collapse
Yes, but Google stated that Android Pay can't be used with root. So of course there will some question to it.
source
And root absolutely does effect Android Pay. However if seems only while adding payment methods, and nothing once they are added.
What Google is using to determine if the device has been tampered with: https://koz.io/inside-safetynet/
Its definitely an interesting and pretty secure setup. Since it seems to happen real-time, maybe they turned off the "su_files" check and thats why Android Pay works on rooted devices now.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
ArkAngel06 said:
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
Click to expand...
Click to collapse
This is correct. If you try to pay, after adding your cards and re rooting, it will fail.
You must disable root again to pay. You can reenable after.
first of all i'm sorry if this has been answered already, but i could not find the answer.
My 6P is setup as follows:
MDB08L build
rooted with systemless root and TWRP
xposed v78 sdk 23
xposed mods:
greenify
gravitybox
App Settings
No Lock Home
Snapprefs
Xinsta
Custom Share
i try to activate my AMEX on android pay and i get the error message stating that Google cannot verify the software (same message as if i was running a rom)
i have tried to unroot in SuperSU and then add the card...no difference
can anyone help me out here?
It won't work if you are rooted. Some people have said that temp unroot works, but I've never been able to get it.
Xposed modifies system, pay won't work
akellar said:
Xposed modifies system, pay won't work
Click to expand...
Click to collapse
alright. i'm going to try to uninstall xposed. add the card and see what happens then i guess.
Thanks!
No AP with root, even systemless root. There might be a few that have said they have figured it out but in general 99.9% of people say it will not work.
I came from an Lg G3 with root and Xposed.
You cannot add cards if Xposed is installed. FIle systesm is checked.
You need to uninstall Xposed.
Once the cards are added re-install Xposed and root.
Use the module "No Device Check" to be able to use Android Pay.
I have Xposed and root and use Pay with no issues.
steveo17 said:
alright. i'm going to try to uninstall xposed. add the card and see what happens then i guess.
Thanks!
Click to expand...
Click to collapse
jawmail said:
No AP with root, even systemless root. There might be a few that have said they have figured it out but in general 99.9% of people say it will not work.
Click to expand...
Click to collapse
yep so even without xposed and disabling root, i cannot activate android pay.
oh well
I have used android pay with system less root.
No android pay with root, it's actually the first time i didnt immediately root my phone
what are u talking about guys? i have full stock, bootloader locked, but still can't use android pay, tells me that it is not available on this device
emiwonder said:
what are u talking about guys? i have full stock, bootloader locked, but still can't use android pay, tells me that it is not available on this device
Click to expand...
Click to collapse
What are you talking about? Android pay absolutely works fine on this and every other device with nfc.
emiwonder said:
what are u talking about guys? i have full stock, bootloader locked, but still can't use android pay, tells me that it is not available on this device
Click to expand...
Click to collapse
Where are you?
emiwonder said:
what are u talking about guys? i have full stock, bootloader locked, but still can't use android pay, tells me that it is not available on this device
Click to expand...
Click to collapse
Works perfectly fine on a stock 6P in the U.S.
tech_head said:
Where are you?
Click to expand...
Click to collapse
i am in Canada
Lots of misinformation about this. Android pay works fine if you use systemless root. I have it on my phone currently.
Is pay available in Canada
Sent from my Nexus 6P using Tapatalk
tech_head said:
Is pay available in Canada
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No. And all banks except RBC in Canada who have tap to pay apps won't work either as the use secure SIM
Sent from my Nexus 6P using Tapatalk
grubbster said:
Lots of misinformation about this. Android pay works fine if you use systemless root. I have it on my phone currently.
Click to expand...
Click to collapse
I too am having problems adding a card to Android Pay due to the "Google is unable to verify. . ." error. I'm on stock ROM, and followed the directions for system-less root (thanks for that thread!).
One thing I'm starting to suspect is that when I first booted TWRP, upon being asked to keep system read only, I chose to "swipe to allow modifications".
Does anyone think this action, of allowing TWRP to modify the system partition, is the root cause for Android Pay not working? Is there a way to undo this action in TWRP, to put the system partition back to read-only?
Thanks!
sentinel230 said:
I too am having problems adding a card to Android Pay due to the "Google is unable to verify. . ." error. I'm on stock ROM, and followed the directions for system-less root (thanks for that thread!).
One thing I'm starting to suspect is that when I first booted TWRP, upon being asked to keep system read only, I chose to "swipe to allow modifications".
Does anyone think this action, of allowing TWRP to modify the system partition, is the root cause for Android Pay not working? Is there a way to undo this action in TWRP, to put the system partition back to read-only?
Thanks!
Click to expand...
Click to collapse
i'm assuming you're rooted with SuperSU 2.62?
you have to delete SU/Bin i think to get it to work
It is available on this device, but is geographically dependent. If you live in a location where Android Pay is available and are completely stock and unrooted it will work. You then go into the lottery once you start looking at root etc.
So I was fortunate enough to have ArnovaG82 to look into the camera app of Essential and he said they enabled compression of 90%, so he changed it to 100%. You can find the modded apk here https://drive.google.com/open?id=1aQ50MgaKjHwVwNDe_1LA2Q46sQl0QtqE . However, it won't let me install due to having same file name or what not. So I used a system uninstall app from the Play Store with root enabled, but it would not remove the stock camera app. No matter what I do, it does a self restart and the app is there again.
If someone figured out how to completely uninstall the stock app and install the modded apk, please share!
Do you have TWRP? Might remove it from there and then install the modded apk. Otherwise, can you remove it and then immediately install the replacement? Titanium Backup to remove it and then install the modded and then TB it to a system app?
Seamonkey79 said:
Do you have TWRP? Might remove it from there and then install the modded apk. Otherwise, can you remove it and then immediately install the replacement? Titanium Backup to remove it and then install the modded and then TB it to a system app?
Click to expand...
Click to collapse
Would you mind testing it? You sound like you know what you are doing vs me.
xterminater07 said:
Would you mind testing it? You sound like you know what you are doing vs me.
Click to expand...
Click to collapse
I won't be able to immediately, I just got this new again today, have to use it for a bit before I'll be able to unlock the bootloader and root.
Seamonkey79 said:
Do you have TWRP? Might remove it from there and then install the modded apk. Otherwise, can you remove it and then immediately install the replacement? Titanium Backup to remove it and then install the modded and then TB it to a system app?
Click to expand...
Click to collapse
Seamonkey79 said:
I won't be able to immediately, I just got this new again today, have to use it for a bit before I'll be able to unlock the bootloader and root.
Click to expand...
Click to collapse
Why do you have to use it for a bit before rooting and unlocking bootloader? Just curious
xterminater07 said:
Why do you have to use it for a bit before rooting and unlocking bootloader? Just curious
Click to expand...
Click to collapse
Because I make it a rule never to do something that can ruin warranty claims until I know something works properly first
Seamonkey79 said:
Because I make it a rule never to do something that can ruin warranty claims until I know something works properly first
Click to expand...
Click to collapse
Essential already stated rooting and unlocking bootloader will not void warranty.
xterminater07 said:
Essential already stated rooting and unlocking bootloader will not void warranty.
Click to expand...
Click to collapse
Possibly, then there's this thread - https://forum.xda-developers.com/es...sential-phone-tech-support-using-xda-t3699646
Suffice it to say, I'm going to probably use my phone the way I see fit, regardless of what a manufacturer says or another user requests It's seldom worth the risk.
The phone is so good stock Root hardly seems worth it. I read all the threads about roms and rooting and will literally gain me nothing in the end but give me unwanted headaches.
I am rooting it for the sole purpose of replacing the stock camera app with the one that is modded by Arnova
so i have galaxy s10+ sm-g975F
i rooted the phone then i flash the last firmware G975FXXUFHVG4 to relock the bootloader and get fresh clean software
so here is the issues samsung pass keep detecting the device was rooted
the second package disabler owner app cannot sit as an admin anymore giving me java errors
i flash other firmware i keep getting the same issue
i email package disabler pro asking them what the issue they give me no answer
how i can totally get rid of all the root files on my phone
UP
Simple, once you root, you lose KNOX forever.
Pass, Secure Folder need KNOX.
You can unroot by just flashing the latest firmware with Odin. But KNOX related stuff, that's bye bye forever.
PlutoDelic said:
Simple, once you root, you lose KNOX forever.
Pass, Secure Folder need KNOX.
You can unroot by just flashing the latest firmware with Odin. But KNOX related stuff, that's bye bye forever.
Click to expand...
Click to collapse
ic i really dont care about knox package disabler all what i care about
i remove the unwanted bloatware using adb command
seen_bawl said:
ic i really dont care about knox package disabler all what i care about
i remove the unwanted bloatware using adb command
Click to expand...
Click to collapse
Just so we dont get confused here.
When i say KNOX, i don't mean any sort of package disabler, i mean the KNOX security system inside Samsung phones. It's an eFuse that gets tripped once you root, and it's impossible to revert back.
Some Samsung services such as Secure Folder, Samsung Pass, WILL NEVER work even if you flash the latest official rom.
Now, if you want my two cents, debloating used to work, but not as much anymore, of course i may stand corrected, but i tested it myself without any difference in results.
Why dont you make use of the Deep Sleep listing in Device care, that way you limit an app from waking up unless you actually want too. Of course, im assuming this is all for battery gains.