Messages

1

Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator

« on: July 01, 2026, 08:20:58 am »

Hi everyone,

Just wanted to give a quick update: I managed to solve the issue on my own!

Instead of messing around with fastboot unlocks that would wipe my dual-boot data, I booted into Linux and dumped the original boot image specifically from the ROOTED_ANDROID partition using the direct path via partlabel:

dd bs=2048 if=/dev/disk/by-partlabel/ROOTED_ANDROID of=magisk.img

I then booted into Android, let Magisk Manager patch this specific magisk.img file, and transferred the patched image back. Finally, I booted back into Linux and flashed the patched image manually right back onto the correct partition:

dd bs=2048 if=magisk_patched.img of=/dev/disk/by-partlabel/ROOTED_ANDROID

Now everything works flawlessly, the root check passes, and my standard Android installation as well as the 60GB dual-boot setup remained completely untouched. Thanks for the pointers in this thread!

2

Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator

« on: July 01, 2026, 06:43:27 am »

​Subject: Cosmo Communicator: "Device failed verification" and no root after V25 update and Magisk installation

​Hi everyone,

​I am trying to root my Cosmo Communicator on V25, but I am stuck in a loop where the system boots but root is not recognized, and I get a verification error. My device is configured as a dual-boot system with two 60 GB partitions (one for Linux, one for Android).
​Crucial preparation steps I already completed:
In the Android Developer Options, I have explicitly allowed OEM unlocking (bootloader unlocking) and enabled USB debugging, as recommended by other users for this process.

​My goal:
I am trying to follow the official Planet Computers rooting guide, but I purposefully skipped the initial step of completely re-flashing and wiping the entire device. I must preserve my existing partition layout and dual-boot setup. I only executed the subsequent steps from their guide (flashing the root image and using Magisk) since the underlying partitions were already set up.
​
Here is the exact sequence of what I have done:
​Started with the old version V19 installed.
​Manually updated the device to V23.
​Downloaded the V25 OTA update from GitHub and installed it via the manual installation method.
​Flashed the V25 root image (following the Planet Computers method, but without wiping).
​Installed the Magisk app, executed the installation/patching process, and let it reboot as prompted.
​After the reboot, the device booted into the recovery menu. I proceeded with a normal reboot from there.
​Once the system was up, I ran a root check, but the device was not rooted.
​I attempted the Magisk installation process once more.
​Since that second attempt, I get the following error message every time I restart the Cosmo Communicator:
"Your device has failed verification and may not work properly. Please download recovery image..."
​After waiting 5 seconds, the device continuing to the boot menu allows me to boot into the OS normally, but the root check still confirms that root access is not installed.

​It seems that by skipping the full wipe/re-flash from the official guide, the boot image verification (AVB / dm-verity) is now failing, or Magisk is not patching the correct partition due to the dual-boot layout, despite OEM unlocking being allowed. Has anyone successfully bypassed this "failed verification" error on V25 and achieved root without performing the full destructive flash required by Planet Computers?

​Thanks in advance for your help!

3

Cosmo Communicator - Linux / Re: Gemian wonˋt boot anymore.

« on: December 06, 2021, 09:02:15 am »

Ok, got it!

Installed Linux Deploy under Android and chrooted into Gemini. Than I removed the complete /data/.stowaway folder from my Sailfish installation. Gemini is booting again! Didn‘t notice that the stowaway folder causes such a problem!

Thanks anyway

4

Cosmo Communicator - Linux / Gemian wonˋt boot anymore.

« on: December 06, 2021, 05:56:54 am »

Hi Cosmo Friends,

it just happened the second time: my gemian partition won‘t boot anymore. It starts with the logo and reboots before the login screen in a loop. The first time I completely reinstalled Linux, because I thought I have messed up something. But now I know the only thing I have done is not using Linux for a while. After that time it does not boot anymore. Is there any repair option or safe boot into Gemini? Why does it happens so often? Is my flash memory corrupted? I tried to flash only the boot partition, but it has to do with the data partition. So because it is decrypted I can’t repair it from TWRP, either?

Thank you

5

Cosmo Communicator - Android / Re: Rooted Android crashing on v25

« on: March 24, 2021, 08:19:17 am »

I flashed the root_image from KDE Linux with the dd command. No wipe is needed. Be careful to select the right partition! I used this path: /dev/disk/by-partlable/ to find the right one.

6

Cosmo Communicator - Android / Re: Rooted Android crashing on v25

« on: March 23, 2021, 07:12:21 pm »

Ok, got it working. Found updated Android root-image for v25 on planet-copmputers website and flashed it.

7

Cosmo Communicator - Android / Rooted Android crashing on v25

« on: March 23, 2021, 04:10:17 pm »

Hi,

today I updated to v25. Now my rooted Android reboots automatically after a few seconds. While it reboots, the display view splits vertically.  On the left side there appears the rotating planets and the right side gets black. After a few seconds the planet animation appears in full screen mode.
Android does not reboot to the multiboot menue, it is only a fast reboot, back to the lock screen.
If I try to open any programm, android is booting immediately. Sometimes it crashes direct after entering the pin. I already uninstalled magisk manager, but it seems it had nothing to do with it. I also tried to disable wlan and 4g.

The normal bootet android runs flawlessy until now.
Has someone else the same problems after updating to v25?

8

Cosmo Communicator - CoDi / Re: CoDi firmware T1.1.1.15

« on: November 21, 2020, 09:03:45 am »

Unfortunately, CODi phone functionality has stopped working under Linux.
It only worked for the first time. I only see the planet logo when closing the lid.
Touchpad functionality sometimes works and sometimes not.
 Did I miss some packages because I manually updated to v3 Linux?

9

Cosmo Communicator - Linux / Re: New Linux Update With New Mouse Button Functionality Using CODI Buttons

« on: November 20, 2020, 08:53:51 am »

Don't install the OTA update. That was my fault.
What I did: flashed manually back the v14 (took some runs to work). Than installed the v15 custom patch with mouse functionality.
Under linux you have to install the codi-app. Android also have to be the latest.

10

Cosmo Communicator - Sailfish OS / Re: Preview version of Sailfish for Cosmo

« on: November 15, 2020, 10:37:12 pm »

Sailfish is booting. but after a few seconds theSailfish deskop freezes and the device reboots with a black screen. I had to complete power-off the device to get rid of the black screen. Why it is crashing?
Tried to vers --dup to version 3.4 in chrooted sailfish under Linux, but terminal hangs on : REFRESHING CACHE AND DOWNLOADING PACKAGES


 

11

Cosmo Communicator - Android / Re: Keyboard Bounces

« on: November 10, 2020, 03:55:27 pm »

I don't know what you mean by bounce. But I have a a problem with my LEDs. The keyboard goes on and of every 5 seconds.
rebooting did not solve the problem! This problem only apears on the lowest LED light settings, I figured out.
Anyone with keyboard backlight problems?

I have to correct me: Unfortunately, the problem appears on any LED level. Backlight still goes on and of every 5-7 seconds.
I tried to solve it with CosmoCtl (rooted device) but no chance.
I will check if the unrooted Android also have this issue.

12

Cosmo Communicator - Linux / wlan failed after lock screen

« on: October 21, 2020, 10:22:58 am »

Hi @all,

I have got a problem with wlan not connecting after screen goes locked and unlocked again under linux.
SSID is showing up, but conman did not connect until a reboot. I tried powering off/on wlan module. Also tried to connect using command line. Only way is to reboot the device.
Anyone with this issue?

thank you!! : )
 

13

Cosmo Communicator - Linux / Re: How to crosscompile the Cosmo Linux kernel

« on: August 21, 2020, 06:47:45 pm »

Ok, what I had read for now, the "-w" disables error messages.
I like to have the option to mount cifs filesystem, so I  crosscompiled the kernel to get the missing modules in the *.ko format.
But I only get .o files in the KERNEL_Output folder. How can I covert them to load them as modules.
It the first time I compile a kernel and I am a little bit confused.
I also tried to dd the Image.gz but I think I have to melt it with a ramdisk. Where I get the ramdisk file for Cosmo?Is it the same ramdisk which is included in the android kernel?
Thank you
   

14

Cosmo Communicator - Linux / Re: How to crosscompile the Cosmo Linux kernel

« on: August 18, 2020, 02:44:39 pm »

Hi,
for what stands the "-w" option in the KBUILD_FLAGS file, please?

How can I create a flashable .img from the build Kernel, please?

Thank you!
klampfenfreak

15

Cosmo Communicator - Android / V22 is out.

« on: June 25, 2020, 07:02:12 am »

still got the random reboots with new firmware v22 and CODI V1.1.1.14  when CODI is switched on.. :/