As promised, here is our new V2.01 of the G.O.T OpenRecovery (G.O.T OR)

New features in 2.01 version are:

Enhancements
– toggle USB switch to enable access to the sdcard from your PC whilst you are still in OR (thanks Skrilax_CZ)
– use metamorph themes in OR directly (to theme launcher for example), experimental
– edit your Android_ID in cfg file direclty (16digit hex), then use the respective option to add this ID to your version of the MS
– added OpenRecovery-CFG folder (this is where the .cfg files for the Android_ID and the stock app removal are stored)
– some changes in script to correct issues
– Now based on V1.45 of Skrilax_CZs OpenRecovery!

FIXES:
– The new folder “OpenRecovery-CFG” includes the cfg files that can be changed by the users.
– We moved the “backup” folder to “OpenRecovery-CFG”, so only 1 backup for all features now and not for every Version of our OR mods (2.1, 2.2.1 etc)
– Facebook issue STILL not solved to our satisfaction with the 2.2.1 release

APP & Framework backup:
If you want to make a new complete backup, go to “Stock OR”, Wipe & Cleaning Menu and apply “Create New Backup”
this will delete your old backup and create a new one.

All cfg files you may edit are in OpenRecovery-CFG now. (folders for GOT_2.1, GOT_2.2.1 and GOT_CM6)
Each folder contains the cfg files you can edit – to edit the cfg files under Windows, don’t use Windows Editor or Notepad
please use Notepad++.

INSTALLATION

– Delete all previous versions of the folder “OpenRecovery” on the SD CARD to ensure all you dont habe “old” stuff in the folder
– Copy the OpenRecovery AND OpenRecovery-CFG folders to your SDCARD as well as the update.zip

We are working on an updated OR to fix the following issues (so that most bugs can be fixed directly via OR or Update)

BUGFIXES
1. Correct our mistake with the Wireless Tether app (we will take it out), then simply download from market as app needs to be installed.
2. Include some reworked script based on Ed Castros input, but we will allow you to enter your own ID as an option via the OR
3. Reworked OR scripts to fix some OR issues you seem to encounter ( update all recoveries to 1.44, only old nandroid stays on 1.14)
4. Facebook workaround when it is finally resolved (see below)

Enhancements
The new OR will also bring some enhancements thats to skrilax_CZ and our scripters are working on at the moment and we are in alpha-testing
– Toggle USB in OR so that you can access your SDCARD from you computer in the OR via USB cable (card shows up as USB storage)
– Metamorph from OR, still experimental, but may be useful for themers

Work in progressThe facebook app not synching remains problematic at the moment. It appears the install V1.2 and then 1.32 workaround still does not work as expected. One of the reasons why this does not work as it should is that the app itself (facebook.apk) is not at all included in the ROM and therefore is not properly installed and supported when flashing the ROM. We will keep working on this issue.

PS: Thanks for working with us to fix some of the remaining issues. Any help you guys can give is greatly appreciated as we can only cover so much with the resources at hand.

G.O.T is proud to finally be in a position to present to you the 2.2.1 firmware files you have all been waiting for.

We have also finished our work on our OpenRecovery modification for this and previous builds.

Lets start with the Credits:

– The entire G.O.T theme for sticking with me during the past week and the numerous IMs/calls/chats we have had to get this done in time. I, personally, feel honored to work with you guys!!
– The great nadlabak and skrilax_CZ. None of this would have been possible without your continuous dedication and support. Nadlabak, go-go-go with your CM6 🙂We are sure once you launch your new edition of CM6, our firmware will no longer be needed by the users!!!
– DAGr8 and -fufu-. Your ideas and cooperation with us (especially our coders/scripters) took our OR to a whole new level. As such, the incremental jump to V2 of the OR is all due to you guys.
– he_stheone64 for agreeing to “licence” his Theme “SummerBlues” to us as the new and improved G.O.T theme. Thank you so much.
– All the other help we had from the people that worked with us day and night and who would like to remain “silent” contributors. You know we owe you a lot!!!

Here is what you need to know:

a) Contrary to previous releases, we would strongly recommend you to use our GOT OR V2.0.
One of the first things you should do is use the “Fix 2.2.1 bugs” selection in the new OR 2.2.1 menu after you flash the sbf file.
This tweak will fix some of the issues with the generic sbf build such as dual USB notifications, replacing some stock Motorola applications such as the old launcher/mediagallery and adding the Wireless Tethering application.
DO NOT USE after installing the G.O.T. theme, as the services.jar is different between both versions. If you did it anyhow, simply install the G.O.T theme again.
b) The sbf firmware files are all modified by us including the vulnerable recovery, so you can flash and root straight away (same as with our previous releases)
c) If you flash the firmware, you might encounter a reboot after the first boot. This is normal and expected behavior, so do not be alarmed
d) We can only provide you with full sbf releases at this moment. We strongly recommend not to use any backup from 2.1 related kernels as you are bound to get into trouble. The best approach is to install the apps you need from the market, set up your accounts and customize your device by hand. This is the only way you can guarantee that any issues encountered are not due to an incompatible data/settings backup.
e) Performing and restoring nandroid backup from 2.1based kernels will result in a bootloopunlessyou use our G.O.T V2.0 OpenRecovery (or any other ORs that have been updated to V1.44 of skrilax_CZ base). The simple reason is that we have worked together with Skrilax_CZ as we, and him, encountered issues when trying to restore 2.1 based nandroid images on top of the flashed 2.2.1 firmware. We are very happy our cooperation with him was as good as it was, and as such be in a position to already have solved this issue at launch.
f) We are extremely proud to give to you the new G.O.T Theme for 2.2.1. Some of you may see the familiarities to the SummerBluesTheme of he_stheone64. There is a reason for it – we are proud to be able to announce that he_stheone64 has worked with us, and agreed, that his SummerBluesTheme is now the new G.O.T theme.
g) NOTE: On some devices, we have encountered that rooting directly after flashing without rebooting after the initial flash can bring some issues with RootExplorer not asking for root permissions. To be safe, reboot after flash so that the “welcome to milestone” menu comes up, set up the device in general, then reboot to recovery and root the device as well as apply our 2.2.1 tweaks with Launcher, Services.jar fix and Wireless Tethering app.

Testing experience from our team regarding features and functionalities:

– AGPS works reliably, no trouble found
– Bluetooth works reliably, no trouble found
– WLAN works as before, no trouble found
– GPRS/HSDPA data works fine, no trouble found
– Framelimit of 30fps lifted
– Kernel 2.6.32 includes and supports the generic 2.2 features known
– Tethering app (3G Hotspot) included, but did not work for us (network provider needs to support this feature failures). We don’t know whether this is possible with your operator, but we have included the wireless tethering app in the Stock 2.2.1 tweaks
– Market needs fixing to show protected apps, bug solved by using the G.O.T fingerprint of build.prop and market fix (provided in 2.2.1 menu)
– Overclocking works fine with the modified overclock2.2.apk written (2.2.1 overclock menu will install it)

These are all the firmware files we can provide at the moment. If we locate further sbfs, we will let you know. RTEU should work with most countries that have the European UMTS frequencies.

EDIT/UPDATE:Thanks for all your feedback so far. 2 prominent bugs we would like to comment on:
1. Missing Android ID: We had noticed that too. So far it seems that the Android ID, which is normally generated by the ROM as a combination of your Phone ID and your Google Log-In account, is not generated by the firmware. We are not sure why, but believe that this may either simply be an “oops” by Motorola or, more probable, be intentional for this beta FW. We might try setting up a dummy ANDROID ID in the settings.db to see whether this could work as an interim fix.
2. Wireless Tethering app: Our fault it seems that slipped by in testing. You need to install the application, simply pushing to /system like we did does not work. FIX: Delete the apk (android.tether.apk) in /system/app and re-download and install from Market (Wireless Tethering for Root users).

EDIT2:
We have seen user comments below that I think you guys should try regarding the Missing Android ID:
You can simply add the Android ID using an SQLITE Editor extension from Root Explorer: (SQLite Editor in market)

1. Open RootExplorer
2. Navigate to /data/data/com.android.providers.settings/databases/settings.db
3. Add an entry insert into secure (‘android_id’,’16-digits-hex-number’) using the SQLite Editor ->New Record->name=android_id -> value= 16digit hex code;
4. You can either use a dummy 16-digit hex number, or what we would recommend, revert to a previous Nandroid from your phone, use root explorer(only view SQLITE db) the same way, and take a note of your AndroidID. Then simply add/enter this 16-digit number to your phone in 2.2.1 as per steps 1,2 and 3
Thanks to Ed Castro and others for pointing this out.

UPDATE3: he_stehone has provided a final fix for the Facebook issue:

Final Fix for Facebook

Basic idea came from el_charlie (thx for that) – he realized 1.2 works, then we investigated more:

* Copy Facebook 1.2 on your SD
* Install with any file explorer
* Choose your desired contact sync
* Run first sync
* Uninstall FB 1.2 – now you`re all set
Issue was that only the first initialization does not work with Facebook 1.32 on this froyo version, once the sync is there 1.32 syncs fine.

We know you are eager to have something to play with, so here you go, at least we want to ease the pain and give you an early version of the new OpenRecovery we are working on for the next firmware – V1.10

We are very happy and grateful for the contributions from the following developers:– Skrilax_CZ
– nadlabak
– tiagosousa
– credits for the JiT Beta, forum.samdroid.net/f9/samdroid-turbo-1301/
– -FuFu-
– DAGr8
– credits to all others who would like to remain anonymous

Changes in this Version:Our new Open Recovery mod is based on the Open Recovery v1.42 and includes features such as Apps2SD, Theme install, build.prop changes and some other enhancements. Please note – you use all features on your own risk, take a nandroid backup before applying any changes.

New features in this version are:– density setting
– remove stock apps
– remove pico langs
– DNS Fix (thanks nadlabak)
– build.prop changes
– Theme install (thanks -FuFu-) and also a bootanimation install
– overclock for firmware 2.0, 2.0.1 and 2.1 (if you are not sure if your firmware is supported, please check the adress of the modules in the GOT_MOD.sh script to verify that the the adresses are set correctly)
– recovery launcher (you now able to load other Open Recovery’s in our recovery mod, seperate readme provided) by DAGr8
– First attempt at G.O.T bootanimation (install via Theme/bootanimation option)

All features have a restore/remove funktion. On first launch the script will take a full backup of /system/app, also backup your framework-res.apk, services.jar from the /framework folder, build.prop and all the stock fonts.

Remove Stock applications (in remove menu)The remove stock app feature is based on the remove.cfg in /OpenRecovery/GOT, you need to edit the file (when you are running Windows do not use notepad or windows editor to edit the file, use notepad++ for example)
You can chose the apps you want to remove, a description is provided in the header of the file. If an app is missing, just add a line withe the name of the .apk file of the app
App names with a “#” won’t be deleted by the script, only apps without the “#” will be deleted

Theme install and bootanimation install
Themes must be copied to /OpenRecovery/addons/Themes or Bootanimation folder (see readme in folder) credits to -FuFU-
Recovery LauncherRecovery launcher is a very fresh new addition – thanks to DAGr8
You are able to switch between Open Recovery Versions/Mods easily with the Recovery Launcher (see readme for details)

Apps2sd:
Before you use apps2sd script, please take a complete nandroid backup and also backup all data from your sdcard.

2.2.1 enhancements:You may note some settings already for 2.2.1, these are preliminary settings at the moment to prepare for the next version of the OR (due soon with entirely new Theme)

Whilst our cooperation with nadlabak and others is progressing very well (we had a little breakthrough yesterday), we are reworking our G.O.T OpenRecovery.

Since some of you have expressed their unhappiness with us “teasing you”, let us comment on this from our side:

1. It was our attempt to keep you posted and informed about what we do and where we are. We will, under no circumstance, release any of our work before it meets our own minimum quality criteria. In the event that a release fails to meet these quality requirements, we will simply go back to the drawing board and continue to improve it if we can. Some of the bugs encountered in firmware releases are bugs that, without access to the kernel, we are unable to fix. In such an event we need to continue to wait for an improved kernel update.
2. We believe and try to continue to believe it is the right approach to communicate to you on a regular basis to keep you posted rather than simply posting releases.
3. As such, we are still hanging on to our approach, but with the following amendments:
– We will no longer issue any indication of timelines. Questions such as “why is it taking so long” or “when?” will be simply ignored and no longer be commented on.
– We will no longer be able to keep you informed in detail but will just post and issue simple and general status messages.
– If we encounter bugs we can fix, we will fix such issues prior to releasing. If we encouter bugs we are not able to fix and that we classify within our group as severe, we will not issue the release.

It is somewhat disappointing to have to do down this route but apparently we cannot please the community as a whole and therefore are trying to find some middle ground.

As stated below, we have now had the software for a couple of days to test and verify. What we have completed is:

a) root was obtained
b) Overclocking was obtained by the mighty nadlabak
c) We could complete 3 days of daily usage testing

What we, GOT and the other developers are struggling with is the following:

– The values we are getting after OC with the new 2.6.32 Kernel from Motorola are, whilst not bad, not overly impressive for the “new” kernel we all have been waiting for
– The performance of the stock ROM by Motorola is, to say the least, not good enough for daily use and fails our testing continuously. We have failures in Wireless LAN, applications not opening (launcher loses focus), minor lags in apps and launcher, AGPS not working and other issues (such as WHY would Motorola still insist of loading all this “crapware” like the interim voice dialer hogging the entire memory, the old & outdated launcher 1 on a 2.2 built when much better alternatives exist such as Google Voice&Search and the standard 2.2 launchers from Google?)
– As such, we believe that the best way forward is for the developers to use the kernel and integrate it into their custom builds. Even if a performance boost is not obtained this way, the ROM developers can access the proprietary features of the ROM itself, which means a CM6 or other mod integrating this kernel is a much more stable approach than releasing the Motorola stock ROM as it is.

Whilst we encourage the developers we are cooperating with to continue down this road, we will seek an updated/new/better froyo beta from our sources. Since Motorola confirmed on facebook that the user trials start next week, we hope to obtain newer and updated versions of the froyo beta’s as Motorola prepares for the user trials. We will keep you posted.

Our sources have advised us that the initial test builts for froyo have started to be compiled. We will try to find and flash them and report back to you asap.

UPDATE!!!!

Guys,

We know you are impatient to get your hands on it, but we need to do some sanity checks and recompiles before we unleash it to you hungry wolves. Why you ask?

1. The 2.2 kernel is sure powerful, but without the ocerclock and other modifications we all, over the months and year by now, learned to use and love, you will not be happy. We sure are not 🙂
2. Since this is, as we stated, an internal test build, we can do some modifications on it/with it that we have already had to do (or others had to do) with the existing 2.2 versions out there. This hopefully will result in a more stable and “ready” release for you guys to get your hands on.
3. Our team has tested the device to death as much as possible, and our test results reveal that there is just too much different results with different users. Example: Some have a working WPA2-encrypted WLAN, others, including me, do not. Now, we know there are developers out there that simply dont care and release it with such behaviors, but we have some sort of minimum quality standards and reputation that we want to ensure once we launch, we are ready and able to tell you “ah this happens you do that”.
Nothing is more frustrating for us than a user comment “this and that happens”, and we only can shrug our shoulders.
4. At the moment, with the “simple” 2.2 kernel and software build as it is, we do not believe that this is ready enough for you guys to use as software for daily use.
5. The well established developers are supporting us on this built. They and we will try to solve the follwing before we are ready:

– Overclocking possible – current status – NO
– WLAN works – current status -NO
– Double USB (the standard Froyo/Google mount message AND the Motorola USB at the same time), this is very confusing and problematic

Once this is sorted, we will launch. Next question I expect – When ?!?!?

Well honestly no idea, BUT!!! we expect something in the next days, or at the latest by the end of the week. If a developer beats us to it, that is fine :):)