ddvk/remarkable-update

force a full factory reset / re-update / upgrade

Note: This only works for OS versions before 3.11 as 3.11 changes the upgrade mechanism that the device uses.

Simple Factory Reset (updater)

A hackish, quick and dirty update server implementation. For a more complete solution, check out codexctl.

Usage

1. Clone this Repo

2. Obtain an official release that you would like to upgrade (er, downgrade) to. A list of firmware releases can be found here.

3. Put your firmware release in ./updates.

4. Figure out the hostname of the computer you are connecting your remarkable to. If you are connecting to USB it will likely be 10.11.99.2. If your ReMarkable device is connected to your local wifi, it may also work to use a local IP address such as 192.168.1.25. The docs will use 10.11.99.2 as the hostname. If you have a different hostname, adjust accordingly.

5. Start the mock upgrade server. (This assumes you are running python3)

   python serve.py 10.11.99.2

6. SSH into your ReMarkable device and edit /usr/share/remarkable/update.conf:

   ssh [email protected]
   nano /usr/share/remarkable/update.conf

7. Add the following line to the update.conf file:

   SERVER=http://10.11.99.2:8000
   

8. Run an automatic update.

Via ReMarkable UI

1. Go to Menu -> Settings -> General: click on the Software Version.

2. Tap Check for Updates. It should download and install the update.

3. Once it is complete, it should prompt you to tap to reboot your device.

Via the CLI

1. In the ReMarkable Terminal, make sure update-engine is running:

   systemctl start update-engine

2. Trigger the update:

   update_engine_client -check_for_update

3. Observe the update progess.

   journalctl -u update-engine -f

4. Once it is complete, reboot the device.

   reboot

To switch the partition i.e. boot the previous version

1. Copy the switch.sh script to the device.

   scp switch.sh [email protected]:~

2. SSH into reMarkable and run the script.

   ssh [email protected]
   ./switch.sh

3. Reboot the device for changes to take effect.

   reboot

Beta

It seems that the update server address (SERVER) is defined in the /home/root/.config/xochitl.conf file Issue

remarkable-update's Issues

Firmware download link is not available anymore

The firmware download link (https://thelastzombie.github.io/remarkable-firmware/) in readme is not available. Please update the link, thank you.

Help im stuck trying to update my Remarkable 2 according to https://github.com/ddvk/remarkable-update

I have done everything on this page. is there any way to force update without using python.

This is error on the device.

So i referred to this (https://github.com/ddvk/remarkable-update#usage)
-Step 3 is where i get stuck i cannot find that (file/folder/conf)
I cannot find the ./updates ANYWHERE?

I then approach Via the CLI and nothing works for me.

Step 2 looks like

Then im stuck here!

I'm very new to this and I have spent two days looking around at constant threads i cant get the automatic update to return back after reverted back to original according to:
sh -c "$(wget https://raw.githubusercontent.com/ddvk/remarkable-hacks/master/patch.sh -O-)" _ purge

Nothing works for me. I would really appreciate some insight.

serve.py dosen't start

python serve.py
File "serve.py", line 46
url = f"http://{host}:{port}/"
^
SyntaxError: invalid syntax

I have try to change value, but without success

Got result code 2 from requesting name

Hi,

This may well be a remarkable software problem -- I ended up here because the normal update process is not working for me. But I thought I'd see if you have any ideas.

I have the server running locally, but the update-engine process segfaults consistently: Here's a sample.

root@reMarkable:~# update_engine -foreground
I1104 10:39:36.481634   284 main.cc:97] reMarkable Update Engine starting
I1104 10:39:36.482774   284 payload_state.cc:377] Current Response Signature = 
NumURLs = 1
Url0 = http://peters-MacBook-Pro-3.local:8000/updates/2.7.0.51_reMarkable2.signed
Payload Size = 67056686
Payload Sha256 Hash = +fGmveJ5GNtEd5iBQyseN+eMm2yl7grdRrVitKJnx40=
Is Delta Payload = 0
Max Failure Count Per Url = 10
Disable Payload Backoff = 1
I1104 10:39:36.486073   284 payload_state.cc:402] Payload Attempt Number = 0
I1104 10:39:36.486971   284 payload_state.cc:429] Current URL Index = 0
I1104 10:39:36.487747   284 payload_state.cc:454] Current URL (Url0)'s Failure Count = 1
I1104 10:39:36.488369   284 payload_state.cc:488] Backoff Expiry Time = 01/01/70 00:00:00 UTC

** (process:284): WARNING **: Got result code 2 from requesting name
F1104 10:39:36.499048   284 main.cc:69] Got result code 2 from requesting name, but expected 1

Any ideas on this requesting name error?

"Downgrade" with a brand new rm2 "out of the box"

Hi everyone.
Did someone try the switch.sh script already with a brand new rm2 device? I just got mine and I am wondering, if I softbrick it when I start it the very first (second) time and using the switch.sh script. Will the switch to the "other" partition work? Is it empty? Will there even be another version before? My device is on 2.14.4.46 now out of the box.

Thanks in advance!

Bug: Error connecting server

Here’s my config:

[General]
REMARKABLE_RELEASE_VERSION=2.5.1.45
SERVER=http://<ipaddress>:10001

Well there’re the error thrown while running update_engine_client -check_for_update

Parsing name error with update file

Hello!

While trying to downgrade to version 2.14.1.866, The scan_updates function fails to find the update file while looking through the directory. Namely, this part:

p = f.split('_')
if len(p) != 2:
   continue

will fail to find the update file named rm2_2.14.1.866_reMarkable2-JLWa2mnXu1-.signed because of the first underscore at the beginning (rm2_) and thus when trying to update will throw this KeyError:

In order to get around this I had to rename the file rm2_2.14.1.866_reMarkable2-JLWa2mnXu1-.signed to 2.14.1.866_reMarkable2-JLWa2mnXu1-.signed

Error Updating

I was looking to update to 3.8, since straight lines would be really helpful to me.

I purged the hack, and the official update server is giving me an error updating, so I tried using this emulated server and recieve the same error.

error from journalctl
Oct 19 15:37:31 reMarkable update_engine[188]: <event eventtype="3" eventresult="0" errorcode="268435461"></event> Oct 19 15:37:31 reMarkable update_engine[188]: </app> Oct 19 15:37:31 reMarkable update_engine[188]: </request> Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.309626 188 libcurl_http_fetcher.cc:50] Starting/Resuming transfer Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.310346 188 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.311332 188 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds. Oct 19 15:37:31 reMarkable update_engine[188]: E20231019 15:37:31.316259 188 libcurl_http_fetcher.cc:264] Unable to get http response code: Empty reply from server Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316607 188 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316663 188 libcurl_http_fetcher.cc:297] Error buffer: Empty reply from server Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316694 188 omaha_request_action.cc:670] Omaha request response: Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316732 188 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316761 188 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316787 188 update_attempter.cc:313] Processing Done. Oct 19 15:37:31 reMarkable update_engine[188]: I20231019 15:37:31.316823 188 update_attempter.cc:317] Error event sent.

error from the server (sorry for the image, the markdown was being hidden from my comment):

Any thoughts on what the root cause could be?

Running on my hostname http://10.11.99.4:8000.

Error finding Update server on new OS Version

Hi,
I have the similar issue to this but coming from 3.9.3.1986. In my case neither the USB nor the WiFi IP can be found by the ReMarkable. I tried every combination without luck. I have command line experiance and its not my first hack of some sorts, but I am out of ideas here. I'd be very happy about input. My goal is to downgrade in order to use the syncthing integration.
Getting this output in some form every time:

In the following example I have manualy changed
REMARKABLE_RELEASE_VERSION=3.9.3.1986
to
REMARKABLE_RELEASE_VERSION=3.8.3.1976
in an attempt to make a difference.

My /usr/share/remarkable/update.conf reads
[General]
REMARKABLE_RELEASE_APPID={< My-App-ID >}
SERVER=http://10.11.99.2:8000/
#GROUP=Prod
#PLATFORM=reMarkable2
REMARKABLE_RELEASE_VERSION=3.8.3.1976

root@reMarkable:~# update_engine_client -check_for_update
I20240217 16:12:30.351001   373 update_engine_client.cc:271] Initiating update check and install.

root@reMarkable:~# journalctl -u update-engine -f
Feb 17 16:12:30 reMarkable update_engine[183]:     <os version="codex 4.0.258" platform="reMarkable2" sp="3.8.3.1976_armv7l" arch="armv7l"></os>
Feb 17 16:12:30 reMarkable update_engine[183]:     <app appid="{98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}" version="3.8.3.1976" track="Prod" ap="Prod" bootid="{bf01014e-cc78-49c8-9ec3-3b8216c09570}" oem="RM110-109-77309" oemversion="4.0.258" alephversion="3.9.3.1986" machineid="a3beee59291b416eab597d95c2b25963" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Feb 17 16:12:30 reMarkable update_engine[183]:         <ping active="1"></ping>
Feb 17 16:12:30 reMarkable update_engine[183]:         <updatecheck></updatecheck>
Feb 17 16:12:30 reMarkable update_engine[183]:         <event eventtype="3" eventresult="2" previousversion=""></event>
Feb 17 16:12:30 reMarkable update_engine[183]:     </app>
Feb 17 16:12:30 reMarkable update_engine[183]: </request>
Feb 17 16:12:30 reMarkable update_engine[183]: I20240217 16:12:30.378751   183 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Feb 17 16:12:30 reMarkable update_engine[183]: I20240217 16:12:30.378899   183 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Feb 17 16:12:30 reMarkable update_engine[183]: I20240217 16:12:30.379503   183 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Feb 17 16:13:00 reMarkable update_engine[183]: E20240217 16:13:00.546649   183 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timeout after 30168 ms
Feb 17 16:13:00 reMarkable update_engine[183]: I20240217 16:13:00.546978   183 libcurl_http_fetcher.cc:281] No HTTP response, retry 1
Feb 17 16:13:10 reMarkable update_engine[183]: I20240217 16:13:10.555297   183 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Feb 17 16:13:10 reMarkable update_engine[183]: I20240217 16:13:10.555565   183 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Feb 17 16:13:10 reMarkable update_engine[183]: I20240217 16:13:10.556196   183 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Feb 17 16:13:41 reMarkable update_engine[183]: E20240217 16:13:41.546527   183 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timeout after 30991 ms
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.546820   183 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.546880   183 libcurl_http_fetcher.cc:297] Error buffer: Connection timeout after 30991 ms
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.546917   183 omaha_request_action.cc:670] Omaha request response:
Feb 17 16:13:41 reMarkable update_engine[183]: E20240217 16:13:41.546953   183 omaha_request_action.cc:686] Omaha request network transfer failed.
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547034   183 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547072   183 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547106   183 update_attempter.cc:313] Processing Done.
Feb 17 16:13:41 reMarkable update_engine[183]: E20240217 16:13:41.547180   183 update_attempter.cc:685] Update failed.
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547219   183 utils.cc:750] Converting error code 2000 to kActionCodeOmahaErrorInHTTPResponse
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547255   183 payload_state.cc:104] Updating payload state for error code: 37 (kActionCodeOmahaErrorInHTTPResponse)
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.547298   183 payload_state.cc:110] Ignoring failures until we get a valid Omaha response.
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.548763   183 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549614   183 omaha_request_action.cc:280] Posting an Omaha request to http://192.168.1.25:8000/
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549681   183 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?>
Feb 17 16:13:41 reMarkable update_engine[183]: <request protocol="3.0" version="3.8.3.1976" requestid="{5bb22f90-f0b4-4440-ad7c-748e3bb858d5}" sessionid="{251704ff-0ac6-4f85-89af-9a8032f6f8fd}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1">
Feb 17 16:13:41 reMarkable update_engine[183]:     <os version="codex 4.0.258" platform="reMarkable2" sp="3.8.3.1976_armv7l" arch="armv7l"></os>
Feb 17 16:13:41 reMarkable update_engine[183]:     <app appid="{98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}" version="3.8.3.1976" track="Prod" ap="Prod" bootid="{bf01014e-cc78-49c8-9ec3-3b8216c09570}" oem="RM110-109-77309" oemversion="4.0.258" alephversion="3.9.3.1986" machineid="a3beee59291b416eab597d95c2b25963" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Feb 17 16:13:41 reMarkable update_engine[183]:         <event eventtype="3" eventresult="0" errorcode="268437456"></event>
Feb 17 16:13:41 reMarkable update_engine[183]:     </app>
Feb 17 16:13:41 reMarkable update_engine[183]: </request>
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549724   183 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549891   183 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.550524   183 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
^C
root@reMarkable:~# nano /usr/share/remarkable/update.conf
root@reMarkable:~# update_engine_client -check_for_update
I20240217 16:14:06.031101   376 update_engine_client.cc:271] Initiating update check and install.
root@reMarkable:~# journalctl -u update-engine -f
Feb 17 16:13:41 reMarkable update_engine[183]:     <app appid="{98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}" version="3.8.3.1976" track="Prod" ap="Prod" bootid="{bf01014e-cc78-49c8-9ec3-3b8216c09570}" oem="RM110-109-77309" oemversion="4.0.258" alephversion="3.9.3.1986" machineid="a3beee59291b416eab597d95c2b25963" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Feb 17 16:13:41 reMarkable update_engine[183]:         <event eventtype="3" eventresult="0" errorcode="268437456"></event>
Feb 17 16:13:41 reMarkable update_engine[183]:     </app>
Feb 17 16:13:41 reMarkable update_engine[183]: </request>
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549724   183 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.549891   183 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Feb 17 16:13:41 reMarkable update_engine[183]: I20240217 16:13:41.550524   183 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Feb 17 16:14:06 reMarkable update_engine[183]: I20240217 16:14:06.047055   183 dbus_service.cc:62] Attempting interactive update
Feb 17 16:14:06 reMarkable update_engine[183]: I20240217 16:14:06.047147   183 update_attempter.cc:283] New update check requested
Feb 17 16:14:06 reMarkable update_engine[183]: I20240217 16:14:06.047176   183 update_attempter.cc:286] Skipping update check because current status is UPDATE_STATUS_REPORTING_ERROR_EVENT
Feb 17 16:14:12 reMarkable update_engine[183]: E20240217 16:14:12.546967   183 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timeout after 30997 ms
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547262   183 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547325   183 libcurl_http_fetcher.cc:297] Error buffer: Connection timeout after 30997 ms
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547369   183 omaha_request_action.cc:670] Omaha request response:
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547420   183 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547456   183 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547490   183 update_attempter.cc:313] Processing Done.
Feb 17 16:14:12 reMarkable update_engine[183]: I20240217 16:14:12.547534   183 update_attempter.cc:317] Error event sent.

update_engine won't start

I got a strange problem, my firmware version is 2.5.1.45, in the xochitl interface, the "check for updates" button is grey, I cannot even click on it, then I used ssh to login to the remarkable, tried "/usr/sbin/update_engine", it tells me "update_engine: error while loading shared libraries: libnghttp2.so.14: cannot open shared object file: No such file or directory", then I used entware to install the libnghttp2 1.38 - 1.43 to the "/usr/lib", all of them tells "update_engine: error while loading shared libraries: /usr/lib/libnghttp2.so.14: internal error", I've got no clue how to solve this problem, could you kindly help to look into it please? thank you

`Could not get owner of name 'no.remarkable.update1': no such name`

I'm trying to upgrade my tablet from 3.0.5.56 to 3.2.3.1595.

On the computer (macOS 13.4.1(c)) ...

$ ifconfig en6
en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6467<RXCSUM,TXCSUM,VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 6a:98:e1:54:d9:df
	inet6 fe80::18e1:819d:94fb:b15e%en6 prefixlen 64 secured scopeid 0x1d
	inet 10.11.99.3 netmask 0xfffffff8 broadcast 10.11.99.7
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active

$ python3 serve.py 10.11.99.3
3.2.3.1595
Device should use:  http://10.11.99.3:8000/
Available updates: {'reMarkable2': ('3.2.3.1595', '3.2.3.1595_reMarkable2-fTtpld3Mvn-.signed')}
Starting fake updater: 8000

On the tablet ...

$ ssh rm2
ｒｅＭａｒｋａｂｌｅ
╺━┓┏━╸┏━┓┏━┓   ┏━┓╻ ╻┏━╸┏━┓┏━┓
┏━┛┣╸ ┣┳┛┃ ┃   ┗━┓┃ ┃┃╺┓┣━┫┣┳┛
┗━╸┗━╸╹┗╸┗━┛   ┗━┛┗━┛┗━┛╹ ╹╹┗╸
reMarkable: ~/ cd /usr/share/remarkable/
reMarkable: /usr/share/remarkable/ who
root            pts/0           00:00   Jul 24 23:37:01  ::ffff:10.11.99.3
reMarkable: /usr/share/remarkable/ nano update.conf
reMarkable: /usr/share/remarkable/ cat update.conf
[General]
#REMARKABLE_RELEASE_APPID={98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}
#SERVER=https://updates.cloud.remarkable.engineering/service/update2
#GROUP=Prod
#PLATFORM=reMarkable2
REMARKABLE_RELEASE_VERSION=3.0.5.56
SERVER=http://10.11.99.3:8000
reMarkable: /usr/share/remarkable/ update_engine_client -check_for_update
I20230724 23:40:29.939951  2064 update_engine_client.cc:271] Initiating update check and install.
W20230724 23:40:29.944379  2064 update_engine_client.cc:64] Error getting dbus proxy for no.remarkable.update1: GError(3): Could not get owner of name 'no.remarkable.update1': no such name
I20230724 23:40:29.944501  2064 update_engine_client.cc:54] Retrying to get dbus proxy. Try 2/4
W20230724 23:40:39.945904  2064 update_engine_client.cc:64] Error getting dbus proxy for no.remarkable.update1: GError(3): Could not get owner of name 'no.remarkable.update1': no such name
I20230724 23:40:39.946043  2064 update_engine_client.cc:54] Retrying to get dbus proxy. Try 3/4
W20230724 23:40:49.947408  2064 update_engine_client.cc:64] Error getting dbus proxy for no.remarkable.update1: GError(3): Could not get owner of name 'no.remarkable.update1': no such name
I20230724 23:40:49.947548  2064 update_engine_client.cc:54] Retrying to get dbus proxy. Try 4/4
W20230724 23:40:59.948927  2064 update_engine_client.cc:64] Error getting dbus proxy for no.remarkable.update1: GError(3): Could not get owner of name 'no.remarkable.update1': no such name
E20230724 23:40:59.949087  2064 update_engine_client.cc:70] Giving up -- unable to get dbus proxy for no.remarkable.update1
reMarkable: /usr/share/remarkable/

Any idea what's going wrong here?

[USER ERROR: FIXED] Unable to connect to server with 3.0.4.1305 and downgrade (RM2)

Let me prefix this by saying I'm an idiot. I went from 2.x (forgot the exact version) and upgraded to 3.x. I discovered that 3.x was missing a feature a really loved ("light sleep" mode) and didn't know about ddvk so I figured let's try a beta version and see if they put it back. Nope. Which then of course made it so that I can't simply use the switch.sh script: I now have two different 3.x versions on my partitions, one retail one beta. So I tried to use the server downgrade method. I'm on a Win 10 PC with Python 3.11.1. Here's what I did:

• Copied 2.9x firmware to the updates folder
• discovered my USB IP address on my Win 10 machine: it's 10.11.99.1, not 10.11.99.2, I can see this along with my wifi IP in Help->Copyright and Licenses to verify
• started just like the instructions say: python serve.py 10.11.99.1

I see what looks like it's working: it says:
python .\serve.py 10.11.99.1
2.9.0.204
Device should use: http://10.11.99.1:8000/
Available updates: {'reMarkable': ('2.9.0.204', '2.9.0.204_reMarkable.signed')}
Starting fake updater: 8000

ssh into my device via the USB address using PuTTY and edit /usr/share/remarkable/update.conf and just simply add this line at the end of the file: SERVER=http://10.11.99.1:8000 (yes I've tried also using a trailing /, no difference). Here's what the contents of the file looked liked after modification:

[General]
#REMARKABLE_RELEASE_APPID={98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}
#SERVER=https://updates.cloud.remarkable.engineering/service/update2
#GROUP=Prod
#PLATFORM=reMarkable2
REMARKABLE_RELEASE_VERSION=3.0.4.1305
SERVER=http://10.11.99.1:8000

Go to Menu->Settings->General, click software version, tap check for updates, and it just simply says on the device "Error checking for update" and no output from the python console on the PC. So I go the CLI route to get more detailed info. Just to verify I'm doing the CLI right, here's what I did after SSHing from my PC into that same USB IP address:

systemctl start update-engine
update_engine_client -check_for_update
journalctl -u update-engine -f

Looking at the output, it seems the primary issue is that it can't connect to the ddvk python server as it says "Unable to get http response code: Failed to connect to 10.11.99.1 port 8000: Connection refused"

I should note that yes, from my SSH session inside the tablet I can ping 10.11.99.1:8000

I presume any other errors are the result of this. I don't know why it can't connect. I tried disabling all firewall settings just in case. I also tried the wifi IP for all the above steps as well, same problem. If you're curious about the full output from the CLI, it is the following:

I20221226 18:06:58.675487 472 update_engine_client.cc:271] Initiating update check and install.
-- Logs begin at Wed 2022-12-21 02:52:08 UTC. --
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]:
Dec 26 18:06:58 reMarkable update_engine[413]: I20221226 18:06:58.694192 413 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Dec 26 18:06:58 reMarkable update_engine[413]: I20221226 18:06:58.694440 413 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Dec 26 18:06:58 reMarkable update_engine[413]: E20221226 18:06:58.695248 413 libcurl_http_fetcher.cc:264] Unable to get http response code: Failed to connect to 10.11.99.1 port 8000: Connection refused
Dec 26 18:06:58 reMarkable update_engine[413]: I20221226 18:06:58.695456 413 libcurl_http_fetcher.cc:281] No HTTP response, retry 1
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.936008 413 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.936373 413 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Dec 26 18:07:08 reMarkable update_engine[413]: E20221226 18:07:08.937165 413 libcurl_http_fetcher.cc:264] Unable to get http response code: Failed to connect to 10.11.99.1 port 8000: Connection refused
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937408 413 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937479 413 libcurl_http_fetcher.cc:297] Error buffer: Failed to connect to 10.11.99.1 port 8000: Connection refused
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937521 413 omaha_request_action.cc:670] Omaha request response:
Dec 26 18:07:08 reMarkable update_engine[413]: E20221226 18:07:08.937562 413 omaha_request_action.cc:686] Omaha request network transfer failed.
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937638 413 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937682 413 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937723 413 update_attempter.cc:313] Processing Done.
Dec 26 18:07:08 reMarkable update_engine[413]: E20221226 18:07:08.937810 413 update_attempter.cc:685] Update failed.
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937858 413 utils.cc:750] Converting error code 2000 to kActionCodeOmahaErrorInHTTPResponse
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937901 413 payload_state.cc:104] Updating payload state for error code: 37 (kActionCodeOmahaErrorInHTTPResponse)
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.937947 413 payload_state.cc:110] Ignoring failures until we get a valid Omaha response.
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.938460 413 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.939330 413 omaha_request_action.cc:280] Posting an Omaha request to http://10.11.99.1:8000
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.939412 413 omaha_request_action.cc:281] Request:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]:
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.939465 413 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.939666 413 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Dec 26 18:07:08 reMarkable update_engine[413]: E20221226 18:07:08.940367 413 libcurl_http_fetcher.cc:264] Unable to get http response code: Failed to connect to 10.11.99.1 port 8000: Connection refused
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940593 413 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940655 413 libcurl_http_fetcher.cc:297] Error buffer: Failed to connect to 10.11.99.1 port 8000: Connection refused
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940699 413 omaha_request_action.cc:670] Omaha request response:
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940752 413 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940793 413 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940831 413 update_attempter.cc:313] Processing Done.
Dec 26 18:07:08 reMarkable update_engine[413]: I20221226 18:07:08.940871 413 update_attempter.cc:317] Error event sent.

Timeout error

my RM1 version is 3.2.3.1595 and i want to downgrade to 2.15.1.1189, but it shows Unable to get http response code: Connection timed out after 30995 milliseconds

C:\Users\hhjj\Desktop\remarkable-update-main
λ python serve.py 10.11.99.2
2.15.1.1189
Device should use: http://10.11.99.2:8000/
Available updates: {'reMarkable': ('2.15.1.1189', '2.15.1.1189_reMarkable-Xdvv3lBmE4-.signed')}
Starting fake updater: 8000

update.conf:
[General]
#REMARKABLE_RELEASE_APPID={98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}
#SERVER=https://updates.cloud.remarkable.engineering/service/update2
#GROUP=Prod
#PLATFORM=reMarkable
REMARKABLE_RELEASE_VERSION=3.2.3.1595
SERVER=http://10.11.99.2:8000

ssh:

root@reMarkable:~# ping 10.11.99.2

PING 10.11.99.2 (10.11.99.2): 56 data bytes
64 bytes from 10.11.99.2: seq=0 ttl=128 time=0.328 ms
64 bytes from 10.11.99.2: seq=1 ttl=128 time=1.166 ms
64 bytes from 10.11.99.2: seq=2 ttl=128 time=0.954 ms
64 bytes from 10.11.99.2: seq=3 ttl=128 time=0.519 ms
64 bytes from 10.11.99.2: seq=4 ttl=128 time=0.979 ms
64 bytes from 10.11.99.2: seq=5 ttl=128 time=1.119 ms
64 bytes from 10.11.99.2: seq=6 ttl=128 time=0.326 ms
64 bytes from 10.11.99.2: seq=7 ttl=128 time=0.405 ms
64 bytes from 10.11.99.2: seq=8 ttl=128 time=0.313 ms
64 bytes from 10.11.99.2: seq=9 ttl=128 time=0.633 ms
64 bytes from 10.11.99.2: seq=10 ttl=128 time=1.219 ms
^C
--- 10.11.99.2 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 0.313/0.723/1.219 ms
root@reMarkable:# systemctl start update-engine
root@reMarkable:# update_engine_client -check_for_update
I20230623 14:33:16.980118 30249 update_engine_client.cc:271] Initiating update check and install.
root@reMarkable:~# journalctl -u update-engine -f
Journal file /var/log/journal/8a08a26d1e3b49bf9fb374fcec989509/system.journal is truncated, ignoring file.
-- Logs begin at Tue 2023-06-20 12:06:58 UTC. --
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]:
Jun 23 14:33:17 reMarkable update_engine[4268]: I20230623 14:33:17.015980 4268 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Jun 23 14:33:17 reMarkable update_engine[4268]: I20230623 14:33:17.016203 4268 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Jun 23 14:33:17 reMarkable update_engine[4268]: I20230623 14:33:17.016713 4268 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Jun 23 14:33:47 reMarkable update_engine[4268]: E20230623 14:33:47.819561 4268 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timed out after 30804 milliseconds
Jun 23 14:33:47 reMarkable update_engine[4268]: I20230623 14:33:47.820036 4268 libcurl_http_fetcher.cc:281] No HTTP response, retry 1
Jun 23 14:33:57 reMarkable update_engine[4268]: I20230623 14:33:57.828977 4268 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Jun 23 14:33:57 reMarkable update_engine[4268]: I20230623 14:33:57.829397 4268 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Jun 23 14:33:57 reMarkable update_engine[4268]: I20230623 14:33:57.830214 4268 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Jun 23 14:34:28 reMarkable update_engine[4268]: E20230623 14:34:28.819518 4268 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timed out after 30990 milliseconds
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.819752 4268 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.819814 4268 libcurl_http_fetcher.cc:297] Error buffer: Connection timed out after 30990 milliseconds
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.819849 4268 omaha_request_action.cc:670] Omaha request response:
Jun 23 14:34:28 reMarkable update_engine[4268]: E20230623 14:34:28.819878 4268 omaha_request_action.cc:686] Omaha request network transfer failed.
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.819942 4268 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.819988 4268 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.820017 4268 update_attempter.cc:313] Processing Done.
Jun 23 14:34:28 reMarkable update_engine[4268]: E20230623 14:34:28.820080 4268 update_attempter.cc:685] Update failed.
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.820116 4268 utils.cc:750] Converting error code 2000 to kActionCodeOmahaErrorInHTTPResponse
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.820145 4268 payload_state.cc:104] Updating payload state for error code: 37 (kActionCodeOmahaErrorInHTTPResponse)
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.820176 4268 payload_state.cc:110] Ignoring failures until we get a valid Omaha response.
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.824244 4268 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.824855 4268 omaha_request_action.cc:280] Posting an Omaha request to http://10.11.99.2:8000
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.824918 4268 omaha_request_action.cc:281] Request:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]:
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.824957 4268 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.825111 4268 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
Jun 23 14:34:28 reMarkable update_engine[4268]: I20230623 14:34:28.825541 4268 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Jun 23 14:34:59 reMarkable update_engine[4268]: E20230623 14:34:59.819463 4268 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timed out after 30995 milliseconds
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819694 4268 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819753 4268 libcurl_http_fetcher.cc:297] Error buffer: Connection timed out after 30995 milliseconds
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819787 4268 omaha_request_action.cc:670] Omaha request response:
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819828 4268 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819861 4268 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819890 4268 update_attempter.cc:313] Processing Done.
Jun 23 14:34:59 reMarkable update_engine[4268]: I20230623 14:34:59.819923 4268 update_attempter.cc:317] Error event sent.
3.2.3.1595

Tablet won't talk to fake server after downgrade

Running the hack from a Mac's Terminal on a RM2 with the latest firmware 2.7.1.53, but all it does is it keeps saying I'm up to date. I think I've done all the steps as required but there seems to be no desired effect when running update_engine_client -check_for_update or pressing the "Check for updates" box in the UI.

• I placed the 2.5.1.47_reMarkable2.signed update file in the /updates folder
• I modified the update.conf file with SERVER=http://my-host-name:8000 and also tried with my IP SERVER=http://my.ip.address:8000
• I ran python3 serve.py with and without changing line 46 to host = "my.ip.address"
  Output:

    Device should use:  http://<built-in function gethostname>:8000/
    Available updates: {'reMarkable2': ('2.5.1.47', '2.5.1.47_reMarkable2.signed')}
    Starting fake updater: 8000

• Depending on the tinkering, I would also get Device should use: http://my.ip.address:8000/ or Device should use: http://my-host-name:8000/ on the first line
• On the RM2 I ping my host with port 8000 to make sure it's reachable
• I enable automatic updates in the UI then run update_engine_client -check_for_update
  Output:
  I20210607 12:31:08.343346 384 update_engine_client.cc:271] Initiating update check and install.
• If I am on the Software screen on the RM2 at the same time, I can see that running the command triggers an update check ("Checking..."), which then displays a check mark with message "Your device is up to date."

So all looks like the RM2 is talking to the legit remarkable's server and reports that the installed version is the latest.

Looking at the logs:

root@reMarkable:~# journalctl -u update-engine -f
-- Logs begin at Mon 2021-06-07 11:57:58 UTC. --
Jun 07 12:34:26 reMarkable update_engine[188]:     <ping status="ok"/>
Jun 07 12:34:26 reMarkable update_engine[188]:   </app>
Jun 07 12:34:26 reMarkable update_engine[188]: </response>
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.105146   188 omaha_request_action.cc:444] No update.
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.105720   188 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.106050   188 omaha_response_handler_action.cc:38] There are no updates. Aborting.
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.106323   188 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing.
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.106623   188 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.106885   188 update_attempter.cc:313] Processing Done.
Jun 07 12:34:26 reMarkable update_engine[188]: I20210607 12:34:26.107182   188 update_attempter.cc:351] No update.

Out of curiosity I tried running switch.sh on the RM2 and I get this:

root@reMarkable:~# ./switch.sh
new: 2
fallback: 3

Is there something I'm missing or is it just not going to work with this specific downgrade?

Why can't my remarkable2 be upgraded?

Via the CLI
reMarkable: ~/ systemctl start update-engine
Failed to start update-engine.service: Unit update-engine.service is masked.

How to solve the above problems？
Thank you.

Not working as of beta 3.1.1.1415

The server line does not appear in xochitl.conf.
I performed the other actions and get this when checking for update:

-- Logs begin at Wed 2023-01-18 22:15:35 UTC. --
Jan 19 08:15:58 reMarkable update_engine[183]:
Jan 19 08:15:58 reMarkable update_engine[183]:
Jan 19 08:15:58 reMarkable update_engine[183]:
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.429481 183 omaha_request_action.cc:444] No update.
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.430349 183 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.430847 183 omaha_response_handler_action.cc:38] There are no updates. Aborting.
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.431273 183 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing.
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.431676 183 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.432050 183 update_attempter.cc:313] Processing Done.
Jan 19 08:15:58 reMarkable update_engine[183]: I20230119 08:15:58.432529 183 update_attempter.cc:351] No update.

Add instructions on how to get other versions

I would be nice to have a link to the source of all versions from remarkable itself.

Like, how to get it for the latest hack compatible version 2.8.0.98?

Btw, thanks for doing all this. :D

Error updating

Followed all the instructions but after showing updating to 2.8 for a few seconds it says error updating,,, (I'm trying to go from 2.9 to 2.8) Stuck on what to do here. Rebooting afterwards with and without running switch.sh does nothing. Need help

Heres my log from terminal which can hopefully clear something up:
requested: 2.9.1.217
platform: reMarkable2
Response:

192.168.0.105 - - [21/Aug/2021 02:00:18] "POST / HTTP/1.1" 200 -

Update done

SyntaxError

Hi, I'm trying to update from 3.5 to 3.3 but I get stuck at the first point.

josef-imac:remarkable-update-main pepikvaio$ python serve.py 10.11.99.2
File "serve.py", line 46
url = f"http://{host}:{port}/"
^
SyntaxError: invalid syntax

Example upgrade links no longer work

The example upgrade links are now returning 404s

Unable to downgrade 3.0.4.1305 (RM2)

I'm having trouble downgrading from 3.04.1305 to 2.15.1.1189 on the reMarkable 2.

How Far I've Gotten

1. After downloading the firmware release into ./updates, I run python3 serve.py 192.168.1.65 on my laptop.

2.15.1.1189
Device should use:  http://192.168.1.65:8000/
Available updates: {'reMarkable2': ('2.15.1.1189', '2.15.1.1189_reMarkable2-wVbHkgKisg-.signed')}
Starting fake updater: 8000

3. Second, I ssh into the remarkable via wifi and modify the update.conf file:

  1 [General]
  2 #REMARKABLE_RELEASE_APPID={98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}
  3 SERVER=http://192.168.1.65:8000
  4 #SERVER=https://updates.cloud.remarkable.engineering/service/update2
  5 #GROUP=Prod
  6 #PLATFORM=reMarkable2
  7 REMARKABLE_RELEASE_VERSION=3.0.4.1305

4. After saving and closing the file, I open the reMarkable UI and check for updates, but I keep getting the Error checking for update. message. I'm stuck at this step. No update happens.

Debugging Attempts

1. I've tried rebooting the reMarkable and checking for updates again via the UI. Same error occurs.
2. In the reMarkable CLI, I tried starting the update engine, triggered an update, and ran journalctl -u update-engine -f. The logs say I'm getting no HTTP response code. So, the update engine times out and tries again indefinitely.

reMarkable update_engine[312]: I20230520 18:02:51.441040   312 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
May 20 18:02:51 reMarkable update_engine[312]: I20230520 18:02:51.441242   312 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP
May 20 18:02:51 reMarkable update_engine[312]: I20230520 18:02:51.441834   312 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
May 20 18:03:22 reMarkable update_engine[312]: E20230520 18:03:22.438445   312 libcurl_http_fetcher.cc:264] Unable to get http response code: Connection timed out after 30997 milliseconds
May 20 18:03:22 reMarkable update_engine[312]: I20230520 18:03:22.438773   312 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
May 20 18:03:22 reMarkable update_engine[312]: I20230520 18:03:22.438835   312 libcurl_http_fetcher.cc:297] Error buffer: Connection timed out after 30997 milliseconds

Any suggestions?

Flash error after checking update

Hi, dear dev.

Recently I met another device which is unable to update but with a strange response.

At first I thought it was the time, so I went into SSH and modified its time. However it still got error connecting to server.

Then I tried to host a update server and, it did work, but not for long.
After triggering update, it did received the package information. Check pic.
On the device it behaves like this: When I trigger update, the device-side responses that it's downloading file, yet after few seconds it stopped and showed ERROR: error updating. Please check following pic.

Then I tried force flashing the device with the tools under extractor/. The environment is a Ubuntu 21.10 server in VMWare Workststion 16, on Windows 10. I extracted the firmware then bash push.sh out into the device. I entered the ssh password as instructed, and no error was shown. Yet after rebooting the device, it's still the original version.

Thus I'm confused if there's something wrong with this device.

It would be nice if you could please offer some help.

Thanks and have a good life :))

Thanks all

As a new RM2 user I lost my Hacks when auto-update kicked in from 2.8 to 2.9.

When @ddvk released the 2.9 Hack I realised I wasn't on quite the right verison, so I needed to use remarkable-update

Not understanding quite well enough remarkable-update I managed to upgrade to 2.10.x

I went through it several times more and have now downgraded to the correct 2.9.x and have the latest remarkable-hacks successfully installed.

Thanks so much to all the contribs on this, it's brilliant. Without the Hacks, RM2 OS is just not good enough.

I think the readme for remarkable-update could be a little clearer, I'm happy happy to edit it, though note sure how to go about requesting access or whatever.

2.14 update link

Hi, i'm currently using a rm with software 2.12 toltec and ddvk-hacks. I want to update to at least 2.14 to get tags, however the tablet only wants to update to 2.15 (incompatible with toltec), so i need this tool to select the proper version. The problem is i can't find anywhere the links to get the right version, and changing the url doesn't work. How can we find the new updates download links ?
thanks in advance

edit: welp 2 seconds after posting this issue (despite having searched the entire web before...) i found the filename for version 2.14.1.866 in issue #21 from which i deduced the url : https://updates-download.cloud.remarkable.engineering/build/reMarkable%20Device%20Beta/RM110/2.14.1.866/2.14.1.866_reMarkable2-JLWa2mnXu1-.signed
It would still be useful to have instructions on how to find new versions

Where to find builds for rM 1?

Hello, thanks for putting together this script. I've been trying to roll back my rM1 to some version of 2.5, since the last update borked remux. Given that the build mentioned in the readme is for rM2, I was wondering if you could point me towards where to find an appropriate build. Very much appreciate your time and help.

DNS issue

It is probably worth mentioning in the readme that, if the machine hosting the server has a name but this name is not resolved by the DNS server, the update will fail. This happens for example when trying the update via usb. A quick fix to this is to add the name to the remarkable's /etc/hosts.

Difficulty finding correct IP host

If 10.11.99.2 doesn't work you can check which IP is online:

• Open CMD as admin and enter "ipconfig";
• Search for "10.11.99.x" and copy the correct digit;
• Then follow the steps again.

You can check if the IP works by entering :"ping 10.11.99.x" in cli (Remarkable's ssh connection)
(where 'x' is your correct digit of course.

Error Updating

I get an error when attempting to downgrade from 2.7.1.53 to 2.7.0.51 on the rM2. The following is the output on the rM2. Any ideas why it's giving an error?

root@reMarkable:/# journalctl -u update-engine -f -- Logs begin at Tue 2021-06-01 15:22:06 UTC. -- Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.361387 889 omaha_request_action.cc:584] Payload size = 67056686 bytes Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.361629 889 omaha_request_action.cc:610] Found 1 action(s). Processing the postinstall action. Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.361757 889 payload_state.cc:208] Payload backoff logic is disabled. Can proceed with the download Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.361888 889 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.361940 889 omaha_response_handler_action.cc:45] Using Url 0 as the download url this time Jun 02 19:48:59 reMarkable update_engine[889]: E20210602 19:48:59.366096 889 payload_processor.cc:540] prefs->GetInt64(kPrefsUpdateStateNextOperation, &next_operation) && next_operation != kUpdateStateOperationInvalid && next_operation > 0 failed. Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.373196 889 omaha_response_handler_action.cc:94] Using this install plan: Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.373294 889 install_plan.cc:57] InstallPlan: , new_update, url: http://evon-ThinkPad-X1-Carbon:8000/updates/2.7.0.51_reMarkable2.signed, payload size: 67056686, payload hash: +fGmveJ5GNtEd5iBQyseN+eMm2yl7grdRrVitKJnx40=, partition_path: /dev/mmcblk2p2, kernel_path: , postinst_args: NEW_VERSION=2.7.0.51, old_partition_path: /dev/mmcblk2p3, old_kernel_path: Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.373908 889 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaResponseHandlerAction, starting FilesystemCopierAction Jun 02 19:48:59 reMarkable update_engine[889]: I20210602 19:48:59.374161 889 filesystem_copier_action.cc:335] Filesystem size: 283115520 Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.911382 889 filesystem_copier_action.cc:310] Hash: EaNYv4cIcEIATctXVn78Pr9CO2u10s3dIVC2uiwAeNc= Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.911690 889 action_processor.cc:99] ActionProcessor::ActionComplete: finished FilesystemCopierAction, starting KernelCopierAction Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.911749 889 action_processor.cc:99] ActionProcessor::ActionComplete: finished KernelCopierAction, starting OmahaRequestAction Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.912370 889 omaha_request_action.cc:280] Posting an Omaha request to http://192.168.1.30:8000 Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.912427 889 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?> Jun 02 19:49:14 reMarkable update_engine[889]: <request protocol="3.0" version="2.7.1.53" requestid="{14a59703-62e1-4f5f-883a-606baaecec88}" sessionid="{b62c0a1f-0a9e-4087-8360-86225a8a8127}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1"> Jun 02 19:49:14 reMarkable update_engine[889]: <os version="codex 3.1.3" platform="reMarkable2" sp="2.7.1.53_armv7l" arch="armv7l"></os> Jun 02 19:49:14 reMarkable update_engine[889]: <app appid="{98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}" version="2.7.1.53" track="Prod" ap="Prod" bootid="{83a7d5b8-ced7-4659-b677-ba297150e94c}" oem="RM110-109-71290" oemversion="3.1.3" alephversion="2.7.1.53" machineid="ac4e502f95d146a4beefee8ce044e240" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="2.7.0.51" brand="" client="" > Jun 02 19:49:14 reMarkable update_engine[889]: <event eventtype="13" eventresult="1"></event> Jun 02 19:49:14 reMarkable update_engine[889]: </app> Jun 02 19:49:14 reMarkable update_engine[889]: </request> Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.912462 889 libcurl_http_fetcher.cc:50] Starting/Resuming transfer Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.912626 889 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP Jun 02 19:49:14 reMarkable update_engine[889]: I20210602 19:49:14.913126 889 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds. Jun 02 19:49:15 reMarkable update_engine[889]: E20210602 19:49:15.432080 889 libcurl_http_fetcher.cc:264] Unable to get http response code: Empty reply from server Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.432796 889 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.433135 889 libcurl_http_fetcher.cc:297] Error buffer: Empty reply from server Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.433377 889 omaha_request_action.cc:670] Omaha request response: Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.433600 889 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting DownloadAction Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.433827 889 install_plan.cc:57] InstallPlan: , new_update, url: http://evon-ThinkPad-X1-Carbon:8000/updates/2.7.0.51_reMarkable2.signed, payload size: 67056686, payload hash: +fGmveJ5GNtEd5iBQyseN+eMm2yl7grdRrVitKJnx40=, partition_path: /dev/mmcblk2p2, kernel_path: , postinst_args: NEW_VERSION=2.7.0.51, old_partition_path: /dev/mmcblk2p3, old_kernel_path: Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.434185 889 update_attempter.cc:443] Download status: active Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.434617 889 multi_range_http_fetcher.cc:34] starting first transfer Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.435056 889 multi_range_http_fetcher.cc:68] starting transfer of range 0+? Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.435408 889 libcurl_http_fetcher.cc:50] Starting/Resuming transfer Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.435822 889 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.436558 889 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds. Jun 02 19:49:15 reMarkable update_engine[889]: E20210602 19:49:15.451444 889 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: evon-ThinkPad-X1-Carbon Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.451771 889 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.451831 889 libcurl_http_fetcher.cc:297] Error buffer: Could not resolve host: evon-ThinkPad-X1-Carbon Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.451865 889 multi_range_http_fetcher.cc:185] Received transfer complete. Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.451895 889 multi_range_http_fetcher.cc:130] TransferEnded w/ code 0 Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.451925 889 multi_range_http_fetcher.cc:173] Done w/ all transfers Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454236 889 update_attempter.cc:443] Download status: inactive Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454335 889 action_processor.cc:81] ActionProcessor::ActionComplete: DownloadAction action failed. Aborting processing. Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454376 889 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type DownloadAction Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454407 889 update_attempter.cc:313] Processing Done. Jun 02 19:49:15 reMarkable update_engine[889]: E20210602 19:49:15.454546 889 update_attempter.cc:685] Update failed. Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454591 889 payload_state.cc:104] Updating payload state for error code: 9 (kActionCodeDownloadTransferError) Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454628 889 payload_state.cc:287] Incrementing the URL failure count Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.454658 889 payload_state.cc:454] Current URL (Url0)'s Failure Count = 3 Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.455826 889 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.456686 889 omaha_request_action.cc:280] Posting an Omaha request to http://192.168.1.30:8000 Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.456743 889 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?> Jun 02 19:49:15 reMarkable update_engine[889]: <request protocol="3.0" version="2.7.1.53" requestid="{2afbc372-6cf1-44cc-a0b1-562fb09c8f6d}" sessionid="{b62c0a1f-0a9e-4087-8360-86225a8a8127}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1"> Jun 02 19:49:15 reMarkable update_engine[889]: <os version="codex 3.1.3" platform="reMarkable2" sp="2.7.1.53_armv7l" arch="armv7l"></os> Jun 02 19:49:15 reMarkable update_engine[889]: <app appid="{98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}" version="2.7.1.53" track="Prod" ap="Prod" bootid="{83a7d5b8-ced7-4659-b677-ba297150e94c}" oem="RM110-109-71290" oemversion="3.1.3" alephversion="2.7.1.53" machineid="ac4e502f95d146a4beefee8ce044e240" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="2.7.0.51" brand="" client="" > Jun 02 19:49:15 reMarkable update_engine[889]: <event eventtype="3" eventresult="0" errorcode="268435465"></event> Jun 02 19:49:15 reMarkable update_engine[889]: </app> Jun 02 19:49:15 reMarkable update_engine[889]: </request> Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.456782 889 libcurl_http_fetcher.cc:50] Starting/Resuming transfer Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.456950 889 libcurl_http_fetcher.cc:163] Setting up curl options for HTTP Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.457592 889 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds. Jun 02 19:49:15 reMarkable update_engine[889]: E20210602 19:49:15.468027 889 libcurl_http_fetcher.cc:264] Unable to get http response code: Empty reply from server Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468266 889 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468322 889 libcurl_http_fetcher.cc:297] Error buffer: Empty reply from server Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468349 889 omaha_request_action.cc:670] Omaha request response: Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468386 889 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468412 889 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468436 889 update_attempter.cc:313] Processing Done. Jun 02 19:49:15 reMarkable update_engine[889]: I20210602 19:49:15.468472 889 update_attempter.cc:317] Error event sent.

Remarkable can't connect to server

Hi. Please excuse me, if there are some protocols I don't follow, this is my first time opening an issue on github.
I want to rollback from 2.9 beta to 2.8.

I can ping my host/server from the tablet, but the update-engine can't connect to host.
Executed on my laptop (hostname: x220)
❯ python3 serve.py
Using hostname, to override use: ./serve.py hostname
Device should use: http://x220:8000/
Available updates: {'reMarkable2': ('2.7.0.51', '2.7.0.51_reMarkable2.signed')}
Starting fake updater: 8000

Executed on remarkable by SSH over wifi
reMarkable: ~/ ping x220
PING x220 (192.168.1.123): 56 data bytes
64 bytes from 192.168.1.123: seq=0 ttl=64 time=3.354 ms

-- Logs begin at Fri 2021-08-06 12:01:24 UTC. --
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.862864 553 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 06 21:35:32 reMarkable update_engine[553]: E20210806 21:35:32.873977 553 libcurl_http_fetcher.cc:264] Unable to get http response code: Failed to connect to x220 port 8000: No route to host
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874430 553 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874534 553 libcurl_http_fetcher.cc:297] Error buffer: Failed to connect to x220 port 8000: No route to host
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874603 553 omaha_request_action.cc:670] Omaha request response:
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874684 553 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874749 553 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874810 553 update_attempter.cc:313] Processing Done.
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874884 553 update_attempter.cc:317] Error event sent.
Aug 06 21:35:32 reMarkable update_engine[553]: I20210806 21:35:32.874990 553 update_check_scheduler.cc:82] Next update check in 49m34s

/usr/share/remarkable/update.conf file:
1 [general]
2 #remarkable_release_appid={98da7df2-4e3e-4744-9de6-ec931886abab}
3 #server=https://get-updates.cloud.remarkable.engineering/service/update2
4 server=http://x220:8000/
5 #group=prod
6 #platform=remarkable2
7 remarkable_release_version=2.9.0.153

Am I doing something wrong? Or is it some incompatibility with the 2.9 software?
Thanks for any help in advance

rm2 not updating past version 3.9.3

I originally found this discord page because of a problem i had with updating my remarkable. I bricked my remarkable a long time ago, and the last version i had installed was 3.0.4.1305. I then tried to update it to the newest version (3.10.2.2063), but that didn't work. I did not get an Error message, it just didn't change the version after Updating. I then used the Tool to make parcial updates and i got up to version 3.9.3.1986, but after that, this tool also didn't help.
Just to clarify, the reMarkable showed the following information:

• when pressing check for updates (after resetting the corresponding file to use the reMarkable update server), it found the newest version and downloaded it.
• It then installed it
• It then said to tap to restart and update to the newest version
• After the restart and looking into the settings, the version is still the old one.

Does anyone has a clue what is going on with my device or how i can resolve this issue?

P.S. I used codexctl to install the updates.

Error checking for update

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::daa1:65f7:379:a801%3
   IPv4 Address. . . . . . . . . . . : 192.168.68.65
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : fe80::2a87:baff:fe27:4b70%3
                                       192.168.68.1```

```C:\Users\Julian\Downloads\remarkable-update-main\remarkable-update-main>python serve.py 192.168.68.65
2.10.2.356
Device should use:  http://192.168.68.65:8000/
Available updates: {'reMarkable2': ('2.10.2.356', '2.10.2.356_reMarkable2-JLB6Ax3hnJ-.signed')}
Starting fake updater: 8000```

```[General]
#REMARKABLE_RELEASE_APPID={98DA7DF2-4E3E-4744-9DE6-EC931886ABAB}
#SERVER=https://updates.cloud.remarkable.engineering/service/update2
#GROUP=Prod
#PLATFORM=reMarkable2
REMARKABLE_RELEASE_VERSION=3.2.3.1595
SERVER=http://192.168.68.65:8000/```

```reMarkable: ~/ ping http://192.168.68.65:8000/
ping: bad port spec 'http://192.168.68.65:8000/'```

"Error checking update"
Not sure what the issue is but im not getting a downgrade to work

update-engine failed ‘core-dump’

Hi.

I hosted a server via python serve.py, and on device side curl <IP>:8000 works.

So when I tried

systemctl restart update-engine
update_engine_client -check_for_update

And I got only one line response like "starting update" or whatchamacallit.

While it's still "up to date" on device's update UI.

So when I use journactl to observe I saw this:

Since I'm now using a Win7 and unable to use WSL I can't use the method you mentioned before to wipe and force flash a firmware.

Any advice on what I should do, or is a normal phenomenon? Thanks!