Home of Fresh Rom for Sprint Evo 3D, Evo 4g, & Evo Shift — Geek For Me
Download: Fresh Pre-Kitchen 0.1 (beta) – Updated 12/28
It is Christmas day and I’m finally releasing it… the fresh pre-kitchen beta by flipz!!
But what is a (pre-)kitchen you ask? A kitchen is a program that allows you to take a base of a rom and basically build it how you want it so that you get a nice custom rom suited to you. Well this application isn’t quite there yet which is why I am calling it a pre-kitchen, making it version 0.1, and labeling it a beta. This is a work in progress… a proof of concept. It is taking all of the individual things that make a kitchen and building them one piece at a time, until finally we have a full working visual kitchen for Android!
This version has been replaced with Fresh Pre-Kitchen 0.2 – Click Here
This is a public beta. There will be bugs. There will be problems. Please come report them so that I can track issues but don’t come here complaining that it just doesn’t work and is crap. Nothing that this program does should cause any real damage to your phone (like brick it) however it is beta so use it safely. If you are reporting an issue then please tell me what happened, what OS you are running, what you were trying to do, and any error codes you may have. This is a windows only application.
FEATURES:
- Auto-rooter (use with caution)
- Stock application installer
- Added Sprint Navigation and HTC Location Service
- Stock application UNinstaller
- Theme installer
- Bootscreen installer
- Create and restore nandroid backups
- Backup and delete custom dictionary
- Backup and delete all text messages
- Clear cache
- Clear lockscreen wallpaper cache (the one that prevented the totally clear lockscreen from working after picking a custom wallpaper)
- Reboot, reboot to recovery, or power off.
Loading ...Known Issues:
- 12/28/09: A bug was found that seems to affect a number of users that prevented them from installing themes and boot screens. I have fixed the issue and released an update. Check the downloads below or click here for more information.
Download here: http://link.geekfor.me/kitchen01
MD5: 20db4ef3b865e9e581271673e02b9e0a
You may also need the 0.1b patch here: http://geekfor.me/known-issues/known-issues-resolved/unable-to-open-debug/
File is not hosted on this server.
Screen shots:
This entry was posted by flipz on December 25, 2009 at 4:55 am, and is filed under Android 1.5, Kitchen. Follow any responses to this post through RSS 2.0.Responses are currently closed, but you can trackback from your own site.
-
#2 written by diesel joe 2 years ago
-
#3 written by crunchybutternut 2 years ago
-
#4 written by Negrito 2 years ago
-
#5 written by Vince 2 years ago
Nice job man! Im having issues with installing the boot screen…Here is a link of my error…
http://i49.tinypic.com/zy7axf.jpg
Like or Dislike:
0 
0-
#6 written by flipz 2 years ago
Thanks for the screen shot, that always makes it easy! So basically that error doesn’t necessarily mean that it failed, it just means that it can’t read the debugger to know if it did or not. Did the boot screen work for you?
If not then send me the contents of this file: c:\folder-where-you-extracted-kitchen\adb\bootscreen-installer-debug.txt
Like or Dislike:
0 0-
#7 written by Vince 2 years ago
This is what I got…
The system cannot find the file specified.
error: device not found
error: device not found
error: device not found
error: device not foundNow at first I didnt read that it needed to be on Fresh 1.0. So I flashed it to Fresh 1.0, but it still didnt work. I also tried to uninstall the apps part and it said the files were read only. The Uninstaller debug file is empty…weird.
Like or Dislike:
0 0
-
-
-
#8 written by flipz 2 years ago
This is what I got…
The system cannot find the file specified.
error: device not found
error: device not found
error: device not found
error: device not foundNow at first I didnt read that it needed to be on Fresh 1.0. So I flashed it to Fresh 1.0, but it still didnt work. I also tried to uninstall the apps part and it said the files were read only. The Uninstaller debug file is empty…weird.
That is showing that it’s not connecting to your phone at all. Device not found means that adb doesn’t see your phone.
You need to turn on USB debugging on your phone (settings < applications < development < usb debugging) and also make sure you don’t have any missing drivers in device manager once you turn it on.
Like or Dislike:
0 0 -
#9 written by Brandon 2 years ago
Flipz I am also having the same issue as Vince
http://i49.tinypic.com/zy7axf.jpg is exactly what I get
Freshrom 1.0 is present
USB Debugging IS enabled.
Devicer Manager shows no Exclamation or Question marks in relation to Drivers/Connected Hardware.Like or Dislike:
0 0-
#10 written by flipz 2 years ago
That error in itself isn’t necessarily bad. I programmed that in there just to show that the kitchen couldn’t tell you if there was an error or not.
Within c:\folder-where-kitchen-is\adb\ there will be a debug file for each thing you tried, and they should be closely named to what you did. So installing a theme would be theme-debug.txt. Installing a lockscreen should be lockscreen-debug.txt.
Can you copy/paste me the debug like Vince did? Thanks.
Like or Dislike:
0 0-
#11 written by Brandon 2 years ago
-
-
-
#12 written by Brandon 2 years ago
Ok. Due to other issues….I started from scratch. Unrooted with Official RUU. RE-rooted, and am now going to try again.
The Kitchen is extracted on my desktop.
USB is connected NOT mounted.
Trying to install Nexus One Boot Screen.
Device Rebooted instantly
————————
bootscreen-installer-debug reads:
The system cannot find the file specified.
push: .\temp\system\media\bootscreen/boot_bg.gif -> /system/media/bootscreen/boot_bg.gif
push: .\temp\system\media\bootscreen/boot_animation.xml -> /system/media/bootscreen/boot_animation.xml
push: .\temp\system\media\bootscreen/boot2.gif -> /system/media/bootscreen/boot2.gif
push: .\temp\system\media\bootscreen/boot1.gif -> /system/media/bootscreen/boot1.gif
cannot open ‘.\temp\system\media\bootscreen/boot1.gif’: No such file or directory
push: .\temp\system\media\bootscreen/boot.mp3 -> /system/media/bootscreen/boot.mp3
cannot open ‘.\temp\system\media\bootscreen/boot.mp3′: No such file or directory
5 files pushed. 0 files skipped.
1382 KB/s (1350486 bytes in 0.954s)Boot Screen did NOT install.
I got a HUGE Microsoft.net Framework “unhandled exeption” error. I will post that in a separate reply.
Like or Dislike:
0 0 -
#13 written by Brandon 2 years ago
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.IO.IOException: The process cannot access the file ‘boot2.gif’ because it is being used by another process.
at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive)
at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive)
at freshkitchen.tools.bootscreen_installer()
at freshkitchen.previewbootscreen.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
—————————————-
fresh pre-kitchen
Assembly Version: 0.1.0.0
Win32 Version: 0.1.0.0
CodeBase: file:///C:/Users/Family/Desktop/fresh-pre-kitchen-0.1/fresh%20pre-kitchen.exe
—————————————-
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
—————————————-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
—————————————-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Like or Dislike:
0 0 -
#14 written by Brandon 2 years ago
-
#15 written by flipz 2 years ago
You still didn’t answer what OS you are on.
So it is seeing your phone and working fine there. The error you are getting is that after extracting the files, your computer is locking them and it can’t read them. It seems like 1 in 10 people have this problem and I’ve yet to figure out why.
Thanks for all the details. Let me know your OS and we’ll go from there. Also if you are on gtalk then please use the “contact me” above and send me your name. Let me know who you are when you do.
Like or Dislike:
0 0-
#16 written by Brandon 2 years ago
-
-
-
#17 written by Cypher 2 years ago
Hey, the kitchen is looking great and everything seems to work except for the bootscreen installer, for me. I’m getting that same error of The installer was unable to open the debug to determine if it was installed thing.
My bootscreen-installer-debug just reads “The system cannot find the file specified.” and I’m running Windows XP. I had usb debugging on and such.
This might just be a repeat of previous information you’ve been given, but it’s all the information you’re asking for together, so I thought I’d just post it anyways.
Like or Dislike:
0 0-
#18 written by flipz 2 years ago
-
-
#19 written by Cypher 2 years ago
-
#20 written by dieseljoe 2 years ago
I get the same error message as Vince but my phone is recognized. And it won’t install the theme. I restored my phone back to stock ruu. Then tried the auto rooter and it worked fine. I can add and remove apps. Just not themes. Cleared cache to. I am using windows xp. I am going to retry later and I will send screen shots if it keeps up.
Like or Dislike:
0 0-
#21 written by flipz 2 years ago
-
-
#22 written by Vince 2 years ago
Vince:
This is what I got…The system cannot find the file specified.error: device not founderror: device not founderror: device not founderror: device not found
Now at first I didnt read that it needed to be on Fresh 1.0. So I flashed it to Fresh 1.0, but it still didnt work. I also tried to uninstall the apps part and it said the files were read only. The Uninstaller debug file is empty…weird.That is showing that it’s not connecting to your phone at all. Device not found means that adb doesn’t see your phone.
You need to turn on USB debugging on your phone (settings < applications < development < usb debugging) and also make sure you don’t have any missing drivers in device manager once you turn it on.Problem with that dude, is it is connecting to my phone. I ran adb devices on the CLI and it showed my phone. In fact, the first thing I thought was that debugging wasnt turned on. It was turned on so I tried again and got the same error. I flashed Fresh on it thinking that was it and nope, got the same error.
Like or Dislike:
0 0-
#23 written by Brandon 2 years ago
Same here. Again I am using Windows 7, instead of XP but other than that me and Vince have the same thing going on. Flipz I sent you a message on the contact page to add me to GTalk Would love to help you sort this thing out. I even have an extra PC to play with different OS’s, Settings, etc.
Vince your welcome to chat with me as well if you like just let me know.Like or Dislike:
0 0
-
-
#24 written by Vince 2 years ago
Ok, so I decided to try installing the boot screen one more time…This time I reinstalled Fresh and made sure my phone was connected via adb devices in the CLI. It was showing so I unchecked debugging and re-checked. I then installed Peep and it worked. Then I tried the boot screen and it FREAKIN WORKED!! I couldnt believe it. LOL Not sure why it worked, but it did.
Like or Dislike:
0 0-
#25 written by flipz 2 years ago
-
-
#26 written by Gui 2 years ago
Hello. I have a few questions about the pre-kitchen:
- Will my sense look and work just as if it was not rooted?
- Is there an apps-to-sd functionality available?
- Will I be able to update to Android 2.1 once Sprint makes it available?
- Is there a way to go back (unroot), if I decide to do it later?
- Will I need to reinstall any apps after I finish the process? Or will my phone be exactly the same (but rooted) afterward?Thanks a lot!
Like or Dislike:
0 0-
#27 written by flipz 2 years ago
Well the pre-kitchen is really more so designed to help you customize fresh rom, which you would have already installed. I’ll try to answer your questions both ways though.
-Sense will look and work the same rooted or unrooted, unless you decide to use a theme that modifies it.
-Apps2sd is integrated in to Fresh 1.0. If you have your sd card partitioned properly for it then it will automatically run.
-My assumption is the 2.1 update will be done via an RUU update just like when they did official winmo updates. If it doesn’t work right away I can assure you that we’ll make it work. I had the 1.56 update ready within an hour of it hitting the wild.
-You can go back to stock using the current 1.29 RUU from Sprint. If your phone came with 1.56 then that RUU won’t work for you, but I’m testing out some fixes.
-Your applications are untouched when rooting. They are also generally untouched when installing a rom. But things happen. After rooting and installing RA’s recovery image you will be able to create a nandroid backup.Like or Dislike:
0 0
-
-
#28 written by flipz 2 years ago
Will someone out there that is getting the “unable to open the debug” error try something for me? Or if a few of you could do this that are seeing this problem I appreciate it. We need to figure out what’s locking the files. I can’t duplicate this problem.
1) Download process monitor: [url]http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx[/url] and run it
2) Run the kitchen and try to install a bootscreen or theme and wait for the error that says it can’t read the debug. Once you pops up don’t click ok… just leave it.
3) Click on the little binoculars on the title bar in process explorer, it will allow you to search for opened items. If you tried a bootscreen you want to search for “bootscreen-installer-debug.txt” if you tried a theme then you need to search for “theme-debug.txt”
4) Once you search it will display in the very first column what program is actually locking the file. Please let me know what it says! Thanks.If it shows up as “non-existent process” (helpful, right??) then you’ll also need to do the following:
1) Open windows task manager (control + alt + delete)
2) Click on View < Select Columbs < PID
3) Click on processes tab and then sort by the PID column and find the PID that process monitor gave you earlier. Task manager will then show you what the process is.Make sure to tell me what OS you are on when you post your info.
As for those of you getting the file not found errors in debug, I’m still working on finding the cause of that. I think I have an idea.
Like or Dislike:
0 0 -
#29 written by jt128 2 years ago
-
#30 written by flipz 2 years ago
-
-
#31 written by flipz 2 years ago
Bug resolved.
http://geekfor.me/known-issues/known-issues-resolved/unable-to-open-debug/
Like or Dislike:
0 0 -
#32 written by Vince 2 years ago
flipz:
Well the pre-kitchen is really more so designed to help you customize fresh rom, which you would have already installed. I’ll try to answer your questions both ways though.
-Sense will look and work the same rooted or unrooted, unless you decide to use a theme that modifies it.-Apps2sd is integrated in to Fresh 1.0. If you have your sd card partitioned properly for it then it will automatically run.-My assumption is the 2.1 update will be done via an RUU update just like when they did official winmo updates. If it doesn’t work right away I can assure you that we’ll make it work. I had the 1.56 update ready within an hour of it hitting the wild.-You can go back to stock using the current 1.29 RUU from Sprint. If your phone came with 1.56 then that RUU won’t work for you, but I’m testing out some fixes.-Your applications are untouched when rooting. They are also generally untouched when installing a rom. But things happen. After rooting and installing RA’s recovery image you will be able to create a nandroid backup.Hey, on that Apps2SD, how do I format my card?
Like or Dislike:
0 0-
#33 written by flipz 2 years ago
-
#34 written by Vince 2 years ago
-
#35 written by flipz 2 years ago
Since you have such a large card, that’s fine. But really the swap can be much smaller… like 32mb. I thought that RA had defaults in there automatically. The “norm” is 512mb for ext2 but you have a larger card so 1gb is good.
Make sure you go back and convert ext2 to ext3. It will help prevent errors later on that can be caused when the phone doesn’t turn off or reboot properly.
Like or Dislike:
0 0
-
-
-
-
#36 written by dieseljoe 2 years ago
-
#37 written by superlinkx 2 years ago
Not sure if anyone else has noticed it, but when I run the auto rooter after flashing the ruu, it has trouble. It goes a few lines, then says invalid syntax. Then it goes for a few more lines, then says _image is not a recognizable command. Does two more lines and is done.
Then I check and it is not rooted. I tried rooting manually, then ran the auto rooter to get the recovery image easier. It ran, then gave about 15 memory errors. After that, it no longer would reboot to recovery, I had to pull the battery everytime I tried. I have Win 7 64-bit. Also, I manually got 1.2.3.img to flash correctly, then used auto rooter to get 1.5.2 flashed, and it seemed to work fine. It now shows up as 1.5.2. Hope that’s enough info.
Thanks for the kitchen! Other than the auto root bugs, everything is working awesome! Flipz is the best dev ever! I’ve been playing with various themes, its great!
Like or Dislike:
0 0-
#38 written by flipz 2 years ago
I was able to run the auto rooter on windows 7 64 bit with no issues after using the RUU.
I am working on some timing issues with the auto-rooter which will help with it sending the files over to the phone.
The “memory” errors that you received are actually kind of “normal”. It just happens sometimes when flashing the recovery.img, even if you are doing it manually. It has to do with the limited partition size that the recovery.img is allowed to have. About 90% of the time even though you see errors it still worked. In your case it sounds like it didn’t, so then all you have to do is go back and try again.
It’s strange that you were getting the “_image is not a recognizable command” error, but then after you got 1.2.3 on there it worked fine for you to flash 1.5.2. I have only seen 3 other people with that error. It is only on windows 7 machines and seems to be related to some type of registry tweak.
Basically what’s happening is the auto-rooter is just mimicking you typing on your keyboard. On some very random windows 7 computers it’s like it won’t kick in to gear until it gets a non-A-Z character. This is completely independent of the phone and has something to do with Windows.
You didn’t change anything between the first time you ran it and the second? Did you reboot your computer or anything like that?
Thanks for the feedback.
Like or Dislike:
0 0
-
-
#39 written by Jamie 2 years ago
Could I recommend that instead of shipping this with the HTC and Sprint copyrighted apps, you provide a script to pull them out of the phone (or rom.zip). That way you don’t run the risk of HTC or Sprint issuing a C&D? Just a thought, but I’m sure they wouldn’t like you distributing their apps.
Great work so far!
Like or Dislike:
0 0 -
#40 written by Victor 2 years ago
-
#41 written by flipz 2 years ago
-
#42 written by Victor 2 years ago
Hmm.. so I re-ran the root and I got the console to come up but only once – I keep trying to remove apps via the Fresh program and it seems like it just reboots the phone and I still have the apps I wanted removed.
Sorry – very new to the root but I am an IT pro so I get things pretty quickly.Like or Dislike:
0 0-
#43 written by flipz 2 years ago
There was a bug I found and fixed in 0.1b with the theme installer where some computers didn’t recognize that the command prompt was still open so the kitchen just kept going without waiting. It’s likely the same bug. I’m working on changing the code throughout the whole kitchen. Sorry about that.
Like or Dislike:
0 0-
#44 written by Victor 2 years ago
-
-
-
-
-
#45 written by Victor 2 years ago
-
#46 written by Tyler 2 years ago
Ok. Sorry for being such a noob. I’ve never tried to root a phone before and I’m so ridiculously frustrated. When using the auto-rooter, before it goes to the command prompt I get this error message–> The auto-rooter has attempted to read the debug to make sure that step 1 completed successfully, however it failed to open the file on your computer. Just click OK to continue. The rooting may or may not work. After the cmd prompt finishes my phone gets an exclamation mark and a lil dead phone under it on the screen. A battery pull fixes this, but still no root for me. Please help this is driving me nuts. I have my phone in debug and I have sync on my PC.
Like or Dislike:
0 0-
#47 written by flipz 2 years ago
(copy and paste from a few comments up. don’t take offense to that, I haven’t posted it as a known issue yet).
There was a bug I found and fixed in 0.1b with the theme installer where some computers didn’t recognize that the command prompt was still open so the kitchen just kept going without waiting. It’s likely the same bug. I’m working on changing the code throughout the whole kitchen. Sorry about that.
Like or Dislike:
0 0
-
-
#48 written by Tyler 2 years ago
-
#49 written by flipz 2 years ago
-
-
#50 written by Ben 2 years ago
-
Comments are closed
- Apps2SD – Android Central Forums
- Root or not to root – Android Central Forums
- electronic drop bolt lock security door lock
- is sound realistic and that girl realy know to express love in words
- kuchyne
- aquasana aq-4100
Didn't find any related posts :(
Thanks for the Christmas gift Flipz
Like or Dislike:
0 
0