The big thread of How-Tos

[jetfin]

Laura, thanks much for this great thread!

I have some good news for all of you, thanks to xda member vampirefo we now have a working custom recovery (TWRP 3.0.2-0)

Worth noting if you intend to flash SuperSU from recovery is that due to unusual moint point of system, the SuperSU script will not properly mount system and it will not actually flash. Before flashing SuperSU you need to manually mount system in TWRP!

I have posted a general step by step for unlocking, flashing modded boot image, flashing TWRP recovery & SuperSU here

 

Cube iWork 10 Ultimate Android hacking & development discussion: http://forum.xda-developers.com/t/iwork-10

[Jade J. Munkey]

Yes, great work Laura, and jetfin. I have this bookmarked ready to use when mine arrives.

[Laura]

jetfin wrote:

Laura, thanks much for this great thread! I have some good news for all of you, thanks to xda member vampirefo we now have a working custom recovery (TWRP 3.0.2-0) Worth noting if you intend to flash SuperSU from recovery is that due to unusual moint point of system, the SuperSU script will not properly mount system and it will not actually flash. Before flashing SuperSU you need to manually mount system in TWRP! I have posted a general step by step for unlocking, flashing modded boot image, flashing TWRP recovery & SuperSU here

 

that’s great but… does that recovery stick? cause the boot.img contains the original one and it’s supposed to re-flash it if it detects a change, so theoretically we should put this in the boot.img…

[jetfin]

Laura wrote:

that’s great but… does that recovery stick? cause the boot.img contains the original one and it’s supposed to re-flash it if it detects a change, so theoretically we should put this in the boot.img…

Need to rename /system/etc/install-recovery.sh to install-recovery.sh.bak or delete it. Preferably in TWRP file manager before first boot into android otherwise it will just overwrite with stock recovery. Then it sticks just fine. 🙂

I put detailed instructions here…

Cube iWork 10 Ultimate Android hacking & development discussion: http://forum.xda-developers.com/t/iwork-10

[jetfin]

I’m trying to make a recovery flashable stock deodexed, debloated Android ROM and my main obstacle at this point is not having access to an update-binary compiled for this device (intel).

Does anybody happen to have an official updater zip (OTA or otherwise) for this device??? What I would need is a copy of the update-binary file located in the META-INF folder….

Cube iWork 10 Ultimate Android hacking & development discussion: http://forum.xda-developers.com/t/iwork-10

[jetfin]

jetfin wrote:

Does anybody happen to have an official updater zip (OTA or otherwise) for this device??? What I would need is a copy of the update-binary file located in the META-INF folder….

No need, I managed to find one in the meantime. 😀

Cube iWork 10 Ultimate Android hacking & development discussion: http://forum.xda-developers.com/t/iwork-10

[Jake]

Does anyone have full drivers in a single zip file.?

I thought we could think about how could we reinstalling fresh window

if its is in any case cube cancel their support line:

Edit: found it from MisterDeery comment

http://techtablets.com/forum/topic/touch-and-camera-after-clean-win10-install/#post-32552

Edit2: alternated source for download(i’ve problem with onedrive)

https://mega.nz/#F!0AVVCJiL!z2NN8hIZEJPQBTngxgVkuw

[Andrew]

Many thanks for the thread!

 

I’m trying to root Android (for now just flashing the modified boot file) and while I’m downloading the big 6GB file, I tried to run CMD as an admin but after entering “fastboot device” (without the quotes) I get a permanent “< waiting for any device >” and I don’t get the device listed.

 

What to do next? Thanks!

[Andrew]

BTW the tablet is connected to the USB port and the drivers were already installed. And when connecting with Android booted already I see it on Windows Explorer as Portable Device named i15-T.

 

Thanks

[Jade J. Munkey]

@Andrew – When I rooted android using jetfin’s instructions, Windows needed different drivers when the tablet was in fastboot mode, you may be in a similar scenario. Check this link for details :

http://forum.xda-developers.com/android/general/cube-iwork-10-flagship-dual-boot-i15td-t3367954

[Andrew]

Thanks Jade!

I tried those instructions but my device still not detected on my PC neither by adb (only show emulator responses) or by fastboot (doesn’t return anything). I checked that developer options on the tablet were active (OEM unlocking & USB debugging) and then rebooted with same results.
Otherwise the tablet’s internal and microsd memory can be seen and used in the PC.

BTW winrar reports error on the big rar 6GB file “Cube iwork10 Ultimate(i15-T)dual boot files.rar”. Any way to have a MD5 sum?

Thanks!

[Andrew]

Anyone?

On the command line (CMD run as an administrator):

1- After typing adb devices I get a list of emulator-56nn –about 15 items

2- After typing fastboot devices I get nothing just an immediate return to the command line.

OEM unlocking & USB debugging were active on the tablet

 

So what else can I do to try to root the tablet?

Thanks!

[Laura]

you’re not following the procedure closely then

[Andrew]

 

Thanks for the input but maybe fastboot mode is not explained? I mean I see a instruction:

 

1. boot tablet in fastboot mode (see other section)

 

But there is no other section where it’s mentioned this fastboot mode (is that the same as DNX mode which is actually mentioned?)

 

[Andrew]

Now I did the instructions for booting in the DNX mode (with chinese logo and the yellow text DNX FASTBOOT MODE on a black background) and I get the same behaviour with both command-line instructions I described before.

[Author]

Posts