Database Develop

[Q] Problem with heimdall 1.3.0 mac 10.5.8

installed heimdall 1.3.0 on mac osx 10.5.8 with xcode 3.2.1 installed/
heimdall command line does not work. Everytime i tried to detect device or download .pit file from device with front-end I get the following error:
"Process: heimdall [289]
Path: /usr/bin/heimdall
Identifier: heimdall
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: heimdall-frontend [283]
Date/Time: 2011-08-05 21:29:38.227 -0400
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: F9D3932B-E440-465E-854D-140EDBA6E24A
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022"
I have cleaned up and reinstalled several time to no vail.
Any suggestions ? Any idea what this error is about ?

Crappyvate said:
installed heimdall 1.3.0 on mac osx 10.5.8 with xcode 3.2.1 installed/
heimdall command line does not work. Everytime i tried to detect device or download .pit file from device with front-end I get the following error:
"Process: heimdall [289]
Path: /usr/bin/heimdall
Identifier: heimdall
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: heimdall-frontend [283]
Date/Time: 2011-08-05 21:29:38.227 -0400
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: F9D3932B-E440-465E-854D-140EDBA6E24A
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022"
I have cleaned up and reinstalled several time to no vail.
Any suggestions ? Any idea what this error is about ?
Click to expand...
Click to collapse
Problem solved after updating to osx 10.6
there seem to be issues between Heimdall 1.3 on Leopard 10.5 and certain binaries. Heimdall command line does not execute and just crashes.

Boot-Time Auto-SuperLog! [12 Apr 2013]

Boot-Time Auto-Superlog! [12 Apr 2013]
USERS --- TESTERS --- DEVS​Plumb the depths of Middle Droid with Auto-Superlog!​
So…
Your device doesn't finish booting
It reboots on its own (and you may not know it)
An application or feature crashes (and you may not know it)
Generally speaking, any manually-launched app or tool could miss key events leading to random reboot or application crash.
Problem addressed with Auto-Superlog!​
cm10-auto-superlog-v1.0.zip (3MB): http://www.mediafire.com/?cf5f9rq4z7p6gep
This flashable zip is tested working on my Atrix running CWM Recovery 5.0.2.0 and CM10 SuperLite. It should also work on epinter’s CM10 4.1.x builds and on close relatives. Not sure about 4.2.x yet.
In this exciting age of alpha-beta ROM testing, my lightweight Auto-Superlog, presently built on epinter’s versatile CM10 boot image (for demo purposes), can help just about anyone, whether end-user, tester or developer!
In fact it is already helping me track down abnormal battery drain and shutdown problems!
Alternatively instead of flashing the boot-time version, you can extract “auto-superlog.sh” from the flashable zip and manually execute it at run time.
Features
Automatically launches at boot-time under “class_start core” --- just after ROM filesystems are mounted, thus maximizing the likelihood of capturing key events, even if phone does not finish booting
Comprehensive log set includes: system build properties (getprop), kernel configuration file (from /proc/config.gz), kernel dmesg and system logcat --- all in sync, all in ASCII text format, and all stored in a single gzipped, time-stamped tar file on $EXTERNAL_STORAGE/auto-superlog for easy access and analysis.
Android events are quietly, nimbly and continuously streamed via kernel “dmesg” and system “logcat” commands. The dmesg log is pushed at 2-second intervals (default) with a 1MB ring buffer which is cleared on each pass. Logcat is configured to log “main” and “system” events with a generous 10MB buffer to help in discerning error trends.
Access real-time dmesg and logcat output right on your device by tapping the /data/auto-superlog directory using a (root) file explorer.
Log file contents are time stamped using absolute time ([YYYY-]MM-DD HH:MM:SS), enabling users to correlate Android events with the outside world
Filename timestamps show when your system was rebooted
Self-cleaning feature: On reboot, your most recent superlog is gzipped and archived to $EXTERNAL_STORAGE and then is removed from /data/auto-superlog so only your most recent superlog remains on the /data partition.
Shell script: auto-superlog.sh is stored under /system/bin, enabling users to extract and execute it at run-time and/or customize.
How to kill dmesg and logcat? Use the ps and grep commands: http://stackoverflow.com/questions/3117095/stopping-an-android-app-from-console (It’s a sheepish way of saying “mechanization of this feature is still in work” lol)
Instructions
Nandroid Backup current ROM (security blanket)
Flash zip if running epinter CM10 4.1.x or close relative (e.g. SuperLite)
Reboot and relax.
…OR, if you don’t want to flash the zip, but still want the run-time features of auto-superlog, simply extract /system/bin/auto-superlog.sh from zip and do this…
copy auto-superlog.sh to /system/bin (Tip: mount /system/bin as read-write (rw), then revert to ro when done)
chmod 0755 /system/bin/auto-superlog.sh
sh /system/bin/auto-superlog.sh (using Script Manager or other tool, as root)
Click to expand...
Click to collapse
After launching the script, just tap the Home button to resume other activity as the loggers are now running in background. Then you will have real-time streaming dmesg and logcat (as well as getprop and kernel config) at your fingertips --- literally.
The advantage of flashing the zip (if it’s compatible with your ROM) is that you are more likely to capture key events leading to a failed boot, random reboot or application crash.
Screenshots
​
Boot Image Source Code
This is the only change I made to CM10 boot.img...
Code:
ramdisk/init.olympus.rc ...
# sendust7 (12 Apr 2013)
service auto-superlog /system/bin/sh /system/bin/auto-superlog.sh
class core
# class main
# class late_start
user root
group system
# disabled
oneshot
# sendust7 (12 Apr 2013)
Documentation
dmesg: http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8
logcat: http://developer.android.com/tools/debugging/debugging-log.html#outputFormat
Android Encryption: http://source.android.com/tech/encryption/android_crypto_implementation.html
from Android Encryption…"This magic was accomplished by requiring all services to be in 1 of 3 groups: core, main and late_start. Core services are never shut down after starting. main services are shutdown and then restarted after the disk password is entered. late_start services are not started until after /data has been decrypted and mounted.”
Click to expand...
Click to collapse
Thoughts and Ideas: This has been a fun project so far. Time permitting, I may be able to service bug fixes and add more goodies like event filtering.
Disclaimer: Standard disclaimers apply.
Credits:Emerson Pinter (CM10 for Atrix 4g), Cyanogenmod Team

Very nice!
The OS considers the internal SD as EXTERNAL_STORAGE in assigning the env variable which is perhaps the reason you should too:
Booted without external sd mounted:
Code:
[email protected]:/ $ echo $EXTERNAL_STORAGE
/storage/sdcard0
Booted with external sd mounted:
Code:
[email protected]:/ $ echo $EXTERNAL_STORAGE
/storage/sdcard0
Possibly just tweak this part of your script:
Before
Code:
/system/bin/mount -t vfat /dev/block/mmcblk1p1 $EXTERNAL_STORAGE
After
Code:
/system/bin/mount -t vfat /dev/block/mmcblk0p18 $EXTERNAL_STORAGE
This then sends the archive to a location that will always exist (sdcard0).
I mention as I don't always have external SD mounted.
Sent from my MB860 using Tapatalk 2

Thanks sendust7
Good job !

[UTILITY] qcndiff: analyze differences between Qualcomm QPST files

[size=+1]QCNDIFF[/size]
This is a utility that parses and displays differences between two text format .qcn files produced by Qualcomm's QPST (Qualcomm Product Support Tools). It's intended use is to display the differences between two files from two different phones in order to help determine which of the nvitems are involved in enabling the different radio frequency bands. This application is meant to be run on Linux or on Windows. Examples for Linux usage and compilation are given for a RHEL / Centos / Fedora distribution. Adapt as necessary to your own distribution.
[size=+1]HOW TO USE[/size]
There are pre-built binaries for 64 and 32 bit Windows as well as pre-built binaries for 64 and 32 bit Linux. The Linux binaries were built on Fedora 20 and the Windows binaries were built with MinGW and statically linked. For Linux you will need to install the boost shared libraries.
Code:
yum install boost
Program usage is as follows
Code:
Usage: qcndiff64 [options] file file
-h [ --help ] show help message
-t [ --type ] arg (=p) show differences
p for items present in both files
m for items missing in either file
b for both present and missing items
-f [ --format ] arg (=i) output format
i for interleaved output
s for sequential output
c to suppress item data and print only
count
-l [ --lookup ] arg (=nv.txt) nv item descriptions
Interleaved output shows the nvitem that is different for both files before displaying the next one. Sequential output displays all the differing items in the first file before proceeding to display the second file.
If the file nv.txt exists (use -l to override the name) it will be used to look up text descriptions of the codes in order to render the output more friendly.
[size=+1]HOW TO COMPILE[/size]
Linux
Code:
yum install boost boost-devel
make
If you wish to compile for a different architecture, for example you run x86_64 and you wish to compile a 32 bit variant, then first make sure you have the 32 bit libraries and then override the target with the ARCH commandline option
Code:
yum install boost.i686 boost-devel.i686
make ARCH=32
Windows
You will need to install MinGW. You need separate toolchains for the 64 bit versions and the 32 bit versions. You will also need to compile the boost libraries.
Once Boost is compiled, edit the Makefile to change the paths to the libraries and include files to conform to where you have them installed. Take note that if the default --layout==versioning option is used to compile Boost then you may also need to change the suffix option in the Makefile
[size=+1]CHANGELOG[/size]
0.2 - add dictionary facility to allow the lookup of text descriptions
0.1 - initial release
[size=+1]DOWNLOAD LINKS[/size]
Binaries and source are available on github
[size=+1]CREDITS[/size]
autoprime for the complete list of nv items used in the dictionary implementation
XDA:DevDB Information
qcndiff, Tool/Utility for the Samsung Galaxy S 5
Contributors
dl12345, autoprime
Source Code: https://github.com/dl12345/qcn
Version Information
Status: Beta
Current Beta Version: 0.2
Beta Release Date: 2014-11-14
Created 2014-11-09
Last Updated 2014-11-13

Version 0.2
Version 0.2 released. This implements a dictionary lookup facility to print textual descriptions of the non-matching nv items so as to make the resulting analysis easier to complete. The included dictionary is not complete but has a substantial number of items defined.
Thanks to autoprime for the list used in the implementation.

Hello
I have tried qcndiff for windows and despite you saed that are statically linked I have an error:
C:\Users\Ovidiu\Desktop\New folder>qcndiff64 80CB5BDE_1.qcn 80CB5BDE_0.qcn
Assertion failed!
Program: C:\Users\Ovidiu\Desktop\New folder\qcndiff64.exe
File: D:\boost_1_57_0/boost/spirit/home/support/char_encoding/ascii.hpp, Line 25
6
Expression: isascii_(ch)
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
C:\Users\Ovidiu\Desktop\New folder>
Thank you

Virtual CD Drive Emulation - Kernel Flag Parameter when Re-Compiling the Kernel?

Hi all
I have an Oppo Find 7 32GB and I installed Omni Rom and it turns out Virtual CD Drive Emulation is not supported by its kernel. I found this out after I tried to mount an ISO using DriveDroid purchased edition as the "CD" icon is disabled when I select an ISO entry. I used both CM and LOS prior this ROM and they both support this feature.
So I downloaded and recompiled the kernel from GitHub (unable to post link as I am new here) and in arch/arm/configs/msm8974_find7_defconfig I added the following flags:
Code:
CONFIG_NLS_ISO8859_1=y
CONFIG_ISO9660_FS=y
CONFIG_ZISOFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
and
Code:
export ARCH=arm
export CROSS_COMPILE=/opt/android/google/android-ndk-r13b/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
make msm8974_find7_defconfig
make
Except for one missing .h file which I copied from LOS kernel zip file, it compiled with no issues.
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
XZKERN arch/arm/boot/compressed/piggy.xzkern
AS arch/arm/boot/compressed/piggy.xzkern.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/ashldi3.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
DTC arch/arm/boot/msm8974pro-ab-pm8941-x9007.dtb
DTC arch/arm/boot/msm8974pro-ac-pm8941-x9076.dtb
CAT arch/arm/boot/zImage-dtb
Kernel: arch/arm/boot/zImage-dtb is ready
I then extracted the boot.image from the ROM's zip file, replaced the kernel image and repacked it and flashed my boot partition:
Code:
sudo fastboot flash boot new_boot.img
I then went to About Phone and I verified that the new custom compiled kernel was up and running only to face with the sad realization that the "CD" icon is still disabled in DriveDroid I have concluded that the flags I've added aren't enough to enable this feature.
Does any know what's the missing parameter that I need to add?

Magisk Module - DiamondJohnHostManager - VERY Large Host File Builder or even small host file

This module is capable of building VERY large hosts files from multiple sources.
In my testing (and is actually my current live environment) I build a host file blocking 2.8 million hosts, from sources listing >4M hosts. Obviously some duplication between sources.
Requirements
Root
BusyBox
CURL - see post 2 for instruction on how to enable
Feature List
Builds from multiple host list sources. I am running >90
Allows whitelist
Supports HTTP, HTTPS as well as local FILE
Runs using multiple parallel threads. i.e. Multi-threaded. Defaults to 16 parallel threads, so while one is awaiting downloading, another would be parsed
In my testing, an older device built large hosts files not too much slower than that on a newer device
Supports mirrors
Fallbacks to previous good run
Multiple file source formats. ie host file with IP and/or simple domain lists even two formats within the same file
Can be run without Magisk
It is script based, so is open source
Configurable via a text file
Tries to clean up / correct some poorly formatted hosts files
Automaically enables / allows the host sources./. ie no need to explicitly include an allow list for the host sources
Automaticallly handles the removal of local hosts in the header from source block lists
Numerous reports on the results can be attained using my other development app with a UI called TeMeFI
You can manually run the build from TeMeFI or from a shell / adb
It defaults to building to the systemless host location of MAgisk, but can build to a RW direct location of /sytsem/etc/hosts
It runs at the LOWEST priority, thus minimal to no degradation of phone performance.
Redirects - text file
triues to minimise downloading files that have not changed
Does not rebuild the host file if the source host lists have not changed
Will force a re-download and host file rebuild if the host sources list has changed
Comments can be aadded to host source list without forcing a rebuild
Its not an app to install and does not run in the background, but a script that only runs on boot
Not Supported
Wildcards in whitelist
No UI, its all script and text files, however reports can be generated using TeMeFI
Install Instructions
Install CURL (see post 2)
Install the Magisk module from within Magisk, using the zip attached to this post
Enable the Magisk systemless host
Reboot twice. Once to finish the install, and the second top actually run the build of host file
MD5: C3464A3A594ECFE95EF87E6E0D324A62
Download: DiamondJohnHostManager_v2.1.zip

Busybox has WGet, and the script will dall back to WGet, but Wget has less featires and also a very well known bug, Dont expect this bug to be fixed too soon as it is even present in the desktop build of Linux!
So the solution is to install CUrl. Following the steps below will get you up and running by installing a MAgisk Module. Its called "Cross Compiled Binaries"
So to clarify the steps.
1. Download & Install "Cross Compiled Binaries" from the Magisk Repo
2. Reboot
3. Open a shell and get an su
4. Run "ccbins"
Spoiler: SCREEN OUTPUT
Code:
sunfish:/ $ su
sunfish:/ # ccbins
===============================
Cross Compiled Binaries v7.2(9)
by Zackptg5
===============================
BusyBox v1.31.1-osm0sis
/dev/a7Y7BvR/.magisk/modules/ccbins/busybox
===============================
Testing internet connection [/] - OK
Fetching available binaries
[|] - Done
Checking for mod updates
[\] - Ccbins is up to date
Checking for binary updates
[/] - Installing NCursesw v6.2
[-] - NCursesw has been installed!
[|] - Binaries are up to date
Checking for conflicting modules
[\] - No conflicting mods were found
===============================
Binary Installer ==============
===============================
Current install location: /system/bin
Auto-update binaries at launch: Enabled (recommended)
DOH Server: None
===============================
Choose option =================
===============================
0: Refresh CCbins (remove everything - start fresh)
1: General Information
2: Options/Settings
3: List all installed binaries
4: List all downloadable binaries
5: Remove binary
6: Install binary
7: Install dynamic linked binary
Type 'q' at any time to quit
-->
5. Select "Install a Binary" ie "--> 6"
Spoiler: SCREEN OUTPUT
Code:
--> 6
===============================
Install which binary? =========
===============================
Current install location: =====
/system/bin ===================
===============================
0: None, go back to main menu
1: Install all binaries listed below
2: Aria2 (v1.35.0)
3: Bash (v5.1.8)
4: Bc (v1.07.1)
5: Brotli (v1.0.9)
6: Coreutils (v8.32)
7: Cpio (v2.12)
8: Curl (v7.78.0)
9: Diffutils (v3.7)
10: Ed (v1.17)
11: Findutils (v4.8.0)
12: Gawk (v5.1.0)
13: Grep (v3.6)
14: Gzip (v1.10)
15: Htop (v3.0.5)
16: Iw (v5.9)
17: Keycheck (v1.0)
18: Nano (v5.8.0)
19: Nethogs (v0.8.6)
20: Openssl (v1.1.1.11)
21: Patch (v2.7.6)
22: Patchelf (v0.12)
23: Sed (v4.8)
24: Strace (v5.13)
25: Tar (v1.34)
26: Tcpdump (v4.99.1)
27: Vim (v8.2.3095)
28: Wavemon (v0.9.3)
29: Xmlstarlet (v1.0)
30: Xxd (v1.10)
31: Zip (v3.0)
32: Zsh (v5.8.0)
33: Zstd (v1.5.0)
-->
6. Install the selected one. "curl" in my case. ie "--> 8"
Spoiler: SCREEN OUTPUT
Code:
--> 8
Downloading Curl
[|] - Curl has been installed!
Reboot for changes to take effect
7. Reboot
8. open a shell, get su and curl is now available
Spoiler: CURL NOW AVAILABLE
Code:
sunfish:/ $ su
sunfish:/ # curl--help
/system/bin/sh: curl--help: inaccessible or not found
127|sunfish:/ # curl --help
Usage: curl [options...] <url>
-d, --data <data> HTTP POST data
-f, --fail Fail silently (no output at all) on HTTP errors
-h, --help <category> Get help for commands
-i, --include Include protocol response headers in the output
-o, --output <file> Write to file instead of stdout
-O, --remote-name Write output to a file named as the remote file
-s, --silent Silent mode
-T, --upload-file <file> Transfer local FILE to destination
-u, --user <user:password> Server user and password
-A, --user-agent <name> Send User-Agent <name> to server
-v, --verbose Make the operation more talkative
-V, --version Show version number and quit
This is not the full help, this menu is stripped into categories.
Use "--help category" to get an overview of all categories.
For all options use the manual or "--help all".

Some file Locations:
Your listt of Host Sources: /storage/emulated/0/Android/data/DiamondJophnDroidHostManager/host_sources.trxt
Each line is a different "row" which is a host source.
Lines Preceded with a "-" will be treated as an allow list, otherwise it will be treated as a deny list
Within each line, a mirror for the host sources is define by sepereating with a piping character ie "|"
A source can be https:// or http:// or file:// Note for a file source, the protocol has 2 slashes and then a third slash will be there for the path. Hence a file will have a tipple slash
Anything after the hash (#) will be ignored and treated as a comment
Empty lines will be ignored
MAKE SURE YOU USE A LINE-FEED and NOT a CARRIAGE RETURN & LINE-FEED to end each line. ie Android/Unix/Linux style, not windows style.
An example of each of the above:
Code:
https://dbl.oisd.nl
https://winhelp2002.mvps.org/hosts.txt|http://winhelp2002.mvps.org/hosts.txt|https://raw.githubusercontent.com/hectorm/hmirror/master/data/winhelp2002.mvps.org/list.txt|https://ssl-proxy.my-addr.org/myaddrproxy.php/http/winhelp2002.mvps.org/hosts.txt
file:///data/media/0/User/hosts/Deny/deny_coinblocker.txt
# Dead Host source
#https://raw.githubusercontent.com/Zelo72/hosts/main/big.txt
-file:///data/media/0/User/hosts/Allow/google_play_whitelist.txt
-file:///data/media/0/User/hosts/Allow/google_video_whitelist.txt
The config is stored at: /data/adb/modules/DiamondJophnDroidHostManager/bin/includes/shared_constants.sh
The logs will go to: /storage/emulated/0/Android/data/DiamondJophnDroidHostManager/logs/*
The history / previous run will go to: /storage/emulated/0/Android/data/DiamondJophnDroidHostManager/previous/*

reserved...

reserved...

Just to give you some context on performance. I have a Pixel 4A and the following is from the end of the log:
Code:
...snip...
download_hosts.sh - Start build final output host file at 2021-10-18 10:40:14.018
21 seconds - download_hosts.sh 91 files combined,
blocking 2,888,313 hosts from 5,172,803 total blocking hosts and 622 allowed hosts
with a file size of 87,246,214 bytes,
built using 79 historic hosts lists, of 91 total sources. at 2021-10-18 10:40:34.596
Resultant Hosts file copied to /data/adb/modules/hosts/system/etc/hosts at 2021-10-18 10:40:34.857
SAVE_PARAM >>> ROW= MIRROR=0 NAME=UNIQUE_BLOCKED_HOSTS VALUE=2888313 at 2021-10-18 10:40:34.905
SAVE_PARAM >>> ROW= MIRROR=0 NAME=BLOCKED_HOSTS VALUE=5172803 at 2021-10-18 10:40:34.952
SAVE_PARAM >>> ROW= MIRROR=0 NAME=ALLOWED_HOSTS VALUE=622 at 2021-10-18 10:40:34.999
SAVE_PARAM >>> ROW= MIRROR=0 NAME=SOURCE_COUNT VALUE=91 at 2021-10-18 10:40:35.050
SAVE_PARAM >>> ROW= MIRROR=0 NAME=HISTORIC_SOURCES VALUE=79 at 2021-10-18 10:40:35.090
SAVE_PARAM >>> ROW= MIRROR=0 NAME=FILE_SIZE VALUE=87246214 at 2021-10-18 10:40:35.126
SAVE_PARAM >>> ROW= MIRROR=0 NAME=ELAPSED_TIME VALUE=232 at 2021-10-18 10:40:35.166
ALL processed in 232 seconds at 2021-10-18 10:40:35.181
I also did some tests on an old 2013 Samsung S4, and it was around 300-400 seconds to build a similar 2.8M host file from 4.8M hosts.

Updated module. v2.1 Removed some debug code that made its way into the release.
Also note, the default host source list does not download 2.8M hosts. Its gets about 200K hosts, which are about 90+% unique.

Buena tarde:
Para agregar más fuentes de las que vienen, ¿qué sería modificar el archivo host_sources.txt?
Lo que no entiendo es que el complemento se descargue de magisk o .zip.
Saludos cordiales FELIZ NAVIDAD Y PRÓSPERO AÑO NUEVO.