• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ABANDONED][ROM][x3_row][6.0.1][CM13][Unofficial] CyanogenMod 13.0 for Lenovo Vibe X3

Status
Not open for further replies.

arpit_nnd

Senior Member
Jun 9, 2012
332
349
0
Bengaluru

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

Code:
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to flash your own Google Applications package (Gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit their Gerrit Code Review.

WARNING: The ROM is in Alpha stage and a lot of things are broken. This is not at all a daily driver.

What works:
  • Display & touchscreen
  • Hardware buttons (including capacitive keys)
  • Mobile network, data & dual SIM
  • WiFi & WiFi hotspot
  • Internal storage, SD card & USB OTG
  • Bluetooth
  • GPS
  • NFC
  • Charger & battery percentage
  • MTP & USB charging
  • All sensors (light, battery, accelerometer, magnetometer, gravity, gyroscope, rotation, proximity) & related features
  • Fingerprint reader
  • Vibration
  • ADB

What's broken:
  • WiFi
  • Speakers & microphone
  • Cameras
  • Notification LED & Flashlight
Feel free to contact me on Telegram @arpit_nnd if you would like to contribute.

How to install:
  1. Make sure you are on S217 stock firmware. Previous versions might work but they haven't been tested.
  2. Boot to TWRP.
  3. Wipe Dalvik/ART cache, system, cache & data.
  4. Install the zip and GApps if you need.
  5. Reboot system.
Changelog:
20161104:
  • Fix boot.
  • Fix WiFi.
  • Latest CM sources.
  • First alpha release.

20160925:
  • Initial release.
Sources:
XDA:DevDB Information
CyanogenMod 13, ROM for all devices (see above for details)

Contributors
arpit_nnd
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: S217 & above
Based On: CyanogenMod

Version Information
Status: Abandoned
Beta Release Date: 2016-11-04

Created 2016-09-27
Last Updated 2017-02-07
 
Last edited:

V_v3k

Senior Member
Mar 2, 2013
410
859
93
Coimbatore
I got the boot loop too. The phone just freezed as i played a game and then restarted itself and now its bootlooping forever. How do you fix that?
You were able to boot the device? What are the changes you made to the device tree? If possible can you share your code? And which ROM did you build?
 

Markovo

Member
Oct 11, 2016
24
2
3
You were able to boot the device? What are the changes you made to the device tree? If possible can you share your code? And which ROM did you build?
I did not do anything at all! I flashed the Marshmallow stock rom months before and yesterday the phone just freezed while i was playing a game. The it restarted itself and got the bootloop... Neither the recovery or the Qualcomm service menu can boot. I tried the QFIL unbrick method by flashing all the stock roms i could find but nothing changed.
 

arpit_nnd

Senior Member
Jun 9, 2012
332
349
0
Bengaluru
I got a clean build. But ended up in bootloop. BTW were you able to get a logcat??
Yeah, I am able to get the logcat and dmesg. Pretty likely it's the kernel or dt causing issues.

I got the boot loop too. The phone just freezed as i played a game and then restarted itself and now its bootlooping forever. How do you fix that?
I did not do anything at all! I flashed the Marshmallow stock rom months before and yesterday the phone just freezed while i was playing a game. The it restarted itself and got the bootloop... Neither the recovery or the Qualcomm service menu can boot. I tried the QFIL unbrick method by flashing all the stock roms i could find but nothing changed.
You are in the wrong thread mate, this one isn't for stock ROM.
 

arpit_nnd

Senior Member
Jun 9, 2012
332
349
0
Bengaluru
Did you try the boot.img of the other cm 13 ROM?? I couldn't try it because I'm away from my PC at the moment.
If you are referring to Xiaobai's CM builds, they aren't for the x3_row. :)
There are a number of reasons why it wouldn't work well.

One thing I haven't really tried (primarily because there is no reason it would help; my device tree is written from scratch for the x3_row), is flashing the Chinese stock before flashing my builds.
I have uploaded a newer build(not booting yet). So, if anyone can test out flashing over Chinese stock and report, it will be great.

EDIT: Tried swapping the boot image with Xiaobai's builds, device booted fine, most of the things were broken though (not so surprising). Things were very much the same as they were when I had built using Xiaobai's tree the very first time. Yet to test flashing over Chinese stock firmware.
 
Last edited:
  • Like
Reactions: nstream

V_v3k

Senior Member
Mar 2, 2013
410
859
93
Coimbatore
If you are referring to Xiaobai's CM builds, they aren't for the x3_row. :)
There are a number of reasons why it wouldn't work well.

One thing I haven't really tried (primarily because there is no reason it would help; my device tree is written from scratch for the x3_row), is flashing the Chinese stock before flashing my builds.
I have uploaded a newer build(not booting yet). So, if anyone can test out flashing over Chinese stock and report, it will be great.

EDIT: Tried swapping the boot image with Xiaobai's builds, device booted fine, most of the things were broken though (not so surprising). Things were very much the same as they were when I had built using Xiaobai's tree the very first time. Yet to test flashing over Chinese stock firmware.
Hmm... Which was your previous ROM? I mean the stock ROM version?
 
Status
Not open for further replies.