Cube T9 64bit octacore A53 4G beast.

[Edius]

Great, Custm CWM is a big step forward.
@Riddick, I don't understand why you don't flash Riley ROM, already rooted/write permission for external SD enabled? You afraid about OTA incompatibility...I doubt in these updates (1.05/1.06) is hidden another type of recovery which will lead to incompatibility.
I used in my ex Talk9X custom CWM made by @900supersport and was completely compatible with 4 different ROM's.
These errors from MTK Droid have origins in one simply thing. This type of ROM doesn't use regular EBR1 & EBR2 file (these files give information about system/user partitions dimmension)like any Mediatek device I've seen until now. It uses another type of file, don't remember what type since I'm far from my PC tonight.
MTK Droid is not compatible with this chipset/Android 4.4.4/this special type of "EBR1_2" and can do backup of NVRAM only (acts like a hidden partition) because has information only about NVRAM existence.
I have read in 4PDA forum/Cube T9 thread about an non-working custom TWRP made by Lepi in two instances. Custom CWM was a request from Lepi to make an working TWRP and maybe we should inform about this huge step forward.
With TWRP we can make a complete backup of all partitions like NVRAM/System/Cache, etc

[rrileypm]

Yes, we are treading new ground with this new chip.

I wish I had one to play with, but I don't.

I've disabled the ability to install OTA updates in my ROM. The reason for this is simple. With a rooted ROM, changes are made to system.img and boot.img. If boot.img is updated, root is lost...and you could possible have boot loops because of conflicting files.

The best way for me to get an updated firmware version to create a new ROM would be for someone to provide me a ROM dump.

Until now, I wasn't aware that MTK Droid Tools isn't compatible with this chip. Therefore, I don't know of an alternative way of dumping the firmware.

If anyone comes up with a solution, please post....and also post the OTA update (or PM me with a link) and I will continue supporting this device with new ROM's.

I don't currently have a T9...so any help is greatly appreciated.

[Riddick]

Great, Custm CWM is a big step forward.
@Riddick, I don't understand why you don't flash Riley ROM, already rooted/write permission for external SD enabled? You afraid about OTA incompatibility...I doubt in these updates (1.05/1.06) is hidden another type of recovery which will lead to incompatibility.

At this stage I wanted to learn how to flash it and restore a stock rom before i ventured down the custom path.
Secondly I have gotten around the storage issue, and my system is only using around 500mb of the 2gig partition.
Thirdly I hope my experience will help Riley and others with the T9 so we can all benefit from its awesomeness.

MTK Droid is not compatible with this chipset/Android 4.4.4/this special type of "EBR1_2" and can do backup of NVRAM only (acts like a hidden partition) because has information only about NVRAM existence.

I honestly hadn't read about the incompatibility issue anywhere, its good to know now as I was blaming myself and my computer.

I have read in 4PDA forum/Cube T9 thread about an non-working custom TWRP made by Lepi in two instances. Custom CWM was a request from Lepi to make an working TWRP and maybe we should inform about this huge step forward.
With TWRP we can make a complete backup of all partitions like NVRAM/System/Cache, etc

Is there no other way to get a full system backup now that I have a fully rooted system.

[Riddick]

Yes, we are treading new ground with this new chip.

I wish I had one to play with, but I don't.

I've disabled the ability to install OTA updates in my ROM. The reason for this is simple. With a rooted ROM, changes are made to system.img and boot.img. If boot.img is updated, root is lost...and you could possible have boot loops because of conflicting files.

The best way for me to get an updated firmware version to create a new ROM would be for someone to provide me a ROM dump.

Until now, I wasn't aware that MTK Droid Tools isn't compatible with this chip. Therefore, I don't know of an alternative way of dumping the firmware.

If anyone comes up with a solution, please post....and also post the OTA update (or PM me with a link) and I will continue supporting this device with new ROM's.

I don't currently have a T9...so any help is greatly appreciated.

HAHAHA, great Riley say it now, I would have done a ROM dump for you last night. But now I have just reinstalled all my apps.

If no one else offers you a 1.06 ROM dump, then I will give you a 1.07 ROM dump when/if it comes out, when i go to do my upgrade.

My promise as I do love your work Riley.

[Edius]

I still think MTK Droid Tools incompatibility is due to tee1 and tee2 files. These files are named in U65GT(and in many other MTK based devices FW) firmwares EBR1 and EBR2 and gives information about how large should be System/User partitions size.
I haven't found any knowledge about this particular type of files.
Maybe someone will be so kind and will modify these damn files and give us some options like 4/6 GB alternatives for System partition size.
As far as I understand Randy disabled OTA updates in Cube_T9_RileyRom V 1.0 and gives some information about reasons for that.

For the moment we have three options:
1. FW untouched/unrooted with OTA capabilities.
2. FW rooted with iRoot/KingRoot - root will be lost after next OTA updates/OTA update packages will give us some errors when installed.
3. FW Cube_T9_RileyRom already rooted/user will have to stick with it.
I see some alternatives to these 3 options written above like a patch for root like U65GT have here who works with original CWM with option to do/undo root.

This will work like this: Flash default firmware (1.04 for now)/apply all updates OTA up to date/apply root with patch like this/enjoy your rooted FW/after we get information about new OTA pushed updates apply second patch to undo root/apply new updates OTA/apply root patch/enjoy.
This sounds pretty tricky but is the only that runs on my mind right now to keep OTA enabled and system files integrity.
To have this kind of root/unroot we need two patches...hopefully, we will see in future if someone will do that successfully.

[Ogu]

Hi guys.

Riley many french thanks for your job!

I think a summary of any root/flash methods would help a lot, with screenshots, links, how-to etc...Is anybody could write this?

I am waiting for the next OTA update to see if it break my rooted OS. If yes i'd like to restore the original ROM cleanly and to start a fresh system.

@ Edius : iRoot can unroot the system before OTA update, isn't it? And then you just have to root your OS back.

[Riddick]

Hi guys.

Riley many french thanks for your job!

I think a summary of any root/flash methods would help a lot, with screenshots, links, how-to etc...Is anybody could write this?

I am waiting for the next OTA update to see if it break my rooted OS. If yes i'd like to restore the original ROM cleanly and to start a fresh system.

From what I have read and experienced, documented in this thread is that the rooted ROM prevented me from running the OTA update from 1.05 -> 1.06

@ Edius : iRoot can unroot the system before OTA update, isn't it? And then you just have to root your OS back.

iRoot fails to unRoot, from what i could see is it changed sys files but not all the ones necessary. Effectively this screwed the Permissions and I could no longer reroot it. I did this all via the pc, AND NOT THE APK. Do not use the APK under any circumstances, it can screw with sys files and leave them corrupted. I am only referring of course to the Cube T9.

I am going to do some more research on sys tools for android that allow me to backup the NVRAM/IMEI safely and accurately.

[Ogu]

Thanks for this informations, i didn't know iRoot fails to unroot.

Do you know if the OTA update will break a "iRoot rooted" system (not the pre-rooted ROM)? Cause a simple rooted system do not prevent OTA to run if i do not make a mystake.

In case of troubles with OTA breaking my boot, what is the way to restore a fresh ROM? There is many way descripted in this topic but i need something synthetized ^^

[Riddick]

Thanks for this informations, i didn't know iRoot fails to unroot.

Do you know if the OTA update will break a "iRoot rooted" system (not the pre-rooted ROM)? Cause a simple rooted system do not prevent OTA to run if i do not make a mystake.

Well if you read this thread you notice I thought exactly what you understood. I rooted mine with Kingroot once I had upgraded via OTA from 1.04 -> 1.05.

When I ran the OTA from 1.05 to 1.06 as a rooted device it sayed my system was 'damaged and upgrade has stopped process has been disabled.'

The only way I could fix this was to flash the stock rom and run the OTA upgrades from 1.04 to 1.06 as I have spammed this thread about.
Once I had completed the OTA upgrades I then ran the iRoot. The only reason I ran iRoot is because it was the only 1-click root app that I knew did work in rooting the device that had the option to unroot my device. However this may no longer be an issue seeing as I now have installed SuperSU binaries which allow me to unroot the device via the APK.

At the end of the day all this could be wrong and it could be simply related to the 1.05 version, I honestly have no idea, as this is the first time I have flashed a chinese tablet.

In case of troubles with OTA breaking my boot, what is the way to restore a fresh ROM? There is many way descripted in this topic but i need something synthetized ^^

[Ogu]

Thanks!

I have SuperSU installed too : how can i "unroot" my system with this app??

Would be great if you could write a memorandum to explain how you definitively manage to flash the stock ROM!

[hammerjoe]

Today I am not able to check for ota firmware update.
It gives the error message that network is no it avail available.

Anyone else has the same problem?

[Riddick]

Thanks!

I have SuperSU installed too : how can i "unroot" my system with this app??

Would be great if you could write a memorandum to explain how you definitively manage to flash the stock ROM!

Ogu to do a stock rom flash you need to do the following ( before you action the below steps ensure you have installed the correct MTK Usb drivers, go here to get the complete set.

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

1. Download Rileys Custom T9 rom bundle
2. Download the Stock rom from the Rileys post here
3. Now the reason I downloaded Rileys Custom bundle was because it the pack you need to be familiary with to manage your MTK tablet for the future.
As it stands we are not aware of a recovery app that can replace the stock on at this stage.
4. Make sure prior to doing any flashing, it may not be entirely necessary seeing as Edius has pointed out that the NVRAM/IMEI won't be touched if you only do a "Download only" or a "Firmware Update."
5. Follow the steps specifically related to the backup, disregard the steps related to the NVRAM/IMEI as that button will always remain greyed out as the device is not supported by MTK Droid tools. However you can in the next tab at the top do a backup which at least back up your NVRAM. At this stage this backup process is more out of precaution than anything directly to restoring a stock rom as the process is only related to the OS and not any other partition on the system.
6. Extract the stock rom rar file to your desktop and change the chinese characters to English, now these names honestly could be anything as the subfolders are in english, however if you want to understand what the chinese says I copied the chinese characters and dumped them into translate.google.com
6. Open the SP_Flashtool the stock rom is bundled with
6. Use SP_Flashtool and populate it via the scatter file you will find is also shipped with the stock rom.
7. Now here is the part that did my HEAD IN -
- Once your scatter file is loaded
- Click the Download Button just below the Download tab
2. The tablet MUST BE ON WHEN YOU ATTACH THE USB TO THE PC.
3. HOLD THE POWER BUTTON UNTIL YOU SEE THE ACTIVITY BAR Below your selected files
4. You will know when the flashing is complete because a pop-up appears with a big tick.

*note: the flashing appears to occur during the shutting down of the device.

Once you have completed the above steps, boot your device and active your wireless and go nuts installing the OTA Updates

Once you have completed that -

1. Use iRoot via your pc to root your device
2. Once rooted install SuperSU then install the binaries which is an option within the app.

Today I am not able to check for ota firmware update.
It gives the error message that network is no it avail available.

Anyone else has the same problem?

Make sure you are doing the update via a wireless connection and not your 4G/3G connection. Its all I got Hammerjoe, lol.

[Lotte234]

Direction of SC Card

hello

Shipped by DHL 3 hours before - my new cube T9. One question I have:

the direction in which I put the SD card into the tablet - Contacts forward or backward from Display?

[giouncino]

you can put it in only in ONE direction!
you can't go wrong

[Lotte234]

you can put it in only in ONE direction!
you can't go wrong

the SD card does not go into the tablet, no matter what. Maybe I'm stupid?