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.
RedTartan04
commented
8 months ago
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