Related
TEST version 1.4 goes public
1.4.test8http://forum.xda-developers.com/showpost.php?p=4836277&postcount=997 - new style SYS tree + COMPLETE 23081 0409 ALL-DPI ALL-RES package! - DELETE msvcr71.dll IN TOOLS FOLDER!
1.4.test7 - only few bugfixes, somewhere lost around pages 95 - 100?
1.4.test6 - Fixed all not-working devices. UPDATE TO .test5 AND IMPLANTXIP FIRST!
1.4.test5 - OVERWRITE YOUR TOOLS FOLDER! + implantxip from this post, otherwise XIP won't implement and ROM woudln't boot!! SELECT DEVICE ONLY KAISER, ALL OTHER WILL CRASH!!
1.4.test4 - OVERWRITE YOUR TOOLS FOLDER!
1.4.test3
1.4.test2
1.4.test (always crashes, don't use it for cooking!)
osKitchen (aka fe~ROM kitchen)
Hello ladies,
I’m too lazy to do many things manually so I build a new kitchen for us. I must thank to TPC for using his .bat (hardcoded into kitchen) and ervius for idea.
It is much simplier than Erviuse’s kitchen. I use external tools from TPC’s kitchen so if crashes any of these tools, it’s not my fault, I just cooked with it and flashed and it works fine if you don’t create crash fault manually. I’ve been writing this first release few hours and it has about 1000 lines of code lol.
Save & Load works as expected, saves everything (you shouldn't modify saved file by yourself).
If you don't know what something does in "More tweaks" menu, just don't touch it and leave it as was default!
What you need: patience and .NET Framework 3.5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Kitchen with 23009 SYS&XIP and TPC's EXT, ver 1.0.3b My Server [CZE] | 4Shared
Kitchen without SYS XIP EXT and OEM, but with all tools My Server [CZE] | 4Shared
Current updates:
I usually do updates WITH Tools and Kitchen folders to ensure you have it complete so update it too!
1.0.3b -> 1.0.8 My Server [CZE] | 4Shared
1.0.8 -> 1.0.9 My Server [CZE] - Only new .exe, make sure you have updated to 1.0.8 first!
!! THERE WILL BE NO MORE UPDATES TO 1.0.x VERSION, I'M NOW FOCUSING ON 1.4 FINAL!!
SYS&XIP updates:
23016 WWE (0409) - SYS&XIP
23028 WWE (0409) - SYS&XIP - not 100% done, but pretty usable
23034 WWE (0409) - SYS&XIP - nice new UI changes (Start moved down etc), FAST, smooth
All SYS&XIP updates unpack into Sources folder
OLD updates: only for history purpose
4Shared | my server [CZE]
Kitchen with 23009 SYS&XIP: 4Shared | my server [CZE]
Updates (rollup, so you just only download latest .exe and overwrite the old one):
1.0.1 4Shared
1.0.2 My Server testing build
1.0.3 4Shared also testing build
1.0.4 4Shared
1.0.5 4Shared | My Server [CZE]
1.0.6 4Shared | My Server [CZE]
1.0.7 My Server [CZE]
WORKS ONLY ON 1.0.x RELEASES ONLY AND 1.4.test TILL 1.4.test8! Watch 1.4.test8 version post for details about NEW tree structure.
Tree structure:
I wanted to have main kitchen root as clean as possible so I moved all things to Source directory.
- In Source directory, there is few folders. The ones starting with _ you don’t have to pay attention on them, or better, don’t touch them at all unless you know what you are doing!
- In folder EXT are four folders: Apps, Fixes, Settings and SYSpkgs. What’s the difference between them? Actually none. In all of them you put EXT packages as you’re used from TPC’s kitchen (app.dat, app.reg and files folder). The only difference is that they show themselves in different tabs in kitchen so you don’t mess different settings with applications etc.
- In folder MSXIPKernel always create numbered folder with XIP version, like 23009 and copy all folders and files from MSXIPKernel you get (busenum.dll etc).
- Into OEM you put your OEM folder with folders like OEM_Drivers
- ROM folder you don’t have to touch on it unless you know what you’re doing – it’s already preset by TPC’s kitchen.
- And into SYS you put, just like in MSXIPKernel folder, numbered folder with build # and inside you place all SYS packages (Base, ConfettiCore, etc)
In the main root are also folders Projects that you can save your projects into, Tools which contains all tools needed to cook so don’t touch it too. Folder „build“ should remove itself after finished cooking. If it doesn’t (like crash etc) you can delete it manually. In FLASH folder (that creates only after cooking) should be only CustomKaisRUU.exe and RUU_Signed.nbh, or you can delete it too – RUU is copied from Source directory and NBH is cooked.
There also might be some other folders, "working" directory is for extracting NBH file (you can delete it if is not kitchen running) or Kitchen folder (new since 1.0.7) - it contains support things to kitchen like tutorials, icons and other material. You shouldn't touch it too.
Examples:
EXT apps directory:
MSXIPKernel:
OEM folder:
SYS folder:
Questions & Answers:
Q: What’s the difference in Device between Kaiser and Tilt?
A: When selected Tilt, keyboard patch is automatically added.
Q: LZX or XPR?
A: LZX saves space, but takes longer to build.
Q: UPX on EXT?
A: Saves space by compressing all EXE files in EXT directory with UPX compression.
Q: SuperRAM?
A: Only switches between nk.exe’s with 79M/85M/101M (and automatically adds MEMFIX).
TIP: You don’t have to manually change always in OEM\OEMVERSION that one .provxml, if you fill it in kitchen it gets created automatically.
Tutorials & Tips
Moved to kitchen Tutorials!
User tips and tutorials:
witschey - Adding HTC StartUp animation with system backup
witschey - Fixing HTC Startup sound
OndraSter - Porting new SYS and XIP to kitchen (valid for version till 1.4.test6)
Changelog
Kitchen 1.4.test2
- Added X button to selecting splash and welcomehead to clean it
- Added option to cook-in radio
- Now you can change cook button name to anything you want in Kitchen\settings.dat (if it doesn't exist, it is created)
- Dropped autoupdate function (I wasn't generating it for download anyway)
- Fixed that public release didn't had Tools update (I'm not allowed yet to publish it) so it crashed when copying Tools
- Now when copying files application doesn't look frozen, you can even select and copy text in cooking log
Kitchen 1.4.test
- Instead of opening windows, everything goes to logs
- No windows will open when cooking (except HTC Rom Tool and XVI since they're not console-only)
- Added new tab with cooking log
- Many more minor changes
- first preparations for more devices support
Kitchen 1.0.9 - last one before new minor build
- Now able to cook for different LOCALEs than 0409 (make sure you swap all folders with your LOCALE ones)
- Platformrebuilder does output to log.txt file in root of the kitchen, but still has opened black window, just ignore it
- Some anticrash fixes
- Etc...
Kitchen 1.0.8
- Added option (into More Tweaks menu) to insert welcomehead and splash images
- Fixed sometimes failing to copy htcrtproj file, or any other file into FLASH folder
Kitchen 1.0.7
- Added new feature - Tutorials section. Who has any tips what I should write about, write me PM or here to this thread.
- I've written few FAQs I've seen around
- Also disabled DEBUG mode in extracting nbh
- Added update option to update kitchen itself from internet
Kitchen 1.0.6
- Fixed after extracting RUU_Signed deleting "working" directory
- Now you must first close all menu's till able to do anything in main window (just for causion)
- Fixed "relly" to "really" when closing main window (exitting program) by ESC key
Kitchen 1.0.5
- Now you can convert complete OEM folder from different QVGA device (like HTC MEGA) to your EXT by one click, converts all PACKAGE* folders
- I forgot to update version, sorry for that
Kitchen 1.0.4
- Now you can export RUU_Signed.nbh into OEM, SYS and ROM folders - it doesn't work with cooked NBH's, only shipped ones
Kitchen 1.0.3b
- Only graphical changes, fixed last ESC/Enter keys action
- When clicked Quit, you must confirm it
Kitchen 1.0.3 - test build
- Improved stability when trying to overwrite files/folders that already exists
- Added scrollbars to selecting tabs (they we're out of display)
- Fixed crashing when OS.nb building has failed
- Added "Convert SYS to SYSpkg" for easy removing (I like having few SYS folders converted to EXT so I can easily find them)
- Removed unescessary buttons from dialogs
- Disabled resization, add ESC key actions in menus
- When upgrading, update Tools folder with enclosed recmod!
Kitchen 1.0.2 - test build
- Some fixes
- Added new "Convert OEM to EXT and place it" feature
Kitchen 1.0.1
- Added advanced tweaks (AKU, IdentName & IdentDesc, Calibration Data, Enable/disable welcome screen, Hide "Beam", ...)
- Changed COOK button
- Fixed "XDA Thread" link in About menu
Requests awaiting to be done: (my TODO)
- Could add the option to view files in the folders duplicates kitchen before you start the process of cooking the rom? To correct any error overwriting files before the cooking process.
- Add tab for adding easy registry stuff
- "When disabled Base package, disable DPI etc folders too" - done in latest .test8 version
- Extendir integration support
- Change a bit "Disable Customer Feedback" function detail
Donators:
Twopumpchump - $20
Witschey - $20
af974 - $20
aaraya1516 - $5
luiggi - $10
wbrown5 - $20
swiss240 - $10
Thank you all, every dollar counts!
Looks like its inbetween ervius and bepe kitchen. Will give it a whirl. Thanks bud.
Edit...
Runs ok, I tried to change EXT folders name, and it didnt like it. I prefer to have my own folder names, so that I know what I have in them!
In vista, it keeps poping up should kitchen run imgfs files! It doesnt do that in ervius for joshs kitchen in vista. So I am thinking there is a security thing maybe!?
All in all, good work, I always love GUI stuff!
OndraSter said:
fe~ROM kitchen
**** ME
Click to expand...
Click to collapse
Joking aside, this seems like a good kitchen. Thank you.
Quetzecotyl said:
Click to expand...
Click to collapse
Yea I dont like that "**** Me" too! LOL
**** ME will be added as Option. (and more things I will add like AKU and such).
This kitchen doesn't want to be like Erviuse's one - I want to make this directly for Kaiser and integrate different predefined tweaks etc. Only get them together will take some time.
OndraSter said:
**** ME will be added as Option. (and more things I will add like AKU and such).
This kitchen doesn't want to be like Erviuse's one - I want to make this directly for Kaiser and integrate different predefined tweaks etc. Only get them together will take some time.
Click to expand...
Click to collapse
I love the GUI. So good work there.
nice work brother, will download and try it out, i did bookmark this thread so i hope that you will keep interest with this and keep it up to date (as needed)
I've been working on some new features and I thought "Hey, I might integrate few tweaks I use".
What about this? More comming.
Also I was thinking of easy "buttons" changer (hold voice button/press voice button etc).
PS: I know that it doesn't support resizing/maximizing window, I will disable both of it.
PPS: **** ME! no more, back to COOK IT
OndraSter said:
I've been working on some new features and I thought "Hey, I might integrate few tweaks I use".
What about this? More comming.
Also I was thinking of easy "buttons" changer (hold voice button/press voice button etc).
PS: I know that it doesn't support resizing/maximizing window, I will disable both of it.
PPS: **** ME! no more, back to COOK IT
Click to expand...
Click to collapse
lol i just got the old one downloaded, but VERY nice brother
I nearly wet myself when I saw the **** ME button... LOL
Latest tweaks update till I release it:
+ it asks after ROM build whether you want to run KaiserCustomRUU.exe and flash it immediatily.
I'll upload it in the morning with clear head, now I'm gonna go sleep. Gnight ladies.
OndraSter said:
Latest tweaks update till I release it:
+ it asks after ROM build whether you want to run KaiserCustomRUU.exe and flash it immediatily.
I'll upload it in the morning with clear head, now I'm gonna go sleep. Gnight ladies.
Click to expand...
Click to collapse
lmao nite mommy
Looks good! Just dont make it too complicated!
OK, here we go: http://www.4shared.com/file/120731385/d9575efd/osKitchen_101.html
Replace the original .exe with this one, saved sessions are compatible (and always will be) on both ways.
is there anyway of using this in vista?
SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
Quick Links
FAQ
Installation Walkthrough
Kitchen Usage Walkthrough
Change Log and Known Bugs
Download Links
**Warning**
Before using this kitchen, you MUST read the walkthrough. Any questions that have been answered there and in the FAQ will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on ervius's excellent Visual Kitchen.
Features
A completely stripped ROM. All the files have been categorized in order to remake packages of all the programs that come stock on the HTC ROM.
LZX and XPR compression
6.1 and 6.5 support
Auto XIP and SYS porting
Auto ULDR removal (Gain 3mb of storage.)
Auto NBH packing
Auto Flashing (for testing your ROM before it's released to the wild)
Simplified structure. Click on RunMe to run and Support for support
Script to convert old OEM packages to new EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Script for auto UPX compression of EXT folders
Script for auto compression of all PNG's in the kitchen
Save custom ROM settings (for cooks for multiple ROMs)
And more!
Builds included
21054 - WM6.1
21869 - WM6.5 with older GUI - Newer internal code - COM2 branch 23071 - WM6.5 with new redesigned GUI - COM3 branch
This is now an ENGLISH only kitchen. It is just too hard to keep up with 13 different languages! If anyone is interested in taking over the other languages, please let me know.
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
FAQ
FAQ
Q: Can you get me package YYYY?
A: No. I will provide packages as I create them. I will not take requests. It takes a LOT of time to make a package, especially when I'm making it for 13+ languages. It takes a long time to find the corresponding packages or to create them from scratch.
Q: Will this work on my [Insert device other than Herald/Wing]?
A: Not, yet. That is why it's posted on the Herald forum.
Q: Will I be able to recreate JustHome or JustStable with this kitchen?
A: No. This is a completely new base. I made this kitchen and these ROM base from scratch.
Q: Will you personally teach me how to....?
A: No.
Q: My phone won't boot after flashing your ROM!
A: You disabled something you needed. Keep track of what you disable and then reenable the stuff that you need.
Q: My phone is bricked!
A: You didn't follow the instructions!
Q: When I use this, I get an error.
A: You didn't follow the instructions!
Q: How do I flash this?
A: It's not a ROM.
Q: How do I flash a ROM I make with this?
A: You must know how to flash before you use this. You must know how to recover from a bad flash. You must know the difference between USPL and HardSPL. You must know how to flash through the SD if needed.
Q: Will this work with Windows XP, Vista or 7?
A: All of the above. Just remember to follow the install instructions.
Walkthrough
Installation:
Step 1
Download the newest build from the download links.
Step 2
Extract the SuperJustKitchen folder into c:\kitchens\
Now you should have c:\kitchens\SuperJustKitchen\RunMe
Step 3 (Optional)
Extract the SuperJustKitchen shortcut into your desktop.
Step 4(Vista and Windows 7 only)
Go to your Start Menu and then click on Start Search or RUN.
Type in "c:\kitchens\SuperJustKitchen\Working_Folder\" without the quotation marks and press Enter.
Right click on erviuskitchen and click on properties.
Click on the Compatibility tab.
Place a check mark on Run this program as an administrator.
Press ok.
Change Logs and Bug Reports
Known Bugs
23047
No known bugs
21864
No known bugs
21064
Older Arcsoft don't work with this
All builds
No known bugs
******************************
Change Log
Unreleased
To-do for Future Release
Info ported to Herald
Info integrated into kitchen support script
Enhance kitchen support script to auto upload support information
Enhance support script to include system information
Enhance script to give option for kitchen host support and ROM/Device support
Add built in HardSPL installer (if you can use USPL, you can also HardSPL.)
Expand RunMe script to encompass support script and HardSPL.
Once info integration is completed, create script to auto detect incompatible phones
If phone is Herald and the IPL version is lower than 4.0, auto update IPL and SPL to newer IPL/SPL before automatically HardSPL'ing phone.
Include "restore to factory default" option. (Autodownload needed RUU from server, USPL into phone to override HardSPL.)
Indepth Cooking walkthrough to supplement kitchen walkthrough
Scripted installer with desktop shortcuts
Scripted Simple new build Port assistant
Much much more
Released
0.6
Cleaned up the Herald's initflashfiles and older packages (This fixes the double control panel icons.)
Ported 21869 and 23071
Cleaned up the Opal OEM a little.
Organized some EXT into categories. (This is still a work in progress.)
Starting with v0.6, I've created a script on my end that will automatically compress the kitchen and separate it into multiple parts:
SJK - The main kitchen files.
OPAL - The Opal files.
HERALD - The Herald files.
SYS - The Build files (Both SYS and XIP.)
EXT - The EXT files.
This should make it easier to update things from now on. I'm going to have scripts to only update certain things. This way, you should only need to download whatever has had the changes, instead of the whole kitchen. Later on, I hope to create an updater that will do these updates for you automatically. (At first, I won't be able to update the EXT without deleting any custom EXT's added by you, the user.)
0.5
English only support
MANY new EXT's (multiple versions for now)
Opal support
All EXT's are being categorized... work in progress
0.4
Added updated packages for the programs that are language agnostic.
Added 23060 and 23420 builds. Fixed their button issues by using 23053 to fill in the blanks. (230xx's are more stable, 234xx's are newer and have more features as well as more bugs.)
Added descriptions to every package (albeit, they're a little more technical that I wanted, but I got them straight from Da_G's mouth, so they're bound to be correct.)
0.3.1
I only left 3 builds. The newest 6.1, the newest 6.5 with the old gui and the newest 6.5 with the gui (23047, it's really nice!)
0.3
CABtoEXT - Thanks to Apreinchner - Update: Edited the script heavily (it went from 4 lines to 88 lines) in order to make it sort out and move all the newly created EXT's appropiately.
Ported 23034 all languages - even MORE gui changes!
Ported 23037 - stable
Ported 23409 - Again, MORE GUI changes! (A few bugs, though.)
Converted many of the problematic modules to files in the 23034
Change the all the languages' start menu on the 23034 build CPR to 4
Change ROM version to show that the ROM was built on SuperJustKitchen
Fix Adobe bug
Change ROM version to show that the ROM was built on SuperJustKitchen
Port other languages from 23031
Integrate Sort program into prepare structure - Script it
Presets for each build
Addition of 7 more languages?
Clean ROM more
0.2
Russian initflashfile.dat fixed - 6.5 start menu works fine now
Port 23028 0409 96dpi - deprecated
Change landscape mode in 21016 and 23028 to show 4 icons instead of 3
Script new EXT folder creation - extra buttons
Fix cab and sync bugs in 23016 and 23028
Port 21054 all languages (newest (and possibly the last) wm6.1)
Remove extra netcf's, extra dummy fwupdate, extra SQM's
6.5 compatible autorun
Port 23031 0409 96dpi
updated all language initflashfiles
Fixed issue with SMS on 6.5 builds
Fixed ActiveSync issues
Replace all start menu icons in all 6.5 in all languages with nicer ones
Empty folders disappearing fixed - different installer (placeholders fix it but some of those folders have to be empty...)
Remove compatibility for all other DPI's and resolutions other than 96dpi/320/340 for now to keep size down.
Remove compatibility with languages that aren't compatible with the Herald for now to keep size down.
0.1
Initial Release
Download Links
v0.4+
Just go to the new redesigned http://justkitchen.infoand click on the download section and then on the kitchen section.
v0.3.1
Version 0.3.1 is
SuperJustKitchen - With 21054(wm6.1), 23016(wm6.5), and 23047(wm6.5 with redesigned GUI.)
It's just one file with a ReadMe with instructions on how to install it.
v0.2
Version 0.2 is
SuperJustKitchen - With 21054(wm6.1), 23016(wm6.5), and 23031(wm6.5 with redesigned GUI.)
It's just one file with a ReadMe with instructions on how to install it.
v0.1
Version 0.1 was seperated into different pieces.
Main Kitchen Installer
SuperJustKitchen v0.1 - Alpha 1
Device Specific Installer
Herald
Build Installers
21051 - WM6.1
23016 - WM6.5 - Original WM6.5 interface
23022 - WM6.5 - The "new" WM6.5 finger-friendliness
EXT Installers
Non-DPI Specific EXT
Cooking Walkthrough
Cooking with SuperJustKitchen
*Warning: This is NOT a walkthrough on how to cook. It is a walkthrough on how to use this kitchen.*
The Layout
The Kitchen is stored in c:\kitchens\SuperJustKitchen\
To simply run the kitchen, double click on RunMe.
Advanced users: There will be a different walkthrough for you. (As far as how to add packages, builds, etc.)
The Usage
Once you doubleclick on RunMe, you will be greeted with the main kitchen window.
Here is a screenshot of the process. Use it to follow the steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 1 - Click on the Device drop down menu and choose Herald (Yes, even though it already says Herald.)
Step 2 - Click on the language drop down menu and choose your language. To find what the language codes mean, see the first page.
Step 3 - Choose a XIP.
Step 4 - Choose a matching SYS.
Step 5 - Make sure you enter a build number other than 2.00.00 in the field near these. Use 5.2.21051 or something similar instead. If not, the ROM will not flash.
Step 6 - Doubleclick on the packages that you want or don't want. (Green means enabled, gray disabled.)
Step 7 - If you want LZX compression, check the LZX Compression.
Step 8 - Click on create ROM.
Wait.
If you get any errors, you probably did not choose a build/language combination included. Look at the list of languages to see what I mean.
Credits
Credits
Ervius for his wonderful visual kitchen (you'll find a donation link for him under Working_Folder.)
HTC for making the HTC ROM
mrhayami for his brainstorming sessions with me to make the recursive scripts
Everyone else that I haven't mentioned
Advanced Tips and Tricks
Advanced Tips and Tricks
This section will detail both advanced cooking tips and advanced usage of my kitchen.
Kitchen structure:
If you notice, the structure of the kitchen is different from the old kitchens.
The only folders you need to worry about are the following:
Cooking Folders
EXT - This is where you would add new programs. EXT packages are similar to OEM packages, but they have a slightly different layout. They are processed by the kitchen after the OEM, so their settings are never overwritten by the stock settings of the base ROM.
OEM - You'll notice that within OEM, you have a HERALD folder. The reason being that this kitchen supports multiple devices at a time. Within the Herald folder, you'll notice several folders.
The .VM is used for memory mapping. DO NOT TOUCH THIS under ANY circumstance.
The COMMON folder where you would find most of the what you'd normally see in your old style OEM folder. (OEMAPPS, OEMDRIVERS, etc.)
Various folders named with 4 letters/numbers. These are language packs. They used to be part of the OEM folder but have been seperated to allow the kitchen to choose which language to cook more easily.
ROM - Inside you'll notice the following:
Device specific folder - Holds all the device specific XIP files/modules, including the nk (which is NOT a native 6.5 kernel.)
SHARED - Where the non-device specific parts go. This is what gets "ported" automatically by the kitchen. This makes it very simple to release upgrade ports to the kitchen.
SYS - The OS files. These are also divided by language, DPI and by resolution. (QVGA, SQVGA, WQVGA, VGA, etc etc) You will only be able to choose DPI's and resolutions compatible with your device.
Other folders:
RELEASE_Device - This is where your flashing software is and where the ROM ends up at in NBH format.
Prepare - I store things here for different reasons. At the moment, it holds the template for a 13 language EXT package.
Other features:
Extra buttons: Click this to access extra features.
The EXT version lets you choose between different EXT's compatible with different DPI's with the common ones (compatible with all DPI's) always displaying.
To be continued...
---Reserved---
Yep, still reserved.
It's still a work in progress, but I am ready for comments.
ivanmmj said:
It's still a work in progress, but I am ready for comments.
Click to expand...
Click to collapse
Commented. I'm trying it out now...figuring out how to work it.
Hah, love the FAQ
Question: For WM6.5 builds, do you have to check the Real WM 6.5 AKU box on the main kitchen screen? Or does it not matter? (I'll be finding out in a minute, anyways, lol)
i may have found a bug. I dont know remember the packages i chose but when it comes down to creating the rom i get a kitchen_build_rom.bat error. i dont get that anymore after altering the packages with HERALD, 409, EXT 0096, 96 DPI, dpi_96_resh_204_resv_320, 1.01.23016 ver., 23016 XIP, 23016 SYS.
Also, i havent been able to create a flash able rom yet. how do you reset the settings to default?
Edit: forgot to mention im on windows 7 build 7100. And yes i did do what was required on the 1st page.
I keep getting a file is corrupt error when I try to flash?
eichenberg said:
I keep getting a file is corrupt error when I try to flash?
Click to expand...
Click to collapse
Yo tambien.
The FAQ says that we didn't follow the instructions, lol.
My NBH is +50 MB, so idk what's the problem....hmm...
Wow works great! Im flashing through SD though. Just made a quick 6.5 build came out with 67.41 Storage and 25 ram
illconcepts said:
Wow works great! Im flashing through SD though. Just made a quick 6.5 build came out with 67.41 Storage and 25 ram
Click to expand...
Click to collapse
Yea, I think the .NBH files have to be over 50 MB in order to flash through PC. Anyone confirm that? (I'm trying out a 6.1 build, with the new Motorola homescreen, cuz it's sick)
ace10134 said:
Yea, I think the .NBH files have to be over 50 MB in order to flash through PC. Anyone confirm that? (I'm trying out a 6.1 build, with the new Motorola homescreen, cuz it's sick)
Click to expand...
Click to collapse
Let me know if you get that Moto home to auto start... im stumped.....
ace10134 said:
Hah, love the FAQ
Question: For WM6.5 builds, do you have to check the Real WM 6.5 AKU box on the main kitchen screen? Or does it not matter? (I'll be finding out in a minute, anyways, lol)
Click to expand...
Click to collapse
Do NOT check it. It will attempt to set all the modules to use another set of virtual memory that is not available to our NK.exe. It's only for originally 6.5 devices.
DestructDez1 said:
i may have found a bug. I dont know remember the packages i chose but when it comes down to creating the rom i get a kitchen_build_rom.bat error. i dont get that anymore after altering the packages with HERALD, 409, EXT 0096, 96 DPI, dpi_96_resh_204_resv_320, 1.01.23016 ver., 23016 XIP, 23016 SYS.
Also, i havent been able to create a flash able rom yet. how do you reset the settings to default?
Edit: forgot to mention im on windows 7 build 7100. And yes i did do what was required on the 1st page.
Click to expand...
Click to collapse
What was the error and what do you mean altering? I made this kitchen mostly on Windows 7 build 7100.
As far as default settings, I didn't include a default ROM. There are many things you should not disable if you want a booting ROM.
eichenberg said:
I keep getting a file is corrupt error when I try to flash?
Click to expand...
Click to collapse
If your ROM is smaller than 52100kb, then it has to be flashed through your SD card.
ace10134 said:
Yo tambien.
The FAQ says that we didn't follow the instructions, lol.
My NBH is +50 MB, so idk what's the problem....hmm...
Click to expand...
Click to collapse
How big is it? See above answer.
This kitchen is a continuation of the Nitrogenious kitchen released at XDA-devlopers.
Nothing has changed from the tools side, only subtle adaptations and altered content.
Thanks go to :
all the experts at XDA-developers (too many to list)
Nitrogenious for releasing his WM6 kitchen and the superb WM6 package contained therein.
The original kitchen is found here: http://forum.xda-developers.com/showpost.php?p=2150690&postcount=1
Mind that usage description has to be taken from there!
Cotulla for publishing the OMAP850_SDHC.dll that can handle SDHC cards and llnhhy for putting the crucial REG setting in his published package for the Tornado.
More details are discussed here: http://forum.xda-developers.com/showthread.php?t=576164
SGregory for revealing (at least I found it there) that "format BINFS" can actuall take a parameter that sizes the BINFS partition and thus opens the path to gain device storage space if the ROM gets smaller!
More details on saving space are outlined here: http://forum.xda-developers.com/showthread.php?t=491240
- Sir.B and geistteufel for the Squeezer batches for UPX. XDA-Develpoer threads are:
original: http://forum.xda-developers.com/showthread.php?t=481880 and post of geistteufel (the one used in this release): http://forum.xda-developers.com/showpost.php?p=3540501&postcount=92
Disclaimer:
This is for educational purposes only!
There will be no support for the published content!
Enjoy and contribute.
Warning:
Mind that from the "cooking" or "kitchen" point of view this is for sure an old base and possibly more elaborate tools and definitely newer OS versions exist. The produced files should not be able to "brick" your device if you correctly set the Image Name to "OS" in the last step of the cooking process. IPL or SPL should never be written unless you know exaclty what you do - the kitchen only cooks the OS part! Writing incorrect content to the IPL or SPL area will brick your device for sure, so be careful!
Motivation:
This effort was only done to get a running stable ROM with SDHC support included that occupies as little storage space as possible
still having mandatory elements on board
filling the remaining space with useful tools
Space saving strategies (order of benefit):
outsource parts to SD card where possible (.NET CF 3.5)
compress files (.exe and .dll) that are not stored as modules with UPX where function permitts.
remove files that are not needed for any function
remove media data (ringtones, pictures) and leave only the bare minimum
resize media data where possible to further decrease size
not done, but possible:
- remove optional packages (additional color schemes) (25k)
- remove empty packages (15k)
- summarize registry tweak packages to just one additional package (edit the .rgu) (few kB)
About UPX and builtin BINFS compression:
My experience is that the BINFS compression shrinks a set of example files (.NET CF 3.5 files that reside in the \Windows path) to about 49% while UPX'ed they only take 32% of their initial size. So on average you may gain 17% of the initial filesize in your ROM. The larger the file, the better is usually the gain.
Mind that UPX will only compress exe/dll files (even if they may be named differently, see Total Commander's *.tfx) and does not compress exe/dll that depend on .NET. It works luckily on the .NET CF core parts itself.
You should not compress (even if compression works, these DLLs will not load later):
resource DLLs
menu extension DLLs (context menus)
Updated and altered content:
added SDHC support by replacing the OMAP850_SDHC.dll with an SDHC capable version initially created for the StrTrk. So far there are no negative impacts visible.
altered the titles of the options to indicate the space they take - also UPX'ed size
moved the oemstartup.dll and the relevant pictures to the folder where the optional sounds already resided
added German T9 to the English T9 - so both is installed in the system if you select this. Mind that an additional language is not eating much space (~70k)
added the SafeInboxExtension as an own option to add, removed the InboxExtension from the combined "Group SMS + ..." menu
put moBlue to the latest version (2.1) and adapted rgu content.
added an option for registry changes called "tobbie GUI tweaks" that sum up everything that I think is useful (smaller menus, fonts, scrollbars, value for gamma).
updated the TotalCmd to the latest released version
created several additional packages from the previous default content (CeleTask, ClearType Tuner, ClockOnTop, ComManager, Dopod SIM Manager, .NET CF 3.5, OMAPClock, OxiosAlarms, OxiosMemory)
added a new package for .NET CF 3.5 where the GAC_* files have to reside on SD card. The complemtary ZIP containing the files to copy on SD card are located in the "_Changes" directory.
added the GPSID Settings tool to the GPSID directory
included the SP1 fixes supplied by Nitrogenious (FakeCursor not included)
changed several tweaked menus in the settings -> system tweaks
added options for volume setting of the initial beep and voice tag to the Voice Tag menu in system tweaks, changed category of the [HKEY_CURRENT_USER\ControlPanel\Sounds\VRecBeg] from "Notifcation" to "System" so that only the sounds sent form the VoiceTag are audible when the System sound volume is set to 0.
completely UPX'ed the SYS\MMSCAMCLKSTK *.exe and *.dll (except 2)
replaced the htcmidi.avd with the WM5 version to get back good midi playback,
added the HTCSourceflt.dll (from Nitrogenious SP1) to get midi playback in wmplayer
removed two large files from this directory which are nowhere referenced (CameraRC_*.dll).
updated WM5torage to the latest version (1.90), already setting suitable defaults.
fixed default settings for A2DP
Directory and contents
added a batchfile (you may want to edit) where the %SystemDrive% can be set to any value. This allows to install the kitchen on any drive you like and not on C:\ (the normal systemdrive) as it was mandatory. Mind that the scope of this %systemdrive setting is limited to the batch execution only. You can put the whole environment on a large RAMdisk (~380MB required) - this speeds up the cooking dramatically! A large RAM disk is available from "[ QSoft ] Qualitative Software" (1 year trial for the lite version) - see here: http://members.fortunecity.com/ramdisk/RAMDisk/ramdriv002.htm .
added a subdirectory "_Squeezer" where you find the UPX compression set "Squeezer" also published at XDA-developers (readme contained there). I have used this set to batch compress many files before putting them to ROM.
added a directory "_Changes" where you find the compressed and original versions of the files in equally named subdirectories OEM and SYS like in the WORK path. So in case you want to go back to the non-UPX-ed version they are there. Continuing the UPX-batch directory logic (2_Backup, 3_Compressed) there are further ones (4_removed and 5_changed) to document the changes done to the original content.
The rest of the kitchen is identical to the one Nitrogenious had released.
Download here: http://www.mediafire.com/file/xdiz2xzmote/Tornado_Kitchen_v09_by_tobbbie.exe
Quick Start:
- Unpack to C:\
- read cooking guide at Nitrogen's thread (see above)
- using defaults you get a ROM with: http://www.mediafire.com/file/z3ynij5ynzd/default-settings.gif
- available storage 27,97MB, free after 1.st boot 24,8MB
Correction: If you want to use the moBlue package, please edit the RGU file and add a blank line at the end. Using notepad will ensure that the file stays in unicode format.
Correction-2 (14.10.2010): You will experience that while WMP is playing the backlight will not go off as normal. This can be fixed by replacing the HTCWMPPlug.dll in the \windows directory on the device or in C:\Torn\_Changes\SYS\MMSCAMCLOCKSTK in the kitchen with the attached file.
Please make sure that your device is "SuperCID" before entering the "Format BINFS command. See post 3.
added 20100314: (edited 20100504)
Despite it is really extremely easy to cook your own ROM with the kitchen, let me give you a head start with your old Tornado. I have cooked the default settings to a ROM and added all tools that you need to step from a stock Tornado to the cooked one in a single archive.
Download it from here: http://www.mediafire.com/file/njm040ttoxm/_tobbbie-tornado-WM6(SDHC-NetCF_on_SD).exe
Unpacking it you will find a directory structure:
Code:
_tobbbie-tornado-WM6(SDHC-NetCF_on_SD)
├───1 prepare security
│ ├───1 HTCUnlock
│ └───2 SDA_ApplicationUnlock
├───2 prepare for custom flash
│ └───Utils
├───3 flash latest Radio and SPL
├───4 format BINFS 1b00000
├───5 flash ROM
└───6 copy NetCF to SD
└───Windows
Follow the actions in the directories one-by-one:
You only need to do steps 1 and 3 if you come from an official ROM but Step 2 (lokiwiz) needs only be done once per device.
If you flash another cooked ROM you can start from step 4.
Attention: In case you did not notice yet - the following procedures will completely erase all content that you stored on the device (email, SMS, MMS, ToDo, Contacts - simply everything) - the device will be as if it comes out of the box. So back up your data before you do this!
Here is what to do in detail, how and why:
Prepare security: This means that the restrictive program execution privileges have to be set less firm to allow step 2 to run later.
Connect your Tornado to the PC and let Active Sync connect. First run HTCUnlock-CVS.exe in the directory 1 HTCUnlock. This will install a program on your device. Run the installed program there and restart the device.
After the device has reconnected to Active Sync, on the PC run the program SDA_ApplicationUnlock.exe in the folder 2 SDA_ApplicationUnlock. It should confirm "succesfully unlocked".
Now the device is ready to receive the "SuperCID" that allows to flash any ROM to it, regardless of Operator or Vendor limitations. To be on the safe side later, please enter on the device *#06# and note down the IMEI that the device reports - you will need it later.
This needs only be done once per device - it is a permanent setting that survives all ROM updates.
Go to the folder 2 prepare for custom flash and
make sure there are no files *.bin left from previous device's activities
then execute Lokiwiz.bat. It will prompt you with 4 options:
Code:
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter:
Input "C" <enter>.
It will copy a program (itsutils) to the device and it should ask you for permission to execute - grant execution and let the batch file continue. You should find 2 new files beside the Lokiwiz.bat (lock-backup.bin and cid-unlocked.bin). Move them to a safe place immediately and do not repeat the procedure or call another option!
Be careful to label these files unambigously (best is to append the device's IMEI to the name - get it with *#06# before and do not use the IMEI printed on the label of the device - as restoring a wrong *.bin file to a device will kill the GSM radio access (Message: Data Crashes, please contact your... when trying to connect to the network with a SIM card inserted).
Now the device is prepared to receive custom ROMs.
Let's first put the last available Radio ROM and SPL (Secondary Program Loader) to the device. Go to the directory 3 flash latest Radio and SPL and execute ROMUpdateUtility.exe. After successfull update the device will restart in the old OS, nothing has visibly changed - you could still use the device as it is, all your data are still there.
Now the preparations start to erase the old OS and flash the new one.
Deactivate USB connections for the Active Sync
Switch off the device and disconnect from USB
Press Camera Key and keep it pushed down while connecting the USB cable to the PC - wait until the 3-color screen appears and release the camera key.
Start ttermpro.exe in directory 4 format BINFS 1b00000
Select Serial and Port USB
Press <enter> in the terminal window, you should get prompt CMD>
enter info 2 <enter> you should see something like:
Code:
Cmd>info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSSuperCID ' HTCE
Cmd>
The last line must show HTCSSuperCID ' HTCE.
If you see anything else there (e.g. HTCSVODA0504 㱍dHTCE - which is for an Austrian V1240) the lokiwiz in step 2 above did not work correctly. Still you have not destroyed anything (hopefully) - so to get the old OS start up again, enter ResetDevice <enter> - the device will restart and boot again. Think about what went wrong in the previous steps.
The lokiwiz batch file and the tools behind it are very powerful and can kill the GSM radio access of the device. Be careful with the *.bin files and keep those of different devices clearly apart.
In case you see HTCSSuperCID ' HTCE then you can pass the point of no return (after this the OS and all your data are deleted from the device) and enter at the prompt format BINFS 1b00000 <enter>. (The value 1b00000 depends on the ROM size, so if you use a different ROM, the value may also be different.) After a few seconds the prompt returns and the partition where the OS was stored is cleaned up now. The device will not boot beyond the 3-color screen in this state. You need to flash the new OS in the next step - but before this enter ResetDevice <enter> - the device will restart and return to the 3-color screen.
Terminate the tterm.exe, you will not need it any further.
Re-activate USB connections in Active Sync - you may forget it later.
Enter the directory 5 flash ROM and execute ROMUpdateUtility.exe. The procedure looks the same as in step 3 but takes a little longer. Do not get nervous as the time at 100% extends a few minutes. The device will reboot and bring you to the new OS.
The SD card that shall be used in the device needs to have the NetCF 3.5 files copied to the directory \Windows finally. This is NOT on the device but on the card - you can copy it on the PC while the sd card is in a card-reader or when the device has is mounted, there the path is \Storage Card\Windows
If the device had a SIM-Lock and it rejects your SIM, go to the lokiwiz.bat (again move out all *.bin files) and select "U" for SIM Unlock - again move the bin files in the directory to a safe place (but you should never need them). Mind that the "lock_backup.bin" is just a copy of the current encrypted area in the device. So this file is different after each step you completed before. Worse: if you do not save the FIRST lock-backup.bin you can never go back to this state.
Mind that lokiwiz.bat has worked for me on a Telenor Sim-Locked nordic ROM CID-locked QTEK 8310, so it should work for any other device as well. If you get the dreaded "Data Crashes..." message and your restore of the correct lock-backup.bin did not help either - your last resort is the SIM Unlock service here: http://imei-check.co.uk/c600_unlock.php. It costs you some bucks, but they seem to re-create the encrypted area with the matching IMEI of your device putting it in a SIM-unlocked and CID Unlocked state. Cheaper than buying a new device.
After you have sucessfully flashed your ROM - maybe you try cooking one yourself?
The selected default settings fill the ROM up to the last few hundred bytes. Adding options will surely jump over the next MB border and your ROM uploading preparations will have to format BINFS with a larger size.
If you have not read it elsewhere yet, the standard sequence to uplad a ROM is:
1.) cook ROM (OS part)
2.) determine size and format BINFS accordingly
more see this thread: http://forum.xda-developers.com/showpost.php?p=3439787&postcount=1
3.) upload ROM
If you start from scratch - so your device is still "untouched" by any custom ROM, you must prepare your device to allow the loading of a custom ROM. This happens in several steps to overcome the various security levels that try to prevent this:
Application unlock the current operating system. Look for "SDA Application unlock" this runs on the PC and remotely unlocks (via the Active Sync Connection) the security of the Windows Mobile operating system. This allows tools to run that you need for the next step.
Super-CID your device (and check if it worked!). Look for "lokiwiz" ZIP file in the forum here. Despite orginally created for the "Wizard" model, it also works for the Tornado in all respect, so it does the Super-CID and it does the SIM Unlock. I did it myself on a QTEK 8310 with a Nordic ROM and SIM-locked to Telnor.
To check if it worked, connect the device in Bootloader mode to the terminal program and enter "info 2" (without the quotes). It has to show HTCSSuperCID ' HTCE
Do not care about SIM lock yet, you can do that anytime later if necessary.
Good luck!
Thanks!
Thanks a lot. Nice work. Very useful. Could you please post one with a PRO rom, preferably the 6.5 version? Or at least the guidelines to make one?
I will not cook any further - this is why I released the kitchen. The strategies to save space are outlined in detail, so other cooks can take them and incorporate to their ROMs.
For me WM6 is sufficient - I don't need the "goodies" that came after that.
Thanks!
Oh fine. Thanks anyway. What is the perceived space saved from this method? And is there any performance hit?
I've seen that UPX'ing has a lot of performance boost so I'm wondering whether it can be made only to the packages or is it applicable to the exe's and large dll's from the CABs too. Since there are a few applications, which even when added later, install to the device memory directly. In these cases, UPX'ing might be highly beneficial in reducing the size as well as giving a speed boost. Any info on this?
Well, indeed you may think that UPX-ing will decrease performance as the file must be decompressed before running - but the opposite is the case!
you save space (most if installed, a little if in ROM - due to BINFS compression that is there anyway)
you get faster file-read time: This pays for especially well for large files (opera, office, acrobat, TomTom and alike). This will by far gain more than you loose for decompression (which goes directly to memory).
Looking at usual read-speeds of about 1MB/sec and an assumed 10 times faster decompression speed to memory, my feeling is that for speed reasons it will pay best for LARGE files (card and memory installed). Mind that after the file is read and loaded to memory, still the application needs to initialize itself. The last step is the same, no matter if UPX-ed or not.
If you tweak the bits for memory saving on the device it is no harm for anything smaller as well. Usually I stop UPX-ing below 50kB in size, but to have the ROM fit in the MB-frame I wanted to achieve I also had to UPX some smaller files as well. Just compare the directories of Nitrogenious' kitchen release and mine.
Hi,
Thanks for kitchen !
Sorry, I'm a novice in ROM cooking (I just modified a bit a ROM for my HTC Touch, long time ago, but I got no problem with flashing ROMS on HTC devices )
So I got a few questions/remarks.
1. I tried to build a custom ROM, but I got an error after selecting options.
I checked log file (a:\Torn\WORK\temp\log.txt) and I found following message :
Failed to parse value name HKEY_LOCAL_MACHINE\Software\hejhej.org\moBlue!!!
InitRegistry FAILED in file ".\Registry\37771312-772c-4ff9-a0a1-b555ad54a025.rgu" within a few lines of line 10.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\37771312-772c-4ff9-a0a1-b555ad54a025.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
If I uncheck "MoBlue", all is OK, so I think MoBlue package is corrupt.
2. When building with default option, what values to put in nb2nbf (CID and start address) ?
I used same as http://forum.xda-developers.com/showpost.php?p=2150690&postcount=1 (82040000 for start adress and ORG_0401 for CID)
Is this OK?
(my phone is an Orange SPV600, CID unlocked, so I think I can put any value for CID)
3. I didn't really understand how to change ROM size. I checked your thread, but I'm still in the dark.
In nb2nbf, in size column, I got "33357824" = "0x13E20248".
So I used "format BINFS 014000000". Is the the way to go ?
Thanks for answers.
Answers!
1. Even I'm unsure about that.
2. Yes. Just select the OS option and it will fill the address by itself.
3. Yes. That is the method I follow. AFAIK, convert the bytes into it's hex equivalent and choose the nearest <higher> hex number with 5 0's at last.
And from what I understand from his post, if you have a ROM with 29.1 mb size, either reduce it to (29 mb - 64k) or add some apps and increase it to (30mb - 64k), to make the optimum use of the available space.
Hi AlainL,
...will have to look after the moblue part - strange, possibly the wrong format of the file (not unicode stored). The content should be ok. I fixed it after updating from the old moBlue inside the old kitchen to the 2.1 version copying the Registry content of the moBlue branch.
Regarding the address it is easy: when you select "OS" and click in the address field, the address is selected automatically - this is the right one.
Your assumption on the format BINFS <size> is correct. This is the way to format it. But your calculation is wrong. The Hex size of your value is 1FD0000 and thus you have to format with 2000000 or your device will not boot after flashing.
The solution to the moBlue problem in the .rgu is very easy.
Edit the .rgu file and add a blank line at the end - that's all.
Editing .rgu files
Just to be on the safer side:
Don't forget to save it in the Unicode format too. Turn off word wrapping while editing .rgu files.
They are all unicode - so if you edit with notepad it should keep this format.
Special attention is required when adding "Multistring" values to the registry. The can be imported as hex - and this hex code must be in unicode format, so 2 bytes per character.
So when exporting the values from the registry to add them to an .rgu package you must take care of this. Took me some tries until I had the .NET CF 3.5 with separated GAC_* package running.
tobbbie said:
Your assumption on the format BINFS <size> is correct. This is the way to format it. But your calculation is wrong. The Hex size of your value is 1FD0000 and thus you have to format with 2000000 or your device will not boot after flashing.
Click to expand...
Click to collapse
Hi
Thanks all for your answers.
I used the right number.
I just made an error while writing in this thread ("0x13E20248" = "333578824").
This cooking works very well.
I just got a problem, maybe someone can help me.
I added Esmertec Java and installed opera mini 4.2, opera mini 5 beta 2 (latest) and opera mobile 10 beta 2 (latest too).
All is OK with 4.2, but with 5b2 and 10b2, I can't pass license agreement screen, because I can't click on "Accept" button (nor "exit" one), neither with left or right menu button or with cursor.
I thinks it's Opera's fault, but if anyone got a suggestion ...
Finally, I got a question :
Now, I'm using a SPV C600 (Orange), and it doesn't have WiFi.
I plan to buy either a XPA1240 or Qtek 8310 (used, quite cheap), but I need to know if WPA is supported.
I can't check by myself, cause every time I try something related to WiFi, I end with an error "Driver not loaded".
I do not cook java in the device but have it installed on SD card - along with the midlets it will take later. The package I use is called "JBEDROSE" (20080813.2.1) and comes from the Vox forum. I have no problems using later versions of Opera there (including 5ß2). I suspect the accept requires a network connection to the opera server (WIFI or AS), so maybe this is your problem?
The WLAN support WEP, WPA, WPA2 and should also cover hidden SSIDs (but I don't use it). The Reg-Tweak "optimal performance for WLAN" is actually putting the WLAN in a mode that will NOT do continuous transmission (and drain your battery real fast - like in WM5) but in a mode that saves battery without affecting performance.
The prices for used 1240 or 8310 are rising at ebay currently
tobbbie said:
I do not cook java in the device but have it installed on SD card - along with the midlets it will take later. The package I use is called "JBEDROSE" (20080813.2.1) and comes from the Vox forum. I have no problems using later versions of Opera there (including 5ß2). I suspect the accept requires a network connection to the opera server (WIFI or AS), so maybe this is your problem?
Click to expand...
Click to collapse
I tied both with AS or via EDGE/GPRS connected (when loading EULA, netwok is required).
It looks like Opera 5b2 and 10b2 didn't recognized both menu button.
I will still do some tests.
tobbbie said:
The WLAN support WEP, WPA, WPA2 and should also cover hidden SSIDs (but I don't use it). The Reg-Tweak "optimal performance for WLAN" is actually putting the WLAN in a mode that will NOT do continuous transmission (and drain your battery real fast - like in WM5) but in a mode that saves battery without affecting performance.
Click to expand...
Click to collapse
Thanks, great
tobbbie said:
The prices for used 1240 or 8310 are rising at ebay currently
Click to expand...
Click to collapse
Because of your excellenet kitchen ?
Opera 5ß2 works on my Jbed (non cooked as I wrote). The opera 10ß2 is native WM - but said to not support smartphones (non-touchscreen) well, so I stick with Opera-mini for the occasional browsing I do there.
Now the default settings are contained in a ready cooked ROM - enjoy!
Appended to the first post:
added 20100314: (edited 20100504)
Despite it is really extremely easy to cook your own ROM with the kitchen, let me give you a head start with your old Tornado. I have cooked the default settings to a ROM and added all tools that you need to step from a stock Tornado to the cooked one in a single archive.
Download it from here: http://www.mediafire.com/file/njm040ttoxm/_tobbbie-tornado-WM6(SDHC-NetCF_on_SD).exe
Unpacking it you will find a directory structure:
Code:
_tobbbie-tornado-WM6(SDHC-NetCF_on_SD)
├───1 prepare security
│ ├───1 HTCUnlock
│ └───2 SDA_ApplicationUnlock
├───2 prepare for custom flash
│ └───Utils
├───3 flash latest Radio and SPL
├───4 format BINFS 1b00000
├───5 flash ROM
└───6 copy NetCF to SD
└───Windows
Follow the actions in the directories one-by-one:
You only need to do steps 1 and 3 if you come from an official ROM but Step 2 (lokiwiz) needs only be done once per device.
If you flash another cooked ROM you can start from step 4.
Attention: In case you did not notice yet - the following procedures will completely erase all content that you stored on the device (email, SMS, MMS, ToDo, Contacts - simply everything) - the device will be as if it comes out of the box. So back up your data before you do this!
Here is what to do in detail, how and why:
Prepare security: This means that the restrictive program execution privileges have to be set less firm to allow step 2 to run later.
Connect your Tornado to the PC and let Active Sync connect. First run HTCUnlock-CVS.exe in the directory 1 HTCUnlock. This will install a program on your device. Run the installed program there and restart the device.
After the device has reconnected to Active Sync, on the PC run the program SDA_ApplicationUnlock.exe in the folder 2 SDA_ApplicationUnlock. It should confirm "succesfully unlocked".
Now the device is ready to receive the "SuperCID" that allows to flash any ROM to it, regardless of Operator or Vendor limitations. To be on the safe side later, please enter on the device *#06# and note down the IMEI that the device reports - you will need it later.
This needs only be done once per device - it is a permanent setting that survives all ROM updates.
Go to the folder 2 prepare for custom flash and
make sure there are no files *.bin left from previous device's activities
then execute Lokiwiz.bat. It will prompt you with 4 options:
Code:
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter:
Input "C" <enter>.
It will copy a program (itsutils) to the device and it should ask you for permission to execute - grant execution and let the batch file continue. You should find 2 new files beside the Lokiwiz.bat (lock-backup.bin and cid-unlocked.bin). Move them to a safe place immediately and do not repeat the procedure or call another option!
Be careful to label these files unambigously (best is to append the device's IMEI to the name - get it with *#06# before and do not use the IMEI printed on the label of the device - as restoring a wrong *.bin file to a device will kill the GSM radio access (Message: Data Crashes, please contact your... when trying to connect to the network with a SIM card inserted).
Now the device is prepared to receive custom ROMs.
Let's first put the last available Radio ROM and SPL (Secondary Program Loader) to the device. Go to the directory 3 flash latest Radio and SPL and execute ROMUpdateUtility.exe. After successfull update the device will restart in the old OS, nothing has visibly changed - you could still use the device as it is, all your data are still there.
Now the preparations start to erase the old OS and flash the new one.
Deactivate USB connections for the Active Sync
Switch off the device and disconnect from USB
Press Camera Key and keep it pushed down while connecting the USB cable to the PC - wait until the 3-color screen appears and release the camera key.
Start ttermpro.exe in directory 4 format BINFS 1b00000
Select Serial and Port USB
Press <enter> in the terminal window, you should get prompt CMD>
enter info 2 <enter> you should see something like:
Code:
Cmd>info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSSuperCID ' HTCE
Cmd>
The last line must show HTCSSuperCID ' HTCE.
If you see anything else there (e.g. HTCSVODA0504 㱍dHTCE - which is for an Austrian V1240) the lokiwiz in step 2 above did not work correctly. Still you have not destroyed anything (hopefully) - so to get the old OS start up again, enter ResetDevice <enter> - the device will restart and boot again. Think about what went wrong in the previous steps.
The lokiwiz batch file and the tools behind it are very powerful and can kill the GSM radio access of the device. Be careful with the *.bin files and keep those of different devices clearly apart.
In case you see HTCSSuperCID ' HTCE then you can pass the point of no return (after this the OS and all your data are deleted from the device) and enter at the prompt format BINFS 1b00000 <enter>. (The value 1b00000 depends on the ROM size, so if you use a different ROM, the value may also be different.) After a few seconds the prompt returns and the partition where the OS was stored is cleaned up now. The device will not boot beyond the 3-color screen in this state. You need to flash the new OS in the next step - but before this enter ResetDevice <enter> - the device will restart and return to the 3-color screen.
Terminate the tterm.exe, you will not need it any further.
Re-activate USB connections in Active Sync - you may forget it later.
Enter the directory 5 flash ROM and execute ROMUpdateUtility.exe. The procedure looks the same as in step 3 but takes a little longer. Do not get nervous as the time at 100% extends a few minutes. The device will reboot and bring you to the new OS.
The SD card that shall be used in the device needs to have the NetCF 3.5 files copied to the directory \Windows finally. This is NOT on the device but on the card - you can copy it on the PC while the sd card is in a card-reader or when the device has is mounted, there the path is \Storage Card\Windows
If the device had a SIM-Lock and it rejects your SIM, go to the lokiwiz.bat (again move out all *.bin files) and select "U" for SIM Unlock - again move the bin files in the directory to a safe place (but you should never need them). Mind that the "lock_backup.bin" is just a copy of the current encrypted area in the device. So this file is different after each step you completed before. Worse: if you do not save the FIRST lock-backup.bin you can never go back to this state.
Mind that lokiwiz.bat has worked for me on a Telenor Sim-Locked nordic ROM CID-locked QTEK 8310, so it should work for any other device as well. If you get the dreaded "Data Crashes..." message and your restore of the correct lock-backup.bin did not help either - your last resort is the SIM Unlock service here: http://imei-check.co.uk/c600_unlock.php. It costs you some bucks, but they seem to re-create the encrypted area with the matching IMEI of your device putting it in a SIM-unlocked and CID Unlocked state. Cheaper than buying a new device.
After you have sucessfully flashed your ROM - maybe you try cooking one yourself?
Some updates to the guideline for flashing in the previous and the first post.
be careful with lokiwiz (several hints added)
last resort if you fail to superCID the device: http://imei-check.co.uk/c600_unlock.php
Enjoy - there is no real successor of the Tornado
Thank you for this. I updated my phone because the previous rom was slow and flawed as I discovered. Phone is working great now.
A few weeks ago when the Android-on-HD2-hype started i made this small app. This piece of software was inspired by GenYDualboot (author: YOZGATG) so some credit should go to him...
To make it clear: I wrote this software by myself (basic4ppc) from the scratch so no code or other intellectual property has been stealed.
ANDROID BOOTCAMP v1.1
System Requirements:
* WVGA (VGA/QVGA not supported!)
* WinMob 6.5.X (not tested on WinMob 6.5)
* min. NETCF 2.0
* a SD-card containing working Android-build
Basic Functionality:
* WinMob based Android loader
* possible to "boot" ANDROID or to stay in Windows
* possible to "autoboot" with countdown (10sec)
* possible to choose if CLRCAD.EXE is loaded prior to HARET.EXE or not
* Autodetection of HARET.EXE and CLRCAD.exe on the SD-Card (checks if files are present in root or "\Android")
* possible to modify the path to your Android-build by changing the path in the registry
* possible to boot at systemstart (the app puts itself to "launch52" in the registry)
* possible to save your settings
* fully functional on non-WWE-Roms (checks the registry for the name of your sd-card)
* full multi-language-support (by editing the "language.ini"; at this time only german an english are buildin)
* full landscape/rotation support
* fully skinable (by modifing the PNGs in the app-folder, i'm going to release a GTX based skin or some other skins if it's wanted by the community)
* new: change font color (black/white)
* new: switchable progressbar (showed during countdown)
* new: ClearAndroid! removes Android-related junk-/tempfiles and cache!
* new: TotalClean! totally ereases your Android environment (for a clean upgrade to a new build) - USE WITH CARE!
Disclaimer:
This piece of software is free and can freely be downloaded here. You are allowed to modify, cook in or distribute my work as long as you give me some credit.
YOU ARE NOT ALLOWED TO CHARGE ANY KIND OF FEE NEITHER FOR THIS SOFTWARE ALONE NOR BY INCLUDING IT OR ANY MODIFICATIONS OF IT INTO A ROM/ANDROID-BUILD OR ANY OTHER "SERVICE"!
(see threat "STOP THE STEALING" in the Android subforum for more details...)
I'm not responsable for any kind of damage or data loss on your device. The software is provided as it is and you are going to use it on your own risk.
Credits:
* the developers here and at htc-linux.org for HARET.EXE/CLRCAD.EXE and for their amazing work!
* YOZGATG for GenYDualboot
Roadmap / future functions to come in Android Bootcamp v1.2 (if wanted by the community):
* GUI-overhaul to a nicer / modern look
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add support to select androit installation (if more than one installation present on SD)
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder) integrated into v1.1!
* add option "TOTALCLEAN" (ereasing all android related files and folders incl. thumbnails/cache/etc) integrated into v1.1!
More inf
o to come....
Feel free to make your suggestions!
FAQ / Userguide
Q: How do I install Android Bootcamp?
A: Just download the CAB attached to the firs post and install it to your device. It's recommended to put it into your phone-storage not to the sd-card.
Q: How do I boot into Android?
A: Click on the Android-button (the picture).
Q: The Android-button is greyed out and the app says "no Android!"
A: Make sure that there is a sd-card plugged into your device containing Android in the root or in the "\Android" subfolder. Also HARET.EXE/zHARET.EXE is required in the same folder to successfully boot Android. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to HARET.EXE/zHARET.EXE. If HARET not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder. If you want to modify the path to your own needs go to the registry and alter the value "Haret" in the key "HKLM\Software\Android Bootcamp".
Q: How do I make sure that CLRCAD.EXE is started prior to HARET.EXE
A: Click on the checkbox next to activate CLRCAD or select the option in the settings-menu. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to CLRCAD.EXE. If CLRCAD not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder and after that it takes the CLRCAD.EXE in the Android-Bootcamp program folder. If you want to modify the path to your own needs go to the registry and alter the value "CLRCAD" in the key "HKLM\Software\Android Bootcamp".
Q: How do I stop the countdown?
A: Just tap on the countdown-message or tap on the checkbox next to "activate AutoBoot".
Q: How do i activate/deactivate AutoBoot?
A: Check or uncheck the checkbox next to "activate AutoBoot" or select the corresponding option in the settings-menu.
Q: What does "execute at Boottime" mean?
A: The App makes 2 entries to the registry ("HKLM\init\Launch52" and "HKLM\init\Depend52"). These entries make sure that Android-Bootcamp is started during the WinMob boot procedure with the saved settings as soon a possible. Please note that the boot process does not stop and continues loading system processes after Bootcamp is started. I suggest also to check the "AutoBoot" option so that Android/WinMob is loaded automatically after 10sec. To disable this option uncheck the option (registy changes made immediately - no "save settings" is needed)
Q: How do I save my settings? Why are my settings not saved?
A: Your settings are not saved automatically - choose "Save settings" in the settings-menu prior to booting Android or closing the app.
Q: How do I activate the landscape support?
A: Landscape and screen-rotation is fully supported by the app itself but it's possible that you have to add the app to the rotation-whitelist. If you don't know how to do this - google for TouchTools or BSB-Tweak. With the help of these apps you can enable rotation service easily to any program.
Q: The program gives me the error-message "No Registry-values found, create them now?"!
A: Possibly you deleted one/some reg-values needed by the app. Just click to "YES" and all settings/RegKeys will be created with default values.
Q: I'm not naturally speaking english/german. How do I add my own language?
A: This can be done very easily by modifing the file "language.ini" in the Android Bootcamp - program folder. Please make sure that the first line is the name of the language and that the ini's structure isn't altered (NO SPACES between value, "=" and translation!!)
Q: How do I add my own skin?
A: Modify the PNG-files in the Android Bootcamp prgram folder to your own needs after making a backup of the orginal files (recommended). Feel free to post your files compressed to a ZIP-file here!
Q: I still don't get "execute at Boottime" to work!!
A: First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless if Bootcamp is in fore- or background. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
Q: Is it possible if you can code it so it can find CLRCAD and Haret in the "cm6-htcleo" folder for the CyanogenMod release / in some other custom folder?
A: Yes, it's already possible - open your registry with a regeditor and go to the key "HKLM\Software\Android Bootcamp". Check and edit the VALUE "Haret" and put the FULL PATH to your HARET.EXE / zHARET.EXE in there. After this modification Bootcamp should be able to find your Android-Installation. The feature of selecting a custom folder is added with the next release of Bootcamp.
NOTE: Be aware that "CleanAndroid!" and "TotalClean!" doesn't work with custom Android folders - these two options look for an Android-environment in the root of your storage card or in the "Storage Card\Android" folder respectively. So keep an eye on those two (probably dangerous) features, so that not the wrong files get lost...
SKINS
Q: How do I install a skin?
A: Download the zipped skin-file here and extract all files to the Android Bootcamp program folder overwriting the orginal files.
Q: How do I add my own skin?
A: Modify the JPG/PNG-files in the Android Bootcamp program folder to your own needs after making a backup of the orginal files (recommended). Make sure that your files have the same dimensions and keep their file format! Feel free to post your files compressed to a ZIP-file - I will add them here!
NOTES:
* GTX-based skin is beta/for testing only and does not look very good - better version will be uploaded with the next program version (see text color issue above)
* Text color can't be changed a this time - going to add an option in the next version to switch between black/white fixed in v1.1
* there is some minor picture-misallignment regarding the android button. This is already fixed in the code an will be included in the upcomming update fixed in v1.1
nice work! good to see several alternatives out there for dual booting
Don't need it...
But really great job!
Pretty GUI !
beautiful my fav booting app so far,
thanks
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Best Dual boot for Android/Winmo out there at the moment.
essojay said:
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Click to expand...
Click to collapse
Please explain this issue to me because i don't have this kind of problem in my setting. Do you want to have an option to "automatically clean" the root/android folder of your sd-card after rebooting (to WinMob)? What kind files should be cleaned? I easyly could add an option to clean the "*.REC" files and the "LOST+Found" folder if this is wanted.
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
essojay said:
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
Click to expand...
Click to collapse
Hmm, I looked at the given threat and this issue seems strange to me. I never had this kind of problem and this could be BECAUSE my Android-installation resides in the folder "SD-CARD\ANDROID". Darkstone and Dani recommend to put their builds (Froyo) into the Android subfolder and not directly to the root-folder of the sd-card.
Adding a option to clear or to delete the android folder seems not acceptible to me because - like I said - many people including myself have their Android installation in this specific folder and consecutively would destroy their Android environment.
But i'm considering to add a TOTALCLEAN-feature so the user can easily prepare the sd-card for a new android build by ereasing his android installation and all corresponding files and folders (thumbnails, cache, etc.) without the need of formatting the sd-card.
Epic
Very nice GUI! I will be giving this a try. Seems like a good time to experiment with some different flavors of Android...Weekend Project! w00t!
Yes Ironheart...am going to try the sdcard/android way and let you know.. just read somewhere about everything in the android folder.. thanks.. will let you know
bR
really nice man, i will jump ship to your loader
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Zell Dinch said:
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Click to expand...
Click to collapse
First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless whether Bootcamp is in foreground or or not. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
my contribution to the theming
ironheart said:
Future functions to come in Android Bootcamp v1.1 (if wanted by the community):
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder)
* add option "TOTALCLEAN" (easy preparation of your SD-Card without formatting by ereasing all android related files and folders incl. thumbnails/cache/etc)
* add support to select androit installation (if more than one installation present on SD)
Click to expand...
Click to collapse
+1 Want have
[/QUOTE]
voiceofid said:
my contribution to the theming
Click to expand...
Click to collapse
Nicely done! going to put your skin to post#3...
Thank you!
EDIT:
I testet your theme and i had to lightly modify it to keep text-readability (blur filter, less light, htc-logo removed)... i hope you are ok with my modifications. Still good job done (added to skins)
HD2_Noob said:
+1 Want have
Click to expand...
Click to collapse
Some of the new features are already working in my beta-build und are going to be released to public soon (ETA for final 1.1-release maybe 1-2 days)...
Stay updated!
Getting Started- This is a simple Tool for MotoTool for Motorola Moto Devices (Beckham, Doha, Lake, River, Evert, Sanders, Potter, Lima) - (All variants), here you will be able to Boot TWRP, flash any firmware that you want and debloat all apps too!
Prerequisites
* You must have NetFramework 4+ installed on your PC * Net Framework
* Windows 8+ 64 Bits
Install
-Start the "MotoTool_v1.4.9.9_Setup.exe"
- The installer will create a desktop shortcut and in Windows app will create a folder with the tool inside.
- When the installer ends, will ask you if you want to launch the Tool and if you want to isntall MotoDrivers. Please if you dont have MotoDrivers installed or you dont know, dont uncheck the option and let the install do it![/B]
How it works?
- The installation will create a "MotoTool" shortcut on desktop
- When you launch the Tool on the first time this will:
-- unpack on "C:\adb" fastboot&adb
-- launch a batch file: **You must accept this, because will remove unnecesary Moto Device Manager to save storage! If you don´t accept this, when you start again the Tool on next launch, will be asking you again! so i recommend you to accept it!**
-- create neccesary folders
-- generate a settings for the Tool. Be careful with this, if you clear the folders, you will lost, TWRP, Firmware, and the Tool settings!
- You must have to be enable usb debugging on your device so the Tool can work!, and IMPORTANT have Bootloader unlocked to use the options like Boot TWRP or flash any Firmware!
- Then you can use any option, remember if you want to download any file, this will check internet connection, if it´s null the tool will reset and restart the Tool!
- If you want to boot TWRP, this will be downloaded (when download finish, click again the option!) and flashed, but remember to put your device on Bootloader mode!
- Themes, the default style it´s dark, so the Tool on the first start will be by default dark, if you want to change it go to "Tool Extras" and select light screen, but be carefoul with your eyes! light Theme it´s so brightness!
Downloads and info
- Download
- Changelog
Source:
- Source-GitHub
- More Info and Help
Tool BetaVersion: v1.4.9.9
Tool Preview Version: ---
franTW said:
Getting Started
- This is a simple Tool for Motorola Moto Z3 Play, here you will be able to Boot TWRP, flash any firmware that you want and debloat all apps too!
Prerequisites
* You must have NetFramework 4+ installed on your PC * Net Framework
* Windows 8+ 64 Bits
Install
- Start the "BeckhamTool_v1.0.0.5_Setup.exe"
- The installer will create a desktop shortcut and in Windows app will create a folder with the tool inside.
- When the installer ends, will ask you if you want to launch the Tool and if you want to isntall MotoDrivers. *Please if you dont have MotoDrivers installed or you dont know, dont uncheck the option and let the install do it (WARNING: Uncheck Launch Tool!)
NOTE Setup: if you check the box "Launch BeckhamTool" the Tool will be executed, but setup wont be closed, so restart the Tool for now
How it works?
- The installation will create a "BeckhamTool" shortcut on desktop
- When you launch the Tool on the first time will unpack on "C:\adb" fastboot&adb, and will create neccesary folders and generate a settings for the Tool. Be careful with this, if you clear the folders, you will lost, TWRP, Firmware, and the Tool settings
- You must have to be enable usb debugging on your device so the Tool can work!, and have Bootloader unlocked to use the options like Boot TWRP or flash any Firmware
- Then you can use any option, remember if you want to download any file, this will check internet connection, if its null the tool will reset and restart the Tool!
- If you want to boot TWRP, this will be downloaded (when download finish, click again the option) and flashed, but remember to put your device on Bootloader mode and ready to flash
- Themes, the default style it´s dark, so the Tool on the first start will be by default dark, if you want to change it go to settings icon and change it, but be carefoul with your eyes! Light Theme its so brightness!
Preview
What is this?
This is a pre-release of the Tool, this have new options and functions than Stable don´t, but if you want to use this previews, you are on your own risk of having bugs, and maybe other accidentally errors!
Downloads and info
- Download Stable
- Download Preview
- Source-GitHub
- More Info and Help
- More screenshots
Tool Stable Version: v1.0.0.6
Tool Preview Version: v1.0.0.7-Preview 2
Click to expand...
Click to collapse
I appreciate your work. Hard for me to believe not one single response to your thread. I appreciate it and thank you for your work.
bob24260 said:
I appreciate your work. Hard for me to believe not one single response to your thread. I appreciate it and thank you for your work.
Click to expand...
Click to collapse
Thank you!
I've been missing from the Moto Z3 for 6 months now.
I think it's time to tinker with the Z3Play so I'll give the tool a try.
Even if I know nothing about TRW, custom ROMs and rooting of THIS device.
My previous experience was with LG devices. Which were pretty straight forward.
Sent from my Moto Z3 Play using Tapatalk
Everything that you can do with this app you can do with fastboot which is multiplatform.
QkiZMR said:
Everything that you can do with this app you can do with fastboot which is multiplatform.
Click to expand...
Click to collapse
Yes i know, this Tool its just to make the things easier... everyone can use whatever they want...
does anyone still have this tool i would like to try it for my z3 play
paulhauth25 said:
does anyone still have this tool i would like to try it for my z3 play
Click to expand...
Click to collapse
Click that github link in the first post.
@franTW
Thanks for this nice tool, I just took my Z3 Play out of the drawer, after a year or so.