Remarkable2 Bootloop on Update

[ClashTheBunny]

Hey folks, I'm facing a remarkable2 bootloop after doing an opkg update && opkg upgrade. I also checked "automatic updates" but didn't get prompted for an update. I then followed (possibly bad) advice from another post on here that suggested deleting /home/root/.entware, so I may have dug my hole a little deeper...

I am on 2.4 (As can be seen in the journalctl output below), and had a 2.5 firmware in updates (updates/2.5.0.27_reMarkable2.signed).

I can get a network connection over USB randomly. I haven't figured out how to predict turning it on and off will get me shell, but it happens on average every 10-15 times. I have a feeling that it's switching between active partitions and failing on one and succeeding sometimes on another.

The remarkable-fail.sh script is outputting a syntax error on line 87, so last crash time is very wrong/missing.

`while ! ssh -o ConnectTimeout=2 [email protected] journalctl -f; do sleep 1; done`

-- Logs begin at Mon 2021-08-23 17:36:40 UTC. --
Aug 25 02:48:03 reMarkable kernel: random: crng init done
Aug 25 02:48:03 reMarkable kernel: random: 7 urandom warning(s) missed due to ratelimiting
Aug 25 02:48:03 reMarkable systemd[1]: Started SSH Per-Connection Server (10.11.99.2:49198).
Aug 25 02:48:03 reMarkable dropbear[287]: Failed loading /etc/dropbear/dropbear_dss_host_key
Aug 25 02:48:03 reMarkable dropbear[287]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Aug 25 02:48:03 reMarkable dropbear[287]: Child connection from ::ffff:10.11.99.2:49198
Aug 25 02:48:03 reMarkable dropbear[285]: Pubkey auth succeeded for 'root' with key md5 15:91:f3:b6:2d:73:a3:f5:65:54:12:2c:a2:a9:3b:73 from ::ffff:10.11.99.2:49194
Aug 25 02:48:03 reMarkable dropbear[285]: Exit (root): Disconnect received
Aug 25 02:48:03 reMarkable dropbear[286]: Pubkey auth succeeded for 'root' with key md5 15:91:f3:b6:2d:73:a3:f5:65:54:12:2c:a2:a9:3b:73 from ::ffff:10.11.99.2:49196
Aug 25 02:48:03 reMarkable dropbear[287]: Pubkey auth succeeded for 'root' with key md5 15:91:f3:b6:2d:73:a3:f5:65:54:12:2c:a2:a9:3b:73 from ::ffff:10.11.99.2:49198
Aug 25 02:48:05 reMarkable systemd-networkd[138]: usb0: Configured
Aug 25 02:48:05 reMarkable systemd-timesyncd[171]: Network configuration changed, trying to establish connection.
Aug 25 02:48:05 reMarkable systemd-networkd-wait-online[151]: ignoring: lo
Aug 25 02:48:05 reMarkable systemd[1]: Started Wait for Network to be Configured.
Aug 25 02:48:05 reMarkable systemd[1]: Reached target Network is Online.
Aug 25 02:48:05 reMarkable systemd[1]: Started A simple mDNS responder.
Aug 25 02:48:05 reMarkable update_engine[182]: I0825 02:48:05.662451   182 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Aug 25 02:48:05 reMarkable update_engine[182]: I0825 02:48:05.662708   182 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS
Aug 25 02:48:05 reMarkable update_engine[182]: I0825 02:48:05.663108   182 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 25 02:48:06 reMarkable update_engine[182]: E0825 02:48:06.653527   182 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.653745   182 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.653805   182 libcurl_http_fetcher.cc:297] Error buffer: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.653844   182 omaha_request_action.cc:670] Omaha request response:
Aug 25 02:48:06 reMarkable update_engine[182]: E0825 02:48:06.653883   182 omaha_request_action.cc:686] Omaha request network transfer failed.
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.653966   182 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654007   182 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654047   182 update_attempter.cc:313] Processing Done.
Aug 25 02:48:06 reMarkable update_engine[182]: E0825 02:48:06.654126   182 update_attempter.cc:685] Update failed.
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654166   182 utils.cc:750] Converting error code 2000 to kActionCodeOmahaErrorInHTTPResponse
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654207   182 payload_state.cc:104] Updating payload state for error code: 37 (kActionCodeOmahaErrorInHTTPResponse)
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654250   182 payload_state.cc:110] Ignoring failures until we get a valid Omaha response.
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.654753   182 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.655619   182 omaha_request_action.cc:280] Posting an Omaha request to https://get-updates.cloud.remarkable.engineering/service/update2
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.655678   182 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?>
Aug 25 02:48:06 reMarkable update_engine[182]: <request protocol="3.0" version="2.4.1.30" requestid="{xxxx}" sessionid="{xxxx}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1">
Aug 25 02:48:06 reMarkable update_engine[182]:     <os version="codex 2.5.2" platform="reMarkable2" sp="2.4.1.30_armv7l" arch="armv7l"></os>
Aug 25 02:48:06 reMarkable update_engine[182]:     <app appid="xxxxx" version="2.4.1.30" track="Prod" ap="Prod" bootid="xxxxx" oem="RM110-xxx-xxxxx" oemversion="2.5.2" alephversion="2.4.1.30" machineid="xxxxx" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Aug 25 02:48:06 reMarkable update_engine[182]:         <event eventtype="3" eventresult="0" errorcode="2000"></event>
Aug 25 02:48:06 reMarkable update_engine[182]:     </app>
Aug 25 02:48:06 reMarkable update_engine[182]: </request>
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.655722   182 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.655918   182 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS
Aug 25 02:48:06 reMarkable update_engine[182]: I0825 02:48:06.656278   182 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 25 02:48:07 reMarkable update_engine[182]: E0825 02:48:07.653662   182 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.653884   182 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.653940   182 libcurl_http_fetcher.cc:297] Error buffer: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.653981   182 omaha_request_action.cc:670] Omaha request response:
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.654031   182 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.654071   182 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.654109   182 update_attempter.cc:313] Processing Done.
Aug 25 02:48:07 reMarkable update_engine[182]: I0825 02:48:07.654155   182 update_attempter.cc:317] Error event sent.
Aug 25 02:48:24 reMarkable remarkable-fail.sh[254]: /usr/bin/remarkable-fail.sh: line 87: 1629859704 - : syntax error: operand expected (error token is "- ")
Aug 25 02:48:24 reMarkable systemd[1]: remarkable-fail.service: Main process exited, code=exited, status=1/FAILURE
Aug 25 02:48:24 reMarkable systemd[1]: remarkable-fail.service: Failed with result 'exit-code'.
Aug 25 02:48:24 reMarkable systemd[1]: remarkable-fail.service: Service hold-off time over, scheduling restart.
Aug 25 02:48:24 reMarkable systemd[1]: remarkable-fail.service: Scheduled restart job, restart counter is at 1.
Aug 25 02:48:24 reMarkable systemd[1]: Stopped reMarkable fail application.
Aug 25 02:48:24 reMarkable systemd[1]: Started reMarkable fail application.
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: We've crashed 4 times
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: Last crashed 31 seconds ago
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: Running fsck
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: fsck from util-linux 2.32
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: e2fsck 1.43.8 (1-Jan-2018)
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: /dev/mmcblk2p2: clean, 8458/65024 files, 199345/260000 blocks
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: Trying to bring up wifi
Aug 25 02:48:24 reMarkable systemd[1]: Reloading.
Aug 25 02:48:24 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring.
Aug 25 02:48:24 reMarkable crashuploader[242]: "/home/root/" Has update, checking...
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: Force upgrade try number 4
Aug 25 02:48:24 reMarkable remarkable-fail.sh[318]: I0825 02:48:24.902359   343 update_engine_client.cc:271] Initiating update check and install.
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.908558   182 dbus_service.cc:62] Attempting interactive update
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.908643   182 update_attempter.cc:283] New update check requested
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919081   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919164   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919194   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919222   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919246   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919271   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919296   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919319   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919343   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919366   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919390   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919414   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919437   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919461   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: E0825 02:48:24.919483   182 omaha_request_params.cc:179] Error parsing serial number stream
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.920233   182 omaha_request_params.cc:75] Current group set to Prod
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.921097   182 update_attempter.cc:533] Not updating boot flags, we don't know the state of the application.
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.921156   182 update_attempter.cc:710] Scheduling an action processor start.
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.921634   182 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.922576   182 omaha_request_action.cc:280] Posting an Omaha request to https://get-updates.cloud.remarkable.engineering/service/update2
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.922641   182 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?>
Aug 25 02:48:24 reMarkable update_engine[182]: <request protocol="3.0" version="2.4.1.30" requestid="{xxxx}" sessionid="{xxxx}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1">
Aug 25 02:48:24 reMarkable update_engine[182]:     <os version="codex 2.5.2" platform="reMarkable2" sp="2.4.1.30_armv7l" arch="armv7l"></os>
Aug 25 02:48:24 reMarkable update_engine[182]:     <app appid="{xxxx}" version="2.4.1.30" track="Prod" ap="Prod" bootid="{xxxx}" oem="RM110-xxx-xxxxx" oemversion="2.5.2" alephversion="2.4.1.30" machineid="xxxx" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Aug 25 02:48:24 reMarkable update_engine[182]:         <ping active="1"></ping>
Aug 25 02:48:24 reMarkable update_engine[182]:         <updatecheck></updatecheck>
Aug 25 02:48:24 reMarkable update_engine[182]:         <event eventtype="3" eventresult="2" previousversion=""></event>
Aug 25 02:48:24 reMarkable update_engine[182]:     </app>
Aug 25 02:48:24 reMarkable update_engine[182]: </request>
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.922678   182 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.922804   182 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS
Aug 25 02:48:24 reMarkable update_engine[182]: I0825 02:48:24.923166   182 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 25 02:48:26 reMarkable update_engine[182]: E0825 02:48:26.654322   182 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:26 reMarkable update_engine[182]: I0825 02:48:26.654587   182 libcurl_http_fetcher.cc:281] No HTTP response, retry 1
Aug 25 02:48:36 reMarkable update_engine[182]: I0825 02:48:36.661844   182 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Aug 25 02:48:36 reMarkable update_engine[182]: I0825 02:48:36.662108   182 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS
Aug 25 02:48:36 reMarkable update_engine[182]: I0825 02:48:36.662530   182 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.652818   182 update_attempter.cc:533] Not updating boot flags, we don't know the state of the application.
Aug 25 02:48:37 reMarkable update_engine[182]: E0825 02:48:37.653050   182 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653223   182 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653285   182 libcurl_http_fetcher.cc:297] Error buffer: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653327   182 omaha_request_action.cc:670] Omaha request response:
Aug 25 02:48:37 reMarkable update_engine[182]: E0825 02:48:37.653367   182 omaha_request_action.cc:686] Omaha request network transfer failed.
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653448   182 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653492   182 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653532   182 update_attempter.cc:313] Processing Done.
Aug 25 02:48:37 reMarkable update_engine[182]: E0825 02:48:37.653611   182 update_attempter.cc:685] Update failed.
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653653   182 utils.cc:750] Converting error code 2000 to kActionCodeOmahaErrorInHTTPResponse
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653690   182 payload_state.cc:104] Updating payload state for error code: 37 (kActionCodeOmahaErrorInHTTPResponse)
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.653734   182 payload_state.cc:110] Ignoring failures until we get a valid Omaha response.
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.654251   182 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.655083   182 omaha_request_action.cc:280] Posting an Omaha request to https://get-updates.cloud.remarkable.engineering/service/update2
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.655143   182 omaha_request_action.cc:281] Request: <?xml version="1.0" encoding="UTF-8"?>
Aug 25 02:48:37 reMarkable update_engine[182]: <request protocol="3.0" version="2.4.1.30" requestid="{xxxx}" sessionid="{xxxx}" updaterversion="0.4.2" installsource="ondemandupdate" ismachine="1">
Aug 25 02:48:37 reMarkable update_engine[182]:     <os version="codex 2.5.2" platform="reMarkable2" sp="2.4.1.30_armv7l" arch="armv7l"></os>
Aug 25 02:48:37 reMarkable update_engine[182]:     <app appid="{xxxx}" version="2.4.1.30" track="Prod" ap="Prod" bootid="{xxxx}" oem="RM110-xxx-xxxxx" oemversion="2.5.2" alephversion="2.4.1.30" machineid="xxxx" lang="en-US" board="" hardware_class="" delta_okay="false" nextversion="0.0.0" brand="" client="" >
Aug 25 02:48:37 reMarkable update_engine[182]:         <event eventtype="3" eventresult="0" errorcode="2000"></event>
Aug 25 02:48:37 reMarkable update_engine[182]:     </app>
Aug 25 02:48:37 reMarkable update_engine[182]: </request>
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.655189   182 libcurl_http_fetcher.cc:50] Starting/Resuming transfer
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.655342   182 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS
Aug 25 02:48:37 reMarkable update_engine[182]: I0825 02:48:37.655717   182 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds.
Aug 25 02:48:38 reMarkable update_engine[182]: E0825 02:48:38.653106   182 libcurl_http_fetcher.cc:264] Unable to get http response code: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653333   182 libcurl_http_fetcher.cc:295] Transfer resulted in an error (0), 0 bytes downloaded
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653395   182 libcurl_http_fetcher.cc:297] Error buffer: Could not resolve host: get-updates.cloud.remarkable.engineering
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653439   182 omaha_request_action.cc:670] Omaha request response:
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653489   182 action_processor.cc:78] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653528   182 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653565   182 update_attempter.cc:313] Processing Done.
Aug 25 02:48:38 reMarkable update_engine[182]: I0825 02:48:38.653610   182 update_attempter.cc:317] Error event sent.
Connection to 10.11.99.1 closed by remote host.
kex_exchange_identification: read: Connection reset by peer
Connection reset by 10.11.99.1 port 22

If there's any other information I can get you, let me know. I'm guessing the update script is failing and then shutting down the host. I'm guessing for the 30 seconds or so I have shell I could move /sbin/poweroff out of the way, but that feels even more risky. I don't have a USB jig, so I'd like to not wait a month to get parts shipped to me.

[Eeems]

I would recommend against ever deleting /home/root/.entware without first removing any modifications to the root partition. The safer way is to run toltecctl uninstall.
Since you can still get SSH access in one of the partitions, I would recommend running the following when you can get access: systemctl stop xochitl. After which I would recommend taking a look to see what is configured, likely there are still files in place trying to load rm2fb's server with the xochitl binary, so you'll need to delete those files, and then it should stabilize.

If you find that the wrong partition is active when you manage to get things working, you can always mount the other partition to /mnt and perform a similar cleanup of the files.

[matteodelabre]

I'm sorry that you're facing this issue @ClashTheBunny–could you please share the link to that post that recommends removing /home/root/.entware so that we can make aure it doesn't mislead more users?

[ClashTheBunny]

It was this one that looked similar to what I was experiencing: ddvk/remarkable2-framebuffer#63 (comment)

[ClashTheBunny]

Is the best way possibly to just reinstall Toltec and rm2fb? I have it plugged into a RPi with those loops going, so I can set up internet access through it.

[ClashTheBunny]

The other option I was thinking was doing an update server on the RPi and running the update. Would that possibly put me in a worse place? I think my current partially working partition would be safe from getting wiped if it's the one that's running when I hit update?

It sure seems like a failed update from dmesg...

[matteodelabre]

Thanks for the link. Running an update from a local server does seem like the easiest solution to get back to a clean root partition. Your home partition will not be touched by the updater.

[ClashTheBunny]

I had to stop one of remarkable-fail xochitl update-engine, start the update server, start update-engine again, and it updated perfectly. I'm back to stock remarkable.

It was interesting that it would work pretty much every time it was "off" for a long time and I turned it on by plugging it in. So weird that it would loop with different mac addresses...

[ClashTheBunny]

Looks similar to ddvk/remarkable2-framebuffer#18 (comment)

[ClashTheBunny]

@jdkruzr, does this look like your problem? If you leave it off and unplugged for a while, does it come up the first time with an IP and then not come back after successive reboots?

[jdkruzr]

well, for one I'm not sure how I could tell whether it was "off" ;) how long should I leave it unplugged?

[ClashTheBunny]

I would try it 12 hours later and it worked most times.