• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][UNOFFICIAL][6.0.1] CyanogenMod 13.0 for Elephone Trunk

Search This thread

josoft86

Member
Mar 9, 2015
30
15
Reggio di Calabria
There's a new update on the server that should fix the issues with AudioFX and the camera:
https://it-chefs.com/cmota/builds/full/cm-13.0-20161116-UNOFFICIAL-trunk.zip
@olidroide:
Can you try this boot image and see whether it solves the touch issues for you?
https://it-chefs.com/cmota/builds/full/boot-20161116-trunk.img

Just do the following:
Code:
adb reboot bootloader
fastboot boot boot-20161116-trunk.img
With this version all the camera work but we have problems with SuperSu and Xposed. After installation go to LOOP start and will not start again. Made several attempts and also the normal SuperSu update without TWRP, it does not work. You can solve !!!!!! !!!!!!:angel::angel::angel::angel:
 
  • Like
Reactions: todoss

olidroide

Member
Sep 15, 2010
25
30
Madrid
@ottmi Dear, thank you for the work you are doing and I hope you will continue to make giving us the CM14. I wanted to advise you, if technically possible, put in SuperUser updates to avoid any update to reinstall it. Thanks again and good work.:cool::cool::cool:

There's a new update on the server that should fix the issues with AudioFX and the camera:
https://it-chefs.com/cmota/builds/full/cm-13.0-20161116-UNOFFICIAL-trunk.zip
@olidroide:
Can you try this boot image and see whether it solves the touch issues for you?
https://it-chefs.com/cmota/builds/full/boot-20161116-trunk.img

Just do the following:
Code:
adb reboot bootloader
fastboot boot boot-20161116-trunk.img


Hi @ottmi thanks for your work and sorry by delay on reply you...

After download it and try to boot from bootloader (AKA fastboot mode) not go into TWRP directly boot the animation start and boot loop in the animation, nothing happens :S too strange :S
 

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
hi ottmi, i would like to thank you for the rom.
But my phone is totally bricked, I don't think is related to last update that i did few minutes before it bricked.
By using lsusb it shows as Qualcomm, Inc. Gobi Wireless Modem (QDL mode).
can i do something?
thank you again

Is fastboot working?
 

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
With this version all the camera work but we have problems with SuperSu and Xposed. After installation go to LOOP start and will not start again. Made several attempts and also the normal SuperSu update without TWRP, it does not work. You can solve !!!!!! !!!!!!:angel::angel::angel::angel:
I neither use use Xposed nor SuperSU, so I really have no idea why they wouldn't work.. But what do you need SuperSu for? CM comes with integrated SU..
 
  • Like
Reactions: saboy1976

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
Hi @ottmi thanks for your work and sorry by delay on reply you...

After download it and try to boot from bootloader (AKA fastboot mode) not go into TWRP directly boot the animation start and boot loop in the animation, nothing happens :S too strange :S
So just to be clear: You've flashed the 20161116 ROM and that boots? But if you try to boot the boot-20161116-trunk.img it bootloops? Can you provide a logcat?
 
  • Like
Reactions: olidroide

olidroide

Member
Sep 15, 2010
25
30
Madrid
So just to be clear: You've flashed the 20161116 ROM and that boots? But if you try to boot the boot-20161116-trunk.img it bootloops? Can you provide a logcat?

Hi @ottmi I only open fastboot mode and boot with the command
Code:
fastboot boot boot-20161116-trunk.img
this not open a recovery, boot directly to the system. I don't flash the ROM 20161116 because I have the old TWRP. I will attach you the log later ;) thanks @ottmi

UPDATE
This is the dmesg of boot: https://gist.github.com/olidroide/96d77542440d7ffd02ad33dde0d5ea9c
 
Last edited:

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
Hi @ottmi I only open fastboot mode and boot with the command
Code:
fastboot boot boot-20161116-trunk.img
this not open a recovery, boot directly to the system. I don't flash the ROM 20161116 because I have the old TWRP. I will attach you the log later ;) thanks @ottmi

UPDATE
This is the dmesg of boot: https://gist.github.com/olidroide/96d77542440d7ffd02ad33dde0d5ea9c
You were supposed to use the boot image with my CM13 ROM, it probably won't work with any other ROM - which would explain the bootloop. Also this has nothing to do with TWRP, the recovery image and the system image are independent of each other.
 

olidroide

Member
Sep 15, 2010
25
30
Madrid
You were supposed to use the boot image with my CM13 ROM, it probably won't work with any other ROM - which would explain the bootloop. Also this has nothing to do with TWRP, the recovery image and the system image are independent of each other.

Hi @ottmi thanks for you advise I do this:

  1. Boot bootloader to install recovery twrp-3.0.2-20161108-trunk.img
  2. boot recovery twrp-3.0.2-20161108-trunk.img
  3. Wipe data
  4. Install cm-13.0-20161116-UNOFFICIAL-trunk.zip with open_gapps-arm64-6.0-pico-20161124.zip
  5. reboot in bootloader for boot boot-20161116-trunk.img

RESULT:
cm13 load but the touchscreen problem now is worst :S :S I copy the dmesg after boot firsts time CM13 with the boot image: https://gist.github.com/olidroide/03946bd7f590d6e4100a1d6ae2f47144 Maybe we can't find a solution for this issue... I revert the changed restored the official Android 5 image :S @ottmi, Do you think we can find a solution? doesn't matter if is too complex I don't wanna take too much time of your. Thanks really for your support :)
 

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
ok i did with Qualcomm flash tool and now the phone shows the elephone logo when connected to pc. After a while the logo started changing multiple colors and i got the android message when is optimizing apps. But then it went back to elephone logo.
What i can do next?

edit: if i try to turn it on by pressing the power button the phone vibrates and the menu light is blinking but nothing happens.

edit2: it booted! let's see how it goes, grazie per ora siljaer ;)

Prego!

Sorry for the delay.... however, it's good to know that you're on board again! :)

---------- Post added at 19:09 ---------- Previous post was at 19:06 ----------

Hi @ottmi,

I've found this: https://github.com/BenefitA3

what do you think about it? Can it be useful to us?
 
Last edited:
  • Like
Reactions: marcachas

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
I've found this: https://github.com/BenefitA3

what do you think about it? Can it be useful to us?
I particularly like how they copied all the modifications I did for the Trunk to their repository without giving credit..

Anyway, there's quite a few devices now with official CM14.1 support, including the Moto G3 that uses the same chipset. So it shouldn't be too hard to get it up and running, but currently I don't have the time to do it.. Maybe I will find some time over christmas..
 
  • Like
Reactions: marcachas

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
I particularly like how they copied all the modifications I did for the Trunk to their repository without giving credit..

Anyway, there's quite a few devices now with official CM14.1 support, including the Moto G3 that uses the same chipset. So it shouldn't be too hard to get it up and running, but currently I don't have the time to do it.. Maybe I will find some time over christmas..

Your CM13 is working so nice that I am not eager to try CM14 :) My question was about any possible improvement in the kernel(s). Unfortunately, you said it is quite the opposite :(

BTW, I am doing some experiments with ubports (looooong way to go), and I've found that your kernel is missing(?) /include/linux/blk_types.h . I had some problem also with blk-iopoll.h (file name too long (?), but this is probably due to some mistake of mines).

besides, I have found a problem in /drivers/input/touchscreen/gt9xx/goodix_tool.c:389:5 (format '%lu' expects long unsigned int instead of unsigned int).

I am reporting here because I am not sure at all the corrections I made are the right ones....

Edit: files were ok, for some unknown reason archive manager did not expand them (!)
 
Last edited:
  • Like
Reactions: marcachas

saboy1976

Senior Member
Jan 4, 2014
57
8
Good morning everybody, i Wonder if anyone else have a problem with EAP-SIM ,because since i've installed android 6 on my both trunk, i have authentification error when i want to connect my phone to "FREE WIFI SECURE" in France with "Free Mobile" sim card, with lollipop the authentification worked. Thanks for all you've done for our Trunk. Have a nice day .
 

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
RESULT:
cm13 load but the touchscreen problem now is worst :S :S I copy the dmesg after boot firsts time CM13 with the boot image: https://gist.github.com/olidroide/03946bd7f590d6e4100a1d6ae2f47144 Maybe we can't find a solution for this issue... I revert the changed restored the official Android 5 image :S @ottmi, Do you think we can find a solution? doesn't matter if is too complex I don't wanna take too much time of your. Thanks really for your support :)
That's really strange. The boot image should use the same kernel like the TWRP image. And that worked fine with your display, didn't it?
 
  • Like
Reactions: olidroide

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
Good morning everybody, i Wonder if anyone else have a problem with EAP-SIM ,because since i've installed android 6 on my both trunk, i have authentification error when i want to connect my phone to "FREE WIFI SECURE" in France with "Free Mobile" sim card, with lollipop the authentification worked. Thanks for all you've done for our Trunk. Have a nice day .
EAP-SIM was indeed disabled.. I've created a new ROM that should now enable it. Could you please try whether that works? It's available via the OTA server.
 
  • Like
Reactions: saboy1976

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.

    Working:
    • Phone
    • Mobile data in dual-sim configuration
    • Wifi
    • GPS
    • Bluetooth
    • Audio

    Known Bugs:
    • Torch tile in the status bar is not available
    • Haptic feedback on soft buttons


    XDA:DevDB Information
    CM13 for Elephone Trunk, ROM for all devices (see above for details)

    Contributors
    ottmi, siljaer
    Source Code: https://github.com/ottmi/android_device_elephone_trunk

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.10.x
    Based On: CyanogenMod

    Version Information
    Status: Beta
    Current Beta Version: 20160902
    Beta Release Date: 2016-09-02

    Created 2016-06-07
    Last Updated 2016-09-02
    10
    New ROM is up: http://forum.xda-developers.com/devdb/project/dl/?id=19864

    It now hopefully includes a working thermal-engine that should fix the overheating problems. Also, I brought back the audio_effects.conf that should enable echo cancellation also for VoIP calls.
    I've updated the kernel to reflect the latest changes upstream, including patches against the QuadRooter vulnerabilities. However, the QuadRooter scanner by Check Point still shows the phone as vulnerable to CVE-2016-5340 which is odd since the new kernel includes Code Aurora's patches (see https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340). So maybe the patch doesn't fix it properly or the app is buggy. There are similar reports for other phones as well.

    I've also uploaded my own build of TWRP 3.0.2 that should fix the issues with the realtime clock. I was able to do a backup with it and also flash the new ROM but apart from that I haven't tested it much. So use at your own risk. But then again, this applies to everything I upload here :)
    http://forum.xda-developers.com/devdb/project/dl/?id=19861
    9
    I've just uploader a new ROM:
    http://forum.xda-developers.com/devdb/project/dl/?id=20162

    It includes the patched kernel that hopefully fixes the sdcard problems as well the fix for the previous ROM that corrects the thermal-engine and audio effects. Apart from that, I've now switched to the Wileyfox blobs for everything but the camera and tweaked the auto-brightness a bit more. I think it's much better now (at least for me ;)). Also, I've setup my own server for OTA updates - so from now on you can conveniently update from your phone.
    8
    Okay, it worked with Gapps Pico - thanks a lot! I installed all the other Google apps from the Playstore :)
    Quick heads-up on the next build:
    any space issues with the system partition will be solved. Turns out that the actual partition is 1.8GB but I'm using only 1GB for the filesystem. So the next build will have 800M of extra space - that should be sufficient for any gapps package.

    Also I will return to the generic CyanogenMod MSM8916 kernel. I had problems with this kernel earlier, with camera and sensors not working. I've solved the problems with the sensors (and actually improved sensitivity for the light sensor) and for now I've also fixed the camera problems by backporting the driver from mdeejay's Ark Benefit kernel. I also had to backport the touchpanel driver, but I'm quite confident to make it work without any backported drivers. All issues until now were due to errors in the devicetree..
    7
    Just in time before the weekend, here's a new ROM for download: http://forum.xda-developers.com/devdb/project/dl/?id=19444

    It incorporates @siljaer's changes to mixer_paths.xml - let's see whether this solves the echo problems for others as well :)

    Apart from that there are only minor changes: I added some more permission files for the lights and proximity sensors, set the screen density to 300dpi, and backported the LZ4 compression from the vanilla 3.12 kernel to use it in ZRAM (the stock rom did so as well). I've also applied a hack that restarts the media service after the phone has fully booted. I've seen this in the Oneplus Onyx source and it seems to improve the issues with the disappearing torch tile.