Database Users

verygreen's agnostic bootloader - edify or amend?

is verygreen's size-agnostic installer - the recovery bootloader that's in there -- is that using amend or edify scripting? The "reboot into recovery" doesn't have any interface for me - it just runs any cm, "update-*.zip" files if it's in the partition where uImage/uRamDisk are.
I'd like to know if it is using amend or edify, for when i want to cook up my own stuff. What bootloader is being used there, anyhow? Is it a flavor of CWM or something?

[Q] [DEV] Error during flashing due to update-binary

I'm trying to build my own custom ROM, I downloaded the original acer 3.1 update and I made some mods, like zipalign, remove apps, add su, busybox ecc...
I edited the updater-script according to my mods, I rebuilded the zip and signed it.
When I try to flash it in cwm i get (Status 0) error.
If I put an update-binary from an other coocked ROM I get (Status 6) error.
How can I build my own and working update-binary?
I'm working on a Windows machine.
I use notepad++ to edit the updater-script.

Need Help with updater-script

Hello everyone. I have been using championswimmer x10s ROM since it was released. When version 8.2 released, the addon pack had the aroma installer. I thought, what if I repackage the entire ROM with aroma installer. Worked on it last night and was able to flash it through aroma. But the problem I get is now, that i am not able to symlink files and directories. The updater-script is attached and so is the log made by aroma. If anyone can help me, I would be grateful.

omnirom won't update

When I try to do the update it says is available I get these messages.
E: zip signature varification failed: 1
E: errror installation zip file '/emmc/opendelta/omni-4.4.4-20141229-i9100- ightly.zip'

I had some issues with open delta not detecting newer versions. I used a file explorer, deleted the omnirom zip file it had listed. For example I was on build from omni-4.4.4-20141217. and it said the 25th was the newest version, although the date should have been the current day 12/31 but it wouldnt find the newer zip. So I re-downloaded my current build 12/17 and put it back in the omni folder. The next time it checked for updates it seen the zip that was my current rom, then it advanced to update it to the newest zip automatically and open delta started working again.
Hope that makes sense? Not sure if it will help you. Let me know. Goodluck.

Building for bacon: question about TWRP and libncurses.so.5 missing

Hey Guys,
So happy that there's a new AOKP coming. I'd like to work towards Device Maintainer. I've got a 1+1 that I want to get going first, then I'll look at your list of other phones that need maintainers. I have two current issues:
1) My 1+1 is running MultiROM TWRP 2015-08-03 (v2.8.7) and multi-rom v32k tramponline v26. I have two 4.4 ROMS but my AOKP ROM seems to be having issues with the kernel. So my question is: can I just blow away my current roms and flash AOKP-Marshmallow?
2) I'm trying to build for Bacon using the Barbeque (Arch) linux distro. When running make I get the following:
$ time make rainbowfarts
...
Header: /home/russellh/Android/AOKP/out/target/product/bacon/obj/include/time-services/time_genoff.h
host C: mkbootimg <= system/core/mkbootimg/mkbootimg.c
prebuilts/clang/linux-x86/host/3.6/bin/clang: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
build/core/binary.mk:817: recipe for target '/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o' failed
make: *** [/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o] Error 127
#### make failed to build some targets (01:01 (mm:ss)) ####
real 1m0.514s
user 0m22.750s
sys 0m16.210s
So I checked what is installed:
[[email protected] AOKP]$ pacman -Ss ncurses
core/ncurses 6.0-4 [installed]
System V Release 4.0 curses emulation library
I tried creating a symbolic link to libncurses.so -> libncurses.so.5 but that didn't work.
Any suggestions would be great.
Thanks,
Russ

Dinsdale247 said:
Hey Guys,
So happy that there's a new AOKP coming. I'd like to work towards Device Maintainer. I've got a 1+1 that I want to get going first, then I'll look at your list of other phones that need maintainers. I have two current issues:
1) My 1+1 is running MultiROM TWRP 2015-08-03 (v2.8.7) and multi-rom v32k tramponline v26. I have two 4.4 ROMS but my AOKP ROM seems to be having issues with the kernel. So my question is: can I just blow away my current roms and flash AOKP-Marshmallow?
Click to expand...
Click to collapse
Okay, I was able to update to MultiROM TWRP v3.0.0 and multi-rom v33a. I tried creating a new rom and flashing aokp_bacon_mm_nightly_2016-02-24.zip but it always ended with:
Code:
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
Failed to install ZIP!
Restoring mounts
Updating partition details...
...done
Erasing incomplete ROM
I then created a new secondary ROM using an older cyanogenmod zip I had around and then tried to upgrade that ROM to aokp_mm. No love. Any suggestions?
Russ

Dinsdale247 said:
Okay, I was able to update to MultiROM TWRP v3.0.0 and multi-rom v33a. I tried creating a new rom and flashing aokp_bacon_mm_nightly_2016-02-24.zip but it always ended with:
Code:
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
Failed to install ZIP!
Restoring mounts
Updating partition details...
...done
Erasing incomplete ROM
I then created a new secondary ROM using an older cyanogenmod zip I had around and then tried to upgrade that ROM to aokp_mm. No love. Any suggestions?
Russ
Click to expand...
Click to collapse
It is due to old and outdated firmware. Flash cm13 nightly once and then reflash the AOKP build.