Does not work with my version of Xochitl

[raisjn]

This issue is for when rm2fb's server process fails to find the signature it needs.

Please respond with which binary was being used and what its md5sum is, thank you!

NOTE: this issue is specifically for if rm2fb server or client prints out an error referencing issue #18. The error message means that the signatures we use are no longer valid in the version of xochitl being used. Please open separate threads for other issues.

[Witos]

Where this (int *)locate_signature(SDK_BIN.c_str(), "|@\x9f\xe5|P\x9f\xe5", 8); come from? How did you get this magic string?

[ddvk]

this is the signature of a function we are loooking for

[Witos]

I know what it is. I don't know how do you know which function to look for? Did you reverse engineer remarkable-shutdown?

[ddvk]

of course

…

On Mon, 16 Nov 2020 at 09:19 Witos ***@***.***> wrote: I know what it is. I don't know how do you know which function to look for? Did you reverse engineer remarkable-shutdown? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYZFLWDZINBXHPR4QUTDVTSQDN7TANCNFSM4TQ3VQVA> .

[pgaskin]

@ddvk or @raisjn, I don't have a reMarkable, but I'd like to take a look at xochitl and remarkable-shutdown. Is there somewhere I can find the binaries?

[Eeems]

@pgaskin Due to licensing you'll need to have a device to get the binaries.

[pgaskin]

Are the firmware updates available somewhere?

[Eeems]

I'm sure they are, just not entirely sure where to look. The code that handles updating can be found here: https://github.com/reMarkable/update_engine

[ddvk]

can you ask in the discord channel, https://discord.gg/ATqQGfu there was an irc bridge as well

…

On Mon, 16 Nov 2020 at 17:23 Patrick Gaskin ***@***.***> wrote: Are the firmware updates available somewhere? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYZFLWB32UMJWIMUASNQULSQFGZXANCNFSM4TQ3VQVA> .

[pgaskin]

I have these:

remarkable-shutdown: eacf23b176dcda8f1727ff0ac433ca8f4c85c809
xochitl: c88d155b7ca8c770240b2c00048968f8445f8115

[ClashTheBunny]

md5sum /usr/bin/remarkable-shutdown /usr/bin/xochitl:

fec600ccae7743dd4e5d8046427244c0  /usr/bin/remarkable-shutdown
aaa77163501618b0cfae54843505df88  /usr/bin/xochitl

More info:

Downloaded the .sos from release 0.0.1.

To show the same data as @pgaskin when doing a sha1sum:
sha1sum /usr/bin/remarkable-shutdown /usr/bin/xochitl:

eacf23b176dcda8f1727ff0ac433ca8f4c85c809  /usr/bin/remarkable-shutdown
c88d155b7ca8c770240b2c00048968f8445f8115  /usr/bin/xochitl

Actual error message:

reMarkable: ~/koreader/ LD_PRELOAD=librm2fb_server.so /usr/bin/remarkable-shutdown
ERROR: ld.so: object 'librm2fb_server.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
EPD platform plugin loaded!
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.qpa.input: evdevtouch: Using device discovery
qt.qpa.input: evdevtouch: Adding device at "/dev/input/event2"
qt.qpa.input: evdevtouch: Using device /dev/input/event2
qt.qpa.input: evdevtouch: /dev/input/event2: Protocol type B  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event2: min X: 0 max X: 1403
qt.qpa.input: evdevtouch: /dev/input/event2: min Y: 0 max Y: 1871
qt.qpa.input: evdevtouch: /dev/input/event2: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event2: device name: cyttsp5_mt
Waveform file with correct FPL_LOT not found, using fallback: /usr/share/remarkable/320_R299_AFC421_ED103TC2U2_VB3300-KCD_TC.wbf
Reading waveforms from /usr/share/remarkable/320_R299_AFC421_ED103TC2U2_VB3300-KCD_TC.wbf
Running INIT (111 phases)
SWTCON initialized \o/
Creating painter
Battery left: 97
REMARKABLE_SHUTDOWN_STATE= ""
Sending update
Epaper integration dying
Epaper integration dead

[raisjn]

can you try using the full path to the so file in the ldpreload?

[ClashTheBunny]

That's exactly my problem. I saw a note in #rm2 about it and it worked perfectly! I've got KOReader up on the screen as we speak. I also did need the full version number at the end.

[LinusCDE]

toltec-dev/toltec#163 (comment)

Triggered the watchdog to downgrade the device. Seems to be some weired combinations between the new entware-reenable doing something that maybe crashes (?) the device and then rm2fb fails to find a signature. My device is a rM 1.

Mounted the old partition to get the hash of the xochitl in question:

MD5: 6709a445112e783c59a926aabdbd49c9 /mnt/usr/bin/xochitl

[Eeems]

rm2fb should probably check to see if it's being run on a rM1 and just stop if not.