Bricked my Liquid, USB FastBoot driver failed

[Guest spraoi]

Hi,

I've bricked my Acer and I'm hoping for a little help to revive it please. I'm running Windows XP Professional Service Pack 3.

I was flashing it with the latest stock rom using the download tool from the Acer FTP and the USB Driver for the USB Fast Boot failed.

I've tried several times including with the older version of the download tool and the leaked ACER_Liquid_2.000.16_EMEA_GEN1 bin. I can't get the driver to work.

Any ideas?

Spraoi

Edited February 24, 2010 by spraoi

[Guest Shreedhan]

What happens when you open download tool, browse to latest .bin file then connect your liquid. Does the bar in the Acer Download Tool go green and say "connected" ?

[Guest spraoi]

I think I know why, I never downloaded the Android SDK. Fast boot relies on it?

[Guest spraoi]

What happens when you open download tool, browse to latest .bin file then connect your liquid. Does the bar in the Acer Download Tool go green and say "connected" ?

Yep. It actually seems to flash most of the files. Then it stops at one in particular and I get the error about the driver. I'm downloading the SDK at the minute. Will find out what file afterwards if that helps.

[Guest Shreedhan]

Silly question but have you installed the Acer liquid drivers?

[Guest spraoi]

Silly question but have you installed the Acer liquid drivers?

Yes. I tried installing on Vista too to try there but it says the install package is not valid.

[Guest spraoi]

Yes. I tried installing on Vista too to try there but it says the install package is not valid.

Here's my logs:

//=======================================================//

//================== Debug Log Start!! ==================//

//=======================================================//

[info] : Program version is : ACER Download Tool [intra][single] v3.100 (2009.10.27)

[Warning] : Process started in AMSS Download mode

[info] : Get AMSS Download Port Start!

[AMSS Port] : WaitTime is : 15

[AMSS Port] : Old vid and pid was NOT Found...

[AMSS Port] : acer vid and pid was Found

[AMSS Port] : AMSS Port is : COM56

[info] : Port for AMSS Download is : COM56

[info] : Beginning to Open AMSS COM Port : UsbConnect()

-----------------------------------------------------------

--------------- [info] : Hex file Start !! ----------------

-----------------------------------------------------------

[Hex] : Receiver thread is ready !

[Hex] : Transfer thread is ready !

[AMSS Port] : WaitTime is : 15

[AMSS Port] : Old vid and pid was NOT Found...

[AMSS Port] : acer vid and pid was Found

[AMSS Port] : AMSS Port is : COM56

-----------------------------------------------------------

------------- [info] : Hex file Finished !! ---------------

-----------------------------------------------------------

-----------------------------------------------------------

---------------- [info] : AMSS Start !! ------------------

-----------------------------------------------------------

[AMSS] : AMSS Receiver Ready !

[AMSS] : No matter the partition table is the same or diff, Restoration is always needed !

[AMSS] : AMSS Start !

-----------------------------------------------------------

--------------- [info] : AMSS Finished !! -----------------

-----------------------------------------------------------

[info] : Change mode Start! (AMSS Download to Fastboot mode)

[info] : Command is ready. (AMSS Download to Fastboot mode)

[info] : Close AMSS com port

[Guest spraoi]

It's quite late here and I've been working on this for hours. I've just tried it again to get more info.

The last step before fail was 'DSP 1'. It seems to have completed then the tool switches fastboot mode and the screen on the phone says usb_init. Thats when the driver fails.

[Guest Shreedhan]

Hmm, if it was a simple problem I would be able to help but I'm not an advanced modder :-(

All I can suggest is trying to uninstall drivers. Rebooting. Reinstall drivers. Then connect the liquid, let the system recognise it, when it says your hardware is ready to use, safely remove it. Then try flashing again.

[Guest designgears]

It sounds more like a windows issue to me

ftp://ftp.support.acer-euro.com/smartphon...re/AcerSync.zip

try those, and maybe on a different computer or do a fresh install of windows and try again.

[Guest symlink]

Hi,

I've bricked my Acer and I'm hoping for a little help to revive it please. I'm running Windows XP Professional Service Pack 3.

I was flashing it with the latest stock rom using the download tool from the Acer FTP and the USB Driver for the USB Fast Boot failed.

I've tried several times including with the older version of the download tool and the leaked ACER_Liquid_2.000.16_EMEA_GEN1 bin. I can't get the driver to work.

Any ideas?

Spraoi

Hi spraoi,

had a similar situation yesterday, I tried flashing the 2.1 LiquidE bin on a win7 system set up in a hurry.

I'm a linux user, and needed the win os just because of the .bin file and the A1 tool.

I never got the usb drivers work properly, at least the adb tool never listed my device.

But I got the A1 tool recognize my phone and so I stared flashing.

All went fine up to the point where the tool wanted to flash the extracted images.

My phone booted into fastboot mode (usb_init), but from there on nothing worked, the info field displayed error messages,

no connect, and that was it.

What I did then was flash the extracted .img files (boot, system, userdata, recovery) with fastboot in a shell.

And that did it - my phone is alive and well, and so far everything works.

I'm not sure of the risks in your case, but I think you don't have much to loose and you might want to try it that way.

[Guest krumbalu]

where can the extracted image files be found in order flash them manually??

[Guest spraoi]

I notice that my Huawei modem is acting funny. Is it possible there is a conflict between the drivers?

What I did then was flash the extracted .img files (boot, system, userdata, recovery) with fastboot in a shell.

And that did it - my phone is alive and well, and so far everything works.

Is there a documented process for doing this?

Edit: It's the Acer ADB Fastboot interface that's screwing up. I'll try and give a go from another windows based PC this evening or tomorrow.

Edited February 25, 2010 by spraoi

[Guest spraoi]

Don't the other flash methods require the ADB driver to work anyway?

[Guest symlink]

I notice that my Huawei modem is acting funny. Is it possible there is a conflict between the drivers?

Is there a documented process for doing this?

Edit: It's the Acer ADB Fastboot interface that's screwing up. I'll try and give a go from another windows based PC this evening or tomorrow.

No, there is nothing documented, I just gave it a try and it worked.

And then, "adb" and "fastboot" are two different tools. To flash a ".bin" file you don't need adb or the android sdk.

"adb" is usefull for other things, but to flash (like ".img" files) you need just "fastboot".

In my case the flashing part with the ACER Download Tool didn't work, I guess because of my faulty usb driver setup.

And I want to add that I switched back to linux to do the flash thing, just feels more comfortable.

But that shouldn't make a difference, the fastboot tool in windows and linux should do the same.

Here's my debug log file, take a look to see where I stopped... 0223_2227_39__COM10.txt

[Guest spraoi]

Thanks for your help folks. I installed Windows 7 on a spare laptop this morning and flashed it again. It's revived and running latest build. :(

Edited May 25, 2010 by spraoi

[Guest spraoi]

I'm running into problems again. I've recently installed Windows 7 Ultimate on my own laptop and attempted to upgrade to Android 2.1 using the Wiki instructions from the community ROM. I'm having the same issues again. This is bizarre because it's a completely new installation of Windows. Does my laptop just not want to work with the Fast USB driver?