maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   I'm in panic. Can't flash anymore. Please help (https://talk.maemo.org/showthread.php?t=60201)

debernardis 2010-08-12 08:53
I'm in panic. Can't flash anymore. Please help
 
Sorry for double posting that also in the BackupMenu thread, but as I wrote I'm in panic and think that my device is definitively bricked.

I had a problem in /home, tried to fsck but had problems in rebooting. Tried to restore from the last backup of BackupMenu from the device but with no joy. Reflashed the original PR1.2 rootfs, then my latest rootfs backup, but when booting got the notice that the telephony services were blocked.

Tried to reflash again with Backupmenu - then making a long story short, seems I'm unable to reflash the pr1.2 system any more. See the log:
Code:
oot@ubuntu:/media/DATA/backup_n900# flasher-3.5 -F RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin -f
flasher v2.5.2 (Oct 21 2009)

SW version in image: RX-51_2009SE_1.2009.42-11_PR_MR0
Image 'kernel', size 1700 kB
    Version 2.6.28-20094102.3+0m5
Image 'rootfs', size 149376 kB
    Version RX-51_2009SE_1.2009.42-11_PR_MR0
Image 'cmt-2nd', size 81408 bytes
    Version 8.2.2009.34.3-2+0m5
Image 'cmt-algo', size 519808 bytes
    Version 8.2.2009.34.3-2+0m5
Image 'cmt-mcusw', size 5786 kB
    Version 8.2.2009.34.3-2+0m5
Image '2nd', size 14720 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.13+0m5
Image 'xloader', size 14848 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.13+0m5
Image 'secondary', size 109440 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.13+0m5
Image '2nd', size 14720 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.13+0m5
Image 'xloader', size 14848 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.13+0m5
Image 'secondary', size 109440 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.13+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.13+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.13+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.13+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.13+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.13+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.13+0m5
Suitable USB device not found, waiting.
USB device found found at bus 002, device address 034.
Found device RX-51, hardware revision 2101
NOLO version 1.4.13
Version of 'sw-release': RX-51_2009SE_1.2009.42-11_PR_MR0
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. 10687 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. 20305 kB/s)
Sending cmt-mcusw image (5786 kB)...
100% (5786 of 5786 kB, avg. 17118 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1700 kB)...
100% (1700 of 1700 kB, avg. 16840 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (149376 kB)...
  0% (1024 of 149376 kB, 3893 kB/s)
Write failed after 1048576 bytes
usb_bulk_write: Resource temporarily unavailable
The rootfs image is not written. Maybe the root partition is over? What can I do? Help please.

debernardis 2010-08-12 09:01
Re: I'm in panic. Can't flash anymore. Please help
 
Can't do either
flasher-3.5 -r rootfs.jffs2 -f

gives same error

AlMehdi 2010-08-12 09:13
Re: I'm in panic. Can't flash anymore. Please help
 
hmm.. isn't that the PR1.1 image... try the PR1.2 image and se if it works better.

giannoug 2010-08-12 09:15
Re: I'm in panic. Can't flash anymore. Please help
 
What are you trying to flash?

RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin
^ this is PR1.2

debernardis 2010-08-12 09:20
Re: I'm in panic. Can't flash anymore. Please help
 
Oh my... :)
...now downloading - hope it works

...damn' my slow connection here... still 47% to download

atilla 2010-08-12 09:52
Re: I'm in panic. Can't flash anymore. Please help
 
yes its the wrong firmware.
i tried to downgrade to pr1.1 long time ago and i got the same reslt.
telephone functions are ****ed up.
flash with the original rootfs/emmc to delete everything.then flash with your rootfs image install backupmenu and restore your optfs.
and everything should be alright

debernardis 2010-08-12 10:55
Re: I'm in panic. Can't flash anymore. Please help
 
The firmware I was using was the old one, and this is the first issue - thanks AlMehdi & Giannoug - but it wasn't the only problem.

There was also the infamous
Code:
Write failed after 1048576 bytes
usb_bulk_write: Resource temporarily unavailable
which prevented the backup to succeed, even with the right image.

Yep, to make the story short after several aborted flashes I was able to restore my PR1.2 and then my rootfs backup. Life's good again. See also http://talk.maemo.org/showpost.php?p...3&postcount=92 for the exact way I could reflash.

It was scary. You can't understand how much you depend on your personal assistant, save when you see it effectively dead. And I'm an addiction doc, after all. Maybe I should write about a new disease, "NIT dependence".

Stskeeps 2010-08-12 10:59
Re: I'm in panic. Can't flash anymore. Please help
 
You'll want to start up and run nand_erase on the area, what has happened probably is that the eraseblocks got out of wack.

What kind of devilish method are people using anyway?

MohammadAG had same problem.

debernardis 2010-08-12 11:02
Re: I'm in panic. Can't flash anymore. Please help
 
Quote:
Originally Posted by Stskeeps (Post 784001)
You'll want to start up and run nand_erase on the area, what has happened probably is that the eraseblocks got out of wack.

What kind of devilish method are people using anyway?

MohammadAG had same problem.
Can you give some details more please before I try? I've never heard of nand_erase and I'm not in the mood of borking my rootfs again for my ignorance :o

RobbieThe1st 2010-08-13 04:47
Re: I'm in panic. Can't flash anymore. Please help
 
Quote:
Originally Posted by Stskeeps (Post 784001)
You'll want to start up and run nand_erase on the area, what has happened probably is that the eraseblocks got out of wack.

What kind of devilish method are people using anyway?

MohammadAG had same problem.
I'd like to know more about this too - Currently, with my tool you can either flash the Rootfs image directly, which works in some cases, but sometimes it gives an error. In those cases, you have to flash PR1.2, then flash your backed up rootfs over that - why you have to do this, I dunno.


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

vBulletin® Version 3.8.8