Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 3 days, 12 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 4 days, 15 hrs ago - more...
|
2011-04-07
, 12:17
|
|
Posts: 1,746 |
Thanked: 1,832 times |
Joined on Dec 2010
|
#12
|
am blaming windows 7 for this. get a linux live cd and use that instead
 |
|
2011-04-07
, 15:36
|
|
Posts: 422 |
Thanked: 320 times |
Joined on Oct 2009
@ Israel
|
#13
|
Originally Posted by m4r0v3r
Then don't
am blaming windows 7 for this. get a linux live cd and use that instead
I just tried reflashing via Kubuntu - still, got the exact same result.
I even tried disabling watchdog, but it didn't help either (yea, I know, it was a long shot
)...
__________________
As long as people will accept crap, it will be financially profitable to dispense it...
As long as people will accept crap, it will be financially profitable to dispense it...
 |
|
2011-04-07
, 16:23
|
|
Posts: 191 |
Thanked: 46 times |
Joined on Jun 2010
@ NanJing China
|
#14
|
Have you ever dropped it off or sth like that ? 
I broke my N900 too and it just appeared like what you described here. So if you want to have a try . That's here: Take your machine apart completely and put a piece of soft paper on the HDD. And also some helps in this url: talk.maemo.org/showthread.php?t=71089
I broke my N900 too and it just appeared like what you described here. So if you want to have a try . That's here: Take your machine apart completely and put a piece of soft paper on the HDD. And also some helps in this url: talk.maemo.org/showthread.php?t=71089
|
|
2011-04-07
, 16:46
|
|
Posts: 422 |
Thanked: 320 times |
Joined on Oct 2009
@ Israel
|
#15
|
Didn't drop it, well not as far as I remember... This problem just appeared by itself... A day before, the device was rebooted successfully when I had to replace its battery...
Originally Posted by pursueky
What? why?
Take your machine apart completely and put a piece of soft paper on the HDD.
__________________
As long as people will accept crap, it will be financially profitable to dispense it...
As long as people will accept crap, it will be financially profitable to dispense it...
|
|
2011-04-07
, 17:15
|
|
Posts: 191 |
Thanked: 46 times |
Joined on Jun 2010
@ NanJing China
|
#16
|
Originally Posted by efekt
in my issue, the HDD loose.....
Didn't drop it, well not as far as I remember... This problem just appeared by itself... A day before, the device was rebooted successfully when I had to replace its battery...
What? why?
|
|
2011-04-07
, 18:57
|
|
Posts: 422 |
Thanked: 320 times |
Joined on Oct 2009
@ Israel
|
#17
|
Nope, nothing was loose in my device. I opened it and everything was intact...
__________________
As long as people will accept crap, it will be financially profitable to dispense it...
As long as people will accept crap, it will be financially profitable to dispense it...
 |
|
2011-04-07
, 21:09
|
|
Posts: 2,473 |
Thanked: 12,265 times |
Joined on Oct 2009
@ Jerusalem, PS/IL
|
#18
|
Flash the COMBINED image without -R, then flash the eMMC image.
 |
|
2011-04-07
, 21:20
|
|
Posts: 889 |
Thanked: 2,087 times |
Joined on Sep 2010
@ Manchester
|
#19
|
efekt I think you've missed a bit on the wiki about flashing the emmc. You need to remove the battery once the emmc has been flashed, presumably because the n900 is on at some level.
Flashing the eMMC in the N900
Image:Ambox_notice.png
When flashing the eMMC content, the safe way is flash the eMMC/VANILLA image first, then remove battery for a moment, and then flash the FIASCO/Rootfs image. Do not boot up the device between the two i.e do NOT use the -R parameter at the end! Rationale: on accidental booting in between the 2 flash processes, the sequence formerly suggested (rootfs first) will result in a broken system. The sequence "eMMC first, then rootfs" is checked back with Nokia affiliates and is proven to work. The former advice on tablets-dev.nokia.com was not based on any facts for the recent eMMC VANILLA image. It's fixed now and in line with this wiki
|
|
2011-04-07
, 21:42
|
|
Posts: 889 |
Thanked: 2,087 times |
Joined on Sep 2010
@ Manchester
|
#20
|
Apologies, I've misread what you've said, you've already done this.
You see, this is what happens if I run the flasher while the device is connected:
1. I execute:
flasher v2.5.2 (Sep 24 2009) Image 'mmc', size 255947 kB Version RX-51_2009SE_10.2010.13-2.VANILLA USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0105. Found device RX-51, hardware revision 2101 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0 Booting device into flash mode.1. The device suddenly starts up again - only showing the 5 running dots.
2. The device reconnects to the PC.
3. The running dots freezes.
4. The flasher is now able to recognize the device, if flasher is started. flashing succeeded:
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2. VANILLA_PR_EMMC_MR0_ARM.bin -f flasher v2.5.2 (Sep 24 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 bus-0, device address \\.\libusb0-0001--0x0421-0x01c8. Raw data transfer EP found at EP2. Using flashing protocol Mk II. Image(s) flashed successfully in 26.668 s (9597 kB/s)!If it matters for any reason - I'm using Windows 7 64bit and flashing through the Windows XP mode. It used to work just fine (though now it isn't
As long as people will accept crap, it will be financially profitable to dispense it...
Last edited by efekt; 2011-04-07 at 11:52.