[ROM][OFFICIAL][THEA][6.0.1] Cyanogenmod 13.0 [UNIFIED] - Moto G 2014 LTE Original Android Development

[ROM][OFFICIAL][THEA][6.0.1] Cyanogenmod 13.0 [UNIFIED] - Moto G 2014 LTE Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : http://download.cyanogenmod.org/?device=thea
Google Apps : http://opengapps.org/
Reporting Bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
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)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
Phone model (XT1072/XT1077/XT1078/XT1079):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
@luca020400: As he is co-maintainer
@Somcom3X: Help during development
@kaustubh88 and @crpalmer : Kernel Tree and Patches
@Thecrazyskull : for being useless
Motorola : For providing the Kernel Source Code
CM Team
Donations :
You don't have to but if you want so...
LuK1337: http://forum.xda-developers.com/donatetome.php?u=5075128
luca020400: http://forum.xda-developers.com/donatetome.php?u=5778309
XDA:DevDB Information
CM13.0 For Moto G 2014 LTE, ROM for the Moto G 2014 LTE
Contributors
LuK1337, luca020400, Somcom3X, crpalmer, Intervigil
Source Code: https://github.com/Cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-11-10
Last Updated 2016-04-22

Good to have a separate thread for CM 13 (thea) since yesterday!:good:
One thing in post #1 is confusing - the title image in post #1 says Cyanogen Mod 12.1 ?!
The changelog-link in post #1 forces an error 404 in loaded page!

bitstra said:
Good to have a separate thread for CM 13 (thea) since yesterday!:good:
One thing in post #1 is confusing - the title image in post #1 says Cyanogen Mod 12.1 ?!
The changelog-link in post #1 forces an error 404 in loaded page!
Click to expand...
Click to collapse
I guess I was too lazy to redo this image. I'll do it later I need to grab PSD outta my old HDD.
I also fixed that link.

LuK1337 said:
I guess I was too lazy to redo this image. I'll do it later I need to grab PSD outta my old HDD.
I also fixed that link.
Click to expand...
Click to collapse
...was not that priority on top
Take your time and YOURS priorities

A pretty damn good build. I'm getting a couple of issues, I'm happy to logcat the first one if it's new to you?
1) I'm getting force close from the Facebook and Facebook Messenger apps. I can't get past the login screen before it freezes and force closes the app.
2) The first time I did an image update using the 11/11/2015 build image I could download the zip to the Downloads directory, but I couldn't find any folder to place it in that could be seen by TWRP. Each folder I tried either couldn't be seen by TWRP or said that it was read only so I couldn't copy the zip there. Is this just a mismatch between the file system structure of Marshmallow since the SD card was incorporated as internal storage meaning that TWRP can't see it? Or was it a file system permissions bug in the build I was attempting to replace? In the end I had to change my SD card back to portable to give myself a location that TWRP could see it and the update installed fine.

sharkyblunt said:
A pretty damn good build. I'm getting a couple of issues, I'm happy to logcat the first one if it's new to you?
1) I'm getting force close from the Facebook and Facebook Messenger apps. I can't get past the login screen before it freezes and force closes the app.
2) The first time I did an image update using the 11/11/2015 build image I could download the zip to the Downloads directory, but I couldn't find any folder to place it in that could be seen by TWRP. Each folder I tried either couldn't be seen by TWRP or said that it was read only so I couldn't copy the zip there. Is this just a mismatch between the file system structure of Marshmallow since the SD card was incorporated as internal storage meaning that TWRP can't see it? Or was it a file system permissions bug in the build I was attempting to replace? In the end I had to change my SD card back to portable to give myself a location that TWRP could see it and the update installed fine.
Click to expand...
Click to collapse
*2) You can copy your flash-zip files to an internel 2GIG partition while you are in TWRP and connect to USB - This partition is visible(as sdcard0) & RW-mounted for TWRP and for MTP on PC ... No need to change the (formatted as internal storage)sdcard!

I don't seem to be able to install SuperSU over the CM built in one. Flashing 2.46 and 2.52 via TWRP 2.8.7.0 gives a continual boot logo. Built in one doesn't seem to be fast enough for Llama. Any ideas? Thanks.

*delete

Will this eventually become a nightly and a update ota for 5.1 thea? and will the 5.1 86 gapps be ok or will we need to flash the rom with a new updated gapps? and then continue on as a nightly?

softsorter said:
Will this eventually become a nightly and a update ota for 5.1 thea? and will the 5.1 86 gapps be ok or will we need to flash the rom with a new updated gapps? and then continue on as a nightly?
Click to expand...
Click to collapse
You definitely need to make a full wipe. In the end it is a complete new os. You should also use the 6.0 gapps to not run into any problems caused by the new permission system. After you installed your first 6.0 version of this rom, you can dirty flash afterwards. There might be nightlys as soon as it is flagged as one. Before that you will have to pick up the new versions from here.

Got my XT1077 today and tried this. Can't do anything cellular related on CDMA network - calls stay at "dialing", hanging up takes forever, no cellular network... Clean install. Tried changing preferred network mode, no dice.
CM12.1 meanwhile is fine out of the box. I don't know if the RIL libs from CM12.1 can be used directly on CM13, but that's a possible fix.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

Hope this one will become an official build - really would like to see it here. Thank you very much for your effort! Will try it soon.

From now after flashing 20151121 build you will have to remove /data/data/com.android.providers.telephony/databases/telephony.db file due to db scheme updates. Otherwise com.android.phone crash will happen.
You can use TWRP file manager to do it.

I have this 'remount rw /system' issue in latest [ROM][UNOFFICIAL][THEA][6.0] Cyanogenmod 13.0 [UNIFIED] too!
bitstra said:
thnx for the update! & dpichanger works now too!
is it only me(?) - or anyone ( or @RolanDroid ) can confirm this: can't mount /system r/w
Code:
[email protected]:/ $ su
1|[email protected]:/ # mount -o remount,rw /system
mount: '/dev/block/platform/msm_sdcc.1/by-name/system'->'/system': Permission denied
1|[email protected]:/ #
- so also the dpi-changer in ->settings -> display can't set changed dpi-value (in /system/build.prop)!
Edit 1:
shoudn't be there the device name in prompt
Code:
[email protected][COLOR="red"]:/[/COLOR] $
1|[email protected][COLOR="Red"]:/[/COLOR] #
like this
Code:
[email protected]:[COLOR="Red"]thea[/COLOR]/ $
1|[email protected]:[COLOR="Red"]thea[/COLOR]/ #
Is all this sepolicy - related ?
wired!
Click to expand...
Click to collapse
solved the remount rw /system - issue!
1.) copied blockdev binary to /system/xbin with twrp filemanager, while was in twrp.
( I've grabbed 'blockdev' binary from busybox binaries on my nexus 7!)
& chmod 0755 /system/xbin/blockdev
2.) rebooted device
3.) after reboot via ./adb shell
Code:
# su
# busybox blockdev --setrw /dev/block/platform/msm_sdcc.1/by-name/system
# mount -o remount,rw /system
this solved my problem!
Root Explorer can remount rw /system now too!
So somehow my device '/dev/block/platform/msm_sdcc.1' was set to readonly ?!
Edit:
after reboot I have to do Step 3.) again - so it seems, that somewhere in init the block-device will be set to readonly!
So @LuK1337 - Please have a look into/solve this!
---------- Post added at 11:56 PM ---------- Previous post was at 11:01 PM ----------
Will make a flashable zip for this fix tomorrow - if anyone is interested in this PM me...

Oh my god I need this. Once I've got my phone in a bootable state (cycling through various degrees of brick right now) this is going straight on. :laugh:
You say some CM features are broken. I'm on a CM12.1 nightly at the moment, which is perfectly stable for a daily driver and a great ROM. Is this stable enough to use as my primary (and only) phone? I don't mind a few bugs here and there, but nothing toooooo crippling. Texts, calls and a fair amount of apps is what I'm looking for. Should I leave it a few weeks?
However, it is BRILLIANT to see proper bleeding-edge development for a device that was fairly barren for so long. Thanks to all the great devs out there!

Jackdafish said:
Oh my god I need this...
...Is this stable enough to use as my primary (and only) phone? I don't mind a few bugs here and there, but nothing toooooo crippling. Texts, calls and a fair amount of apps is what I'm looking for. ...
Click to expand...
Click to collapse
Though, if this ROM is in alpha state - I'm using it as daily driver on my device since 1st time released/up.
LTE/calls/messaging/SMS/android wear with smartwatch connected - alls is working out of the box!:good:

Yes - in /data/local/RootToolsMounts I can see, that /dev/block/platform/msm_sdcc.1/by-name/system is mounted RO at boot:
RootToolsMounts:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
So, cyanogenmod doesn't want let us change stuff in /system/media i.e.? WHY? (more restrictive than AOSP)

bitstra said:
Though, if this ROM is in alpha state - I'm using it as daily driver on my device since 1st time released/up.
LTE/calls/messaging/SMS/android wear with smartwatch connected - alls is working out of the box!:good:
Click to expand...
Click to collapse
Fantastic. I'll stick this on at some point today. Anyone tried Xposed? Wear Messenger, Eggster and No Lock Home are calling for me...

some guys are interested in make the /system folder rw...
(they PMed me)
So (as a workaround ) here is a flashable zip file that extratcs/copies
2 binary(busybox) files to /system/xbin
(cat-binary + blockdev-binary)
&
1 scriptfile (z_mount_blockdev_msmsdcc1_rw.sh) to /data/local.
The scriptfile you have to run after each reboot manually!
After this you can mount /system to RW (i.e. with root explorer or via ab shell).
Trying to make the script running via int failed here until now!
Keep in mind, that a rw /system is a security-leak!!! - So, as always you use it at your own risk, and you should remount the /system RO, after you've done your changes to file system!
after flashing the zip file + reboot:
make /system RW via adb shell:
Code:
mount -o remount,rw /system
make /system RO via adb shell:
Code:
mount -o remount,ro /system
or you can toggle this with root explorer...
you can download the flashable rw_mount_blockdev_msm_sdcc1_fix.zip here...
BTW: the cause for restricted RO /system lies in the fstab.qcom - where the system-partition will be mounted readonly!
So the better solution would be a custom kernel with a modified fstab!

I just want to say this ROM is awesome, it's very stable, fast and almost lag free on my XT1068 (using the latest 23/11 build). I was a little skeptical at first with how new it is, but for me, it's actually as stable as the official CM12.1 I came from, but not yet as fully featured, so great work so far! Using as my daily driver .
What was almost a deal breaker for me was the inability to mount /system as rw, but @bitstra's post helped a lot The ROM comes with busybox, so you can skip his first 2 steps. This is what I do:
Install a root file explorer that allows you to execute bash scripts as root, I use Root Browser ( https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en ).
Create a new .sh file somewhere easily to find (I called it "mount_system.sh") and copy and paste this into it:
Code:
#! /bin/bash
busybox blockdev --setrw /dev/block/platform/msm_sdcc.1/by-name/system
mount -o remount,rw /system
You can now run the script from Root Browser whenever you need to modify /system, just make sure the "Execute script as root" box is checked (it is by default) and you're good to go .

Related

[OFFICIAL] CyanogenMod 12 - Tilapia [ext4][f2fs]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We will not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our instructions word by word
are unfriendly
WIKI
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Tilapia_Info
INSTRUCTIONS
First time installing CyanogenMod 12.0 to your Nexus 7 or coming from another ROM:
Read the official Wiki page
Unlock your bootloader if you haven't done so already
Flash a custom recovery via Fastboot
Push GApps and the CM 12.0 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Reboot (be patient, "optimizing apps" takes a while)
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 12.0:
Push the new CM 12.0 zip to your SD card
Boot into Recovery
Flash the CM 12.0 zip from SD card
Optionally flash the most recent GApps for Lollipop if you encounter problems
Reboot (be patient, "optimizing apps" takes a while)
Upgrading from CyanogenMod 11.0:
Read the last paragraphs from http://www.cyanogenmod.org/blog/the-l-is-for-lollipop
DO A BACKUP
Push GApps and CM 12.0 ZIP to your SDCard
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Reboot (be patient, "optimizing apps" takes a while)
DOWNLOADS
Official CM 12.0 builds: http://download.cyanogenmod.org/?device=tilapia
Google Apps: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Recovery (SR) : http://puu.sh/ftbeN.img (md5: 18c7841b395e5f6f04718efd65123bc0)
BUGS
Report bugs for nightly builds at https://jira.cyanogenmod.org/browse/NIGHTLIES. Please keep in mind that bugs are expected on these builds. If you want something stable, choose the Snapshot branch.
Tilapia specific features
CMHW: Adaptative Blacklight (Nvidia SmartDimmer)
F2FS support (you can use both ext4 or f2fs, no need of patches or custom kernels)
SMS and MMS support
Tethering
MiraCast
Convert to f2fs for cm
It will wipe your data! No need of custom kernels or patches
Download the lastest twrp here
Sideload it via fastboot boot recovery.img
Go to wipe > data > Repair or Change File System > f2fs
Go to wipe > cache > Repair or Change File System > f2fs
Reboot and enjoy
FAQ
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all do not flash any supersu/superuser/superman zip package to get root. Go to Settings>Developement Settings>Root acces > Apps Only
How do I update from nightly to snapshot and vice versa?
You must download the update manually, wipe data and flash the zip file
Can i send messages with the sim?
Yes you can send SMS
Can i use my connection to create an hotspot?
Yes you can
Are these gapps <insert random gapps package here> working with cm12?
Use the suggested package
Why today I got no nightly?
There were a build error or it means there's something wrong with the rom and I've choosen to stop nightlies until the problem gets fixed
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 12.0, ROM for the Nexus 7
Contributors
linuxxxx
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Version Information
Status: Nightly
Created 2015-02-03
Last Updated 2015-05-16

F2Fs Support
Information
Builds now have experimental support for F2FS for /data and /cache. A compatible recovery is requiried.
WARNING
The F2FS version used by CM is newer than the one used by existing ROMs, recoveries and custom kernels. Features like inline_dentry and inline_data have been enabled to save disk space and improve the performance. Those features are not available on older kernels and this can cause corruption and data loss if you switch back! Just rebooting into a unsupported recovery or any other f2fs kernel can be enough to corrupt your userdata partition. Always make a backup when you switch ROMs!
F2fs is NOT supported on /system and it will never be!
Convert to cm's f2fs from any other fs/rom
It will wipe your userdata!
If you're already on f2fs for any reason, flash a factory image to revert to stock partitions (DO NOT USE ANY OTHER WAY TO REVERT TO EXT4)
Download the this recovery
Sideload it via fastboot boot recovery.img
Go to wipe > data > Repair or Change File System > f2fs
Go to wipe > cache > Repair or Change File System > f2fs
Reboot and enjoy

FAQ
FAQ
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all do not flash any supersu/superuser/superman zip package to get root. Go to Settings>Developement Settings>Root acces > Apps Only
How do I update from nightly to snapshot and vice versa?
You must download the update manually, wipe data and flash the zip file
I switched to f2fs and I booted recovery/f2fs-kernel device, now it doesn't boot anymore, what can I do?
Read the next post about f2fs
Can i send messages with the sim?
Yes you can send SMS and MMS
Can i use my connection to create an hotspot?
Yes you can with usb and wifi tethering
Are these gapps <insert random gapps package here> working with cm12.x?
Use the suggested package
Why today I got no nightly?
There were a build error or it means there's something really wrong with the rom and I've choosen to stop nightlies until the problem gets fixed

Finally! Yehuuu! Thank you very much for so operative work. Waiting for download. Can't wait to test it!
Sent from my Nexus 7 using XDA Free mobile app

dinozaur516 said:
Finally! Yehuuu! Thank you very much for so operative work. Waiting for download. Can't wait to test it!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Nightlies should start tomorrow

linuxxxx said:
Nightlies should start tomorrow
Click to expand...
Click to collapse
Ooops!))) anyway, i am waiting for tomorrow
Sent from my Nexus 7 using XDA Free mobile app

So... They should appear sometime tonight?

cmstlist said:
So... They should appear sometime tonight?
Click to expand...
Click to collapse
http://jenkins.cyanogenmod.com/job/android/

yay!!! finally!!!
been waiting so long for this. time to download and flash

b4b4.4l1 said:
yay!!! finally!!!
been waiting so long for this. time to download and flash
Click to expand...
Click to collapse
Let me warn you: some grouper users with ext4 had problems booting on the today build, I haven't test it yet on tilapia (with ext4), but I can tell for sure f2fs is working (I have to convert mine back to ext4). Will report later.

well done mate! just a question: for f2fs installation do i need to convert the zip? ...now i'm on slimkat f2fs version...
EDIT: it seems somehow automatic!

linuxxxx said:
Let me warn you: some grouper users with ext4 had problems booting on the today build, I haven't test it yet on tilapia (with ext4), but I can tell for sure f2fs is working (I have to convert mine back to ext4). Will report later.
Click to expand...
Click to collapse
Oh, I see. I've reverted mine back to ext4 when testing out lollipop out of curiosity. Was using f2fs when running cm11 though. I'll test it out first with ext4.
Btw, I've read some comments debating about staying with ext4 or switch to f2fs. Does f2fs really give any benefit over ext4? Sorry for the dumb question which may have been asked too many times before :s

b4b4.4l1 said:
Oh, I see. I've reverted mine back to ext4 when testing out lollipop out of curiosity. Was using f2fs when running cm11 though. I'll test it out first with ext4.
Btw, I've read some comments debating about staying with ext4 or switch to f2fs. Does f2fs really give any benefit over ext4? Sorry for the dumb question which may have been asked too many times before :s
Click to expand...
Click to collapse
Yes, especially on this device. Cm supports f2fs on /cache and /data

linuxxxx said:
Yes, especially on this device. Cm supports f2fs on /cache and /data
Click to expand...
Click to collapse
Thanks for the reply. And I see from the other post here stating that now CM12 fully supports f2fs out of the box, so I guess I'll switch back to f2fs.
Thanks for the answers :highfive:

b4b4.4l1 said:
Thanks for the reply. And I see from the other post here stating that now CM12 fully supports f2fs out of the box, so I guess I'll switch back to f2fs.
Thanks for the answers :highfive:
Click to expand...
Click to collapse
Working on ext4 too. Have fun!

linuxxxx said:
Working on ext4 too. Have fun!
Click to expand...
Click to collapse
Final edit : Ah, finally I found it where to change the partition system
Btw, why restoring app+data with titaniumbackup is not recommended? Since I have several apps and games backed up with titaniumbackup

Trying it now.
First big Lollipop peeve: There is no way to disable mobile data when you are not yet connected to a mobile network. This is irritating because the default APN for my SIM card in all Android installations is wrong and any attempt to connect to that mobile network costs me several dollars per second. So every time I have flashed a new ROM on this tablet I have had to boot it without the SIM, disable mobile data first, then insert the SIM, then boot it up, then fix the APN, then I can finally turn mobile data on.
On Lollipop the mobile data toggle just refuses to show up if the SIM is out or I'm in airplane mode. So it forced me to let it connect on the wrong (expensive!) APN first before I could actually fix any of the settings. Garr.
Also still working out some Gapps issues.

cmstlist said:
Trying it now.
First big Lollipop peeve: There is no way to disable mobile data when you are not yet connected to a mobile network. This is irritating because the default APN for my SIM card in all Android installations is wrong and any attempt to connect to that mobile network costs me several dollars per second. So every time I have flashed a new ROM on this tablet I have had to boot it without the SIM, disable mobile data first, then insert the SIM, then boot it up, then fix the APN, then I can finally turn mobile data on.
On Lollipop the mobile data toggle just refuses to show up if the SIM is out or I'm in airplane mode. So it forced me to let it connect on the wrong (expensive!) APN first before I could actually fix any of the settings. Garr.
Also still working out some Gapps issues.
Click to expand...
Click to collapse
I cant test cuz my sim has no internet connection, I just use it to test ril, but it looks like I can toggle it on off with no problems, try to manage it via adb shell su -c 'svc data disable'
And adb shell su -c 'svc data enable'
Updated op, now you can find SR (Cyanogen Simple Recovery), it's great for cm and it can manage both ext4 and f2fs, but there's no toggle to switch to f2fs or ext4

Ah, dang, I'm still getting error to change /data partition to f2fs. It gives me:
E: Unable to wipe '/data'
E: Unknown MTP message type: 1
E: Error changing file system.
What should I do? Or should I use the old modded TWRP 2.7.0.0 all-f2fs recovery from the thread?
/system and /cache went just fine and switched to f2fs.

b4b4.4l1 said:
Ah, dang, I'm still getting error to change /data partition to f2fs. It gives me:
E: Unable to wipe '/data'
E: Unknown MTP message type: 1
E: Error changing file system.
What should I do? Or should I use the old modded TWRP 2.7.0.0 all-f2fs recovery from the thread?
/system and /cache went just fine and switched to f2fs.
Click to expand...
Click to collapse
See op

[ROM][6.0.1_r10][UNOFFICIAL] CyanogenMod 13.0 [2016-01-23]

Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.

Reserved

Finally!! Great work

Solved : Gapps not able to flash
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work

Great Work!

Uc browser not working......

jayent said:
Uc browser not working......
Click to expand...
Click to collapse
Download UC Browser from here

please help
Hey I am facing problem while flashing thus ROM. Please help please

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe/factory reset

Yash98 said:
wipe/factory reset
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
---------- Post added at 04:59 AM ---------- Previous post was at 04:58 AM ----------
TheStrix said:
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted

Update!
CyanogenMod 13.0 R2 Update:
Download: http://goo.gl/h7CkVJ
Changelog:
AOSP 6.0.1_r10 tag.
January 2016 security patches.
Fix offline charging issue (Screen didn't go completely off while offline charging earlier).
Fix Google+ app installation bug present in previous build.
Increased in-call volume speaker gain (reported by some users).
Updated build fingerprint from YU's latest COS release.
Some Wi-Fi updates.
Fix for external SD Card in CM file manager.
Replaced Toybox with Busybox (This may cause some root apps to crash, but CM now uses Toybox!).
Latest CyanogenMod sources with much new patches..

CyanogenMod 13.0 Jan 23rd update:
Download: https://www.androidfilehost.com/?fid=24385658843824514
Just don't hurry up. Read the whole post for once!
Changelog:
Support for F2FS for /data and /cache
Update audio configs to cope up with CyanogenMod's latest changes in audio HAL.
Switch to qcom libhealthd.msm standard library for offline charging (Also it shows battery % now while offline charge)
Switch to Snap camera
Enable USB MIDI support
RIL and connectivity updates
Update new regenerated blobs from crackling
CyanogenMod updates. (CM API v5, new wallpaper, etc. find out own ) [Many changes are made in CyanogenMod repo everyday, so of course can't list all]
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Damn, that was just copy paste from wikipedia and I just didn't get it! So what is F2FS in our language?
It a better file system than ext4 in terms of performance.
Useful Link: http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
To get a better idea, XDA forum have a dedicated thread highlighting F2FS features and a very detailed comparison between EXT4 (file system we use by default) and F2FS!
Have a look here: http://forum.xda-developers.com/showthread.php?t=2697069
So, I liked F2FS and wanna try it! But, how do I?
First of all, backup your internal SD Card as it will be wiped if you are switching to F2FS.
So, to start with, first you'll need a new recovery. I compiled modified TWRP recovery with F2FS support and some other cool features like pressing power button will now switch device display off, also wiping the partitions should not take much time now as it did earlier! (EXT4 users can use the same recovery. I just made it for my convenience)
1. Download TWRP: https://www.androidfilehost.com/?fid=24385658843824749
2. In recovery, go to 'wipe' -> 'Advanced Wipe'
3. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
4. Here select 'F2FS' and Swipe to Change
5. Repeat step 3 and 4 for 'Cache' by checking only 'Cache' in Wipe menu.
6. Reboot! Enjoy!
I want to get back to EXT4 again from F2FS, how should I?
Again, while you are changing your file system, the partition gets wiped. So do backup your data of Internal SD Card and proceed!
1. In recovery, go to 'wipe' -> 'Advanced Wipe'
2. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
3. Here select 'EXT4' and Swipe to Change
4. Repeat step 2 and 3 for 'Cache' by checking only 'Cache' in Wipe menu.
5. Reboot
PS: Only support for F2FS is added on /data and /cache. It still uses EXT4 by default and is just same as it was in previous builds!

first of all
its an amazing rom
but would absolutely love it if i know how to activate power save mode
and a small request " can you add the theme engine from cyanogen os??????"
i really hate the cm theme engine

hello, why cm13 isn't official because there aren't no bugs?

aminvishwas said:
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Click to expand...
Click to collapse
Can't we use the gap 6.0 Full

problm in 5.0.2 ?
there is problm of wake up while charging that it may not happen while m charging phone sir can u pls tell me to fix this problm it will be appreciated could you help me pls....??

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
bro before flashing the zip file.
do following in TWRP
wipe davlik
wipe data
wipe cache
wipe system
and install the zip file the above error will not appear

reserved

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe data and system and install and that will fix the error and one more thing can you make a system backup with twrp and give me i need this rom but my devices is irulu v3 and i try cm12 but its old now.

[ROM][OFFICIAL][kirin][10] LineageOS 17.1

oh btw you might want to use this TWRP for flashing my builds.

LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
I didn't expect you here mr Luk. I'm gonna test it when I will be at home. I'm glad that Kirin got such a developer

Problem Resolved.
Problem Resolved.

AlexDaBoii said:
Hello! So I tried to install a custom rom called Lineage OS, version 17.1 unofficial for my SOny Xperia 10 through TWRP custom recovery. I then tried installing the GApps and then rebooted the system. Then it came up with a prompt saying that the OS was corrupted and then to factory reset it. I did just that, and then LineageOS booted up just fine. However no Google Apps could be seen. I then tried to boot in to TWRP custom recovery, however it came up with the LineageOS recovery instead. I then tried to flash TWRP and managed to get it up and running, but when I rebnooted the phone, it just brought me in a boot loop.
I tried for hours to fix it and the I finally managed to flash TWRP again, however all of my save files were gone. I then tried to flash the Stock ROM for the Xperia 10 to the "system" folder and then my device powered off. I tried to power it on again and then it came up with a prompt saying "Your device is corrupt. It can't be trusted and will not boot. Powering off in 5 sec.". I got really freaked out at this point and did not know what to do. I know that I am an idiot for doing this, but if there is any fix at all for this that anybody can tell me, then I would be very thankful.
Click to expand...
Click to collapse
If you join irc I may be able to help you:
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev

Flawless on I3123 so far. Really appreciate the work on this device.

Has somebody tried this on I3113?
Are all components working fine?

xXqepXx said:
Has somebody tried this on I3113?
Are all components working fine?
Click to expand...
Click to collapse
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.

LuK1337 said:
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.
Click to expand...
Click to collapse
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!

thesandroid said:
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!
Click to expand...
Click to collapse
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).

What gapps do you recommend? I have an i3113 and after i flashed opengapps, i always get this weird "Android setup isn't responding" "System UI Keeps crashing" thing. What can i do?

LuK1337 said:
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).
Click to expand...
Click to collapse
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.

thesandroid said:
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.
Click to expand...
Click to collapse
Yeah that doesn't sound fun. Not going to bother.
On a sidenote, next build will fix Netflix Widevine L1.

Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.

zzz00072 said:
Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.
Click to expand...
Click to collapse
You build it exactly the same you'd be building an official device.

Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
LuK1337 said:
You build it exactly the same you'd be building an official device.
Click to expand...
Click to collapse

After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
zzz00072 said:
Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse

zzz00072 said:
After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
Click to expand...
Click to collapse
hint: themuppets.

Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
LuK1337 said:
hint: themuppets.
Click to expand...
Click to collapse

zzz00072 said:
Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
Click to expand...
Click to collapse
Yikes, you're doing so much stupid stuff...
Msg me on irc if you want it done anytime soon.

[ROM][Android 10][Android 11]Meizu E3 LineageOS 17.1/18.1 ROM Porting (20210418)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there,
I prepared an alpha version of LineageOS 17.1/18.1 for Meizu E3 for your taste about it. Now it so more useable as dev-phone for outdoor YouTube viewing. Do play with it your own risk. I am not responsible any liability, nor any technical support too. So please think twice before taking action. AND be safe to backup ALL partitions before and action taken.
You can visit another thread of Meizu E3 unlock bootloader tutorial from your author, to unlock Meizu E3 without any external tool.
Instruction:
(0) to make it align with latest flyme v8000 fw, update system to v8000 is highly recommended. (20200926)
(1) get the phone unlocked bootloader as above mentioned.
(2)download below mentioned fw (boot.img.signed, system.img, vendor.img, recovery.img) in to a folder like "E3_LOS17.1", unzip and get "vendor_image.emmc.win", "system_image.emmc.win" and "boot.img.signed", rename them as boot.img, system.img, recovery.img and vendor.img
(3)hold power+vol_down and do "fastboot.exe boot recovery.img"
(4)in twrp, backup all partition to /sdcard, aka, "/sdcard/system.img", "/sdcard/persist.img"
(5)in host PC backup from phone and upload all above downloaded and unzip rom.img to phone, procedure like open cmd.exe, "mkdir E3", "cd E3/", "adb.exe pull /sdcard .", "adb.exe push E3_LOS17.1 /sdcard"
(6) twrp install, choose install img, select /sdcard/E3_LOS17.1/system.img, system partition, go
(7) twrp install, choose install img, select /sdcard/E3_LOS17.1/vendor.img, vendor partition, go
(8) twrp wipe, choose data partition, go (your data partition got WIPED, all data are LOST)
(9) wait above finish, go back to PC terminal, cmd.exe, issue "adb.exe reboot-bootloader", then "fastboot.exe boot boot.img"
(10) wait for LOS17.1 boots up
optional steps
(2a) you can choose to phh's quack build instead of jasmine_sprout system image as well. download it from phh's github release channel, unpack the zip, use simg->img tool to get regenerated system.ext2.img; check with linux "file" util and get
[email protected]:/mnt/jasmine_vendor# file /mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img
/mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img: Linux rev 1.0 ext2 filesystem data, UUID=05050abd-8baa-4dd4-905c-903071f9ac68, volume name "system" (extents) (large files) (huge files)
Click to expand...
Click to collapse
Note:
(1)Please sure to DO backup all the partitions
(2)Please sure DO NOT to flash boot.img to boot partition, every time use fastboot to boot into LOS17.1 thus can easily restore to flyme8 rom
(3)please sure when revert back flyme8, please DO use your own twrp backup to restore all partition is your first choice. Second choise is by flyme8's recovery from recovery partition, or at least the flyme8 recovery downloaded below. DO NOT use TWRP restore the flyme rom directly, and this can avoid many issues; otherwise you are compulsively to reflash flyme once again at least and all your data partition backup become useless; and if you force restore data partition, it wont help, due to internal hw keystore and crypto salt changes. so step (5) "adb.exe pull /sdcard/ ." is essential.
(4)use twrp recovery to restore data partition might not work at all. so once again, backup by using "adb.exe pull /sdcard ." is important. As said, some partition might get changed by bootloader and internal fw, so hw crypto and salt, keystore partition might get changed too after first boot LOS17.1; and you cant backup these partition at twrp screen operation. and even through if you are expert enough, restoring those partitions in adb shell also might not work at all due to same reasoning.
(5)using "adb.exe pull /sdcard ." is important! this is important so as i said 3 times.
(6)backup all partition by "adb shell" if possible. TWRP only list some of usual partition, and some rarely used partition are not listed. Like i suffered from persist partition wiped out and cant restore without a copy. so do a "dd if=/dev/block/bootdevice/by-name/XXX of=/sdcard/XXX" is a good idea.
(7)I had tried my best to make the all mount as "r/o" as possible, but i CANT guarantee all other partition are safe. So best is do as note(6) said.
Release Alpha 13
==================
Latest alpha release on LineageOS 18.1, camera is not working, check below for detail:
Release Alpha 13 · 99degree/android_vendor_meizu_m851q
This release (Alpha 13) is an alpha release that based on brand new Nokia PL2 LineageOS 18.1 release. Detail refer to below: https://lineageos.org/Changelog-25/ This release have an issue about cam...
github.com
Release Beta 2
==================
Latest stable ROM on LineageOS 17.1
Release Beta 2 (20210221) · 99degree/android_vendor_meizu_m851q
This release aimed to get entire system updated to Feb-05 Security bulletin. Changelog: Update to LineageOS Amber 20210214 Known issue: LineageOS clean (wipe data in TWRP) and first time startup wi...
github.com
Older release:
Release note 20210124
==================
Update dts and libmmcamera module. Camera should be alright, actuator is still in progress.
download release 20210126
Release note 20201214
==================
Update to CAF LA.UM.8.2.r2-03400-sdm660.0
Based on LineageOS Nokia PL2 Dragon build 20201208
This is no longer pure CAF due to adreno older fw logic fail.
Selinux enforced now on
Release note 20201011
==================
Update to CAF LA.UM.8.2.r2-02700-sdm660.0
LineageOS Amber 20201011 release, kernel is no longer pure rely on CAF anymore.
It is due to a adreno fw checking logic fail on older fw.
Release note 20200813
==================
Update to CAF LA.UM.8.2.r2-02500-sdm660.0
LineageOS Amber 20200809 release
Release note 20200705
==================
Some sensors are available.
external speaker (TAS2560 SmartAmp) functioning.
Release note 20200701
==================
(1)Special release! Voice-out-loud for social injustice!
(2)Mobile feature enablement
https://github.com/99degree/LineageOS/releases/tag/20200701
Release note 20200613
==================
First version with earphone sound playing. So YouTube is more than possible! This version shifts to official LineageOS.org Yandex Amber build
https://mirrorbits.lineageos.org/full/Amber/20200607/lineage-17.1-20200607-nightly-Amber-signed.zip
Release note 20200303
==================
Workaround the wifi problem, now wifi is working. boot.img.clear is updated.
Release note 20200223
==================
This is a ported version of LineageOS 17.1 based on this thread so you can download the original version of the build over there. In case of preference in phh's treble quack release, it seemed system.img is working well too.
The solo modification in vendor.img included:
(A) fstab.qcom to disable persist partition mount by "r/o", so no longer as "r/w" mode in order to protect it against lost wifi firmware, lost signal, mac address etc.
(B) replace all file lived in /vendor/firmware/* with flyme8's
The modification in system.img:
NIL
Things verified to work:
LCD PANEL
TOUCH PANEL
BLUETOOTH
USB
CHARGING
WIFI
vibration
earphone w/button
mobile feature
speaker and incoming ringing
GNSS
sensors (luminous, proximate, compass, magnet)
selinux-enforced
front camera
back imx362 camera
back imx350 camera(not tested)
Things not working:
those not listed above is considered not working
ROM download:
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210418 for LOS18.1
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210221 for beta 2
release 20210126
release 20201214
https://github.com/99degree/LineageOS/releases/tag/20201011
https://github.com/99degree/LineageOS/releases/tag/20200813 for boot.img and recovery.img
https://github.com/99degree/LineageOS/releases/tag/20200705 system and vendor image
https://github.com/99degree/LineageOS/releases/tag/20200701
https://github.com/99degree/LineageOS/releases/tag/20200613
https://github.com/99degree/LineageOS/releases/tag/20200223
https://github.com/99degree/LineageOS/releases/tag/20200303 for boot.img.clear
Repositories:
https://github.com/99degree/
kernel https://github.com/99degree/android_kernel_meizu_m851q
vendor & release https://github.com/99degree/android_vendor_meizu_m851q
So if you wanted to cook it yourself, please find necessary file with you. All needed files are hosted either in GitHub and LineageOS official Amber/PL2 build),
Please consider to show your support by donation or even YouTube clicks. Last and most importantly, happy ROM flashing and stay away from corona-virus outbreak!
Regards,
99degree

Can you public source code of kernel with device driver? Thank mate

thinhx2 said:
Can you public source code of kernel with device driver? Thank mate
Click to expand...
Click to collapse
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.

99degree said:
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
Click to expand...
Click to collapse
Nice sir

99degree said:
...
kernel https://github.com/99degree/android_kernel_meizu_m851q
...
Regards,
99degree
Click to expand...
Click to collapse
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.

Spencer_D said:
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Click to expand...
Click to collapse
No! Not the way you through. I managed to clone kernel from CAF and search for hardware info. By app "device info hw", google and find some public available driver (basically touch driver and sound driver), add them to CAF tree then analysis the device tree dtb->dts difference. Move them to new dtsi and compile it with kernel as a whole. Then make use of LineageOS Yandex Amber ROM, modify and make it boots into LineageOS, that's it.
So best wish your development on SantinK1.

[ROM] [TB3-710F] [BETA] [UNOFFICIAL] [7.1.2] LineageOS 14.1 for Lenovo Tab3 7 Essential Wi-Fi

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aptivi presents...
LineageOS 14.1 for Lenovo Tab3 7 Essential TB3-710F
Disclaimer
----------
Code:
#include <std_disclaimer.h>
/*
*
* I'm 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.
*
*/
This ROM is currently in alpha state and bugs might exist without us spotting them. Please use the ROM with caution.
Description
-----------
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 restores 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.
Downloads
---------
* For ROM:
- Link to all the LineageOS builds made by us is found on MEGA!
- Link to download GApps
* For recovery:
- Link to download Tzul's TWRP
- Link to download SP Flash Tool
Installation
------------
First, make sure that your TB3-710F tablet contains the TWRP recovery made by Tzul to be able to install LineageOS 14.1 into it. If you want to get the recovery, you can follow this guide on YouTube to install the recovery or you can follow the recovery part of this thread. After installing the recovery, follow the steps:
1. Download the latest build of LineageOS 14.1 in the MEGA folder listed in the Downloads section. It's found in the LineageOS > TB3-710F folder.
2. Download the GApps package
3. Place the downloaded files to your tablet. We recommend storing them on your external SD card.
4. Power off your Lenovo TB3-710F.
5. Turn the tablet on to recovery mode by holding the POWER + VOLUME UP + VOLUME DOWN buttons simultaneously until you see the TeamWin logo.
6. Backup your system, data, boot, and recovery partitions. TWRP provides you an option to store the backup on your external SD card.
7. Now, wipe your system, data, cache, and dalvik cache partitions by Wipe > Advanced Wipe.
>>> If you're upgrading LineageOS 14.1 to the newer build, don't wipe the data partition. The first time you reboot into the newer build, the boot time will be longer. It should take no more than 15 minutes. If any problems occur, wipe your data partition.
8. Once the wipe is done, go to Install and navigate to the folder that contains the LineageOS zip file. It should say "lineage-14.1-xxxxxxxx-UNOFFICIAL-TB3710F.zip". Click on the ZIP file and install it. Beware that it may take a long time.
9. Now, repeat the previous step, but this time, selecting the GApps ZIP file. Make sure the version you're installing is GApps for Android 7.1 ARM Pico.
10. Once you're done, wipe the cache and dalvik cache to make sure that no stale cache is left.
11. Go to Reboot > System to boot to your LineageOS installation.
Known issues
------------
This ROM is not perfect and could have stability issues.
* Build March 11th, 2023 -> March 23rd, 2023
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
* Build March 8th, 2023
- Camera not working with the green screen
- E-mail app not working with force closes
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
* Build March 5th, 2023
- Camera not working with the green screen
- E-mail app not working with force closes
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
- Microphone may not work
- WiFi listing may display "NVRAM WARNING = ERR 0x10"
Working features
----------------
* WiFi and Bluetooth
* Sound and Headphones
* Microphone [Build March 8th onwards]
* Touch
* SD card support
* Camera
* ...and more
Changes
-------
* lineage-14.1-20230323-UNOFFICIAL-TB3710F.zip [Beta]
- Fixed Internal storage issues with sdcardfs by reverting to FUSE
* lineage-14.1-20230311-UNOFFICIAL-TB3710F.zip [Beta]
- Fixed camera not working
* lineage-14.1-20230310-UNOFFICIAL-TB3710F.zip [Internal]
- Fixed E-mail force closes
* lineage-14.1-20230308-UNOFFICIAL-TB3710F.zip [Alpha]
- Fixed microphone not working
- Suppressed the "NVRAM WARNING = ERR 0x10" warning message
- Imported some patches from the device tree
* lineage-14.1-20230305-UNOFFICIAL-TB3710F.zip [Alpha]
- Fixed Android failing to boot because of missing libstlport.so
- Initial public alpha release
* lineage-14.1-20230304-UNOFFICIAL-TB3710F.zip [Internal]
- Initial internal release
Reporting issues
----------------
* DO NOT report bugs if you're running a custom kernel or you installed Xposed.
* Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
* If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
* If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits
-------
* Android AOSP Team: for the Android operating system source code
* LineageOS Team: for the ROM source code
* andrew264: for his kernel, device, and vendor trees for TB3-710F
* We maintain our own forks for his trees that shouldn't have been abandoned. Links below:
- Kernel: [Original] [Fork]
- Device: [Original] [Fork]
- Vendor: [Original] [Fork]
* @Tzul: for his TWRP build for TB3-710F
Screenshots
-----------
Screenshots are found in the bottom of this post as attachments.

What is your: TB3-710F Tablet
LineageOS version: 14.1
LineageOS Download url: from this post
Gapps version: from the link of the post
Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: no
other modifications: no
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: when i want to move a file from SDCard to internal storage, doesnt work, or when i want to move a file in the internal storage, doesnt work also, some apps have trouble writing some files on internal storage, they have fully permitions for writing and modifiying

IsaacCastle said:
when i want to move a file from SDCard to internal storage, doesnt work, or when i want to move a file in the internal storage, doesnt work also, some apps have trouble writing some files on internal storage, they have fully permitions for writing and modifiying
Click to expand...
Click to collapse
Thanks for reporting this issue!
We're aware of this issue and will investigate it. Once investigation is done, the fix will be released shortly.
By the way, we tested creating and writing a file on the internal storage using QuickEdit, and received this error on Logcat:
Code:
java.io.FileNotFoundException: /storage/emulated/0/untitled.txt (Invalid argument)

@IsaacCastle Good news!
We found a fix for your problem with the internal storage. It involves disabling sdcardfs and restarting your tablet. This is caused by incompatibility with sdcardfs on the TB3-710F.
1. Open Settings
2. Tap About and tap on the Build number 7 times to unlock developer settings
3. Go to Developer options and enable Android debugging
4. Enable Android debugging and set "Root access" to "Apps and ADB"
5. Connect your tablet to your PC (assuming that it's Windows) and download the Platform tools from here: https://developer.android.com/studio/releases/platform-tools
6. Unzip the platform tools ZIP file (we recommend unzipping to C:\platform-tools for easier access)
7. Open the command prompt to the platform tools directory.
- 7a. Open the command prompt
- 7b. Change the current directory to the platform tools folder (cd C:\platform-tools)
8. Execute the following commands:
Code:
adb.exe devices
adb.exe shell
- We require running adb.exe devices before the shell to verify that you can authorize your tablet to your computer.
9. Re-mount the system, because we're going to edit build.prop
Code:
su
mount -o rw,remount /system
10. IMPORTANT! Back the build.prop file up in case something is wrong
Code:
cp /system/build.prop /system/build.prop.bkp
11. Now, use the sed command to replace the ro.sys.sdcardfs=true line with ro.sys.sdcardfs=false:
Code:
sed -i 's/ro.sys.sdcardfs=true/ro.sys.sdcardfs=false/g' /system/build.prop
12. Restore the system to read only
Code:
mount -o ro,remount /system
13. Exit the ADB shell and unplug your tablet from your computer
14. Restart your tablet
15. Try to write a file to the internal storage now. It should work.
If it still didn't work, post your dmesg and logcat.
Meanwhile, we'll upstream the fix to the second beta release!
Again, thanks for reporting this to us!

All right! Thank you very much for your attention! I will fix the problem as you said, i will be waiting for the beta release, again thank you very much for your attention!

I will download the other beta release with that fix, i will be analising the beta in this (Really old) tablet, i need to say something: the performace is really really awesome, it is much better even from the stock rom! your work is really apreciated, and again thank you very much for your attention!

You're welcome, @IsaacCastle! Enjoy this ROM!

Hello! I've used this ROM and it's pretty good! The performance is good and i fell it really stable, but i've found some problems:
YouTube vídeos get lagged with 720P Quality, in 480P is ok, but looks píxeled, the camera is not working (I don't even use the camera but is a detail) and that's all! It would be great is you can optimize the operating system lowering the RAM usage, and that would be all! I wanna thank you for your hard work of this ROM for reviving my old tablet, again, thank you very much.

What is your--
LineageOS version:14
LineageOS Download url: mentioned above
Gapps version:mentioned above
Did you--
wipe:yes
restore with titanium backup:no
reboot after having the issue:yes
Are you using--
a task killer:no
a non-stock kernel:no
other modifications:no
Provide any additional information (observations)
Hello, i just came across this rom and i tried installing it the exact way mentioned, andit just doesnt boot whatever i do, i tried about 4-5 times now, i didnt restore anything, just flashed rom and gapps mentioned above, it still doesnt boot.

Database Info

welcome