Cube T9 64bit octacore A53 4G beast.

[Edius]

Hi, guys !
Without any screen protector, don't you afraid of a "DULL" glass in a while...?
.....
I post 3 pictures: Antutu v5.6 (40221), Antutu X v5.1 (38291; it works, now, and it's "coherent"...) and another screenshot of the peak result on Droidfish (a chess app) which is 1768 knps (just behind iPad 2, with 1970 knps and far ahead Nexus 9, 1093 knps); that evaluation, the main reason why I bought that tablet...

Looking on your screenshots I realised that your network signal 3G/4G bars are in orange colour with an little R letter ...you are in Roaming?
I have tried until now with 2 SIM cards :
1.one with 4G with data plans/calling ( signal bars in orange colours, like yours - Telekom Mobile)
2.one only with 3G data plans (no calling possible) from other carrier (RDS Mobile) who looks different (signal bars in blue colour, with no R letter - in theory no roaming) like you see in this picture
My ex Talk 9X was kept with no screen protector for over 4 months and when I sold it guess what...not even a single scratch

[Edius]

Well after just saying I am too worried about stuffing up my tablet. I thought bugger it, its a cheap tablet, so I did do the vroot thing. The unroot failed. I did a factory reset. Which brought me back to 1.04. I did the update via wireless again to 1.05. After that I went to do the 1.06 update then BOOM, same error.

Can anyone confirm if they were able to do the 1.06 update?

CHeers

If you are rooted is very possible to loose ability for OTA.
I was in the same boat after rooting with KingRoot (I have rooted only to backup/restore my NVRAM with MtkDroidTools) and I have found errors like you have.
After I flashed factory 1.04 ROM with SP Flash Tool, OTA works like a charm 1.04>1.05>1.06.

[Ogu]

After I flashed factory 1.04 ROM with SP Flash Tool, OTA works like a charm 1.04>1.05>1.06.

Can you please write a how- to ?

[Riddick]

If you are rooted is very possible to loose ability for OTA.
I was in the same boat after rooting with KingRoot (I have rooted only to backup/restore my NVRAM with MtkDroidTools) and I have found errors like you have.
After I flashed factory 1.04 ROM with SP Flash Tool, OTA works like a charm 1.04>1.05>1.06.

Now ya talking. Edius I can't find the factory rom, riley i think posted in this thread, but I seriously must be going blind trying to find it.

But ye you are right on the money. When I do a system file integrity check it appears files have been modified and won't bloody restore the original.

It really concerns me, do you think Kingroot is a piece of shit, or do all the 1 click root apps do the same thing?

[Edius]

Now ya talking. Edius can I can't find the factory rom, riley i think posted in this thread, but I seriously must be going blind trying to find it.

But ye you are right on the money. When I do a system file integrity check it appears files have been modified and won't blood restore the original.

It really concerns me, do you think Kingroot is a piece of shit, or do all the 1 click root apps do the same thing?

I'll make a new thread with ROM's - drivers for T9.
When I downloaded ROM's 1.02 and 1.04 my PC was left opened overnight..it was a pain in the as's, over 18 hours for ~700 MB

[Riddick]

here you can find cube stock roms:

http://www.51cube.com/ch/DownList.asp

1.04 is the latest available there (the others comes only as OTA updates).

Found the poster who posted the stock rom ( thanks Giouncino ).

I am downloading that now, can I install this simply by using SP Flash tool, or is there some extra things i need to do?

[giouncino]

Yes you can install with sp_flashtool, remember to do a backup first! Otherwise flashing with sp_flashtool you will lose all your data.

[Riddick]

Yes you can install with sp_flashtool, remember to do a backup first! Otherwise flashing with sp_flashtool you will lose all your data.

hahaha, already lost all data. Its ok there wasn't anything too serious.

Also do I need to have rooted the device prior to running the flash tool?

NFI how to use sp_flashtool, I guess I'll have to wait on Edius 'how to.'

Talk about pain in the ass.

[BamaPanda]

Well after just saying I am too worried about stuffing up my tablet. I thought bugger it, its a cheap tablet, so I did do the vroot thing. The unroot failed. I did a factory reset. Which brought me back to 1.04. I did the update via wireless again to 1.05. After that I went to do the 1.06 update then BOOM, same error.

Can anyone confirm if they were able to do the 1.06 update?

CHeers

I was able to update to 1.06 with my T9 rooted using VRoot. After the update the root went away. I applied VRoot from the PC once more ....viola, proper root.

The only issue I have seen with VRoot is it seems to run and run, finally coming up with a screen asking me to root the tablet, making it look as if it failed ...but actually worked. Probably just translation.

@ maxecume
The T9 has a glass screen, not plastic ...so dulling should not be an issue. Still I would not expect removal of the factory installed screen protector to help touch issues.
Hopefully it will rectify itself, but one thin layer of plastic is not the problem. The extra throwaway layer is not either. I still have both, and I do note some missed touches when typing occasionally, but I have seen that with a bare screen.

[giouncino]

hahaha, already lost all data. Its ok there wasn't anything too serious.

Also do I need to have rooted the device prior to running the flash tool?

NFI how to use sp_flashtool, I guess I'll have to wait on Edius 'how to.'

Talk about pain in the ass.

No, rooting is not related with sp_flashtool

[Riddick]

No, rooting is not related with sp_flashtool

Well now I have a bloody MTK Driver issue on the pc. Sigh, damn I need to revive my linux pc.

The driver is stopping me from doing the NVRAM and IMEI backup, as outlined in Riley's custom rom post.

I was just going to do the first section then flash the stock rom I have instead of the custom ( was going to ).

[Edius]

Well now I have a bloody MTK Driver issue on the pc. Sigh, damn I need to revive my linux pc.

The driver is stopping me from doing the NVRAM and IMEI backup, as outlined in Riley's custom rom post.

I was just going to do the first section then flash the stock rom I have instead of the custom ( was going to ).

Look here http://www.freaktab.com/showthread.p...760#post275760 , search in FAQ section..is not too hard to install Preloader/VCOM drivers

[Riddick]

Look here http://www.freaktab.com/showthread.p...760#post275760 , search in FAQ section..is not too hard to install Preloader/VCOM drivers

Genius, I had to go through the troubleshooter FAQ to fix the driver issue.

CWM recovery installed!!!

Update:

More fail ->



It will only populate when the device is booted. And of course the NVRAM/IMEI is greyed out.

If I boot into CWM Recovery MODE, the device is not detected by the MTK Tool. *sigh*

Update Clarification: When I select Recovery mode, after about a minute of there being a black screen it appears to then just boot normally.

[Edius]

@Riddick, now you are in stock CWM or in custom CWM provided by Randy in RileyROM?
I have seen the same errors but managed to backup my NVRAM

Go to tab root/backup/recovery and you'll be able to backup NVRAM ..will be also some errors but NVRAM is more important than anything else.

[Riddick]

@Riddick, now you are in stock CWM or in custom CWM provided by Randy in RileyROM?

I installed Riley's. I could install the standard clockworkmod, now I got the flash tool working.

should I install the latest version of cwm?

Does Riley's custom rom support OTA updates?