My Phone is Lenovo P70 running in Lollipop. TWRP recovery is installed. I've updated Supersu through playstore. Then Supersu suggested me to update binary. I've selected normal mode. It showed successful and the phone should be rebooted. I clicked reboot and I got stuck in Bootloop for 2 min. I just tried to Open recovery. But no use and the phone is not responding now. Any way to make it working.....?
Related
This is the scenario that i have encountered during rooting my htc one XL for fun. But i have encountered a problem of SuperSU binary "installation failed" when trying to update the binary.
Here i am going to share the solution that have been tried out accidentically.
Premises:
Device : HTC One XL ( i think other device may also counter this problem too when they trying to root with the ZIp version SuperSU apk.
Device's bootloader is unlocked (HTC required, i dont think samsung need this step)
recovery mode Clockworkmod is installed (i think all devices need this mod in order to install apk in the sd_card)
SuperSU apk is installed in recovery mode by install app in the sd_card
Consequence:
The superSU is installed successfully in the phone, you can see the app located in the home screen.
When you try to click in the app, it prompt it requires to update some binary files of the phone. however it will just return "Installation Failed".
Your root access is not stable.
For example:
You might contain root access by using root browser (on google play)
But you couldn't "su" in the linux terminal emulator (on google play)
Also you couldn't "su" by using android shell in the android sdk tools's .adb shell
Solution:
Below is the steps i performed and it is worked.
Update the latest version SuperSU in the google play
Afterwards, it will prompt the binary update screen again
Choose the Txxx/CWB instead of Normal
My device cannot automatically boot up the recovery mode, thus i manually started the recovery mode
binary will be updated when you go in recovery mode
Importance Note:
Actually I am not success in point 5 (binary will be updated when you go in recovery mode).
It means that the binary doesn't update when SuperSU is still the latest version (updated on google store).
and if you have also encountered this circumstance. reboot in the phone again, in the latest version of SuperSU, selected update binary by Txxx/CWB, and then uninstall the latest version of SuperSU by normal apps uninstallation (you can never able to uninstall the old version SuperSU in the phone normally because its installed in the recovery mode).
Now you can boot into the Recovery mode, it will update the binary automatically, And you can grant the actual root access for your phone after reboot the phone again.
Do you think this will work for the Note 3 running 4.4.2 ? for some reason as of now on verizon note 3 there seems to be no fix for the supersu not updating binary on the new kitkat 4.4.2 im rooted using towelroot i let it update the binary once and i never opened it again to avoid it asking me to update again then failing ... so to avoid uninstall and reinstall i just let it do its magic once and never touch it again... it will update the first run but once you reboot .. youre f you also want to make sure you delete the file su in system/xbin/su then uninstall and install fresh to get this to update you binary .. but you can never open it again or it will ask to update and fail ... however all apps asking to grant permisson will be granted so apon screen pop up and your prompt to allow .... but i am however going to try this just dont know if i should choose the txxx/CWB as apose to normal
No Luck to me too.
I did what the top comment said but Super SU still says it needs to update binaries. I am using Version 2.65.
I am using one Moto E 2015 4G (XT1524) European Edition, I have unlocked the bootloader, and managed to flash the TWRP recovery image via fastboot.
Before I flash the CM12.x ROM, I need to install SuperSU.zip, however, when I entered the recovery mode, only "no command" shows up, I can do nothing about this situation.
I tried to install SuperSU through Google Play Store; when I open it, it says "There is no SU binary installed, and SuperSU cannot install it........ If you just upgraded to Android 5.0, you need to manually re-boot ...."
Following what it says, I re-booted the phone, but the SuperSU app still shows the above message when I open it.
What should I do right now? Thank you!
It sounds like your root didn't take. The "no command" recovery is stock. And, if su binary isn't installed, it generally means root didn't take.
Sent from my MotoE2(4G-LTE) using Tapatalk
I have rooted my phone got supersu app but when I am opening that app its asking to install su binary either by normal or recovery mod. When I click on normal mod the installation gets failed. I need ur help! !
Choose Recovery mode.
Or do it manually. Download the latest SuperSU ZIP, reboot in to recovery, and just flash it there, it is the same process.
Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Longlast said:
Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Click to expand...
Click to collapse
You should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
thisisapoorusernamechoice said:
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.[/QUOTE
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
Longlast said:
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
thisisapoorusernamechoice said:
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
Click to expand...
Click to collapse
when i run supersu a message appear that there is no su binary installed, and supersu connot install it. if you just upgrade to android 4.3 you need to manually re-root.
the current version is 4.4.2 bn3
I successfully flashed TWRP 3.4.0.0 and flashed patched image using magisk, the phone was successfully rooted and I used it as well.
I downloaded SUPER SU apk but showed up "SU binary occupied" so I downloaded an older version that asked me to flash it using either TWRP or without TWRP, firstly I chose without but it failed, so when I chose with TWRP the phone rebooted and still stuck on realme logo!
Tried many solutions but failed, so I hope anybody could help me.
NOTE: realme logo stays for about 70 seconds then it turns into FastBoot mode automatically.
*Tried this one
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
But in vain