Having big problems here, if you quit out when it hangs, it still creates a readable seemingly complete tar file so i thought i'd try restoring the rootfs.
Just sits there forever saying restoring and size:n/a (guessing this should read a size) and rebooting the phone obviously results in a bricked device.
Just reflashed pr1.3 fiasco and going to try and restore again and see what happens...
Still just getting size:n/a, going to leave this until morning and see what happens. Would greatly appreciate a fix on this soon so I can send my N900 off to be repaired (cracked screen) .
Just to report my first recover. As my first language is Portuguese, there are a lot of diacritical marks... I particularly hate this but well, I can't just convince the people here to stop using =]
The point is, I was playing around with the "/usr/share/X11/xkb/symbols/nokia_vndr/rx-51" file and guess what... My N900 stop booting. I had already did this some months ago and had to reflash it. Now, I used the recover from BackupMenu and everything back to normal.
Love you Robbie, I would even marry you if I wasn't already. ;D
At c), i didn't mean allow user to select folder, I meant only searching a subfolder. If I want to arhive a backup, remove it from the menu, I have to move it off the card or kill the extension. It would be easier and neater if the backup path would include a folder, like osso backup dues, it uses /backup/
Done, in 0.50-1(if I can ever get it to you guys).
Do you plan on pushing a known-good version to testing, so we can revert if the alpha -devel breaks for any reason? (I know the .deb is available on the forum).
Once I have one that works and people are happy with.
Robbie,
I dont know if the most of user think the same but, for me, would be even better if the timestamp of the resulting file shows the hour and minutes.
Also getting this problem, was stuck on 253.4m, rm-rf'd /var/tmp/* and /tmp/*, now stuck on 253.5m, desperately need this working as am supposed to be sending my n900 off to be replaced...
Cheers Robbie
Edit: I don't get any error, it just hangs...
I'd like you to try it with 0.50-1, as soon as I can get it up.
@others:
Thanks for the comments. I'm only one person here, and it's hard to do things when the damn repo's down. I'm trying to build a package myself, but it doesn't work quite right yet.
You're doing a great job Robbie, and rest assured all your hard work is really appreciated. The repositories are playing up which isn't helping anyone..
Done, in 0.50-1(if I can ever get it to you guys).
Once I have one that works and people are happy with.
Yea, I'll do that in a bit.
So am I.
Let me know when it's fixed and works.
Added in 0.50-1
I'd like you to try it with 0.50-1, as soon as I can get it up.
@others:
Thanks for the comments. I'm only one person here, and it's hard to do things when the damn repo's down. I'm trying to build a package myself, but it doesn't work quite right yet.
we know dude an your work is very much appreciated
Any chance you can write a step-by-step on how to do this for non-coders? I'm confident I could get this working too but not without the proper guidance. Thank you in advance!
Sure. I'm assuming you've already got multiboot 0.2.10 installed here - if not, you'll need to look up the instructions for that elsewhere (the multiboot/NITDroid/power kernel threads).
Unfortunately the only implementations of patch appear to be in the SDK repository, so rather than using the diff, just grab the patched files and save them to the MyDocs directory.
Now overwrite the existing multiboot files with the new versions:
Code:
root
cd /sbin
tar -xzf /home/user/MyDocs/multiboot_patched.tar.gz
chmod 755 multiboot multiboot_read_item
That's the patched multiboot all done, so you now just need to create a new boot item. You'll need to create a file (either on the N900, or on a desktop/laptop then copied to the N900) containing:
Move this file to /etc/multiboot.d/99-BackupMenu.item (you'll need to be root to do this).
Now when you reboot with the keyboard open, you'll get an option for BackupMenu. I think this'll work irrespective of which OS/kernel you've been booting with, but I've only tested it from the standard Maemo kernel so far.
EDIT: Missed a bit - you also need to symlink evkey (which handles key detection) to where backupmenu is expecting it: