When Official CM14.1? - Wileyfox Swift

When Official CM14.1? - Wileyfox Swift

When will have official support?

I wanna know too!

No reason to expect official support for bleeding-edge android software on old (budget) devices. Sorry to be the one to tell you :/

Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g

[email protected] said:
Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g
Click to expand...
Click to collapse
My phone is a gm 4g but i have always treated it as a swift

It has also stopped CM13 support?The latest nightly is on 18 November.

They have not stoped cm13 support but updates it more rarely because the build only when major changes are there. And second they are working on cm14.1 and are focused more on new cm version...

Guys I'll be building an unofficial CM14.1 for the swift tonight, I'll post when it's here

Why dont. Build rr remix N 5.8.0 64bit so we can use it with foxy kernel...

[email protected] said:
Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g
Click to expand...
Click to collapse
Do you have a source for these claims?

The cm13 nightlies have all moved to weeklies unless some urgent bug is found,
As a reference
https://github.com/CyanogenMod/hudson/commit/5f49ecc49fcf22358ca2a87190df20ed9bad6da3

VivaLaVent said:
Guys I'll be building an unofficial CM14.1 for the swift tonight, I'll post when it's here
Click to expand...
Click to collapse
Any news ? I also planned to build CM14.1 too but in the crackling repo there is no branch called cm-14.1

Math314 said:
Any news ? I also planned to build CM14.1 too but in the crackling repo there is no branch called cm-14.1
Click to expand...
Click to collapse
Yeah I stumbled on that problem too and gave up.

Ok, so we have to wait for an official release of CM14.1 for the swift.

Math314 said:
Ok, so we have to wait for an official release of CM14.1 for the swift.
Click to expand...
Click to collapse
I found out that you can install official CM14.1 for seed on WileyFox Swift. First flash stock General Mobile 4G ROM using fastboot, then flash TWRP for seed and CM14.1 for seed.
I'll send detailed instructions if you'd like.

VivaLaVent said:
I'll send detailed instructions if you'd like.
Click to expand...
Click to collapse
Yeah I'd be very interested. I have some time to try it during the Christmas holiday.

Math314 said:
Yeah I'd be very interested. I have some time to try it during the Christmas holiday.
Click to expand...
Click to collapse
Okay so here is what I did and I am now running official CM14.1 arm (so no 64 bit). From my experience it is very fast, very battery friendly and most importantly: very stable.
WHAT YOU'LL NEED:
TWRP for WileyFox Swift (crackling)
General Mobile 4G (seed) stock rom
TWRP for Android One 2nd gen (seed)
CyanogenMod 14.1 for Android One 2nd gen (seed)
Optional, but I strongly recommend these:
Open GApps (ARM, 7.1, pico variant)
Google Pixel Bootlogo and Bootanimation
INSTRUCTIONS:
First, I suggest making a backup using TWRP for WileyFox Swift (crackling). I strongly suggest that you backup everything, in case something goes wrong or you aren't satisfied with CM14.1.
Now for effectively installing CM14.1 on the device:
YOU WILL LOSE ALL DATA AND INTERNAL STORAGE PAST THIS POINT UNLESS YOU BACKUP!
Download the General Mobile 4G (seed) stock rom. We need this in order to make sure the device identifies as an Android One Second Generation device (seed) instead of WileyFox Swift (crackling). The devices are clones and are essentially the same hardware. Once you've downloaded the stock rom, unzip it. Then put your device in fastboot mode and execute "INSTALL_MOB30Z.exe". Choose "A. INSTALL STOCK ROM" and wait for it to complete.
Now install TWRP for Android One 2nd gen (seed).
Now boot into TWRP recovery and got to Wipe > Advanced Wipe. Check Dalvik / ART Cache, System, Data, Internal Storage and Cache.
When the wipe is complete, go to Reboot > Recovery to reboot into recovery again. Now install CyanogenMod 14.1 for Android One 2nd gen (seed).
If desired, install Open GApps (ARM, 7.1, pico variant). To replace the "General Mobile" boot image with the Google logo, also flash Google Pixel Bootlogo and Bootanimation.
Let me know if you need help. Happy holidays! :fingers-crossed:
arvinquilao said:
IMPORTANT: Please note that the latest official TWRP for seed is not yet updated to handle CM's updater app. If users want to update to latest nightly, they need to download the zip and flash normally using TWRP. CM updater app is not recommended until the patched official TWRP is released.
Click to expand...
Click to collapse

Related

[ROM][5.1.1] CM12.1 Official Nightlies for Find 7A/S

Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:

Somebody successfully flashed it ? It works ?

raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.

Anyone tried 20150119 build yet? is it working??

CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.

It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.

I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small

on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7

sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.

mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app

You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries

Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers

darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.

ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:

Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/

Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )

alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.

Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.

Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?

Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.

LineageOS 18.1 [R] [11] (Unofficial) Mi Pad 4 Plus (clover)

LineageOS 18.1, see this link
Installation instructions :
- Download the zip(s).
- Install latest TWRP for clover
- Perform a backup of your current ROM (optional)
- Wipe dalvik/cache (upgrade from lineageos 18.1) and wipe system/data if upgrade from other rom.
- Flash ROM.
- Flash GApps (NikGApps is recommended) is a must.
- Optional: Flash latest Magisk for root.
Everything should work.
Source :
sdm660

Hello !
No SD card.
Clean installation.
NikGapps-core-arm64
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------

Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.

Awesome! Thanks!

rchoi999 said:
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Click to expand...
Click to collapse
I didn't use sdcard...it would be help if log is available...

-----> Have New Update 2020/10/19 I didn't install it, don't know the difference

addro said:
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
Click to expand...
Click to collapse
Some update in lineageos qcom repo....

Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
@sabar_op, @sb56637, @amityg
Please keep in mind that there are many reports of bootloops etc using TWRP with Android 11.
TWRP officially supports all devices running Android up to 10, except devices LAUNCHED with 10 or later (having dynamic/logical partitions). There are no versions officially supporting devices running Android 11 to date:
TWRP 3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10. It does, however, fix support for legacy devices that upgraded to Android 10, but retain the old partition scheme.
Click to expand...
Click to collapse
https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/
Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10 (only). There's been no further versions. See here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83725859
The solution for most using custom Android 11 based ROMs has been to KEEP STOCK Recovery and use ADB fastboot boot TWRP (NOT flash) command from PC when needing custom recovery functions to flash ROMs etc. This seems to work for most despite having no TWRP fully supporting Android 11.
Nb. To achieve root with MagiskSU, this method is probably even more critical as users are reporting bootloops with TWRP custom recovery (flashed) and Android 11 when flashing Magisk pretty much accross the board.
Nb2. Achieving root with MagiskSU can alternatively be done without custom recovery by flashing Magisk Manager patched boot.img (extracted from ROM) using ADB fastboot flash image command from PC. This may be a less fraught method.
I'm still on LOS 17.1, but the above outlines the approach I intend to take / try soon.
Hope it helps, PW

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...

I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.

Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.

Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.[/QUOTE]
View attachment 5123311

idcom said:
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Click to expand...
Click to collapse
View attachment 5123311[/QUOTE]
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?

Enry44 said:
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Click to expand...
Click to collapse
Thanks for confirmation...it means no problem with mipad 4 wifi only... :good::good::good:

sabar_op Sure, where can I find the log?

Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?[/QUOTE]
Have PMed you. Settings-≥Storage shows Portable but corrupted. When I format nothing changes.

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
This is probably because didn't install a *Gapps package.

sabar_op said:
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
Click to expand...
Click to collapse
Alex Kane said:
This is probably because didn't install a *Gapps package.
Click to expand...
Click to collapse
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.

sb56637 said:
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
Click to expand...
Click to collapse
Yeah, but apparently LOS 18.0 beta doesn't.
I tried LOS 18.0 (beta) without gapps first and it would bootloop after reaching the home-screen. Flashing gapps would solve the issue (for me) but I don't use gapps so ... I went back to LOS 17.1.
I also experienced the issue with the sdcard not being properly detected.

[ROM][UNOFFICIAL][10.0]LineageOS 17.1 beyond1qlte

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working:
IMS (no volte)
Bixby button currently not set
Instructions:
Make sure twrp by afaneh92 is installed and functional.
Download the latest build (and optionally gapps).
Reboot to recovery
Wipe system, data, and cache (required if you switch from other ROMs)
Flash the latest build, gapps, and magisk.
Reboot
Downloads:
Galaxy S10 Snapdragon (G973U): https://github.com/klabit87/OTA/rel...eage-17.1-20201114-UNOFFICIAL-beyond1qlte.zip
Google Apps: https://opengapps.org/
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred.
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. For now please report any bug below.
Group:
Join this group for contacting me and bug reporting (typically fast response )
Unlocked Samsung US devices
https://t.me/joinchat/CG3Ojlb0TwDDrN-RY5UqmQ
Also dont forget to hit the thanks button!
Contributors
Thanks to @jrkruse and @afaneh92 for testing initial builds.
ROM Firmware Required: Minimum of Android 10 firmware
Based On: LineageOS
Version Information
Status: Beta
Source:
https://github.com/klabit87/android_device_samsung_beyond1qlte
https://github.com/klabit87/android_device_samsung_sm8150-common
https://github.com/klabit87/android_kernel_samsung_sm8150-common
https://github.com/klabit87/android_vendor_samsung_sm8150-common
Created 2020-11-14
Last Updated 2020-11-14

Reserved

Got it installed. Haven't had a chance to use as a daily driver, since I use volte. Hope it gets working eventually! Would definitely love to use as a daily driver after that!

Same. would love to see volte.

illspiritX said:
Same. would love to see volte.
Click to expand...
Click to collapse
I also had issuess with GPS on the sm-g973u, but that's something I testing with op, when he gets a new build made

Hi. I'm new here and I need some information. Do the fingerprint sensor and all the cameras work for this custom rom?

I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?

pitchdown said:
I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?
Click to expand...
Click to collapse
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.

klabit87 said:
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.
Click to expand...
Click to collapse
what will be shared?
Is it on a s10 not possible yet?

pitchdown said:
what will be shared?
Is it on a s10 not possible yet?
Click to expand...
Click to collapse
I have been working on a lineage 18.1 build for s10. Just be patient.

Will 18.0 qork
klabit87 said:
I have been working on a lineage 18.1 build for s10. Just be patient.
Click to expand...
Click to collapse
Will 18.0 work with Magisk?

I don't see why not. I haven't tested that yet though

klabit87 said:
I don't see why not. I haven't tested that yet though
Click to expand...
Click to collapse
until now magisk isn`t installed after flashing with 18.1
I hope your new version will have a help to this.

I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.

Replicatorz said:
I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.
Click to expand...
Click to collapse
You have to use the Magisk Hide option, and select everything with "com.google" in the package name.

Does this work with G9730 Chinese / Hong kong snapdragon variant?

Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.

BWhitmore said:
Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.
Click to expand...
Click to collapse
I encountered the same problem for Google Map when I'm in battery save mode.

Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!

aceqdl0925 said:
Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!
Click to expand...
Click to collapse
Yes, it's just like how you flash every other ROM. Check this.

[ROM][UNOFFICIAL][PORT] LineageOS 13.0 for Lenovo A1000

LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
LineageOS 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github Repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Device-specific source code:
Kernel source: https://github.com/Lehkeda/kernel_lenovo_sp7731ge
Downloads:
ROM: https://drive.google.com/file/d/1F_dTLQGIspPb4LI8jNmnrE-iVovkSaKa/view?usp=sharing
Gapps: http://opengapps.org
Extras (su or Weather Provider): https://download.lineageos.org/extras
What works?
Wi-Fi
RIL (partially)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera
Video (playback & recording)
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues:
Bluetooth doesn't work
You'll get "CM audio error" on boot. Just ignore that.
Keyboard error when booting the system up, workaround is to install an another keyboard software like OpenBoard.
Incorrect RIL signal. Shouldn't be a problem .
WiFi doesn't get disabled on sleep mode, and it's draining the battery
Installation Instructions:
Download TWRP 3.0.3 here: https://www.androidfilehost.com/?fid=15664248565197185286
Root your phone!
Flash TWRP 3.0.3 to your phone using Rashr/Flashify
If you did flash the recovery, copy the ROM to your phone, then reboot to recovery
In the recovery, wipe: Data, Dalvik/ART cache, System, Cache
Install the ROM, and GApps! (optional)
When you did finish installing the ROM, reboot!
Woala! You installed LineageOS to your Lenovo A1000

What is the base ROM?

TriDiscord said:
What is the base ROM?
Click to expand...
Click to collapse
grandprimeve3g

hello!
my old phone is a dual sim a1000.
~2 years ago i wanted to flash a newer android cuz the stock was a slow piece of **** but i was not successful.
ive flashed twrp 3.2.1-0 on it somehow (i dont remember, was a long time ago) then ive tried to install a custom rom but didnt work, it got stuck on the lenovo screen. since i havent found any other custom rom ive just put it into my drawer and forget about it.
today i wanted to try it again so after a quick search ive found your rom and it worked. finally the phone can start and basically its not a brick anymore. but that bluetooth problem is severe.
since your post is from the summer, can i ask if you abandoned the project or not? did you manage to get the BT working eventually? is there any new build i can try that may work?
if not, do you know how should i restore the stock rom to this phone? is it worth it tho? or the broken custom lineage is still better than the bloated stock in 2022?
thank you

kwallet said:
hello!
my old phone is a dual sim a1000.
~2 years ago i wanted to flash a newer android cuz the stock was a slow piece of **** but i was not successful.
ive flashed twrp 3.2.1-0 on it somehow (i dont remember, was a long time ago) then ive tried to install a custom rom but didnt work, it got stuck on the lenovo screen. since i havent found any other custom rom ive just put it into my drawer and forget about it.
today i wanted to try it again so after a quick search ive found your rom and it worked. finally the phone can start and basically its not a brick anymore. but that bluetooth problem is severe.
since your post is from the summer, can i ask if you abandoned the project or not? did you manage to get the BT working eventually? is there any new build i can try that may work?
if not, do you know how should i restore the stock rom to this phone? is it worth it tho? or the broken custom lineage is still better than the bloated stock in 2022?
thank you
Click to expand...
Click to collapse
hi, let's answer to these questions!
kwallet said:
since your post is from the summer, can i ask if you abandoned the project or not? did you manage to get the BT working eventually? is there any new build i can try that may work?
if not, do you know how should i restore the stock rom to this phone? is it worth it tho? or the broken custom lineage is still better than the bloated stock in 2022?
Click to expand...
Click to collapse
1. yes, i did abandon the project, since i didnt have any testers.
2. No, I didn't get it working, I don't own this device. I ported it and guess it boots. D
3. Nope, sorry. I might try to port LOS14.1 if you can test the ROM of course.
4. I don't know. But it's definitely NOT worth it to install stock rom back since it's full of bloatware. It's better to use LineageOS

Headset is Reversed, How to fix this ?

AetherTF said:
Headset is Reversed, How to fix this ?
Click to expand...
Click to collapse
What do you mean "reversed"

notnoelchannel said:
What do you mean "reversed"
Click to expand...
Click to collapse
Im sorry my english is broken i mean Left audio coming from right headset and vice versa

AetherTF said:
Im sorry my english is broken i mean Left audio coming from right headset and vice versa
Click to expand...
Click to collapse
I think it's not a rom-related problem, can you try with an other headset?

notnoelchannel said:
I think it's not a rom-related problem, can you try with
Click to expand...
Click to collapse
I already try this headset with 2 different phone and its work correctly

notnoelchannel said:
hi, let's answer to these questions!
1. yes, i did abandon the project, since i didnt have any testers.
2. No, I didn't get it working, I don't own this device. I ported it and guess it boots. D
3. Nope, sorry. I might try to port LOS14.1 if you can test the ROM of course.
4. I don't know. But it's definitely NOT worth it to install stock rom back since it's full of bloatware. It's better to use LineageOS
Click to expand...
Click to collapse
hello. thank you for replying.
if you want i can test any build you throw at me just i dont wanna flash another bootloader cuz i dont wanna risk permabricking the phone. right now that twrp 3.2.1 is installed and working properly.

LineageOS 14.1 is ready for testing!!
Can someone test it please?
You can find the download link here.

notnoelchannel said:
LineageOS 14.1 is ready for testing!!
Can someone test it please?
You can find the download link here.
Click to expand...
Click to collapse
ill install it when i get home

kwallet said:
ill install it when i get home
Click to expand...
Click to collapse
Make sure to make a backup of your current os!!

notnoelchannel said:
Make sure to make a backup of your current os!!
Click to expand...
Click to collapse
no joy

kwallet said:
no joy
Click to expand...
Click to collapse
Oops sorry the partitions are wrong lemme fix that

Go into the zip, delete everything inside the META-INF folder, and replace them with this. Then repack the zip and try to install the rom again.

notnoelchannel said:
Go into the zip, delete everything inside the META-INF folder, and replace them with this. Then repack the zip and try to install the rom again.
Click to expand...
Click to collapse
installer finishes but after reboot nothing happens, its stuck on lenovo logo. ive waited 10 minutes but nothing. maybe ive f..ed up the zip?
didnt unzip, just opened with winrar, copypasted the inf and saved the zip.

kwallet said:
installer finishes but after reboot nothing happens, its stuck on lenovo logo. ive waited 10 minutes but nothing. maybe ive f..ed up the zip?
didnt unzip, just opened with winrar, copypasted the inf and saved the zip.
Click to expand...
Click to collapse
this means that lineage 14.1 doesn't boot, you can reflash the 13.0 version instead. i got a new stable pacrom build that has only have the bluetooth bug, i'll post it soon.

notnoelchannel said:
this means that lineage 14.1 doesn't boot, you can reflash the 13.0 version instead. i got a new stable pacrom build that has only have the bluetooth bug, i'll post it soon.
Click to expand...
Click to collapse
thank you, will waiting for that.
btw this A1000 is such a crap phone, i cant even enter the recovery properly. it should work fine with volume up + power (until lenovo logo then release power) but sometimes it just stuck at lenovo logo. its annyoing.
edit: actually its volume down + power lol.

my experiences - flashing custom rom Xiaomi Mi Play (lotus)

I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you

Can you share the link of the other builds please?

RezaUllah__ said:
Can you share the link of the other builds please?
Click to expand...
Click to collapse
Havoc: https://download.havoc-os.com/?dir=arm64-aonly
CrDroid R Mod: https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
AOSP: https://forum.xda-developers.com/t/aosp-9-0-2019-08-25-phh-treble.3831915/
Ressurection: https://forum.xda-developers.com/t/resurrection-remix-unofficial-2018-06-28-phh-treble.3767688/

Good blog! I truly love how it is simple on my eyes and the data are well written. I’m wondering how I could be notified when a new post has been made. I have subscribed to your feed which must do the trick! Have a great day!
meta trader 4

IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
The 2nd link is twrp ryt?

RezaUllah__ said:
The 2nd link is twrp ryt?
Click to expand...
Click to collapse
3rd link

It’s nearly impossible to find knowledgeable folks on this topic, however, you appear to be there’s more you are talking about! Thanks
Monoprice 110010

Bro it shows this...why?

RezaUllah__ said:
Ok it I flashed it ...but it shows that I can't wipe data ..shows error
Click to expand...
Click to collapse
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data

IpyZ said:
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data
Click to expand...
Click to collapse
So if I just use format data ...I am good to go?

RezaUllah__ said:
So if I just use format data ...I am good to go?
Click to expand...
Click to collapse
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it.

IpyZ said:
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it
Click to expand...
Click to collapse
Reformat partition? How do you do that?

RezaUllah__ said:
Reformat partition? How do you do that?
Click to expand...
Click to collapse
I mean, option "format data" is doing it for you

IpyZ said:
I mean, option "format data" is doing it for you
Click to expand...
Click to collapse
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?

RezaUllah__ said:
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?
Click to expand...
Click to collapse
Yeah that should work.
Please remember that all your personal data like photos or documents will be gone so, make sure u made a backup

You produced some decent points there. I looked on the internet with the problem and discovered most individuals go in addition to along with your website.
Internet Plans and Offers

how stable is the rom?

Well, many apps just don't works, because they are thinking that the device is rooted. In some way it's true.
There are some strange behaviours of fingerprint detector.
But overall the ROM is not crushing
I haven't noticed any other bugs or I do not remember them. But that was mine main pain about this rom
alcatel4010x said:
how stable is the rom?
Click to expand...
Click to collapse

Develop Bugs

welcome