Polaroid PMID702c & PMIC703 CM10 Jelly Bean Compatibility

[[email protected]]

I am using the stock ROM I downloaded from Momo.
Yes livesuite is working. It asks me to format and I say yes. ROM flashes and tablet boots fine. Just no touch screen now.

ADB is not enabled by default and since the screen is not working now, I cannot turn it on.
I just edited default.prop and added:
persist.service.adb.enable=1

Still no go, ADB is not on after flashing.

I think I need to ERASE ROM or something but without ADB I am stuck.


Bob

Sorry I thought the device didn't boot did you verify you download the correct firmware. Is this an a10 or a13? Usb2go addaptor to add a mouse and keyboard. Adb is normally enabled for the first few moments of boot do adb wait for device and maniually reboot

[Finless]

It's an A10. I just edited build.prop as it has ADB=0 in it.
Just made a new system and will see if it boots with ADB on now.

So let me ask. How do I recover the touch screen?
Will the erase ROM script do it?

Bob

[Finless]

OK I have ADB up now on boot. Sheesh....

Using a mouse I was able to reboot into recovery.
I erased cache and then did a erase factory reset.

I still have no touch screen

There must be something I am missing. I think the kernel that was in the polaroid recovery somehow uncalibrated the hardware. I cant believe there is not a way to recovery from this?

Any ideas?

Bob

[Finless]

Thats what it is. My screen is no longer calibrated!
In developer options I turned on show pointer location. Touch screen is WAY OFF.

There must be a way to fully reset this thing?

Bob

[Finless]

So Allwinner is not fully recoverable. My touch screen only works now in the lower right 1/4 of the screen. Hard to believe a simple recovery flash screwed it up.

I have tried everything I can think of to get it back including 3 different versions of the stock ROM from Ployer. I cant be the first person this has happened to? There must be a way to reset the thing.
It does have a reset pinhole on the unit but I have tried all kinds of patterns with it and buttons to see if there is a "magic" reset.

So unlike RockChip and AMLogic which can always be recovered 100% from a bad flash, it seems AllWinner is not that way. So I just ate $125 bucks

I havent gevin up yet looking for a solution but after hours of searching the web not much comes up for calibration, etc.

Bob

[JonChance]

Bob;

just for S and G's have you installed the cm9 for the 702c ? in that process is a wipe-rom zip. In theory it should reformat the entire flash area except for the boot nand. from there you should have a "clean slate" and eliminate the possibility of left overs from other rom installs. I have the 703c and have had my series of unfortunate experiments including a USB cable becoming undone from the computer during mid flash. I have always managed to reflash the device with out a hitch. Granted some of the reflashing sessions have taken me several hours to get the device to FEL mode, that was mostly due to OE ( op Error) and not the device.

One experience I had was the DCpad 2121 firmware managed to boot for the first time lost the touchscreen and rebooted. then it went into a bootloop. I recovered from that with a 3 tap of the reset button and a reflash of the stock firmware.

This may be just a babble or it may help... Your mileage may vary

[[email protected]]

So Allwinner is not fully recoverable. My touch screen only works now in the lower right 1/4 of the screen. Hard to believe a simple recovery flash screwed it up.

I have tried everything I can think of to get it back including 3 different versions of the stock ROM from Ployer. I cant be the first person this has happened to? There must be a way to reset the thing.
It does have a reset pinhole on the unit but I have tried all kinds of patterns with it and buttons to see if there is a "magic" reset.

So unlike RockChip and AMLogic which can always be recovered 100% from a bad flash, it seems AllWinner is not that way. So I just ate $125 bucks

I havent gevin up yet looking for a solution but after hours of searching the web not much comes up for calibration, etc.

Bob

Please post your full model and the actual part number of your device and ill do some digging, this isn't a rezistive touch screen based devices is it, I would have to suspect that maybe the real firmware for your device might not be out. With the captive based devices screen mapping is handled through uboot nanda partition if someone with this device could do a dump of that nanda from a fresh out of box unit should be able to flash just that partition back with dd command, I should be able to post a batch file that some one could run and dump all the nand partitions and rebuild the shipped with Tom from that. In 10 allwinner devices I've worked with I've never not been able to restore to fictional. Post model and full part number we will go from there.

[Finless]

It's a Ployer MOMO 8 Birdie. AllWinner A10.

Here is a link to the site. Yes it is in Chinese so use google translate:

http://www.ployer.cn/prshow.asp?id=125

Transalted:

http://translate.google.com/translate?hl=en&sl=zh-CN&tl=en&u=http%3A%2F%2Fwww.ployer.cn

English site but has less info:

http://en.ployer.cn/mid_detail.php?id=9

Yes there is official ROMs. I have downloaded them all and tried them all.

I have no issues getting into flash mode with LiveSuite. Power the tablet off. Hold volume + and power. When windows bongs, hit the power button about 7 times and lives suite recognizes it and asks if you wan to format.

After doing some research it "appears" that the polaroid recovery somehow told the screen it was IPS or vise versa. See this post as all I could find:

http://www.slatedroid.com/topic/29480-help-me-please-touch-screen-problem-flash-issue/page__st__20

On post #15, the guys says
this occurs when a firmware for ips screen tablet (eg ainol aurora) is flashed on a tablet which does not have ips screen .
Then a white screen appears on the tablet and some thin coloured lines on the tablet divides the tablet vertically into 3 parts
like
! 1 ! 2 ! 3 !
And then if we flash the stock rom again (everything works normally except touch)

I tried the momo9 touch_fix and the other one. Just bricks the tab and I have to reflash the stock ROM again.

JonChance, I have done the wipe. Still no go. No matter what ROM I put on the thing the touch screen is jacked up.

So if the IPS screen thing is correct maybe there is a tool out there to reprogram the chip?
Or I take the damn thing apart and disconnect the battery and see if I can reset it.


Bob

[Finless]

Well for sure it maybe the MOMO ROM is not setting something. I have made some progress.
Before only the lower left 1/4 of the screen responded to touch. Like it thought it was a phone small screen or something.

After flashing a few other ROMs for other devices (not sure which did it), now the entire screen works but it is off. The upper left corner is right on but as I move to the lower right corner it gets off. Like it thinks the touch screen is smaller than it is.

So now... to try and find a ROM that will set the hardware and has the same screen.

At least I am getting closer to fixing this!

Bob

[onef]

Digging a bit on this. Don't know if you have seen this or not. (Interesting beast the touch screen.)

http://linux-sunxi.org/LY-F1

FT5X touchscreen issues

If you flash your LY-F1 with firmware from branded clone (Texet, explay, onda & etc.) or vice versa, you will get your FT5X touchscreen EEPROM empty. Log:

< SEE SITE FOR LISTING >

==ft5x_ts_probe over = This will lead complete zero response from touchscreen. Only way to fix this is to flash different firmware to your FT5X. Files and simple .bat script can be found in this archive.

This would imply that the configurations are complied into the .ko.

Here is the the C-code for it. Don't know if it is the real stuff. but comparing the strings out and the .ko it looks similar.

http://pastebin.com/DnYnu54Z

Once it boots up and you are about to get the text console do a dmesg and does it look like this? This is from a working Polaroid 703c. Just curious as to what you have in the dmesg when it boots up.

<6>[ 4.970000] ===========================ft5x_ts_init=========== ==========
<6>[ 4.980000] ctp_fetch_sysconfig_para.
<6>[ 4.980000] ctp_fetch_sysconfig_para: after: ctp_twi_addr is 0x38, dirty_addr_buf: 0x38. dirty_addr_buf[1]: 0xfffe
<6>[ 4.990000] ctp_fetch_sysconfig_para: ctp_twi_id is 1.
<6>[ 5.000000] ctp_fetch_sysconfig_para: screen_max_x = 800.
<6>[ 5.000000] ctp_fetch_sysconfig_para: screen_max_y = 480.
<6>[ 5.010000] ctp_fetch_sysconfig_para: revert_x_flag = 0.
<6>[ 5.020000] ctp_fetch_sysconfig_para: revert_y_flag = 0.
<6>[ 5.020000] ctp_fetch_sysconfig_para: exchange_x_y_flag = 0.

[Finless]

THIs is what I get there and my screen res seems correct?

<6>[ 6.029196] ===========================ft5x_ts_init=========== ==========
<6>[ 6.036025] ft5x_ts VERSION =Rocky@[email protected]
<7>[ 6.041133] m_inet_ctpState return false,continue deteck
<6>[ 6.046608] ctp_fetch_sysconfig_para.
<6>[ 6.050430] ctp_fetch_sysconfig_para: after: ctp_twi_addr is 0x38, dirty_a
ddr_buf: 0x38. dirty_addr_buf[1]: 0xfffe
<6>[ 6.061190] ctp_fetch_sysconfig_para: ctp_twi_id is 2.
<6>[ 6.066464] ctp_fetch_sysconfig_para: screen_max_x = 1024.
<6>[ 6.072138] ctp_fetch_sysconfig_para: screen_max_y = 768.
<6>[ 6.077653] ctp_fetch_sysconfig_para: revert_x_flag = 0.
<6>[ 6.083117] ctp_fetch_sysconfig_para: revert_y_flag = 0.
<6>[ 6.088538] ctp_fetch_sysconfig_para: exchange_x_y_flag = 0.
<6>[ 6.094366] ctp_fetch_sysconfig_para: screen_rotate_flag = 0.
<3>[ 6.100253] ft5x_ts: script_parser_fetch err.
<6>[ 6.104721] ctp_fetch_sysconfig_para: minetPowerEnreserver = 0.
<7>[ 6.110772] script parser fetch err.
<4>[ 6.114461] touch panel tp_en request gpio fail!
<6>[ 6.119102] ft5x_ts_init: after fetch_sysconfig_para: normal_i2c: 0x38. n
ormal_i2c[1]: 0xfffe
<7>[ 6.127870] script parser fetch err.
<4>[ 6.131594] ctp_init_platform_resource: tp_reset request gpio fail!
<6>[ 6.137882] ctp_wakeup.
<6>[ 6.298315] ctp_detect: Detected chip ft5x_ts at adapter 2, address 0x38
<6>[ 6.305328] ====ft5x_ts_probe begin=====.
<7>[ 6.309554] I2C communication client->addr=56
<7>[ 6.509443] [AXP]battery state change
<7>[ 6.514941] charger->usb_valid = 1
<7>[ 6.518408] [AXP]event = 0x400
<7>[ 6.820482] ft5x06 Chip ID=0x79
<7>[ 6.823638] I2C communication ok
<6>[ 6.827901] input: ft5x_ts as /devices/virtual/input/input2
<6>[ 6.834333] ==register_early_suspend =
<6>[ 6.838123] CONFIG_FT5X0X_MULTITOUCH is defined.
<6>[ 6.842897] ctp_set_irq_mode: config gpio to int mode.
<6>[ 6.848174] INTERRUPT CONFIG
<6>[ 6.851691] ==ft5x_ts_probe over =
<6>[ 6.855274] init: command 'insmod' r=0
<7>[ 7.526315] [AXP]battery state change
<7>[ 7.531792] charger->usb_valid = 1
<7>[ 7.535228] [AXP]event = 0x400
<7>[ 8.671467] [AXP]battery state change
<7>[ 8.676927] charger->usb_valid = 1
<7>[ 8.680384] [AXP]event = 0x400

[Finless]

Some other interesting things from dmesg

<7>[ 8.770604] ===========================goodix_ts_init========= ============

<7>[ 8.777495] goodix_ts VERSION =Rocky@inet@20120207
<7>[ 8.782371] m_inet_ctpState return true,just return
<6>[ 8.787811] init: command 'insmod' r=-1
<7>[ 8.815423] HA2608 i2c touch panel device driver module init
<6>[ 8.821253] ite_ts_init VERSION =Rocky@[email protected]
<6>[ 8.827215] init: command 'insmod' r=-1
<6>[ 8.864462] SSL Touchscreen driver, (c) 2011 Solomon Systech Ltd.
<7>[ 8.870705] ==================ssd253x_ts_init================= ==========
<7>[ 8.877442] Inet Version =ssd253x_20120519.1618_Rocky@inet
<7>[ 8.883009] m_inet_ctpState return true,just return
<6>[ 8.888445] init: command 'insmod' r=-1
<6>[ 8.917466] =====================================Novatek_Touch Driver======
==========================
<6>[ 8.926709] Novatek_TouchDriver VERSION =Rocky@inet Novatek_TouchDriver_20
120412.1417
<7>[ 8.934618] m_inet_ctpState return true,just return
<6>[ 8.940149] init: command 'insmod' r=-1
<7>[ 8.974249] goodix_touch_3F goodix_ts_init @20120306 m_inet_ctpState retur
n true,just return
<6>[ 8.988230] init: command 'insmod' r=-1
<7>[ 9.017461] **********************gt82x init************************
<7>[ 9.023971] gt82x VERSION =Rocky@inet@gt82x@20120614_2020
<7>[ 9.029399] m_inet_ctpState return true,just return
<6>[ 9.034847] init: command 'insmod' r=-1
<7>[ 9.071137] **********************gt811 init************************
<7>[ 9.077511] gt811 VERSION =Jicky@inet@gt811@20120614
<7>[ 9.082797] m_inet_ctpState return true,just return
<6>[ 9.088238] init: command 'insmod' r=-1
<7>[ 9.110911] sun4i-ts.c: sun4i_ts_init: start ...
<7>[ 9.115585] rtp_used == 0.
<6>[ 9.118841] init: command 'insmod' r=-1
<6>[ 9.122899] init: command 'insmod' r=-1
<7>[ 9.202875] UMP<2>: Inserting UMP device driver. Compiled: Jun 14 2012, ti
me: 23:34:30
<7>[ 9.221517] UMP<2>: Using OS memory backend, allocation limit: 134217728
<7>[ 9.228346] UMP: UMP device driver loaded
<6>[ 9.232769] init: command 'insmod' r=0
<7>[ 9.360077] set usbcur 0 mA
<7>[ 9.363159] set usbvol 4000 mV
<7>[ 9.512325] Mali: Mali device driver loaded
<6>[ 9.517031] init: command 'insmod' r=0
<7>[ 9.570556] ========gsensor_fetch_sysconfig_para============== =====

[[email protected]]

POLAROID PMID701 series CM9, AOKP, CM10

CM9 / AOKP / CM10 compatibility trials see link below:

http://www.freaktab.com/showthread.php?1543-Polariod-PMID701i-PMID701i_10-PMID701_x10-PMID701c-CM9-AOKP-CM10-compatibility

[Finless]

More progress being made I think.

So the momo8 kernel will not wirte the FT5x firmware to the screen EEPROM.
Dmesg shows update=0 every time.

But the Plaroid kernel does and because there was no "firmware" in /vendor/firmware it erased my EEPROM.
But somewhere along the line I flashed a ROM that did update the EEPROM but to a 800x600 touch screen. Mine is a 1024x768 touch screen. So the screen got working but it's not right.

Needless to say I am now trying to find a kernel that will boot and will allow flashing of the Eprom. I think I found the Eprom firmware I need. Now it's just messing around until I can make that happen.

What a mess honestly... I have spent 2 days trying to fix my screen

Let that be a lesson to people that flash something they shouldnt!

Bob

[Finless]

NAILED IT!

Sorry to derail your thread William but you guys are the most knowledgable when ity comes to ALLWinner. But I fixed it!

BUT... Hopefully this infor will help people that screw up thier FocalTech screen chip like I did.

First you have to find a ft5x_ts.ko module that supports writing to the EEPROM for the screen chip. My MOMO8 ft5x_ts.ko did not. This was why I could never fix it!
You will know if your KO module supports that by seeing this line in the dmesg under
=============ft5x_ts_init=============
ctp_fetch_sysconfig_para: script_parser_fetch firmware_upgrade_used = 0

If you do not see that line, your KO module does not support flashing the touch driver EEPROM.


OK so once you have found a KO that works, then we have to do more work!
We have to mod script.bin (sysconfig1.fex) in bootfs. You actually have to get the linux tools bin2fex and fex2bin. You will take script.bin from bootfs and use fex2bin to convert it to editable text.
Then you will go to the CTP section under [ctp_para]. There you will see something like this:
ctp_int_port = port:PH21<6><default><default><default>
ctp_wakeup = port:PB13<1><default><default><1>
ctp_io_port = port:PH21<0><default><default><default>
We need to tell the script we want to program the EEPROM and we will ADD these 2 lines.
ctp_upgrade_used = 1
ctp_firmware_name = "ft5x_newfw"
Please note, the firmware name you use here must be used in the ADB commands below! You can use whatever name you like but it needs to be whats is used below.
Now use fex2bin and make a new script.bin

OK getting closer.... Now we need to actually FIND the required EEPROM firmware. This was a MAJOR pain in the butt. Only site I found it on was Chinese web sites. But I found a RAR file containing many different firmwares. I am not even sure this contains ALL of them but it had the one I needed.
I have uploaded the firmware files to FreakTab here:
http://video.freaktab.com/?subpath=f...x_firmware.zip

Now you just have to figure out which firmware is for your chip. The files have a resolution in the name so that helps. However I had to do this several times to find my correct version.


OK now that you have a KO file that supports programming the EEPROM, you have a firmware file, and you have a modified script.bin, we can go to town with ADB and get the screen fixed!
For this example we have these files:
ft5x_ts.ko
script.bin
and the firmware file which for me was: ft5406-sc3052-1024X768.bin

In Windows fire up a command shell or you can script this as a .bat file. We will do the following:

adb remount
adb shell cd /
adb shell mount -o remount,rw -t ext4 /dev/root /
adb shell mkdir bootfs
adb shell mount -t vfat /dev/block/nanda /bootfs

OK now we need to puch the files

adb push "script.bin" /bootfs/script.bin
adb push "script.bin" /bootfs/script0.bin
adb push "ft5x_ts.ko" /vendor/modules/ft5x_ts.ko
adb shell chmod 644 /vendor/modules/ft5x_ts.ko
adb push "ft5406-sc3052-1024X768.bin" /vendor/firmware/ft5x_newfw
adb shell chmod 644 /vendor/firmware/ft5x_newfw
adb reboot



OK tablet should reboot and your screen should be fixed! You should make a new script.bin and remve these lines:
ctp_upgrade_used = 1
ctp_firmware_name = "ft5x_newfw"
Then push once again the new script.bin like above.

However, if your screen now works BACKWARDS which it did for me, then once again you need to make a new script.bin. Go in and make these changes under [ctp_para]
If your script originally had this:
ctp_revert_x_flag = 0
ctp_revert_y_flag = 0
Then change the 0 to a 1 or visa versa. This should fix the backwards screen.


So..... 2 days of trying to figure this all out and success. I hope this information can help someone.

Bob