Database Info

[Q] How to get OTA 1.78.401.2

For the few days ive been trying to get the OTA to install correctly.
I have seen other people talking about this, and i have tried all i could find about this problem.I
m not sure if im posting this in the correct place, sorry if nok!
I did find out its because of the used custom recovery that it wont install.
So using the allinone tool i put the stock recovery on, i believe with succes.
And i had also installed the ota rootkeeper app (not sure why)
But the OTA keeps on reporting errors when installing
assert failed apply patch check /system/app/phonesky.odex (long numbers)
E: error in internal sdcard/download/ota-ville u htc europe 1784012-1.53401.2 release-numberrapskwje.zip
status 7
aborted
I tried (in stock recoverymode) installing a zipfile i found somewhere which was the 1.78..update (I think) but that also gave errors, i cant find a ruu for 1.78, so cant try that.
Is there a complete list of things you have to do to get this update? and if so can someone help, thanks.

Lacuna666 said:
For the few days ive been trying to get the OTA to install correctly.
I have seen other people talking about this, and i have tried all i could find about this problem.Im not sure if im posting this in the correct place, sorry if nok!
I did find out its because of the used custom recovery that it wont install.
So using the allinone tool i put the stock recovery on, i believe with succes.
And i had also installed the ota rootkeeper app (not sure why)
But the OTA keeps on reporting errors when installing
assert failed apply patch check /system/app/phonesky.odex (long numbers)
E: error in internal sdcard/download/ota-ville u htc europe 1784012-1.53401.2 release-numberrapskwje.zip
status 7
aborted
I tried (in stock recoverymode) installing a zipfile i found somewhere which was the 1.78..update (I think) but that also gave errors, i cant find a ruu for 1.78, so cant try that.
Is there a complete list of things you have to do to get this update? and if so can someone help, thanks.
Click to expand...
Click to collapse
Retry to install Rootkeeper or u can do it later
Use this tool: [TOOL] HTC One S All-In-One Toolkit V1.0 (find at Android Development). Boot to fastboot mode then reflash the "STOCK RECOVERY"
After that go to Setting-About-Software Update and install it with the choice "install now".u get it.
if u didn't use RootKepper,just re-root again with the same tool.
Have Fun.

After that go to Setting-About-Software Update and install it with the choice "install now".u get it.
Thanks, but I dont undersstand your answer.
Are you saying to : do the OTA update just after flashing the stock recovery?
Thats exactly what i did.

That was exactly what i did too.
so u can try re-flash the shipp Rom at "[ROM]Ville Shipped ROM Collection" (Thread of Football, at Development).then do it again.
Coz i think the Problem is at ur Stock Recovery.mb there is smth not right there...
i did exactly what i wrote and it worked for me.
Good luck!

Ok, i will try :
using the europe 1.53 ruu(from post from "Football")
then use the all_in_one tool to put the stock-recovery back again
then try the OTA again
i will let you know later on,..thank you

I ran the europe 1.53 ruu(from post from "Football")
After a while it said error 155 image update error, get correct image
I still have no idea how to get the 1.78 update,
Can anyone help please?
=====> Never mind, luckily today football released a 1.78 basis rom which does work for me

[Q] [TF700] Root not working after updating Cromi-X to 4.7.0

Hello there ! Newbie here.
I've just updated my Asus TF700T to Cromi-X 4.7.0.
After the installation, I noticed that it was not rooted anymore. When opening SuperSU, an error message appears: "There is no SU binary installed and SuperSu cannot install it, it's a problem."
I tried afterwards a fresh install of Cromi-X, but the problem was still there.
Then I tried to execute the Motochopper script, which appeared as successful, but the error message is still there.
Do you know what could be the solution for this problem ? Without root, I cannot execute applications like lagfix, titanium backup and full screen, which is annoying.
Thanks in advance for your help !
And sorry for my english (french talking here !)

Sounds like the ROM didn't flash properly. Flash it again please.

sbdags said:
Sounds like the ROM didn't flash properly. Flash it again please.
Click to expand...
Click to collapse
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.

Soralito said:
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.
Click to expand...
Click to collapse
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.

sbdags said:
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.
Click to expand...
Click to collapse
Hello, I can't find any log file in the folder of my zip file... What would be the name of this log file ? Maybe I can find it somewhere else...
I have re-downloaded the rom from another source and try a new flash tonight.
Anyway thanks for your help ! (I just noticed I was talking to THE developer of Cromi-X Sir, it's an honor )

It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !

Soralito said:
It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !
Click to expand...
Click to collapse
You are welcome - glad you got it sorted

Hey there guys and gals. Newbie here. I've read this thread and I am having the same issue as the original poster. I don't really understand what was said here but this is my question: if I downloaded the motochopper root app to the tablet and opened it from there and did the root right from my tablet would the root take hold then? I have an Asus TF700 by the way.

Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891

berndblb said:
Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Should I factory reset to stock software first or just go ahead and run the new root software?
---------- Post added at 03:32 AM ---------- Previous post was at 02:47 AM ----------
reubdog30 said:
Should I factory reset to stock software first or just go ahead and run the new root software?
Click to expand...
Click to collapse
It worked!!! I'm good now. Thanks for your help!!

[Q] Can't update CWM Recovery

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.

error executing updater binary

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?

Can't root after installing OxygenOS

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.