CUBE TALK 9X CUSTOM ROM BASED ON STOCK FIRMWARE 1.8

[Lepi]

Thank for your kindness,

adb command to restore the backup image.

dd if=/sdcard/pro_info.img of=/dev/pro_info


dd if=/sdcard/protect_f.img of=/dev/protect_f


dd if=/sdcard/protect_s.img of=/dev/protect_s


dd if=/sdcard/seccfg.img of=/dev/seccfg


dd if=/sdcard/misc.img of=/dev/misc


dd if=/sdcard/expdb.img of=/dev/expdb


dd if=/sdcard/bmtpool.img of=/dev/bmtpool
..

Thanks, I'll try it. But that's part of my script for my TWRP and CWM

format("ext4", "EMMC", "/dev/block/mmcblk0p5", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
ui_print(">>> Copy Files");
package_extract_dir("system", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/data");
package_extract_dir("data", "/data");

[Rara Avis]

Talk9x had a different (original)device name and partition pointer

And this (stock!) recovery.fstab is incompatible with real device partition table.
Can't believe, but it is...

[mmrrdd]

And this (stock!) recovery.fstab is incompatible with real device partition table.
Can't believe, but it is...

According to my opinion,
fstab of third party recovery is incompatible with real device partition table.

[mmrrdd]

Thanks, I'll try it. But that's part of my script for my TWRP and CWM

format("ext4", "EMMC", "/dev/block/mmcblk0p5", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
ui_print(">>> Copy Files");
package_extract_dir("system", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/data");
package_extract_dir("data", "/data");

if you see in "update-scrip" file (from factory stock firmware)
"/system" should to be "/dev/block/mmcblk0p6 "

"/dev/block/mmcblk0p6" is the real system partition

[mmrrdd]

This is my root tool update-scrip,it work perfectly with original recovery.

[Lepi]

if you see in "update-scrip" file (from factory stock firmware)
"/system" should to be "/dev/block/mmcblk0p6 "

"/dev/block/mmcblk0p6" is the real system partition

I've known about it. Do you think that the error of my touchscreen linked to this markings?

[Rara Avis]

Well, can anybody with access to the tablet show the output of

cat /proc/dumchar_info

?

[unanonimo]

R: CUBE TALK 9X CUSTOM ROM BASED ON STOCK FIRMWARE 1.8

Well, can anybody with access to the tablet show the output of

cat /proc/dumchar_info

?

u0_a193@U65GT:/ $ cat /proc/dumchar_info
Part_Name************************************ Size****************** StartAddr************************************ Type****************** MapTo************ Region
preloader****************** 0x0000000000040000************ 0x0000000000000000************ 2************ /dev/misc-sd************************ BOOT_1
mbr*********************************************** ******* 0x0000000000080000************ 0x0000000000000000************ 2************ /dev/block/mmcblk0************************ USER
ebr1********************************************** ** 0x0000000000080000************ 0x0000000000080000************ 2************ /dev/block/mmcblk0p1************ USER
pro_info************************ 0x0000000000300000************ 0x0000000000100000************ 2************ /dev/block/mmcblk0************************ USER
nvram****************************************** 0x0000000000500000************ 0x0000000000400000************ 2************ /dev/block/mmcblk0************************ USER
protect_f****************** 0x0000000000a00000************ 0x0000000000900000************ 2************ /dev/block/mmcblk0p2************ USER
protect_s****************** 0x0000000000a00000************ 0x0000000001300000************ 2************ /dev/block/mmcblk0p3************ USER
seccfg************************************ 0x0000000000040000************ 0x0000000001d00000************ 2************ /dev/block/mmcblk0************************ USER
uboot****************************************** 0x0000000000060000************ 0x0000000001d40000************ 2************ /dev/block/mmcblk0************************ USER
bootimg****************************** 0x0000000000a00000************ 0x0000000001da0000************ 2************ /dev/block/mmcblk0************************ USER
recovery************************ 0x0000000000a00000************ 0x00000000027a0000************ 2************ /dev/block/mmcblk0************************ USER
sec_ro************************************ 0x0000000000600000************ 0x00000000031a0000************ 2************ /dev/block/mmcblk0p4************ USER
misc********************************************** ** 0x0000000000080000************ 0x00000000037a0000************ 2************ /dev/block/mmcblk0************************ USER
logo********************************************** ** 0x0000000000800000************ 0x0000000003820000************ 2************ /dev/block/mmcblk0************************ USER
ebr2********************************************** ** 0x0000000000080000************ 0x0000000004020000************ 2************ /dev/block/mmcblk0************************ USER
expdb****************************************** 0x0000000000f60000************ 0x00000000040a0000************ 2************ /dev/block/mmcblk0************************ USER
android****************************** 0x0000000080000000************ 0x0000000005000000************ 2************ /dev/block/mmcblk0p5************ USER
cache****************************************** 0x0000000008000000************ 0x0000000085000000************ 2************ /dev/block/mmcblk0p6************ USER
usrdata****************************** 0x0000000080000000************ 0x000000008d000000************ 2************ /dev/block/mmcblk0p7************ USER
fat*********************************************** ******* 0x0000000639700000************ 0x000000010d000000************ 2************ /dev/block/mmcblk0p8************ USER
bmtpool****************************** 0x0000000000000000************ 0x00000000ffff00a8************ 2************ /dev/block/mmcblk0************************ USER
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
u0_a193@U65GT:/ $



Note: attention, my tablet is with 13.5gb of data partition

(talk9x 32gb black serialcode n. 1423)

[Lepi]

Well, can anybody with access to the tablet show the output of

cat /proc/dumchar_info

?

And not simply through the Root Explorer to see what is written in what sections? Sorry for Google Translate.
QED!
UPD
Before I began to edit the updater-script, I looked the locations of data in the memory sections through Root explorer.

[Rara Avis]

As expected:

android******************************  0x0000000080000000************ 0x0000000005000000************  2************ /dev/block/mmcblk0p5************ USER

And still don't undestand why

...
"/system" should to be "/dev/block/mmcblk0p6 "

"/dev/block/mmcblk0p6" is the real system partition

when it is

cache******************************************  0x0000000008000000************ 0x0000000085000000************  2************ /dev/block/mmcblk0p6************ USER

?

[mmrrdd]

As expected:

android******************************  0x0000000080000000************ 0x0000000005000000************  2************ /dev/block/mmcblk0p5************ USER

And still don't undestand why

when it is

cache******************************************  0x0000000008000000************ 0x0000000085000000************  2************ /dev/block/mmcblk0p6************ USER

?

on Android 4.4-security way,
adb dumchar_info,maybe can not directly to detec the hardware device( harddisk),
real system partition is "/dev/block/mmcblk0p6" (follow the udate-script command).

[mmrrdd]

I've known about it. Do you think that the error of my touchscreen linked to this markings?

many many ... symlink , metedata setting (hardware drivers) commands in update-script ,
will work after the first boot of flashed new firmware ,
it will take a long time to start a device,
result-setting-data may be stored on another hidden partition
(depending on link-pointer in uboot,kernel(recovery and boot image),
and ebr,etc(/dev/pro_info, /dev/protect_f, /dev/protect_s , /dev/seccfg ,
/dev/misc, /dev/expdb ,/dev/bmtpool ))


You should to flash-back to the original(Chinese stock firmware) recovery, boot, ebr1, ebr2,uboot.
and then, flash again with this factory OTA update,
and restore this image to this partition

/dev/pro_info
/dev/protect_f
/dev/protect_s
/dev/seccfg
/dev/misc
/dev/expdb
/dev/bmtpool


by adb command

[Lepi]

You should to flash-back to the original(Chinese stock firmware) recovery, boot, ebr1, ebr2,uboot.
and then, flash again with this factory OTA update,
and restore this image to this partition
/dev/pro_info
/dev/protect_f
/dev/protect_s
/dev/seccfg
/dev/misc
/dev/expdb
/dev/bmtpool
by adb command

Thank you.

[Rara Avis]

on Android 4.4-security way,
adb dumchar_info,maybe can not directly to detec the hardware device( harddisk),
real system partition is "/dev/block/mmcblk0p6" (follow the udate-script command).

I thought of security is to block access to some restricted data, rather than generate malformed output...
Ok, let's see (ADB to Lepi's TWRP):

~ # ls -la / | grep emmc
drwxrwxrwx root     root              1970-01-01 00:00 emmc
[COLOR=#008000]lrwxrwxrwx root     root              1970-01-01 00:00 emmc@android -> /dev/block/mmcblk0p5[/COLOR]
[COLOR=#ff0000]lrwxrwxrwx root     root              1970-01-01 00:00 emmc@cache -> /dev/block/mmcblk0p6[/COLOR]
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@ebr1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@fat -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@protect_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@protect_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@sec_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-01 00:00 emmc@usrdata -> /dev/block/mmcblk0p7
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
[COLOR=#ff0000]/dev/block/mmcblk0p6 on /cache type ext4 (rw,relatime,data=ordered)[/COLOR]
/dev/block/mmcblk0p8 on /emmc type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p8 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
[COLOR=#ff0000]~ # ls -la /cache
drwx------ system   system            2013-01-01 11:41 backup
drwxrwx--- root     root              1970-01-01 00:00 lost+found
drwxrwx--- system   cache             2014-08-21 12:30 recovery[/COLOR]
[COLOR=#008000]~ # mkdir p5
~ # mount /dev/block/mmcblk0p5 p5
~ # ls -la p5
drwxr-xr-x root     root              2014-08-17 18:04 app
drwxr-xr-x root     shell             2014-08-17 18:04 bin
-rw-r--r-- root     root         4024 2014-07-04 12:43 build.prop
drwxr-xr-x root     root              2014-07-04 12:56 data
drwxr-xr-x root     root              2014-08-20 16:53 etc
drwxr-xr-x root     root              2014-07-04 13:09 fonts
drwxr-xr-x root     root              2014-08-16 05:41 framework
drwxr-xr-x root     root              2014-07-04 11:31 lib
drwx------ root     root              1970-01-01 00:00 lost+found
drwxr-xr-x root     root              2014-07-04 13:02 media
drwxr-xr-x root     root              2014-07-04 13:02 mobile_toolkit
drwxr-xr-x root     root              2014-07-04 13:58 priv-app
drwxr-xr-x root     root              2014-07-04 12:56 res
drwxr-xr-x root     root              2014-07-04 12:56 thirdparty
drwxr-xr-x root     root              2014-07-04 12:56 tts
drwxr-xr-x root     root              2014-07-04 13:01 usr
drwxr-xr-x root     shell             2014-07-04 11:12 vendor
drwxr-xr-x root     shell             2014-08-17 18:04 xbin[/COLOR]
~ #

Which one looks like /system?

Not to mention that this TWRP (assuming system -> /dev/block/mmcblk0p5) was used for rooting, replacing framework-res.apk etc more than once. Can't imagine success with system mapped improperly.

[pix64]

pix64
check this firmware I patched the VID & PID on 928 firmware
I think swallow

Hi !

Thanks for this firmware, but it didn't work better than with the other, nothing happens at all imo.


I've read your other new posts guys, thank you very much for helping.

Recovery partitions messing is interesting, but would be surprising imho.
Would touch screen failure be the only problem if partitions were melt at flashing ? I think system would not boot at all, or we would at least see inconsistent mounts or space left on partitions, don't you think ?
Or i did not understand something.

This morning i finaly had an answer from the store i bought the tablet, it's going for RMA by this weekend... so i think i have to stop trying anything more, and wait patiently it comes back, repaired or exchanged.

Lepi, maybe you could insist with your aliexpress seller and try to get your tablet to RMA too. If it works, you can sell your new tablet.

It's been a long time trying to rise these touch screens back from the dead, many sleepless nights, thanks a million time for helping guys. Thanks a lot.This forum rocks :-)