<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Well, here's the situation.<br>
I can power up into NAND or NOR uBoot. Option to boot from SD is
available to me. If i do "screen /dev/ttyACM0" on the host machine I
get the bootloader command prompt and can run those commands (e.g. i
can see the partition lists for both NOR and NAND).<br>
So it's not a full brick yet. However after several previous reflash
attempts i'm pretty sure that Android installation is corrupted, as I
can no longer boot into it.<br>
There's still a possibility of booting from SD card into a regular moko
environment (one of) and maybe flashing from there... At least I hope
that it will work.<br>
If not - i'll be looking for a person with a debug board in Vancouver :D<br>
Vasili Sviridov wrote:
<pre wrap="">Not sure what has changed, but when I do dfu-util -l from both NOR and
NAND uBoot i get this
Found Runtime [0x1d50:0x5119] devnum=3, cfg=0, intf=2, alt=0, name="USB
Device Firmware Upgrade"
and thats the only line in there.
So i'm currently not even able to update the bootloader (as i hoped
that'll allow me to see the rest of the partitions).
You can't even update?
That sounds pretty bad. If you get that from both NAN and NOR then you've
got problems. I was going to suggest that maybe you follow the " What if I
borked my bootloader environment and don't get a prompt anymore?"
<a class="moz-txt-link-freetext" href="http://wiki.openmoko.org/wiki/Bootloader">http://wiki.openmoko.org/wiki/Bootloader</a>
but if you get that from both then... Are you still running uboot or did you
switch to the new thing?