Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
svyatogor92 said:
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
Click to expand...
Click to collapse
For anyone who struggle with the same issues.
Use ADB and twrp_2.8.7.7.img. I don't know why, I don't know how but this version of TWRP works.
Related
I've had trouble rooting since I updated to stock 4.4.2. Device has been unlocked & rooted before the update. It still is unlocked, of course.
I've tried using WugFresh's toolkit but that doesn't work. I've tried manually flashing TWRP (v2.6.3.1) and SuperSU (v1.8.5). They install without any errors but when I boot to system and open SuperSU I get the "There is no SU binary installed, and SuperSU cannot install it." error.
Help? Suggestions?
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
planet_x69 said:
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
Click to expand...
Click to collapse
I stopped using the toolkit after it wouldn't work. I already have the latest SuperSU installed and am using TWRP as my custom recovery. When I open SuperSU it says, "There is no su binary installed" and then closes. That's it. I can't even remove SuperSU because it's installed as a system app and while not rooted I cannot uninstall system apps.
Hello!
I have spent around 5-6 hours tonight fixing my phone. Before it had CM13 working just fine but my recovery didn't work (got an error when trying to enter recovery). I manged to solve that problem by doing lots of things I have already forgotten about now and to be honest I didn't really have any idea what I was doing as I am very new to this and have no knowledge about it.
Right now my CM13 works just fine. No problems booting. My recovery works just fine. I have CAF bootstack and the latest TWRP recovery that was mentioned in the guide. However, my SuperSU doesn't want to work properly. At first, I had to download the SuperSu app from Play Store. I don't know if that's how it is supposed to be. When I start the app it says "The SU binary needs to be updated. Continue?". I press Continue and it says "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?". I have two options: "NORMAL" and "TWRP/CWM". If I press "NORMAL" it proceeds to installing and the circle is spinning and spinning... "Installing, please wait..." After about 30 seconds it says "Installation failed! Please reboot and try again". Rebooting and trying again doesn't help. If I try the TWRP/CWM option it reboots me into TWRP Recovery but nothing happens there. If I reboot system from recovery the problem remains. I googled a bit and found some thread where they said I needed to download some SuperSU zip-file and install it from recovery. I did that but that just broke it even more giving me some error saying SuperSu wasn't installed at all, or something like that. I ended up re-rooting the device and installing bootstack, CM, and GAPPS again.
I have enabled root access in the CM developer options menu, for both apps and ADB. I have downloaded Root Checker and it says i am rooted. In download mode it also says rooted.
Is there some step I have missed? Please help me. I just want CM13, Recovery, and SuperSU to all be working at the same time. Not just pick two, like I have done before.
I had the same problem on my d802. That thing you did in development settings worked for me. Is supersu so neccesary?
EDIT: This can be marked as resolved -- I used ADB to succesfully send a reboot recovery command to the phone and it worked!
Hope I don't run into any more issues down the road.
-----------
Hi guys
In short, my LG D802 International model has lost it's ability to enter DL mode, and the recovery is also missing.
It is now running Stock Lollipop (Custom version) which I installed according to instructions with no problem
However once it was installed I then realized TWRP is no longer accessible. My next step was to then go to the Play Store and download Autorec Lollipop for LG G2 D802
https://play.google.com/store/apps/details?id=b007.autorec2&hl=en
Once that was installed I tried to install the recovery, but the app was unresponsive. The author of the app then mentioned ->If you experience unresponsive button (the button flash doesn´t work) look up this post
http://forum.xda-developers.com/showpost.php?p=65698392&postcount=797
I went ahead to uninstall SuperSU using it's full cleanup and remove function. BIIIG mistake!
That's where the problems compounded, because now SuperSU is not even working and won't let me install the SU Binaries, and the app is telling me to search forums for help
Basically: No TWRP -- No Download Mode -- No Root -- Cannot install SuperSU either!
I'm now stuck with a very unstable phone that hangs and crashes every 10 minutes. I have tried to factory reset but to no avail -- I still cannot use SuperSU.
Thanks in advance
Hi everyone,
I have some weird root on my Meizu Pro 5 with 5.1.6.0 G. Root permissions are ON in the Settings/Fingerprint and Security/Root Permission/ . I have a list of apps with Allow permission, including SuperSU, BusyBox, Root Explorer and Terminal Emulator. When I launch any of these apps for the first time I get a prompt for permission and I choose Allow.
However, Root checker does not recognize the root and Kingroot failed to root the device. When I boot device into fastboot to unlock the bootloader to install TWRP, I see “Fastboot [locked, rooted]” message. Whenever I try to use “su” command in the Terminal it returns access denied or something similar. SuperSU app fails to update the binary, although, ES Explorer has root access to explore files.
I tried to Reset to factory settings - same issue
Tried to Factory reset + Format internal storage and test root on clean device without even restoring from a backup - same issue
Tried to flash update.zip from File Explorer and from Recovery itself - firmware corrupt and does nothing.
Not sure when and what went wrong. I updated to 5.1.6.0G via terminal commands, hence I had su access with no problems.
Do you have any ideas? Now I just want to revert to the original state of the device and repeat the rooting from scratch, but unable to do so since any firmware I tried was "corrupt" and terminal does not let to use commands.
P.S. After "Factory reset + Format internal storage" in the very first boot of the device I noticed that Root access was already ON, even though I skipped the Flyme account login step. The phone is working fine - no bootloops, not bricked. Even Xposed is installed and working fine. The only issue is with the root, which appears to be incomplete.
Something similar happened to me.
Just update Flyme and check clear data. Then root it again.
Found the problem: if you are unrooted on the bootloader (check with [power] + [vol-])
And rooted within flymeos, you experience this problem.
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Atarhorn said:
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Click to expand...
Click to collapse
I might be able to help you, do you have a locked bootloader ?
I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.