Any way to rollback from 3.11? #71
Comments
|
From https://github.com/Jayy001/codexctl?tab=readme-ov-file#please-read-before-using
|
|
I would also like to do this. I think I understand what you're indicating should be done, but given the "nuclear" nature of the I'm assuming that you have to create a mount point for the new OS version, then |
|
#95 (comment) has instructions that go into further detail. Please refer to it instead
|
|
I'm in a similar boat. Got a new reMarkable 2 today mainly for 3rd party software and was super disappointed to learn that 3.11 stops me in my tracks. A few questions:
|
By issues, do you mean the new update mechanism that needs new development to support? Or do you mean for third party software? If that's the case, I would recommend looking at toltec-dev/toltec#820 instead of asking here.
You would just update like normally.
|
|
I ran Thanks again for the help! I rarely have to use |
Thanks for the instructions @Eeems, this was exactly what I was looking for! |
|
I've followed the directions above but at the last step
I must be misunderstanding something? UPDATE: Looking closely at Unrelated aside (just FYI): When I ran the
|
|
While I understand that this should be marked as completed because the issue is solved, I would argue that there should be a change to the main Readme.md file to make this solution more accessible. Either the instructions given here should be put in the Readme.md, or a link to this issue should be added. |
You are welcome to open a pull request |
Please open a new issue to track this |
|
The |
|
Restore didn't work for me, as it complained about fw_printenv and fw_setenv not being in the path, but copy-pasting the bash snippet into a script and running with bash worked. There's something about the PATH environment variable not being passed into that subprocess. |
|
|
Let's keep the issue open until we got the PR for the instructions then. |
Already merged |
|
EDIT: corrected the extract step In case this is helpful for anyone else in the short term, I was able to get things working with the following steps on MacOS 13.6 and a reMarkable 2, OS version 3.11.x: On my laptop: # Clone repos
git clone https://github.com/Jayy001/codexctl.git
git clone https://github.com/ddvk/remarkable-update.git
# Download the latest toltec-compatible image to my Downloads folder
cd /path/to/codexctl
pip3 install -r requirements.remote.txt
python3 codexctl.py download 2.15.1.1189
# Extract the image
cd /path/to/remarkable-update/extractor
pip3 install -r requirements.txt
mv ~/Downloads/2.15.1.1189_reMarkable2-wVbHkgKisg-.signed ./
extractor.py 2.15.1.1189_reMarkable2-wVbHkgKisg-.signed # will create a raw image file called `out`
# Copy the image to the reMarkable
# (I already have a DHCP reservation for `remarkable-dev` but you can substitute an IP address here)
scp ./out root@remarkable-dev:/home/root/remarkable-2.15.1.1189.img
# Copy the remarkable-update repo to the reMarkable, so we can run the `switch.sh` script
# (You can also just copy the contents of that one file)
scp -r /path/to/remarkable-update/ root@remarkable-dev:~/remarkable-updateThen after SSHing into the device: # Make sure the image is where I expect it
cd /home/root
ls -al
# List disk partitions
fdisk -l
# Figure out the active and fallback partitions (they are the digits at the end of /dev/mmcblk2p[NUM])
fw_printenv active_partition
fw_printenv fallback_partition
# My fallback partition was 2, so copy the image to that partition
dd if=/home/root/remarkable-2.15.1.1189.img of=/dev/mmcblk2p2
# Switch the active and fallback partitions
/home/root/remarkable-update/switch.sh
# Now reboot the device through the GUI (Menu > Settings > General > Restart)I know the maintainers are doing an awesome job keeping these utilities updated to work with the newer reMarkable OS versions, but I wanted to post this in case it helps anyone in the meantime. |
|
Is there a reason you aren't using the pre-compiled version of codexctl instead of manually running the source? EDIT: Actually, this should not have worked for you, |
Honestly, I forgot it was an option 😀 I was an hour or so into diving through the various linked issue convos and trying things over SSH that I thought to myself, "right, let's see how far I can get by running things from my own machine and copying them over."
Oops, I mis-remembered that step. I tried to modify |
I want to confirm that this was helpful on Linux. I followed you steps almost exactly and it worked. Thanks for writing it down and for all the people that contributed to the tools that allowed for the downgrade from 3.11. |
|
I recently tried to downgrade my Remarkable 1 using the procedure outlined in andrewjensen's post. I ran into an error with It looks like there's an extra byte in the image file? I followed the steps in downloading and extracting the file exactly, so I'm not sure where the error was introduced. |
|
You likely downloaded a rM2 image instead of a rM1 image. |
|
That was it exactly. Thanks for the help! |
Thank you, this worked perfectly. |
Would it be possible to go in a little more detail please? I'm attempting to downgrade from 3.12.4.4, to v3.11.2.5 for rmhacks.
After this process, I'm left with an "extracted" file, approx 280mb in size. I'm not 100% sure whether this file is now usable or not, given the public key error.
Any help would be appreciated. |
I don't see an error, just a warning. You can ignore the warning. It's just because 3.11 is the first version to have the new update mechanism, so the key file changed location. That's why it's a warning and not an error.
This would be the extracted raw partition image that you would use in the further steps.
Somewhere on the data directory, so under
|
Awesome. Thanks for your assistance. Managed to successfully roll it back to v3.11.2.5. Now for rmhacks. |
|
For anyone else looking for more detailed steps, here they are. Run codexctl.exe from the downloads folder (C:\users\username\downloads\codexctl.exe), with the download argument. Example - "C:\users\username\downloads\codexctl.exe download 3.11.2.5" Once downloaded, use the extract argument to extract the raw image. You should be presented with a file called "extracted" Example - "C:\users\username\downloads\codexctl.exe extract 3.11.2.5_reMarkable2-qLFGoqPtPL.signed" Copy "extracted" file to reMarkable Example - "scp "C:\users\username\downloads\extracted" [email protected]:/home/root/" Verify file is in correct directory using WinSCP SSH to reMarkable. Run these commands to verify the ACTIVE Partition rootdev = /dev/mmcblk2p3 (Partition 3 is active) Run these commands to verify the FALLBACK Partition fw_printenv fallback_partition = fallback_partition=2 Use DD Command to copy downloaded (extracted) FW image to the Fallback Partition Example - dd if=/home/root/extracted (location of fw image on device) of=/dev/mmcblk2p2 (fallback partition) Run codexctl.exe restore argument. Example - C:\users\username\downloads\codexctl.exe restore Reboot |
Hello!
Sorry for noob-ish question but I wonder if there are any way, today, to rollback my Remarkable 3.11.2 to something like 3.3?
As I understand from the Readme codexctl can't so it automatically but are there any any other way? Or am I stuck there for the moment?
Realised a little to late that I would very much like to have Toltec and other nice stuff
The text was updated successfully, but these errors were encountered: