Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I bricked then recovered my reMarkable 2

operand.ca

Post reply on HN
Print view View original

91–100 of 242 posts

Re: I bricked then recovered my reMarkable 2

#91

Post by kayodelycaon »

morpheuskafka wrote: post #10

I work part-time for my university's help desk and I was both impressed and disappointed the first time I came across one of these--one the one hand, its highly customizable and supports SSH access. On the other hand, there is shockingly no way to get the MAC address without connecting via SSH, even though this is popular among academics who often need to get onto MAC filtered networks. In hindsight, we probably coul…

The reMarkable is surprisingly good for its primary purpose. Everything else it does... is limited. They things they did do are done well given how they are implemented. The epub/pdf experience sucks because it doesn't have a real pdf reader. It just renders the epub to pdf and then throw the pdf into the note-taking app.

Arguably, none of the functionality is half-assed. It works very well as a writing tablet. It absolutely sucks as a general purpose device because everything except the very core experience is flat-out missing.

There isn't a good general purpose eInk tablet and the reMarkable is the closest thing we have. :(

Re: I bricked then recovered my reMarkable 2

#92

Post by kayodelycaon »

throwaway09223 wrote: post #89
kayodelycaon wrote: post #70

Oh boy do I have opinions with this one. This seems like a lot of work to avoid using a perfectly good package manager on the device . They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used. They could have installed the package manager and left it. It doesn't run anything in the background on my device. It's easy enough to verify you don't…

"They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used." This is not true.

It very much is true. I do it all the time. If the target device is running ssh, you can use rsync on the source.

https://www.digitalocean.com/community/tutorials/how-to-copy...

Edit: Looks like I was wrong.

Re: I bricked then recovered my reMarkable 2

#93

Post by MrGilbert »

loloquwowndueo wrote: post #82

Back in the day “bricked” meant it was actually and permanently about as useful as a brick - no chance of recovery. These days it just seems to mean “can’t boot and can’t be fixed/reflashed easily”. Having to plug a resistor into the device to put it in any sort of recovery mode does walk a very fine line between “not really bricked” and “dude you squeezed water out of a stone, you are a demigod”.

One might call it "soft-bricked".

Re: I bricked then recovered my reMarkable 2

#94

Post by cortesoft »

jiveturkey wrote: post #81
cortesoft wrote: post #33

Earlier quoted context omitted.

Yeah, I think you are right. I am convinced. I would probably draw the line at physical work, meaning if it requires physically opening the device and changing/fixing/bypassing wiring it can count as bricked.

Well, I mean, that is a reasonable line. But it's still moving the goalposts. I'll stick with bricked meaning bricked. I lost that personal battle for 'hacker' and 'begs the question' but dammit I am sticking to it for 'brick'!!

> I'll stick with bricked meaning bricked.

Well that is what I am sticking with, too!

Re: I bricked then recovered my reMarkable 2

#95

Post by Eeems »

idorosen wrote: post #15

My only regret about this device is that it seems to lack full disk encryption on the device or any meaningful privacy (encryption) for documents stored in reMarkable Cloud...which is all of them if you want to use features like Screen Share (f.k.a. LiveView). ReMarkable should not be able to access contents of docs backed up from my device without my password or recovery key, but AFAICT, there is no such protection…

gocryptfs is available in toltec[0]. So you could in theory add full device encryption behind a password on startup. I know there has been some work on creating a UI for this kind of setup, but I don't know if anyone has actually released one yet.

0. https://toltec-dev.org/stable/

Re: I bricked then recovered my reMarkable 2

#96

Post by xdfgh1112 »

kayodelycaon wrote: post #92
throwaway09223 wrote: post #89

Earlier quoted context omitted.

"They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used." This is not true.

It very much is true. I do it all the time. If the target device is running ssh, you can use rsync on the source. https://www.digitalocean.com/community/tutorials/how-to-copy... Edit: Looks like I was wrong.

Doesn't that run rsync --server on the server via ssh?

Re: I bricked then recovered my reMarkable 2

#97

Post by throwaway09223 »

kayodelycaon wrote: post #92
throwaway09223 wrote: post #89

Earlier quoted context omitted.

"They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used." This is not true.

It very much is true. I do it all the time. If the target device is running ssh, you can use rsync on the source. https://www.digitalocean.com/community/tutorials/how-to-copy... Edit: Looks like I was wrong.

No, it is not true. You're misunderstanding how this works.

The document you link is using ssh as a transport protocol as opposed to the rsync protocol. The rsync binary must be installed on both systems for this to work.

When you run something like:

rsync file user@rhost:/dest/path

The local rsync binary invokes ssh, and then executes the rsync binary on the remote system and from there the two instances of rsync effectuate the transfer.

If you do not have rsync available in your path on the remote system you will not be able to copy files over ssh. This is documented in the manpage.

Try it.

Re: I bricked then recovered my reMarkable 2

#98

Post by Eeems »

myself248 wrote: post #49
unexpected wrote: post #3

This is anxiety-inducing and a good promo for the pinenote!

The Pinenote can't arrive fast enough! I'm sitting on a ReMarkable 2 that I hate because I didn't realize how serious they were about crippling the usefulness of a really beautiful stack of hardware. It's really, Really, REALLY dead-set against letting you do anything useful like use wikipedia or stackoverflow on your ultra-long-battery-life beautiful-display device that you might, I dunno, want to use to look at ref…

Wikipedia is kind of solved[0]. As for stackoverflow, you might be able to use netsurf[1] already, I'm not sure how JS dependent it is.

0. https://github.com/dps/remarkable-wikipedia

1. https://github.com/alex0809/netsurf-reMarkable

Re: I bricked then recovered my reMarkable 2

#99

Post by _e »

kayodelycaon wrote: post #70

Oh boy do I have opinions with this one. This seems like a lot of work to avoid using a perfectly good package manager on the device . They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used. They could have installed the package manager and left it. It doesn't run anything in the background on my device. It's easy enough to verify you don't…

Does remarkable use a fork of ChromiumOS? ChromiumOS uses the BOOT-A and BOOT-B partitions for upgrades and it reverts to the previously used boot partition if the OS fails to successfully boot[0].

[0] https://www.chromium.org/chromium-os/chromiumos-design-docs/...

Re: I bricked then recovered my reMarkable 2

#100

Post by throwaway09223 »

xdfgh1112 wrote: post #96
kayodelycaon wrote: post #92

Earlier quoted context omitted.

It very much is true. I do it all the time. If the target device is running ssh, you can use rsync on the source. https://www.digitalocean.com/community/tutorials/how-to-copy... Edit: Looks like I was wrong.

Doesn't that run rsync --server on the server via ssh?

yup.
Post reply on HN