I have rooted my phone with CF auto root and Odin, everything was successful but I have several banking apps that don't work with root and I have tried magisk to hide it but I don't want to mess with twrp, so I ended up uninstalling root via supersu. I thought everything went fine but when I went to Google play and tried to search for Netflix or revolut it said that my device is not supported for some reason. Also in one of my banking apps I've used a biometrics scanner and now it failed to use it and I got the message. Your device has su binary or something like that. How do I fix it? How do I completely remove root without twrp or factory reset?
Deivis16 said:
I have rooted my phone with CF auto root and Odin, everything was successful but I have several banking apps that don't work with root and I have tried magisk to hide it but I don't want to mess with twrp, so I ended up uninstalling root via supersu. I thought everything went fine but when I went to Google play and tried to search for Netflix or revolut it said that my device is not supported for some reason. Also in one of my banking apps I've used a biometrics scanner and now it failed to use it and I got the message. Your device has su binary or something like that. How do I fix it? How do I completely remove root without twrp or factory reset?
Click to expand...
Click to collapse
there's 2 option
1)Flash Magisk using twrp and hide root
2)Reflash stock firmware but you will lose all data
Roowz said:
there's 2 option
1)Flash Magisk using twrp and hide root
2)Reflash stock firmware but you will lose all data
Click to expand...
Click to collapse
Damn that sucks then, I don't want to use twrp and when I tried to install magisk via magisk manager even with boot img I couldn't make it to work, the magisk app always were on magisk is not installed, guess I'll stick to downloading certain bank apps from Aptoide or something because that works apparently. Unless someone will be able to help me with magisk installation via ota (inside the app itself) and not via twrp
Related
My note was previously rooted and flashed using cf autoroot method a long while ago. Last week I tried the ps4 remote play installation and uninstalled superuser for the remote play to actual work. Now I tried to reinstall superuser from the play store and got an unknown error -10. So did some googling and installed it through my recovery (teamwin). Its installed but wont work without an update which also gets an error but an error -110. So I went to my root checker and now its saying my root access is denied. Is there a fix for this? Thanks for any help
akareem27 said:
My note was previously rooted and flashed using cf autoroot method a long while ago. Last week I tried the ps4 remote play installation and uninstalled superuser for the remote play to actual work. Now I tried to reinstall superuser from the play store and got an unknown error -10. So did some googling and installed it through my recovery (teamwin). Its installed but wont work without an update which also gets an error but an error -110. So I went to my root checker and now its saying my root access is denied. Is there a fix for this? Thanks for any help
Click to expand...
Click to collapse
I don't think there is a qwik fix. Sounds like you lost something during the reinstall. Do you have a TWRP backup of the OS ? Try a backup restore. If not, BACK UP ALL YOUR DATA TO YOUR PC and do a factory reset. Then try and root again, if it doesn't root then I would odin flash a copy of your stock OS i.e. NC5 or NH7. Here is a link to help with that http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Thanks but did some more digging and found a beta of superuser. I installed and it worked fine. Everything says rooted again. Maybe it was just that version
Hi guys, just recently Odin'ed to stock Lollipop (DOB1), rooted by Odin CF Auto root and then installed twrp recovery also by Odin. Wiped data, cache and dalvik, the phone boots up just fine and I can use it normally but every once in a while it will pop up the Knox warning notification ("unauthorized actions have been detected"). Nothing too big, just annoying. Previously after rooting 4.4.2 via towelroot and opening superSU for the first time it offered to disable KNOX, I pressed ok and it went well. But this time launching SuperSU does not show the KNOX disabling dialog, it just works like normal (showing which apps have root access,...). How can I manually trigger SuperSU to remove KNOX?
Master619 said:
Hi guys, just recently Odin'ed to stock Lollipop (DOB1), rooted by Odin CF Auto root and then installed twrp recovery also by Odin. Wiped data, cache and dalvik, the phone boots up just fine and I can use it normally but every once in a while it will pop up the Knox warning notification ("unauthorized actions have been detected"). Nothing too big, just annoying. Previously after rooting 4.4.2 via towelroot and opening superSU for the first time it offered to disable KNOX, I pressed ok and it went well. But this time launching SuperSU does not show the KNOX disabling dialog, it just works like normal (showing which apps have root access,...). How can I manually trigger SuperSU to remove KNOX?
Click to expand...
Click to collapse
grab TitaniumBackup and freeze everything KNOX related... SuperSU doesn't remove KNOX, all it does is freeze it also.
Master619 said:
Hi guys, just recently Odin'ed to stock Lollipop (DOB1), rooted by Odin CF Auto root and then installed twrp recovery also by Odin. Wiped data, cache and dalvik, the phone boots up just fine and I can use it normally but every once in a while it will pop up the Knox warning notification ("unauthorized actions have been detected"). Nothing too big, just annoying. Previously after rooting 4.4.2 via towelroot and opening superSU for the first time it offered to disable KNOX, I pressed ok and it went well. But this time launching SuperSU does not show the KNOX disabling dialog, it just works like normal (showing which apps have root access,...). How can I manually trigger SuperSU to remove KNOX?
Click to expand...
Click to collapse
reboot and re open super su
So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.
Hello,
I have a honor 8 rooted since like one year but sudenly I cant' login in snapchat.
I heard about 'we cant log in snapchat when the phone is rooted', but I always did and never got problems before. I switxh everydays (i have 2 acount)
So i tried to uninstall phh's superuser then clear all cache, uninstall busybox reboot and verify that my phone is unrooted..(with the checker).
But still i can't login...
I don't have xposed or anything else
I wanted to try the trick with bluestack/titanium backup but it looks like we can't use snapchat with the last bluestack.....
So I don't know what to do now
If you have any ideas
Thanks
remi13014 said:
Hello,
I have a honor 8 rooted since like one year but sudenly I cant' login in snapchat.
I heard about 'we cant log in snapchat when the phone is rooted', but I always did and never got problems before. I switxh everydays (i have 2 acount)
So i tried to uninstall phh's superuser then clear all cache, uninstall busybox reboot and verify that my phone is unrooted..(with the checker).
But still i can't login...
I don't have xposed or anything else
I wanted to try the trick with bluestack/titanium backup but it looks like we can't use snapchat with the last bluestack.....
So I don't know what to do now
If you have any ideas
Thanks
Click to expand...
Click to collapse
Flash a unrooted stock rom... log into snapchat (you can make a full backup of ROM to restore to after) and then root and backup with titanium backup. Then copy titanium files to external sd and then restore the ROM backup and then snap backup
Yea but i haven't a custom rom
I jave b380 stock but maybe the problem is my boot.omg (prepatched pph's user)
Should y try to flash the b380 boot.img stock?
remi13014 said:
Yea but i haven't a custom rom
I jave b380 stock but maybe the problem is my boot.omg (prepatched pph's user)
Should y try to flash the b380 boot.img stock?
Click to expand...
Click to collapse
No. You cannot have xposed or root and many root apps. Not 100% sure but snapchat might even check selinux and safterynet
So flash complete stock ROM. (Official firmware will work) and then do it
I tried the unSU scrript from here https://forum.xda-developers.com/showpost.php?p=63615067
It said it delete phh's user then I flashed my stock boot.img but still can't login in snpachat lol
I also tried to install Magisk ( I heard it can hide root for some apps) but I have loopboot when I install It. So I flashed back my stock boot.img and it's ok
I don't know what snapchat check/detect, I don't have anything root anymore
remi13014 said:
I tried the unSU scrript from here https://forum.xda-developers.com/showpost.php?p=63615067
It said it delete phh's user then I flashed my stock boot.img but still can't login in snpachat lol
I also tried to install Magisk ( I heard it can hide root for some apps) but I have loopboot when I install It. So I flashed back my stock boot.img and it's ok
I don't know what snapchat check/detect, I don't have anything root anymore
Click to expand...
Click to collapse
Only I can tell you, which works for me: Flash complete stock and then login and reroot
Yea I guess I will do that, thinks anyways
I'll take the opportunity to update it to the latest version but I need to backup all
Whats is the best ways to update? I need to downgrade ? Or maybe I will try a custom rom like lineage
remi13014 said:
Yea I guess I will do that, thinks anyways
I'll take the opportunity to update it to the latest version but I need to backup all
Whats is the best ways to update? I need to downgrade ? Or maybe I will try a custom rom like lineage
Click to expand...
Click to collapse
Not familiar with honor devices. I wouldn't know. I'd just flash a rom for stock firmware with twrp
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
bskov said:
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
Click to expand...
Click to collapse
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
Yeah, im going to back it all up once I get home and wipe it clean to flash DFE and flash the ROM on top.
Also, I flash Magisk Uninstaller, it told me it couldn't find a stock boot image (and then proceeded to generate one), and then once I restarted the phone I went to CPU-Z to check root access and it changed to "No", so something was taking effect.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
So, I tried decrypting, but I can't, because of something with Android Pie. Doesn't matter now, I wiped every storage partition clean and flashed the firmware twice, then flashed Magisk on top, now it's working. Thanks anyway!
That prompt not showing up and magisk manager not showing in app drawer is a common issue for me even though I've never installed MultiROM on my device. You can ignore both.
Here's what I do to resolve the issue:
1) Install Magisk Manager apk.
2) Go to settings, scroll down to "automatic response", click that, click either grant or deny, then click it again and this time set it as prompt.
That should show the superuser prompt.