Active Topics

 



Notices


Reply
Thread Tools
Posts: 842 | Thanked: 1,197 times | Joined on May 2010
#121
Well, I'm not opposed; If someone who knows Multiboot code wants to try to figure it out, I'll do my best to help out.

I have a feeling though that, without changing Multiboot's code, there are two options:
1. run it via console mode or,
2. set up an item that loads the Maemo OS, but somehow launches BackupMenu in the boot process. (with boot options?)
 
Posts: 478 | Thanked: 165 times | Joined on Apr 2010 @ Manchester
#122
Well the item file would need to be

ITEM_NAME="Maemo Backupmenu"
ITEM_KERNEL=2.6.28-omap1
ITEM_MODULE=ext3

That would boot maemo normally, Then maybe adding

ITEM_INITRC="path to backupmenu.item"

Might launch bootmenu for you. Although, I am thinking backupmenu.item might have to be renamed and possibly modified as ITEM_INITRC tells multiboot which init program to execute when switching over to root.

There is no way to tell the existing multiboot of boot options as such so that is the only way I can see at the moment.

I was going to install backupmenu and have a play around to see if I could work anything out but it depends on bootmenu which conflicts with multiboot.

Edit: Not sure how easy it is to change multiboot's code to make them work together or how busy he is, but JAY-C is the creator of multiboot so it might be worth contacting him to see if there is anything you can work out between you to get the two to intergrate?

Edit 2: Especially if backupmenu is just a shell script, as he may be able to add support for running a script prior to booting?
__________________
Temporary signature: Real signature removed for cleaning.

Don't forget the thanks button if I helped you

Last edited by mornage; 2010-08-22 at 14:55.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#123
Originally Posted by mornage View Post
Well the item file would need to be

ITEM_NAME="Maemo Backupmenu"
ITEM_KERNEL=2.6.28-omap1
ITEM_MODULE=ext3

That would boot maemo normally, Then maybe adding

ITEM_INITRC="path to backupmenu.item"

Might launch bootmenu for you. Although, I am thinking backupmenu.item might have to be renamed and possibly modified as ITEM_INITRC tells multiboot which init program to execute when switching over to root.

There is no way to tell the existing multiboot of boot options as such so that is the only way I can see at the moment.

I was going to install backupmenu and have a play around to see if I could work anything out but it depends on bootmenu which conflicts with multiboot.

Edit: Not sure how easy it is to change multiboot's code to make them work together or how busy he is, but JAY-C is the creator of multiboot so it might be worth contacting him to see if there is anything you can work out between you to get the two to intergrate?

Edit 2: Especially if backupmenu is just a shell script, as he may be able to add support for running a script prior to booting?
Unfortunately using ITEM_INITRC doesn't seem to do anything. Even if it did, I doubt it would work. Both bootmenu and multiboot work by modifying the initrd used during boot, and unless the multiboot initrd contains all the same added programs as the bootmenu one, the backupmenu script will fail to find the necessary executables.

EDIT: In fact, the initrc would be called after switching from the initrd, so the contents of that wouldn't matter. You'd still need all the executables installed on the N900 though.

Last edited by Rob1n; 2010-08-23 at 08:10.
 
Posts: 22 | Thanked: 5 times | Joined on May 2010
#124
Originally Posted by Dany-69 View Post
1) If you have any problem .. you have to flash with the fiasco image before (the originale one) and with your root after,

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
After selecting 'Restore OptFS' and 'eMMC/MyData'

'Select File: OptFS image' dialog somehow does not let me to select option 'a)'; which is my OptFS image.

There seems to be no way of choosing the OptFS.img neither from the SD or the eMMC.

Interesting part is: the OptFS restores fine if the backed up RootFS.img is not flashed first.

Is there a way of restoring the OptFS as well using the PC flasher?

Thanks in advance!

Last edited by tan; 2010-08-23 at 22:07.
 
hawaii's Avatar
Posts: 1,030 | Thanked: 792 times | Joined on Jun 2009
#125
No. You can not restore /opt/ using flasher.
 

The Following User Says Thank You to hawaii For This Useful Post:
Posts: 22 | Thanked: 5 times | Joined on May 2010
#126
I also tried restoring the OptFS first using the BackupMenu and flashing the RootFS right after from PC flasher, in that case system stays on 5 loading lights for hours.

P.s. I'm using a U.S. keyboard layout with v0.32-1 of BackupMenu.

Is there a "safe restore" mode available, or would a manual restore from the 'command line' option would work?

Last edited by tan; 2010-08-24 at 07:09.
 
Posts: 22 | Thanked: 5 times | Joined on May 2010
#127
Also restoring RootFS via BackupMenu leads to an unbootable state. I'm wondering if this is normal. Maybe something is wrong with my RootFS.img (although the sumcheck was ok).
 
Posts: 326 | Thanked: 335 times | Joined on Feb 2010
#128
I've made a lot of experienxe about this .. it seems that it's impossible to restore OPT because something is corrupted in the file...

Making a new backup i were able to restore even OPT...

Robbie for example the images that i gave you weren't good and this is why my tester wasn't able to restore them .. T_T
Making a new one i have solved.. but this is a big bug
 
Posts: 842 | Thanked: 1,197 times | Joined on May 2010
#129
Originally Posted by tan View Post
After selecting 'Restore OptFS' and 'eMMC/MyData'

'Select File: OptFS image' dialog somehow does not let me to select option 'a)'; which is my OptFS image.

There seems to be no way of choosing the OptFS.img neither from the SD or the eMMC.

Interesting part is: the OptFS restores fine if the backed up RootFS.img is not flashed first.

Is there a way of restoring the OptFS as well using the PC flasher?

Thanks in advance!
I assume you are using an older version of BackupMenu. Version .31, IIRC, has a glitch that wouldn't let you select anything in that menu. V.30 and V.32 didn't have it; the latest is fine.
If you have that problem, you are going to have to somehow get V.32 installed on your box.
You can try this:
1. flash to PR1.2
2. Boot up, install BackupMenu V.32.
3. Reboot into BackupMenu
4. Restore the OptFS.
5. Connect your USB cable, ready the Maemo flasher utility and reboot your N900
6. Flash PR1.2 again, then flash your RootFS image.

If everything went correctly, you should have a working system.




Originally Posted by tan View Post
I also tried restoring the OptFS first using the BackupMenu and flashing the RootFS right after from PC flasher, in that case system stays on 5 loading lights for hours.

P.s. I'm using a U.S. keyboard layout with v0.32-1 of BackupMenu.

Is there a "safe restore" mode available, or would a manual restore from the 'command line' option would work?
Check the first post in the topic. You are going to have to flash PR1.2, then your RootFS from flasher, then boot into BackupMenu and restore your OptFS.

Originally Posted by tan View Post
Also restoring RootFS via BackupMenu leads to an unbootable state. I'm wondering if this is normal. Maybe something is wrong with my RootFS.img (although the sumcheck was ok).
This happens sometimes - You have to use Flasher to flash to PR1.2, then flash your RootFS for it to work.
I'm not sure why it does it.


Originally Posted by Dany-69 View Post
I've made a lot of experienxe about this .. it seems that it's impossible to restore OPT because something is corrupted in the file...

Making a new backup i were able to restore even OPT...

Robbie for example the images that i gave you weren't good and this is why my tester wasn't able to restore them .. T_T
Making a new one i have solved.. but this is a big bug
So the problem was with a corrupted image? Ok, great. Let me know if you run into other corrupted images, or if it was a problem thats solved in the current version.

Last edited by RobbieThe1st; 2010-08-24 at 21:34.
 

The Following 2 Users Say Thank You to RobbieThe1st For This Useful Post:
Posts: 22 | Thanked: 5 times | Joined on May 2010
#130
Thank you RobbieThe1st,

Originally Posted by RobbieThe1st View Post
You can try this:
1. flash to PR1.2
2. Boot up, install BackupMenu V.32.
3. Reboot into BackupMenu
4. Restore the OptFS.
5. Connect your USB cable, ready the Maemo flasher utility and reboot your N900
6. Flash PR1.2 again, then flash your RootFS image.
Following these steps I was able to restore both the OptFS and RootFS, although somehow system stays on the loading screen.

Last edited by tan; 2010-08-25 at 09:40.
 
Reply


 
Forum Jump


All times are GMT. The time now is 13:56.