Database Info

[Q] cant seem to get modded recovery! wth?

alright... i was recently soft-bricked, then got everything fixed, up and running, spent a day on stock making sure everything would work correctly... it did.
This morning, i rooted, got SU installed, and setCPU running, so root is fine... but heres what happens when i try to load into recovery:
3-finger boot
-- Movi_check Start..!!
checksum confirmation nned_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!..
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk-files, please wait
Install default apk-files, finished
Click to expand...
Click to collapse
from this point i use the volume keys to select "reinstall packages"
then i get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Click to expand...
Click to collapse
_________________________________________________
...anyone have any idea what this means... or what to do?
Working with the stock blue 3e-recovery.

Looks like you need to re install modded 3e recovery. The Super Thread in the Dev section has links to the download for it. That or you can use SGS kernel flasher to flash the Froyo CWM kernel (assuming your on Froyo/stock). Also found in the Super Thread. Good Luck!

xIC-MACIx said:
Looks like you need to re install modded 3e recovery. The Super Thread in the Dev section has links to the download for it. That or you can use SGS kernel flasher to flash the Froyo CWM kernel (assuming your on Froyo/stock). Also found in the Super Thread. Good Luck!
Click to expand...
Click to collapse
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.

Ph0z3 said:
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.
Click to expand...
Click to collapse
Maybe you have to mount storage partrition? Oh nvm you did lol. Try downloading again.

Ph0z3 said:
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.
Click to expand...
Click to collapse
I've never flashed MIUI from green CWM before, only red. Maybe try a diff download link or Galnet? Are you wiping data,dalvik, and cache before flash? Also, is the zip on your internal SD card? Sorry for the 20 questions lol

Ryanscool said:
Maybe you have to mount storage partrition? Oh nvm you did lol. Try downloading again.
Click to expand...
Click to collapse
I've downloaded like 15 times now from both my phone and comp. Tried to, flash from blue, red, and green... Still says bad.
xIC-MACIx said:
I've never flashed MIUI from green CWM before, only red. Maybe try a diff download link or Galnet? Are you wiping data,dalvik, and cache before flash? Also, is the zip on your internal SD card? Sorry for the 20 questions lol
Click to expand...
Click to collapse
I don't want to flash galnet... Thats what caused me to brick in the first place... Well... Trying to flash out from there. Everyone said flash miui 11.25 right over the latest galnet and they had no issues, I bricked. So I'm trying to assess what went wrong, and get it installed.

[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

How to update to newest bootloader and install custom ROM

I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?

Bagel Bear said:
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Click to expand...
Click to collapse
Did u try using fastboot to flash it? Also dont forget to extract the ROM from the downloaded zip file.

I did not realize the ROM .zip file was inside the .zip file...
Thank you installing now. After that I just have to flash an updated recovery and then install an custom ROM, correct. You've been a great help.

Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.

Bagel Bear said:
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Click to expand...
Click to collapse
Did you install the -42 TWRP since you are now on the 4.2 boootloader?

Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?

Bagel Bear said:
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Click to expand...
Click to collapse
Did you mount the correct partition in the settings of TWRP. Try unmounting and then remounting what you need.

Even the log on TWRP says it is unable to mount anything on startup. When I try to exit TWRP it says that I am not rooted and prompts me if it can root for me. Can I do it this way?

Anyone know anything about this?

Bump

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?

Issues updating OTA - Rooted + TWRP

Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
Code:
...
....
Source: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS254 : user/release-keys
Target: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys
Verifying current system...
Package expects build fingerprint of oneplus/bacon/A0001/6.0.1/MHC19Q/ZNHKAS254 : user/release-keys or oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys;
this device has oneplus/bacon/A0001: 5.1.1/LMY48B/YOG4PAS1NO: user/release-keys
Updater process ended with ERROR: 7
Error installing zip file '@/cache/recovery/block.map
...
...
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!

Sopis said:
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Click to expand...
Click to collapse
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.

Durso81 said:
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Click to expand...
Click to collapse
hi, thanks for your reply..I did that but it did not work

Sopis said:
hi, thanks for your reply..I did that but it did not work
Click to expand...
Click to collapse
What do you mean did not work? What happen when you flashed all the stock files via fastboot?

are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..

Sopis said:
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Click to expand...
Click to collapse
Are you running stock recovery or twrp? Cause your title says twrp.

hey, I got it finally..thanks for the effort...thread can be deleted