I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.
my1stSmartPhone said:
I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.
Click to expand...
Click to collapse
This is the wrong forum to post this in. Also, Snapshot M6 is almost a year old. Flash the latest nightly. That will work better. There's no CM10 for this device since it shipped with Android 4.3, so you'd be wasting your time looking for it. Even though systemui is crashing, mtp will still work, so you can transfer files to your phone normally. Also, this should teach you, that it is dangerous to experiment with your phone without a legitimate way out of issues or a backup.
As you able to flash a custom rom via custom recovery?
Press and hold power and volume down button together till 10 secs after your phone is turned off. You will go to bootloader menu. Connect it via USB to access fastboot.
@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.
my1stSmartPhone said:
@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
I'm sorry, but you're misunderstanding/reading the wrong things. You WILL NEVER find CM10 for the Moto G because CM 10 simply never existed for this device. You need to look for issues which are device specific and not just general issues all over the internet. Also, you WILL NEVER find a system.img and data.img in a CM11 zip. Those are only found in the stock ROM meant specifically for flashing via fastboot. All that information can be found by looking around the Moto G XDA forums itself. You'll find a lot of helpful stuff in the General section. You can also push a zip to /sdcard. You need to boot into bootloader and then push via ADB. MTP works on the latest TWRP recovery. So you can transfer it to your phone that way too.
audit13 said:
Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.
Click to expand...
Click to collapse
I need to become familiar with Philz. Being a newcomer to smartphones, it's not familiar to me. One of the fundamental requirements that I established at the outset of my search for a smartphone was to have the provider of the OS & phone be trustworthy or, failing that, go to open source so that it has the eyes of the world on it. It is also why I seek to be familiar with the source of ROMs, tools, etc. So far, I tried to download to from main sites for CWM, TWRP, and CM 11.
I know, it sounds odd these days, but I'm spoiled from before the internet days, when you can store any personal info you want on electronic organizers that had no connection, wired or wireless, to computers or the internet (which didn't exist). These days, it seems that you have to be very careful if you wish store any personal info on these personal devices. Either that, or carry a paper organizer around for the personal stuff (and I don't want to do that).
Thanks for confirming flashability via fastboot even without system.img and data.img. As it turns out, however, it isn't as promising a way ahead for me because I found out that the reversion back to CM 10 was a mistake (www.reddit.com/r/cyanogenmod/comments/2gvmqu/cm11moto_g_comandroidsystemui_is_crashing_after). The OP meant M10 snapshot, not CM 10. Which is odd, since the Moto G has no M10 snapshot (download.cyanogenmod.org/?type=snapshot&device=falcon). There's no M10 in the names of the nightly snapshots either (though that's less of a concern for me as I don't want to wander into nightly territory until I get the confidence of having my first attempt working).
I'll mull over Philz after some web search. I also distinctly recall backing up the stock Carrier ROM, so perhaps another way out is to find it and go through the details of restoring it.
my1stSmartPhone said:
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
1. Boot into Fastboot.
2. Flash TWRP recovery via Fastboot.
3.. Select Recovery from the menu and boot to TWRP recovery.
4. Put the ROM zip in a USB OTG drive.
5. Connect it to your device and mount it from recovery menu.
6. Install the zip via TWRP recovery from USB OTG.
DONE !
This is very odd.
I could not restore from my pre-CyanogenMod backups because when I browse to the date+time-stamped folders, it was empty. However, I had previously copied to contents of at least one date+time-stamped folder to my laptop.
I used fastboot to uprade TWRP from 2.8.3 to 2.8.4 in hopes of getting past the MTP driver problem, which would enable me to copy the files back to the device. Halleluya, it did allow the device to be seen in Windows Explorer. But I didn't need to use the copy on the laptop because moving to 2.8.4 also allowed the backups to be seen on the device.
I gleefully restored the backup. It said "failed", but I rebooted anyway. Unfortunately, the failed restoration was real, and I was still with CyanogenMod. I interrupted the boot process to get back to bootloader.
I reverted back to TWRP 2.8.3, hoping that it would still see the backup. I was hoping that 2.8.3 would properly restore the backup because it was created using 2.8.3. It did indeed see the backup, but the restoration still resulted in "failed", and a reboot still led to the CyanogenMod bootup.
Oddly, CyanogenMod booted properly this time without the repeated systemui popups. It's great! Though I wonder if I somehow affected CyanogenMod with the failed attempts at restoring the stock carrier's ROM. Not that I care right now. CyanogenMod awaits exploration.
But there are a couple of things that I hope someone can comment on. What might cause CyanogenMod to boot properly after upgrading TWRP and reverting back, failing to restore the stock carrier ROM with both versions? Could CyanogenMod now be corrupt? And why won't my backups restore? How can I ensure that I create good backups?
P.S. Thanks to i_rnb for the tip about USB OTG. I did not go that route because I only have the cable that came with the device.
P.P.S. I'm a bit (or rather, quite) unsettled by the randomness with which things work...
I downloaded the CyanogenMod nightly for Moto G, cm-12-20150213-NIGHTLY-falcon.zip. I got it working. Pretty robust so far, so I want to enjoy it a bit before clobbering it by attempting to restore the Carrier stock ROM. I admit that I will have to do that at some point because I need to ensure that my backups are good.
I would like to take this opportunity to recount how I got around the problems I faced. I think that others may run into this, and my story may help them get back to a working phone when it looks like it is bricked.
The problem was that CM 11 was crippled by the repeated systemui popup messages. I thought it went away, but it came back. I still don't know what triggers it. And my backups of the carrier OS either failed to restore (twrp 2.8.3) or were not visible (twrp 2.8.4). I had spent so many days trying to think of a way ahead that simply didn't care about bricking the phone anymore. After all, it wasn't doing a whole lot of good as-is. So in one of my attempts of trying something, I erased the OS in the process of re-installing CM 11. And the re-install failed. Not a good situation, since ADB worked only when an OS was running (not when a recovery was running), and the MTP driver errors prevented the device from being accessed from windows when recovery was running. It didn't matter whether I was running twrp 2.8.3, 2.8.4, or CWM. So sideload didn't work in any of those recoveries.
There was basically no way to push *any* new OS to the phone. I forgot the details, but the CM 11 imag file that was on the phone might not have been visible to the one or more of the recoveries I tried. I was so out of options that I even tried fastboot to flash to OS, and that did not succeed.
Here is what I found worked. I don't know what particular detail was responsible for the success, so it requires experimentation.
First, I un-installed re-installed the SDK tool set for installing custom ROMs, making sure that I included Google USB drivers. The subsequent update required many more things to be installed, so that might have been part of the solution. I then looked for Motorola driver apps in Windows's Programs menu, uninstalled both, and re-installed. I don't know what contribution it had to the success, as I never got the Device Manager running. Whenever I launched it, it searched for updates, came back and reported no updates and that my device was uknown, then quit. Maybe because no OS on the device was running.
The one thing that seemed to help was that, even though the device was otherwise incommunicato from the laptop, I was able to fastboot flash recoveries. After the above re-installs, a re-install of twrp 2.8.4 allowed the computer to see the device in Windows Explorer. I believe it had something to do with better-functioning MTP USB drivers in the re-install, but I can't be sure. So I was able to copy the nightly CM 12 to the device, then use one of the recoveries to install it.
But the story didn't end there. Even after the CM install, I was still getting repeated popups. This time, however, it was something other than systemui, but otherwise, the symptoms were the same. At that point, I had pretty well concluded that my experiment with Moto G was at its end, and that I would look at Blackberry (now that they committed to stay in the handset market). But I did half-heartedly experiment a bit more. Good thing, too, because the 2nd attempt at re-installing CM 12 seems to have worked. No repeated popups so far. What I made sure that I did was to wipe out anything for which there was a check box, e.g., any cache, data partition, OS, etc. Since it was a virgin phone, I could do this with impunity, so I'm not sure how well this "solution" would fit someone else's situation. Also, I did try to wipe things in past attempts, just not with so much thoroughness.
So there you have it. I hope this helps someone.
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor
THREAD UPDATED 4/22/19
So I started having pre-flash errors, boot looping, and bricked modem problems from just flashing the modems so I decided to upload the entire stock firmware for Nougat and Marshmallow. It's the same process but you have to flash the entire firmware then flash TWRP to use custom roms. Just click the FLASH-ALL.bat in the Nougat or Marshmallow folder and it will flash the firmware automatically and reboot. If you have any issues please report it here. I also included TWRP and the stock boot images all in one package just go into the folder and hit FLASH-ALL.bat. Everything is automated no more looking for firmware and flashing manually.
Link 1:
https://mega.nz/#!K1o0XIDS!taCkfjVbWunmkEOFVrqUaFeTLEQZ-JQACqO2EpebnAo
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
jabberjaw007 said:
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
Click to expand...
Click to collapse
If you want stock Nougat go ahead and update to it but I had battery drain issues on the Nougat modem from personal experience. If you decide to update you can use this thread and downgrade to stock 6.0.
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
AndroidMilos said:
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
Click to expand...
Click to collapse
Okay if the terminal window flashes really fast and you can't read it that usually means it can't write to the phone. Either your bootloader isn't unlocked or your usb cable doesn't support data transfer. If that isn't the issue make sure you install Motorola device manager and the adb fastboot sdk drivers which can be found on XDA. More than likely you're getting a remote failure error I have this problem myself a lot on Windows 10.
Thank you for your reply. I will follow through with the info you gave me.
I no longer own this device so I will no longer participate in any Moto X Pure threads. FYI if you flash the Nougat firmware in this thread you have to OTA to the final update for Nougat ROMs to work.
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Blackest Pain said:
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Click to expand...
Click to collapse
You can't use TWRP on OOS 12, though you might be able to install the OOS 12 zip using TWRP if you're on OOS 11.
Check your drivers if you can't connect to the phone in bootloader mode. You might need to simply reinstall it (I've had to do this a number of times).
You might be able to switch active partition it might save you I had something similar happen changing partion helped me get back into adroid