Notices

no, but I got errors during the restore.
right, on my device atm stock kernel, on the backup image kernel-power 48... hmm how to solve it?
To be honest, personally, I don't see point 3 as a compliment. No you're wrong

Sorry for point 3 - I just wasn't able to stop myself for writing it, after seeing totally unrelated messages in Your report - they appear everytime You open backupmenu, without those two reported (unnecessary) files on device. So You were basically reporting messages from backupmenu starting process, as a reason for unbootable device

To be honest, error messages - that you get, while trying to restore - would be much more useful.

As for Your question - reflashing, installing kp48 + backupmenu, and restoring backup after that, should do the trick. Ho ever, posting here errors that You get during backup restoration may be sane thing to do - it's possible, that Your backup is corrupted (not related to fact that you're trying to restore over wrong kernel).

To be honest, I would post errors here, then, immediately, try proposed solution - it's a chance that You'll fix everything without waiting for answer. At the same time, *if* Your backup is corrupted, You're doomed to start form scratch (reflash, manually installing) anyway. Ho ever, keep in mind that I've not seen any case, where wrong backup happen "out of the blue sky" - backuping algorithm is quite reliable, and if it finished backuping without errors + announced that it was completed successfully, it is probably some kind of user fault (pure assumption here, thought).

Anyway, please report here about results - it's interesting.

/Estel

seems to solve it, thx a lot

No problem, I'm glad it solved your problem. Also, in future, You may use "thanks" button on the downright part of post You would like to "thank". Not mocking up, just saying in case of future "thank you" situations

Good luck with hackin' on Your N900!

Forgive me if I'm not posting this in the right place.

I have a problem with backupmenu.

I have two N900s (both PR-1.2), and I want to clone one to the other. The trouble is that backupmenu does not work on the phone from which I want to write a backup (it works fine on phone I want to read the backup).

When I boot with the keyboard open the screen just shows:

I have bash installed, but /usr/sh still points to busybox.

I tried removing and reinstalling backupmenu, but that didn't help.

Does anyone have an suggestions to help me diagnose and fix the problem?

Thanks.

I found the problem with my setup. backupmenu was trying to use the gnu "find" command instead of the "find" command which links to busybox. So, nothing wrong with backupmenu, it was my personal settings which were causing the problem.

Can you add the feature to exclude some folders when backing up? I have a webos game folder which is about 3.5GB and it takes very long to back it up. Furthermore, since fat32 can't handle files larger than 4GB, I think I may not be able to back up when my games folder grow larger.

FYI:

To remove the pesky messages about battery charging state with frame buffer console (root terminal) edit:

/usr/share/backupmenu/Backupmenu.item

and change line 294 from:

to:

dumb question mode on:
Of course You've tested, that charging still really occur in background?

There are no dumb questions just dumb answers (or some sh1t).

Yes the n900 STILL charges. You can tell because when you plug it in the screen goes bright. All the above does is redirect the script output to /dev/null (black hole that compresses data to a singularity and sends it back in time to when you had the n900 switched off, thus you cannot see it.)