Suspect bricking

[Mychaela Falconia]

Hi Ajay,

and welcome to our little odd community! :)

> I had a moto c139 phone which was locked. I realised it when I had to use
> tfc139 to get to the prompt.
>
> I then made a dump of my flash.it was successful too. Then i tried to
> unlock it and erase-program-boot ran perfectly.

The flash erase-program-boot loadtool command programs an image you
specify into the boot sector.  Which image did you flash with this
command, and what was the exact full command?

> I could do the second step on erasing 54 sectors too, but then while
> execution of the third step program-bin after 10 percent I got "command
> echo mismatch"  and it failed.

The most likely reason for the "command echo mismatch" error would be
the serial cable making an unreliable connection; the second most
likely reason would be the phone's battery running down too low during
the flashing operation.  In any case one should be able to recover
(power the phone down by pulling the battery out, put a fully charged
one in, then get back in with fc-loadtool and finish the flashing job)
*if* the boot code that was programmed in the flash erase-program-boot
step is a good and unlocked version - hence me asking about that above.

> As per what I read in docs as the first step was successful good boot code
> sgud have been written. But now I can't switch on and the serial port
> doesn't respond.
>
> Is there any way of rejuvenating the phone again or should I loose hope.

Because the flashing of the main fw image (which image were you
flashing anyway?) got interrupted after you only got some 10% in, the
phone most certainly will not power on and boot normally in this
state.  However, if the boot code you have flashed with that flash
erase-program-boot command is good and unlocked, then you should be
able to recover the phone with fc-loadtool.

Do you have another C1xx phone (another C139 or any other C1xx model)
running one of the official fw versions to charge batteries?  Try the
following steps:

1. Remove the battery from the troubled phone and put a fully charged
   one in, but don't touch the red power button yet.

2. Connect the serial cable (make sure it's a good and reliable one),
   but again, don't touch the red power button yet.

3. Run fc-loadtool like this:

   fc-loadtool -h compal -c 1003 /dev/ttyXXX

4. Now momentarily press the red power button on the phone.

If the phone has good boot code in it, you should be able to get in
this way; then just rerun flash erase and flash program-bin steps
starting at offset 0x10000 without touching the boot sector.  If the
above method still fails, then your phone is most likely unrecoverably
bricked, but just to be absolutely sure, repeat the above procedure
(including removing and reinsering the battery) with this debug
command instead of fc-loadtool:

fc-serterm /dev/ttyXXX 115200

When you press the red power button on the phone (after a freshly
reinserted battery) with the serial cable connected and this command
running, you should see what the phone's boot code emits on the serial
port on power-up, if anything.  Post the output to the list exactly as
it prints on your terminal (including all "garbage" characters), and I
might be able to tell if the phone is bricked or not, and how it may
have got into the bricked state.

M~