Cyclone wrote:I was just about to ask if changing to ur original code was ok to do, but you beat me to it. 😊 Is there a way to check on the phone to make sure it has been accepted?
btw I used the NSS program to change the number.
I think the NSS program can READ the product code from the phone...
just tick the box next to the product field then click READ. Fingers crossed.
Also, when you update the product code using NSS and click WRITE, there's a status message "write completed successfully" (or something similar) displayed.
Dez
skibeaver wrote:which product code do i use to update O2 UK phone please
sorry for being thick but what is difference between
Euro 1 Smooth Stainless, Euro 1 Pearl Black and ordinary N80 code
The difference is only in how Nokia know which Network and Market (country) the phone was sold to. It can also affect warranty length (I believe UK models have 2 year warranties and some others do not). However, if the code in the internal memory does not match the label behind the battery, then your warrany period is probably ZERO.
If you have the standard silver O2-UK N80 you should probably use the following code:- Euro 1 Smooth Stainless 0529378
BUT I strongly advise you to write down the code on the label hehind the battery and reset the product code to that number after the FW upgrade.
Dez
Can some one help me, im probably being stupid but the gsm magic wont open, what program does it open with?
Wahoo update worked fine.
😊 😊 😊 😊
dez_borders wrote:I think the NSS program can READ the product code from the phone...
just tick the box next to the product field then click READ. Fingers crossed.Also, when you update the product code using NSS and click WRITE, there's a status message "write completed successfully" (or something similar) displayed.
Dez
Thanks for the reply.
Tried to read using NSS and the program took ages to get the info. Infact after 5 minutes it still hadnt found it so I quit :frown:
Surely it cant take minutes to find a product code?
Cyclone wrote:Thanks for the reply.Tried to read using NSS and the program took ages to get the info. Infact after 5 minutes it still hadnt found it so I quit :frown:
Surely it cant take minutes to find a product code?
My apologies, I gave you the wrong info.
After scanning the Device (with TMT enforcer loaded and enabled), click on the FLASH button, and then click SCAN (on the right hand side of the screen).
The result comes back in about 5 seconds, and inlcudes the Product Description and Code currently set on the phone.
Hope it works this time! 😉
is it possible to use this method to upgrade an n80 to the n80 internet edition or is this firmware not yet available?
dez_borders wrote:Hope it works this time! 😉
Yes it does. The same number as my label.
Thank you 😊 😊 😊 :icon14: :icon14:
updated product code ok with NSS
but NSU will not start
Could it be an issue with my router blocking the ports?
So near yet so far
it seems alot of u r doing a FW update with this method, and as mentiond in the post is a v good idea to change ur product code back to default, keep it up guys!
I think my phone runs even better now! 😊 Feels abit faster navigating the phone. I have more phone memory too.
fdxd wrote:I think my phone runs even better now! 😊 Feels abit faster navigating the phone. I have more phone memory too.
another good trick isto go into LOG, and open the logs options then settings, and change log from 10 days to 1 day, speeds up the menu abit, sounds daft but works lol
Marvelous. I followed all the instructions in the thread. Got as far as the Nokia updater saying it was flashing the phone. It reached the end and said it had failed.
I now have an N80 shaped brick on my desk that won't switch on.
EDIT:
What's my next course of action. I've had the phone more than 28 days so I don't think O2 will be bothered with it. Do I take it to my nearest Nokia Service Centre and play dumb? Will there be a way for them to tell I've change the product code?
I tried the phoenix method a few months ago on a 1day old N80 and bricked it. Was a bit wary about giving this a go but tried it anyway and it worked perfectly, on an O2 branded handset, now with a generic nokia firmware and OTA update available 😊 Thanks for the link Biggzy.
Stezos
WPKenny:
Since it's bricked now, there's not much else to loose so personally I'd try a dead phone flash using Phoenix...
* http://www.seventy4.co.uk/weblog/wp-content/dead.pdf
(obviously pick RM-92 and not RM-70 as shown in the PDF)
* http://www.seventy4.co.uk/weblog/2006/11/02/how-to-install-phoenix/
Let us know how you get on if you try this!
EDIT:
WPKenny wrote:
What's my next course of action. I've had the phone more than 28 days so I don't think O2 will be bothered with it.
Actually, the Sale of Goods Act holds O2 to a much longer time period, up to 6 years (depending on the product) and during the first 6 months of purchase the onus is on O2 to prove the product wasn't inherently faulty at the time of sale.
(If they can't turn it on / read anything off it - that could be difficult 😉)
WPKenny wrote:What's my next course of action. I've had the phone more than 28 days so I don't think O2 will be bothered with it. Do I take it to my nearest Nokia Service Centre and play dumb? Will there be a way for them to tell I've change the product code?
You could try doing what I did when I bricked mine. I took it back to carphone and told them that I was doing a video and when I finished and it tried saving to the memory card phone froze, rebooted and didnt come back on. They just did a straight swap from thier stock. Its worth a try.
i hava an N80 on o2 and couldnt be bother to wait.. i used the Euro 1 Smooth Stainless is 0529378
and it worked a treat cheers lads !
oh and i just did the back(content copier) up using nokia pc suite and it worked fine .....
I just followed those instructions and within 15minutes I'd flashed my phone. Well done and thanks!! :icon14:
Neil
Well I've hit another brick wall.
It seemed to install ok but when I follow the instructions the first problem I hit is not being able to find "Firmware update". I can only select SW Update which seems to give me the right options but only if I choose USB connection and not "No Connection" as specified in the guide.
It attempts to flash the phone in USB mode but fails. It doesn't even let me start in No Connection mode. The dialogue box indicates something might need configuring with regards to USb ports or some such.
When I go to enable these ports it asks me about installing drivers. Since the whole thing relies on cracked drivers and very specific things I'm worried that it would break something. Do I go "ok"? or something else?
EDIT:
Ok it seems that the software's quite different to the Dead guide. I'm currently flashing the phone *fingers crossed*.
I started it in USB mode and went to the SW Updater. While it was running it's checks I pressed the power button on the phone as it suggests to do at a specific point in the Dead guide. It's accepting the firmware now and hopefully it will revive the phone! I'll let you know.
EDIT2:
For some reason it lost connection to the phone briefly at 75% 😞 I'm trying to re-create what I did before to try and get the flashing restarted.
EDIT3:
Heh. Well It seems I may just have a crappy cable. I've wiggled and bent and twisted the cable and got it to establish a connection again. *fingers crossed for a second time*
EDIT4: YAY! It's working!
How do i open the gsm-magic file? It's an unknown extention so i have to select which i want to use, not a clue!
WPKenny wrote:
EDIT3:
Heh. Well It seems I may just have a crappy cable. I've wiggled and bent and twisted the cable and got it to establish a connection again. *fingers crossed for a second time*
Now THAT is interesting. I also have a crappy cable and mine's an O2 branded phone too. I borrowed someone elses cable to do the flash cause of how bad my cable seemed to be. (Mine's a dark gray, the one I borrowed was a black one.)
WPKenny wrote:
EDIT4: YAY! It's working!
Does this mean your phone is working again or the flashing is working? 😊
*crosses fingers for phone*
EDIT: If indeed your phone is back alive, it'd be great if you had time to post a seperate thread explaining the dead phone flashing proceedure since the PDF and software don't seem to match, like you said...
It is indeed working again with .41 generic firmware. I've uninstalled phoenix now in order to restore my phone's settings etc but I'll work from memory asap and try to make it as detailed as possible.
Glad to hear your phone is back up and running again and that the dead phone flash worked!
(Don't forget to use NSS to reset your product code to match the label 😊)
I've been left with an odd bug where the phone still thinks the USB cable's connected and stays in PC Suite mode.
Which is fine if I want to plug it back in and use PC Suite but it means it's not giving me the option of selecting Data mode unless I reboot. (EDIT: Just did FOTW update to .42 and it's fixed this problem)
Ok. So how did I rescue my bricked phone?
I followed the phoenix installation guide linked earlier ... http://www.seventy4.co.uk/weblog/2006/11/02/how-to-install-phoenix/
Then I installed the firmware file I downloaded a while ago but didn't have the guts to use. 😊 it was version .41
After it was installed I hooked up my phone. I clicked File...Manage Connections and added a USB connection. Then I clicked File...Open Product and chose the RM-92 (N80) option.
Once this was done I went to the SW Update (can't remember which menu option it was under!) and it went through detecting the phone. After much cable waggling and opening and closing of the SW Update box it finally found the phone. At the top it should say RM-92 and then you select which region your phone is. I chose EURO 1 for my own.
It will then find the firmware files you installed earlier and you just click start.
I daren't breath on it the second time around and it went ok until it came to the end where it said it was rebooting the phone and wanting to run a diagnostic on it. For some reason this timed out but I removed the battery from the phone and tried the power button and it switched back on.
For some reason my PC Suite back up I made of the phone hasn't really put anything back on the phone. I may end up resetting it to factory defaults and installing software from scratch. But it did find TomTom and I'm happy to report it at least boots up. I'll give tomtom a try later.
Only bug I've found so far is that it doesn't always find my Wifi network where it never had this issue before.
I hope that makes sense. It will probably make more sense when you've got the software open in front of you.
another happy N80 user updated his firmware.
I'm on vodafone, had 3.18 i believe. and the damn vodafone woudnt want to update it. worse yet, nokia center told me they'd charge me 40 quid for firmware update (huh?).
just finished updating via NSS and NSU, worked flawlessly.
but after the update i went over to device manager to check if FOTA works... and suprisingly it found a newer version of firmware
V4.0623.0.41 -> V4.0623.0.42
oh well, the newer the better i guess.
thanks for the awesome guide.
Hello, all.
I'm stuck here with v3 firmware. There is no Nokia Center here, in Rio or anywhere else in Brazil.
The phone is mostly OK, but I can't, for instance, do a backup to the card. And it has rebooted twice last week (first time it does it). I want to upgrade, but as many of you, NSU won't find an update.
Mine seems to be Asian (there's some small characteres on the 1,2,3,4 and * buttons), but it is unlocked and unbranded.
It displays a lot of language options, and I use Portuguese (PT). I would like to know if any of you know which is the right code for a black N80 with Portuguese language, so I can change it and try the update again.
😊 Hi all,after updating my firmware to generic from orange, I have just updated it to v4.0623.0.42 using fota with wifi.:icon14:
Superb thread, job done. 😊
whats the difference between updating your phone using the software updater by the nokia, from using the generic firmware?
Finally managed the update using NSS and NSU used Euro 1 stainless code 0529378
Had an issue with NSU starting but think it was Norton preventing it opening
Used a computer at worked and it sailed through effortlessly
Updated to .42 using device manager
TomTom 6 works a treat and everything else seems ok
Many thanks to all here who made it possible