Develop Bugs

[Q] Zip flashing problems

Hi all,
I'm trying to replace the font on bubor's CM11 ROM by means of flashing one on of the ZIPs available at http://forum.xda-developers.com/goo...-fontster-betas-flashable-font-packs-t2513985
I am using bubor's TWRP v2.7.1.
The problem I first encountered when trying to flash a font was the error message "Error executing updater binary" and thus the flashing "Failed". Based on the advice at http://forum.xda-developers.com/showthread.php?t=2290009 , I figured it would probably be a good idea to replace the update-binary with the one found in my ROM's ZIP, so I did that.
However, the ZIP still doesn't flash. Although I no longer get the "Error executing updater binary" message, now TWRP simply tells me "Error flashing zip" without offering me any explanation.
Please can you help with this, and apologies for the noob question. I have tried installing the ZIP from both internal and external SD. My SD's are swapped - could that have something to do with it?

- downlaoded http://www.mediafire.com/download/40x5qm44a24p0dg/CantarellFontPack.zip
- downlaoded http://dualhoki.vim.hu/bubor/dev/keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.

bubor said:
- downlaoded /CantarellFontPack.zip
- downlaoded keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
Click to expand...
Click to collapse
I'm sorry for not being detailed enough.
I tried following your steps but unfortunately the flashing still failed. I eventually got it to work after a combination of actions, but I think the most crucial one was changing the write permissions of the \system\fonts folder from "drwxr-xr-x" to "drwxrwxrwx".
Thanks for your efforts in any case, I really appreciate all the work you're doing.

[Q]Looking for some guidence (zips & updater-binaries)

Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}

Dude360 said:
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Click to expand...
Click to collapse
What is it you are flashing exactly? And which recovery are you using? Could be a problem with the recovery you use

I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.

Dude360 said:
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Click to expand...
Click to collapse
TWRP will not work with older update-binary. Could you upload an example zip which does not flash ?

This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!

Dude360 said:
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Click to expand...
Click to collapse
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.

aWFSuser said:
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
Click to expand...
Click to collapse
That error would make sense then, reverting to an older binary.
From memory, Ive used these binaries myself on:
Desire
CWM 5x, 6x
EXT4 Recovery All versions
Desire HD:
CWM 5x, 6x
EXT4 Recovery All versions
Nexus 4:
CWM 5x (I think it was)
TWRP 2.x to latest
Nexus 7:
TWRP 2.x to latest
Samsung S2
Aman Ra I think its called
Transformer 101
CWM 5x (I think)
Nook Simple Touch:
CWM 5x
OUYA:
CWM 5x
Tesco HUDL
CWM 5x
Several Cheap Chinese Tabs with CWM 5x
And as far as I know they've been used on the rest of the ROMCleaner devices as well, but have no idea about the recoveries as I was on hiatus for some of them.
Sensation
Incredible S
One X
One S
EVO 4G LTE
HTC One (m7)
HTC One (m8)
GNex
TF201
Galaxy S3
Galaxy Note II
Galaxy S4
I remember we did a LOT of testing with updater binaries to find one that was compatible with as many devices as possible but at the time none of us had access to a WFS hence why we were never able to check with them.
We we quite surprised that this one worked with everything we tested and tbh I cant even remember where it came from and Its still running on everything we throw at it!
aWFSuser said:
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
Click to expand...
Click to collapse
I was using PA at the time, same error with CM11 though.
At the end of the day, the binary can be worked around. The romcleaner binary not working is (child status 4 error) cant!
Im beginning to think its definitely a recovery incompatibility, maybe the way it has to be compiled to run on ARM6 or maybe just particular to the WFS.
The romcleaner binary hasnt changed either and is running on the above devices as well.

[Q] Error /temp/sideload/package.zip STATUS 7

Hi Everyone!
I have a Samsung Galaxy Nexus and last week after some issues I decided to format /system folder via TRWP (yes, I know...). The thing is that when I try to flash any new rom (I'm using AOKP custom rom) I get the error message of the title: "/temp/sideload/package.zip".
I've been researching and I found how to delete the 'asset' command from the file inside the rom, but I want to recover my model number in the phone so I don't have to do it everytime I flash a new Rom.
I guess there is something to modify in the system folder so asset command is ok when I'm flashing. I suppose I erased the model name after formating the system folder.
Thanks in advance for your help!

I want to add that erasing the asset command, doesn't work for me. I still have an error that aborts the installation.

[Q&A][UNOFFICIAL] CyanogenMod 12 Nightlies

Q&A for [ROM][UNOFFICIAL] CyanogenMod 12 Nightlies
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Update your recovery to supported one. See the list below.
TWRP 2.8.1.2 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Where is my root?
A: http://www.cyanogenmod.org/blog/all-about-l-part-2 (Read under "Superuser where?")
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12
cd cm12/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.

Thanks..reserved?
Sent from my ATRIX HD using Tapatalk

Home button not working. Have to use back button

Camera Bug
Camera is in the Apps not listen and it dont work from Lockscreen.
Sorry for my English and a big Thanks from Germany / EinfachAleks

No sounds.
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
I don't have camera at all
Sent from my Desire HD using Tapatalk

Great job Tested on my Inspire 4G with alpha gaps all - so all works good but one problem at startup setting after ten minutus of thinking it cant set up my GSM career and tell me to set up it next time I'll think okay wait when all google sutups done ..... go to setting /mobile wireless/operator settings ... and at this moment I have a crash. I hawe an Ukrainian operator maybe this thing cause such problem Thank you a lot for you futer job at this rom And WiFi works greate ))))

For me the Home Key just working fine...im waiting for the next Snapshot

I'm gonna download zip again and flash again. Maybe bad flash.

Doge2 and recovery
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Finnaly old bug for me.
Does anyone have same problem like I do? I can't make partitions with TWRP 2.8.1.0 partition editor! With 4ext recovey I can make partition but with TWRP I can't.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947

first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom

marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
Click to expand...
Click to collapse
I have the same error

marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
marek287 said:
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Click to expand...
Click to collapse
You'll probably need even smaller gapps. Our system partition is getting very small as the base system size has increased a lot since gingerbread. I haven't tried any gapps yet as they are irrelevant to our roadblocker issues so I can't give any recommendations.
desire hd user said:
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
Click to expand...
Click to collapse
Yes, if you are S-ON. There are some kernel related changes which are included in the boot.img so it needs to be updated too.

Mustaavalkosta said:
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
Click to expand...
Click to collapse
That was mine second throught but main goal was to anounce others that problem. I posted it to 4EXT recovery Q/A threat
http://forum.xda-developers.com/showpost.php?p=57171180&postcount=2
and recontacted (PM) to jrior001 TWRP recovery partition bug.

rom not working
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5

DOGE2 + PA GApps ALPHA1 flash succeeded
Thank you Musta and the team for great job!
http://forum.xda-developers.com/showthread.php?p=56560109
I flashed DOGE2 + PA GApps ALPHA1, and they work fine.
(cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip + pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip)
Before flashing, I made .gapps-config which containing the text "NanoGApps", and placed it in the same folder as the GApps zip.
Then, flashing has succeeded.
I didn't try "PicoGApps" option, but it will also succeed, I suppose.

matbeta said:
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
Click to expand...
Click to collapse
Install TWRP 2.8.1.0 then install the rom again. http://forum.xda-developers.com/showthread.php?t=2780164

After downloading writes: "sim card added restart your device".

bratmarat said:
After downloading writes: "sim card added restart your device".
Click to expand...
Click to collapse
Yeah, it's a bit wonky. Just hit back to skip it for now. Telephony code is still undergoing some changes.

Very good job. I wait for doge3

hello Mustaavalkosta, Great job, say thanks to you and all the dev team.
I am chinese user, i found doge 3 always crash when i install most common app.
such as baidunews, baidu market, zhihu
please check it, hope doge 4 coming as soon as possible.

D852 - Unable to flash Lineage 16 because of error 7

Hi everyone, first time here. I should say i have computing background and had no experience whatsoever with android other than using it. Now im trying to revive my old LG G3 i loved so much with Lineage 16 for android 9. I tried to follow guides found here and there with flashing to 4.4.2 to be able to root, flashing TWRP recovery, etc.
I managed to get some valuable experience on how android is working but still, im stuck in 4.4.2 because anything i've tried ended up with softbricked device or error 7 when flashing lineage 16.
The error 7 message looks like it detects my device as being model "." so it cannot continue. I've tried removing the code lines talking about the model restriction only to get another error on the unfindable updater-script.
I've flashed back to 4.4.2 with the .tot and .dll method successfully multiple times to get my G3 back in working state but now i have to admit, i am short of ideas...
I would like insight from more experienced users that successfully flash LineageOS 16 on canadian LG G3 (d852) on what are the errors i do. After 25+ hours, i need help.
Thank you in advance

Do yo follow that procedure?
https://wiki.lineageos.org/devices/d852/install

error still
I gave it another try tonight, wasnt exactly what i did before but i end up with roughly the same message :
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
E3004: This package is for device: g3, d852; this device is .
E:unknown command [log]
E:Error executing updater binaryin zip '/data/media/sideload.zip'

Ok, finally using both this guide And removing the lines of code for model, it finally worked!
Thank you very much for your time