Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.216.240,10.89.1.2
Lock expires at: 2025/06/18 09:09 (5 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

== [turbooster 2012/09/26]  ==
As allways when there's the boot-partition to be found then it is not mine. I do ''for dev in /dev/mmcblk0p*; do abootimg -i $dev;done'' and mmcblk0p2 is NOT a boot-partition. My model is the ac-100 10K, german model no UMTS Android 2.2 bootloader. I haven't played around with bct or similar. That's why I think I'm not the only one having the issue.

== [ggrandou 2010/09/29] ==
  * Please fix the title
  * Please don't mess with boot command line. Every device has a different one, so giving yours in example will only make others to make their device unbootable. If you really want to update your kernel, you don't need to change cmdline, so simply don't give -c argument, and your old cmdline will not be changed.
  * and anyway, if you install a kernel from a .deb package, there is no need to run abootimg at all. the package post-install script will do it for you.
  * when you put image, please upload them to wiki and don't rely on third-party website to serve them.