CUBE TALK 9X CUSTOM ROM BASED ON STOCK FIRMWARE 1.8

[bloommax]

I flash separately uboot, boot, preloader, recovery, and so on. I flash all factory firmware version (1.3 - 1.8). I did clear separately all caches. It did not help. Touch is dead. Only mouse trought OTG...

You didn't restore NVRAM?

[dejan1979]

Ok I flashed your rom. I used the stock cwm ( not lepi twrm ) and all is fine . touchscreen and everything else working perfectly. Will now evaluate the rom.

I have talk 9x 16g

Phil

Great to hear that. I don't understand why so many users are going through hell with the touchscreen
They must be doing something wrong.

[dejan1979]

Great to hear that. I don't understand why so many users are going through hell with the touchscreen
They must be doing something wrong.

I have solution for touchscreen problem.
Works with white or black cube talk9x.They are the same.
YOU MUST HAVE BACKUP OF YOUR NVRAM.BIN FILE. To make it work.

Later today I am going to upload FlashTool and stock firmware.
I have edited scatter file and disabled CRC check in flash tool to make it work
So if you don't have nvram.bin backup make it and save on computer
Instructions and details will follow later. Thank you!

[mick154]

Has anyone successfuly flashed this ROM from ss rom using ss cwm?

[dejan1979]

FIX FOR TOUCHSCREEN

http://www.freaktab.com/showthread.php?15940-CUBE-TALK-9X-CUSTOM-ROM-BASED-ON-STOCK-FIRMWARE-1-8&p=213337#post213337

[pix64]

FIX FOR TOUCHSCREEN
http://www.freaktab.com/showthread.p...337#post213337

Thanks a lot Dejan for this !

I don't have a nvram.bin backup... so i googled.

In MTK Droid tools, my device is detected, i get a value for IMEI 1, none for IMEI 2.
Although i can succesfuly get a root shell (the little square gets green), "IMEI/NVRAM" button stays greyed and i can't backup.

So i googled more and found a script using adb that gets a dd image of /dev/nvram.
I ran it and got a 5MB nvram.img, but i have a big doubt about the 5242880c size : the command is
>adb.exe shell su -c "dd if=/dev/nvram of=/sdcard/nvram.img bs=5242880c count=1"

Yesterday, among my different tries, i did format+download, and had to restore an IMEI backup i had done a month ago with Mobile Uncle Tools. I got it back back in "about this tablet...".

For now i use 900ss rooted rom, a bluetooth keyboard/mouse , USB debugging is enabled, wifi is working fine, i just realized that the last 3 bytes of wifi MAC change on every reboot ?!?

Any thoughts guys ?

Thanks !


EDIT : In my last TWRP backup before the incident, i have a nvram.emmc.win file (5120 KB) and its md5 file, is that the backup i need ?

[mmrrdd]

Thanks a lot Dejan for this !

I don't have a nvram.bin backup... so i googled.

In MTK Droid tools, my device is detected, i get a value for IMEI 1, none for IMEI 2.
Although i can succesfuly get a root shell (the little square gets green), "IMEI/NVRAM" button stays greyed and i can't backup.

So i googled more and found a script using adb that gets a dd image of /dev/nvram.
I ran it and got a 5MB nvram.img, but i have a big doubt about the 5242880c size : the command is
>adb.exe shell su -c "dd if=/dev/nvram of=/sdcard/nvram.img bs=5242880c count=1"

Yesterday, among my different tries, i did format+download, and had to restore an IMEI backup i had done a month ago with Mobile Uncle Tools. I got it back back in "about this tablet...".

For now i use 900ss rooted rom, a bluetooth keyboard/mouse , USB debugging is enabled, wifi is working fine, i just realized that the last 3 bytes of wifi MAC change on every reboot ?!?

Any thoughts guys ?

Thanks !


EDIT : In my last TWRP backup before the incident, i have a nvram.emmc.win file (5120 KB) and its md5 file, is that the backup i need ?

This is my 2 nvram files ,backup by MTK Droid tools, my device(32GB , dark grey) is detected and get a value for IMEI 1, none for IMEI 2,files size is 5 MB and 367KB.

nvram.bin
http://www.4shared.com/file/MM2JDDdnce/nvram.html

userdata_nvram_only.zip
http://www.4shared.com/file/j_LS3RLZce/userdata_nvram_only.html

[dejan1979]

This is my 2 nvram files ,backup by MTK Droid tools, my device(32GB , dark grey) is detected and get a value for IMEI 1, none for IMEI 2,files size is 5 MB and 367KB.

nvram.bin
http://www.4shared.com/file/MM2JDDdnce/nvram.html

userdata_nvram_only.zip
http://www.4shared.com/file/j_LS3RLZce/userdata_nvram_only.html

Use this nvram.binfrom here. And follow my guide from main post.
Mainly why you need nvram.bin is for wifi and phone calls. Flash it and change later to your own with tool like sn writer or mauimeta.
Go to settings about tablet and write down wifi mac address somewhere before you flash. For IMEI verification there is ton of resources on google.

[dejan1979]

Thanks a lot Dejan for this !

I don't have a nvram.bin backup... so i googled.

In MTK Droid tools, my device is detected, i get a value for IMEI 1, none for IMEI 2.
Although i can succesfuly get a root shell (the little square gets green), "IMEI/NVRAM" button stays greyed and i can't backup.

So i googled more and found a script using adb that gets a dd image of /dev/nvram.
I ran it and got a 5MB nvram.img, but i have a big doubt about the 5242880c size : the command is
>adb.exe shell su -c "dd if=/dev/nvram of=/sdcard/nvram.img bs=5242880c count=1"

Yesterday, among my different tries, i did format+download, and had to restore an IMEI backup i had done a month ago with Mobile Uncle Tools. I got it back back in "about this tablet...".

For now i use 900ss rooted rom, a bluetooth keyboard/mouse , USB debugging is enabled, wifi is working fine, i just realized that the last 3 bytes of wifi MAC change on every reboot ?!?

Any thoughts guys ?

Thanks !


EDIT : In my last TWRP backup before the incident, i have a nvram.emmc.win file (5120 KB) and its md5 file, is that the backup i need ?

Why use twrp for backup i dont understand you people. All you need is mobile uncle tools. My nvram.bin backup is same size 5120kb or 5,242,880bytes. Try rename nvram.img it to nvram.bin and try to flash.It may work. You never knew.
Its not easy to brick MEDIATEK device definitelly

[pix64]

My nvram.bin backup is same size 5120kb or 5,242,880bytes. Try rename nvram.img it to nvram.bin and try to flash.It may work. You never knew.
Its not easy to brick MEDIATEK device definitelly

Ok, mine is the same size, this must be the good file.

Flashing went fine, booting to chinese stock rom too but... i'm sorry to say that touchscreen still does not work...
Tried two times, no luck.

Wifi is ok, MAC address is not changing anymore and is not the same shape than before nvram flash. BT Mac changed too.
So i think/hope/whatever nvram.bin flashing did something, except i have no IMEI yet, will try to restore it later with MUT.

[Lepi]

FOR ALL OF YOU HAVING PROBLEM WITH TOUCHSCREEN NOT FUNCTIONING AFTER FLASHING MY ROM HERE IS MY FIX.
TESTED ONLY ON CUBE TALK 9X WHITE/BLACK

Thank you. I unfortunately did not help your way. And before that I repeatedly flash all factory firmware by Format All + Download. Touch still not working.

[mmrrdd]

Thank you. I unfortunately did not help your way. And before that I repeatedly flash all factory firmware by Format All + Download. Touch still not working.

or software can damage hardware ?

[Lepi]

or software can damage hardware ?

I once thought so. In my practice is for the first time.

[giouncino]

I once thought so. In my practice is for the first time.

I agree with you: never seen a SW that is able to damage the HW...
There is something still missing during FW upload! The question is What is still missing?
I'm really sorry for your devices...

[u669983]

tochscreen failure

I agree with you: never seen a SW that is able to damage the HW...
There is something still missing during FW upload! The question is What is still missing?
I'm really sorry for your devices...

Read this thread. Might help understanding and eventual solution :

http://www.modaco.com/topic/355021-most-touchscreen-issue%E2%80%99s-explained-and-the-reason-some-touchscreens-are-dying-on-p10an01%E2%80%99s-advent-vega-viewsonic-10s-point-of-view-mobii-ect/