Jiska Classen

Looks plausible :) The `.hcd` comes in slightly different variants, though, depending on the chip. Especially the Patchram can be at different positions. Some of that is summarized in our...

Hi @misterAnderson90 , thank you for running your tool on this repository and informing us about potential vulnerabilities. Since your tool is an open-source project, I assume anyone could run...

Hi @jurek4321, definitely looks as if something goes wrong there. To debug if it is the `bluetooth.default.so` I can recommend just using plain Wireshark. Usually, if Android/Lineage loads the module...

Ah, and maybe one thing I should add: If InternalBlue gets the correct firmware version answer, it will send a command starting with `0x7`, which enables diagnostics, instead of `0x1`,...

Hi @jurek4321, building the module properly is somewhat complicated and I did that a loooong time ago :( I just realized that the debugging method with Wireshark in parallel doesn't...

Hi @jurek4321 , Android has minor versions. For example, Android 6.0.1 has multiple releases for the Nexus 5 (see https://source.android.com/setup/start/build-numbers). Most likely, you're using an incompatible pre-built `bluetooth.default.so`. And yes,...

Looks like you got a chip with a more recent patch level :) Ideally, it should have the same ROM, so you can simply copy the file as you did....

Hi, thanks for pointing this out, I'm aware of that issue but didn't fix it yet. It's something weird going on when bytes are filled in the dump between different...

It works but for whatever reason it is really slow. (Tested for most recent iPhone firmware on Linux.) Example from the *InternalBlue* CLI: ``` > dumpmem -f iphone11_13.5.bin [*] No...

Hi @wrlu, I currently don't have the most recent Raspberry Pi with *InternalBlue*, and @unixb0y only tested this on an older version. According to the log you have the same...