Jump to content


Photo

[HOW TO's] Fix a non responsive touchscreen / wrongly calibrated touchscreen


  • Please log in to reply
45 replies to this topic

#1
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
Guide 1: This guide will help you solve your touch screen issue that was caused by a wrong calibration, a side affect of a rom flash, or other software issue

[YOU WILL NEED]

(1) A Windows PC
(2) ADB Installed http://theunlockr.co...ndroid-devices/
(3) A USB Mouse ( Some lazer mouse's do not work )
(4) A USB to USB Cable ( Included with the Vega)
(5) Audi: http://android.modac...iver-installer/
(5) moded stock rom by newb5: http://android.modac...ddedstock-1-10/
(6) vegacomb rom ( or any other rom with mouse support) on your vegas sd card http://android.modac...nd-teamvillain/


[ STEPS]

1: Use Audi to remove any previous drivers for the Vega & install the drivers you will be needing (modaco drivers)

2: Put your Vega in recovery mode: hold down power button for 6 seconds until the Vega switches off, Hold in the back button for 2 seconds, hold in the power button for 2 seconds ( whilst keeping back button pressed), release the power button then after 2 seconds release the back button and plug your Vega into your PC (if it isn't already)

3: Launch Newbe5 moded stock rom flasher (VegaModdedStock_v1.10.exe ) and wait for it to finish.

4: Your Vega should now have newbe5 modded rom installed, power on your Vega and wait till you see USB debugging icon in your notification bar, then use adb to reboot into recovery using this comand. adb shell reboot recovery_2

4.a : Plug your USB mouse into your Vega

5: In clockworkmod recovery wipe data & cache + dalvic cache from the advanced section then select install rom from sdcard & select the Vegacomb rom you previously placed on your sdcard

6: When clockworkmod has finished installing the rom go back and select reboot device, from the moment clockworkmod exits...

6.a : hold in back button until you reach the vegacomb lockscreen or home screen, your mouse should now be functional... select apps from the top right corner and launch the touchsceen calibration app then select calibrate touchscreen DO NOT TOUCH THE SCREEN AT ALL DURING THE PROCESS

Your touch screen should now be fully functional!

If you already had vegacomb installed when your touch screen messed up you should just hold in the power button until the Vega completly switches off and start from ' 6.a '



Guide 2: This guide will help you recover from a bricked or bootlooping vega, This guide can also be used to help you install a rom on your Vega for the first time, or to upgrade your system partition for vegacomb 1.7+up



[YOU WILL NEED]

(1) A Windows PC
(2) A USB to USB Cable ( included with your Vega)
(3) Audi: http://android.modac...iver-installer/
(4) moded stock rom by newb5: http://android.modac...ddedstock-1-10/
(5) A rom of your choice placed on your vegas memory card

[ STEPS]

1: Use Audi to remove any previous drivers for the Vega & install the drivers you will be needing (modaco drivers)

2: Put your Vega in recovery mode: hold down power button for 6 seconds until the Vega switches off, Hold in the back button for 2 seconds, hold in the power button for 2 seconds ( whilst keeping back button pressed), release the power button then after 2 seconds release the back button and plug your Vega into your PC (if it isn't already)

3: Launch Newbe5 moded stock rom flasher (VegaModdedStock_v1.10.exe ) and wait for it to finish.

4: Your Vega should now have newbe5 modded rom installed, Power on your Vega and finish the first time setup, you will now have an app in your app draw called reboot recovery.. use this to boot into clockworkmod

5: In clockworkmod recovery wipe data & cache + dalvic cache from the advanced section then select install rom from sdcard & select the rom you previously placed on your sdcard

6: Wait for clockworkmod to finish installing your rom, then select reboot device.

Your Vega should now be unbricked!... if you cannot get your Vega into recovey mode it has been suggested that some devices need to be plugged into the mains power.

Edited by SWOriginal, 09 July 2011 - 11:51 PM.

  • 0

#2
simonta

simonta

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,298 posts
  • Gender:Male
  • Location:Southampton
  • Devices:Vega. HTC Desire
adb shell reboot recovery

  • 0
If I've helped you, you want to say "thanks" and you do not use Dropbox (it's enormously useful, especially with mobile devices), please consider signing up for it using my reference. You'll get 2GB of disk space for files available anywhere, any time on any device. They give us both an extra 250MB if you do sign up!

Sign up for Dropbox

Apple? I'd rather eat my own kidneys!

#3
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
thanks for the command... the only problem is i dont have adb installed to use it.. tried using the adb-windows.exe in pauls rom folder but it scrolls through all the txt and then closes (windows xp). is there a guide or something i can follow without downloading the whole sdk?

  • 0

#4
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
got adb working but now when i enter "adb shell reboot recovery" it just reboots the device as normal, ive installed pauls clockworkmod using vegatools but it still does it

  • 0

#5
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
anyone know what file the calibration app creates and where and could you share your calibration file

  • 0

#6
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
seriously guys i need help here :), is there a way to flash a normal rom through adb like vegacomb?

  • 0

#7
dibbles

dibbles

    Addict

  • Members
  • PipPipPipPipPip
  • 812 posts
  • Gender:Male
  • Location:Earth, for now
  • Interests:Life and family :)
  • Devices:Moto G Excite Pro Nexus 7
Can you not just use the Vegatools to update the ROM on the device, under the Recovery tab...?

I know that you installed Paul's ROM (not sure which stock version you are referring to) but maybe using the Vegatools to download and install the official 1.10 ROM might be helpful..?

When I was in similar situation as yourself I found that my issue was that somehow CWM wasn't "correctly" installed as it would not boot into recovery until I then reinstalled it.

I used the file recovery_vega_3028_easyinst_donotflash for the latest version of CWM.

http://android.modac...asy-install-v2/

Edited by dibbles, 06 July 2011 - 12:53 PM.

  • 0

#8
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
i used vegatools to flash pauls rom and the stock rom from advent.. both booted without touchscreen working.

i think the flashing of both roms is leaving the wrong calibrated file behind so i just need to know where that file is and replace it with someones whos works ( im hoping thats all i need )

  • 0

#9
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
i just manually flash clockwork mod from the modaco rom thread and its still not booting into recovery.. someone help!

  • 0

#10
scumball

scumball

    Regular

  • Members
  • PipPip
  • 81 posts
  • Devices:Advent Vega

i just manually flash clockwork mod from the modaco rom thread and its still not booting into recovery.. someone help!


Use the VEGA Stock 1.10 ROM install and start again?

  • 0

#11
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
Tried tha didnt work. Convinced its a hardware issue now (somehow brought on by the calibration app)tphoned currys for repair now.. don't know how im going to manage without it :)

  • 0

#12
simonta

simonta

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,298 posts
  • Gender:Male
  • Location:Southampton
  • Devices:Vega. HTC Desire

thanks for the command... the only problem is i dont have adb installed to use it.. tried using the adb-windows.exe in pauls rom folder but it scrolls through all the txt and then closes (windows xp). is there a guide or something i can follow without downloading the whole sdk?


adb-windows.exe is just a renamed copy of adb.exe. Try this:

adb devices

What happens?

  • 0
If I've helped you, you want to say "thanks" and you do not use Dropbox (it's enormously useful, especially with mobile devices), please consider signing up for it using my reference. You'll get 2GB of disk space for files available anywhere, any time on any device. They give us both an extra 250MB if you do sign up!

Sign up for Dropbox

Apple? I'd rather eat my own kidneys!

#13
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal

adb-windows.exe is just a renamed copy of adb.exe. Try this:

adb devices

What happens?

I got adb working in the end (that's how I manually flashed clockworkmod) , the problem is that It refused to reboot into clockwork, when using adb reboot recovery or adding shell after adb the Vega would just do a normal reboot. I flashed the stock rom from The advent Vega site and then flashed clockwork through adb and that still resulted in a normal reboot. Paul's modaco rom also done a normal reboot.. its truely a brick

  • 0

#14
tarling

tarling

    Newbie

  • MoDaCo Silver
  • Pip
  • 13 posts
  • Devices:Vega

I got adb working in the end (that's how I manually flashed clockworkmod) , the problem is that It refused to reboot into clockwork, when using adb reboot recovery or adding shell after adb the Vega would just do a normal reboot. I flashed the stock rom from The advent Vega site and then flashed clockwork through adb and that still resulted in a normal reboot. Paul's modaco rom also done a normal reboot.. its truely a brick


Hi,

Not sure if this is same issue, but take a look at:
http://android.modac...-vega-unusable/

HTH,
J

  • 0

#15
simonta

simonta

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,298 posts
  • Gender:Male
  • Location:Southampton
  • Devices:Vega. HTC Desire

I got adb working in the end (that's how I manually flashed clockworkmod) , the problem is that It refused to reboot into clockwork, when using adb reboot recovery or adding shell after adb the Vega would just do a normal reboot. I flashed the stock rom from The advent Vega site and then flashed clockwork through adb and that still resulted in a normal reboot. Paul's modaco rom also done a normal reboot.. its truely a brick


Sorry, my mistake. try

adb shell reboot recovery_2

or

adb shell recovery_2 && reboot

Plus, the Vega is never a brick. You can always get to recovery (not clockworkmod - see myadventvega) and reinstall the stock ROM.

  • 0
If I've helped you, you want to say "thanks" and you do not use Dropbox (it's enormously useful, especially with mobile devices), please consider signing up for it using my reference. You'll get 2GB of disk space for files available anywhere, any time on any device. They give us both an extra 250MB if you do sign up!

Sign up for Dropbox

Apple? I'd rather eat my own kidneys!

#16
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
THANKS FOR THE HELP GUYS! THE VEGA Is TRUELY UNBRICKABLE!!

Now time to let pcworld know ive fixed it :)

  • 0

#17
dibbles

dibbles

    Addict

  • Members
  • PipPipPipPipPip
  • 812 posts
  • Gender:Male
  • Location:Earth, for now
  • Interests:Life and family :)
  • Devices:Moto G Excite Pro Nexus 7
Well done on the fix, and for those who helped.

Even more well done on posting back how you did resolve it so that it could help others unfortunate enough to be in a similar situation :)

  • 0

#18
dibbles

dibbles

    Addict

  • Members
  • PipPipPipPipPip
  • 812 posts
  • Gender:Male
  • Location:Earth, for now
  • Interests:Life and family :)
  • Devices:Moto G Excite Pro Nexus 7
I never thought that I would need this thread but for the first time my Vega lost the use of the touchscreen. This was after using the latest VegaComb 1.7 but NOT using the calibration tool. It simply stopped working after booting it up after previously being ok.

Using ADB I booted into recovery and wiped everything and, for now maybe, I simply restored my previous nandroid of CM 7 (done just prior to the VegaComb 1.7 install).

Hopefully this experience was just due to the VegaComb install as it had never happened previously. Not sure why it did though...?

Thanks again to the OP for the first post containing a solution.

  • 0

#19
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal

I never thought that I would need this thread but for the first time my Vega lost the use of the touchscreen. This was after using the latest VegaComb 1.7 but NOT using the calibration tool. It simply stopped working after booting it up .

Thanks again to the OP for the first post containing a solution.

that's OK, I think I should rewrite the solution as Richard (newbe5) has provided us with a stock rom with clockwork already installed so we can cut out a few steps.. I'll get to it now :blink:

  • 0

#20
SWOriginal

SWOriginal

    Diehard

  • Members
  • PipPipPipPip
  • 341 posts
  • Location:Essex, London
  • Devices:ZTE Blade, Advent Vega
  • Twitter:@@SW0riginal
Guide updated! Hopefully its allot easier to understand now

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users