Polaroid PMID702c & PMIC703 CM10 Jelly Bean Compatibility

[[email protected]]

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

awesome congradulations on your hard work to solve the problem you added very useful information that will help everyone in the long run. you still intrested in a write up on how i build my compatibility for my device.

[Finless]

Thanks but not quite yet. My head is still burnt trying to get my momo working again.

I could use a little help though. I cant seem to remake system.img.
I am using the tool kit and the ext4 conversion stuff

./simg2img system.fex system.img
mkdir system
sudo mount -o loop system.img system

However on mount system is read only and I cant seem to make it mount RW. What gives?

Then if I do nothining to it

sudo ./mkuserimg.sh -s system new-system.fex ext4 tmp 300Mg

I realize I have to adjust 300M for the size of my system so it fits. But this makes the system but the ROM wont boot.

Any ideas?

Bob

[BigMcKinney]

Boot loop

i just bought a pmid703c, i have been trying to get cm9 and cm10 on this device and it will not load when i boot into recovery it will take the update and the boot files but the gapps and the root wipe gives me an error and says instillation was aborted, with cm9 it will load to the boot screen then just locks up, same with the 10, i have been sitting watching it for an hour now with CM10, i have an Evo 4g and i have loaded CM9 on it with no problems, the first boot did take approx 45 min to complete, do you have any thoughts on how i can get this tablet rolling? any thoughts or suggestions are appreciated

[[email protected]]

i just bought a pmid703c, i have been trying to get cm9 and cm10 on this device and it will not load when i boot into recovery it will take the update and the boot files but the gapps and the root wipe gives me an error and says instillation was aborted, with cm9 it will load to the boot screen then just locks up, same with the 10, i have been sitting watching it for an hour now with CM10, i have an Evo 4g and i have loaded CM9 on it with no problems, the first boot did take approx 45 min to complete, do you have any thoughts on how i can get this tablet rolling? any thoughts or suggestions are appreciated

Which compatibility zip are you using? The CM9 zip I posted yesterday has a new driver added but I don't see that as an issue. It doesn't sound like your installing the compatibility zip CT rom wont boot with out the compatibility zip installed.

[lukenova]

I'm trying this on a 701i 13 model. I followed the steps mostly step by step from the beginning. The only thing I had to change is I had to put all the files on the internal SD because clockwork recovery wouldn't mount what it called external SD. Probably due to the whole internal-sd/external-sd bullcrap with the 701 models. I don't know if that is the same with the newer models.

Waiting at the CyanogenMod bootscreen now. We shall see what happens.

[Finless]

What that is complaining of is not external SD. It is EXT-SD. That does not mean external SD.
With clockwork you can partition your SD card into 2 parts. One part as standard FAT SDcard and another part as EXT4 partition. When you do this you can use an APP like link2sd to move apps to the fast and reliable EXT4 partition on external SDcard. Clockwork will backup that partition as part of backup if it is there. So on boot up what it is telling you is it did not find a EXT-SD partition! Clockwork will still work fine and backup your tablet and data no problem. Just ignore that message unless you want to do the partitioning! You can do this on Clockwork by going to the advanced menu.

Bob

[lukenova]

Well, it looks like it booted but the touch screen isn't off for about the top 1/4 of the screen. Also, it doesn't rotate at all. It only stays in landscape mode all the time. I'm going to try the stuff listed here http://www.freaktab.com/showthread.p...patibility-zip that has apparently been known to work with 701i 13... we shall see.

[[email protected]]

Well, it looks like it booted but the touch screen isn't off for about the top 1/4 of the screen. Also, it doesn't rotate at all. It only stays in landscape mode all the time. I'm going to try the stuff listed here http://www.freaktab.com/showthread.p...patibility-zip that has apparently been known to work with 701i 13... we shall see.

nova has screen rotation disabled by default im posting a new one for the 702c, 703c, 7Xc, Soon, should work for the 701i_x13 Cant verify.

[onef]

Thanks but not quite yet. My head is still burnt trying to get my momo working again.

I could use a little help though. I cant seem to remake system.img.
I am using the tool kit and the ext4 conversion stuff

./simg2img system.fex system.img
mkdir system
sudo mount -o loop system.img system

However on mount system is read only and I cant seem to make it mount RW. What gives?

Then if I do nothining to it

sudo ./mkuserimg.sh -s system new-system.fex ext4 tmp 300Mg

I realize I have to adjust 300M for the size of my system so it fits. But this makes the system but the ROM wont boot.

Any ideas?

Bob

That should have mounted as rw but try this
mount -o loop,rw system.img system

With the -o you should be able to string many other options as it needed.

Did you squish the mbr? And not sure about the hardware if it need to have the boot flag set on the partition. Working with images can be fun as I have done this many times trying to build custom USB boot deviced.

Can you PM the steps that you are doing to get the boot.img built?

[Finless]

onef, yes I tried that but Ubuntu still mounted it RO.

But thats OK I can use DD and mkfs and make a new IMG and copy everything over preserving all links etc. So thats no problem if I have to do that. But either way my new system wont boot.....

>Did you squish the mbr? And not sure about the hardware if it need to have the boot flag set on the partition

You lost me here. The tutorials I am using dont say anything about this subject. I am using the kitchen tool kit. Got a link or something I can study please about this?

FYI I am in a Ubuntu 32bit VM (Virtual box). Might that be the issue as I noticed the tool kit suggested a 64bit OS? I do have a dual boot 64bit Unbuntu I can use but I prefer the VM because livesuite etc is windows. Just makes it faster for me to test ROMs rather than rebooting all the time.

Bob

[lukenova]

Re: Polaroid PMID702c &amp;amp; PMIC703 CM10 Jelly Bean Compatibility

nova has screen rotation disabled by default im posting a new one for the 702c, 703c, 7Xc, Soon, should work for the 701i_x13 Cant verify.

I will try it out when it is posted.

Im not sure what I've done, but the top 1/4 of my screen (holding it landscape) is unusable. I turn on the on screen display of where I can touch and any time I touch that top portion, it is as if I touched it directly below in the usable portion.

I tried the cm9 rom. Same thing. Also, ever since I started with the whole CWM recovery being installed thing, I can't get livesuite to recognize it to reflash stock.

Any advice???

Sent from my HTC Thunderbolt using Tapatalk 2

[lukenova]

Update: finally got it to let me flash the stock rom back on it. Screen works fine with the stock rom, so looks like it was something either with the recovery image or with the custom rom images that was causing the screen to go all funky on me.

[sallan513]

Watching your progress Lukenova!!

Update: finally got it to let me flash the stock rom back on it. Screen works fine with the stock rom, so looks like it was something either with the recovery image or with the custom rom images that was causing the screen to go all funky on me.

I fell in love with CWM on my old cell phone and got excited to see some one trying to get it loaded on a Polaroid PMID701i x13. When I first started reading this thread I was dissapointed to see that the x13 seemed like it was being forgotten about. So now I am waiting patiently to read of your progress before diving into the ROM pool.

One question for you...are you giving this a try because you haven't found any other alternative ROM for the x13 model??? It would be nice if there was a bloat-free stock ROM with Google included to try out. For the $$ this tablet is a good value but I think the original ROM is really holding it back..plus, the Wi-Fi issue drives me insane!! Using apps to keep it alive is a crappy solution and Polaroid is zero help..

Good luck and keep trucking!!

[lukenova]

Re: Polaroid PMID702c &amp;amp; PMIC703 CM10 Jelly Bean Compatibility

Google market can't be included on stock rom from the manufacturer because the device isn't an officially licensed android device. That means Google didn't approve it. That's the same reason that CyanogenMod can't include the Google apps in their roms, and you have to download them seperately.

I would love to have a working version of CyanogenMod on my 701i 13, but sadly it looks like it might not be in the cards. There simply aren't enough of the device out there to spark enough interest for a lot of development.

If you can get Google market sideloaded onto the stock rom, then load an app called Auto Airplane Mode, it fixes the wifi. Doesn't keep wifi alive - it actually turns wifi off when the device sleeps. An added bonus is it saves a lot of battery life.

Sent from my HTC Thunderbolt using Tapatalk 2

[sallan513]

Yeah I have that running now but it doesnt always work. I did get the Google apps sideloaded with no problem but it would be SO nice to have CWM on it. Oh well, I'll keep searching I guess!