Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 15 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 10 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 19 hrs ago - more...
|
2010-08-09
, 02:18
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#82
|
Well, two things: One, remember what files are on the OptFS - Only supporting files. Those files probably did get copied, but until you copy the rootfs, you can't access any applications, as the application excecutables(or, if they are stored on thw OptFS, any links to those files) aren't on the RootFS.
In Windows terminology, its like copying your old programs to the program files directory, then wondering why those programs aren't showing up in the start menu.
Edit:
Also, I've gotten that "can't flash" message - Flashing to PR1.2, and then immediately flashing the rootfs with the flasher tool seems to fix that - IF your RootFS backup is not corrupt.
I am thinking though that bad blocks have some part in this whole thing - thats why some of us can backup and restore successfully, yet others do the exact same steps and it not work quite.
If you can't flash, hold on for a while, see if you can't get that ubifs mount code working, and I'm gonna try to figure out a different way of backing up and restoring that is more tollerant of bad blocks.
Last edited by RobbieThe1st; 2010-08-09 at 02:22.
In Windows terminology, its like copying your old programs to the program files directory, then wondering why those programs aren't showing up in the start menu.
Edit:
Also, I've gotten that "can't flash" message - Flashing to PR1.2, and then immediately flashing the rootfs with the flasher tool seems to fix that - IF your RootFS backup is not corrupt.
I am thinking though that bad blocks have some part in this whole thing - thats why some of us can backup and restore successfully, yet others do the exact same steps and it not work quite.
If you can't flash, hold on for a while, see if you can't get that ubifs mount code working, and I'm gonna try to figure out a different way of backing up and restoring that is more tollerant of bad blocks.
Last edited by RobbieThe1st; 2010-08-09 at 02:22.
 |
|
2010-08-10
, 10:51
|
|
Posts: 149 |
Thanked: 15 times |
Joined on Jul 2010
@ Russia
|
#83
|
RobbieThe1st, hello!
Just want to know, if can i use ur backup menu with Nitdroid and Maemo installed?
Now i'm using ur latest version and can't get any points in menu.
Maemo + MeeGo + NitDroid and ur backupmenu = all i need =)
Just want to know, if can i use ur backup menu with Nitdroid and Maemo installed?
Now i'm using ur latest version and can't get any points in menu.
Maemo + MeeGo + NitDroid and ur backupmenu = all i need =)
 |
|
2010-08-10
, 17:58
|
|
Posts: 1,210 |
Thanked: 597 times |
Joined on Apr 2010
@ hamburg,germany
|
#84
|
hej robbie first thanks for your great work
but ive got a question.
if my phone is messed up and i have to reflash it.how i should to it?
i explain you how i understand it say if something is wrong.
i have to run the maemo flasher but can i use my image or the original one?
and after that i have to install your app and restore optfs is that right?
and after that everything should be alright?
one question left.
if i want to go into flashing mod with my n900 can i press and hold u like always??
thanks
but ive got a question.
if my phone is messed up and i have to reflash it.how i should to it?
i explain you how i understand it say if something is wrong.
i have to run the maemo flasher but can i use my image or the original one?
and after that i have to install your app and restore optfs is that right?
and after that everything should be alright?
one question left.
if i want to go into flashing mod with my n900 can i press and hold u like always??
thanks
__________________
Nobody likes us but we dont care....
Nobody likes us but we dont care....
|
|
2010-08-11
, 01:43
|
|
Posts: 326 |
Thanked: 335 times |
Joined on Feb 2010
|
#85
|
Originally Posted by atilla
1) If you have any problem .. you have to flash with the fiasco image before (the originale one) and with your root after,
hej robbie first thanks for your great work
but ive got a question.
if my phone is messed up and i have to reflash it.how i should to it?
i explain you how i understand it say if something is wrong.
i have to run the maemo flasher but can i use my image or the original one?
and after that i have to install your app and restore optfs is that right?
and after that everything should be alright?
one question left.
if i want to go into flashing mod with my n900 can i press and hold u like always??
thanks
Before everything .. put your OPT image in MyDocs. Shut down the phone.
Press U while you connect the usb port (yes, in every type of flash, even the one of the root created by backupmenu, you HAVE TO activate the flash mode pressing U).
Then give the command :
flasher-3.5.exe -F nameofFIASCOimage.bin -f
At the end of the process ... give this other command:
flasher-3.5.exe -r nomeOFyourROOTimage -f
The first one erase everything... the second one put the old root image in the phone.
Than unplug the cable and make the first boot with the opened keyboard.
Backupmenu should run.. and from here you should select the option to restore ONLY OPT .
At the end of this everything should be all right
Last edited by Dany-69; 2010-08-11 at 01:45.
|
|
2010-08-11
, 09:56
|
|
Posts: 1,210 |
Thanked: 597 times |
Joined on Apr 2010
@ hamburg,germany
|
#86
|
thank you very much i was a little bit confused but now im know it
__________________
Nobody likes us but we dont care....
Nobody likes us but we dont care....
 |
|
2010-08-12
, 08:17
|
|
Posts: 2,142 |
Thanked: 2,054 times |
Joined on Dec 2006
@ Sicily
|
#87
|
Having borked my rootfs while trying to fsck the /home partition, I tried to reflash from inside backupmenu, but the device didn't start.
So I reflashed from a desktop machine, first the pr1.2 image, then the rootfs, but this time when restoring a message says that all telephony functions are disabled.
The flasher output is
Maybe the problem is in the last line, possible? It doesn't flash the CMT.
Thing is I don't know if restart with a fresh firmware altogether or there is a way to restore my latest rootfs image correctly. Please help...
So I reflashed from a desktop machine, first the pr1.2 image, then the rootfs, but this time when restoring a message says that all telephony functions are disabled.
The flasher output is
Code:
root@ubuntu:/media/DATA/backup_n900# flasher-3.5 -r 20100809-backup-rootfs.img -f flasher v2.5.2 (Oct 21 2009) Suitable USB device not found, waiting. USB device found found at bus 002, device address 012. 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 and flashing rootfs image (257280 kB)... 100% (257280 of 257280 kB, avg. 13257 kB/s) Finishing flashing... Sending request 0x52 failed: No such device
Thing is I don't know if restart with a fresh firmware altogether or there is a way to restore my latest rootfs image correctly. Please help...
__________________
Ernesto de Bernardis
Ernesto de Bernardis
|
|
2010-08-12
, 08:34
|
|
Posts: 2,142 |
Thanked: 2,054 times |
Joined on Dec 2006
@ Sicily
|
#88
|
And now I can't reflash the original rootfs either.
Seems my N900 is dead.
Code:
root@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 024. 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. 11875 kB/s) Flashing bootloader... done. Sending cmt-2nd image (79 kB)... 100% (79 of 79 kB, avg. 7950 kB/s) Sending cmt-algo image (507 kB)... 100% (507 of 507 kB, avg. 18129 kB/s) Sending cmt-mcusw image (5786 kB)... 100% (5786 of 5786 kB, avg. 16253 kB/s) Flashing cmt-mcusw... done. Sending kernel image (1700 kB)... 100% (1700 of 1700 kB, avg. 15896 kB/s) Flashing kernel... done. Sending and flashing rootfs image (149376 kB)... 0% (1024 of 149376 kB, 3968 kB/s) Write failed after 1048576 bytes usb_bulk_write: Resource temporarily unavailable
__________________
Ernesto de Bernardis
Ernesto de Bernardis
|
|
2010-08-12
, 08:59
|
|
Posts: 575 |
Thanked: 621 times |
Joined on May 2010
|
#89
|
maybe try to remove battery for some times ...
and start again
and start again
|
|
2010-08-12
, 09:03
|
|
Posts: 2,142 |
Thanked: 2,054 times |
Joined on Dec 2006
@ Sicily
|
#90
|
nope, I tried also that. I also tried to flash the rootfs only:
flasher-3.5 -r rootfs.jffs2 -f
but the same error is logged.
flasher-3.5 -r rootfs.jffs2 -f
but the same error is logged.
__________________
Ernesto de Bernardis
Ernesto de Bernardis
With a fresh flash of the RootFS followed by the reinstallation of BackupMenu from the repositories, the two backup files were found in the restore menu. I first tried to restore only the OptFS. It was successful according to BackupMenu, but when rebooting the N900, I saw absolutely no change (same applications as before, that is to say almost none). So I tried to restore both RootFS and OptFS using the adequate option in your application. I don't know if it was successful or not, I was not watching the screen during the process and when I came back to check, the N900 was shut off. Now, I cannot boot it, it just displays the white Nokia screen and then switches off. The same thing happens when booting with the keyboard slided out, so no way to come back to BackupMenu. The battery was full.
What really annoys me is that I can't flash again using Maemo Flasher. I flashed my N900 many times and this is the first time I can't do it. Here is the error I get:
Is it bricked? :/
[Edit] OK, I fixed the flashing issue by flashing without the -R option. It worked and now I can flash flawlessly again, with or without -R. But this doesn't really say us why restoring OptFS did not actually restore anything and why restoring RootFS and OptFS screwed up my N900. I'm going to reinstall apps manually and create new backup files just in case, but I'm really interested in your app so I would like to understand why it was not working in my case (and only in my case, obviously). Maybe the backups are corrupted but it would be surprising as BackupMenu said "Success" for the OptFS restoration; and I see no reason why they would be corrupted.
Last edited by Kabouik; 2010-08-09 at 02:10.