Database Info

[RADIO] Evo-1.39.00.05.31

I AM NOT RESPONSIBLE FOR THE "BRICKING" OF YOUR DEVICE. FLASHING A RADIO IS DANGEROUS, DO NOT PULL THE BATTERY OR STOP THE UPDATE AT ANY TIME. FOLLOW ON SCREEN INSTRUCTIONS AND BE PATIENT.
That said... let the fun begin!!!
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
INSTRUCTIONS FOR FLASHING:
- Download the EVO-1.39.00.05.31-radio-signed.zip from below
- Put it on the root of your sdcard (top level)
- Reboot to recovery and run .sh or .bat file to gain custom recovery
- Select "Flash zip from sdcard" in recovery
- Select "EVO-1.39.00.05.31-radio-signed.zip" and confirm the flash
- Ath the bottom it will say "Reboot via menu to complete installation" do as it says and select reboot in the menu
- it will then say "writing image" then reboot to a screen with a phone and a green arrow
- then it will reboot again showing the same screen with the arrow but have a little status bar.
- after that it will reboot into android and prompt u with a congrats on flashing the new radio. press ok ansd cancel the firmware update (its useless )
- navigate to settings>About phone>Software information
- under Baseband u will see "1.39.00.05.31"
- your done now. enjoy the awesome new radio <~~~ congrats its not a brick!!!
DOWNLOAD LINK

Thanks toast!

Sweet thanks
Wait where's the link lol

Download Link
Download Link PLZ

is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
thanks!!

toast your a monster
Man what a good job your doing toast I can hardly keep up I am loving my rooted Evo I/O Phone tho thanks to you I am even sending someone my Incredible to see about root cuz I sill never use it again lol

joeykrim said:
is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
Click to expand...
Click to collapse
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.

What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?

could this be a fix for the weak Wifi radio?
which radio is this?

toastcfh said:
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.
Click to expand...
Click to collapse
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a simple way to determine this? compare radios? what partition are they kept in? mtd2?
sorry bunch of questions as my thoughts flow

ChrisDos said:
What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?
Click to expand...
Click to collapse
4d9404ebc30c32b20a7b8fa304225680

joeykrim said:
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a way to find this out?
Click to expand...
Click to collapse
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed

So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!

pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
this will not replace the ota. this will only replace the radio.img and yes u must be root and have access to a custom recovery

pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
somebody can correct me if im wrong, this is just what ive gathered from reading.
yes, apply this radio udpate.zip after rooting using's toasts method and running his recovery. when the recovery UI pops up, then load this radio update.zip file posted in the OP. that way you'll still be able to keep root and have the latest radio.
this does not replace the OTA update, this update only patches the radio, it does not patch the software.

Call me stupid, but what are the benefits of flashing the radio?

Thanks for the quick response guys. So are we free to apply the OTA ourselves after we root and use this radio upgrade? I keep remembering toast saying not to apply any RUU's (not sure if the OTA update counts as an RUU)
jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
Since they don't release the changelogs, we don't know what has changed. But as toast said, there must be a reason they updated the radio.

jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
You must not be the only stupid one, Im stupid too, what does this new radio do?

arkshel said:
You must not be the only stupid one, Im stupid too, what does this new radio do?
Click to expand...
Click to collapse
could increase signal or optimize hardware. the radio controls a lot of function of the device.

thanks. Everything went well.

Radio 2.15.00.09.01 with PRI 1.77_003 w/ RA Recovery incl Flipz Flashable

Here is the RA-Recovery, Extracted radio, Wimax and PRI from the update directly from Sprint. Must be S-Off. Rename to PC36IMG.zip and put on SD card. Boot into Boot loader.
USE AT YOUR OWN RISK. I Tested it thru the Bootloader (pc36IMG.zip way) but I am not responsible for anything that Happens!!!!!!!!!!
2.15.00.09.01.zip Thx Vivix729
Mirror 1
Mirror 2
Flashable version from Flipz http://link.geekfor.me/radio215000901 Does not include recovery. Flashable thru Recovery
The reason for the File size is I always add the Wimax flash with all my radio flashes that I have done to be safe that they both match. Also this has RA Recovery as well for easy flashing of the recovery as well.

hmm, so the 3.29 OTA contains a new radio afterall

tatnai said:
hmm, so does the 3.29 OTA contain a new radio afterall?
Click to expand...
Click to collapse
Yes in deed it does. dated 9-20-2010
James

Wait... WTF?!
Cal just released all the NV and PRI stuff and did not mention anything about a new radio. In fact, his post still lists the older one as the latest.
Where is all this stuff coming from and how is it coming out of no where?
I just did CALs zips for NV and PRI... is it safe to do this right over the top of that?

edufur said:
Wait... WTF?!
Cal just released all the NV and PRI stuff and did not mention anything about a new radio. In fact, his post still lists the older one as the latest.
Where is all this stuff coming from and how is it coming out of no where?
I just did CALs zips for NV and PRI... is it safe to do this right over the top of that?
Click to expand...
Click to collapse
i uploaded the OTA update zip... it seems that i t had a lot more than we thought.
this is for real...

NICE!!!!
10char

I do not see why not. I did his update yesterday. This is not for Flashing in Recovery. Its for Flashing in the Bootloader.
James

edufur said:
Wait... WTF?!
Cal just released all the NV and PRI stuff and did not mention anything about a new radio. In fact, his post still lists the older one as the latest.
Where is all this stuff coming from and how is it coming out of no where?
I just did CALs zips for NV and PRI... is it safe to do this right over the top of that?
Click to expand...
Click to collapse
Calk released all of that stuff before this latest OTA though, thats why this is now newer. No worries though, I'm sure Calk will have all the latest stuff in flashable .zips in no time!!

The OTA update I recieved came in 2 files/apk's here they are if anybody wants them:
It is 2 different apk's here:
1: http://www.mediafire.com/?cljyvv281l1b000
2: http://www.mediafire.com/?i2ypi9121snmpyo

God, I hate Rapid****.

Someone send me the file, I'll host it on my FTP >.>

Send me a PM with some FTP info and I will post it there.. 25mb upload pipe here

Lol, wow that was quick.. within 15 min of posting max reached...

See updated Original post
James

Nevermind......

Dude, stop using Rapid****. Put it on mediafire or something that doesn't completely suck.
And once I can get it downloaded, I'm going to put it on my webspace as a mirror.

Rapidshare is a POS. New link posted Rapidshare links are removed now

here is a mirror for u guys...
http://www.multiupload.com/S0C582CVZJ

So Guys and Gals. Feedback???
James

this is on flipz' site
http://geekfor.me/evo/radio/baseband-215000901/
you dont need to rename anything. just download it and then flash.

OTA_Supersonic_3.30.651.3-3.30.651.2 11/10/2010

Here is the latest,
It contains a new boot.img and recovery.img
http://www.unlocksolutions.us/XDA/OTA_Supersonic_3.30.651.3-3.30.651.2.zip
Anyone have any information on it ?

well thats intresting?
bad block fix maybe?

Who knows, i'm s-off for now
Updating
ill take a shot.

Ok people,
Updated the phone. Looks like root and nand unlock still possible.

tried to update but i got an error message!

What error ?

3.30.651.3 will address issues where users are experiencing power cycling when accessing the camera through some applications.
Sent from my PC36100 using XDA App

Hmm it updates a lot of crap just for a fix for camera... Anything else ? It updates the whole framework folder, fotaboot etc.

Mine threw me an error. I did a Nandroid, then downloaded and installed the new OTA.
It says,
E:Error in /cache/Supersonic_3.30.651.3-3.30.651.2_releaseziblddc3oqo05zyk.zip
(Status 7)
Installation aborted.
Weird, so far I am thinking maybe this is only for newer Evos that came with 3.30.651.2 as the default ROM (the new hardware 0004 with the new camera chip).
Mine is a Evo version 0003 with the Epson panel. Bought in July of this year of course.
Think Sprint is trying to throw us some curveballs or put a bandaid on their newest.

Doesnt make sense,
My girlfriends evo is HW V3. I updated it.
Mine is HW V2-3 and its updated now.

ok i guess this is the .30 you were talking about..how do i apply this ...as an update.zip or PC36IMG.zip thru HBOOT?... like i said on my previous post on the other thread of HBOOT 2.02 off i dont have root anymore... please let me know so i do the right thing...thanks

eldiablito004 said:
ok i guess this is the .30 you were talking about..how do i apply this ...as an update.zip or PC36IMG.zip thru HBOOT?... like i said on my previous post on the other thread of HBOOT 2.02 off i dont have root anymore... please let me know so i do the right thing...thanks
Click to expand...
Click to collapse
You cannot just "install" the file posted. Well, at least I cannot!
Here is what happens when I try and install it (both from OTA and flashed.)
Same results, see picture.

This is not the update i was talking about. read my thread i have pointed to it so many times already.

ricsim78 said:
You cannot just "install" the file posted.
Click to expand...
Click to collapse
im sorry for the dumb question...so how do i apply this to my phone? do i have to root it first or can i just apply it....im guessing i need root and a recovery image to apply the zip isnt?

nv i just saw i need a recovery image to do it...

amoamare said:
Here is the latest,
It contains a new boot.img and recovery.img
http://www.unlocksolutions.us/XDA/OTA_Supersonic_3.30.651.3-3.30.651.2.zip
Anyone have any information on it ?
Click to expand...
Click to collapse
interesting.
definitely has a kernel (boot.img) and recovery.img
majority of patches are done to /system/framework - 44 files
including - com.sprint.hardware.twinCamDevice.jar.p
system/lib/modules are also included to go along with the kernel (boot.img)
system/etc/otacerts.zip is also present
everything else is standard for an OTA, it seems.
doesn't appear to be significantly changes...also, the OTA server isn't offering this to EVOs on 3.29...

joeykrim said:
interesting.
definitely has a kernel (boot.img) and recovery.img
majority of patches are done to /system/framework - 44 files
including - com.sprint.hardware.twinCamDevice.jar.p
system/lib/modules are also included to go along with the kernel (boot.img)
system/etc/otacerts.zip is also present
everything else is standard for an OTA, it seems.
doesn't appear to be significantly changes...also, the OTA server isn't offering this to EVOs on 3.29...
Click to expand...
Click to collapse
Right - and this won't be - Sprint reps are being told to verify the HW version and Build version before doing any camera hardware swaps, etc. as putting a 3.29 build camera in a device with 3.30 build will cause nuclear meltdown
I see this causing a lot of problems in the future for Sprint (and HTC) as new updates come out - and for ROM devs as well - we now have two different frameworks and two different Evo types.... the potential for a lot of noob issues is there....

jerdog said:
Right - and this won't be - Sprint reps are being told to verify the HW version and Build version before doing any camera hardware swaps, etc. as putting a 3.29 build camera in a device with 3.30 build will cause nuclear meltdown
I see this causing a lot of problems in the future for Sprint (and HTC) as new updates come out - and for ROM devs as well - we now have two different frameworks and two different Evo types.... the potential for a lot of noob issues is there....
Click to expand...
Click to collapse
yep...i was just thinking the same issue.
The question is all evos should be able to get this due to the fact it should be backwards compatible.

zikronix said:
yep...i was just thinking the same issue.
The question is all evos should be able to get this due to the fact it should be backwards compatible.
Click to expand...
Click to collapse
Yeah - should be. I have noticed some issues with Myn's ROM on the 3.30 build that I am not sure if they're related to 3.30 or for some reason my hw v002 phone.... (pissed that I got a v002 when I got it replaced for a 4G issue - had v003 and could OC to 1.226 but now with v002 can't get above 1.15)

3.30 isn't supposed to work on hardware 0002? Works on my phone...

[HOW TO] Flash Froyo without loosing downgradability and keeping cam flash

Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder)
• Once restored pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!

I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.

Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.

sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....

conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.

As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.

racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?

Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf

Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?

Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin

Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149

Thanks mate, my DEFY is perfect now.

Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!

Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.

conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.

Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy

Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.

racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol

Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?

Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)

[Q] Can VRLG1 be downgraded back to VRLF2 if needed?

I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks

newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.

yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.

droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.

pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.

Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out

Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.

I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?

excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:

Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.