yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] shourya jain:
I don't know why but for some reason i'm unable to install cm 14.1. When i try to install any of the cm14.1 nightlies i got the following message:-

Finding update package...

Opening update package....

Installing update....

Target: 1481683112

could not detect file system for /dev/block/bootdevice/by-name/system: No such file or directory.

Unmount of /system failed: no such volume

Patching system unconditionally....

E1001: Failed to update system image

E: unknown command [log]

E: Error in /sdcard/cm14.1-20161214-NIGHTLY-falcon.zip

(Status 7)

E: Installation Abort.

How can i fix this??
[Moto G Original Android Development] Phrodini:
Your TWRP, bootloader up to date,your install steps? Also verify your download
[Moto G Original Android Development] fxcatalyst:
Are you using cm updater. Try using TWRP . flash zip and wipe cache & dalvik. Use TWRP 3.x.xx
[Moto G Original Android Development] dhabsot:
Is the long swipe to unlock fixed in newer builds? On older builds there was that bug that made me reinstall IDcrisis rom.
[Moto G Original Android Development] shourya jain:
TWRP: 3.0.2-2 FALCON

Bootloader: 41.1A (sha- 804819e, 2015-05-10 14:30:28)

install steps: 1) wipe date. dalvik cache

2) install zip from sd card > cm14.1 20161214-falcon.zip

---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------

I have been using TWPR 3.0.2-2
[Moto G Original Android Development] sathvik07:
Wipe system, data, dalvik cache, cache & then install the Rom's zip
[Moto G Original Android Development] shourya jain:
Already tried that several times..evertime same error shows up.
[Moto G Original Android Development] Phrodini:
Maybe check to see if system mount is checked in twrp
[Moto G Original Android Development] gaarared23:
So I did some deep s***. I was getting the same error above mentioned (error 7) and could not install the ROM. After some frustration tries, I do not know why I decided to install the cyanogenmod recovery. Problem is I cannot get back to the TRWP as I cannot see the option to install another recovery... Anyone can help me, please? I really dont know what to do and I am desperate...

Forgot to mention, on the fastboot menu (bootloader?) it does not recognise the connection to PC so I can't do a fastboot flashing.
[Moto G Original Android Development] koshikas:
if you get error 7, reboot TWRP immediately after wiping and before you flash anyhting
[Moto G Original Android Development] gaarared23:
That's the thing, with the frustration I ended flashing the cyanogenmod recovery.... Which doesn't have any option to install other recovery.
[Moto G Original Android Development] Raju-Kol:
What is the Emergency option after pressing the power button and how to edit it?
[Moto G Original Android Development] Christian_U29:
wich is the best kernel for this ROM?
[Moto G Original Android Development] gaarared23:
So I was able to get back to TWRP. Same error. I tried that, wipe and then reboot recovery before flash but same error...
[Moto G Original Android Development] triggerlord:
Just flash twrp via fastboot.
[Moto G Original Android Development] gaarared23:
It wasn't working but I managed to do it eventually, thanks! The thing now is the same, error 7 ...
[Moto G Original Android Development] TiNcHoX:
help

hi, any ideas why my 3g dont work on the last 2 CM13 Snap, but works fine on CM14 ?

i have the 3g! (exclamation sign)
[Moto G Original Android Development] steford:
Error 7 disappeared for me when I flashed from internal memory and not SD card.
[Moto G Original Android Development] spajdo:
do you have SD card on Falcon?

---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------

Hi people... has this rom some issues or everything works fine? Please let me know.
[Moto G Original Android Development] c3maker:
my phone is an xt1031 it has 41.1A bootloader and TWRP 3.0.2-2. the system format is ext4 the data format is f2fs and the cache format is ext4. I have been running cm13 since it's release, decided to try cm14.1. It flashes with no errors but will not boot past the android animation. I have left till the battery was dead waiting. the phone buzzes every few seconds after a couple minutes of the boot. I power down reboot to recovery and try a different rom or reinstall cm13. I am still trying things but any suggestions would be appreciated.
[Moto G Original Android Development] drfr:
Why not? I do have one. Connected through USB OTG. Used for storing nand backups, TiBu files, ROMs, gapps, whatever.
[Moto G Original Android Development] legendavey:
That's not the same as an SD card inside the phone (you can't use adoptable storage, etc)
[Moto G Original Android Development] shourya jain:
Yea i tried that too, installing rom via my sandisk otg pendrive, but still i get that error (status 7)
[Moto G Original Android Development] matmutant:
It is not what I said : (see attachment). I mean, I did say Falcon supports f2fs, not that you should try to format everything you could find to f2fs.

(and btw you had the hint from the beginning, my first screenshot showed you that ONLY /data was on f2fs on my

own

device.)
[Moto G Original Android Development] kamesh_kraken:
I misunderstood in some way. Now I have days partition in feds, others in ext4. It's working fine now. Thanks for your time! :)

---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------

Wipe everything and copy the ROM to internal storage then flag using internal storage. MTP will work on twrp. So you can copy ROM and GApps. Then flash. It will work.

PS: Backup your data before wiping.
[Moto G Original Android Development] shourya jain:
Flag using internal storage??

U mean flash?
[Moto G Original Android Development] spajdo:
Hi people.

I'm trying this ROM and it looks good. There are only two things what I miss:

1. profile tile in quick settings

2. threestate location tile

Can I solve this in nightly from 15 of december?
[Moto G Original Android Development] shourya jain:
okay, so no error 7, but Error: unknown command[log] is still there , plus now i'm stuck on the boot-loop
[Moto G Original Android Development] sgrbk:
For error 7, better falsh with Gapps pico version.
[Moto G Original Android Development] drwierdo:
Can't add Google account after updating to latest Nightly:

Today I clean updated from CM 14.1 earlier build (Boot into TWRP 3.0.2-2>Wipe dalvik/cache/system >Install CM and Gapps>Wipe Dalvik/cache>Reboot into System) to the latest nightly 12/15 and flashed the ROM and latest Nano Gapps (12/16). After boot, I opened the Google Play Store and it asked to add the account. Everything went fine and I agreed to the terms of services. After that instead of opening the store, it again prompts to Add the account. This happens again and again.

I tried to add account from inside the settings, and same thing happens. I tried to open the Inbox app and tried to add the account and still same problem. I tried after wiping the cache of Google search, Google Play store and Google Play services and rebooting. Still the same.

If possible I don't want to do the full format.
[Moto G Original Android Development] fxcatalyst:
A clean install requires wipe System, cache, dalvik and data. Did you wipe data? An updating just requires wiping cache + dalvik .
[Moto G Original Android Development] gaarared23:
That's what I did and still error 7.
[Moto G Original Android Development] drwierdo:
I followed the instruction on post#2 of this thread where it says: For clean update → Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA!

There it says that wiping cache+dalvik only means dirty update. I intended to do a clean install.

I did not wipe data. I have all of my apps intact. Any suggestion?
[Moto G Original Android Development] efeenes7474:
I enabled root on Apps + ADB in the Developer Settings menu but it doesn't work. I'm using the latest build. Any way to solve it?
[Moto G Original Android Development] fxcatalyst:
from the first official build onwards i wiped cache+dalvik for updating from each build to the other and never incurred any error. Also when updating i never flashed gapps on each update of ROM. I did a complete factory reset(cache+dalvik+system+data) only for First time flashing of CM 13 to my phone.

Try wiping data along with system,cache and dalvik.
[Moto G Original Android Development] drwierdo:
Well, I was just following the instruction from the post #2. From next time on, I will try your method.

For now, I think I will wait to see if others have any suggestion. If not I will have to wipe the Data and reinstall all the apps :(

---------- Post added at 05:38 PM ---------- Previous post was at 05:13 PM ----------

Screw it - I'm wiping the data as well. My fault - as always - was not taking a backup :laugh::laugh:.

But I guess anybody trying to do a clean update, please take a backup. Because I ran into a problem while doing it.
[Moto G Original Android Development] efeenes7474:
Root doesn't work AND I can't write on system. I installed SuperSU to go around the root bug, but the system partition is definitely f-'d somehow.
[Moto G Original Android Development] fxcatalyst:
Enable root in developer options > use fx explorer with root access module (both are available at play store). When root access module of fx is installed, a new option named '' system (root)'' is available. Open it tap lock button on the screen for unlocking for writing.
[Moto G Original Android Development] TiNcHoX:
is this rom good for everyday used ?
[Moto G Original Android Development] triggerlord:
Yeah, it works fine.
[Moto G Original Android Development] Mickeyvdb:
Absolutely
[Moto G Original Android Development] kamesh_kraken:
E:unknown command is a known error and it should not affect ROM.

But you might as well check the partition type of /system, /cache. If they're in f2fs, please change it to ext4. This could happen only if you've tried. I got on boot loop for same reason. I couldn't see any other reason why you get boot loop if you wiped everything on your device.

---------- Post added at 01:29 AM ---------- Previous post was at 01:29 AM ----------

Of course I meant flash. Sorry :)
[Moto G Original Android Development] pierremg:
Did you do a clean install? Without any error message it's hard to find out what's going on.
[Moto G Original Android Development] shourya jain:
worked like charm..!
[Moto G Original Android Development] TiNcHoX:
there is any theme engine that works on this rom ?
[Moto G Original Android Development] c3maker:
Yes I did. I have even tried formating system and data partitians. since this not my primary device I have nothing to lose.
[Moto G Original Android Development] Northwinds:
Hi everyone,

since my last post I went back to stock 6.0 and then updated back up to falcon CM 14.1

I'm having 2 major problems though:

1) My Titanium Backup Pro won't work as it complains it can't get root access. There was an issue with SuperSU but I updated that and checked the root and everytning ok and other apps like BusyBox Pro are happy too - so really confused what's wrong with Titanium???

2) More importantly I'm noticing my moto g is restarting itself and ending up in twrp recovery mode - hence I'm missing calls and texts and my alarm isn't waking me - any suggestions please?

Like a lot of people I will be heading off in a few days for "family Christmas" and I could really do with having these (especially the latter) problems fixed!

Many thanks!

Cheers!
[Moto G Original Android Development] kamesh_kraken:
I'm glad it worked.

But what was the problem exactly? Did you find out?

---------- Post added at 12:43 PM ---------- Previous post was at 12:41 PM ----------

#cleaninstall. See OP for instructions. You updated from 6.0 means, that was a dirty flash I guess?

---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------

I'm not sure. I think some users said they use Substratum on CM14.1. But try it. Please backup your data before doing it.
[Moto G Original Android Development] shourya jain:
TBH, I didn't know exactly what was the problem :confused:

All i did was clean wipe my device multiple times and then install the rom.

After flashing and rebooting the device i thought my device was stuck on bootloop but then i came to realised that it was the rom which take so much time booting up after flashing for the first time.
[Moto G Original Android Development] kamesh_kraken:
It'll take around 10 mins with nano GApps. :)
[Moto G Original Android Development] shourya jain:
YEAH,it doesn't matter what GApps package you install, it'll take around 10 mins.
[Moto G Original Android Development] rydarg:
For those asking about Emergency button, it's been detailed in a post on AOSP. I can't link yet, so I'll post a para below.

Edit: More at source.android[dot]com/devices/tech/connect/emergency-affordance.html
[Moto G Original Android Development] Bzonedroid:
after clean update to last build, my google acc disappear and i cant login anymore... cant open many of my apps, so its all going crazy here... anyone know how to solve this? thanks.
[Moto G Original Android Development] seadersn:
flashing gapps should fix it ?
[Moto G Original Android Development] legendavey:
Thanks for this! Interesting that it works only in India, every country could use the button theoretically.
[Moto G Original Android Development] Bzonedroid:
nop, i already tried some... anyone?!
[Moto G Original Android Development] fr_jason:
Still no problems.

Running cm-14.1-20161208-NIGHTLY-falcon.zip
[Moto G Original Android Development] :
Hello

The rom runs very well.

Have only one problem: when I'm called, the display is dark. Only when I switch on the display manually, I see above the notification that I am called.
[Moto G Original Android Development] vkp1997:
Go to settings>apps>gear icon>phone app> set default dialer. :cool:
[Moto G Original Android Development] :
Thank you, but it (system dialer) was already set. I only had this dialer. Now I have the google dialer installed. Now goes display on with google dialer, if someone calls. With a system dialer it is not the case :confused:
[Moto G Original Android Development] rydarg:
I think that's what they plan to do eventually. Won't affect the older devices though :p
[Moto G Original Android Development] allrightlite:
I use this version, too. Works well, but last night it has rebooted alone by incoming whatsapp-message. Don't know why. But no bugs else, almost stable. Maybe its because the age of the phone. First problems with hardware? Hope it won't happen again :rolleyes::victory:
[Moto G Original Android Development] jaford:
Excellent ROM - totally transforms the geriatric Moto G!.

One point: Are the nightly changes cumulative? In other words, if I miss a nightly will the changes still be incorporated in subsequent nightlies? (I suspect so.) .

Jim
[Moto G Original Android Development] TiNcHoX:
how can i remove the translucent rectangle where the pinned apps are ?
[Moto G Original Android Development] TiNcHoX:
nevermind
[Moto G Original Android Development] fr_jason:
Strangely enough I got my first problem today. I was running an app and it suddenly froze the app itself.

I was able to back out, re-enter it to where it was locked up, go to home screen, lock and unlock the screen as normal.

I happened twice, I restarted and ran the app, just left it on most of the day and it it hasn't happened again.
[Moto G Original Android Development] fxcatalyst:
Yes. Just install any subsequent nightly and all changes up to that build will be added to your system.
[Moto G Original Android Development] TheKsprx:
I miss themes so I downloaded substratum from play store and the app icon is not showing. I even tried as a system app.

Has anyone been able to make it work?
[Moto G Original Android Development] nuttkrakk:
I think it doesn't work on CM. The ROM needs to be implemented with RRO support.
[Moto G Original Android Development] TheKsprx:
I read a post in the substratum thread that it works in some CM 14.1 roms..... I think it's not the case with this one. Oh well... I'll wait then, I don't feel like going back to CM13. I wonder how long it will take.
[Moto G Original Android Development] coolbird22:
I've been having this bug since as long as I've been on CM14 and it still exists for me. Could someone confirm if it is just me or is it for everyone ?

When in the Camera app, clicking on the Gallery button makes the Gallery load but freeze before loading any images up. I try to go to the Gallery app, which results in pretty much the same thing. However, I can access the images in other apps like Whatsapp.
[Moto G Original Android Development] xof1:
I can confirm this bug, it occurs sometimes.
[Moto G Original Android Development] mato_d007:
Yeah, the gallery is not very good. Im using piktures and so far it works as expected.
[Moto G Original Android Development] hal9008:
This also happens here.
[Moto G Original Android Development] smd100:
2nd SIM data probs

Hi. Thanks for all your fabulous work!

Since installing CM14/14.1 on my dual SIM XT1033, my 2nd 3G data SIM has slowed to a crawl. Switching SIM slots makes no difference. If I only use one SIM, data rate is fast again.

I did a clean install btw.

Any help would be really appreciated!
[Moto G Original Android Development] xof1:
I think I tracked gallery problem:12-22 15:10:54.582 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.582 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.582 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.582 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.615 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.615 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.615 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.615 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.649 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.649 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.649 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.649 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=1280

12-22 15:10:54.682 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.682 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.682 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=384

12-22 15:10:54.682 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=384

12-22 15:10:54.699 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.699 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.699 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=485

12-22 15:10:54.699 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=485

12-22 15:10:54.715 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.716 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.716 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=710

12-22 15:10:54.716 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=710

12-22 15:10:54.733 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.733 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.733 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=979

12-22 15:10:54.733 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=979

12-22 15:10:54.749 E/qdoverlay(208): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=1

12-22 15:10:54.749 E/qdoverlay(208): src msmfb_img w=1920 h=1280 format=5 MDP_RGB_888

12-22 15:10:54.749 E/qdoverlay(208): src_rect mdp_rect x=0 y=0 w=720 h=1116

12-22 15:10:54.749 E/qdoverlay(208): dst_rect mdp_rect x=0 y=0 w=720 h=1116

12-22 15:10:54.885 W/OpenGLRenderer(1765): Incorrectly called buildLayer on View: method, destroying layer...

12-22 15:10:57.078 I/ActivityManager(674): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.gallery3d/.app.GalleryActivity (has extras)} from uid 10090 on display 0
[Moto G Original Android Development] nikhilmdv:
Music play without enabling equalizer

From past one and half month, I'm using CM 14.1 on XT1033. One thing I have noticed that Music Player playing the music without enabling the equaliser while

1. Pause and Play Track

2. Changing Prev and Next Track

3. Select the track to play

Once I go into equaliser, its get automatically enable.

Is this same thing happening with you ???
[Moto G Original Android Development] seri0099:
Hi guys how I can download older versions of nightly builds?
[Moto G Original Android Development] DPX:
The oldest nightly I can find online is 12/18/2016 (https://download.cyanogenmod.org/get/jenkins/189172/cm-14.1-20161218-NIGHTLY-falcon.zip).
[Moto G Original Android Development] Stefano187:
Hi guys,

sorry for bothering you all! I miss this forum since a year now and I'm really impressed how far the development for falcon is gone!

My "old" moto G is now on my mom'shands and it has a very old version of CM 12.1.

Is it safe to update to CM14.1 from CM12.1?

Of course I'm going to install latest official TWRP and clean flash before doing anything.

Thanks in advance for your answers

Best regards

Stefano
[Moto G Original Android Development] nuttkrakk:
The nightlies appear to good for daily use. The one thing the ROM is lacking is CM themes.

I never got a chance to thank developers. So here it is: a big THANK YOU.
[Moto G Original Android Development] Voha888:
I install this ROM on xt1031 and has error "com.android.phone" when enter to mobile settings.

How to disable 1xRTT ? I want EVDO only.
[Moto G Original Android Development] mohitvshah123:
Are developers working on theme engine?
[Moto G Original Android Development] kamesh_kraken:
Stability over additional functionality. I guess they're indeed on the side. But they're trying to get the ROM stable based on our bug reports.

---------- Post added at 02:17 PM ---------- Previous post was at 02:15 PM ----------

Probably you should update to CM13's stable build for daily use. But CM14.1 is as good as CM13's snapshot. You can use it as a daily driver.

I recommend Clean Flash if you're gonna do CM13 or CM14.1.
[Moto G Original Android Development] AnkinDs:
It affects us? Or only to cyanogenOs users??

Enviado desde mi Moto G mediante Tapatalk
[Moto G Original Android Development] kamesh_kraken:
:crying:
[Moto G Original Android Development] sideswipeer:
Put the sim you don't use to 2g, apparently the network doesn't switch if both the Sims are on 3g.
[Moto G Original Android Development] DPX:
It definitely affects Cyanogen OS ROM but maybe our nightlies too...(http://www.androidpolice.com/2016/12/24/cyanogen-shutting-service-nightly-builds-december-31-2016/)
[Moto G Original Android Development] vkp1997:
No dear, both companies share same severs to build nightlies. CM is going to shut down too.

Last nightly will be 30 December build.

So the question is what is next?

Ok, don't worry, our favourite CM will return during February (it can take more time too) I think.... Under the name LineageOS.

https://github.com/LineageOS
[Moto G Original Android Development] DPX:
Cyanogen != CyanogenMod but I don't know whether they use the same servers or not. But I would say there still is a chance that we will get nightlies after 30th december.
[Moto G Original Android Development] TheKsprx:
So... should I lose hope for CMTE in CM14.1? :P our Moto g will die soon :(
[Moto G Original Android Development] kamesh_kraken:
we have some good AOSP ROMs that we can try.

But let's hope our best for CM.
[Moto G Original Android Development] DPX:
For further information check this: https://www.xda-developers.com/the-death-of-cyangenmod-and-whats-in-store-for-the-future/