Reply
Thread Tools
sujanshrestha308 is offline sujanshrestha308
2014-07-21 , 17:14
Posts: 6 | Thanked: 0 times | Joined on Jul 2014
#1
I tried flashing my rootfs as per instructed in wiki.maemo.org/Updating_the_firmware
but i encountered the problem showing dis without any change for several minutes:
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
Suitable USB device not found, waiting.
.
Can any genius head help me sort out dis.Plz show ur kindness and concern to dis post and do favour me leaving a useful reply below.
Thanks..!!
Last edited by sujanshrestha308; 2014-07-21 at 17:17. Reason: Incomplete post
 
vincr is offline vincr
2014-07-21 , 18:27
Posts: 136 | Thanked: 68 times | Joined on Nov 2013 @ Streets of Avalon | Zwolle, the Netherlands
#2
Code:
Suitable USB device not found, waiting.

Sure you did it correct? Start flasher with correct flasher command, slide open your N900 and hold the u button pressed and then connect the usb cable which is connected to a 'main usb port' of your pc, not a hub or something. If fails again try an other usb cable.
 
sujanshrestha308 is offline sujanshrestha308
2014-07-22 , 00:19
Posts: 6 | Thanked: 0 times | Joined on Jul 2014
#3
Originally Posted by pichlo View Post
Eh?



Or maybe even with the correct flasher. I don't know what version is that, but the version that works with our N900s is 3.5.
I exactly followed the following procedure:
Installed the latest version of the Flasher i.e. v3.5
Downloaded the latest firmware (.bin) and saved it to %ProgramFiles%\maemo\flasher-3.5\
The battery was made full.
Switched off the device.
Opened the Command Prompt (Started Run) and typed cmd then pressed Enter.And typed dis.
cd "%ProgramFiles%\maemo\flasher-3.5"
I then Held the u key on the device keyboard and connected the USB cable at the same time.I Held the u key until a dim screen showing nokia logo with usb icon on top right corner appeared.
Then I typed the following command followed by hitting enter:
flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f

Then it showed above msg.Then nothing changed.My device wasnt flashed.If it was the problem with the usb cable,let me tell u dat it is the same usb cable i have been using to transfer data via pc in mass storage mode.Plz,consider my problem and suggest working reply.
 
sujanshrestha308 is offline sujanshrestha308
2014-07-22 , 00:27
Posts: 6 | Thanked: 0 times | Joined on Jul 2014
#4
Originally Posted by vincr View Post
Code:
Suitable USB device not found, waiting.

Sure you did it correct? Start flasher with correct flasher command, slide open your N900 and hold the u button pressed and then connect the usb cable which is connected to a 'main usb port' of your pc, not a hub or something. If fails again try an other usb cable.
"connect the usb cable which is connected to a 'main usb port' of your pc, not a hub or something."
I couldnt get dis.I connected the usb cable right in the front where we usually do,don't particularly know if its actually a main usb port or not.
I exactly followed the following procedure:
Installed the latest version of the Flasher i.e. v3.5
Downloaded the latest firmware (.bin) and saved it to %ProgramFiles%\maemo\flasher-3.5\
The battery was made full.
Switched off the device.
Opened the Command Prompt (Started Run) and typed cmd then pressed Enter.And typed dis.
cd "%ProgramFiles%\maemo\flasher-3.5"
I then Held the u key on the device keyboard and connected the USB cable at the same time.I Held the u key until a dim screen showing nokia logo with usb icon on top right corner appeared.
Then I typed the following command followed by hitting enter:
flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f
Then it showed above msg.Then nothing changed.My device wasnt flashed.If it was the problem with the usb cable,let me tell u dat it is the same usb cable i have been using to transfer data via pc in mass storage mode.Plz,consider my problem and suggest working reply.
 
pichlo's Avatar
pichlo is offline pichlo
2014-07-22 , 00:38
Posts: 6,445 | Thanked: 20,981 times | Joined on Sep 2012 @ UK
#5
Originally Posted by sujanshrestha308 View Post
"connect the usb cable which is connected to a 'main usb port' of your pc, not a hub or something."
I couldnt get dis.I connected the usb cable right in the front where we usually do,don't particularly know if its actually a main usb port or not.
"The main USB port" in this context just means the USB port on the PC itself. The clue is in the "not a hub" part.

Your procedure looks OK. I am still a bit confused with the "v2.5.2" bit, but I do not have a working setup right now to check what flasher 3.5 prints so I will let it pass for now.

One thing comes to mind. Until the last two posts I did not realize you were doing this in Windows. If you are using Windows 7 or newer and/or any 64-bit Windows, then you may need some special considerations. Look up one of about two dozen threads on the topic. None of the suggested solutions have ever worked for me though. The only thing that worked was booting a live, 32-bit Debian or Ubuntu CD and flashing from that.
 
sujanshrestha308 is offline sujanshrestha308
2014-07-22 , 00:48
Posts: 6 | Thanked: 0 times | Joined on Jul 2014
#6
Originally Posted by pichlo View Post
"The main USB port" in this context just means the USB port on the PC itself. The clue is in the "not a hub" part.

One thing comes to mind. Until the last two posts I did not realize you were doing this in Windows. If you are using Windows 7 or newer and/or any 64-bit Windows, then you may need some special considerations. Look up one of about two dozen threads on the topic. None of the suggested solutions have ever worked for me though. The only thing that worked was booting a live, 32-bit Debian or Ubuntu CD and flashing from that.
I am using Windows 7 32-bit OS.After my detailed and wide surf in the internet regarding updating the firmware, I came acrossed the fact that nothing wierd occurs with 32-bit Windows 7 unlike the case with 64-bit.
 
viento23 is offline viento23
2014-07-22 , 02:45
Posts: 119 | Thanked: 24 times | Joined on Jun 2012
#7
hii.. try to install the driver once again directly after showing "Suitable USB device not found, waiting." without unpluging the usb cable.
 
panjgoori's Avatar
panjgoori is offline panjgoori
2014-07-22 , 03:15
Posts: 1,236 | Thanked: 1,278 times | Joined on Aug 2011 @ Balochistan
#8
@pichlo Flasher 3.5 shows version 2.5.2 in CMD but its 3.5 in actual. Check this thread for a log of flasher 3.5 http://talk.maemo.org/showthread.php?t=82822

There must be a driver issue. Try to re-install drivers and check again.
__________________
N900 Firmware files with Flasher Linux+Windows
 

The Following 2 Users Say Thank You to panjgoori For This Useful Post:
Reply

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 15:57.

Contact Us - Home - Archive - Top