Database Info

[Q] Market not working: "Download failed", tried everything.

I know that there are tons of threads about this but none of them have helped. My market just will not work. It shows it downloading, then displays the message "Download failed" for a split second and disappears.
I have an HTC Desire (BravoC/CDMA) with the latest version of CyanogenMod 7 Nightly and ClockworkMod 2.5.0.9 for recovery. I also have Firerat's Custom MTD Partition. Details and links to all these can be found in my signature.
I feel like I've tried everything. Uninstall updates, Installed latest GApps, Installed old versions of GApps, Installed leaked versions of Gapps, cleared cache, formatted device.
This has been happening since the new market website was released. It really sucks, I can't update any apps or download any new apps.
If anyone can offer any help or suggestions I would greatly appreciate it.
Thank you

Try removing SD card then try again. I had the same problem with my galaxy s I removed SD card backup on PC then I formatted it put it back in and market works perfect, don't ask me why but this worked for me
Sent from my Ideos using XDA App

a little weird thing i noticed is,if i have checked the box that allows applications to be download to the external(Apps2sd) whatever i try to download, will be resulted with Unsuccessful. When i unchecked it, my downloads were successful.
See if you have it checked.

I discovered that it was a problem with the CSC file. I had exactly the same issue with a 'mixed up' firmware. Download would not work at all from the market. Anyhow, I flashed the phone (galaxy s) with a different CSC file and the market started downloading.
the only thing I had changed was that file.
So u may want to consider that Hope this helps.

I think there is also a possibility of going to applications --> market, and then stop & clear data.

same situation here...
re-flash the rom and market won't download anything.
But it's strange that I can install apps from web market.

i know i'm at the wrong thread but could somebody help me pls with sgs gingerbread im stuck at on command where it is saying that busybox is not a valid command and thats its not recognized

Thanks for all the suggestions guys, after some time I have discovered what was causing the market issue. It was the Firerat Custom MTD Partition Mod the whole time. Apparently the new version of the market deals with downloads a little differently now and doesn't get along with Firerat's mod.
So now the waiting game begins for a new update from Firerat.

Hi,
NOt a solution, but I found a workaround for this issue on my phone.
I am using Hyperdroid GBX V8 on my HTC HD2 now. From last 2 days I was struggling with this problem. I tried all solutions I found with google. Clearning everything and Reflashing, clearing the market and caches for other apps, reflashing, unmount/mount SDCARD and so on, smaller bigger recovery partition, without EXT3/4 partition.
Still the problem exist on the phone. But I found a workaround. Logon to market.android.com using your google id and password, select the app you want to install and click install. if your phone is up and live, it will be installed in a few seconds.
In other words, pull doesnt work, but push works .
Thanks.
Anil

[Q] Force close after adding Reboot option

So I'm using lfaber's Supercharged V5 ROM and I tried to add the Reboot option to the power menu (JRW's method).
I messed up when following the instructions, however. I downloaded the ZIP to my phone and then installed it from the SD card, but forgot to wipe the cache first like the instructions said. So I wiped the cache and then went back and installed the ZIP again.
When I booted back up, I got force close messages for what seemed to be all my apps. Is this because I messed up the instructions? And what should I do to fix it? Can I backup into SCV5 again like I did at first or should I go back to the stock deodexed 2.3.6?
Thanks in advance for any advice!

Usually it will force close because of an issue with signing, not because of cache wiping... try flashing the different 1% battery mods. (Don't forget to wipe cache partition and Dalvik Cache)
Sent from my MB865 using Tapatalk

I'm not able to get my computer to recognize that my phone is plugged in (I think I saw a 'usb' force close message as some point) and I can't access the XDA app or the internet with my phone. Any suggestion on how to get the ZIP onto my SD card so I can flash it?

mcm743 said:
I'm not able to get my computer to recognize that my phone is plugged in (I think I saw a 'usb' force close message as some point) and I can't access the XDA app or the internet with my phone. Any suggestion on how to get the ZIP onto my SD card so I can flash it?
Click to expand...
Click to collapse
Is everything force closing or are just Google/Motorola apps force closing? Just keep closing the notification windows until they stop.
There's three ways of getting the zip onto your SD card, two of which may not be possible...
-Use the Motorola "Phone Portal" app to "Connect with wifi" and transfer the zip from your computer to your phone via wifi.
-Use the browser to download the zip file and make sure you can find it on your sd card
-Use a microSD card reader to put the file on your sd card
However there's another thing you can do that should fix you up.
-Make a CWM backup
-Flash SCV5, then the update zip
-Use CWM to "advanced restore" "data".
This will fix you up on any system modifications but restore your apps/data.

I didn't have an sd card reader, so I just backed up my system, then backed up into SCV5 and flashed the update. Phone is running fine with no force close issues.
If I understood you correctly, what I need to do now is put a different 1% battery mod than the one included in the ROM and then flash the reboot option again?
I'm a little confused as to why the 1% battery mod is involved at all?
Also, restoring data via CWM didn't seem to bring back my home screen setup. Would I need to restore system in CWM for that? I'm guessing if I did that my force close issue would just come back though, right?
Thanks again for all your help.

mcm743 said:
I didn't have an sd card reader, so I just backed up my system, then backed up into SCV5 and flashed the update. Phone is running fine with no force close issues.
If I understood you correctly, what I need to do now is put a different 1% battery mod than the one included in the ROM and then flash the reboot option again?
I'm a little confused as to why the 1% battery mod is involved at all?
Also, restoring data via CWM didn't seem to bring back my home screen setup. Would I need to restore system in CWM for that? I'm guessing if I did that my force close issue would just come back though, right?
Thanks again for all your help.
Click to expand...
Click to collapse
Restoring a CWM data backup should bring back your homescreen setup, as it restores the entire /data folder... Interesting. Don't restore system otherwise your problems will comeback

Very strange, shouldn't be nothing with the reboot.zip that would affect any of that unless you got a bad download?

farshad525hou said:
Restoring a CWM data backup should bring back your homescreen setup, as it restores the entire /data folder... Interesting. Don't restore system otherwise your problems will comeback
Click to expand...
Click to collapse
Yea, I got an error when I backed up through CWM, but it was just generic. I was more worried about having the phone working at that point than having everything backed up, so I didn't worry about.
JRW 28 said:
Very strange, shouldn't be nothing with the reboot.zip that would affect any of that unless you got a bad download?
Click to expand...
Click to collapse
Are you saying that you don't think flashing a different 1% mod would allow me to flash the reboot.zip without getting those force close errors again?
Thanks guys.

mcm743 said:
Are you saying that you don't think flashing a different 1% mod would allow me to flash the reboot.zip without getting those force close errors again?
Thanks guys.
Click to expand...
Click to collapse
Not at all. When I first released the reboot.zip it worked fine with V5 but I have always run my 1% vertical mod and when I flashed it I lost the ability to reboot with the power menu. So I then went back and modified all of my 1% battery mods to work correctly with my reboot.zip. you should have zero problems with them as long as they are mine or the one that comes with V5. I have not had a chance to test with anything on 2.3.5 yet though

The reason I first recommend you to flash a different 1% battery mod was because it re-writes any system files that the first flash may have messed up. Now that you're up and running again you don't need to do anything else.
It's odd that your homescreen configuration wasn't saved... what launcher do you use?

cogeary said:
The reason I first recommend you to flash a different 1% battery mod was because it re-writes any system files that the first flash may have messed up. Now that you're up and running again you don't need to do anything else.
It's odd that your homescreen configuration wasn't saved... what launcher do you use?
Click to expand...
Click to collapse
I use the one that comes with SCV5, Go Launcher. I was able to restore the home screen directly from the Go Launcher app. So at this point, I'm up and running, but I still don't have the reboot option. Should I just backup as is (with SCV5.1) and try flashing the reboot option again the same way I did before? I would just seem weird if I just did the same thing again, because why I wouldn't just have that same force close issue like the first time?

mcm743 said:
I use the one that comes with SCV5, Go Launcher. I was able to restore the home screen directly from the Go Launcher app. So at this point, I'm up and running, but I still don't have the reboot option. Should I just backup as is (with SCV5.1) and try flashing the reboot option again the same way I did before? I would just seem weird if I just did the same thing again, because why I wouldn't just have that same force close issue like the first time?
Click to expand...
Click to collapse
Sure, backup and try flashing reboot again. But this time redownload the zip first.

cogeary said:
Sure, backup and try flashing reboot again. But this time redownload the zip first.
Click to expand...
Click to collapse
I second that. Do a CWM backup then redownload the mod, and flash it. The download may have been corrupted last time around.

farshad525hou said:
I second that. Do a CWM backup then redownload the mod, and flash it. The download may have been corrupted last time around.
Click to expand...
Click to collapse
Running the backup now. I will let you know how it goes and I'll make sure to do a fresh download. Thanks.
Edit: this worked perfect. I realized when I did the download again that originally downloaded via the QR code, so maybe there's something wrong with that? Or something wrong with my phones QR code reader? I used Goggles.
Thanks again!

TWRP won't mount anything

apologies if this has been covered already.
I have an Asus Transformer Infinity TF700T, I installed cynogenmod 10 and gapps, and then wouldnt boot past splash screen, so I found out to install a new bootloader. after I did that, I could boot into Android, but it was like a brand new installation. My apps were all gone (which may or not be normal). I had to install a file manager and I found that my files are still there, so I wanted to reattempt a google app installation because I didn't have any google apps. When I booted, It requested a password. I have no idea what this password is supposed to be, and I can't find any info anywhere. so i gave up and hit cancel and nothing is mounted. I tried to mount stuff, but the screen seem unresponsive when i click those areas. I cant clear any data or anything because it isnt mounted, I cant restore my backup because nothing is mounted.
Please help me. Thanks in advance

I may have found something. Im using goomanager to install a later version I think

Ok, that fixed it. I just wish I could get all of the apps.

[Q] Cannot Install any apps - hot reboots before install finishes

Has anyone seen this issue? It happens if I install from an apk file or from Google Play. Here is what happens.
It sits at install for about a minute (which is much longer than most installs used to be) then the UI on the phone restarts. It looks like a hot reboot.
My phone is running the Blaz3r 3 ROM and I am running "Root External 2 Internal SD" to have my phone install things to the External SD.
I made no major changes between the previous successful install and my failed installs.
I tried rebooting and I do have enough disk space for an install. I tried installing CatLog to find out whats wrong, but...I get the same error. Anyway to get at catlog without running an install to find out what sort of errors might be going on?
Thanks
ButterQuark
EDIT:
If there is a different forum that this question could be better answered, I would love to know. Im still new to how this forum is laid out.
EDIT2:
So I ran logcat from the adb and I got this
http://pastebin.com/QrBFtqUQ
I am pretty sure this has to do with the "Root External 2 Internal SD" so I will attempt to go through the developer.

Problems when updating a previously rooted Nvidia Shield Tablet [MOVED HERE]

[This was already posted, I just moved it to the Shield Q&A.]
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.

Quick answer:
- You don't need to restore to full stock before updating to the latest OTA. This is what I did, running a rooted stock system with TWRP recovery:
-- Go to Settings > About tablet > System updates and continue to click Check Now until the update has been found. I had to click like 4 or 5 times before it was found. It'll download automatically to your device (not your SD card), but I forget where that download location is... XD
-- once you've found your downloaded OTA.zip, copy it to a location you can easily find from your custom recovery.
-- reboot into custom recovery, flash OTA.zip, reflash superSU.zip, wipe cache NOT DATA, reboot
-- wait until device boots up, wait until the Optimizing blah blah process is done.
-- enjoy!
Additional thoughts:
- I've tried the Link2SD app, but I think it messes with my system in a way I don't like; personally I'd rather delete the apps I never use via custom recovery (see THIS THREAD on how to debloat your tablet for yourself!
- I think your error happened when you flashed stock recovery on top of the custom one. To prevent this next time, simply wait for either a flashable zip in THIS OTHER THREAD, or you can check to see if nVidia released any OTA3.1 recovery images if you want that full-stock experience.
Hope this helps!