• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Windows MTB USB Device driver error when Moto G running TWRP

M

my1stSmartPhone

Member
I am trying to sideload cyanogen mod. Whenever I boot the phone into TWRP, Windows 7 (64 bit) tries to install MTB USB Device drivers and fails.

> Driver Software Installation:
>
> Device driver software was not successfully installed
>
> Please consult with your device manufacturer for
> assitance getting this device installed.
>
> MTB USB Device X Failed

I already uninstalled Android SDK Tools and re-installed, making sure that Google USB Drivers are installed. I also installed Motorola drivers, but that was at the start of my journey and I didn't take notes on the details.

I have no problems accessing the phone via USB when the phone is booted up normally. I also have no problems using fastboot when the phone is is bootloader mode.

I originally tried a number of ways to use CWM instead of TWRP, but was unsuccessful. I've posted those efforts in this forum and abandoned CWM after a while.

Has anyone who owns a Moto G actually been able to install CWM or install CyanogenMod using TWRP? I want to use adb rather than non-mainstream tools, and I'm not interested in rooting at the moment (though rooters are more likely to be familiar with issues at this level).
 
I installed TWRP because I couldn't get CWM to work. Every time I booted into recovery, I saw a picture of a green R2D2 unit lying on its back.

As for changing recovery, I'm not trying to change recovery at the moment (if I understood you properly). I'm just trying to sideload CyanogenMod.

By the way, from further web search, this is the last news that I can find about MTP USB drivers when booted up in TWRP: <<erroneous URL removed (I can't re-find the correct webpage)>>

I'll continue sleuthing a bit more before looking at how to install cyanogenMode without sideload. But for now, it seems that the MTP issue remains (though I admit, I'm new to the whole smartphone thing and I could be wrong about that).

Afternote: I chose sideload so that I wouldn't have to worry about where the cyanogenMod zip file goes. From using adb shell to "ls" around, it seemed a bit confusing, and it wasn't obvious how the directory structure from "ls"ing around matched the 5-7 partitions that are on most Android file systems. In fact, entire subtrees seemed to repeat themselves at different parts of the tree.
 
Last edited:
OK, it's a terminology problem.

To sideload means to install.

You're evidently just wanting to do an adb push, not a sideload.

Send it to /sdcard.
 
Thanks, EarlyMon. That's exactly what it says at wiki.cyanogenmod.org/w/Install_CM_for_falcon. I found that I needed to bookend sdcard with slashes: "/sdcard/".

I am now facing the (apparently commonplace) problem of being in an endless loop with the popup "Unfortunately, the process com.android.systemui has stopped. [OK]". I'm one step further, though. There seem to be many causes for this problem, with varying degrees of similarity in the symptom. I've not yet run across a case with exactly the same symptom, where the loop occurs at the language selection screen. Of the various circumstances that I've read about, the one that seems that it might be most relevant is the association of this error with an Italian keyboard app. In my case, the English (Canada) language seems to be selected, if I'm interpretting the graphics properly. I will try replacing the keyboard apk with one from a nightly. New territory.

The other causes are flipboard app, ART vs. Dalvik, and possibly a few others.
 
I googled how-to-clear-data-and-cache-on-Google-Play-Framework, and read www.androidpit.com/google-play-not-working. It seems that you have to be able to get the OS working before you can actually clear those Google Play data. I haven't been able to get beyond the language screen. I can't access the device via adb, either. :(

Afternote: I was able to press Next a few times in between the error message popups, and I got the the home screen. The devices shows as XT1032 in the Windows Explorer, but there's nothing in that "folder".

Update: I don't have any app beginning with the word "Google", so it seems that none of the above measures having to do with Google Play apply in my case. I suspect that this may be because I'm working with a virgin install of CyanogenMod. Looks like I'm still on search for a way ahead. I also tried switching the language from English (Canada) to English (US), based on the info I found online that the problem was due to a keyboard apk. No joy.....

Update: Another user had the same problem and solved it by reverting to CM 10 (www.reddit.com/r/cyanogenmod/comments/2gvmqu/cm11moto_g_comandroidsystemui_is_crashing_after). Looks like I have a way ahead.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom