[ROM Tools] Team Get~R~Done D2G Rom-er Tool - a tool Convert D2 Roms for use on D2G

[bobrowley]

Flashed stock SBF, then wiped all, updated Liberty then romer v6, but still could not turn bluetooth on

 

[evoBaron]

donation in the 3 digit range coming from me when sensors get done! Thanks for all the hard work guys!

Sent from my DROID2 GLOBAL using DroidForums App

 

[eyan414]

Just noticed that I can't turn Bluetooth on either. Not a problem because I never use it, but I wonder if maybe it's linked to the idea someone raised in the Think Tank thread about radio files.

Running Liberty 1.5 if it matters. Willing to test anything you folks come up with.

Sent from my DROID2 GLOBAL using DroidForums App

 

[buryboi]

I believe I know why bluetooth is not working for some of you.

For those of you that dont have working bluetooth, how many of you updated to the latest OTA before flashing the D2 Roms? I was just comparing the OTA to my nandroid (pre-OTA), and there are some differences relating to bluetooth that would not get overwritten by flashing a rom.

If you SBF'd you'll need to get the OTA before flashing a D2 Rom and the Romer.
I'm not 100% positive, but there is a good chance that this is part of (or all of) the issue with bluetooth.

 

[bobrowley]

Hi buryboi,

It could be, cause I have not updated the latest OTA, just flashed SBF then updated Liberty and Romer. But BT worked fine after SBF'd and before flashing Liberty + Romer.

 

[buryboi]

Bluetooth would work fine after the sbf...that uses the old radio firmware. The update replaces the radio firmware as well as some of the bt_init files in /system/bin. If you flash the romer without the OTA, you're getting the updated bt_init but still have the old radio firmware. They may not properly communicate.

I'm working on assembling a complete, rooted, deodexed, busybox, OTA Blur rom that would update the radio. This would let people revert to stock after trying D2 roms without needing a good nandroid or sbf.

Team defused stock rom only flashes apps and frameworks so it can't revert you to stock after flashin D2 roms.

Sent from my DROID2 GLOBAL using DroidForums App

 

[bobrowley]

Thanks for clarifying and your great work! I am going to try and let you know later.

UPDATED: bluetooth works after get OTA updated, and flashed liberty + romer v6.

Good job man, thanks!

 

[13th angel]

Then it comes down to can you include these files in the romer just to avoid these problems down the road?

Sent from my Fissioned D2G

 

[buryboi]

Great point 13th! I only realized that might be an issue yesterday...Since we haven't had any Fission updates since before the OTA, many people that have had their phones that long, never got the update. I suppose I could add the radio firmware to the Romer. It might be redundant for those that already have the current firmware, but it would eliminate some of the issues (unfortunately there isn't yet a reliable fix for the sensors).

Regardless it may just be time for v7.

On a side note, I'm uploading a complete Deodexed, Rooted Stock 2.4.330, that includes the radio update. This will let you revert from a D2 Rom back to complete Blurristockiness with the most current firmware without an SBF or a Nandroid. From there you can reload clean Fission if you want.

It should also allow those on Fission that never got the OTA to update the radio and try D2 Roms with bluetooth!

I need a couple beta testers before I post it. PM me if you care to give it a shot and I'll send the link. (I'll edit this post to remove this request when we've had enough successful attempts to warrant its own thread).

 

[aaeigs]

I can't figure out why no BT, mine don't have this kind of issue, BT's working fine, but still bad GSM signal.

I wonder if I can change the baseband of my D2G for a better signal, but I heard some rumors that changed the baseband may get you unactivated and that's a risk I can't afford.
Anybody know the right answer?

 

[na8flush]

The sensors need to be disabled using the sensor zip in the first post of this thread. Flash through Clockwork bootstrap to turn them off, flash again to turn them back on.

We have a thread discussing possible solutions. We may have a fix for CDMA users (Compliments of WoZzy), but we need to test it a bit more, and see if we cant find a way to implement the fix without forcing everybody to buy an app from the market.

Not to bug you guys, as I'm sure you busy with your own stuff. (And I should be with midterms and all), but is there any word on the fix for CDMA users? I'd totally stay in the country for a while and cough up a few bucks to get the sensors working.

 

[buryboi]

I should have announced it, but...that fix was unstable, and didn't work all the time...also caused random reboots and terrible battery life. We're back to square one. Sorry to get your hopes up.

 

[Alcia]

It's perfectly understandable. Tis why things are test before release. Sad that we're back to square one though. Something will probably be figured out eventually.

 

[na8flush]

Bummer. I have faith it'll be figured out eventually, just a matter of time. think ill go back to stock, then try fission. Totally donating a beer or twos worth to your site when its figured out.

Btw, im just starting to learn about the droid, any good books or sources from a technological pov? I've started reading pro android, but that's more of a programming perspective.

Sent from my DROID2 GLOBAL using DroidForums App

 

[13th angel]

Bummer. I have faith it'll be figured out eventually, just a matter of time. think ill go back to stock, then try fission. Totally donating a beer or twos worth to your site when its figured out.

Btw, im just starting to learn about the droid, any good books or sources from a technological pov? I've started reading pro android, but that's more of a programming perspective.

Sent from my DROID2 GLOBAL using DroidForums App

Most of us have just learned from trial and error... i might check out that book though (if you would recommend it?), been wanting to get into the programming side of it.