I just picked up a new Nokia 6301 from T-Mobile and immediately went to install my opera mini and google maps that I had been using on my Dash and RIZR. They both installed but nether would run due to permission error. i noticed that some others had posted similar issues with newer model Nokias on T-mobile. Most had some way to work around it. Is there a patch for this model or is this phone to new to know yet? Thanks.

BTW I am currently using the WiFi service that T-Mobile sells, so I don't thinkflashing it to another carrier software will work, as I assume that it would break the WiFi calling feature with Tmobile.

From what I understand, the only way around this is for Nokia or T-mobile to release a newer version of the firmware that doesn't have the same lockdowns. As a datapoint, there was at least a six month lag between 6263 release and a T-mobile branded firmware update available through Nokia that enabled 3rd party apps (and removed some T-mobile functionality).

so T-Mobile actually let loose on some of the restrictions on the 6263 or was it Nokia that just released the new firmware for the T-mobile phone and fixed it? If T-Mobile actually is playing ball then that may be good news for this and future Nokias from them.

Does anyone know of an app that will sign java apps with the appropriate permissions for the phone to just work normally? Doesn't this seem like an easier method, instead of flashing a device with firmware that will ruin the warranty.

A new firmware was made available through official Nokia channels with T-mobile branding on it for the 6263. Whether it was intentional or not isn't totally clear. It's possible that Nokia made a mistake. It's also possible that T-mobile heard user complaints and will allow for "power users" to update their firmware while leaving their phones locked down by default.

And just "signing" the app isn't enough. The way T-mobile likes to release their phones is with a version of a firmware crippling everything except apps signed with T-mobile's certificate. If you're a developer for T-mobile or working directly with T-mobile, you might be able to get that T-mobile signature onto your apps. If you have no direct affiliate with T-mobile, you'll never get a T-mobile signed app.

I have already written them regarding how unhappy I was due to this limitation on the phone. Their response was that they didn't think that the user experience for these apps were good enough and that I could enjoy them much better if I would get one of their smartphones. Let me decide if the user experience is good enough or not.

I wish I had visited before buying my 6301, the lack of 3rd party apps makes the phone almost useless to me. The Email app is locked to providers that I don't use, except for Gmail - I think I have to enable POP3 access to make that work. It's useless for my business email account which is why I bought the thing. I sent a very unpleasant email to my sales rep. We'll see what he says...

Phone is nice but too many limitations which I pretty much appreciate. Phone is very simple and easy to use, great "day off from work" kind of phone.

yeah i just got the phone and i was so excited about some of the software i was able to find till i got it and tried to install it....... very upset now..... why lock stuff like this out... i mean i do understand the need for blocking it but if you know how to do the stuff you should be allowed to install stuff on the phone you spent money on........

thanks for the info ^_^

Ravidavi has a script for S40 v2/v3 phones that allows a work around for T-Mobile's 3rd party software lockdown. Do a search using s40 v2/v3 and one of the top items returned will bring you to that thread.

if you have the newest firmware for rm-323 and rm-337 just flash the phone with the image from rm-337 and your phone will be unbrand. remember to backup your setting in the "settings" or you can't use your UMA after unbranding your phone. that will solve the problem with limitations ^^. and I am quite happy with what I got XD. BTW rm-337 is 6300i.

and this trick also works and any look alike phones like 6263 with 6267, 6085 with 6086. but don't mix around with mcusw and ppm or you can brick your phone in a awfully nice way like I did.

also don't update the phone though NSS since I don't know if that changed the product code to a 6300i which might cause a problem

FWIW, I have not heard of a single case of someone successfully flashing their 6263 with a 6267 firmware. Everyone that I know of that tried it, ended up bricking their phone. If you know of someone who's done it or can even point us to post of someone reporting success, I'd appreciate it and I'm sure others would too.

well like I say only the image part of it not the mcusw or the ppm. A firmware have 3 parts mcusw, ppm, and image. if you leave the mcusw and ppm unchange and only flashing with another image you can unbrand the phone. since most of the restrictions are in the user settings. so flashing image from other phone will not cause a problem.
you have to use a flashing program to do this job though
and what this does it only unbranding you can't change the language since its in the ppm.

I have tried flashing with ppm from 6267 to a 6263 after it turned on I would get a white screen with something blue I think its the background on the bottom corner of the screen and it will not respond at all. but you can always flash it back as long as the flashing did not corrupt or damage the written data, or you have to resolve though Fbus. which I don't have XD

btw when you normally flash your phone they will choose all 3 file for you depending on you product code you just need to change the image that it is going to flash. but as for unbranding I think 6263 do have one is unbrand so there is not such need to get an image from another phone unlike 6301 which only have fido and t-mobile right now.

and I am using a 6301b that is unbranded with image of 6300i. but having the image does not mean my phone became 6300i.

I'm curious, did you just change your product code on your 6301b to the generic code of a 6300i and still maintained T-Mobile UMA support?