View Single Post
Old 01-10-2012, 06:40 PM   #21
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 rastik View Post
Why are you asking questions about K3?
Oops. I mean "touch". I was just answering K3 questions for somebody else earlier and I typed the wrong thing here. I type the wrong thing all too often these days. At least I can edit my posts here. I will go back and edit those "s/k3/touch/g"... Done.

Hmm.. There was only one reference to k3 in my posts that I could edit. All the rest are in your posts (or your copies of my post). Anyway, I changed the one instance of "k3" to "touch" that was in my posts.

But, the idea is the same. Is the TOUCH apparently ignoring the '3' key in the uboot menu BECAUSE it cannot find a file formatted the way it wants?

The recovery menu on TOUCH is in mmcblk0p2, which was whacked by by zeroing the entire mmc, it looks like.

Is the uboot source code that you have for the TOUCH?

Last edited by geekmaster; 01-10-2012 at 06:51 PM.
geekmaster is offline   Reply With Quote