Recent Posts

Pages: [1] 2 3 ... 10
1
Zaurus - Hardware discussion / SL-5500 syncing with Ubuntu 24.04
« Last post by Edranom on August 13, 2026, 09:54:25 am »
I've been working on getting my SL-5500 to sync PIM data with Ubuntu 24.04. So far I've been able to retrieve the data but PC Link stays running after the transfer has finished. Anybody here knowledgeable with such things?
2
Zaurus - Other distros support / Greetings and my new project!
« Last post by fsshacks on August 06, 2026, 01:41:49 pm »
Hi everyone,
I’m a technician/developer that specializes in bringing old handhelds and phones back to life.

I got into Zaurii about a month ago with restoring an SL-5500 (worked for a while, now having battery issues).

My idea has been to put my vintage tech collection on the internet along with archives of the files I’ve data hoarded.
This project includes a working package feed for the Zaurus and should be completed in about a month with copies of all the ROMs that were available at least for the SL-5500 if not other models.

I’m also working on a very similar project on another handheld with the same Xscale processor, the Psion Netbook Pro.
We were able to conclude a worldwide hunt for a special beta of a Linux distro developed for the Psion by the Psion company itself, PsionLX, which has disappeared from the Internet and whose GUI has never been displayed on the internet before.

The PsionLX beta is unfinished and it is running off a specific version of OpenEmbedded from the early 2000s as a base. I am planning to try to refine and finish this beta and put it on Linux kernel 3.2.9, which was the last and most recent kernel for this device.

Given this forum and its closeness to OpenEmbedded, and the CPU similarities, I wanted to ask if anyone here happens to have any archives of the armv5te package feeds from OpenEmbedded stashed away somewhere.

I had tried to use a mirror provided by Gumstix for their SBCs but it’s the wrong version and creates a segmentation fault.

Really happy to be here, I tried for a literal month to get an account registered to post on here and help out here.

Thanks!
3
Site Suggestions, Requests, and Updates / Re: Issue with new users registrations
« Last post by Varti on August 03, 2026, 03:54:49 am »
New account fss/hacks activated, I have manually sent him an email to confirm that his account has been activated.

Varti
4
Site Suggestions, Requests, and Updates / Re: Issue with new users registrations
« Last post by Varti on July 22, 2026, 03:59:50 am »
As a general reminder: new account requests are still being manually approved, although no confirmation email is being sent (yet). These two members account are now active:

sam1am
fss-hacks/fsshacks
yota9/yota99

If you have a duplicated account and want to delete one of them please let me know which one you'd like to keep.

Varti
5
Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator
« Last post by Varti on July 09, 2026, 03:39:43 am »
Hi, glad to read that you have solved the problem!

Varti
6
Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator
« Last post by klampfenfreak 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!
7
Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator
« Last post by klampfenfreak 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!
8
Hi all, apologies for posting to a long-inactive thread. Wanted to share my experience doing a custom battery swap.

Huge thanks to mifritscher and 346L3 for sharing their battery replacement experiences. Thanks to them I was able to bring one of my Cosmos (which had been dead-on-arrival) back to life. I'd purchased it online as seemingly new-old-stock from a third-party, and it arrived with a bloated battery and showed no signs of life, even when plugged in.
I tried using a Huawei Ascend P6 battery after seeing in daffyduck's thread and the linked article- the Cosmo became more responsive with the Huawei Ascend P6 battery, but consistent with jakfish's comment in that thread, it did not seem to actually charge. It would power on though as if it were charging though, which it would not do with the bloated OEM battery, so that gave me hope that a BMS swap to a new cell would get it working again.

I can confirm 346L3's comment that the BMS doesn't lock up if it loses power- my bloated cell seems to have been in such bad state that my multimeter was reading zero volts from it, so i figured if it was going to lock itself, it would already have done so. So I didn't bother keeping it powered during the swap, and cut away the original cell.
After soldering the new cell to the board, it booted fine and read the new battery as being at 35%, which lined up with the ~3.81V I'd measured from it.

I did not remove the BMS of the newly-installed cell, I just connected its positive and negative wires to the corresponding terminals on the BMS (with a JST connector inbetween but that's not important), which seemed to work fine. I also used a higher-capacity cell (6500mAh) than the Cosmo originally shipped with (4220mAh) since I was unable to get my hands on a 3mm cell with comparable capacity for a reasonable price, and plan for this device to be mostly stationary and for development purposes. For reference, I used a 3.7V 956090 (0.95 x 9.0 x 6.0 cm) LiPo cell, which definitely does not fit in the original housing as it's a little over 3X the thickness of the battery mifritscher linked to, but I'll likely be replacing it with something more reasonable later. I may try looking into 3.85V batteries of similar sizes/capacities made for other phones that I can swap the original BMS onto, if they're easier to get for a decent price.

Apologies for the lack of pictures, with this being my test device this initial assembly isn't particularly pretty, nor does it really show anything you can't see in mifritscher or 346L3's pictures. This was my first time doing work like this on batteries, but I do have soldering/small electronics repair experience and I found this incredibly easy to do.
9
Site Suggestions, Requests, and Updates / Re: Security certificate expired
« Last post by Varti on June 11, 2026, 09:54:59 am »
Thanks for the confirmation, I'll write them back about the issue being solved!

Varti
10
Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator
« Last post by Varti on June 11, 2026, 09:54:06 am »
Thanks Radovan for posting this guide! It's important to have information like this stored and preserved. Regardless of when it is posted  :)

Varti
Pages: [1] 2 3 ... 10