|
||||
Re: Qwest + Mogul = No Update Ever?
robeerski
Check out this link http://forum.xda-developers.com/showthread.php?t=378007 Pretty good instructions here. I am trying to locate all the software to get me going. |
|
||||
Re: Qwest + Mogul = No Update Ever?
Another Qwest/Mogul user here...
Just wanted to share my experience with upgrading... Started with the standard Qwest 2.13 ROM (didn't write down all the details ... didn't think I'd need them). 1) Used ##778# to grab EPST info (did not have the MSL, so I didn't get my passwords ) 2) Unlocked bootloader with Olipro 2.4 3) Installed the Sprint 3.35 ROM 4) Stupidly allowed it to complete its customizations (I think it resulted in the wiping of my extrom info ... which included the iota/internet/data info that I needed and didn't record) 5) Installed DCD Qwest_3.01 ROM After #5, everything but the internet worked great (Google maps worked ... using WiFi ... sent/received phone calls & text/SMS). Thinking I had nothing to lose, I went back to step #3 and reinstalled the Sprint_3.35 ROM (must say that I really do prefer the application set that Sprint offers over Qwest). With just the Sprint ROM installed, everything but the internet worked perfectly (again, GPS worked with WiFi ... send/receive calls and SMS worked). I even called Qwest and asked if they could reset my account to see if that would help. They claimed they did, but I was still fiddling with my settings, so I may have negated whatever they did. I then tried to downgrade back to Qwest 2.13 and have observed the following: Relocking Bootloader w/ Titan_Relocker: - BootLoader/SPL: Titan 1.06 (Titan_Relocker) - Radio: 3.35 - ROM: Sprint 3.35 - Result: Mogul would 'reboot' a few seconds after loading up - Trying to downgrade via an old Sprint ROM (ie: 2.17) results in an RUU error (Invalid Vendor ID). Keeping the Unlocked BootLoader: - BootLoader/SPL: Olipro 2.40 - Radio: 3.35 - ROM: Qwest 2.13 (used the 'signed' ROM provided by Bunvilla (sp?) ) - Result: Mogul would freeze at the black 'HTC' logo screen Also tried downgrading the radio ROM while still using the Olipro 2.40 bootloader: - Result: Received an RUU error '328' (Invalid Command) (Same error when trying to downgrade to previous Sprint ROMs- ie: 2.17) So, as it stands, I currently have a Qwest/Mogul phone running the following: - BootLoader/SPL: Olipro 2.40 - Radio: 3.35 (from Sprint 3.35 ROM ... also known as Special_4350.nbh) - ROM: Sprint 3.35 I can send/receive calls and text and even do some GPS tracking via WiFi ... but I have NO internet/data service. I need to either: A) Get internet/data working under either the Sprint 3.35 or DCD_Qwest_3.01 ROM, or B) Downgrade the phone back to Qwest 2.13 (and either 1.39/1.40/1.47 radio ROM) with a locked bootloader (Titan 1.06 ?) If anyone has any thoughts, feel free to post/email them (I'm willing to try just about anything). -kiawud@gmail.com P.S.: On a few occasions, I've gotten the phone stuck at the bootloader (3 colored stripes) and found out you can use 'mtty.exe' to unfreeze the phone. |
|
||||
Re: Qwest + Mogul = No Update Ever?
Update:
===== I got everything working. I was able to downgrade the phone back to Qwest 2.13 w/ 1.47 radio (had to use the microSD method to downgrade the radio). Once there, the internet started working. Grabbed the missing EPST info (ie: my HA Shared Secret and AA Shared Secret for my M.IP profile). And then was able to upgrade completely to DCD Qwest 3.0.1 via: 1) Grab EPST info (all of it ... needed to use MSL) 2) Installed Olipro 2.40 3) Installed Sprint 3.35 ROM (DID NOT ALLOW CUSTOMIZATIONS!!!!!) 4) Installed DCD Qwest 3.0.1 Everything is working now (GPS, Internet/Data, Send/Receive phone calls and text, WiFi, Bluetooth, etc.) If this ordeal helps anyone else, then it was worth it -kiawud |
|
||||
Re: Qwest + Mogul = No Update Ever?
Latest Summary:
I am currently running the Sprint 3.35 ROM on a Qwest issued Mogul and, so far, everything is working (Internet/Data, GPS, Phone, Text/SMS, Email, Bluetooth, etc.). For those interested, here's how I did it: Upgrading from Qwest 2.13 --> Sprint 3.35: =========================== Info/files needed: -------------------- - MSL/sublock code for existing Qwest 2.13 phone (call Qwest) - GetSPC.exe ('MSL Generator.zip') - Olipro 2.40 bootloader ('Hard-SPL-MFG.exe') - Sprint 3.35 ROM ('RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04 _4350H_SPCS_AM_Ship.exe') - DCD's Qwest 3.01 (optional - 'DCD_3.0.1_Qwest.exe') Most of these files can be found in this thread: http://forum.ppcgeeks.com/showthread.php?t=17667 Method: --------- - Step 1) Call Qwest and get the MSL (aka 'sublock code') for the EPST. - Step 2) Dial "##778#", select 'Edit' and use the 6-digit MSL code. - Step 3) Copy ALL the info from all pages/tabs of the EPST* - Step 4) Install Olipro 2.40 (via 'Hard-SPL.exe') - Step 5) Install Sprint 3.35 ROM (via the Sprint 3.35 ROM from their site) - Step 6) Allow phone to customize under Sprint** - Step 7) Use "GetSPC.exe" to obtain new MSL code - Step 8 ) Dial "##778#" and new MSL code to manually edit the EPST settings (pay particular attention to the "M.IP Customer Profile 1" and the HA/AAA passwords) *Not all the EPST info is nec., but it's nice to have it any way. What are really important are: MSID, MDN, and the NAI, HA/AAA Addresses and Passwords from the "M.IP Customer Profile 1" tab ... FYI: The passwords only show up in the 'Edit' mode of EPST. **When/if the phone is customized via the Sprint ROM, it will corrupt some of the EPST settings. Despite this, the phone should still send/receive phone calls and text messages. To enable internet/data (which is what the IOTA would normally do), we have to manually modify the EPST settings in Step 8. Using DCD's Qwest 3.01 ROM: =================== Of course, you can avoid a lot of hardache/anxiety by simply skipping Steps 6 - 8 and installing DCD's Qwest 3.01 ROM immediately after installing Sprint's 3.35 ROM (if you go this route, DO NOT LET THE PHONE CUSTOMIZE AFTER THE SPRINT ROM INSTALLATION). Doing so should result in a fully functional phone (working internet, phone, gps, etc.) that does not require much, if any, EPST modifications. For those curious, DCD's ROM has some interesting features, such as: - It's relatively bare (so it doesn't include a lot of the 'fluff' you find in the corporate releases ... such as 'trial ware') - It's Windows Mobile 6.1 (I believe Sprint's 3.35 ROM is still just 6.0) - It has a different dialer which seems to have bigger buttons and simpler interface - It can group text/email messages by thread giving texting a sort of 'IM' feel by showing all the related messages at once In any case, I hope this helps any fellow Qwesters out there who are tired of waiting for Qwest to catch up to Sprint. I'll continue to play around with the Sprint installation and post if I have any problems or issues, but so far, I must say it's great having a working Bluetooth and GPS capability Feel free to email/pm me if there is anything I can do to help -kiawud@gmail.com Last edited by kiawud; 04-08-2008 at 01:24 AM. |
|
||||
Re: Qwest + Mogul = No Update Ever?
That sounds great. I think I amy try and tackle upgrading mine this weekend when I have some time incase I mess it up. Thank you for all the information on your experience.
|
|
||||
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?
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 |
|
||||
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). |
|
|
|