View Single Post
Old 07-12-2012, 04:03 PM   #32
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by arooni View Post
I know that I would do this with dd, but I'd love some help with the command to do it.

-rw-r--r-- 1 david david 2115008 Jun 6 2011 uImage
Well, 2115008 is NOT a multiple of 512, so it DOES need some padding.

Using integer arithmetic:

(2115008+511)/512)*512-2115008 = 64

So you need to append another 64 bytes to your uImage file:

dd if=/dev/zero bs=64 count=1 >> uImage

Then try flashing that...

@hawhill: How about having k3flasher append zeros to the next 512 byte boundary to avoid this problem?

Last edited by geekmaster; 07-12-2012 at 04:11 PM.
geekmaster is offline   Reply With Quote