maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   N900 - Cannot Boot, but Flash VANILLA and FIASCO done (https://talk.maemo.org/showthread.php?t=90312)

Jackeye 2013-06-01 08:46
N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Hi all maemo-users,

I would like to ask for help. I'm "old-new" owner of n900. I bought one with SW problem and decided to repair it.

What's the problem?
After I charge battery externaly, put it to device, power on, only the NOKIA word shown, but cannot boot. I don't see Maemo loader (four or five points looping until the OS is loaded).

So, I start with downloading newest VANILLA and FIASCO. Install flasher-3.5 on Win 7 64 bit (with usblibs - PC see the N900 good - in Update Mode), also on Virtual Ubuntu 10. Firstly I try flash VANILLA, with no error it try to reboot after flashing it. I put the battery outside and back and continue flash FIASCO. Also it wrote no error, all done.

BUT! The problem with booting is still the same. Cannot see the Maemo Loader Looping Points. Only NOKIA is shown, after a few minutes it shut down.

I try the INITRD, can access the console mode (without display backlight) on N900 where I can select Repair Terminal, USB Network Mode (after selection it's PC Suite), Storage Mode and other.

I realy don't know which part is defective. What's the problem when the phone only word NOKIA show and than wont BOOT? What's the solution, please?

Many thanks to all who help me in any way!

Jackeye 2013-06-01 09:00
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
I tried cold flash, but only what I get is the message:

Code:
Using serial port usb
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
106.
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 34 30 07 57  13 02 01 00 12 15 01 f5
00 6f 97 59 c8 fd de 92  81 b6 51 57 a7 80 62 c5
31 b1 b7 14 15 01 87 3b  4d cd ca f5 44 4d 24 ec
b2 ac 95 53 88 41 4f ab  cd 66 15 09 01 f7 48 8f
28 a0 27 e5 b3
Sending 2nd image (zu bytes)... done.
Sending ping... usb_bulk_read: No error
failed.
Sending ping... usb_bulk_read: No error
timeout!
failed.
Sending ping... usb_bulk_read: No error
timeout!
failed.
Sending ping... usb_bulk_read: No error
timeout!
failed.

elros34 2013-06-01 09:08
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Maybe try to boot with enabled R&D mode. Next step is great tool rescueOS: dmesg.

Jackeye 2013-06-01 09:20
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
I tried cold flash with and without R&D mode, but wihout any change.

Please, can you tell me more about RescueOS ? I found image of this, and documentation, but autor wrote about some scripts, which I can't find on his website (http://206.253.166.96/N900/rescueOS/).

elros34 2013-06-01 09:31
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Scripts are in image.

Jackeye 2013-06-01 10:03
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Ok, I think so. But than I cannot understand, why when I use command
Code:
flasher-3.5 -k 2.6.37 -n initrd.img -l -b"rootdelay root=/dev/ram0
the bash show symbol ">" on the new line, and nothing happend. No output from running script, or nothing like error message. Only the > shown on new line.

elros34 2013-06-01 10:08
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
It's mistake in the documentation. It should be: flasher-3.5 -k 2.6.37 -n "correct name of rescue image" -l -b"rootdelay root=/dev/ram0"

lo9314 2013-06-01 10:31
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Sounds similar to the problems I had. If nothing else works try this as a last resort. http://talk.maemo.org/showthread.php?t=90236

Good luck!

Jackeye 2013-06-01 10:32
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Oh yes, mistake - but on my side, forgot the " on the end. Thanks for your time, man.

So, I boot RescueOS, use file script with mount-maemo-root.sh, but when I than write poweroff command, the maemo wouldn't boot, and the situation with Cold Flash is the same. Also I tried flash Vanilla and Fiasco, but nothing which made my n900 bootable Maemo OS.

elros34 2013-06-01 10:47
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Nothing has changed because you just mount/unmount maemo rootfs. You should check dmesg command.

Jackeye 2013-06-01 11:41
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
lo9314
Thank you for link, I will try after this my run work will have no success. Thanks!

elros34
If I run dmesg, it should save somewhere some log, don't it? Because I see only the last few lines, which can be displayed - no scrolling. But what I saw even without scrolling is massage:
Code:
i2c_omap i2c_omap.2: controller timed out
Unfortunately I cannot find this exactly means or how to repair this (if possible).

EDIT:
What lo9314 suggests doesn't function on my side. When try to use flasher, it cannot get n900 in update mode as suitable device and is still waiting.

Now I really don't know, what to do. Should I set N900 into storage mode and repatition eMMC? I definitely don't know, what part is bad, why cannot boot Maemo...Maybe that's the right time to offer half of kingdom for a solution!

lo9314 2013-06-01 12:27
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
If you can type in special characters you can redirect the output of dmesg to a file using this command:

Code:
dmesg > log.txt
The log.txt will be created in the directory you are in at the moment you execute the command. You'll somehow need to access the file of course afterwards and I'm not sure if this is possible. If there's no option to scroll like you said you can also try:

Code:
dmesg | more

Jackeye 2013-06-01 13:09
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Thanks, this works good -> I have log. Nano function good on this file, so I check it. Because I didn't find a way how to transfer it from N900 before battery drained, I re-write lines, where was not "Done", "Ok" or memory adress as postive result as this:

(without "positive" lines)

Code:
IRQ: Found an INTC at 0xfa200000 (revision 4.) with 96 interrupts
Total of 96 interrupts on 1 active controller

omap_hwmod: sr1_fck: missing clockdomain for sr1_fck
omap_hwmod: sr2_fck: missing clockdomain for sr2_fck

rotfd image is not intramfs (junk in compressed archive): looks like an initrd

onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400

Faild to add route TPA6130A2 Headphone Left->Headphone Jack

more than 100x is in log mentioned:
i2c_omap i2c_omap.2: controller timed out

Jackeye 2013-06-01 15:05
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
I have one new observation.

When I try to update Vanilla in Update mode, it find and refuese the device connection. - the USB symbol is shown, I press the Enter on keyboard with command on Terminal and symbol of USB on N900 display is gone.

So, cold flash it cannot do, because it cannot see the device. But Vanilla cannot do, because it refuse it. After 2 minutes the device (if is in R&D mode) change on the screen - some information about kernel, product, hw-build are added (green font) and flashing with Vanilla STARTS! And ends with success.

But, the problem is stil the same - cannot boot the device, only NOKIA is shown.

lo9314 2013-06-01 15:35
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Sorry, it's probably a dumb question, but you did press "u" while plugging in your N900, right? Otherwise I would try a different usb cable and a debian live cd. Since you can't even install the temporary nolo bootloader (which should always work) I'd try looking for the error elsewhere.

Jackeye 2013-06-01 16:28
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Yes, I always press "u" and check if it is in Update Mode. No question is dumb in these thread.

Ok, I will try the different cable. Debians I use are different, but the same situatuin everywhere (when need to Cold Flash, still "no suitable device").

In fact, I see the problem in something "third". The Vanilla and Fiasco can be done quite without problems. But reflashing these two doesn't help and the problem is like before - boot looping with no result, restart, boot, nothing, restart, boot, nothing....Moreover the Cold Flash telling "no suitable device" - on Windows, and also on Ubuntu. What's the difference, between Vanilla/Fiasco flash and Cold Flash using Fiasco bin file?

What next is important to boot OS, instead eMMC, kernel?

What could cause loop booting with no result to infinity?

elros34 2013-06-01 17:09
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Maybe try this:
flasher-3.5 --enable-rd-mode --set-rd-flags=no-lifeguard-reset --set-rd-flags=no-omap-wd --set-rd-flags=no-ext-wd
and flash latest image once again or/and flash fb kernel and watch logs:
flasher-3.5 -f -b -k zImage-2.6.28-omap1-fb

Jackeye 2013-06-01 17:23
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Ok. I tried this on Windows. I'm downloading image of Ubuntu, until now - if use linux - run from Virtual Box. Here's the result, no fault:


Code:
C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 --enable-rd-mode --set-rd-f
lags=no-lifeguard-reset --set-rd-flags=no-omap-wd --set-rd-flags=no-ext-wd
flasher v2.5.2 (Sep 24 2009)

USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.003_PR_003
The device is now in R&D mode

C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_20.2010.36-
2_PR_COMBINED_MR0_ARM.bin -f -R
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
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
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 14 kB, avg. 3625 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 13359 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 11357 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 8905 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 25223 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 21321 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185728 kB)...
100% (185728 of 185728 kB, avg. 13792 kB/s)
Finishing flashing... done
CMT flashed successfully

C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 -f -b -k zImage-2.6.28-omap
1-fb
flasher v2.5.2 (Sep 24 2009)

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 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Sending kernel image (1728 kB)...
100% (1728 of 1728 kB, avg. 27011 kB/s)
Flashing kernel... done.

C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 --disable-rd-mode
flasher v2.5.2 (Sep 24 2009)

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 2101
NOLO version 1.4.14
Version of 'sw-release': <no version>
The device is now in production mode

elros34 2013-06-01 17:26
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
please don't disable R&D mode. Now you have fb kernel. I know it's hard but did you see any errors on n900.

Jackeye 2013-06-01 17:30
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
So, the kernel don't start. After these three commands, N900 is still in R&D mode, and the NOKIA (with symbol of rd mode) is lighting.

EDIT:
fb kernel starts. The error messages I saw was something like before in RescueOS -
Code:
i2c_omap i2c_omap.2: controller timed out
Also I see the: tpa6130az - read (and than also write) failed

elros34 2013-06-01 18:03
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Flash u-boot and use Arch linux :) but seriously I do not know what to do next. Show your full dmesg log, maybe someone will help you.
Quote:
Originally Posted by Jackeye (Post 1348698)
i2c_omap i2c_omap.2: controller timed out
it's normal.

peterleinchen 2013-06-01 23:17
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
I would try that way:
disable all r&d flags (normal operation)
flash fiasco and omit the -R option (do not boot up)
then flash vanilla also without -R option
and once again flash fiasco (this time you may use -R but it is not needed, just detach usb)

If that does not help (of course there were no errors?), I assume some hw failure.

Jackeye 2013-06-02 09:14
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
So, what I find out (using not a virtual, but Live distribution of Ubuntu 10.10):


(1) I can do flasher-3.5 -i | so it seams, that booloader is OK. Also from Live Ubuntu I can do Cold flash with positive result (no error).
(2) I can flash FIASCO all-time with no error (kernel only, NOLO only, everything OK)


In R&D mode:
If I try to flash FIASCO (without -R) | is OK

Than I try to flash VANILLA (also no -R) | is WAITING FOR SUITABLE DEVICE for long time. No wainting helps. Flasher never catch it and is still waiting for SUITABLE DEVICE.

Than FIASCO (with, also without -R) | is OK



In classic (no R&D) mode:
If I try to flash FIASCO (without -R) | is OK

Than I try to flash VANILLA (also no -R) | is WAITING FOR SUITABLE DEVICE for long time, no wainting helps. Flasher never catch it and is still waiting for SUITABLE DEVICE.


Next informations:
If I write the command for flashing VANILLA, it is waiting for suitable device. Than connect N900 with pressed "U", flasher load informations and than the USB symbol on N900's display is missing.
If I than reconnect N900 with pressed "U", nothing happend - flasher is still in waiting mode.


What do you think, is it HW problem?

Jackeye 2013-06-02 09:18
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Try to flash VANILLA after FIASCO in non-R&D mode with these details:

Code:
root@ubuntu:/home/ubuntu/Stažené# flasher-3.5 --disable-rd-mode
flasher v2.5.2 (Oct 21 2009)

USB device found found at bus 001, device address 013.
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
The device is now in production mode
root@ubuntu:/home/ubuntu/Stažené# flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f
flasher v2.5.2 (Oct 21 2009)

Image 'mmc', size 255947 kB
        Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus 001, device address 013.
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.
Suitable USB device not found, waiting.

Also I see the problem in RescueOS with charging. When I start the charging script, it wrote some errors, that was not able to read last value. Voltage informations are all on 0 value. After a few tens of minutes N900 goes down (with battery drained). External charger charge battery to full, so it is ok.

Can it be connected with eMMC (VANILLA) flashing (status: "wating for suitable device") and means any HW problem?

peterleinchen 2013-06-02 11:04
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Quote:
Originally Posted by Jackeye (Post 1348881)
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

root@ubuntu:/home/ubuntu/Stažené# flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f
flasher v2.5.2 (Oct 21 2009)

Image 'mmc', size 255947 kB
Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus 001, device address 013.
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
[/CODE]
Possibly you tried a downgrade?
On device is newer version of fw than of the emmc image you try to flash.
Please fetch latest version from tabletsdev.maemo.org and try again with my method.
Or give us full output of all flashing commands.

Jackeye 2013-06-02 11:25
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Maybe I do a downgrade, but the files seems to be the the same - in device is RX-51_2009SE_10.2010.13-2.VANILLA and i try flash it with RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin.

Also it is the newest eMMC binary file which I can get on the website you post here. Do you know about newer eMMC bin, please?

peterleinchen 2013-06-02 19:20
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Okay, just to assure: you also have the fiasco 20.2010.36-2? And used that for flashing? In order of fiasco 36, then emmc 13 and again fiasco 36?

Could you provide output of these three flashes (each without reboot), please?

I am running out of ideas else. And yes the emmc image is latest, no newer available. Flashing emmc is no downgrade, but should match the fiasco, which is the case with above numbers.

karidushi 2013-06-03 07:40
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Quote:
Originally Posted by Jackeye (Post 1348653)
I have one new observation.

When I try to update Vanilla in Update mode, it find and refuese the device connection. - the USB symbol is shown, I press the Enter on keyboard with command on Terminal and symbol of USB on N900 display is gone.

So, cold flash it cannot do, because it cannot see the device. But Vanilla cannot do, because it refuse it. After 2 minutes the device (if is in R&D mode) change on the screen - some information about kernel, product, hw-build are added (green font) and flashing with Vanilla STARTS! And ends with success.

But, the problem is stil the same - cannot boot the device, only NOKIA is shown.

Hi Jackeye, I'm Tanzanian so my Endlish is not so good but even me I have the same problem no r&d mode in my bricked N900. I have tried to flash it but last in vain because cannot enter into r&d mode. may you help me please if you have succeeded?

elros34 2013-06-03 16:35
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Quote:
Originally Posted by Jackeye (Post 1348881)
Also I see the problem in RescueOS with charging. When I start the charging script, it wrote some errors, that was not able to read last value. Voltage informations are all on 0 value. After a few tens of minutes N900 goes down (with battery drained). External charger charge battery to full, so it is ok.
Try to charge on nemo mobile. Download image and write it to sd card
Code:
bzcat nemo-armv7hl-n900-mmcblk0p.raw.bz2 | dd bs=4096 | dd bs=4096 of=/dev/sdX
then download uboot and flash it to n900
Code:
./flasher-3.5 -f -F u-boot-2012.10-rc3-1+zImage-2.6.28-omap1.fiasco

michaaa62 2013-06-03 16:55
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
This may be some silly question...
Did you wait a couple of minutes while the N900 boots after the complete flash for the system to take its time to, may be, check file systems and optify the system once?

Jackeye 2013-06-03 19:36
Re: N900 - Cannot Boot, but Flash VANILLA and FIASCO done
 
Many thanks for all of yours kindness!

After two days of flashing with no success I decided to spent time with quite better way. So, this piece of N900 I'm selling after a few days of ownership. What a shame, that last user provide me very "courved facts" about N900's problems. I will buy new one, with no SW problem.

If anyone of you want or need N900 for parts (touch digitizer, display, slider mechanism, battery, camera, maybe some other parts from mainboard, stylus and charger are absolutelly OK, except the housing), here is the link on ebay.com. If you bouht it and contact me with PASS MAEMO.ORG, I will add also a SanDisk MicroSD card with 4GB memory as a gift.

Thanks to all for your time!


All times are GMT. The time now is 11:00.

vBulletin® Version 3.8.8