Reply
Thread Tools
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#21
Installed Nokia Suite and tried connecting N900 to it via USB cable....after I few tries, I did see on PC that it recognized that a 'Nokia device' was attached, but doesn't see it as a N900....

N900 display lights up and then soon I see the blinking little white dots on the black background again....but doesn't boot up....

So, think it's back to reflasing Emmc and rootfs again.....
__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800
 
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#22
Tried flashing Emmc again....but as the previous time, I get the error message that device or resource busy.....

I've followed the wiki instructions carefully, including the command to deal with this error message, but to no avail.....

Any other suggestions???....

Thanks!

__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800
 
sifo's Avatar
Posts: 1,359 | Thanked: 1,292 times | Joined on Oct 2011 @ Tartus.Syria
#23
i saw in other threads you were booting somthing with u-boot right ? maybe it is your boot loader i dont know but let cold flash the last thing you do
Good luck

./sifo
__________________
[ N900-Crack ] [ The Purge ] [ New Smiles ] [ New icons ] [ ? ]
" Hey ! I've just met you and this is crazy, so install cssu maybe ? "
Please help out keeping Maemo.org alive, and consider donating.
https://www.facebook.com/ZoRk7
 

The Following User Says Thank You to sifo For This Useful Post:
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#24
Originally Posted by sifo View Post
i saw in other threads you were booting somthing with u-boot right ? maybe it is your boot loader i dont know but let cold flash the last thing you do
Good luck

./sifo
Thanks for your help!

Followed those instructions, but at last step, I still get the error message that 'device or resource busy.....'.....

__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800
 
sifo's Avatar
Posts: 1,359 | Thanked: 1,292 times | Joined on Oct 2011 @ Tartus.Syria
#25
did you tried to flash emmc then FIASCO image then emmc ? or flash to pr-1.2 and if you able to access to OS then you can reflash to pr-1.3 if you want.
i dont knwo if this got any meaning or will work but i hope

./sifo
__________________
[ N900-Crack ] [ The Purge ] [ New Smiles ] [ New icons ] [ ? ]
" Hey ! I've just met you and this is crazy, so install cssu maybe ? "
Please help out keeping Maemo.org alive, and consider donating.
https://www.facebook.com/ZoRk7
 

The Following User Says Thank You to sifo For This Useful Post:
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#26
Originally Posted by sifo View Post
did you tried to flash emmc then FIASCO image then emmc ? or flash to pr-1.2 and if you able to access to OS then you can reflash to pr-1.3 if you want.
i dont knwo if this got any meaning or will work but i hope

./sifo
Thanks for your help, sifo....appreciate it!

As for chronology, if you read through my posts, it describes the process I've gone through regarding flashing attempts....

In summary, I did the following as I recall:

1. Flashed FIASCO (rootfs...) image, but still only boots up to the blinking white dots part....

2. Flashed emmc image, got the 'device busy' message, and did command regarding this, but no go, still only boots up to the blinking white dots part....

3. Flashed FIASCO (rootfs...) image using the 'Cold Flashing' method you referred me to, but got the 'device busy' message, and still only boots up to the blinking white dots part....

So, it seems my key problem now, is how to deal with the 'device busy' issue, so, that the flashing process can take place properly.....

__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800
 

The Following User Says Thank You to ArchiMark For This Useful Post:
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#27
Originally Posted by ArchiMark View Post
Thanks for your help, sifo....appreciate it!

As for chronology, if you read through my posts, it describes the process I've gone through regarding flashing attempts....

In summary, I did the following as I recall:

1. Flashed FIASCO (rootfs...) image, but still only boots up to the blinking white dots part....

2. Flashed emmc image, got the 'device busy' message, and did command regarding this, but no go, still only boots up to the blinking white dots part....

3. Flashed FIASCO (rootfs...) image using the 'Cold Flashing' method you referred me to, but got the 'device busy' message, and still only boots up to the blinking white dots part....

So, it seems my key problem now, is how to deal with the 'device busy' issue, so, that the flashing process can take place properly.....

take out the battery for 12 to 24 hrs.
(if you already took it out for a few hrs, this is probably not going to change anything, though)

MAKE SURE BATTERY IS COMPLETELY CHARGED BEFORE DOING THIS
when putting battery back in, start right away with a cold flash
__________________
information is a necessary though no sufficient condition to rationality...
 

The Following 2 Users Say Thank You to misterc For This Useful Post:
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#28
Originally Posted by misterc View Post
take out the battery for 12 to 24 hrs.
(if you already took it out for a few hrs, this is probably not going to change anything, though)

MAKE SURE BATTERY IS COMPLETELY CHARGED BEFORE DOING THIS
when putting battery back in, start right away with a cold flash
Thanks, misterc....that helped!....

Now, I can connect with flashing process....

I did cold flash....

Then flashed emmc...went OK....

Then flashed rootfs....went OK partially....

Code:
Users-MacBook:nokia marks$ flasher-3.5 -F RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin -f -R
flasher v2.5.2 (Nov 25 2009)

SW version in image: RX-51_2009SE_20.2010.36-2.002_PR_002
Image 'kernel', size 1705 kB
	Version 2.6.28-20103103+0m5
Image 'rootfs', size 185856 kB
	Version RX-51_2009SE_20.2010.36-2.002_PR_002
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, 2113, 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, 2113, 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, 2113, 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, 2210, 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, 2210, 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, 2210, 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.
USB device found found at bus 005, device address 007-0421-0105-02-00.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.002_PR_002
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 805 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 11875 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 4184 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 14930 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 20883 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
 82% (1408 of 1705 kB, 15644 kB/s)
Write failed after 1441792 bytes
usb_bulk_write: Operation timed out
Users-MacBook:nokia marks$
What to do now?

Thanks!
__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800
 
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#29
Originally Posted by ArchiMark View Post
Thanks, misterc....that helped!....

[,,,]
glad to be able to help, but...
afraid you got a serious problem here...
Originally Posted by ArchiMark View Post
Code:
[...]
Sending kernel image (1705 kB)...
 82% (1408 of 1705 kB, 15644 kB/s)
Write failed after 1441792 bytes 
usb_bulk_write: Operation timed out
Users-MacBook:nokia marks$ 
What to do now?

Thanks!
looks like your EMMC is corrupt
if your N900 is still under warranty, NOKIA Care Center seems the only option to me
__________________
information is a necessary though no sufficient condition to rationality...
 

The Following User Says Thank You to misterc For This Useful Post:
ArchiMark's Avatar
Posts: 414 | Thanked: 109 times | Joined on Mar 2007 @ Silicon Valley
#30
Originally Posted by misterc View Post
glad to be able to help, but...
afraid you got a serious problem here...


looks like your EMMC is corrupt
if your N900 is still under warranty, NOKIA Care Center seems the only option to me
Thanks for your input....but I don't understand why you think problem is with EMMC (as I noted that I was able to flash the EMMC successfully after doing the cold flashing) ?

Here's what I saw in terminal while flashing EMMC:

Code:
Users-MacBook:nokia marks$ flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f
flasher v2.5.2 (Nov 25 2009)

Image 'mmc', size 255947 kB
	Version RX-51_2009SE_10.2010.13-2.VANILLA
Suitable USB device not found, waiting.
USB device found found at bus 005, device address 007-0421-0105-02-00.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.002_PR_002
Booting device into flash mode.
Suitable USB device not found, waiting.
USB device found found at bus 005, device address 007-0421-01c8-02-00.
Raw data transfer EP found at EP2.
Image(s) flashed successfully in 39.245 s (6521 kB/s)!
The error message you refer I got while flashing the rootsf image after flashing EMMC....
__________________
Mark
Silicon Valley Digerati

Nokia N900
Previous: Nokia N810 & N800

Last edited by ArchiMark; 2012-06-03 at 19:25.
 
Reply


 
Forum Jump


All times are GMT. The time now is 16:18.