I have a QWEST 6800 w/ROM v2.13 & Radio 1.39
 

hey fellas i havent seen really anyone else with a qwest mogul.
Nor have i seen much feed back with the v2.13 ROM and or 1.39 radio
I would just like to let u guys know that i have had no problems with this ROM version or the radio. pretty darn stable and no blue tooth issues to speak of/ if there was or is a way i can copy my rom for u guys to try , let me know./ i didnt get a disc with this version on it, but if i do a hard reset it will automatically restore to default settings, so i know that the complete ROM is imaged on my phone/ specially u sprint guys would benefit probably most from this version/ anyways just thought i would mention it for what its worth.

We've got someone running it already. We'll test extensively for a bit and see where it goes. I'll be comparing differences and trying to pinpoint all the goodies.

Thanks a mil bro, this is a great contribution!

- DogGuy

if there is an nbh out there, i'll throw it on my mogul for testing purposes...running sampson's WM5 now, going to try out the stock alltel WM5 before trying dcd's clean ROM...wouldn't hurt to try the qwest rom as well...lol

EDIT - it's over at xda-dev => http://forum.xda-developers.com/showthread.php?t=343758

I made up an nbh from the raws so people can flash this with just the RUU and no extra work. It has no radio as usual from my nbhs. Enjoy!

ftp://up.ppcgeeks.com/Titan/Users/Im...RUU_signed.rar

looks real similar to 2.14 versions

"Adobe Reader"="2.00.261818"
"AVDecDll"="1.00.070110.0"
"Camera"="4.05.26938.00"
"CyberonVSD"="1_2_b070626_0"
"DShow"="1.00.070213.0"
"HTCWMPPlug"="1.07.0412.0"
"IOTA"="20070427"
"LockStreamDRM"="1_1_x_070209"
"MFCDLL"="1.0.20060406.0001"
"mHub"="6.37.070320.X0"
"RingtonePlugin"="1.00.070124.0"
"ShareDLL"="2.0.070404.0000"

It IS very similar, except that the BT sound is LOUDER and it doesn't lock up the device when a BT headset is disconnected while off (which 2.14 does). It DOES disable BT on some tests like 2.16 did, but without all the other problems that 2.16 had (D-pad issues, etc).

So far, this seems the most stable of the official releases. More testing is required, but it may be a good candidate for a new ROM core.

Thats great news, i was nervous that i might have done it wrong. I gues the real test will be to see how it runs on the sprint moguls/ i couldnt imagine it be any different from how it runs on mine/ a mogul is a mogul right. did the radio not get included or u just dont add it? if u guys have any questions about the ROM's performance or stability / i could help answer a question or 2 since this is all ive been running since i owed my mogul/ great work IMacokman and Dogguy/
i know u guys are gonna be able to put us together a great hybrid ROM for our moguls/ and bring honor back to our beloved 6800's

oh yea i almost forgot to ask if u seen any big differences?

dishe, could you please cite your sources, or give detail on your own testing to produce these claims. i have compared the following files from 2.13 and 2.14:

btagext.dll
bthamb.dll
bthci.dll
bthcsr.dll
bthsc.dll
bthuart.dll
Serial_BTUR.dll
BT_FIR_Param.txt
BT_Init_Script_TI_300.txt
BT_Init_Script_TI_311.txt
BT_Init_Script_TI_331.txt
BT_Name_INFO.txt
AudioPara.csv
AUDPP_PARAM_TABLE_SYSTEM.TXT

THESE FILES ARE IDENTICAL. Compared with WinMD5.

The OEMDrivers rgu contains the following in 2.14, but its absent in 2.13:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Keyboard Layout"="00000409"

Otherwise the rgu's are identical.

OEMDrivers that ARE different:
SDHC.dll
battery.dll
msm7500usbfn.dll
rilphone.dll
allledmgr.dll
cif.dll
keybddr.dll
virser_atcmd.dll
virser_dmr_dpram.dll


While I really do appreciate the OP's effort to obtain this rom for us (I like to have as many sources as we can find) I do not see anything 2.13 offers us that we dont have from 2.14 (yet)

Also, I have not looked, but I beleive ImCoKeMaN is packing these into a donor .nb using the 2.09 XIP/kernel. That could have some effect on testing results.

i was wondering if i should have done a hard reset before i made a copy of the raws files/ because i do use a different comm mgr and and applied a few reg tweaks and some over progs that might possibly affect what is copied/ or is the raw files the core files which always stay with in the rom?

Being unable to force the crashing failure to return from standby is a plus. I spoke with someone running it while they were on BT and the quality was slightly echoy, but very good. Other than a forced disconnect, we have not been able to replicate the DSOD that I personally experience with Alltel at will. More testing is needed of course, but if you simply removed the crashing from Alltel's faults, you'd have my ideal BT rom.

- DogGuy