وستان کسی هست بتونه اینو ترجمه کنه..؟
Issue solved, here's how:
This guide applies to A820 only, for A820T you need the first firmware, flashtools and drivers - nothing else.
You also don't need to replace anything, just flash the special A820T firmware and you should be ready to go.
What you need:
1. Special A820T firmware, taken from lenovohome Chinese forum:
Dev-Host - A820t_repair_touchscreen_20130515.7z - The Ultimate Free File Hosting / File Sharing Service – I have uploaded it in my dev-host folder and removed password protection.
2. Any official A820 firmware, I have used S139 from needrom site:
ROM Lenovo A820 | [Official]-[Updated] add the 05/24/2013 on Needrom
3. FlashTools - the version included in A820T firmware
4. Ofcourse you need MTK drivers, but if you have flashed the wrong firmware first, then you should have them installed.
- Extract all archives into separate folders
- Load A820T scatter file in FlashTools, turn off the phone and leave battery in. Remove all SIM and external SD cards just for safety.
Now click on preloader (not on the checkbox, but on the name inside FlashTools) and a prompt will pop up.
Select the preloader from A820_S139 firmware (or from the version you chose on step 2). This step is necessary, because phone doesn't start with preloader from A820T.
Alternatively you can replace the preloader inside the A820T firmware folder.
Then hit Firmware->Upgrade and connect the phone to PC.
- After you see the green circle, try to power up the phone. I have tried it on two A820 phones. One of them booted into OS, the other one was stuck at Lenovo logo, but both worked after next step.
- Now turn off the phone again, load scatter file from A820_S139 (or from the version you chose on step 2) and flash the full firmware with Firmware->Upgrade. After that touchscreen should work normally.
Thanks to lenovohome Chinese forums and Russian lenovo-forums.ru. This wouldn't be possible without them.
Note: As I understood from other users, replacing the touchscreen also fixes the problem, so it seems the original assumption that something happens with the controller/drivers is correct.
However I can't explain why and what exactly goes wrong.
