Related
Hi all,
I'm using the latest build of quarx cm10 image, 20130110.
I've got an app that only runs on unrotted devices (Excitor DME).
In the past I was able to use SuperOneClick 2.3.3 to unroot my defy again after having installed an update. Now however it stopped working, but it's dependened on the quarx image. In older images that functioned smoothly, now it just stops.
Superoneclick now also hands out a warning: "Automatic version check failed. Is your OS version 2.0 or higher?"
Now I'm not dependend on SuperOneClick, it was just a simple tool I used. If there's another way I can unroot my Defy, I'd be glad to learn from you.
Nevertheless I attached the window output from SuperOneClick to this post.
Thanks for your help in advance
Alex
Hi,
could someone please just point me to the right direction?
Maybe I've overseen the obvious but please give me a hint on how to solve this.
thanks a lot!
nightmare devil said:
Hi,
could someone please just point me to the right direction?
Maybe I've overseen the obvious but please give me a hint on how to solve this.
thanks a lot!
Click to expand...
Click to collapse
I dunno if superoneclick can manage with custom ROM. You can try one of the apps which can do the root/unroot from inside but I am not shure if work.
pgreed said:
I dunno if superoneclick can manage with custom ROM. You can try one of the apps which can do the root/unroot from inside but I am not shure if work.
Click to expand...
Click to collapse
If someone's interested in it, the solution for me was to use the "SuperSU" app. Installed it, removed root access inside the app, uninstalled the app and that's it. DME is now working as expected.
Also tried "Hide my root" but this didn't help at all.
Cheers!
nightmare devil said:
If someone's interested in it, the solution for me was to use the "SuperSU" app. Installed it, removed root access inside the app, uninstalled the app and that's it. DME is now working as expected.
Also tried "Hide my root" but this didn't help at all.
Cheers!
Click to expand...
Click to collapse
Hi I've tried using SuperSU and it didn't worked.
I've also made sure that the Kernel I was using doesn't re-root the device on boot.
DME is still detecting root access
I'm using cyanogenmod 9.1
Which rom are you using ?
Can please someone else help on bypass dme excitor root detection?
Thanks in advance!
Hi I'm using Quarx' latest CM10 image (http://forum.xda-developers.com/showthread.php?t=1768702)
I installed Super SU and in the propertys I found an option (sorry, unsure what it was called exactly) to uninstall root. I hit that option and it also uninstalled Super SU. Finally, DME didn't recognize any sort of root any more.
See if you can find that option as well and use it the way described. If it's not working for you, it might be something within the kernel/mod/image you're using. Maybe you should give Quarx mod a try, it's working quite well! :fingers-crossed:
HI, I have a samsung Galaxy S4 I9500 with 4.4.2, I Have tried a lot to root it, but nothing seems to work form me, I flashed the last version of cwm,
try to root using the root your phone option in cwm and when I entered the super user app, the famous binary files problem comes up, I tried installing the super us by cwm
manually and the app just doesnt appear in my phone anymore, I want to try using philz touch method, so my question is, can I just flash by odin philz
even if i already have cwm already installed, or I have to do something extra before I tried to install philz? or do you know of any method that maybe I havent
tried yet that can make the root work?
plz help, Im tired of trying different options and nothing seems to work, everytime the binary options comes up, and now I dont even have or see the super user app anymore .
I thanks in advance for your replies.
Well. You can try this method: HERE.
- COUNCIL: Make all the process explained in the link I attached u. Reflash one second time the CF-Auto-Root package if you still without see the SUPERSU icon. Good luck :highfive:
Joku1981 said:
Well. You can try this method: HERE.
- COUNCIL: Make all the process explained in the link I attached u. Reflash one second time the CF-Auto-Root package if you still without see the SUPERSU icon. Good luck :highfive:
Click to expand...
Click to collapse
Thanks! didnt work but gave me an idea, i find the super user app and downloaded, i flash by the cmw, them i went to the play store, and downloaded the sper user app, and now it works.
Dont know whym but just work out.
Thanks for your reply!
warriorand said:
Thanks! didnt work but give me an idea, i find the super user app and downloaded, i flash by the cmw, them i went to the play store, and downloaded the sper user app, and now it works.
Dont know whym but just work out.
Thanks for your reply!
Click to expand...
Click to collapse
Enjoy your rooted machine :highfive:
Download SU from play store & later check for Root access via root checker app simple
Ankit Gor said:
Download SU from play store & later check for Root access via root checker app simple
Click to expand...
Click to collapse
thats exactly what I did, and it seems to works perfectly, thanks fot the follow up
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
Was wondering about this too. Not entirely confident about what things to reflash in case things go wrong otherwise wouldve tried this.
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
reddrago said:
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
Click to expand...
Click to collapse
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
piskr said:
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
Click to expand...
Click to collapse
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
tdgillihan said:
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
Click to expand...
Click to collapse
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
ultramag69 said:
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
Click to expand...
Click to collapse
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
piskr said:
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
Click to expand...
Click to collapse
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
piskr said:
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
Click to expand...
Click to collapse
If you're running a custom ROM it may or may not work. Some are saying it does and others not. But if we're talking about the A7 here that'll be stock for now.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
ultramag69 said:
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
Click to expand...
Click to collapse
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Don't know , I just downloaded the root manager Tenfars recommended from play store...
It works fine...
Are there any new reports on this subject? I have been able to successfully install Magisk and PHH SU on a Nexus 6P , but using the identical procedure on my Axon 7 (U) does not work. I am puzzled.
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
lokissmile said:
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
Click to expand...
Click to collapse
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
lokissmile said:
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
Click to expand...
Click to collapse
that's my thought too, since magisk seems not to create a log in /cache as it should and doesn't reaveal itself via logcat it looks like it doesn't realy get executed.
The guys in the common magisk were not realy able to help, guess we have to dig more into the init.rc script / boot.img patch. But might be that it get's fixed with v7 anyway, hope @topjohnwu is able to get it done quickly (or maybe has some ideas he how to debug it more, i didn't get an answer from him in the common, probably way too crowded magisk thread - goddamn pokemongo!)
Subscribing. Would like to get this working as well.
Edit: I've gone ahead and opened up a thread so it is easy to find: http://forum.xda-developers.com/axon-7/how-to/guide-installing-magisk-systemless-phhs-t3524270
We're up to Magisk V9 now and it still doesn't work. I'm almost certain it has to do with the execution of the patched boot.img, due to the write-protected /system partition. I finally got it working by using the the method in the guide I posted.
Hey guys,
This is almost certainly a stupid question but I would be grateful for any help. I have a Nexus 6p thats upgraded to the lastest Android O beta version of OPP2. I wanted to finally go around rooting it. I have enabled USB debugging, always allowed the PC's RSA fingerprint and checked allow OEM unlocking. Nothing else has been done before, I plan on following a step by step guide that will help me unlock bootloader, install custom recovery and root etc.
I tried googling and to my surprise I could not find any root guide for this version of Nexus 6p (maybe I am just blind?)
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Woah. Cheers mate! so i just need to plug my Nexus 6p in, execute the file and click on unlock bootloader? I assume i have to install super su after that and that will be it? :3 Sorry. I know i am asking stupid questions and you are obv a pro. Also the fact that my version is opp2.170420.019 makes no difference right?
chevycam94 said:
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Click to expand...
Click to collapse
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Allrighty then, ill take the plunge real soon! Thank you for all the help Any specific why I should go with TheFlash's build instead of this one: dl.twrp(dot)me/angler/? As far as I can see it only supports F2FS which I will probably not be using.
chevycam94 said:
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Click to expand...
Click to collapse
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
chevycam94 said:
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Click to expand...
Click to collapse
UsmanPirzada said:
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
Click to expand...
Click to collapse
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
chevycam94 said:
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Click to expand...
Click to collapse
UsmanPirzada said:
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
Click to expand...
Click to collapse
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
I flashed it to 7.1.1 N4F26T using NRT and now the it has severe lag and keeps freezing and screen isnt accepting touch commands. Since this is a fresh install I assume the RSA fingerprint and USB Debuugging option has been unchecked as well? I have downloaded the official stock image of 7.1.2. Can I apply it using recovery or something?
chevycam94 said:
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
Click to expand...
Click to collapse
Okay, flashed it to 7.1.2 using recovery. Everything seems fine now. Thank god. Helpful tip to any noob out there trying to root Android O Beta 2 on your nexus 6p: dont.
Hi there,
I recently rooted my phone. I figured out various bugs and I thought everything seemed to be working fine. However, the audio doesn't seem to be working now. I've checked all the relevant settings I can find that might be a cause (the voice recorder won't work either) - but I think it must be related to the root process. In a PC I would know how to fix it- in phone I don't know. Has anyone encountered this before? any suggested solutions?
Thanks
Monkeyfuzzle said:
Hi there,
I recently rooted my phone. I figured out various bugs and I thought everything seemed to be working fine. However, the audio doesn't seem to be working now. I've checked all the relevant settings I can find that might be a cause (the voice recorder won't work either) - but I think it must be related to the root process. In a PC I would know how to fix it- in phone I don't know. Has anyone encountered this before? any suggested solutions?
Thanks
Click to expand...
Click to collapse
How did you root your phone?
GReaper-DEV said:
How did you root your phone?
Click to expand...
Click to collapse
By using CF auto root...
Link originally found on samsungsfour website.
Also have Link 2SD. This had a bug where it wouldn't recognise the SD card mount. So I had to install system app mover and app2SD apps.... went through the process and all seemed fine...except the speaker no worky. No music. No ringtone, etc.
Thanks
Monkeyfuzzle said:
By using CF auto root...
Link originally found on samsungsfour website.
Also have Link 2SD. This had a bug where it wouldn't recognise the SD card mount. So I had to install system app mover and app2SD apps.... went through the process and all seemed fine...except the speaker no worky. No music. No ringtone, etc.
Thanks
Click to expand...
Click to collapse
Simplest method to root your phone is to flash twrp and flash supersu or magisk. No problems at all.
What is the type of the ROM that u installed in your rooted phone after rooting. Is it a custom ROM or the stock?
GReaper-DEV said:
Simplest method to root your phone is to flash twrp and flash supersu or magisk. No problems at all.
Click to expand...
Click to collapse
I looked at TWRP. However, could not see the Samsung J5 2017 listed specifically - so did not run this. If you believe that this works on another device, can you specify which model no.? or alternatively provide a link to a working version?
Similarly, for the SuperSu or Magisk?
Thanks
mjhonny14377 said:
What is the type of the ROM that u installed in your rooted phone after rooting. Is it a custom ROM or the stock?
Click to expand...
Click to collapse
Just the stock...
Can u tell me what is the root manager were u using and ur twrp version ?
mjhonny14377 said:
Can u tell me what is the root manager were u using and ur twrp version ?
Click to expand...
Click to collapse
I used CF auto root which put SuperSu on my phone. I didn't use TWRP because it seems that there isn't a working version for the Samsung J5 2017....
Has anyone encountered this before?
Click to expand...
Click to collapse
I had the same problem after rooting. I tried many ways to root the phone and various firmware versions. Always the main speaker was not working after rooting. Headphones worked fine, maybe you can confirm this.
Finally I got it working.
any suggested solutions?
Click to expand...
Click to collapse
Try this rooting method: https://forum.xda-developers.com/galaxy-j5/help/guide-root-samsung-galaxy-j5-pro-sm-t3765067