Finally a Java Fix for Cingular-branded E62s
Were you super-pumped when Cingular launched their Nokia E62? Yeah, it’s a bit more limited than it’s older brother the E61, but to some people (myself included) WiFi means nothing on a cellphone. And it’s cheap if you do a contract.
However, as many people discovered, there was one gleaming drawback to the Cingular E62: the java. Cingular’s firmware crippled the hell out of the java restrictions on the E62, making it so that any app that’s not Cingular-signed Java has to repeatedly request permission to access the internet. This basically cripples apps such as Opera MIni and Google Maps Mobile.
However, As posted on HoFo and Cingular’s User Forums, there’s a way around it. It’s free, legal, and easy as pie. Click on to read the full text. Basically you’re fooling Nokia’s Software Updater (like many have done to get a N73 Music Edition or N80 Internet Edition) into thinking you have a Rogers (Canadian GSM Operator) branded E62, and re-installing their firmware. Apparently Rogers puts a bit more freedom into the hands of their users than Cingular does. Shame on you, Cingular! Did you think we wouldn’t find out!?
*Update* The Unbranded firmware product code has been discovered, click on for the walkthrough and the code. I just did it on my E62 which I had previously flashed to Rogers firmware and it is now unbranded.
**Update** It would appear as though Nokia has updated NSU and removed the ability to re-apply a phone’s firmware.
***Update*** It appears as though, for both the Cingular branded E62 and N75, you must have the phone unlocked before you can follow the steps below. Simply call AT&T’s customer service, tell them you’re going to London for business and will be using a local SIM card. They should be able to provide you an unlock code within 24-48 hours.
*FINAL Update* - Both the E62 and the N75 (with AT&T’s ‘Tab Top’) can no longer be unbranded using this walkthrough. Unfortunately, you’ll need to get a different handset if you want an unbranded one. I’d recommend the E61 or the N76.
**Begin Direct Quote**
Hello,
I’m one of the guys who bought Nokia E62 the day after this phone was
released and available at Cingular stores. And I’m the one of those who
is suffering with the Java applet issue caused by the crippled Cingular
firmware. Sure most of you who have Cingular E62 already discovered
that issue, and those who didn’t, can read about it in the following
threads:
http://forums.cingular.com/cng/boar…essage.id=40201
http://forums.cingular.com/cng/boar…essage.id=39935
This issue was also discussed in many other forums. Some of us even
contacted Cingular asking for explanation/help, but nothing promising
came out of it.
More than 3 months passed since Nokia E62 owners discovered that issue
but Cingular did nothing. Frankly saying I do not believe that Cingular
is interested in the Java applets problem investigation and making its
customers happy. Most likely Nokia E62 is not a best Cingular seller,
so they are not going to invest in fixing that issue.
I spent about 3 months trying to fix that issue on my own, but any
attempts to create a “missing” certificate and apply to the
applications that “affected” by Cingular’s firmware were unsuccessful.
So, I did choose another way and yesterday I was able to fix this
issue. The solution was simple, but took me a long time to find the
necessary code. (Thanks to one of Canadian E62 owners who provided me
the data I needed!)
The fix is easy and it takes about 30 min. to implement. The main idea
is that instead using Cingular “crippled” firmware we can use the
firmware from another operator which is not “crippled” and allows Java
applets work normally. I did try several firmware versions and chose
the firmware from a Canadian operator called “Rogers”. Again… what
I’m writing here is not a theory. I DID try it and it works. I’m a
happy E62 user now. 
So, what do you need to get rid of Cingular’s firmware and to flash
your phone to a Rogers firmware? Not much to be honest. I got the
flashing idea from the URL bellow, so I’m not creating anything new,
except that I found, tested and verified Rogers firmware in our
Cingular’ Nokia E62.
All the credits are to the author who posted the following article:
http://www.gsmhosting.com/vbb/showthread.php?t=344689
Bellow you will find the steps you need:
1) Download and install Nokia Software Updater (NSU) from:
http://www.nokiausa.com/support/sof…update_via_pc_1
IMPORTANT NOTE: Nokia Software Updater is very sensitive to software
firewalls. During the many tests I have done, I found that I must
completely disable software firewall, as granting full network access
to (NSU_UI_CLIENT.EXE and NSL_HOST_PROCESS.EXE) was not enough to make
NSU work. So, the bottom line is if you do not want an additional
headache and want to receive quick results, then just temporarily
disable software firewall before you run NSU in step 6).
2) Download and install Nemesis Service Suite (NSS) software in order to change the phone’s product code from here:
http://www.b-phreaks.co.uk/files/NSS/NSS10387.zip
3) Now we are ready to change Cingular’s Product Code to Rogers Product
Code which will allow us to upload a Rogers’s firmware in step 6).
3.1 Connect your phone to USB and choose “PC Suite” mode (same as if you always do when sync your phone): Open NSS and click on “Scan for new device” button on the right-upper part of the window: Click on the icon «Phone info»; Click on “Scan” and wait until you get “…Done” in the status string at the bottom of NSS window;
3.5 Now, in a “Product Data Edit” window check “Enable” next to
“Product Code” string and type the next code: 0538175 (For Rogers branded firmware. Use 0524513 for Unbranded firmware.) Then press
“Write” button and wait until you get “…Done” in the status string at
the bottom of the NSS window;
3.6 Press “Scan” button again (same as you did in 3.4) just to be sure you still can get “…Done” at the bottom of NSS window;
3.7 Right click on a small icon (located above “Device Info” button) and choose “close device”;
3.8 Now you can completely close NSS. We do not need it anymore.
3.9 Disconnect USB cable.
4) Backup your phone information at that step. How and what backup
depends on your needs. Just understand at that point that we need to do
a hardware reset of the phone at next step, so it will erase all your
Phone Memory data.
5) At this step we will reset the phone to the factory configuration:
5.1 On your phone press several times Red button, so to be sure you are in an “Idle Screen”;
5.2 Press * #7370#
At that point you will be asked if you want “Restore all original phone
settings”. Answer Yes and confirm the code (which is 12345 by default.
Be careful and verify that you are typing a numbers, but not symbols).
When you provided the right code, your phone will be restarted and you
will be asked if to you want a read a tutorial. Answer NO.
6) Now we are ready to update phone to Rogers or Unbranded firmware.
6.1 Connect your phone to USB and choose “PC Suite” mode;
6.2 Connect your phone to a charger;
6.3 Run Nokia Software Updater (NSU);
6.4 Follow the prompts. At the point when NSU says that you already
have the latest firmware and if you want to download it again, confirm
it with checkmark and let NSU do its work;
6.5 After about 15 minutes, NSU will finish its work, reboot the phone
and tell you that your phone software is updated and you are ready to
go.
6.6 Close NSU window. Disconnect your phone from USB.
6.7 You must have Rogers or Unbranded firmware in your phone now.
7) This step is optional, but I would still recommend that after
updating your phone with NSU, you reset your phone to the factory
configuration one more time. For that, repeat step 5).
I hope everything I wrote was clear enough and you have a phone without
Java applet issue now. You can install the Java applets your like (the
first one I immediately tried was Google Maps for Mobile) and they must
run OK.
Shame on you Cingular! We are US customers, but because you do not want
to fix the problem in your firmware we are forced to use firmware from
Canadian operator. What a “nice” way to promote your service, Cingular!
It’s so sad that we have to come up with workarounds. And I can’t believe that Nokia has no clue of the matter. They would do better giving their contract to T-Mobile.
This worked great! Thanks much for your research
Cingular has the money to do what they want with the firmware. I’m wonder why Nokia hasn’t given any extensive contracts to ANY U.S. carriers but cingular
how would i put the cingular firmware back on my e62
Nokia E62 (Cingular US Branded)
RM-88
Product code: 0530924
Use that code to restore back to cingular defaults.
Now if only I can figure out how to change the startup music…
Thank you for this! Apart from the rebooting problem, the java issues were VERY annoying. I now have a Generic Nokia firmware on my E62 and it’s working great. Synced w/out issue (I even restored, but got nervous… I *#7370# the unit, and just synced. Has all the info that I need.)
Thank you!!!!
Awesome. This has been my biggest complaint about the E62, and my unbranded one now runs widsets perfectly.
The NSU just tells me that no software updates are available for my phone. How do I force the update?
I’m in the same boat as Ajakk.
I need to go back to the Cingular firmware so I can replace the phone under the warranty.
Thanks!
@Tom - Be sure that you have successfully changed your product code with NSS. There is no way to “force” NSU to give you a new firmware. If it checks your phone and says there’s nothing new, then that’s that. But like I said, make sure you successfully changed the product code.
@ Austin - I don’t think you need to rebrand it to send it to Cingular’s warranty department. They will merely check the IMEI, which obviously will check in with their system. However, should you still wish to go back to Cingular branded, I believe the product code is 0530924
I followed the instructions for changing the product code to the letter. Is there any way to verify it is correct?
Tom, repeat step 3.4, only instead of clicking “enable”, there should be a button near there labeled “read” or “load” or something that would imply the software reading the current product code off the device. I don’t have it open in front of me to check.
Also, 2.0618.06.17 is the newest unbranded firmware. If your Cingular firmware is a higher number than that, you won’t be able to perform the update.
Ricky,
That is the firmware version I have. The product ID seems to be changed correctly. The only thing I can think of is that I seem to have a new version of the NSU. I have version 1.2.30. What version did you use? Perhaps Nokia killed the ability to reinstall the firmware this way??
Have the 2.0618.06.17, 10-08-06 firmware.
Just tried the process again, both set to the Rogers and Unbranded Product Code.
Never was presented an option to download firmware again by confirming with a checkmark.
Also noticed that a thread discussing this subject on Cingular’s forums (with a few recent posts indicating failure), was deleted today. I had just read it last night, bookmarked it, and today its gone.
Sheesh, appears Cingular and Nokia have slipped on the jackboots for a little march.
Welcome to the new draconian at&t.
Just a matter of time before someone finds a link to the old updater or posts it somewhere, and I’m assuming at that point we can just use the above method again.
Very frustrating in the mean time.
If you try to use an older Nokia Software Updater it tells you there is a newer version and that you must update to it … so you can’t use older versions of NSU.
I tried to use my older 1.2.20 and it won’t run other than to update.
I’m sure someone out there is working on this even as we sit here lamenting our inability to unbrand this sucker.
Love the phone so far, but if I can’t unbrand it to turn JAVA loose, I’m thinking it goes back.
So far I’ve located version 1.0.88. It does not require you to update the current version, however, it does not allow you re-load either.
Will continue the search…
yeah, I’ve been looking on and off all day. I knew about this issue with the cingular firmware but also knew it could be unbranded … looks like I bought my e62 a day late.
There’s no other way to get the firmware onto these things reliably and safely, is there?
I’m sorry to those of you who aren’t able to unbrand your device. Even Darla Mack was trying on hers yesterday and was unable to, with the same problems as you.
It could happen that in the next (whenever that is) NSU release, Nokia re-enables the ability to re-install a firmware (which is the function that this process takes advantage of) but who knows for sure?
As for now, I would suggest contacting Evan @ iUnlock.com. It costs a bit, but I have had him update and unbrand several 6230s, as well as misc. other phones, and he’s got a VERY quick turnaround. Yes, that’s a sucky suggestion, but at least it’s something, for now.
I’ll continue to monitor things and if I hear of an update, I’ll surely post it on this thread. Thanks for reading my site and participating, guys.
I found an earlier installer version 1.0.86, but this version did not even recognize the E62. I tried to see if a hack way of combining the two installers made a difference. I used the newer installer and the older binaries…was able to recognize the phone but still no option to re-apply the firmware.
Since we have updated the product code to Rogers/Unbranded, the next firmware release should free java. But how long will that be…
You’d think Nokia and Cingular would get a clue and free this stuff up. If Cingular/ATT came out with an ungimped firmware and a statement “hey, guys, we screwed up, please forgive us,” not only would I not unbrand my phone (I’ve always *at least* taken the operator logo off), I’d actually become a cingular/ATT fanboi. I’m sure others would follow suit.
Hell, they’re already getting me for the unlimited PDA data access plan on top of my regular cell phone plan, you’d think they least they could do is let me use the device I *bought* from them the way I see fit.
I can’t even get the operator logo off, let alone install a working IM client, etc.
Hopefully we won’t have to wait for long.
Kris, the problem with that is that Cingular doesn’t see the java limitations as a “problem.” It’s something they requested to be done. Cingular has a java certification program for developers that gives their apps full reign. But if you don’t get your java app “Cingular Signed” then it doesn’t get to have full access.
The only thing we can hope for at this stage is an updated unbranded firmware, which honestly, I think is about due, so it might only be a month or so.
Gotta love companies that feel the need to protect us from ourselves. I understand the rationale, but it should be optional, a setting instead of an edict.
Found this on another site, thought I’d cross post it here.
***
[...] On a further note, complaining to Cingular’s regular Customer Care isn’t going to get you anywhere.
If you guys want your complaints heard, you have to contact Cingular’s Office of the President. They don’t make it easy to find their number, or even to know they exist, so when a customer has gone through the hoops to reach them, they tend to take their complaints a bit more seriously, because you’re obviously pissed enough to have tracked them down.
Cingular’s Corporate Office phone number is 404-236-6000. If you ask the operator to transfer you to the Office of the President, they will, and then you can register your complaint. They’ll take your complaint and have a case worker get back to you within 24-48 hours (which they
do).
When you call that number above and ask to be transferred, they’ll give you the Office of the President designated for West Coast customers.
People on the East Coast who want to contact the Office of the President can call 877-850-0761. That is a direct line to the East Coast Office of the President.
All you E62 owners, *please* call and complain that you are furious at being sold a crippled phone, and demand that they remove their limitations via a firmware update. And don’t let them try to pawn off responsibility by claiming that a third party app is concerned. Remind them that where there is a difference of opinion on where responsibility lies, it’s the *consumer* that has the final say.
***
I haven’t verified those phone numbers (yet), but it’s been cross-posted to a couple of different forums, including Cingular’s own (where they’ll probably delete it, if recent activity is any guideline).
Whether the various Presidents of Cingular listen to customer complaints or not, it’ll give us something to do until we get new firmware.
too bad lot of us missed the un-brand procedure for E62, b’coz of new NSU [ i'm sailing in the same boat..:-( ]
Is there a on-line Complaint/suggesstion forum at Cingular that we praise
about their Crippled firmware…
I have an Cingular/Nokia e62 that locks up all the time. Only way to fix it is to pop the battery out and put it back in. Very annoying. Anyone else have this problem or any ideas for a fix?
Thanks…
Freeze Up:
Yes, I experience this almost on a daily basis. I’ve had this phone less than a month and I’m feeling the urge to introduce my 8lbs sledge to it…
can someone upload the correct nsu to rapidshare?
Bob,
It doesn’t matter if you have the “correct” version of NSU, when you start it up, it will automatically update itself to the newest version, thereby disabling the ability to reapply firmware, which is the loophole that we had used before.
So basically, untill there’s a NEW firmware out (therefore you’re updating and not reapplying) there’s no way to unbrand a Cingular branded E62.
Why doesn’t anyone just replace the binary code on the old NSU with the new NSU’s binary code and just start the update that way? Seriously would take all of 10 minutes to stratch your butt, wipe, and get it done…
Also it says the version on my phone is:
Vp 2.0618.06.17 10-08-06 RM-88…
Cheers
Stephen
Another way you can do it is if you change the version of the firmware to an older version on your phone. Then NSU will think that it needs to update an it will update your phone. Is this possible?
The situation appears to be getting even worse as the newest update to the NSU, version 1.3.60 won’t even recognize my E62.
does anyone have an update as of today 5/11. Is there a new firmware in the works? is there any way around the current impass?
Well well well… E62…. We could have done so much together… But the jealous lover that cingular is turned it into a confusing mess… I tried so hard to make it work, for so long, but in the end she just had to tear us apart..to bad i will be running you over with my truck, back and forth,back and forth, i must say it is satisfying, almost exhilirating to reach a decision, a point where i can just move on, get on with my life,start fresh, re-energised and in love once again, with my old flame- tmobile….
Sep 11th, 2008 at 11:39 am
[...] you can (at your own risk) use the free NSS software to change your product code, as guided in this handy walkthrough. When you get to setp 3.5, you’ll use the 0558752 product code, instead of the one [...]