View Single Post
Old 02-27-2012, 11:10 AM   #40
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: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by giorgio130 View Post
if you want to retry under ubuntu, the correct command is "sudo ./fastboot flash system mmcblk0p1.img"
This does not seem to work for the Touch. If you monitor status messages at the internal serial port, it says it is flashing mmcblk0, which can kill your linux kernels for both main and diags. It appears that there is a fastboot bug that needs to be fixed with a custom bist u-boot. After I tried flashing with fastboot, booting to main or diags gives status messages on the serial port saying "linux kernel not found" (or something like that)...

This command worked will on my K4NT though, so this problem seems to be restricted to the touch. It is better to use dd in a RUNME.sh script while booting diags, as described elsewhere.

Last edited by geekmaster; 02-27-2012 at 11:13 AM.
geekmaster is offline   Reply With Quote