search

ddvk / remarkable-update

force a full factory reset / re-update / upgrade
MIT License
172 stars 18 forks source link

Timeout error #36

Open cstrike99a opened 1 year ago

cstrike99a commented 1 year ago

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: <?xml version="1.0" encoding="UTF-8"?> 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

thespyboss commented 1 year ago

I am also having the same exact problem. It's both happening with a USB connection and a connection through my laptop's hotspot. Obviously the laptop and remarkable2 are connecting because I can force the remarkable2 to check for an update but as soon as the update starts moving the file, it fails and doesn't connect.

PK-4 commented 9 months ago

Hi, I have the similar issue 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.