Flashed a900 with sprint firmware - - help

I was desperate in having my Aliant a900 flashed to the 900m. There were no current bell zh17 firmware files kicking around, so I obtained one from Sprint. The operation of the phone works beautifully and I can live with the Sprint branding, however, I have one small problem. I am unable to access the internet because the phone wants to connect to sprint's vision service which denies me of course. I had backed up my settings, but didn't realize the more advanced settings wouldn't be backed up with the softare that I used. I was able to load the settings I did have backed up, which fixed text messaging, but the browser app and multimedia apps try to connect to vision still.

I have come to believe it is the actual browser app that has been taylored to sprint. Also the MMG/MCD/MMSC and picture mail settings in ##3282 (##3282#) are stuck on sprint urls. Also my NAM password/secret are not entered. I dont know how to reset these. If anyone could help me with the jar/jad url embedded into the phone (which would have to be changed using QPST) that is tailored to downloading and setting the browser, I would really appreciate it. If anyone can help me by giving me the multimedia url's I would be very thankful.

Once I can obtain these settings, I may have restored my service back to normal. Again, I can live with the Sprint branding.

---

› See More: Flashed a900 with sprint firmware - - help

I have a similar problem. I switched from Sprint to Cricket, everything works great except the web. It is locked in to Sprint. How to do change those settings????
Thanks

Well i've been talking to senior techs and they've done everything they could; or so they say.

One guy said that flashing the phone may have currupted the mn-AAA hash or something. Looking in QXDM I didn't see any mn-aaa hash, only A-key hash, NAM hash, ESN Hash, and a few others. One thing I noticed was my ESN hash was set to 0x0fffffff, which is a different hash that I get when using an ESN Calculator. Tried writing the hash to the phone, QXDM said it succesfully written the hash, but when viewing it again, I got the same results.

I think it really has to do with the MN-AAA and the MN-HA secrets. Mine were blank and "secret" respectivly.

I need to find someone on either the Bell network or the Aliant network to give me these secrets.

I'd help you out, but I really don't know enough about the AAA settings in the handsets to give you much of any direction. I will continue to read this thread though and chime in if there's something that I can find / know.

Well I spent about an hour with Sprint senior tech support which seem to be VERY helpful compared to Aliant. Sprint could have just said it wasn't their problem and hang up on me, but the guy didn't. Cudo's to him. I should tip him. Anyways, he verified to me that the mn-aaa and mn-ha passwords are network specific AND can be entered manually using the keypad of the phone. Aliant told me otherwise (dumasses), he also said that the mn-aaa and the mn-ha addresses THEY use are full range ip addresses. Here, it's just 1235 and 2 respectively...now, I dont know if that's network specific either, but it does have me thinking.

I've done all that I can. I've made sure that I had a correct A-key which I've obtained from a peice of software that calculates it based on the ESN of the phone, and i've made sure that hashes are correct. Using other software to read the phone tell me that the hash for my ESN is correct. seems like QXDM has a little bug in it.

I have been in contact with another person in the United States who does this sort of stuff as a hobby I suppose, and he has got other phones working with bad ESN's just by replacing contents of the NVM folder in a working phone into the non-working phone. That got me thinking as well.

So, if anyone has access to their phones directory, it would be appreciated if I could obtain those contents of the NVM directory. Since sprints browsers are tailored to their network, I would also need those 1.txt/jad/jar and 2.txt/jad/jar files as well to restore my phone back to the way it was.

If no one knows how to do this you may feel free to pm me and I will walk you through the steps using the software I will provide.

I have been in communication with a level 3 cellular network technition (someone the general public will never get to) and we have figured out the problem. The problem at least with data, lies in the way Sprint and Bell use passwords for authentication. Sprint allows custom passwords to be made on behalf of the person with the cell phone. This password has a maximum entry data field of 16 characters. Bell, on the other hand, will NOT let you choose your own password and is a 32 character md5 hash. As you can clearly see, 32 characters will not fit into a field designed for only 16. It's a shame. There is a work around confirmed and that would be to have my password customized, but I do believe Bell's policy is pretty clear about this. The only other option, without getting my phone reflashed to bell firmware, would be to try and hex edit the md5 hash into the file that stores the password. I've tried this already with no luck, it still will only accept 16 characters. There must be a way to increase this size.