hi friends... whenever i try to update my phone from S058 to S059. after downloading update it does not proceed further. it reboot in recovery (TWRP) { I dont know what to do next}. and when i downloaded the zip file of OTA and tried to update through TWRP it shows an error msg : "Error executing updater binary in zip. . . . . " please help me..
rkhatana said:
hi friends... whenever i try to update my phone from S058 to S059. after downloading update it does not proceed further. it reboot in recovery (TWRP) { I dont know what to do next}. and when i downloaded the zip file of OTA and tried to update through TWRP it shows an error msg : "Error executing updater binary in zip. . . . . " please help me..
Click to expand...
Click to collapse
Try to flash stock lollipop recovery and then try.... bcz lollipop update needs stock recovery only. Not this twrp
Related
Hello,
I have a perfectly working phone, that doesn't want to enter into download mode. From what I've seen in other threads, it seems to be related to the laf partition. Another user with a similar problem gave me this link:
http://downloads.codefi.re/shelnutt2/g2/fixlaf/
I downloaded the version for my device (D802) but TWRP refuses to flash it:
"assert failed: run_program( " /system/bin/sh" , " /data/local/tmp//revert_aboot.sh" ) == 0
E : Error executing updater binary in zip ' /sdcard/fixlaf_d802.zip '
Error flashing zip ' /sdcard/fixlaf_d802.zip '
Updating partition details...
Any ideas? I want to go back to a 100% stock rom, I need Download mode for that.
Thanks!
CaraMuuu said:
Hello,
I have a perfectly working phone, that doesn't want to enter into download mode. From what I've seen in other threads, it seems to be related to the laf partition. Another user with a similar problem gave me this link:
http://downloads.codefi.re/shelnutt2/g2/fixlaf/
I downloaded the version for my device (D802) but TWRP refuses to flash it:
"assert failed: run_program( " /system/bin/sh" , " /data/local/tmp//revert_aboot.sh" ) == 0
E : Error executing updater binary in zip ' /sdcard/fixlaf_d802.zip '
Error flashing zip ' /sdcard/fixlaf_d802.zip '
Updating partition details...
Any ideas? I want to go back to a 100% stock rom, I need Download mode for that.
Thanks!
Click to expand...
Click to collapse
Up!
For anybody interested, probably we will get an answer here, we will see!
https://plus.google.com/118339857242349748059/posts/2t2TMncsokV
Do it on your own responsibility! if you follow this guide properly u will be on the safe side
HI
I found a bug in GT-i9505 OB8 Update Lollipop
Suddenly Rebooting again and again or Stuck On Samsung Galaxy S4 Logo !
I Dont Know How But My Partitions Goes Wrong Or My Permissions !
When I Open Recovery
I see Error Like That :
Code:
unable to mount /efs
unable to mount /cache
unable to mount /system
unable to mount /data
And Bla Bla Bla ..
Solution :
1 . Download ODIN !
2. Download Stock Rom [Latest Lollipop Update] !
3.Flash Stock Rom Via ODIN
Please Ensure That
----------------------------
3.1 NAND ERASE ALL √
3.2 Re-Patriation √
---------------------------
4. Flash TWRP Recovery Via ODIN DOWNLOAD FROM TWRP SITE .TAR File Of Any Version !
5. Open Twrp Recovery
6. Wipe --->> Format DATA ----> YES
7. Advance ----->> FIX PERMISSIONS --->> SWIPE
8 REBOOT ! [Enjoy]
If This Post Helps You Then Press Thanks Button
This Is My First Post ... !
Model: A501CG -
Rooted/Unlocked: No
-----------------------------------
Hello . I will describe my problem. It was the stock rom lollipop V .78 in Zenfone 5. I manually update to the V .87 . So I entered the droidboot and first installed boot.img v .87 and then recovery.img v .87 .
After that, I installed by adb ( sideload ) the stock rom v .87 lollipop . There was an error at the 54 % ( blablabla ) . So the update did not work and my zenfone returned to V .78 .
The problem is that my zenfone 5 now lost access to droidboot and recovery is the version v .87. I can only access the recovery mode. I can not install anything via adb and not to downgrade . Always appears the error: Signature file validation .... aborted ... ( blablabla ) .
The interesting thing is that the smartphone is running on stock rom v .78 even without access to droidbot and wrong recovery .. Has anyone experienced this ?And does anyone know if you can reverse this situation ?. Any developer can advise me ? Thank you.:good:
Sorry for my English.
Can you flash the .87 through adb again? You shouldn't flash the recovery and the droid boot from .87 in the first place.Just flash the .87 via adb and the next time you acess the recovery agin it will be updated from 78 version to .87
ChristopherXI said:
Can you flash the .87 through adb again? You shouldn't flash the recovery and the droid boot from .87 in the first place.Just flash the .87 via adb and the next time you acess the recovery agin it will be updated from 78 version to .87
Click to expand...
Click to collapse
Unfortunately we can not go back to .87 . When the error occurs : Verification signature failed ... ( blabla ). Thank you.
rodrigo.fac said:
Model: A501CG -
Rooted/Unlocked: No
-----------------------------------
Hello . I will describe my problem. It was the stock rom lollipop V .78 in Zenfone 5. I manually update to the V .87 . So I entered the droidboot and first installed boot.img v .87 and then recovery.img v .87 .
After that, I installed by adb ( sideload ) the stock rom v .87 lollipop . There was an error at the 54 % ( blablabla ) . So the update did not work and my zenfone returned to V .78 .
The problem is that my zenfone 5 now lost access to droidboot and recovery is the version v .87. I can only access the recovery mode. I can not install anything via adb and not to downgrade . Always appears the error: Signature file validation .... aborted ... ( blablabla ) .
The interesting thing is that the smartphone is running on stock rom v .78 even without access to droidbot and wrong recovery .. Has anyone experienced this ?And does anyone know if you can reverse this situation ?. Any developer can advise me ? Thank you.:good:
Sorry for my English.
Click to expand...
Click to collapse
haha i told u what u shld do on zentalk website....
[email protected] said:
haha i told u what u shld do on zentalk website....
Click to expand...
Click to collapse
haha, thaks again.
Hi Developers.. Im new to this Forum site..
Im21.40.1220.1794 for WW Using Asus ZenFone 2 Laser (ZE550KL).
Lollipop 1.17.40.1234.. I can't upgrade L to MM. I don't know why..
Here is the problem.. I cant upgrade with OTA.. files are download, when i install the firmware the phone reboots normally..
Then i try to upgrade with Fastboot mode.. even cant be upgrade in sideload.. I think my phone has some problems on bootloader..
TWRP Method Flashing only working on my device.. But i don't have Marshmallow TWRP files.. So i need a MM firmware ( 21.40.1220.1794 for WW) with TWRP flashing method.. Plz help me.. ?
You have tried with update from sdcard.download lastest versione of firmware and rename .zip in update.zip and put the firmware in sdcard,go in recovery and select zip from sdcard and select update.zip.sorry for my bad english
Okay.. Bro.. I'll try..
Couldn't update ASUS ZenFone 2 laser 550kL
Facing the same problem
Baseband version - 202c10_10.0.0_160602
Build no. - WW_21.40.1220.1708.20160621
First I tried to update automatically through OTA update but failed.
Downloaded file from ASUS website (build no. 1877 ) and tried to do it manually by placing it in the root folder but still that failed.
ERROR - E: failed to mount / asdf ( invalid argument )
Please help with updation using simple method
flash stock recovery first if you want to do Gabbro16Hz method.
3gb ram varient of ze550kl has this kind of problem.
You need to download latest firmware from the asus' site. Place it in the sd card.
Enable usb debugging in developers' setting. Then boot your phone into fastboot mode. Connect phone to pc via cable.
Then put the tools.zip file in the pc and unzip it. Open that folder. Run 'flash all.bat' file. This will flash stock recivery to your phone.
Now boot phone into recovery mode. Select 'apply update from sd card. Select the firmware and flash. Then reboot. Work done. Your phone will have latest update.
Hello GUYS.. So I was on the latest nougat update and I wanted to try CM13 on my P9 Lite VNS-L31 but someone told me that I need to downgrade to 6.0 before I install CM13 So I downloaded oeminfo and 6.0 rom from update finder.. and first I wiped system, data, cache and dalvik cache..okay so now I have no os installed.. Then I tried to install oeminfo with TWRP.. But it can't mount product/vendor/version (invalid argument) And I was like wtf does this mean? so I flashed stock rom image with fastboot again.. it said it's installed but twrp says no os is installed.. ugh I just tried everything to fix that..I tried to extract vendor.img and product.img and flashed them from fastboot.. But it said command not allowed and still twrp gives me the same errors when i try to wipe data or install system.. I asked people on another site and they told me I should install stock boot and recovery images from twrp and install system with 3 buttons method.. So I did but it said failed.. And when I wanted to flash twrp again the bootloader was locked wtf? so then I tried to unlock it again it asked me if i really wanna unlock it and I choose yes..the phone rebooted and I got this
Error Mode
Attention
Please update system again
(Android Logo)
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
now I can't boot into recovery or fastboot it just stays in this screen
I tried to install system with the 3 button method but it just won't boot to anything.. I also tried to connect the cable and boot to fastboot..But it. just shows the huawei logo and then goes back to error mode.. please tell me what I should I do now?
hi, did you solve this issue?
You should've just downloaded the rollback package and stock mm rom. Flash the roll back package and then the mm rom in eRecovery. Btw if you are going for meticulus Cm13 rom then ot has been removed from his website and in the beanstalk rom of meticulus when you call someone or someone calls you then the UI restarts. Thats a major bug