|
|
||||
Re: Qwest + Mogul = No Update Ever?
you guys need to stay away from doing anything with that "Special_4350.nbh" file...its leaving phones bricked in certain situations. read ImCokeMan's signature line; he's got a bricked Mogul to prove it.
__________________
Evo 4G Powered by Dev-Host roms
|
|
||||
Re: Qwest + Mogul = No Update Ever?
Incredibly well written Post Kiawud!
Where were you when i started my upgrade a month ago? ![]() I have had a long and arduous effort trying to make this upgrade, but i am very glad that i did. i intended to write an upgrade post as well since there is so little Qwest specific upgrade info out there, but i still haven't got my mogul working 100% (plus you beat me to it...swEEt!) I did the same as you. i let the sprint customizations run in the 3.35 upgrade which hosed my data, but i had my MSL and still couldn't edit my epst. i am wondering if i could have called qwest and got everything working without the downgrade, but i was worried they might catch that i had upgraded, so... i finally got my downgrade to work. ( i used the SD method, left Olipro 2.40 in place, loaded my 2.13 rom, then loaded the 1.40 radio you gave me a copy of. my radio install failed and my phone started continually rebooting after a few seconds of trying to start booting and no amount of reloading the 2.13 radio or 1.40 or 1.47 radio would get it out of this reboot scenario. i finally unpacked all the files from the sprint 3.35 rom into my SD card and renamed the sprint .nbh file to TITAIMG.nbh and ignored the special_4350.nbh file. i had to pull my battery a couple of time for about 20 seconds because the phone did not want to see the image file or load it from the SD card. finally it began to load and i was able to get the 3.35 rom installed into the phone. From here i did not let the customizations run, but simply loaded the 2.13 rom and then the 1.40 radio again. each time i pulled my battery for 20 seconds and they both finally loaded. I still had no data or the ability to edit my epst settings, so i called Qwest who had me dial ##970697# which allowed me to edit the msid and mdn #'s. this got my phone working and my data working as well. i did not check to see if my wifi worked, but assumed that it did. i then reloaded 3.35 using the activesync connection and the sprint .exe file, skipped the "tapping of the screen to setup" after it booted the 1st time and went straight to DCD 3.0.1 this time everything went perfect, except i still have no wifi. turning on the button and/or enabling wifi from the comm manager do nothing. once i solve this problem, i should be in the same boat as you and be able to assist others getting their mogul's running the way they should and not the feature and stability limited way qwest is allowing them to remain. |
|
||||
Re: Qwest + Mogul = No Update Ever?
chirodj5:
I had the same reboot problem when I downgraded to Qwest 2.13. I didn't try relocking the bootloader but I did do a hard reset which seemed to help a bit (at least long enough to grab the HA/AAA passwords I missed the first time around). As I mentioned before, I'm currently running the stock Sprint 3.35 ROM and, after manually modifying the "M.IP Customer Profile 1" settings, I have everything working (GPS, Internet/Data, WiFi, calls, text, bluetooth, etc.). Hopefully things will work out for you and you're phone will stabilize at some point. If I can help in any way, let me know. -kiawud P.S.: You might want to try and get the Qwest_extrom.nbh file and see if it helps with the rebooting problem (perhaps there is something in the extrom that is disrupting the Qwest 2.13 ROM). |
|
||||
Re: Qwest + Mogul = No Update Ever?
I was planning to upgrade my phone this weekend but hit a bit of a snag when obtaining my MSL number.
I first tried to use the program called GETspc.exe (MSL Extractor) which did return a number but that number was invalid for unlocking the EPST settings. I assume this is probably a number for a Sprint phone and not a Qwest phone. I wonder if anyone has written an MSL extractor for Qwest phones...? I then called Qwest as listed in the above post: - MSL/sublock code for existing Qwest 2.13 phone (call Qwest) When on the phone with Qwest I explained my delima that I am angered at their lack of firmware releases and lack of solutions to fix the BlueTooth problems etc. and that I have found a possible solution to this problem that requires knowing my MSL code. At first I was told that Qwest will not give out that information and that I am out of luck. After some persistance the agent I spoke with talked with someone higher up the food chan and I was finally given my MSL number. Before giving me the MSL I was told that if I broke my phone by trying this upgrade that my warrenty would be void. During this conversation, I was also told something that might interest other Qwest customers using this phone. She told me that Qwest is aware of the Sprint ROM and is in the process of converting it to be used on Qwest ![]() I have dealt with these problems for so long that another month is really no big deal to me. I think I may wait a month to see if Qwest really delivers and not take a chance on voiding my Warrenty. I guess if a month goes by and I see nothing from Qwest then I will take the plunge at that time. |
|
||||
Re: Qwest + Mogul = No Update Ever?
From what I understand, the 'Special_4350.nbh' file is installed as part of the Sprint 3.35 ROM Upgrade. The whole upgrade updates the radio to 3.35 as well as the operating ROM/firmware.
Once installed, the 3.35 radio rom it is very difficult to remove (ie: if you wish to downgrade back to a 1.x radio rom, you have to use the microSD/TITAIMG.nbh method). So, if you want to avoid installing it, don't use the Sprint 3.35 ROM (grab a titan_radio_3.35.nbh instead and use a custom ROM such as DCD's Qwest 3.01 ROM ... although I'm not sure if the titan_radio_3.35.nbh is any less resistant to downgrading). Additionally, I understand that the Sprint 3.35 ROM is a complete upgrade and, normally, also touches the bootloader (perhaps that's another aspect of the 'Special_4350.nbh' file). However, I read that Olipro 2.40 is able to resist the bootloader changes that the Sprint 3.35 ROM attempts to make. Personally, I have used the Sprint 3.35 ROM to upgrade several times on three separate phones (all running Olipro 2.40 first) without any significant issues (the worst being a phone stuck in bootloader mode ... just had to use the 'exit_bootloader.exe' program or 'mtty.exe' to reset the phone). However, everyone's experience will vary and you should go with what you are comfortable with (there's a good chance I just had a case of extreme dumb luck). HTH, -kiawud |
![]() |
|
|
|