10 replies to this topic

[Thomas J Marshall]

Have been using my sf2 for over a year now with no problems, running  bouncer5's rom.  Recently i have been getting an error 406 from google play store, I can't install any apps.  I have tried all the suggested fixes, clearing cache/data, deleting the apk etc. but nothing works.  I get the same error trying to install an apk from the sd card.  I reflashed the rom and am still getting the same error.

Edited by Thomas J Marshall, 03 February 2013 - 07:15 PM.

[Thomas J Marshall]

Alas, no replies.  Tumbleweed drifting across this post!

[gbosh]

How much free space do you have left ?
Also can you give a logcat of trying to install an app ?

[Thomas J Marshall]

gbosh, on 06 February 2013 - 05:24 PM, said:

How much free space do you have left ?
Also can you give a logcat of trying to install an app ?

Just over 27 mb.  I never could get adb to work and I don't have a logcat app installed.

[gbosh]

Well that's a bummer.
Wipe your system partition and re-install the ROM you have wihtout wiping data, if that doesn't work, try to do it with a wipe.
If that doesn't work you could always install another ROM with a wipe, that should fix it.

If you never got ADB working, how did you get your ROM on there ?

Edited by gbosh, 06 February 2013 - 06:34 PM.

[Thomas J Marshall]

gbosh, on 06 February 2013 - 06:34 PM, said:

Well that's a bummer.
Wipe your system partition and re-install the ROM you have wihtout wiping data, if that doesn't work, try to do it with a wipe.
If that doesn't work you could always install another ROM with a wipe, that should fix it.

If you never got ADB working, how did you get your ROM on there ?

I did flash the rom again after wiping everything but it was the same problem so I just restored my backup.  I used an image from flibblesan that installed recovery.  Not sure why adb wouldn't work, I'm using windows 7 and I think it was something to do with the drivers.

I've just bought a Raspberry Pi, it runs a version of debian.  Could I run adb there?

[gbosh]

Try installing the driver by following this guide http://sanfranciscoa...i-zte-crescent/
on windows

adb should work on the Pi as well

Edited by gbosh, 06 February 2013 - 07:38 PM.

[Thomas J Marshall]

gbosh, on 06 February 2013 - 07:37 PM, said:

Try installing the driver by following this guide http://sanfranciscoa...i-zte-crescent/
on windows

adb should work on the Pi as well

No, still not working.  I had installed the google driver and a crescent initially and now the link you gave me but still no adb, same error device not found.. Path variables appear to be ok so I think it's the driver.

[gbosh]

Do you have ClockWorkMod, if yes try to install another ROM like CM7 and see if the bug is stilol there

[Thomas J Marshall]

gbosh, on 06 February 2013 - 09:00 PM, said:

Do you have ClockWorkMod, if yes try to install another ROM like CM7 and see if the bug is stilol there

Yes, i was thinking of installing fish n chips anyway, just to see.  I'm not particularly savvy with flashing roms, I follow the instructions on the forums, so I just want to check - I have clockwork mod so if I change roms will clockwork be available on the new rom?

I think the problem must have arose from something i installed since it worked for over a year.  However, although I re-flashed my original rom the problem was still there so it must be something else.  I did read somewhere about a port 5580 that android uses so i fixed that in the forewall but it made no difference.

[dodgetimmy]

What size apps are you testing with?

What tpt/cwm version did you flash?

I had the same error and it was because I was downloading an app larger than the cache size of the tpt I chose. Since there are cwms on here containing tpts with only 2mb cache maybe it's the same for you?

Seems to be a recent change to the play store though. I can't recall having the error before now.