So I flashed the OxygenOS and right after installing it told me to install SuperSU. I chose the TWRP option, (since the other option with the 'Play' button basically comes back in the same screen) and it downloads and then it does nothing. I've tried multiple times doing this same thing, it does not go to recovery on its own. So I used a zip file and flashed it from recovery. But now, it's saying the following:
"There is no SU binary installed and SuperSU cannot install it. This is a problem. If you just upgraded to Android 5.0 you need to manually re-root-consult the relevant forums for your device."
I searched for it and most of the things direct to cf-root. And most of the posts are outdated. Can someone help me with this? It sucks to install the latest OxygenOS ROM and facing such a problem right after it.
any luck?
Did you manage to solve this issue? Have the same problem
msakr1 said:
Did you manage to solve this issue? Have the same problem
Click to expand...
Click to collapse
Yes I was able to solve it. Download the SuperSU from this link and flash it from TWRP/recovery. This worked for me.
Related
I'm trying to update to the nightlies for CM11 on my xt926. I receive an error when I try to flash it, and tracking that error down, it says that my recovery isn't up to date. I tried flashing the most recent version of clockwork recovery touchthrough the ROM Manager app, but it won't take. When I go back into the app, it says I'm using 6.0.4.4, but when I reboot to recovery, it says I'm using v 6.0.2.8.
Any idea what I can do to overwrite it? Thanks in advance for any help you can offer.
EDIT: NVM, in the grand tradition of tech support, as soon as I mention the problem to someone who can help, I find the solution myself. Worked when I flashed recovery via ADB.
Oh man. I was having the same problems as you, I even tried with ADB. But i was a bit rusty and totally named my file "recovery.img.img".
Thanks for posting, it made me double check and find the problem.
danstuart said:
I'm trying to update to the nightlies for CM11 on my xt926. I receive an error when I try to flash it, and tracking that error down, it says that my recovery isn't up to date. I tried flashing the most recent version of clockwork recovery touchthrough the ROM Manager app, but it won't take. When I go back into the app, it says I'm using 6.0.4.4, but when I reboot to recovery, it says I'm using v 6.0.2.8.
Any idea what I can do to overwrite it? Thanks in advance for any help you can offer.
EDIT: NVM, in the grand tradition of tech support, as soon as I mention the problem to someone who can help, I find the solution myself. Worked when I flashed recovery via ADB.
Click to expand...
Click to collapse
I have found an easy way to update the recovery images. I just download the image I want then use a app called flashify you can find it on the play store.
Just flash with this app. I hope this helps someone who is having problems
Cool thing about this method. It's all done thru your phone.
Yesterday I rooted my nexus 5 following a guide from teamandroid website for android 4.4.2. Everything went okay and I was able to root it.
Then today I wanted to experiment with xposed framework but realized that I didn't have a recovery when I tried to make a backup. So first I tried installing TWRP through Goomanager but for some reason it would fail after the download. So I decided to install CWM touch trough fastboot. So I installed it and then did a backup. The problem came when I tried to exit. A message appeared and it said "ROM may flash stock recovery on boot. Fix?". I pressed yes, and then it told me something like "Root may have been lost. Try to get it back?" and pressed yes again. I rebooted and thats when supersu dissapear.
I panicked and tried to do the same procedure fro the guide again to get root. I repeated every single step but it wasn't succesful. I thought that maybe CWM was causing the problem so I installed TWRP trough fastboot and did the root process one more time. But again supersu just wouldn't appear back.
I really don't know what else to do. Everything in the stock ROM works fine but I just can't root my phone again. Does anyone know what I can do?
PS: Im not a native speaker.
just flash the latest supersu in your recovery, that is all. did you really search?
simms22 said:
just flash the latest supersu in your recovery, that is all. did you really search?
Click to expand...
Click to collapse
Thanks. It worked. I'm new to this so I wasn't sure what to do.
patrick.star said:
Thanks. It worked. I'm new to this so I wasn't sure what to do.
Click to expand...
Click to collapse
figured as much, rereading your post later, after first read. if you have any more questions, just ask.
Hi Guys,
I have tried many of the ROMs available however, for the most part, I get this error "error executing updater binary" in TWRP. I have also tried CWM and Philz recovery. The only ROM that installs is CM11. Does any one know what is the issue? Anyone got a solution? Thanks.
Current Recovery: TWRP 2.7.1.1
I'm the only one experiencing this issue?
Specifically which ROMs have you tried?
Transmitted via Bacon
I've tried the following:
AOSP from the Oneplus homepage
AOSP flapped
mahdi-rom
Team GUMMY
Are you checking the md5 when you download?
Transmitted via Bacon
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
bill1clinton said:
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
Click to expand...
Click to collapse
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Well, just re-downloaded AOSP from the oneplus homepage and flapped AOSP. I also checked their md5 hashes; they match. I will report back.
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
timmaaa said:
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Click to expand...
Click to collapse
Just tried to flash both, both times I get the "error executing updater binary" error. I do not have the technical expertise to try to correct this.
Anyone else with any ideas?
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
demkantor said:
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
Click to expand...
Click to collapse
The ROM that works is CM11 nightly and the one that I would like to install is pure AOSP. Are you certain that their update binary files would/could be interchangeable?
And how to do you "set to store"? I use 7zip.
I have the international 64GB. And I am not sure how to check my bootloader.
I really do apologize for my newb-ness on this matter.
There shouldn't be an issue, but of course I can't promise as I don't know what specifically is going on in your case
When you choose zip, there you will have different compression options, choose store
Try
fastboot oem device-info
Write down output here
No worries, we all are noobs in our own ways
did anyone figure this out? im having the same issue trying to install lollipop roms
Same problem here
jlinn75 said:
did anyone figure this out? im having the same issue trying to install lollipop roms
Click to expand...
Click to collapse
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
viriatis said:
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
Click to expand...
Click to collapse
I get the exact same error, as you I can only flash CM-11, strange cause I was running Euphoria OS Lollipop!
Someone must know the cause!
sad problem
doe or die said:
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
Click to expand...
Click to collapse
I'm having exactly same problem. So is this common problem or what? I had multirom and xposed framework but after uninstalling them both I get the same error again. I hope this does not happen when we are getting the Lollipop-update. Sry for bad enklish.
Anyone help?
I can't post in the http://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-12-1-oneplus-x-t3254072 where is my phone.
I done all the steps, rooted my phone, backuped with TWRP, and deleted all of the content on the phone.
I am trying and failing to install Cyanogenmod(from the tread) with TWRP.
Message that i am geting is "error executing updater binary in zip".
I tried searching for the problem but only solution is to install CM-recovery, but the link is not correct and i cant find it anywhere for Oneplus X.
I see that some people installed Cyanogen mod with TWRP but i can't find solution for my problem.
Can someone help me solve the problem?
TrutY007 said:
I can't post in the http://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-12-1-oneplus-x-t3254072 where is my phone.
I done all the steps, rooted my phone, backuped with TWRP, and deleted all of the content on the phone.
I am trying and failing to install Cyanogenmod(from the tread) with TWRP.
Message that i am geting is "error executing updater binary in zip".
I tried searching for the problem but only solution is to install CM-recovery, but the link is not correct and i cant find it anywhere for Oneplus X.
I see that some people installed Cyanogen mod with TWRP but i can't find solution for my problem.
Can someone help me solve the problem?
Click to expand...
Click to collapse
You may want to try re downloading the zip file as the download may be corrupted.
If that dosent work tell me and I will try to find another solution.
Solved, i folowed 2 sets of instructions for rooting. And installed the wrong version of TWRP. With new version it works like a charm.
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.