Reply
Thread Tools
Posts: 90 | Thanked: 2 times | Joined on May 2010 @ New delhi, India
#31
Originally Posted by ossipena View Post
have you overclocked?

plus zillion other questions for background information that might reveal something useful.
no i did not overclock it but i had upgraded to pr 1.3 yesterday
 
Posts: 4 | Thanked: 0 times | Joined on Aug 2010
#32
Originally Posted by aspetri View Post
hey i have this same broblem what extenson to the end u mean?
He means the ".bin" at the end of the file.
I have the same Problem as many else here, so I tried it step by step as mentioned with the result:

Code:
C:\Programme\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_C
OMBINED_MR0_ARM.bin -f -R
flasher v2.5.2 (Sep 24 2009)

SW version in image: RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'kernel', size 1705 kB
        Version 2.6.28-20103103+0m5
Image 'rootfs', size 185728 kB
        Version RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'cmt-2nd', size 81408 bytes
        Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
        Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
        Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
        Valid for RX-51: 2217, 2218, 2219, 2220, 2120
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2217, 2218, 2219, 2220, 2120
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2217, 2218, 2219, 2220, 2120
        Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
        Valid for RX-51: 2101, 2102, 2103
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2101, 2102, 2103
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2101, 2102, 2103
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2307, 2308, 2309, 2310
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2307, 2308, 2309, 2310
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2307, 2308, 2309, 2310
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2407, 2408, 2409, 2410
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2407, 2408, 2409, 2410
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2407, 2408, 2409, 2410
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
        Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
        Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2607, 2608, 2609, 2610
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2607, 2608, 2609, 2610
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2607, 2608, 2609, 2610
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2507, 2508, 2509, 2510
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2507, 2508, 2509, 2510
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2507, 2508, 2509, 2510
        Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
        Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
        Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
        Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
        Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
        Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
        Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
        Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
        Version 1.4.14.9+0m5
Unknown arguments specified!
Usage: flasher [OPTIONS]
Options:
  -F, --fiasco=ARG            Location of a FIASCO image
  -k, --kernel=ARG            Location of kernel image
  -n, --initfs=ARG            Location of initfs image
  -r, --rootfs=ARG            Location of root JFFS2 image
      --cmt-2nd=ARG           Location of CMT FIASCO 2nd image
      --cmt-algo=ARG          Location of CMT FIASCO algorithm image
      --cmt-mcusw=ARG         Location of CMT FIASCO MCUSW image
      --cmt-no-verify         Disable verification of CMT programming
  -x, --xloader=ARG           Location of X-Loader image
  -s, --secondary=ARG         Location of NOLO secondary bootloader image
  -2, --2nd=ARG               Location of NOLO cold flasher ("2nd") image
  -u, --unpack[=ARG]          Unpack a FIASCO image
  -f, --flash                 Load and flash all supplied images
  -l, --load                  Only load all supplied images
  -b, --boot[=ARG]            Boot the kernel with optional cmdline
  -R, --reboot                Reboot the board (e.g. after flashing NOLO)
  -i, --read-device-id        Print out the device type
  -S, --serial-port=ARG       Serial port used for cold flashing or "usb"
  -I, --init-port             Only initialize the serial port
  -c, --cold-flash            "Cold flash" the device
  -h, --hw-revision=ARG       Specify product code and HW revision
      --enable-rd-mode        Enable R&D mode on the device
      --disable-rd-mode       Disable R&D mode on the device
      --set-rd-flags[=ARG]    Set R&D mode flags on the device
      --clear-rd-flags[=ARG]  Clear R&D mode flags on the device
      --query-rd-mode         Query the device R&D mode status and flags
      --set-hw-revision[=ARG] Set HW revision override on device
      --flash-only=ARG        Flash only certain components
  -U, --usb-device=ARG        Specify USB device to use (bus:device address)
I aint got a clue - somebody knows what to do?
 
Posts: 4 | Thanked: 0 times | Joined on Aug 2010
#33
Ok I got it

Code:
100% (185728 of 0 kB, avg. 185728 kB/s)
Finishing flashing... done
CMT flashed successfully
Well I charged the battery for more hours yesterday and connected the n900 with my PC. I started the CMD and run
Code:
flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f -R
No USB Device found, waiting......... now I inserted the battery into the mobile device, voila!
 
Posts: 58 | Thanked: 13 times | Joined on Jan 2010 @ Los Angeles
#34
Originally Posted by jamie721 View Post
System Malfunction!
device shutdown in 10s!.


it would then reboot repeatedly until battary ran out.


SOLUTION!!!!!-!!!WOOT WOOT !!!

... ...

The computer should then recognize your n900 and start to do stuff wait for this to finish. on my computer it only took 1 minuet 30 seconds ruffley. but be patiant dont rush it dont stop half way through dont unplugg make sure it has completly stoped before unplugging.

reboot the n900 walla

aww man i was hoping u saved me. but i have the same problem you started with, but cant get the flasher to work. after doing 'u' and inserting the battery, the flasher is still waiting. but phone shows usb icon
 
James_Littler's Avatar
Posts: 820 | Thanked: 436 times | Joined on May 2010 @ Portsmouth, UK.
#35
try it through an ubuntu live cd or usb stick, windows always does this.
you can try pulling the usb from the pc and trying a different port. I found one that always works, since then I've not had one error.
 
Posts: 58 | Thanked: 13 times | Joined on Jan 2010 @ Los Angeles
#36
im still new to linux. whats a live cd? and how would i use a usb stick for this? im installing ubuntu through wubi. will that help me? thanks again for the help
 
Posts: 12 | Thanked: 0 times | Joined on Nov 2010
#37
please anyone help me....! my N900 shows NOKIA WITH VIBRATION and continues doing this until it says MALFUNCTION! DEVICE SHUTDOWN IN 10S please help me...! please please please..! i m in a great trouble and please give me some safe solution. please please.........................!
 
Posts: 12 | Thanked: 0 times | Joined on Nov 2010
#38
Originally Posted by jamie721 View Post
I had this problem the other day. I was getting angry with the fact i could no longer download any appplications due to having a full rootfs so i decided i was gonna try and clean it up manualy. i gained root *Woops* then did rm -f /usr/lib/* . seemed to have worked ok then i tryed to boot some applications they started to load but then disapeared. i then paniced thought opps why did i have to do that and restarted at this point i was faced with the dreaded
System Malfunction!
device shutdown in 10s!.


it would then reboot repeatedly until battary ran out.


SOLUTION!!!!!-!!!WOOT WOOT !!!

1.Find somebody with either the same phone n900 or the nokia x5800 or go buy an external charger to charge your battery for your phone.

i didnt belive these next 2 statements untill i tryed it.

Your n900 is unable to charge your battery in this state!!

You are unable to flash your phone with less then over half a battery!!!


2. Once you have charged your battery remove it and sit it on your side.

Prepare your computer for a re-flashing the n900.

3.You must install flasher 3.5. There are tutorials for installing this to windows linux and mac on this site.
3.1.Download and install the latest version of Flasher e.g.
maemo_flasher-3.5_2.5.2.2.exe


4.Download the firmware for your n900 save this in a memorable place.

Connecting your phone to computer.

5.With the battery still removed hook your computer up to the n900 using the usb data cable.

Running flasher "haha" 3.5

6. Run the flashing application on computer. Like i said befor i will post the exact details when i get home

This application will stop and say its waiting to find the device that you want to flash.

Back to the phone
7.now with your phone all ready plugged into the computer open the keyboard and hold the "u" button and insert the battery while holding the "u" button. keep holding the u button untill you can see a very faint usb sign in the top right of the screen. This will put the phone into flashing mode aka R&D mode.

Warning you can not enter R&D mode with little battery must be full or nearly full.

The computer should then recognize your n900 and start to do stuff wait for this to finish. on my computer it only took 1 minuet 30 seconds ruffley. but be patiant dont rush it dont stop half way through dont unplugg make sure it has completly stoped before unplugging.

reboot the n900 walla

You may find that your sim card is no longer recognised do not panic this is just because you need to update your n900 . Do this by either connecting to wireless lan at your home and using the app manager update accross the internet or plugging the phone into the computer and using the nokia suite to update it over the internet. The latter i have not tested.

i hope this will help every one and could maybe become a basis for a flashing tutorial on this site. as i had to find all this infprmation all over the place.
is this safe please help me.
 
XiliX's Avatar
Posts: 356 | Thanked: 217 times | Joined on Aug 2010 @ Netherlands
#39
Originally Posted by youngcalihottie View Post
im still new to linux. whats a live cd?
A live cd is a bootable cd/dvd with an operating system on the disk.
That means you can simply stuff the dvd/cd into you computer and boot Linux or windows from it without actually installing it.

Anyway, back ontopic: where did you get the idea to RM -RF /usr/lib?
 
Posts: 12 | Thanked: 0 times | Joined on Nov 2010
#40
hey do u know what to do if my NOKIA N900 sys MALFUNCTION! DEVICE SHUTDOWN IN 10S please help me
 
Reply

Tags
boot, boot error, boot message, error, error message, fremantle, green error, green message, maemo, maemo 5, power on, power on error, power on message, shutdown in 10s, startup, startup error, startup message, system malfunction


 
Forum Jump


All times are GMT. The time now is 02:20.