SUBARU LEGACY BP5/BL5 IMMOBILIZER TEACHING OPERATION CODES

Thankfully the immobilizer software in SSM3 (immo.exe) works with J2534 04.04 VCI modules

The relevant “REGISTRATION MANUAL FOR IMMOBILIZER” is unavailable on the open internet for BP5/BL5 at late 2025

Through a brute-force method, I have discovered the following:

CodeEnglish DescriptionJapanese Description
0276Finish Factory Registration Mode工場登録モードを終了させますか
1826Unused?
3071Immobilizer Registration number displayキー登録本数表示を実行しますか
3781Immobilizer Key registration mode executeキー登録モードを実行しますか
7548Execute Personal No. Registration ModeパーソナルNo.登録モードを実行しますか
7602Audio ID Registration mode Is executed?オーディオID 登録モードを実行しますか

(Note: This is relevant to a MY2005 Legacy 2.5i)

After each teaching operation, cycle the ignition key. Due to discovering this after, I am unsure which code allowed me to re-marry my modules.

Cleared NVRAM / PRAM on a Mac now it won’t boot?

Foreword 1: This is originally drafted from 2018 or so. Releasing now as it is too useful to delete. I had intended to update the code sections with worked examples. This is for broad reference only, and you will need to refer to the efibootmgr documentation.

Foreword 2: If your mac still has the apple recovery partition on the hard drive this information might be interesting but probably won’t help directly.

According to internet rumor, a slow running mac might have a funky configuration saved in the PRAM/NVRAM – a small amount of storage used to save system information. Wiping this out is often openly recommended on forums, without the caveat: it wipes out the efi boot configuration and sets it to an apple default.

According to Apple (https://support.apple.com/en-us/HT204063)
Information stored in NVRAM can include:

  • Speaker volume
  • Screen resolution
  • Startup disk selection
  • Recent kernel panic information, if any

Normally resetting this wouldn’t be a problem, but I single boot linux and there’s nothing apple left on the hard drive. After resetting and rebooting I get boot disk not found.

Here’s how to reconstruct the efi boot record:

You’ll need a linux live environment you’re comfortable with. I used Linux Mint. I’ve included the output of commands so you can see what I’m seeing.

  1. Start by booting your live cd/usb and install efi boot manager:
    $ sudo apt-get install efibootmgr
  2. Inspect the current boot record
    $ efibootmgr
    ...
  3. Find your boot partition uuid. efi boot records are flexible and it makes sense to refer to file systems by uuid.
    $ ls -al /dev/disk/by-uuid
    ...

    To see what uuids symlink to what file systems. If you’re not sure which one your boot partition is, mount them until you find it.

  4. Write a new efi boot record that links to your boot partition and boot loader
    $ efibootmgr
    ...

    In my case the path to my boot loader was /boot/EFI/grub/grub64.efi, but yours might be different if you use a different linux distribution.

  5. Delete the 9999 one loaded in by default (that I guess points to the apple recovery partition)
    efibootmgr
    ...
  6. print it again just to check
    efibootmgr
    ...
  7. Reboot

There it is. Seven steps to get your non-mac mac booting again.

Windows 11 unable to make changes to lock screen

Some settings are managed by your organization.

The specific registry setting as follows:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization

NoChangingLockScreen

Dword set to 0

Careful with the recommendations made on microsoft forums, as many of the recommendations remove entire policy trees which we are using to disable telemetry.

(Running a debloat script may have been where this block was set – will keep an eye on it over the next updates if any new trash appears on the lock screen)

Reference https://www.winhelponline.com/blog/personalize-some-settings-managed-organization/

fastrlock fails to build on python 3.13

fastrlock\rlock.c(9635): error C2198: 'int _PyLong_AsByteArray(PyLongObject *,unsigned char *,size_t,int,int,int)': too few arguments for call

Solution is to revert to python 3.12 until fastrlock is updated.

Issue is caused by removal of functions from the internal API

Reference:

Ducati Monster 600 clutch bearing replacement

Building on the very helpful earlier (2012) work of Andy and his M 620 i.e. https://twoslow.com/2012/09/ducati-monster-wet-clutch-throwout-bearing/

The M 600 uses a different clutch pressure plate (1 piece) and bearing. See below for comparison.

M620i.e. 6201 bearingM600 6003 bearing

Parts Catalogue Reference:

https://www.motorcyclespareparts.eu/en/ducati-parts/2001-monster-600-eu-motorcycles/clutch

https://www.bike-parts-ducati.com/ducati-motorcycle/Monster/2000/Monster_600/Monster-600/CLUTCH/691/2302/0/691

They really are a small bike compared to the other models.

Adding a static location to geoclue versions < 2.7.1

Note: this is only adding a static location to geoclue. If you need more flexibility, there are google location API keys out there.

With the shutdown of Mozilla Location Service, many programs depending on geoclue break. (redshift, some browsers location, etc.) Some programs can be manually configured to a static location, but some can not. My preference is to keep them deferring to geoclue so there is only one static location to remember.

The new release of geoclue does support static address, but many distro releases will not be updated. Here we will point our old version geoclue at a local web server to tell it where we are. Internally geoclue uses libsoup which means it can’t open url file://, so we must feed it with http.

Reference

1. Install Nginx

$ sudo apt-get install nginx-light

2. Put the following in /etc/nginx/sites-available/static-location

server {
        listen 127.0.0.1:8080;
        server_name static-location;
        root /var/www/html;
        error_page  405     =200 $uri;
        index index.html;
        location / {
                try_files $uri $uri/ =404;
        }
}

Note: thanks for the response code rewrite trick:
https://distinctplace.com/2017/04/17/405-not-allowed-nginx-fix-post-requests/

3. Link your new nginx rule to be enabled [you may want to remove any other links in this folder]

$ sudo ln -s /etc/nginx/sites-available/static-location /etc/nginx/sites-enabled/static-location

4. Set your static location by creating the following file at /var/www/html/static.json

{
    "location": {
        "lat": -22.7539192,
        "lng": -43.4371081
    },
    "accuracy": 100.0
}

5. Make sure nginx is started [note: I have not verified if this starts at system start]

$ sudo service nginx status
$ sudo service nginx stop
$ sudo service nginx start

6. Edit /etc/geoclue/geoclue.conf to refer to the local server instead of Mozilla

url=http://localhost:8080/static.json

7. Verify geoclue is working

$ /usr/libexec/geoclue-2.0/demos/where-am-i 
Client object: /org/freedesktop/GeoClue2/Client/1

New location:
Latitude:    -22.753919°
Longitude:   -43.437108°
Accuracy:    100.000000 meters
Timestamp:   Tue 15 Oct 2024 22:57:16 (1728997036 seconds since the Epoch)

Lexus IS200 1G-FE manual throttle body

There is a manual throttle body available for 1G-FE vvti motors. They can be found on GXE10 Altezzas and late (vvti 1G) GX100s, only on the non-TRC variants. They have stepper motor idle control, so will not be compatible with an IS200 ECU.

E-throttle on the left, Mechanical on the right (click for full size):

This is an option for running aftermarket ecus which don’t support drive-by-wire. They can be found easily and cheaply on yahoo japan, but you will need a forwarding service or local agent to send it to you.

There’s been talk about this option on forums and youtube comments for years without solid information, so I hope this clears things up a bit.

GXE10 機械式スロットルボディ (GXE10 Mechanical Throttle Body) [22210-70420]

 

Early IS200/Altezza Stereo Pin Out

This post covers 2 topics related to the early cars (98-99) with a 4 channel amplifier.

Later cars had a 2 channel amplifier. They handled balance, fade, and equaliser settings within the amplifier. Communication between the head unit and amplifier occurred over the AVC-LAN bus.

The TSRM wiring diagrams don’t cover the early cars, and most information on the internet refers to the later cars only.

Radio head unit pin out

Thanks to user Adrian Eccles at tezzaworld.com the 18 pin plug on the head unit is already pinned out:

tezzaworld.com – Mini disc, cd changer radio pin out

S7004852copy
Image from linked forum post

In the past I have successfully used the factory amp and speakers with an aftermarket head unit by soldering RCA positives onto the 4 signal lines. The signal ground is common, so I joined the RCA negatives together.

The amplifier turns on with positive signal voltage like an aftermarket amplifier.

Amplifier pin out

The factory amplifier worked quite well at first. Over time it developed a constant quiet hiss from the speakers, and a speaker pop when turning off the amp. The amplifier did this without a head unit connected.

The harness connecting the amplifier to the car body is standard Toyota. In Toyota vehicles the amplifier is viewed as the head of the system.

The 4 rear speakers in the 8 speaker system are driven separately, with 4 ohm midrange speakers and 2 ohm woofers. Because the mids have a narrow frequency range, and the woofers are low impedance, it is common to replace them with aftermarket 6×9’s.

Extra

If you care about impedance:

  • Head unit line outs are 10k between channel+ and sgnd
  • Amplifier line input is over 2m
  • Amplifier speaker output is over 2m on the mids, 3.6k on the woofers

Amplifier turns on at a minimum of +3.3v