Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (3)
to General by Kalatti - 1 day, 8 hrs ago - more...
|
2012-01-09
, 16:07
|
|
Posts: 78 |
Thanked: 9 times |
Joined on Oct 2011
|
#22
|
So basicly, if I understand this all.
If I restore the backup given to me on the this thread with Backupmenu it'll just restore the rootfs and the other one, but it doesn't remove the kernels ( as they are in /boot/ ).
Thanks Ade and Pali for the information !!
Now I have a qeustion about nitdroid, isn't that one under a different location? ( /and/ ) instead of /boot/ ?
If I restore the backup given to me on the this thread with Backupmenu it'll just restore the rootfs and the other one, but it doesn't remove the kernels ( as they are in /boot/ ).
Thanks Ade and Pali for the information !!
Now I have a qeustion about nitdroid, isn't that one under a different location? ( /and/ ) instead of /boot/ ?
__________________
I'm new to Meamo, don't be too hard on me.
I'm new to Meamo, don't be too hard on me.
|
|
2012-01-09
, 16:21
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#23
|
Originally Posted by Pondake
Mostly correct. It won't overwrite the kernel, but because it is located in /dev/mtd. /boot does get overwritten, because that it is part of rootfs.This means the kernel from the rootfs backup will be placed in /boot during restore.
So basicly, if I understand this all.
If I restore the backup given to me on the this thread with Backupmenu it'll just restore the rootfs and the other one, but it doesn't remove the kernels ( as they are in /boot/ ).
Now I have a qeustion about nitdroid, isn't that one under a different location? ( /and/ ) instead of /boot/ ?
/and/ is the filessystem used by nitdroid itself.
| The Following User Says Thank You to ade For This Useful Post: | ||
|
|
2012-01-09
, 16:25
|
|
Posts: 78 |
Thanked: 9 times |
Joined on Oct 2011
|
#24
|
Originally Posted by ade
Ooooh, okay. Thanks a lot for explaining.
Mostly correct. It won't overwrite the kernel, but because it is located in /dev/mtd. /boot does get overwritten, because that it is part of rootfs.This means the kernel from the rootfs backup will be placed in /boot during restore.
Nitdroid requires multiboot. So the part describing multiboot applies. The nitdroid kernel used for flashing is in /boot (just like the other kernel images)
/and/ is the filessystem used by nitdroid itself.
__________________
I'm new to Meamo, don't be too hard on me.
I'm new to Meamo, don't be too hard on me.
|
|
2012-01-11
, 17:11
|
|
Posts: 78 |
Thanked: 9 times |
Joined on Oct 2011
|
#25
|
Now this is just great, just backed everything up and restored the backup given to me. Now it's in a boot loop. Just.. just great.
F*CK, I can't even get acces to the backupmenu, it says loading and then shuts off.
Am I doomed?
Last edited by Pondake; 2012-01-11 at 17:16.
F*CK, I can't even get acces to the backupmenu, it says loading and then shuts off.
Am I doomed?
__________________
I'm new to Meamo, don't be too hard on me.
I'm new to Meamo, don't be too hard on me.
Last edited by Pondake; 2012-01-11 at 17:16.
|
|
2012-01-11
, 17:54
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#26
|
The restored backup is an image of system with multiboot and backupmenu installed ?
If not you have done a serious mistake restoring that image.
If yes it is possible that internal flasher (used by multiboot) has done an uncomplete kernel flash when it has changed kernel after first reboot.
Sometime happens that multiboot fails to flash kernel.
Unfortunately in these cases you need an Usb cable to fix
Last edited by Fabry; 2012-01-11 at 17:56.
If not you have done a serious mistake restoring that image.
If yes it is possible that internal flasher (used by multiboot) has done an uncomplete kernel flash when it has changed kernel after first reboot.
Sometime happens that multiboot fails to flash kernel.
Unfortunately in these cases you need an Usb cable to fix
Last edited by Fabry; 2012-01-11 at 17:56.
|
|
2012-01-11
, 17:56
|
|
Posts: 78 |
Thanked: 9 times |
Joined on Oct 2011
|
#27
|
Originally Posted by Fabry
Dude, they told me that I had to restore the backup and they gave me a link.
The restored backup is an image of system with multiboot and backupmenu installed ?
If not you done a serious mistake.
If yes it is possible that internal flasher (used by multiboot) has done an uncomplete kernel flash.
Sometime happens that multiboot fails to flash kernel.
Unfortunately in these cases you need an Usb cable to fix
Which was this: http://robbiethe1st.afraid.org/Backu...omplete_image/
And yes I had multiboot, but after that I installed backupmenu and the multiboot was gone but I think the kernels are there.
...
__________________
I'm new to Meamo, don't be too hard on me.
I'm new to Meamo, don't be too hard on me.
|
|
2012-01-11
, 18:04
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#28
|
Originally Posted by Pondake
Multiboot MUST BE present on image you restore and not only on your system that you will overwrite with a restore.
And yes I had multiboot, but after that I installed backupmenu and the multiboot was gone but I think the kernels are there.
...
I don't know if the image at proposed link is an image of a system that has multiboot installed (and so copied to rootfs backup).
Since BackupMenu is usually used with BootMenu and not with Multiboot, I suspect that the image proposed is without multiboot.
But only examing backup image (rootfs) we can be sure.
| The Following 2 Users Say Thank You to Fabry For This Useful Post: | ||
|
|
2012-01-11
, 18:06
|
|
Posts: 78 |
Thanked: 9 times |
Joined on Oct 2011
|
#29
|
Originally Posted by Fabry
Let us assume it was an image without multiboot, what do I do now?..
Multiboot MUST BE present on image you restore and not only on your system that you will overwrite with a restore.
I don't know if the image at proposed link is an image of a system that has multiboot installed (and so copied to rootfs backup).
Since BackupMenu is usually used with BootMenu and not with Multiboot, I suspect that the image proposed is without multiboot.
But only examing backup image (rootfs) we can be sure.
__________________
I'm new to Meamo, don't be too hard on me.
I'm new to Meamo, don't be too hard on me.
Last edited by Pondake; 2012-01-11 at 18:13.
 |
|
2012-01-11
, 18:11
|
|
Posts: 106 |
Thanked: 81 times |
Joined on Dec 2011
@ /
|
#30
|
The problem is you restored a full clean backup, without backupmenu and all the stuff installed.
| The Following 2 Users Say Thank You to eight For This Useful Post: | ||
The kernel is stored in nand memory (/dev/mtd...).
When the device is started, it will boot the kernel from that nand memory.
In case of multiboot:
When you choose another kernel, the multiboot application reads the corresponding kernel image stored in /boot/, flashes it into nand memory and restarts the device. Then the device will boot the new flashed kernel.
It can be flashed from the phone or via USB.
This means that Estel is technically speaking most right
But it also means that in most cases (at least in multiboot), your rootfs backup from backupmenu will be helpfull to reflash your kernel.
It makes my own restore situation also clearer to me:
I did a restore from rootfs (with pk48) on a pk49 phone. After restart I had a good working pk48 situation. Now its clear to me that the restored multiboot config had pk48 as default kernel, so when started it saw it had another version in dev/mtd... and flashed the restored pk48 image. I wrongly assumed it just used /boot/multiboot/vmlinuz-2.6.28.10-power48.
Thanks for the explanation Pali.