Unable to ROOT OS11 - OB3 - OnePlus 8 Questions & Answers

Hi
I am unable to ROOT the OB3. tried patched boot image from the forums and also tried manually patching the boot.
Magisk manager shows status as N/A.
tried multiple times.
Please help.

OK so i have no clue what happened. but one of my banking apps reported I have root and so cannot work.
Then installed Root checker and i got request for root access.
Been trying from yesterday to get root and suddenly without clue its working.
the Magisk manager also got installed with 'SM' name as i usually name it (no idea how it knew) and its working.
Still scratching my head.

Related

[Resolved] [Q] Rooting lost

Hello,
Until today, I was using the v18 of the Omega ROM on my Galaxy Note 2 and today I installed the v26. But the Wifi was bugging, so I tried to flash the fix from CWM. I didn't manage because it didn't find the file and when I quitted CWM, my root has been disabled. Since that, I don't manage to root it again, I have done like many tutos but each time, even if the software like Odin was telling me it was OK, when I launched SuperSU, it tells me that no SU Binaries is installed. I have tried to uninstall/reinstall, I have also tried with Framaroot, but it tells me to try with another exploit, but there is only one...
I don't know what to do, I can't back up my folders and apps with titanium backup without root... Do you have a solution ?
EDIT : I have installed again CWM recovery, and then the Omega ROM. And everything is good now.

root 4.4.2 ??

hi all
i installed the 4.4.2 kitkat on my device the indian version
i tried to root it but no luck
i tried this way in this thread
http://forum.xda-developers.com/showthread.php?t=2102677
first of all everything seems fine , the supersu installed and can give root permissions
but after a while it can't give permissions
just like there is no supersu
it says the app gets the permission but it can't get it
i dont know what is the problem or 4.4.2 still not get root ?
and if there is another way to root let me know
thank you
more than 90 views and no respones :crying:
ok it dosen't matter. i figure out what is the problem and i solve it :laugh:
the problem was because the KNOX is installed in the new 4.4.2 kitkat update But it was hidden and you cannot find it in the app drawer
and if you check the app manager in the setting you will find it as KSML
KNOX prevent the root from working and the option that appear when i open the SuperSu app to disable the KNOX seems to be not effective
i tried a lot of things to remove it but i end up with fails every time :crying:
the sloution seems simple just remove knox and you will be ok and the root will works great
but
the problem was how to delete it with no root
i noticed in my device after i flash the root file and install an app that require root the root works on this app just for less than 10 mintues and then dosen't work at all
- so i flash the kitkat room again and turn on the device
- i download the root explorer app from the google play
- root my device
after rooting, the supersu app give force close but i went to google play and update it from there and it works fine
- lunched the root explorer and give it root permission (for me it can take the permission)
- searched about KNOX
- then deleted everything related to KNOX
- again search about KSML and delete it as well
and after that everythings goes right
a installed more than 3 apps that required root and all works flowlessly
and the root cheacker app finally says i succesfuly root my device (before was say a havent rooted my device)
damm it looks easy but it freaks me out to made the root working
KNOX really is a great saftey app but very annoying in matter of rooting
i hope anyone face my problem to try my way and it could works
thanks to me to reply me
Another thing I noticed
the root dosen't work if you change the language from English.
I don't know why???
After update to official 4.4.2, I just flashed CWM 6.0.3.6 with Odin, restarted in recovery mode and installed UPDATE-SuperSU-v2.01.zip in CWM.
Reboot tablet and start SU app; the app detects KNOX and asks to disable it. Just answer yes and you are ready in less than 5 minutes.
I must admit I first used Phil_Z recovery and then SU-app hung when disabling KNOX. After switching to CWM is worked right away.
I have N8010.

Root not working anymore.

I've rooted my phone a month and a half ago and today I noticed that none of my apps can acquire root. SuperSU says that there's no SU binary installed and it can't be installed.
What should I do? Do I just root again? Is the process different than it was for the first time?
And why did this happen?

[GT-I9195] Unable to Root! Tried almost everything!

Hi there guys!
I do have a s4 mini lte and for the past week I've tried almost everything when it comes to rooting my mobile.
THe first thing I tried was Kingoroot and then Kingroot but it looked like it wasn't possible to root it using them.
Then I installed CWM with Odin(I tried with TWRP but got Red error on Odin). I flashed the zip with CWM and when the phone booted up, it looked for updates for 5-10 secs and then I opened SuperSU (it was installed) it kept saying that there were no binary found.
I had to download the latest version of Supersu (2.79) and when I tried to flash it, I got "You lost root access"
FIx it? Yes/No
I pressed no since it was suggested on other forums to do so, but then I still got the same problem with SuperSU ( no binary found)
I did wipe cache,tried also with factory reset,disabled and then re-enabled supersu,updated it from playstore, but still no root.
How the hell am I supposed to root this stupid phone?
Thank you

Finally root and TWRP stuck...

I have the ZTE 2050 which has the MT6771 chipset. It seems to well developed in Russia for some reason. The rest of the world hasn't really done much with it. After several battles with root and recovery, I finally got them both to stick. I downgraded the phone from Android 10 to the earlier Android 9 and have TWRP 3.4.0. Still have issues though. As soon as TWRP starts, it ask me for a password. I have tried using no dm verity force encrypt.zip, and I have a patched boot.img from Magisk. When I flash the no dm zip, the phone stays stuck on the boot screen. And the one time it it finally passed that screen, the phone told me the phone could not be decrypted. Another issue is that when I open my root file explorer and try to alter, copy, or do anything within that file system, the phone freezes and needs to be rebooted. I can use Magisk modules to do certain things, but not all that I am trying to do is made into modules. Even simple things like adding to my build.prop. Also, after debloating, when I try to open and read any file, no matter what file manager I use it tells me that my web viewer is no longer installed even though it is. Can anyone tell me what I may possibly be doing wrong in all of these situations? Thanks in advance.

Categories

Resources