OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - Android => Topic started by: Stardust21 on June 01, 2023, 10:08:08 am
-
Is anyone using an unrooted version of the v25 firmware:
https://support.planetcom.co.uk/index.php/Rooted_Android_For_Cosmo
If so, how did you get it?
Thanks
-
With the "standard" OTA update. They never bothered to publish the V25 on the support site...
-
If you need to be running unrooted, see at the bottom of that page:
> Please note that the firmware will be rooted only when selecting ROOTED_ANDROID boot when starting the phone. If you select NORMAL boot, then the standard Android will be started.
-
The OTA update doesn't work for me, it says there are no updates or something to that effect. I didn't notice you could run the rooted version in an unrooted mode. I don't suppose you know if installing the rooted firmware affects the warranty in anyway? It normally does but then manufacturers don't normally offer it themselves.
-
At this point, I'd recommend contacting Planet. The "rooted" image is just for the boot partition, not the entire OS image. Tell them that you were able to get V23 from support site but cannot upgrade to V25 since OTA is not working, and ask for the image (and better yet, have then upload it to the support site). Would be nice if they'd just add it to the list here, https://support.planetcom.co.uk/index.php/Cosmo_Android_Firmware_Manual_Installation - but guess not...
-
I've contacted planet over a week ago but they haven't responded, might email them again. If all else fails I might look at the rooted V25.
-
Has anyone used the rooted V25? I've downloaded it and was tempted to give it a go but it's less than 10MB where the V23 one is 3.9GB. There's also only two files in the zip.
-
Has anyone used the rooted V25? I've downloaded it and was tempted to give it a go but it's less than 10MB where the V23 one is 3.9GB. There's also only two files in the zip.
I'm using it, but as I said, that 10 MB image is *just* the bootloader. The difference between "rooted" and "unrooted" is just the contents of the boot partition.
I upgraded to V25 via the OTA upgrade, but apparently that does not work anymore.
-
Correct me if I'm wrong, but if that's just the bootloader, doesn't that mean there's no way for me to upgrade to V25 right now, because I don't have an image for it and the OTA doesn't work?
-
Correct me if I'm wrong, but if that's just the bootloader, doesn't that mean there's no way for me to upgrade to V25 right now, because I don't have an image for it and the OTA doesn't work?
You are correct. That's why I suggested that you'd contact Planet and ask them to either 1) Fix the OTA upgrades or 2) Provide the full V25 image via support site.
(Even better would be if they would bother to upgrade the software, but Android 9 is end-of-life and upgrading to newer Androids probably won't happen).
-
Oh ok, I nearly wiped it yesterday good job I didn't. I have contacted Planet twice but they don't respond. The Cosmo was supposed to get Android 11 once they'd had the experience of implementing it on the Astro, I think Planet are a bit short staffed to do it though.
-
Oh ok, I nearly wiped it yesterday good job I didn't. I have contacted Planet twice but they don't respond. The Cosmo was supposed to get Android 11 once they'd had the experience of implementing it on the Astro, I think Planet are a bit short staffed to do it though.
How exactly did you contact Planet? If you send mail to hello@planetcom.co.uk, you should at least get the Zendesk automatic reply about a created ticket. That way I've always gotten responses.
-
I contacted them at hello@planetcom.co.uk and got a Zendesk response on both occasions. I assume my query is not straightforward which is why they are not replying. Can I ask how long they normally take to get back to you in your case?
-
I contacted them at hello@planetcom.co.uk and got a Zendesk response on both occasions. I assume my query is not straightforward which is why they are not replying. Can I ask how long they normally take to get back to you in your case?
Well, my last contact was regarding the battery and well, according to my inbox, Zendesk autoreply received at
Thu, 26 Jan 2023 10:56:27
Paul E. Pinnock replied at Thu, 26 Jan 2023 12:59:14
Before that I asked about Astro protection pack shipping, Zendesk reply at
Tue, 15 Nov 2022 12:14:32
Paul's response at Tue, 15 Nov 2022 15:48:04
So only a few hours...
-
Oh ok interesting.
-
Just tested by the way, I requested a refund on my Astro protection pack (Since I've been using my Astro for quite some time now, and frankly, I don't need the protection pack anymore).
Zendesk autoreply: Mon, 5 Jun 2023 16:29:10
Paul's boilerplate reply: Mon, 5 Jun 2023 16:41:01 - all of ten minutes.
Of course, he replied with a canned response about me getting my Astro soon, without even bothering to read that my request was about the protection pack, not about the phone. But still, they can respond quite quickly if they want to.
-
That's interesting, I assume the issue is with my request and they are choosing not to reply. Can I ask what you think to your Astro, how does the keyboard compare to the Cosmo?
-
Hi everybody, I'm a new Cosmo user and I'm running into the same problems. I have manually upgraded to V23 with the help of this forum and the downloads from Planet. Am I understanding correctly in that I'm just screwed and unable to update to V25 unless Planet actually responds to one of us with the firmware? I have also emailed them several days ago and they have yet to reply. Based on this thread that seems to be the case, but maybe bumping this thread will catch someone's eye who may be able to help. Really enjoying the device so far, even with the downfalls, I knew it was an imperfect device to tinker around with when I bought it but really wasn't expecting that it couldn't even update because Planet decided it wasn't important enough to upload the latest firmware to their site. That just seems like a slap in the face to customers, especially considering they still sell the device on their site with no warnings or disclaimers that it's stuck on old firmware..
-
OTA is down, but you can root V23 by extracting the *V23* boot image (@Zarhan, the bootloader is lk (what was recently taken down by Mediatek), and the boot image, i.e, the kernel, is what the bootloader passes control of the CPU to), and rooting that with Magisk on the device.
I could get around to this this weekend, and publish it somewhere. It's relatively easy to do.
I've been trying to get Lineage on my Cosmo, and even with my MTK debug cable, it just boot loops.
-
OK, so I've patched the V23 root image.
A couple of warnings: a) do not flash to `boot`, use the installer scripts. You can rename the file to `root-boot.img`, and follow the Planet wiki on that front. As long as you don't use the Planet-provided `root-boot.img`, you should be fine.
b) If you do want to flash to `boot`, you'll need to unlock the bootloader - this will erase your data.
Below is a link to a Google Drive link with the rooted kernel image.
https://drive.google.com/file/d/1IXLS7zJR9L1L7DPJjzVEYGlwgIjeVCy0/view?usp=sharing
Hopefully, V25 will be available soon. I did have the Update ZIP, but I've since deleted it. I feel like a bit of a moron now.
-
Thank you again for your help Dom. I'll hold out for V25 from Planet, root isn't necessarily on my radar right now but I've read there were some keyboard firmware improvements (amongst other things) in the newer versions, and that is my biggest reason for wanting the upgrade.
If anyone does have a copy of that update ZIP and could provide it, I know many including myself would be grateful! On the chance that Planet does get back to me via email sooner than they fix the OTA problem (I can dream), I'll be sure to upload a copy here for everyone as well. Fingers are crossed, but breath isn't being held.
-
+1 I Just opt to get the old Cosmo instead of the Astro and now stuck on V23. Can someone please provide V25 ? would be much appreciated, thx
-
Unfortunately no one's got it, I've emailed Planet multiple times over a month ago now and they don't respond. I assume there's some sort of issue with V25 otherwise they would provide it.
-
I ran V25 for ages, and don't recall it being any buggier than previous versions. So I don't think there's a reason it's not available besides some kind of incompetence.
I'll take an image of my Cosmo on the weekend and share the relevant partition images here.
-
I have a variation of this problem
My Cosmo says Android V 9
There should be a V 12 available - where & how do I get it & upload it?
-
I think your confusing OS version and firmware version. The Cosmo only runs Android 9 Pie, it was never updated beyond that. However we don't even have the latest version of the Android 9 firmware.
Unfortunately I sent Planet multiple messages and got multiple automated tickets but never got a response from them.
-
OTA is still down. I've asked Planet if they can direct queries on Zendesk regarding software to me - but with OTA, my help is limited. All I have is v23.
I'm sure they have copies of the firmware, but they don't deal with OTA. It was only with Astro it began to be hosted by PC.
(Side note, but this is Agnostos: https://github.com/shymega/Agnostos - a privacy-focused, cloud-native OTA application. Any thoughts on design would be welcome before I send a formal proposal to PC).
-
I have a couple of working Cosmo (one with a cracked CODI) Typical the broken CODI one is v 25 and the perfect one is v 23. is it possible to extract the V 25 and put it on the other rather than having to dismember them. Not urgent as I have an Astro but I would like the perfect one to have V 25 as it is my disaster recovery solution. any ideas?
-
You could readback the partitions, but I would _not_ recommend it.
There are numerous partitions for Android, and it's better to use the OTA.
-
Found this https://github.com/shymega/cosmo-v25-android-fw-ota
So far so good!
-
Bear in mind, this was only by luck I found the OTA package on an old server of mine, so obviously it's not an official solution.
Although I suspect the next update for Cosmo will *have* to be an OTA package like in my Git repository, because the Wireless Updater is offline.
-
Bear in mind, this was only by luck I found the OTA package on an old server of mine, so obviously it's not an official solution.
Although I suspect the next update for Cosmo will *have* to be an OTA package like in my Git repository, because the Wireless Updater is offline.
I get an error message after OTA updater find the local OTA package and rebooted my cosmo. Is it the package on github with 134bytes? Thanks!
-
Found this https://github.com/shymega/cosmo-v25-android-fw-ota
So far so good!
How did you performed the updated? I can't finish it. Thanks!
-
I have addressed the issues in the README. I suspect people are downloading HTML as a 'zip'.
-
I have addressed the issues in the README. I suspect people are downloading HTML as a 'zip'.
You are right, my browser give a me a .zip html file.
Redownloaded the right file and updated, thank you Dom!
-
I have addressed the issues in the README. I suspect people are downloading HTML as a 'zip'.
Your a star, I was able to use your OTA package to update my Cosmo to v25, thanks.
-
I have addressed the issues in the README. I suspect people are downloading HTML as a 'zip'.
You are right, my browser give a me a .zip html file.
Redownloaded the right file and updated, thank you Dom!
Hi!
Do you happen to have a copy of the v25 or the correct link?
, HERE https://support.planetcom.co.uk/index.php/Rooted_Android_For_Cosmo (https://support.planetcom.co.uk/index.php/Rooted_Android_For_Cosmo) I can only get a zip w/ two files.
Thanks
-
Found this https://github.com/shymega/cosmo-v25-android-fw-ota
So far so good!
Hi,
GitHub comes w/ a 404 error. Do you happen to keep a copy of the v25 for sharing?
Thanks
-
If it is a partition images retrieved by dd, I have it.
-
Found this https://github.com/shymega/cosmo-v25-android-fw-ota
So far so good!
Hi,
GitHub comes w/ a 404 error. Do you happen to keep a copy of the v25 for sharing?
Thanks
Try now, for some reason, the repository was marked private.
It's best to update on your own Cosmo, rather than using dd'd images.