[Q] twrp backup works, causes windows driver errors topic

I'm getting the attached errors when running TWRP using:

Code:

---

  fastboot boot openrecovery-twrp-2.8.3.0-xt1032.img

---

Here is a summary of the message:

Code:

---

  Device driver software was not successfully installed
      XT1032                  No driver found
      USB Composite Device    Ready to use
      MTP USB Device          Failed
      Motorola ADB Interface  No driver found

---

If I flash instead of just booting, I only get the MTP USB Device error. I know that I have working drivers for fastboot & adb, but I'm not sure how relevant they are when the Moto G is in recovery. I just included all errors shown in the message window.

Can I safely ignore the errors?

Here are the details (1st generation Moto G):
* Android 4.4.4
* Kernel version 3.4.42-g67b2f25
* System version 210.12.50.falcon_umts.Telus.en.CA
* Build number KXB21.14-L1.50
* Laptop: Windows 7 64-bit

Background for reference only
-----------------------------
In case this heads off any questions, here is the history and context behind my usage scenario.

I've unlocked my boot loader and wanted to backup the carrier's OS before installing CyanogenMod and/or rooting. The carrier is Koodo Mobile, and I wanted to make a backup rather than download what was available on the web.

"fastboot boot cwm.img" didn't work, so I used "fastboot flash recovery cwm.img" (actual file was recovery-clockwork-6.0.4.7-falcon.img from http://www.clockworkmod.com/rommanager). When I tried to go into recovery, I got an android logo with the message "No command".

According to http://forum.xda-developers.com/show....php?t=2563599, the Android 4.4 bootloader doesn't work with CWM, and I would have to flash the 4.3 bootloader. Or so it seems to me. Being new to the whole smartphone thing, I decided against doing that and went with TWRP instead (http://teamw.in/project/twrp2/233). I got the same "No Command", and http://forum.xda-developers.com/show...&postcount=129, indicated that I could not flash TWRP due to its size. Instead:

Code:

---

  fastboot boot openrecovery-twrp-2.8.3.0-xt1032.img

---

It ran and created backup files according my settings (including PDS, as per http://www.reddit.com/r/MotoG/commen...ds_partition):

Code:

---

  [X] Data (156MB)
  [ ] Cache (11MB)
  [X] System (763MB)
  [X] Boot (10MB)
  [X] PDS (3MB)

  No Encryption                Refresh Sizes
      Storage: Internal Storage (4040MB)

  [X] Enable compression
  [ ] Skip MDF generation during backup

---

The files were located at both /mnt/shell/emulated/0/TWRP/BACKUPS/TA929174HF and /storage/emulated/legacy/TWRP/BACKUPS/TA929174HF. In the Windows Explorer, it was found in "Computer\XT1032\Internal storage\TWRP\BACKUPS\TA929174HF".

I later ran across webpages saying that you should use mfastboot for large *.img files, and that seemed to allow me to flash TWRP onto the Moto G. When I re-did the backup, I only go the MTP message in the device driver error window. Here is the listing of the Windows folder "Computer\XT1032\Internal storage\TWRP\BACKUPS\TA929174HF15-01-04--20-29-45 KXB21.14-L1.50":

Code:

---

-rw-rw---- root sdcard_r 10485760  2015-01-04 21:31 boot.emmc.win
-rw-rw---- root sdcard_r      48  2015-01-04 21:31 boot.emmc.win.md5
-rw-rw---- root sdcard_r 70714967  2015-01-04 21:30 data.f2fs.win
-rw-rw---- root sdcard_r      48  2015-01-04 21:30 data.f2fs.win.md5
-rw-rw---- root sdcard_r      64  2015-01-04 21:30 data.info
-rw-rw---- root sdcard_r  3145728  2015-01-04 21:31 pds.emmc.win
-rw-rw---- root sdcard_r      47  2015-01-04 21:31 pds.emmc.win.md5
-rw-rw---- root sdcard_r  487236  2015-01-04 21:31 recovery.log
-rw-rw---- root sdcard_r 475807073 2015-01-04 21:31 system.ext4.win
-rw-rw---- root sdcard_r      50  2015-01-04 21:31 system.ext4.win.md5
-rw-rw---- root sdcard_r      64  2015-01-04 21:31 system.info

---

Attached Thumbnails

 

Browse More Articles

Tweet

Written by dd

We are Creative Blogger Theme Wavers which provides user friendly, effective and easy to use themes. Each support has free and providing HD support screen casting.