thanks man but tell me please whats the best firmware for pov mobii please i cant fix it
Most touchscreen issue’s explained and the reason some touchscreens are dying on P10AN01’s (Advent Vega, Viewsonic 10s, Point Of View Mobii, ect)
Started by
richardmlea
, Jun 14 2012 09:26 AM
#41
Posted 17 September 2012 - 07:55 AM
#42
Posted 19 September 2012 - 01:07 PM
Many thanks for this. It worked for me. My screen FW was showing as "0"
#43
Posted 23 September 2012 - 03:56 PM
Hello,
Thanks for your work but I found some inconsistency...
I try to recover my tablet from the "bottom reverse scrolling problem and I could not get it work yet so I did some tests.
I found something out:
You wrote:
This is the latest fw for the A19 touchscreen and also works on the 101H too. Use this one to if your not sure.
https://dl.dropbox.c...7260_Config_MIL
https://dl.dropbox.c...ginal/it7260_FW
then you wrote:
This is the firmware from a similar tablet (DVC P10). It works (badly) on the P10AN01 but If you have flashed the latest 101H fw to an A19 touchscreen, flashing the correct firmware wont fix it (bottom half of the screen touches are reversed) you will need to flash this firmware first and then the original test rom, calibrate, flash the new test rom, install tputility2, flash correct firmware for your touchscreen and and then flash original test rom to calibrate.
https://dl.dropbox.c...7260_Config_MIL
https://dl.dropbox.c...��DVC/it7260_FW
The files did somehow match too exactly.
so I did a checksum (SHA1) on both Firmwares and detected, that they are identical
Firmware:
badd0751c543810ed450ede421f6df6e890166e2 *it7260_Config_MIL
1138a8e91758abe6704b3711f7f359cf0291004b *it7260_FW
"Revovery-Firmware:"
badd0751c543810ed450ede421f6df6e890166e2 *it7260_Config_MIL
1138a8e91758abe6704b3711f7f359cf0291004b *it7260_FW
So can you please reupload the original recoveryfirmware again?
thanks in advance.
Thanks for your work but I found some inconsistency...
I try to recover my tablet from the "bottom reverse scrolling problem and I could not get it work yet so I did some tests.
I found something out:
You wrote:
This is the latest fw for the A19 touchscreen and also works on the 101H too. Use this one to if your not sure.
https://dl.dropbox.c...7260_Config_MIL
https://dl.dropbox.c...ginal/it7260_FW
then you wrote:
This is the firmware from a similar tablet (DVC P10). It works (badly) on the P10AN01 but If you have flashed the latest 101H fw to an A19 touchscreen, flashing the correct firmware wont fix it (bottom half of the screen touches are reversed) you will need to flash this firmware first and then the original test rom, calibrate, flash the new test rom, install tputility2, flash correct firmware for your touchscreen and and then flash original test rom to calibrate.
https://dl.dropbox.c...7260_Config_MIL
https://dl.dropbox.c...��DVC/it7260_FW
The files did somehow match too exactly.
so I did a checksum (SHA1) on both Firmwares and detected, that they are identical
Firmware:
badd0751c543810ed450ede421f6df6e890166e2 *it7260_Config_MIL
1138a8e91758abe6704b3711f7f359cf0291004b *it7260_FW
"Revovery-Firmware:"
badd0751c543810ed450ede421f6df6e890166e2 *it7260_Config_MIL
1138a8e91758abe6704b3711f7f359cf0291004b *it7260_FW
So can you please reupload the original recoveryfirmware again?
thanks in advance.
Edited by devurandom, 23 September 2012 - 04:43 PM.
#44
Posted 02 October 2012 - 09:43 AM
Just posting to say THANK YOU! My touchscreen just died and got re-surrected following the guide here...
#45
Posted 13 October 2012 - 02:55 PM
A huge thanks Richard. The config files you posted worked a treat!
#46
Posted 15 October 2012 - 10:52 AM
as an update. the touchscreeñ works but is very sensitive
#47
Posted 24 October 2012 - 01:18 PM
Thanks a lot. You're a GREAT!!!
#48
Posted 11 November 2012 - 11:27 PM
Richard
Thank you so much for the post it has absolutely restored my touchscreen to full working order took a couple of flashes to achieve this but your instructions for completing this were top notch, once again thank you so very much
Thank you so much for the post it has absolutely restored my touchscreen to full working order took a couple of flashes to achieve this but your instructions for completing this were top notch, once again thank you so very much
#49
Posted 20 November 2012 - 01:20 AM
thanks for frimwares my touchscreen works now but it have a problem in bottom line ((( how else it can be fixed? i have pov mobii .thanks in advance
#50
Posted 30 December 2012 - 01:14 PM
Hi Richard
What a ton of work - but unfortunately my Viewpad 10s is now not booting.
I've used NVflash to flash 4 of the images linked to in this thread including the stock 20110411_v1.10.4_std_dev : after each one it starts up to the green Droid showing for ~2secs, then goes blank.
So I tried VGAfixer from http://www.modaco.co...is-will-fix-it/ .
and despite the bootloader.bin file in its folder its batch file readsthat it doesn't find it:
=======================================
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c108443fff2d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
(edited)
tools\H5PS1G83EFR-S6C_V24_0625.bct sent successfully
(edited)
tools\bootloader.bin sent successfully
(edited)
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
(edited out lots of success messages between these.....)
Formatting partition 11 UDA please wait.. done!
file not found: bootloader.bin
failed executing command 2147483647 NvError 0x4
command failure: create failed
Press enter to continue:
===================================================
Any clues in the above?
Viewpad screen stuck showing "Entering NVFlash recovery mode / Nv3p Server"
Newbie at this so please excuse if have missed the obvious ;-)
What a ton of work - but unfortunately my Viewpad 10s is now not booting.
I've used NVflash to flash 4 of the images linked to in this thread including the stock 20110411_v1.10.4_std_dev : after each one it starts up to the green Droid showing for ~2secs, then goes blank.
So I tried VGAfixer from http://www.modaco.co...is-will-fix-it/ .
and despite the bootloader.bin file in its folder its batch file readsthat it doesn't find it:
=======================================
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c108443fff2d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
(edited)
tools\H5PS1G83EFR-S6C_V24_0625.bct sent successfully
(edited)
tools\bootloader.bin sent successfully
(edited)
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
(edited out lots of success messages between these.....)
Formatting partition 11 UDA please wait.. done!
file not found: bootloader.bin
failed executing command 2147483647 NvError 0x4
command failure: create failed
Press enter to continue:
===================================================
Any clues in the above?
Viewpad screen stuck showing "Entering NVFlash recovery mode / Nv3p Server"
Newbie at this so please excuse if have missed the obvious ;-)
#51
Posted 01 January 2013 - 10:53 PM
Signed up just to say thanks for this topic - I'd bought a Vega on ebay back in April last year that I knew from the description simply had a bad ROM flash problem. Got that sorted a few minutes after receiving it but it had an unresponsive stripe in a perfect line about an inch wide from top to bottom right down the middle of the screen in portrait mode/across in landscape. I was convinced it was a physical fault - I'd tried all the ROMs available at the time and got nowhere with the shuttle tools or your other fixes - even tried the iron just in case it was a detachment problem. I was just about to order a bargain basement tablet on Amazon this morning then remembered the Vega sat in the drawer and thought I'd have one last search for repair tips and found this. Oddly, it didn't show any problem with the firmware for the touch screen - when I checked the TPUtility it showed a valid version 1.7.20.21 but after flashing to a different FW the dead stripe moved (ended up with the reversed strip issue). A few more tries with different FW and I ended up back on my original version numbers but everything working. Vega is now happily running VegaCream RC2 with no issues. (Apologies for the formatting, for some reason IE or the forum code isn't liking 'Enter'.
#52
Posted 09 January 2013 - 09:30 AM
The screen on my Vega has just become completely unresponsive, at what point in the steps in the OP would I find if I was going to get any response at all from the screen - in other words after running the tputility do I need to flash the next rom before getting any response or should I be able to get some sort of response even if not calibrated properly before that ?
Sorted
used the viewpad rom and the screen came back to life, flashed on a new rom and calibrated a few times and now works nicely.
Sorted
Edited by piran, 15 January 2013 - 08:56 PM.
#53
Posted 15 January 2013 - 10:27 AM
I need help.. ready to fleabay this or smash it up.
My 101H touchscreen as been playing up for months. Over sensitive in places, dead in others, double touches, ghost touches etc.... I've tried all the firmwares and whilst sometimes i can get the testrom (1.10.4) to work perfectly, as soon as i flash any other rom including the original advent one it just goes back to playing up..
Any help...
My 101H touchscreen as been playing up for months. Over sensitive in places, dead in others, double touches, ghost touches etc.... I've tried all the firmwares and whilst sometimes i can get the testrom (1.10.4) to work perfectly, as soon as i flash any other rom including the original advent one it just goes back to playing up..
Any help...
#54
Posted 23 January 2013 - 12:08 AM
I tried first one and it worked. You're lifesaver. Thanks a lot!
#55
Posted 07 March 2013 - 10:13 AM
#56
Posted 01 April 2013 - 02:34 AM
thank you- the instructions worked!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account
Back to top











