View Single Post
Old 10-16-2011, 03:25 PM   #165
nikkie
Guru
nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40nikkie is slicker than a case of WD-40
 
nikkie's Avatar
 
Posts: 614
Karma: 73700
Join Date: Oct 2009
Location: WA, USA
Device: Android, Kindle Paperwhite, lots of ancient readers
Quote:
Originally Posted by vicinc View Post
I did not hijacked the thread. The thread was about the serial.
my post is saying that I build the cable and worked, (i will send pics of my setup shortly, I used the cable from an old serial mouse).
Also I reported than on my device did not worked forcing the update through. I thought was the right place to report my results, sorry if i disturbed anybody. I know the most knowledgeable people are here on this thread. Unfortunately my system is garbled badly. if anybody knows a way from forcing the update from the terminal I will really appreciate this.
Vicinc, running "run boot_user" does force the upgrade. I can't tell from your logs whether you actually ran that in the u-boot prompt (it looks like not, you typed it before the prompt, but did not succeed at getting into u-boot). Regardless, the problem with YOUR device appears to be filesystem corruption. So you have two options, either make sure you get the device into the u-boot prompt, or run fsck on your partitions from busybox from adb.
nikkie is offline   Reply With Quote