-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 2.2 #32
Comments
if you had it previously, you can make a copy of xochitl.2113 which should be in the root, download the latest patch and use bspatch to patch it and replace /usr/bin/xochitl (making a backup first) or you can just boot the old partition and disable the updates |
Thank you for the answer. I made a backup of the two xochitl files and downloaded the patch in /home/root but now I am not sure how to use the patch. Is it this way? : Afterwards, I will have to replace /usr/bin/xochitl by /home/root/xochitl.2113? |
the patch is: patches/2113/patch_06 then start to test and move .patched |
you can do |
make sure you get the raw content feom github and not some html
…On Wed, 10 Jun 2020 at 17:59 ZacharieALES ***@***.***> wrote:
Ok something is odd.
bspatch seems to work fine on an older patch that was already on the
remarkable (patch_04).
However, if I download any patch with wget and use bspatch on it (even
patch 04), I get:
***@***.***:~# bspatch xochitl.2113 xochitl.patched patch_06
bspatch: Corrupt patch
***@***.***:~#
(I tried with patches 4, 5, 6 and 6_1)
Maybe I can try one of the two other options you mentioned but I am not
sure how to do it.
To boot the old partition, I just need to run xochitl.2113? (I tried but
the device still seems to be in v2.2)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYZFLVRSUO3ZON35MXKBGDRV6UWBANCNFSM4N2FULEQ>
.
|
First I just ran ./xochitl.patched and I had 2 sidebars one over the other (yours and the classic one). Then I followed patch.sh and did these commands and it worked! :
Thank you for your help. |
you’re welcome ;)
…On Wed, 10 Jun 2020 at 18:18 ZacharieALES ***@***.***> wrote:
First I just ran ./xochitl.patched and I had 2 sidebars one over the other
(yours and the classic one).
Then I followed patch.sh and did these commands and it worked! :
***@***.***:~# systemctl stop xochitl
***@***.***:~# systemctl stop remarkable-fail
***@***.***:~# rm /tmp/*crash*
***@***.***:~# rm -fr .cache/remarkable/xochitl/qmlcache/
***@***.***:~# QT_LOGGING_RULES=*=false ./xochitl.patched || echo "It crashed?"
Thank you for your help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYZFLRCEJIQE53QKUIGRV3RV6W3VANCNFSM4N2FULEQ>
.
|
Hello ddvk-- I love the tools you created! They made reMarkable incredible. I accidentally updated to 2.2 and lost your tools. The above thread is beyond my capability. Is there a forthcoming update that is compatible with 2.2, or is there a way to downgrade back to 2.1? A million thanks to you from Denver, Colorado! |
here is somthing easier:
|
ddvk. |
Hi ddvk. Thanks so much for creating the hack and for helping everyone with this. I know it must be super annoying to answer, but do you have any plans on updating to 2.2? :-) Thanks! |
try again with the automagic, the official version has some bugs and was waiting for them to fix them, but anyway here's something |
It worked! Thanks so much. Epic tweaks, very much appreciated :-) |
[2.2.0.48 - patch_01] |
sorry about that, fixed in patch_02 |
Which version is installed right now using the automagic code on the home page of the hack? I recently upgraded to rM OS 2.2, so reinstalled the hack. My rM is reporting Version 2.2.0.48, with hack version patch05_1... |
well, depends on your version, the patches are version specific |
OK, so the automagic code on home page, if I'm running rM OS 2.2.0.48 is automatically going to install the 22048 version of your hack? And even though the above thread says that the eraser problem was fixed in patch_02, it's normal that mine is reporting patch05_1? Sorry, I'm not at all Linux literate, so the only thing I know how to do is SSH in and use your automagic script. Thanks! |
correct, if the eraser is working then it s fixed ;). ignore the version in setting (for problem reporting only) |
Perfect! Thanks so much for letting me know, and once again my thanks for this incredible hack! |
updated readme, patches ported to 22048 |
Hi. i did this to revert to an earlier version so i could use your hacks. How do i revert back to the latest version? Also, i would like to thank you for your contributions. :) |
just apply the pach should probably work
or to revert (if you followed the instructions exactly)
‘’’
cp xochitl.22048 /usr/bin/xochitl
systemctl restart xochitl
‘’’
…On Fri, 24 Jul 2020 at 19:58 cyh002 ***@***.***> wrote:
here is somthing easier:
cp /usr/bin/xochitl xochitl.22048
mkdir -p other
mount -v | grep 'on / ' | cut -f1 -d ' '
# will show /dev/mmcblk1p2 or /dev/mmcblk1p3 use the opposite (e.g. if p3 use p2) below
mount /dev/mmcblk1p2 other
cp other/usr/bin/xochitl /usr/bin/xochitl
systemctl restart xochitl
Hi. i did this to revert to an earlier version so i could use your hacks.
How do i revert back to the latest version?
Also, i would like to thank you for your contributions. :)
I really love what you have implemented and i wouldn't have love my tablet
as much as i do, without your hacks.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYZFLT7PBPEASJIYLF5ACLR5G4SFANCNFSM4N2FULEQ>
.
|
Hello,
Version 2.2 has just been installed on my remarkable. The hack does not yet seem supported with it. Can I do anything to make it work? (e.g., downgrade my remarkable version or something else)
The text was updated successfully, but these errors were encountered: