new version

[huo2021]

Hi, i update to the new verison 2.11.0.442, koreader cannot be open anymore is there any solution? thank you so much!

[williamhern]

Yes, I have the same issue.

Looking at the touchinjector logs, it seems that the RM2FB is not finding the signature for 2.11.0.442. Looking at the installer code, it looks like the version of RM2FB being installed is still v0.0.10. This is two versions behind the current version (v0.0.12) which does support 2.11.0.442.

[williamhern]

I have just manually updated the install script to use a later version of RM2FB (v0.0.12) and this does indeed resolve the problem - KOReader is accessible again.

[huo2021]

Hi , Thanks for the reply. I just tried again, still doesn't work, it says Reboot the device. My device is not hacked. I don't know what to do, could you please help with this?

[williamhern]

Unfortunately I don't have the necessary permissions to upload my corrected version of the installer code to this repository so I attach it to this message instead.

In order to use it, you'll need to change the file suffix from ".txt" to ".sh" and download it to your RM2. Make the file executable ("chmod 777 auto_rm2.sh") and then run it ("./auto_rm2.sh". This should cause the later version of RM2FB to be installed. The final step is to restart your RM2, which is done from the "General settings" page on the RM2.

Hope the above is clear - I'm assuming that you know your way well enough around UNIX systems to interpret what I've written. If you're not, or you feel uncomfortable about downloading a shell script from a random stranger on the Internet and running it as root on your precious RM2 (I certaily would!) then hopefully DDVK will get round sometime soon to making the official update to the installer - it's literally work that takes just a few seconds.

auto_rm2.txt

[huo2021]

Thank you so much for the help. I am not good at UNIX, can not do anything myself. I just wait and see how it goes. thank you so much!

[ddvk]

sorry for the delay, i bumbed the rm2fb version

[huo2021]

I just tried again twice, still doesn't work, it says Reboot the device. My device is not hacked. Do I need to delete the previous vision because I tried before? Could you please me advice me what should i do? @ddvk

Thank you so much for all the support!

[williamhern]

Here's what worked for me with regards to installation:

1. I deleted the previous version by executing on the RM2 the following commands:

systemctl stop touchinjector rm /etc/systemd/system/touchinjector.service

2. I ran the script provided by ddvk.

3. I rebooted my device when prompted to. I did this by going to "Menu" and selecting "Settings". I then clicked on the "Restart" button at the bottom of the screen.

When the RM2 finished rebooting, the long upward swipe from the bottom of the screen took me to KOReader.

[huo2021]

Hi sorry to bother you again, i am not good as this : (. after i enter the password i type: systemctl stop touchinjector rm /etc/systemd/system/touchinjector.service it still not work. it sais failed to stop:

i put the picture there , hope you can see it , would you please help me with this ,thank you so much!!!!

[williamhern]

Thanks for the picture. It appears that you combined the two instructions for deleting the existing version into one line. You need to execute them individually:

systemctl stop touchinjector

then

rm /etc/systemd/system/touchinjector.service

Also, in the second instruction, make sure that there is a space between the "rm" and the start of path (ie. "/etc/systemd/system/touchinjector.service")

Fingers crossed, this should solve your problems.

[huo2021]

thank you so much for the instruction. i just run again showed like this. sorry about this , neek to keep ask you, I am really not good at computer.

did I something wrong before? could you send me a picture to show me how to do this?

thanks for all the support!!!!

[williamhern]

It looks like you're executing the instructions correctly, though I don't know why the warning message comes up for the first instruction, nor the error message for the second.

I suggest that you try executing the command that's suggested in the warning message:

systemctl daemon-reload

And then repeat the original two instructions:

systemctl stop touchinjector

Followed by

rm /etc/systemd/system/touchinjector.service

I don't have my RM2 with me right now but when I do, I will send a follow-up post, showing what successful execution of the instructions looks like.

[williamhern]

OK, here's what the instructions look like when I execute the instructions on my RM2:

I then restarted my RM2 by going into "General Settings" and clicking the "Restart" button at the bottom of the screen:

I confirmed my decision on the next screen by clicking on the "Restart" button and the RM2 then restarted (it should take around 30 seconds).

[huo2021]

Hi William, thanks for the demonstration, i really appreciate it!

I just tried and it looks like this. what is happening I have no idea :(

thanks again for all the support!

[williamhern]

Hmmm, not sure what is going on with your RM2 to be honest ... What messages do you get if you try to run ddvk's install script now? In other words, what happens when you execute the following line?

sh -c "$(wget https://raw.githubusercontent.com/ddvk/remarkable-autoinstall/master/rm2/auto_rm2.sh -O-)"

[williamhern]

After you've done a long-swipe up, try running these commands on your RM2:

systemctl status touchinjector journalctl -u touchinjector

Are there any messages displayed?

P.S. Am I right in thinking that you're connecting wirelessly to your RM2 from your computer (i.e. via WiFi)? I prefer to connect via a USB cable when doing software installs/updates as that avoids any issues with a flaky wifi connection ...