Hi redditors!
I've been a 2.15 user with DDVK hack for some time now, and my experience has been great so far. New rm-hacks repo and 3.8 native features are tempting though.
I wanted to test the upgrade while beeing able to revert to 2.15 in case I don't like the new experience. I know the switch.sh script. My issue is the following : in 2.15, the only version I can update to seems to be 3.04, and not directly 3.8. However, if the update goes in two steps (2.15 -> 3.04, then 3.04 -> 3.8), I believe the 2.15 partition will be wiped by the two steps process, am I correct ? Then, how to upgrade to 3.8 and keeping the ability to revert back ?
Thanks for your help
Edit : Currently, one partition is on 2.15, the other one in 3.3
There's a new rmHacks that's working to mirror most of DDVK's features and adding more that has been working great for me. They're up to 3.8 right now.
DDVK seems to have abandoned the project.
https://github.com/mb1986/rm-hacks
Yes it was my point. I would like to test 3.8 + rmHacks setup and to not lose the ability to roll back to 2.15 if I don't like it. What are the steps to update to 3.8 while not loosing the 2.15 partition ?
Ah sorry - I misunderstood you.
Seeing that edit, I could be wrong, but I would update from the 3.3 partition, and in theory you should be able to switch back to your other partition (2.15) using switch.sh.
I also believe downgrading is feasible using the remarkable-update server. Just don't open any important notebooks in 3.8 until you're sure you want to stay on that version, there's a new file format that isn't backwards compatible, and your notebooks get converted on opening.
Actually this is the issue. New firmware is always written to the inactive partition. Thus, if I update from 3.3, it will overwrite the 2.15 inactive partition with the new 3.8. The solution have been given by rmhack : using RCU, you can upload a firmware to the inactive partition.