Cube T9 64bit octacore A53 4G beast.

[Edius]

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?

I haven't flashed RileyROM, really have no ideea about OTA with this ROM
In theory, if you flash this Riley ROM and stock CWM from V1.04 (click) I see no problems and you'll be rooted.

[Riddick]

I haven't flashed RileyROM, really have no ideea about OTA with this ROM
In theory, if you flash this Riley ROM and stock CWM from V1.04 (click) I see no problems and you'll be rooted.

Thanks Edius, that's exactly what I will do. Hopefully OTA updates work.

[BamaPanda]

Thanks Edius, that's exactly what I will do. Hopefully OTA updates work.

MTK may be different, but every custom ROM Riley made for my Pipo M8 Pro was a new updated ROM, usually with updated firmware.

[giouncino]

Generally on custom roms is better to NOT use ota updates, often developer of custom roms disabled this option by default.
Ota updates are designed and tested on stock rom, if you use ota on custom you can have bootloops or other malfunctions!

[Hekatombe]

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

CWM recovery installed!!!

Update:

More fail ->

[ATTACH=CONFIG]10038[/ATTACH]

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.

Could you please explane how you backup NVRAM/IMEI and installed CWM? I can't do it... I can't backup NVRAM/IMEI... I can't find this option on MTK droid tools when I connect the Tablet.
EDIT: Finally I could backup NVRAM/IMEI!! But now I can't load Ssupersu binaries!! Help please

[Riddick]

Generally on custom roms is better to NOT use ota updates, often developer of custom roms disabled this option by default.
Ota updates are designed and tested on stock rom, if you use ota on custom you can have bootloops or other malfunctions!

Well my situation sucks a whole lot more. i thought there was standard cwm img file i could use to replace rileys custom cwm, but it appears cwm is built per device, sigh ( for some reason i thought otherwise ).

All i bloody want is to install the 1.04 stock rom, and upgrade using the ota updates to 1.06, then i will do a titanium backup before rooting. Something as simple as that is turned into a gawd damn saga.

Sigh, i thought a HTC m7 rooting was hard enough, this tablet is right on par.

[Edius]

Well my situation sucks a whole lot more. i thought there was standard cwm img file i could use to replace rileys custom cwm, but it appears cwm is built per device, sigh ( for some reason i thought otherwise ).

All i bloody want is to install the 1.04 stock rom, and upgrade using the ota updates to 1.06, then i will do a titanium backup before rooting. Something as simple as that is turned into a gawd damn saga.

Sigh, i thought a HTC m7 rooting was hard enough, this tablet is right on par.

Just flash 1.04 stock ROM (do not forget to rename all folders from .rar archive on latin characters before and select Download Only mode in SP Flash Tool) and you'll be able to update to 1.05>1.06 OTA.
Still I dont't see how to do a Titanium Backup without Root. Titanium is Root dependent.
That's a 5 min. job.

[BamaPanda]

Easy root for T9

http://vrootdownload.org/

[Riddick]

Just flash 1.04 stock ROM (do not forget to rename all folders from .rar archive on latin characters before and select Download Only mode in SP Flash Tool) and you'll be able to update to 1.05>1.06 OTA.
Still I dont't see how to do a Titanium Backup without Root. Titanium is Root dependent.
That's a 5 min. job.

Mm, Ye, I was hoping to install all my regular apps in the non rooted stock Rom then back it up prior to rooting seeing as it appears that rooting changes a lot of system files that is currently stuck in my factory reset. Meaning at the moment I can't get to 1.06 due to the ota detecting system file errors since I used kingroot.

Btw Edius, I don't quit understand the renaming requirement. Can u elaborate on this point. I vaguely remember it being mentioned in other posts but I can't remember the specifics.

Cheers again for your assistance.

[Riddick]

http://vrootdownload.org/

Yep, that's the tool I will use this time on the stock Rom, especially seeing its in English and there is a unroot option.

Although I think it's iRoot at version 2.08 or something.

[maxecume]

...not very related to all that, but I confirm simcards work in France; calling capabilities, SMS, MMS, 3G/4G datas with few settings, roaming....
and microSDHC 32Gbs maximum; micro SDXC (64, 128...Gbs) doesn't work....
...still waiting for my touchscreen to be better...

[BamaPanda]

Yep, that's the tool I will use this time on the stock Rom, especially seeing its in English and there is a unroot option.

Although I think it's iRoot at version 2.08 or something.

I loaded it on my PC, and I have 2 icons on my desk top ...iRoot and vRoot.

Is there a difference? Version 2.08??

[DAGO]

...still waiting for my touchscreen to be better...

hi,
(sorry for my bad english)
I'm sure understand what is the cause of the malfunction of the touch screen, it is not the screen protector or the bad quality of the touch but ...... THE BATTERY CHARGE !!!
when it is connected the touch works badly (see image ....)




when it is disconnected the touch works perfectly ....




now I use a Samsung charger 5V - 1.0A .....
charging is slow but when connected the touch works well !!!
I'll try to do other tests with different chargers
I hope this can be useful

[fasty]

hi,
(sorry for my bad english)
I'm sure understand what is the cause of the malfunction of the touch screen, it is not the screen protector or the bad quality of the touch but ...... THE BATTERY CHARGE !!!
when it is connected the touch works badly (see image ....)
<snip>
now I use a Samsung charger 5V - 1.0A .....
charging is slow but when connected the touch works well !!!
I'll try to do other tests with different chargers
I hope this can be useful

I do not have T9 but I noticed similar problem with my U65GT.
The supplied charger creates high frequency electrical interference which upsets the touch sensor during charging. I examined the charger inside; it seems safe enough but not as good quality as the tablet itself.
I now use Samsung 2A charger which is excellent quality and creates no problems.

[maxecume]

Cube T9 64bit octacore A53 4G beast.

hi,
(sorry for my bad english)
I'm sure understand what is the cause of the malfunction of the touch screen, it is not the screen protector or the bad quality of the touch but ...... THE BATTERY CHARGE !!!
when it is connected the touch works badly (see image ....)

[ATTACH=CONFIG]10049[/ATTACH]


when it is disconnected the touch works perfectly ....

[ATTACH=CONFIG]10048[/ATTACH]


now I use a Samsung charger 5V - 1.0A .....
charging is slow but when connected the touch works well !!!
I'll try to do other tests with different chargers
I hope this can be useful

Back to our "old" touchscreen problem... thanks to @DAGO and @fasty to give ideas... The problem for me occurs even when I'm not connected... It looks like related to how long it is switched on... At the beginning, often bad then better; and in "intense" use with "hot" screen, bad again...
Sorry to bother you, rooting experts... I let you at your explorations... ; )