Jump to content

Faulty bootloader and recovery


Recommended Posts

Guest Richard Högberg
Posted (edited)

Hi!

I was going to move on to froyo and had to downgrade to the 2.000.016 firmware but the flash timed out several times and finally the boot and recovery writings became faulty, so now i'm sitting with an checksum error on both boot and recovery. Is there any way to force a flash? Or is a service the only way out?

Splashscreen and system partition check sums are okay!

EDIT: Okey, so now i've successfully flashed it, or at least the system partition became installed. But everytime i flash the acer flash tool times out during fastboot, always during verifying /system. Any one else with this problem?!

Edited by Richard Högberg
Guest fantong
Posted

try to replace a better usb cable first,I think

Guest G_Technik
Posted
EDIT: Okey, so now i've successfully flashed it, or at least the system partition became installed. But everytime i flash the acer flash tool times out during fastboot, always during verifying /system. Any one else with this problem?!

Check drivers.

There should be no unknown or uncorrectly installed devices.

Guest Richard Högberg
Posted
Check drivers.

There should be no unknown or uncorrectly installed devices.

There was no incorrectly installed drivers. I've flashed the phone tons of times but the latest it has only given me a wrong flash, always during the verifying process in fastboot. Anyhow, the phone works now and is running Froyo.

Next problem though; Why doesn't it clock up to 998MHz? Of course i've flashed the boot.oc.img but it only clocks up to 768? I have no crashes or anything, it just doesn't clock up?

Guest xedamen
Posted

I have a same problem. I had to downgrade to 2.000.016 firmware, but now the flashboot doesn't work. If i connect the phone in normal boot, run the command, and it's writing "device not found" I uninstalled all programs and driver of acer, reinstall all, but the problem is the same. Any idea?

Guest G_Technik
Posted

Oh, guys, I forgot!!!

Seems the problem is in Acer DownLoad Tool. After 3.1 version it doesn't let to DOWNGRADE!

To downgrade you should use ADT 3.1

Guest xedamen
Posted
Oh, guys, I forgot!!!

Seems the problem is in Acer DownLoad Tool. After 3.1 version it doesn't let to DOWNGRADE!

To downgrade you should use ADT 3.1

I have 3.1, and it let to downgrade, but the fastboot doesn't work.... The fastboot doesn't see the phone, and if i try the "usb-remove battery ....."mode, the phone only switch on...

Guest G_Technik
Posted
I have 3.1, and it let to downgrade, but the fastboot doesn't work.... The fastboot doesn't see the phone, and if i try the "usb-remove battery ....."mode, the phone only switch on...

Try to off the phone and push volume UP+camera+power buttons and after this plug USB-cabel.

Acer DTool should see it then.

Guest xedamen
Posted (edited)
Try to off the phone and push volume UP+camera+power buttons and after this plug USB-cabel.

Acer DTool should see it then.

Acer Dtools see the phone... adb doesn't find the device...

Edited by xedamen
Guest G_Technik
Posted
Acer Dtools see the phone... adb doesn't find the device...

If ADTools sees phone why don't you flash 2.000.16.bin by it&

Why are you using adb?

Guest Richard Högberg
Posted

It seems like it is some kind of timer that times out beacause the phone takes too long to verify the /system partition or something.

Guest xedamen
Posted (edited)
If ADTools sees phone why don't you flash 2.000.16.bin by it&

Why are you using adb?

Does it include the root? Where can I find it ?

Edited by xedamen
Guest G_Technik
Posted
Does it include the root? Where can I find it ?

It doesn't include root, it's just a stock rom. Here it is. After you flash it you can try to flash malezRecovery and get root there.

Guest xedamen
Posted

Now, I'm very angry. I downloaded the firmware, that you linked, downloaded the Acer DTools 3.1, fleshed the firmware, after it I opened cmd: cd C:\android-sdk-windows\tools it was okey, but when i wrote : adb reboot bootloader it started daemon, but "device not found". I tried it so many times... I tried it by usb, remove battery, reinstall battery when the battery icon shown, press the power button while I holding camera key, but it just only switch on. I could root already. But now I don't understand it... Any idea?

Guest B4rt
Posted
Now, I'm very angry. I downloaded the firmware, that you linked, downloaded the Acer DTools 3.1, fleshed the firmware, after it I opened cmd: cd C:\android-sdk-windows\tools it was okey, but when i wrote : adb reboot bootloader it started daemon, but "device not found". I tried it so many times... I tried it by usb, remove battery, reinstall battery when the battery icon shown, press the power button while I holding camera key, but it just only switch on. I could root already. But now I don't understand it... Any idea?

Did you turn on usb debugging on the phone. Without that adb wont recognise your phone

Guest xedamen
Posted (edited)
Did you turn on usb debugging on the phone. Without that adb wont recognise your phone

I love you, I love you, I love you :) Thank you very much :) I know it at my last root, but now... :) This problem is worked out, but now I have another problem:

I'm using the 2.00.16 EMEA GEN1... But when i want to flash zip from sd (no sign check) It started the install, but "Aborted" Umount all FS in the main menu, I umounted it, but the problem is the same. The phone is not the best, with this firmware (1.6) LoL Any idea?

Edited by xedamen
Guest xedamen
Posted (edited)

Any idea? Sorry for the double post, but I must to go work, and my phone has 1.6, it's really bad.

Edited by xedamen
Guest B4rt
Posted
Any idea? Sorry for the double post, but I must to go work, and my phone has 1.6, it's really bad.

Sorry not sure what you are trying to do.

Could you please explain what exactly to you are trying to achieve?

Guest xedamen
Posted
Sorry not sure what you are trying to do.

Could you please explain what exactly to you are trying to achieve?

Now, it works. The problem was with the zip. I downloaded again, and now it's working :) Thanks

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.