Open
Description
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:8000and also tried with my IPSERVER=http://my.ip.address:8000 - I ran
python3 serve.pywith and without changing line 46 tohost = "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/orDevice 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?
Metadata
Metadata
Assignees
Labels
No labels