so, I was messing around with android pay and had disabled super su - then i rebooted the phone and now it's stuck. im guessing it is bc i tried to boot with super su unticked - is there a way to fix this in twrp?
tmob s6 edge 5.1.1 rooted
ADB push super user zip or copy it and refresh super user
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.
anyone know the safest way if any to root the kitkat update.?
edit. never mind. feel dumb ass now. installed twrp and gave option to flash su when reboot from recovery!
then when phone starts, run su installer
I need some help !!
After using Supersu-me to replace Kingroot to SuperSu, everything as OK until update the SuperSu binary.
After the reboot, my phone enter in bootloop.
I tried adb reboot recovery, but no sucess.
Super SU me seems to have some problem but doing this manually by terminal emulator works for sure
after rooting my phone using king root and then i used super su me to remove the king root and install super su after thats done i opend super su it showed me a pop up how to install i selected normal and then it rebooted and boot loop and now what should i do i didnt install twrp r any thing just custom recovery coming up plz help:crying::crying::crying:
aryan varma said:
after rooting my phone using king root and then i used super su me to remove the king root and install super su after thats done i opend super su it showed me a pop up how to install i selected normal and then it rebooted and boot loop and now what should i do i didnt install twrp r any thing just custom recovery coming up plz help:crying::crying::crying:
Click to expand...
Click to collapse
(Power + Vol-) leads you to recovery?
If so, you should put the full 2.2.1-x on a micro SD, put it in your phone and flash it with the recovery.
Then wipe caches.
Kingroot method is clearly to avoid. I has been told many times !
is there anyway to re root it without having to factory reset? i still have twrp / fastboot installed
okay i update super su binaries with fastboot i think it's is a problem with root/super su not loading first when booting up. all the apps and stuff try to load first before super su and root and don't see root/su and get all crashy and hangy.
flash magisk for root