Resolved

Issue: When trying to install a theme or boot screen you receive a pop-up message error that says it’s unable to open the debug to tell you if the install failed. Additionally, the process does actually fail. It doesn’t successfully install the theme or boot screen on to your phone.

Cause: It took me a bit to track this down. I want to thank 702droid for letting me remotely connect to his computer and test it out because I was never able to duplicate the problem on my computer. When the kitchen is installing a theme or boot screen it opens an adb shell to do the work, and then waits for it to close when it’s done. For some reason on some computers when you launch adb shell it actually opens a second copy and does the work there. This confused the kitchen and it thought that adb was done so it continued on which caused the whole process to fail. You will now see a new message box that pops up telling you to hit ok after the phone reboots.

Resolved: I have released 0.1b of the toolbox to fix this issue. It is only the toolbox so you will still need to download 0.1 if you don’t have it already. Just extract this to where you have 0.1 and overwrite the exe that is already there. If your computer was not suffering from this issue then you don’t need to worry about getting this update, however I will be including it in 0.2, whenever that gets released.

DOWNLOAD UPDATE: http://link.geekfor.me/kitchen01b

Issue: After playing with the 2.1 beta and then coming back to Fresh 1.0 some items aren’t showing up in your market.

Cause: My theory on what was causing this was that the market is some how cached on your google account and tied to it. We had a similar issue when Sprint released the 1.56MR update. Protected apps weren’t showing up. This theory was confirmed by dreamphyre when he created a new google account and was able to see the apps again.

Workaround: The only known workaround is to wait until they show up again (it is unknown how to force it to refresh) or create a second “test” google account that you use. There isn’t anything that I can do to fix this issue because it has nothing to do with the phone.

Resolved: We figured out a while ago that my theory on the cause as stated above is correct. Something gets cached on google’s end and the apps get locked out. Thanks to zippy-man on xda we now have a (long but) working fix. Here is a copy/paste of his fix.

1. Download the AOSP 1.6 build HERE put that onto your sd card in the root directory
2. Boot into recovery and NANDROID backup
3. Now Wipe Device
4. Now install the zip from the sdcard and once finished reboot
5. Download Googlebit HERE
6. unarchive google bits to c:\android-sdk-windows\tools
7. open a command prompt
8. cd c:\android-sdk-windows\tools
   adb remount
   adb push system/framework /system/framework
   adb push system/etc/permissions /system/etc/permissions
   adb push system/app /system/app
   adb reboot
9. Setup Market with your not working account (the one that we need to work on 1.5)
10. Download and install a copy protected app (like Twidroid Free)
11. Boot back into Recovery
12. Wipe Device
13. Now restore your nandroid backup of 1.5 Cupcake
14. Reboot phone and goto market let twidroid re-install if it tries to and do not interupt
15. Manually Reboot phone

Now the copy protected apps should be showing again.

Your previous downloaded apps might not show in downloads anymore but wait a while and they will all come back

Mine is now working perfect.