Nokia Firmware
Elida Obrian
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
firmware for the device in question is unsupported by OpenWRT, and can only be used on carriers that sell the device. It would have to be ported to run on openwrt specifically however it is based on an old mip soc.
Nokia firmware really suck!! Im already download the latest firmare but my N70 doesnt perform like i hope..
I doesnt see any difference with oldest version..
Hopefully someone can tell me how to downgrade my firmare =(
Hi, been trying to figure out how to reset my n70 and have been trying the dial/*/3/power combo many times, to no avail. how long should i keep them pressed down before i see a formatting screen? thanks!
A long time ago, (I felt like) I was the coolest kid on the block, with my heavily modified Nokia 3310. A thriving community existed with the purpose of reverse engineering Nokia DCT3 phone firmwares, creating from the simplest mods like changing a few bitmaps to writing a full alternative open source firmware, aka Project MADos. Yes, I was cooking ROMs" before it was cool.
As the years passed, everyone got new phones and these projects got abandoned. While I was writing this article and working on my project, I looked back at the iconic websites of that era to find myself in a ghost city full of dilapidated buildings. blacksphere.tk is now just a black page. nokiafree.org attempted to renew itself providing recent Nokia news, but got abandoned early this year (but still kept the awesome forum archive). g3gg0.de, the website of one of the legendary hackers that put a lot of effort on the reverse engineering, lost a lot of the old content in an update and stopped updating his blog in 2013. Most of the links point to dead websites, and it's getting harder to find copies of the tools and firmware images. I'll upload some later.
and the PPM is what I'm looking for: it stores all the localization data (strings and operator list), fonts, ringtones and bimaps. PPMEdit is a nice piece of software to edit and export that data.
When I informed Nokia that all Fastmiles with a firmware version older than 3TG00118ABGA17 came with the same secret admin account password, I expected the solution to be obvious. Disable the account, or generate the password based off things like the Serial number of the device.
Around August/October 2022, a new firmware version 3TG00118ABGA31 got rolled out to my device. I could no longer log into the web interface as admin using the old password, awesome, they fixed it I thought. Oh how wrong I was.
Recently I had a chance to take a look at what they'd done. I started by doing the laziest thing possible, as I had 2 devices, I patched both of them, and just thought I'd retrieve the config for both of the devices to compare them.
EDIT 05/2023: This password seems to be generated from the password you set prior to upgrading to 3TG00118ABGA31, in my case both my units were set with the same password. If someone can provide extract their config following an upgrade without having changed the last one that would be appreciated.
Unless they change their mind, there's a good chance this new hardcoded password is here to stay. If you own one of these devices, I suggest you login yourself with the credentials above and change it yourself to something unique.
Through working with @cookie we now also know a bit more about the firmware versions available for the Fastmile. I've compiled a table of the versions we've observed thus far and where possible have provided a download link for your consumption.
While there's snippets of information spread across various forums about how to do this, none of this was super obvious to me. I swear most forum threads ended something like this instead of actually being helpful:
In the first part of this series, I wrote about how you could connect to the serial port of the router. This enables us to dump firmware/config off the router side of the Fastmile. While there are tools to help with this, they seemed to be in varying states of unreliable so I opted to do everything manually.
We need to remove the first column and last column from our output log keeping only columns 2-5 and then convert it to a binary file. This blog here explains in detail what we're trying to do ( -to-binary.html).
Shifting our attention to the Android side of the device. EDL stands for Emergency DownLoad Mode and is a special boot mode normally used by OEMs to allow recovery of bricked devices, force flashes of firmware or dumping of firmware.
To place the Fastmile into EDL mode, two headers (next to the UART ones) need to be shorted on boot. The power switch button pictured was just used to more conveniently short those 2 pins, but you can use a screwdriver to do this as well.
All the following Nokia Stock ROM (zip file) contains the original Nokia USB Driver, Flash Tool, and the Firmware File. After Downloading the firmware, follow the instruction manual shipped with the firmware to flash or install firmware on mobile.
While in general third-party firmware (Custom ROM) has system bugs and stability issues. In this case, you may experience battery issues, network issues, camera issues, missing features, lags, overheating, slow performance, and many more. But whenever you switch to Stock ROM, you can quickly fix them all.
[*] After flashing (installing) the Nokia Stock ROM on your device, you may need to flash (install) the IMEI using the IMEI tool provided with the firmware file. If you are going to flash the IMEI, then flash the Original IMEI that comes with your device.
[*] Request Firmware: If you are looking for any specific firmware that is not listed above, you can request it through the comment box below (do not request firmware through the contact page, or else it will be ignored).
I've developed an issue since the last Android 10 OS update where the phone doesn't charge unless it's in 'USB Controlled by device' mode, which it usually fails to switch to. I'd like to try flashing stock firmware to it, as resetting to factory default didn't fix the issue.
I've tried downloading a stock firmware file and using the recovery mode option to install from SD card, but alas the timestamp on the file was older than the current OS, and so it refused to downgrade.
Since I'm a complete newbie to the android hacking world, I'm looking for an easy to understand solution to install a fresh stock firmware / ROM (not sure what the nomenclature difference is) or failing that, backing up the existing firmware and re-installing that. Naturally, the phone isn't rooted nor is the bootloader unlocked etc, nor do I currently know how to do those things.
Few days ago I published some notesabout my personal experience with PR 1.1.1 firmware upgrade in NokiaN900. In particular my device got an infinite reboot loop afterupgrading the firmware and I had to flash the firmware image fromscratch to fix the problem. Today I was kindly contacted by MaxWaterman (I suppose he works for Nokia) and he explained me what wasthe problem. It was caused by a little bug in Harmattan UI demo and theyfixed it (the fix is already available in extras-devel).
1. Backup all your contacts, etc. by using the Nokia PC Suite Backup feature (Nokia Content Copier). I always like to have double-backups (especially since last time!) so backup your contacts to memory card using your phone as well.
3. Connect your fully-charged Nokia N95 via USB cable to your computer. Run Nemesis Service Suite and click on the magnifying glass at the top-right of the screen. This will search for connected devices.
5. Click on the Read icon on the right-hand side of the screen to bring up details about the firmware on your N95. Press the radio button next to Product Code and change the numbers in the box to 0536062. Press the Write button.
6. To check that you have changed the product code successfully, disconnect your N95, reconnect it and then go through steps 3 and 4 again. You should see 0536062 in the box where you changed it.
It's a fair cop, I just couldn't resist trying out another custom firmware for Symbian. At least in this case I had a willing volunteer, in the form of an old Nokia C7 which had been in heavy use for a year and which was in dire need of a clear out and rebuild anyway. Delight 6.2 for the C7 is freshly released, so I threw caution to the wind and flashed it onto what is now a two-and-a-half year old smartphone. How was the experience and what does Delight 6.2 firmware actually get you? Here's my report.
The 'Delight' series of firmwares is quite well known, of course, but this is the first time I'd tried one. The documentation pages are a little scattered and somewhat technical in places, but here's a plain English, summarised guide to what's different for Delight 6.2, compared to the stock Belle Befresh firmware:
As usual, I won't go into the intricacies of flashing firmware onto Symbian smartphones - there are plenty of guides online and it's not strictly above board. Nokia doesn't seem to mind too much, unofficially, but the act of going down this route will void any warranty or right to support. Of course, you're probably flashing custom firmware because the device is quite old and well out of warranty anyway, so the chances are that this won't bother you. (For reassurance, though, see my postscript, below.)
In broad strokes, the idea is to download the Delight 6.2 firmware (a self extracting .EXE file) onto a Windows Vista or 7 PC, and put the files it contains into a 'RM-675' folder inside \Phoenix\Products in your PC's 'Program files' folder tree. Note that if you want a non-English version then you'll have to delve into the Delight documentation and add a few extra files in.
59fb9ae87f