yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] kaja008:
Please help.

I found how to update official rom on Needrom.com

I got stucked at section 8: "click Start all"

I am getting the following error message:

"FAIL

Warning: Maybe error as follows:

(1)COM ports number repetitive or invalid

(2)Brom and preloader have the same comport number!

Please modify them in INI file or scan again."

Can you please help me what is the problem? Phone is recognized by PC, so drivers should be OK.

I am on Windows 10 x64.

I am trying to go through below method:

"Install ROM:

Install with SP MDT:

1). Turn off the smartphone. Cable is not connected to the computer.

2). Remove the battery and insert it again

3). Connect your phone to a computer cable. The operating system detects a new device

4). Disconnect the cable from the computer.

5). Run SPMultiPortFlashDownloadProject.exe

6). Choose File> Open File Agent download and specify the file MTK_AllInOneDA.bin (it is in the folder SP_MDT).

7). Click Scatter File and select the MT6735_Android_scatter.txt file (it's in the folder with the rom).

8). Click "Start all".

9). Connect your phone to a computer cable. The program should see and blink. If the phone is not detected, then unplug it from the computer,

remove and insert the battery (if the battery is removable) and reconnect it to the computer.

10). After (OK) click Stop and disable any phone.

11). Completed."
[Device Reviews and Information] frankandwendy:
OK, I will do it. :)
[Device Reviews and Information] kaja008:
To antigag!

Can you please give us a step-by-step guide how to install 2015 11 16 official ROM manually?

Unfortunately It is not offered by OTA...

Come on, let's start to build a community and support for this great phone! ;)

Thanks a lot!

brgds,

kaja008
[Device Reviews and Information] tomthelong:
I flashed the new ROM successfully with antigag's guide! Just choose the new scatter.txt and uncheck userdata to safe your data. Everything else stays checked. Worked for me!
[Device Reviews and Information] antigag:
Hi together,

i'm back from holidays ;) Obviously you found the respective method for flashing yourself :D You can use my tutorial for every rom or recovery flashing. Just start the tool, choose a scatter-file, click Download and restart your connected phone. The scatter-file comes with every suited rom-zip and mananges the install directories for the rom-data (be sure, that the scatter-file name fits to your phone!). You can choose which data should be installed. If you uncheck userdata (like tomthelong did) your data and apps stay untouched during the update process. I highly recommed to do a backup before updating (e.g. with Titanium Backup Pro or via Recovery) and consider that your root may be gone after updating (but you can reinstall it). However, especially for rooted phones i recommend to do a clean reinstall of the rom, when you want to update. Rooting your phone means that you have customized important system values, which will be overwritten with the cubot-standard values during the update. This may cause errors (e.g. bootloop, battery draining, ...). So do a factory reset before flashing and leave userdata checked if you have any problems after updating (and yes, all your data will be lost after that, but you hopefully backed up your stuff :P )

Btw there's a new update for our phone published a few days ago.

CUBOT_X16_5092C_V13_20151215 – full_sf6735_65c_l1-user 5.1 LMY47D

Available at needrom.com
[Device Reviews and Information] Charly0001:
Das OTA Update funktioniert NICHT mehr. Nach dem Update mit TRWP hängt sich das Handy beim Bootvorgang auf.

Nur das Flashen des Original-Roms hat bei mir geholfen.
[Device Reviews and Information] kaja008:
There is a new ROM: V13_20151215 published on needrom.com

Can I flash this new rom with SPMultiPortFlashDownloadProject.exe, if I have a rooted phone with TWRP recovery?

What is new or fixed in V13 ROM?
[Device Reviews and Information] loeland:
V13 is now available over OTA
[Device Reviews and Information] Zunera M:
I got my Cubot X16, just wondering where to buy the screen protector and case for it? Any help?
[Device Reviews and Information] loeland:
I bought my cases on ebay:

Articlenumbers:

331718842585

361258509601
[Device Reviews and Information] Janonym:
Problem

There is am problem after choosing scatter file. It seems to be wrong. Please watch pictures!

What can I do?
[Device Reviews and Information] megthebest:
old wrong flashtool..

use this one 5.1532:

https://mega.nz/#!CBsR2Yza!bhuzY3JJVgyP4GSNktbd4fROXmwbvOI4vQIH5gUo1pA
[Device Reviews and Information] Janonym:
It is not possible for me to flash the recovery because the X17 is not recognized. After restart the X17 nothing happens but I can see the Battery loading graphic. The Drivers are installed correct, even the important Preload Drivers. What can I do? I did it step by step acording your instructions.
[Device Reviews and Information] burimek:
[IMG="flash tool fail"]http://img4.hostingpics.net/pics/870671trmcubotx16.jpg[/IMG]

anyone can help to flash the recovery, i have for all version from flash tool this same error, my version from phone is v13 the last update, with the originale recovery i can flash the super user

???
[Device Reviews and Information] kaja008:
New update for X16 is released: V15_20160202

Does anyone know what is new or fixed in this latest rom?
[Device Reviews and Information] Starzi:
Hello, will come Android 6 firmware for the X16?
[Device Reviews and Information] Laus_bub:
Anyone knows an official way to Download except at needrom ...

Or an official source?

Thanks!
[Device Reviews and Information] chriskoups:
Hi, i bought the phone but does not updates to the latest rom (last update from november) also the phone stay awake for ever...! With the most feature disable (gesture and wifi-bt scans)... Any idea?
[Device Reviews and Information] tatomou:
your system was damaged, wireless update is disabled

Hi!!

After rooting it (thanks to you:victory:), I am trying to install the last update via OTA (20160202)

...Downloaded, but when installing it says:

'your system was damaged, wireless update is disabled'

I guess it is because it was rooted, (I thought I had unrooted it correctly.)

Any quick solution via phone?, I dont care if I loose everything, I rather it...

Or do I need install it manually with the flashhtool?

Thanks in advance
[Device Reviews and Information] xplorr:
Use this uninstall SU "update" below to remove all traces of SuperSU (copy the zip file to your phone sd card).

I had to do it because I could not get my phone rooted, I got endless reboots.

http://xdaforums.com/showpost.php?p=63615067&postcount=2459

---------- Post added at 09:21 PM ---------- Previous post was at 09:11 PM ----------

This procedure did not work for me.

I started with a new updated Cubot X16 version Cubot_X16_5092C_V15_20160202

I could install TWRP-Recovery, but SuperSU failed.

Sympthoms: the phone rebooted enlessly. First it starts doing "application optimizations" for all installed apps.

When that is done, the phone wants to starts, but fails and reboots and process continues endlessly.

I managed to uninstall any traces of SuperSU using this tool: http://xdaforums.com/showpost.php?p=63615067&postcount=2459

After that, my phone started again normally (after app optimizations).

But now I end up with an unrooted phone.

I am sure is was caused by SuperSU, but have no idea why?

Can anybody help to get my phone rooted? Possibly with another version of SuperSU?

Posssibly the procedure is not compatible with version Cubot_X16_5092C_V15_20160202?
[Device Reviews and Information] kaja008:
Latest version V15_20160202 is not compatible with old TWRP recovery, I can confirm.

Moreover this latest version is crap, for example I don't receive notifications for many apps, for example Viber. I can only see my messages when I enter into the app.

I am going back to V13...
[Device Reviews and Information] menschenhain:
On my CUBOT X17 touch input is not working in TWRP. Is it a solution to try an older version of TWRP and if so which version? What else can i try?
[Device Reviews and Information] Patxperia:
I'm waiting for my cubot x16 to arrive, and want to root it. If v16 is installed already do you recommend I download v13 and follow instructions on installing it, before or after rooting?

Another question is related to the StryFlex LP Minimal Edition rom, based on cm12.1 that requires an unlocked Bootloader. Is x16 already unlocked?
[Device Reviews and Information] xplorr:
I believe V16 firmware is not out yet.

Latest is V15, but I could not root this version. I ended up with TWRP installed, but could not install SuperSU from within TWRP. My phone booted endlessly.

I had to remove SuperSU, then phone booted normally, but no root.

when your phone arrives, could you tell me if you are successful in rooting V15 and how you did it?

Somebody else successful in rooting V15? Reason why endless booting?
[Device Reviews and Information] Patxperia:
I meant v15 , hope that won't be on the phone. I read on the cubot forum that there is a power boost bug. Perhaps if you disable that app that might allow the root to take.

http://forum.cubot.net/viewtopic.php?f=16&t=230&start=10
[Device Reviews and Information] Patxperia:
I installed TWRP recovery and Cubot ROM v13 using a linux version SP_Flash_Tool. It works very well, I found a few tutorials some helped more than others. If anyone is interested let me know ad I'll write it up.

ROM v13 has three instances of malware detected by Malwarebytes, I deleted them safely with Solid Explorer .

Ant keyboard, priv-app/135.apk, and pupadware.adpush.

I have been having ads on apps I use everyday like aldiko and mortplayer and I think the cubot ROM may be responsible. Certainly after a restart they are absent.
[Device Reviews and Information] xplorr:
I downgraded from ROM V15 to V13 and I am able to root now :) (I unticked preloader, recovery, cache and userdata to preserve my userdata)

About the malware apps: can you be more specific where to find these apps, cause I don't find these on my version of V13:

priv-app/135.apk, and pupadware.adpush.?
[Device Reviews and Information] Patxperia:
I'll try to upload a screenshot of malwarebytes.

This shows the location, and then you can search for the associated odex file.

It would be interesting if a copy of v13 was significantly different when my download was this week.

SUCCESS. It's uploaded. Love the phone, I got antutu score 35,500 on v13. But I haven't yet cracked off the plastic case, and it's edges are sharp! It won't come off easily.
[Device Reviews and Information] xplorr:
Thx.

I have dowloaded my V13 version from: https://docs.google.com/uc?id=0B1KB17RxflpzRXl1VUxla2FKckk&export=download

The case is indeed a designflaw. With a dremel/grinder tool, I have rounded off the edges of the case. They are to sharp.

Now it can easily be removed and doesn't hurt my fingers anymore. Just grind of 1 mm or so and afterwards use the cotton grinder to polish the edges smooth.
[Device Reviews and Information] xplorr:
135.apk seems to be Sin_batterys_service=com.sin.batterys.service: no idea what it is meant for and if you can delete it. But I didn't delete it.
[Device Reviews and Information] Patxperia:
I kept the 135.apk on file just in case, but my battery Master and android battery stats in settings are working fine.

Did you find the other files on v13?

I downloaded v13 from needrom.
[Device Reviews and Information] xplorr:
Yes the 3 apk's you mentioned are in my version as well.

Other question: can you get MTK Droid tools v2.5.3 working on your phone?

You need it to translate a backup you make with SP Flash Tool into the different blocks again for later restore.

I can make the backup with SP Flash tool, but can't translate the ROM_0 into the different blocks.

Reason is that MTK Droid tools v2.5.3 won't recognize my phone when connected.

I read somewhere that MTK Droid tools does not support 64 bit processors like 6735.

Also the adb from MTK Droid tools v2.5.3 does not connect, but I found another adb that can connect, but this version won't work with MTK Droid tools v2.5.3. If you find a solution let me know. (Although I can also do a backup from within TWRP, I prefer an offline backup on my pc)
[Device Reviews and Information] Patxperia:
As I used a Linux version of sp-flash tool I didn't see this tool. I'll look for it as there may be a desktop back up available.

Currently I made one backup to my sdcard. I'll have to test it.

Have you tried antutu? I was surprised, the score went from v5 unrooted, 23,400, to v13 rooted, 33,540.

My xperia m4 is supposed to be faster, running at 1.5 Ghz but the score for what its worth is 28,899

If only I had 16gb ram on Sony xperia I'd not be replacing it, as its a capable phone with a nice GUI. Pity that takes up 6gb of the 8gb I have to play with.
[Device Reviews and Information] xplorr:
Indeed, I also have about 33500 Antutu score. That is amazing isn't it. I read somewhere that a 6753 might have a higher Antutu score with 8 cores, but since most apps don't cope with multi-cores the user-experience is even better on a 6735 because the power is divided between only 4 cores. And is more battery-efficient.

Also the phone has a premium build. It is so thin an amazingly well crafted. High-end quality at a low price (I bought it for 119 USD 2 weeks ago).

The screen is so clear, sharp and bright and the colors remind me of an amoled screen. Only weakness: no compass and speaker sound could be better, but the camera is great!
[Device Reviews and Information] Patxperia:
Yes, the phone is like a sliver of glass, colour saturated as I like the vivid setting. I loved the nexus 4 but that was far more chunky.

The headphone output is very clear, no buzz or distortion.

I play it headphone out, on a mono speaker when I want to listen to music, as I hate the built in speaker

I paid £81 on eBay brand new, and one year warranty return to China. Cubot has the 4g for all UK bands. Unlike Xiaomi, Meizu et al.
[Device Reviews and Information] xplorr:
That is a great price! What shop did you buy? Did you have to pay customs?

Other question: I cannot get to work any of the "call recording" apps. I have no idea why. On my old Samsung they work perfect. Not so on the Cubot. It seems the apps don't get access to the call information or don't get triggered to start recording. Any clue? Perhaps changing security as root?
[Device Reviews and Information] Patxperia:
The seller is on ebay, they change trading names all the time but ebay keeps track by id. I looked at auction of the phone located in UK, and no one else bid. The seller sent it to me and I received it within one business day. Very happy with the transaction. No import duties as it is within EU.

There is sound recording app in the ROM, haven't tried it yet.

I got the hard case off without scratching it, now I use a pouch which fits it well from Amazon. £4.99 for leatherette.
[Device Reviews and Information] xplorr:
Call recording now works after rooting on version 13 (Did not work on unrooted v15). :)

---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------

I noticed that many apps cannot write to the external SD card.

As you might be knowing, from Android 4.4 and higher, Google has slightly modified the default permissions for the external SD Card. Now it is accessible for writing only by a special user group of members called media_rw.

When some process needs to write to external media, it requests the appropriate permission. This was the usual behavior in earlier versions of Android. However, third-party apps have no access to that permission! So, there is no way for them to obtain write access to the external SD Card. You might face various issues with the new access rules, i.e. your favorite File manager can stop working. Here's how to give these apps the correct permission.

Launch your favorite file manager with root access rights.

Navigate to the following file:

/system/etc/permissions/platform.xml

Take a backup of this file.

Find android.permission.WRITE_EXTERNAL_STORAGE and android.permission.WRITE_MEDIA_STORAGE lines.

Modify them as follows:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[B] <group gid="media_rw" />[/B]
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="sdcard_rw" />
[B] <group gid="media_rw" />[/B]
</permission>

Save the platform.xml file. It’s necessary to set the file permissions to 644 (rw-/r–/r–) before mobile restarting.

Now reboot your Android device.

Problem solved.
[Device Reviews and Information] Patxperia:
I notice that Solid Explorer (my preference) asks for permission to access the sdcard after a firmware update. Maybe they found a workaround. What a major omission for android in not supporting external memory. Does marshmallow correct this?
[Device Reviews and Information] xplorr:
In Android 4 and 5 Google has restricted access to external SD cards. Apps should request the user to access it, when they are programmed well.

Older apps (or apps from app-builders that have forgotten this) do not get access to the card, because they didn't ask for it.

I read somewhere that Google has loosened security at that point in the newest Android. (I believe it was ridiculous to do so in the first place, it reminds me of the plague within Microsoft Vista of asking every action to the end-user).

My post above frees the SD card to "non-conform" apps.
[Device Reviews and Information] xplorr:
Could you do me a favor and check what is the value for your default "install-location".

You can get it by typing (fi. using the app Terminal Emulator for Android or within TWRP):

pm get-install-location

It can be either:

0 [auto]: Lets system decide the best location

1 [internal]: Installs on internal device storage

2 [external]: Installs on external media

I changed the value without first checking the previous value. :o
[Device Reviews and Information] Patxperia:
Sorry I've been out of signal for a few days , a walking holiday in Wales.

Terminal command With root in twrp gave me

sh: not found
[Device Reviews and Information] gipas69:
Trojan/malware found on ROM V15.

Hello XDA forum member,

I'm new to this forum and I'm posting to solve a problem with my X16.

I'm an owner of a Cubot X16 since february and considering the price I paid for this phone (around 110 €) I've been quite satisfied until I upgraded to the official rom V15 via OTA.

Since then, apart fro the known issues casued by battery master, I've found two malware/trojan installed in this Rom : AntBeydord.apk and operaService.apk; could someone check if also the V13 Rom is affected by the presence of this two malwasre files? I've found them by doing a scan with malwarebytes.

Many thanks in advance.:)

Regards.
[Device Reviews and Information] xplorr:
If you read the thread above you will notice that V13 has the same "trojans" (possibly false positives).
[Device Reviews and Information] Patxperia:
Anything else I can try? Post #62 for last test
[Device Reviews and Information] xplorr:
Thanks to reply again!

Strange that you get the notice in twrp:

sh: not found

When typing:

pm get-install-location

You can also (temporarily) install "Terminal Emulator for Android" (https://play.google.com/store/apps/details?id=jackpal.androidterm)

You don't even need to "su" (root) to type this command.

I just tested it a moment ago.
[Device Reviews and Information] Patxperia:
Terminal emulator works!

result is

0[auto]
[Device Reviews and Information] Patxperia:
On a rooted ROM v13 with their own screen protector I am getting intermittent touch failure. I have to move the link up the screen to get it to work. I ordered another protection just in case I applied it badly, but its an invisible air bubble if so!
[Device Reviews and Information] xplorr:
I don't see the point why you would use a screen protector, if the screen is Gorilla Glass ... and in ads they hit the keyboard with a hammer, crack nuts with it, cut it with a cutter, with carkeys,.... If this is all true, why use a screenprotector?
[Device Reviews and Information] Patxperia:
Odd isn't it.

But the reason for a protector is to take the stress of a fall. Glass is more prone to cracking than plastic, two layers of glass less so.

Before I put it on the fingerprints looked gross and hard to remove, now I can wipe it off with a soft cloth. Due the curved screen, the protector is millimetres short of the touchscreen. That may explain one kind of touch failure. Maybe grease may affect contact as well. I had similar problems on the xperia m4 til I got a good brand of glass protector.
[Device Reviews and Information] Patxperia:
[MENTION=1661434]xplorr[/MENTION] have yougot the driver you need for the mtk tools? I found a video on the official site which has a walkthrough. http://mtktools.com/

I am going to install it on a w7 pro laptop just to test back up.

Is Cubot ROM AOSP or is it skinned?
[Device Reviews and Information] xplorr:
You can find all info about drivers here:

http://xdaforums.com/showpost.php?p=64093232&postcount=8

You need MTK Droid tools v2.5.3.

But this tool uses adb and the adb included does not work with cubot, so I used another adb version, but this is incompatible with MTK Droid tools v2.5.3.

Conclusion: I can use adb, but cannot use MTK Droid tools v2.5.3.

You need MTK Droid tools v2.5.3 to translate the backup you make with SP Flash tool.

Perhaps you can get it working.

AFIK the android on the Cubot is almost stock ROM.
[Device Reviews and Information] Patxperia:
So I can avoid the driver issue, and have a way of storing these huge files on my laptop until I'm ready to twerp restore from sd card.

I'll use dd to copy the twrp nandroid and perhaps create an image.

The img could be installed as a rom with sp flash tool, but I wouldn't chance using the standard scatter file. I think flashify would work.

I'm going to try a Xperia home screen that can be used on aosp, lollipop and cm roms.
[Device Reviews and Information] xplorr:
I have installed APEX Launcher, which allows me to have more icons on one page (the Cubot ROM allows coexistence of different launchers, without rooting).

About TWRP backup: how to move the large backup images from SD Card to PC? Can you move them back to SD when needed?
[Device Reviews and Information] Patxperia:
I use dd terminal command to copy the nandroid files, and another to create an image.

I will test how effective it is to transfer back to the phone storage. Will the restore work?

I found twrp backup defaults to phone storage, at data/media/0/TWRP which can be accessed by pc once you identify the disk number.

This is possible for a rooted phone. You can also just copy to external drive or sdcard and copy to your pc for backup. I use solid Explorer which takes 5 minutes to transfer 5gb from phone to sdcard
[Device Reviews and Information] xplorr:
The camera-app on the Cubot X16 does not have the option to assign one of the hardware buttons as shutter (volume up/down or power).

Anybody have a clue how to do this without installing an app that has to run in the background?

I prefer altering .xml or config files and/or modifying the app and reinstalling the modified app.
[Device Reviews and Information] jakeythesnake:
Nice walkthrough, antigag.

The link you specified to the USB drivers is down at the moment - I found a mirror here if anyone needs. However, these didn't work for me, so I googled "MT6735 USB driver" and found a link to these: https://www.androidfilehost.com/?fid=24438995911972499. They have a weird installer, but I took a punt, and they worked fine and allowed me to flash TWRP Recovery.

I've taken the liberty of creating a Google Drive mirror for all of the things required: https://drive.google.com/folderview?id=0B6hF1sItcxw7dlRTNGhjQTRHbTA&usp=sharing.
[Device Reviews and Information] kaja008:
Hi!

I have problems with my Cubot X16.

I can only charge the phone when it is switched off. Is it a problem of battery or software related?

I already tried with another USB cable/adapter, but the problem is still the same.

Is there any solution?

brgds,

kaja008