Related
Hey guys,
I noticed the mention in red for the safestrap install mentioning not to try it if encrypted. Does he mean SELinux? If so, I can't disable/set to permissive no matter what I try. I've tried the app, su'ing and running setenforce, and whatever else has been mentioned and I have yet to get out of Enforcing. Is there a trick that I am missing or is all this even necessary? Thanks!
Hello there everyone, total noob here.
I have tried to "root" my S3 LTE using this method: http://forum.xda-developers.com/gal...-cf-root-cwm-recovery-ported-supersu-t1914394 (or more likely this: http://forum.xda-developers.com/showpost.php?p=45291825&postcount=306 ). Everything went great, Odin has shown a pass and it was successful while installing CWM, then I installed Supersu through CWM (only thing I did differently was putting a supersu zip file on internal storage) and that was a success too. I did everything like it said, even without plugging out my phone. After rebooting everything went down...
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Now, I dont have root AND internet access.
Other info that might me useful:
Android 4.3
Null IMEI: no
Baseband: i9305XXUEMK1
I have performed factory reset, still no use.
Any help regarding repairing wifi, getting root access or bringing back state before "rooting" would be appreciated.
Regards,
Maziu92.
Maziu92 said:
Hello there everyone, total noob here.
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
Click to expand...
Click to collapse
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Maziu92 said:
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Click to expand...
Click to collapse
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
tharinduwijewardane said:
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Click to expand...
Click to collapse
Oh, I did it, that's why it said the binary was missing. But I did it other way around:
1. I have flashed CWM like it said in second link provided in first post
2. Installed SuperSU 2.02 from zip file on internal card though CWM instead of file provided in thread (I could have installed remove-boot-recovery too, but I didnt notice that I needed that. Anyway, I did that later)
3. Rebooted and tried to turn on - supersu was still blocked by knox :/ BUT!
4. I have installed manually supersu.apk, then opened it via installator (important! Dont tap 'done' but 'run'!) and next I didnt get the "missing binary" popup but if I want to disable KNOX. Well, yeah, I do, so I tapped OK and it looped and looped... http://www.reddit.com/r/galaxys5/comments/2a92qq/supersu_stuck_disabling_knox/cisq087 found this soulution and it worked (reboot phone and start supersu again). Sorry about my short memory, but I think I needed to install supersu.apk manually again and tap disable once more time, but disabling KNOX took a few seconds.
5. And then I went to the settings in Supersu and tapped option 'install supersu into /system', rebooted and it worked fine!
5.a To make sure it really works I downloaded (via 3g ) Root checker and it said it is rooted.
So now I have root, yaay, but still no Wifi access :/
tharinduwijewardane said:
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
Click to expand...
Click to collapse
I have been using odin 3.07.
Really, It is the only way to get back wifi? Are there any other options apart this?
Nooby questions:
-will it work with my phone? It says that its "MODEM: I9305XXUFNI3" and mine is XXUEMK1.
-in the meantime I have read about efs files/folder, what are they for and should I somehow backup them?
-while flashing 4.4.4 it is possible that my IMEI will go null?
-will it be possible to go back to 4.3?
I dont want to brick it or anything, thats why I am asking.
And of course, thanks for your help, Tharinduwijewardane ^^
Edit:
Actually, I have managed to repair my WIFI connection without flashing new rom etc.... So what was wrong, you will ask? Me.
I have downloaded adblock (before factory reset) and it asked to connect via proxy, so I did. And then I have disabled it because it was blocking SuperSU along with KNOX. And my phone tried to connect with internet via proxy, but it couldnt, because of this configuration.
Found this by complete coincidence (my GF told me to check if I get connection though Chrome and it said that it cant connect because of proxy settings). It is strange that this configuration was still there, even after factory reset.
Oh well, case solved, thanks again for helping and even everyone else for checking this out^^
glad to hear u got it fixed.
:good: :good:
I'm rooted 5.1.1 and wanted to try and activate Android Pay since my bank is supported. Found some workarounds people were posting online, but they seem to not work for certain devices/roms. Just wondering if anyone here has had success.
Nope, I've tried everything short of flashing from ftf. I'm also curious if anyone's had luck.
Sent from my iPad using Tapatalk
Tried rootcloak for hiding root to Android pay?
Disable SuperSU in settings, setup android pay, re-enable SuperSU - worked for me.
Android Pay + Root?
cschmitt said:
Disable SuperSU in settings, setup android pay, re-enable SuperSU - worked for me.
Click to expand...
Click to collapse
Just tried this and couldn't get it to work.... can you give some more detail since I might be doing something wrong. Thanks! I unchecked the setting for (enable Superuser) is that correct?
Bayouland1 said:
Just tried this and couldn't get it to work.... can you give some more detail since I might be doing something wrong. Thanks! I unchecked the setting for (enable Superuser) is that correct?
Click to expand...
Click to collapse
Yes, that's exactly what I did. Are you receiving 'unable to add card' or 'could not verify system' (something like that.)
Guys i had this issue and then i flashed a PRF zip and set up android pay and it worked fine. Then i enabled xposed and all i think it came with supersu but i didnt use any root apps before setting up Android pay. But now i tried to use it and it said my card was not supported... maby my bank??It worked fine on Google Wallet. So i deleted card and was gonna re add it but now cant get past the error message again. I have rootcloak and disable device check xposed modules still no worky. Please let me know if you find a fix.
Sent from my D5803 using Tapatalk
So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT
Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0
Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk
At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.