Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - soCket23

Pages: [1]
1
Cosmo Communicator - Hardware / Re: Completely re flashing the Cosmo
« on: July 19, 2022, 08:19:03 am »
Necrothread alert, reporting back: this saved my day today.

I made the mistake of doing a factory reset from a rooted boot (I'm an Android n00b) and this got me stuck in a loop from blank to Red State. The device didn't respond to the usual Power-volume combo.

The difference for me: when I tried to flash, I got a PMT error, so I had, using the SP Tool itself, to format the flash EXCEPT THE BOOTLOADER first, then I could restore my Cosmo just fine.

Thank you so much for putting these instructions together.

so if I accidentally chose the "Format Whole Flash" option, meaning the bootloader also would I still be able to make this work? I was on v25, would it be better to use the v23 or another option? I am just trying to figure my options before sending it to Planet again..

2
Cosmo Communicator - Hardware / Re: Completely re flashing the Cosmo
« on: July 19, 2022, 08:16:24 am »
Hi there!

@drbytes, thank you for your post - I hoped it'd be my rescue as well. Or my cosmo's at least.

What happened: Back then when the linux image v2 has been released I flashed it and everything seemed fine until I did the sudo apt update && sudo apt upgrade. The display suddenly went black and stayed black forever. No boot logo, no display illumination, no recovery mode no nothing. The only thing that 'works' is when I push the silver button CoDi wakes up and greets me.

I tried this guide and am unsure if what I see is related to a malfunction of the phone or my PC or anything else. Maybe someone has an idea what I could try to unbrick my device. As I think this is an issue that falls under warranty I contacted planet computers but they wanted me to spend ~ 200 pounds or similarb just to let them try.

When I flash the phone at first the status bar goes red with some information. The window looks like this:
 


After a while this error message appears:
 


I tried different timeouts in options, connected and disconnected the phone, used alternative cables, put a USB hub inbetween, disconnected the battery for a short while, ... nothing.

BTW: Flashing behaves differently when no phone is connected, so at least something seems to be working.

As @Shiunbird1 tried reformatting the flash I tried this myself. Again, only with an error message. This time nothing is printed in the status area - not even a timer. Shortly after I start this action I can hear the USB connection sound on my PC and a message is shown, that the last connected USB device could not be identified. After the period of time set in options for 'timeout' the timeout occurs ;) and a not that helpful error message appears.
 


Any help would be very much appreciated.

I'm using Windows 11 on a Surface Go 2 and the phone is connected via USB-C. (Well most of the times. I also tried connecting it via a USB hub and an A to C cable.)

Thanks and best wishes,
yo


did you find a solution?

3
Cosmo Communicator - Hardware / Re: Completely re flashing the Cosmo
« on: July 19, 2022, 08:16:01 am »
I have the same problem, have you found a solution?  I am hoping to find a way to reinstall the system.  I'm looking for someone who has another scatter or systems v15, v16, and I understand that there is v25, someone who provides me to try to revive my cosmo, even disarm it to connect it via test point but although it connects, it marks that I do not have the system Rom .  I hope to upload images of what I took from the cosmo, thanks to Sorber's tutorial and how to connect it via test point.


were you able to get any option to work?

4
Cosmo Communicator - General Discussion / Scatter file?
« on: July 19, 2022, 07:56:25 am »
Does anyone have the full SP Flash-compatible firmware set of V25 or V23 for Cosmo? I would also settle for the full scatter file. Also if you have  flash-compatible firmware set for a different software tool that would be interesting also.. Thank you. Please, Please.

5
where can I get the unedited scatterfile with all the image addresses listed? so I could flash a 100% fresh device.

6
Cosmo Communicator - Android / Re: Signature spoofing
« on: July 08, 2022, 03:59:57 am »
Keep at it I would love to see this happen. Just like a Kali image for Cosmo..


Sorry, no, misread, thought you were on Gemini.

PCLineageOSPorts is an org I run. We haven't got LineageOS working on Cosmo just yet, but I did have another go last night. I need to finish my CoDi daemon for Cosmo Android/other ROMs.

i think you're stuck for the moment, the ROM will need signature spoofing support, and you're using the ODM/OEM-built stock ROM...

7
Is this something where you could never get past the splash? like boot loop status?

Greetings.
I received my cosmo last month. :)
I'm planning to use it mostly as a portable device to learn linux and run some android apps.
I received it with the SD Card containing v23 firmware.
I followed the video on multi boot linux/android(with twrp installed).
The normal boot never worked, but the android root booted until....
At one point I wanted to restore to original condition using a v23 twrp backup.
When I did the backup, I selected all available content to backup.
During the restore, it hung.  :( at 60% during /system restore.
I tried to use recovery to setup again as above, without success.
I ended up in a boot loop on android root and normal.
linux boots and works however and I have twrp, recovery menu and SD Card will mount.
I am not able to connect via ADB. Device doesn't show up on USB connection.
I downloaded and tried to fastboot or flash the v23 zip, without success.
When I tried update from SD Card with v23 zip, I get signature verification failed.

I think I need to flash a stock rom, but I don't know the details for Cosmo.
The last phone I flashed was a samsung using odin years ago.
I see references to a SP Flash tool, but what image to flash and how I don't know.

Any help would be great.
Happy holidays and be safe.

8
I have TWRP installed. Linux v4 and Android v25 with rooted partition. I used Magisk to install modules for Kali NetHunter. What I did not do, was to allow booting of unsigned images. I’ve tried playing with MTK WWR software, scatter files, SP flash tool, etc. and so on.

I realized I just need a way to flip that unsigned images verification switch. Can anyone help? I’m really interested in this side of the game. I’m willing to buy hardware if I need, Medusa, Octoplus, Z3X whatever. If someone can just give me a lead on how to figure this out I would appreciate it very much.

The one thing I do not want to do is send my phone to London again. The last time I did that it ended up at the wrong office address and was LOST IN THE UK POSTAL SYSTEM FOR 8 MONTHS!!, still had to pay 100€ and barely got it back. I love experimenting with images and OS builds. And I do not trust the UK post offices to send it back, and understandably will never try to again. So please please please, if you’re reading this and you’re one of the engineers that works for Planet Computers, or in the cell phone industry in general and you can help please let me know!! I work in cyber security and I find this side of the industry absolutely fascinating and fundamental. I’d be willing to make it worth your time to help. I’ll be at BlackHat and DEFcon this year. So I’d be happy to meet up there also. Message me, please.

9
Cosmo Communicator - General Discussion / Re: Red State
« on: December 29, 2021, 06:42:07 am »
How do you suggest going about this process do you think that this would help my boot loop??? I just sent this damn thing in the mail to planet computers in London.. it got lost for eight months in the mail. Then I still had to pay for it to be flashed for 100 bucks.

Plug the Cosmo to PC, and issue 'fastbood flashing unlock'. There should window when the system is still in bootloader stage to accept the command.

Result should be that instead of Red state, the Cosmo should be in Orange state, essentially "image in unverified, but I'll boot off it anyway".

Or just try if the thread here https://www.oesf.org/forum/index.php?topic=35879.0 helps in any way, e.g. using sp_flashtool to just flash the entire image. Just be careful not to overwrite device-specific stuff like IMEI numbers (so take backup first).


Subtle I do have a couple of MTK tools, spflash, WWR, MTK flash & Droid root & tools. I’m a little out of my depth. This is the first time I’ve gotten myself to this level and found these type of tools that can be effective.

I did use SP to run a memory test and that stopped my boot loop but just shut off the device. And I’ve tried using various boot key combinations to get anywhere outside of the boot loop and it doesn’t work. So I can’t issue the Facebook command because I can’t do it the phone to sit still to be seen. But apparently I’m not 100% out of options otherwise the memory test wouldn’t have stopped the loop. I’m not really sure where to go from here because I’ve never use this type of software for flashing. Ideas?

10
Cosmo Communicator - General Discussion / Re: Red State
« on: December 29, 2021, 05:35:25 am »
I guess I’ll have to be fast then, Because basically it reboots every like 15 seconds. I’m just hoping that can actually get a read on the device to get the command off. I’m going to try this because it would be better if it worked. And give me the room to do more maneuvering without trying some thing like flashing it all the way

I took a scatterfile using WWR MTK. Is that what you mean by back up. I mean I have all the images saved and I have a boot card to install the different OSs.

11
Cosmo Communicator - General Discussion / Re: Red State
« on: December 29, 2021, 01:04:21 am »
I’d also like to add then I have by sheer luck used a tool to create a scatter file based on my Cosmo. So if there’s a way I can stop this boot loop I can probably flash the scatter file and take it back to normal

12
Cosmo Communicator - General Discussion / Re: Red State
« on: December 28, 2021, 11:10:55 pm »
How do you suggest going about this process do you think that this would help my boot loop??? I just sent this damn thing in the mail to planet computers in London.. it got lost for eight months in the mail. Then I still had to pay for it to be flashed for 100 bucks.


What would be a Hardwear option like planet computer uses in order to directly flash like they do in the factory? Is there a piece of equipment out there that would allow me direct control over these devices for flashing?



This is what it says

This means that the image on flash is not signed. So you must have reset to some non-planet image (e.g. one that has been rooted using the instructions on this forum).

In my opinion, you have two options:

Unlock the phone so it boots regardless of signing (using fastboot tool)
Or
Re-flash the phone with a signed image

13
Cosmo Communicator - General Discussion / Re: Red State
« on: December 28, 2021, 11:07:23 pm »
So any advice on how to stop the boot loop so that you can do this. I’m getting this exact same thing in a boot loop. I have TWRP installed routed android and Gemian but I can’t get to any screens to do anything. And I didn’t do anything major to get to this point all I did was uninstall busybox. And then decide I wanted to start from scratch with all my software so I did and erase all content in android, So that I could start from scratch I don’t understand what happened here it shouldn’t have had this severe of a reaction.

14
Cosmo Communicator - Linux / Re: Ubports for Cosmo
« on: November 21, 2020, 11:29:24 pm »
The UBPorts image resides in the same main partition as Debian, so you don't need to delete either. The bootloader has extra boot options, and by using my script (attached) on your Cosmo alternative OS installer SD card thing you can flash the UBPorts boot.img to one of these boot options and essentially triple-boot Android, Debian and UBPorts. 

You'll also need to put the boot.img on your SD card in the same folder and change its name to 'ubports-boot.img' for my script to work, and also add this: 

Code: [Select]
echo "UBPorts,$MBF/Cosmo_Installer_UBPorts.sh" >> $INSTALLER_FILE 

To the bottom of the list_installers.sh file (above the 'rm -f $PARTITION_FILE' line) and, as noted above, put the ubuntu.img file in the root directory of your Gemian install. Now boot to recovery with the SD card inserted and install UBPorts to another boot partition of your choice (But not the second one, as noted above there's no networking there!)

I've found the UBPorts image to be the most fleshed-out alternate OS yet - the camera works, keyboard layout works, 4G works, Bluetooth works  8)

Well I got a solid install of UB using the steps throughly, bu still ened up wiping Gemian I think. if you were genuinely able to boot Android, Rooted Droid, Debian and UB, I would lke to see it. the only thing I didn'y do is run that last line of code from step 1 in the top post. the only thing i didn't do was the last step of the first instruction post.

next flash the boot.img to one of the free boot slots using the following command "dd if=~/out/boot.img of=/dev/disk/by-partlabel/boot4 <- the last part will need to be changed to reflect you boot slot.

I was thinking about adding that line if code into the UBports-cosmo-installer.sh, loooking at the other installers I feel like that was the missing piece. buuuuut I am not code savvy enough to just through it in and hope for the best. also I think it needed edited a pinch to pull from the righ locations and the syntax seemed off.. I wish I could just image the whole device onto an extraneland the start from scratch , but I need another SD card for that. I'll let you know. WOuld love feedback on  my theory.


AND ITS STUCK. Opening terminal, going through some sort of instruction/show of features and the screen won’t swipe to keeping moving through it.

15
Cosmo Communicator - Linux / Re: Default Boot Partition
« on: November 21, 2020, 02:08:53 pm »
any word on being able to adjust the default boot option??? i would love my cosmo to just boot straight to rooted android everytime without having to select it.

Pages: [1]