FORUMS
Remove All Ads from XDA

[HOWTO] Cube iWork 10 Flagship Dual boot (i15-T) - unlock, TWRP, root

297 posts
Thanks Meter: 135
 
By jetfin, Senior Member on 28th April 2016, 04:42 PM
Post Reply Email Thread
WARNING: Performing the actions decribed here will void your warranty and possibly brick your device. This was not written for complete noobs and assumes some prior experience. I will not be held responsible if you ruin your device.

NOTE: This was all tested on a stock iWork 10 Flagship dual boot (aka iWork 10 Ultimate) purchased from the manufacturers website. Device model is "i15 T", Device serial number starts with "i15TD": if you have another variant such as i15TL i can not vouch for any of this working the same way.is tablet
UPDATE: @popcorn2404 modified the boot.img on his USB Type-C variant if this tablet (i15-TCL), confirmed everything working well and was nice enough to provide the modified boot image. See downloads at end of post.


OTA: Most likely this will break OTA. Dont know yet...

Prerequisites:
  • PC with working ADB/Fastboot
  • Device properly recognized.
I'm using ubuntu 15.10 so I just added an entry to /etc/udev/rules.d/51-android.rules to get things going properly

(EDIT: Windows 64 bit usb drivers attached to post -thanks @Jade.J.Munkey)

TIP: I would highly recommend extracting your stock recovery, boot and system images for safekeeping. These can easily be flashed back in fastboot if something goes wrong. Some may say this is overkill as you will be able to backup and recover with TWRP, but one never knows...


Unlocking bootloader

WARNING: this will erase all data, settings, etc... AND system default language will be chinese when you reboot
  1. Go to settings, about tablet and tap 5 times on the Build number to activate developer options
  2. Go to Developer options and enable OEM unlocking & USB debugging
  3. Plug in your device while booted into android, then open a terminal

just to make sure adb is good type
Code:
adb devices
my output looks like this
Code:
List of devices attached 
0123456789ABCDEF	device
reboot tablet into fastboot mode
Code:
adb reboot fastboot
The device will now reboot to the OS selection screen. Select android and then it will boot into fastboot mode

once again just to be sure all is good type
Code:
fastboot devices
once again, my output
Code:
0123456789ABCDEF	fastboot

then to unlock the bootloader
Code:
fastboot oem unlock
you then should see something like:

Code:
...
(bootloader) Unlock protection is set
(bootloader) Unlocking anyway since this is not a User build
OKAY [ 15.330s]
finished. total time: 15.330s
This is what you should see now in the bootloader if all went well:
SECURE BOOT - DISABLED
LOCK STATE - unlocked


Your bootloader in now unlocked. When you reboot it will take some time for the first boot and the system language will have defaulted back to chinese. Not too difficult to sort if you're familar with Android settings. Otherwise just google "android change system language from chinese to english".

Tip: At this point you may want to already download/copy the supersu zip to internal storage of the tablet so you're all set up for flashing it later...

Modified boot.img

Because of built in security, if you make any changes to system the device will not boot, so you need a modified boot image.

If you have the exact same kernel version as I do you can download the provided modified boot image here. Otherwise you can look HERE for instructions on how to make your own modified boot image. Personally I used SuperR's Kitchen to unpack & repack the image and did the modifications manually with gedit.

Kernel version 3.14.37-x86_64-L1-R429 made on Wed Mar 2 18:22:46 CST 2016
-if you have that one you are good to go ahead and use the image provided here.

Boot device into fastboot connected to PC. From the directory where you have the modified boot image type:
Code:
fastboot flash boot i15TDboot.img
Obviously if you made your own boot image you'll need to replace "i15TDboot.img" with the name of yours...

That's it, now on to recovery and rooting...


Flashing custom TWRP (compiled by @vampirefo)

Assuming you are still connected to the device in fastboot and the custom recovery is in the same directory:

Code:
fastboot flash recovery i15t_recovery.img
Now use volume buttons to select recovery mode and tap power button.

You should now be in TWRP. First, please be smart and make a backup!

Because this device has an unusual mount point, the supersu script will fail to properly mount system (thus failing to flash) so:
  1. From TWRP main screen select "mount" then select system, then return to main screen
  2. Select "install" and then the supersu zip you should already have on the tablet.

Boot system. Now there is one thing left to do:

To prevent the system from overwriting TWRP with the stock recovery on the next reboot:
With a root enabled file manager mount system r/w and navigate to /system/etc
Rename install-recovery.sh to install-recovery.sh.bak

That's it. Enjoy!



If you're looking for more info on this device, check out Laura's great thread


Thanks
@vampirefo - for taking the time to compile TWRP for this device, you rule man!
Laura - for all the info she's made available for this device
@SuperR. - for his kitchen
@Chainfire
@popcorn2404

Downloads
Attached Files
File Type: zip AndroidUsbDeviceClass_Win10_64bit.zip - [Click for QR Code] (5.21 MB, 2860 views)
The Following 11 Users Say Thank You to jetfin For This Useful Post: [ View ] Gift jetfin Ad-Free
 
 
28th April 2016, 04:44 PM |#2  
jetfin's Avatar
OP Senior Member
Zagreb
Thanks Meter: 135
 
Donate to Me
More
There will be additional resources for this device here
28th April 2016, 04:45 PM |#3  
jetfin's Avatar
OP Senior Member
Zagreb
Thanks Meter: 135
 
Donate to Me
More
Delete
3rd May 2016, 03:20 PM |#4  
Junior Member
Thanks Meter: 1
 
More
Windows 10 64bit fastboot driver for Cube iwork10 Ultimate
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
4th May 2016, 07:20 AM |#5  
Junior Member
Thanks Meter: 1
 
More
Cube iwork10 Ultimate Fastboot driver for Windows 10 64bit
Quote:
Originally Posted by Jade.J.Munkey

When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?

Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.

Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:

onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNI frlvxfvI&ithint=file%2czip

if anyone needs it. (remove space from url before pasting in to browser)
The Following User Says Thank You to Jade.J.Munkey For This Useful Post: [ View ] Gift Jade.J.Munkey Ad-Free
4th May 2016, 01:05 PM |#6  
jetfin's Avatar
OP Senior Member
Zagreb
Thanks Meter: 135
 
Donate to Me
More
Quote:
Originally Posted by Jade.J.Munkey

Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.

Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:

onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNI frlvxfvI&ithint=file%2czip

if anyone needs it. (remove space from url before pasting in to browser)

Glad it worked out for you. Based on your experience I changed the instructions in the OP. Actually that's the exact same I did after doing this the first time but I thought it would be easier to do before first boot in TWRP. Anyhow thanks for pointing this out.

Attached windows usb driver to OP. Thanks!
4th May 2016, 05:11 PM |#7  
jetfin's Avatar
OP Senior Member
Zagreb
Thanks Meter: 135
 
Donate to Me
More
Stock based, recovery flashable ROMs now available:
http://forum.xda-developers.com/andr...i15-t-t3372281
15th May 2016, 11:07 PM |#8  
Junior Member
Thanks Meter: 0
 
More
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
16th May 2016, 02:44 PM |#9  
Junior Member
Thanks Meter: 1
 
More
Will the recovery work with i15-TL?
Thank you in advance
16th May 2016, 04:30 PM |#10  
jetfin's Avatar
OP Senior Member
Zagreb
Thanks Meter: 135
 
Donate to Me
More
Quote:
Originally Posted by flubber1911

Will the recovery work with i15-TL?
Thank you in advance

From what I understand from reading at http://techtablets.com/forum/forums/...k-10-ultimate/
-it *should* work as my understanding is that the TD and TL are virtually identical other than different flavors of windows installed. But I can NOT personally confirm this as I have not tested on the TL variant.

What I can say with a higher level of certainty is that the procedure for unlocking the bootloader should be exactly the same. Once the bootloader is unlocked it is easy to reflash the stock recovery via fastboot should the custom recovery not work properly. (Assuming one has previously extracted an image of the original recovery to begin with. Same for boot and system images.)

So if the custom recovery does not work, it is pretty easy to reflash the original, as well as the original boot or system images should something else get messed up.

Hope this helps. Feel free to ask anything else if anything is unclear...

Sent from my OnePlus2 using XDA Labs
16th May 2016, 04:52 PM |#11  
Junior Member
Thanks Meter: 1
 
More
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
Post Reply Subscribe to Thread

Tags
cube iwork10 flagship, cube iwork10 ultimate, i15-t, iwork-10

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes