What did BusyBox do? URGENT PLEASE HELP - Galaxy S 5 Q&A, Help & Troubleshooting

Hello, I have a S5 rooted running stock. I'm pretty sure I didn't trip knox when I rooted it. So anyway I rooted my phone a while ago using odin and it was all good. See I use ANZ mobile pay, which is pretty much like android pay. Then the other day I was messing around with overclocking and undervolting and stuff, so I installed busybox for the app. Then when I went to go pay and now the app doesn't work. It says something because the device has been modified. I believe there is an Xposed module for this but I don't have Xposed because of TouchWiz. I would prefer not to have to reset or loose data. As soon as there is a stable CyanogenMod (13) release for this I will probably go over to that so I can use the Xposed module but I'm not sure when that is. So I uninstalled BusyBox and wanted to know if I could undo what ever it did. Anyway if there is another solution it will be much appreciated. Thanks

devondale16 said:
Hello, I have a S5 rooted running stock. I'm pretty sure I didn't trip knox when I rooted it. So anyway I rooted my phone a while ago using odin and it was all good. See I use ANZ mobile pay, which is pretty much like android pay. Then the other day I was messing around with overclocking and undervolting and stuff, so I installed busybox for the app. Then when I went to go pay and now the app doesn't work. It says something because the device has been modified. I believe there is an Xposed module for this but I don't have Xposed because of TouchWiz. I would prefer not to have to reset or loose data. As soon as there is a stable CyanogenMod (13) release for this I will probably go over to that so I can use the Xposed module but I'm not sure when that is. So I uninstalled BusyBox and wanted to know if I could undo what ever it did. Anyway if there is another solution it will be much appreciated. Thanks
Click to expand...
Click to collapse
If BusyBox is installed into system/xbin it will break ANZ Mobile Pay. There is an Xposed module called And Mobile Pay Root Detection. You can find the XDA thread explaining it here:
http://forum.xda-developers.com/xposed/modules/xposed-anz-mobile-pay-root-detection
It is available in the Xposed download section and the Xposed repo.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
If BusyBox is installed into system/xbin it will break ANZ Mobile Pay. There is an Xposed module called And Mobile Pay Root Detection. You can find the XDA thread explaining it here:
http://forum.xda-developers.com/xposed/modules/xposed-anz-mobile-pay-root-detection
It is available in the Xposed download section and the Xposed repo.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks man but I can't get Xposed (without deodexing the rom, which is a pain). Is there anyway to uninstall what busybox put in so ANZ Mobile Pay can't detect it anymore?

devondale16 said:
Thanks man but I can't get Xposed (without deodexing the rom, which is a pain). Is there anyway to uninstall what busybox put in so ANZ Mobile Pay can't detect it anymore?
Click to expand...
Click to collapse
You can install xposed on an odexed ROM.
Sent from my Galaxy S5 using XDA Labs

devondale16 said:
Thanks man but I can't get Xposed (without deodexing the rom, which is a pain). Is there anyway to uninstall what busybox put in so ANZ Mobile Pay can't detect it anymore?
Click to expand...
Click to collapse
If you are still rooted, you will have to delete the BusyBox files that were installed to system/bin or system/xbin, I believe. If you want to know exactly where BusyBox was installed into the system, install the app again, let it load and look at the top of the app. It shows where BusyBox is installed. Then you can use your root file explorer and navigate to the folder and delete the files that were installed.
Also, Xposed works on odexed and deodexed Rom's. Did you receive an error in TWRP when trying to install the Xposed framework?
Why not Odin the stock firmware and give yourself a fresh start?
and now a word from our sponsors....

All the above is sound advice......
But just to comment on what you said about tripping knox.......
You say you rooted via Odin.....
That means you flashed either CF ROOT and superSU or TWRP and superSU....
Both these methods WILL trip knox.

keithross39 said:
All the above is sound advice......
But just to comment on what you said about tripping knox.......
You say you rooted via Odin.....
That means you flashed either CF ROOT and superSU or TWRP and superSU....
Both these methods WILL trip knox.
Click to expand...
Click to collapse
Kiethross39 is correct. CF AutoRoot will trip the Knox counter as well as using Odin to install TWRP. I have a Galaxy S5 rooted with CF AutoRoot and with TWRP installed and my Knox counter is 0x1. Boot to download mode and look in the top left corner of the screen and check your Knox counter. I guess it really doesn't matter at this point but just for future reference it's there. Let me know how everything works out.
Sent from my shamu using XDA Labs

fast69mopar said:
If you are still rooted, you will have to delete the BusyBox files that were installed to system/bin or system/xbin, I believe. If you want to know exactly where BusyBox was installed into the system, install the app again, let it load and look at the top of the app. It shows where BusyBox is installed. Then you can use your root file explorer and navigate to the folder and delete the files that were installed.
Also, Xposed works on odexed and deodexed Rom's. Did you receive an error in TWRP when trying to install the Xposed framework?
Why not Odin the stock firmware and give yourself a fresh start?
and now a word from our sponsors....
Click to expand...
Click to collapse
Yes I am still rooted. So removing these will allow ANZ mobile pay to work. Is there an easier way to remove all of them. (yes I know there is this one tool, but I don't want to flash it). I am happy with Stock Touchwiz for now but I am waiting until Official Stable CM13 because I really like CM. Thanks you have helped me heaps.

fast69mopar said:
Kiethross39 is correct. CF AutoRoot will trip the Knox counter as well as using Odin to install TWRP. I have a Galaxy S5 rooted with CF AutoRoot and with TWRP installed and my Knox counter is 0x1. Boot to download mode and look in the top left corner of the screen and check your Knox counter. I guess it really doesn't matter at this point but just for future reference it's there. Let me know how everything works out.
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Haha yeh guys I did Trip Knox. I was checking somewhere else but idk what I was looking at. Haha thanks.

Related

[ROOT SUCCESS+ GT-N7100 [Leaked firmware] N7100XXUEMJ5 (JB 4.3) - Open Asia (OLB)

I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
how about warranty bit status in download mode? still 0?
sora9009 said:
how about warranty bit status in download mode? still 0?
Click to expand...
Click to collapse
I did not care about Knox warranty, however following your question I went into download mode. This is what I see:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (12 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
WARRANTY BIT: 0
That is all the information at present. I hope this answers your question.
Cheers.
thanks for answering.:good:
sora9009 said:
thanks for answering.:good:
Click to expand...
Click to collapse
You are welcome.
YOSEFE said:
I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
Click to expand...
Click to collapse
Sorry--but this is a bit ambiguous--
"Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5."
I follow that we Flash CWM-Supersu-v.0.99. zip in Philz Recovery[which we have previously flashed to device with ODIN]--but what is the tar.md5 bit about--surely we don't reflash Philz in ODIN, again--or, are you simply referring to the, now, on board, CWM Recovery?
Not trying to be a 'smart-alec' just not following.
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Hey, @YOSEFE, just another question--which ROM were you using before you Flashed this latest leak?
Reason I'm asking is that, I am currently on Dr.Ketan's 'hybrid' ROM which is a mix of XXMI6, and XXMJ2 plus mods taken from latest Note3 firmwares--and, it's great with many things not available to standard Note 2.
I would like your opinion of this latest leak firmware, XXUEMJ5, and how it compares--presumably it doesn't have any of the fancy Note 3 'gizmos'???
But, is it fast, smooth, clean, not buggy. etc....
BTW I'm not saying that Dr. K's ROM is not super fast, smooth, clean, etc...in fact it's excellent but, just wanting a comparison, to see if there was any good reason to Flash it.
haybill said:
Sorry--but this is a bit ambiguous--
"Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5."
I follow that we Flash CWM-Supersu-v.0.99. zip in Philz Recovery[which we have previously flashed to device with ODIN]--but what is the tar.md5 bit about--surely we don't reflash Philz in ODIN, again--or, are you simply referring to the, now, on board, CWM Recovery?
Not trying to be a 'smart-alec' just not following.
Click to expand...
Click to collapse
Philz Recovery will have already been flashed by others, however I mention it because there will be those who have not flashed anything past the firmware or ROM.
If CWM Recovery works for anyone that is fine too, but I have flashed Philz Recovery on advice somewhere in a thread. (Lazy me, can't say which thread).
edan1979 said:
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Click to expand...
Click to collapse
You are 100% correct.
haybill said:
Hey, @YOSEFE, just another question--which ROM were you using before you Flashed this latest leak?
Reason I'm asking is that, I am currently on Dr.Ketan's 'hybrid' ROM which is a mix of XXMI6, and XXMJ2 plus mods taken from latest Note3 firmwares--and, it's great with many things not available to standard Note 2.
I would like your opinion of this latest leak firmware, XXUEMJ5, and how it compares--presumably it doesn't have any of the fancy Note 3 'gizmos'???
But, is it fast, smooth, clean, not buggy. etc....
BTW I'm not saying that Dr. K's ROM is not super fast, smooth, clean, etc...in fact it's excellent but, just wanting a comparison, to see if there was any good reason to Flash it.
Click to expand...
Click to collapse
I was on XXMI6. The ROM can be a bit laggy. As someone pointed out to me, it is only a test firmware. Nevertheless, it is smooth enough for my daily use.
There are obviously no Note 3 goodies on the ROM. If those are very important to you, and considering the amount of trouble you have gone through to flash Doc's ROM, I would say keep Doc's ROM.
Thanks for the info @YOSEFE, The Good Doctor's latest work is pretty cool and definitely what I want. Sometimes we get caught up in Flash mania and need to find a good solution and stick with it.
All the best.
Sent from my GT-N7100 using xda app-developers app
edan1979 said:
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Click to expand...
Click to collapse
Thanks for your input--nice to know some of us are smart alecs.
I agree with what you have said below.
haybill said:
Thanks for the info @YOSEFE, The Good Doctor's latest work is pretty cool and definitely what I want. Sometimes we get caught up in Flash mania and need to find a good solution and stick with it.
All the best.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
how can i use efs professioal to fix 0049 imei problem?
does any body know how to use it?
OP:
R u on mj5?
Knox Disabler only disables notifications?
Thx
Sent from my GT-N7100 using Tapatalk
I'm on MJ5.
I have no knox notifications anymore.
I also used Root Explorer to search for all knox files and references to knox, I then deleted all these. My phone still works well.
No guarantees from me though. I took a risk, thankfully, my phone did not suffer any problems.
Sent from my GT-I9505 using xda app-developers app
I am just an end user like most people. I don't know anything about EFS issues.
I'm unable to comment on the question you asked.
Sent from my GT-I9505 using xda app-developers app
YOSEFE said:
I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
Click to expand...
Click to collapse
LOL , Why we need KNOX Disabler ? Installing that app ask fr root permission . And if i am rooted why do i need to disable it its already disabled.
BTW Not work on Note 7100 4.3 JB
Formingus said:
LOL , Why we need KNOX Disabler ? Installing that app ask fr root permission . And if i am rooted why do i need to disable it its already disabled.
BTW Not work on Note 7100 4.3 JB
Click to expand...
Click to collapse
You are too late in responding to this.
That method you refer to was one of the two or so of available means. Since then, Chainfire has released superuser version that incorporates a disabler or uninstaller.

Successfully rooted without tripping knox!!!!

just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
snir2 said:
just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
Click to expand...
Click to collapse
A PHOTO
snir2 said:
A PHOTO
Click to expand...
Click to collapse
Can I ask a huge favor? Can you write a simple list of steps you did. That thread is chaos from people who have 10 different devices. Like a simple
1. step a
2. step b
I don't want to screw up the device I just bought yesterday lol.
Jpfan01 said:
Can I ask a huge favor? Can you write a simple list of steps you did. That thread is chaos from people who have 10 different devices. Like a simple
1. step a
2. step b
I don't want to screw up the device I just bought yesterday lol.
Click to expand...
Click to collapse
sure,
1. downloaded the file from towelroot.com
2. installed the apk file
3. Run the app
4. the device rebooted
5. installed supersu from the play store
done....
snir2 said:
sure,
1. downloaded the file from towelroot.com
2. installed the apk file
3. the device rebooted
4. installed supersu from the play store
done....
Click to expand...
Click to collapse
Wow, Ok I thought there would be more haha. You said you were on a sm-p905, I wonder if this will go as smooth on an sm-p900. I'm on the wifi not lte version. Any guess?
Thanks for summarizing that though.
edit: seeing mixed results related to the Exynos chips from people's s4s and s5s. hmm.
snir2 said:
just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
Click to expand...
Click to collapse
Can you please tell more details about your SM-P905
AP, CP, CSC (These can be found at least on SM-P905 by opening dialer, then type *#1234#)
Kernel version (Settings - General - About device)
And for any else of you, if you try this method, report please how did it go, did you got root? did it trip KNOX flag and what firmware version you were using, thanks
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Jpfan01 said:
Wow, Ok I thought there would be more haha. You said you were on a sm-p905, I wonder if this will go as smooth on an sm-p900. I'm on the wifi not lte version. Any guess?
Thanks for summarizing that though.
edit: seeing mixed results related to the Exynos chips from people's s4s and s5s. hmm.
Click to expand...
Click to collapse
anyway from what i have read so far there is no harm in trying...... In the worst case scenario it will not work....
SM-P900 On KOT49H.P900XXUANC4
Does not work, but did not trigger knox. So no harm no fowl. Shame, really got my hopes up.
Spere said:
Can you please tell more details about your SM-P905
AP, CP, CSC (These can be found at least on SM-P905 by opening dialer, then type *#1234#)
Kernel version (Settings - General - About device)
And for any else of you, if you try this method, report please how did it go, did you got root? did it trip KNOX flag and what firmware version you were using, thanks
Click to expand...
Click to collapse
here
snir2 said:
here
Click to expand...
Click to collapse
Thank you..
Anyway, I pulled the trigger and tried this on my SM-P905, it kinda worked.. I'll post my device info later since I didn't have time for that, had to go to work just after rooting..
SM-P905
AP: P905XXUAND1
CP: P905XXUANA7
CSC: P905NEEAND1
Kernel verison: 3.4.0-1131235 (April 3 2014)
Okay then..
I installed and ran tr.apk
Then after reboot I checked recovery
KNOX Warranty Void: 0x0
System status: custom
Then I installed SuperSU (v1.94 if I remember right) from play store (and paid version also)
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
Anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Okay, as #snir2 said, I downloaded SuperSU from HERE (was v1.99r5). I unzip that and took Superuser.apk from there and installed it on my NP 12.2. After that SU updated binary using normal method like it should and everythings ok
And after all this odin mode still shows this:
System Status: Custom
KNOX Warranty Void: 0x0
Will do some tests tomorrow and if there comes anything interesting, I'll post some info..
Sent from my SM-N9005 using XDA Premium HD app
Spere said:
Thank you..
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
But anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
JUST OPEN THE Zip.
U will find the apk file inside...
milan188 said:
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
did u check with "root checker"?
at first the binaries weren't installed for me, but, when checking with "root checker" I did have root.
the supersu in the play store is not the last version of the app... u need to download it from chainfire's site:
download.chainfire.eu/supersu
then it will install the binaries
snir2 said:
JUST OPEN THE Zip.
U will find the apk file inside...
Click to expand...
Click to collapse
Thank you, that did work!!
Spere said:
Thank you..
Anyway, I pulled the trigger and tried this on my SM-P905, it kinda worked.. I'll post my device info later since I didn't have time for that, had to go to work just after rooting..
SM-P905
AP: P905XXUAND1
CP: P905XXUANA7
CSC: P905NEEAND1
Kernel verison: 3.4.0-1131235 (April 3 2014)
Okay then..
I installed and ran tr.apk
Then after reboot I checked recovery
KNOX Warranty Void: 0x0
System status: custom
Then I installed SuperSU (v1.94 if I remember right) from play store (and paid version also)
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
Anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Okay, as #snir2 said, I downloaded SuperSU from HERE (was v1.99r5). I unzip that and took Superuser.apk from there and installed it on my NP 12.2. After that SU updated binary using normal method like it should and everythings ok
And after all this odin mode still shows this:
System Status: Custom
KNOX Warranty Void: 0x0
Will do some tests tomorrow and if there comes anything interesting, I'll post some info..
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
mine says: "System Status: official"
snir2 said:
mine says: "System Status: official"
Click to expand...
Click to collapse
I'm not worried about custom status because if I'm right:
- I cannot accidentally update phone since OTA is not possible with custom status
- I can fake status back to official using Wanam Xposed
- I can get status back also by flashing stock rom again, if I need to
Does this work on WiFi only version?
Sent from my SM-N900P using XDA Free mobile app
milan188 said:
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
For those who can't root for P905 (LTE version), I have found a solution.
1. Update the kernel to NC1 or newer through Download Mode
(like this one at the bottom of OP)
2. Root with towelroot. This time if you see those wordings after pressing "Make it ra1n", it works!
I have P905ZSUANB1/P905XXUANA7/P905OZSANB1 on my tablet and after I update the kernel to NC1, I got it rooted! YAY!
BTW I get "System status: Official" in both Download Mode and under Settings, and also 0x0 for the f**king KNOX thing
One4mNoWhere said:
Does this work on WiFi only version?
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
maybe try reading the previous posts.. no it doesnt.
Sent from my HTC6435LVW using Tapatalk
Broomfundel said:
SM-P900 On KOT49H.P900XXUANC4
Does not work, but did not trigger knox. So no harm no fowl. Shame, really got my hopes up.
Click to expand...
Click to collapse
Seconded, on SM-P900 this did not work. Tried twice. Though I had my hunch it would not.

what is the best for root galaxy a3?

waiting for me arrivals [I ordered today] I am preparing to root immediately but I have doubts
- Some who have used cf-autoroot had problems [the phone start always in recovery]
- Towelroot and kingoroot on their sites do not speak of compatibility wth this device
- Framaroot? does it work? but did not in the list
suggest me because I'm afraid of brick just bought [and i love xposed]
Use kingoroot. No knox tripping.
Cf auto root works but trips the knox.
Sent from my SM-A300H using XDA Free mobile app
sam_777 said:
Use kingoroot. No knox tripping.
Cf auto root works but trips the knox.
Sent from my SM-A300H using XDA Free mobile app
Click to expand...
Click to collapse
kingoroot from pc safely?
thank you so much
Kitkat. Yes from pc. Safe. Takes around 3 minutes.
Sent from my SM-A300H using XDA Free mobile app
sam_777 said:
Kitkat. Yes from pc. Safe. Takes around 3 minutes.
Sent from my SM-A300H using XDA Free mobile app
Click to expand...
Click to collapse
many thanks again.
At this point, I hope I do not come with a phone already lollipop inside :cyclops:
sam_777 said:
Use kingoroot. No knox tripping.
Cf auto root works but trips the knox.
Sent from my SM-A300H using XDA Free mobile app
Click to expand...
Click to collapse
Hello. kingroot works on A300FU with lollipop?
Not yet for LP but hopefully it will.
Got to use cf auto root to root and with a tripped knox.
Sent from my SM-A300H using XDA Free mobile app
Would it still be possible to flash official Lollipop using Odin and knox tripped to 0x1 ? What about future versions if any should be ever released?
hannez_r said:
Would it still be possible to flash official Lollipop using Odin and knox tripped to 0x1 ? What about future versions if any should be ever released?
Click to expand...
Click to collapse
Very possible in present and should be in future.
Sent from my SM-A300H using XDA Free mobile app
hannez_r said:
Would it still be possible to flash official Lollipop using Odin and knox tripped to 0x1 ? What about future versions if any should be ever released?
Click to expand...
Click to collapse
i don't like lollipop, for various things.i hope my galaxy a3 [in delivery on the 3/8/15] has kitkat, especially for compatibility with xposed
without root and this mod, for me, my telephone is an "half" telephone
the phone arrived, I did the whole procedure with kingoroot , rootchecker and told me that I had got the root. then a message informed me that SE Linux would reactivated to restart. restart and lose the root. knox is definitely keeping me from, how should I do?
Luca TIR said:
the phone arrived, I did the whole procedure with kingoroot , rootchecker and told me that I had got the root. then a message informed me that SE Linux would reactivated to restart. restart and lose the root. knox is definitely keeping me from, how should I do?
Click to expand...
Click to collapse
I've had similar problem with KingRoot. Lost root after every reboot (I used SuperSume previously to replace it with SuperSu). However, sometimes root access was intact. Then i copied su binary from /system/xbin to /system/bin/.ext (yes, dot ext) and after that problem was gone.
hannez_r said:
I've had similar problem with KingRoot. Lost root after every reboot (I used SuperSume previously to replace it with SuperSu). However, sometimes root access was intact. Then i copied su binary from /system/xbin to /system/bin/.ext (yes, dot ext) and after that problem was gone.
Click to expand...
Click to collapse
i was tryed SuperSU app and the message is "impossible to disable knox"
i think is knox the problem.i would to try to re-root, immediatly freeze knox apps with titanium or similar, then reboot.
but with this device i very very afraid of bootlop or brick, also because we haven't a recovery for solve problems [nandroid backup save me may times with s4 mini]
tomorrow i re-try, tonight the eletric line in my city is on-off [many air conditioners busy the line!!!]
since it can be useful for other users, I notice that I was able to solve the problems. before i freeze the knox apps with uninstaller pro, then I removed manually with root explorer [uninstaller pro could not eliminate them], so I have not gone more posts by SElinux and the root is safe and full garanted. xposed ok. please not install SuperSU because was in conflict with the similar app provided by kingo
who should serve: root with kingoroot from PC > elimination knox apks> reboot
I read now that are coming to the recovery ... interesting !!!
Cf aouto root is king but if you dont like it or have problems try downloading towel root or kingroot onbthe phone or kingoroot on windows or try cyanogenmod installer.
Sent from my SM-N910V using XDA Free mobile app
Wait when i get 10 posts, then i create thread for TWRP, then flash it using odin, and flash update-supersu.zip, and that's all
I've used in the past TWRP touch on galaxy s3 mini, I really liked
but yours go on kitkat? someone has tried it? it allows the nandroid backup ?
Luca TIR said:
I've used in the past TWRP touch on galaxy s3 mini, I really liked
but yours go on kitkat? someone has tried it? it allows the nandroid backup ?
Click to expand...
Click to collapse
This TWRP works only at lollipop and I use it like every day, yes all basic functions are works but some advanced(like MTP mounting and adb sideload) is not working at all.
Works kingo root for A3-FU on 4.4.4 and has it no problems?

Bypass Safety Net root check (for Pokemon) on Lollipop?

Hello. I am running Alliance ROM, with an OH4 build and an OD5 bootloader. My phone has been rooted forever, and I can't remember which root method I used, but I know that I can ODIN an NI2 kernel and get to Safestrap. I've never gotten Xposed to work properly.
There are a lot of threads about using Magisk, but everything talks about it needing some sort of "Systemless root". I'm not sure what that means. Is that some newfangled root method that everyone is using now? I have SuperSU pro 2.78. How do I know if it's Systemless?
Can anyone decipher the Magisk thread and tell me if it will work with this phone? Or are there any other methods that will work?
Sent from my SM-G900V using XDA-Developers mobile app
i dont know if it will work with pokemon go or not but here is a way to hide root you would have to downgrade to super su 2.77 or earlier though to use this http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Magisk works if you have an unlocked bootloader. I am using it on my s5 with Pokémon. It's fairly straightforward with twrp to setup. I am on resurrection remix.
Sent from my SM-G900V using Tapatalk
Hopeful
xmoox said:
Magisk works if you have an unlocked bootloader. I am using it on my s5 with Pokémon. It's fairly straightforward with twrp to setup. I am on resurrection remix.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Can you tell us in some detail how you installed it and what version your using of Magisk. I've not been as lucky with my installs and yes I can unlock my bootloader
unitop4 said:
Can you tell us in some detail how you installed it and what version your using of Magisk. I've not been as lucky with my installs and yes I can unlock my bootloader
Click to expand...
Click to collapse
Sorry for the delay. It looks like Magisk no longer works as google updated safetynet. If I find something that works I will let you know. I am probably done with the game though.
https://www.reddit.com/r/pokemongod...kemon_go_magisk_workaround_no_longer_working/
I updated to V7 and no luck. Here is the link to instructions.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
xmoox said:
Magisk works if you have an unlocked bootloader. I am using it on my s5 with Pokémon. It's fairly straightforward with twrp to setup. I am on resurrection remix.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Maybe I am not erasing all the su files, but even with magisk installed, regardless of being on a stock rom or a custom rom, i can't get it to work.
I assumed that magisk working means that magisk is working properly and...should, in theory, allow me to play pokemon go.
I guess I'll just have to hope they repeal it, mostly because iphone has so many hacks....not requiring jailbreak.
fking joke
Su hide by chainfire works with newest pokemon go update from what I've heard
Sent from my SM-G900V using Tapatalk
[email protected] said:
Su hide by chainfire works with newest pokemon go update from what I've heard
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
but not with phh superuser? that's what i've been using since that seems to be what magisk has been pushing.
edit: also, does it work with xposed as well? at least, the systemless exposed.
actually, i don't even know if the zip i have to use for my samsung is systemless, even though it uses the same installer...
Apparently no magisk doesn't work with newest pokemon go update
Sent from my SM-G900V using Tapatalk
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268Magisk v.7 +Suhide v0.54 + Xposed confirmed working POGO on my S3 running CM13
My S5 has locked bootloader =(
Magisk requires unlocked bootloader +TWRP
Suhide requires android 6.0+
If you can get TWRP on your S5 you are good to go to play POGO
1.Uninstall xposed and Majisk and Supersu(i used http://forum.xda-developers.com/attachment.php?attachmentid=3528363&d=1446472307
2.Reflash whatever rom you are on(if using rooted rom(like cm13) reflash unsu.zip and delete the SU binaries or anything that says "su" from /system/bin & /system/xbin & /data with TWRP file browser)
3.TWRP shell, type
echo SYSTEMLESS=true > /data/.supersu
4.Flash SuperSU. only this version http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
5.Reboot to system once before going back to recovery.
6.Flash Magisk v7, then suhide v.54, then Xposed Systemless). Reboot to system.(do not flash batch)(flash each individually)
7.Install Magisk Manager v2.apk
8.Install Material Design Xposed Installer apk
9. i like the "Snorlax" xposed mod
=)
*also earlier today Magisk v6 + Suhide v.54 +xposed was working fine but i went ahead and updated to new verrsions to hopefully stay ahead of safety net
*also here is oudated thread where i learned this method...my steps slightly different and use updated links
*also some report problem with xposed systemless v86.6 ... redo all steps with v86.2
*also xposed not required for POGO (just ignore all xposed entries in setup for working POGO and root) but who doesnt want xposed =P
What would work for my stock rom on a Samsung E7 Lollipop 5.1.1? I rooted, installed GoGPS in system with Lucky Patcher, unrooted and now the game says my phone is not compatible with Pogo. I can't install Marshmallow cause there is no version of it for my smartphone.
Nanda51 said:
What would work for my stock rom on a Samsung E7 Lollipop 5.1.1? I rooted, installed GoGPS in system with Lucky Patcher, unrooted and now the game says my phone is not compatible with Pogo. I can't install Marshmallow cause there is no version of it for my smartphone.
Click to expand...
Click to collapse
Wrong forum and warez talk. No help for you!
Nanda51 said:
What would work for my stock rom on a Samsung E7 Lollipop 5.1.1? I rooted, installed GoGPS in system with Lucky Patcher, unrooted and now the game says my phone is not compatible with Pogo. I can't install Marshmallow cause there is no version of it for my smartphone.
Click to expand...
Click to collapse
Use a system app mover instead

how to hide root on my note 3

Hello
Quick info
I have Samsung Note 3 n9005 ,stock rom 5.0 , rooted with chainfire root , twrp recovery installed. I really need to hide my root from banking apps. Or at least be able to install xposed on my rom so I can use rootcloack apparentlty xposed isn't compatible with Samsung phone using Android 5.0
Any help? :angel:
delete wrong answer
Google.
apparentlty xposed isn't compatible with Samsung phone using Android 5.0
Have you asked on the xposed forum ??
I'm also looking for a way to hide my root from specific application.
I already "googled" it as Dejan Sathanas suggest, and solutions like temporary disable root are not good for me.
Thanks,
Look for app Magisk for hide root
Sent from Galaxy Note
dr_spear said:
Hello
Quick info
I have Samsung Note 3 n9005 ,stock rom 5.0 , rooted with chainfire root , twrp recovery installed. I really need to hide my root from banking apps. Or at least be able to install xposed on my rom so I can use rootcloack apparentlty xposed isn't compatible with Samsung phone using Android 5.0
Any help? :angel:
Click to expand...
Click to collapse
Search and you will find working Xposed. I had used Arter's Xposed version (number I forgot).
I used Xposed with 5.0 AryaMod (stock based ROM) for more than 1.5years.
And then install Rootcloak and things should be fine.
Look for app Magisk for hide root
Sent from Galaxy Note
Click to expand...
Click to collapse
I tried this once. Magisk then systemless xposed, it only got me in boot loop. Have you tried it yourself?
_GRIZZLY_ said:
Look for app Magisk for hide root
Sent from Galaxy Note
Click to expand...
Click to collapse
The OP clearly say "rooted with chainfire root", so how can you advice on Magisk?

Categories

Resources