Workaround for update.zip verification failure?

[Guest SmartSpook]

I've scoured the forum looking for a solution but cannot find one so am hoping a developer here has got a workaround to this problem.

I picked up a "cheap" Acer Liquid S100 from the world's favourite auction website that was listed as not booting properly.

Right enough it wasn't. It got past the boot splash and animation screens then played a boot jingle over and over again with the touchscreen buttons all illuminated but nothing showing on screen. Occasionally with several button presses it would show locale screen but I couldn't select any of the three options (English, Francais and a Chinese character) before it went black and into the boot jingle loop again.

OK so I thought I'd flash a ROM but unfortunately I can't get my computer to recognise the phone via USB using either the Acer A1 Tool (v3.1) or ADB. I've tried this on 3 PCs including one running XP and all had the correct Acer drivers installed. So I'm concluding that I can't flash it via a bin file.

It does boot into the recovery utility (3e) but every time I try to flash a ROM in update.zip format from the sdcard I get an "E:signature verification failed" error message which stops the update. I've tried as many ROMS as I can find for the Liquid in update.zip format including ones which are supposedly signed without any success. Would love to change to malez recovery but I need USB connectivity to do that...

So I've ran out of ideas and am asking for help. Has anyone come across this problem on the Liquid and found a solution? Can anyone advise what to try next to either circumvent the recovery signature check to either flash a ROM or a new recovery utility from the sdcard?

Here's hoping so. Cheers

[Guest zorginho]

install that drivers: http://www.megaupload.com/?d=AKCSL8WD

use that acer tool: http://www.megaupload.com/?d=EF2QNANO

follow that steps:

• download this: http://www.megaupload.com/?d=7WT2GIY5
  and unzip it.
• power off the phone with the pc cable unplugged.
• press volume up + camera button + power button
• you will hear two vibrations and nothing happen on display
• connect the usb cable and open the acer tool (with administrator rights)
• u will see that u're connected in amss mode, select a bin (i advice the 4.002.14), then click "Select file qcn file manually"
• click yes on the message
• wait until appears a new window, select the unzipped file desimlock.xml
• wait until the flash process ends.

[Guest SmartSpook]

Hi zorginho, thanks for the different approach but I still cannot get the A1 Tool to connect.

Followed the instructions to the letter;

Extracted and installed the USB drivers

Extracted the A1 Tool (it's identical to the one I have)

Added a BIN file to the Acer_A1_Bin folder

Did volume up + camera + power. Confirm I felt 2 vibrations and the screen was blank.

Connected USB cable

Executed A1 Tool as administrator; Device 01 shown as "Not Connected"

Could it be a driver issue - I doubt it. As I said I've tried the drivers & A1 Tool on 3 PCs. Plus I have several Android devices which connect without any problem at all.

Could it be a hardware fault with the USB on this mobile?

Is there another way without a USB connection that gets around the verification check?

[Guest zorginho]

the drivers needs to be installed with the phone unplugged.

try other usb ports or do the procedure on another pc, and u will have the liquid like a new one.

Edited September 26, 2011 by zorginho

[Guest SmartSpook]

the drivers needs to be installed with the phone unplugged.

try other usb ports or do the procedure on another pc, and u will have the liquid like a new one.

Thanks but they were installed with the phone unplugged on all three PCs I've tried this on. So while it may look like a new one it unfortunately still doesn't work like one. :(

[Guest zorginho]

:S maybe is damaged the phone usb... so i can't help u;

u need malez recovery to flash the .zip roms and if u can't boot and connect ur device u can't install it.

[Guest fear_factory84]

Using linux, what the dmesg says if you connect your phone to pc?

What does it write on dmesg in fastboot mode? and in recovery mode?

[Guest SmartSpook]

Using linux, what the dmesg says if you connect your phone to pc?

What does it write on dmesg in fastboot mode? and in recovery mode?

I don't currently have a PC running Linux. So what are you telling me? Is it worth installing Linux to find out what "dmesg" says when I connect the phone? Whatever "dmesg" means! Can you be a bit clearer? Feel free to use "noob speak" Thanks