Remarkable won't boot

Question

Remarkable won't boot

muke101 opened this issue 4 years ago · comments

Hi, I hope this isn't an inappropriate place to post this, if so I'd appreciate being pointed into the right direction.

I tried to compile and install a new kernel for my remarkable 1 tablet. It's the same version with the same def config, just with a couple things changed. I did this over the serial console by replacing the zImage and .dtb files in /boot, while saving the original in /home. The remarkable failed to boot, so I suppose I misconfigured my kernel somehow, but now after accessing the remarkable again and replacing the old files in /boot, it still refuses to boot. Here's the current state of the /boot directory mounted on /dev/mmcblk1p2:

I'm almost certain these are all the original files the remarkable came with. What are my options here? Can I completely reflash the system somehow? I tried running the reflash.uuu file but this doesn't appear to change anything. Any help would be appreciated, thanks.

Dobrin von Känel · Answer 1 · Mon Nov 02 2020 22:55:19 GMT+0800 (China Standard Time)

there are 2 root partitions, 2 and 3 , copy to both of them

…

On Mon, 2 Nov 2020 at 15:52 muke ***@***.***> wrote: Hi, I hope this isn't an inappropriate place to post this, if so I'd appreciate being pointed into the right direction. I tried to compile and install a new kernel for my remarkable 1 tablet. It's the same version with the same def config, just with a couple things changed. I did this over the serial console by replacing the zImage and .dtb files in /boot, while saving the original in /home. The remarkable failed to boot, so I suppose I misconfigured my kernel somehow, but now after accessing the remarkable again and replacing the old files in /boot, it still refuses to boot. Here's the current state of the /boot directory mounted on /dev/mmcblk1p2: [image: image] <https://user-images.githubusercontent.com/39006618/97881884-dda70d80-1d1a-11eb-9a30-69c0c69571a3.png> I'm almost certain these are all the original files the remarkable came with. What are my options here? Can I completely reflash the system somehow? I tried running the reflash.uuu file but this doesn't appear to change anything. Any help would be appreciated, thanks. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYZFLVCFIWXCI4AQLR25ODSN3BSZANCNFSM4THR7GEA> .

muke · Answer 2 · Mon Nov 02 2020 23:19:48 GMT+0800 (China Standard Time)

partition 3 is untouched, I've only been modifying 2. They seem to have the same content, would you suggest copying over the boot partition from 3 to 2?

Dobrin von Känel · Answer 3 · Mon Nov 02 2020 23:28:54 GMT+0800 (China Standard Time)

i'm not sure the reflash.uuu was finished.

try ./uuu upgrade.uuu this will overwrite both root partitions

also you my find more that can help on the discord chanel

muke · Answer 4 · Mon Nov 02 2020 23:41:58 GMT+0800 (China Standard Time)

upgrade.uuu has fixed it, thank you. It would be helpful if this were documented in the repo!

Could you also please share the discord server? I'm sure I would find this helpful.

Nathaniel van Diepen · Answer 5 · Mon Nov 02 2020 23:43:39 GMT+0800 (China Standard Time)

upgrade.uuu has fixed it, thank you. It would be helpful if this were documented in the repo!

You mean https://github.com/ddvk/remarkable-uuuflash#semi-upgrade-overwriting-the-root-with-version-2113 ?

Could you also please share the discord server? I'm sure I would find this helpful.

muke · Answer 6 · Mon Nov 02 2020 23:44:46 GMT+0800 (China Standard Time)

The subsection says 'to be documented' so I wasn't certain what it would do, and didn't want to run it without knowing.

Nathaniel van Diepen · Answer 7 · Mon Nov 02 2020 23:46:35 GMT+0800 (China Standard Time)

The subsection says 'to be documented' so I wasn't certain what it would do, and didn't want to run it without knowing.

The title is fairly clear about what it does though. That said, that's a good point. There is a bunch of extra documentation that should really be added at some point.