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.
Quote from: cam1965I've compiled with clang. But when loading the module I've got the same error.Have you tried to read the running kernels configuration (cat /proc|config.gz|gunzip>.config) and use this as a base for your kernel configuration? Another possible cause could be compiling from git head. Maybe there have been commits relevant for the module layout after the kernel has been built.
Maybe in the future I will try to compile the kernel and modules with gcc.
Thank you so much again.
Quote from: mithrandirQuote from: cam1965gemini@cosmopda:~$ cat /proc/version
Linux version 4.4.146 (nekit@supernova) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #28 SMP PREEMPT Sat Jan 18 22:23:37 GMT 2020
gemini@cosmopda:~$
thank you.
OK, that's it. From your output, the kernel has been compiled using clang. So install a clang compiler as near as possible to clang version 6.0.2. Command line should be similar to the one I have been using for the Android modules: https://www.mygnu.de/2020/02/exfat-support-...o-communicator/
First I also have tried with gcc and got the same exec format error on Android.
Another aproach would be to compile kernel and modules with gcc. For the Gemini this involved a mkbootimg step ( @see: https://github.com/gemian/gemini-keyboard-a...rnelCompilation ) to get a bootable image. I don't know if this also applies to the Cosmo and how to do it, yet.
OK. Thank you so much again.
Quote from: cam1965gemini@cosmopda:~$ cat /proc/version
Linux version 4.4.146 (nekit@supernova) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #28 SMP PREEMPT Sat Jan 18 22:23:37 GMT 2020
gemini@cosmopda:~$
thank you.
OK, that's it. From your output, the kernel has been compiled using clang. So install a clang compiler as near as possible to clang version 6.0.2. Command line should be similar to the one I have been using for the Android modules: https://www.mygnu.de/2020/02/exfat-support-...o-communicator/
First I also have tried with gcc and got the same exec format error on Android.
Another aproach would be to compile kernel and modules with gcc. For the Gemini this involved a mkbootimg step ( @see: https://github.com/gemian/gemini-keyboard-a...rnelCompilation ) to get a bootable image. I don't know if this also applies to the Cosmo and how to do it, yet.
Quote from: cam1965Hi , I am trying to compile some modules from kernel ( available at github ) . But when I did the command : modprobe " some module" it gave me an error something about exec format. ( because the kernel module compiled doesn't match the boot kernel ). I've also tried the kernel and kernel-headers from repository ( using apt-get install ) but in this case the Fn key doesn't work and also no module was loaded ( wifi also didn't work ). So what is the kernel source repository that matches the kernel boot ?Just guessing, had no time to try out the Linux image, yet.
Note : I've tried all branches from the kernel available at github .
Thank you all.
Maybe the compiler does not match the one used to compile the kernel. Had the same problem when compiling android modules.
Which compiler did you use? gcc? What is the output of cat /proc/version ?
Just to be sure, what is the version of the kernel packages?
If I am right with my guess, either use the matching compiler, probably clang, or create an own boot image. (boot image and modules compiled with same compiler).
Sorry that I have to ask again:
Did you flashed the TWRP.img using flashtool? I want to backup my Android non-rootet installation before repartitioning the Cosmo.
Which version did actually working and boot up properly, the oesf or the planet c. one?
Thanks!!
Quote from: cam1965Quote from: mifritscherHmm, for me it is working... Despite having problems unlocking the user partition (I didn't activated the encryption...)
Did you install twrp from the zip file ( link above ) ?
Thanks
Yep, I used the one at http://support.planetcom.co.uk/download/co...taller-beta.zip . Note that it shows the TWRP logo for 1-2 minutes before giving up on decrypt the user partition. And I repartitioned the system before (60/60).
Quote from: NinjiHey folks,
I've been experimenting over the past few days with trying to compile TWRP for the Cosmo so I can mess around with updates a bit more easily. Ultimately this may be a bit of a fruitless endeavour if Planet ends up releasing their own, but perhaps this will be useful for some reason or other anyway?
Source code on GitHub: https://github.com/Treeki/unofficial-twrp-cosmo
Initial flashable release: https://github.com/Treeki/unofficial-twrp-cosmo/releases
This is a fairly standard TWRP port with one exception - the Cosmo's userdata partition is encrypted, and getting TWRP to decrypt it is an adventure. I finally got it working after importing a bunch of blobs from Planet's vendor partition so that TWRP can start up the TrustKernel TEE, obtain the correct key and decrypt everything.
I've confirmed that the following features work on my Cosmo:
- Flashing partition images
- Creating backups
- adb while in recovery mode
Android hackery is still a very new thing for me and there's probably ways I could have made this better, but I did what I could with my lack of skills.
Unfortunately the Planet OTA doesn't seem to be flashable from TWRP - it complains about the build fingerprint being different, and even after commenting out that check in the updater script it fails to update the system partition. I think I may have to resort to manually flashing the updated partitions one-by-one.
Hi. I've installed twrp using the image provided by planet here ( http://support.planetcom.co.uk/download/co...taller-beta.zip ) in EMPTY_RECOVERY_BOOT_2 partition ( http://support.planetcom.co.uk/index.php/C...id_installation ).
But nothing happens when I boot to twrp.
I've also installed Debian in EMPTY_RECOVERY_BOOT_3 partition and debian boots fine.
What is the problem with twrp ?
I've also installed again twrp and the problem persists. I think the problem is because of Cosmo's userdata partition is encrypted. Mine is encrypted. Because mifritscher ( an user from this forum ) said in this post ( https://www.oesf.org/forum/index.php?showtopic=36119 ) that for him it is working... Despite having problems unlocking the user partition (he didn't activated the encryption...). He used the the same file from http://support.planetcom.co.uk/download/co...taller-beta.zip . He said that it shows the TWRP logo for 1-2 minutes before giving up on decrypt the user partition.
Can I use your twrp image overwriting the planet image after decompressing this zip file above ?
Thank you
Hey folks,
I've been experimenting over the past few days with trying to compile TWRP for the Cosmo so I can mess around with updates a bit more easily. Ultimately this may be a bit of a fruitless endeavour if Planet ends up releasing their own, but perhaps this will be useful for some reason or other anyway?
Source code on GitHub: https://github.com/Treeki/unofficial-twrp-cosmo
Initial flashable release: https://github.com/Treeki/unofficial-twrp-cosmo/releases
This is a fairly standard TWRP port with one exception - the Cosmo's userdata partition is encrypted, and getting TWRP to decrypt it is an adventure. I finally got it working after importing a bunch of blobs from Planet's vendor partition so that TWRP can start up the TrustKernel TEE, obtain the correct key and decrypt everything.
I've confirmed that the following features work on my Cosmo:
- Flashing partition images
- Creating backups
- adb while in recovery mode
Android hackery is still a very new thing for me and there's probably ways I could have made this better, but I did what I could with my lack of skills.
Unfortunately the Planet OTA doesn't seem to be flashable from TWRP - it complains about the build fingerprint being different, and even after commenting out that check in the updater script it fails to update the system partition. I think I may have to resort to manually flashing the updated partitions one-by-one.
Thank you again.Quote from: cam1965Quote from: mifritscherHmm, for me it is working... Despite having problems unlocking the user partition (I didn't activated the encryption...)
Did you install twrp from the zip file ( link above ) ?
Thanks
Yep, I used the one at http://support.planetcom.co.uk/download/co...taller-beta.zip . Note that it shows the TWRP logo for 1-2 minutes before giving up on decrypt the user partition. And I repartitioned the system before (60/60).
Hmm, for me it is working... Despite having problems unlocking the user partition (I didn't activated the encryption...)
Quote from: cam1965Quote from: mibryThere was an email sent out this afternoon from Planet to people that had indicated they wanted beta Linux for the Cosmo. There is a Linux beta image available for testing from Planets site. Be aware it is very early beta.
Regards
Mibry
Where is the link to download the image ? Can I install this image ( I've already partitioned my Cosmo ) without damage my rooted android installed? Thank you.
Already found it : http://support.planetcom.co.uk/index.php/Cosmo_Linux_Beta
Only to know : Can I install this image ( I've already partitioned my Cosmo ) without damage my rooted android installed. ?Thank you.
I have also not been able to get twrp to boot. I was planning on making a full backup before modifying stuff.
