Active Topics
-
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 19 hrs, 49 mins ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 1 day, 4 hrs ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 4 days, 13 hrs ago -
Maemo repository (3)
to Community by torsen - 5 days, 6 hrs ago - more...
|
2010-01-16
, 13:03
|
|
Posts: 102 |
Thanked: 7 times |
Joined on Jan 2010
|
#22
|
Originally Posted by wongdong
ive been pressing hard on that "u" key it will eventually go underground.
That should be right
Thats alright if you are from the US
if you put RX-51_2009SE_2.2009.51-1.002_PR_COMBINED_002_ARM.bin isntead of (insert file name here) at least the command is correct
For the flasher you have to remember 2 things:
- It does not work under 64 bit Operating Systems
- The phone must be in production mode (not development mode). According to your description it is correctly set to production mode. maybe you forgot to press "u" on the keyboard while pluggin it in?
and yes i put the RX-51..etc file name on that LOL.
i dont know why it wouldnt start with the flashing
how would you know if its in production mode?
more: i think my phone messed up cause i installed that "haze plug in for IM like yahoo and the likes. i also enabled the extras repo setting? not sure if thats what its called but those 3rd party stuff just didnt do good with my day.
im gonna try to flash the phone again later today with vista 32bit using the same flasher but with the 1st maemo firmware for USA. im using the 2nd right now.
Last edited by bulelet; 2010-01-16 at 13:10.
|
|
2010-01-16
, 13:11
|
|
Posts: 40 |
Thanked: 42 times |
Joined on Jan 2010
@ Vienna
|
#23
|
When the nokia screen appears (where the little usb icon is shown) and you are in the development mode, there will be another icon directly under the logo. But it happens not alone you would know if you had set it so 
Are you using the command from the command line? Post the output then i could say more.
Right now it looks a lot like you would use a 64 bit OS (like Win 7 64bit). What are you actually using?
Are you using the command from the command line? Post the output then i could say more.
Right now it looks a lot like you would use a 64 bit OS (like Win 7 64bit). What are you actually using?
|
|
2010-01-16
, 13:17
|
|
Posts: 102 |
Thanked: 7 times |
Joined on Jan 2010
|
#24
|
Originally Posted by wongdong
When the nokia screen appears (where the little usb icon is shown) and you are in the development mode, there will be another icon directly under the logo. But it happens not alone you would know if you had set it so
Are you using the command from the command line? Post the output then i could say more.
Right now it looks a lot like you would use a 64 bit OS (like Win 7 64bit). What are you actually using?
i use a windows XP media center edition SP3.
i input this words on command prompt EXACTLY AS I SEE THEM: cd "%ProgramFiles%\maemo\flasher-3.5"
after that i plug the USB in while pressing on "u"
and then enter this:
flasher-3.5.exe -F RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R
*oh after i press enter this shows up" RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R %m *
what does the "%m" mean?
nothing happens on my phone, nokia logo and usb on the upper right corner can be seen, lights off on screen.
i wait for 5 minutes, no result.
WHY NOKIA WHY.
Last edited by bulelet; 2010-01-16 at 13:20.
|
|
2010-01-16
, 13:31
|
|
Posts: 40 |
Thanked: 42 times |
Joined on Jan 2010
@ Vienna
|
#25
|
Ok, step by step, like with my studens
1.) You still didnt tell me if you have a 64 bit os or a 32 bit os, but i'll just assume you do.
2.) if you just enter flahser-3.5.exe (without anything) you MUST see this output:
-----------------------------------
C:\flasher>flasher-3.5.exe
flasher v2.5.2 (Sep 24 2009)
Nothing to do!
Usage: flasher [OPTIONS]
Options:
-F, --fiasco=ARG Location of a FIASCO image
-k, --kernel=ARG Location of kernel image
..........
-----------------------------------
Then make sure the .bin image is in the same directory and you are good to go
If you don't please follow a guide that explains how to correctly use the flasher. This threat is supposed to discuss the PR1.1 issue and not the associated problems that come with flashing. Sorry pal...
Last edited by wongdong; 2010-01-16 at 13:37.
1.) You still didnt tell me if you have a 64 bit os or a 32 bit os, but i'll just assume you do.
2.) if you just enter flahser-3.5.exe (without anything) you MUST see this output:
-----------------------------------
C:\flasher>flasher-3.5.exe
flasher v2.5.2 (Sep 24 2009)
Nothing to do!
Usage: flasher [OPTIONS]
Options:
-F, --fiasco=ARG Location of a FIASCO image
-k, --kernel=ARG Location of kernel image
..........
-----------------------------------
Then make sure the .bin image is in the same directory and you are good to go
If you don't please follow a guide that explains how to correctly use the flasher. This threat is supposed to discuss the PR1.1 issue and not the associated problems that come with flashing. Sorry pal...
Last edited by wongdong; 2010-01-16 at 13:37.
 |
|
2010-01-16
, 13:31
|
|
Posts: 780 |
Thanked: 855 times |
Joined on Sep 2009
@ Helsinki, Finland
|
#26
|
Even when I run
"flasher-3.5.exe -F RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R"
without any phone connected I get:
You must use a 32 bit OS!
Last edited by joppu; 2010-01-16 at 13:34.
"flasher-3.5.exe -F RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R"
without any phone connected I get:
Code:
flasher v2.5.2 (Sep 24 2009)
SW version in image: RX-51_2009SE_2.2009.51-1_PR_MR0
Image 'kernel', size 1704 kB
Version 2.6.28-20094803.3+0m5
Image 'rootfs', size 153344 kB
Version RX-51_2009SE_2.2009.51-1_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 5824 kB
Version rx51_ICPR82_09w47
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.2+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.2+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.2+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.2+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.2+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.2+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.2+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.2+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.2+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.2+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.2+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.2+0m5
Suitable USB device not found, waiting.
__________________
My blog (mostly about my themes)
My blog (mostly about my themes)
Last edited by joppu; 2010-01-16 at 13:34.
|
|
2010-01-16
, 13:52
|
|
Posts: 32 |
Thanked: 4 times |
Joined on Jan 2010
|
#27
|
Originally Posted by wongdong
I eventually got the update to take. From a clean install I tried the over the air update and the same problem occured - bricked device.
jaxxstorm? Any news from the front?
I'm still running the 44-version and will wait for a new patch which i'm going to directly flash then.
Heres some tips.
I used Ubuntu - if you don't have it available try getting a live cd and running the flasher from there. There is no reason the Windows flasher shouldn't work, but I trust Ubuntu a hell of a lot more than flashing a Linux device with Win7.
IT WILL NOT WORK ON A 64BIT OS - no idea why, but it won't.
Make sure you run flasher-3.6 -F etc without the phone connected via USB. You will get a prompt "no suitable device found, waiting.." at this stage, plug in via USB.
That should fix it, I'm relieved to know that I'm not the only one with this problem
Oh, and just for the record, I didn't have testing or devel enabled, and I don't really appreciate those people saying its user error, because I'm by no means an idiot.
|
|
2010-01-16
, 15:41
|
|
Posts: 68 |
Thanked: 9 times |
Joined on Nov 2009
|
#28
|
just a quick question,
If you install items such as the haze plugin from extra/devel/testing,
Does this alter system files which do not get restored when you un install?
The user above who is re flashing I am assuming this deletes everything on the device and provides a factory image ?
Cheers,
MB
If you install items such as the haze plugin from extra/devel/testing,
Does this alter system files which do not get restored when you un install?
The user above who is re flashing I am assuming this deletes everything on the device and provides a factory image ?
Cheers,
MB
 |
|
2010-01-16
, 16:12
|
|
Posts: 1,743 |
Thanked: 1,231 times |
Joined on Jul 2006
@ Twickenham, UK
|
#29
|
Just to be complete.
Run the flasher-3.5 command as root:
sudo flasher-3.5 -F <firmware file name> -f -R
when it tells you that it didn't find a device and it's waiting, plug in the USB cable into your turned off N900.
If the flasher complains that the resource is busy, reboot the computer, remove the battery from the N900, put it back in again and retry.
Usually there's no need to keep the 'u' key pressed, but you may want to do it just to be on the safe side. It just tell the N900 to boot up into flash mode.
Aniello
Run the flasher-3.5 command as root:
sudo flasher-3.5 -F <firmware file name> -f -R
when it tells you that it didn't find a device and it's waiting, plug in the USB cable into your turned off N900.
If the flasher complains that the resource is busy, reboot the computer, remove the battery from the N900, put it back in again and retry.
Usually there's no need to keep the 'u' key pressed, but you may want to do it just to be on the safe side. It just tell the N900 to boot up into flash mode.
Aniello
|
|
2010-01-16
, 16:35
|
|
Posts: 41 |
Thanked: 0 times |
Joined on Dec 2009
|
#30
|
Originally Posted by anidel
I put the command but they say me the file not exist i use ubuntu the firmware are in the desktop why the terminal say me this?
Just to be complete.
Run the flasher-3.5 command as root:
sudo flasher-3.5 -F <firmware file name> -f -R
when it tells you that it didn't find a device and it's waiting, plug in the USB cable into your turned off N900.
If the flasher complains that the resource is busy, reboot the computer, remove the battery from the N900, put it back in again and retry.
Usually there's no need to keep the 'u' key pressed, but you may want to do it just to be on the safe side. It just tell the N900 to boot up into flash mode.
Aniello
Because I DID and it still does not work.
So before telling me that its my own fault you need to tell me which file there could possibly be which is not set to factory default by my actions.
Cheers, WD