CUBE TALK 9X CUSTOM ROM BASED ON STOCK FIRMWARE 1.8

[corvik]

My 32gb black with working touch
Got PID:928 VID 0x1040

[FestivusOz]

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

@ FestivusOz, I just bought Cube Talk 9x from AliExpress (delivery with DHL _ HongKong > Bucharest in 3 days), second day seller have posted a picture with package content...and very good communication)
[ATTACH=CONFIG]7544[/ATTACH]


I looked in a hurry and found a difference of 33 USD, with DHL delivery to Australia included.
[ATTACH=CONFIG]7545[/ATTACH]

Seller name is in screenshot.

Thanks so much. Will look into this

[pix64]

Сергей Михайлович, did You try to make folder named "goodix" at the root of sdcard, put this _goodix_update_.bin there and reboot?

I did a few more tries, using bad kernel rom (rooted) :

firmware : _goodix_update_.bin file posted by Lepi (how did you get this btw ?)

config : i found a config file for another model which had the exact same amount of hexadecimal values than a gt9xx_config paragraph, its format is one line comma separated. I took Brian's real config and put it in this format. I also tried the same file with version + 1 (0x41->0x42)

I tried to put files in /storage/sdcard0/, /storage/sdcard0/goodix/, /storage/sdcard1/goodix/, /storage/sdcard1/, /data/, /etc/touch/
with names _goodix_update_.bin/goodix.bin, _goodix_config_.cfg/goodix.cfg

Nothing helped...



Dear devs who are reading :-), is there a way to manualy create the node /proc/goodix_tool ?
See https://github.com/qdk0901/q98_source/blob/11bb2c3338827660bd13b1933d99e278b792c632/drivers/input/touchscreen/gt9xx.c#L65 and https://github.com/qdk0901/q98_sourc...ix_tool.c#L179


If not, how to try and build a kernel ? Even one that only manages to update firmware/config so that we could flash a working one afterwards.

I did some simple linux kernel compiling once, but not for android, we would need kernel sources from cube isn't it ?

[Lepi]

I did a few more tries, using bad kernel rom (rooted) :

firmware : _goodix_update_.bin file posted by Lepi (how did you get this btw ?)

config : i found a config file for another model which had the exact same amount of hexadecimal values than a gt9xx_config paragraph, its format is one line comma separated. I took Brian's real config and put it in this format. I also tried the same file with version + 1 (0x41->0x42)

I tried to put files in /storage/sdcard0/, /storage/sdcard0/goodix/, /storage/sdcard1/goodix/, /storage/sdcard1/, /data/, /etc/touch/
with names _goodix_update_.bin/goodix.bin, _goodix_config_.cfg/goodix.cfg

Nothing helped...

I sympathize, I've already ordered a new tablet. Tired revive. Chinese thanks for the lost time.

[pix64]

CUBE TALK 9X CUSTOM ROM BASED ON STOCK FIRMWARE 1.8

I sympathize, I've already ordered a new tablet. Tired revive. Chinese thanks for the lost time.

Ordered a new one ? What about warranty ?

[Lepi]

Ordered a new one ? What about warranty ?

Anna Fang Seller from AliExpress does not respond to my letters with attached video dead touch.
Members of forum 4PDA expect me to new modifications, and the tablet does not work. I am very angry!

[cubelibre]

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

[mmrrdd]

Anna Fang Seller from AliExpress does not respond to my letters with attached video dead touch.
Members of forum 4PDA expect me to new modifications, and the tablet does not work. I am very angry!

I bought from Anna Fang,same.

[Lepi]

I bought from Anna Fang,same.

But in fact you have no problems, thank God.

[giouncino]

Anna Fang Seller from AliExpress does not respond to my letters with attached video dead touch.
Members of forum 4PDA expect me to new modifications, and the tablet does not work. I am very angry!

I'm really sorry for that...

[mmrrdd]

But in fact you have no problems, thank God.

Yes I have a good luck,
After recived talk9x from Anna ,I just play and learn about it(my first mtk device) only 3 day,
and I have sold talk 9x to my friend several week, before the rom Cool Ui came out .

[Lepi]

I'm really sorry for that...

Thank you very much. I already live with new hopes.

[mmrrdd]

Thank you very much. I already live with new hopes.

I have check a several recovery(original , cwm ,twrp) from any rom.
and found something wrong in file "recovery.fstab" in ramdisk folder(extrac from recover.img by this windows tool),
left side is content of recovery.fstab from original stoock rom,
right side is recovery.fstab from CWM(chinese and 900 supersport cwm ,Lepi TWRP ,and orther MTK stock rom)



Talk9x had a different (original)device name and partition pointer from another MTK recovery(chinese cwm and 900 supersport cwm ,Lepi TWRP ,and orther MTK stock rom)

That the cause,after flash with cool ui v3 ,the recovery had crash.(cool ui, must flash by third paty recovery)

boot.img from Cool Ui V3 rom had moded-kernel(check from kernel file size ,don't know how they mod),

After flashed with cool ui v3 ,You will have 2 different kernel in one device,one in the boot.img(moded kernel) ,and one in the recovery.img(original).

I think,some script in moded kernel had affect or damage data on another hidden partition(wrong pointer and device name of moded or third party-recovery part),

So,any body that have Talk 9x 32GB , please dump image of this partition for Lepi,
/dev/pro_info
/dev/protect_f
/dev/protect_s
/dev/seccfg
/dev/misc
/dev/expdb
/dev/bmtpool
(see how to dump hidden partition Click here)

[unanonimo]

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

I have check a several recovery(original , cwm ,twrp) from any rom.
and found something wrong in file "recovery.fstab" in ramdisk folder(extrac from recover.img by this windows tool),
left side is content of recovery.fstab from original stoock rom,
right side is recovery.fstab from CWM(chinese and 900 supersport cwm ,Lepi TWRP ,and orther MTK stock rom)



Talk9x had a different (original)device name and partition pointer from another MTK recovery(chinese cwm and 900 supersport cwm ,Lepi TWRP ,and orther MTK stock rom)

That the cause,after flash with cool ui v3 ,the recovery had crash.(cool ui, must flash by thirth paty recovery)

boot.img from Cool Ui V3 rom have moded-kernel(check from kernel file size ,don't know how they mod),
I think,some script in moded kernel had affect or damage data on another hidden partition(wrong pointer and device name of moded or thirth party-recovery part),

So,any body that have Talk 9x 32GB , please dump image of this partition for Lepi,
/dev/pro_info
/dev/protect_f
/dev/protect_s
/dev/seccfg
/dev/misc
/dev/expdb
/dev/bmtpool
(see how to dump hidden partition Click here)

No problem... I have backup my data with your instructions. I hope to help you for solution of problem Lepi and pix64 tablets.
(Pardon for my bad english)

https://app.box.com/s/vykh6uhl11h0qotj2cel

(32Gb black serialcode 1423)

[mmrrdd]

No problem... I have backup my data with your instructions. I hope to help you for solution of problem Lepi and pix64 tablets.
(Pardon for my bad english)

https://app.box.com/s/vykh6uhl11h0qotj2cel

(32Gb black serialcode 1423)

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
..