[ROM] [FINAL] [06.26.09] MightyROM4 w. OEM BASE Included

[OR78]

Originally Posted by heydjbobby74

What do you guys like about the new Reborn that you dont like about Mighty ROM 5? Just curious, I am new to flashing ROMS and I think MR5 is great! Any thoughts?

Its based on personal pref. If you want day to day use that is very stable then R3BORN is for you. If you like playing with new OS then Mighty5 is for you. Keeping in mind that 6.5 is not official it still has too many problems for day to day users. Yea its cool and sharp looking but untill the release is official and the bugs are worked out its not there yet IMO. You just have to test them out for yourelf to decide or take our word for it. The one nice part about being able to use 6.5 is that we have bada$$ people on here that make it better but they can only polish a turd so much. Thanks to Mike its one gleaming turd. No offense to Mike of course.

[whatsleft4her]

i found this on xda its for cdma and i figured id share it with my fellow mighty rom fans.

[MN-Joe]

Originally Posted by whatsleft4her

i found this on xda its for cdma and i figured id share it with my fellow mighty rom fans.

How about sharing the URL so if we have questions about it we have the background.

[BRIVERS73]

Originally Posted by MN-Joe

How about sharing the URL so if we have questions about it we have the background.

Right here post 526 is where it starts...

[mcw]

Originally Posted by sumo911

The only two 'network adapter' settings I had to change was 'Bluetooth PAN Driver' and the 'NDISWAN Miniport'; it was pretty quick and fast.

I have created three different "fixes"...
A = Only changes Bluetooth PAN Driver to DHCP
B = Only changes Remote-NDIS Host to DHCP
C = Does both

Registry locations:
HKLM\Comm\BTPAN1\Parms\TcpIp
"EnableDHCP": DWORD:0x0000001

HKLM\Comm\RNDISFN1\Parms\TcpIp
"EnableDHCP": DWORD:0x0000001

Since I haven't upgraded to the new ROM yet, I was getting my SDConfig ready, and wanted... If someone can confirm that the NDIS registry actually needs to be changed, let me know.. In MR 4.16, this is what I found:

Bluetooth: 192.168.0.1/255.255.255.0

NDIS: No IP, Subnet of 255.255.255.0

[land2634]

Originally Posted by LilRico

Wow.. Well, as long as you got it working, that's all that matters. All of my stuff are in the \Windows folder, but they are in .wma format. What are yours? MP3's?

Yeah they are MP3's.

[ItsDon]

Originally Posted by whatsleft4her

i found this on xda its for cdma and i figured id share it with my fellow mighty rom fans.

Wow! Works on my phone running WM6.5, nice skin! It has some issues like the 'contacts' soft key is inoperative but otherwise this dialer is hot! I have never had my phone ring faster, even with the WM stock dialer. The phone lights up during the first ring and starts playing the ring tone before the second ring - awesome!

[LilRico]

Originally Posted by mightymike

Definitely getting the Pro2 once its released.

Without a doubt.

Psh, who you're kidding? Day 1 and I'm game!

[dnalevelc]

So far this Rom is the smoothest out of all of them. It has one issue and it's the Bluetooth issue I get on every 6.1 rom I have used. Many times I turn on bluetooth and it doesn't come on. I soft reset and bluetooth is on. It's annoying, but I can live with it for such a polished rom. Oh and it's an issue I had on stock as well, so it's not just cause of cooked roms.

[dementedgerbil]

mmmkay so im sure i look like a idiot asking for help with my first post on these forums, but here it goes


got my touch pro in the mail today, i was refered to mightyrom by a m8 at work.

launch the updater, phone gets too the 0% screen but the activesync drops for somereason and i cant seem to get past this.

ive been going threw dozens of threads and i see people saying to do this and that but with thousands of posts and tons of people suggesting diffrent things its getting a bit overbearing

so heres what i got:

brand new touch pro
a copy of MightyROM4.16_032509R

i sync up, it starts its thing then bam sync drops, phone stalls at 0% and i get error msg (262 i think it was)

pop out battery and turn phone back on, try 100 more times but i just dont quite know what im doing wrong.

am i missing some important step here?