Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 1 day, 9 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 3 days, 6 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 4 days, 2 hrs ago - more...
|
2010-08-04
, 21:40
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Mar 2010
|
#22
|
Managed to finally do it. It seems Windows 7 was the key. All this time I was trying to do it on an Windows XP box but today I did it from Windows 7 and it worked.
|
|
2010-08-16
, 18:39
|
|
Posts: 4 |
Thanked: 0 times |
Joined on Jul 2010
@ NSW, Australia
|
#23
|
I've tried everything I can find in this thread and others to flash the eMMC but it keeps getting stuck after trying to reboot in flashing mode (even though it already was in flashing mode):
I've held down the 'u' from near the end of CMT flash until after running the eMMC flash (it still rebooted into the OS)
I've tried pulling the battery out and going back into update mode (it still picks it up in PC suite mode, even without PC suite installed!)
I tried pulling the battery out again (even when the computer detected the phone in update mode the flasher just sat there without detecting the phone).
I tried it with digital driver signing disabled on Vista x86, you never know
(same results as before)
I tried starting it, then connecting the device (still said it needed to reboot into flashing mode and loaded the OS)
I tried with and without PC Suite (didn't make a difference to my results)
I tried all of the above using different USB ports on all 3 OS's I used.
I have tried all of the above on Vista x86 and XP Mode virtual machine, getting the same results on both. As a last ditch effort I tried Win7 x64 and as expected the flasher didn't even pick it up for a firmware flash (which I've been doing before attempting eMMC, as the guide says to do). I tried doing a firmware flash on the virtual machine, removing the battery and then trying eMMC on the win7 x64, which got me nowhere as expected
Does anyone have any suggestions that might help?
On a weird note I thought that flashing rootfs/kernal was supposed to reset the device to default? Cause mine has kept calender, contacts, APN's, bookmarks, contacts, conversations, etc. It did remove all the apps however. It said it was successful. Log is below.
firmware flash:
Attempt @ eMMC flash:
Last edited by Dragon_Orb; 2010-08-16 at 18:45.
I've held down the 'u' from near the end of CMT flash until after running the eMMC flash (it still rebooted into the OS)
I've tried pulling the battery out and going back into update mode (it still picks it up in PC suite mode, even without PC suite installed!)
I tried pulling the battery out again (even when the computer detected the phone in update mode the flasher just sat there without detecting the phone).
I tried it with digital driver signing disabled on Vista x86, you never know
(same results as before)I tried starting it, then connecting the device (still said it needed to reboot into flashing mode and loaded the OS)
I tried with and without PC Suite (didn't make a difference to my results)
I tried all of the above using different USB ports on all 3 OS's I used.
I have tried all of the above on Vista x86 and XP Mode virtual machine, getting the same results on both. As a last ditch effort I tried Win7 x64 and as expected the flasher didn't even pick it up for a firmware flash (which I've been doing before attempting eMMC, as the guide says to do). I tried doing a firmware flash on the virtual machine, removing the battery and then trying eMMC on the win7 x64, which got me nowhere as expected
Does anyone have any suggestions that might help?
On a weird note I thought that flashing rootfs/kernal was supposed to reset the device to default? Cause mine has kept calender, contacts, APN's, bookmarks, contacts, conversations, etc. It did remove all the apps however. It said it was successful. Log is below.
firmware flash:
Code:
C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.19-1_
PR_COMBINED_MR0_ARM.bin -f
flasher v2.5.2 (Sep 24 2009)
SW version in image: RX-51_2009SE_10.2010.19-1_PR_MR0
Image 'kernel', size 1705 kB
Version 2.6.28-20101501+0m5
Image 'rootfs', size 173568 kB
Version RX-51_2009SE_10.2010.19-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 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+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.8+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.8+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.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+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.8+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.8+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.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_10.2010.19-1_PR_MR0
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 14500 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 7125 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 79500 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 33841 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 26727 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 21860 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (173568 kB)...
100% (173568 of 173568 kB, avg. 15583 kB/s)
Finishing flashing... done
CMT flashed successfully
C:\Program Files\maemo\flasher-3.5>
Code:
C:\Program Files\maemo\flasher-3.5>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-0x0
105.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_10.2010.19-1_PR_MR0
Booting device into flash mode.
Suitable USB device not found, waiting.
Last edited by Dragon_Orb; 2010-08-16 at 18:45.
|
|
2010-08-16
, 20:18
|
|
Posts: 3 |
Thanked: 0 times |
Joined on Aug 2010
|
#24
|
I have exactly same problem, can nobody help here??
I have found elsewhere that Linux may help, but is it really?
http://talk.maemo.org/showthread.php?t=49148&page=4
Desperated...
I have found elsewhere that Linux may help, but is it really?
http://talk.maemo.org/showthread.php?t=49148&page=4
Desperated...
|
|
2010-08-16
, 20:31
|
|
Posts: 374 |
Thanked: 75 times |
Joined on Nov 2009
@ Hungary
|
#25
|
After FW update, just wait until 4 points animation stops on N900.
At this point you can start to flash the EMMC part!
)
At this point you can start to flash the EMMC part!
)
|
|
2010-08-16
, 20:43
|
|
Posts: 131 |
Thanked: 78 times |
Joined on May 2010
|
#26
|
I never could flash eMMC via XP Mode VM.
W7 x86 worked just fine. I never tried it via Vista.
W7 x86 worked just fine. I never tried it via Vista.
|
|
2010-08-16
, 20:47
|
|
Posts: 3 |
Thanked: 0 times |
Joined on Aug 2010
|
#27
|
Originally Posted by taril
After FW update, just wait until 4 points animation stops on N900.
At this point you can start to flash the EMMC part!
Problem is that after CMT flashed successfully nothing happens, just stuck with the yellow light on as it was. Until I unplug it, then I have reboot and the animation for 1 second and black screen again. But it wont find the device for eMMC flash.
I am doing it with XP, do I really need Win 7 32 bit to do it?
|
|
2010-09-16
, 02:29
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Sep 2010
|
#28
|
the eMMC flash freezing saga continues...
Got a new N900 from amazon - worked well for 4 days, though battery was weaker than expected. Installed applications, adapted all my contacts transferred from my (recently stolen) N95... and then - the black beauty froze and couldn't reboot. On the recommendation of a more experienced user, I flashed the phone - and it woke up again (though I lost all my adapted contacts)!
But ever since - application memory is full, internal errors happen daily... I even had to uninstall some of the very few applications to be able to add some new contacts - because they strangely save in the application memory (or I don't understand where).
I studied all possible solutions. eMMC flash though did exactly the same as described above - it freezes - and my memory remains full (although almost no applications installed).
I literally tried all the advice I could read - I even booted ubuntu USB - and tried there - but not knowing where the maemo flasher installed in ubuntu - I used a nice script published on nokia.com forum - which was apparently helpful to everybody but me. Because even with ubuntu - eMMC freezes.
I didn't restart between OS and eMMC flashing, I took out battery hundreds of times, I tried to clean N900 as root (I'm really not an IT - but I learn fast). NOTHING HELPED. Btw - my comp runs Vista - I didn't chose it - it was the only available option to me at that time (and Ubuntu, however beautiful it is, didn't work any better).
I just want to free the bloody full application memory. Anybody got any new clever idea? Thank you in advance...
Got a new N900 from amazon - worked well for 4 days, though battery was weaker than expected. Installed applications, adapted all my contacts transferred from my (recently stolen) N95... and then - the black beauty froze and couldn't reboot. On the recommendation of a more experienced user, I flashed the phone - and it woke up again (though I lost all my adapted contacts)!
But ever since - application memory is full, internal errors happen daily... I even had to uninstall some of the very few applications to be able to add some new contacts - because they strangely save in the application memory (or I don't understand where).
I studied all possible solutions. eMMC flash though did exactly the same as described above - it freezes - and my memory remains full (although almost no applications installed).
I literally tried all the advice I could read - I even booted ubuntu USB - and tried there - but not knowing where the maemo flasher installed in ubuntu - I used a nice script published on nokia.com forum - which was apparently helpful to everybody but me. Because even with ubuntu - eMMC freezes.
I didn't restart between OS and eMMC flashing, I took out battery hundreds of times, I tried to clean N900 as root (I'm really not an IT - but I learn fast). NOTHING HELPED. Btw - my comp runs Vista - I didn't chose it - it was the only available option to me at that time (and Ubuntu, however beautiful it is, didn't work any better).
I just want to free the bloody full application memory. Anybody got any new clever idea? Thank you in advance...
|
|
2010-09-16
, 17:51
|
|
Posts: 3 |
Thanked: 0 times |
Joined on Aug 2010
|
#29
|
It's really stupid but getting it done on Win 7 32bit was the only way for me that worked so far.
|
|
2010-10-14
, 23:54
|
|
Posts: 56 |
Thanked: 26 times |
Joined on Aug 2010
|
#30
|
After fighting for this problem for a few hours this afternoon, I successfully solved it and have both PR 1.2 and the vanilla eMMC image flashed.
During fighting with it, behavior between the N900 and my PC running stock Slackware 13.1 was leading me to think that the problem was on the PC rather than the tablet, mainly signs of racing between different device drivers trying to grab the N900's USB port first.
You should be able to modify this for most any Linux distro and, hopefully for OS-X as well; winblows lusers are on their own, but I'm sure there's a similar work-around there somewhere as well.
In the steps here, the "cdc_phonet" driver is a thorn. You can blacklist it if you'll be doing a lot of flashing, but if this is a one-time thing just deal with it. (This driver is the Nokia CDC modem driver that allows you to tether.)
Here are the steps I used:
1. You need kill X--particularly your window manager and its automounter--and use a regular non-graphical virtual terminal as root. In my case, I logged out of xfce and my user account and then logged back in as root (or as root in another VT).
2. Attach the tablet in flash mode as usual.
3. "rmmod cdc_phonet" (equivalent to "modprobe -r cdc_phonet" in the wiki but less to type)
4. Try to flash the the firmware (*NOT* the eMMC) first; it will probably fail. Don't forget to leave off the "-R" at the end so the tablet won't reboot (*VERY IMPORTANT*--the wiki says this but not enough emphasis is placed on it; see the bottom comments)
5. "rmmod cdc_phonet" again
6. Flash again if it didn't succeed before: this time it will.
7. Flash the eMMC; "rmmod cdc_phonet" again if necessary. Don't forget adding "-R" here at the end this time.
8. If it succeeded, flasher will tell you it did and the tablet will immediately reboot; if not, the tablet will be stuck with the dim screen.
When I figured this out, I tried to flash eMMC only; the N900 had been rebooted in between this and the last firmware flash. This caused some ugly and scary problems on the screen and constant rebooting, only fixed when I removed the battery. Re-flashing both images in order, as per the wiki instructions, left me with a clean, working device, confirmed by looking at the videos and images in the PC with the N900 in the mass storage mode (those videos and images were corrupt with the blown eMMC flash).
Here is what I think is going on: a race between flasher, xfce's HAL-driven automounter (probably trying to mount it as a SCSI storage device), and the kernel thinking it's a CDC modem; the kernel obviously wins and flasher seems to have the lowest priority of the three. Nicing up flasher may help, but I haven't tried it. I think this is confirmed in that this only hangs with flashing the eMMC, which is accessible in normal (non-flashing) mode as mass storage, but not when flashing the firmware's 256MB NAND. Watching what happens elsewhere in the host's kernel and userspace as flasher tries to upload to the eMMC would absolutely confirm this, but I don't think it's necessary at this point.
Hopefully some people with more distro-specific knowledge than me can come up with easier ways to implement this work-around that is distro--or even OS--independent.
Mike
Last edited by storkus; 2010-10-15 at 00:12. Reason: Added additional automounter thoughts
During fighting with it, behavior between the N900 and my PC running stock Slackware 13.1 was leading me to think that the problem was on the PC rather than the tablet, mainly signs of racing between different device drivers trying to grab the N900's USB port first.
You should be able to modify this for most any Linux distro and, hopefully for OS-X as well; winblows lusers are on their own, but I'm sure there's a similar work-around there somewhere as well.
In the steps here, the "cdc_phonet" driver is a thorn. You can blacklist it if you'll be doing a lot of flashing, but if this is a one-time thing just deal with it. (This driver is the Nokia CDC modem driver that allows you to tether.)
Here are the steps I used:
1. You need kill X--particularly your window manager and its automounter--and use a regular non-graphical virtual terminal as root. In my case, I logged out of xfce and my user account and then logged back in as root (or as root in another VT).
2. Attach the tablet in flash mode as usual.
3. "rmmod cdc_phonet" (equivalent to "modprobe -r cdc_phonet" in the wiki but less to type)
4. Try to flash the the firmware (*NOT* the eMMC) first; it will probably fail. Don't forget to leave off the "-R" at the end so the tablet won't reboot (*VERY IMPORTANT*--the wiki says this but not enough emphasis is placed on it; see the bottom comments)
5. "rmmod cdc_phonet" again
6. Flash again if it didn't succeed before: this time it will.
7. Flash the eMMC; "rmmod cdc_phonet" again if necessary. Don't forget adding "-R" here at the end this time.
8. If it succeeded, flasher will tell you it did and the tablet will immediately reboot; if not, the tablet will be stuck with the dim screen.
When I figured this out, I tried to flash eMMC only; the N900 had been rebooted in between this and the last firmware flash. This caused some ugly and scary problems on the screen and constant rebooting, only fixed when I removed the battery. Re-flashing both images in order, as per the wiki instructions, left me with a clean, working device, confirmed by looking at the videos and images in the PC with the N900 in the mass storage mode (those videos and images were corrupt with the blown eMMC flash).
Here is what I think is going on: a race between flasher, xfce's HAL-driven automounter (probably trying to mount it as a SCSI storage device), and the kernel thinking it's a CDC modem; the kernel obviously wins and flasher seems to have the lowest priority of the three. Nicing up flasher may help, but I haven't tried it. I think this is confirmed in that this only hangs with flashing the eMMC, which is accessible in normal (non-flashing) mode as mass storage, but not when flashing the firmware's 256MB NAND. Watching what happens elsewhere in the host's kernel and userspace as flasher tries to upload to the eMMC would absolutely confirm this, but I don't think it's necessary at this point.
Hopefully some people with more distro-specific knowledge than me can come up with easier ways to implement this work-around that is distro--or even OS--independent.
Mike
Last edited by storkus; 2010-10-15 at 00:12. Reason: Added additional automounter thoughts
| The Following User Says Thank You to storkus For This Useful Post: | ||
I decided to do a hard reset following the instructions here to fix the emmc drive but I get stuck when flashing the emmc. It just says "Suitable USB device not found, waiting.". I have waited for upto an hour but it doesn't progress any further. Trying all combinations of suggestions on this thread of booting the device and holding down "u" while plugging in cable after the firmware flash but still no luck.
Can anyone please suggest anything else? Is there a way to re-format the emmc device without actually re-flashing it?