I rooted my phone and installed TWRP recovery. When i try to flash a cm 10.1 (LOKI) i get the error: Error executing binary in zip ' /external_sd/cm-10.1 -20130524-N
What am i doing wrong?
This error sometimes occurs while flashing a custom ROM on new devices. i dont know why but i know i've seen it happen to phones, tablets, etc of all brands. it is commonly fixed by downgrading to the previous/an older version of twrp. in this case, i dont know if an earlier version for the s4 exists as i use cwm only. i would imagine it would flash in cwm, but i would also imagine you would prefer to stay on twrp. just passing on what i know. cheers
Related
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319
Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.
I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.
I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
You probably need to update to the latest TWRP version. Use the TWRP link in my signature and get the latest version in the "mako" folder.
Use fastboot to flash it, use the command:
fastboot flash recovery twrp.img
(replacing twrp.img with actual file name)
If you don't know how to use fastboot, use the 3rd link for guide on installing custom recoveries.
dreammaster252 said:
I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
Click to expand...
Click to collapse
had the same error and resolved it like this:
installed ROM Installer vom play store
installed cwm, and then twrp again from rom installer.. worked perfectly!
BUT WHATCH OUT! i think the error you get is called "error 9".. or something like that, it appears, when you try to install a zip, and the updater-skripts cancels the installation process, e.g., because it is not hte right zip for your phone!
so look at first, if you have the right zip downloaded
Hi i'm trying to flash Albe95 S6 PORT 3.5 on my i9505 using the latest TWRP. When I try to flash it, I get the error "error executing updater binary in zip". I have done a full wipe and have re downloaded and tried to flash again but to no success, any one have any ideas on how to fix this? I have also tried CWM
What version of TWRP? 2.8.7.0 is the latest.
i9506
Strephon Alkhalikoi said:
What version of TWRP? 2.8.7.0 is the latest.
Click to expand...
Click to collapse
I have the same problem
Mobile Samsung i90506 5.1
Installed twrp 2.8.7
And flashed supersu 2.4.6
I try ed 2 times
Help
hello,
Same problem here with i9500 and latest TWRP. In a OnePlus thread: ..."simply changes the "name" of your device for it to be compatible with the ROM you flash. Most ROM's have the codename for OPO specified as "A0001", while the phone itself reads as "bacon".
So when flashing in TWRP if the ROM's target codename does not match the name given by the device it reads it as incombatible device and cancels the flashing. That flashable zip to my knowledge fixes it so the device now reads as A0001 instead of bacon and then it matches the code string in most ROMs so there is no error when installing. Thanks to @4nlimited3dition for the explanation" simply changes the "name" of your device for it to be compatible with the ROM you flash. Most ROM's have the codename for OPO specified as "A0001", while the phone itself reads as "bacon".
Im using twrp 3.0.3-0. i get error 7 When i flash lineageos but other roms dont. How can i fix it?
S7 edge with exynos
did you find the fix?
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.
Click to expand...
Click to collapse
More info here: https://forum.xda-developers.com/showthread.php?t=2522762
Ty. I fixed it by wiping everything the second time, tho.
I have seen some people suggesting to update the firmware(bootloader?)(not quite sure) as an alternative to removing the asserts. What is your opinion on that?