yashsingh1/xdaforums huggingface dataset:
[Android General] PassieWater:
I did backup my boot image.... But the file is corrupt... Cant read the Sd card anymore... Grrrrrrrrrr.

Someone got a proper backup for the TL model PLEASE. Or knows where to get it?

Thnx for reply
[Android General] jetfin:
I linked to Laura's thread in the OP - there is a downloadable zip there that contains a modified TL boot image
[Android General] PassieWater:
I have messed up. Twrp cant find or mount data... Not even manually.....

And now?

System keeps bootlooping to twrp
[Android General] jetfin:
Sounds like you'll need to reflash the whole tablet with the factory package - follow the link in the OP for Laura's thread at Tech tablet.com for information about that. (once again, it's all there in the OP... :/ )
[Android General] czajunia:
I have just received the iWork 10 which is the v2 version with the USB type-C and crippled memory speed.

Has anyone had problems connecting their iWork 10 to Windows through USB? I have no idea what is wrong but when I plug in the tablet to my PC nothing happens. At all. Neither on the tablet nor on the PC. There is no prompt on the tablet to pick a USB mode as if it wasn't even connected. When I connect my LG Android phone Windows immediately recognizes the device and if I enable USB debugging ADB works fine and my phone is recognized.

Is there a chance that USB connection was disabled or even removed from the installation? Any idea how to make it work? Thanks.
[Android General] xyesos:
Video have for root td version?
[Android General] czajunia:
OK. It's all working. After reading some info at TechTablets forums I was led to believe that USB-C port is only used to charge the tablet and the micro USB port is for everything else. So initially I didn't even try using the USB-C port when connecting to the PC but at some point I thought to give it a go. It turned out that's how it works.
[Android General] Jade.J.Munkey:
Can't update to newest SuperSU

Hello again,

I had initial success in the method outlined in the OP (thanks again); now sometime later SuperSU wants to update via Google Play, after doing so I receive a notification from SuperSU that the binary needs to be updated. The 'Normal' method fails, and the method where the app reboots and tries to update through a temporary TWRP leaves me with the same notification upon rebooting in to android ( I assume due to the unusual system mount). I tried installing UPDATE-SuperSU-v2.76-20160630161323.zip manually via TWRP after mounting system, again, upon rebooting into android I still get the notification that the SuperSU binary needs to be updated (which if I try again via either method, fail again).

Any help would be appreciated.

P.s. I forgot to mention that currently I am running i15-T_Stock_Odexed_Debloated_Root.zip (Thanks), I am not sure if this is of any relevance.

Nevermind, SuperSU-v2.78-201609011115.zip installs fine. :)
[Android General] xyesos:
how to use? pls help me

You use with cwm?

As would not have a brick(

Pls make video for noobie
[Android General] Cube iWork 10:
Help, android error

Hello everyone, I have a problem with my cube iWork 10 (i15TD) dual os, build number is i15-T_v1.0_20160302. The tablet is NOT rooted.

I hope someone can help...

After I had some problem turning on The tablet I thought restoring to factory settings might help, so I restored the Windows 10, and all went fine. Then I restored the android From factory data-reset all personal data. However, now I can not enter a backup account. In the backup account I see "backing up to debug-only private cache".

I tried to google about this issue but couldn't find nothing except something that fix it with a root.

Can anyone please help about this issue?
[Android General] xyesos:
How did he do it ? Where to put this file??? :crying:

I need to make a backup! But I don't know how to do it. Tell me somebody. And as this archive to do in Root?

Do in pictures, I don't understand
[Android General] Ceccis:
Guys, I need help. I bricked Android on my i15-TL. My back-up files are corrupted and I don't know how to solve.

Does anyone have backup files for Android on i15-TL? I can access TWRP, so I can restore backups from there. Please help
[Android General] filipe_m:
Sory my basic question...

But when i connect the iwork to Pc nothing happens..

I tried with Type C connection and USB 2.0

Someone can give me some tips?

Could be a drivers problem? I see the "AndroidUsbDeviceClass_Win10_64bit.zip" on first post but i don´t know how use it

Thank you
[Android General] xyesos:
Need tutorialo video how root and backup
[Android General] RASTAVIPER:
This topic must have some of the most not helpful members that someone can find at XDA.

Many people have questions or problems and although there are more experienced users around, still most of the questions remain unanswered.

At the end of the day, it's ok if you provide some instructions and guides, but you should be prepared also to reply to people who have some issues with your info .
[Android General] brainvision:
hey there, don't know if you solved your issue with /data partition corrupted, if not I can give you hint, I had the same problem and solved by creating the partition from custom recovery.. You can read the thread linked below into the EDIT section or ask directly, see you ;)

- - - - - -

totally agree with [MENTION=4043335]RASTAVIPER[/MENTION]

also, I have a question for whom who may have a iWork 10 Ultimate i15-TCL (Type C variant, so). I own this tablet since July but I'm rooting it just now, mostly because I used Windows 10 there since I have many others Android devices; but now it's time to root this one, too. Strange is that when I boot into fastboot I found the bootloader already unlocked; I'm sure I did not do it, but here I find:

SECURE BOOT - DISABLED
LOCK STATE - unlocked

So, my question: do you guys noticed the same thing? Am I the only one with a TCL model already unlocked? Naturally I still have to root and install a custom recovery, it's just the bootloader to be unlocked..

Thanks a lot guys, see you!

EDIT:

also, please, if you can take a look here and try to help.. thanks a lot
[Android General] RASTAVIPER:
I just received a TCL.

Is there an easy way to check what you have mentioned?

I don't have adb installed.
[Android General] brainvision:
sure, you just need to access the bootloader; to do that, turn off the tablet, wait 10 seconds just because and then press the power button and turn it ON; once at the OS selection menu tap Android, then tap OK and immediately AFTER tapping OK just press and keep pressed the Volume - button; keep it pressed until you are in bootloader.. there you'll find 6 or 7 lines of text, the last are the ones we are looking for..

Also if you follow the link into the EDIT section of my previous post you'll find the entire story of my root experience with this tablet. I really thought I messed it completely and that I would never be able to use Android anymore, but then fortunately I create the /data partition from scratch and then flashed a rooted i15T ROM.. now I have a TCL with a T ROM! :D Everything is working as normal, btw. The problem is that only a few of us have the Type C variant; I suggest you to backup everything with Macrumium Reflect but also by usign the dd command for every single partition.

If you agree you could also provide me those backup (you don't need to backup personal data, only system partitions) so that I could be able to entirely restore my unit, but to be honest I'm fnally happy with the Android part of this tablet: now I have root and Link2Sd so that I have more space for apps; while with the original rom of the TCL variant I only was able to mess things up (pretty sure it's because of the modified boot.img file - you need to modify it by yourself, the one provided by [MENTION=7154855]popcorn2404[/MENTION] seems to be from April 2016 while mine was from May 2016)

Also, please, if you follow the link in my last post I made a few questions in techtablets forum, would you mind to try to check them, too? It would be great!

Thanks a lot, see you!
[Android General] RASTAVIPER:
Just tried that.

Nothing happens with the volume up button.

Is it the moment that the blue Chinese letters are on the screen?

Also how to use the macrium reflect?
[Android General] brainvision:
Just briefly (I'm on tablet ATM) I said Volume - (so volume Down). Ad sono ad possibile I'll reply YOU from PC

Inviato dal mio i15-TCL utilizzando Tapatalk
[Android General] jetfin:
I did this work for myself and provided it as a favor for the community. You will find in this thread and also the stock rom thread that unanswered questions fall into these categories:

1. Person didn't thoroughly read OP

2. Windows related (this is an android thread and a link to other forum that has more windows related resources and users is provided in OP)

3. Other device variant (created this thread for i15-TD/TL)

4. Off-topic problems or questions not related to this device and better posted in a more appropriate xda thread.

I actually have a day job and this job has me working 12 hour shifts 7 days a week on ships offshore at remote locations around the world, usually with crappy internet, if any at all. Someday I hope to have a more normal job/work routine and be able to be more active on xda but until then i will just continue to share what I can regardless of some peoples ungrateful attitudes and ridiculous concept that just because I make a howto I should answer OT questions, cater to people who can't read OP or worse yet cater to people who shouldn't even be here due to lack of knowledge and/or experience with android dev & hacking. There are plenty of great resources for learning the basics here on xda and I will not cater to people who are too lazy or impatient to learn them before trying to hack their devices.
[Android General] RASTAVIPER:
Ok, I managed.

Mine is locked.

So, you definitely did something with your own and you unlocked it. Even without knowing it.

Thanks for the favor.

What did you expect to happen afterwards?

What you wrote is the ideal scenario.

People would read/know a lot about these things etc

But in XDA, its usual to find all sort of people.

So your approach is that you first help and then everyone is for himself.

On the same time, also no other people weren't interested or knew how to help other members.
[Android General] master.pumpgun:
My i15-TCL is also unlocked and I did nothing. Dumped the boot.IMG and it looks like the modified on the first page just without default.prop edited. Got mine from gearbest this week
[Android General] RASTAVIPER:
Maybe GB unlocked it then.

I doubt that it comes unlocked by the factory.

Anyone that can tell me how to do the Macruium backup?
[Android General] brainvision:
hi master...

How did you manage to dump the boot.img file pf the parttion? DId you use dd? And what size is your boot.img once extracted?

I can't understand what's the matter..

I extracted mine (also I had bootloader unlocked and one of the modification required for the build.prop to root was already there) and it was 30 MB big.

But the boot users posted here are less than 11 MB! A user from techtablets extracted the first 5 partitions and his boot is also 30 MB, don't know how he extracted BTW, still asking..

The only explanation I can think is that with dd you get a 30 MB file, once you unpack and repack the compression is bigger so the file is smaller.. BUT I have the original CUBE files for i15-T variant and the boot.img is still 10,2 MB! I'm becoming mad!! :(

[MENTION=3563432]jetfin[/MENTION] do you have any clue about that, please?

Also, if you guys need original dumped partitions for the i15-TCL ask, I'll share the links after asking the original uploaders.. see you soon
[Android General] jetfin:
I initially backed up all the partitions with dd when I first got the device. (i15-td)

dd boot.img files were around 30mb and twrp boot.img ones around 10mb.

From what i understand dd writes the whole partition including empty space whereas with twrp you're just getting the actual data on that partition.

I've flashed both of them no problems with same results.
[Android General] brainvision:
Ok guys, so...

I finally managed to root my TCL after modifying the boot.img; the issue was due to the new android boot unpack tool version, that needs to use the option in a different way from Laura OP in techtablets thread..

Also, once you flashed the boot.img there's no need to use the root.bat method (actually to be run 2 times after rebooting), just download the latest SuperSU TWRP file from here http://www.supersu.com/download, flash the T/TD/TCL custom recovery, boot recovery and allow modification to /system partition and then flash SuperSU..

If owner of the TCL should need the boot.img file for the May kernel build, just ask and I'll pass it to you, no problem..

See you! ;)
[Android General] RASTAVIPER:
So, is this an easier way to root it in comparison to the first post?

If yes, can you give more like a step by step guide for beginners?
[Android General] brainvision:
I'll write an HOW-TO for TCL unit in the afternoon (here in Italy it's lunch time) basically divided per 2 sections: first, the manual way to modify the boot.img and root and second the "automatic" way providing all necessary files that the user have to flash..

I have to say, BTW, that it's not a question about easy and difficult, yea the Laura thread is actually missing something but I think it's because of the techtablets forum editor which is pretty bad (like it cuts some stuff the user write; for example you write a double -- that becomes single - when publishing the post) and the new android_tools_boot version which changes the command option you need to add to your command prompt. Once you get into this I think it's important to understand those stuff, because - even if it would hardly happen - if Cube update the Android version or kernel it would be very risky to use the "automatic" way.. But this is another story.. ;)
[Android General] RASTAVIPER:
Buongiorno!

You must be one of the few Italians that can write English so well!

Can't wait to try your method.

Will it be required to make a factory reset?
[Android General] brainvision:
well well well well! Thanks for your kind words about my English but you got to believe me if I tell that a lot of italians known english better than me, it's maybe that you (still) don't know the right ones! ;) :D

about your question related to the oem unlock it's what I'm trying now: I searched and searched and it seems that a limited number of devices could be rooted without unlocking oem, but it's clear that you will not able to boot a custom recovery or a custom ROM, in that case, so the only way is trying to flash SuperSu with Flashify..

I'm trying it know starting with an unrooted and oem locked restored iWork..

Sorry if I ask you again but last time your reply was not so clear.. So could you please tell me again after checking once more your bootloader? I'll tell you the steps:

1. OFF you iwork

2. Press Power ON until you see the led bright on

3. choose Android and tap OK (a shortcut for that is pressing the volume UP for Android and Volume Down for choosing Winzozz) and immediately after that press and keep pressed Volume Down until you reach the bootloader..

There you should look for two fields:

SECURE BOOT - ............. (please report yours)

LOCK STATE - locked (this one you told me is locked, isn't it?)

So, lock state is the well know oem lock/unlock that wipes userdata, while the SECURE BOOT is related to the Windows UEFI BIOS and I don't know if it matters to us. I managed to enter the BIOS from WInzozz (Settings / Update / Restore / Advanced and then Troubleshot / UEFI BIOS, like they tell here: http://www.digitalcitizen.life/how-boot-uefi-bios-any-windows-81-tablet-or-device) and in my BIOS settings at Boot voices the Secure is already disabled. If you could check that, too, it would be great
[Android General] RASTAVIPER:
I thought that my reply was obvious.

My bootloader is locked.

Also currently I don't care to flash a custom Rom, only to root my tablet.
[Android General] brainvision:
as said, those are two separate stuff..

once is SECURE BOOT and it should be related more to Windows

the other is LOCK STATE and it's the Android bootloader..

into your reply days ago you told me about the bootloader not the secure boot.. ;)

For example, I'm telling you that I did

fastboot oem lock

and the SECURE BOOT is still disable, that's why I'm asking you what you have there for both fields..
[Android General] brainvision:
so it seems to me that it's impossible to obtain a temp root and recovery into this device, so at the moment OEM unlock is still required.

For [MENTION=4043335]RASTAVIPER[/MENTION] and for who may need it I wrote a very detailed step by step guide for the i15-TCL, also providing all files needed ad my personal modified boot.img, tested more than once and perfectly working. hope you'll find it useful, here's the link: [GUIDE|HOW-TO|ROOT] Cube iWork 10 i15-TCL - Root / Recovery / Boot.img [WIN|LINUX]
[Android General] RASTAVIPER:
Here is my status:

SECURE BOOT: DISABLED

LOCK STATE: VERIFIED
[Android General] brainvision:
so, I tried to boot the TWRP without flashing it with fastboot boot recovery.img bu as expected even with the unsecured boot the bootloader blocks the temp flash, sorry you'll need to unlock if you want to root ;)
[Android General] nealeegg:
Fast boot oem unlock not working 'remote: unknown command'

Help! I installed ext2fsd on Windows 10 so to read ext4 and now Android doesn't boot. Windows 10 is still fine. I hadn't enabled Android developer mode/ USB debugging and can now only get my PC to recognise the device in fast boot/ DNX mode. Any fast boot command I try is generally returned with 'FAILED (remote: unknown command).' In Recovery the device is not being picked up by Windows 10 or Windows 7 device manager at all. Am I missing something or is it looking like I may need to re-flash the entire thing using Intel Flash Tool and factory firmware - latest is dated 26/05/2016 located 51cube.com/ch/DownShow.asp?ID=407 - of which I can't currently download as requires Baidu account which I can't create due to not accepting any phone number I try.

Options please?
[Android General] brainvision:
hi there, don't understand how exactly did you messed things up by just using a windows program, it's very strange but I prefer not to investigate this :D

you can look at techtablets forums for mirror of the restore oem stock images and how-to in english
[Android General] nealeegg:
Thanks brainvision. Steve C had similar issue here when installing Ext2FSD - techtablets.com/forum/topic/unable-to-boot-android-win10-boots-ok/ ..ext2fsd must have written something to the android partitions to cause the problem.

Found a shared google drive copy of the latest firmware in a user post here - cube-tablet.com/cube-iwork10-ultimate.html. Did a recover of android via DNX mode which was fine but it wiped out the windows partitions, so reinstalled that by booting off a USB key with latest windows 10 build rather than using the Cube Windows 10 WIM image. Just performed a standard Win10 Pro install which got Windows 10 working but with no drivers installed. Extracted the Cube Windows 10 Install.WIM and used the drivers from C:\Windows\System32\DriverStore\FileRepository to update all devices from a USB key via device manager. All back up and running.
[Android General] brainvision:
great, just 1 thing: you would been able tor restore only the Android side by using fastboot flash etc with the Android images provided into the zip you downloaded; next time you can try that instead of losing the Windows installation too ;)
[Android General] flowin_through:
Hello all,

I received my TCL version, it is a very good tablet but I'm surprised no one mentioned that it kills apps, it never goes over 1GB RAM! just all the other 4GB-RAM Chinese tablets!

I fixed my Chuwi hibook pro with this fix http://xdaforums.com/showpost.php?p=67862906&postcount=30

Is there anything similar for cube?
[Android General] RASTAVIPER:
In Android or in Windows?

Sent from mTalk
[Android General] flowin_through:
Android ofcourse..
[Android General] hetzbh:
Regarding the TWRP..

It seems that this version of TWRP doesn't work with adb command. Running "adb devices" from my Linux machine shows no devices at all (so I cannot do any push command or do a backup command from ADB) and it doesn't show the tablet (when in TWRP/recovery) using MTP even when trying to enable/disable MTP.

Is there a fixed version of TWRP somewhere?

Thanks
[Android General] brainvision:
Never noticed that, I'll see if I'll be able to fix it using the same workaround..

Well it's a very common issue, I already had it with other devices.. but you can try to edit your udev rules so that at least sideload should work.. search Google for 'adb android user rules"

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[Android General] hetzbh:
I'm afraid it's not related to rules. If it was rules (an issue which I had tons of times) then adb would show "no permissions" and on Fedora, the simplest fix would be to run: sudo systemctl start adb ;)

Anyway, the device doesn't show even on Windows when running TWRP.. when booting to fastboot, fastboot shows the device and the standard android shows the device with ADB.

Edit: I checked this with 2 more tablets (same - iwork10 ultimate). Issue is the same, only happens with TWRP.
[Android General] brainvision:
Yes you are right, not related to udev in this case, but when I tied to use sideload I got the no permissions error and because I don't like to use root for common stuff I added use rules..

BTW you are indeed right.. [emoji106]

On a side note, I want to contact vampirefo to ask him how did he ported the recovery for this tablet. I own the TCL variant but I still use the T one recovery, which lead to errors when flashing my mod ROM if not I don't change the updater-script.

I will also ask him about and from recovery, hope he knows how to fix..

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[Android General] hetzbh:
sideload works without permissions issue because it's a protocol to only push files, so it doesn't need permissions to access local (PC) resources.
[Android General] brainvision:
Weird, didn't work for me into my debian stretch! Always had no permission error!

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[Android General] hetzbh:
On Debian stretch I think you should use the adb package from their official repo and IIRC it also solves the issue of permissions, just don't forget to run systemctl start adb and this should take care of any permissions issue so you can work without being root on your Debian machine
[Android General] brainvision:
Neer used root and using the official android SDK platform-tools (I also need Android Studio) and solved issues I found with udev rules.

At the moment the only issue is about adb and recovery, but it's not really hurting me..

But thanks for your hint, I may find it useful in the future! ?

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[Android General] brainvision:
I just tried the already compiled apk from the post you provided.. it works, or at least it installs and the tool starts nice: I still ha no time to test it but I guess it should work..

Did you already tested it?
[Android General] flowin_through:
No, I haven't attempted, because the tablet was not intended for me.. I will ask if I can find it again..