Related
Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help
Hey guys!
INFO:
OS: Win8 x64 Pro
Phone: Nexus 5
Recovery thing: TWRP
Current ROM: NONE (corrupted)
USB Driver: Google USB Driver (works 100% fine)
I was trying to install a custom ROM, but failed horribly. I formatted the Nexus 5 in TWRP. Now I have no ROM installed, and cannot install any ROM because the one on the phone was deleted. Luckily I backed up everything useful on my PC before.
I tried using ADB to fix it. In CMD, my computer recognizes my Nexus 5, and shows it in CMD but I can't do anything. When I type in "adb devices" it says "109231blahblah unauthorized". "adb shell" also says I need to accept the "authorization dialog". "adb push" also says I am unauthorized.
I think I am "unauthorized" from doing anything because I didn't enable USB debugging (stupid I know) and now I can't even change it since I have no ROM installed.
Any way to enable USB debugging in TWRP?
I think the first thing to try is to restore whatever back up you have made with TWRP. Then you can redownload the ROM and try to flash it again.
If you don't have a back up on your device, I would download a ROM that you are sure has worked on your device before (or one that can be checked with MD5 or sha hash tags) and then use adb sideload to install the ROM. You can find the TWRP documentation for adb sideload here: http://teamw.in/ADBSideload
justmpm said:
I think the first thing to try is to restore whatever back up you have made with TWRP. Then you can redownload the ROM and try to flash it again.
If you don't have a back up on your device, I would download a ROM that you are sure has worked on your device before (or one that can be checked with MD5 or sha hash tags) and then use adb sideload to install the ROM. You can find the TWRP documentation for adb sideload here: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Since he's getting the unauthorized messages, I don't think sideloading would work.. It's really weird though, sideloading should work in a custom recovery without enabling debugging in phone settings...
@Sharmster
If you can't use adb then here are your choices:
1. Use OTG Cable and a flash drive to install rom/gapps from the flash drive itself.
2. If you don't have an OTG cable then you are left with flashing the factory images(which needs fastboot) and starting all over again! Follow this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:
You can ADP from TWRP so all is not lost
apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.
Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((
[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.
My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?
It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going