Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

"<app> could not be downloaded due to an error"


  • Please log in to reply
2 replies to this topic

#1 deacon68

deacon68
  • Members
  • 1 posts
  • Device Model:nexus one
  • MOD Version:7.1.0
  • Recovery Image:Cyanogen

Posted 17 October 2011 - 10:32 PM

Hello all,

This is my first post, and my first attempt and modding my Nexus One.

I followed the guide found here:
http://wiki.cyanogen...ll_Update_Guide

I used the Amon_Ra's Recovery method.

After rebooting into CM7 I found that when I attempted to install any APP from the Google Market I received the message "<app> could not be downloaded due to an error"

I ran "fix permissions" from the ROM manager app as suggested in one of the threads, but continue to have the same issue.

Any other recommendations?

Thanks.

#2 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 18 October 2011 - 08:26 AM

From within recovery, wipe the cache partition. If that doesn't work, do a search for the system-only wipe from temasek and flash that. Then reinstall CM and gapps and see if your problem is resolved.

#3 Vineet3

Vineet3
  • Members
  • 1 posts
  • Device Model:Samsung GT-S5570
  • MOD Version:7.1.0
  • Recovery Image:Cyanogen

Posted 28 December 2011 - 11:24 AM

The same thing happened with me. Try creating a new Gmail a/c. It worked for me!