How to update Q 9c to WM 6.1 w/o warranty

Is it possible for my Q 9c to get the WM 6.1 update without warranty. I tried using the motorolla update tool but I can't get it past step 2. It appears my Q 9c is out of the warranty period it and it stops the update from preceding. I'm I out of luck or is their still hope?

if it's sprint of verizon you could try giving it a date within the past year, or search for a monster flash file and use RSD lite

Click to expand...

It's a Sprint phone. Give date? If your talking about the motorolla update tool it doesn't let you input any of those options. It seems to check only the imen (serial) number for manufacturer's warranty status.

You don't have to put in a date to dl the file. It checks the serial number of the phone to see whether its covered under warranty which is bs. If your phone is passed the warranty period (1 yr) it wont let you continue with the update. I found a wm 6.1 rom for q 9c but its says its for verizon q9c. is it compatible with sprint q 9c phone.

the update flashed ok but no data access. so i took it to sprint and they said i flashed it wrong. the program that allows sprint to program the phone was deleted. i used rsd lite 4.2 to flash. will flashing again fix the problem?

the update flashed ok but no data access. so i took it to sprint and they said i flashed it wrong. the program that allows sprint to program the phone was deleted. i used rsd lite 4.2 to flash. will flashing again fix the problem?

Click to expand...

Sprint has some really propiatary messaging settings and they have been posted somewhere, I think here, but I can't find them. I'd bet the farm that I've even used them for friends too. Can someone please point Kahale to them, if y'all know. I'll keep looking too . . . might have them in my notes. A few registry edits is all it takes. If anyone on Sprint here could kindly post all the relative registry entries, THAT would be the BEES KNEES !!!! TIA to any and all. -Q

Sprint has some really propiatary messaging settings and they have been posted somewhere, I think here, but I can't find them. I'd bet the farm that I've even used them for friends too. Can someone please point Kahale to them, if y'all know. I'll keep looking too . . . might have them in my notes. A few registry edits is all it takes. If anyone on Sprint here could kindly post all the relative registry entries, THAT would be the BEES KNEES !!!! TIA to any and all. -Q

Click to expand...

thanks man i appreciate it. hopefully i can get my phone running normally again. if all it takes is a few registry entries that would be great.

the update flashed ok but no data access. so i took it to sprint and they said i flashed it wrong. the program that allows sprint to program the phone was deleted. i used rsd lite 4.2 to flash. will flashing again fix the problem?

Click to expand...

You really shouldn't dive right into things like flashing without doing some research first.

You should always back up your service programming before you flash so that it can restore all your carrier specific settings after flashing, unless you are only flashing an upgrade file, which will preserve those during the flash.

In the specific case of Sprint, which uses a unique 6 digit Service Programming Code for every handset, you need to get that SPC before you can back up the service programming with QPST. They also use a rather complicated data authentication protocol that uses two MIP profiles, each with it's own set of shared secrets for hardware authentication of phone, and protected by the SPC for both OTA and manual programming.

You must back up these critical components before you do anything or you will end up exactly where you are now...and Sprint may not be able to help you recover data services because it seems their techs are not well versed enough in how to reset those authentication components properly.

A friend of mine just went through all of this with a Sprint Q9c which he flashed without backing up first and they couldn't fix it and ended up replacing the phone.

Sorry, that's not what you want to hear but it is unfortunately the truth.

You really shouldn't dive right into things like flashing without doing some research first.

You should always back up your service programming before you flash so that it can restore all your carrier specific settings after flashing, unless you are only flashing an upgrade file, which will preserve those during the flash.

In the specific case of Sprint, which uses a unique 6 digit Service Programming Code for every handset, you need to get that SPC before you can back up the service programming with QPST. They also use a rather complicated data authentication protocol that uses two MIP profiles, each with it's own set of shared secrets for hardware authentication of phone, and protected by the SPC for both OTA and manual programming.

You must back up these critical components before you do anything or you will end up exactly where you are now...and Sprint may not be able to help you recover data services because it seems their techs are not well versed enough in how to reset those authentication components properly.

A friend of mine just went through all of this with a Sprint Q9c which he flashed without backing up first and they couldn't fix it and ended up replacing the phone.

Sorry, that's not what you want to hear but it is unfortunately the truth.

Click to expand...

if i knew i had to backup those things i would've done so. so i guess i just get a replacement from sprint $50. it's silly that sprint can't re-program their own phones or is that they can but don't want the hassle.

I really don't know...I'm not a Sprint customer and it certainly makes no sense to me but that's what happened. I then took his replacement phone and flashed it to VZW and then back to Sprint with all data services working on both carriers, just to prove that the hardware itself was identical, for the VZW GPS work that I've been doing.

If you do it right it's fairly simple but you have to have the SPC first, which can be read in the NVM in seem 2786 record 0001 length E using RadioComm or other programs with direct access to the NVM.