Active Topics

 


Page 3 of 4 12 3 4
Reply
Thread Tools
J4ZZ is offline J4ZZ
2012-04-24 , 00:37
Posts: 539 | Thanked: 518 times | Joined on May 2010 @ nanaurbusiness
#21
Could it be, that you experiencing the same issue as this member?
Broken eMMC
Can you please boot up and post the output of xterminal:
Code:
sudo gainroot
sfdisk -l /dev/mmcblk0
Regards,

J4ZZ
 
ijAcK is offline ijAcK
2012-04-24 , 09:19
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#22
Originally Posted by J4ZZ View Post
Could it be, that you experiencing the same issue as this member?
Broken eMMC
Can you please boot up and post the output of xterminal:
Code:
sudo gainroot
sfdisk -l /dev/mmcblk0
Regards,

J4ZZ
Here it is JAZZ

BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ sudo gainroot
Root shell enabled


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # sfdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 1 884864 884864 28315648 c W95 FAT32 (LBA)
/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux
/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris
/dev/mmcblk0p4 0 - 0 0 0 Empty
/home/user #
 
ijAcK is offline ijAcK
2012-04-24 , 09:42
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#23
Please help me out....
 
ijAcK is offline ijAcK
2012-04-24 , 14:11
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#24
Still the same.
Now I am trying to run meego on it. Is everything working with Meego on N900.
 
ijAcK is offline ijAcK
2012-04-24 , 15:37
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#25
Ok I will try installing on SD card first.
 
J4ZZ is offline J4ZZ
2012-04-24 , 20:07
Posts: 539 | Thanked: 518 times | Joined on May 2010 @ nanaurbusiness
#26
Btw. have you read and tried all this??? And please always use a full battery and no usb hubs. (try also leaving battery out for a few hours, then start again)

From the wiki
Note that flashing eMMC will delete the /opt directory, so you *always* need to reflash your rootfs (the COMBINED image) after - or same time as - flashing eMMC (VANILLA img)
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!

Also see troubleshooting section, bullet 6:"If you cannot establish..."

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 as long as your rootfs still is somewhat functional. Note however that eMMC flashing will fail when your rootfs is completely messed up, the recommended flash sequence then is rootfs, eMMC, rootfs *again*.
For users familiar with flashing and interested in a smooth fast process: you can flash combined first, and then *immediately* after that - without one 10th of a second of booting - directly continue with flashing the vanilla. The other way round doesn't work due to a bug in NOLO - so after flashing vanilla you need to remove battery to recover

Cheers,

J4ZZ
 
ijAcK is offline ijAcK
2012-04-24 , 23:22
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#27
Hi J4ZZ

I have exactly the same sequence. But no joy... As you can see here.. I did remove the battery after flashing vanilla without rebooting.

E:\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_20.2010.36-2.003_PR_003
Booting device into flash mode.
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
1c8.
Raw data transfer EP found at EP2.
Image(s) flashed successfully in 35.718 s (7165 kB/s)!

E:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2.
003_PR_COMBINED_003_ARM.bin -f
flasher v2.5.2 (Sep 24 2009)

SW version in image: RX-51_2009SE_20.2010.36-2.003_PR_003
Image 'kernel', size 1705 kB
Version 2.6.28-20103103+0m5
Image 'rootfs', size 185856 kB
Version RX-51_2009SE_20.2010.36-2.003_PR_003
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.
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_20.2010.36-2.003_PR_003
Sending xloader image (14 kB)...
100% (14 of 0 kB, avg. 14 kB/s)
Sending secondary image (106 kB)...
100% (106 of 0 kB, avg. 106 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 0 kB, avg. 79 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 0 kB, avg. 507 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 0 kB, avg. 5826 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 0 kB, avg. 1705 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185856 kB)...
100% (185856 of 0 kB, avg. 185856 kB/s)
Finishing flashing... done
CMT flashed successfully

E:\Program Files\maemo\flasher-3.5>



Any idea.
Thanks for your effort in helping me.
Last edited by ijAcK; 2012-04-24 at 23:36.
 
J4ZZ is offline J4ZZ
2012-04-25 , 00:10
Posts: 539 | Thanked: 518 times | Joined on May 2010 @ nanaurbusiness
#28
Hmmm, this is really strange mate...

I'm starting to think that you probably need another firmware.
So do you know if it probalby needs another firmware variant?
like:
Maemo 5 USA release for Nokia N900
Maemo 5 Middle East and North Africa release for Nokia N900
Maemo 5 India release for Nokia N900
Maemo 5 UK release for Nokia N900

Or another idea would be trying another simcard, or ask your provider for a new one.

Last thing that comes to my mind is:
do you get the loading animation? the dots? If so how patient have you been? Because the very first boot after flashing could at least take a few (minutes) seconds...

Sorry, for not being able to help you more...

Regards,

J4ZZ
Last edited by J4ZZ; 2012-04-25 at 00:12.
 
ijAcK is offline ijAcK
2012-04-25 , 06:51
Posts: 79 | Thanked: 27 times | Joined on Apr 2012 @ India
#29
Originally Posted by j4zz
J4ZZ Hmmm, this is really strange mate..
Yes this is strange
I'm starting to think that you probably need another firmware.
So do you know if it probalby needs another firmware variant?
Yeah I have already tried
the following..
1. Maemo 5 Global
2. Maemo 5 Middle East and North Africa release for Nokia N900
3. Maemo 5 India release for Nokia N900

I haven't tried USA or UK variant though.

do you get the loading animation? the dots? If so how patient have you been? Because the very first boot after flashing could at least take a few (minutes) seconds...
If I re-flash with enable R&D mode and pull the battery at Erasing CMT: 66% the animation dots shows for about 2 minutes and then boot up with the Nokia Handshake with an error code "All telephony functions, including emergency calls, are disable due to communication error. to recover, you might have to reboot the device." In this mode sims is not working, charging is not working and no wifi.

If I re-flashed with disable R&D mode the Animation dots appears for about 20 seconds and turn it off.


Sorry, for not being able to help you more...
That's fine
Last edited by ijAcK; 2012-04-25 at 09:13.
 
evan is offline evan
2012-04-25 , 11:35
Posts: 136 | Thanked: 115 times | Joined on Jul 2010 @ Greece
#30
Sorry to see you are still in the same situation.
I am not certain it's a firmware downgrade problem as I suggested before, but the "telephony functions disabled" message does show up in those situations.
If you would care to try with the firmware I suggested before the direct link from nokia navifirm servers is this
http://nds2.fds-fire.nokia.com/fdp/i...ED_MR0_ARM.bin
 
Reply
Page 3 of 4 12 3 4

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 20:09.

Contact Us - Home - Archive - Top