CM13.0 (Marshmallow) unofficial builds for the TATE
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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 our Gerrit Code Review.
download:
new: https://www.mediafire.com/folder/u7sb7p10ik7v0/tate
old:https://www.mediafire.com/folder/5a97vbv93k24n/tate
old:https://www.mediafire.com/folder/w9nh7oyabwvww/tate
backup before flash, gapps need for upgrade, don`t flash SuperSU
deep sleep fixed
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
bluetooth lte-version fix: https://forum.xda-developers.com/ki...elp/kindle-fire-hd-8-9-bluetooth-rom-t3315904
Great, now it's time to bring TWRP 3.0.0.0 for better results.
alexander_32 said:
Great, now it's time to bring TWRP 3.0.0.0 for better results.
Click to expand...
Click to collapse
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
build 20160215 (backup before flash, gaaps need for upgrade): http://www.mediafire.com/download/pj2994j9p358tit/cm-13.0-20160214-UNOFFICIAL-tate.zip
xWolf13 said:
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
Click to expand...
Click to collapse
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
alexander_32 said:
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
Click to expand...
Click to collapse
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you very much :good::good::good:
@transi1 Great rom! Very fluid. Only issue is the lack of deepsleep. Do you have an idea what might be causing it?
Also I flashed the ROM with Twerp 2.7.x.x so Twerp 3.0 is not required (but if you guys build it,i'll still take it )
Thanks for bringing CM13!
hope this rom to be official
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Screenshots please??
transi1 said:
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Click to expand...
Click to collapse
My battery thanks you. From what I can tell, everything that was working in cm12.1 also works in cm13. Along with very aggressive memory killer recommended from OP, I'm also using max cpu freq 1500MHz with performance governor and deadline scheduler with 512kB read-ahead in kernel adiutor and the performance is good. In cm12 I remember several crashes with the same cpu oc but for now it seems stable.
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
LOL! Definitely don't flash supersu! Just got my kindle back up from soft bricking it that way.
Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Click to expand...
Click to collapse
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
r3t3ch said:
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
Click to expand...
Click to collapse
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Sent from my Amazon Tate using Tapatalk
Jrhoop said:
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Click to expand...
Click to collapse
If you can enter fastboot you have nothing to fear. TWRP is the only recovery that is consistently updated and is highly recommended over philz/cwm. Download TWRP 2.8.7.0 and extract the img from the zip.
I've never been a fan of flashing tools from within android. It's much simpler to just go into fastboot and use:
Code:
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Maromi said:
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Click to expand...
Click to collapse
Hey what rom are you running on the KFHD?
Related
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. WIPE (wipe data/factor reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Latest version: 7.2.0-bravo - 18/03/2012
Download: CyanogenMod Mirror Network
Also available for download via ROM Manager
Google Addon:
Download: http://goo-inside.me/google-apps/
CM7 HBOOT r2 by Alpharev | xda thread
Change partition table size 145/5/287 (system/cache/size)
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7r2.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD:
Simple2Ext (Easy with a GUI)
CM7 Legacy App2SD Addon Script (For Advanced user, Command Line)
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
reserved for future use
Thank you!
Cant wait to see first CM9 Nightlies (yes i know it will be difficult to do because of HTC and QCOM but i still have hope)
Gr8!I'm downloading now,i know it takes too much to have such another rc version,thank you devs!
Sent from my HTC Desire using XDA
Download is very very slowly... :-(
Inviato dal mio HTC Desire usando Tapatalk
Quit complaining about the downloadspeed. Do you have any idea how many of us are probably downloading this rom right now?
via xda app
i try all rom,not all but many,and today is my first cyanogenmod
thanks
Jordywild said:
Download is very very slowly... :-(
Click to expand...
Click to collapse
http://www.cyanogenmod.com/blog
7.2RC1 is out for "only" 70 devices
Its probably placebo but this release candidate seems a lot smoother than the last nightlies. So issues so far. :thumbup:
via xda app
Im having problems installing market applications like:
SMS backup and restore
Call logs backup and restore
and other applications
Just in case you have successfully installed one of the following please post it. Maybe its my installer or something.
Thanks!
SMS backup and restore is fine. I just had my messages restored. Same with the other apps. I would suggest a clean install if you are having trouble.
via xda app
Thanks for everyones hard work on this. If upgrading from 7.1 can someone confirm if I need to do a wipe?
Thanks,
Womble
Update from CM 7.1.0 work? Because i get bootloop...
19blacktiger77 said:
Update from CM 7.1.0 work? Because i get bootloop...
Click to expand...
Click to collapse
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Jordywild said:
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Click to expand...
Click to collapse
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
frankoid said:
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
Click to expand...
Click to collapse
Full wipe?
I've got "only" 90 app installed.
Ok: I need a backup with Titanium.
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
GPS does not works with this version... back to 7.1
Home button does not work... buggy...
Back to 7.1!
Jordywild said:
Have you got EXT4 partition?
Click to expand...
Click to collapse
Yes!
stankyou said:
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
Click to expand...
Click to collapse
carval2k said:
GPS does not works with this version... back to 7.1
Click to expand...
Click to collapse
I will stay on 7.1 too...
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), 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. 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.
IMPORTANT!
Click to expand...
Click to collapse
* PLEASE READ THE ENTIRE TOPIC BEFORE FLASHING THE ROM.
Bug Reports
Click to expand...
Click to collapse
* REPORT BUGS IN THE TOPIC ONLY.
* DON'T SEND ME PM MESSAGES ABOUT BUGS OR FEATURE REQUESTS.
* ONLY REPORT THE BUGS IN CM11. I DON'T PROVIDE SUPPORT FOR OTHER ROMS. POST IN THEIR RESPECTIVE THREADS.
* IF YOU ARE ON A CUSTOM KERNEL, FIRST CHECK WITH THE STOCK KERNEL AND THEN REPORT THE BUG.
Downloads
Click to expand...
Click to collapse
ROM Downloads
Google Apps
Download the Pico Modular Package to save space on the system partition.
Changelog
Click to expand...
Click to collapse
20160705
Android Security patch level - 1st June 2016
20160421
Android Security patch level - 1st April 2016
Improved multitasking ability
Upstream Changes.
20150713
Upstream changes.
20141008
Upstream changes.
20140902
Updated to 4.4.4
Pull in changes from NamelessROM
Improved Video Recording
Fixed media playback issues.
20140513
Upstream Changes
20140507
Upstream changes.
20140423
Fixed front camera recording issues.
Upstream Changes.
20140324
Optimized CPU speed when screen off
Bluetooth HID support
Upstream updates.
20140318
Fixed issues with Audio and Media Playback
Upstream changes.
20140309
Upstream changes.
20140222
Upstream changes.
20140209
Bought back battery changes from 20140120 build
Fixed Compass
Fixed media playback.
Upstream changes.
20140128
Upstream changes.
20140124
Reverted battery driver changes.
Upstream changes.
20140120
Fixed Battery Drain
Fixed WiFI Tethering
Installation Instructions
Click to expand...
Click to collapse
IMPORTANT! READ BEFORE FLASHING!
1. If you flash this ROM from Stock ROM, it will wipe data due to different partitioning. The device would reboot while flashing and resume again.
2. Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
3. While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
4. Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
5. Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Stock ROM
1. Flash CWM Compatible Kernel (CF ROOT)
2. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
Any other AOSP ROM (CM7/MIUI/CM9)
1. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
Upgrading from previous versions of CM10
1. Reboot to Recovery.
2. Select the ROM zip from your SD Card and flash.
3. Flash Google Apps.
4. Reboot
Sources
Click to expand...
Click to collapse
https://github.com/dhiru1602
Credits
Click to expand...
Click to collapse
codeworkx
sconosciuto
Known Issues
Click to expand...
Click to collapse
None
The Google Apps package doesn't include Google Home, Google+, Hangouts and Face Detection.
Yaay Finally,
>testing,
a preview is coming soon
Thank You Master
Thank you master Dhiru!!! Great job!
Thanks i flash it and Report =)
Gesendet mit meinem Mäusekino =)
Hi Dhiru.. Currently on it and its great work... A big thanks to you bro..
I have two questions.
1. How to SWAP SD Card.
2. How to disable Touchpad lights.
Oh God Dhiru you shocked me again!
But oops! I got stuck at the first boot screen. Previous was your CM10.2 A4. Flashed CM11 and gapps without wiping anything. After rebooting it stucked.
Edit: Tried clean flash from DDLF2 but still stucked after CM11A1 flashing.
First look.. Awesome...
Unable to customize UI.. Seems like brightness is little higher even at the minimal level..
So far so good...
Hit Thanks if I have helped you...
Sent from I9003 XDA App
thanx
thanx dhiru for keepig our device alive samsung ditched our phone but thanks to you devs for keeping our device alive :good::good::good::good:
big thanx Dhiru for your amazing work, finally Kitkat arrived for our device, will try it and subscribe this thread...
best regards,
deDante
CF-ROOT
Hi @dhiru1602
please share the CWM or CF-ROOT you use to flash CM rom from stock.
thanks
chongns said:
Hi @dhiru1602
please share the CWM or CF-ROOT you use to flash CM rom from stock.
thanks
Click to expand...
Click to collapse
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
woooow,it's so smooooth.and the free ram is almost 100+MB.:good:
I installed the googlehome. it works fine.but how to make the Statusbar transparent?
nbrian2012 said:
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
Click to expand...
Click to collapse
Different ROM, different RAMdisk
Downloading now...... Thanks dhiru
Will try to give the review once i have tested it
nbrian2012 said:
And to come to think of it, how did you get 240 likes if you don't know which CF-ROOT to use?
Here, tho. Download.
Click to expand...
Click to collapse
By porting "CF-ROOT" for those CF-ROOT which make people phone boot loop .....funny hah...
well, i just want to ensure, our member are using the cwm or cf-root which Dhiru is using so, we can avoid unnecessary incompatibility between our so old cf-root. and also "why i get status 7 ? "
Downloading now...... Thanks dhiru
Will try to give the review once i have tested it
AWESOME. Amazing. Dhiru you're the best, seriously. Thank you for doing this. I hope you can make a stable ROM out of this. Thank you so much.
EDIT: Waited patiently for this... what are the absolute major bugs which effect everyday stuff? Phone calls/texts/app incompability/battery ... anyone who is using the ROM currently, please answer.
#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.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM12.1 Lollipop Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0 and 12.0 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-12.1
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.1 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12.1
cd cm12.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.1/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Unofficial CyanogenMod 12.1 Nightlies, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, Phantom Shadow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-02
Last Updated 2017-01-04
Bugs / Not working stuff
headset mic in call
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
Thanks, Kylon, Mustaavalkosta, Paunb_nl, and Phantom Shadow, for being active in supporting DS's community with up to date development. I am very appreciated your kind contribution. Thank you very much.
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Yeah, I fell asleep before the build finished and I had chance to say the same here that I already said on the ace thread:
First build is now on the mirrors. Expect everything to be broken, be thankful for anything that works. There's no schedule for these nightlies yet as I haven't really had time to think how I'll juggle 3 different versions so they don't start compiling at the same time. New builds will come whenever I feel like making one until things settle down a bit and build schedule is decided.
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Thanks, I got the same thing as you mention plus android keyboard FC. However, it is the first built, just booted up is alright. The rest is leaving for Mustaavalkosta to take care of. If DHD is working, DS should be working as well. Thanks for Mustaavalkosta hard work.
Hi Mustaavalkosta, CM-12.1-20150403-UNOFFICIAL-saga.zip faced the same issues as previous built, Android keyboard FC, not enough space for the system. There should be somethings wrong because the internal storage still has 1.03 GB available as well as my SDCard still has 14 GB available space. However, front camera is working on this built. I am wondering if it is possible to copy files related to camera from this built to CM-12 and which files should it be replaced. I am trying to produce logcat without success. I am sorry about that. Thank you very much for your great effort.
Thanks, Mustaavalkosta, I got the answer by replacing Camera2.apk from this built to CM-12 by installing using root explorer and front camera is now working on my device, CM-12 Rom.
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
No, it is not. Front camera is working fine on CM-12.1. Thanks.
Can I perform update from CM12 to 12.1?
@qd42: Shouldn't be a problem since it's a minor Android update. But since this is in alpha state I'd suggest you wipe.
Same for me: "not enough space", keyboard FC on first boot (works good now in German). Front-camera works flawlessly. I'll be testing more.
Well, I'm tried to make update from CM12 and I don't reccommend to do this to others because of various system errors after boot like "android.process.acore errors".
How can i install this rom ?
I am using TWRP 2.8.5.2 as Recovery
I have swiped evertyhing i could on the phone
When i choose to install this ROM i get the Message: script succeeded result was /system
After flash boot.img, the Cyanogenmod-Logo still dont disappear after 10 Minutes ... (while booting)
€dit: Forget it. After 15 mins the Logo disappeared and the system has booted. But my SIM was not detected ...
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
LuckyLoop said:
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
Click to expand...
Click to collapse
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Mustaavalkosta said:
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Click to expand...
Click to collapse
Thanks MUstaavalkosta. So far, It is working fine. Flashed superSU v.2.48 beta makes it better. Ringtone is good, front camera is good. Just keyboad and google service have stop sign showed up some time. In fact they are still working. Thanks for your kind contribution.
I can't install any apps from the store get an error ’'-504''
Remove Boot animation before flashing as Mustaavalkosta suggested.
Okay,now that ive taken a break from studying,i can post a bug report on this. Accorrding to what ive seen,other than the known,solved ones,there are no other bugs. Much faster than 5.0.1 thats for sure. This is my new daily driver.
Sent from my SM-G900T using XDA Free mobile app
Hey guys, last time I flashed this the opposite side was not able to hear me upon my first call and the call quality was terrible when I returned the call after.
Of course I was in an area with good signal coverage.
Was this solved lately by any chance?
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
vojtah1 said:
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
Click to expand...
Click to collapse
How about without gapps? Works fine here on ace after that commit.
#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.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM13.0 Marshmellow Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0, CM 12.0 and CM 12.1 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-13.0
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
Do not donate to me, but if you insist on donating, I suggest you donate that money to Mustaavalkosta or EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM13.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm13.0
cd cm13.0/
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-13.0/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: My problem is not listed here.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[ROM][UNOFFICIAL] CyanogenMod 13.0 Nightlies OpenDesireProject, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, PhantomShadow
Source Code: https://github.com/OpenDesireProject
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-04
Last Updated 2017-01-04
Bugs (Device specific):
Glitches here and there
Headset Mic in call
SAGAOPT SETUP INSTRUCTIONS (see also Mustaavalkosta dhd post)
Disclaimer: You will lose everything on your sdcard if you follow these instructions so take appropriate steps to secure your data before continuing. Also this will be a "clean flash" from the start due to different partition layout.
Prerequisites:
TWRP for sagaopt by @jrior001
saga cm13 zip
Gapps and addons if you want them. IIRC, there was around 400-500MB space left on new /system partition after flashing base gapps package so there's a bit more room for addons.
If you have already partitioned your sdcard you may want to repartition it to have only single partition because you won't benefit from having separate sd-ext partition with this variant build. I won't write anything about this as I expect you can reverse what you have done yourself.
Installation instructions:
Flash TWRP in fastboot or your current TWRP (Install > Images > etc.)
Reboot to recovery even if you are already in TWRP. You need to reboot to be in newly flashed sagaopt TWRP.
Wipe cache and system under Advanced wipe.
Convert your sdcard to either EXT4 or F2FS under Advanced wipe by choosing data partition > Repair or Change File System > Change File System > EXT4 or F2FS.
(Optional) If you had your old /data partition formatted as F2FS you also need to convert it to EXT4 meaning converting system partition in the sagaopt recovery.
At this point your sdcard is completely empty so you will need to move the ROM zip and any additional zips into sdcard or use adb sideload.
Install cm-13-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps.
Reboot
kylon said:
Bugs (Device specific):
Glitches here and there
Headset Mic in call
Click to expand...
Click to collapse
Thank you very much Kylon for putting up the thread for CM-13. I have already tried 20151203 and 20151204 nightlies with no CM Account and facing problem on flashing either Open GApps or Delta GApps for MM, it is showing Setting Wizard has stop mainly and some time Google play service has stop and System does not response all the time making setting up impossible. Anyway no problem on ROM flashing. Thanks.
It s a known problem on cm13.
You have to delete setup wizard
kylon said:
It s a known problem on cm13.
You have to delete setup wizard
Click to expand...
Click to collapse
Thanks for your prompt reply. I shall do that.
<Reserve>
aakashasaj said:
<Reserve>
Click to expand...
Click to collapse
Hi Kylon,
I am wondering if the keyboard and google play service stop could be solved on CM-13 sagaopt. Thank you very much.
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
kylon said:
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
Click to expand...
Click to collapse
Thanks. I will try the kernel.
kchaisu said:
Thanks. I will try the kernel.
Click to expand...
Click to collapse
It caused boot loop at the HTC logo. Thanks for your kind contribution. I have noticed that system partition is always formatted to ext4 no matter how you have changed to f2fs and finally it will be formatted back to ext4. Thanks.
Can you take a log?
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I flashed your kernel and everything is all right! Any bootloop I didn't get. Work well, don't see any difference.:highfive:
kchaisu said:
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
Click to expand...
Click to collapse
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
kylon said:
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
Click to expand...
Click to collapse
I made a clean install, factory reset and all wiped except internal memory and SD-Ext and also change file system to f2fs. It did not boot up with black screen. So, if you and Lapyyy have no problem with the kernel, it should be my device problem or set up. However, I have tried with every nighlies and Open Gapps and Delta Gapps and have faced the same problems. Now I shall try with difference SDcard with different format. Thanks for your kind contribution.
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
kylon said:
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
Click to expand...
Click to collapse
Thanks for your prompt reply. We will see how the problem could be solved. Now I reformatted the Data partition to EXT4 and all the stuff was gone. I have to copy all necessary files to the SDcard again and will try your kernel. By the way replaceing AnySolfKeyboard by F-Droid eliminated FC on keyboard issue and making Google Account setup possible. Thanks.
Amazingly mature
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
ralfbergs said:
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
Click to expand...
Click to collapse
Well, nothing is removed per se but system hides the camera icon etc. if it can't find appropriate camera hardware which it currently can't find because camera libs won't load due to missing symbols.
ralfbergs said:
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
Click to expand...
Click to collapse
Actually, I got the idea from HD CM-13 forum which was post by @marek287. Thanks to him.
Thanks to Mustaavalkosta and Kylon for the CM-13-20151211-sagaopt nightly. This bulid is fast booting up for GApps. However, SetupWizard and AOSP Keyboard still remains FC. Thank you very much.
{
"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"
}
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Build
- TWRP : Get here
Bugs
bluetooth calling
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
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.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
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 or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
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 access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
A big thanks to @erfanoabdi to kick start the development.
XDA:DevDB Information
LineageOS, ROM for the Moto G6
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Beta
Created 2018-08-11
Last Updated 2018-08-11
Copy Partition- Initial Setup
Flash the attachement via TWRP
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.
If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?
Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.
Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk
Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?
Anyone running xposed? Any issues?
Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?