how make livesuite.img with dumped rom.

[Lexridge]

You do not seem to have the files that create_image.bat is complaining about either. Here is the contents of my _extract directory

    20480 Jun 13 00:04 12345678_1234567890boot_0.fex
     1024 Jun 13 00:04 12345678_1234567890boot_0.hdr
   131072 Jun 13 00:04 12345678_1234567890boot_1.fex
     1024 Jun 13 00:04 12345678_1234567890boot_1.hdr
    81920 Jun 13 00:04 12345678_1234567890cardtl.fex
     1024 Jun 13 00:04 12345678_1234567890cardtl.hdr
     1340 Jun 13 00:04 12345678_1234567890dlinfo.fex
     1024 Jun 13 00:04 12345678_1234567890dlinfo.hdr
     4096 Jun 13 00:04 12345678_1234567890___mbr.fex
     1024 Jun 13 00:04 12345678_1234567890___mbr.hdr
     2014 Jun 13 00:04 12345678_1234567890script.fex
     1024 Jun 13 00:04 12345678_1234567890script.hdr
      190 Jun 12 23:59 base.hdr
    24576 Jun 13 00:04 BOOT    _BOOT0_0000000000.fex
     1024 Jun 13 00:04 BOOT    _BOOT0_0000000000.hdr
   221184 Jun 13 00:04 BOOT    _BOOT1_0000000000.fex
     1024 Jun 13 00:04 BOOT    _BOOT1_0000000000.hdr
      512 Jun 12 23:59 COMMON  _SPLIT_0000000000.fex
     1024 Jun 12 23:59 COMMON  _SPLIT_0000000000.hdr
     6010 Jun 12 23:59 COMMON  _SYS_CONFIG000000.fex
     1024 Jun 12 23:59 COMMON  _SYS_CONFIG000000.hdr
    52466 Jun 12 23:59 COMMON  _SYS_CONFIG100000.fex
     1024 Jun 12 23:59 COMMON  _SYS_CONFIG100000.hdr
    26352 Jun 13 00:04 FED     _CARD_FED_0000000.fex
     1024 Jun 13 00:04 FED     _CARD_FED_0000000.hdr
   116736 Jun 13 00:04 FED     _FED_NAND_0000000.fex
     1024 Jun 13 00:04 FED     _FED_NAND_0000000.hdr
    80960 Jun 13 00:04 FES     _FES_000000000000.fex
     1024 Jun 13 00:04 FES     _FES_000000000000.hdr
      692 Jun 13 00:04 FES     _FES_1-1000000000.fex
     1024 Jun 13 00:04 FES     _FES_1-1000000000.hdr
     3100 Jun 13 00:04 FES     _FES_1-2000000000.fex
     1024 Jun 13 00:04 FES     _FES_1-2000000000.hdr
     1488 Jun 13 00:04 FES     _FES_200000000000.fex
     1024 Jun 13 00:04 FES     _FES_200000000000.hdr
    18944 Jun 13 00:04 FET     _CARD_HW_SCAN_000.fex
     1024 Jun 13 00:04 FET     _CARD_HW_SCAN_000.hdr
    19936 Jun 13 00:04 FET     _CARD_UPDATE_BOT0.fex
     1024 Jun 13 00:04 FET     _CARD_UPDATE_BOT0.hdr
    20048 Jun 13 00:04 FET     _CARD_UPDATE_BOT1.fex
     1024 Jun 13 00:04 FET     _CARD_UPDATE_BOT1.hdr
     4528 Jun 13 00:04 FET     _FET_RESTORE_0000.fex
     1024 Jun 13 00:04 FET     _FET_RESTORE_0000.hdr
   113152 Jun 13 00:04 FET     _HW_SCAN_00000000.fex
     1024 Jun 13 00:04 FET     _HW_SCAN_00000000.hdr
      128 Jun 13 00:04 FET     _MAGIC_CRC_EN_000.fex
     1024 Jun 13 00:04 FET     _MAGIC_CRC_EN_000.hdr
      128 Jun 13 00:04 FET     _MAGIC_CRC_START_.fex
     1024 Jun 13 00:04 FET     _MAGIC_CRC_START_.hdr
      128 Jun 13 00:04 FET     _MAGIC_DE_END_000.fex
     1024 Jun 13 00:04 FET     _MAGIC_DE_END_000.hdr
      128 Jun 13 00:04 FET     _MAGIC_DE_START_0.fex
     1024 Jun 13 00:04 FET     _MAGIC_DE_START_0.hdr
   103728 Jun 13 00:04 FET     _UPDATE_BOOT0_000.fex
     1024 Jun 13 00:04 FET     _UPDATE_BOOT0_000.hdr
   108560 Jun 13 00:04 FET     _UPDATE_BOOT1_000.fex
     1024 Jun 13 00:04 FET     _UPDATE_BOOT1_000.hdr
     2280 Jun 13 00:04 Filelist.txt
   166912 Jun 13 00:04 PXTOOLS _xxxxxxxxxxxxxxxx.fex
     1024 Jun 13 00:04 PXTOOLS _xxxxxxxxxxxxxxxx.hdr
  9021440 Jun 12 23:59 RFSFAT16_BOOT_00000000000.fex
     1024 Jun 12 23:59 RFSFAT16_BOOT_00000000000.hdr
  6577152 Jun 12 23:59 RFSFAT16_BOOTFS_00000.fex
  6577152 Jun 12 23:59 RFSFAT16_BOOTLOADER_00000.fex
     1024 Jun 12 23:59 RFSFAT16_BOOTLOADER_00000.hdr
        8 Jun 13 00:04 RFSFAT16_DISKFS_000000000.fex
     1024 Jun 13 00:04 RFSFAT16_DISKFS_000000000.hdr
   131072 Jun 12 23:59 RFSFAT16_ENVIROMENT_00000.fex
     1024 Jun 12 23:59 RFSFAT16_ENVIROMENT_00000.hdr
  9361408 Jun 13 00:04 RFSFAT16_RECOVERY_0000000.fex
     1024 Jun 13 00:04 RFSFAT16_RECOVERY_0000000.hdr
224860612 Jun 13 00:04 RFSFAT16_SYSTEM_000000000.fex
     1024 Jun 12 23:59 RFSFAT16_SYSTEM_000000000.hdr
        4 Jun 13 00:04 RFSFAT16_VBOOT_0000000000.fex
     1024 Jun 13 00:04 RFSFAT16_VBOOT_0000000000.hdr
        4 Jun 13 00:04 RFSFAT16_VBOOTLOADER_0000.fex
     1024 Jun 13 00:04 RFSFAT16_VBOOTLOADER_0000.hdr
        4 Jun 13 00:04 RFSFAT16_VENVIROMENT_0000.fex
     1024 Jun 13 00:04 RFSFAT16_VENVIROMENT_0000.hdr
        4 Jun 13 00:04 RFSFAT16_VRECOVERYFS_0000.fex
     1024 Jun 13 00:04 RFSFAT16_VRECOVERYFS_0000.hdr
        4 Jun 13 00:04 RFSFAT16_VSYSTEMFS_000000.fex
     1024 Jun 13 00:04 RFSFAT16_VSYSTEMFS_000000.hdr
total 252388

This was taken from a PMID701i ROM. I did a grep on the entire pack_ics folder looking for what is calling for the RFSFAT16_OEM file, and it is in the image.cfg file. I am wondering what will happen if I just comment this line out.

{filename = INPUT_DIR .. "_extract\\RFSFAT16_OEM_000000000000.fex",             maintype = ITEM_ROOTFSFAT16, subtype = "OEM_000000000000",}

Okay, I commented out that line, and viola!!! It built!! I now have a 334MB output.img file!!! Yay!!

Now, I just need to grow some bigger bawls and try to flash it! DOH!
I will wait to hear from you on whether or not commenting out the OEM and VOEM lines was safe to do before attempting to flash it.

[sabercatpuck]

I am fairly sure I did that too

You do not seem to have the files that create_image.bat is complaining about either. Here is the contents of my _extract directory

This was taken from a PMID701i ROM. I did a grep on the entire pack_ics folder looking for what is calling for the RFSFAT16_OEM file, and it is in the image.cfg file. I am wondering what will happen if I just comment this line out.

{filename = INPUT_DIR .. "_extract\\RFSFAT16_OEM_000000000000.fex",             maintype = ITEM_ROOTFSFAT16, subtype = "OEM_000000000000",}

Okay, I commented out that line, and viola!!! It built!! I now have a 334MB output.img file!!! Yay!!

Now, I just need to grow some bigger bawls and try to flash it! DOH!
I will wait to hear from you on whether or not commenting out the OEM and VOEM lines was safe to do before attempting to flash it.

I am fairly sure I did that as well. Except I didn't even just comment them out I flat out deleted them. So far I cant say that I have had any problems with the images that I have made not working, well not for that anyways. I have not gotten very far cooking my own stuff up from scratch as yet.
I know it can be a bit nerve racking trying to flash a unit if you don't know if it will work. I had the Onda firmwares available for a good couple weeks before I finally tried it and that was because there was someone that was locked out and Polarid was being less than forthcoming with their factory ROM's. The good news is that the A10 is nearly impossible to permanently brick, unless you can not get the firmware at all. The good news is that there are more things figured out about these guys all the time. It is a really good processor for the budget end of things.

[Lexridge]

I am fairly sure I did that as well. Except I didn't even just comment them out I flat out deleted them. So far I cant say that I have had any problems with the images that I have made not working, well not for that anyways. I have not gotten very far cooking my own stuff up from scratch as yet.
I know it can be a bit nerve racking trying to flash a unit if you don't know if it will work. I had the Onda firmwares available for a good couple weeks before I finally tried it and that was because there was someone that was locked out and Polarid was being less than forthcoming with their factory ROM's. The good news is that the A10 is nearly impossible to permanently brick, unless you can not get the firmware at all. The good news is that there are more things figured out about these guys all the time. It is a really good processor for the budget end of things.

Good to know. I have been attempting to get this tablet into flash mode. I have tried all kinds of key combinations with and without reset button, but still nothing. I can get into Recovery by holding down the volume minus when powering on, but I still have not figured out how to get into flash mode. Damn!

EDIT: Okay, figured out how to get into flash mode. I have to hold down the volume minus while plugging in the USB cable, then hit the power button six times.

The update failed.

Okay, I found another ROM, the Yarvik ROM. It is very similar, and it will actually flash, but not completely boot. I used this to rebuild my ROM, and it did flash, and does boot. However, it crashes after about 10 minutes, and is bogged down really bad. I can adb into the device however.

I had put in previous to starting this project an update.zip file, and this image has the Google market installed because of that reason. I am wondering if I should start over with my second table, which I have not even removed from the box yet, and get a totally stock ROM.

I got the yarvik ROM from here. http://www.yarvik.com/en/download_upgrade/

The tables are very similar. The only difference I could find was where I have soft buttons, the Yarvik has hard buttons.

[Lexridge]

Pulled the complete stock ROM from the new tablet

Okay, I opened up the other Zeki tablet finally, and pulled the completely stock images. I then created a new ROM using those images.

Now it boot loops, or just freezes on the Android logo. I rebooted it into recovery, and formatted the cache, and wiped the data partition, and same thing. I guess I need a "more compatible" ROM image to start with than what I have been using so far. I really thought the Yarvik ROM would solve my problems. It helped, but no prize yet.

However, even with the bad results so far, I am feeling much more confident about this entire process. I will continue to try with different similar ROMs, and hopefully soon find a good match.

[sabercatpuck]

Guess you dont need these now, but I hate wasting research

I went through and found several tablets methods for getting into LiveSuite. There is the nuclear option as well. If you just plain cant get it into FEL mode, but are bound and determined to (and the device boots at least to a point you can access with ADB) you can delete the stuff in the NANDA partition

$ adb shell
# mkdir /sdcard/nanda
# mount -t vfat /dev/block/nanda /sdcard/nanda
# ls /sdcard/nanda

Then just start deleting a few things (boot.ini and the linux directory are good choices). When you reboot, there will be no bootloader so it will default into FEL mode. Warning I did do this once to try and it did seem to be one of the harder attempts with LiveSuite, but with a bit of persistance I did make it work.
Now, if you are really really really (did I say really yet?) desperate you can go to the supernuclear option and start shorting out pins on the flash to wipe it out, I only recomend this if you are really really (there is that really word again, perhaps I should pay attention) desperate.

As for the other methods people have used (I figure one of these days it might be needed by someone):
Hold menu while plugging in the USB cable (note seems like all buttons will do it)

Press and HOLD the HOME button (do not release).
Insert the USB cord into the tablet (while holding HOME).
Quick-press the POWER button 3 times (still holding HOME).
Quick-press the VOLUME UP button (still holding MENU).
Release the HOME button.

Next, you go through the selection, open your firmware etc.
Hold power to shut down your G9 completely.
Hold Vol+ (according to GemeiTech, any button will do) and plugin USB to (NON-HOST) port.
Press power 6-10x... For me it always "ting" on 6...

The A10 can update the firmware from USB, so it can not be bricked. In case you bricked your devices, here is the instruction for flash the firmware from USB. Note that this is only can be done in Windows. You need a tool from Allwinner called livesuite, download livesuite.exe. It's a self extract program, make a new folder put it inside and click the exe, it will extract the program to the folder. And you need your firmware, which is a image file. You can download the Ainol Novo 7 Advanced stock firmware here aino_2.0.4.img. Click LiveSuite.exe to execute it and click SelectImg button to select the aino_2.0.4.img downloaded. Connect your devices to pc with a usb cable. Then do the following:
Here is instructions to let the device go to firmware upgrading mode(It should be applied for all A10 devices):
1. power off the device
2. Press and hold any physical key except the power key on the device(ie, press and hold Vol+ key, still holding in 3 and 4)
3. Press and hold power key for about 2s(power on the device, when powering on, if a key is pressed, the devices will not boot until key released or 4)
4. Release power key and press power key 3 times(i usually just keep pressing the power key)
If you pc are prompted finding new hardware, install the driver in the livesuite program UsbDriver folder.

4. Initiate the restore process:
- power off the Aurora
- press and hold the "back" button
- connect the usb cable to the Aurora
- while still holding the "back" button press "power" button rapidly, 15 times until menu disappears from the screen
- wait for the driver to be detected, the first time you do this it will install the drivers and can take some time
- LiveSuit will pop up and ask questions, hit "yes" to both

[Lexridge]

Lol, I am not that desperate yet! It boots to the Android logo, and from there I DO have adb access. Also, once in a few boots, it will actually boot all the way, but if I try to do anything, it crashes shortly thereafter. I am going to try a few more of the Yarvik ROMS first. The 701i ROM was a no go. It wouldn't even flash when using it as an extraction directory. So that also most likely rules out the Onda ROM as well.

I will keep hacking along and hopefully get something that works, and is stable. BTW, was OEM and VOEM the only things you removed from the image.cfg file? That would be very helpful perhaps to know. It is crazy that it will boot all the way sometimes, and not others.

Anyway, I will keep you informed with my progress. Thanks again for all your help. You have been awesome!

[Lexridge]

Okay, this is a bit odd. I did some comparisons between my unaltered tablet, and the newly flashed one. Check this out.

My ROM flashed tablet first:
df command

Filesystem             Size   Used   Free   Blksize
/dev                   407M    44K   407M   4096
/mnt/asec              407M     0K   407M   4096
/mnt/obb               407M     0K   407M   4096
/system                251M   217M    34M   4096
/data                    1G    86M     1G   4096
/cache                 125M     4M   121M   4096
/mnt/extsd               5G     8K     5G   4096

cat/proc/mounts

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

and now, this is the stock unaltered tablet:

df command

Filesystem             Size   Used   Free   Blksize
/dev                   407M    44K   407M   4096
/mnt/asec              407M     0K   407M   4096
/mnt/obb               407M     0K   407M   4096
/system                251M   206M    45M   4096
/data                  787M    70M   717M   4096
/cache                 251M     4M   247M   4096
/mnt/sdcard              6G   336M     5G   4096
/mnt/secure/asec         6G   336M     5G   4096

/proc/mounts

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

While there are some significant differences, I wonder if they are significant enough to cause all these instability problems. Also, notice the differences in sizes of the /data and /cache partitions.

Do you notice anything else there that looks abnormal?

Thanks,

[c,lei]

Okay, this is a bit odd. I did some comparisons between my unaltered tablet, and the newly flashed one. Check this out. My ROM flashed tablet first: df command

 Filesystem             Size   Used   Free   Blksize /dev                   407M    44K   407M   4096 /mnt/asec              407M     0K   407M   4096 /mnt/obb               407M     0K   407M   4096 /system                251M   217M    34M   4096 /data                    1G    86M     1G   4096 /cache                 125M     4M   121M   4096 /mnt/extsd               5G     8K     5G   4096

cat/proc/mounts

 rootfs / rootfs rw 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 /dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0 /dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/vold/93:64 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

and now, this is the stock unaltered tablet: df command

 Filesystem             Size   Used   Free   Blksize /dev                   407M    44K   407M   4096 /mnt/asec              407M     0K   407M   4096 /mnt/obb               407M     0K   407M   4096 /system                251M   206M    45M   4096 /data                  787M    70M   717M   4096 /cache                 251M     4M   247M   4096 /mnt/sdcard              6G   336M     5G   4096 /mnt/secure/asec         6G   336M     5G   4096

/proc/mounts

 rootfs / rootfs rw 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 /dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0 /dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

While there are some significant differences, I wonder if they are significant enough to cause all these instability problems. Also, notice the differences in sizes of the /data and /cache partitions. Do you notice anything else there that looks abnormal? Thanks,

Just a thought, and I may be wrong about this, but I'll guess the different sizes of the cache partitions is one cause of the problems you're seeing, especially if things are being swapped to and from ram, since the unaltered tablet's cache partition is twice the size of the reflashed one. If the cache on the ROM flashed tablet is getting filled up because of the smaller size, wouldn't that cause the system to bog down in the way you're describing as it tries to create free space within the smaller cache partition?

[sabercatpuck]

These are the parts that bug me the most

Filesystem Size Used Free Blksize
Flashed
/mnt/extsd 5G 8K 5G 4096

Stock
/mnt/sdcard 6G 336M 5G 4096
/mnt/secure/asec 6G 336M 5G 4096


Flashed
/dev/block/vold/93:64 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

Stock
/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

What bugs me here is that in the stock the lines referenced are SDCARD, which on the polaroid tablets I have worked with is actually the internal flash, where the flashed ones are referencing the EXTSD which is a SD, or uSD card inserted into the unit, with then no mention of the internal SD card.

One question, just to be safe, you did have the SD card pulled out when you flashed right? I know I have seen odd things happen in that case, and that is one of the first steps in the procedures I have seen.

[Lexridge]

What bugs me here is that in the stock the lines referenced are SDCARD, which on the polaroid tablets I have worked with is actually the internal flash, where the flashed ones are referencing the EXTSD which is a SD, or uSD card inserted into the unit, with then no mention of the internal SD card.

One question, just to be safe, you did have the SD card pulled out when you flashed right? I know I have seen odd things happen in that case, and that is one of the first steps in the procedures I have seen.

Oh, I can explain that. I had modified my /etc/void.fstab file in order to swap the SDCard and the ExtSD. Of course when I ripped the /system for the unit, that changed stayed intact. However, the Internal FLASH was indeed 6GB before this, and now only 5GB.

And, not only that, but I tried adb shell and cd'ing into /system/etc in order to copy void.fstab.orig over my modified one, and it tells me that neither file exists, although they do indeed show up in the directory. Very STRANGE! Also, the permissions seem to not be the same as they were originally on those files.

The current ROM I am on currently was one built from my modified system, void.fstab, market, etc. I cannot use the tablet directly, but it is stable enough for adb to always work. However, when I pull the stock stuff and build from that, it infinitely boot loops to the point I cannot even adb into it.

I am suspecting that either the NANDs are getting formatted wrong, in the wrong order, or just not getting formatted at all, thus allowing my modified ROM to work somewhat, and not allowing the pulls from the totally stock unit work at all.

Is there a difference between livesuite software perhaps, or even the A10 Kitchen software. I have been using the Yarvik version of Livesuite, but it looks exactly the same as the Southern Telecom version.

[Lexridge]

okay, since I was not comparing apples to apples, I went back and built a totally stock ROM, based on the unaltered tablet and the Yarvik 260 ROM for extraction purposes. Now it will boot. However, it does still lock out the GUI, but finally I do have adb access and is not crashing after 10 minutes.

So, with that in mind, the void.fstab file is now stock again. A df still shows this. Note the extsd is gone now, since it is a stock void.fstab file.

Filesystem             Size   Used   Free   Blksize
/dev                   407M    44K   407M   4096
/mnt/asec              407M     0K   407M   4096
/mnt/obb               407M     0K   407M   4096
/system                251M   206M    45M   4096
/data                    1G    71M     1G   4096
/cache                 125M     4M   121M   4096
/mnt/sdcard              5G    20K     5G   4096
/mnt/secure/asec         5G    20K     5G   4096

and the cat /proc/mounts shows this:

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Still about the same. This leads me to believe that the Yarvik 260 ROM which I am using to extract is still not close enough to this tablet to be useful.

I think at this point, until I find a tablet that is damn near identical, I am dead in the water. Most of these Chinese tablets are clones of other Chinese tablets, but the ocean is full of them. Finding a good match is like finding a kidney or liver donor. Every ROM I have used for extraction was from a 4GB unit. This is an 8GB unit, and that is possibly where all the problems are originating. Just a theory anyway.

Where are the logs located? I am used to finding them in /var/log/messages, but that is non existent on Android.

[Lexridge]

I finally did find a ROM that boots, and is apparently stable, as it does not crash. However, the touchscreen does not work, nor does the g-sensor. So, I assumed I could build my ROM against this one and get my correct touch screen drivers back, but it fails in flashing at about 85% in.

I have no idea what this ROM is from, as I have downloaded so many by now, that I lost track.

Back to the drawing board.

[sabercatpuck]

guessing driver issue

seems like there are drivers (ko files) that are loaded in oneof the support files in the flash. the environment one seems a likely candidate by name. wonder if that one can be mounted and edited. i would need to research how but i know those ko files can be loaded after the fact.

[Lexridge]

seems like there are drivers (ko files) that are loaded in oneof the support files in the flash. the environment one seems a likely candidate by name. wonder if that one can be mounted and edited. i would need to research how but i know those ko files can be loaded after the fact.

I did get one to build against that ROM that works. The G-Sensor works, the touchscreen works, and it is stable. However (of course there would be a however involved), the touch sensor is really off. I turned on the touch screen debugging so I could see the touch points, and it is really odd. When I touch the top of the screen, the actual target point appears to the lower right. When I touch near the bottom, the actual touch point is to the top left.

I dont have a touch screen calibration in my settings, but I think it is probably just hidden. Any clue how I can find and run the screen calibration? I am not sure it would fix this anyway, but it would certainly be worth a shot. I am soooo close now!!

Thanks

[Lexridge]

Okay. I am finally to the point that I REALLY think this thing is suffering hardware issues. It is constantly freezing even in recovery mode, and the display is going to hell with green stripes. I really don't think this is something that could be caused by flashing it. After all, it is still on the original kernel. The only thing that maybe flashing could cause would be permissions issues. Everything is bootfs is 777, which I thought kinda strange, and adb shell will NOT let me change them.

When is it booted (rarely), and I plug in either a USB mouse, or SDCard, the screen goes green, it crashes. I noticed I could make it work if I put the tablet in the freezer for a few minutes before trying either, and it would work then for up to several minutes, then back to the green screen and crashing.

And what sucks even worse, Even though I am certain I have hardware issues with this tablet, I am afraid to try this ROM on my other one, for fear that is IS something I did...at least until they release an official ROM for it.

I even managed to get an A10 version of CM9 installed on it, and working except for no touch screen driver....but again, after 5 minutes or so, or plugging in sdcard or usb, CRASH!

I took it apart again, and checked all the connections, everything looks good there.

I think I will look at a Novo Elf II next. I have seen them for as little as $139 with dual cameras, and dual core 1.5ghz cpu.

Anyway, I think I am finished with trying to build a ROM for this. It did nothing but leave a very bad taste in my mouth. However, experience points gained. Thank you guys for all your help in this.