Nokia N9 help? MALF indicator file?
 

A few days ago my Nokia N9 went dead flat and then when i went to charge it it would only boot up to the nokia logo on screen and then eventually would come up with "Device not working properly" "try updating the device software with Nokia Software Updater. If the problem persists, contact the nearest Nokia Care point." "Software problem (boot-watchdog): too many reboots.

If i try the connect it to the computer for Nokia Software Updater or Phoenix test and service software the phone turns on with the nokia logo on screen and then a USB connection logo in the corner that goes away, and on my computer it comes up with "USB device not recognized" "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." "Recommendation Try reconnecting the device. If windows still does not recognize it, your device may not be working properly."

Suggestions...?

Re: Nokia N9 please help...
 

It looks your device has the MALF flag set. This is a sorts of a protection method, albeit it usually causes more trouble than helps :)

When the phone detects that it has too many restarts in a short period, the system protects itself by creaing a file /var/malf on the filesystem. This is a signal for the device to stop and instruct user to get maintanance for the device.

You can clear the malf file by booting into device rescue mode, using flasher and a dedicated kernel+initramfs image.

Search the forum for "/var/malf" and you will find the procedure.

Re: Nokia N9 please help...
 

I don't understand how this will work when my computer doesn't recognize my N9 and says it malfunctioned?

Re: Nokia N9 please help...
 

You cannot use "Nokia Software Updater" or "Phoenix" to fix this problem :)

You need to get a repair mode kernel and flash that to your device. Furthermore, if you are using Windoze you need a NDIS driver for it if you are going to fix via telnet connection, or EXT4FS driver if you want to mount the device to your PC.

Re: Nokia N9 please help...
 

Thanks, and can this be done via USB..?

Re: Nokia N9 please help...
 

I'm guessing these are the instructions i need to follow? http://www.allboutn9.info/2013/01/lo...lution_23.html

Re: Nokia N9 please help...
 

Yes, it is done via USB. Procedure goes like this:

• 1.) The device is booted so that a special "rescue mode" kernel is pushed to the device via USB. (this will work even for quite dead device)
• 2.) When the device boots, it will export the internal filesystems as USB drives to the computer. It looks like 3 USB drives are connected to the computer. Also, the device will configure IP-over-USB (NDIS) type of network interface, allowing you to telnet to the device
• 3.) You fix the MALF state, either via filesystem export or telnet
• 4.) Profit...:D

Re: Nokia N9 please help...
 

Are these the correct instructions? http://www.allboutn9.info/2013/01/lo...lution_23.html

Re: Nokia N9 please help...
 

Thanks are these the correct instructions?

A. Preparations

Download these files (if download doesn't work: Use right-click / Save file as, or similar):

MeeGo kernel
N950 MeeGo rescue initrd
Flasher (Flasher for Linux / WinFlasher 3.12 for Windows / MacFlasher 3.12 for OSX)
Windows Driver (for Windows users)


B: Flashing and mount

Provided here are Linux commands. If you are a Windows/OSX user, you need an ext4 Filesystem driver (Windows solution / OSX solution).

1. Unplug the USB cable from your phone2. Turn your phone off
3. Load the N950 MeeGo kernel and N950 MeeGo rescue initrd using flasher:

$ sudo flasher --load -k vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot

4. Insert the usb cable.5. Wait about a minute until a new USB mass storage device appears on the host.

You should now have three partitions: /dev/sdX1 which is MyDocs, /dev/sdX2 which is MeeGo 1.2 Harmattan rootfs, and /dev/sdX3 which is the MeeGo 1.2 Harmattan home directory.

6. If your PC is running a recent version of Ubuntu (or similar) the partitions should be mounted automatically or offered to be mounted. If not:

Find exact partition's names found on your Nokia N9/N950 and mount these partitions:

$ fdisk -l$ sudo mkdir /mnt/n9; sudo mount /dev/sdb2 /mnt/n9


C: Copy files

Now that the three partitions are mounted, you are able to copy all files away. The rootfs is not needed, but the MyDocs and home partitions store all your important files and settings:

$ rsync -avH --progress /media/Nokia\ N9/ MyDocs/$ rsync -avH --progress /media/101359bd-1016-4d06-8e80-4da91dc2c96f/user/ home/$ rsync -avH --progress /media/rootfs/ rootfs/


Step 2: Flash original OS

Follow the directions here, they are really well explained: http://talk.maemo.org. If you're OSX user you can also follow our tutorial: Flash N9 on OSX.
You should use "Zeroize device (destroys user data)" to remove the lost Password. Any other type of reflash will NOT remove the password!


Step 3: Restore your data

As soon as the reflash is done, you're able to use your phone again. You can now connect the phone via USB and copy all needed data back to the N9. To restore SMS, contacts calendar and so on, I hope you have done a manual backup with the built-in backup application or have them synced with Mail for Exchange (or similar). Otherwise it wouldn't be that easy, as the data is stored in the tracker database. Maybe someone finds out how to do it, I didn't.

Learning points: Don't forget or loose the password and always make backups of your important data. Backups up your personal data can be done manually and everything else with NokiaLink or Nokia Suite (links can be found here).

Re: Nokia N9 please help...
 

Yes, those instructions tell you how to backup data of your device before flashing when you have non-bootable device.

However, it is possible that you do not need to flash it, just to remove the MALF indicator file (/var/malf) to fix your device.
(If you have no other problems, than device MALFfing due to too many boot attempts)

If you want to flash your device also, you'll need the firmware images (emmc and main firmware) that are correct for your PR level and device country variant.

Re: Nokia N9 please help...
 

Okay cool, do you know where i can find specific instructions to remove the MALF indicator file (/var/malf)?

Re: Nokia N9 please help...
 

I'm using windows and im stuck at

You should now have three partitions: /dev/sdX1 which is MyDocs, /dev/sdX2 which is MeeGo 1.2 Harmattan rootfs, and /dev/sdX3 which is the MeeGo 1.2 Harmattan home directory.

6. If your PC is running a recent version of Ubuntu (or similar) the partitions should be mounted automatically or offered to be mounted. If not:

Find exact partition's names found on your Nokia N9/N950 and mount these partitions:

$ fdisk -l$ sudo mkdir /mnt/n9; sudo mount /dev/sdb2 /mnt/n9

Re: Nokia N9 please help...
 

When you do the things in the instruction above, until you get to the phase 4.) where is says:
"You should now have three partitions: /dev/sdX1 which is MyDocs, /dev/sdX2 which is MeeGo 1.2 Harmattan rootfs, and /dev/sdX3 which is the MeeGo 1.2 Harmattan home directory."

You will see the MALF file in your mounted Harmattan rootfs which probably will be something like /media/rootfs/var/malf if you are using Ubuntu. Some other Linux version might mount it to different place.

You can check it by command "ls -l /media/rootfs/var/malf", and if it exists, then you can remove it by command "sudo rm /media/rootfs/var/malf"

Re: Nokia N9 please help...
 

You need to ask advice from somebody else, then, I am afraid :(
I have no windows so cannot help you with that...

Re: Nokia N9 please help...
 

Could i install Ubuntu and do it from there?

Re: Nokia N9 please help...
 

I am determined to fix this so if anyone else has any advice please don't hold back!

how to remove MALF indicator file from Nokia N9 using Windows?
 

A few days ago my Nokia N9 went dead flat and then when i went to charge it it would only boot up to the nokia logo on screen and then eventually would come up with "Device not working properly" "try updating the device software with Nokia Software Updater. If the problem persists, contact the nearest Nokia Care point." "Software problem (boot-watchdog): too many reboots.

If i try the connect it to the computer for Nokia Software Updater or Phoenix test and service software the phone turns on with the nokia logo on screen and then a USB connection logo in the corner that goes away, and on my computer it comes up with "USB device not recognized" "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." "Recommendation Try reconnecting the device. If windows still does not recognize it, your device may not be working properly."

Apparently i need to remove the MALF indicator file to fix this? can anyone help me, i am using windows..

Re: Nokia N9 please help...
 

Yes, you can for example download an Ubuntu disk image and boot from the disk, no need to install it permanenetly.

Re: Nokia N9 please help...
 

I'm on Ubuntu now..
Where am i going wrong..?

ubuntu@ubuntu:~$ /home/ubuntu/Downloads/flasher_3.12.1_i386.deb --load -k /home/ubuntu/Downloads/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n /home/ubuntu/Downloads\initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
/home/ubuntu/Downloads/flasher_3.12.1_i386.deb: line 1: syntax error near unexpected token `newline'
/home/ubuntu/Downloads/flasher_3.12.1_i386.deb: line 1: `!<arch>'

Re: Nokia N9 please help...
 

The .deb file is a installation package, not an executable.
First you install the flasher on your ubuntu with a command like "sudo dpkg -i /home/ubuntu/Downloads/flasher_3.12.1_i386.deb", then you use it (probably as /usr/bin/flasher, just type flasher<Tab> and it should complete the name if it's in the command path)

Re: Nokia N9 please help...
 

Okay i'm running Ubuntu on 64-bit...

So i'd go "sudo dpkg -i --force-architecture /home/ubuntu/Downloads/flasher_3.12.1_i386.deb"

And then

--load -k /home/ubuntu/Downloads/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n /home/ubuntu/Downloads\initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot ?

Re: Nokia N9 help? MALF indicator file?
 

Most probably it will work OK. :)
I haven't actually ever installed a 32bit package on a 64bit machine, but if you can install it, the binary itself should run OK.

Re: Nokia N9 help? MALF indicator file?
 

Okay i managed to get flasher_3.12.1_amd64.deb for 64bit but am still having issues...

ubuntu@ubuntu:~$ sudo dpkg --install /home/ubuntu/Downloads/flasher_3.12.1_amd64.deb
(Reading database ... 169560 files and directories currently installed.)
Preparing to unpack .../flasher_3.12.1_amd64.deb ...
Unpacking flasher (3.12.1) over (3.12.1) ...
Setting up flasher (3.12.1) ...
ubuntu@ubuntu:~$ --load -k /home/ubuntu/Downloads/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n /home/ubuntu/Downloads\initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
--load: command not found

Re: Nokia N9 help? MALF indicator file?
 

The command is "sudo flasher --load ... ... "

Re: Nokia N9 help? MALF indicator file?
 

BTW, I just tried to install the 32bit package on my 64bit Linux Mint 17 (but note that recent Ubuntus have multiarch support) and I was at least able to get the flasher help page without coredumps :)

Re: Nokia N9 help? MALF indicator file?
 

Hmmm now what :S

ubuntu@ubuntu:~$ sudo dpkg --install /home/ubuntu/Downloads/flasher_3.12.1_amd64.deb
(Reading database ... 169573 files and directories currently installed.)
Preparing to unpack .../flasher_3.12.1_amd64.deb ...
Unpacking flasher (3.12.1) over (3.12.1) ...
Setting up flasher (3.12.1) ...
ubuntu@ubuntu:~$ sudo flasher --load
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 003, device address 004.
Device identifier: 357923040690689 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Success
ubuntu@ubuntu:~$ -k /home/ubuntu/Downloads/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n /home/ubuntu/Downloads\initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
Traceback (most recent call last):
File "/usr/lib/command-not-found", line 27, in <module>
from CommandNotFound.util import crash_guard
File "<frozen importlib._bootstrap>", line 2214, in _find_and_load
File "<frozen importlib._bootstrap>", line 2203, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
File "<frozen importlib._bootstrap>", line 1129, in _exec
File "<frozen importlib._bootstrap>", line 1444, in exec_module
File "<frozen importlib._bootstrap>", line 1548, in get_code
File "<frozen importlib._bootstrap>", line 1601, in get_data
OSError: [Errno 5] Input/output error

Re: Nokia N9 help? MALF indicator file?
 

is single command

Re: Nokia N9 help? MALF indicator file?
 

Why won't it let me instal the flasher? ubuntu@ubuntu:~$ sudo dpkg --install /home/ubuntu/Downloads/flasher_3.12.1_amd64.deb
dpkg: error: failed to open package info file `/var/lib/dpkg/available' for reading: Input/output error
ubuntu@ubuntu:~$

Re: Nokia N9 help? MALF indicator file?
 

How do you run Ubuntu, from an USB stick?
Google for that exact error, you find similar posts like this one:
http://ubuntuforums.org/showthread.php?t=1644026
(which seems to hint towards a cr@ppy memory stick)

Re: Nokia N9 help? MALF indicator file?
 

Just booted it from the USB? I think it might be because /flasher_3.12.1_amd64.deb is still running in the terminal when i try and use /home/ubuntu/Downloads/flasher_3.12.1_amd64.deb how do i end the package running in the terminal?

Re: Nokia N9 help? MALF indicator file?
 

Thanks for the patience people.. i managed to get this far lol :S what should i do next..? ubuntu@ubuntu:~$ sudo flasher --load -k /home/ubuntu/Downloads/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n /home/ubuntu/Downloads/initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 003, device address 004.
Device identifier: 357923040690689 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending kernel image (2497 kB)...
100% (2497 of 2497 kB, avg. 39648 kB/s)
Sending initfs image (1920 kB)...
100% (1920 of 1920 kB, avg. 38400 kB/s)
Success

Re: Nokia N9 help? MALF indicator file?
 

Anyone............?

Re: Nokia N9 help? MALF indicator file?
 

Okay, so did you see the new disk drives pop visible on your PC when you got to this point?
What should happen, is you should now have 3 new devices available on your system; the rootfs, the /home and the /MyDocs

As you are using Ubuntu, the mountpoints are under /media but I believe you should have 3 different file folders pop up on your display.

Re: Nokia N9 help? MALF indicator file?
 

No i didn't see anything new devices come up and couldn't find them. If they don't come up apparently you find exact partition's names found on your Nokia N9/N950 and mount these partitions?

$ fdisk -l$ sudo mkdir /mnt/n9; sudo mount /dev/sdb2 /mnt/n9

How do i go about doing that..

Re: Nokia N9 help? MALF indicator file?
 

Well, open a new console and give command "sudo fdisk -l"

What happens, is it shows all partitions that are mounted to your Linux box.
There probably is something that starts like /dev/sdb-something.

Please show what you see.

Re: Nokia N9 help? MALF indicator file?
 

ubuntu@ubuntu:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 750.2 GB, 750156374016 bytes
256 heads, 63 sectors/track, 90845 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xebfcfc03

Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdb: 7964 MB, 7964983296 bytes
91 heads, 18 sectors/track, 9497 cylinders, total 15556608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 * 8192 15556607 7774208 c W95 FAT32 (LBA)

Disk /dev/sdc: 29 MB, 29393408 bytes
1 heads, 10 sectors/track, 5740 cylinders, total 57409 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 57408 28704 1 FAT12

Disk /dev/sdd: 20 MB, 20972032 bytes
1 heads, 2 sectors/track, 20480 cylinders, total 40961 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdd1 1 40960 20480 4 FAT16 <32M

Re: Nokia N9 help? MALF indicator file?
 

Okay, this looks a bit different than what I expected.
The warning about /dev/sda being GUID partition is okay, that's your system's linux rootdisk, and nowdays old-style partition tables are considered legacy.

the other disks, sdb to sdd thouhg, seem to be windows fat partitions, probably housing windows on your machine.

I cannot see any N9 partitions there, which is strange...

Could you do a "dmesg" command after you push the kernel & initramfs to your N9?
There could probably be a logging about the reason why the filesystem exports are not detected....
(dmesg output is fairly long, just copy the last 50 lines or so here)

Re: Nokia N9 help? MALF indicator file?
 

One other thing you might want to try BTW.
Instead of the rescue kernel&initramfs, you can downlload the latest ubiboot kernel which contains the integrated maintanance mode.

• Get it from here: http://www.swagman.org/juice/ubiboot...3.5_301013.tar
• Unpack the tarfile, and you will get the ubiboot kernel (zImage_2.6.32.54-ubiboot-02_301013)
• Boot your N9 with the kernel; "sudo flasher -k zImage_2.6.32.54-ubiboot-02_301013 -l -b"

Now, see if this gives you a better filesystem export.

Re: Nokia N9 help? MALF indicator file?
 

[ 5.464772] usb 2-1: New USB device found, idVendor=8087, idProduct=0024

[ 5.632533] usb 3-4: new high-speed USB device number 2 using xhci_hcd
[ 5.649028] usb 3-4: New USB device found, idVendor=054c, idProduct=0707
[ 5.649034] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5.649038] usb 3-4: Product: DSC-W710
[ 5.649050] usb 3-4: Manufacturer: Sony
[ 5.649052] usb 3-4: SerialNumber: C605305834E3
[ 5.652228] usb-storage 3-4:1.0: USB Mass Storage device detected
[ 5.652339] scsi6 : usb-storage 3-4:1.0
[ 5.652391] usbcore: registered new interface driver usb-storage
[ 5.662002] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x127c00, board id: 1999, fw id: 1106483
[ 5.697824] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 5.712623] tsc: Refined TSC clocksource calibration: 2195.013 MHz
[ 5.720781] usb 1-1.2: new full-speed USB device number 3 using ehci-pci
[ 5.814450] [drm] fb mappable at 0xB0474000
[ 5.814454] [drm] vram apper at 0xB0000000
[ 5.814455] [drm] size 4325376
[ 5.814456] [drm] fb depth is 24
[ 5.814457] [drm] pitch is 5632
[ 5.814589] fbcon: radeondrmfb (fb0) is primary device
[ 5.814825] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e036
[ 5.814827] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5.814828] usb 1-1.2: Product: Bluetooth USB Host Controller
[ 5.814829] usb 1-1.2: Manufacturer: Atheros Communications
[ 5.814830] usb 1-1.2: SerialNumber: Alaska Day 2006
[ 5.884964] usb 1-1.3: new high-speed USB device number 4 using ehci-pci
[ 5.987499] usb 1-1.3: New USB device found, idVendor=5986, idProduct=02d3
[ 5.987501] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5.987502] usb 1-1.3: Product: USB2.0 Camera
[ 5.987503] usb 1-1.3: Manufacturer: USB2.0 Camera
[ 6.421557] Console: switching to colour frame buffer device 170x48
[ 6.424154] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 6.424156] radeon 0000:01:00.0: registered panic notifier
[ 6.424295] [drm] Initialized radeon 2.36.0 20080528 for 0000:01:00.0 on minor 0
[ 6.650129] scsi 6:0:0:0: Direct-Access Sony DSC 1.00 PQ: 0 ANSI: 0
[ 6.650421] scsi 6:0:0:1: Direct-Access Sony DSC 1.00 PQ: 0 ANSI: 0
[ 6.650711] scsi 6:0:0:2: Direct-Access Sony DSC 1.00 PQ: 0 ANSI: 0
[ 6.651035] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 6.651330] sd 6:0:0:1: Attached scsi generic sg3 type 0
[ 6.651337] sd 6:0:0:0: [sdb] 15556608 512-byte logical blocks: (7.96 GB/7.41 GiB)
[ 6.651523] sd 6:0:0:2: Attached scsi generic sg4 type 0
[ 6.662533] sd 6:0:0:0: [sdb] Write Protect is off
[ 6.662537] sd 6:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 6.662698] sd 6:0:0:1: [sdc] 57409 512-byte logical blocks: (29.3 MB/28.0 MiB)
[ 6.673486] sd 6:0:0:0: [sdb] No Caching mode page found
[ 6.673489] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 6.684628] sd 6:0:0:1: [sdc] Write Protect is on
[ 6.684634] sd 6:0:0:1: [sdc] Mode Sense: 0f 00 80 00
[ 6.684814] sd 6:0:0:2: [sdd] 40961 512-byte logical blocks: (20.9 MB/20.0 MiB)
[ 6.695644] sd 6:0:0:1: [sdc] No Caching mode page found
[ 6.695649] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 6.695926] sd 6:0:0:2: [sdd] Write Protect is on
[ 6.695932] sd 6:0:0:2: [sdd] Mode Sense: 0f 00 80 00
[ 6.699897] sd 6:0:0:2: [sdd] No Caching mode page found
[ 6.699900] sd 6:0:0:2: [sdd] Assuming drive cache: write through
[ 6.713836] Switched to clocksource tsc
[ 6.719047] sd 6:0:0:0: [sdb] No Caching mode page found
[ 6.719052] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 6.731822] sdb: sdb1
[ 6.742723] sd 6:0:0:1: [sdc] No Caching mode page found
[ 6.742728] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 6.764605] sd 6:0:0:2: [sdd] No Caching mode page found
[ 6.764609] sd 6:0:0:2: [sdd] Assuming drive cache: write through
[ 6.765308] random: nonblocking pool is initialized
[ 6.769470] sd 6:0:0:0: [sdb] No Caching mode page found
[ 6.769474] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 6.769476] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 6.773936] sdc: sdc1
[ 6.776815] sdd: sdd1
[ 6.809643] sd 6:0:0:1: [sdc] No Caching mode page found
[ 6.809647] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 6.809649] sd 6:0:0:1: [sdc] Attached SCSI removable disk
[ 6.834652] sd 6:0:0:2: [sdd] No Caching mode page found
[ 6.834657] sd 6:0:0:2: [sdd] Assuming drive cache: write through
[ 6.834661] sd 6:0:0:2: [sdd] Attached SCSI removable disk
[ 18.858843] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 34.100268] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 34.501338] systemd-udevd[1304]: starting version 204
[ 35.381676] lp: driver loaded but no devices found
[ 35.662811] init: cups main process (1349) killed by HUP signal
[ 35.662824] init: cups main process ended, respawning
[ 35.664186] ppdev: user-space parallel port driver
[ 35.903138] Bluetooth: Core ver 2.17
[ 35.903155] NET: Registered protocol family 31
[ 35.903157] Bluetooth: HCI device and connection manager initialized
[ 35.903164] Bluetooth: HCI socket layer initialized
[ 35.903168] Bluetooth: L2CAP socket layer initialized
[ 35.903172] Bluetooth: SCO socket layer initialized
[ 36.140973] Bluetooth: RFCOMM TTY layer initialized
[ 36.140985] Bluetooth: RFCOMM socket layer initialized
[ 36.140990] Bluetooth: RFCOMM ver 1.11
[ 36.141459] sony_laptop: Sony Notebook Control Driver v0.6
[ 36.141568] input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input6
[ 36.141660] input: Sony Vaio Jogdial as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input7
[ 36.147673] sony_laptop: brightness ignored, must be controlled by ACPI video driver
[ 36.208126] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
[ 36.208135] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 36.208140] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
[ 36.208143] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 36.208144] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
[ 36.208146] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 36.208148] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 36.494320] device-mapper: multipath: version 1.6.0 loaded
[ 36.572815] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 36.572819] Bluetooth: BNEP filters: protocol multicast
[ 36.572829] Bluetooth: BNEP socket layer initialized
[ 36.572867] mei_me 0000:00:16.0: irq 46 for MSI/MSI-X
[ 36.712966] usbcore: registered new interface driver btusb
[ 36.729365] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 36.730096] acer_wmi: Brightness must be controlled by acpi video driver
[ 36.730259] input: Acer BMA150 accelerometer as /devices/virtual/input/input8
[ 36.810282] kvm: disabled by bios
[ 36.818454] cfg80211: Calling CRDA to update world regulatory domain
[ 37.149900] Linux video capture interface: v2.00
[ 37.295934] usbcore: registered new interface driver ath3k
[ 37.311525] usb 1-1.2: USB disconnect, device number 3
[ 37.502560] uvcvideo: Found UVC 1.00 device USB2.0 Camera (5986:02d3)
[ 37.504180] input: USB2.0 Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input9
[ 37.504246] usbcore: registered new interface driver uvcvideo
[ 37.504248] USB Video Class driver (1.1.1)
[ 37.507167] cfg80211: World regulatory domain updated:
[ 37.507170] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 37.507172] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 37.507174] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 37.507175] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 37.507177] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 37.507178] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 37.509857] usb 1-1.2: new full-speed USB device number 5 using ehci-pci
[ 37.531639] init: failsafe main process (1538) killed by TERM signal
[ 37.603822] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e036
[ 37.603827] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 37.603831] usb 1-1.2: Product: Bluetooth USB Host Controller
[ 37.603834] usb 1-1.2: Manufacturer: Atheros Communications
[ 37.603836] usb 1-1.2: SerialNumber: Alaska Day 2006
[ 37.776185] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
[ 37.826176] intel_rapl: domain uncore energy ctr 0:0 not working, skip
[ 37.843026] SKU: Nid=0x1d sku_cfg=0x4016862d
[ 37.843029] SKU: port_connectivity=0x1
[ 37.843030] SKU: enable_pcbeep=0x1
[ 37.843031] SKU: check_sum=0x00000006
[ 37.843032] SKU: customization=0x00000086
[ 37.843033] SKU: external_amp=0x5
[ 37.843033] SKU: platform_type=0x1
[ 37.843034] SKU: swap=0x0
[ 37.843035] SKU: override=0x1
[ 37.843252] autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 37.843255] speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 37.843256] hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[ 37.843257] mono: mono_out=0x0
[ 37.843258] inputs:
[ 37.843259] Mic=0x18
[ 37.843261] Internal Mic=0x12
[ 37.843262] realtek: No valid SSID, checking pincfg 0x4016862d for NID 0x1d
[ 37.843263] realtek: Enabling init ASM_ID=0x862d CODEC_ID=10ec0269
[ 37.847689] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 37.847781] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 37.848080] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 37.848082] hda-intel 0000:01:00.1: Using LPIB position fix
[ 37.848116] snd_hda_intel 0000:01:00.1: irq 48 for MSI/MSI-X
[ 37.850456] hda-intel 0000:01:00.1: Enable sync_write for stable communication
[ 37.909752] HDMI ATI/AMD: no speaker allocation for ELD
[ 37.909822] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12
[ 38.352718] ath: phy0: ASPM enabled: 0x42
[ 38.352722] ath: EEPROM regdomain: 0x65
[ 38.352723] ath: EEPROM indicates we should expect a direct regpair map
[ 38.352725] ath: Country alpha2 being used: 00
[ 38.352726] ath: Regpair used: 0x65
[ 38.492005] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 38.492320] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xffffc90004a80000, irq=16
[ 40.881837] init: alsa-restore main process (1831) terminated with status 99
[ 40.990727] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 40.993766] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 41.135672] r8169 0000:0e:00.0 eth0: link down
[ 41.135720] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 41.136158] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 44.058420] init: plymouth-upstart-bridge main process ended, respawning
[ 44.064178] init: plymouth-upstart-bridge main process (2362) terminated with status 1
[ 44.064192] init: plymouth-upstart-bridge main process ended, respawning
[ 55.810648] HDMI ATI/AMD: no speaker allocation for ELD
[ 56.109254] HDMI ATI/AMD: no speaker allocation for ELD
[ 56.409548] HDMI ATI/AMD: no speaker allocation for ELD
[ 56.709868] HDMI ATI/AMD: no speaker allocation for ELD
[ 57.010195] HDMI ATI/AMD: no speaker allocation for ELD
[ 57.310502] HDMI ATI/AMD: no speaker allocation for ELD
[ 57.610835] HDMI ATI/AMD: no speaker allocation for ELD
[ 57.911141] HDMI ATI/AMD: no speaker allocation for ELD
[ 58.211457] HDMI ATI/AMD: no speaker allocation for ELD
[ 69.616058] systemd-hostnamed[3695]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 79.522137] wlan0: authenticate with 00:24:17:3a:d3:01
[ 79.529030] wlan0: send auth to 00:24:17:3a:d3:01 (try 1/3)
[ 79.531392] wlan0: authenticated
[ 79.531571] ath9k 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 79.531577] ath9k 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 79.533755] wlan0: associate with 00:24:17:3a:d3:01 (try 1/3)
[ 79.536731] wlan0: RX AssocResp from 00:24:17:3a:d3:01 (capab=0x411 status=0 aid=1)
[ 79.536958] wlan0: associated
[ 79.536969] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 519.505538] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[ 519.522277] usb 3-1: unable to get BOS descriptor
[ 519.523258] usb 3-1: New USB device found, idVendor=0421, idProduct=0106
[ 519.523266] usb 3-1: New USB device strings: Mfr=34, Product=38, SerialNumber=0
[ 519.523269] usb 3-1: Product: Nokia USB ROM
[ 519.523272] usb 3-1: Manufacturer: Nokia
[ 522.527100] usb 3-1: USB disconnect, device number 3
[ 524.118394] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[ 524.142457] usb 3-1: New USB device found, idVendor=0421, idProduct=0105
[ 524.142465] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 524.142469] usb 3-1: Product: N9 (Update mode)
[ 524.142472] usb 3-1: Manufacturer: Nokia
[ 524.142475] usb 3-1: SerialNumber: 357923040690689
[ 524.173885] NET: Registered protocol family 35
[ 524.194783] usbcore: registered new interface driver cdc_phonet
[ 524.855252] usb 3-1: USB disconnect, device number 4

Re: Nokia N9 help? MALF indicator file?
 

ubuntu@ubuntu:~$ sudo flasher -k /home/ubuntu/Downloads/zImage_2.6.32.54-ubiboot-02_301013 -l -b
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 003, device address 004.
Device identifier: 357923040690689 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending kernel image (11672 kB)...
100% (11672 of 11672 kB, avg. 40250 kB/s)
Success

Also came up with some details on my phone in green writing