I tried installing twrp but all i kept getting was no command so i used an auto installer and i got droidboot and twrp but now i cant install anything cause i keep getting error executing updater binary my devices codename is gone i keep failing the device check and where it should say what my device is its just blank :crying: I am using Asus zenfone 5
Related
Hi,
I recently acquired a Huawei Ascend G7...smashed screen and what not, replaced the screen on the phone and it starts bootlooping.
Booted into recovery, (already had TWRP), Tried flashing a zip file and i consistently get "Error executing updater binary". I have tried a few things that I have found on here but nothing seems to be working and its just stuck in boot loop. HiSuite doesn't recognize the device in fastboot mode. Before I go any further I was wondering any advice anyone could offer me on how to resolve this issue. Thanks
tdstt said:
Hi,
I recently acquired a Huawei Ascend G7...smashed screen and what not, replaced the screen on the phone and it starts bootlooping.
Booted into recovery, (already had TWRP), Tried flashing a zip file and i consistently get "Error executing updater binary". I have tried a few things that I have found on here but nothing seems to be working and its just stuck in boot loop. HiSuite doesn't recognize the device in fastboot mode. Before I go any further I was wondering any advice anyone could offer me on how to resolve this issue. Thanks
Click to expand...
Click to collapse
The "Error executing updater binary" may be due to your device name not listed in the zip file. In the updater-script file the first line is usually an assert, you can try to remove that line, re-zip the whole thing and try to flash again.
Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Most unfortunate. Nobody is there to help on this ?
YOu have installed bootloader version 4.18 while the latest bootloader version for Nexus 7 is 4.23 which means you have an outdated bootlaoder installed on your device while TWRP 3.1.1 is the latest version available supporting android 7.x. I am not sure but this already might cause some issues. Additionally there were some changes in handling /data/media and /sdcard/internal/
To get out of your situation you should either install a factory image with a current (4.23) bootloader (but be aware that there are some factory images out which have a buggy bootloader (!))
Otherwise you could install a working bootloader 4.23 and TWRP 3.1.1 using fastboot and and then a custom ROM based on Android 7.x
vsrkmurthy said:
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Click to expand...
Click to collapse
The exact same thing happens to me on my redmi note 9s
What can I do?
Just Open Terminal from TWRP Recovery then open `data`. now create Media folder thats all
cd data & mkdir media
This one works for me in redmi k20 pro, Now your Internal storage mount in PC
Guys, my zenfone selfie is in bootloop i guess. I am not sure cause i didnt flash any roms or something. But phone is not turning on except i plug it in with charging cable, it just keeps restarting.
So, first thing i did was, i pulled out my imp. Data from device via adb v29.0.1 . I installed twrp recovery(dont know the version of it, but downloaded from a youtube video link posted on 2017). So now i download stock rom for my device from asus site and try adb sideload, but didnt work,. It shows the error (need adb 1.0.32 or newer to sideload). So then i tried installing rom with twrp, so i pushed stock rom via adb, then tried installing rom,. But then again error comes, md5 file not found and cant install this M package (2017_ 11_ 10_ ___16:15:27 CST) L less than 20160426 build (fri nov 18 18:43:08 EST 2016).
Updater process ended with ERROR:7
error installing zip file.
So this was the error i faced, and cant find other roms for my device anymore.
These all things i learn mostly from xda yesterday.
Plus cant even go to recovery mode without charging cable,.
Guys plzz help me
Yesterday i downgraded android 10 beta to android 8 .1.0 (_WW__ZB631KL_15.2016.1810.158_20181120) but MY wifi not turning on so i decided to update again to andoid 9 and download (WW-16.2017.2002.073) but it getting problems to update. via installing through sd card getting error operation aborted , after that i pasted that zip file in internal and updating its say system update failed (3) unknown error , amd with asus flash tool also dosent work nothing happens after resume, and with adb showing my device first but after giving flash command its says no devices, how can i update now ? please help.