Thread: A way to flash without USB?
View Single Post
ade is offline ade
2012-01-08 , 23:07
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#21
Originally Posted by ade View Post
Estel,
I am pretty sure in my multiboot configuration, /boot/multiboot/vmlinuz-2.6.28.10-power49 is my kernel image, just like /boot/multiboot/vmlinuz-2.6.28.NIT.07 is my nitdroid kernel image. Remove it, and you can't start your system. Now you say it is a totally different thing. You may be right for a non-multiboot system (then it uses the fiasco image in my opinion), but not in my case.

Please elaborate on this if you can show me I am wrong.
Pali was willing to give me more information about this, I will rephrase what told me:
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.
 

The Following 2 Users Say Thank You to ade For This Useful Post: