[Release] OFFICIAL FRG22D - Deodexed, SU and Busybox

[dmbfan36_23]

[quote=skeezicks;782838]

Edit: in fact, after a couple hours of futzing around, I was unable to get Swype working on this build. Happily, I backed up my FRG01B at the start of this using Rom Manager, so I was able to revert without a hitch. But does anyone know what the problem might be and, more importantly, how to fix it? Having rooted and flashed Froyo, the Swype installer doesn't work anymore (as indicated above). Any help would be appreciated. Although I'm happy to live with the phone I've got now -- rooted Droid 1 running Clockwork's version of FRG01B -- I wish it weren't such an iffy thing to move from one Android version to another.

Very weird... I'm running Swype on my Droid 1. I had FRG01B, rooted w/one of P3's kernels. Applied this FRG22D Odex update w/Clockwork, installed a custom kernel, uninstalled swype, re-ran the swype installer (I still had it on my SD card). Everything installed as expected and it appears to be working fine.

[dwoid]

Just to add one thought here...

Even if you need or prefer Deodexed, just having the Odexed version available sort of helps to verify that the sources (in this case the full FRG01B and the FRG22D patch) are from Google/Moto/Verizon, because the encoding signatures in the Odexed version comes from them.

This is one of the pieces that was missing from the earlier full leaked FRG22D release from another developer, and the fact that it never was made available in that leaked version contributed to doubts about authenticity.

metiCkOne has been extremely transparent and helpful about this FRG22D release, I personally have no doubt that this is all the real thing.

And it runs great too .

Thanks again, metiCkOne!!!

I can tell you why I prefer Odexed, but I can't speak for anyone else... I simply prefer to stay closer to stock. So if there's an Odexed version and a Deodexed version of a stock-rooted OS, I'll always choose Odexed.

Back in the early Android days I liked doing themes, but quickly got tired of it when I noticed every time I upgraded a themed app it overwrote all my theme work. And now days I use ADW launcher which allows use of its own custom themes.

This does not prevent you from using custom ROMs. Custom ROMs overwrite all of this stuff anyway, providing the themes that the ROM developer has put into place.

Anyway, it's just another choice that you get to make if you're rooted.

[leonozug]

I flashed the Deodexed version just now and Rom Manager would not work, kept giving me an error. Damn. I wanted to put that FRG22 Droid 2 theme on it. Going back to LFY 1.5 I guess.

[dwoid]

Interesting... ROM Manager is working fine for me, I've used it a lot since installing this release... And I did not wipe data, only wiped cache.

Are you up-to-date with Market's version of ROM Manager?

Also, did Superuser register ROM Manager properly?

I flashed the Deodexed version just now and Rom Manager would not work, kept giving me an error. Damn. I wanted to put that FRG22 Droid 2 theme on it. Going back to LFY 1.5 I guess.

[leonozug]

Dwoid, I deinitely did everything the correct way...Set CPU was up and running, installed Rom Manager and it asked for premissions. Very strange, that never happened to me before. Maybe I'll try it again later on tonight, wouldn't hurt.

[pigpen]

Hey leonozug, every time rom manager has failed to make a backup or install a new rom, i've cleared the cache from the menu, and then reflashed the clockworkmod recovery, and then the SPrecovery, and then back to and flashed the clockworkmod recovery. after that series of reflashes, after any rom manager update, rom manager has successfully created back ups for me or been able to install a rom. I always use the "install rom from SD card" function. and it has always worked for me. This new build is awesome, you should definitely give it another crack.

[metiCkOne]

Hey guys, I confirmed the issues with rom manager. Its not the rom its kous's server. The cm6 release killed the recovies. He should have a mirror up soon. You can still flash sprecovery through it.

[pigpen]

Hey guys, I confirmed the issues with rom manager. Its not the rom its kous's server. The cm6 release killed the recovies. He should have a mirror up soon. You can still flash sprecovery through it.

Wow really? im running the stock recoveries now and i reflashed this morning when i woke up. i installed your FRG22D and i'm not having any issues with it. I use the clockwordmod recovery.

Rom manager version v2.0.2.6
clockworkmod recovery version 2.5.0.1
SPRecovery version is 0.99.3b(standard in Rom manager)

[Phiber187]

I still think the update.zip from sprecovery is by far easier than using rom manager... it's 5 mins versus 30...

[nxmehta]

Personally I would recommend the deodexex build because there is always a possibility that somebody may develop a nice theme for the build that you want to try out. If you are running the odexed version you would have to flash the deodexed version to get the theme on and that would mean setting up your device all over again.

Its just nice to have that peace of mind of the available option whether you take advantage of it or not.

There are no cons to running the deodexed version but there is a downside to running odexed builds (stuck with stock theme)

This is incorrect. By deodexing you are removing code that contains device specific optimizations. Think of it like gcc -O or something like that if you are familiar with C programming. Here are details that explain what deodexing actually does: Deodex Instructions

Personally, I have no use for any themes. If I want my Droid to look all fancy I'll install a custom ROM, which will wipe this OS anyways.